WO2013091303A1 - Procédé et système de traitement d'un message de déclenchement de terminal et élément de réseau associé - Google Patents

Procédé et système de traitement d'un message de déclenchement de terminal et élément de réseau associé Download PDF

Info

Publication number
WO2013091303A1
WO2013091303A1 PCT/CN2012/071721 CN2012071721W WO2013091303A1 WO 2013091303 A1 WO2013091303 A1 WO 2013091303A1 CN 2012071721 W CN2012071721 W CN 2012071721W WO 2013091303 A1 WO2013091303 A1 WO 2013091303A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal
trigger message
mme
sgsn
trigger
Prior art date
Application number
PCT/CN2012/071721
Other languages
English (en)
Chinese (zh)
Inventor
杨坤
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2013091303A1 publication Critical patent/WO2013091303A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks

Definitions

  • Terminal trigger message processing method system and related network element
  • the present invention relates to the field of machine type communication (MTC), and in particular, to a terminal trigger message processing method, system and related network element.
  • MTC machine type communication
  • FIG. 1 is a schematic structural diagram of a cellular wireless communication system.
  • a cellular wireless communication system is mainly composed of a core network (CN, Core Network), an access network (RAN, Radio Access Network), and a terminal, wherein the core network Responsible for non-access layer transactions, such as terminal location updates, etc., and is the anchor point of the user plane.
  • the access network includes a base station, or a base station and a base station control, and the access network is responsible for access layer transactions (for example, management of radio resources).
  • the base stations may have physical or logical connections according to actual conditions, and the base station may be connected with one or more other ones.
  • the base stations are connected, and each base station can be connected to one or more core network nodes.
  • a user equipment UE, User Equipment
  • a user equipment refers to various devices that can communicate with a cellular wireless communication network, such as a mobile phone or a notebook computer.
  • the mobility management unit ( ⁇ (Mobility Management Entity) or SGSN (General Packet Radio Service Technical Service Support Node)) is the unit in the core network responsible for managing terminal access control, location information update, and handover.
  • the SG or SGSN is responsible for the core network-to-terminal non-access stratum signaling control and the function of registering the terminal to the network.
  • the home subscriber information unit (HSS (Home Subscriber Server) or HLR (Home Subscriber Location Register) is an entity in the core network responsible for storing identity information, authentication information, and authorization information of the terminal device. Depending on the situation, the HSS or HLR can be used to store the identity information of the user and the binding information of the user and the terminal device, or only the identity information of the user (the binding information of the user and the terminal device can be saved by the gateway), or the terminal device can be directly saved. Identity information. HSS or HLR It is also responsible for the user's subscription database, as well as the user's authentication and authorization. The service platform can query user or terminal information from the HSS or HLR.
  • HSS Home Subscriber Server
  • HLR Home Subscriber Location Register
  • MTC Interoperability Function Entity 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 interoperability function entity is connected to the application server, and the peer can be connected to the HSS/HLR, or the MME/SGSN.
  • the monitoring management system needs to obtain monitoring data from the monitoring terminal.
  • the server needs to trigger the terminal to establish a connection with the server, and report the required data.
  • the terminal needs to be able to respond immediately and establish a connection with the server.
  • the existing solution sends the trigger information to the HSS through the server, and then queries the MME or the SGSN of the serving terminal through the HSS, and sends a trigger message to the MME or the SGSN, and then passes the non-access stratum signaling.
  • the terminal establishes a connection with the server according to the trigger message. If both the MME and the SGSN are registered on the HSS, the HSS will simultaneously send a trigger message to the MME and the SGSN.
  • the MME and the SGSN respectively run a periodic update timer. If the MME or the SGSN does not receive the periodic update request of the terminal before the periodic update timer expires, the implicit detachment can be performed independently, and the implicit detachment of the MME or the SGSN can deactivate the ISR function.
  • ISR Idle state Signalling Reduction
  • the MME or the SGSN still retains the trigger message of the corresponding terminal, respectively, after the deactivation of the ISR function and the terminal triggers the message valid timer, which may cause waste of network storage resources.
  • a terminal trigger message processing method includes:
  • the mobility management entity MME or the general packet radio service technology service support node SGSN deactivates the idle state signaling to reduce the ISR function, and then removes the trigger message of the corresponding terminal.
  • the method further includes:
  • the server sends a trigger message of the terminal to the MME and the SGSN, and the MME and the SGSN respectively store the trigger message of the terminal.
  • the method further includes: sending, by the MME or the SGSN, a trigger response message to the home subscriber server HSS and/or the machine type communication interoperation function entity MTC IWF, notifying the HSS and/or The trigger message of the terminal described by the MTC IWF fails to be sent.
  • the method further includes: the HSS and/or the MTC IWF storing the trigger message of the terminal, and after receiving the trigger response message that the MME and the SGSN respectively send a notification failure, the stored trigger message of the terminal is removed. .
  • the method further includes: the HSS and/or the MTC IWF sending a trigger response message to the server, notifying the server that the trigger message of the terminal fails to be sent.
  • the method further includes: sending, by the MME or the SGSN, a trigger response message to the server, notifying that the trigger message of the terminal of the server fails to be sent.
  • a terminal trigger message processing system including an MME and an SGSN, where
  • the MME or the SGSN is configured to remove the trigger message of the corresponding terminal after the ISR function is deactivated.
  • the system also includes a server,
  • the server is configured to send a trigger message of the terminal to the MME and the SGSN;
  • the MME or the SGSN is further configured to store a trigger message of the terminal.
  • the system also includes HSS and / or MTC IWF,
  • the MME or the SGSN is further configured to send a trigger response message to the HSS and/or the MTC IWF after the trigger message of the corresponding terminal is removed, to notify the HSS and/or the MTC IWF that the trigger message of the terminal fails to be sent.
  • the HSS and/or the MTC IWF are further configured to: after the trigger message of the terminal is stored, and after receiving the trigger response message that the MME and the SGSN respectively send a notification failure, the stored trigger message of the terminal is removed.
  • the HSS and/or the MTC IWF are further configured to send a trigger response message to the server, and notify the server that the trigger message of the terminal fails to be sent.
  • the MME or the SGSN is further configured to send a trigger response message to the server, to notify the server that the trigger message of the terminal fails to be sent.
  • An MME the MME is configured to remove a trigger message of the corresponding terminal after the ISR function is deactivated.
  • An SGSN the SGSN is configured to remove a trigger message of the corresponding terminal after the ISR function is deactivated.
  • An HSS is configured to: after storing the trigger message of the terminal, and receiving the trigger response message that the MME and the SGSN respectively send a notification failure, the stored trigger message of the corresponding terminal is removed.
  • An MTC IWF is configured to remove the trigger message of the stored corresponding terminal after storing the trigger message of the terminal and receiving the trigger response message that the MME and the SGSN respectively send the notification failure.
  • the terminal trigger message processing method, system, and related network element are described in the embodiment of the present invention.
  • the trigger message of the corresponding terminal is removed. Since the MME or the SGSN can quickly remove the trigger message of the corresponding terminal after deactivating the ISR function, the waste of the network storage resource can be avoided.
  • FIG. 1 is a schematic structural diagram of a cellular wireless communication system
  • FIG. 2 is a schematic flowchart of a terminal trigger message processing method according to an embodiment of the present invention
  • FIG. 3 is a schematic flowchart of a terminal trigger message processing process according to Embodiment 1 of the present invention
  • FIG. 4 is a schematic flowchart of a terminal trigger message processing process according to Embodiment 2 of the present invention.
  • FIG. 5 is a schematic flowchart of a terminal trigger message processing process according to Embodiment 3 of the present invention.
  • FIG. 6 is a schematic flowchart of a terminal trigger message processing process according to Embodiment 4 of the present invention.
  • FIG. 7 is a schematic flowchart of a terminal trigger message processing process according to Embodiment 5 of the present invention. detailed description
  • the basic idea of the present invention is: After the MME or the SGSN deactivates the ISR function, the trigger message of the corresponding terminal is removed.
  • the present invention mainly relates to trigger message processing in an ISR scenario.
  • FIG. 2 is a schematic flowchart of a method for processing a terminal trigger message according to an embodiment of the present invention. As shown in FIG. 2, the method includes:
  • Step 201 The MME or the SGSN deactivates the ISR function.
  • Step 202 The MME or the SGSN removes a trigger message of the corresponding terminal.
  • the trigger message of the corresponding terminal is generally removed immediately.
  • the method further includes: the server sending the trigger message of the terminal to the MME and the SGSN, where the MME and the SGSN respectively store the trigger message of the terminal.
  • the invention may further comprise:
  • Step 203 The MME or the SGSN sends a trigger response message to the HSS and/or the MTC IWF, and notifies the HSS and/or the MTC IWF that the trigger message of the terminal fails to be sent.
  • the MME or the SGSN sends a trigger response message to the HSS and the MTC IWF.
  • the MME or the SGSN sends a trigger response message to the HSS, and the HSS triggers the response.
  • the message is sent to the MTC IWF.
  • Step 204 The HSS and/or the MTC IWF store the trigger message of the terminal, and after receiving the trigger response message that the MME and the SGSN respectively send a notification failure, the stored trigger message of the terminal is removed.
  • the invention may further comprise:
  • Step 205 The HSS and/or the MTC IWF send a trigger response message to the server, and notify the server that the trigger message of the terminal fails to be sent.
  • the MME or the SGSN may directly send a trigger response message to the server, and notify the server that the trigger message of the terminal fails to be sent.
  • the present invention also correspondingly discloses a terminal trigger message processing system, where the system includes an MME and an SGSN, where
  • the MME or the SGSN is configured to remove the trigger message of the corresponding terminal after the ISR function is deactivated.
  • the system also includes a server,
  • the server is configured to send a trigger message of the terminal to the MME and the SGSN;
  • the MME or the SGSN is further configured to store a trigger message of the terminal.
  • the system also includes HSS and / or MTC IWF,
  • the MME or the SGSN is further configured to send a trigger response message to the HSS and/or the MTC IWF after the trigger message of the corresponding terminal is removed, to notify the HSS and/or the MTC IWF that the trigger message of the terminal fails to be sent.
  • the HSS and/or the MTC IWF are further configured to: after the trigger message of the terminal is stored, and after receiving the trigger response message that the MME and the SGSN respectively send a notification failure, the stored trigger message of the terminal is removed.
  • the HSS and/or the MTC IWF are also configured to send a trigger response message to the server, It is known that the trigger message of the terminal of the server fails to be sent.
  • the MME or the SGSN is further configured to send a trigger response message to the server, to notify the server that the trigger message of the terminal fails to be sent.
  • the present invention also correspondingly discloses an MME, which is configured to remove a trigger message of a corresponding terminal after deactivating the ISR function.
  • the present invention also correspondingly discloses an SGSN that is configured to remove a trigger message of a corresponding terminal after deactivating the ISR function.
  • the invention also correspondingly discloses an HSS, which is configured to remove the trigger message of the stored corresponding terminal after the trigger message of the terminal is received and the trigger response message of the notification sent by the MME and the SGSN is received.
  • the present invention also correspondingly discloses an MTC IWF, which is configured to: after the trigger message of the terminal is stored, and after receiving the trigger response message that the MME and the SGSN respectively send a notification failure, the trigger of the stored corresponding terminal is removed. Message.
  • the trigger message of the terminal is stored on the MTC IWF and the HSS.
  • FIG. 3 is a schematic flowchart of a terminal trigger message processing process according to Embodiment 1 of the present invention. As shown in FIG. 3, the process includes:
  • Step 301 terminal is powered on, and attached to the network to activate ISR function, the terminal is currently serving the MME and the SGSN respectively have a terminal opening in the idle state terminal reachable timer (Mobile Reachable Timer) 0
  • the terminal reachable timer It can also be called a periodic update timer.
  • Step 302 When the MTC application server needs to acquire real-time data from the terminal, send a trigger message to the MTC IWF.
  • the trigger message includes the identifier of the terminal, the identifier of the application, the address of the server, the effective time of the trigger indication, and the like (where the identifier of the terminal is an external identifier used outside the network).
  • the MTC IWF stores and parses the trigger message, 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 mapping table of the external identifier and the internal identifier stored in the local database, and Find the HSS where the terminal is located according to the internal identifier stored in the database and the corresponding table of the HSS. After the HSS where the terminal is located is found, a new trigger message is constructed, and the terminal internal identifier is used to replace the external identifier of the terminal in the original trigger message, and is sent to the HSS by triggering the request signaling.
  • Step 304 After the terminal registers with the network and activates the ISR function, the HSS stores the current serving MME and the SGSN of the terminal. After receiving and storing the trigger message, the HSS searches for the serving MME and SGSN of the terminal in the locally stored information according to the terminal identifier in the trigger message, and passes S6a (reference point between MME and HSS) and S6d (SGSN and HSS) The signaling on the inter-reference point, such as Insert Subscriber Data signaling, sends a trigger message to the MME and the SGSN, respectively.
  • S6a reference point between MME and HSS
  • S6d SGSN and HSS
  • Step 305 After receiving the signaling sent by the HSS, the MME reads the trigger message included therein, sets the trigger timer T1 locally, and locally sets the value of the timer T1 according to the valid time value in the trigger message, and starts the The timer stores the trigger message of the terminal at the same time.
  • the SGSN reads the trigger message included therein, sets the trigger timer T2 locally, sets the value of the timer T2 locally according to the valid time value in the trigger message, and starts the The timer stores the trigger message of the terminal at the same time.
  • Step 306 The MME and the SGSN do not immediately send a trigger message because the terminal is in an idle state, and wait for the terminal to establish a NAS connection with the MME or the SGSN before transmitting.
  • the MME or the SGSN does not receive the periodic update request of the terminal, that is, the terminal reachability timer expires
  • the ISR function is deactivated after the MME or the SGSN independently performs implicit detachment, and the trigger message corresponds to The trigger timer T1 or T2 does not arrive, that is, the trigger message is still valid.
  • the MME or the SGSN removes the trigger message of the terminal, and sends a trigger request response message to the HSS through signaling on the S6a or S6d reference point, such as Stream Control Transmission Protocol (SCTP) signaling. Notifying the HSS that the trigger message of the terminal failed to be sent.
  • SCTP Stream Control Transmission Protocol
  • Step 307 If the MME and the SGSN do not receive the periodic update request of the terminal and perform the implicit detachment, the MME and the SGSN respectively send a trigger request response message to the HSS, and notify the HSS that the trigger message of the terminal fails to be sent. Then, after confirming that the trigger request response message sent by both the MME and the SGSN is received, the HSS removes the trigger message of the terminal. At the same time, the HSS sends a trigger response message to the MTC IWF, informing the MTC IWF that the trigger message of the terminal fails to be sent.
  • Step 308 After receiving the trigger response message sent by the HSS, the MTC IWF removes the trigger message of the terminal, and sends a trigger response message to the MTC application server to notify the MTC application server that the trigger message of the terminal fails to be sent.
  • the MTC IWF After receiving the trigger response message sent by the HSS, the MTC IWF removes the trigger message of the terminal, and sends a trigger response message to the MTC application server to notify the MTC application server that the trigger message of the terminal fails to be sent.
  • a trigger message of the terminal is stored on the HSS.
  • FIG. 4 is a schematic flowchart of a terminal trigger message processing process according to Embodiment 2 of the present invention. As shown in FIG. 4, the process includes:
  • Step 401 After the terminal is powered on, attached to the network, and activated by the ISR function, the MME and the SGSN currently served by the terminal have respectively opened the terminal reachable timer for the terminal in the idle state.
  • Step 402 When the MTC application server needs to acquire real-time data from the terminal, the trigger message is sent to the MTC IWF.
  • the trigger message includes the identifier of the terminal, the identifier of the application, the address of the server, the effective time of the trigger indication, and the like (where the identifier of the terminal is an external identifier used outside the network).
  • Step 403 The MTC IWF local database stores a one-to-one mapping table between the external identifier and the internal identifier, and a many-to-one correspondence table between the internal identifier and the HSS.
  • MTC IWF resolution touch Sending a message, reading the terminal identifier in the trigger message, searching for the internal identifier used in the network corresponding to the terminal identifier in the trigger message according to the mapping table of the external identifier and the internal identifier stored in the local database, and according to the internal identifier in the database
  • the HSS in which the terminal is located is found in the correspondence table between the internal identifier stored in the HSS and the HSS. After the HSS where the terminal is located is found, a new trigger message is constructed, and the terminal internal identifier is used to replace the external identifier of the terminal in the original trigger message, and is sent to the HSS by triggering the request signaling.
  • Step 404 After the terminal registers with the network and activates the ISR function, the HSS stores the current serving MME and the SGSN of the terminal. After receiving and storing the trigger message, the HSS searches for the serving MME and the SGSN of the terminal in the locally stored information according to the terminal identifier in the trigger message, and performs signaling on the reference points of S6a and S6d, such as inserting subscription data signaling, respectively. A trigger message is sent to the MME and the SGSN.
  • Step 405 After receiving the signaling sent by the HSS, the MME reads the trigger message included therein, sets the trigger timer T1 locally, and locally sets the value of the timer T1 according to the valid time value in the trigger message, and starts the The timer stores the trigger message of the terminal at the same time.
  • the SGSN After receiving the signaling sent by the HSS, the SGSN reads the trigger message included therein, sets the trigger timer T2 locally, sets the value of the timer T2 locally according to the valid time value in the trigger message, and starts the The timer stores the trigger message of the terminal at the same time.
  • Step 406 The MME and the SGSN do not immediately send a trigger message because the terminal is in an idle state, and wait for the terminal to establish a NAS connection with the MME or the SGSN before transmitting.
  • the MME or the SGSN does not receive the periodic update request of the terminal, that is, the terminal reachability timer expires
  • the ISR function is deactivated after the MME or the SGSN independently performs implicit detachment, and the trigger message corresponds to The trigger timer T1 or T2 does not arrive, that is, the trigger message is still valid.
  • the MME or the SGSN removes the trigger message of the terminal, and sends a trigger request response message to the HSS through the signaling on the S6a or S6d reference point, such as the flow control transmission protocol signaling, to notify the HSS of the trigger message sent by the terminal. failure.
  • Step 407 If the MME and the SGSN do not receive the periodic update request of the terminal, and perform the implicit detachment, the MME and the SGSN respectively send a trigger request response message to the HSS, and notify the HSS that the trigger message of the terminal fails to be sent. Then, after receiving the trigger request response message sent by both the MME and the SGSN, the HSS removes the trigger message of the terminal. At the same time, the HSS sends a trigger response message to the MTC application server, and notifies the MTC application server that the trigger message of the terminal fails to be sent.
  • the trigger message of the terminal is stored on the MTC IWF.
  • FIG. 5 is a schematic flowchart of a terminal trigger message processing process according to Embodiment 3 of the present invention. As shown in FIG. 5, the process includes:
  • Step 501 After the terminal is powered on, attached to the network, and activated by the ISR function, the MME and the SGSN currently served by the terminal have respectively opened the terminal reachable timer for the terminal in the idle state.
  • Step 502 When the MTC application server needs to obtain real-time data from the terminal, the trigger message is sent to the MTC IWF.
  • the trigger message includes the identifier of the terminal, the identifier of the application, the address of the server, the effective time of the trigger indication, and the like (where the identifier of the terminal is an external identifier used outside the network).
  • Step 503 The MTC IWF local database stores a one-to-one mapping table between the external identifier and the internal identifier, and a many-to-one correspondence table between the internal identifier and the HSS.
  • the MTC IWF stores and parses the trigger message, 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 mapping table of the external identifier and the internal identifier stored in the local database, and Find the HSS where the terminal is located according to the internal identifier stored in the database and the corresponding table of the HSS. After finding the HSS where the terminal is located, a new trigger message is constructed, and the terminal internal identifier is used to replace the external identifier of the terminal in the original trigger message, and is sent to the HSS by triggering the request signaling.
  • Step 504 After the terminal registers with the network and activates the ISR function, the HSS stores the current terminal. Service MME and SGSN. After receiving the trigger message, the HSS searches for the serving MME and the SGSN of the terminal in the locally stored information according to the terminal identifier in the trigger message, and uses signaling on the reference points of S6a and S6d, such as inserting subscription data signaling, respectively. A trigger message is sent to the MME and the SGSN.
  • Step 505 After receiving the signaling sent by the HSS, the MME reads the trigger message included therein, sets the trigger timer T1 locally, and locally sets the value of the timer T1 according to the valid time value in the trigger message, and starts the The timer stores the trigger message of the terminal at the same time.
  • the SGSN After receiving the signaling sent by the HSS, the SGSN reads the trigger message included therein, sets the trigger timer T2 locally, sets the value of the timer T2 locally according to the valid time value in the trigger message, and starts the The timer stores the trigger message of the terminal at the same time.
  • Step 506 The MME and the SGSN do not immediately send a trigger message because the terminal is in an idle state, and wait for the terminal to establish a NAS connection with the MME or the SGSN before sending.
  • the MME or the SGSN does not receive the periodic update request of the terminal, that is, the terminal reachability timer expires
  • the ISR function is deactivated after the MME or the SGSN independently performs implicit detachment, and the trigger message corresponds to The trigger timer T1 or T2 does not arrive, that is, the trigger message is still valid.
  • the MME or the SGSN removes the trigger message of the terminal, and sends a trigger request response message to the MTC IWF, informing the MTC IWF that the trigger message of the terminal fails to be sent.
  • Step 507 If the MME and the SGSN do not receive the periodic update request of the terminal, and perform implicit detachment, the MME and the SGSN respectively send a trigger request response message to the MTC IWF, and notify the MTC IWF that the trigger message of the terminal fails to be sent. . Then, after confirming that the trigger request response message sent by both the MME and the SGSN is received, the MTC IWF removes the trigger message of the terminal. At the same time, the MTC IWF sends a trigger response message to the MTC application server, notifying that the trigger message of the terminal of the MTC application server fails to be sent.
  • FIG. 6 is a schematic flowchart of a terminal trigger message processing process according to Embodiment 4 of the present invention. As shown in FIG. 6, the process includes:
  • Step 601 After the terminal is powered on, attached to the network, and activated by the ISR function, the MME and the SGSN currently served by the terminal have respectively enabled the terminal reachable timer for the terminal in the idle state, and the HSS has provided the MTC-IWF currently served by the terminal. The address of the MME and SGSN currently served by the terminal.
  • Step 602 When the MTC application server needs to obtain real-time data from the terminal, the trigger message is sent to the MTC IWF.
  • the trigger message includes the identifier of the terminal, the identifier of the application, the address of the server, the effective time of the trigger indication, and the like (where the identifier of the terminal is an external identifier used outside the network).
  • Step 603 The MTC IWF local database stores a one-to-one mapping table between the external identifier and the internal identifier, and a many-to-one correspondence table between the internal identifier and the MME and the SGSN.
  • the MTC IWF stores and parses the trigger message, 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 mapping table of the external identifier and the internal identifier stored in the local database, and
  • the MME and the SGSN where the terminal is located are searched according to the internal identifier stored in the database according to the internal identifier and the correspondence table of the MME and the SGSN.
  • a new trigger message is constructed, and the terminal internal identifier is used to replace the external identifier of the terminal in the original trigger message, and is sent to the MME and the SGSN by triggering the request signaling.
  • Step 604 After receiving the signaling sent by the MTC IWF, the MME reads the trigger message included therein, sets the trigger timer T1 locally, and locally sets the value of the timer T1 according to the valid time value in the trigger message, and starts. The timer stores the trigger message of the terminal at the same time.
  • the SGSN After receiving the signaling sent by the MTC IWF, the SGSN reads the trigger message included therein, sets the trigger timer T2 locally, and locally sets the value of the timer T2 according to the valid time value in the trigger message, and starts. The timer stores the trigger message of the terminal at the same time.
  • Step 605 The MME and the SGSN do not immediately send a trigger because the terminal is in an idle state.
  • the message needs to wait for the terminal to establish a NAS connection with the MME or the SGSN before sending.
  • the ISR function is deactivated after the MME or the SGSN independently performs implicit detachment, and the trigger message corresponds to The trigger timer T1 or T2 does not arrive, that is, the trigger message is still valid.
  • the MME or the SGSN removes the trigger message of the terminal, and sends a trigger request response message to the MTC IWF, informing the MTC IWF that the trigger message of the terminal fails to be sent.
  • Step 606 If the MME and the SGSN do not receive the periodic update request of the terminal, and perform implicit detachment, the MME and the SGSN respectively send a trigger request response message to the MTC IWF, and notify the MTC IWF that the trigger message of the terminal fails to be sent. . Then, after confirming that the trigger request response message sent by both the MME and the SGSN is received, the MTC IWF removes the trigger message of the terminal. At the same time, the MTC IWF sends a trigger response message to the MTC application server, notifying that the trigger message of the terminal of the MTC application server fails to be sent.
  • the trigger message of the terminal is not stored on the HSS or the MTC IWF.
  • FIG. 7 is a schematic flowchart of a terminal trigger message processing process according to Embodiment 5 of the present invention. As shown in FIG. 7, the process includes:
  • Step 701 After the terminal is powered on, attached to the network, and activated by the ISR function, the MME and the SGSN currently served by the terminal have respectively enabled the terminal reachable timer for the terminal in the idle state, and the HSS has provided the MTC-IWF currently served by the terminal. The address of the MME and SGSN currently served by the terminal.
  • Step 702 When the MTC application server needs to obtain real-time data from the terminal, the trigger message is sent to the MTC IWF.
  • the trigger message includes the identifier of the terminal, the identifier of the application, the address of the server, the effective time of the trigger indication, and the like (where the identifier of the terminal is an external identifier used outside the network).
  • Step 703 The MTC IWF local database stores one between the external identifier and the internal identifier. A mapping table, and a many-to-one correspondence table between the internal identifier and the MME and the SGSN.
  • the MTC IWF parses the trigger message, 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 mapping table of the external identifier and the internal identifier stored in the local database, and according to the internal
  • the MME and the SGSN where the terminal is located are identified in the correspondence between the internal identifier stored in the database and the MME and the SGSN.
  • a new trigger message is constructed, and the terminal internal identifier is used to replace the external identifier of the terminal in the original trigger message, and is sent to the MME and the SGSN by triggering the request signaling.
  • Step 704 After receiving the signaling sent by the MTC IWF, the MME reads the trigger message included therein, sets the trigger timer T1 locally, and locally sets the value of the timer T1 according to the valid time value in the trigger message, and starts. The timer stores the trigger message of the terminal at the same time.
  • the SGSN After receiving the signaling sent by the MTC IWF, the SGSN reads the trigger message included therein, sets the trigger timer T2 locally, and locally sets the value of the timer T2 according to the valid time value in the trigger message, and starts. The timer stores the trigger message of the terminal at the same time.
  • Step 705 The MME and the SGSN do not immediately send a trigger message because the terminal is in an idle state, and wait for the terminal to establish a NAS connection with the MME or the SGSN before sending.
  • the MME or the SGSN does not receive the periodic update request of the terminal, that is, the terminal reachability timer expires
  • the ISR function is deactivated after the MME or the SGSN independently performs implicit detachment, and the trigger message corresponds to The trigger timer T1 or T2 does not arrive, that is, the trigger message is still valid.
  • the MME or the SGSN removes the trigger message of the terminal, and sends a trigger request response message to the MTC application server, notifying the MTC application server that the trigger message of the terminal fails to be sent.

Landscapes

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

Abstract

La présente invention concerne un procédé de traitement d'un message de déclenchement de terminal comprenant : une entité de gestion de mobilité (MME) ou un nœud de support GPRS de desserte (SGSN) supprimant un message de déclenchement de terminal correspondant après la désactivation d'une fonction de réduction de signalement d'état inactif (ISR). L'invention concerne également un système de traitement d'un message de déclenchement de terminal et un élément de réseau associé. Selon la présente invention, puisque la MME ou le SGSN peuvent supprimer rapidement un message de déclenchement de terminal correspondant après la désactivation de la fonction ISR, on évite le gaspillage de ressources de stockage sur réseau.
PCT/CN2012/071721 2011-12-23 2012-02-28 Procédé et système de traitement d'un message de déclenchement de terminal et élément de réseau associé WO2013091303A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201110439267.7A CN103179542B (zh) 2011-12-23 2011-12-23 终端触发消息处理方法、系统及相关网元
CN201110439267.7 2011-12-23

Publications (1)

Publication Number Publication Date
WO2013091303A1 true WO2013091303A1 (fr) 2013-06-27

Family

ID=48639105

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2012/071721 WO2013091303A1 (fr) 2011-12-23 2012-02-28 Procédé et système de traitement d'un message de déclenchement de terminal et élément de réseau associé

Country Status (2)

Country Link
CN (1) CN103179542B (fr)
WO (1) WO2013091303A1 (fr)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109300074B (zh) * 2017-07-24 2020-11-10 中国电信股份有限公司 通信方法、系统以及归属用户服务器

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101572943A (zh) * 2008-04-28 2009-11-04 大唐移动通信设备有限公司 Mme释放isr情况下空闲态ue上下文的方法、装置及系统
CN101572942A (zh) * 2008-04-30 2009-11-04 华为技术有限公司 一种隐分离方法、系统和装置
CN102202270A (zh) * 2010-03-24 2011-09-28 中兴通讯股份有限公司 基于机器类通信的消息传输方法及互通功能实体
CN102244855A (zh) * 2010-05-10 2011-11-16 华为技术有限公司 一种基于位置的机器对机器通信方法、系统和装置

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2011149252A2 (fr) * 2010-05-26 2011-12-01 Lg Electronics Inc. Protocole de signalisation à base de nas pour protection contre les surcharges d'accès aléatoire dans des communications massives du type machine

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101572943A (zh) * 2008-04-28 2009-11-04 大唐移动通信设备有限公司 Mme释放isr情况下空闲态ue上下文的方法、装置及系统
CN101572942A (zh) * 2008-04-30 2009-11-04 华为技术有限公司 一种隐分离方法、系统和装置
CN102202270A (zh) * 2010-03-24 2011-09-28 中兴通讯股份有限公司 基于机器类通信的消息传输方法及互通功能实体
CN102244855A (zh) * 2010-05-10 2011-11-16 华为技术有限公司 一种基于位置的机器对机器通信方法、系统和装置

Also Published As

Publication number Publication date
CN103179542B (zh) 2019-04-02
CN103179542A (zh) 2013-06-26

Similar Documents

Publication Publication Date Title
WO2011082538A1 (fr) Procédé et appareil pour une optimisation de la mobilité basée sur un groupe dans des communication du type machine
WO2013107074A1 (fr) Procédé et système de détermination d'accessibilité de groupe de terminaux
WO2018170626A1 (fr) Procédé de récupération de connexion, entité de fonction de gestion d'accès et de mobilité, et équipement utilisateur
WO2012097757A2 (fr) Procédé d'association d'un équipement utilisateur "single-card dual-standby" (une seule carte, deux modes réseau) à un réseau
WO2014067466A1 (fr) Procédé et dispositif permettant de transmettre des données en liaison descendante
WO2013097332A1 (fr) Procédé et système de gestion d'un groupe de terminaux
WO2012151925A1 (fr) Procédé et système permettant une mise à jour de zone de suivi
WO2012113178A1 (fr) Procédé et appareil de détection de perte de connexion d'un terminal
WO2014201630A1 (fr) Procédé, dispositif et système de traitement de mise à jour de position de rattachement
CN103024810B (zh) 一种触发消息发送方法及系统
WO2013163945A1 (fr) Procédé pour rapporter un événement de communication de type de machine et dispositif associé
WO2013056595A1 (fr) Procédé, système et dispositif pour établir une connexion
WO2019095379A1 (fr) Procédé, dispositif, et support de stockage informatique pour l'activation et la désactivation d'un service
WO2014023175A1 (fr) Procédé de traitement de message en cas de coexistence de multiples identifiants externes d'un terminal, et dispositif côté réseau
WO2012016546A1 (fr) Procédé de traitement de radiomessagerie destiné à un équipement utilisateur et équipement
WO2013143218A1 (fr) Méthode de mise à jour pour compteur de messages de déclenchement, serveur de communication de type machine et terminal
WO2011044816A1 (fr) Procédé de suivi et dispositif de surveillance pour équipement utilisateur
CN103108305B (zh) 一种终端触发消息有效时间控制方法及系统
WO2013113240A1 (fr) Procédé de transmission d'informations de rn, procédé d'appel d'ue et appareil correspondant
WO2012129853A1 (fr) Procédé et système pour détecter un état de mobilité d'un terminal de communication de type machine
WO2012152046A1 (fr) Procédé et système d'accès à un terminal
WO2013091303A1 (fr) Procédé et système de traitement d'un message de déclenchement de terminal et élément de réseau associé
WO2013097337A1 (fr) Procédé et système de régulation d'encombrement de réseau
EP2696619B1 (fr) Système et procédé permettant de traiter des messages déclencheurs d'un terminal
WO2012151916A1 (fr) Procédé et système pour déclencher une réponse d'un terminal, terminal et côté réseau

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 12859031

Country of ref document: EP

Kind code of ref document: A1