WO2013102316A1 - 响应触发信息的方法、系统和mtc用户设备 - Google Patents

响应触发信息的方法、系统和mtc用户设备 Download PDF

Info

Publication number
WO2013102316A1
WO2013102316A1 PCT/CN2012/071360 CN2012071360W WO2013102316A1 WO 2013102316 A1 WO2013102316 A1 WO 2013102316A1 CN 2012071360 W CN2012071360 W CN 2012071360W WO 2013102316 A1 WO2013102316 A1 WO 2013102316A1
Authority
WO
WIPO (PCT)
Prior art keywords
trigger information
mtc
user equipment
network node
node device
Prior art date
Application number
PCT/CN2012/071360
Other languages
English (en)
French (fr)
Inventor
许辉
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2013102316A1 publication Critical patent/WO2013102316A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/70—Services for machine-to-machine communication [M2M] or machine type communication [MTC]

Definitions

  • the present invention relates to wireless communication technologies, and more particularly to a method, system and machine type communication (MTC) user equipment responsive to trigger information.
  • MTC machine type communication
  • M2M Machine to Machine
  • M2M business appeared on the market and developed rapidly in the following years, becoming the focus of many communication equipment vendors and telecom operators. At present, the number of machines in the world is much larger than that of people, so it is possible to foresee the good market prospects of M2M technology.
  • the existing mobile communication networks are mainly designed for communication between people, and the communication between machines and machines, people and machines is insufficiently optimized.
  • how operators can provide M2M communication services at low cost is also the key to the successful deployment of M2M communication.
  • the solution should maximize the reuse of existing networks, reduce the impact of a large number of M2M communications on the network, and the complexity of operation and maintenance.
  • MTC Machine Type Communication
  • H2H Human to Human
  • MTC Machine to Machine and Machine
  • QoS quality of service
  • business model and other aspects are very different from the current H2H communication mode.
  • the EPS includes a radio access network (such as a UMTS (Universal Terrestrial Radio Access Network), an evolved UTRAN (E-UTRAN, Evolved UTRAN).
  • UMTS Universal Terrestrial Radio Access Network
  • E-UTRAN evolved UTRAN
  • GSM/EDGE Radio Access Network GSM/EDGE Radio Access Network
  • the core network such as the Mobile Management Entity (MME) and the Serving Gateway in the Evolved Packet Core (EPC) a network element such as a packet data network (PDN) gateway (PGW, PDN Gateway), including a network element such as a serving general packet radio service support node (SGSN) in the GPRS core network; and an evolved node B in the E-UTRAN (eNB, evolved Node B).
  • PDN packet data network gateway
  • SGSN serving general packet radio service support node
  • eNB evolved Node B
  • MTC user equipment trigger (Device Trigger) is one of the basic requirements for the MTC system.
  • the problem of this requirement is that in order to control the communication of the MTC user equipment, the polling method initiated by the MTC server (Server) can be adopted.
  • the MTC server For communication, for the communication initiated by the MTC user equipment, the MTC server is sometimes required to pop data from the MTC user equipment. If the MTC server query fails or the IP address of the MTC user equipment is unavailable, the MTC server can use the MTC user equipment trigger to establish communication with the MTC user equipment. If the network cannot trigger the MTC user equipment, it reports to the MTC server that the MTC user equipment trigger fails, and the MTC user equipment trigger is implemented in 3GPP through control plane signaling.
  • MTC user equipment triggers include mobile calling (MO, Mobile Originated) and mobile being Called (MT, Mobile Terminating) service, that is, the MTC user equipment sends or receives information.
  • MO Mobile Originated
  • MT Mobile Terminating
  • the proposed solution includes: sending the MTC user equipment trigger information through the SMS SMS, or sending the MTC user equipment trigger information through the control plane signaling.
  • the MTC server sends control plane signaling including the trigger information of the MTC user equipment to the network node, and the network node parses and processes the trigger information of the MTC user equipment in the control plane signaling. Then, the MTC user equipment trigger information is sent to the user equipment (UE, User Equipment).
  • UE User Equipment
  • the MTC architecture in 3GPP is shown in Figure 1.
  • the MTC application device Application
  • the MTC user User
  • GGSN Gateway GPRS Support Node
  • MTC server communicates with GGSN/PGW/EPDG through MTCi interface; GGSN/PGW/EPDG through Radio Access Network (RAN) and user Device (UE) communication;
  • MTC server sends control plane signaling including MTC user equipment trigger information to the MTC-Interface function (MTC-IWF, MTC InterWorking Function) through the MTCsp interface or to the short message service-service center through the MTCsms interface ( SMS-SC, Short Message Service- Service Centre) / IP Short Message Gateway (IP-SM-GW, IP-Short-Message-Gateway) sends control plane signaling including MTC user equipment trigger information, MTC-IWF or SMS-
  • the SC/IP-SM-GW sends control plane signaling to the MME/SGSN or SMS Service-Mobile Service Switch Center (SMS-GMSC, Gateway MSC For Short Message Service)
  • SMS-GMSC
  • FIG. 2 is a schematic diagram of the MTC server transmitting control plane signaling including the trigger information of the MTC user equipment through the MTC-IWF, where the MTC server directly sends the control plane signaling including the trigger information of the MTC user equipment to the MTC-IWF, MTC through the MTCsp interface.
  • the -IWF sends trigger information to the MTC user equipment through the MME/SGSN.
  • the MTC user equipment After receiving the trigger information, the MTC user equipment can communicate with the MTC server according to the indication of the trigger information, such as establishing a user plane bearer, or communicating with the MTC server through SMS or the like.
  • the main object of the present invention is to provide a method, system and MTC user equipment for responding to trigger information, which can implement a response to a trigger message in a 3GPP network.
  • a method of responding to trigger information including:
  • the network node device After receiving the trigger information from the machine type communication MTC server, the network node device forwards the trigger information to the corresponding MTC user equipment;
  • the network node device determines that the trigger information forwarding fails, and reports a trigger information failure message to the MTC server.
  • the method further includes:
  • the MTC user equipment After successfully receiving the trigger information, the MTC user equipment returns a trigger information receiving response message to the network node device;
  • the network node device forwards the trigger information receiving response message to the MTC server.
  • the network node device determines that the trigger information forwarding fails: the network node device does not find the registration information or routing information of the corresponding MTC user equipment, or the network node device forwards the trigger message, and presets The trigger information receiving response message from the corresponding MTC user equipment is not received within the valid time.
  • the trigger information failure message includes one or more of the following: an MTC user equipment identifier in the trigger information, a trigger information count, and a trigger failure reason.
  • the method also includes:
  • the MTC server determines whether to resend the corresponding trigger information according to the received trigger information failure message or the trigger information receiving response message.
  • the method further includes: the network node device does not receive the trigger information receiving response message from the corresponding MTC user equipment within a preset retransmission time, Sending the trigger information, where the retransmission time is not greater than the preset valid time.
  • the trigger information receiving response message is sent by SMS SMS or control plane signaling.
  • the network node device includes one or more of the following: a machine type communication interconnection function
  • MTC-IWF home subscriber server HSS/home location register HLR, short message service SMS-service center SC, mobility management entity MME/general packet radio service support node SGSN.
  • a system for responding to trigger information comprising: an MTC server, a network node device; wherein, the MTC server is configured to send trigger information to the network node device;
  • the network node device is configured to: after receiving the trigger information from the MTC server, forward the trigger information to the corresponding MTC user equipment; and report the trigger information failure message to the MTC server when determining that the trigger information fails to be forwarded .
  • the system also includes MTC user equipment,
  • the MTC user equipment is configured to: after successfully receiving the trigger information, return a trigger information receiving response message to the network node device;
  • the network node device is further configured to forward the trigger information receiving response message from the MTC user equipment to the MTC server.
  • the MTC server is further configured to determine whether to resend the corresponding trigger information according to the received trigger information failure message or the trigger information receiving response message.
  • the network node device is further configured to resend the corresponding trigger information when the trigger information receiving response message from the MTC user device is not received within the preset retransmission time.
  • the network node device includes one or more of the following: MTC-IWF, HSS/HLR, SMS-SC, MME/SGSNo
  • An MTC user equipment comprising: a receiving unit, a setting unit, and a sending unit; wherein the receiving unit is configured to receive trigger information from a network node device;
  • the setting unit is configured to: after the trigger information receiving unit successfully receives the trigger information, set a trigger information to receive a response message content;
  • the sending unit is configured to return a trigger information receiving response message set by the setting unit to the network node device.
  • the present invention provides a method, a system, and an MTC user equipment, in response to the trigger information, after receiving the trigger information from the MTC server, the network node device forwards the trigger information to the corresponding MTC user equipment; the network node device determines the trigger If the information forwarding fails, a trigger information failure message is reported to the MTC server.
  • the transmission of the trigger response information can be implemented by the present invention, thereby determining the content of the trigger response information and the processing flow of the trigger response information.
  • FIG. 1 is a schematic diagram of an MTC architecture in 3GPP in the prior art
  • FIG. 2 is a schematic diagram of control plane signaling in which an MTC server sends trigger information through an MTC-IWF in the prior art
  • FIG. 3 is a schematic flowchart of a method for implementing a trigger response according to an embodiment of the present invention
  • FIG. 4 is a schematic structural diagram of a system for implementing a trigger response according to an embodiment of the present invention
  • FIG. 5 is a schematic structural diagram of an MTC user equipment that implements a trigger response according to an embodiment of the present invention
  • FIG. 6 is a schematic flowchart of a method for implementing a trigger response according to Embodiment 1 of the present invention.
  • FIG. 7 is a schematic flowchart of a method for implementing a trigger response according to Embodiment 2 of the present invention.
  • FIG. 8 is a schematic flowchart of a method for implementing a trigger response according to Embodiment 3 of the present invention.
  • FIG. 9 is a schematic flowchart of a method for implementing a trigger response according to Embodiment 4 of the present invention.
  • the basic idea of the present invention is: after receiving the trigger information from the MTC server, the network node device forwards the trigger information to the corresponding MTC user equipment; and the network node device determines that the trigger information fails to be forwarded, and reports to the MTC server. Trigger message failure message.
  • FIG. 3 is a schematic flowchart of a method for responding to trigger information according to an embodiment of the present invention. As shown in FIG. 3, the method includes:
  • Step 301 The MTC server sends trigger information to the network node device.
  • the MTC server sets the trigger information content, and sends the trigger information to the network node device.
  • the network node device is generally located in the 3GPP network, and may be any one or more of the following: MTC-IWF, HSS/ HLR, SMS-SC, MME/SGSN.
  • Step 302 After receiving the trigger information, the network node device forwards the trigger information to the corresponding MTC user equipment.
  • the network node device processes the received trigger information, and searches for routing information of the MTC user equipment according to the identifier of the MTC user equipment carried therein.
  • the network node device can forward the trigger information directly to the MTC user equipment, or forward it through other network nodes.
  • Step 303 it is determined whether the trigger information is successfully forwarded, if yes, then go to step 304, otherwise, go to step 305;
  • the success of the forwarding trigger information refers to: the network node device finds the way of the MTC user equipment.
  • the trigger information is sent to the MTC user equipment (received by the trigger information received from the MTC user equipment) by the information and within the set validity time.
  • the processing trigger information unsuccessful may be any of the following situations: The network node device does not find the registration information or routing information of the MTC user equipment, the network node device processes the trigger information beyond the valid time, and the like.
  • the reason for the network node device processing timeout may be network congestion or overload.
  • Step 304 The MTC user equipment receives the trigger information, and sends a trigger information receiving response message to the MTC server, and the process ends.
  • the MTC user equipment generally needs to send a trigger information receiving response message to the MTC server through the network node device.
  • Receiving the trigger information by the MTC user equipment means that the MTC user equipment correctly receives the trigger information; the receiving response message may be sent by using SMS SMS or control plane signaling.
  • the MTC user equipment may determine the next action according to the indication of the trigger information and its own capability, such as: establishing a user plane bearer with the MTC server, or waiting for the MTC server to send other information, or collecting the MTC user. Device status, and more.
  • the network node device does not receive the trigger information receiving response message from the corresponding MTC user equipment in the preset retransmission time, the trigger information is resent, and the retransmission time is not greater than the preset validity. time.
  • Step 305 The network node device reports a trigger information failure message to the MTC server, and the process ends.
  • the network node If the network node does not successfully send the trigger information within the valid time, the network node sends a failure message for receiving the trigger information to the MTC server;
  • the trigger information failure message may include one or more of the following: an MTC user equipment identifier in the trigger information, a trigger information count, a trigger failure reason, and the like.
  • the MTC server can also fail the message or touch according to the received trigger information. Sending a message to receive a response message to determine whether to resend the corresponding trigger information. After receiving the trigger information failure message, the MTC server may resend the trigger information.
  • the trigger information count can be used to distinguish trigger information sent to different MTC user devices and/or different content.
  • the embodiment of the present invention further provides a system for responding to trigger information.
  • the system includes: an MTC server 41, a network node device 42, and an MTC user device 43;
  • the MTC server 41 is configured to send trigger information to the network node device 42;
  • the network node device 42 is configured to: after receiving the trigger information from the MTC server 41, forward the trigger information to the corresponding MTC user equipment 43; and report the trigger information to the MTC server 41 when determining that the trigger information fails to be forwarded. Failure message.
  • the MTC user equipment 43 is configured to return a trigger information receiving response message to the network node device 42 after successfully receiving the trigger information;
  • the network node device 42 is further arranged to forward the trigger information reception response message from the MTC user equipment 43 to the MTC server 41.
  • the MTC server 41 is further configured to decide whether to resend the corresponding trigger information according to the received trigger information failure message or the trigger information reception response message.
  • the network node device 42 is further configured to resend the corresponding trigger information when the trigger information receiving response message from the MTC user device 43 is not received within the preset retransmission time.
  • the network node device 42 includes one or more of the following: MTC-IWF, HSS/HLR, SMS-SC, MME/SGSN.
  • the embodiment of the present invention further provides an MTC user equipment.
  • the MTC user equipment includes: a receiving unit 51, a setting unit 52, and a sending unit 53.
  • the receiving unit 51 is configured to receive from the network. Trigger information of the node device;
  • the setting unit 52 is configured to: after the trigger information receiving unit successfully receives the trigger information, Setting the trigger information to receive the response message content;
  • the sending unit 53 is configured to return the trigger information receiving response message set by the setting unit to the network node device.
  • the following embodiment assumes that the MTC trigger information is sent by the MTC-IWF in the control plane signaling manner.
  • the MTC trigger information can also be selected to be sent by SMS SMS.
  • the trigger information and response information are implemented by using the existing SMS technology.
  • This example implements a method for the MTC user device to trigger a response in the scenario where the trigger information is successfully sent to the MTC user device. As shown in FIG. 6, the method includes the following steps:
  • Step 601 The MTC server sends trigger information to the MTC-IWF.
  • the MTC server sets the content of the trigger information, and searches for the corresponding MTC-IWF through the MTC user equipment identifier, and sends the trigger information to the MTC-IWF.
  • the MTC server sends the MTC user equipment trigger information to the MTC-IWF through the MTCsp interface;
  • Step 602 The MTC-IWF forwards the triggering message to the MME/SGSN corresponding to the MTC user equipment, and the MTC-IWF queries the corresponding HSS/HLR according to the external identifier of the MTC user equipment in the trigger information, and queries the MTC user equipment by using the HSS/HLR.
  • the internal identifier is used to change the MTC user equipment external identifier in the MTC user equipment trigger information to the 3GPP network internal identifier IMSI, and obtain the MME/SGSN registered by the MTC user equipment through the HSS/HLR query; where, the MTC-IWF and the HSS/ A communication interface is established between the HLR, the MTC-IWF and the MMS/SGSN.
  • Step 603 The MME/SGSN sends the MTC user equipment trigger information to the target user equipment, where the MTC user equipment trigger information passes an ongoing signaling connection, or a paging message, Or broadcast message transmission; the signaling connection may be a dedicated NAS message;
  • Step 604 The MTC user equipment receives the trigger information, and sends a trigger information receiving response message to the MME/SGSN.
  • the MTC user equipment sets the content of the trigger response message, and the trigger response message includes: an MTC user equipment identifier, a trigger information count, and the like.
  • the MTC user equipment establishes application layer communication with the MTC server according to the address and port information of the MTC server in the trigger information content.
  • Step 605 The MME/SGSN forwards a trigger information receiving response message to the MTC-IWF.
  • the MME and the SGSN may send a trigger information response message to the MTC-IWF at the same time or separately.
  • Step 606 The MTC-IWF forwards the trigger information response message to the MTC server, and the process ends;
  • the MTC-IWF sends a trigger response message to the MTC server through the MTCsp interface.
  • Example 2
  • the method for triggering the MTC user device to trigger the MTC user device to trigger the response of the MTC user device includes the following steps:
  • Step 701 The MTC server sends trigger information to the MTC-IWF.
  • This step is the same as step 601 and will not be described here.
  • Step 702 the MTC-IWF processes the trigger information, determines whether there is routing information of the MTC user equipment, and if so, proceeds to step 703, otherwise, proceeds to step 705;
  • the processing trigger information includes: querying, by the HSS/HLR, the routing information and the internal identifier of the MTC user equipment, determining whether the valid time expires, and the like;
  • the routing information refers to the information of the MME/SGSN corresponding to the MTC user equipment.
  • Step 703 The MTC-IWF forwards the trigger information to the MTC user equipment.
  • the MTC-IWF forwards the trigger information to the MTC user equipment by using the MME/SGSN corresponding to the MTC user equipment.
  • Step 704 The MTC user equipment receives the trigger information, sends a trigger response message to the MTC server, and the process ends.
  • the MTC user equipment sets the content of the trigger response message and sends the content to the network node device.
  • the MTC server sends a trigger response message; the content of the trigger response message includes: an MTC user equipment identifier, a trigger information count, and the like.
  • Step 705 the MTC-IWF determines whether the valid time expires, and if so, proceeds to step 706, otherwise proceeds to step 702;
  • the valid time is indicated in the trigger information. If network congestion or node overload occurs, the trigger information needs to be buffered in the MTC-IWF, and the time for buffering the trigger information cannot exceed the valid time of the trigger information.
  • Step 706 The MTC-IWF sends a trigger failure message to the MTC server, and the process ends.
  • the MTC-IWF sets the content of the trigger failure message, including: the MTC user equipment identifier in the trigger information, the trigger information count, the trigger failure reason, and the like;
  • the MTC-IWF sends a trigger failure message to the MTC server through the MTCsp interface.
  • the MTC-IWF sends a trigger failure message
  • the locally stored trigger message is deleted.
  • This embodiment is directed to a method for triggering an MTC user equipment to trigger a response in an MME/SGSN, and the MTC user equipment triggers a response. As shown in FIG. 8, the method includes the following steps:
  • Step 801 The MTC server sends trigger information to the MTC-IWF.
  • This step is the same as step 601 and will not be described here.
  • Step 802 The MTC-IWF forwards the trigger message to the MME/SGSN corresponding to the MTC user equipment. This step is the same as step 602, and details are not described herein again.
  • Step 803 the MME / SGSN processes the trigger information, determines whether there is MTC user equipment registration information, and if so, proceeds to step 804, otherwise proceeds to step 806;
  • the device registration information refers to that the MTC user equipment registers in the MME/SGSN during the attach attach process
  • the current MME/SGSN cannot find the registration information of the MTC user equipment.
  • Step 804 The MME/SGSN sends trigger information to the MTC user equipment.
  • This step is the same as step 603 and will not be described here.
  • Step 805 The MTC user equipment that receives the trigger information sends a response to receive the trigger information to the MTC server, and the process ends.
  • the MTC user equipment sets the content of the trigger response message, and sends a trigger response message to the MTC server through the network node device;
  • the trigger response message content includes: an MTC user equipment identifier, a trigger information count, and the like.
  • Step 806 the MME / SGSN determines whether the valid time expires, and if so, proceeds to step 807, otherwise proceeds to step 803;
  • the valid time is indicated in the trigger information. If network congestion or node overload occurs, the trigger information needs to be buffered in the MME/SGSN, and the time for buffering the trigger information cannot exceed the valid time of the trigger information.
  • the MME/SGSN determines that the valid time expires, indicating that the trigger fails; the valid time does not expire.
  • the MME/SGSN may resend the locally stored trigger information
  • Step 807 The MME/SGSN sends a trigger failure message to the MTC-IWF.
  • the MME/SGSN deletes the locally stored trigger information, and sends a trigger failure message to the MTC-IWF;
  • the trigger failure message includes: an MTC user equipment identifier, a trigger information count, a failure reason, and the like.
  • Step 808 The MTC-IWF sends a trigger failure message to the MTC server, and the process ends.
  • the MTC-IWF receives the trigger failure message sent by the MME/SGSN, and the valid time at the MME/SGSN times out, indicating that the MTC-IWF has also timed out, the MTC-IWF has deleted the corresponding trigger information, and the MTC-IWF sends the MTC-IWF to the MTC server. Trigger a failure message;
  • the trigger failure message includes: an MTC user equipment identifier, a reason for failure, and the like.
  • This embodiment is directed to a method for triggering an MTC user equipment to trigger a response on an MTC user equipment to trigger a response of the MTC user equipment. As shown in FIG. 9, the method includes the following steps:
  • Step 901 The MTC server sends trigger information to the MTC-IWF.
  • This step is the same as step 601 and will not be described here.
  • Step 902 The MTC IWF forwards the triggering message to the MME/SGSN corresponding to the MTC user equipment, which is the same as step 602, and is not described here.
  • Step 903 The MME/SGSN sends the trigger information to the MTC user equipment.
  • This step is the same as step 603 and will not be described here.
  • Step 904 the MTC user equipment determines whether the trigger information is correctly received, and if so, proceeds to step 905, otherwise proceeds to step 906;
  • the reason why the MTC user equipment cannot correctly receive the trigger information includes: the MTC user equipment is full of memory, the MTC user equipment is faulty, and the like.
  • Step 905 The MTC user equipment sends a trigger information receiving response message to the MTC server, and the process ends.
  • the MTC server sets the content of the trigger response message by the MTC user equipment, and
  • the MTC server sends a trigger response message;
  • the content of the trigger response message includes: an MTC user equipment identifier, a trigger information count, and the like.
  • Step 906 The MTC user equipment sends a trigger failure message to the MME/SGSN.
  • the MTC user equipment sends a trigger failure message to the MME/SGSN by using control plane signaling, or a short message.
  • Step 907 the MME / SGSN determines whether the local trigger information is timed out, and if so, proceeds to step 908, otherwise proceeds to step 903;
  • This step is the same as step 806, and is not described here.
  • Step 908 The MME/SGSN sends a trigger failure message to the MTC-IWF.
  • This step is the same as step 807, and is not described here.
  • Step 909 The MTC-IWF sends a trigger failure message to the MTC server, and the process ends. This step is the same as step 808, and is not described here.

Abstract

本发明公开了一种响应触发信息的方法，包括：网络节点设备收到来自机器类通信（MTC）服务器的触发信息后，向相应的MTC用户设备转发所述触发信息；网络节点设备判定所述触发信息转发失败，则向所述MTC服务器报告触发信息失败消息。本发明还相应地公开了一种响应触发信息的系统及MTC用户终端。通过本发明，能够实现触发响应信息的发送，从而确定了触发响应信息的内容和对触发响应信息的处理流程。

Description

响应触发信息的方法、 系统和 MTC用户设备 技术领域
本发明涉及无线通信技术， 尤其涉及一种响应触发信息的方法、 系统 和机器类型通信 (MTC)用户设备。 背景技术
M2M ( Machine to Machine )指机器之间建立连接的所有技术和手段。 M2M 理念在上个世纪九十年代就出现了， 但是只停留在理论阶段。 2000 年以后， 随着移动通信技术的发展， 以移动通信技术实现机器设备的联网 成为可能。 2002年左右 M2M业务就在市场上出现， 并在随后的几年迅速 发展， 成为了众多通信设备商和电信运营商的关注焦点。 目前全球的机器 数量比人的数量要多很多， 因此可以预见到 M2M技术的良好的市场前景。
对 M2M通信应用场景研究表明在移动网络上提供 M2M通信具有潜在 的市场前景。但 M2M业务对系统提出了很多新的要求， 为了增强移动网络 在这方面的竟争力， 有必要对现有的移动网络进行优化， 来更有效的支持 M2M通信。
现有的移动通信网络主要针对人与人的通信进行设计， 而对机器与机 器，人与机器的通信则优化不足。此外，运营商如何能够以低成本提供 M2M 通信服务， 也是 M2M通信部署成功的关键。
基于以上情况，有必要研究移动网络支持 M2M通信的解决方案，解决 方案要最大限度重用现有网络，降低大量 M2M通信对网络造成的影响以及 运营维护的复杂度。
目前电信市场竟争日趋激烈， 资费不断下降， 运营商利润空间不断减 小， 以人为基础的通信市场正在趋于饱和， M2M对运营商来说是全新的发 展机遇。
为了有效地利用移动网络资源， 第三代合作伙伴计划 （3GPP , 3rd Generation Partnership Project )提出了机器类型通信 ( MTC, Machine Type Communication ), 即机器^机器（ Machine to Machine )、机器 ^人 ( Machine to Man )进行通讯的业务，其业务范围远远超出了以往人对人（ H2H, Human to Human )之间的通讯， MTC在接入控制、计费、安全性、服务质量（QoS, Quality of Service )、业务模式等方面与现在的 H2H通讯模式有很大的区别。
3GPP演进分组系统（ EPS, Evolved Packet System )架构中， EPS包括 了无线接入网 （如 UMTS陆地无线接入网 （UTRAN, Universal Terrestrial Radio Access Network )、 演进的 UTRAN ( E-UTRAN, Evolved UTRAN )、 GSM/EDGE无线接入网络 ( GERAN, GSM/EDGE Radio Access Network ) ) 和核心网， 如在演进分组核心网 （EPC, Evolved Packet Core ) 中有移动管 理实体（MME )、 服务网关（ Serving Gateway )、 分组数据网 （PDN ) 网关 ( PGW, PDN Gateway )等网元， 在 GPRS核心网中包括服务通用分组无 线服务技术支持节点 （ SGSN )等网元； 在 E-UTRAN中包括演进的节点 B ( eNB , evolved Node B )。
MTC用户设备触发（ Device Trigger )是对 MTC系统的基本要求之一， 该要求所关注的问题是：为了控制 MTC用户设备的通信，可以采用由 MTC 服务器（ Server )发起轮询（poll )的方式进行通信， 对于 MTC用户设备发 起的通信，有时也需要 MTC服务器从 MTC用户设备 poll数据。如果 MTC 服务器查询失败或者 MTC用户设备的 IP地址不可用，则 MTC服务器可以 使用 MTC用户设备触发来与 MTC用户设备建立通信。 如果网络不能触发 MTC用户设备， 则向 MTC服务器报告 MTC用户设备触发失败， MTC用 户设备触发在 3GPP中通过控制面信令实现。
MTC用户设备触发包括移动主叫 （MO, Mobile Originated )和移动被 叫 （MT, Mobile Terminating )业务， 即包括 MTC用户设备发送或者接收 信息。
为了实现 MTC用户设备触发请求的有效传输， 已提出的方案包括： 通 过短信 SMS发送 MTC用户设备触发信息， 或者通过控制面信令发送 MTC 用户设备触发信息。对于通过控制面信令发送 MTC用户设备触发信息的方 式， MTC服务器发送包含 MTC用户设备触发信息的控制面信令到网络节 点， 网络节点将控制面信令中的 MTC用户设备触发信息解析处理， 然后发 送 MTC用户设备触发信息到用户设备 ( UE, User Equipment )。
3GPP中的 MTC架构如图 1所示， 在用户面， 连接 MTC用户 （ User ) 的 MTC应用设备 ( Application )通过 API接口与 MTC服务器通信， 或者 通过 Gi/SGi接口直接与 3GPP 网络中的网关 GPRS 支持节点 （ GGSN, Gateway GPRS Support Node ) /PGW/演进分组数据网关 （ EPDG )通信； MTC服务器通过 MTCi接口与 GGSN/PGW/EPDG通信； GGSN/PGW/EPDG 通过无线接入网 （RAN )与用户设备（UE )通信； 在控制面， MTC服务器 通过 MTCsp接口向 MTC互联功能（ MTC-IWF , MTC InterWorking Function ) 发送包含 MTC用户设备触发信息的控制面信令或通过 MTCsms接口向短信 业务-业务中心（ SMS-SC, Short Message Service- Service Centre ) /IP短信网 关（ IP-SM-GW, IP-Short-Message-Gateway )发送包含 MTC用户设备触发 信息的控制面信令， MTC-IWF或 SMS-SC/IP-SM-GW将控制面信令发送到 MME/SGSN 或短信业务-移动业务交换中心网关 （SMS-GMSC, Gateway MSC For Short Message Service )或短信业务路由器（ SMS Router )或移动 业务交换中心（ MSC, Mobile-services Switching Centre )或拜访位置寄存器 ( VLR ), 进而通过 RAN 发送到 UE; 其中， MME/SGSN 还可以通过 Gr/S6a/S6d接口从归属用户服务器（HSS, Home Subscriber Server )或归属 位置寄存器（ HLR, Home Location Register ) ( HSS/HLR )获得所述控制面 信令。
图 2为 MTC服务器通过 MTC-IWF发送包含 MTC用户设备触发信息 的控制面信令的示意图， 其中， MTC服务器通过 MTCsp接口直接发送包 含 MTC 用户设备触发信息的控制面信令到 MTC-IWF, MTC-IWF 通过 MME/SGSN发送触发信息到 MTC 用户设备。
MTC 用户设备收到触发信息后， 可以根据触发信息的指示， 与 MTC 服务器进行通信， 如建立用户面承载， 或者通过 SMS等和 MTC服务器通 信。
在对现有技术的研究和实践过程中发现现有技术存在以下问题： MTC 用户设备收到触发信息后， 需要向 MTC服务器发送触发信息接收响应消 息， 但是目前对于触发响应消息的内容和处理流程还没有解决方案。 发明内容
有鉴于此， 本发明的主要目的在于提供一种响应触发信息的方法、 系 统和 MTC用户设备， 能够实现 3GPP网络中对触发消息的响应。
为达到上述目的， 本发明实施例的技术方案是这样实现的：
一种响应触发信息的方法， 包括：
网络节点设备收到来自机器类通信 MTC服务器的触发信息后，向相应 的 MTC用户设备转发所述触发信息；
网络节点设备判定所述触发信息转发失败，则向所述 MTC服务器报告 触发信息失败消息。
所述网络节点设备向相应的 MTC用户设备转发所述触发信息后，该方 法还包括：
所述 MTC用户设备成功接收所述触发信息后，向所述网络节点设备返 回触发信息接收响应消息；
所述网络节点设备将所述触发信息接收响应消息转发给 MTC服务器。 所述网络节点设备判定所述触发信息转发失败为： 所述网络节点设备 没有查找到相应 MTC用户设备的注册信息或路由信息， 或者， 所述网络节 点设备转发所述触发消息后，在预设的有效时间内未收到来自相应 MTC用 户设备的触发信息接收响应消息。
所述触发信息失败消息包括以下一项或多项：触发信息中的 MTC用户 设备标识、 触发信息计数、 触发失败原因。
该方法还包括：
MTC服务器根据接收的触发信息失败消息或触发信息接收响应消息决 策是否重发相应的触发信息。
所述向相应的 MTC用户设备转发所述触发信息后， 该方法还包括： 所述网络节点设备在预设的重发时间内未收到来自相应 MTC 用户设 备的触发信息接收响应消息， 则重发所述触发信息， 所述重发时间不大于 所述预设的有效时间。
所述触发信息接收响应消息通过短信 SMS或控制面信令发送。
所述网络节点设备包括以下一种或多种： 机器类型通信互联功能
MTC-IWF, 归属用户服务器 HSS/归属位置寄存器 HLR、 短信业务 SMS-业 务中心 SC、 移动管理实体 MME/通用分组无线服务技术支持节点 SGSN。
一种响应触发信息的系统， 包括： MTC服务器、 网络节点设备； 其中， 所述 MTC服务器， 设置为向网络节点设备发送触发信息；
所述网络节点设备， 设置为在收到来自 MTC服务器的触发信息后， 向 相应的 MTC用户设备转发所述触发信息； 以及在判定所述触发信息转发失 败时， 向 MTC服务器报告触发信息失败消息。
该系统还包括 MTC用户设备，
所述 MTC用户设备， 设置为在成功接收触发信息后， 向网络节点设备 返回触发信息接收响应消息； 所述网络节点设备，还设置为将来自 MTC用户设备的触发信息接收响 应消息转发给 MTC服务器。
所述 MTC服务器，还设置为根据接收的触发信息失败消息或触发信息 接收响应消息决策是否重发相应的触发信息。
所述网络节点设备，还设置为在预设的重发时间内未收到来自 MTC用 户设备的触发信息接收响应消息时， 重发相应的触发信息。
所述网络节点设备包括以下一种或多种： MTC-IWF、 HSS/ HLR、 SMS- SC、 MME/SGSNo
一种 MTC用户设备， 包括： 接收单元、 设置单元和发送单元； 其中， 所述接收单元， 设置为接收来自网络节点设备的触发信息；
所述设置单元， 设置为在触发信息接收单元成功接收所述触发信息后， 设置触发信息接收响应消息内容；
所述发送单元， 设置为将设置单元设置的触发信息接收响应消息返回 网络节点设备。
本发明提供了一种响应触发信息的方法、 系统和 MTC用户设备， 网络 节点设备收到来自 MTC服务器的触发信息后， 向相应的 MTC用户设备转 发所述触发信息；网络节点设备判定所述触发信息转发失败，则向所述 MTC 服务器报告触发信息失败消息。 通过本发明能够实现触发响应信息的发送， 从而确定了触发响应信息的内容和对触发响应信息的处理流程。 附图说明
图 1为现有技术中 3GPP中的 MTC架构示意图；
图 2为现有技术中 MTC服务器通过 MTC-IWF发送触发信息的控制面 信令的示意图；
图 3为本发明实施例实现一种触发响应的方法的流程示意图； 图 4为本发明实施例实现一种触发响应的系统的结构示意图； 图 5 为本发明实施例实现一种触发响应的 MTC用户设备的结构示意 图；
图 6为本发明实施例 1实现触发响应的方法的流程示意图；
图 7为本发明实施例 2实现触发响应的方法的流程示意图；
图 8为本发明实施例 3实现触发响应的方法的流程示意图；
图 9为本发明实施例 4实现触发响应的方法的流程示意图； 具体实施方式
本发明的基本思想是： 网络节点设备收到来自 MTC服务器的触发信息 后， 向相应的 MTC用户设备转发所述触发信息； 网络节点设备判定所述触 发信息转发失败， 则向所述 MTC服务器报告触发信息失败消息。
图 3为本发明实施例响应触发信息的方法流程示意图， 如图 3所示， 该方法包括：
步驟 301 : MTC服务器向网络节点设备发送触发信息；
具体的， MTC服务器设置触发信息内容， 将所述触发信息发送到网络 节点设备， 这里， 所述网络节点设备一般位于 3GPP网络中， 可以为以下任 意一种或多种： MTC-IWF、 HSS/HLR、 SMS-SC、 MME/SGSN。
步驟 302, 网络节点设备收到所述触发信息后， 向相应的 MTC用户设 备转发所述触发信息；
所述网络节点设备对收到的触发信息进行处理， 如根据其中携带的 MTC用户设备的标识查找 MTC用户设备的路由信息。
网络节点设备可以直接向 MTC用户设备转发触发信息，也可以通过其 他网络节点进行转发。
步驟 303 ,判断所述触发信息是否转发成功，如果是， 则转向步驟 304, 否则， 转向步驟 305;
所述转发触发信息成功是指： 网络节点设备查找到 MTC用户设备的路 由信息， 并在设置的有效时间内将触发信息发送到 MTC用户设备 (收到来 自 MTC用户设备的触发信息接收响应消息）。
所述处理触发信息不成功可以是以下任意一种情况： 网络节点设备没 有查找到 MTC用户设备的注册信息或路由信息， 网络节点设备处理触发信 息超过有效时间， 等等。 其中， 网络节点设备处理超时的原因可能是网络 拥塞或过载。
步驟 304, MTC用户设备收到所述触发信息， 向 MTC服务器发送触发 信息接收响应消息， 流程结束。
这里， MTC用户设备一般需要通过网络节点设备向 MTC服务器发送 触发信息接收响应消息。
所述 MTC用户设备接收到触发信息是指 MTC用户设备正确接收所述 触发信息； 所述接收响应消息可以通过短信 SMS或控制面信令发送。
进一步的， MTC用户设备发送了接收响应消息后， 可以根据触发信息 的指示及自身能力确定下一步的动作，如：与 MTC服务器建立用户面承载， 或等待 MTC服务器发送其他信息， 或收集 MTC用户设备状态， 等等。
可选的， 如果网络节点设备在预设的重发时间内未收到来自相应 MTC 用户设备的触发信息接收响应消息， 则重发所述触发信息， 所述重发时间 不大于预设的有效时间。
步驟 305 , 所述网络节点设备向 MTC服务器报告触发信息失败消息， 流程结束。
所述网络节点在有效时间内没有成功发送触发信息，则向 MTC服务器 发送接收触发信息失败消息；
所述触发信息失败消息可以包括以下一项或多项： 触发信息中的 MTC 用户设备标识， 触发信息计数， 触发失败原因等。
需要说明的是， MTC服务器还可以根据接收的触发信息失败消息或触 发信息接收响应消息决策是否重发相应的触发信息 MTC服务器收到所述 触发信息失败消息后， 可以重发所述触发信息。
需要说明的是，触发信息计数可以用于区分发送至不同 MTC用户设备 和 /或内容不同的触发信息。
为了实现上述方法， 本发明实施例还相应地提供一种响应触发信息的 系统， 如图 4所示， 该系统包括： MTC服务器 41、 网络节点设备 42、 MTC 用户设备 43; 其中，
MTC服务器 41， 设置为向网络节点设备 42发送触发信息；
网络节点设备 42, 设置为在收到来自 MTC服务器 41的触发信息后， 向相应的 MTC用户设备 43转发所述触发信息； 以及在判定所述触发信息 转发失败时， 向 MTC服务器 41报告触发信息失败消息。
MTC 用户设备 43 , 设置为在成功接收触发信息后， 向网络节点设备 42返回触发信息接收响应消息；
网络节点设备 42 , 还设置为将来自 MTC用户设备 43的触发信息接收 响应消息转发给 MTC服务器 41。
MTC服务器 41 ,还设置为根据接收的触发信息失败消息或触发信息接 收响应消息决策是否重发相应的触发信息。
网络节点设备 42, 还设置为在预设的重发时间内未收到来自 MTC用 户设备 43的触发信息接收响应消息时， 重发相应的触发信息。
所述网络节点设备 42包括以下一种或多种： MTC-IWF、 HSS/ HLR、 SMS- SC、 MME/SGSN。
本发明实施例还相应地提出了一种 MTC用户设备， 如图 5所示， 该 MTC用户设备包括： 接收单元 51、 设置单元 52和发送单元 53; 其中， 接收单元 51 , 设置为接收来自网络节点设备的触发信息；
设置单元 52, 设置为在触发信息接收单元成功接收所述触发信息后， 设置触发信息接收响应消息内容；
发送单元 53 , 设置为将设置单元设置的触发信息接收响应消息返回网 络节点设备。 以下实施例假设 MTC触发信息通过 MTC-IWF以控制面信令方式发送 为例； 此外， MTC触发信息还可以选择通过短信 SMS方式发送， 此时触 发信息和响应信息采用现有 SMS技术实现。 实施例 1
本实例针对触发信息成功发送到 MTC用户设备的场景， 实现 MTC用 户设备触发响应的方法， 如图 6所示， 该方法包括以下几个步驟：
步驟 601 , MTC服务器向 MTC-IWF发送触发信息；
所述 MTC服务器设置触发信息的内容， 并通过 MTC用户设备标识查 找对应的 MTC-IWF , 将所述触发信息发送到所述 MTC-IWF。
具体的，所述 MTC服务器通过 MTCsp接口发送所述 MTC用户设备触 发信息到 MTC-IWF;
步驟 602, MTC-IWF向 MTC用户设备对应的 MME/SGSN转发触发信 所述 MTC-IWF根据触发信息中的 MTC用户设备外部标识查询到对应 的 HSS/HLR, 通过 HSS/HLR查询 MTC用户设备的内部标识， 将 MTC用 户设备触发信息中的 MTC 用户设备外部标识改为 3GPP 网络内部标识 IMSI, 并通过 HSS/HLR查询得到 MTC用户设备注册的 MME/SGSN; 这里， 所述 MTC-IWF和 HSS/HLR, MTC-IWF和 MMS/SGSN之间建 立有通信接口。
步驟 603 , MME/SGSN向目标用户设备发送 MTC用户设备触发信息； 所述 MTC用户设备触发信息通过正在进行的信令连接、 或寻呼消息、 或广播消息发送； 所述信令连接可以是专用 NAS消息；
步驟 604, MTC用户设备接收所述触发信息，向 MME/SGSN发送触发 信息接收响应消息；
所述 MTC 用户设备设置触发响应消息的内容， 触发响应消息包括： MTC用户设备标识， 触发信息计数， 等。
进一步的， 所述 MTC用户设备根据触发信息内容中的 MTC服务器的 地址、 端口信息与 MTC服务器建立应用层通信。
步驟 605 , MME/SGSN向 MTC-IWF转发触发信息接收响应消息； 这里，所述 MME和 SGSN可能同时或分别向 MTC-IWF发送触发信息 响应消息。
步驟 606, MTC-IWF向 MTC服务器转发触发信息响应消息， 流程结 束；
所述 MTC-IWF通过 MTCsp接口向 MTC服务器发送触发响应消息。 实施例 2
本实施例针对 MTC用户设备触发信息在 MTC-IWF发送失败的场景， 实现 MTC用户设备触发响应的方法， 如图 7所示， 该方法包括以下几个步 驟：
步驟 701 , MTC服务器向 MTC-IWF发送触发信息；
本步驟与步驟 601相同， 此处不再赘述。
步驟 702, MTC-IWF处理触发信息， 判断是否有 MTC用户设备的路 由信息， 如果是， 转向步驟 703 , 否则， 转向步驟 705;
所述处理触发信息包括： 通过 HSS/HLR查询 MTC用户设备的路由信 息和内部标识， 判断有效时间是否超时， 等等；
所述路由信息是指 MTC用户设备对应的 MME/SGSN的信息。
步驟 703 , MTC-IWF转发触发信息到 MTC用户设备； 所述 MTC-IWF通过 MTC用户设备对应的 MME/SGSN向 MTC用户设 备转发触发信息。
步驟 704, MTC用户设备收到触发信息， 向 MTC服务器发送触发响应 消息， 流程结束。
所述 MTC用户设备设置触发响应消息的内容，并通过网络节点设备向
MTC服务器发送触发响应消息；触发响应消息内容包括： MTC用户设备标 识， 触发信息计数， 等。
步驟 705 , MTC-IWF判断有效时间是否超时， 如果是， 转向步驟 706, 否则转向步驟 702;
所述有效时间在触发信息中指示， 如果发生网络拥塞或节点过载， 则 需要在 MTC-IWF緩存触发信息，緩存触发信息的时间不能超过触发信息的 有效时间。
步驟 706, MTC-IWF向 MTC服务器发送触发失败消息， 流程结束； 所述 MTC-IWF设置触发失败消息的内容， 包括： 触发信息中的 MTC 用户设备标识， 触发信息计数， 触发失败原因， 等；
所述 MTC-IWF通过 MTCsp接口向 MTC服务器发送触发失败消息； 所述 MTC-IWF发送触发失败消息时， 删除本地存储的触发消息。 实施例 3
本实施例针对 MTC用户设备触发信息在 MME/SGSN发送失败的场景， 实现 MTC用户设备触发响应的方法， 如图 8所示， 该方法包括以下几个步 驟：
步驟 801 , MTC服务器向 MTC-IWF发送触发信息；
本步驟与步驟 601相同， 此处不再赘述。
步驟 802 , MTC-IWF向 MTC用户设备对应的 MME/SGSN转发触发信 本步驟与步驟 602相同， 此处不再赘述。
步驟 803 , MME/SGSN处理触发信息，判断是否有 MTC用户设备注册 信息， 如果是， 转向步驟 804, 否则转向步驟 806;
所述设备注册信息是指 MTC 用户设备在附着 attach 过程中， 在 MME/SGSN进行注册；
如果 MTC用户设备进行了去附着 detach, 或者由于 MTC移动， 离开 当前 MME/SGSN的覆盖区域， 则在当前 MME/SGSN无法查找到 MTC用 户设备的注册信息。
步驟 804 , MME/SGSN向 MTC用户设备发送触发信息；
本步驟与步驟 603相同， 此处不再赘述。
步驟 805, 收到触发信息的 MTC用户设备向 MTC服务器发送接收触 发信息响应消息， 流程结束。
所述 MTC用户设备设置触发响应消息的内容，并通过网络节点设备向 MTC服务器发送触发响应消息；触发响应消息内容包括： MTC用户设备标 识， 触发信息计数， 等。
步驟 806, MME/SGSN判断有效时间是否超时，如果是，转向步驟 807, 否则转向步驟 803;
所述有效时间在触发信息中指示， 如果发生网络拥塞或节点过载， 则 需要在 MME/SGSN緩存触发信息，緩存触发信息的时间不能超过触发信息 的有效时间；
所述 MME/SGSN判断有效时间超时，表明触发失败；有效时间未超时，
MME/SGSN可以重新发送本地存储的触发信息；
步驟 807, MME/SGSN向 MTC-IWF发送触发失败消息；
所述 MME/SGSN删除本地存储的触发信息， 向 MTC-IWF发送触发失 败消息； 所述触发失败消息包括： MTC用户设备标识， 触发信息计数， 失败原 因等。
步驟 808, MTC-IWF向 MTC服务器发送触发失败消息， 流程结束。 所述 MTC-IWF收到 MME/SGSN发送的触发失败消息， MME/SGSN 处的有效时间超时， 说明 MTC-IWF也已超时， MTC-IWF已删除相应的触 发信息， MTC-IWF向 MTC服务器发送触发失败消息；
所述触发失败消息包括： MTC用户设备标识， 失败原因等。 实施例 4
本实施例针对 MTC用户设备触发信息在 MTC用户设备接收失败的场 景， 实现 MTC用户设备触发响应的方法， 如图 9所示， 该方法包括以下几 个步驟：
步驟 901 , MTC服务器向 MTC-IWF发送触发信息；
本步驟与步驟 601相同， 此处不再赘述。
步驟 902 , MTC IWF向 MTC用户设备对应的 MME/SGSN转发触发信 本步驟与步驟 602相同， 此处不再赘述。
步驟 903 , MME/SGSN向 MTC用户设备发送触发信息；
本步驟与步驟 603相同， 此处不再赘述。
步驟 904, MTC用户设备判断是否正确接收触发信息， 如果是， 转向 步驟 905, 否则转向步驟 906;
所述 MTC用户设备不能正确接收触发信息的原因包括： MTC用户设 备内存满， MTC用户设备出错等。
步驟 905 , MTC用户设备向 MTC服务器发送触发信息接收响应消息， 流程结束。
所述 MTC用户设备设置触发响应消息的内容，并通过网络节点设备向 MTC服务器发送触发响应消息；触发响应消息内容包括： MTC用户设备标 识， 触发信息计数， 等。
步驟 906 , MTC用户设备向 MME/SGSN发送触发失败消息； 所述 MTC用户设备通过控制面信令， 或短信等方式向 MME/SGSN发 送触发失败消息。
步驟 907, MME/SGSN判断本地的触发信息是否超时， 如果是， 转向 步驟 908, 否则转向步驟 903;
本步驟与步驟 806相同， 此处不再赘述。
步驟 908, MME/SGSN向 MTC-IWF发送触发失败消息；
本步驟与步驟 807相同， 此处不再赘述。
步驟 909, MTC-IWF向 MTC服务器发送触发失败消息， 流程结束。 本步驟与步驟 808相同， 此处不再赘述。
以上所述， 仅为本发明的较佳实施例而已， 并非用于限定本发明的保 护范围。

Claims

权利要求书
1、 一种响应触发信息的方法， 其中， 该方法包括：
网络节点设备收到来自机器类通信 MTC服务器的触发信息后，向相应 的 MTC用户设备转发所述触发信息；
网络节点设备判定所述触发信息转发失败，则向所述 MTC服务器报告 触发信息失败消息。
2、 根据权利要求 1 所述的方法， 其中， 所述网络节点设备向相应的 MTC用户设备转发所述触发信息后， 该方法还包括：
所述 MTC用户设备成功接收所述触发信息后，向所述网络节点设备返 回触发信息接收响应消息；
所述网络节点设备将所述触发信息接收响应消息转发给 MTC服务器。
3、 根据权利要求 1所述的方法， 其中，
所述网络节点设备判定所述触发信息转发失败为： 所述网络节点设备 没有查找到相应 MTC用户设备的注册信息或路由信息， 或者， 所述网络节 点设备转发所述触发消息后，在预设的有效时间内未收到来自相应 MTC用 户设备的触发信息接收响应消息。
4、 根据权利要求 1所述的方法， 其中， 所述触发信息失败消息包括以 下一项或多项： 触发信息中的 MTC用户设备标识、 触发信息计数、 触发失 败原因。
5、 根据权利要求 2所述的方法， 其中， 该方法还包括：
MTC服务器根据接收的触发信息失败消息或触发信息接收响应消息决 策是否重发相应的触发信息。
6、 根据权利要求 3所述的方法， 其中， 所述向相应的 MTC用户设备 转发所述触发信息后， 该方法还包括：
所述网络节点设备在预设的重发时间内未收到来自相应 MTC 用户设 备的触发信息接收响应消息， 则重发所述触发信息， 所述重发时间不大于 所述预设的有效时间。
7、 根据权利要求 3所述的方法， 其中， 所述触发信息接收响应消息通 过短信 SMS或控制面信令发送。
8、 根据权利要求 1至 7任一项所述的方法， 其中， 所述网络节点设备 包括以下一种或多种： 机器类型通信互联功能 MTC-IWF、 归属用户服务器 HSS/归属位置寄存器 HLR、 短信业务 SMS-业务中心 SC、 移动管理实体 MME/通用分组无线服务技术支持节点 SGSN。
9、 一种响应触发信息的系统， 其中， 该系统包括： MTC服务器、 网 络节点设备； 其中，
所述 MTC服务器， 设置为向网络节点设备发送触发信息；
所述网络节点设备， 设置为在收到来自 MTC服务器的触发信息后， 向 相应的 MTC用户设备转发所述触发信息； 以及在判定所述触发信息转发失 败时， 向 MTC服务器报告触发信息失败消息。
10、根据权利要求 9所述的系统，其中，该系统还包括 MTC用户设备， 所述 MTC用户设备， 设置为在成功接收触发信息后， 向网络节点设备 返回触发信息接收响应消息；
所述网络节点设备，还设置为将来自 MTC用户设备的触发信息接收响 应消息转发给 MTC服务器。
11、 根据权利要求 10所述的系统， 其中，
所述 MTC服务器，还设置为根据接收的触发信息失败消息或触发信息 接收响应消息决策是否重发相应的触发信息。
12、 根据权利要求 10所述的系统， 其中，
所述网络节点设备，还设置为在预设的重发时间内未收到来自 MTC用 户设备的触发信息接收响应消息时， 重发相应的触发信息。
13、 根据权利要求 9至 12任一项所述的系统， 其中， 所述网络节点设 备包括以下一种或多种： MTC-IWF、 HSS/ HLR、 SMS- SC、 MME/SGSN。
14、 一种 MTC用户设备， 其中， 该 MTC用户设备包括： 接收单元、 设置单元和发送单元； 其中，
所述接收单元， 设置为接收来自网络节点设备的触发信息；
所述设置单元， 设置为在触发信息接收单元成功接收所述触发信息后， 设置触发信息接收响应消息内容；
所述发送单元， 设置为将设置单元设置的触发信息接收响应消息返回 网络节点设备。
PCT/CN2012/071360 2012-01-04 2012-02-20 响应触发信息的方法、系统和mtc用户设备 WO2013102316A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201210000759.0A CN103200553B (zh) 2012-01-04 2012-01-04 响应触发信息的方法、系统和mtc用户设备
CN201210000759.0 2012-01-04

Publications (1)

Publication Number Publication Date
WO2013102316A1 true WO2013102316A1 (zh) 2013-07-11

Family

ID=48722877

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2012/071360 WO2013102316A1 (zh) 2012-01-04 2012-02-20 响应触发信息的方法、系统和mtc用户设备

Country Status (2)

Country Link
CN (1) CN103200553B (zh)
WO (1) WO2013102316A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104768137B (zh) * 2014-01-08 2019-03-12 阿尔卡特朗讯 一种用于mtc的触发报告的传递方法与装置

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101316221A (zh) * 2007-05-30 2008-12-03 深圳华为通信技术有限公司 通知消息处理方法及设备
CN102149105A (zh) * 2010-02-10 2011-08-10 电信科学技术研究院 离线通知的方法、系统和设备
CN102238477A (zh) * 2010-04-30 2011-11-09 华为终端有限公司 触发一组mtc设备与mtc服务器通信的方法及mtc设备

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR101641542B1 (ko) * 2010-01-15 2016-07-22 삼성전자주식회사 메시지 전송 방법 및 시스템

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101316221A (zh) * 2007-05-30 2008-12-03 深圳华为通信技术有限公司 通知消息处理方法及设备
CN102149105A (zh) * 2010-02-10 2011-08-10 电信科学技术研究院 离线通知的方法、系统和设备
CN102238477A (zh) * 2010-04-30 2011-11-09 华为终端有限公司 触发一组mtc设备与mtc服务器通信的方法及mtc设备

Also Published As

Publication number Publication date
CN103200553A (zh) 2013-07-10
CN103200553B (zh) 2018-05-08

Similar Documents

Publication Publication Date Title
WO2012151981A1 (zh) 发送mtc设备触发信息的方法、系统和目标用户设备
EP2753106B1 (en) Method and system for sending a trigger message to a mtc ue, and mtc ue
US20190028337A1 (en) Method for setting configuration of non-ip data delivery (nidd) in wireless communication system and device for same
EP3619985A1 (en) Paging policy differentiation in 5g system
KR20170081229A (ko) 진화된 패킷 시스템에서 모바일-착신 통신의 지원
WO2014000337A1 (zh) 机器类型通信用户设备的通信方法及系统
US8743752B2 (en) Method and apparatus for status transition
WO2012151963A1 (zh) 一种触发信息中有效时间的处理方法和系统
WO2014000336A1 (zh) 机器类型通信用户设备的寻呼方法及装置
US9204273B2 (en) Method and system for trigger information transmission and protocol conversion
WO2013056486A1 (zh) 一种消息类型的指示方法、系统及装置
WO2011140698A1 (zh) 一种短消息的处理方法、装置和系统
US20150215725A1 (en) Method, system, and equipment for sending trigger message
WO2014048173A1 (zh) 一种小数据发送方法、系统及用户设备
WO2014161293A1 (zh) 一种发送小数据的方法、系统及用户设备
WO2013063852A1 (zh) 设置触发信息有效时间方法、系统和用户设备
US9854382B2 (en) Method and unit for processing triggering information of MTC devices
CN103517415B (zh) 一种触发mtc用户设备的方法、mtc iwf、mtc用户设备
WO2014071758A1 (zh) 信息的发送方法、mtc服务器、用户设备及mtc系统
WO2013102316A1 (zh) 响应触发信息的方法、系统和mtc用户设备

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 12864577

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 12864577

Country of ref document: EP

Kind code of ref document: A1