WO2007128242A1 - A method and a system for registering by network side instead of a terminal - Google Patents

Abstract

A method and a system for registering by a network side instead of a terminal, the method includes: the network side receives an attachment request initiated by the terminal over a first access network, wherein the attachment request carries a terminal registration information; the network side which takes the replace of the terminal carries out the registration operation based on the location area which the first access network lies in. During the terminal registration, the terminal registration is convenient and the terminal registration means is rich by using the method in which the network side replaces the terminal. During the terminal registration, the procedure of the terminal registration is efficient and rational by considering fully the location area which the terminal lies in and treating distinctively the local network and the visited network.

Description

 Method and system for network side to replace terminal registration

 The present invention relates to the field of communications, and in particular, to a method and system for replacing a terminal by a network side. Background technique

 In order to ensure the competitiveness of the 3GPP system in the next 10 years and beyond, an access technology evolution work is being carried out within the 3GPP organization. In particular, in order to enhance the ability of 3GPP systems to handle rapidly growing IP data services, the use of packet technology within 3GPP systems requires further enhancement. The most important parts of this type of technology evolution include: reduced latency, higher user data rates, increased system capacity and coverage, and lower overall operator costs. Moreover, the evolved network structure is also an important indicator for the backward compatibility of existing networks.

 Several conditions that an evolved network architecture needs to meet are as follows:

 1. In the initialization phase of the terminal access network, the basic IP connection needs to be established in the evolved network;

 2. The evolved network architecture must support access to non-3GPP systems, including support for service continuity.

As shown in Figure 1, it is a current wireless evolution network architecture diagram. As can be seen from the figure, the core network of the wireless evolution network mainly includes a mobility management entity (MME, Mobility Management Entity), and a user data plane entity (Serving GW, User Plane Entity). ), three logical function modules (PDN GW, Inter Access Systems Anchor), wherein the MME is a mobility management module, responsible for mobility management of the control plane, including user context and mobility state management, assigning user temporary identity, Security function, etc., which corresponds to the control plane part of the current GPRS support node (SGSN) of the UMTS system; the Serving GW is a user plane entity, responsible for initiating paging for downlink data in idle state, managing and saving IP bearers Parameters and intra-network routing information, etc., it is for the current UMTS system internal SGSN and gateway GPRS support node The data plane part of the (GGSN, Gateway GPRS Support Node); the PDN GW acts as a user plane anchor between different access systems. In the figure, S1 - S7 are different interfaces.

 In an evolved network architecture, the terminal must be permanently online, that is, a default IP bearer needs to be established when the user attaches the network. Figure 2 shows the process of network attachment in a non-roaming scenario, including the following steps:

 5001. Network Discovery and Access System Selection „

 The terminal discovered (system framework evolution/long-term evolution) SAE/LTE access system, and then initiated network selection and access. If there is a network share, select a shared network.

 5002. The terminal initiates an attach request (Attach Request) to the MME/Serving GW, including previously registered information, such as: a temporary identifier, etc.; if the terminal does not have previous registration information, includes its permanent identifier.

 In the case of considering network sharing, the attach request message should include the selected network or the MME/Serving GW.

 Considering the redundancy of the MME/Serving GW, the evolved RAN will select an MME/Serving GW.

 The attach request may include information of a default IP access bearer, such as: a user selected IP address or APN.

 5003. If the previous registration information is reported by the terminal, the MME/Serving GW retrieves the user's information from the previous MME/Serving GW by sending the old registration information.

 5004. The previous MME/Serving GW sends user information to the new MME/Serving GW, for example: the permanent identity of the user.

 5005. The user or terminal authenticates at the new MME/Serving GW.

5006. The MME/Serving GW registers with the HSS as the serving MME/Serving GW (Register MME) of the terminal.

5007. The information of the user or terminal on the old MME/Serving GW is deleted or annotated as Delete UE registration information.

 5008. The HSS confirms the registration of the new MME/Serving GW, confirms that the subscription information of the default IP access bearer is transmitted to the MME/Serving GW, and the policy and charging control information related to the default bearer is also transmitted to the MME/Serving. GW.

 5009. The MME/Serving GW selects a PDN GW (Selection of Intersystem Mobility Anchor GW) and configures the terminal IP address.

 The configuration of the IP address is determined by the policy of receiving user selection parameters, subscription data, home network or visited network from the terminal.

 5010. The PDN GW performs the IP Plane Configuration (User Plane Route Configuration) based on the determined user IP address.

 The user plane establishes and applies default policy and charging procedures.

 SOU. The MME/Serving GW provides the default QoS configuration (Configure IP Bearer QoS) to the evolved RAN, for example: the upper limit of the data rate.

 5012. The MME/Serving GW sends an attach message (Attach Accept) of the accepting terminal and assigns a temporary identifier to the terminal, and the user IP address is also sent to the terminal.

 In a roaming scenario, the roaming limit is checked, and if it is violated, the attachment is rejected.

 5013. The terminal confirms the attach success (Attach Confirm).

 In the foregoing prior art, the user may be in the home network, or in the network of the SAE to which the network is attached, and the location of the user is different, which will directly lead to different user attachment process usage schemes. According to the prior art described above, The terminal registers with the network side and does not use resources on the network side, and allocates different bearers and service IP addresses according to scenarios in different networks of the user. This scheme adopts the principle of allocation of default IP addresses, which causes a lot of inconvenience. The PDN GW selection and other issues have not been resolved. Summary of the invention

The embodiment of the invention provides a method for the network side to replace the terminal registration, which is used to solve the problem that the registration scheme is inconvenient in the user registration process existing in the prior art. The embodiment of the invention provides a method for the network side to replace the terminal registration, including:

 The network side receives the attach request initiated by the first access network, and the attach request carries the terminal registration information;

 The network side performs a registration operation instead of the terminal according to the location area where the first access network is located. The embodiment of the invention further provides a network side replacement terminal registration system, including:

 An attach request initiating unit, configured to initiate an attach request to the network side by using the first access network, where the attach request carries the terminal registration information;

 The registration unit is located at the network side, and is configured to perform a registration operation instead of the terminal according to the location area where the first access network is located.

 The embodiment of the invention further provides a method for registering a terminal, including:

 The network side receives an attach request initiated by the terminal through the access network, where the attach request carries the terminal registration information;

 The network side obtains the PDN GW information corresponding to the terminal from the HSS.

 The network side selects the corresponding PDN-GW according to the PDN GW information, and establishes a related user plane bearer.

 The embodiment of the invention further provides a terminal registration system, including:

 An attach request initiating unit, configured to initiate an attach request to the network side by using the first access network, where the attach request carries the terminal registration information;

 The PDN GW information acquiring unit is configured to obtain the PDN GW information corresponding to the terminal from the HSS, and the user plane bearer establishing unit is configured to select a corresponding PDN GW according to the PDN GW information corresponding to the terminal, and establish a related user plane bearer.

 In the solution of the embodiment of the present invention, in the terminal registration process, the network side is used to replace the terminal registration method, which can facilitate the terminal registration and enrich the terminal registration means.

In the solution of the embodiment of the present invention, in the process of registering the terminal, the location area of the terminal is fully considered, and the difference between the local network and the visited network can make the registration process of the terminal effective and reasonable. DRAWINGS

 1 is a schematic structural diagram of an evolved network in the prior art;

 2 is a schematic diagram of a terminal attachment process in the prior art;

 3 is a schematic flowchart of an embodiment of the present invention;

 4 is a schematic flow chart of Embodiment 1 to Embodiment 34 of the present invention;

 38 is a schematic structural diagram of a system according to an embodiment of the present invention;

 FIG. 39 is a schematic structural diagram of another system according to an embodiment of the present invention. Detailed ways

 Specific embodiments of the present invention are described below in conjunction with the drawings.

 As shown in FIG. 3, it is a flow chart of registration of a terminal in a 3GPP access system according to an embodiment of the present invention. As can be seen from the figure, the method mainly includes the following steps:

 S100. The terminal discovers that the SAE/LTE access system subsequently initiates network selection and access.

 If there is a network share, one of the shared networks will be selected.

 S200. The terminal initiates an attach request to the MME, including previously registered information (for example: temporary identification). If the terminal does not have previous registration information, its permanent identity is included.

 In the case of considering network sharing, the attach request message should include the selected network or the MME/Serving GW.

 The attach request may include information about the associated default IP bearer, such as the preferred IP address or APN.

 S300. If the previous registration information is reported by the terminal, the MME retrieves the user's information from the previous MME by sending the previous registration information.

 S400. The previous MME sends the user information to the new MME (for example: the permanent identity of the user).

S500. The user or terminal performs authentication on the new MME/Serving GW.

S300. The user or terminal authenticates at the new MME.

S600. The MME discovers the IP address of a Serving GW by using a DNS query mode (other manners) according to the APN parameter included in the terminal attachment information. S700. The MME notifies the Serving GW to allocate an IP address to the user terminal, and the address may be the user's home address, or a local address (whether or not the local address is assigned).

 The manner of obtaining the address in the step may be obtained by querying the DHCP server, or may be obtained by the PDN GW to allocate the home address of the terminal, and may also be configured by the MME/Serving GW by configuring the static address in the HSS. Request acquisition from HSS.

 S800. The MME registers with the HSS as the serving MME of the terminal.

 S900. The information of the user or terminal on the old MME is deleted or identified as unreachable.

 S1000. The old MME notifies the old Serving GW to release information about the user plane.

 SHOO. HSS confirms the registration of the new MME. The subscription information of the authorized default IP access bearer is transmitted to the MME. The default bearer related policy and charging control information is also transmitted to the MME. In addition, the information of the PDN GW corresponding to the user terminal (which can be used as HA in this scheme) will also be transmitted to the MME. The PDN GW information may be an IP address, or an access point name APN or other indication information.

 The user's home address can also be stored in the user's subscription information in a static manner. When the HSS responds to the MME registration, the user's home address is transmitted to the MME.

 Step S700 in the above solution has no strict order relationship with S800, S900, S1000, and S1100, and can be completed in other orders.

 There is no strict order relationship between the above steps S1000 and S1100, and the order of the two steps can be reversed.

 S1200. The MME compares the IP prefix address of the obtained PDN GW (ie, HA) with the IP address of the Serving GW obtained by the MME, and determines that the access network is the home network or the visited network.

 In the foregoing step S1200, the manner of determining is not limited to this manner, and the access network may be compared to the network prefix of the PDN GW IP address according to the address allocated in step S700 to determine that the access network is a home network or a visited network. .

S1300. When the terminal is in the home network, the MME notifies the Serving GW to perform proxy mobile registration with the PDN GW instead of the terminal. This step is optional when the terminal is within the home network.

 S1400. Serving GW replaces the terminal to perform proxy mobile registration with the PDN GW, wherein the registered message format is the same as the format specified in the IETF.

 This step is optional when the terminal is within the home network.

 When the terminal is in the visited network, the Serving GW performs proxy mobile registration with the PDN GW instead of the terminal, wherein the registration message format is the same as the message format specified in the IETF, but the terminal address (HoA) is all 0s to indicate that the PDN GW is required (ie : HA ) Assigns the home address (HoA) of the terminal; and the CoA address option is the IP address of the Serving GW.

 S1500. The PDN GW (ie: HA) verifies the reliability of the message to the AAA server after receiving the registration request message.

 S1600. The PDN GW confirms the registration response message. When the terminal is within the home network, the PDN GW (i.e., HA) receives the proxy mobile IP registration message and responds to the Serving GW according to the normal registration response message specified in the IETF.

 This step is optional when the terminal is within the home network.

 When the terminal is in the visited network, it is determined according to the HoA all 0 in the message that the home address needs to be assigned to the terminal; the PDN GW (ie: HA) first requests an IP address from the DHCP as the home address of the terminal, and then establishes a home address and handed over. Binding of the address (its own IP address reported by the Serving GW), and then returning a registration confirmation message to the Serving GW; the format of the registration confirmation message is consistent with the IETF specification, the home address is the assigned IP address, and the destination address of the message is Serving GW's address.

 S1700. When the terminal is in the visited network, the Serving GW receives the registration response message of the PDN GW, and establishes a home address of the terminal and a local address binding assigned to the terminal.

 S1800. The Serving GW notifies the MME of the completion of the registration request. And report the home address (HoA) assigned to the terminal.

 SI 900. The MME provides the QoS configuration of the default bearer to the evolved RAN, such as the maximum rate limit for transmitting data. This QoS configuration may require a trigger mechanism.

S2000. The MME accepts the network attachment of the terminal and assigns a temporary flag to the UE, together with the assigned The home IP address and local address (LoA) are given to the terminal.

 In a roaming scenario, the roaming limit is checked and if it is violated the attachment will be rejected.

 S2100. The terminal responds with a confirmation message of successful attachment.

 Several specific embodiments are seen below. Example 1:

 Embodiment 1 is a process of registering a terminal in a 3GPP home network, where the MME and the Serving GW are merged entities, and the home address of the terminal stores the subscription information of the user in the HSS. When the MME/Serving GW registers with the HSS document, The MME/Serving GW is replied to by the HSS through a registration response message.

 As shown in FIG. 4, the registration process of the terminal in the 3GPP home network includes the following steps:

5101. The terminal discovers that the SAE/LTE access system subsequently initiates network selection and access. If there is a network share, then one of the shared networks will be selected and the specific mechanism is not determined.

 5102. The terminal initiates an attach request to the MME/Serving GW, including previously registered information (for example: temporary identification). If the terminal does not have previous registration information, its permanent identity is included.

 In the case of considering network sharing, the attach request message should include the selected network or the MME/Serving GW.

 The attach request may include information about the associated default IP bearer, such as the preferred IP address or APN.

 5103. If the previous registration information is reported by the terminal, the MME/Serving GW retrieves the user's information from the previous MME/Serving GW by sending the previous registration information.

 5104. The previous MME/Serving GW sends user information to the new MME/Serving GW (eg, the user's permanent identity).

 5105. The user or terminal authenticates at the new MME/Serving GW.

 5106. The MME/Serving GW registers with the HSS as the serving MME/Serving GW of the terminal.

 5107. The information of the user or terminal on the old MME/Serving GW will be deleted or identified as unreachable.

S1.08. The HSS confirms the registration of the new MME/Serving GW. Authorize the default IP access bearer The approximate information is transmitted to the MME/Serving GW. The default bearer related policy and charging control information is also transmitted to the MME/Serving GW. In addition, the IP address of the PDN GW (ie: HA) corresponding to the user terminal will also be transmitted to the MME/Serving GW. The user's home address is stored in the user's subscription information in a static manner, and is transmitted to the MME when the HSS confirms the registration of the new MME.

 After the MME/Serving GW obtains the IP address of the PDN GW (ie, HA), it compares the network prefix address with its own IP address, and determines that the access network is the home network or the visited network.

 5110. When the terminal is in the home network, the MME/Serving GW replaces the terminal to perform proxy mobile registration with the PDN GW, where the registration message format is the same as the message format specified in the IETF.

 5111. The PDN GW (ie: HA) authenticates to the AAA server after receiving the registration request message. The reliability of the message. '

 5112. The PDN GW confirms the registration response message. When the terminal is in the home network, the PDN GW (ie: HA) receives the proxy mobile IP registration message and responds to the MME/Serving GW according to the normal registration response message specified in the IETF.

 5113. The MME/Serving GW provides the QoS configuration of the default bearer to the evolved RAN, such as the maximum rate limit for transmitting data. Whether or not this QoS configuration needs to be increased is not yet determined (for example, the need to send upstream or downstream data).

 5114. The MME accepts the network attachment of the terminal and allocates a temporary identifier to the UE, together with the assigned home IP address to the terminal.

 5115. The terminal responds with a confirmation message of a successful attachment. Example 2:

 Embodiment 2 is a process in which a terminal registers in a 3GPP home network, where the MME, the Serving GW is a merged entity, and the home address of the terminal stores the subscription information of the user in the HSS. When the MME/Serving GW registers with the HSS, The HSS responds to the MME/Serving GW by registering a response message.

As shown in FIG. 5, the registration process of the terminal in the 3GPP home network specifically includes: Step S201 - Step S209 is the same as Step S101 - Step S109 of Embodiment 1, and will not be described again. '

 5210. When the terminal is in the home network, the MME/Serving GW determines that the terminal is returned to the home network by the external network or the VPLMN network, and then performs proxy mobile deregistration to the PDN GW instead of the terminal.

 5211. The PDN GW (ie: HA) verifies the reliability of the message to the AAA server after receiving the deregistration request message.

 5212. The PDN GW acknowledges the deregistration response message to the MME/Serving GW.

 5213. The MME/Serving GW provides the QoS configuration of the default bearer to the evolved RAN, such as the maximum rate limit for transmitting data. Whether or not this QoS configuration needs to be increased is not yet determined (for example, the need to send upstream or downstream data).

 5214. The MME accepts the network attachment of the terminal and assigns a temporary flag to the UE, together with the assigned home IP address to the terminal.

 5215. The terminal responds with a confirmation message of a successful attachment. Example 3:

 Embodiment 3 is a process in which a terminal registers in a 3GPP home network, where the MME and the Serving GW are merged entities, and the MME/Serving GW requests the HA to allocate a home address to the terminal.

 As shown in Figure 6, the registration process of the terminal in the 3GPP home network includes the following steps:

5301. The terminal discovers that the SAE/LTE access system subsequently initiates network selection and access. If there is a network share, then 'shared one network will be selected, and the specific mechanism is not determined.

 5302. The terminal initiates an attach request to the MME/Serving GW, including previously registered information (for example: temporary identification). If the terminal does not have previous registration information, its permanent identity is included.

 In the case of considering network sharing, the attach request message should include the selected network or the MME/Serving GW.

 The attach request may include information about the associated default IP bearer, such as the preferred IP address or APN.

5303. If the previous registration information is reported by the terminal, the MME/Serving GW will send the message. The previous registration information is sent to the previous MME/Serving GW to retrieve the user's information.

 5304. The previous MME/Serving GW sends user information to the new MME/Serving GW (eg, the user's permanent identity).

 5305. The user or terminal authenticates at the new MME/Serving GW.

 5306. The MME/Serving GW registers with the HSS as the serving MME/Serving GW of the terminal.

 5307. The information of the user or terminal on the old MME/Serving GW will be deleted or identified as unreachable.

 5308. The HSS confirms the registration of the new MME/Serving GW. The subscription information authorizing the default IP access bearer is transmitted to the MME/Serving GW. The default bearer related policy and charging control information is also transmitted to the MME/Serving GW. In addition, the IP address of the PDN GW (ie: HA) corresponding to the user terminal will also be transmitted to the MME/Serving GW.

 5309. The MME/Serving GW compares the network prefix address with its own IP address according to the IP of the PDN GW (ie, HA), and determines that the access network is the home network or the visited network.

 In step S310, the MME/Serving GW requests the HA to assign the home address to the terminal, and A receives the request and assigns the home address of the terminal to the MME/Serving GW.HA to allocate the home address of the terminal, and can send a request to the DHCP server. But it is not limited to this way.

 5311. When the terminal is in the home network, the MME/Serving GW performs proxy mobile registration with the PDN GW instead of the terminal, wherein the registration message format is the same as the message format specified in the IETF.

 5312. The PDN GW (ie: HA) verifies the reliability of the message to the AAA server after receiving the registration request message.

 5313. The PDN GW confirms the registration response message. When the terminal is in the home network, the PDN GW (ie, HA) receives the proxy mobile IP registration message and responds to the MME/Serving GW according to the normal registration response message specified in the IETF.

 5314. The MME/Serving GW provides the evolved RAN with a default bearer QoS configuration, such as a maximum rate limit for transmitting data.

 5315. The MME accepts the network attachment of the terminal and assigns a temporary flag to the UE, together with the assigned

II Home IP address to the terminal.

 S316. The terminal responds with a confirmation message of successful attachment. Example 4:

 Embodiment 4 is a process in which a terminal registers in a 3GPP home network, where the MME, the Serving GW is a merging entity, and the MME/Serving GW requests the HA to allocate a home address to the terminal.

 As shown in Figure 7, the registration process of the terminal in the 3GPP home network.

 The specific procedure is consistent with the steps in Embodiment 3, except that the S411-S413 step is that the MME/Serving GW determines that the terminal is returned to the home network by the external network or the VPLMN network, and then performs proxy mobile deregistration to the PDN GW instead of the terminal.

 5411. When the terminal is in the home network, the MME/Serving GW determines that the terminal is returned to the home network by the external network or the VPLMN network, and then the proxy terminal performs proxy mobile deregistration to the PDN GW.

 5412. The PDN GW (ie: HA) verifies the reliability of the message to the AAA server after receiving the deregistration request message.

 5413. The PDN GW acknowledges the deregistration response message to the MME/Serving GW.

 Step S414 - Step S416 is identical to steps S314 - S316 of Embodiment 3. Example 5

 Embodiment 5 is a process in which a terminal registers in a 3GPP visited network, where the MME and the Serving GW are merged entities, as shown in FIG. 8, which is a registration process of the terminal in the 3GPP visited network.

 5501. The terminal discovers that the SAE/LTE access system subsequently initiates network selection and access. If there is a network share, then one of the shared networks will be selected and the specific mechanism is not determined.

 5502. The terminal initiates an attach request to the MME/Serving GW, including previously registered information (for example: temporary identification). If the terminal does not have previous registration information, its permanent identity is included.

In the case of network sharing, the attach request message should include the selected network or MME/Serving GWo. The attach request may include information about the associated default IP bearer, such as a preferred IP address or APN.

 5503. If the previous registration information is on the terminal, the MME/Serving GW retrieves the user's information from the previous MME/Serving GW by sending the previous registration information.

 5504. The previous MME/Serving GW sends user information to the new MME/Serving GW (eg, the user's permanent identity).

 5505. The user or terminal authenticates at the new MME/Serving GW.

 5506. The Serving GW is triggered by the MME to assign an IP address to the user terminal. This address is the user's local address. The way to obtain an address can be queried to the DHCP server, but it is not limited to this method.

 5507. The MME/Serving GW registers with the HSS as the serving MME/Serving GW of the terminal.

 5508. The information of the user or terminal on the old MME/Serving GW is deleted or identified as unreachable.

 5509. The HSS confirms the registration of the new MME/Serving GW. The subscription information authorizing the default IP access bearer is transmitted to the MME/Serving GW. The default bearer related policy and charging control information is also transmitted to the MME/Serving GW. In addition, the IP address of the PDN GW (ie: HA) corresponding to the user terminal will also be transmitted to the MME/Serving GW.

 In step S506, there is no strict order relationship with S507, S508, and S509.

 5510. The MME/Serving GW compares the network prefix address with its own IP address according to the IP of the PDN GW (ie, HA), and determines that the access network is the home network or the visited network. The manner of the judgment is not limited to this manner, and the access network may be determined to be the home network or the visited network according to the network address prefix allocated in step S506 and the network prefix of the PDN GWIP address.

5511. When the terminal is in the visited network, the MME/Serving GW performs proxy mobile registration with the PDN GW instead of the terminal, wherein the registration message format is the same as the message format specified in the IETF. The registration message format is the same as the message format specified in the IETF, but the terminal address (HoA) is all 0s, indicating that the home address (HoA) of the terminal to be allocated by the PDN GW (ie, HA) is required; and the CoA address option is the MME/ Serving GW's address. 5512. The PDN GW (ie: HA) verifies the reliability of the message to the AAA server after receiving the registration request message.

 5513. When the terminal is in the visited network, it is determined according to the HoA all 0 in the message that the home address needs to be assigned to the terminal; the PDN GW (ie: HA) first requests an IP address from the DHCP as the home address of the terminal, and then establishes a home address. And the binding of the care-of address (the MME/Serving GW reports its own IP address), and then returns a registration confirmation message to the MME/Serving GW; the format of the registration confirmation message is consistent with the IETF specification, and the home address is the assigned IP address. The address of the message is the address of the MME/Serving GW.

 5514. When the terminal is in the visited network, after receiving the registration response message of the PDN GW, the MME/Serving GW establishes a home address of the terminal and a local address binding assigned to the terminal.

 5515. The MME/Serving GW provides the QoS configuration of the default bearer to the evolved RAN, such as the maximum rate limit for transmitting data. Whether this QoS configuration needs to be increased is not yet determined (for example: the need to send upstream or downstream data).

 5516. The MME accepts the network attachment of the terminal, and allocates a temporary identifier to the UE, together with the assigned home IP address and local address (LoA) to the terminal. In a roaming scenario, the roaming limit is checked and if it is violated the attachment will be rejected.

 5517. The terminal responds with a confirmation message of a successful attachment. Example 6:

 Embodiment 6 is a process 2 in which a terminal registers in a 3GPP visited network, where the MME and the Serving GW are merged entities, but the manner of acquiring the HoA address is different from that in Embodiment 5.

 As shown in Figure 9, it is the registration process of the terminal in the 3GPP visited network.

 5601. The terminal discovers that the SAE/LTE access system subsequently initiates network selection and access. If there is a network share, then one of the shared networks will be selected and the specific mechanism is not determined.

 5602. The terminal initiates an attach request to the MME/Serving GW, including previously registered information (for example: temporary identification). If the terminal does not have previous registration information, its permanent identity is included.

In the case of network sharing, the attach request message should include the selected network or MME/Serving GW.

 The attach request may include information about the associated default IP bearer, such as the preferred IP address or APN.

 5603. If the previous registration information is reported by the terminal, then the VDVE/Serving GW retrieves the user's information from the previous MME/Serving GW by sending the previous registration information.

 5604. The previous MME/Serving GW sends user information to the new MME/Serving GW (eg, the user's permanent identity).

 5605. The user or terminal authenticates at the new MME/Serving GW.

 5606. The Serving GW is triggered by the MME to assign an IP address to the user terminal, which is the user's local address. The way to obtain an address can be queried to the DHCP server, but is not limited to this method.

 5607. The MME/Serving GW registers with the HSS as the serving MME/Serving GW of the terminal.

 5608. The information of the user or terminal on the old MME/Serving GW is deleted or identified as unreachable.

 5609. The HSS confirms the registration of the new MME/Serving GW. The subscription information authorizing the default IP access bearer is transmitted to the MME/Serving GW. The default bearer related policy and charging control information is also transmitted to the MME/Serving GW. In addition, the IP address of the PDN GW (ie: HA) corresponding to the user terminal will also be transmitted to the MME/Serving GW.

 The user's home address is stored in the user's subscription information in a static manner, and is transmitted to the MME when the HSS confirms the registration of the new MME.

 Note: There is no strict order relationship with S607, S608, S609 in step S606.

 The MME/Serving GW compares the network prefix address with its own IP address according to the IP of the PDN GW (ie, HA), and determines that the access network is the home network or the visited network. However, the manner of judging is not limited to this manner, and the access network may be compared to the network prefix of the PDN GWIP address according to the network address obtained in step S606 to determine whether the access network is a home network or a visited network.

5611. When the terminal is in the visited network, the MME/Serving GW performs proxy mobile registration with the PDN GW instead of the terminal, wherein the registration message format is the same as the message format specified in the IETF. Note The message format is the same as the message format specified in the IETF, but the terminal address (HoA) is the static home address obtained from the HSS, and the CoA address option is the address of the MME/Serving GW.

 5612. The PDN GW (ie: HA) verifies the reliability of the message to the AAA server upon receiving the registration request message.

 5613. When the terminal is in the visited network, the HA will establish a binding of the home address and the care-of address (its own IP address reported by the MME/Serving GW), and then return a registration confirmation message to the MME/Serving GW.

 5614. When the terminal is in the visited network, after receiving the registration response message of the PDN GW, the MME/Serving GW establishes a home address of the terminal and a local address binding assigned to the terminal.

 5615. The MME/Serving GW provides the QoS configuration of the default bearer to the evolved RAN, such as the maximum rate limit for transmitting data.

 The MME accepts the network attachment of the terminal and assigns a temporary flag to the UE, together with the assigned home IP address and local address (LoA) to the terminal. In a roaming scenario, the roaming limit is checked and if it is violated the attachment will be rejected.

 5617. The terminal responds with a confirmation message of a successful attachment. Example 7

 Embodiment 7 is a process in which a terminal registers in a 3GPP visited network, where the MME and the Serving GW are merged entities, and the LoA address does not need to be allocated to the terminal.

 As shown in Figure 10, the registration process of the terminal in the 3GPP visited network:

 5701. The terminal discovers that the SAE/LTE access system subsequently initiates network selection and access.

 5702. The terminal initiates an attach request to the MME/Serving GW.

 5703. If the previous registration information is reported by the terminal, the MME/Serving GW retrieves the user's information from the previous MME/Serving GW by transmitting the previous registration information.

 5704. The previous MME/Serving GW sends user information to the new MME/Serving GW (eg, the user's 7-year long identifier).

5705. The user or terminal authenticates at the new MME/Serving GW. 5706. The MME/Serving GW registers with the HSS as the serving MME/Serving GW of the terminal.

 5707. The information of the user or terminal on the old MME/Serving GW is deleted or identified as unreachable.

 5708. The HSS confirms the registration of the new MME/Serving GW.

 S709: The MME/Serving GW compares the network prefix address with its own IP address according to the IP of the PDN GW (ie, HA), and determines that the access network is the home network or the visited network.

 5710. When the terminal is in the visited network, the MME/Serving GW replaces the terminal to perform proxy mobile registration with the PDN GW, where the registration message format is the same as the message format specified in the IETF. The registration message format is the same as the message format specified in the IETF, but the terminal address (HoA) is all 0s, indicating that the home address (HoA) of the terminal to be allocated by the PDN GW (ie, HA) is required; and the CoA address option is the MME/ Serving GW's address.

 5711. The PDN GW (ie: HA) verifies the reliability of the message to the AAA server after receiving the registration request message.

 5712. When the terminal is in the visited network, it is determined according to the HoA all 0 in the message that the home address needs to be assigned to the terminal; the PDN GW (ie: HA) first requests an IP address from the DHCP as the home address of the terminal, and then establishes a home address. And the binding of the care-of address (the MME/Serving GW reports its own IP address), and then returns a registration confirmation message to the MME/Serving GW; the format of the registration confirmation message is consistent with the IETF specification, and the home address is the assigned IP address. The destination address of the message is the address of the MME/Serving GW.

 5713. The MME/Serving GW provides the default RA QoS configuration to the evolved RA, such as the maximum rate limit for transmitting data. Whether this QoS configuration needs to be increased is not yet determined (for example: the need to send upstream or downstream data).

 S714: The MME accepts the network attachment of the terminal, and allocates a temporary identifier to the UE, together with the assigned home IP address to the terminal. In a roaming scenario, the roaming limit is checked and if it is violated the attachment will be rejected.

S715: The terminal responds with a confirmation message of successful attachment. Example 8

 As shown in Figure 11, the registration process of the terminal in the 3GPP visited network includes:

 5801. The terminal discovers that the SAE/LTE access system subsequently initiates network selection and access.

 5802. The terminal initiates an attach request to the MME/Serving GW.

 5803. If the terminal is reported by the terminal with the static registration information, the MME/Serving GW retrieves the user's information from the previous MME/Serving GW by transmitting the previous registration information.

 5804. The previous MME/Serving GW sends user information to the new MME/Serving GW.

 5805. The user or terminal authenticates at the new MME/Serving GW.

 5806. The MME/Serving GW registers with the HSS as the serving MME/Serving GW of the terminal.

 5807. The information of the user or terminal on the old MME/Serving GW is deleted or identified as unreachable. .

 5808. The HSS confirms the registration of the new MME/Serving GW. The subscription information authorizing the default IP access bearer is transmitted to the MME/Serving GW. The default bearer-related policy and charging control information is also transmitted to the MME/Serving Gl. The IP address of the PDN GW (ie: HA) corresponding to the user terminal is also transmitted to the MME/Serving GW.

 The user's home address is stored in the user's subscription information in a static manner, and is transmitted to the MME when the HSS responds to the MME's registration message.

 5809. The MME/Serving GW compares the network prefix address with its own IP address according to the IP of the PDN GW (ie, HA), and determines that the access network is the home network or the visited network.

 5810. When the terminal is in the visited network, the MME/Serving GW performs proxy mobile registration with the PDN GW instead of the terminal, wherein the registration message format is the same as the message format specified in the IETF. The registration message format is the same as the message format specified in the IETF, but the terminal address (HoA) is a static home address obtained from the HSS, and the CoA address option is the address of the MME/Serving GW.

5811. The PDN GW (ie: HA) verifies the reliability of the message to the AAA server after receiving the registration request message. 5812. When the terminal is in the visited network, the HA will establish a binding of the home address and the care-of address (the MME/Serving GWJ^'s own IP address), and then return a registration confirmation message to the MME/Serving GW.

 5813. The MME/Serving GW provides the QoS configuration of the default bearer to the evolved RAN, such as the maximum rate limit for transmitting data.

 5814. The MME accepts the network attachment of the terminal and allocates a temporary identifier to the UE, together with the assigned home IP address to the terminal. In a roaming scenario, the roaming limit is checked and if it is violated the attachment will be rejected.

 5815. The terminal responds with a confirmation message of successful attachment. Example 9

 Embodiment 9 is a process in which a terminal registers in a 3GPP home network, where the MME, the Serving GW, and the PDN GW are separate entities; the HoA address of the terminal is allocated by the Serving GW or the Serving GW queries the DHCP server to allocate.

 As shown in FIG. 12, the terminal is in the 3GPP home network MME, Serving GW, PDN GW full separation registration process, including:

 5901. The terminal discovers that the SAE/LTE access system subsequently initiates network selection and access.

 5902. The terminal initiates an attach request to the MME, including previously registered information (eg, temporary identification). If the terminal does not have previous registration information, its permanent identity is included.

 In the case of network sharing, the attach request message should include the selected network or MME/Serving GWo.

 The attach request may include information about the associated default IP bearer, such as a preferred IP address or APN.

 5903. If the previous registration information is reported by the terminal, the MME retrieves the user's information from the previous MME by sending the previous registration information.

 5904. The previous MME sends the user information to the new MME (for example: the user's permanent identity).

5905. The user or terminal checks in the new MME.

5906. The MME queries the DNS according to the APN parameters included in the terminal attachment information. ,

Way (but not limited to this method) to discover the IP address of a Serving GW; the discovery mechanism of Serving GW is not covered by the patent;

 5907. The MME informs the Serving GW to assign an IP address to the user terminal, which is the user's home address. The way to obtain an address can be queried to the DHCP server, but it is not limited to this method. The Serving GW will assign the HoA address of a terminal to the MME.

 5908. The MME registers with the HSS as the serving MME of the terminal.

 5909. The information of the user or terminal on the old MME will be deleted or identified as unreachable.

 5910. The old MME notifies the old Serving GW to release information about the user plane.

 5911. The HSS confirms the registration of the new MME. The subscription information of the authorized default IP access bearer is transmitted to the MME. The default bearer related policy and charging control information is also transmitted to the MME. In addition, the IP address of the PDN GW (ie: HA) corresponding to the user terminal will also be transmitted to the MME.

 5912. After obtaining the IP of the PDN GW (ie, HA), the MME compares the network prefix address with the IP address of the Serving GW obtained by the MME, and determines that the access network is the home network or the visited network. However, the manner of judging is not limited to this manner, and the access network obtained by the step 7 is compared with the network prefix of the PDN GW IP address to determine whether the access network is a home network or a visited network.

 5913. When the terminal is in the home network, the MME notifies the Serving GW to perform proxy mobile registration with the PDN GW instead of the terminal.

 5914. Serving GW replaces the terminal to perform proxy mobile registration with the PDN GW, where the registration message format is the same as that specified in the IETF.

 5915. The PDN GW (ie: HA) verifies the reliability of the message to the AAA server after receiving the registration request message.

 5916. The PDN GW confirms the registration response message. When the terminal is in the home network, the PDN GW (ie: HA) receives the proxy mobile IP registration message and responds to the Serving GW according to the normal registration response message specified in the IETF.

 5917. The Serving GW notifies the MME of the completion of the registration request. ;

5918. The MME provides the QoS configuration of the default bearer to the evolved RAN, for example, the maximum transmission data Rate limit.

 5919. The MME accepts the network attachment of the terminal and assigns a temporary identifier to the UE, together with the assigned home IP address to the terminal.

 5920. The terminal responds with a confirmation message of a successful attachment. Example 10

 Embodiment 10 is a process for a terminal to register in a 3GPP home network, where the MME, the Serving GW, and the PDN GW are separate entities; the HoA address of the terminal is allocated by the Serving GW or the Serving GW queries the DHCP server for allocation, but the Serving GW is not required to be used for the terminal. Go to HA registration.

 As shown in Figure 13, the terminal is in the 3GPP home network MME, Serving GW, PDN GW full separation registration process:

 51001. The terminal discovered that the SAE/LTE access system subsequently initiated network selection and access.

 51002. The terminal initiates an attach request to the MME, including previously registered information (eg, temporary identification). If the terminal does not have previous registration information, its permanent identity is included.

 In the case of considering network sharing, the attach request message should include the selected network or the MME/Serving GW.

 The attach request may include information about the associated default IP bearer, such as a preferred IP address or APN.

 51003. If the previous registration information is reported by the terminal, the MME retrieves the user's information from the previous MME by sending the previous registration information.

 51004. The previous MME sends user information to the new MME (eg, the user's permanent identity).

51005. The user or terminal authenticates at the new MME.

 51006. The MME discovers the IP address of a Serving GW through a DNS query mode (but not limited to this method) according to the APN parameter included in the terminal attachment information; the discovery mechanism of the Serving GW is not within the scope of the patent protection;

51007. The MME notifies the Serving GW to assign an IP address to the user terminal, which is the home address of the user. The way to obtain an address can be queried to a DHCP server, but is not limited to this method. The Serving GW will assign the HoA address of a terminal to the MME. 51008. The MME registers with the HSS as the serving MME of the terminal.

 51009. The information of the user or terminal on the old MME will be deleted or identified as unreachable.

 51010. The old MME notifies the old Serving GW to release information about the user plane.

 51011. The HSS confirms the registration of the new MME. The subscription information for the authorized default IP access bearer is transmitted to the VIME. The default bearer related policy and charging control information is also transmitted to the MME. In addition, the IP address of the PDN GW (ie: HA) corresponding to the user terminal will also be transmitted to the MME.

 The MME compares the network prefix address with the IP address of the Serving GW obtained by the PDN GW (ie, HA), and determines whether the access network is the home network or the visited network. However, the manner of judging is not limited to this manner, and the access network may be compared to the network prefix of the PDN GW IP address according to the address allocated in step 7, to determine whether the access network is a home network or a visited network.

 51018. The MME provides the QoS configuration of the default bearer to the evolved RAN, such as the maximum rate limit for transmitting data.

 51019. The MME accepts the network attachment of the terminal and assigns a temporary flag to the UE, together with the assigned home IP address to the terminal.

 51020. The terminal responds with a confirmation message of a successful attachment. Example 11

 Embodiment 11 is a process of registering a terminal in a 3GPP home network, where MME, Serving GW>PDN GW is a separate entity; the HoA address of the terminal is allocated by the Serving GW or the Serving GW queries the DHCP server to allocate, but the scenario is that the terminal accesses the network from the visited network. Go back to the home network.

 As shown in Figure 14, the terminal is in the 3GPP home network MME, Serving GW, PDN GW full separation registration process.

 51101. The terminal discovers that the SAE/LTE access system subsequently initiates network selection and access.

 51102. The terminal initiates an attach request to the V1ME, including previously registered information (eg, temporary identification). If the terminal does not have previous registration information, its permanent identity is included.

In the case of network sharing, the attach request message should include the selected network or MME/Serving GW.

 The attach request may include information about the associated default IP bearer, such as a preferred IP address or APN.

 51103. If the previous registration information is reported by the terminal, M E retrieves the user's information from the previous MME by sending the previous registration information.

 51104. The previous MME sends user information to the new MME (eg, the user's permanent identity).

51105. The user or terminal authenticates at the new MME.

 51106. The MME discovers the IP address of a Serving GW through a DNS query mode (but not limited to this method) according to the APN parameters included in the terminal attachment information; the discovery mechanism of the Serving GW is not within the scope of the patent protection.

 51107. The MME informs the Serving GW to assign an IP address to the user terminal, which is the user's home address. The way to obtain an address can be queried to the DHCP server, but it is not limited to this method. The Serving GW will assign the HoA address of a terminal to the MME.

 51108. The MME registers with the HSS as the serving MME of the terminal.

 SI 109. The information of the user or terminal on the old MME will be deleted or identified as unreachable.

 51110. The old MME informs the old Serving GW to release information about the user plane.

 51111. The HSS confirms the registration of the new MME. The subscription information of the authorized default IP access bearer is transmitted to the MME. The default bearer related policy and charging control information is also transmitted to the MME. In addition, the IP address of the PDN GW (ie: HA) corresponding to the user terminal will also be transmitted to the MME.

 SI 112. The MME compares the network prefix address with the IP address of the Serving GW obtained by the PDN GW (ie, HA), and determines that the access network is the home network or the visited network. However, the manner of judging is not limited to this manner, and the address obtained by assigning in step 7 may be compared with the network prefix of the PDN GW IP address to determine whether the access network is a home network or a visited network.

 S1113. When the terminal is in the home network, the MME notifies the Serving GW to perform proxy mobile registration with the PDN GW instead of the terminal.

 S1114 - Step S1116 is a process for deregistering with the HA.

S1117. The Serving GW notifies the MME of the completion of the registration request. ―

 SI 118. The MME provides the QoS configuration of the default bearer to the evolved RAN, such as the maximum rate limit for transmitting data.

 51119. The MME accepts the network attachment of the terminal and assigns a temporary identifier to the UE, together with the assigned home IP address to the terminal.

 51120. The terminal responds with a confirmation message of a successful attachment. Example 12:

 Embodiment 12 is a process in which a terminal registers in a 3GPP home network, where the MME, the Serving GW, and the PDN GW are separate entities; the HoA address of the terminal is requested by the Serving GW to be assigned by the Inter As Anchor to the terminal.

 As shown in Figure 15, the terminal is in the 3GPP home network MME, Serving GW, PDN GW full separation registration process, where:

 51201. The terminal discovers that the S AE/LTE access system subsequently initiates network selection and access.

 51202. The terminal initiates an attach request to the MME, including previously registered information (eg, temporary identification). If the terminal does not have previous registration information, its permanent identity is included.

 In the case of considering network sharing, the attach request message should include the selected network or the MME/Serving GW.

 The attach request may include information about the associated default IP bearer, such as a preferred IP address or APN.

 51203. If the previous registration information is reported by the terminal, the MME retrieves the user's information from the previous MME by sending the previous registration information.

 51204. The previous MME sends user information to the new MME (eg, the user's permanent identity).

51205. The user or terminal authenticates at the new MME.

 51206. The MME discovers the IP address of a Serving GW through a DNS query mode (but not limited to this method) according to the APN parameters included in the terminal attachment information; the discovery mechanism of the Serving GW is not within the scope of the patent protection.

 51207. The MME registers with the HSS as the serving MME of the terminal.

51208. The information of the user or terminal on the old MME will be deleted or identified as unreachable. 51209. The old MME informs the old Serving GW to release information about the user plane.

51210. The HSS confirms the registration of the new MME. The subscription information of the authorized default IP access bearer is transmitted to the MME. The default bearer related policy and charging control information is also transmitted to the MME. In addition, the IP address of the PDN GW (ie: HA) corresponding to the user terminal will also be transmitted to the MME.

 After the IP address of the PDN GW (ie, HA) is obtained, the MME compares the network prefix address with the IP address of the Serving GW that is obtained by the MME, and determines that the access network is the home network or the visited network.

 51212. Triggered by the MME, the Serving GW goes to the Inter AS anchor^ to allocate the HoA address to the terminal, and the Inter As Anchor responds to the message, and sends the assigned HoA address to Serving GW and MME.

 51213. The MME notifies the Serving GW to perform proxy mobile registration with the PDN GW instead of the terminal.

51214. Serving GW replaces the terminal to perform proxy mobile registration with the PDN GW, where the registration message format is the same as that specified in the IETF.

 51215. The PDN GW (ie: HA) verifies the reliability of the message to the AAA server after receiving the registration request message.

 51216. The PDN GW acknowledges the registration response message. After receiving the proxy mobile IP registration message, the PDN GW (ie: HA) responds to the Serving GW according to the normal registration response message specified in the IETF.

 51217. The Serving GW notifies the MME of the completion of the registration request.

 51218. The MME provides the QoS configuration of the default bearer to the evolved RAN, such as the maximum rate limit for transmitting data.

 51219. The MME accepts the network attachment of the terminal and assigns a temporary flag to the UE, together with the assigned home IP address to the terminal.

 51220. The terminal responds with a confirmation message of successful attachment. Example 13

Embodiment 13 is a process in which a terminal registers in a 3GPP home network, where the MME, the Serving GW, and the PDN GW are separate entities; the HoA address of the terminal is requested by the Serving GW to the Inter As Anchor. Terminal allocation, but does not require the Serving GW to register with the HA on behalf of the terminal.

 As shown in Figure 16, the terminal is in the 3GPP home network MME, Serving GW, PDN GW full separation registration process.

 The scenario of the embodiment is that the terminal initiates the attachment from the home network, but does not need the Serving GW to register with the HA on behalf of the terminal. Therefore, in accordance with the steps in Embodiment 12, only the MME is notified to notify the Serving GW to register and register the HA on behalf of the terminal. Message. That is, step S1301 - step S1312 and step S1201 - S1212 in step 12, step S1313 - step S1315 are consistent with step S1218 - step S1220 in embodiment 12. Example 14

 Embodiment 14 is a process of registering a terminal in a 3GPP home network, where the MME, the Serving GW, and the PDN GW are separate entities; the HoA address of the terminal is requested by the Serving GW to be assigned by the Inter As Anchor to the terminal, but the scenario is that the terminal returns from the visited network. To the home network.

 As shown in Figure 17, the terminal is in the 3GPP home network MME, Serving GW, PDN GW full separation registration process.

 The steps in the embodiment 14 are basically the same as those in the embodiment 12, except that the scenario occurs is that the scenario is that the terminal returns from the visited network to the home network, and the difference is that the Serving GW replaces the terminal to perform the process of deregistering with the HA, that is, step S1415. - S1416 is a deregistration process. The rest corresponds to Embodiment 12. The visited network includes an external network and a VPLMN network. Example 15

 Embodiment 15 is a process of registering a terminal in a 3GPP home network, where the MME, the Serving GW, and the PDN GW are separate entities; the HoA address of the terminal is statically stored in the HSS, and is carried when the HSS responds to the registration request message to the MME. Address to the MME.

As shown in FIG. 18, the terminal is in the 3GPP home network, and the MME, Serving GW, and PDN GW are completely separated and registered. 51507. The MME registers with the HSS as the serving MME of the terminal.

 51508. The information of the user or terminal on the old MME will be deleted or identified as unreachable.

 51509. The old MME notifies the old Serving GW to release information about the user plane.

 51510. The HSS confirms the registration of the new MME. The subscription information of the authorized default IP access bearer is transmitted to the MME. The default bearer related policy and charging control information is also transmitted to the MME. In addition, the IP address of the PDN GW (ie: HA) corresponding to the user terminal and the HoA address of the user (which is stored in the subscription information of the user in the HSS in a static manner) will be delivered to the MME through the message.

 There is no strict order relationship between step S 1509 and step S 1510.

 51511. The MME compares the network prefix address with the IP address of the Serving GW obtained by the PDN GW (ie, HA), and determines that the access network is the home network or the visited network.

 51512. The MME notifies the Serving GW to perform proxy mobile registration with the PDN GW instead of the terminal.

51513. The Serving GW performs proxy mobile registration with the PDN GW instead of the terminal, where the registration message format is the same as that specified in the IETF.

 51514. The PDN GW (ie: HA) verifies the reliability of the message to the AAA server upon receipt of the registration request message.

 51515. The PDN GW confirms the registration response message. When the terminal is in the home network, the PDN GW (i.e., HA) receives the proxy mobile IP registration message and responds to the Serving GW according to the normal registration response message specified in the IETF.

 51516. The Serving GW notifies the MME of the completion of the registration request.

 51517. The MME provides the default RA QoS configuration to the evolved RA, such as the maximum rate limit for transmitting data.

 51518. The MME accepts the network attachment of the terminal and assigns a temporary flag to the UE, together with the assigned home IP address to the terminal.

51519. The terminal responds with a confirmation message of a successful attachment. Example 16: Embodiment 16 is a process of registering a terminal in a 3GPP home network, where the MME, the Serving GW, and the PDN GW are separate entities; the HoA address of the terminal is statically stored in the HSS, and is carried when the HSS responds to the registration request message to the MME. The address is given to the MME. Unlike the embodiment 16, the Serving GW is not required to register with the HA L.

 As shown in Figure 19, the terminal is in the 3GPP home network MME, Serving GW, PDN GW full separation registration process.

 The difference between the embodiment 16 and the embodiment 15 is that only the MME is not required to notify the Serving GW to register with the HA, and the corresponding interaction step can be deleted. That is, the steps S1601 - S1611 of the embodiment 16 are the same as the S1501 - S1511 of the embodiment 15, the steps S1612 - S1614 are the same as the embodiment 15 steps S1517 - S1519. Example 17

 Embodiment 17 is a process of registering a terminal in a 3GPP home network, where the MME, the Serving GW, and the PDN GW are separate entities; the HoA address of the terminal is statically stored in the HSS, and is carried when the HSS responds to the registration request message to the MME. Addressing the MME, this embodiment is consistent with the steps in Embodiment 16, except that the scenario is that the terminal returns from the visited network to the home network, which requires the MME to notify the Serving GW to deregister the HA on behalf of the terminal.

 As shown in Figure 20, the terminal is in the 3GPP home network MME, Serving GW, PDN GW full separation registration process.

 Embodiment 17 is consistent with the steps in Embodiment 15, except that the scenario is a case where the terminal returns from the visited network to the home network, which requires the MME to notify the Serving GW to deregister the HA on behalf of the terminal. That is, step S1713 - S1715 is a process of deregistration. The remaining steps are consistent with Example 15. Example 18

Embodiment 18 is a process for a terminal to register in a 3GPP visited network, where the MME, the Serving GW, and the PDN GW are separate entities; the HoA address of the terminal is notified by the MME that the Serving GW applies to the Inter As Anchor during the HA registration process, this embodiment It includes the case where LoA is allocated by the Serving GW. As shown in FIG. 21, the terminal is in the 3GPP visited network MME, Serving GW, PDN GW full separation registration process, including:

 51801. The terminal discovers that the SAE/LTE access system subsequently initiates network selection and access.

 51802. The terminal initiates an attach request to the MME, including previously registered information (eg, temporary identification). If the terminal does not have previous registration information, its permanent identity is included.

In the case of considering network sharing, the attach request message should include the selected network or MME/Serving GW ₀

 The attach request may include information about the associated default IP bearer, such as a preferred IP address or APN.

51803. If the previous registration information is reported by the terminal, the MME retrieves the user's information from the previous MME by sending the previous registration information.

 51804. The previous MME sends user information to the new MME (eg, the user's permanent identity).

51805. The user or terminal is raising rights in the new MME.

 51806. The MME discovers the IP address of a Serving GW through a DNS query mode (but not limited to this method) according to the APN parameters included in the terminal attachment information.

 51807. The MME informs the Serving GW to assign an IP address to the user terminal, which is the LoA of the user. The way to obtain an address can be queried to the DHCP server, but it is not limited to this method. The Serving GW will assign the LoA address of a terminal to the MME.

 51808. The MME registers with the HSS as the serving MME of the terminal.

 51809. The information of the user or terminal on the old MME will be deleted or identified as unreachable.

 51810. The old MME notifies the old Serving GW to release information about the user plane.

 51811. The HSS confirms the registration of the new MME. The subscription information of the authorized default IP access bearer is transmitted to the MME. The default bearer related policy and charging control information is also transmitted to the MME. In addition, the IP address of the PDN GW (ie: HA) corresponding to the user terminal will also be transmitted to the MME.

 Step S1807, there is no strict order relationship with S1808, S1809, S1810, S1811. There is no strict order relationship between step S 1810 and step S 1811.

The MME compares the network prefix address with the IP address of the Serving GW obtained by the MME according to the IP of the PDN GW (ie, HA), and determines that the access network is the home network or the visited network. Network. However, the manner of judging is not limited to this manner, and the access network may be determined to be the home network or the visited network according to the network prefix that is allocated in step S3907 and compared with the network prefix of the PDN GW IP address.

 51813. The MME notifies the Serving GW to register with the PDN GW instead of the terminal.

 51814. Serving GW replaces the terminal to perform proxy mobile registration with the PDN GW, where the registration message format is the same as the message format specified in the IETF, but the terminal address (HoA) is all 0s, indicating that the PDN GW (ie: HA) is required to allocate the terminal. Home address (HoA); and the CoA address option is the IP address of the Serving GW;

 51815. The PDN GW (ie: HA) verifies the reliability of the message to the AAA server after receiving the registration request message.

 51816. The PDN GW confirms the registration response message. According to the HoA all 0 in the message, the terminal needs to be assigned a home address; the PDN GW (ie: HA) first requests an IP address from the DHCP as the home address of the terminal, and then establishes a home address and a care-of address (the Serving GW reports it) Binding of its own IP address), and then returning a registration confirmation message to the Serving GW; the format of the registration confirmation message is consistent with the IETF specification, the home address is the assigned IP address, and the destination address of the message is the address of the Serving GW.

 51817. After receiving the registration response message of the PDN GW, the Serving GW establishes a home address of the terminal and a local address binding assigned to the terminal.

 51818. The Serving GW notifies the MME of the completion of the registration request, and reports the home address (HoA) assigned to the terminal to the MME.

 51819. The MME provides the QoS configuration of the default bearer to the evolved RAN, such as the maximum rate limit for transmitting data.

 51820. The MME accepts the network attachment of the terminal, and allocates a temporary identifier to the UE, together with the assigned home IP address and local address (LoA) to the terminal. In a roaming scenario, the roaming limit is checked and if it is violated the attachment will be rejected.

51821. The terminal responds with a confirmation message of a successful attachment. Example 19

 Embodiment 19 is a process for a terminal to register in a 3GPP visited network, where the MME and the Serving GW PDN GW are separate entities; the HoA address of the terminal is notified by the MME that the Serving GW applies to the Inter As Anchor during the HA registration process, in this embodiment There is no case where LoA is allocated by the Serving GW.

 As shown in Figure 22, the terminal is in the 3GPP visited network MME, Serving GW, PDN GW full separation registration process.

 51901. The terminal discovers that the SAE/LTE access system subsequently initiates network selection and access.

 51902. The terminal initiates an attach request to the MME, including previously registered information (eg, temporary identification). If the terminal does not have previous registration information, its permanent identity is included.

 In the case of considering network sharing, the attach request message should include the selected network or the MME/Serving GW.

 The attach request may include information about the associated default IP bearer, such as a preferred IP address or APN.

 51903. If the previous registration information is reported by the terminal, the MME retrieves the user's information from the previous MME by sending the previous registration information.

 51904. The previous MME sends user information to the new MME (eg, the user's permanent identity).

51905. The user or terminal authenticates at the new MME.

 51906. The MME discovers the IP address of a Serving GW through a DNS query mode (but not limited to this method) according to the APN parameter included in the terminal attachment information; the discovery mechanism of the Serving GW is not within the scope of the patent protection;

 51907. The MME registers with the HSS as the serving MME of the terminal.

 51908. The information of the user or terminal on the old MME will be deleted or identified as unreachable.

 51909. The old MME notifies the old Serving GW to release information about the user plane.

 51910. The HSS confirms the registration of the new MME. The subscription information of the authorized default IP access bearer is transmitted to the MME. The default bearer-related policy and charging control information is also transmitted to the MME. In addition, the IP address of the PDN GW (ie: HA) corresponding to the user terminal will also be transmitted to MMEo.

There is no strict order relationship between step S1909 and step S1910. 51911. The MME compares the network prefix address with the IP address of the Serving GW obtained by the PDN GW (ie, HA), and determines that the access network is the home network or the visited network.

 51912. The MME notifies the Serving GW to register with the PDN GW instead of the terminal.

 51913. Serving GW replaces the terminal to perform proxy mobile registration with the PDN GW, where the registration message format is the same as the message format specified in the IETF, but the terminal address (HoA) is all 0s, indicating that the PDN GW (ie: HA) is required to allocate the terminal. Home address (HoA); and the CoA address option is the IP address of the Serving GW.

 51914. The PDN GW (ie: HA) verifies the reliability of the message to the AAA server upon receiving the registration request message.

 51915. The PDN GW confirms the registration response message. According to the HoA all 0 in the message, the terminal needs to be assigned a home address; the PDN GW (ie: HA) first requests an IP address from the DHCP as the home address of the terminal, and then establishes a home address and a care-of address (the Serving GW reports it) Binding of its own IP address), and then returning a registration confirmation message to the Serving GW; the registration confirmation message ^ is consistent with the IETF specification, the home address is the assigned IP address, and the destination address of the message is the address of the Serving GW.

 51916. The Serving GW notifies the MME that the registration request has been completed. And reporting the home address (HoA) assigned to the terminal to the MME.

 51917. The MME provides the QoS configuration of the default bearer to the evolved RAN, such as the maximum rate limit for transmitting data. Whether this QoS configuration needs to be increased is not yet determined (for example: the need to send upstream or downstream data).

 51918. The MME accepts the network attachment of the terminal and assigns a temporary flag to the UE, together with the assigned home IP address to the terminal. In a roaming scenario, the roaming limit is checked and if it is violated the attachment will be rejected.

51919. The terminal responds with a confirmation message of a successful attachment. Example 20 The application example 20 is a process in which the terminal registers in the 3GPP visited network, where the MME, the Serving GW, and the PDN GW are separate entities; the HoA address of the terminal is stored in the HSS in a static form, and is carried in the registration message of the HSS in response to the MME. The address is given to the MME, and this embodiment includes a case where the LoA is allocated by the Serving GW.

 As shown in Figure 23, the terminal is in the 3GPP visited network MME, Serving GW, PDN GW full separation registration process, including:

 52001. The terminal discovers that the SAE/LTE access system subsequently initiates network selection and access.

 52002. The terminal initiates an attach request to the MME, including previously registered information (eg, temporary identification). If the terminal does not have previous registration information, its permanent identity is included.

 In the case of considering network sharing, the attach request message should include the selected network or the MME/Serving GW.

 The attach request may include information about the associated default IP bearer, such as a preferred IP address or APN.

 52003. If the previous registration information is reported by the terminal, the MME retrieves the user's information from the previous MME by sending the previous registration information.

 52004. The previous MME sends user information to the new MME (eg, the user's permanent identity).

52005. The user or terminal authenticates at the new MME.

 52006. The MME discovers the IP address of a Serving GW through a DNS query mode (but not limited to this method) according to the APN parameters included in the terminal attachment information.

 52007. The MME informs the Serving GW to assign an IP address to the user terminal, which is the LoA of the user. The way to obtain an address can be queried to the DHCP server, but it is not limited to this method. The Serving GW will assign the LoA address of a terminal to the MME.

 52008. The MME registers with the HSS as the serving MME of the terminal.

 52009. The information of the user or terminal on the old MME will be deleted or identified as unreachable.

 52010. The old MME notifies the old Serving GW to release information about the user plane.

52011. The HSS confirms the registration of the new MME. The subscription information of the authorized default IP access bearer is transmitted to the MME. The default bearer related policy and charging control information is also transmitted to the MME. In addition, the IP address of the PDN GW (ie: HA) corresponding to the user terminal will also be transmitted to the MME. The user's home address is The static form is stored in the HSS, and the HSS notifies the MME of the HoA address of the user when responding to the registration message.

 There is no strict order relationship between step S2010 and step S2011.

 There is no strict order relationship between step S2007 and steps S2008 to S2011.

 52012. After obtaining the IP of the PDN GW (ie: HA), the MME compares the network prefix address with the IP address of the Serving GW obtained by the MME, and determines that the access network is the visited network.

 52013. The MME notifies the Serving GW to register with the PDN GW instead of the terminal, and reports the HoA address of the user to the Serving GW.

 52014. Serving GW replaces the terminal to perform proxy mobile registration with the PDN GW, where the registration message format is the same as the message format specified in the IETF, the terminal address (HoA) is obtained from step 13, and the CoA address option is the IP address of the Serving GW. .

 52015. The PDN GW (ie: HA) verifies the reliability of the message to the AAA server after receiving the registration request message.

 52016. The PDN GW confirms the registration response message, and establishes a binding of the home address and the care-of address (its own IP address reported by the Serving GW), and then returns a registration confirmation message to the Serving GW; the registration confirmation message format and the IETF specification Consistent.

 52017. After receiving the registration response message from the PDN GW, the Serving GW establishes a home address of the terminal and a local address assignment for the terminal.

 52018. The Serving GW notifies the MME of the completion of the registration request.

 52019. The MME provides the QoS configuration of the default bearer to the evolved RAN, such as the maximum rate limit for transmitting data.

 52020. The MME accepts the network attachment of the terminal and assigns a temporary flag to the UE, together with the assigned home IP address and local IP address to the terminal. In a roaming scenario, the roaming limit is checked and if it is violated the attachment will be rejected.

52021. The terminal responds with a confirmation message of successful attachment. Example 21: Embodiment 21 is a process for a terminal to register in a 3GPP visited network, where the MME and the Serving GW PDN GW are separate entities; the HoA address of the terminal is stored in the HSS in a static form, and the address is carried in the registration message of the HSS in response to the MME. The MME does not include the case where the LoA is allocated by the Serving GW in this embodiment.

 As shown in Figure 24, the terminal is in the 3GPP visited network MME, Serving GW, PDN GW full separation registration process, including:

 52101. The terminal discovers that the SAE/LTE access system subsequently initiates network selection and access.

 52102. The terminal initiates an attach request to the MME, including previously registered information (eg, temporary identification). If the terminal does not have previous registration information, its permanent identity is included.

 In the case of considering network sharing, the attach request message should include the selected network or the MME/Serving GW.

 The attach request may include information about the associated default IP bearer, such as a preferred IP address or APN.

 52103. If the previous registration information is reported by the terminal, the MME will send the user's information to the previous MME by sending the previous registration information.

 52104. The previous MME sends user information to the new MME (eg, the user's permanent identity).

52105. The user or terminal authenticates at the new MME.

 52106. The MME discovers the IP address of a Serving GW through a DNS query mode (but not limited to this method) according to the APN parameters included in the terminal attachment information.

 52107. The MME registers with the HSS as the serving MME of the terminal.

 52108. The information of the user or terminal on the old MME will be deleted or identified as unreachable.

 52109. The old MME notifies the old Serving GW to release information about the user plane.

 52110. The HSS confirms the registration of the new MME. The subscription information of the authorized default IP access bearer is transmitted to the MME. The default bearer related policy and charging control information is also transmitted to the MME. In addition, the IP address of the PDN GW (ie: HA) corresponding to the user terminal will also be transmitted to the MME. The user's home address is stored in the HSS in a static form. When responding to the registration message, the HSS notifies the MME of the user's HoA address.

There is no strict order relationship between step S2109 and step S2110. 7

52111. The MME compares the network prefix address with the IP address of the Serving GW obtained by the PDN GW (ie, HA), and determines that the access network is the visited network.

 52112. The MME notifies the Serving GW to register with the PDN GW instead of the terminal, and reports the HoA address of the user to the Serving GW.

 52113. Serving GW replaces the terminal to perform proxy mobile registration with the PDN GW, where the registration message format is the same as the message format specified in the IETF, the terminal address (HoA) is obtained from step 12, and the CoA address option is the IP address of the Serving GW. .

 52114. The PDN GW (ie: HA) verifies the reliability of the message to the AAA server after receiving the registration request message.

 52115. The PDN GW confirms the registration response message, and establishes a binding of the home address and the care-of address (its own IP address reported by the Serving GW), and then returns a registration confirmation message to the Serving GW; the registration confirmation message format and the IETF specification Consistent.

 52116. The Serving GW notifies the MME that the registration request has been completed.

 52117. The MME provides the QoS configuration of the default bearer to the evolved RAN, such as the maximum rate limit for transmitting data.

 52118. The MME accepts the network attachment of the terminal and assigns a temporary identifier to the UE, together with the assigned home IP address to the terminal. In a roaming scenario, the roaming limit is checked and if it is violated the attachment will be rejected.

 52119. The terminal responds with a confirmation message of a successful attachment. Example 22

 Embodiment 22 is a process for a terminal to register in a 3GPP visited network, where the MME is an entity, the Serving GW, and the PDN GW are merged entities, and the new Serving GW/IASA, the previous Serving GW/IASA are located in the visited network; The IP address of the terminal is assigned by Serving GW/IASA; the terminal needs to be assigned a LoA address.

As shown in FIG. 25, the registration process of the terminal in the all-in-one architecture of the 3GPP network-1 includes: S2201: The terminal discovers that the SAE/LTE access system subsequently initiates network selection and access. 52202. The terminal initiates an attach request to the MME, including previously registered information (for example, a temporary identifier). If the terminal does not have previous registration information, its permanent identity is included. In the case of considering network sharing, the attach request message should include the selected network or MME. The attach request may include information about the associated default IP bearer, such as a preferred IP address or APN.

 52203. If the previous registration information is ^=艮 on the terminal, the MME retrieves the user's information from the previous MME by sending the previous registration information.

 52204. The previous MME sends the user information to the new MME (for example, the permanent identity of the user).

52205. The user or the terminal performs authentication on the new MME.

 52206. The MME finds a Serving GW/IASA IP address by using a DNS query manner according to the APN parameter included in the terminal attachment information.

 52207. The MME registers with the HSS as the serving MME of the terminal.

 52208. The information of the user or the terminal on the old MME is deleted or identified as unreachable.

 52209. The old MME notifies the old Serving GW/IASA to release information about the user plane.

52210. The HSS confirms the registration of the new MME. The subscription information of the authorized default IP access bearer is transmitted to the MME. The default bearer related policy and charging control information is also transmitted to the MME. In addition, the IP address of the HA corresponding to the user terminal will also be transmitted to the MME.

 52211. After obtaining the IP of the HA, the MME compares the network prefix address with its own IP address, and determines that the access network is a visited network.

 52212. The MME notifies the Serving GW/IASA to assign an IP address to the user terminal. The address is the local address of the user. The way to obtain an address can be queried to a DHCP server.

 The S2213 MME notifies the Serving GW/IASA to perform proxy mobile registration with the HA instead of the terminal.

52214. The Serving GW/IASA replaces the terminal to perform proxy mobile registration with the HA, wherein the registration message format is the same as the message format specified in the IETF. The registration message format is the same as the message format specified in the IETF, but the terminal address (HoA) is all 0s to indicate that the home address (HoA) of the HA distribution terminal is required; and the CoA address option is the address of the Serving GW/IASA.

 52215. After receiving the registration request message, the HA verifies the reliability of the message to the AAA server.

52216, HA confirms the registration response message. When the terminal is in the home network, HA receives the proxy After the IP registration message is sent, it responds to the Serving GW/IASA according to the normal registration response message specified in the IETF. The HA needs to allocate the home address to the terminal according to the HoA all 0 in the message; the HA first requests an IP address from the DHCP as the home address of the terminal, and then establishes a home address and a care-of address (the own IP address reported by the Serving GW/IASA). Binding, and then return a registration confirmation message to Serving GW/IASA; the registration confirmation message format is consistent with the IETF specification, the home address is the assigned IP address, and the destination address of the message is the address of Serving GW/IASA.

 52217. After receiving the registration response message of the HA, the Serving GW/IASA establishes a home address of the terminal and a local address binding assigned to the terminal.

 52218. The Serving GW/IASA notifies the MME of the completion of the registration request. And reported to the home address (HoA) assigned to the terminal.

 52219. The MME provides a default bearer QoS configuration to the evolved RAN, such as a maximum rate limit for transmitting data.

 52220. The MME accepts the network attachment of the terminal, and allocates a temporary identifier to the UE, and sends the assigned home IP address and local address (LoA) to the terminal. In a roaming scenario, the roaming limit is checked and if it is violated the attachment will be rejected.

 The S222 terminal responds with a confirmation message of successful attachment. Example 23

 Embodiment 23 is a process for a terminal to register in a 3GPP visited network, where the MME is an entity, the Serving GW and the PDN GW are merged entities, and the new Serving GW/IASA previous Serving GW/IASA are located in the visited network; The IP address is assigned by Serving GW/IASA; there is no need to assign a LoA address to the terminal.

 As shown in Figure 26, the registration process of the terminal in the all-in-one architecture of the 3GPP network includes:

52301. The terminal discovers that the SAE/LTE access system subsequently initiates network selection and access. If there is a network share, one of the shared networks will be selected.

52302. The terminal initiates an attach request to the MME, including previously registered information (for example: temporary identifier). If the terminal does not have previous registration information, its permanent identity is included. Consider network sharing In the case where the attach request message is to include the selected network or MME. The attach request may include information about the associated default IP bearer, such as a preferred IP address or APN.

 52303. If the previous registration information is reported by the terminal, the MME retrieves the user's information from the previous MME by sending the previous registration information.

 52304. The previous MME sends user information to the new MME (eg, the user's permanent identity).

52305. The user or terminal authenticates at the new MME.

 52306. The MME discovers the IP address of a Serving GW/IASA through a DNS query mode (but not limited to this method) according to the APN parameters included in the terminal attachment information.

 52307. The MME registers with the HSS as the serving MME of the terminal.

 52308. The information of the user or terminal on the old MME is deleted or identified as unreachable.

 52309. The old MME notifies the old Serving GW/IASA to release information about the user plane.

52310. The HSS confirms the registration of the new MME. The subscription information of the authorized default IP access bearer is transmitted to the MME. The default bearer related policy and charging control information is also transmitted to the MME. In addition, the IP address of the HA corresponding to the user terminal will also be transmitted to the MME.

 52311. After obtaining the IP of the HA, the MME compares the network prefix address with its own IP address, and determines that the access network is the visited network.

 52312. The MME notifies the Serving GW/IASA to perform proxy mobile registration with the HA instead of the terminal. S2313. Serving GW/IASA replaces the terminal with proxy mobile registration to HA, where the registration message format is the same as the message format specified in the IETF. The registration message format is the same as the message format specified in the IETF, but the terminal address (HoA) is all 0s to indicate that the home address (HoA) of the HA distribution terminal is required; and the CoA address option is the address of the Serving GW/IASA.

 52314. After receiving the registration request message, the HA verifies the reliability of the message to the AAA server.

52315. HA confirms the registration response message. When the terminal is in the home network, the HA responds to the Serving GW/IASA according to the normal registration response message specified in the IETF after receiving the proxy mobile IP registration message. The HA needs to allocate the home address to the terminal according to the HoA all 0 in the message; the HA first requests an IP address from the DHCP as the home address of the terminal, and then establishes a home address and a care-of address (the own IP address reported by the Serving GW/IASA). Binding, then to Serving GW/IASA returns a registration confirmation message; the format of the registration confirmation message is consistent with the IETF specification, the home address is the assigned IP address, and the destination address of the message is the address of Serving GW/IASA.

 S2316.Serving GW/IASA notifies M E to complete the registration request. And report the home address (HoA) assigned to the terminal.

 52317. The MME provides the QoS configuration of the default bearer to the evolved RAN, such as the maximum rate limit for transmitting data.

 52318. The MME accepts the network attachment of the terminal and assigns a temporary flag to the UE, together with the assigned home IP address to the terminal. In a roaming scenario, the roaming limit is checked and if it is violated the attachment will be rejected.

 52319. The terminal responds with a confirmation message of successful attachment. Example 24

 Embodiment 24 is a process of registering a terminal in a 3GPP home network, where the MME is an entity, the Serving GW and the PDN GW are merged entities, and the new Serving GW/IASA is located in the home network, and the previous Serving GW/IASA are located in the visit. In the network; the IP address of the terminal is assigned by Serving GW/IASA.

 As shown in Figure 27, the registration process of the terminal in the all-in-one architecture of the 3GPP network - 5 includes:

52401. The terminal discovers that the SAE/LTE access system subsequently initiates network selection and access. If there is a network share, one of the shared networks will be selected.

 52402. The terminal initiates an attach request to the MME, including previously registered information (eg, temporary identification). If the terminal does not have previous registration information, its permanent identity is included. In the case of network sharing, the attach request message shall include the selected network or MME. The attach request may include information about the default IP bearer, such as the preferred IP address or APN.

 52403. If the previous registration information is reported by the terminal, VIME will retrieve the user's information from the previous MME by sending the previous registration information.

 52404. The previous MME sends user information to the new MME (eg, the user's permanent identity).

52405. The user or terminal authenticates at the new MME. - S2406. The MME discovers the IP address of a Serving GW/IASA through a DNS query mode (but not limited to this method) according to the APN parameters included in the terminal attachment information.

 52407. The MME registers with the HSS as the serving MME of the terminal.

 52408. The information of the user or terminal on the old MME is deleted or identified as unreachable.

 52409. The old MME notifies the old Serving GW/IASA to release information about the user plane.

52410. The HSS confirms the registration of the new MME. The subscription information of the authorized default IP access bearer is transmitted to the MME. The default bearer related policy and charging control information is also transmitted to the MME. In addition, the IP address of the HA corresponding to the user terminal (that is, the current Serving GW/IASA) will also be transmitted to the MME.

 52411. After obtaining the IP of the HA, the MME compares the network prefix address with its own IP address, and determines that the access network is the home network.

 52412. The MME notifies the HA to replace the terminal to perform proxy mobile logout.

 52413. HA deletes all address bindings for this terminal.

 52414. The HA notifies the MME that the logout request has been completed.

 52415. The MME provides the QoS configuration of the default bearer to the evolved RAN, such as the maximum rate limit for transmitting data.

 52416. The MME accepts the network attachment of the terminal and assigns a temporary flag to the UE, together with the assigned home IP address to the terminal. In a roaming scenario, the roaming limit is checked and if it is violated the attachment will be rejected.

 52417. The terminal responds with a confirmation message of successful attachment. Example 25:

 Embodiment 25 is a process for a terminal to register in a 3GPP home network, and this is the first registration of the terminal, where the MME is an entity, the Serving GW and the PDN GW are merged entities; the IP address of the terminal is allocated by the Serving GW/IASA .

As shown in FIG. 28, the registration process of the terminal in the all-in-one architecture of the 3GPP network-6 includes: S2501. The terminal discovers that the SAE LTE access system subsequently initiates network selection and access. If there is a network share, one of the shared networks will be selected. 52502. The terminal initiates an attach request to the MME, including previously registered information (eg, temporary identifier). If the terminal does not have previous registration information, its permanent identity is included. In the case of considering network sharing, the attach request message should include the selected network or MME. The attach request may include information about the associated default IP bearer, such as a preferred IP address or APN.

 52503. The user or terminal authenticates at the new MME.

 52504. The MME discovers the IP address of a Serving GW/IASA through a DNS query mode (but not limited to this method) according to the APN parameters included in the terminal attachment information.

 52505. The MME registers with the HSS as the serving MME of the terminal.

 52506. The HSS confirms the registration of the new MME. The subscription information of the authorized default IP access bearer is transmitted to the MME. The default bearer related policy and charging control information is also transmitted to the MME. In addition, the IP address of the HA corresponding to the user terminal (that is, the current Serving GW IASA) will also be transmitted to the MME.

 52507. After obtaining the IP of the HA, the MME compares the network prefix address with its own IP address, and determines that the access network is the home network.

 52508. The MME informs the Serving GW/IASA to assign an IP address to the user terminal, which is the user's home address. The way to obtain an address can be queried to a DHCP server.

 52509. The MME provides the QoS configuration of the default bearer to the evolved RAN, such as the maximum rate limit for transmitting data.

 52510. The MME accepts the network attachment of the terminal and assigns a temporary identifier to the UE, together with the assigned home IP address to the terminal. In a roaming scenario, the roaming limit is checked and if it is violated the attachment will be rejected.

 52511. The terminal responds with a confirmation message of successful attachment. Example 26

 Embodiment 26 is a process for a terminal to register in a 3GPP visited network, and is a first registration, where the MME is an entity, the Serving GW, and the PDN GW are merged entities; the IP address of the terminal is allocated by the Serving GW/IASA; The terminal allocates a LoA address.

As shown in FIG. 29, the registration process of the terminal in the all-in-one architecture of the 3GPP network includes: 52601. The terminal discovers that the SAE/LTE access system subsequently initiates network selection and access. If there is a network share, one of the shared networks will be selected.

 52602. The terminal initiates an attach request to the MME, including previously registered information (eg, temporary identification). If the terminal does not have previous registration information, its permanent identity is included. In the case of network sharing, the attach request message shall include the selected network or MME. The attach request may include information about the default IP bearer, such as the preferred IP address or APN.

 52603. The user or terminal authenticates at the new MME.

 52604. The MME discovers the IP address of a Serving GW/IASA through a DNS query according to the APN parameters included in the terminal attachment information.

 52605. The MME registers with the HSS as the serving MME of the terminal.

 52606. The HSS confirms the registration of the new MME. The subscription information of the authorized default IP access bearer is transmitted to the MME. The default bearer related policy and charging control information is also transmitted to the MME. In addition, the IP address of the HA corresponding to the user terminal will also be transmitted to the MME. .

 52607. The MME compares the network prefix address with its own IP address after obtaining the IP of the HA, and determines that the access network is the visited network.

 52608. The MME informs the Serving GW/IASA to assign an IP address to the user terminal, which is the user's local address. The way to obtain an address can be queried to a DHCP server.

 52609. The MME notifies the Serving GW/IASA to perform proxy mobile registration with the HA instead of the terminal. The S2610.Serving GW/IASA replaces the terminal with the proxy mobile registration to the HA, where the registration message format is the same as the message format specified in the IETF. The registration message format is the same as the message format specified in the IETF, but the terminal address (HoA) is all 0s to indicate that the home address (HoA) of the HA distribution terminal is required; and the CoA address option is the address of the Serving GW/IASA.

 52611. After receiving the registration request message, the HA verifies the reliability of the message to the AAA server.

52612. The HA confirms the registration response message. When the terminal is in the home network, the HA responds to the Serving GW/IASA according to the normal registration response message specified in the IETF after receiving the proxy mobile IP registration message. The HA needs to assign the home address to the terminal according to the HoA all 0 in the message; the HA first requests an IP address from the DHCP as the home address of the terminal, and then establishes a home address and a handover address. Binding of the address (the own IP address reported by Serving GW/IASA), and then returning the registration confirmation message to Serving GW/IASA; the format of the registration confirmation message is consistent with the IETF specification, the home address is the assigned IP address, the message The destination address is the address of Serving GW/IASA.

 After receiving the registration response message of the HA, the S2613.Serving GW/IASA establishes a home address of the terminal and a local address binding assigned to the terminal.

 The S2614.Serving GW/IASA notifies the MME of the completion of the registration request. And report the home address (HoA) assigned to the terminal.

 52615. The MME provides the QoS configuration of the default bearer to the evolved RAN, such as the maximum rate limit for transmitting data.

 52616. The MME accepts the network attachment of the terminal and assigns a temporary identifier to the UE, together with the assigned home IP address and local address (LoA) to the terminal. In a roaming scenario, the roaming limit is checked and if it is violated the attachment will be rejected.

 52617. The terminal responds with a confirmation message of successful attachment. Example 27

 The embodiment 27 is a process for the terminal to register in the 3GPP visited network, and is the first registration, where the MME is an entity, the Serving GW and the PDN GW are merged entities; the IP address of the terminal is allocated by the Serving GW/IASA; Assign a LoA address to the terminal.

 As shown in Figure 30, the registration process of the terminal in the all-in-one architecture of the 3GPP network - 8, includes:

52701. The terminal discovers that the SAE/LTE access system subsequently initiates network selection and access. If there is a network share, one of the shared networks will be selected.

 52702. The terminal initiates an attach request to the MME, including previously registered information (eg, temporary identification). If the terminal does not have previous registration information, its permanent identity is included. In the case of network sharing, the attach request message shall include the selected network or MME. The attach request may include information about the default IP bearer, such as the preferred IP address or APN.

 52703. The user or terminal authenticates at the new MME.

52704. The MME queries the DNS according to the APN parameters included in the terminal attachment information. The way (but not limited to this way) to discover the IP address of a Serving GW/IASA.

 52705. The MME registers with the HSS as the serving MME of the terminal.

 52706. The HSS confirms the registration of the new MME. The subscription information of the authorized default IP access bearer is transmitted to the MME. The default bearer related policy and charging control information is also transmitted to the MME. In addition, the IP address of the HA corresponding to the user terminal will also be transmitted to the MME.

 52707. After obtaining the IP of the HA, the MME compares the network prefix address with its own IP address, and determines that the access network is the visited network.

 52708. The MME notifies the Serving GW/IASA to perform proxy mobile registration with the HA instead of the terminal. S2709.Serving GW/IASA replaces the terminal with proxy mobile registration to HA, where the registration message format is the same as the message format specified in the IETF. The registration message format is the same as the message format specified in the IETF, but the terminal address (HoA) is all 0s to indicate that the home address (HoA) of the HA distribution terminal is required; and the CoA address option is the address of the Serving GW/IASA.

 52710. After receiving the registration request message, the HA verifies the reliability of the message to the AAA server.

 52711. HA confirms the registration response message. When the terminal is in the home network, the HA responds to the Serving GW/IASA according to the normal registration response message specified in the IETF after receiving the proxy mobile IP registration message. The HA needs to allocate the home address to the terminal according to the HoA all 0 in the message; the HA first requests an IP address from the DHCP as the home address of the terminal, and then establishes a home address and a care-of address (the own IP address reported by the Serving GW/IASA). Binding, and then return a registration confirmation message to Serving GW/IASA; the registration confirmation message format is consistent with the IETF specification, the home address is the assigned IP address, and the destination address of the message is the address of Serving GW/IASA.

 S2712. Serving GW/IASA notifies the MME of the completion of the registration request. And report the home address (HoA) assigned to the terminal.

 52713. The MME provides the QoS configuration of the default bearer to the evolved RAN, such as the maximum rate limit for transmitting data.

52714. The MME accepts the network attachment of the terminal and assigns a temporary flag to the UE, together with the assigned home IP address to the terminal. In a roaming scenario, the roaming limit is checked and if it is violated the attachment will be rejected. S2715. The terminal responds with a successful attached confirmation message. Example 28:

 Embodiment 28 is a process in which a terminal registers in a 3GPP visited network, where the MME is an entity, the Serving GW, and the PDN GW are merged entities, and the new Serving GW/IASA and the previous Serving GW/IASA are all located in the visited network; The HoA address of the terminal is assigned by the HSS; the terminal needs to be assigned a LoA address.

 As shown in Figure 31, the registration process of the terminal in the all-in-one architecture of the 3GPP network includes:

52801. The terminal discovers that the SAE/LTE access system subsequently initiates network selection and access. If there is a network share, one of the shared networks will be selected.

 52802. The terminal initiates an attach request to the MME, including previously registered information (eg, temporary identification). If the terminal does not have previous registration information, its permanent identity is included. In the case of network sharing, the attach request message shall include the selected network or MME. The attach request may include information about the default IP bearer, such as the preferred IP address or APN.

 52803. If the previous registration information is reported by the terminal, the MME retrieves the user's information from the previous MME by sending the previous registration information.

 52804. The previous MME sends user information to the new MME (eg, the user's permanent identity).

52805. The user or terminal authenticates at the new MME.

 52806. The MME discovers the IP address of a Serving GW/IASA through a DNS query mode (but not limited to this method) according to the APN parameters included in the terminal attachment information.

 52807. The MME registers with the HSS as the service M E of the terminal, and simultaneously requests an IP address from the HSS as the HoA address of the terminal.

 52808. The information of the user or terminal on the old MME is deleted or identified as unreachable.

 52809. The old MME notifies the old Serving GW/IASA to release information about the user plane.

52810. The HSS confirms the registration of the new MME. The subscription information of the authorized default IP access bearer is transmitted to the MME. The default bearer related policy and charging control information is also transmitted to the MME. In addition, the IP address of the HA corresponding to the user terminal and the HoA address assigned by the HSS to the terminal are also transmitted to the MME. 52811. After obtaining the IP of the HA, the MME compares the network prefix address with its own IP address, and determines that the access network is a visited network.

 52812. The MME informs the Serving GW/IASA to assign an IP address to the user terminal, which is the user's local address. The way to obtain an address can be queried to a DHCP server.

 52813. The MME notifies the Serving GW/IASA to perform proxy mobile registration with the HA instead of the terminal.

52814. The proxy mobile registration is performed to the HA instead of the terminal, wherein the registration message format is the same as the message format specified in the IETF. The registration message format is the same as the message format specified in the IETF. The terminal address (HoA) is the address assigned by the HSS to the terminal in step 10; and the CoA address option is the address of the Serving GW/IASA.

 52815. After receiving the registration request message, the HA verifies the reliability of the message to the AAA server.

52816. HA confirms the registration response message. When the terminal is in the home network, after the HA receives the proxy mobile IP registration message, it establishes a binding between the home address and the care-of address (the own IP address reported by the Serving GW/IASA), according to the normal conditions specified in the IETF. Registration response message is sent to Serving GW/IASA ₀

 After receiving the registration response message of the HA, the S2817.Serving GW/IASA establishes a home address of the terminal and a local address binding assigned to the terminal.

 The S2818.Serving GW/IASA notifies the MME of the completion of the registration request. And report the home address (HoA) assigned to the terminal.

 52819. The MME provides the QoS configuration of the default bearer to the evolved RAN, such as the maximum rate limit for transmitting data.

 52820. The MME accepts the network attachment of the terminal, and allocates a temporary identifier to the UE, together with the assigned home IP address and local address (LoA) to the terminal. In a roaming scenario, the roaming limit is checked and if it is violated the attachment will be rejected.

 52821. The terminal responds with a confirmation message of successful attachment. Example 29

Embodiment 29 is a process for a terminal to register in a 3GPP visited network, where the MME is an entity, The Serving GW and the PDN GW are merged entities, and the new Serving GW/IASA and the previous Serving GW/IASA are all located in the visited network; the HoA address of the terminal is allocated by the HSS; there is no need to allocate a LoA address to the terminal.

 As shown in Figure 32, the registration process of the terminal in the all-in-one architecture of the 3GPP network includes:

52901. The terminal discovers that the SAE/LTE access system subsequently initiates network selection and access. If there is a network share, one of the shared networks will be selected.

 52902. The terminal initiates an attach request to the MME, including previously registered information (eg, temporary identification). If the terminal does not have previous registration information, its permanent identity is included. In the case of network sharing, the attach request message shall include the selected network or MME. The attach request may include information about the default IP bearer, such as the preferred IP address or APN.

 52903. If the previous registration information is reported by the terminal, the MME retrieves the user's information from the previous MME by sending the previous registration information.

 52904. The previous MME sends user information to the new MME (eg, the user's permanent identity).

52905. The user or terminal authenticates at the new MME.

 52906. The MME discovers a Serving GW/IASA IP address by means of DNS query (but not limited to this method) according to the APN parameters included in the terminal attachment information.

 52907. The MME registers with the HSS as the serving MME of the terminal, and requests an HS address from the HSS as the HoA address of the terminal.

 52908. The information of the user or terminal on the old MME will be deleted or identified as unreachable.

 52909. The old MME notifies the old Serving GW/I ASA to release information about the user plane.

 52910. The HSS confirms the registration of the new MME. The subscription information of the authorized default IP access bearer is transmitted to the MME. The default bearer related policy and charging control information is also transmitted to the MME. User end

52911. After obtaining the IP of the HA, the MME compares the network prefix address with its own IP address, and determines that the access network is the visited network.

 52912. The MME notifies the Serving GW/IASA to perform proxy mobile registration with the HA instead of the terminal.

52913. Proxy mobile registration with the terminal instead of the terminal, where the registration message format and the IETF rules The message format is the same. The registration message format is the same as the message format specified in the IETF. The terminal address (HoA) is the address assigned by the HSS to the terminal in step 10; and the CoA address option is the address of the Serving GW/IASA.

 52914. After receiving the registration request message, the HA verifies the reliability of the message to the AAA server.

 52915. HA confirms the registration response message. When the terminal is in the home network, after the HA receives the proxy mobile IP registration message, it establishes a binding between the home address and the care-of address (the own IP address reported by Serving GW/IASA), according to the normal conditions specified in the IETF. The registration response message is sent to Serving GW/IASA.

 S2916. Serving GW/IASA notifies the MME of the completion of the registration request. And report the home address (HoA) assigned to the terminal.

 52917. The MME provides the QoS configuration of the default bearer to the evolved RAN, such as the maximum rate limit for transmitting data.

 52918. The MME accepts the network attachment of the terminal and assigns a temporary flag to the UE, together with the assigned home IP address to the terminal. In a roaming scenario, the roaming limit is checked and if it is violated the attachment will be rejected.

 52919. The terminal responds with a confirmation message of a successful attachment. Example 30

 Embodiment 30 is a process in which a terminal registers in a 3GPP visited network, where the MME is an entity, the Serving GW, and the PDN GW are merged entities, and the new Serving GW/IASA is located in the visited network, and the previous Serving GW/IASA are located at the home. In the network; the HoA address of the terminal is allocated by the HSS; the terminal needs to be assigned a LoA address.

 As shown in Figure 33, the registration process of the terminal in the all-in-one architecture of the 3GPP network includes:

53001. The terminal discovers that the SAE/LTE access system subsequently initiates network selection and access. If there is a network share, one of the shared networks will be selected.

53002. The terminal initiates an attach request to the MME, including previously registered information (for example: temporary identifier). If the terminal does not have previous registration information, its permanent identity is included. Consider network sharing In the case where the attach request message is to include the selected network or MME. The attach request may include information about the associated default IP bearer, such as a preferred IP address or APN.

 53003. If the previous registration information is reported by the terminal, the MME retrieves the user's information from the previous MME by sending the previous registration information.

 53004. The previous MME sends user information to the new MME (for example: the user's permanent identity).

53005. The user or terminal authenticates at the new MME.

 53006. The MME discovers the IP address of a Serving GW/IASA through the DNS query mode (but not limited to this method) according to the APN parameters included in the terminal attachment information.

 53007. The MME registers with the HSS as the serving MME of the terminal, and requests an HS address from the HSS as the HoA address of the terminal.

 53008. The information of the user or terminal on the old MME will be deleted or identified as unreachable.

 53009. The old MME notifies the old Serving GW/IASA to release information about the user plane.

53010. The HSS confirms the registration of the new MME. The subscription information of the authorized default IP access bearer is transmitted to the MME. The default bearer related policy and charging control information is also transmitted to the MME. In addition, the IP address of the HA corresponding to the user terminal (that is, the previous Serving GW/IASA) and the HoA address assigned by the HSS to the terminal are also transmitted to the MME.

 After the IP address of the HA is obtained, the MME compares the network prefix address with its own IP address, and determines that the access network is the visited network.

 53012. The MME informs the Serving GW/IASA to assign an IP address to the user terminal, which is the user's local address. The way to obtain an address can be queried to a DHCP server.

 53013. The MME notifies the Serving GW/IASA to perform proxy mobile registration with the HA instead of the terminal.

53014. The proxy mobile registration is performed to the HA instead of the terminal, wherein the registration message format is the same as the message format specified in the IETF. The registration message format is the same as the message format specified in the IETF. The terminal address (HoA) is the address assigned by the HSS to the terminal in step 10; and the CoA address option is the address of the Serving GW/IASA.

 53015. After receiving the registration request message, the HA verifies the reliability of the message to the AAA server.

53016. HA acknowledges the registration response message. When the terminal is in the home network, HA receives the agent mobile After the IP registration message, a binding of the home address and the care-of address (the own IP address reported by the Serving GW/IASA) is established, and the Serving GW/IASAo is responded to according to the normal registration response message specified in the IETF.

 After receiving the registration response message of the HA, the S3017.Serving GW/IASA establishes a home address of the terminal and a local address binding assigned to the terminal.

 The S3018.Serving GW/IASA notifies the MME of the completion of the registration request. And the home address (HoA) assigned to the terminal.

 53019. The MME provides the QoS configuration of the default bearer to the evolved RAN, such as the maximum rate limit for transmitting data.

 53020. The MME accepts the network attachment of the terminal, and assigns a temporary identifier to the UE, together with the assigned home IP address and local address (LoA) to the terminal. In a roaming scenario, the roaming limit is checked and if it is violated the attachment will be rejected.

 53021. The terminal responds with a confirmation message of successful attachment. Example 31:

 Embodiment 31 is a process in which a terminal registers in a 3GPP visited network, where the MME is an entity, the Serving GW, and the PDN GW are merged entities, and the new Serving GW/IASA is located in the visited network, and the previous Serving GW/IASA are located at the home. In the network; the HoA address of the terminal is assigned by the HSS; there is no need to assign a LoA address to the terminal.

 As shown in Figure 34, the registration process of the terminal in the all-in-one architecture of the 3GPP network includes:

53101. The terminal discovers that the SAE/LTE access system subsequently initiates network selection and access. If there is a network share, one of the shared networks will be selected.

 53102. The terminal initiates an attach request to the MME, including previously registered information (eg, temporary identification). If the terminal does not have previous registration information, its permanent identity is included. In the case of network sharing, the attach request message shall include the selected network or MME. The attach request may include information about the default IP bearer, such as the preferred IP address or APN.

53103. If the previous registration information is reported by the terminal, the MME will send a previous registration letter. The information is retrieved from the previous MME.

 53104. The previous MME sends user information to the new MME (eg, the user's permanent identity).

53105. The user or terminal authenticates at the new MME.

 53106. The MME discovers the IP address of a Serving GW/IASA through a DNS query mode (but not limited to this method) according to the APN parameters included in the terminal attachment information.

 53107. The MME registers with the HSS as the serving MME of the terminal, and requests an HS address from the HSS as the Ho A address of the terminal.

 53108. The information of the user or terminal on the old MME is deleted or identified as unreachable.

 53109. The old MME notifies the old Serving GW/IASA to release information about the user plane.

53110. The HSS confirms the registration of the new MME. The subscription information of the authorized default IP access bearer is transmitted to the MME. The default bearer related policy and charging control information is also transmitted to the MME. In addition, the IP address of the HA corresponding to the user terminal (that is, the previous Serving GW/IASA) and the HoA address assigned by the HSS to the terminal are also transmitted to the MME.

 After the IP address of the HA is obtained, the MME compares the network prefix address with its own IP address, and determines that the 'access network is the visited network.

 53112. The MME notifies the Serving GW/IASA to perform proxy mobile registration with the HA instead of the terminal.

53113. The proxy mobile registration is performed to the HA instead of the terminal, wherein the registration message format is the same as the message format specified in the IETF. The registration message format is the same as the message format specified in the IETF. The terminal address (HoA) is the address assigned by the HSS to the terminal in step 10; and the CoA address option is the address of the Serving GW/IASA.

 53114. After receiving the registration request message, the HA verifies the reliability of the message to the AAA server.

 53115. HA confirms the registration response message. When the terminal is in the home network, after the HA receives the proxy mobile IP registration message, it establishes a binding between the home address and the care-of address (the own IP address reported by Serving GW/IASA), according to the normal conditions specified in the IETF. Registration response message is sent to Serving GW/IASAo

S3116. Serving GW/IASA notifies the MME to complete the registration request. And report the home address (HoA) assigned to the terminal. 53117. The MME provides the QoS configuration of the default bearer to the evolved RAN, such as the maximum rate limit for transmitting data.

 53118. The MME accepts the network attachment of the terminal and assigns a temporary flag to the UE, together with the assigned home IP address to the terminal. In a roaming scenario, the roaming limit is checked and if it is violated the attachment will be rejected.

 53119. The terminal responds with a confirmation message of successful attachment. Example 32:

 Embodiment 32 is a process for a terminal to register in a 3GPP home network, where the MME is an entity, the Serving GW and the PDN GW are merged entities, and the new Serving GW/IASA is located in the home network, and the previous Serving GW/IASA are located in the call. In the network; the HoA address of the terminal is allocated by the HSS.

 As shown in Figure 35, the registration process of the terminal in the all-in-one architecture of the 3GPP network includes:

53201. The terminal discovers that the SAE/LTE access system subsequently initiates network selection and access. If there is a network share, one of the shared networks will be selected.

 53202. The terminal initiates an attach request to the MME, including previously registered information (eg, temporary identification). If the terminal does not have previous registration information, its permanent identity is included. In the case of network sharing, the attach request message shall include the selected network or MME. The attach request may include information about the default IP bearer, such as the preferred IP address or APN.

 53203. If the previous registration information is reported by the terminal, the MME retrieves the user's information from the previous MME by sending the previous registration information.

 53204. The previous MME sends user information to the new MME (eg, the user's permanent identity).

53205. The user or terminal authenticates at the new MME.

 The MME discovers the IP address of a Serving GW/IASA through a DNS query according to the APN parameters included in the terminal attachment information.

 53207. The MME registers with the HSS as the serving MME of the terminal, and requests an HS address from the HSS as the HoA address of the terminal.

53208. The information of the user or terminal on the old MME is deleted or identified as unreachable. 53209. The old MME notifies the old Serving GW/IASA to release information about the user plane.

 53210. The HSS confirms the registration of the new MME. The subscription information of the authorized default IP access bearer is transmitted to the MME. The default bearer-related policy and charging control information is also transmitted to Mj^. In addition, the IP address of the HA corresponding to the user terminal (that is, the current Serving GW/IASA) and the HoA address assigned by the HSS to the terminal are also transmitted to the MME.

 After the IP address of the HA is obtained, the MME compares the network prefix address with its own IP address, and determines that the access network is the home network.

 53212. The MME notifies the HA to perform a proxy mobile logout to the HA instead of the terminal.

 53213. HA deletes all address bindings for this terminal.

 53214. The HA notifies the MME of the completion of the registration request.

 The MME provides the evolved RAN with a default bearer QoS configuration, such as a maximum rate limit for transmitting data.

 53216. The MME accepts the network attachment of the terminal and assigns a temporary flag to the UE, together with the assigned home IP address to the terminal. In a roaming scenario, the roaming limit is checked and if it is violated the attachment will be rejected.

 53217. The terminal responds with a confirmation message of a successful attachment. Example 33:

 Embodiment 33 is a procedure for a terminal to register in a 3GPP home network, and this is the first registration of the terminal, where the MME is an entity, the Serving GW and the PDN GW are merged entities; the HoA address of the terminal is allocated by the HSS.

 As shown in Figure 36, the registration process of the terminal in the all-in-one architecture of the 3GPP network - 14, includes:

53301. The terminal discovers that the SAE/LTE access system subsequently initiates network selection and access. If there is a network share, one of the shared networks will be selected.

53302. The terminal initiates an attach request to the MME, including previously registered information (for example: temporary identifier). If the terminal does not have previous registration information, its permanent identity is included. In the case of network sharing, the attach request message should include the selected network or ME. Attachment requests may include Information about the default IP bearer, such as the preferred IP address or APN.

 53303. The user or terminal authenticates at the new MME.

 53304. The MME discovers the IP address of a Serving GW/IASA through a DNS query mode (but not limited to this method) according to the APN parameters included in the terminal attachment information.

 53305. The MME registers with the HSS as the serving MME of the terminal, and requests an HS address from the HSS as the HoA address of the terminal.

 53306. The HSS confirms the registration of the new MME. The subscription information of the authorized default IP access bearer is transmitted to the MME. The default bearer related policy and charging control information is also transmitted to the MME. In addition, the IP address of the HA corresponding to the user terminal (that is, the current Serving GW/IASA) and the HoA address assigned by the HSS to the terminal are also transmitted to the MME.

 The MME compares the network prefix address with its own IP address according to the IP of the HA, and determines that the access network is the home network.

 53308. The MME informs the Serving GW/IASA to assign an IP address to the user terminal, which is the user's home address. The way to obtain an address can be queried to a DHCP server.

 53309. The MME provides the QoS configuration of the default bearer to the evolved RAN, such as the maximum rate limit for transmitting data.

 53310. The MME accepts the network attachment of the terminal and assigns a temporary identifier to the UE, together with the assigned home IP address to the terminal. In a roaming scenario, the roaming limit is checked and if it is violated the attachment will be rejected.

 53311. The terminal responds with a confirmation message of a successful attachment. Example 34

 The embodiment 34 is a process for the terminal to register in the 3GPP visited network, and is the first registration, where the MME is an entity, the Serving GW and the PDN GW are merged entities; the HoA address of the terminal is allocated by the HSS; address.

As shown in FIG. 37, the registration process of the terminal in the all-in-one architecture of the 3GPP network includes: S3401. The terminal discovers that the SAE/LTE access system subsequently initiates network selection and access. if it exists For network sharing, a shared network will be selected.

 53402. The terminal initiates an attach request to the MME, including previously registered information (eg, temporary identification). If the terminal does not have previous registration information, its permanent identity is included. In the case of network sharing, the attach request message shall include the selected network or MME. The attach request may include information about the default IP bearer, such as the preferred IP address or APN.

 53403. The user or terminal authenticates at the new MME.

 53404. The MME finds a Serving GW/IASA IP address through DNS query according to the APN parameters included in the terminal attachment information.

 53405. The MME registers with the HSS as the serving MME of the terminal, and requests an HS address from the HSS as the HoA address of the terminal.

 53406. The HSS confirms the registration of the new MME. The subscription information of the authorized default IP access bearer is transmitted to the MME. The default bearer related policy and charging control information is also transmitted to the MME. In addition, the IP address of the HA corresponding to the user terminal and the HoA address assigned by the HSS to the terminal are also transmitted to the MME.

 After the MME obtains the IP address of the HA and compares the network prefix address with its own IP address, the MME determines that the access network is the visited network.

 53408. The MME informs the Serving GW/IASA to assign an IP address to the user terminal, which is the user's local address. The way to obtain an address can be queried to a DHCP server.

 53409. The MME notifies the Serving GW/IASA to perform proxy mobile registration with the HA instead of the terminal.

53410. The proxy mobile registration is performed to the HA instead of the terminal, wherein the registration message format is the same as the message format specified in the IETF. The registration message format is the same as the message format specified in the IETF. The terminal address (HoA) is the address assigned by the HSS to the terminal in step 10; and the CoA address option is the address of the Serving GW/IASA.

 After receiving the registration request message, S3411.HA verifies the reliability of the message to the AAA server.

S3412.HA confirms the registration response message. When the terminal is in the home network, after the HA receives the proxy mobile IP registration message, it establishes a binding between the home address and the care-of address (the own IP address reported by Serving GW/IASA), according to the normal conditions specified in the IETF. Registration response message is sent to Serving GW/IASAo After receiving the registration response message of the HA, the S3413.Serving GW/IASA establishes a home address of the terminal and a local address binding assigned to the terminal.

 S3414. Serving GW/IASA notifies the MME of the completion of the registration request. It is reported as the home address (HoA) assigned to the terminal.

 53415. The MME provides the QoS configuration of the default bearer to the evolved RAN, such as the maximum rate limit for transmitting data.

 53416. The MME accepts the network attachment of the terminal and assigns a temporary flag to the UE, together with the assigned home IP address and local address (LoA) to the terminal. In the roaming scenario, the roaming limit will be checked, and if it is violated, the attachment will be rejected.

 53417. The terminal responds with a confirmation message of successful attachment. As shown in FIG. 38, it is a system for registering a network side instead of a terminal according to the present invention. As can be seen from the figure, the system includes:

 The attach request initiation unit 101 may be located at the terminal 100 or may be located in another network element, and configured to initiate an attach request to the network side by using the first access network, where the attach request carries the terminal registration information; and the registration unit is located in the network. The side is configured to perform a registration operation instead of the terminal according to the location area where the first access network is located.

 The network side includes an MME/Serving GW 200 that performs mobility management on the terminal, a PDN GW 300, and an HSS 400 that manages user subscription data. The system further includes:

 a service MME/Serving GW registration unit 201, located in the MME/Serving GW, configured to register with the HSS as a monthly MME/Serving GW of the terminal;

 The access network location area determining unit 202 is located at the MME/Serving GW, and is configured to determine a location area where the first access network is located;

 The terminal registration operation unit 203 is located at the MME/Serving GW, and is configured to perform a terminal registration operation according to the location area where the first access network is located.

The PDN GW information acquiring unit 205 is located at the MME/Serving GW, and is configured to learn PDN GW information corresponding to the terminal. The first access network location area determining unit 202 determines the location area where the first access network is located according to the PDN GW information corresponding to the terminal.

 The terminal registration processing unit 203 is configured to select a terminal to register with the PDN GW according to the location area where the first access network is located, and return the registration result to the terminal.

 The system further includes:

 The first IP address allocating unit 206 is located at the MME/Serving GW, and is configured to allocate a first IP address to the terminal.

 The proxy mobile IP registration unit 2031 is located in the terminal registration operation unit, and is used to perform proxy mobile IP registration with the PDN GW instead of the terminal.

 The system further includes:

 The second IP address allocating unit 301 is located at the PDN GW and is used to allocate a home address for the terminal.

 The terminal home address saving unit 401 is located in the home subscriber server and is used to store the terminal home address.

 The system further includes:

 The deregistration unit 207 is located at the MME/Serving GW and is used to perform a deregistration operation instead of the terminal.

 The MME and the Serving GW may be configured as one physical entity or may be separately configured. The MME, the Serving GW, and the PDN GW may be configured as one physical entity, or may be separately configured.

 The MME may be configured as one physical entity, and the Serving GW and the PDN GW may be configured as one physical entity.

 As shown in FIG. 39, a terminal registration system according to an embodiment of the present invention includes:

 The attach request initiation unit 102 may be located at the terminal 100 or may be located in another network element, and configured to initiate an attach request to the network side by using the first access network, where the attach request carries the terminal registration information.

The network side includes an MME/Serving GW 200 that performs mobility management on the terminal, a PDN GW 300, and an HSS 400 that manages user subscription data. The system further includes: W

 The PDN GW information acquiring unit 208 is located at the MME/Serving GW 200, and is configured to acquire PDN GW information corresponding to the terminal from the HSS;

 The user plane bearer establishing unit 209 is configured to select a corresponding PDN GW according to the PDN GW information corresponding to the terminal, and establish an associated user plane bearer. The spirit and scope of the invention. Thus, it is intended that the present invention cover the modifications and variations of the inventions

Claims

Rights request A method for a network side to replace a terminal registration, comprising:  The network side receiving terminal attaches an attachment request initiated by the first access network, and the attach request carries the terminal registration information;  The network side performs a registration operation instead of the terminal according to the location area where the first access network is located. The method of claim 1, wherein the network side performs the registration operation step in place of the terminal according to the location area of the first access network, and further includes:  The network side determines a location area where the first access network is located;  The network side performs a terminal registration operation according to the location area where the first access network is located.  The method of claim 2, wherein the network side comprises a packet data gateway PDN GW, and the network side performs a registration operation step instead of the terminal according to the location area where the first access network is located, Further includes:  The network side knows the PDN GW information corresponding to the terminal;  The network side determines, according to the PDN GW information corresponding to the terminal, the location area where the first access network is located;  The network side selects the terminal to register with the PDN GW according to the location area where the first access network is located, and performs a registration operation instead of the terminal.  The method according to claim 3, wherein the network side acquires PDN GW information from the home subscriber server HSS.  5. The method according to claim 3, wherein the network side comprises a mobility management entity/user data plane entity MME/Serving GW,  The PDN GW information corresponding to the terminal is an IP address of the PDN GW corresponding to the terminal; the network side determines, according to the PDN GW information corresponding to the terminal, the location area of the first access network, by comparing The IP address of the MME/Serving GW is determined by the network prefix of the IP address of the PDN GW corresponding to the terminal, and the first access network is determined to be the home network or the visited network. 6. The method of claim 2, wherein the network side comprises mobility management The entity/user data plane entity MME/Serving GW, the step of determining, by the network side, the location area of the first access network, further includes:  The MME/Serving GW allocates a first IP address to the terminal;  The MME/Serving GW determines whether the first access network is located or the visited network by comparing the first IP address with the network prefix of the IP address of the PDN GW corresponding to the terminal.  7. The method of claim 5 or 6, wherein  The first access network is a home network, and the network side performs a terminal registration operation according to the location area where the first access network is located, and the MME/Serving GW replaces the terminal to perform proxy movement to the PDN GW. IP registration.  8. The method of claim 5 or 6, wherein  The first access network is a visited network, and the network side performs a terminal registration operation according to the location area where the first access network is located, and the MME/Serving GW replaces the terminal to perform proxy movement to the PDN GW. IP registration.  The method according to claim 8, wherein the MME/Serving GW replaces the terminal to perform proxy mobile IP registration with the PDN GW, and the PDN GW allocates a home address to the terminal, and the care-of address is MME/ Serving GW's IP address.  10. The method according to claim 9, wherein the PDN GW is a home address assigned by the terminal, and is obtained by requesting a dynamic host configuration protocol server.  The method according to claim 8, wherein the terminal home address is stored in a home subscriber server, and the MME/Serving GW acquires the terminal as a serving MME/Serving GW of the terminal when the MME/Serving GW registers with the home subscriber server Home address.  The method according to claim 10 or 11, wherein the network side performs the terminal registration operation step according to the location area where the first access network is located, and further includes the home address of the terminal established by the PDN GW. Binding relationship with the care-of address, and returning a registration confirmation message to the MME/Serving GW. 13. The method according to claim 12, wherein the mesh side is according to the first The MME/Serving GW establishes a binding relationship between the home address and the local address of the terminal according to the registration confirmation message.  The method according to claim 12 or 13, wherein the network side performs the terminal registration operation step according to the location area where the first access network is located, and further includes the MME/Serving GW assigning the terminal A temporary sign, and return the temporary sign and home address to the terminal.  15. The method of claim 2, wherein  The MME/Serving GW may be located in the home network or in the visited network. The method according to claim 2, wherein the MME/Serving GW is located in a home network, the original MME/Serving GW of the terminal is located in a visited network, and the network side is configured according to the first access network. In the location area, in the terminal registration operation step, the MME/Serving GW performs a deregistration operation instead of the terminal.  The method of claim 2, wherein the MME, the Serving GW, and the PDN GW may be configured as one physical entity, or may be configured as different physical entities in any combination.  18. A network side replacement terminal registration system, comprising:  An attach request initiating unit, configured to initiate an attach request to the network side by using the first access network, where the attach request carries the terminal registration information;  The registration unit is located at the network side, and is configured to perform a registration operation instead of the terminal according to the location area where the first access network is located.  The system of claim 18, wherein the network side comprises an MME/Serving GW that performs mobility management on the terminal, and an HSS that manages user subscription data, the system further comprising:  a service MME/Serving GW registration unit, located at the MME/Serving GW, for registering with the HSS as a service MME/Serving GW of the terminal;  a first access network location area determining unit, located in the MME/Serving GW, configured to determine a location area where the first access network is located; The terminal registration operation unit is located at the VIME/Serving GW, and is configured to perform a terminal registration operation according to the location area where the first access network is located. 20. The system of claim 19, wherein:  The network side further includes a PDN GW that provides management for the terminal;  The system also includes:  a PDN GW information acquiring unit, located at the MME/Serving GW, for obtaining PDN GW information corresponding to the terminal;  The first access network location area determining unit determines, according to the PDN GW information corresponding to the terminal, a location area where the first access network is located;  The terminal registration operation unit is configured to select a terminal to register with the PDN GW according to the location area where the first access network is located, and return the registration result to the terminal.  21. The system of claim 20, further comprising:  The first IP address allocation unit is located at the MME/Serving GW, and is configured to allocate a first IP address to the terminal.  11. The system of claim 21, further comprising:  A proxy mobile IP registration unit, located in the terminal registration unit, is used to replace the terminal to the PDN The GW performs proxy mobile IP registration.  The system of claim 20, further comprising:  a second IP address allocation unit, located at the PDN GW, for a home address assigned to the terminal.  24. The system of claim 19, further comprising:  The terminal home address saving unit is located in the home subscriber server and is used to store the terminal home address.  The system of claim 19, further comprising:  The deregistration unit is located at the MME/Serving GW and is used to perform a deregistration operation instead of the terminal. The system of claim 19, wherein the MME, the Serving GW, and the PDN GW may be configured as one physical entity, or may be configured as different physical entities in any combination. 27. A method for registering a terminal, comprising:  The network side receives an attach request initiated by the terminal through the access network, where the attach request carries the terminal registration information;  The network side obtains the PDN GW information corresponding to the terminal from the HSS.  The network side selects a corresponding PDN GW according to the PDN GW information, and establishes a related user plane bearer.  The method according to claim 27, wherein the PDN GW information corresponding to the terminal acquired from the HSS may be an IP address of the PDG-GW, or an APN, or other indication parameter.  29. A terminal registration system, comprising:  An attach request initiating unit, configured to initiate an attach request to the network side by using the first access network, where the attach request carries the terminal registration information;  The PDN GW information acquiring unit is configured to obtain the PDN GW information corresponding to the terminal from the HSS, and the user plane bearer establishing unit is configured to select a corresponding PDN GW according to the PDN GW information corresponding to the terminal, and establish a related user plane bearer.