WO2012151951A1

WO2012151951A1 - Method and system for triggering terminal

Info

Publication number: WO2012151951A1
Application number: PCT/CN2011/082893
Authority: WO
Inventors: 吴昊
Original assignee: 中兴通讯股份有限公司
Priority date: 2011-08-22
Filing date: 2011-11-24
Publication date: 2012-11-15
Also published as: CN102958036A; CN102958036B

Abstract

Disclosed is a method for triggering a terminal, comprising: a mobility management entity before change of a terminal determining whether a trigger message stored in itself is valid upon receiving a context request message sent by a mobility management entity after the change; if valid, sending the trigger message to the mobility management entity after the change through a context response message, and the mobility management entity after the change sending the trigger message to the terminal. Also disclosed is a system for triggering a terminal. According to the present invention, after movement of a terminal, a trigger message can still be sent to the terminal in time, thereby achieving real-time reporting of data.

Description

Method and system for terminal triggering

The present invention relates to the field of machine type communication (MTC) terminal management, and in particular, to a terminal triggering method and system. Background technique

The cellular wireless communication system is mainly composed of a Core Network (CN), a Radio Access Network (RAN), and a terminal. The core network is responsible for non-access layer transactions, such as terminal location update, and the core network is The anchor point of the user plane; the access network includes the base station or the base station and the base station control, and the access network is responsible for the access layer transaction, such as radio resource management, and the physical or logical connection may exist between the base stations according to actual conditions, as shown in FIG. The connection between the base station 1 and the base station 2 or the base station 3, and each base station can be connected to one or more core network nodes; the terminal, ie, User Equipment (UE), can communicate with the cellular wireless communication network. Various devices, such as mobile phones or laptops.

A mobility management unit, such as a Mobility Management Entity (MME) or a GPRS Service Support Node (SGSN), is a unit in the core network responsible for managing terminal access control, location information update, and handover, and is responsible for the core. Network-to-terminal non-access stratum signaling control and the ability to register terminals to the network.

The Home Subscriber Server (HSS) or the Home Location Register (HLR) is the entity responsible for storing the identity information, authentication information, and authorization information of the terminal device in the core network. According to different situations, the HSS or HLR. It can be used to save the identity information of the user and the binding information of the user and the terminal device, or only save the identity information of the user (the binding information of the user and the terminal device can be saved by the network management), or directly save the identity information of the terminal device. The HSS or HLR is also responsible for the user's subscription database and for performing user authentication. And authorization, etc. The service platform can query user or terminal information from the HSS or HLR.

The MTC Inter-working Function (MTC IWF) is a connection entity between the mobile communication network and the external public network, which can implement functions such as protocol conversion, address query, and information storage. The interoperation function entity is externally connected. The application server can be connected to the HSS/HLR, or MME/SGSN.

Generally, some services, such as the monitoring management system, need to obtain monitoring data from the monitoring terminal. The server needs to trigger the terminal to establish a connection with the server, and the required data is reported. After receiving the trigger message of the server, the terminal needs to be able to respond immediately. The connection to the server. At present, in order to meet the triggering requirement of the server to the terminal, the existing solution is to send a trigger message to the HSS or the HLR through the server, and then query the MME or SGSN of the service terminal through the HSS or HLR, and send a trigger message to the MME or the SGSN, and finally The non-access stratum (NAS) signaling is sent to the terminal, and the terminal establishes a connection with the server according to the trigger message.

However, the existing solution moves the mobility management unit MME or SGSN after the terminal moves in the idle state, and the trigger message is still stored in the mobility management unit before the change, so the network may not be able to The trigger message is sent to the terminal, and the terminal cannot establish a connection with the server in time to perform data reporting. Summary of the invention

In view of this, the main object of the present invention is to provide a terminal triggering method and system, which can send a trigger message to a terminal in time.

In order to achieve the above object, the technical solution of the present invention is achieved as follows:

A method for triggering a terminal, the method comprising:

After receiving the context request message sent by the changed mobility management unit, the mobility management unit before the terminal change determines whether the trigger message of the terminal stored by the terminal is valid.

When the trigger message is valid, the trigger message is sent to the changed mobility management unit by using a context response message, and the trigger message is sent by the changed mobility management unit. Send to the terminal.

Further, before the mobility management unit before the terminal change receives the context request message sent by the changed mobility management unit, the method further includes:

Sending, by the server, a trigger message of the terminal to the mobility management unit of the terminal;

After the terminal enters a new tracking area or routing area, the update request including the terminal identifier is sent to the changed mobility management unit;

The changed mobility management unit obtains the mobility management unit before the change based on the update request, and transmits a context request message to the mobility management unit before the change.

After the server sends a trigger message of the terminal to the mobility management unit of the terminal, the method further includes:

The mobility management unit receives and saves the trigger message, and sets and starts a timer according to an effective time of the trigger message.

The mobility management unit before the change determines whether the trigger message of the terminal stored by itself is valid:

The trigger message is valid when it is determined whether the timer expires or not.

The changed mobility management unit sends the trigger message to the terminal: the changed mobility management unit carries the trigger message in an update accept message and sends the trigger message to the terminal.

A system for triggering a terminal, comprising a terminal, the system further comprising: a mobility management unit, which is divided into a mobility management unit before the change and a mobility management unit after the change;

The mobility management unit before the change is configured to: after receiving the context request message sent by the changed mobility management unit, determine whether the trigger message stored by itself is valid; when the trigger message is valid, the context response message is The trigger message is sent to the changed mobility management unit;

The changed mobility management unit is configured to send a context request message and receive The triggered message is sent to the terminal.

Further, the system further includes: a server; wherein

The server is configured to send a trigger message of the terminal to the mobility management unit of the terminal, where the terminal is configured to send an update request including the terminal identifier to the changed after entering a new tracking area or routing area. Mobility management unit;

The changed mobility management unit is specifically configured to obtain the mobility management unit before the change according to the update request, and send a context request message to the mobility management unit before the change.

The mobility management unit before the change is specifically configured to receive and save the trigger message, and set and start a timer according to an effective time of the trigger message.

The mobility management unit before the change is specifically configured to: after receiving the context request message sent by the changed mobility management unit, determine whether the timer expires, and the trigger message is not received. effective.

The changed mobility management unit is specifically configured to carry the trigger message in an update accept message and send the message to the terminal.

In the present invention, when the mobility management unit is changed in the terminal, the mobility management unit before the change receives the context request message transmitted by the changed mobility management unit, and determines that the trigger message of the locally stored terminal is valid. Sending the trigger message to the changed mobility management unit, and sending the trigger message to the terminal by the changed mobility management unit to ensure that the trigger message can be sent to the terminal in time after the terminal moves. The terminal, thereby realizing real-time reporting of data. DRAWINGS

1 is a schematic structural diagram of an existing cellular wireless communication system;

2 is a schematic flowchart of an implementation process of a method for triggering a terminal according to the present invention;

3 is a schematic flowchart of an implementation manner of Embodiment 1 of a method for triggering a terminal according to the present invention;

4 is a schematic flowchart of an implementation manner of Embodiment 2 of a method for triggering a terminal according to the present invention; FIG. 5 is a schematic structural diagram of a system triggered by a terminal according to the present invention. detailed description

The basic idea of the present invention is: after receiving the context request message sent by the changed mobility management unit, the mobility management unit before the terminal change determines whether the trigger message of the terminal stored by the terminal is valid; the trigger message is valid. The trigger message is sent to the changed mobility management unit by the context response message, and the triggered mobility message is sent to the terminal by the changed mobility management unit.

The present invention will be further described in detail below with reference to the accompanying drawings.

FIG. 2 shows an implementation flow of a method for triggering a terminal of the present invention. As shown in FIG. 2, the method includes the following steps:

Step 201: After receiving the context request message sent by the changed mobility management unit, the mobility management unit before the terminal change determines whether the trigger message of the terminal stored by the terminal is valid. Here, the mobility management unit is MME or SGSN;

Before the step, the method further includes: when the MTC application server needs to obtain real-time data from the terminal, sending a trigger message of the terminal to the MTC IWF; and the MTC IWF sends the trigger message to the mobility management of the terminal by using the HSS or the HLR. The unit or the MTC IWF sends the trigger message directly to the mobility management unit of the terminal;

The mobility management unit receives and saves the trigger message, where the trigger message may include a terminal identifier, a valid time of the trigger message, an address of the server, an application identifier, and the like; the mobility management unit is configured according to the trigger message. Setting a validity time and starting a timer; after the terminal establishes a non-access stratum connection with the mobility management unit, the mobility management unit sends a trigger message to the terminal;

After the terminal moves to the new tracking area or the routing area, the update request including the terminal identifier is sent to the changed mobility management unit, where the update request may specifically be tracking Zone update request or routing area update request;

Specifically, in this step, when the mobility management unit before the change receives the context request message sent by the changed mobility management unit, it is determined whether the timer expires, and if not, the trigger message If yes, go to step 202, otherwise the current processing flow ends.

Step 202: When the trigger message is valid, send the trigger message to the changed mobility management unit by using a context response message, and send the trigger message to the terminal by the changed mobility management unit.

Here, the changed mobility management unit may send the trigger message to the terminal by carrying the trigger message in the update accept message.

FIG. 3 is a flowchart showing an implementation of the first embodiment of the method for triggering a terminal according to the present invention. Embodiment 1 is a description of a terminal in a third generation (3G) mobile communication system. As shown in FIG. 3, the terminal is triggered by the embodiment. The method includes the following steps:

Step 301: When the MTC application server needs to obtain real-time data from the terminal, send a trigger message to the MTC IWF.

The trigger message includes a terminal identifier, a valid time of the trigger message, an address of the server, and an application identifier. Here, the terminal identifier is an external identifier used by the terminal outside the network.

Step 302: The MTC IWF parses the received trigger message to find the HSS where the terminal is located. After finding the HSS where the terminal is located, a new trigger message is constructed, and the newly generated trigger message is sent to the terminal by triggering the request signaling. HSS;

Specifically, the MTC IWF local database stores a one-to-one mapping table between the external identifier and the internal identifier, and a multi-to-one correspondence table between the internal identifier and the HSS;

The MTC IWF reads the terminal identifier in the trigger message, and searches for the terminal identifier corresponding to the trigger message in the network according to the external identifier and the internal identifier mapping table saved in the local database. The internal identifier is identified, and the HSS where the terminal is located is found in the correspondence table between the internal identifier and the HSS according to the internal identifier; and the terminal external identifier of the original trigger message is replaced by the internal identifier of the terminal, and a new trigger message is constructed.

Step 303: After the terminal registers with the network, the HSS saves the current serving MME of the terminal. After receiving the trigger message, the HSS searches for the service MME of the terminal locally according to the terminal identifier in the trigger message, and inserts the subscription data signaling. The trigger message is sent to the MME. Here, for convenience of presentation, the current serving MME of the terminal may be recorded as the MME before the change. Step 304: After receiving the insertion subscription data signaling sent by the HSS, the MME reads the trigger message included therein, and sets a timer T1 locally, and locally sets the timer T1 according to the valid time of the trigger message in the trigger message. Value, and start the timer, while saving the trigger message of the terminal.

Step 305: If the terminal has established a NAS connection with the MME, the MME before the change sends a downlink universal transmission NAS message to the terminal, where the message includes a trigger message of the terminal.

In addition, the step further includes: if the terminal is in an idle state, the MME does not immediately send a trigger message until the terminal establishes a NAS connection with the MME, and then sends the message.

Step 306: When the terminal in the idle state moves to the new tracking area, the tracking area update request needs to be sent to the changed MME, where the tracking area update request includes the identifier of the terminal; Step 307, the changed MME receives the After the tracking area update request of the terminal, the identifier of the MME before the change is extracted according to the identifier of the terminal, and then the context request message is sent to the MME before the change, and the MME before the change is requested to forward the context information of the terminal to the MME. The changed MME;

Step 308: After receiving the context request message of the changed MME, the MME before the change sends a context response message to the changed MME, and the context response message includes the terminal locally saved by the MME before the change. Contextual information, at the same time, the judgment step Whether the trigger message saved in 304 is valid, and if valid, the MME before the change includes the trigger message of the terminal in the context response message;

Specifically, determining whether the trigger message is valid is whether the timer T1 set in the determining step 304 is up, and if not, the trigger message is still valid.

Step 309: After the changed MME receives the context response message sent by the MME before the change, the MME sends the trigger message to the terminal in the tracking area update accept message.

Step 310: After receiving the tracking area update accept message, the terminal reads the trigger message, and determines the access point that needs to establish a connection according to the application identifier given in the trigger message, and the local application identifier and the access point name comparison table. Name, which is included in the packet data network connection request message and sent to the changed MME;

Step 311: After receiving the packet data network connection request message of the terminal, the changed MME establishes a bearer according to the access point name provided by the terminal in the packet data network connection request message. In addition, the step further includes: after the changing The MME deletes the trigger message of the terminal saved locally.

Step 312: After the bearer is established, the terminal communicates with the server, and the terminal can report the data to the server in real time.

FIG. 4 is a flowchart showing the implementation of the method for triggering the terminal of the present invention. As shown in FIG. 4, the method for triggering the terminal in the second embodiment includes the following steps:

Step 401: When the MTC application server needs to obtain real-time data from the terminal, send a trigger message to the MTC IWF.

Step 402: The MTC IWF parses the received trigger message to find the HLR where the terminal is located. After finding the HLR where the terminal is located, constructs a new trigger message, and sends a newly generated trigger message to the terminal by triggering the request signaling. HLR; Specifically, the MTC IWF local database stores a one-to-one mapping table between the external identifier and the internal identifier, and a multi-to-one correspondence table between the internal identifier and the HLR;

The MTC IWF reads the terminal identifier in the trigger message, and searches for the internal identifier used in the network corresponding to the terminal identifier in the trigger message according to the external identifier and the internal identifier mapping table saved in the local database, and internally identifies the internal identifier according to the internal identifier. The HLR corresponding table is used to find the HLR where the terminal is located. The terminal internal identifier is used to replace the external identifier of the original trigger message, and a new trigger message is generated.

Step 403: After the terminal registers with the network, the HLR saves the current serving SGSN of the terminal. After receiving the trigger message, the HLR searches for the service SGSN of the terminal according to the terminal identifier in the trigger message, and inserts the subscription data signaling. The trigger message is sent to the SGSN. Here, for convenience of description, the current service SGSN of the terminal may be recorded as the SGSN before the change. Step 404: After receiving the insertion subscription data signaling sent by the HLR, the SGSN before the change reads the trigger message included therein, sets the timer T2 locally, and sets the timing locally according to the valid time of the trigger message in the trigger message. The value of T2, and start the timer, while saving the trigger message of the terminal.

Step 405: If the terminal has established a NAS connection with the SGSN, the SGSN sends a downlink general transmission NAS message to the terminal, where the message includes a trigger message of the terminal.

In addition, the step further includes: if the terminal is in an idle state, the SGSN does not immediately send a trigger message until the terminal establishes a NAS connection with the SGSN and then sends the message.

Step 406: When the terminal in the idle state moves to the new routing area, the routing area update request needs to be sent to the changed SGSN, where the routing area update request includes the identifier of the terminal. Step 407, the changed SGSN receives the terminal. After the routing area update request, the identifier of the SGSN before the change is extracted according to the identifier of the terminal, and then the context request message is sent to the SGSN before the change, and the SGSN before the change is requested to forward the context information of the terminal to the change. After the SGSN; Step 408: After receiving the context request message of the changed SGSN, the SGSN before the change sends a context response message to the changed SGSN, where the context response message includes the terminal locally saved by the SGSN before the change. Context information; at the same time, determining whether the trigger message saved in step 404 is valid, if valid, the SGSN before the change includes the trigger message of the terminal in the context response message;

Specifically, it is determined whether the trigger message is valid to determine whether the timer T2 set in step 404 is up, and if not, the trigger message is still valid.

Step 409: After receiving the context response message sent by the SGSN before the change, the SGSN sends the trigger message to the terminal in the routing area update accept message.

Step 410: After receiving the routing area update accept message, the terminal reads the trigger message, and determines the access point that needs to establish a connection according to the application identifier given in the trigger message, and the local application identifier and the access point name comparison table. The name is included in the Packet Data Protocol Context Setup Request message and sent to the changed SGSN.

Step 411: After receiving the packet data protocol context establishment request message of the terminal, the changed SGSN establishes a bearer name according to the access point name provided by the terminal in the packet data protocol context establishment request message.

Specifically, the step further includes: deleting, by the changed SGSN, the locally saved trigger message of the terminal.

Step 412: After the bearer is established, the terminal communicates with the server, and the terminal can report the data to the server in real time.

FIG. 5 shows the structure of the system triggered by the terminal of the present invention. As shown in FIG. 5, the system includes: a mobility management unit and a terminal 53. Further, the mobility management unit is divided into a mobility management unit 51 before the change. And the changed mobility management unit 52; wherein

The mobility management unit 51 before the change is used to receive the context request message sent by the changed mobility management unit 52, and determine whether the trigger message stored by itself is valid; When the message is valid, the trigger message is sent to the changed mobility management unit 52 by using a context response message;

The changed mobility management unit 52 is configured to send a context request message, and send the received trigger message to the terminal 53.

Further, the system further includes: a server 54 for transmitting a trigger message of the terminal 53 to the mobility management unit of the terminal 53;

Correspondingly, the terminal 53 is configured to: after entering a new tracking area or routing area, send an update request including the terminal identifier to the changed mobility management unit 52;

The changed mobility management unit 52 is specifically configured to obtain the mobility management unit 51 before the change according to the update request, and send a context request message to the mobility management unit 51 before the change.

The mobility management unit 51 before the change is specifically configured to receive and save the trigger message, and set and start a timer according to the valid time of the trigger message.

Further, the mobility management unit 51 before the change is specifically configured to determine, after the change of the context request message sent by the mobility management unit 52, whether the timer expires or not. The trigger message is valid.

The mobility management unit 51 before the change is specifically configured to: after receiving the trigger message of the terminal 53 sent by the server 54, when the terminal 53 and the mobility management unit have established a NAS connection, The trigger message is sent to the terminal 53.

The changed mobility management unit 52 is specifically configured to carry the trigger message to the terminal 53 in an update accept message.

The above is only the preferred embodiment of the present invention and is not intended to limit the scope of the present invention.

Claims

Claim

A method for triggering a terminal, the method comprising:

When the trigger message is valid, the trigger message is sent to the changed mobility management unit by using a context response message, and the triggered mobility management unit sends the trigger message to the terminal.

The method according to claim 1, wherein before the mobility management unit before the terminal change receives the context request message sent by the changed mobility management unit, the method further includes:

The method according to claim 2, wherein, after the server sends a trigger message of the terminal to the mobility management unit of the terminal, the method further includes:

The method according to claim 3, wherein the mobility management unit before the change determines whether the trigger message of the terminal stored by itself is valid:

The method according to any one of claims 1 to 4, wherein the changed mobility management unit sends the trigger message to the terminal:

The changed mobility management unit carries the trigger message in an update accept message To the terminal.

A system for triggering a terminal, comprising a terminal, wherein the system further comprises: a mobility management unit, which is divided into a mobility management unit before the change and a mobility management unit after the change;

The changed mobility management unit is configured to send a context request message, and send the received trigger message to the terminal.

The system according to claim 6, wherein the system further comprises: a server; wherein

The system according to claim 7, wherein the mobility management unit before the change is specifically configured to receive and save the trigger message, and set and start a timer according to a valid time of the trigger message.

The system according to claim 8, wherein the mobility management unit before the change is specifically configured to determine the timing after receiving the context request message sent by the changed mobility management unit. If the timer expires, the trigger message is valid.

The system according to any one of claims 6 to 9, wherein the changed mobility management unit is specifically configured to carry the trigger message in an update accept message. Send to the terminal.