WO2013127122A1 - 一种触发mtc设备的方法和系统 - Google Patents

一种触发mtc设备的方法和系统 Download PDF

Info

Publication number
WO2013127122A1
WO2013127122A1 PCT/CN2012/075147 CN2012075147W WO2013127122A1 WO 2013127122 A1 WO2013127122 A1 WO 2013127122A1 CN 2012075147 W CN2012075147 W CN 2012075147W WO 2013127122 A1 WO2013127122 A1 WO 2013127122A1
Authority
WO
WIPO (PCT)
Prior art keywords
mtc
mtc device
sgsn
trigger information
trigger
Prior art date
Application number
PCT/CN2012/075147
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 US14/380,137 priority Critical patent/US9380405B2/en
Priority to EP12870261.0A priority patent/EP2822305B1/en
Publication of WO2013127122A1 publication Critical patent/WO2013127122A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
    • 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/12—Messaging; Mailboxes; Announcements
    • H04W4/14—Short messaging services, e.g. short message services [SMS] or unstructured supplementary service data [USSD]
    • 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 the field of communications technologies, and in particular, to a method and system for triggering an MTC device. Background technique
  • Machine Type Communication refers to a data interaction between two entities that do not require human intervention.
  • MTC is a machine-like communication, a dialogue between a machine and a machine.
  • the number of MTC devices will greatly exceed the number of terminals in the existing H2H (Human to Human) communication.
  • the communication between these huge numbers of MTC devices will generate a large amount of data. It needs to be transmitted through the communication network, so the communication between the machine and the machine also needs to be managed on the network side.
  • the existing wireless communication network is the most efficient and promising information for MTC communication, and it is carried over the transmission technology because it does not need to be wired and has a wide coverage.
  • the MTC device In order to optimize the signaling/data transmission between the network side and the MTC device, the MTC device can only maintain the signaling connection with the control plane of the network side when the data interaction with the network is not required, and the MTC device is required. When the network side performs data interaction, the data connection of the user plane is established. In this way, when the MTC server needs to report data to the MTC device, it must trigger the MTC device to wake up the MTC device and establish a user-side data connection between the MTC device and the network.
  • the MTC device needs to have time control. Sign, according to the contract information of a certain MTC device and the strategy of the local network operator to jointly determine the
  • the communication time window of each MTC device is set by the network.
  • the MTC device can access the network only within the communication time window, so as to avoid network overload caused by a large number of MTC devices requesting access to the network at the same time.
  • the MTC server During the triggering of the MTC device by the MTC server, the MTC server generates a request to trigger the MTC device and sends the request to the 3GPP network. If the MTC device is an MTC device with time control features, the 3GPP network not only needs to verify that the MTC server is a legitimate authorization, but also triggers the MTC server of the MTC device, and also queries whether the MTC device is in the network for setting Within the communication time window. Only when the MTC device is in the communication time window, the MTC server can send trigger information to the MTC device.
  • the MTC device Since the MTC device is forcibly attached by the network at the end of its communication window time, if the MTC device is in an attached state, the MTC device must be in its communication window time; if the MTC device is in an unattached state, then the MTC device It may be outside of its communication window time or outside its communication window time.
  • the existing trigger mode can be used without determining the time control information.
  • no triggering method has been proposed for an MTC device that is not attached. Summary of the invention
  • the main object of the present invention is to provide a method and system for triggering an MTC device to solve the problem that the MTC device in the unattached state cannot be triggered in the prior art.
  • a method of triggering a machine type communication MTC device comprising:
  • the general packet radio service technology service support node SGSN/mobility management entity MME receives trigger information from the machine type communication operation function MTC-IWF, and the trigger information carries at least the international mobile subscriber identity IMSI of the MTC device to be triggered, and the The MTC device is Whether it has the ability to receive short messages;
  • the SGSN/MME determines that the MTC device is in an unattached state, and the MTC device is in a corresponding communication window, and the SGSN/MME waits for the MTC device to attach;
  • the MTC device attaches to the network before the end time of the communication window, and the SGSN/MME sends the trigger information to the MTC device; if the MTC device is not attached to the network before the end time of the communication window, The SGSN/MME sends a trigger information transmission report to the MTC-IWF. After receiving the trigger information transmission report, the MTC-IWF sends the trigger information to the short message service center SMS-SC for storage, and forwards the message to the corresponding MTC server. The trigger information transmission report.
  • the SGSN/MME sends the trigger information to the MTC device by using a network access service NAS signaling manner.
  • the method further includes: when the SGSN/MME sends the trigger information to the MTC device by using the NAS signaling manner, and the MTC device has the capability of receiving a short message, the SGSN/MME sends the trigger information to the SMS- SC, triggering the MTC device by means of a short message.
  • the method further includes:
  • the SGSN/MME determines whether the communication window of the MTC device is stored locally, stores the communication window of the MTC device locally, and determines whether the MTC device is in the communication window;
  • the SGSN/MME does not store the communication window of the MTC device locally, and further determines whether the time control information of the MTC device is stored locally, and the communication window of the MTC device is not stored locally but the time control of the MTC device is stored.
  • Information generating a communication window according to the time control information and the local network policy, and determining whether the MTC device is in the communication Within the message window; if the communication window of the MTC device is not stored locally and the time control information of the MTC device is not stored, the time control information of the MTC device is obtained from the home subscriber server HSS/home location register HLR, according to the The time control information and the local network policy generate a communication window, and then determine whether the MTC device is in the communication window.
  • the method also includes:
  • the SGSN/MME determines that the MTC device is in an unattached state, and the MTC device is outside the corresponding communication window, the SGSN/MME sends a trigger information transmission report to the MTC-IWF, and the MTC-IWF receives the trigger information transmission report. Afterwards, the trigger information is sent to the SMS-SC for saving, and the trigger information transmission report is forwarded to the corresponding MTC server.
  • the method further includes: the MTC server sends a trigger transmission request to the MTC-IWF, where the trigger transmission request carries an external identifier of the MTC device that needs to be triggered, a trigger reference code, Trigger information and the MTC server information;
  • the MTC server After determining, by the triggering transmission request, the MTC server is a valid MTC server, requesting the HSS/HLR to verify whether the MTC server is authorized to trigger the MTC device;
  • the HSS/HLR returns a response message to the MTC-IWF, where the response message carries information about whether the MTC server is authorized to trigger the MTC device, the IMSI of the MTC device, the SGSN/MME address, and whether the MTC device has received Short message ability;
  • the MTC-IWF determines, according to the response message, that the MTC server is authorized to trigger the MTC device, and then forwards the trigger information to the corresponding SGSN/MME.
  • the trigger information transmission report carries a reason for the trigger failure of the MTC device, and an IMSI and a communication window of the MTC device,
  • a system for triggering an MTC device comprising: an SGSN/MME, an MTC-IWF, an MTC device, an SMS-SC, and an MTC server;
  • the SGSN/MME is configured to receive trigger information from the MTC-IWF, where the trigger information carries at least an IMSI of the MTC device that needs to be triggered, and whether the MTC device has the capability of receiving a short message; and determining the MTC When the device is in an unattached state, and the MTC device is in a corresponding communication window, waiting for the MTC device to attach, if the MTC device is attached to the network before the communication window end time, sending the trigger information Giving the MTC device; if the MTC device is not attached to the network before the end of the communication window, sending a trigger information transmission report to the MTC-IWF,
  • the MTC-IWF is configured to send trigger information to the SGSN/MME, and after receiving the trigger information transmission report, send the trigger information to the SMS-SC for saving, and forward the trigger information transmission report to the corresponding MTC server;
  • the MTC device is configured to receive trigger information sent by the SGSN/MME;
  • the SMS-SC is configured to store trigger information from the MTC-IWF;
  • the MTC server is configured to receive a trigger information transmission report from the MTC-IWF.
  • the SGSN/MME is specifically configured to send the trigger information to the MTC device by using a NAS signaling manner; and is further configured to fail to send the trigger information to the MTC device by using the NAS signaling manner, and the MTC When the device has the ability to receive a short message, the trigger information is sent to the SMS-SC.
  • the SGSN/MME is further configured to: after determining that the MTC device is in an unattached state, further determining whether a communication window of the MTC device is stored locally, locally storing a communication window of the MTC device, and determining the Whether the MTC device is in the communication window; the SGSN/MME does not store the communication window of the MTC device locally, and further determines whether the time control information of the MTC device is stored locally, and the communication window of the MTC device is not stored locally.
  • the home location register HLR acquires time control information of the MTC device, generates a communication window according to the time control information and the local network policy, and determines whether the MTC device is in the communication window.
  • the SGSN/MME is further configured to send a trigger information transmission report to the MTC-IWF when determining that the MTC device is in an unattached state and the MTC device is outside a corresponding communication window;
  • the MTC-IWF is further configured to, after receiving the trigger information transmission report, send the trigger information to the SMS-SC for saving, and forward the trigger information transmission report to the corresponding MTC server.
  • the system also includes HSS/HLR,
  • the MTC server is further configured to send a trigger transmission request to the MTC-IWF, where the trigger transmission request carries an external identifier, a trigger reference code, a trigger information, and the MTC server information of the MTC device that needs to be triggered;
  • the MTC-IWF is further configured to: after determining that the MTC server is a valid MTC server according to the trigger transmission request, requesting the HSS/HLR to verify whether the MTC server is authorized to trigger the MTC device; and according to the HSS/ The response message of the HLR determines that the MTC server is authorized to trigger the MTC device, and then forwards the trigger information to the corresponding SGSN/MME;
  • the HSS/HLR configured to return a response message to the MTC-IWF, where the response message carries information about whether the MTC server is authorized to trigger the MTC device, an IMSI of the MTC device, an SGSN/MME address, and the Whether the MTC device has the ability to receive short messages.
  • the MTC server is further configured to receive the trigger information from the MTC-IWF After the message is output, the trigger process is initiated again when the next communication window time comes.
  • the SGSN/MME receives trigger information from the MTC-IWF; the SGSN/MME determines that the MTC device is in an unattached state, and the MTC device is in a corresponding communication window.
  • the MTC device attaches to the network before the end of the communication window, and the SGSN/MME sends the trigger information to the MTC device; the MTC device does not attach to the network before the end of the communication window, then the SGSN
  • the MME sends a trigger information transmission report to the MTC-IWF, and the MTC-IWF sends the trigger information to the SMS-SC for saving, and forwards the trigger information transmission report to the corresponding MTC server.
  • the MTC device in the unattached state can be triggered.
  • FIG. 1 is a schematic flowchart of a method for triggering an MTC device according to an embodiment of the present invention
  • FIG. 2 is a schematic diagram of a triggering process when an MTC device is in an attached state according to Embodiment 1 of the present invention
  • FIG. 3 is a schematic diagram of a triggering process of an MTC device in an unattached state according to Embodiment 2 of the present invention, but the MTC device is in a communication window thereof;
  • FIG. 4 is a schematic diagram of a triggering process of an MTC device in an unattached state in an embodiment 3 of the present invention, but the MTC device is in a communication window thereof;
  • FIG. 5 is a schematic diagram of a triggering process in which the MTC device is in an unattached state and the MTC device is not in its communication window according to Embodiment 4 of the present invention. detailed description
  • the basic idea of the embodiment of the present invention is:
  • the SGSN/MME receives trigger information from the MTC-IWF; the SGSN/MME determines that the MTC device is in an unattached state, and the MTC device is in a corresponding communication window.
  • the MTC device is attached to the network before the end of the communication window, and the SGSN/MME sends the trigger information to the MTC device; If the MTC device is not attached to the network before the end of the communication window, the SGSN/MME sends a trigger information transmission report to the MTC-IWF, and the MTC-IWF sends the trigger information to the SMS-SC for saving, and corresponding to The MTC server forwards the trigger information transmission report.
  • this type of MTC device can only access the network within the communication window time allocated by the network.
  • the MTC server triggers the MTC device with time control feature through the network, the network must first determine whether the MTC device is in its communication window time. Only when the MTC device is in its communication window time, the MTC server can trigger the MTC server. MTC device.
  • the network performs a de-attachment process for the MTC device, disconnecting the MTC device from the network. If the MTC device is in an attached state, the MTC device must be in its communication window; if the MTC device is in an unattached state, the MTC device may be in its communication window or may be outside its communication window.
  • the MTC server wants to trigger an MTC device, if the network finds that the MTC device is in an unattached state, but the MTC device is in its communication window, the MTC device may be attached to the network within the communication window time, so the network may be turned on.
  • a timer storing trigger information and waiting in the communication window of the MTC device, and immediately transmitting the trigger information to the MTC device once the MTC device is attached to the network; if the network finds that the MTC device is in an unattached state, and The MTC device is not in its communication window, so that the MTC device is not attached to the network in a short period of time, so the network can store the trigger information in the SMS-SC, so as to pass the short when the MTC device is attached to the network.
  • the message triggers the MTC device, and the network notifies the MTC server of the communication window time of the MTC device, and causes the MTC server to initiate the triggering process again when the communication window of the MTC device arrives.
  • the MTC-IWF and the HSS/HLR need not only authenticate the MTC server, but only the authorized MTC server triggers the specific MTC device, and the MTC-IWF queries the SGSN/MME to check whether the MTC device is in the attached state. And check that the MTC device is Whether it is in the communication window set by the network, different processing is performed on the MTC device in the communication window time and the MTC device in the communication window time, thereby reducing the burden on the network during the triggering process and improving the efficiency of the triggering process.
  • FIG. 1 is a schematic flowchart of a method for triggering an MTC device according to an embodiment of the present invention. As shown in FIG. 1, the method includes:
  • Step 101 The General Packet Radio Service Technology Service Support Node (SGSN) / Mobility Management Entity (MME) receives trigger information from a Machine Class Communication Operation Function (MTC-IWF).
  • SGSN General Packet Radio Service Technology Service Support Node
  • MME Mobility Management Entity
  • MTC-IWF Machine Class Communication Operation Function
  • the trigger information carries at least an international mobile subscriber identification code IMSI of the MTC device to be triggered, and whether the MTC device has the capability of receiving a short message.
  • the method may further include:
  • the MTC server sends a trigger transmission request to the MTC-IWF, where the trigger transmission request carries an external identifier of the MTC device that needs to be triggered, a trigger reference code (for preventing replay attacks), trigger information, and the MTC server information;
  • the MTC server After determining, by the triggering transmission request, the MTC server is a valid MTC server, requesting the HSS/HLR to verify whether the MTC server is authorized to trigger the MTC device;
  • the HSS/HLR returns a response message to the MTC-IWF, where the response message carries information about whether the MTC server is authorized to trigger the MTC device, the IMSI of the MTC device, the SGSN/MME address, and whether the MTC device has received Short message ability;
  • the MTC-IWF determines, according to the response message, that the MTC server is authorized to trigger the MTC device, and then forwards the trigger information to the corresponding SGSN/MME.
  • the MTC server requests the 3GPP network to transmit the trigger information by triggering the transmission request, where the trigger information is an operation that the MTC server should perform after the MTC device receives the trigger information, and the operation is performed by the MTC server and the MTC device.
  • the trigger information is an operation that the MTC server should perform after the MTC device receives the trigger information, and the operation is performed by the MTC server and the MTC device.
  • Step 102 The SGSN/MME determines whether the MTC device is in an attached state, and if so, Execute the existing process; otherwise, go to step 103.
  • Step 103 The SGSN/MME determines whether the MTC device is in the corresponding communication window, and if yes, performs step 104: Otherwise, go to step 107.
  • the method may further include:
  • the SGSN/MME determines whether the communication window of the MTC device is stored locally, stores the communication window of the MTC device locally, and determines whether the MTC device is in the communication window;
  • the SGSN/MME does not store the communication window of the MTC device locally, and further determines whether the time control information of the MTC device is stored locally, and the communication window of the MTC device is not stored locally but the time control of the MTC device is stored. And generating a communication window according to the time control information and the local network policy, and determining whether the MTC device is in the communication window; not storing the communication window of the MTC device locally and not storing the time of the MTC device Controlling the information, obtaining time control information of the MTC device from the home subscriber server HSS/home location register HLR, generating a communication window according to the time control information and the local network policy, and determining whether the MTC device is in the communication window Inside.
  • the time control information generally includes: a g ran t time interval, a forbidden time interval, and an access duration.
  • Step 104 The MTC device is in an unattached state, and the MTC device is in a corresponding communication window, and the SGSN/MME waits for the MTC device to attach.
  • Step 105 Determine whether the MTC device is attached to the network before the end of the communication window. If yes, go to step 106; otherwise, go to step 107.
  • Step 106 The SGSN/MME sends the trigger information to the MTC device.
  • the SGSN/MME generally transmits the trigger information to the MTC device through a Network Access Service (NAS) signaling manner.
  • NAS Network Access Service
  • the SGSN/MME sends the trigger information to the SMS-SC, and triggers the MTC device by means of a short message.
  • Step 107 The SGSN/MME sends a trigger information transmission report to the MTC-IWF.
  • the trigger information transmission report may carry the reason that the MTC device triggers failure, and the IMSI and the communication window of the MTC device.
  • Step 108 After receiving the trigger information transmission report, the MTC-IWF sends the trigger information to the short message service center (SMS-SC) for saving, and forwards the trigger information transmission report to the corresponding MTC server.
  • SMS-SC short message service center
  • the MTC server initiates the triggering process again when the next communication window time comes.
  • the trigger information can be transmitted to the MTC device by means of SMS (Short Message Service).
  • SMS Short Message Service
  • the embodiment of the present invention further provides a system for triggering an MTC device, where the system includes: an SGSN/MME, an MTC-IWF, an MTC device, an SMS-SC, and an MTC server; wherein the SGSN/MME is configured to receive from The trigger information of the MTC-IWF, the trigger information carries at least an IMSI of the MTC device to be triggered, and whether the MTC device has the capability of receiving a short message; and determining that the MTC device is in an unattached state, and the MTC Waiting for the MTC device to be attached when the device is in the corresponding communication window, and sending the trigger information to the MTC device if the MTC device is attached to the network before the communication window end time; the MTC device If the network is not attached to the network before the end time of the communication window, a trigger information transmission report is sent to the MTC-IWF.
  • the system includes: an SGSN/MME, an MTC-IWF, an MTC device
  • the MTC-IWF is configured to send trigger information to the SGSN/MME, and after receiving the trigger information transmission report, send the trigger information to the SMS-SC for saving, and send the corresponding MTC service Transmitting the trigger information transmission report by the server;
  • the MTC device is configured to receive trigger information sent by the SGSN/MME;
  • the SMS-SC is configured to store trigger information from the MTC-IWF;
  • the MTC server is configured to receive a trigger information transmission report from the MTC-IWF.
  • the SGSN/MME is specifically configured to send the trigger information to the MTC device by using a NAS signaling manner; and is further configured to fail to send the trigger information to the MTC device by using the NAS signaling manner, and the MTC When the device has the ability to receive a short message, the trigger information is sent to the SMS-SC.
  • the SGSN/MME is further configured to: after determining that the MTC device is in an unattached state, further determining whether a communication window of the MTC device is stored locally, locally storing a communication window of the MTC device, and determining the Whether the MTC device is in the communication window; the SGSN/MME does not store the communication window of the MTC device locally, and further determines whether the time control information of the MTC device is stored locally, and the communication window of the MTC device is not stored locally. But the time control information of the MTC device is stored, the communication window is generated according to the time control information and the local network policy, and then the MTC device is determined to be in the communication window; the communication of the MTC device is not stored locally.
  • the SGSN/MME is further configured to send a trigger information transmission report to the MTC-IWF when determining that the MTC device is in an unattached state and the MTC device is outside a corresponding communication window;
  • the MTC-IWF is further configured to: after receiving the trigger information transmission report, send the trigger information to the SMS-SC for saving, and forward the trigger information transmission report to the corresponding MTC server.
  • the system also includes HSS/HLR,
  • the MTC server is further configured to send a trigger transmission request to the MTC-IWF, where the trigger transmission request carries an external identifier, a trigger reference code, a trigger information, and the MTC server information of the MTC device that needs to be triggered;
  • the MTC-IWF is further configured to: after determining that the MTC server is a valid MTC server according to the trigger transmission request, requesting the HSS/HLR to verify whether the MTC server is authorized to trigger the MTC device; and according to the HSS/ The response message of the HLR determines that the MTC server is authorized to trigger the MTC device, and then forwards the trigger information to the corresponding SGSN/MME;
  • the HSS/HLR is configured to store subscription information (e.g., IMSI, time control information, etc.) of the MTC device, and optionally provide certain subscription information of the MTC device to other security entities.
  • the HSS/HLR is configured to return a response message to the MTC-IWF, where the response message carries information about whether the MTC server is authorized to trigger the MTC device, the IMSI of the MTC device, the SGSN/MME address, and the Whether the MTC device has the ability to receive short messages.
  • the MTC server is further configured to, after receiving the trigger information transmission from the MTC-IWF, initiate the triggering process again when the next communication window time arrives.
  • This embodiment provides a triggering process when the MTC device is in an attached state. As shown in FIG. 2, the process includes:
  • Step 201 The MTC server wants to trigger an MTC device. If the MTC server does not know how to connect to the MTC-IWF, the MTC server uses the external identifier of the MTC device to initiate an inquiry to the DNS, and queries the IP address and port of the MTC-IWF.
  • step 202 the DNS notifies the MTC server of the IP address and port of the MTC-IWF.
  • Step 203 The MTC server initiates an MTC device trigger transmission request to the MTC-IWF. This includes the external ID of the MTC device, the MTC server ID, the IP address and port of the MTC Server, and other information.
  • Step 204 The MTC-IWF authenticates the MTC server, checks whether the MTC server is an authorized server, and allows a trigger request to be sent.
  • Step 205 If the MTC server is a valid MTC server, the MTC-IWF sends an inquiry to the HSS/HLR, and the HSS/HLR authenticates the MTC server to see whether the MTC server authorizes the triggering of the MTC device, where the message includes the MTC device. External ID, MTC server ID.
  • Step 206 The HSS/HLR queries the IMSI of the MTC device by using the external identifier of the MTC device, and then queries whether the MTC server authorizes sending a trigger message to the MTC device, and the HSS/HLR returns the authentication result to the MTC-IWF. And informing the MTC server whether the MTC device is authorized to trigger, and notifying the MTC-IWF of the IMSI of the MTC device.
  • the HSS/HLR shall inform the MTC-IWF of the address of the SGSN/MME, which is the SGSN/MME address registered by the MTC device in the HSS by the last TAU/RAU procedure.
  • the HSS/HLR also informs the MTC-IWF if the MTC device has the ability to receive short messages.
  • Step 208 If the MTC server is authorized to trigger the MTC device, the MTC-IWF forwards the trigger information to the SGSN/MME notified by the HSS/HLR in step 207, where the IMSI of the MTC device is attached, and the MTC- The IWF wants to inform the SGSN/MME whether the MTC device has the ability to receive short messages.
  • Step 209 If the SGSN/MME detects that the MTC device is in an attached state, the MTC device must be in its communication window time. The SGSN/MME will transmit trigger information to the MTC device by means of NAS signaling. Step 210: The SGSN/MME sends a trigger information transmission report to the MTC-IWF, informing the MTC-IWF that the trigger information is successful or failed.
  • Step 211 If the MTC-IWF receives the indication that the trigger information fails to be transmitted through the NAS signaling, and the MTC device has the capability of receiving the short message, the MTC-IWF transmits the trigger information to the SMS-SC for saving, so as to pass the short The message mode triggers the MTC device.
  • Step 212 The network triggers the MTC device by using a short message mode.
  • This embodiment describes a triggering process in which the MTC device is in an unattached state, but the MTC device is in its communication window. In this case, the MTC device is attached to the network in the communication window. As shown in FIG. 3, the process specifically includes :
  • Step 301 The MTC server wants to trigger an MTC device. If the MTC server does not know how to connect to the MTC-IWF, the MTC server uses the external identifier of the MTC device to initiate an inquiry to the DNS, and queries the IP address and port of the MTC-IWF.
  • step 302 the DNS notifies the MTC server of the IP address and port of the MTC-IWF.
  • Step 304 The MTC-IWF authenticates the MTC server, checks whether the MTC server is an authorized server, and allows a trigger request to be sent.
  • Step 305 The MTC-IWF sends an inquiry to the HSS/HLR, and the HSS/HLR authenticates the MTC server to see whether the MTC server is authorized to trigger the MTC device.
  • the message includes the external identifier of the MTC device and the MTC server ID.
  • Step 306 The HSS/HLR queries the IMSI of the MTC device by using the external identifier of the MTC device, and then queries whether the MTC server authorizes sending a trigger message to the MTC device.
  • Step 307 The HSS/HLR returns an authentication result to the MTC-IWF, informing whether the MTC server is authorized to trigger the MTC device, and notifying the MTC-IWF of the IMSI of the MTC device.
  • the HSS/HLR shall inform the MTC-IWF of the address of the SGSN/MME, which is the SGSN/MME address registered by the MTC device in the HSS by the last TAU/RAU procedure.
  • the HSS/HLR also informs the MTC-IWF if the MTC device has the ability to receive short messages.
  • Step 308 If the MTC server is authorized to trigger the MTC device, the MTC-IWF forwards the trigger information to the SGSN/MME notified by the HSS/HLR in step 107, where the IMSI of the MTC device is attached, and the MTC- The IWF wants to inform the SGSN/MME whether the MTC device has the ability to receive short messages.
  • Step 309 If the SGSN/MME determines that the MTC device is in an unattached state, and if there is no valid time control information of the MTC device at the SGSN/MME, the HSS/HLR is queried, and the IMSI of the MTC device is included in the message.
  • Step 310 The HSS/HLR returns the time control information of the MTC device to the SGSN/MME, including a grant time interval, a forbidden time interval, an access duration 0 step 311, if the SGSN/MME does not have the MTC device. a communication window, the SGSN/MME randomizes a communication window as an effective communication window of the MTC device according to the local network policy and the time control information sent by the HSS/HLR; if the MSG device is in the SGSN/MME Communication window, then the communication window is an effective communication window of the MTC device.
  • Step 312 If the MTC device is in its active communication window, the SGSN/MME sets the waiting identifier of the MTC device, and stores trigger information, and starts a timer.
  • the length of the timer is the length of the current time to the end of the communication window.
  • Step 313 If the MTC device is attached to the network in the timer timing period, the SGSN/MME sends the trigger information to the MTC device by using the NAS signaling manner.
  • Step 314 The SGSN/MME sends a trigger information transmission report to the MTC-IWF, informing the MTC-IWF that the trigger information is successfully transmitted or failed.
  • Step 315 If the MTC-IWF receives the indication that the trigger information fails to be transmitted through the NAS signaling, and the MTC device has the capability of receiving the short message, the MTC-IWF transmits the trigger information to the SMS-SC for saving, so as to pass the short The message mode triggers the MTC device.
  • Step 316 The network triggers the MTC device by using a short message mode.
  • This embodiment describes a triggering process in which the MTC device is in an unattached state, but the MTC device is in its communication window. In this case, the MTC device is not attached to the network in the communication window, as shown in FIG. 4, the process is specific.
  • Step 401 The MTC server wants to trigger an MTC device. If the MTC server does not know how to connect to the MTC-IWF, the MTC server uses the external identifier of the MTC device to initiate an inquiry to the DNS, and queries the IP address and port of the MTC-IWF.
  • Step 402 The DNS informs the MTC server of the IP address and port of the MTC-IWF.
  • Step 404 The MTC-IWF authenticates the MTC server, checks whether the MTC server is an authorized server, and allows a trigger request to be sent.
  • Step 405 The MTC-IWF sends an inquiry to the HSS/HLR, and the HSS/HLR authenticates the MTC server to see whether the MTC server authorizes the MTC device to be triggered.
  • the message includes the external identifier of the MTC device and the MTC server ID.
  • Step 406 The HSS/HLR queries the IMSI of the MTC device by using the external identifier of the MTC device, and then queries whether the MTC server authorizes sending a trigger message to the MTC device.
  • Step 407 The HSS/HLR returns an authentication result to the MTC-IWF, informing whether the MTC server is authorized to trigger the MTC device, and notifying the MTC-IWF of the IMSI of the MTC device.
  • the HSS/HLR shall inform the MTC-IWF of the address of the SGSN/MME, which is the SGSN/MME address registered by the MTC device in the HSS by the last TAU/RAU procedure.
  • the HSS/HLR also informs the MTC-IWF if the MTC device has the ability to receive short messages.
  • Step 408 If the MTC server is authorized to trigger the MTC device, the MTC-IWF forwards the trigger information to the SGSN/MME notified by the HSS/HLR in step 107, where the IMSI of the MTC device is attached, and the MTC- The IWF wants to inform the SGSN/MME whether the MTC device has the ability to receive short messages.
  • Step 409 If the SGSN/MME determines that the MTC device is in an unattached state, and if there is no valid time control information of the MTC device at the SGSN/MME, the HSS/HLR is queried, and the IMSI of the MTC device is included in the message.
  • Step 410 The HSS/HLR returns time control information of the MTC device to the SGSN/MME, including a grant time interval, a forbidden time interval, an access duration 0 step 411, if the SGSN/MME does not have the MTC device. a communication window, the SGSN/MME randomizes a communication window as an effective communication window of the MTC device according to the local network policy and the time control information sent by the HSS/HLR; if the MSG device is in the SGSN/MME Communication window, then the communication window is an effective communication window of the MTC device.
  • Step 412 If the MTC device is in its active communication window, the SGSN/MME sets the waiting identifier of the MTC device, and stores the trigger information, and starts the timer.
  • the length of the timer is the length of the current time to the end of the communication window.
  • Step 413 If the timer timing period has expired, the MTC device has not been attached to the network, and the SGSN/MME sends a trigger information transmission message to the MTC-IWF, informing the MTC-IWF of the touch.
  • the IMSI and communication window of the MTC device is included in the trigger failure report.
  • Step 414 If the MTC device has the capability of receiving a short message, the MTC-IWF sends the trigger information to the SMS-SC for saving, so that the MTC device can trigger the MTC device through the short message when the MTC device is attached.
  • Step 415 The MTC-IWF forwards the trigger information transmission report to the MTC server, indicating that the failure reason is that the MTC device is not attached to the network within the communication window time.
  • the external flag and communication window of the MTC device are included in the trigger failure report, instructing the MTC server to initiate the trigger process again when the next communication window time comes.
  • This embodiment describes a triggering process in which the MTC device is in an unattached state, and the MTC device is not in the communication window. As shown in FIG. 5, the process specifically includes:
  • Step 501 The MTC server wants to trigger an MTC device. If the MTC server does not know how to connect to the MTC-IWF, the MTC server uses the external identifier of the MTC device to initiate an inquiry to the DNS, and queries the IP address and port of the MTC-IWF.
  • Step 502 The DNS informs the MTC server of the IP address and port of the MTC-IWF.
  • Step 504 The MTC-IWF authenticates the MTC server, checks whether the MTC server is an authorized server, and allows a trigger request to be sent.
  • Step 505 The MTC-IWF sends an inquiry to the HSS/HLR, and the HSS/HLR authenticates the MTC server to see whether the MTC server is authorized to trigger the MTC device.
  • the message includes the external identifier of the MTC device and the MTC server ID.
  • Step 506 the HSS/HLR queries the MTC device by using the external identifier of the MTC device.
  • the IMSI then querying whether the MTC server authorizes sending a triggering message to the MTC device, step 507, the HSS/HLR returns an authentication result to the MTC-IWF, informing whether the MTC server is authorized to trigger the MTC device, and
  • the IMSI of the MTC device informs the MTC-IWF.
  • the HSS/HLR shall inform the MTC-IWF of the address of the SGSN/MME, which is the SGSN/MME address registered by the MTC device in the HSS by the last TAU/RAU procedure.
  • the HSS/HLR also informs the MTC-IWF if the MTC device has the ability to receive short messages.
  • Step 508 If the MTC server is authorized to trigger the MTC device, the MTC-IWF forwards the trigger information to the SGSN/MME notified by the HSS/HLR in step 107, where the IMSI of the MTC device is attached, and the MTC- The IWF wants to inform the SGSN/MME whether the MTC device has the ability to receive short messages.
  • Step 509 If the SGSN/MME determines that the MTC device is in an unattached state, and if there is no valid time control information of the MTC device at the SGSN/MME, the HSS/HLR is queried, and the IMSI of the MTC device is included in the message.
  • Step 510 The HSS/HLR returns time control information of the MTC device to the SGSN/MME, including a grant time interval, a forbidden time interval, and an access duration.
  • Step 511 If the communication window of the MTC device is not in the SGSN/MME, the SGSN/MME randomizes a communication window to the MTC device according to the local network policy and the time control information sent by the HSS/HLR. An effective communication window; if there is a communication window of the MTC device in the SGSN/MME, the communication window is an effective communication window of the MTC device.
  • Step 512 If the MTC device is not in the valid communication window, the SGSN/MME sends a trigger information transmission report to the MTC-IWF, and informs the MTC-IWF that the triggering of the MTC device fails.
  • the reason for the failure is that the MTC device is not attached. And not in its communication window. Touch The IMSI and communication window of the MTC device is attached to the failure report.
  • Step 513 If the MTC device has the capability of receiving a short message, the MTC-IWF sends the trigger information to the SMS-SC for saving, so that the MTC device can be triggered by the short message when the MTC device is attached.
  • Step 514 The MTC-IWF forwards the trigger information transmission report to the MTC server, indicating that the failure reason is that the MTC device is in an unattached state and is not in its communication window.
  • the triggering failure report is accompanied by an external flag and communication window of the MTC device, instructing the MTC server to initiate the triggering process again when the next communication window time comes.

Abstract

本发明公开了一种触发机器类通信（MTC）设备的方法，包括：SGSN/MME接收来自MTC-IWF的触发信息；SGSN/MME判定所述MTC设备处于未附着状态、且所述MTC设备处于对应的通信窗口内，所述MTC设备在所述通信窗口结束时间之前附着到网络，则SGSN/MME将所述触发信息发送给所述MTC设备；所述MTC设备未在所述通信窗口结束时间之前附着到网络，则SGSN/MME向MTC-IWF发送触发信息传输报告，MTC-IWF将所述触发信息发送至SMS-SC保存，并向相应的MTC服务器转发所述触发信息传输报告。本发明还相应地公开了一种触发MTC设备的系统。通过本发明，能够触发处于未附着状态的MTC设备。

Description

一种触发 MTC设备的方法和系统 技术领域
本发明涉及通信技术领域， 尤其涉及一种触发 MTC设备的方法和系 统。 背景技术
机器通信（ Machine Type Communication, MTC )是指一种不需要人干 涉的两实体之间的数据交互。 换言之， MTC就是一种机器类的通信， 是机 器与机器之间的对话。
MTC 系统中， MTC设备的数量将会大大超过现有的 H2H(Human to Human)通信中的终端数量， 同时， 这些数量庞大的 MTC设备之间相互通 信将产生大量的数据， 这大量的数据都需要经过通信网络的传输， 所以这 种机器与机器之间的通信也需要有网络侧的管理。 现有的无线通信网络由 于无须布线， 并且覆盖范围广泛， 成为 MTC通信的最有效、 最有前景的信 息承载于传输技术。
在未来的产业中， MTC设备将用于各个行业， 如何处理这数量庞大的 MTC设备产生的庞大的数据交互， 成为急需解决的问题。 为了能够优化网 络侧和 MTC设备之间的信令 /数据传输，可以使 MTC设备在不需要和网络 进行数据交互的时候,仅仅保持与网络侧的控制面的信令连接，在需要 MTC 设备和网络侧进行数据交互的时候再建立起用户面的数据连接。这样， MTC 服务器需要 MTC设备上报数据的时候， 就要先触发 MTC设备， 将该 MTC 设备唤醒， 让 MTC设备和网络之间建立起用户面的数据连接。
同时， 为了避免大量的 MTC设备在同一时间一起接入到网络， 从而对 网络造成过重负担， 甚至导致网络瘫痪， MTC设备需要具有时间控制的特 征，根据某一 MTC设备的签约信息和本地网络运营商的策略来共同决定该
MTC设备的通信时间窗口。 每一个 MTC设备的通信时间窗口都是由网络 设置， 该 MTC设备只有在该通信时间窗口内才能够接入网络， 以避免大量 MTC设备同时请求接入网络而造成的网络过载问题。
在 MTC服务器触发 MTC设备的过程中， MTC服务器产生触发 MTC 设备的请求， 并将该请求发送给 3GPP网络。 如果该 MTC设备是具有时间 控制特征的 MTC设备， 那么 3GPP网络不仅要验证所述 MTC服务器是合 法的授权可以触发该 MTC设备的 MTC服务器， 还要查询该 MTC设备是 否处于网络为其设定的通信时间窗口内。只有 MTC设备处于所述通信时间 窗口内， MTC服务器才能够向该 MTC设备发送触发信息。
由于 MTC设备在其通信窗口时间结束时会被网络强行去附着， 所以， 如果 MTC设备处于附着状态， 则 MTC设备必处于其通信窗口时间内； 如 果 MTC设备处于未附着的状态， 那么该 MTC设备可能在其通信窗口时间 内， 也可能在其通信窗口时间外。 对于已附着的 MTC设备， 可以使用现有 触发方式而无需对其时间控制信息进行判断， 但对于未附着的 MTC设备， 有必要在触发时对其时间控制信息进行判断以提高触发效率。 目前， 尚未 提出适用于处于未附着状态的 MTC设备的触发方法。 发明内容
有鉴于此，本发明的主要目的在于提供一种触发 MTC设备的方法和系 统， 用以解决现有技术中无法触发处于未附着状态的 MTC设备的问题。
为达到上述目的， 本发明实施例的技术方案是这样实现的：
一种触发机器类通信 MTC设备的方法， 包括：
通用分组无线服务技术服务支持节点 SGSN/移动性管理实体 MME接 收来自机器类通信操作功能 MTC-IWF的触发信息，所述触发信息至少携带 需要触发的 MTC设备的国际移动用户识别码 IMSI、以及所述 MTC设备是 否具有接收短消息的能力；
SGSN/MME判定所述 MTC设备处于未附着状态、且所述 MTC设备处 于对应的通信窗口内， 则 SGSN/MME等待所述 MTC设备附着；
所述 MTC 设备在所述通信窗口结束时间之前附着到网络， 则 SGSN/MME将所述触发信息发送给所述 MTC设备；所述 MTC设备未在所 述通信窗口结束时间之前附着到网络， 则 SGSN/MME向 MTC-IWF发送触 发信息传输报告， MTC-IWF收到所述触发信息传输报告后， 将所述触发信 息发送至短消息服务中心 SMS-SC保存，并向相应的 MTC服务器转发所述 触发信息传输报告。
所述 SGSN/MME 将所述触发信息发送给所述 MTC 设备为： SGSN/MME通过网络接入服务 NAS信令方式将所述触发信息发送给所述 MTC设备，
该方法还包括： SGSN/MME通过 NAS信令方式向所述 MTC设备发送 所述触发信息失败、 且所述 MTC 设备具有接收短消息的能力， 则 SGSN/MME将所述触发信息发送至 SMS-SC, 通过短消息的方式触发所述 MTC设备。
所述 SGSN/MME判定所述 MTC设备处于未附着状态之后， 该方法还 包括：
SGSN/MME判断本地是否存储有所述 MTC设备的通信窗口， 本地存 储有所述 MTC设备的通信窗口， 再判断所述 MTC设备是否处于所述通信 窗口内；
SGSN/MME本地未存储所述 MTC设备的通信窗口， 则进一步判断本 地是否存储有所述 MTC设备的时间控制信息， 本地未存储所述 MTC设备 的通信窗口但存储有所述 MTC设备的时间控制信息，则根据所述时间控制 信息和本地网络策略生成通信窗口，再判断所述 MTC设备是否处于所述通 信窗口内； 本地未存储所述 MTC设备的通信窗口且未存储所述 MTC设备 的时间控制信息，则从归属用户服务器 HSS/归属位置寄存器 HLR获取所述 MTC设备的时间控制信息， 根据所述时间控制信息和本地网络策略生成通 信窗口， 再判断所述 MTC设备是否处于所述通信窗口内。
该方法还包括：
SGSN/MME判定所述 MTC设备处于未附着状态、且所述 MTC设备处 于对应的通信窗口外，则 SGSN/MME向 MTC-IWF发送触发信息传输报告， MTC-IWF收到所述触发信息传输报告后， 将所述触发信息发送至 SMS-SC 保存， 并向相应的 MTC服务器转发所述触发信息传输报告。
所述 SGSN/MME接收来自 MTC-IWF的触发信息之前，该方法还包括： MTC服务器向 MTC-IWF发送触发传输请求， 所述触发传输请求携带 需要触发的 MTC设备的外部标识、 触发参考码、 触发信息以及所述 MTC 服务器信息；
MTC-IWF根据所述触发传输请求判定所述 MTC服务器是合法的 MTC 服务器后，请求 HSS/HLR验证所述 MTC服务器是否被授权触发所述 MTC 设备；
HSS/HLR向 MTC-IWF返回应答消息， 所述应答消息携带所述 MTC 服务器是否被授权触发所述 MTC设备的信息、 所述 MTC设备的 IMSI、 SGSN/MME地址以及所述 MTC设备是否具有接收短信息的能力；
MTC-IWF根据所述应答消息判定所述 MTC服务器被授权触发所述 MTC设备， 则向相应的 SGSN/MME转发触发信息。
所述触发信息传输报告携带所述 MTC设备触发失败的原因， 以及所述 MTC设备的 IMSI和通信窗口，
所述 MTC-IWF向相应的 MTC服务器转发所述触发信息传输报告后， 所述 MTC服务器在下一个通信窗口时间到来时再次发起触发过程。 一种触发 MTC设备的系统， 包括： SGSN/MME、 MTC-IWF, MTC设 备、 SMS-SC和 MTC服务器； 其中，
所述 SGSN/MME, 设置为接收来自 MTC-IWF的触发信息， 所述触发 信息至少携带需要触发的 MTC设备的 IMSI、以及所述 MTC设备是否具有 接收短消息的能力； 以及在判定所述 MTC设备处于未附着状态、 且所述 MTC设备处于对应的通信窗口内时， 等待所述 MTC设备附着， 如果所述 MTC设备在所述通信窗口结束时间之前附着到网络， 则将所述触发信息发 送给所述 MTC设备； 所述 MTC设备未在所述通信窗口结束时间之前附着 到网络， 则向 MTC-IWF发送触发信息传输报告，
所述 MTC-IWF, 设置为向 SGSN/MME发送触发信息， 以及在收到触 发信息传输报告后， 将触发信息发送至 SMS-SC保存， 并向相应的 MTC服 务器转发所述触发信息传输报告；
所述 MTC设备， 设置为接收 SGSN/MME发送的触发信息；
所述 SMS-SC, 设置为存储来自 MTC-IWF的触发信息；
所述 MTC服务器， 设置为接收来自 MTC-IWF的触发信息传输报告。 所述 SGSN/MME, 具体设置为通过 NAS信令方式将所述触发信息发 送给所述 MTC设备；以及还设置为在通过 NAS信令方式向 MTC设备发送 所述触发信息失败、 且所述 MTC设备具有接收短消息的能力时， 将所述触 发信息发送至 SMS-SC。
所述 SGSN/MME, 还设置为在判定所述 MTC设备处于未附着状态之 后， 进一步判断本地是否存储有所述 MTC设备的通信窗口， 本地存储有所 述 MTC设备的通信窗口，再判断所述 MTC设备是否处于所述通信窗口内； SGSN/MME本地未存储所述 MTC设备的通信窗口， 则进一步判断本地是 否存储有所述 MTC设备的时间控制信息， 本地未存储所述 MTC设备的通 信窗口但存储有所述 MTC设备的时间控制信息，则根据所述时间控制信息 和本地网络策略生成通信窗口，再判断所述 MTC设备是否处于所述通信窗 口内； 本地未存储所述 MTC设备的通信窗口且未存储所述 MTC设备的时 间控制信息，则从归属用户服务器 HSS/归属位置寄存器 HLR获取所述 MTC 设备的时间控制信息， 根据所述时间控制信息和本地网络策略生成通信窗 口， 再判断所述 MTC设备是否处于所述通信窗口内。
所述 SGSN/MME, 还设置为在判定所述 MTC设备处于未附着状态、 且所述 MTC设备处于对应的通信窗口外时， 向 MTC-IWF发送触发信息传 输报告；
所述 MTC-IWF, 还设置为在收到所述触发信息传输报告后， 将所述触 发信息发送至 SMS-SC保存，并向相应的 MTC服务器转发所述触发信息传 输报告。
该系统还包括 HSS/HLR,
所述 MTC服务器， 还设置为向 MTC-IWF发送触发传输请求， 所述触 发传输请求携带需要触发的 MTC设备的外部标识、 触发参考码、 触发信息 以及所述 MTC服务器信息；
所述 MTC-IWF, 还设置为根据所述触发传输请求判定所述 MTC服务 器是合法的 MTC服务器后， 请求 HSS/HLR验证所述 MTC服务器是否被 授权触发所述 MTC设备； 以及根据来自 HSS/HLR 的应答消息判定所述 MTC服务器被授权触发所述 MTC设备后，向相应的 SGSN/MME转发触发 信息；
所述 HSS/HLR, 设置为向 MTC-IWF返回应答消息， 所述应答消息携 带所述 MTC服务器是否被授权触发所述 MTC设备的信息、 所述 MTC设 备的 IMSI、 SGSN/MME地址以及所述 MTC设备是否具有接收短信息的能 力。
所述 MTC服务器， 还设置为在收到来自 MTC-IWF的所述触发信息传 输 ·^艮告后， 在下一个通信窗口时间到来时再次发起触发过程。
本发明实施例触发 MTC设备的方法和系统， SGSN/ MME接收来自 MTC-IWF的触发信息； SGSN/MME判定所述 MTC设备处于未附着状态、 且所述 MTC设备处于对应的通信窗口内， 所述 MTC设备在所述通信窗口 结束时间之前附着到网络，则 SGSN/MME将所述触发信息发送给所述 MTC 设备； 所述 MTC 设备未在所述通信窗口结束时间之前附着到网络， 则 SGSN/MME向 MTC-IWF发送触发信息传输报告， MTC-IWF将所述触发信 息发送至 SMS-SC保存，并向相应的 MTC服务器转发所述触发信息传输报 告。通过本发明实施例所述的方案，能够触发处于未附着状态的 MTC设备。 附图说明
图 1为本发明实施例触发 MTC设备的方法流程示意图；
图 2为本发明实施例 1 中 MTC设备处于附着状态时的触发流程示意 图；
图 3为本发明实施例 2中 MTC设备处于未附着状态下， 但是 MTC设 备在其通信窗口内的一种触发流程示意图；
图 4为本发明实施例 3中 MTC设备处于未附着状态下， 但是 MTC设 备在其通信窗口内的一种触发流程示意图；
图 5为本发明实施例 4中 MTC设备处于未附着状态下， 同时 MTC设 备又不在其通信窗口内的触发流程示意图。 具体实施方式
本发明实施例的基本思想是： SGSN/ MME接收来自 MTC-IWF的触发 ( trigger )信息； SGSN/MME判定所述 MTC设备处于未附着状态、 且所述 MTC设备处于对应的通信窗口内， 所述 MTC设备在所述通信窗口结束时 间之前附着到网络，则 SGSN/MME将所述触发信息发送给所述 MTC设备； 所述 MTC设备未在所述通信窗口结束时间之前附着到网络，则 SGSN/MME 向 MTC-IWF发送触发信息传输报告， MTC-IWF将所述触发信息发送至 SMS-SC保存， 并向相应的 MTC服务器转发所述触发信息传输报告。
由于某些 MTC设备具有时间控制特征， 这一类的 MTC设备只有在网 络为其分配的通信窗口时间内才能够接入网络。 MTC服务器在通过网络触 发具有时间控制特征的 MTC设备时， 网络必须先确定该 MTC设备是否处 于其通信窗口时间内， 只有该 MTC设备处于其通信窗口时间内， MTC月良 务器才能够触发该 MTC设备。
因为 MTC设备在其通信窗口结束时， 网络会为该 MTC设备执行去附 着过程， 使 MTC设备断开和网络的连接。 如果 MTC设备处于已附着的状 态， 那么该 MTC设备一定位于其通信窗口内； 如果 MTC设备处于未附着 状态，那么该 MTC设备可能处于其通信窗口内，也可能处于其通信窗口外。 当 MTC服务器要触发某 MTC设备时， 如果网络发现该 MTC设备处于未 附着状态， 但该 MTC设备处于其通信窗口内， 该 MTC设备有可能会在通 信窗口时间内附着到网络， 所以网络可以开启一个定时器， 在该 MTC设备 的通信窗口内储存触发信息并进行等待，一旦该 MTC设备附着到网络就可 以立即将触发信息发送给该 MTC设备； 如果网络发现该 MTC设备处于未 附着状态， 并且该 MTC设备未处于其通信窗口内， 那么认为该 MTC设备 在近段时间内都不会附着到网络， 所以网络可以将触发信息储存在 SMS-SC,目的在于当 MTC设备附着到网络时通过短消息触发该 MTC设备， 同时网络将该 MTC设备的通信窗口时间告知 MTC服务器， 让 MTC服务 器在该 MTC设备的通信窗口到达时再次发起触发过程。
本发明实施例中， MTC-IWF、 HSS/HLR不仅仅要认证 MTC服务器， 只让授权的 MTC服务器触发特定的 MTC设备， 而且 MTC-IWF要询问 SGSN/MME, 查看该 MTC设备是否处于附着状态并且查看该 MTC设备是 否处于网络为其设定的通信窗口内，对于处于通信窗口时间内的 MTC设备 和处于通信窗口时间外的 MTC设备进行不同的处理，减少触发过程时网络 的负担和提高触发流程的效率。
图 1为本发明实施例触发 MTC设备的方法流程示意图， 如图 1所示， 该方法包括：
步驟 101 : 通用分组无线服务技术服务支持节点（SGSN ) /移动性管理 实体（MME )接收来自机器类通信操作功能（MTC-IWF ) 的触发信息。
这里，所述触发信息至少携带需要触发的 MTC设备的国际移动用户识 别码 IMSI、 以及所述 MTC设备是否具有接收短消息的能力。
需要说明的是， 该步驟之前， 该方法还可以包括：
MTC服务器向 MTC-IWF发送触发传输请求， 所述触发传输请求携带 需要触发的 MTC设备的外部标识、 触发参考码 (用于防止重放攻击）、 触发 信息以及所述 MTC服务器信息；
MTC-IWF根据所述触发传输请求判定所述 MTC服务器是合法的 MTC 服务器后，请求 HSS/HLR验证所述 MTC服务器是否被授权触发所述 MTC 设备；
HSS/HLR向 MTC-IWF返回应答消息， 所述应答消息携带所述 MTC 服务器是否被授权触发所述 MTC设备的信息、 所述 MTC设备的 IMSI、 SGSN/MME地址以及所述 MTC设备是否具有接收短信息的能力；
MTC-IWF根据所述应答消息判定所述 MTC服务器被授权触发所述 MTC设备， 则向相应的 SGSN/MME转发触发信息。
需要说明的是， MTC服务器通过触发传输请求请求 3GPP网络传输触 发信息，所述触发信息是 MTC服务器指示 MTC设备在收到该触发信息后， 应该执行的操作， 该操作是 MTC服务器和 MTC设备之间协商的行为。
步驟 102: SGSN/MME判断所述 MTC设备是否处于附着状态，如果是， 执行现有流程； 否则， 执行步驟 103。
步驟 103: SGSN/MME判断所述 MTC设备是否处于对应的通信窗口内， 如果是， 执行步驟 104: 否则， 转到步驟 107。
需要说明的是， 该步驟之前， 该方法还可以包括：
SGSN/MME判断本地是否存储有所述 MTC设备的通信窗口， 本地存 储有所述 MTC设备的通信窗口， 再判断所述 MTC设备是否处于所述通信 窗口内；
SGSN/MME本地未存储所述 MTC设备的通信窗口， 则进一步判断本 地是否存储有所述 MTC设备的时间控制信息， 本地未存储所述 MTC设备 的通信窗口但存储有所述 MTC设备的时间控制信息，则根据所述时间控制 信息和本地网络策略生成通信窗口，再判断所述 MTC设备是否处于所述通 信窗口内； 本地未存储所述 MTC设备的通信窗口且未存储所述 MTC设备 的时间控制信息，则从归属用户服务器 HSS/归属位置寄存器 HLR获取所述 MTC设备的时间控制信息， 根据所述时间控制信息和本地网络策略生成通 信窗口， 再判断所述 MTC设备是否处于所述通信窗口内。
其中， 时间控制信息一般包括： 允许时间间隔（ grant time interval )、 禁 止时间间隔 ( forbidden time interval ), 接入时长 ( access duration )。
步驟 104: 所述 MTC设备处于未附着状态、 且所述 MTC设备处于对 应的通信窗口内， 则 SGSN/MME等待所述 MTC设备附着。
步驟 105: 判断所述 MTC设备是否在所述通信窗口结束时间之前附着 到网络， 如果是， 执行步驟 106; 否则， 执行步驟 107。
步驟 106: SGSN/MME将所述触发信息发送给所述 MTC设备。
这里， SGSN/MME—般通过网络接入服务（NAS )信令方式将所述触 发信息发送给所述 MTC设备。
需要说明的是，如果 SGSN/MME通过 NAS信令方式向所述 MTC设备 发送所述触发信息失败、 且所述 MTC 设备具有接收短消息的能力， 则
SGSN/MME将所述触发信息发送至 SMS-SC, 通过短消息的方式触发所述 MTC设备。
步驟 107: SGSN/MME向 MTC-IWF发送触发信息传输报告。
这里， 所述触发信息传输报告可以携带所述 MTC设备触发失败的原 因， 以及所述 MTC设备的 IMSI和通信窗口。
步驟 108: MTC-IWF收到所述触发信息传输报告后， 将所述触发信息 发送至短消息服务中心 （SMS-SC )保存， 并向相应的 MTC服务器转发所 述触发信息传输报告。
需要说明的是， 所述 MTC-IWF向相应的 MTC服务器转发所述触发信 息传输报告后，所述 MTC服务器在下一个通信窗口时间到来时再次发起触 发过程。
SMS-SC存储来自 MTC-IWF的触发信息后，可以以 SMS(Short Message Service)的方式将触发信息传输给 MTC设备。
本发明实施例还相应地提出一种触发 MTC设备的系统， 该系统包括： SGSN/MME, MTC-IWF, MTC设备、 SMS-SC和 MTC服务器； 其中， 所述 SGSN/MME, 设置为接收来自 MTC-IWF的触发信息， 所述触发 信息至少携带需要触发的 MTC设备的 IMSI、 以及所述 MTC设备是否具有 接收短消息的能力； 以及在判定所述 MTC设备处于未附着状态、 且所述 MTC设备处于对应的通信窗口内时， 等待所述 MTC设备附着， 如果所述 MTC设备在所述通信窗口结束时间之前附着到网络， 则将所述触发信息发 送给所述 MTC设备； 所述 MTC设备未在所述通信窗口结束时间之前附着 到网络， 则向 MTC-IWF发送触发信息传输报告，
所述 MTC-IWF, 设置为向 SGSN/MME发送触发信息， 以及在收到触 发信息传输报告后， 将触发信息发送至 SMS-SC保存， 并向相应的 MTC服 务器转发所述触发信息传输报告；
所述 MTC设备， 设置为接收 SGSN/MME发送的触发信息；
所述 SMS-SC, 设置为存储来自 MTC-IWF的触发信息；
所述 MTC服务器， 设置为接收来自 MTC-IWF的触发信息传输报告。 所述 SGSN/MME, 具体设置为通过 NAS信令方式将所述触发信息发 送给所述 MTC设备；以及还设置为在通过 NAS信令方式向 MTC设备发送 所述触发信息失败、 且所述 MTC设备具有接收短消息的能力时， 将所述触 发信息发送至 SMS-SC。
所述 SGSN/MME, 还设置为在判定所述 MTC设备处于未附着状态之 后， 进一步判断本地是否存储有所述 MTC设备的通信窗口， 本地存储有所 述 MTC设备的通信窗口，再判断所述 MTC设备是否处于所述通信窗口内； SGSN/MME本地未存储所述 MTC设备的通信窗口， 则进一步判断本地是 否存储有所述 MTC设备的时间控制信息， 本地未存储所述 MTC设备的通 信窗口但存储有所述 MTC设备的时间控制信息，则根据所述时间控制信息 和本地网络策略生成通信窗口，再判断所述 MTC设备是否处于所述通信窗 口内； 本地未存储所述 MTC设备的通信窗口且未存储所述 MTC设备的时 间控制信息，则从归属用户服务器 HSS/归属位置寄存器 HLR获取所述 MTC 设备的时间控制信息， 根据所述时间控制信息和本地网络策略生成通信窗 口， 再判断所述 MTC设备是否处于所述通信窗口内。
所述 SGSN/MME, 还设置为在判定所述 MTC设备处于未附着状态、 且所述 MTC设备处于对应的通信窗口外时， 向 MTC-IWF发送触发信息传 输报告；
所述 MTC-IWF, 还设置为在收到所述触发信息传输报告后， 将所述触 发信息发送至 SMS-SC保存，并向相应的 MTC服务器转发所述触发信息传 输报告。 该系统还包括 HSS/HLR,
所述 MTC服务器， 还设置为向 MTC-IWF发送触发传输请求， 所述触 发传输请求携带需要触发的 MTC设备的外部标识、 触发参考码、 触发信息 以及所述 MTC服务器信息；
所述 MTC-IWF, 还设置为根据所述触发传输请求判定所述 MTC服务 器是合法的 MTC服务器后， 请求 HSS/HLR验证所述 MTC服务器是否被 授权触发所述 MTC设备； 以及根据来自 HSS/HLR 的应答消息判定所述 MTC服务器被授权触发所述 MTC设备后，向相应的 SGSN/MME转发触发 信息；
所述 HSS/HLR, 设置为存储 MTC设备的签约信息 (如 IMSI、 时间控制 信息等)， 并可选地向其他安全实体提供所述 MTC设备的某些签约信息。 本发明中， HSS/HLR设置为向 MTC-IWF返回应答消息， 所述应答消息携 带所述 MTC服务器是否被授权触发所述 MTC设备的信息、 所述 MTC设 备的 IMSI、 SGSN/MME地址以及所述 MTC设备是否具有接收短信息的能 力。
所述 MTC服务器， 还设置为在收到来自 MTC-IWF的所述触发信息传 输 ·^艮告后， 在下一个通信窗口时间到来时再次发起触发过程。
下面结合具体实施例对本发明作进一步详细说明。 实施例 1
本实施例提供了 MTC设备处于附着状态时的触发流程， 如图 2所示， 该流程包括：
步驟 201 , MTC服务器想要触发某 MTC设备， 如果 MTC服务器不知 道怎样连接上 MTC-IWF, 那么 MTC服务器使用该 MTC设备的外部标识 向 DNS发起询问 , 询问 MTC-IWF的 IP地址和端口。
步驟 202, DNS将 MTC-IWF的 IP地址和端口告知 MTC服务器。 步驟 203 , MTC服务器向 MTC-IWF发起 MTC设备触发传输请求。 其 中包括 MTC设备的外部标识、 MTC服务器 ID、 MTC Server的 IP地址及 端口和其他信息。
步驟 204, MTC-IWF认证该 MTC服务器， 查看该 MTC服务器是否是 授权的服务器， 是否允许发送触发请求。
步驟 205 , 如果所述 MTC服务器是合法的 MTC服务器， MTC-IWF向 HSS/HLR发起询问， 让 HSS/HLR认证该 MTC服务器， 看该 MTC服务器 是否授权触发该 MTC设备， 消息中包括 MTC设备的外部标识、 MTC服务 器 ID。
步驟 206, HSS/HLR通过所述 MTC设备的外部标识查询到 MTC设备 的 IMSI,然后查询所述 MTC服务器是否授权向所述 MTC设备发送触发信 步驟 207, HSS/HLR向 MTC-IWF返回认证结果， 告知所述 MTC服务 器是否被授权触发所述 MTC 设备， 并将所述 MTC 设备的 IMSI 告知 MTC-IWF。 HSS/HLR 要将 SGSN/MME 的地址告知 MTC-IWF , 所述 SGSN/MME地址是 MTC设备通过上一次 TAU/RAU过程在 HSS中注册的 SGSN/MME地址。 HSS/HLR还要告知 MTC-IWF , 所述 MTC设备是否具 有接收短消息的能力。
步驟 208, 如果所述 MTC服务器是授权可以触发所述 MTC设备的， MTC-IWF将触发信息转发给步驟 207中 HSS/HLR告知的 SGSN/MME,其 中附带所述 MTC设备的 IMSI, 并且 MTC-IWF要告知 SGSN/MME, 所述 MTC设备是否具有接收短消息的能力。
步驟 209, 如果 SGSN/MME检测到该 MTC设备处于附着状态， 则该 MTC设备必位于其通信窗口时间内。 SGSN/MME将通过 NAS信令的方式 向 MTC设备传输触发信息。 步驟 210, SGSN/MME向 MTC-IWF发送一个触发信息传输报告， 告 知 MTC-IWF传输触发信息成功或失败。
步驟 211 , 如果 MTC-IWF收到触发信息通过 NAS信令传送失败的指 示， 并且该 MTC设备有接收短消息的能力， 那么 MTC-IWF将该触发信息 传送至 SMS-SC中保存， 以便通过短消息方式触发该 MTC设备。
步驟 212, 网络通过短消息方式触发该 MTC设备。 实施例 2
本实施例描述 MTC设备处于未附着状态下， 但是 MTC设备在其通信 窗口内的一种触发流程， 这种情况下 MTC设备在通信窗口内附着到了网 络， 如图 3所示， 该流程具体包括：
步驟 301 , MTC服务器想要触发某 MTC设备， 如果 MTC服务器不知 道怎样连接上 MTC-IWF, 那么 MTC服务器使用该 MTC设备的外部标识 向 DNS发起询问 , 询问 MTC-IWF的 IP地址和端口。
步驟 302, DNS将 MTC-IWF的 IP地址和端口告知 MTC服务器。 步驟 303 , MTC服务器向 MTC-IWF发起 MTC设备触发传输请求。 其 中包括 MTC设备的外部标识、 MTC服务器 ID、 MTC Server的 IP地址及 端口和其他信息。
步驟 304, MTC-IWF认证该 MTC服务器， 查看该 MTC服务器是否是 授权的服务器， 是否允许发送触发请求。
步驟 305 , MTC-IWF向 HSS/HLR发起询问，让 HSS/HLR认证该 MTC 服务器， 看该 MTC服务器是否授权触发该 MTC设备， 消息中包括 MTC 设备的外部标识、 MTC服务器 ID。
步驟 306, HSS/HLR通过所述 MTC设备的外部标识查询到 MTC设备 的 IMSI,然后查询所述 MTC服务器是否授权向所述 MTC设备发送触发信 步驟 307, HSS/HLR向 MTC-IWF返回认证结果， 告知所述 MTC服务 器是否被授权触发所述 MTC 设备， 并将所述 MTC 设备的 IMSI 告知 MTC-IWF。 HSS/HLR 要将 SGSN/MME 的地址告知 MTC-IWF , 所述 SGSN/MME地址是 MTC设备通过上一次 TAU/RAU过程在 HSS中注册的 SGSN/MME地址。 HSS/HLR还要告知 MTC-IWF , 所述 MTC设备是否具 有接收短消息的能力。
步驟 308, 如果所述 MTC服务器是授权可以触发所述 MTC设备的， MTC-IWF将触发信息转发给步驟 107中 HSS/HLR告知的 SGSN/MME,其 中附带所述 MTC设备的 IMSI, 并且 MTC-IWF要告知 SGSN/MME, 所述 MTC设备是否具有接收短消息的能力。
步驟 309, 如果 SGSN/MME判断 MTC设备处于未附着状态， 并且如 果 SGSN/MME 处没有所述 MTC 设备的有效时间控制信息， 则询问 HSS/HLR , 消息中附带所述 MTC设备的 IMSI。
步驟 310, HSS/HLR给所述 SGSN/MME返回所述 MTC设备的时间控 制信息 , 包括 grant time interval , forbidden time interval, access duration 0 步驟 311 , 如果所述 SGSN/MME中没有所述 MTC设备的通信窗口， 那么该 SGSN/MME根据本地网络策略和 HSS/HLR发送过来的时间控制信 息， 随机化一个通信窗口为所述 MTC 设备的有效通信窗口； 如果所述 SGSN/MME中有所述 MTC设备的通信窗口， 那么该通信窗口为所述 MTC 设备的有效通信窗口。
步驟 312,如果所述 MTC设备在其有效通信窗口内，所述 SGSN/MME 将所述 MTC设备的等待标识置位， 并存储触发信息， 开启定时器。 所述定 时器的长度为当前时间到通信窗口结束时间的长度。
步驟 313, 如果在所述定时器定时周期内， MTC设备附着到了网络， 所述 SGSN/MME通过 NAS信令方式将触发信息发送给 MTC设备。 步驟 314, SGSN/MME向 MTC-IWF发送一个触发信息传输报告， 告 知 MTC-IWF传输触发信息成功或失败。
步驟 315, 如果 MTC-IWF收到触发信息通过 NAS信令传送失败的指 示， 并且该 MTC设备有接收短消息的能力， 那么 MTC-IWF将该触发信息 传送至 SMS-SC中保存， 以便通过短消息方式触发该 MTC设备。
步驟 316, 网络通过短消息方式触发该 MTC设备。 实施例 3
本实施例描述 MTC设备处于未附着状态下， 但是 MTC设备在其通信 窗口内的一种触发流程， 这种情况下 MTC设备在通信窗口内未附着到网 络， 如图 4所示， 该流程具体包括：
步驟 401 , MTC服务器想要触发某 MTC设备， 如果 MTC服务器不知 道怎样连接上 MTC-IWF, 那么 MTC服务器使用该 MTC设备的外部标识 向 DNS发起询问 , 询问 MTC-IWF的 IP地址和端口。
步驟 402, DNS将 MTC-IWF的 IP地址和端口告知 MTC服务器。 步驟 403 , MTC服务器向 MTC-IWF发起 MTC设备触发传输请求。 其 中包括 MTC设备的外部标识、 MTC服务器 ID、 MTC Server的 IP地址及 端口和其他信息。
步驟 404, MTC-IWF认证该 MTC服务器， 查看该 MTC服务器是否是 授权的服务器， 是否允许发送触发请求。
步驟 405 , MTC-IWF向 HSS/HLR发起询问，让 HSS/HLR认证该 MTC 服务器， 看该 MTC服务器是否授权触发该 MTC设备， 消息中包括 MTC 设备的外部标识、 MTC服务器 ID。
步驟 406, HSS/HLR通过所述 MTC设备的外部标识查询到 MTC设备 的 IMSI,然后查询所述 MTC服务器是否授权向所述 MTC设备发送触发信 步驟 407, HSS/HLR向 MTC-IWF返回认证结果， 告知所述 MTC服务 器是否被授权触发所述 MTC 设备， 并将所述 MTC 设备的 IMSI 告知 MTC-IWF。 HSS/HLR 要将 SGSN/MME 的地址告知 MTC-IWF , 所述 SGSN/MME地址是 MTC设备通过上一次 TAU/RAU过程在 HSS中注册的 SGSN/MME地址。 HSS/HLR还要告知 MTC-IWF , 所述 MTC设备是否具 有接收短消息的能力。
步驟 408, 如果所述 MTC服务器是授权可以触发所述 MTC设备的， MTC-IWF将触发信息转发给步驟 107中 HSS/HLR告知的 SGSN/MME,其 中附带所述 MTC设备的 IMSI, 并且 MTC-IWF要告知 SGSN/MME, 所述 MTC设备是否具有接收短消息的能力。
步驟 409, 如果 SGSN/MME判断 MTC设备处于未附着状态， 并且如 果 SGSN/MME 处没有所述 MTC 设备的有效时间控制信息， 则询问 HSS/HLR , 消息中附带所述 MTC设备的 IMSI。
步驟 410 , HSS/HLR给所述 SGSN/MME返回所述 MTC设备的时间控 制信息 , 包括 grant time interval , forbidden time interval, access duration 0 步驟 411 , 如果所述 SGSN/MME中没有所述 MTC设备的通信窗口， 那么该 SGSN/MME根据本地网络策略和 HSS/HLR发送过来的时间控制信 息， 随机化一个通信窗口为所述 MTC 设备的有效通信窗口； 如果所述 SGSN/MME中有所述 MTC设备的通信窗口， 那么该通信窗口为所述 MTC 设备的有效通信窗口。
步驟 412,如果所述 MTC设备在其有效通信窗口内，所述 SGSN/MME 将所述 MTC设备的等待标识置位， 并存储触发信息， 开启定时器。 所述定 时器的长度为当前时间到通信窗口结束时间的长度。
步驟 413 , 如果所述定时器定时周期已到， MTC设备还未附着到网络， SGSN/MME向 MTC-IWF发送触发信息传输 4艮告， 告知 MTC-IWF此次触 发 MTC设备失败， 指示失败原因是 MTC设备未在通信窗口时间内附着到 网络。 触发失败报告中附带所述 MTC设备的 IMSI和通信窗口。
步驟 414,如果所述 MTC设备具有接收短消息的能力，所述 MTC-IWF 将触发信息发送至 SMS-SC保存，以便 MTC设备附着时能够通过短消息触 发该 MTC设备。
步驟 415, MTC-IWF向所述 MTC服务器转发触发信息传输报告， 指 示失败原因是 MTC设备未在通信窗口时间内附着到网络。触发失败报告中 附带所述 MTC设备的外部标志和通信窗口， 指示 MTC服务器在下一个通 信窗口时间到来时再次发起触发过程。 实施例 4
本实施例描述 MTC设备处于未附着状态下， 同时 MTC设备又不在其 通信窗口内的触发流程， 如图 5所示， 该流程具体包括：
步驟 501 , MTC服务器想要触发某 MTC设备， 如果 MTC服务器不知 道怎样连接上 MTC-IWF, 那么 MTC服务器使用该 MTC设备的外部标识 向 DNS发起询问 , 询问 MTC-IWF的 IP地址和端口。
步驟 502, DNS将 MTC-IWF的 IP地址和端口告知 MTC服务器。 步驟 503 , MTC服务器向 MTC-IWF发起 MTC设备触发传输请求。 其 中包括 MTC设备的外部标识、 MTC服务器 ID、 MTC Server的 IP地址及 端口和其他信息。
步驟 504, MTC-IWF认证该 MTC服务器， 查看该 MTC服务器是否是 授权的服务器， 是否允许发送触发请求。
步驟 505 , MTC-IWF向 HSS/HLR发起询问，让 HSS/HLR认证该 MTC 服务器， 看该 MTC服务器是否授权触发该 MTC设备， 消息中包括 MTC 设备的外部标识、 MTC服务器 ID。
步驟 506, HSS/HLR通过所述 MTC设备的外部标识查询到 MTC设备 的 IMSI,然后查询所述 MTC服务器是否授权向所述 MTC设备发送触发信 步驟 507, HSS/HLR向 MTC-IWF返回认证结果， 告知所述 MTC服务 器是否被授权触发所述 MTC 设备， 并将所述 MTC 设备的 IMSI 告知 MTC-IWF。 HSS/HLR 要将 SGSN/MME 的地址告知 MTC-IWF , 所述 SGSN/MME地址是 MTC设备通过上一次 TAU/RAU过程在 HSS中注册的 SGSN/MME地址。 HSS/HLR还要告知 MTC-IWF , 所述 MTC设备是否具 有接收短消息的能力。
步驟 508, 如果所述 MTC服务器是授权可以触发所述 MTC设备的， MTC-IWF将触发信息转发给步驟 107中 HSS/HLR告知的 SGSN/MME,其 中附带所述 MTC设备的 IMSI, 并且 MTC-IWF要告知 SGSN/MME, 所述 MTC设备是否具有接收短消息的能力。
步驟 509, 如果 SGSN/MME判断 MTC设备处于未附着状态， 并且如 果 SGSN/MME 处没有所述 MTC 设备的有效时间控制信息， 则询问 HSS/HLR , 消息中附带所述 MTC设备的 IMSI。
步驟 510, HSS/HLR给所述 SGSN/MME返回所述 MTC设备的时间控 制信息, 包括 grant time interval、 forbidden time interval, access duration。
步驟 511 , 如果所述 SGSN/MME中没有所述 MTC设备的通信窗口， 那么该 SGSN/MME根据本地网络策略和 HSS/HLR发送过来的时间控制信 息， 随机化一个通信窗口为所述 MTC 设备的有效通信窗口； 如果所述 SGSN/MME中有所述 MTC设备的通信窗口， 那么该通信窗口为所述 MTC 设备的有效通信窗口。
步驟 512, 如果所述 MTC设备不在其有效通信窗口内， SGSN/MME 向 MTC-IWF发送触发信息传输艮告， 告知 MTC-IWF此次触发 MTC设备 失败， 指示失败原因是 MTC设备为未附着状态并且未在其通信窗口内。 触 发失败报告中附带所述 MTC设备的 IMSI和通信窗口。
步驟 513 ,如果所述 MTC设备具有接收短消息的能力，所述 MTC-IWF 将触发信息发送至 SMS-SC保存，以便 MTC设备附着时能够通过短消息触 发该 MTC设备。
步驟 514, MTC-IWF向所述 MTC服务器转发触发信息传输报告， 指 示失败原因是 MTC设备为未附着状态并且未在其通信窗口内。触发失败报 告中附带所述 MTC设备的外部标志和通信窗口， 指示 MTC服务器在下一 个通信窗口时间到来时再次发起触发过程。
以上所述， 仅为本发明的较佳实施例而已， 并非用于限定本发明的保 护范围。

Claims

权利要求书
1、 一种触发机器类通信 MTC设备的方法， 其中， 该方法包括： 通用分组无线服务技术服务支持节点 SGSN/移动性管理实体 MME接 收来自机器类通信操作功能 MTC-IWF的触发信息，所述触发信息至少携带 需要触发的 MTC设备的国际移动用户识别码 IMSI、以及所述 MTC设备是 否具有接收短消息的能力；
SGSN/MME判定所述 MTC设备处于未附着状态、且所述 MTC设备处 于对应的通信窗口内， 则 SGSN/MME等待所述 MTC设备附着；
所述 MTC 设备在所述通信窗口结束时间之前附着到网络， 则 SGSN/MME将所述触发信息发送给所述 MTC设备；所述 MTC设备未在所 述通信窗口结束时间之前附着到网络， 则 SGSN/MME向 MTC-IWF发送触 发信息传输报告， MTC-IWF收到所述触发信息传输报告后， 将所述触发信 息发送至短消息服务中心 SMS-SC保存，并向相应的 MTC服务器转发所述 触发信息传输报告。
2、 根据权利要求 1所述的方法， 其中，
所述 SGSN/MME 将所述触发信息发送给所述 MTC 设备为： SGSN/MME通过网络接入服务 NAS信令方式将所述触发信息发送给所述 MTC设备，
该方法还包括： SGSN/MME通过 NAS信令方式向所述 MTC设备发送 所述触发信息失败、 且所述 MTC 设备具有接收短消息的能力， 则 SGSN/MME将所述触发信息发送至 SMS-SC, 通过短消息的方式触发所述 MTC设备。
3、根据权利要求 1所述的方法，其中，所述 SGSN/MME判定所述 MTC 设备处于未附着状态之后， 该方法还包括：
SGSN/MME判断本地是否存储有所述 MTC设备的通信窗口， 本地存 储有所述 MTC设备的通信窗口， 再判断所述 MTC设备是否处于所述通信 窗口内；
SGSN/MME本地未存储所述 MTC设备的通信窗口， 则进一步判断本 地是否存储有所述 MTC设备的时间控制信息， 本地未存储所述 MTC设备 的通信窗口但存储有所述 MTC设备的时间控制信息，则根据所述时间控制 信息和本地网络策略生成通信窗口，再判断所述 MTC设备是否处于所述通 信窗口内； 本地未存储所述 MTC设备的通信窗口且未存储所述 MTC设备 的时间控制信息，则从归属用户服务器 HSS/归属位置寄存器 HLR获取所述 MTC设备的时间控制信息， 根据所述时间控制信息和本地网络策略生成通 信窗口， 再判断所述 MTC设备是否处于所述通信窗口内。
4、 根据权利要求 1所述的方法， 其中， 该方法还包括：
SGSN/MME判定所述 MTC设备处于未附着状态、且所述 MTC设备处 于对应的通信窗口外，则 SGSN/MME向 MTC-IWF发送触发信息传输报告， MTC-IWF收到所述触发信息传输报告后， 将所述触发信息发送至 SMS-SC 保存， 并向相应的 MTC服务器转发所述触发信息传输报告。
5、 根据权利要求 1 所述的方法， 其中， 所述 SGSN/MME接收来自 MTC-IWF的触发信息之前， 该方法还包括：
MTC服务器向 MTC-IWF发送触发传输请求， 所述触发传输请求携带 需要触发的 MTC设备的外部标识、 触发参考码、 触发信息以及所述 MTC 服务器信息；
MTC-IWF根据所述触发传输请求判定所述 MTC服务器是合法的 MTC 服务器后，请求 HSS/HLR验证所述 MTC服务器是否被授权触发所述 MTC 设备；
HSS/HLR向 MTC-IWF返回应答消息， 所述应答消息携带所述 MTC 服务器是否被授权触发所述 MTC设备的信息、 所述 MTC设备的 IMSI、 SGSN/MME地址以及所述 MTC设备是否具有接收短信息的能力；
MTC-IWF根据所述应答消息判定所述 MTC服务器被授权触发所述 MTC设备， 则向相应的 SGSN/MME转发触发信息。
6、 根据权利要求 1至 5任一项所述的方法， 其中， 所述触发信息传输 报告携带所述 MTC设备触发失败的原因， 以及所述 MTC设备的 IMSI和 通信窗口，
所述 MTC-IWF向相应的 MTC服务器转发所述触发信息传输报告后， 所述 MTC服务器在下一个通信窗口时间到来时再次发起触发过程。
7、 一种触发 MTC设备的系统， 其中， 该系统包括： SGSN/MME、 MTC-IWF, MTC设备、 SMS-SC和 MTC服务器； 其中，
所述 SGSN/MME, 设置为接收来自 MTC-IWF的触发信息， 所述触发 信息至少携带需要触发的 MTC设备的 IMSI、 以及所述 MTC设备是否具有 接收短消息的能力； 以及在判定所述 MTC设备处于未附着状态、 且所述 MTC设备处于对应的通信窗口内时， 等待所述 MTC设备附着， 如果所述 MTC设备在所述通信窗口结束时间之前附着到网络， 则将所述触发信息发 送给所述 MTC设备； 所述 MTC设备未在所述通信窗口结束时间之前附着 到网络， 则向 MTC-IWF发送触发信息传输报告，
所述 MTC-IWF, 设置为向 SGSN/MME发送触发信息， 以及在收到触 发信息传输报告后， 将触发信息发送至 SMS-SC保存， 并向相应的 MTC服 务器转发所述触发信息传输报告；
所述 MTC设备， 设置为接收 SGSN/MME发送的触发信息；
所述 SMS-SC, 设置为存储来自 MTC-IWF的触发信息；
所述 MTC服务器， 设置为接收来自 MTC-IWF的触发信息传输报告。
8、 根据权利要求 7所述的系统， 其中，
所述 SGSN/MME, 具体设置为通过 NAS信令方式将所述触发信息发 送给所述 MTC设备；以及还设置为在通过 NAS信令方式向 MTC设备发送 所述触发信息失败、 且所述 MTC设备具有接收短消息的能力时， 将所述触 发信息发送至 SMS-SC。
9、 根据权利要求 7所述的系统， 其中，
所述 SGSN/MME, 还设置为在判定所述 MTC设备处于未附着状态之 后， 进一步判断本地是否存储有所述 MTC设备的通信窗口， 本地存储有所 述 MTC设备的通信窗口，再判断所述 MTC设备是否处于所述通信窗口内； SGSN/MME本地未存储所述 MTC设备的通信窗口， 则进一步判断本地是 否存储有所述 MTC设备的时间控制信息， 本地未存储所述 MTC设备的通 信窗口但存储有所述 MTC设备的时间控制信息，则根据所述时间控制信息 和本地网络策略生成通信窗口，再判断所述 MTC设备是否处于所述通信窗 口内； 本地未存储所述 MTC设备的通信窗口且未存储所述 MTC设备的时 间控制信息，则从归属用户服务器 HSS/归属位置寄存器 HLR获取所述 MTC 设备的时间控制信息， 根据所述时间控制信息和本地网络策略生成通信窗 口， 再判断所述 MTC设备是否处于所述通信窗口内。
10、 根据权利要求 7所述的系统， 其中，
所述 SGSN/MME, 还设置为在判定所述 MTC设备处于未附着状态、 且所述 MTC设备处于对应的通信窗口外时， 向 MTC-IWF发送触发信息传 输报告；
所述 MTC-IWF, 还设置为在收到所述触发信息传输报告后， 将所述触 发信息发送至 SMS-SC保存，并向相应的 MTC服务器转发所述触发信息传 输报告。
11、 根据权利要求 7所述的系统， 其中， 该系统还包括 HSS/HLR, 所述 MTC服务器， 还设置为向 MTC-IWF发送触发传输请求， 所述触 发传输请求携带需要触发的 MTC设备的外部标识、 触发参考码、 触发信息 以及所述 MTC服务器信息；
所述 MTC-IWF, 还设置为根据所述触发传输请求判定所述 MTC服务 器是合法的 MTC服务器后， 请求 HSS/HLR验证所述 MTC服务器是否被 授权触发所述 MTC设备； 以及根据来自 HSS/HLR 的应答消息判定所述 MTC服务器被授权触发所述 MTC设备后，向相应的 SGSN/MME转发触发 信息；
所述 HSS/HLR, 设置为向 MTC-IWF返回应答消息， 所述应答消息携 带所述 MTC服务器是否被授权触发所述 MTC设备的信息、 所述 MTC设 备的 IMSI、 SGSN/MME地址以及所述 MTC设备是否具有接收短信息的能 力。
12、 根据权利要求 7至 11任一项所述的系统， 其中，
所述 MTC服务器， 还设置为在收到来自 MTC-IWF的所述触发信息传 输 ·^艮告后， 在下一个通信窗口时间到来时再次发起触发过程。
PCT/CN2012/075147 2012-03-02 2012-05-07 一种触发mtc设备的方法和系统 WO2013127122A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US14/380,137 US9380405B2 (en) 2012-03-02 2012-05-07 Method and system for triggering MTC device
EP12870261.0A EP2822305B1 (en) 2012-03-02 2012-05-07 Method and system for triggering mtc device

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201210053773.7A CN103298110B (zh) 2012-03-02 2012-03-02 一种触发mtc设备的方法和系统
CN201210053773.7 2012-03-02

Publications (1)

Publication Number Publication Date
WO2013127122A1 true WO2013127122A1 (zh) 2013-09-06

Family

ID=49081568

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2012/075147 WO2013127122A1 (zh) 2012-03-02 2012-05-07 一种触发mtc设备的方法和系统

Country Status (4)

Country Link
US (1) US9380405B2 (zh)
EP (1) EP2822305B1 (zh)
CN (1) CN103298110B (zh)
WO (1) WO2013127122A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
FR3025686A1 (fr) * 2014-09-10 2016-03-11 Thales Sa Procede de traitement dans un systeme de telecommunication, terminal radio et programme d'ordinateur associes

Families Citing this family (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9713071B2 (en) * 2012-09-28 2017-07-18 Nokia Solutions And Networks Oy Provisioning external identifiers
KR102082442B1 (ko) 2013-01-04 2020-02-27 아이오티 홀딩스, 인크. 서비스 계층 분리 커맨드 및 부착 통지를 처리하는 방법 및 장치
EP3104648B1 (en) * 2014-02-04 2021-02-24 NTT DoCoMo, Inc. Service control system, user device and service control method
US9693178B2 (en) * 2015-03-18 2017-06-27 Intel IP Corporation Procedures to provision and attach a cellular internet of things device to a cloud service provider
US10405158B2 (en) 2017-02-27 2019-09-03 Oracle International Corporation Methods, systems and computer readable media for providing service capability exposure function (SCEF) as a diameter routing agent (DRA) feature
US10530599B2 (en) 2017-02-27 2020-01-07 Oracle International Corporation Methods, systems and computer readable media for providing service capability exposure function (SCEF) as a cloud service
US10506403B2 (en) 2017-02-27 2019-12-10 Oracle International Corporation Methods, systems and computer readable media for providing integrated service capability exposure function (SCEF), service capability server (SCS) and application server (AS) services
US10448449B2 (en) 2017-07-13 2019-10-15 Oracle International Corporation Methods, systems, and computer readable media for dynamically provisioning session timeout information in a communications network
US10334419B2 (en) 2017-08-16 2019-06-25 Oracle International Corporation Methods, systems, and computer readable media for optimizing machine type communication (MTC) device signaling
US10313883B2 (en) * 2017-11-06 2019-06-04 Oracle International Corporation Methods, systems, and computer readable media for using authentication validation time periods
US11146577B2 (en) 2018-05-25 2021-10-12 Oracle International Corporation Methods, systems, and computer readable media for detecting and mitigating effects of abnormal behavior of a machine type communication (MTC) device
US10616802B2 (en) 2018-09-04 2020-04-07 Oracle International Corporation Methods, systems and computer readable media for overload and flow control at a service capability exposure function (SCEF)
US11381955B2 (en) 2020-07-17 2022-07-05 Oracle International Corporation Methods, systems, and computer readable media for monitoring machine type communications (MTC) device related information
US11700510B2 (en) 2021-02-12 2023-07-11 Oracle International Corporation Methods, systems, and computer readable media for short message delivery status report validation

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2002076065A2 (en) * 2001-03-15 2002-09-26 Intel Corporation Generic external proxy
CN102088668A (zh) * 2011-03-10 2011-06-08 西安电子科技大学 基于群组的机器类型通信设备的认证方法
CN102118700A (zh) * 2009-12-31 2011-07-06 中兴通讯股份有限公司 机器类通信消息传输方法及系统
CN102149105A (zh) * 2010-02-10 2011-08-10 电信科学技术研究院 离线通知的方法、系统和设备

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
BR112014010786B1 (pt) * 2011-11-04 2022-07-12 Apple Inc Configurações e técnicas de pequenos dados em uma rede de comunicação sem fios

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2002076065A2 (en) * 2001-03-15 2002-09-26 Intel Corporation Generic external proxy
CN102118700A (zh) * 2009-12-31 2011-07-06 中兴通讯股份有限公司 机器类通信消息传输方法及系统
CN102149105A (zh) * 2010-02-10 2011-08-10 电信科学技术研究院 离线通知的方法、系统和设备
CN102088668A (zh) * 2011-03-10 2011-06-08 西安电子科技大学 基于群组的机器类型通信设备的认证方法

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP2822305A4 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
FR3025686A1 (fr) * 2014-09-10 2016-03-11 Thales Sa Procede de traitement dans un systeme de telecommunication, terminal radio et programme d'ordinateur associes

Also Published As

Publication number Publication date
EP2822305A4 (en) 2015-02-18
US20150036591A1 (en) 2015-02-05
CN103298110B (zh) 2018-08-28
EP2822305B1 (en) 2019-07-10
US9380405B2 (en) 2016-06-28
EP2822305A1 (en) 2015-01-07
CN103298110A (zh) 2013-09-11

Similar Documents

Publication Publication Date Title
WO2013127122A1 (zh) 一种触发mtc设备的方法和系统
US10404677B2 (en) Secure method for MTC device triggering
EP3836581B1 (en) Information processing method and system, and mobility management network element
WO2007137519A1 (en) A method and system for a ue in spare mode logging out a network
WO2015059925A1 (en) Control of small data transmission in a mobile radio communications network
WO2013113186A1 (zh) 一种mtc用户设备触发信息的发送方法、系统和用户设备
JP5994869B2 (ja) Ｍｔｃデバイス・トリガ配信の最適化
WO2013068867A1 (en) Message forwarding among disparate communication networks
JP6065124B2 (ja) Ｕｅのｍｔｃグループに対するブロードキャストにおけるグループ認証
EP2852083B1 (en) Method and core network device for transmitting device trigger message
US20140357262A1 (en) Method and apparatus for secure processing of short message
JP5773074B2 (ja) Ｍ２ｍにおけるプライバシー問題
WO2011044816A1 (zh) 用户设备的监控方法及监控装置
WO2013143218A1 (zh) 触发消息计数器的更新方法、机器类型通信服务器和终端
JP6732794B2 (ja) モバイル無線通信ネットワーク及び通信ネットワークデバイスへのモバイル端末の接続を確立するための方法
US20180343559A1 (en) Method and device for obtaining user equipment identifier, and method and device for sending user equipment identifier
WO2014166257A1 (zh) 触发消息处理方法、装置及通信系统
WO2013113185A1 (zh) 业务签约信息处理方法及装置
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: 12870261

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 14380137

Country of ref document: US

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 2012870261

Country of ref document: EP