WO2014071758A1 - 信息的发送方法、mtc服务器、用户设备及mtc系统 - Google Patents

信息的发送方法、mtc服务器、用户设备及mtc系统 Download PDF

Info

Publication number
WO2014071758A1
WO2014071758A1 PCT/CN2013/081359 CN2013081359W WO2014071758A1 WO 2014071758 A1 WO2014071758 A1 WO 2014071758A1 CN 2013081359 W CN2013081359 W CN 2013081359W WO 2014071758 A1 WO2014071758 A1 WO 2014071758A1
Authority
WO
WIPO (PCT)
Prior art keywords
information
trigger
application
mtc
identifier
Prior art date
Application number
PCT/CN2013/081359
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 中兴通讯股份有限公司
Priority to EP13853033.2A priority Critical patent/EP2919494A4/en
Priority to US14/439,166 priority patent/US9706334B2/en
Publication of WO2014071758A1 publication Critical patent/WO2014071758A1/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]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/12—Messaging; Mailboxes; Announcements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/20—Services signaling; Auxiliary data signalling, i.e. transmitting data via a non-traffic channel
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/14—Direct-mode setup

Definitions

  • the present invention relates to the field of communications, and in particular to a method for transmitting information, an MTC server, a user equipment, and an MTC system.
  • M2M Machine to Machine
  • M2M concept emerged in the 1990s, but only stayed in the theoretical stage. After 2000, with the development of mobile communication technology, it is possible to realize the networking of machine equipment with mobile communication technology. M2M business appeared on the market around 2002, and it developed rapidly in the following years, becoming the focus of many communication equipment vendors and telecom operators. At present, there are more machines in the world than people, so it is foreseeable that M2M technology has a good market prospect.
  • M2M communication application scenarios shows that providing M2M communication on mobile networks has potential market prospects.
  • the M2M service puts forward many new requirements for the system.
  • the existing mobile communication networks are mainly designed for human-to-human communication, while 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. Based on the above situation, it is necessary to study the solution of mobile network supporting M2M communication.
  • MTC Machine Type Communication
  • the EPS includes a radio access network, for example, a UMTS Terrestrial Radio Access Network (UTRAN), an evolved UTRAN (Evolved UTRAN).
  • UTRAN UMTS Terrestrial Radio Access Network
  • Evolved UTRAN evolved UTRAN
  • E-UTRAN Evolved Packet Core
  • MME mobile management entity
  • Serving Gateway Serving Gateway
  • PGW packet data network gateway
  • SGSN serving GPRS support node
  • eNB evolved Node B
  • MTC device trigger (Device Trigger) is one of the basic requirements for the MTC system.
  • the problem of this requirement is: In order to control the communication of the MTC device, the polling can be initiated by the MTC server (Server). For the communication initiated by the MTC device, the MTC Server sometimes needs to poll the data from the MTC device. If the MTC server fails to query or the IP address of the MTC device is unavailable, the MTC server can use the MTC device trigger to establish communication with the MTC device. If the network cannot trigger the MTC device, the network reports to the MTC server that the MTC device trigger fails.
  • the MTC device trigger is implemented in 3GPP through control plane signaling.
  • the MTC device triggers the Mobile Originated (MO) and Mobile Terminating (MT) services, that is, the MTC device sends or receives information.
  • the proposed solution includes: sending the MTC device trigger information by using a short message (SMS), or sending the MTC device trigger information by using control plane signaling.
  • SMS short message
  • the MTC server sends control plane signaling including the trigger information of the MTC device to the network node, and the network node parses the MTC device trigger information in the control plane signaling, and then sends the MTC.
  • the device triggers information to the user equipment (User Equipment, UE for short).
  • User Equipment User Equipment
  • an MTC application device that connects an MTC user (User) communicates with an MTC server through an API interface, or through a Gi/ The SGi interface directly communicates with a Gateway GPRS Support Node (GGSN) in the 3GPP network; the MTC server communicates with the GGSN/PGW through the Gi/SGi interface; the GGSN/PGW communicates with the user through the Radio Access Network (RAN) Device (UE) communication;
  • the MTC server sends control plane signaling including the trigger information of the MTC device to the MTC Interworking Function (MTC-IWF) through the Tsp interface, or the SME uses the Tsms interface to SMS (Short Message Service-Service Centre, SMS-SC for short) / IP-Short-Message-Gateway (IP-SM-GW) Sends control information including trigger information of MTC devices
  • SMS Short Message Service-Service Centre, SMS-SC for short
  • IP-Short-Message-Gateway IP-SM-GW
  • FIG. 2 is a schematic diagram of the control plane signaling including the trigger information of the MTC device sent by the MTC-IWF through the T4 interface according to the related art, where the MTC-IWF directly sends the SMS to the SMS-SC transmitting the MTC including the trigger information of the MTC device through the T4 interface.
  • the device triggers information and finally sends the message to the UE.
  • the UE sends an acknowledgement message to the MTC server through the network node. If the trigger is successful, the UE establishes a connection with the MTC server and communicates.
  • the SMS application port ID 49152 is used to indicate the SMS trigger information.
  • the 49152 port label is added to the trigger information.
  • the indication is the SMS triggering information, and the SMS triggering information is sent to the target UE through the T4 process.
  • the target UE determines the received short message as the triggering information according to the 49152 identifier in the SMS, and forwards the SMS triggering information to the corresponding application for processing.
  • the UE cannot identify the application according to the existing solution and forwards it to the corresponding application processing; in the presence of the non-MTC application
  • the UE cannot identify the application corresponding to the short message triggering information through the existing solution, and thus cannot meet the requirement that the MTC device trigger information is sent to the correct application for processing.
  • SUMMARY OF THE INVENTION The present invention provides a method for transmitting information, an MTC server, a user equipment, and an MTC system to solve at least the above problems.
  • a method for sending information including: adding, by an MTC server or an SME, a trigger identifier, where the trigger identifier is set to indicate that the information is trigger information;
  • the server or the SME sends the information to the user equipment.
  • the information indicated by the triggering identifier further includes at least one of the following: indicating an application type triggered by the information, where the application type includes: an MTC application and a non-MTC application; indicating an application triggered by the information ;
  • the indication triggers billing.
  • the triggering identifier includes at least one of the following: an application port number identifier of the application triggered by the information; a protocol identifier of the application triggered by the information; and an application identifier of the application triggered by the information.
  • the MTC server sends the information to the user equipment, including: the MTC server carries the information in a short message or control plane signaling, and sends the information to the MTC-IWF; the MTC-IWF determines the letter.
  • the information is trigger information; the MTC-IWF sends the information to the user equipment through a T4 interface and/or a T5 interface.
  • the sending, by the SME, the information to the user equipment includes: the SME carrying the information in a short message and sending the information to the user equipment through a Tsms interface.
  • the method further includes: the user equipment receiving the information; the user equipment processing the information according to the trigger identifier.
  • the user equipment is configured to process the information according to the trigger identifier, where: the user equipment sends the information to an application corresponding to the information according to the trigger identifier;
  • the trigger information carried in the information communicates with the MTC server or the SME.
  • a method for forwarding information including: the MTC-IWF receiving information carrying a trigger identifier, where the trigger identifier is set to indicate that the information is trigger information; Determining, by the MTC-IWF, the information as trigger information according to the trigger identifier; the MTC-IWF forwarding the information to a network filtering unit, where the network filtering unit is configured to determine a machine type communication MTC that sends the information. Whether the server or SMS entity SME is authorized to send trigger information.
  • the information indicated by the triggering identifier further includes at least one of the following: an application type that indicates the triggering of the information, where the application type includes: an MTC application and a non-MTC application; indicating that the information is triggered Application; indicates triggering billing.
  • the network filtering unit includes at least one of the following: a short message service-service center SMS-SC, a GMSC, a short message router SMS Router, and a dedicated network entity.
  • the triggering identifier includes at least one of the following: an application port number identifier of the application triggered by the information; a protocol identifier of the application triggered by the information; and an application identifier of the application triggered by the information.
  • an MTC server including: an adding module, configured to add a trigger identifier to the information, where the trigger identifier is set to indicate that the information is trigger information; Set to send the information to the user device.
  • the adding module includes at least one of the following: a first adding unit, configured to carry an application port number identifier set to indicate an application triggered by the information in the information; and a second adding unit, configured to be in the information Carrying a protocol identifier set to indicate an application triggered by the information; and a third adding unit configured to carry, in the information, an application identifier that is set to indicate an application triggered by the information.
  • a user equipment including: a determining module, configured to determine, according to a trigger identifier carried in the received information, the information as trigger information; and a forwarding module configured to be triggered according to the triggering Identifying an application that will forward the information to the user equipment, where the application types include: an MTC application and a non-MTC application.
  • the forwarding module includes: a first forwarding unit configured to forward the information to an application type indicated by the trigger identifier; or a second forwarding unit configured to forward the information to the trigger identifier The indicated application.
  • an MTC system including: an MTC server and/or an SME, configured to carry, in an information, a trigger identifier that is set to indicate that the information is trigger information, and send the information
  • the user equipment is configured to receive the information, and determine, according to the trigger identifier, that the information is trigger information, and forward the information to an application on the user equipment according to the trigger identifier.
  • the user equipment is configured to forward the information to an application type indicated by the trigger identifier, or forward the information to an application indicated by the trigger identifier, and trigger according to the information Information is communicated with the MTC server or the SME.
  • the system further comprises: a network filtering unit, configured to verify whether the MTC server or the SME that sent the information has authorized to send the trigger information.
  • the MTC server or the SME adds a trigger identifier that is set to indicate that the information is trigger information, and sends the information to the user equipment, so that the trigger information is sent to the correct application.
  • FIG. 1 is a schematic diagram of an MTC architecture in 3GPP according to the related art
  • FIG. 2 is a schematic diagram of control plane signaling including MTC device trigger information transmitted through a T4 interface according to the related art
  • FIG. 4 is a structural block diagram of a preferred MTC server according to an embodiment of the present invention
  • 5 is a structural block diagram of a preferred add-on module according to an embodiment of the present invention
  • FIG. 6 is a structural block diagram of a user equipment according to an embodiment of the present invention
  • FIG. 7 is a structural block diagram of a preferred forwarding module according to an embodiment of the present invention
  • FIG. 9 is a flowchart of a method for forwarding information according to an embodiment of the present invention
  • FIG. 10 is a flowchart of a method for identifying trigger information of an MTC device according to an embodiment of the present invention
  • 11 is a schematic diagram of a system for identifying trigger information according to an embodiment of the present invention
  • FIG. 12 is a flowchart of a method for identifying trigger information of an MTC device according to an example 1 of the present invention
  • FIG. 13 is a device for identifying an MTC according to Example 2 of the present invention
  • FIG. 14 is a flowchart of a method of identifying trigger information of an MTC device according to Example 3 of the present invention.
  • an MTC system where the information carries a trigger identifier that is set to indicate that the information is trigger information, to send the trigger information to the correct application.
  • FIG. 3 is a schematic diagram of an MTC system according to an embodiment of the present invention. As shown in FIG.
  • the system mainly includes: an MTC server 1 configured to carry a trigger identifier that is set to indicate that the information is trigger information, and send the The user equipment 2 is configured to receive the foregoing information, and determine the received information as trigger information according to the trigger identifier, and forward the foregoing information to the application on the user equipment 2 according to the trigger identifier.
  • the MTC server 1 carries the trigger identifier that is set to indicate that the information is the trigger information, and sends the information, and the user equipment 2 receives the information, and determines that the received information is triggered information according to the trigger identifier. According to the triggering identifier forwarding information, the trigger information is sent to the correct application.
  • the trigger identifier is further configured to indicate an application type triggered by the information, where the application type includes an MTC application and a non-MTC application.
  • the user equipment 2 may be configured to determine the type of application triggered by the received information according to the trigger identifier.
  • the trigger identifier is further configured to indicate an application triggered by the information.
  • the user equipment 2 is configured to forward the information to the application type indicated by the trigger identifier, or forward the information to the application indicated by the trigger identifier.
  • the trigger identifier may include, but is not limited to, at least one of the following: an application port number identifier of the application triggered by the information; a protocol identifier of the application triggered by the information; and an application identifier of the application triggered by the information.
  • different applications or application types may correspond to different port identifiers, protocol identifiers, and application identifiers.
  • the MTC server 1 may carry the application port identifier of the application triggered by the information in the information, and the user equipment 2 may determine the information as the trigger information according to the application port identifier, and determine the application type triggered by the information according to the application port identifier, and The information is forwarded according to the application port identifier.
  • the MTC application is triggered, the information is forwarded to the MTC application for processing. If the non-MTC application is triggered, the information is forwarded to the non-MTC application for processing. If different applications correspond to different application port identifiers, the user equipment 2 may also forward the information to the application indicated by the application port identifier. Alternatively, the MTC server 1 may carry the protocol identifier of the application triggered by the information in the information, and the user equipment 2 may determine the information as the trigger information according to the protocol identifier, and determine the application type triggered by the information according to the protocol identifier, and identify the application type according to the protocol identifier. Forward this information.
  • the system may further include: a network filtering unit, configured to verify whether the MTC server or the SME that sends the information is authorized to send the trigger information.
  • the MTC-IWF receives the information carrying the trigger identifier, where the trigger identifier is set to the trigger information, and the trigger information is used as the trigger information, and the information is forwarded to the network filtering unit, and the network filtering unit verifies the MTC that sends the information. Whether the server or SME is authorized to send trigger information.
  • the network filtering unit includes but is not limited to at least one of the following: SMS-SC, Gateway Mobile Switching Center (GMSC), Short Message Router (SMS Router), private network entity.
  • FIG. 4 is a structural block diagram of a preferred MTC server according to an embodiment of the present invention.
  • the MTC server mainly includes: an adding module 12 and a sending module 14.
  • the adding module 12 is configured to carry a trigger identifier that is set to indicate that the information is trigger information in the information.
  • the sending module 14 is coupled to the adding module 12 and configured to send the foregoing information to the user equipment.
  • the adding module 12 carries the trigger identifier that is set to indicate that the information is the trigger information, and the sending module 14 sends the information, and indicates the information to the user equipment as the trigger information, and the trigger information is sent. Go to the right application.
  • the information indicated by the trigger identifier further includes, but is not limited to, at least one of the following: an application type triggered by the information, where the application type includes an MTC application and a non-MTC application; application.
  • the trigger identifier may include, but is not limited to, at least one of the following: an application port number identifier of the application triggered by the information; a protocol identifier of the application triggered by the information; and an application identifier of the application triggered by the information.
  • 5 is a structural block diagram of a preferred adding module according to an embodiment of the present invention. As shown in FIG. 5, the adding module 12 includes at least one of the following: a first adding unit 122, configured to carry in the information to be set to indicate that the information is triggered.
  • FIG. 6 is a structural block diagram of a user equipment according to an embodiment of the present invention.
  • the user equipment 2 mainly includes: a determining module 22 and a forwarding module 24.
  • the determining module 22 is configured to determine that the received information is triggered information according to the trigger identifier carried in the received information.
  • the forwarding module 24 is coupled to the determining module 22, and configured to forward the information to the user equipment according to the trigger identifier.
  • the determining module 22 determines, according to the triggering identifier carried in the received information, that the received information is triggered information, and the forwarding module 24 forwards the information to the application on the user equipment according to the triggering identifier, and implements trigger information transmission. Go to the right application.
  • the information indicated by the trigger identifier further includes, but is not limited to, an application triggered by the information.
  • the determining module 22 is configured to determine the information as the trigger information according to the trigger identifier.
  • FIG. 7 is a structural block diagram of a preferred forwarding module according to an embodiment of the present invention.
  • the forwarding module 24 may include: a first forwarding unit 242 configured to forward information to an application type indicated by a trigger identifier; or The second forwarding unit 244 is configured to forward the information to the application indicated by the trigger identifier.
  • the trigger identifier may include, but is not limited to, at least one of the following: an application port number identifier of the application triggered by the information; a protocol identifier of the application triggered by the information; and an application identifier of the application triggered by the information.
  • the determining module 22 may determine that the information is trigger information according to the application port identifier, and the first forwarding unit 242 determines the application type triggered by the information according to the application port identifier, and forwards the information according to the application port identifier, if the MTC application is triggered. Then, the information is forwarded to the MTC application for processing; if the non-MTC application is triggered, the information is forwarded to the non-MTC application for processing. If the different applications correspond to different application port identifiers, the second forwarding unit 244 can forward the information to the application indicated by the application port identifier.
  • the determining module 22 may determine that the information is trigger information according to the protocol identifier, and the first forwarding unit 242 determines the application type triggered by the information according to the protocol identifier, and forwards the information according to the protocol identifier.
  • a method for transmitting information and a method for forwarding information are also provided, which are used to implement identification of information in the above system or device.
  • FIG. 8 is a flowchart of a method for sending information according to an embodiment of the present invention. As shown in FIG. 8, the method mainly includes steps S802 to S804: Step S802, the MTC server or the SME adds a trigger identifier to the information, where The departure identifier is set to indicate that the information is trigger information.
  • the MTC server or the SME sends the foregoing information to the user equipment.
  • the MTC server or the SME carries the trigger identifier that is set to indicate that the information is the trigger information, and sends the information, and indicates the information to the user equipment as the trigger information, so that the trigger information is sent to the correct one. application.
  • the information of the triggering identifier further includes, but is not limited to, at least one of the following: an application type triggered by the indication information, an application triggered by the indication information, and an indication triggering charging.
  • the trigger identifier may include, but is not limited to, at least one of the following: an application port number identifier of the application triggered by the information; a protocol identifier of the application triggered by the information; and an application identifier of the application triggered by the information.
  • the information may be carried in the short message or control plane signaling to the MTC-IWF by the MTC server, for example, the Service Capacity Server (SCS); the MTC-IWF determines the information as the trigger information.
  • the information is confirmed as trigger information according to the trigger identifier; the MTC-IWF sends the information to the user equipment through the T4 interface and/or the T5 interface.
  • the information may be carried in the short message by the SME and sent to the user equipment through the Tsms interface.
  • the foregoing method may further include: receiving, by the user equipment, the foregoing information; processing the information according to the trigger identifier.
  • the user equipment processing the information according to the trigger identifier may include: the user equipment according to The triggering identifier sends the information to the application corresponding to the information; the user equipment communicates with the MTC server or the SME according to the trigger information carried in the information.
  • FIG. 9 is a flowchart of a method for forwarding information according to an embodiment of the present invention. As shown in FIG.
  • the method mainly includes steps S902 to S906: Step S902, the MTC-IWF receives information carrying a trigger identifier, where The identifier is set to indicate that the information is trigger information. Step S904, the MTC-IWF determines that the received information is trigger information according to the trigger identifier. Step S906, the MTC-IWF forwards the information to the network filtering unit, where the network filtering unit is set to determine Whether the MTC server or SME that sent the message has been authorized to send trigger information.
  • the MTC-IWF receives the information carrying the trigger identifier that is set to indicate that the information is the trigger information, and determines that the received information is triggered information according to the trigger identifier, and the MTC-IWF forwards the information to the network filtering unit.
  • the trigger information is forwarded correctly.
  • the information indicated by the triggering identifier further includes, but is not limited to, at least one of the following: an application type triggered by the indication information, where the application type includes an MTC application and a non-MTC application; and the application triggered by the indication information ;
  • the indication triggers billing.
  • the trigger identifier may include, but is not limited to, at least one of the following: an application port number identifier of the application triggered by the information; a protocol identifier of the application triggered by the information; and an application identifier of the application triggered by the information.
  • the network filtering unit includes but is not limited to at least one of the following: an SMS-SC, a GMSC, an SMS Router, and a dedicated network entity.
  • forwarding the information according to the trigger identifier of the application type triggered by the indication information in the information including: forwarding the information to the application type indicated by the trigger identifier; or forwarding the information to The trigger identifies the application indicated.
  • the information may be determined according to the application port identifier, and the application type determined by the information is determined according to the application port identifier, and the information is forwarded according to the application port identifier. If the MTC application is triggered, the information is forwarded. Processing to the MTC application; if the non-MTC application is triggered, the information is forwarded to the non-MTC application for processing. If different applications correspond to different application port identifiers, the information can be forwarded to the application indicated by the application port identifier.
  • the information may be determined according to the protocol identifier as trigger information, and the type of the application triggered by the information is determined according to the protocol identifier, and the information is forwarded according to the protocol identifier.
  • the MTC server SCS includes a trigger identifier in the trigger information, and sends the trigger information to the MTC-IWF.
  • the MTC-IWF determines the information as the trigger information according to the trigger identifier, and forwards the trigger information to the target user equipment.
  • the target user equipment receives the trigger information, and forwards the trigger information to the corresponding application according to the indication information for processing.
  • FIG. 10 is a flowchart of a method for identifying trigger information of an MTC device according to an embodiment of the present invention. As shown in FIG.
  • Step S1002 The MTC server adds a trigger identifier to the trigger information, and sends trigger information for adding the trigger identifier to the MTC-IWF.
  • the MTC server is an application capability server SCS.
  • the triggering identifier is set to indicate that the information is the MTC triggering information, and may be any one of the following: an application port identifier, a protocol identifier, and an application identifier; where the application port identifier, the protocol identifier, and the application identifier are respectively included, except for indicating the trigger information.
  • the triggering information content may include: an MTC device external identifier (External ID), an MTC device triggering validity period (validity period), and a triggering identifier. Further, the MTC device triggering information content further includes at least one of the following: MTC device triggering information priority , MTC server ID, MTC device trigger reference number, trigger payload, etc.
  • the MTC device external identifier is set to identify the target user equipment, the MTC device external identifier, and the corresponding 3GPP network internal identifier is the IMSI, and the mapping between the external identifier and the internal identifier can be completed by using the MTC-IWF.
  • the MTC device identifier may also be a group ID (group ID); the MTC device trigger valid time is set to indicate the time when the network node saves the trigger information of the MTC device; The priority of the information is set to indicate whether the trigger information of the MTC device is urgent or general; the MTC server ID is set to identify the SCS that initiates the trigger information of the MTC device; the MTC device trigger reference number (reference number) is set to indicate whether it is a duplicate trigger request.
  • group ID group ID
  • the MTC device trigger valid time is set to indicate the time when the network node saves the trigger information of the MTC device
  • the priority of the information is set to indicate whether the trigger information of the MTC device is urgent or general
  • the MTC server ID is set to identify the SCS that initiates the trigger information of the MTC device
  • the MTC device trigger reference number reference number
  • the MTC trigger payload is set to include content related to triggering the application, such as indicating the response mode of the user equipment, etc., and the MTC trigger payload is transparent to the 3GPP network node, that is, only the target user equipment can read the corresponding content.
  • the MTC-IWF is located in the home network. As shown in Figure 1, the MTC server SCS is connected to the MTC-IWF through the Tsp interface, the SME is connected to the SMS-SC through the Tsms interface, the MTC-IWF is connected to the SMS-SC through the T4 interface, and the MTC-IWF is connected to the MME through the T5 interface. /SGSN/MSC connection.
  • the SME may send the trigger information to the SMS-SC through the Tsms interface, and include the trigger identifier in the trigger information.
  • the MTC-IWF determines whether it is trigger information. If yes, the process goes to step S1006, otherwise, the process goes to step S1008.
  • the MTC-IWF can determine whether to trigger information according to the trigger identifier. If it is the trigger information, the MTC-IWF selects the manner of sending the trigger information. If it is not the trigger information, the MTC-IWF sends the information to the user equipment according to the process of sending the information. Step S1006: The MTC-IWF selects a trigger information sending path, and forwards the MTC device trigger information to the target user equipment. The sending path can be selected by the MTC-IWF to select the T5 interface or the T4 interface to send trigger information.
  • the foregoing step may further include: determining, by the MTC-IWF, whether the SCS in the trigger information is a server that is authorized to send trigger information to the target MTC device, and the MTC-IWF generates a charging information (CDR, Charging Data Record) according to the trigger identifier and sends the information.
  • CDR Charging Data Record
  • the MTC-IWF sends a trigger message success or failure, it notifies the SCS whether the trigger succeeds or fails (including the cause of the failure).
  • Step S1008 The MTC-IWF sends the received information to the target user equipment.
  • the information may be MTC trigger information or non-MTC trigger information, and the MTC-IWF sends the information to the UE.
  • Step S1010 The target user equipment determines whether the received information is trigger information, and if yes, proceeds to the step
  • Step S1012 otherwise, go to step S1014.
  • the target user equipment determines whether it is trigger information by triggering the identifier.
  • Step S1012 The user equipment forwards the trigger information to the application, and the process ends.
  • the UE reads the trigger identifier in the trigger information, and forwards the trigger information to the corresponding application according to the trigger identifier, and the application processes the received trigger information, such as generating application data, or communicating with the application server. If the UE fails to receive the trigger information, if the UE is full, the trigger failure message is sent to the MTC server.
  • the user equipment in order to communicate with the MTC server, the user equipment may request to establish a PDN connection or activate a PDN connection (PDP) context. If the PDN connection already exists, the PDN connection does not need to be re-established; In step S1014, the user equipment processes the received information, and the process ends.
  • the information is not the MTC trigger information, and the UE can process the information according to the requirements.
  • a system for identifying trigger information is provided corresponding to the foregoing method. As shown in FIG. 11, the system includes: an SCS 31, an MTC-IWF 32, and a user equipment 33;
  • the SCS 31 is configured to include a trigger identifier in the trigger information, and send the trigger information to the MTC-IWF 32.
  • the SCS 31 is configured to set the trigger information content, and send the trigger information to the MTC-IWF 32;
  • the trigger identifier is as follows Any one: Application port ID, protocol ID, and application ID.
  • the triggering information of the MTC device includes: an external identifier of the MTC device, a triggering identifier, and an effective time of triggering the MTC device. Further, the triggering information content of the MTC device further includes at least one of the following: priority of the triggering information of the MTC device, the SCS identifier of the MTC server, and the MTC Device trigger reference number, MTC trigger payload, etc.
  • the MTC-IWF 32 is configured to determine whether the received information is trigger information, and send the received trigger information to the user equipment 33.
  • the MTC-IWF 32 may be configured to receive trigger information, select a transmission mode (eg, a transmission path) of the trigger information, and transmit the trigger information to the user equipment 33.
  • the MTC-IWF 32 is also configured to send a success or failure (including a cause of failure) message to the SCS 31 after the trigger information is successfully sent or failed.
  • the user equipment 33 is configured to receive the trigger information, determine whether the received information is trigger information, and forward the trigger information according to the trigger identifier to the corresponding application for processing.
  • the user equipment 33 is further configured to process the information when it is determined that the received information is not trigger information.
  • the user equipment 33 includes: a receiving unit 331 and a forwarding unit 332, where the receiving unit 331 is configured to receive the MTC device trigger information sent by the MTC-IWF 32, and determine the received information. Whether the information is trigger information, the content of the trigger information is read; the sending unit 332 is configured to forward the trigger information according to the trigger identifier to the corresponding application for processing.
  • the user equipment in the embodiment of the present invention may be a user equipment with an MTC function. The implementation process and principle of the method of the embodiment of the present invention are described in detail below with reference to specific examples.
  • Example one The method for identifying the trigger information of the MTC device is implemented in the scenario that the trigger information of the MTC device is sent through the T5 interface. As shown in FIG. 12, the method includes steps S1202 to S1218. Step S1202: The MTC server SCS sets the MTC device trigger information content.
  • the trigger information includes indication information, that is, a protocol identifier, and/or an application identifier.
  • the MTC device trigger information includes: MTC device identifier, MTC device trigger valid time, and trigger identifier.
  • the MTC device trigger information content further includes at least one of the following: an priority of the MTC device trigger information, an MTC server ID, an MTC device trigger count, an MTC trigger payload, and the like.
  • Step S1204 The MTC server sends the MTC device trigger information to the MTC-IWF. Specifically, the MTC server sends the MTC device trigger information to the MTC-IWF through the Tsp interface. The MTC device trigger information is carried by the control signaling on the Tsp interface. In step S1206, the MTC-IWF determines whether the received information is trigger information, and if yes, proceeds to step S1208, otherwise proceeds to step S1212. Step S1208: The MTC-IWF sends the MTC device trigger information to the MME/SGSN/MSC.
  • the MTC-IWF changes the external identifier of the MTC device in the trigger information of the MTC device to the internal identifier IMSI of the 3GPP network, and obtains the serving MME/SGSN/MSC of the target user equipment by using the HSS/HLR query.
  • a communication interface S6m is established between the MTC-IWF and the HSS/HLR.
  • the MTC-IWF sends the trigger information to the MME through the T5 interface.
  • the trigger information is sent to the MME through the T5b, and the trigger information is sent to the SGSN through the T5b, and the trigger information is sent to the MSC through the T5c.
  • the location where the UE is registered sends the trigger information through the corresponding interface. Otherwise, the trigger information can be sent through the above three interfaces.
  • the MTC-IWF sends the MTC device trigger information to the MME/SGSN/MSC
  • the MTC-IWF retransmits the MTC device trigger information.
  • the MTC-IWF determines the MTC before the MTC-IWF retransmits the MTC device trigger information. Whether the device triggering valid time expires. If yes, the MTC-IWF stops resending, deletes the MTC device trigger information record, and notifies the MTC server that the trigger information transmission fails. After the trigger message is sent through T5, the MTC server can choose to send the trigger information through T4.
  • Step S1210 The MME/SGSN/MSC sends trigger information to the user equipment.
  • the MME/SGSN/MSC may send the trigger information to the user equipment by using the NAS message or the short message mode.
  • the user equipment is configured with the user equipment that supports the MTC function.
  • the MME/SGSN/MSC sends the MTC device trigger to the UE.
  • the information fails, for example, when the MTC device trigger information fails due to network congestion/overload, the MME/SGSN/MSC retransmits the MTC device trigger information; before the MME/SGSN/MSC retransmits the MTC device trigger information, the MME/SGSN/ The MSC determines whether the triggering time of the MTC device is timed out.
  • Step S1212 The MTC-IWF sends information to the user equipment.
  • the target user equipment receives the trigger information, and determines whether it is the trigger information. If yes, the process goes to step S1216, otherwise, the process proceeds to step S1218.
  • the user equipment determines whether the trigger information is triggered according to the trigger identification information, and the trigger identification information is included in the trigger information. It is any of the following: Application port ID, protocol ID, and application ID.
  • Step S1216 The user equipment forwards the trigger information to the application, and the process ends.
  • the UE receives the trigger information, and sends an acknowledgement message to the MTC server; the UE reads the content in the trigger information; the target user equipment forwards the trigger information to the target application according to the trigger identifier in the trigger information content; the application may be an MTC application or a non-MTC application.
  • the corresponding application is processed according to the content of the trigger information, such as generating application data, or communicating with the MTC application server AS.
  • Step S1218 the user equipment processes the received information, and the process ends.
  • the user equipment performs corresponding processing according to the information content.
  • Example 2 This example implements a method for transmitting trigger information of an MTC device according to a scenario in which the trigger information of the MTC device is sent through the T4 interface.
  • the method includes steps S1302 to S1318.
  • Step S1302 the MTC server sets the MTC device trigger information content. This step is the same as step S1202, and details are not described herein again.
  • Step S1304 The MTC server sends the MTC device trigger information to the MTC-IWF. This step is the same as step S 1204, and details are not described herein again.
  • the MTC-IWF determines whether the received information is trigger information. If yes, go to step S1308, otherwise go to step S 1312.
  • Step S1308 the MTC-IWF sends the trigger information through T4.
  • the MTC-IWF sends trigger information to the SMS-SC through T4.
  • the SMS-SC receives the trigger information through T4, and forwards the trigger information to the target user equipment.
  • the SMS-SC receives the trigger information sent by the MTC-IWF through the T4, and the SMS-SC sends the trigger information to the user equipment through the short message. If the SMS-SC fails to send the trigger information to the user equipment, the ij SMS-SC resends the trigger information to the user equipment within the valid time. Otherwise, the SMS-SC sends a trigger information transmission failure indication to the MTC-IWF, and the MTC-IWF receives the indication. After the indication, the trigger information is resent to the SMS-SC within the valid time. Otherwise, the MTC-IWF sends a trigger failure indication to the MTC server, and the MTC server resends the trigger information according to the failure indication.
  • MSISDN-less refers to the scenario where SMS is sent over IP (in this case, IMS-IP Multimedia Subsystem is deployed in the network), and SMS-SC can pass IP-SM-GW.
  • Send SMS trigger information The MTC-IWF sends information to the user equipment.
  • Step S 1314 The target user equipment receives the MTC device trigger information, determines whether it is trigger information, and if yes, proceeds to step S 1316, otherwise proceeds to step S 1318.
  • the triggering identification information is performed by using the triggering identifier information in the short message, and the triggering identifier information is any one of the following: an application port identifier, a protocol identifier, and an application identifier.
  • Step S1316 The user equipment forwards the trigger information to the target application for processing, and the process ends.
  • the UE receives the trigger information, and sends an acknowledgement message to the MTC server.
  • the UE reads the content in the trigger information. If the UE fails to receive the trigger information, if the UE is full, the trigger failure message is sent to the MTC server.
  • the target user equipment forwards the trigger information to the target application according to the triggering identifier in the triggering information content of the MTC device.
  • the foregoing application may be an MTC application or a non-MTC application, and the corresponding application performs processing according to the content of the trigger information, such as generating application data, or interacting with the MTC application.
  • the server AS communicates. Step S1318, the user equipment processes the received information, and the process ends.
  • Step S1401 The short message entity (SME) sets the MTC device trigger information content.
  • the SME is set to generate the SMS trigger information.
  • the SME in this step has the same function as the SCS in step S1202, and is not described here.
  • Step S1402 The SME sends the MTC device trigger information to the SMS-SC.
  • the trigger information is sent to the SMS-SC through the Tsms interface.
  • Step S1406, the SMS-SC forwards the trigger information to the target user equipment.
  • the SMS-SC sends the trigger information to the user equipment through the short message mode, and the trigger information is forwarded to the UE through other network nodes.
  • the other network nodes include one or more of the following: GMSC, SMS-Router, MSC/VLR, SGSN, MME. If the SMS-SC fails to send the trigger information to the user equipment, the ij SMS-SC resends the trigger information to the user equipment within the valid time. Otherwise, the SMS-SC sends a trigger information transmission failure indication to the MTC-IWF, and the MTC-IWF receives the indication. After the indication, the trigger information is resent to the SMS-SC within the valid time.
  • Step S1408 The target user equipment receives the MTC device trigger information, determines whether it is trigger information, and if yes, proceeds to step S1410, otherwise proceeds to step S1412. This step is the same as step S1316, and is not described here.
  • Step S1410 The user equipment forwards the trigger information to the target application for processing, and the process ends.
  • the UE receives the trigger information and sends an acknowledgement message to the SME.
  • the UE reads the content included in the application information container in the trigger information.
  • the UE fails to receive the trigger information, if the UE is full, the trigger failure message is sent to the SME.
  • the target user equipment forwards the trigger information to the target application according to the trigger identifier in the trigger information content.
  • the application may be an MTC application or a non-MTC application, and the corresponding application performs processing according to the content of the trigger information, such as generating application data, or communicating with the SME.
  • the user equipment processes the received information, and the process ends. If the information is not trigger information, the user equipment performs corresponding processing according to the information content.
  • the MTC server includes trigger identification information in the trigger information, and sends the trigger information to the MTC-IWF; the MTC-IWF determines according to the trigger identification information.
  • the information is triggered information, and the trigger information is forwarded to the target user equipment.
  • the target user equipment receives the trigger information, and forwards the trigger information to the corresponding application according to the trigger identification information, and can distinguish different application trigger information to implement the MTC-IWF and the user.
  • the device identifies the trigger information and determines the processing scheme of the trigger information by the MTC-IWF and the user equipment.
  • modules or steps of the present invention can be implemented by a general-purpose computing device, which can be concentrated on a single computing device or distributed over a network composed of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device, such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein.
  • the steps shown or described are performed, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps are fabricated as a single integrated circuit module.
  • the invention is not limited to any specific combination of hardware and software.
  • the above is only the preferred embodiment of the present invention, and is not intended to limit the present invention, and various modifications and changes can be made to the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and scope of the present invention are intended to be included within the scope of the present invention.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Telephonic Communication Services (AREA)

Abstract

本发明公开了一种信息的发送方法、机器类型通信（MTC）服务器、用户设备及MTC系统，其中，信息的发送方法包括：MTC服务器或短信实体（SME）在信息中添加触发标识，其中，该触发标识设置为指示该信息为触发信息；MTC服务器或SME向用户设备发送该信息。通过本发明，实现了将触发信息发送到正确的应用。

Description

信息的发送方法、 MTC服务器、 用户设备及 MTC系统 技术领域 本发明涉及通信领域， 具体而言， 涉及一种信息的发送方法、 MTC服务器、 用户 设备及 MTC系统。 背景技术 机器到机器（Machine to Machine, 简称为 M2M)， 指机器之间建立连接的所有技 术和手段。 M2M 理念在上个世纪九十年代就出现了， 但是只停留在理论阶段。 2000 年以后， 随着移动通信技术的发展， 以移动通信技术实现机器设备的联网成为可能。 2002年左右 M2M业务就在市场上出现， 并在随后的几年迅速发展， 成为了众多通信 设备商和电信运营商的关注焦点。 目前全球的机器数量比人的数量要多， 因此可以预 见到 M2M技术的良好的市场前景。 对 M2M通信应用场景研究表明在移动网络上提供 M2M通信具有潜在的市场前 景。 但 M2M业务对系统提出了很多新的要求， 为了增强移动网络在这方面的竞争力， 有必要对现有的移动网络进行优化， 来更有效的支持 M2M通信。 现有的移动通信网络主要针对人与人的通信进行设计， 而对机器与机器， 人与机 器的通信则优化不足。此外，运营商如何能够以低成本提供 M2M通信服务，也是 M2M 通信部署成功的关键。 基于以上情况， 有必要研究移动网络支持 M2M通信的解决方案， 解决方案要最 大限度重用现有网络， 降低大量 M2M通信对网络造成的影响以及运营维护的复杂度。 目前电信市场竞争日趋激烈， 资费不断下降， 运营商利润空间不断减小， 以人为 基础的通信市场正在趋于饱和， M2M对运营商来说是全新的发展机遇。 为了有效地利用移动网络资源， 第三代合作伙伴计划 （3rd Generation Partnership Project, 简称为 3GPP) 提出了机器类型通信 （Machine Type Communication, 简称为 MTC), 即机器对机器 （Machine to Machine )、 机器对人 （Machine to Man) 进行通讯 的业务， 其业务范围远远超出了以往人对人（Human to Human, 简称为 H2H)之间的 通讯， MTC在接入控制、 计费、 安全性、服务质量（Quality of Service, 简称为 QoS)、 业务模式等方面与现在的 H2H通讯模式有很大的区别。 3GPP演进分组系统 （Evolved Packet System, 简称为 EPS) 架构中， EPS包括了 无线接入网，例如， UMTS陆地无线接入网（Universal Terrestrial Radio Access Network, 简称为 UTRAN)、演进的 UTRAN (Evolved UTRAN,简称为 E-UTRAN)、 GSM/EDGE 无线接入网络 （GSM/EDGE Radio Access Network, 简称为 GERAN), 以及核心网， 例如， 在演进分组核心网 （Evolved Packet Core, 简称为 EPC ) 中有移动管理实体 (MME)、 服务网关 （Serving Gateway )、 分组数据网 （PDN) 网关 （PDN Gateway, 简称为 PGW)等网元， 在 GPRS核心网中包括服务 GPRS支持节点 （SGSN)等网元； 在 E-UTRAN中包括演进的节点 B (evolved Node B， 简称为 eNB)。
MTC设备触发 （Device Trigger) 是对 MTC系统的基本要求之一， 该要求所关注 的问题是： 为了控制 MTC设备的通信， 可以采用由 MTC服务器 （Server) 发起轮询 (poll)的方式进行通信，对于 MTC设备发起的通信，有时也需要 MTC Server从 MTC 设备 poll数据。 如果 MTC服务器查询失败或者 MTC设备的 IP地址不可用， 则 MTC 服务器可以使用 MTC设备触发来与 MTC设备建立通信。 如果网络不能触发 MTC设 备，则网络向 MTC服务器报告 MTC设备触发失败， MTC设备触发在 3GPP中通过控 制面信令实现。
MTC设备触发包括移动主叫（Mobile Originated,简称为 MO)和移动被叫（Mobile Terminating, 简称为 MT) 业务， 即包括 MTC设备发送或者接收信息。 为了实现 MTC设备触发请求的有效传输， 已提出的方案包括： 通过短信 （SMS) 发送 MTC设备触发信息， 或者通过控制面信令发送 MTC设备触发信息。对于通过控 制面信令发送 MTC设备触发信息的方式， MTC服务器发送包含 MTC设备触发信息 的控制面信令到网络节点， 网络节点将控制面信令中的 MTC设备触发信息解析处理， 然后发送 MTC设备触发信息到用户设备 （User Equipment, 简称为 UE)。 图 1是根据相关技术的 3GPP中的 MTC架构的示意图， 如图 1所示， 在用户面， 连接 MTC用户 （User) 的 MTC应用设备 （Application) 通过 API接口与 MTC服务 器通信， 或者通过 Gi/SGi接口直接与 3GPP网络中的网关 GPRS支持节点 （GGSN， Gateway GPRS Support Node )/PGW通信； MTC服务器通过 Gi/SGi接口与 GGSN/PGW 通信； GGSN/PGW通过无线接入网（RAN)与用户设备（UE)通信； 在控制面， MTC 服务器通过 Tsp接口向 MTC互联功能（MTC Inter Working Function,简称为 MTC-IWF) 发送包含 MTC设备触发信息的控制面信令， 或者， SME通过 Tsms接口向短信业务- 业务中心 （Short Message Service-Service Centre, 简称为 SMS-SC ) /IP 短信网关 (IP-Short-Message-Gateway, 简称为 IP-SM-GW) 发送包含 MTC设备触发信息的控 制面信令， MTC-IWF通过 T5发送触发信息到 MME/SGSN/MSC, 进而发送到 UE; 或者 MTC-IWF通过 Τ4发送触发信息到 SMS-SC, 进而发送到 UE。 图 2是根据相关技术的 MTC-IWF通过 T4接口发送包含 MTC设备触发信息的控 制面信令的示意图， 其中， MTC-IWF通过 T4接口直接发送包含 MTC设备触发信息 的 SMS到 SMS-SC传送 MTC设备触发信息， 并最终发送到 UE， UE通过网络节点向 MTC服务器发送确认消息， 如果触发成功， UE与 MTC服务器建立连接并通信。 其 中，为了区分 SMS触发信息和普通 SMS信息，利用 SMS应用口标识（application port ID) 49152指示 SMS触发信息， 即 MTC-IWF从 SCS收至 lj MTC触发信息后， 在触发 信息中加入 49152口标号指示为 SMS触发信息， 并通过 T4流程发送 SMS触发信息 到目标 UE，目标 UE根据 SMS中的 49152标识判断收到的短信为触发信息，并将 SMS 触发信息转发到对应的应用进行处理。 目前在 3GPP的 MTC触发信息流程中，至少存在以下问题： 如果存在多个不同的 应用服务器 AS发送触发信息， UE无法根据现有方案识别应用并转发到对应的应用处 理； 在存在非 MTC应用的触发信息时， UE也无法通过现有方案识别短信触发信息对 应的应用， 从而不能满足 MTC设备触发信息发送到正确的应用进行处理的要求。 发明内容 针对相关技术中触发信息无法发送到正确的应用的问题， 本发明实施例提供了一 种信息的发送方法、 MTC服务器、 用户设备及 MTC系统， 以至少解决上述问题。 根据本发明实施例的一个方面， 提供了一种信息的发送方法， 包括： MTC服务器 或 SME在信息中添加触发标识，其中，所述触发标识设置为指示所述信息为触发信息； 所述 MTC服务器或所述 SME向用户设备发送所述信息。 优选地， 所述触发标识指示的信息还包括以下至少之一： 指示所述信息所触发的 应用类型， 其中， 所述应用类型包括： MTC应用和非 MTC应用； 指示所述信息所触 发的应用； 指示触发计费。 优选地， 所述触发标识包括以下至少之一： 所述信息所触发的应用的应用端口号 标识； 所述信息所触发的应用的协议标识； 所述信息所触发的应用的应用标识。 优选地， 所述 MTC服务器向用户设备发送所述信息， 包括： 所述 MTC服务器将 所述信息携带在短消息或控制面信令中发送至 MTC-IWF;所述 MTC-IWF确定所述信 息为触发信息；所述 MTC-IWF通过 T4接口和 /或 T5接口向所述用户设备发送所述信 息。 优选地， 所述 SME向用户设备发送所述信息， 包括： 所述 SME将所述信息携带 在短消息中通过 Tsms接口发送至用户设备。 优选地， 该方法还包括： 所述用户设备接收所述信息； 所述用户设备根据所述触 发标识对所述信息进行处理。 优选地， 所述用户设备根据所述触发标识对所述信息进行处理， 包括： 所述用户 设备根据所述触发标识将所述信息发送到所述信息对应的应用； 所述用户设备根据所 述信息中携带的触发信息与所述 MTC服务器或所述 SME进行通信。 根据本发明实施例的另一个方面， 提供了一种信息的转发方法， 包括： MTC-IWF 接收携带有触发标识的信息， 其中， 所述触发标识设置为指示所述信息为触发信息； 所述 MTC-IWF根据所述触发标识确定所述信息为触发信息； 所述 MTC-IWF将所述 信息转发到网络过滤单元， 其中， 所述网络过滤单元设置为确定发送所述信息的机器 类型通信 MTC服务器或短信实体 SME是否已授权发送触发信息。 优选地， 所述触发标识指示的信息还包括以下至少之一： 指示所述信息所述触发 的应用类型， 其中， 所述应用类型包括： MTC应用和非 MTC应用； 指示所述信息所 触发的应用； 指示触发计费。 优选地， 所述网络过滤单元包括一下至少之一： 短信业务-业务中心 SMS-SC, GMSC, 短消息路由器 SMS Router, 专用网络实体。 优选地， 所述触发标识包括以下至少之一： 所述信息所触发的应用的应用端口号 标识； 所述信息所触发的应用的协议标识； 所述信息所触发的应用的应用标识。 根据本发明实施例的另一个方面， 提供了一种 MTC服务器， 包括： 添加模块， 设置为在信息中添加触发标识，其中，所述触发标识设置为指示所述信息为触发信息; 发送模块， 设置为向用户设备发送所述信息。 优选地， 所述添加模块包括以下至少之一： 第一添加单元， 设置为在信息中携带 设置为指示所述信息所触发的应用的应用端口号标识； 第二添加单元， 设置为在信息 中携带设置为指示所述信息所触发的应用的协议标识； 第三添加单元， 设置为在信息 中携带设置为指示所述信息所触发的应用的应用标识。 根据本发明实施例的又一个方面， 提供了一种用户设备， 包括： 确定模块， 设置 为根据接收到的信息携带的触发标识确定所述信息为触发信息； 转发模块， 设置为根 据所述触发标识将转发所述信息到用户设备上的应用，其中，所述应用类型包括： MTC 应用和非 MTC应用。 优选地， 所述转发模块包括： 第一转发单元， 设置为将所述信息转发至所述触发 标识所指示的应用类型； 或者第二转发单元， 设置为将所述信息转发至所述触发标识 所指示的应用。 根据本发明实施例的再一个方面， 提供了一种 MTC系统， 包括： MTC服务器和 /或 SME，设置为在信息中携带设置为指示所述信息为触发信息的触发标识，并发送所 述信息； 用户设备， 设置为接收所述信息， 并根据所述触发标识确定所述信息为触发 信息， 根据所述触发标识转发所述信息到用户设备上的应用。 优选地， 所述用户设备， 设置为将所述信息转发至所述触发标识所指示的应用类 型， 或将所述信息转发至所述触发标识所指示的应用， 以及根据所述信息携带的触发 信息与所述 MTC服务器或所述 SME进行通信。 优选地， 所述系统还包括： 网络过滤单元， 设置为验证发送所述信息的 MTC服 务器或 SME是否已授权发送触发信息。 通过本发明实施例， MTC服务器或 SME在信息中添加设置为指示该信息为触发 信息的触发标识， 并向用户设备发送该信息， 实现了将触发信息发送到正确的应用。 附图说明 此处所说明的附图用来提供对本发明的进一步理解， 构成本申请的一部分， 本发 明的示意性实施例及其说明用于解释本发明， 并不构成对本发明的不当限定。 在附图 中- 图 1是根据相关技术的 3GPP中的 MTC架构的示意图； 图 2是根据相关技术的 MTC-IWF通过 T4接口发送包含 MTC设备触发信息的控 制面信令的示意图； 图 3是根据本发明实施例的 MTC系统的示意图； 图 4是根据本发明实施例优选的 MTC服务器的结构框图; 图 5是根据本发明实施例优选的添加模块的结构框图; 图 6是根据本发明实施例的用户设备的结构框图； 图 7是根据本发明实施例优选的转发模块的结构框图； 图 8是根据本发明实施例的信息的发送方法的流程图； 图 9是根据本发明实施例的信息的转发方法的流程图； 图 10是根据本发明实施例的识别 MTC设备触发信息的方法的流程图； 图 11是根据本发明实施例的识别触发信息的系统的示意图； 图 12是根据本发明实例一的识别 MTC设备触发信息的方法的流程图； 图 13是根据本发明实例二的识别 MTC设备触发信息的方法的流程图； 图 14是根据本发明实例三的识别 MTC设备触发信息的方法的流程图。 具体实施方式 下文中将参考附图并结合实施例来详细说明本发明。 需要说明的是， 在不冲突的 情况下， 本申请中的实施例及实施例中的特征可以相互组合。 根据本发明实施例， 提供了一种 MTC 系统， 在信息中携带设置为指示该信息为 触发信息的触发标识， 以将触发信息发送到正确的应用。 图 3是根据本发明实施例的 MTC系统的示意图， 如图 3所示， 该系统主要包括： MTC服务器 1， 设置为在信息中携带设置为指示该信息为触发信息的触发标识， 并发 送该信息； 用户设备 2， 设置为接收上述信息， 并根据触发标识确定接收到的信息为 触发信息， 根据上述触发标识转发上述信息到用户设备 2上的应用。 通过本发明实施例， MTC服务器 1在在信息中携带设置为指示该信息为触发信息 的触发标识， 并发送该信息， 用户设备 2接收信息， 并根据触发标识确定接收到的信 息为触发信息， 根据触发标识转发信息， 实现了将触发信息发送到正确的应用。 在本发明实施例的一个实施方式中， 上述触发标识还设置为指示信息所触发的应 用类型， 其中， 应用类型包括 MTC应用和非 MTC应用。 用户设备 2， 可以设置为根 据触发标识确定接收到的信息所触发的应用类型。 在本发明实施例的另一个实施方式中， 上述触发标识还设置为指示信息所触发的 应用。 用户设备 2， 设置为将上述信息转发至触发标识所指示的应用类型， 或将信息 转发至触发标识所指示的应用。 优选地， 上述触发标识可以包括但不限于以下至少之一： 信息所触发的应用的应 用端口号标识； 信息所触发的应用的协议标识； 信息所触发的应用的应用标识。 在实 际应用中， 不同的应用或应用类型可以对应不同的端口标识、协议标识以及应用标识。 例如， MTC服务器 1可以在信息中携带该信息触发的应用的应用端口标识， 用户 设备 2可以根据应用端口标识确定该信息为触发信息， 并根据应用端口标识确定该信 息所触发的应用类型， 并根据应用端口标识转发该信息， 如果触发的是 MTC应用， 则将信息转发至 MTC应用进行处理； 如果触发的非 MTC应用， 则将该信息转发至非 MTC应用进行处理。如果不同的应用对应着不同的应用端口标识， 用户设备 2还可以 将信息转发至应用端口标识所指示的应用。 或者， MTC服务器 1可以在信息中携带该信息触发的应用的协议标识， 用户设备 2 可以根据协议标识确定该信息为触发信息， 并根据协议标识确定该信息所触发的应 用类型， 并根据协议标识转发该信息。 在本发明实施例的一个实施方式中， 上述系统还可以包括： 网络过滤单元， 设置 为验证发送该信息的 MTC服务器或 SME是否已授权发送触发信息。 MTC-IWF接收 携带有触发标识的信息， 其中， 触发标识设置为指示信息为触发信息， 根据触发标识 确定信息为触发信息， 将该信息转发到网络过滤单元， 网络过滤单元验证发送该信息 的 MTC服务器或 SME是否已授权发送触发信息。 网络过滤单元包括但不限于以下至 少之一： SMS-SC, 网关移动交换中心 （GMSC)， 短消息路由器（SMS Router), 专用 网络实体。 对应于上述系统， 根据本发明实施例， 还提供了一种 MTC服务器和用户设备， 下面对本发明实施例优选的 MTC服务器 1和用户设备 2的实现方式进行描述。 图 4是根据本发明实施例优选的 MTC服务器的结构框图， 如图 4所示， MTC服 务器主要包括： 添加模块 12和发送模块 14。 其中， 添加模块 12， 设置为在信息中携 带设置为指示该信息为触发信息的触发标识； 发送模块 14， 与添加模块 12相耦合， 设置为向用户设备发送上述信息。 通过本发明实施例，添加模块 12在信息中携带设置为指示该信息为触发信息的触 发标识， 并由发送模块 14发送该信息， 向用户设备指示该信息为触发信息， 实现了将 触发信息发送到正确的应用。 在本发明实施例的一个实施方式中， 上述触发标识指示的信息还包括但不限于以 下至少之一：信息所触发的应用类型，其中，应用类型包括 MTC应用和非 MTC应用； 信息所触发的应用。 优选地， 上述触发标识可以包括但不限于以下至少之一： 信息所 触发的应用的应用端口号标识； 信息所触发的应用的协议标识； 信息所触发的应用的 应用标识。 图 5是根据本发明实施例优选的添加模块的结构框图， 如图 5所示， 添加模块 12 包括以下至少之一： 第一添加单元 122， 设置为在信息中携带设置为指示该信息所触 发的应用的应用端口号标识； 第二添加单元 124， 设置为在信息中携带设置为指示该 信息所触发的应用的协议标识； 第三添加单元 126， 设置为在信息中携带设置为指示 该信息所触发的应用的应用标识。 图 6是根据本发明实施例的用户设备的结构框图， 如图 6所示， 用户设备 2主要 包括： 确定模块 22和转发模块 24。 其中， 确定模块 22， 设置为根据接收到的信息携 带的触发标识确定接收到的信息为触发信息； 转发模块 24， 与确定模块 22相耦合， 设置为根据上述触发标识转发该信息到用户设备上的应用，其中，应用类型包括： MTC 应用和非 MTC应用。 通过本发明实施例，确定模块 22根据接收到的信息携带的触发标识确定接收到的 信息为触发信息，转发模块 24根据上述触发标识转发该信息到用户设备上的应用， 实 现了将触发信息发送到正确的应用。 在本发明实施例的一个实施方式中， 上述触发标识指示的信息还包括但不限于： 信息所触发的应用。在触发标识指示信息为触发信息的情况下，确定模块 22设置为根 据触发标识确定该信息为触发信息。 图 7是根据本发明实施例优选的转发模块的结构框图， 如图 7所示， 转发模块 24 可以包括： 第一转发单元 242， 设置为将信息转发至触发标识所指示的应用类型； 或 者， 第二转发单元 244， 设置为将信息转发至触发标识所指示的应用。 在实际应用中， 上述触发标识可以包括但不限于以下至少之一： 信息所触发的应 用的应用端口号标识； 信息所触发的应用的协议标识； 信息所触发的应用的应用标识。 例如，确定模块 22可以根据应用端口标识确定该信息为触发信息，第一转发单元 242 根据应用端口标识确定该信息所触发的应用类型， 并根据应用端口标识转发该信 息， 如果触发的是 MTC应用， 则将信息转发至 MTC应用进行处理； 如果触发的非 MTC应用， 则将该信息转发至非 MTC应用进行处理。 如果不同的应用对应着不同的 应用端口标识， 第二转发单元 244可以将信息转发至应用端口标识所指示的应用。 或者， 确定模块 22可以根据协议标识确定该信息为触发信息， 第一转发单元 242 根据协议标识确定该信息所触发的应用类型， 并根据协议标识转发该信息。 根据本发明实施例， 还提供了一种信息的发送方法和信息的转发方法， 用以在上 述系统或设备中实现信息的标识。 图 8是根据本发明实施例的信息的发送方法的流程图， 如图 8所示， 该方法主要 包括步骤 S802至步骤 S804: 步骤 S802， MTC服务器或 SME在信息中添加触发标识， 其中， 该出发标识设置 为指示该信息为触发信息； 步骤 S804， MTC服务器或 SME向用户设备发送上述信息。 通过本发明实施例， MTC服务器或 SME在信息中携带设置为指示该信息为触发 信息的触发标识， 并发送该信息， 向用户设备指示该信息为触发信息， 实现了将触发 信息发送到正确的应用。 在本发明实施例的一个实施方式中， 上述触发标识指示的信息还包括但不限于以 下至少之一： 指示信息所触发的应用类型、 指示信息所触发的应用、 指示触发计费。 优选地， 上述触发标识可以包括但不限于以下至少之一： 信息所触发的应用的应 用端口号标识； 信息所触发的应用的协议标识； 信息所触发的应用的应用标识。 在实际应用中，可以由 MTC服务器，例如服务能力服务器（ Service Capacity Server, 简称为 SCS)， 将信息携带在短消息或控制面信令中发送至 MTC-IWF; MTC-IWF确 定信息为触发信息， 例如， 根据触发标识确认该信息为触发信息； MTC-IWF通过 T4 接口和 /或 T5接口向用户设备发送该信息。或者， 可以由 SME将该信息携带在短消息 中， 并通过 Tsms接口发送至用户设备。 进一步的， 上述方法还可以包括： 用户设备接收上述信息； 根据触发标识对信息 进行处理。 优选地， 用户设备根据触发标识对信息进行处理可以包括： 用户设备根据 触发标识将信息发送到该信息对应的应用； 用户设备根据信息中携带的触发信息与 MTC服务器或 SME进行通信。 图 9是根据本发明实施例的信息的转发方法的流程图， 如图 9所示， 该方法主要 包括步骤 S902至步骤 S906: 步骤 S902， MTC-IWF接收携带有触发标识的信息， 其中， 触发标识设置为指示 该信息为触发信息； 步骤 S904， MTC-IWF根据触发标识确定接收到的信息为触发信息； 步骤 S906， MTC-IWF将信息转发到网络过滤单元， 其中， 网络过滤单元设置为 确定发送信息的 MTC服务器或 SME是否已授权发送触发信息。 通过本发明实施例， MTC-IWF接收携带有设置为指示该信息为触发信息的触发标 识的信息，根据触发标识确定接收到的信息为触发信息， MTC-IWF将信息转发到网络 过滤单元， 实现了将触发信息正确的转发。 对应于上述信息的发送方法， 上述触发标识指示的信息还包括但不限于以下至少 之一： 指示信息所触发的应用类型， 其中， 应用类型包括 MTC应用和非 MTC应用； 指示信息所触发的应用； 指示触发计费。 优选地， 上述触发标识可以包括但不限于以 下至少之一： 信息所触发的应用的应用端口号标识； 信息所触发的应用的协议标识； 信息所触发的应用的应用标识。 在本发明实施例的一个实施方式中， 网络过滤单元包括但不限于以下至少之一： SMS-SC, GMSC, SMS Router, 专用网络实体。 在本发明实施例的一个实施方式中， 根据信息中设置为指示信息所触发的应用类 型的触发标识转发该信息， 包括： 将信息转发至触发标识所指示的应用类型； 或者， 将信息转发至所述触发标识所指示的应用。 在实际应用中， 可以根据应用端口标识确定该信息为触发信息， 根据应用端口标 识确定该信息所触发的应用类型， 并根据应用端口标识转发该信息， 如果触发的是 MTC应用， 则将信息转发至 MTC应用进行处理； 如果触发的非 MTC应用， 则将该 信息转发至非 MTC应用进行处理。 如果不同的应用对应着不同的应用端口标识， 可 以将信息转发至应用端口标识所指示的应用。 可以根据协议标识确定该信息为触发信 息， 根据协议标识确定该信息所触发的应用类型， 并根据协议标识转发该信息。 下面以在如图 1所示的 MTC架构中实现上述方案的优选实施例为例， 对本发明 实施例的方案进行描述。 在本优选实施方式中， MTC服务器 SCS在触发信息中包含触发标识， 并将触发 信息发送到 MTC-IWF; MTC-IWF根据触发标识确定该信息为触发信息， 并向目标用 户设备转发该触发信息； 目标用户设备接收触发信息， 根据指示信息转发触发信息到 对应的应用进行处理。 下面对本发明实施例的方法及系统进行描述。 图 10是根据本发明实施例的识别 MTC设备触发信息的方法的流程图， 如图 10 所示， 该方法包括步骤 S1002至步骤 S1014。 步骤 S1002， MTC服务器在触发信息中添加触发标识， 并将添加触发标识的触发 信息发送到 MTC-IWF。 在如图 1所示的 MTC构架中， MTC服务器为应用能力服务 器 SCS。 上述触发标识设置为指示该信息为 MTC触发信息， 具体可以是以下任意一种： 应用端口标识， 协议标识， 应用标识； 其中应用端口标识， 协议标识， 应用标识分别 有多个， 除了指示触发信息外， 还可以设置为指示 MTC设备上的不同应用 （如 MTC 应用和非 MTC应用）， 同时还可以设置为触发计费。 触发信息内容可以包括： MTC设备外部标识 （External ID)， MTC设备触发有效 时间 （validity period), 触发标识； 进一步的， MTC设备触发信息内容还包括以下至 少一种： MTC设备触发信息的优先级、 MTC服务器标识、 MTC设备触发参考号、 触 发净荷等。 其中， MTC设备外部标识设置为标识目标用户设备， MTC设备外部标识， 对应 的 3GPP网络内部标识为 IMSI， 外部标识和内部标识之间的映射可以通过 MTC-IWF 完成。 进一步的， 为了实现对多个目标用户设备的 MTC设备触发， MTC设备标识还 可以是组标识（group ID); MTC设备触发有效时间设置为指示网络节点保存 MTC设 备触发信息的时间； MTC设备触发信息的优先级设置为表明该 MTC设备触发信息是 否为紧急或一般； MTC服务器 ID设置为标识发起 MTC设备触发信息的 SCS; MTC 设备触发参考标号（reference number)设置为指示是否为重复的 trigger请求信息； MTC 触发净荷设置为包含触发应用相关的内容， 如指示用户设备的响应方式等， MTC触发 净荷对 3GPP网络节点透明， 即只有目标用户设备可以读取相应的内容。 MTC-IWF位于归属网络。 如图 1所示， 其中， MTC服务器 SCS通过 Tsp接口与 MTC-IWF连接， SME通过 Tsms接口与 SMS-SC连接， MTC-IWF通过 T4接口与 SMS-SC连接， MTC-IWF通过 T5接口与 MME/SGSN/MSC连接。 需要指出的是， 本步骤也可以是 SME通过 Tsms接口向 SMS-SC发送触发信息， 并在触发信息中包含触发标识。 步骤 S1004， MTC-IWF判断是否为触发信息， 如果是， 转向步骤 S1006， 否则转 向步骤 S1008。
MTC-IWF可以根据触发标识判断是否为触发信息；如果是触发信息，则 MTC-IWF 选择发送触发信息的方式， 如果不是触发信息， 则 MTC-IWF按照发送信息的流程向 用户设备发送信息。 步骤 S1006， MTC-IWF选择触发信息发送路径， 向目标用户设备转发 MTC设备 触发信息。 选择发送路径可以是 MTC-IWF选择 T5接口或 T4接口发送触发信息。 优选地， 上述步骤还可以包括： MTC-IWF判断触发信息中的 SCS是否为授权向 目标 MTC设备发送触发信息的服务器， MTC-IWF根据触发标识生成计费信息（CDR， Charging Data Record) 并发送到计费系统。 如果 MTC-IWF发送触发信息成功或失败， 则通知 SCS触发成功或失败 （包括失 败原因）。 步骤 S1008， MTC-IWF将收到的信息发送到目标用户设备。 信息可以是 MTC触 发信息或非 MTC触发信息， MTC-IWF将信息发送到 UE。 步骤 S1010， 目标用户设备判断收到的信息是否为触发信息， 如果是， 转向步骤
S1012, 否则， 转向步骤 S1014。 优选地， 目标用户设备通过触发标识判断是否为触发信息。 步骤 S1012， 用户设备向应用转发触发信息， 流程结束。
UE读取触发信息中的触发标识，并根据触发标识向对应的应用转发触发信息，应 用对收到的触发信息进行处理， 如生成应用数据， 或与应用服务器进行通信。如果 UE 接收触发信息失败， 如 UE内存满， 则向 MTC服务器发送触发失败消息。 在实际应用中， 为了与 MTC服务器进行通信， 用户设备可以请求建立 PDN连接 或激活分组数据协议 （PDP) 上下文 （PDN connection/PDP context), 如果 PDN连接 已存在， 则不需要重新建立 PDN连接； 步骤 S1014, 用户设备对收到的信息进行处理， 流程结束。信息不是 MTC触发信 息， UE可以根据需求对信息进行处理。 根据本发明实施例， 对应于上述方法， 还提供一种识别触发信息的系统， 如图 11 所示， 该系统包括： SCS 31、 MTC-IWF 32和用户设备 33; 其中，
SCS 31, 设置为在触发信息中包含触发标识， 并将触发信息发送到 MTC-IWF 32; 优选地， SCS 31设置为设置触发信息内容， 将触发信息发送到 MTC-IWF 32; 触 发标识为以下任意一种： 应用端口标识， 协议标识， 应用标识。
MTC设备触发信息内容包括： MTC设备外部标识，触发标识和 MTC设备触发有 效时间； 进一步的， MTC设备触发信息内容还包括以下至少一种： MTC设备触发信 息的优先级、 MTC服务器 SCS标识、 MTC设备触发参考号、 MTC触发净荷等。
MTC-IWF 32,设置为判断收到的信息是否为触发信息，将接收到的触发信息发送 到用户设备 33。 优选地， MTC-IWF 32可以设置为接收触发信息， 选择触发信息的发送方式 （例 如发送路径），并将触发信息发送到用户设备 33。 MTC-IWF 32还设置为在发送触发信 息成功或失败后， 向 SCS 31发送触发成功或失败 （包括失败原因） 消息。 用户设备 33， 设置为接收触发信息， 判断收到的信息是否为触发信息， 根据触发 标识转发触发信息到对应的应用进行处理。在实际应用中，用户设备 33还设置为在判 断收到的信息不是触发信息时， 对信息进行处理。 在本发明实施例中， 如图 11所示， 用户设备 33包括： 接收单元 331和转发单元 332， 其中， 接收单元 331， 设置为接收 MTC-IWF 32发送的 MTC设备触发信息， 判 断收到的信息是否为触发信息， 读取触发信息内容； 发送单元 332， 设置为根据触发 标识转发触发信息到对应的应用进行处理。 本发明实施例中的的用户设备可以是具有 MTC 功能的用户设备。 下面结合具体 实例详细说明本发明实施例的方法的实现过程和原理。 实例一 本实例针对 MTC设备触发信息通过 T5接口发送的场景， 实现识别 MTC设备触 发信息的方法， 如图 12所示， 该方法包括步骤 S1202至步骤 S1218。 步骤 S1202， MTC服务器 SCS设置 MTC设备触发信息内容； 本步骤中， 触发信息包含指示信息， 即协议标识， 和 /或应用标识。 MTC 设备触 发信息内容包括： MTC设备标识、 MTC设备触发有效时间和触发标识。 进一步的， MTC设备触发信息内容还包括以下至少一种： MTC设备触发信息的 优先级、 MTC服务器 ID、 MTC设备触发计数， MTC触发净荷等。 步骤 S1204， MTC服务器发送所述 MTC设备触发信息到 MTC-IWF; 具体的， MTC服务器通过 Tsp接口发送 MTC设备触发信息到 MTC-IWF; MTC 设备触发信息通过 Tsp接口上的控制信令承载。 步骤 S1206，MTC-IWF判断收到的信息是否为触发信息，如果是，转向步骤 S1208， 否则转向步骤 S1212。 步骤 S1208， MTC-IWF将 MTC设备触发信息发送到 MME/SGSN/MSC。 具体的， MTC-IWF将 MTC设备触发信息中的 MTC设备外部标识改为 3GPP网 络内部标识 IMSI，并通过 HSS/HLR查询得到目标用户设备的服务 MME/SGSN/MSC。 MTC-IWF和 HSS/HLR之间建立有通信接口 S6m。 本步骤中， MTC-IWF通过 T5接口发送触发信息， 具体的， 通过 T5a向 MME发 送触发信息， 通过 T5b向 SGSN发送触发信息， 通过 T5c向 MSC发送触发信息； 其 中， 如果 MTC-IWF已知目标 UE注册的位置， 则通过相应接口发送触发信息， 否则 可以通过上述 3个接口发送触发信息。 当 MTC-IWF向 MME/SGSN/MSC发送 MTC设备触发信息失败时， MTC-IWF重 发 MTC设备触发信息； 需要指出的是， 在 MTC-IWF重发 MTC设备触发信息之前， MTC-IWF判断 MTC设备触发有效时间是否超时， 如果是则 MTC-IWF停止重发， 删 除 MTC设备触发信息记录， 并通知 MTC服务器触发信息发送失败。 通过 T5发送触 发信息失败后， MTC服务器可以选择通过 T4发送触发信息。 步骤 S1210， MME/SGSN/MSC向用户设备发送触发信息。 MME/SGSN/MSC可以通过 NAS消息或短信方式向用户设备发送触发信息；优选 地， 用户设备是指配置有支持 MTC功能的用户设备； 进一步的， 当 MME/SGSN/MSC向 UE发送 MTC设备触发信息失败时， 例如， 由于网络拥塞 /过载导致发送 MTC设备触发信息失败时， MME/SGSN/MSC重发 MTC 设备触发信息； 在 MME/SGSN/MSC重发 MTC设备触发信息之前， MME/SGSN/MSC 判断 MTC设备触发有效时间是否超时， 如果是则 MME/SGSN/MSC停止重发， 删除 MTC设备触发信息记录， 并通知 MTC-IWF, 进一步的， MTC-IWF通知 MTC服务器 触发信息发送失败。 收到发送触发信息失败指示后， MTC服务器可以选择通过 T4发 送触发信息。 步骤 S1212， MTC-IWF向用户设备发送信息。 步骤 S1214， 目标用户设备接收触发信息， 判断是否为触发信息， 如果是， 转向 步骤 S1216， 否则转向步骤 S1218; 用户设备根据触发标识信息判断是否为触发信息， 触发标识信息包含在触发信息 中， 具体为以下任意一种： 应用端口标识， 协议标识， 应用标识。 步骤 S1216, 用户设备向应用转发触发信息进行处理， 流程结束。
UE收到触发信息， 向 MTC服务器发送确认消息； UE读取触发信息中的内容； 目标用户设备根据触发信息内容中的触发标识向目标应用转发触发信息； 上述应 用可以为 MTC应用或非 MTC应用， 对应的应用根据触发信息的内容进行处理， 如生 成应用数据， 或与 MTC应用服务器 AS进行通信。 步骤 S1218, 用户设备处理收到的信息， 流程结束。 优选地， 如果信息不是触发信息， 用户设备根据信息内容进行相应处理。 实例二 本实例针对 MTC设备触发信息通过 T4接口发送的场景， 实现发送 MTC设备触 发信息的方法， 如图 13所示， 该方法包括步骤 S1302至步骤 S1318。 步骤 S1302， MTC服务器设置 MTC设备触发信息内容。 本步骤与步骤 S1202相同， 此处不再赘述。 步骤 S 1304， MTC服务器发送 MTC设备触发信息到 MTC-IWF。 本步骤与步骤 S 1204相同， 此处不再赘述。 步骤 S 1306，MTC-IWF判断收到的信息是否为触发信息，如果是，转向步骤 S 1308， 否则转向步骤 S 1312. 本步骤与步骤 S 1206相同， 此处不再赘述。 步骤 S 1308， MTC-IWF通过 T4发送触发信息。 MTC-IWF通过 T4向 SMS-SC发 送触发信息。 步骤 S 1310， SMS-SC通过 T4收到触发信息， 向目标用户设备转发触发信息。
SMS-SC通过 T4收到 MTC-IWF发送的触发信息， SMS-SC将触发信息通过短信 形式发送到用户设备。 如果 SMS-SC向用户设备发送触发信息失败， 贝 ij SMS-SC在有效时间内向用户设 备重发触发信息，否贝 lj， SMS-SC向 MTC-IWF发送触发信息发送失败指示， MTC-IWF 收到指示后， 在有效时间内向 SMS-SC重发触发信息， 否则， MTC-IWF向 MTC服务 器发送触发失败指示， MTC服务器根据失败指示重发触发信息。 需要指出的是， 对于无 MSISDN ( MSISDN-less )的场景， MSISDN-less是指 SMS 通过 IP发送的场景（此时网络中部署 IMS-IP Multimedia Subsystem) , SMS-SC可以通 过 IP-SM-GW发送 SMS触发信息。 步骤 S 1312， MTC-IWF向用户设备发送信息。 步骤 S 1314， 目标用户设备接收 MTC设备触发信息， 判断是否为触发信息， 如果 是， 转向步骤 S 1316， 否则转向步骤 S 1318。 判断通过短信中的触发标识信息进行， 触发标识信息为以下任意一种： 应用端口 标识， 协议标识， 应用标识。 步骤 S 1316, 用户设备向目标应用转发触发信息进行处理， 流程结束。
UE收到触发信息， 向 MTC服务器发送确认消息； UE读取触发信息中的内容； 如果 UE接收触发信息失败， 如 UE内存满， 则向 MTC服务器发送触发失败消息。 目标用户设备根据 MTC设备触发信息内容中触发标识向目标应用转发触发信息； 上述应用可以为 MTC应用或非 MTC应用，对应的应用根据触发信息的内容进行处理， 如生成应用数据， 或与 MTC应用服务器 AS进行通信。 步骤 S1318, 用户设备处理收到的信息， 流程结束。 如果信息不是触发信息， 用 户设备根据信息内容进行相应处理。 实例三 本实例针对 MTC设备触发信息通过 Tsms接口发送的场景， 实现识别 MTC设备 触发信息的方法， 如图 14所示， 该方法包括步骤 S1402至步骤 S1412。 步骤 S1401 , 短信实体 （SME) 设置 MTC设备触发信息内容。 SME设置为生成 SMS触发信息， 本步骤的 SME同步骤 S1202中的 SCS作用相 同， 此处不再赘述。 步骤 S1402， SME发送 MTC设备触发信息到 SMS-SC. 优选地， 触发信息通过 Tsms接口发送到 SMS-SC. 步骤 S1406， SMS-SC向目标用户设备转发触发信息。 SMS-SC 将触发信息通过短信方式向用户设备发送， 触发信息通过其它网络节点 转发到 UE， 其它网络节点包括一下一种或多种： GMSC， SMS-Router, MSC/VLR, SGSN, MME。 如果 SMS-SC向用户设备发送触发信息失败， 贝 ij SMS-SC在有效时间内向用户设 备重发触发信息，否贝 lj， SMS-SC向 MTC-IWF发送触发信息发送失败指示， MTC-IWF 收到指示后， 在有效时间内向 SMS-SC重发触发信息， 否则， MTC-IWF向 MTC服务 器发送触发失败指示， MTC服务器根据失败指示重发触发信息。 步骤 S1408, 目标用户设备接收 MTC设备触发信息， 判断是否为触发信息， 如果 是， 转向步骤 S1410, 否则转向步骤 S1412。 本步骤与步骤 S1316相同， 此处不再赘述。 步骤 S1410, 用户设备向目标应用转发触发信息进行处理， 流程结束。 UE收到触发信息， 向 SME发送确认消息； UE读取触发信息中的应用信息容器 包含的内容； 如果 UE接收触发信息失败， 如 UE内存满， 则向 SME发送触发失败消 息。 目标用户设备根据触发信息内容中触发标识向目标应用转发触发信息； 上述应用 可以为 MTC应用或非 MTC应用， 对应的应用根据触发信息的内容进行处理， 如生成 应用数据， 或与 SME进行通信。 步骤 S1412, 用户设备处理收到的信息， 流程结束。 如果信息不是触发信息， 用 户设备根据信息内容进行相应处理。 从以上的描述中， 可以看出， 本发明的实施例实现了如下技术效果： MTC服务器 在触发信息中包含触发标识信息， 并将触发信息发送到 MTC-IWF; MTC-IWF根据触 发标识信息确定信息为触发信息， 并向目标用户设备转发触发信息； 目标用户设备接 收触发信息， 根据触发标识信息将触发信息转发到对应的应用进行处理， 能够区分不 同的应用触发信息， 实现 MTC-IWF和用户设备对触发信息的识别， 确定了 MTC-IWF 和用户设备对触发信息的处理方案。 显然， 本领域的技术人员应该明白， 上述的本发明的各模块或各步骤可以用通用 的计算装置来实现， 它们可以集中在单个的计算装置上， 或者分布在多个计算装置所 组成的网络上， 可选地， 它们可以用计算装置可执行的程序代码来实现， 从而， 可以 将它们存储在存储装置中由计算装置来执行， 并且在某些情况下， 可以以不同于此处 的顺序执行所示出或描述的步骤， 或者将它们分别制作成各个集成电路模块， 或者将 它们中的多个模块或步骤制作成单个集成电路模块来实现。 这样， 本发明不限制于任 何特定的硬件和软件结合。 以上所述仅为本发明的优选实施例而已， 并不用于限制本发明， 对于本领域的技 术人员来说， 本发明可以有各种更改和变化。 凡在本发明的精神和原则之内， 所作的 任何修改、 等同替换、 改进等， 均应包含在本发明的保护范围之内。

Claims

权 利 要 求 书
1. 一种信息的发送方法， 包括：
机器类型通信 MTC服务器或短信实体 SME在信息中添加触发标识，其中， 所述触发标识设置为指示所述信息为触发信息；
所述 MTC服务器或所述 SME向用户设备发送所述信息。
2. 根据权利要求 1所述的方法， 其中， 所述触发标识指示的信息还包括以下至少 之一：
指示所述信息所触发的应用类型， 其中， 所述应用类型包括： 机器类型通 信 MTC应用和非 MTC应用； 指示所述信息所触发的应用；
指示触发计费。
3. 根据权利要求 1或 2所述的方法， 其中， 所述触发标识包括以下至少之一： 所述信息所触发的应用的应用端口号标识；
所述信息所触发的应用的协议标识；
所述信息所触发的应用的应用标识。
4. 根据权利要求 1至 3中任一项所述的方法， 其中， 所述 MTC服务器向用户设 备发送所述信息， 包括：
所述 MTC服务器将所述信息携带在短消息或控制面信令中发送至机器类 型通信互联功能 MTC-IWF;
所述 MTC-IWF确定所述信息为触发信息；
所述 MTC-IWF通过 T4接口和 /或 T5接口向所述用户设备发送所述信息。
5. 根据权利要求 1至 3中任一项所述的方法， 其中， 所述 SME向用户设备发送 所述信息， 包括- 所述 SME将所述信息携带在短消息中通过 Tsms接口发送至用户设备。
6. 根据权利要求 1至 5中任一项所述的方法， 其中， 还包括： 所述用户设备接收所述信息；
所述用户设备根据所述触发标识对所述信息进行处理。
7. 根据权利要求 6所述的方法， 其中， 所述用户设备根据所述触发标识对所述信 息进行处理， 包括：
所述用户设备根据所述触发标识将所述信息发送到所述信息对应的应用； 所述用户设备根据所述信息中携带的触发信息与所述 MTC服务器或所述 SME进行通信。
8. 一种信息的转发方法， 包括：
机器类型通信-互联功能 MTC-IWF接收携带有触发标识的信息， 其中， 所 述触发标识设置为指示所述信息为触发信息；
所述 MTC-IWF根据所述触发标识确定所述信息为触发信息； 所述 MTC-IWF将所述信息转发到网络过滤单元， 其中， 所述网络过滤单 元设置为确定发送所述信息的机器类型通信 MTC服务器或短信实体 SME是否 已授权发送触发信息。
9. 根据权利要求 8所述的方法， 其中， 所述触发标识指示的信息还包括以下至少 之一：
指示所述信息所述触发的应用类型， 其中， 所述应用类型包括： 机器类型 通信 MTC应用和非 MTC应用；
指示所述信息所触发的应用；
指示触发计费。
10. 根据权利要求 8或 9所述的方法，其中，所述网络过滤单元包括一下至少之一： 短信业务-业务中心 SMS-SC, 网关移动交换中心 GMSC， 短消息路由器 SMS Router, 专用网络实体。
11. 根据权利要求 8至 10中任一项所述的方法，其中，所述触发标识包括以下至少 之一：
所述信息所触发的应用的应用端口号标识；
所述信息所触发的应用的协议标识；
所述信息所触发的应用的应用标识。
12. 一种机器类型通信 MTC服务器， 其中， 包括：
添加模块， 设置为在信息中添加触发标识， 其中， 所述触发标识设置为指 示所述信息为触发信息；
发送模块， 设置为向用户设备发送所述信息。
13. 根据权利要求 12所述的 MTC服务器，其中，所述添加模块包括以下至少之一:
第一添加单元， 设置为在信息中携带设置为指示所述信息所触发的应用的 应用端口号标识；
第二添加单元， 设置为在信息中携带设置为指示所述信息所触发的应用的 协议标识；
第三添加单元， 设置为在信息中携带设置为指示所述信息所触发的应用的 应用标识。
14. 一种用户设备， 包括：
确定模块， 设置为根据接收到的信息携带的触发标识确定所述信息为触发 信息；
转发模块，设置为根据所述触发标识将转发所述信息到用户设备上的应用， 其中， 所述应用类型包括： 机器类型通信 MTC应用和非 MTC应用。
15. 根据权利要求 14所述的用户设备， 其中， 所述转发模块包括- 第一转发单元，设置为将所述信息转发至所述触发标识所指示的应用类型; 或者
第二转发单元， 设置为将所述信息转发至所述触发标识所指示的应用。
16. 一种机器类型通信 MTC系统， 包括：
机器类型通信 MTC服务器和 /或短信实体 SME，设置为在信息中携带设置 为指示所述信息为触发信息的触发标识， 并发送所述信息；
用户设备， 设置为接收所述信息， 并根据所述触发标识确定所述信息为触 发信息， 根据所述触发标识转发所述信息到用户设备上的应用。 根据权利要求 16所述的系统， 其中， 所述用户设备，设置为将所述信息转发至所述触发标识所指示的应用类型， 或将所述信息转发至所述触发标识所指示的应用， 以及根据所述信息携带的触 发信息与所述 MTC服务器或所述 SME进行通信。
18. 根据权利要求 16或 17所述的系统， 其中， 所述系统还包括：
网络过滤单元， 设置为验证发送所述信息的 MTC服务器或 SME是否已授 权发送触发信息。
PCT/CN2013/081359 2012-11-06 2013-08-13 信息的发送方法、mtc服务器、用户设备及mtc系统 WO2014071758A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP13853033.2A EP2919494A4 (en) 2012-11-06 2013-08-13 METHOD FOR SENDING INFORMATION, MTC SERVER, USER DEVICE AND MTC SYSTEM
US14/439,166 US9706334B2 (en) 2012-11-06 2013-08-13 Method for sending information, MTC server, user equipment and MTC system

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201210438270.1 2012-11-06
CN201210438270.1A CN103813276A (zh) 2012-11-06 2012-11-06 信息的发送方法、mtc服务器、用户设备及mtc系统

Publications (1)

Publication Number Publication Date
WO2014071758A1 true WO2014071758A1 (zh) 2014-05-15

Family

ID=50684016

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2013/081359 WO2014071758A1 (zh) 2012-11-06 2013-08-13 信息的发送方法、mtc服务器、用户设备及mtc系统

Country Status (4)

Country Link
US (1) US9706334B2 (zh)
EP (1) EP2919494A4 (zh)
CN (1) CN103813276A (zh)
WO (1) WO2014071758A1 (zh)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103369497B (zh) * 2012-03-27 2018-11-30 中兴通讯股份有限公司 触发消息计数器的更新方法、机器类型通信服务器和终端
US20150172882A1 (en) * 2013-12-18 2015-06-18 Alcatel-Lucent Usa Inc. Method For Correlation Of Requesting Information From A Remote Device
EP3482551B1 (en) * 2016-07-07 2022-03-02 Nokia Solutions and Networks Oy Machine type communication using mobile originated short messaging service without mobile station international subscriber directory number

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102427604A (zh) * 2011-12-02 2012-04-25 电信科学技术研究院 MTC Device触发消息的投递确认方法和设备
CN102523315A (zh) * 2011-12-22 2012-06-27 电信科学技术研究院 一种确定mtc-iwf实体的方法及装置
CN102547658A (zh) * 2011-12-22 2012-07-04 电信科学技术研究院 一种数据传输方法及装置

Family Cites Families (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102088729B (zh) * 2009-12-02 2014-06-25 华为技术有限公司 网络接入的方法、装置及系统
EP3328102B1 (en) * 2010-03-23 2020-02-19 IOT Holdings, Inc. Method for communication for a machine type communication device and corresponding wireless transmit/receive unit
CN102404825B (zh) * 2010-09-19 2016-03-30 中兴通讯股份有限公司 一种通过nas信令触发终端的方法和系统
WO2012142618A2 (en) * 2011-04-14 2012-10-18 Zte (Usa) Inc. Methods and apparatus for determining address of a machine type communication device in a wireless network
CN102217261B (zh) * 2011-05-12 2016-07-06 华为技术有限公司 设备之间的交互方法和机器通信网络系统
KR101645109B1 (ko) * 2011-11-04 2016-08-12 인텔 코포레이션 무선 통신 네트워크 내의 스몰 데이터 기술 및 구성
EP3442247A1 (en) * 2011-12-14 2019-02-13 Interdigital Patent Holdings, Inc. Method and apparatus for triggering machine type communications applications
CN103249013B (zh) * 2012-02-03 2018-08-03 中兴通讯股份有限公司 一种mtc用户设备触发信息的发送方法、系统和用户设备
CN102572714B (zh) * 2012-02-10 2015-02-18 电信科学技术研究院 一种机器型通信终端的触发控制方法、装置及系统
US20130265937A1 (en) * 2012-04-09 2013-10-10 Puneet Jain Machine type communication (mtc) via non-access stratum layer

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102427604A (zh) * 2011-12-02 2012-04-25 电信科学技术研究院 MTC Device触发消息的投递确认方法和设备
CN102523315A (zh) * 2011-12-22 2012-06-27 电信科学技术研究院 一种确定mtc-iwf实体的方法及装置
CN102547658A (zh) * 2011-12-22 2012-07-04 电信科学技术研究院 一种数据传输方法及装置

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
RESEARCH IN MOTION UK LIMITED: "S2-123810 Routing a Device Trigger to the target application.", 3GPP SA WG2 MEETING #93., 12 October 2012 (2012-10-12), pages 1 - 4, XP050683515 *
See also references of EP2919494A4 *

Also Published As

Publication number Publication date
US20150304796A1 (en) 2015-10-22
EP2919494A1 (en) 2015-09-16
CN103813276A (zh) 2014-05-21
EP2919494A4 (en) 2015-12-23
US9706334B2 (en) 2017-07-11

Similar Documents

Publication Publication Date Title
US11089500B2 (en) Machine type communication monitoring framework for 3GPP systems
CN103249013B (zh) 一种mtc用户设备触发信息的发送方法、系统和用户设备
CN107852669B (zh) 利用vnf的mtc服务管理的方法和系统
WO2012151981A1 (zh) 发送mtc设备触发信息的方法、系统和目标用户设备
WO2013170120A1 (en) Service capability server (scs) terminated short message service (sms) systems and methods
WO2012151963A1 (zh) 一种触发信息中有效时间的处理方法和系统
CN102244856B (zh) 一种mtc设备下行数据传输控制方法和设备
US9204273B2 (en) Method and system for trigger information transmission and protocol conversion
WO2013056486A1 (zh) 一种消息类型的指示方法、系统及装置
WO2014000337A1 (zh) 机器类型通信用户设备的通信方法及系统
EP2811786A1 (en) Method, system, and device for sending triggering information
WO2014048173A1 (zh) 一种小数据发送方法、系统及用户设备
WO2014071758A1 (zh) 信息的发送方法、mtc服务器、用户设备及mtc系统
WO2013063852A1 (zh) 设置触发信息有效时间方法、系统和用户设备
EP2941022B1 (en) Method and unit for processing triggering information of mtc device
WO2014029284A1 (zh) 拥塞控制方法及装置
WO2013102316A1 (zh) 响应触发信息的方法、系统和mtc用户设备
EP2827661B1 (en) System, apparatus, and method for triggering roaming mtc device

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: 13853033

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 14439166

Country of ref document: US

WWE Wipo information: entry into national phase

Ref document number: 2013853033

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: DE