Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, embodiments of the present invention will be described in detail with reference to the accompanying drawings.
A first embodiment of the present invention relates to a signaling tracking method, in this embodiment, a terminal switches between SGSNs, a first core network device is an old SGSN, a second core network device is a new SGSN, and a specific flow is shown in fig. 5.
In step 501, the source RNC decides to initiate a migration procedure of the serving RNS.
Next, in step 502, the source RNC sends a migration request (relocation required) message to the old SGSN.
Next, in step 503, the old SGSN determines that it is a migration flow of the serving RNS across SGSNs, and therefore, forwards the migration request message to the new SGSN. And the old SGSN judges whether the terminal needs to be tracked according to the tracking control and configuration parameters of the terminal which needs to be migrated and is stored by the old SGSN, and if so, the tracking control and configuration parameters of the terminal are added into the forwarded migration request message. If the terminal needing to be migrated does not need to be tracked, the migration flow of the service RNS of the terminal is completely the same as the migration flow in the prior art. In this embodiment, the terminal that needs to be migrated needs to be tracked, and the old SGSN adds the tracking control and configuration parameters of the terminal to the forwarded migration request message. Because the original signaling is used to carry the tracking control and configuration parameters in the step, no additional signaling is needed to be added.
Next, in step 504, the new SGSN sends a migration request (relocation request) message to the target RNC. And establishing a radio access bearer between the target RNC and the new SGSN.
Next, in step 505, after all necessary resources are successfully reserved, the target RNC sends a migration Request acknowledgement (Relocation Request Acknowledge) message to the new SGSN.
Next, in step 506, after receiving the migration request confirm message, the new SGSN sends a CN Invoke Trace message to the target RNC, where the message includes the tracking control and management parameters of the terminal. And the target RNC tracks the signaling of the terminal according to the received tracking control and configuration parameters.
Next, the new SGSN sends a migration request Response (ForwardRelocation Response) message to the old SGSN in step 507.
Next, the old SGSN sends a migration command (relocation command) message to the source RNC in step 508.
Next, in step 509, the source RNC forwards the data to the target RNC.
Next, in step 510, the source RNC transmits a Radio Resource Control (RRC) message to the terminal, instructing the terminal to start handover. After the terminal accesses the target cell, an RRC message is also sent to the target RNC, as in step 510'.
In step 511, the source RNC sends a serving RNS context to the target RNC via the old SGSN and the new SGSN. Specifically, the source RNC transmits the serving RNS Context to the old SGSN through a Forward SRNS Context message, and the old SGSN forwards the received serving RNS Context to the new SGSN through a Forward SRNS Context message. After receiving the service RNS Context, the new SGSN returns a response message to the old SGSN and sends the service RNS Context to the target RNC through a Forward SRNS Context message.
Next, in step 512, the target RNC sends a migration detection (relocation detect) message to the new SGSN to detect the terminal that needs to be migrated.
Next, in step 513, the target RNC sends a migration complete (relocation complete) message to the new SGSN.
Next, in step 514, the new SGSN forwards the migration complete message to the old SGSN, and the old SGSN returns a response message to the new SGSN after receiving the migration complete message.
Next, in step 515, the new SGSN sends an update PDP Context Request (update PDP Context Request) message to the GGSN, requesting the GGSN to perform a user plane handover. After finishing the user plane switching, the GGSN returns a response message for updating the PDP context to the new SGSN.
In step 516, the old SGSN sends an Iu release command (Iu ReleaseCommand) message to the source RNC, requesting the source RNC to release the resources of the terminal. After releasing the resources of the terminal, the source RNC returns an Iu release completion message to the old SGSN.
Next, in step 517, the terminal initiates an update procedure of a Routing Area (RA).
Therefore, in the embodiment, the tracking can be continued after the tracked terminal is migrated across the SGSNs, and the continuity of the tracking is ensured. Moreover, since the SGSN transmits the tracking control and configuration parameters to the relevant RNC in the corresponding access network after the tracking control and configuration parameters of the terminal are transmitted to the new SGSN, the tracking of the terminal can be maintained in the new access network.
In this embodiment, a terminal is switched across MMEs, a first core network device is an old MME, a second core network device is a new MME, and a specific flow is shown in fig. 6.
In step 601, the establishment of an IP bearer service via the serving SAE gateway 1 is completed between the terminal and the PDN SAE gateway.
Next, in step 602, the eNB1, which is the source eNB (evolved base station node), decides to initiate a handover to the eNB2, which is the target eNB.
Next, in step 603, the eNB1 sends a Handover request (Handover Required) message to the source MME (i.e., MME1), where the message needs to carry the eNB context of the terminal and the identity of the eNB 2.
Next, in step 604, the MME1 selects the MME2 as the target MME for serving the eNB2, and sends a Handover Preparation Request (Handover Request) message to the MME2, where the message includes context information of the terminal. In this step, the MME1 needs to determine whether the terminal needs to be tracked based on the tracking control and configuration parameters of the terminal that needs to be switched, which are stored in the MME 1. If necessary, the tracking control and configuration parameters of the terminal are added to the handover preparation request message. If the terminal needing to be switched does not need to be tracked, the cross-MME switching process of the terminal is completely the same as the cross-MME switching process in the prior art. In this embodiment, the terminal that needs to be handed over needs to be tracked, so the MME1 adds the tracking control and configuration parameters of the terminal to the handover preparation request message. Because the original signaling is used to carry the tracking control and configuration parameters in the step, no additional signaling is needed to be added.
Next, in step 604', the MME2 creates a context for the terminal, and sends a handover preparation request message to the serving SAE gateway 2, where the message carries information such as the eNB2 address and the Session Management (SM) context for the terminal. Serving SAE gateway 2 returns a response message to the handover preparation request to MME 2.
Next, in step 605, the MME2 transmits a handover preparation request message to the eNB2, which carries the eNB context information of the terminal and the tracking control and configuration parameters of the terminal. The eNB2 signals the terminal to track based on the received tracking control and configuration parameters. eNB2 sends a Handover Preparation Confirm (Handover confirmation) message to MME 2. The bearer plane establishment of eNB2 and serving SAE gateway 2 is completed.
Another implementation manner is that, in step 605, the tracking control and configuration parameters of the terminal are not included, but in subsequent step 606, after receiving the handover preparation confirm message, the MME2 sends a CN triggered tracking message (such as CN Invoke Trace) to the eNB2, where the message includes the tracking control and configuration parameters of the terminal. The eNB2 signals the terminal to track based on the received tracking control and configuration parameters.
If the tracking control and configuration parameters of the terminal are carried in the message of step 605, step 606 is not required. If step 606 is to be used, the tracking control and configuration parameters of the terminal cannot be carried in the message of step 605.
Next, in step 607, MME2 sends a handover preparation confirm message to MME1 and MME1 informs the serving SAE gateway 1 to migrate.
Next, in step 608, serving SAE gateway 1 forwards the data to serving SAE gateway 2 and the necessary methods are employed to reduce data loss.
Next, in step 609, MME1 sends a Handover Command message to eNB 1.
Next, in step 610, eNB2 detects the terminal and establishes a radio bearer.
Next, in step 611, eNB2 sends a handover complete message to MME2, MME2 informs serving SAE gateway 2 that the handover is complete.
Next, in step 612, a route update is made between the serving SAE gateway 2 and the PDN SAE gateway, i.e. the serving SAE gateway 2 sends a route update/bearer request to the PDN SAE gateway, and the PDN SAE gateway returns a response to the serving SAE gateway 2.
Next, in step 613, serving SAE gateway 2 notifies MME2 of the handover completion and MME2 notifies MME1 of the release of resources.
Next, in step 614, the resources of the terminal in the source system are released. That is, the MME notifies eNB1 of the handover completion, releases resources in this eNB1, and notifies serving SAE gateway 1 of the release of resources.
Next, in step 615, the establishment of the IP bearer service between the terminal and the PDN SAE gateway through the serving SAE gateway 2 is completed.
Therefore, in the embodiment, the tracked terminal can still continue to track after being switched across the MME, and the tracking continuity is ensured. Furthermore, since the MME sends the tracking control and configuration parameters to the relevant eNB2 in the corresponding access network after the tracking control and configuration parameters of the terminal are transferred to the new MME, the tracking of the terminal may be maintained in the new access network.
In the third embodiment of the present invention, in a signaling flow in which an MME and a serving SAE gateway interact, if a terminal involved in the signaling flow needs to be tracked, the MME sends tracking control and configuration parameters of the terminal to the serving SAE gateway, and the serving SAE gateway performs signaling tracking on the terminal according to the received tracking control and configuration parameters. In this embodiment, an interactive signaling flow is taken as an example of an attach flow of a terminal in an SAE system, and a specific flow is shown in fig. 7.
In step 701, the terminal sends an attach request (attach request) message to the MME, where the message carries an Access Point Name (Access Point Name, abbreviated as "APN").
Next, in step 702, the MME and HSS authenticate the terminal, which is an optional step.
Next, in step 703, the MME updates the location information of the terminal to the HSS.
Next, in steps 704 and 705, the HSS inserts the subscription data of the terminal into the MME. The MME responds to the HSS insert data message.
Next, in step 706, the HSS responds to the terminal location update message of the MME.
Then, in step 707, the MME determines whether the terminal needs to be tracked according to the tracking control and configuration parameters of the terminal stored in the MME itself, and if so, carries the tracking control and configuration parameters of the terminal in the bearer establishment request message and sends the bearer establishment request message to the serving SAE gateway. The bearer establishment request message also needs to include APN, User Plane (UP) key and other information. Because the original signaling is used for carrying the tracking control and the configuration parameters, additional signaling is not required to be added. And the service SAE gateway carries out signaling tracking on the terminal according to the received tracking control and configuration parameters of the terminal.
Next, in steps 708 to 710, the serving SAE gateway sends a route update/bearer request to the PDN SAE gateway; the PDN SAE gateway and the PCRF entity carry out interaction; the PDN SAE gateway replies a routing update/bearer confirmation message to the serving SAE gateway, and the serving SAE gateway sends a bearer establishment response message to the MME, wherein the message carries the IP configuration information.
Next, in steps 711 to 713, the MME sends a radio bearer setup request message to the eNB, requesting the eNB to set up a radio bearer, where the request message carries information such as Quality of service (QoS) and RRC key; eNB distributes wireless resources and establishes wireless bearing with the terminal; the eNB sends a radio bearer setup response message to the MME. Steps 711 to 713 are optional steps.
In step 714, the MME sends a bearer setup confirm message to the serving SAE gateway.
Next, in step 715 and step 716, the MME sends an attach accept (attach accept) message to the terminal, where the message carries IP configuration information and indicates that the attach request of the terminal is accepted; and the terminal sends an attachment completion message to the MME to complete the attachment process of the terminal.
It is not difficult to find that, in the present embodiment, the MME transmits the tracking control and the configuration parameter to the serving SAE gateway of the terminal through the interface between the MME and the serving SAE gateway, thereby implementing tracking of the signaling of the terminal in the serving SAE gateway and expanding the signaling tracking range.
A fourth embodiment of the present invention relates to a signaling tracking method, in which a terminal is handed over from a 2G (second generation mobile communication system)/3G (third generation mobile communication system) network to an evolved network, that is, a first core network device is an SGSN, a second core network device is an MME, and the first core network device and the second core network device are devices in different core networks. The specific flow is shown in fig. 8.
In step 801, the establishment of an IP bearer service between the terminal and the serving SAE gateway via the 2G/3G access network and the SGSN is completed.
Next, in step 802, the 2G/3G access network decides to initiate a handover procedure to the LTE access network.
Next, in step 803, the 2G/3G access network sends a handover request (handover required) message to the SGSN, and the SGSN selects a target MME for handover.
Then, in step 804, the SGSN determines whether the terminal needs to be tracked according to the tracking control and configuration parameters of the terminal stored in the SGSN, and if so, carries the tracking control and configuration parameters of the terminal in a Handover Preparation Request (Handover Request) message and sends the message to the selected MME; if the terminal does not need to be tracked, the switching process is exactly the same as the prior art. In this embodiment, the terminal needs to be tracked, and the SGSN carries the tracking control and configuration parameters of the terminal in the handover preparation request message and sends the handover preparation request message to the MME. Because the original signaling is used for carrying the tracking control and the configuration parameters, additional signaling is not required to be added.
And after receiving the message, the MME forwards the message to the LTE access network to request the LTE access network to reserve resources. And the LTE access network carries out signaling tracking on the terminal according to the tracking control and configuration parameters in the message.
Next, in step 805, the LTE access network reserves User Plane (UP) resources and establishes a user plane context for the terminal.
Next, in step 806, the LTE access network sends a handover preparation confirm message to the MME, which forwards the message to the SGSN.
A scheme of transferring the Trace parameter to the LTE access network in step 804 may be that instead of transferring the Trace parameter in step 804, a step is added after step 806, and the MME sends the Trace parameter to the LTE access network through a CNINVOKE Trace message.
Next, the SGSN sends a handover command message to the terminal through the 2G/3G access network in step 807.
Next, in step 808, the network side devices send data in a bi-cast or data forwarding manner to reduce data loss.
Next, in step 809, the LTE access network detects the access of the terminal.
Next, in step 810, the LTE access network sends a handover complete message to the MME, and the MME forwards the message to the SGSN.
Next, in step 811, the SGSN returns a handover complete response message to the MME.
Next, in step 812, the serving SAE gateway switches the user plane path into the LTE access network.
Next, in step 813, the SGSN instructs the 2G/3G access network to release the resources.
Next, in step 814, the establishment of the IP bearer service between the terminal and the serving SAE gateway over the LTE access network is completed.
Next, in step 815, the terminal updates the location information through a Tracking area update Procedure (Tracking area update Procedure).
Therefore, in the embodiment, the core network device of the tracked terminal can continue to track after being switched from the SGSN to the MME, thereby ensuring the continuity of tracking. Moreover, after the tracking control and configuration parameters of the terminal are transmitted to the MME, the MME sends the tracking control and configuration parameters to the corresponding access network, so that the terminal can be kept tracked in the new access network.
A fifth embodiment of the present invention relates to a signaling tracking method, in which a terminal is switched from an evolved network to a 2G/3G network, that is, a first core network device is an MME, a second core network device is an SGSN, and the first core network device and the second core network device are devices in different core networks. The specific flow is shown in fig. 9.
In step 901, the establishment of an IP bearer service between the terminal and the serving SAE gateway via the LTE access network is completed.
Next, in step 902, the LTE access network decides to initiate a handover procedure to the 2G/3G access network.
Next, in step 903, the LTE access network sends a handover request message to the MME, which selects a target SGSN for handover.
Then, in step 904, the MME determines whether the terminal needs to be tracked according to the tracking control and configuration parameters of the terminal stored in the MME itself, and if so, carries the tracking control and configuration parameters of the terminal in a handover preparation request message, and sends the handover preparation request message to the selected SGSN; if the terminal does not need to be tracked, the switching process is exactly the same as the prior art. In this embodiment, the terminal needs to be tracked, and the MME carries the tracking control and configuration parameters of the terminal in a handover preparation request message and sends the message to the SGSN. Because the original signaling is used for carrying the tracking control and the configuration parameters, additional signaling is not required to be added.
After receiving the message, SGSN forwards the message to 2G/3G access network to request 2G/3G access network to make resource reservation. And the 2G/3G access network carries out signaling tracking on the terminal according to the tracking control and configuration parameters in the message.
Next, in step 905, the 2G/3G access network reserves the user plane resources and establishes the user plane context for the terminal.
Next, in step 906, the 2G/3G access network sends a handover preparation confirm message to the SGSN, which forwards the message to the MME.
Next, in step 907, the MME sends a handover command message to the terminal through the LTE access network.
Next, in step 908, the network side devices transmit data in a bi-cast or data forwarding manner to reduce data loss.
Next, in step 909, the 2G/3G access network detects the access of the terminal.
Next, in step 910, the 2G/3G access network sends a handover complete message to the SGSN, and the SGSN forwards the message to the MME.
Next, in step 911, the MME returns a handover complete response message to the SGSN.
Next, in step 912, the serving SAE gateway switches the user plane path into the SGSN access network.
Next, in step 913 to step 915, the MME instructs the LTE access network to release resources; completing the establishment of IP bearing service between the terminal and the service SAE gateway through the 2G/3G access network and the SGSN; the terminal updates the location information through a tracking area update procedure.
Therefore, in the embodiment, the core network device of the tracked terminal can continue to track after being switched from the MME to the SGSN, thereby ensuring the continuity of tracking. Moreover, since the SGSN transmits the tracking control and configuration parameters of the terminal to the corresponding access network after the tracking control and configuration parameters of the terminal are transmitted to the SGSN, the tracking of the terminal can be maintained in the new access network.
A sixth embodiment of the present invention relates to a signaling tracking method, in this embodiment, a terminal is attached to a UMTS and a Radio Access Technology (RAT) is converted into an LTE network, so that a first core network device is an SGSN and a second core network device is an MME. The specific flow is shown in fig. 10.
In step 1001, the terminal sends a network attach request to the SGSN.
Next, in step 1002, the SGSN initiates an authentication procedure for the terminal.
Next, in step 1003, the SGSN registers with the HSS, and the HSS replies a registration confirmation message to the SGSN.
Next, in step 1004, the SGSN transmits an attach accept message to the terminal and accepts the network attach request of the terminal. The message carries information such as a Temporary Mobile Subscriber Identity (TMSI) of the terminal, a Routing Area (RA), and the like.
Next, in step 1005, the terminal initiates an activate PDP Context (Active PDP Context) flow.
After the RAT is converted into the LTE network, step 1006 is entered, the terminal selects the LTE access network, and initiates a route area Update (RA Update) message to the MME/UPE, where the message carries the TMSI, the routing area, and other information of the terminal.
Next, in step 1007, the MME/UPE requests the context of the terminal from the SGSN through an SGSN context request message. The SGSN sends the context of the terminal to the MME/UPE through the SGSN context response message, and the SGSN judges whether the terminal needs to be tracked according to the tracking control and configuration parameters of the terminal stored by the SGSN, if so, the tracking control and configuration parameters of the terminal are added to the SGSN context response message and sent to the MME/UPE. If the terminal does not need to be tracked, the procedure is the same as that of the prior art. In this embodiment, the terminal needs to be tracked, the SGSN adds the tracking control and configuration parameters of the terminal to the SGSN context response message, and sends the SGSN context response message to the MME/UPE, where the SGSN context response message also needs to include information such as the TMSI of the terminal, a key in a Mobility Management (MM) context, and the like. Because the original signaling is used to carry the tracking control and configuration parameters in the step, no additional signaling is needed to be added.
Next, in step 1008, the MME/UPE authenticates the terminal, which is an optional step.
Next, in step 1009, the MME/UPE sends an SGSN context confirm message to the SGSN.
Next, in step 1010, the MME registers with the HSS, and the HSS transmits a registration acknowledgement to the MME indicating that the registration is complete.
Next, in step 1011 and step 1012, the MME/UPE sends a routing area update accept message to the terminal; the terminal returns a routing area updating completion message to the MME/UPE to complete the routing area updating process.
When RAT change occurs again, that is, after RAT is changed to 2G/3G access network, step 1013 is entered, and the terminal sends a routing area update request to SGSN, where the request carries relevant information.
Next, in step 1014, the SGSN sends a message requesting the context of the terminal to the MME/UPE. The MME/UPE sends the context of the terminal to the SGSN through the SGSN context response message, and the MME/UP also needs to judge whether the terminal needs to be tracked according to the tracking control and configuration parameters of the terminal stored by the MME/UP, if so, the tracking control and configuration parameters of the terminal are added into the SGSN context response message and sent to the SGSN. If the terminal does not need to be tracked, the procedure is the same as that of the prior art. This step is similar to step 1007 and will not be described herein.
Next, in step 1015, the SGSN registers with the HSS, and the HSS returns a registration acknowledgement to the SGSN.
Next, in step 1016, the SGSN sends a routing area update accept message to the terminal, completing the update of the routing area.
Therefore, in the embodiment, when the tracked terminal is attached to the UMTS and the RAT is changed, the tracking can be continued, and the continuity of the tracking is ensured.
A seventh embodiment of the present invention relates to a signaling tracking method, in which a terminal attaches to SAE and a RAT is changed to a 2G/3G network, and thus a first core network device is MME and a second core network device is SGSN. The specific flow is shown in fig. 11.
In step 1101, the terminal sends a network attach request to the MME/UPE, where the request carries related information.
Next, in step 1102, the MME/UPE performs an authentication procedure with the terminal.
Next, in step 1103, the MME/UPE registers with the HSS, which replies a registration confirmation message to the MME/UPE.
Next, in step 1104, the MME/UPE transmits an attach accept message to the terminal and accepts the network attach request of the terminal. The message carries the relevant information of the terminal.
After the RAT is changed to a 2G/3G network, steps 1105 and 1106 are entered. Step 1105 and step 1106 are the same as step 1013 and step 1014, respectively, and are not described herein again. Thereafter, an authentication procedure may be performed between the SGSN and the terminal, as in step 1107.
Next, in step 1108, the SGSN registers with the HSS, and the HSS replies a registration confirmation message to the SGSN.
Next, in step 1109, the SGSN returns an SGSN context confirm message to the MME/UPE.
Next, in step 1110 and step 1111, the SGSN sends an update PDP request message to the MME/UPE; and the MME/UPE returns an update PDP response message to the SGSN.
Next, in step 1112, the SGSN sends a routing area update accept message to the terminal, and the terminal returns a routing area update complete message to the SGSN, thereby completing the update of the routing area.
Therefore, in the embodiment, when the tracked terminal is attached to the SAE and the RAT is converted into the 2G/3G network, the tracking can be continued, and the tracking continuity is ensured.
It should be noted that, in the embodiment of the present invention, the MME and the UPE are taken as an example to be described in one physical device, and if the MME and the UPE are separated in different physical devices, a corresponding signaling interaction procedure needs to be performed between the MME and the UPE, which is not described herein again.
An eighth embodiment of the present invention relates to a core network device (e.g., SGSN or MME) including: the storage unit is used for storing tracking control and configuration parameters of the terminal; a judging unit, configured to judge whether the terminal needs to be tracked according to the tracking control and configuration parameters of the terminal stored in the storage unit when the terminal migrates from the core network device to another core network device; and the sending unit is used for sending the tracking control and the configuration parameters of the terminal to the other core network device when the judging unit judges that the terminal needs to be tracked.
The core network equipment also comprises a receiving unit used for receiving the tracking control and configuration parameters from other core network equipment; and the tracking unit is used for tracking the signaling of the terminal according to the tracking control and configuration parameters received by the receiving unit. Through each unit contained in the core network equipment, the tracked terminal can still continue to track after the migration across the SGSN or the MME or the migration between the SGSN and the MME occurs, and the tracking continuity is ensured.
A ninth embodiment of the present invention relates to a signaling tracking system, as shown in fig. 12, including an MME device and a serving SAE gateway device.
Wherein, MME equipment includes: the storage unit is used for storing tracking control and configuration parameters of the terminal; a judging unit, configured to judge whether the terminal needs to be tracked in a signaling flow (for example, an attachment flow of the terminal in the SAE system) where the MME and the serving SAE gateway interact with each other, according to the tracking control and configuration parameters of the terminal stored in the storage unit; and a sending unit, configured to send the tracking control and configuration parameters of the terminal to the serving SAE gateway device when the determining unit determines that the terminal needs to be tracked.
The serving SAE gateway device comprises a receiving unit, a tracking control unit and a configuration unit, wherein the receiving unit is used for receiving the tracking control and configuration parameters of the terminal from the MME device; and the tracking unit is used for carrying out signaling tracking on the terminal according to the tracking control and configuration parameters received by the receiving unit. The signaling of the terminal can be tracked in the service SAE gateway, and the signaling tracking range is expanded.
In summary, in the embodiment of the present invention, when a terminal migrates between two core network devices, if the terminal needs to be tracked, tracking control and configuration parameters of the terminal are transmitted between the two core network devices. Therefore, the tracked terminal can still continue to track after the migration of the SGSN or MME, and the continuity of tracking is ensured.
The core network device may be an SGSN or an MME, and the transmission of the tracking control and configuration parameters may occur between two SGSNs, two MMEs, or between an SGSN and an MME, so that the terminal may still continue tracking when migrating between UMTS and SAE.
The tracking control and configuration parameters are carried in the migration request message, the handover preparation request message or the SGSN context response message, and the tracking control and configuration parameters can be carried by using the original signaling, so that additional signaling is not required to be added.
After the tracking control and configuration parameters are transmitted to the new core network device, the core network device may send the tracking control and configuration parameters to the relevant RNC or eNodeB in the corresponding access network, so that the tracking of the corresponding terminal may be maintained in the new access network.
The MME transmits the tracking control and the configuration parameters to the service SAE gateway through an interface between the MME and the service SAE gateway, so that the tracking of the signaling of the terminal in the service SAE gateway can be realized, and the signaling tracking range is expanded.
In the signaling flow where the MME and the serving SAE gateway interact, such as the attachment flow of the terminal in the SAE system, the tracking control and the configuration parameters are transmitted to the serving SAE gateway, and the tracking control and the configuration parameters can be carried by using the original signaling, so that additional signaling is not required to be added.
While the invention has been shown and described with reference to certain preferred embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the invention.