WO2007128232A1

WO2007128232A1 - Terminal registraion method and system in evolution networks

Info

Publication number: WO2007128232A1
Application number: PCT/CN2007/001460
Authority: WO
Inventors: Lan Liu; Ming Li; Peng Zhang
Original assignee: Huawei Technologies Co., Ltd.
Priority date: 2006-04-30
Filing date: 2007-04-29
Publication date: 2007-11-15
Also published as: CN1984162A; CN100589502C

Abstract

A terminal registration method and system in evolution networks are provided. The method comprises steps of: non-3GPP access gateway receives registration request from terminal and then registers the terminal at Inter AS Anchor instead of the terminal by using proxy mobile IP; the Inter AS Anchor does registration for the terminal, determines its home address, and sends registration acknowledgement message to non-3GPP access gateway; the non-3GPP access gateway sends response message to the terminal to inform the home address. This method provides successful registration at Inter AS Anchor in evolution network frame for terminal by use of proxy mobile IP mechanism and then access 3GPP services through evolution core networks.

Description

Method and system for registering terminal in non-3GPP access system in evolved network

The embodiments of the present invention relate to the field of communications, and in particular, to a method and system for registering a terminal in a non-3GPP access system in an evolved network. 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 evolution of the network structure is also an important indicator for the backward compatibility of existing networks.

Several principles that an evolved network architecture needs to satisfy are as follows:

1. During 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 business 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 side of the wireless evolution network mainly includes a mobility management entity (MME, Mobility Management Entity), and a user data plane entity (UPE, User Plane). Entity), Inter AS Anchor (Inter Access Systems Anchor) three logical function modules, wherein the MME is a mobility management module, responsible for the mobility management of the control plane, including user context and mobile state management. Assigning a user temporary identity, security function, etc., which corresponds to the control plane part of the current UMTS system internal service GPRS support node (SGSN, serving GPRS Support Node); UPE is a user plane entity, responsible for initiating paging for downlink data in idle state , management saves IP bearer parameters and intra-network routing letters Information, etc., which corresponds to the data plane part of the current UMTS system internal SGSN and Gateway GPRS Support Node (GGSN); Inter AS Anchor acts as a user plane anchor between different access systems. The interface between Inter AS Anchor and the non-3GPP access system is S2 in Figure 1.

The basic mobile IP registration process is defined in the IETF specification. As shown in Figure 2, it is a working flow diagram of mobile IPv4. As can be seen from Figure 2, it mainly includes the following steps:

The S20 mobile terminal (MN, Mobile Node) establishes a connection with a gateway (GW, Gateway), such as: an ASGW or a PDG Packet Data Gateway;

5202. The GW mobile agent's foreign agent (FA, Foreign Agent) sends a FA broadcast message, including the address of the FA, to be used as the MN's Care-of Address (CoA, Care-of Address);

5203. After receiving the broadcast message, the MN determines that it leaves the home network to enter a visited network. Then uploading a mobile IPv4 registration request R Q, including CoA;

5204. In order to authenticate the user, the FA exchanges information with the AAA server of the user home network, and the home AAA server provides a home agent (HA, Home Agent) and its IP address to the FA;

S205, the FA forwards the registration request of the user to the HA, the RRQ;

S206. The HA queries the AAA server for the MN-HA pre-set key.

This step only occurs after the first registration, and then the MN does not need to make a key request when connecting to other FAs.

S207 - S208, the HA accepts the registration of the MN, generates a binding of the MN's home IP address and the CoA address, and returns a registration response of the mobile IPv4.

The mobile IPv6 registration process is basically the same as the above solution, except that the GW no longer assumes the function of the FA but transparently transmits all the data packets. Therefore, it will not be repeated here.

The mobile IP mechanism in the IETF specification cannot be directly applied to the current evolved network, and the terminal directly registers, and the HA and the FA need to periodically broadcast broadcast messages of their own information to the terminal. The consumption of the air interface of the entire radio access network is enormous. Summary of the invention

An embodiment of the present invention provides a method and system for registering a terminal in a non-3GPP access system in an evolved network, which is used to solve the direct registration process of the terminal in the prior art, and requires the HA and the FA to periodically broadcast a broadcast message of its own information to the terminal. The problem of huge consumption of air interface resources of the entire radio access network is caused.

The method for registering a terminal in an evolved network includes:

The non-3GPP access gateway receiving terminal sends a registration request;

The non-3GPP access gateway replaces the terminal to perform proxy mobile IP registration with the anchor point between the access systems; the anchor point between the access systems registers with the terminal, determines the terminal home address and goes to the non-

The 3GPP access gateway sends a registration confirmation message;

The non-3GPP access gateway sends a response message to the terminal to inform the home address.

An embodiment of the present invention provides an anchor point in an evolved network in which a non-3GPP access system registration system includes a non-3GPP access gateway that provides access for a terminal, and an access system that registers the terminal mobility, and includes:

a proxy mobile IP registration unit, located in the non-3GPP access gateway, configured to perform proxy mobile IP registration for accessing the intersystem anchor point to the terminal;

a registration response unit, located in the non-3GPP access gateway, configured to send a response message to the terminal to notify the home address;

The terminal registration unit is located at an anchor point between the access systems, and is configured to perform mobile IP registration for the terminal, and determine a terminal home address.

The embodiment of the invention enables the terminal to successfully register to the Inter AS Anchor through the proxy mobile IP mechanism under the evolved network architecture, and access the 3GPP service through the evolved core network. Compared with the basic mobile IP mechanism, the scheme greatly reduces the consumption of air interface signaling, thereby saving resources of air interfaces. DRAWINGS

1 is a schematic diagram of a wireless evolution network architecture in the prior art;

2 is a schematic diagram of a mobile IPv4 workflow in the prior art;

3 is a schematic flowchart of Embodiment 1 of the present invention;

4 is a schematic flowchart of Embodiment 2 of the present invention;

Figure 5 is a schematic flowchart of Embodiment 3 of the present invention;

6 is a schematic flowchart of Embodiment 4 of the present invention;

FIG. 7 is a schematic structural diagram of a system according to Embodiment 5 of the present invention. detailed description

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

Example 1:

As shown in FIG. 3, it is a schematic flowchart of Embodiment 1 of the present invention. As can be seen from the figure, the following steps are mainly included:

The S30K terminal sends a request to the non-3GPP access gateway.

After the terminal is successfully connected to the non-3GPP access system through access authentication, the terminal initiates an end-to-end tunnel establishment request to the non-3GPP access gateway. The request may also be a request to register with a non-3GPP access gateway; the request carries information for verifying the terminal.

S302> The non-3GPP access gateway performs proxy mobile IP registration for the terminal to the Inter AS Anchor.

In the solution of the present invention, the non-3GPP access gateway is used to perform mobile IP registration of the terminal to the Inter AS Anchor.

In this step, the non-3GPP access gateway may also be included to authenticate the terminal to the AAA server. In this step, the non-3GPP access gateway may obtain the IP address information of the Inter AS Anchor corresponding to the terminal from the AAA server, which may include:

The AAA server registers with the Home Subscriber Server (HSS); The HSS returns a registration confirmation message to the AAA server and informs the terminal of the IP address of the Inter AS Anchor.

In this step, the non-3GPP access gateway performs network prefix comparison with the IP address of the Inter AS Anchor according to the IP address of the Inter AS Anchor, and determines whether the non-3GPP access network is a local network or a visited network according to the comparison result. A step of. If the non-3GPP access network is a visited network, the non-3GPP access gateway assigns the first IP address to the terminal as a care-of address. And if the non-3GPP access network is a home network, it may not be allocated.

5303. The Inter AS Anchor registers with the terminal, determines the terminal HoA, and sends a registration acknowledgement message to the non-3GPP access gateway.

In the above step, the non-3GPP access gateway sends a proxy mobile IP registration message to the InterAS Anchor, carrying whether the Inter AS Anchor is required to allocate HoA information to the terminal, and the information may be set in the proxy mobile IP registration message. The HoA field is carried.

In this step, if the Inter AS Anchor is required to allocate a HoA to the terminal, the Inter AS Anchor obtains the second address from the DHCP server as the terminal's ΗοΑ.

In this step, if the non-3GPP access gateway is a visited network, the CoA confirmed by the Inter AS Anchor for the terminal may be the first IP address previously allocated, and if there is no previous allocation, the non-3GPP access gateway address is used as the CoA.

In this step, the step of verifying the reliability of the proxy mobile IP registration message by the Inter AS Anchor to the AAA server may also be included.

S304: The non-3GPP access gateway sends a response message to the terminal to notify the HoA.

The non-3GPP access gateway returns a response message to the terminal, and returns the assigned HoA to the terminal. If the non-3GPP access network is a visited network, the assigned CoAs are also sent to the terminal together.

The solution of Embodiment 1 of the present invention is based on the current evolved network architecture, and the registration mechanism of the MP is improved. In addition, the gateway of the non-3GPP system access network is used instead of the terminal to perform mobile IP registration.

Example 2:

As shown in FIG. 4, it is a schematic flowchart of Embodiment 2 of the present invention, which can be seen from the figure, mainly including Next steps:

5401. The terminal is successfully connected to the non-3GPP access system through access authentication.

5402. The terminal sends an end-to-end tunnel establishment request to the non-3GPP access gateway, where the information carries information used to verify the terminal.

S403 The non-3GPP gateway sends a request message for verifying the terminal to the AAA server. The <3⁄4' .-vT v *)i 曰 7, m H- TTH P rt

5404. The AAA server registers with the HSS.

Through the registration, the HSS can know which AAA server the terminal is currently in. The registration message can be utilized but is not limited to the Diameter protocol specified in the IETF.

5405. The HSS returns a registration confirmation message to the AAA server.

The HSS returns a registration confirmation message, and tells the AAA server the IP address information of the Inter AS Anchor (ie, HA) corresponding to the terminal to complete the registration process of the mobile IP.

The registration confirmation message can be utilized but is not limited to the Diameter protocol specified in the IETF.

In the solution of Embodiment 2, the AAA server and the HSS may exist in the same entity, so that the registration process can be completed internally, that is, steps S403 and S404 do not exist in this case, and are internal messages.

5406. The AAA server returns a verification response to the non-3GPP access gateway.

In the verification response, the IP address of the Inter AS Anchor (ie: HA) corresponding to the terminal is carried. The non-3GPP access gateway obtains the IP address of the Inter AS Anchor (ie: HA) corresponding to the terminal and compares the network prefix address with its own IP address. If the judgment result is different in the two steps, the non-3GPP access is obtained. The net is for visiting the network.

5407. The non-3GPP access gateway allocates an IP address to the terminal.

The non-3GPP access gateway assigns an IP address to the terminal, which is the CoA of the terminal.

5408. The non-3GPP access gateway replaces the terminal to perform proxy mobile IP registration to the Inter AS Anchor.

The registration message format is the same as the message format specified in the IETF, but the HoA is all 0s, Indicates that the Inter AS is required to allocate the HoA of the terminal; in this embodiment, the terminal is visiting the network, and the CoA address option is the address of the non-3GPP access gateway.

5409. After receiving the registration request message, the Inter AS Anchor verifies the reliability of the message to the AAA server.

5410. Inter AS Anchor performs mobile IP registration for the terminal and returns a mobile IP registration response.

After the Inter AS Anchor receives the proxy mobile IP registration message, it needs to assign the home address to the terminal according to the HoA all 0 in the message.

The Inter AS Anchor first requests an IP address from the DHCP as the HoA of the terminal. Since the CoA is not 0, a binding between the HoA and the CoA is established, and then a registration confirmation message is returned to the non-3GPP access gateway.

5411. The non-3GPP access gateway returns a response to the end-to-end tunnel of the terminal, and returns the allocated HoA and HoA to the terminal.

Example 3:

Embodiment 3 is a process in which a terminal registers in an IWLAN visited network, where the AAA server and the HSS are separate entities, as shown in FIG. 5, including the following steps:

S501. The terminal is successfully connected to the IWLA access network through access authentication.

5502. The terminal sends an end-to-end tunnel establishment request to a Packet Data Gateway (PDG), where the request carries information for verifying the terminal.

5503. The PDG sends a request for verifying the terminal to the AAA server.

5504. The AAA server registers with the HSS.

5505. The HSS returns a registration confirmation message to the AAA server, and tells the AAA server the IP address information of the Inter AS Anchor corresponding to the terminal to complete the registration process of the mobile IP.

5506. The AAA server returns a verification response to the PDG, and returns an IP address of the Inter AS Anchor corresponding to the terminal.

The PDG obtains the IP address of the Inter AS Anchor corresponding to the terminal and performs its own IP address. For comparison of the network prefix addresses, in this embodiment, if the determination result is different, the IWLAN access network is a visited network.

5507. The PDG allocates an IP address to the terminal, which is the local IP address (HoA) of the terminal.

5508. The PDG replaces the terminal to perform proxy mobile IP registration with the Inter AS Anchor.

The registration message format is the same as the message format specified in the IETF, but the HoA is all 0s to indicate that the Inter AS Anchor needs to allocate the HoA of the terminal; and the CoA address option is the IP address of the PDG.

5509. After receiving the registration request message, the Inter AS Anchor verifies the reliability of the message to the AAA server.

5510. After receiving the mobile IP registration message, the Inter AS Anchor determines that the HoA needs to be allocated to the terminal according to the HoA all 0 in the message.

Inter AS Anchor first requests a DHCP address with a DHCP address from the terminal, then establishes a binding between the HoA and the CoA, and then returns a registration confirmation message to the PDG.

The S51UPDG returns a response to the terminal returning the end-to-end tunnel and returns the assigned HoA and CoA to the terminal.

Example 4:

Embodiment 4 is a process of registering a terminal in an IWLAN home network, where the AAA server and the HSS are separate entities, as shown in the flowchart 6, and the following steps are included:

S601: The terminal is successfully connected to the IWLA access network through access authentication.

5602. The terminal sends an end-to-end tunnel establishment request to the PDG, where the information carries information for verifying the terminal.

5603. The PDG sends a request message of the authentication terminal to the AAA server.

5604. The AAA server registers with the HSS.

5605. The HSS returns a registration confirmation message to the AAA server, and tells the AAA server the IP address information of the Inter AS Anchor corresponding to the terminal to complete the registration process of the mobile IP. 5606. The AAA server returns a verification response to the PDG, and returns an IP address of the Inter AS Anchor corresponding to the terminal.

The non-3GPP access gateway obtains the IP address of the Inter AS Anchor corresponding to the terminal and compares the network prefix address with its own IP address. In this embodiment, the IWLAN access network is determined to be the home network.

5607. The PDG replaces the terminal to perform proxy mobile IP registration with the Inter AS Anchor, where the registration message format is the same as the format specified in the IETF, but the HoA is all 0s, indicating that the Inter AS Anchor is required to allocate the HoA of the terminal; and the CoA address option is Also 0.

5608. After receiving the registration request message, the Inter AS Anchor verifies the reliability of the message to the AAA server.

5609. After receiving the mobile IP registration message, the Inter AS Anchor needs to allocate the home address to the terminal according to the HoA all 0 in the message; the Inter AS Anchor first requests an IP address as the home address of the terminal from the DHCP, and then returns a registration confirmation to the PDG. Message; The format of the registration confirmation message is consistent with the IETF specification. HoA is the assigned IP address, and the destination address of the message is the address of the PDG.

5610. The PDG returns a response to the terminal returning the end-to-end tunnel, and returns the allocated HoA to the terminal.

Example 5

As shown in FIG. 7 , it is a schematic structural diagram of a terminal in a non-3GPP access system registration system in an evolved network according to Embodiment 5 of the present invention. As can be seen from the figure, the system includes a non-3GPP access gateway that provides access for the terminal 710. 720, and Inter AS Anchor 730, which registers the mobility of the terminal 710, further includes:

a proxy mobile IP registration unit 721, configured to be used by the non-3GPP access gateway to perform proxy mobile IP registration for the terminal 710 to the Inter AS Anchor 730;

The registration response unit 722 is configured to be sent to the non-3GPP access gateway 720, and configured to send a response message to the terminal 710 to notify the HoA and the CoA;

a terminal registration form ^ 731 located at the InterAS Anchor 730, configured to enter the terminal 710 07 001460 Mobile IP registration, determine the terminal HoA and CoA.

The system also includes:

A terminal verification unit 723 is located at the non-3GPP access gateway 720 for authenticating the terminal 710 to the AAA server 740.

The system also includes:

The IP address information obtaining unit 724 is located at the non-3GPP access gateway 720, and the system for reporting to the AAA further includes:

The comparing unit 725 is located at the non-3GPP access gateway 720, and is configured to perform network prefix comparison with the IP address of the Inter AS Anchor 730 according to the IP address of the Inter AS Anchor 730, and determine whether the non-3GPP access network is a local network or a visited network. .

The system also includes:

The first IP address allocating unit 726 is located at the non-3GPP access gateway 720, and is configured to allocate the first IP address as the CoA to the terminal 710 when the non-3GPP access network is a visited network.

The system also includes:

The Inter AS Anchor allocates a HoA information setting unit 727 for the terminal, and the non-3GPP access gateway 720 is configured to set whether the Inter AS Anchor 730 is required to be the terminal 710 in sending the Proxy Mobile IP registration message to the Inter AS Anchor 730. Assign HoA information.

The system also includes:

The second IP address obtaining unit 732 is located at the Inter AS Anchor 730, and is configured to acquire the second IP address as the HoA of the terminal 710 from the DHCP server when the Inter AS Anchor is required to allocate the HoA to the terminal 710.

The system also includes:

The proxy mobile IP registration message reliability verification unit 728 is located at the non-3GPP access gateway 720 for authenticating the proxy mobile IP registration message reliability to the AAA server 740.

According to the foregoing embodiment of the present invention, the terminal can move the IP machine through the proxy under the evolved network architecture. The system successfully registers with the Inter AS Anchor and accesses the 3GPP service through the evolved core network. Compared with the basic mobile IP mechanism, the scheme greatly reduces the consumption of air interface signaling, thereby saving resources of air interfaces. The spirit and scope of the Ming. Thus, it is intended that the present invention cover the modifications and the modifications of the invention

Claims

Rights request

1. A terminal registration method in an evolved network, comprising:

The non-3GPP access gateway receiving terminal sends a registration request;

The non-3GPP access gateway replaces the terminal to perform proxy mobile IP registration with the anchor point between the access systems; the point between the access systems registers with the terminal, determines the home address of the terminal, and sends a registration to the non-3GPP access gateway. Confirmation message

The method according to claim 1, wherein in the step of receiving the registration request by the non-3GPP access gateway, the request sent by the terminal may be an end-to-end tunnel establishment request or a registration request.

The method according to claim 1, wherein the non-3GPP access gateway replaces the terminal in the proxy mobile IP registration step with the anchor point between the access systems, and further includes the non-3GPP access gateway to the AAA server. Verify the terminal.

The method according to claim 3, wherein the non-3GPP access gateway replaces the terminal to perform proxy mobile IP registration in the anchor point between the access systems, and further includes the non-3GPP access gateway to the AAA server. Obtaining Π>address information of an anchor point between access systems corresponding to the terminal.

The method according to claim 4, wherein the non-3GPP access gateway replaces the terminal in the proxy mobile IP registration step with the anchor point between the access systems, and the non-3GPP access gateway goes to the AAA server. Obtaining the IP address information of the anchor point between the access systems corresponding to the terminal, including the following steps:

The authentication and authentication charging server registers with the home subscriber server;

The home subscriber server returns a registration confirmation message to the authentication and authentication accounting server, and informs the terminal of the anchor IP address between the access systems.

The method according to claim 4, wherein the non-3GPP access gateway replaces the terminal to perform proxy mobile IP registration in the anchor point between the access systems, and further includes a non-3GPP access network. According to the IP address of the anchor point between the access systems, the network prefix is compared with the own IP address, and the step of determining whether the non-3GPP access network is a local network or a visited network is determined.

The method according to claim 6, wherein the non-3GPP access gateway replaces the terminal in the proxy mobile IP registration step with the anchor point between the access systems, and further includes if the non-3GPP access network To access the network, the non-3GPP access gateway assigns the terminal the first IP address as the care-of address.

The method according to claim 6 or 7, wherein the anchor point between the access systems registers with the terminal, determines a terminal home address, and sends a registration confirmation message to the non-3GPP access gateway. The non-3GPP access gateway sends a proxy mobile IP registration message to an anchor point between the access systems, and carries an anchor point between the access systems to allocate a home address address to the terminal.

The method according to claim 8, wherein the anchor point between the access systems registers with the terminal, determines a terminal home address, and sends a registration confirmation message to the non-3GPP access gateway. The proxy mobile IP registration message is provided with a home address field, and whether the anchor point between the access systems needs to allocate the home address information to the terminal, and the setting of the home address field carried by the proxy mobile IP registration message is carry.

The method according to claim 9, wherein the anchor point between the access systems registers with the terminal, determines a terminal home address, and sends a registration confirmation message to the non-3GPP access gateway, if An anchor point between the access systems is required to allocate a home address to the terminal, and an anchor point between the access systems acquires a second IP address as a home address of the terminal to the dynamic host configuration protocol server.

The method according to claim 7, 9 or 10, wherein the anchor point between the access systems registers the terminal, determines a terminal home address, and sends a registration confirmation message to the non-3GPP access gateway. In the step,

If the non-3GPP access gateway allocates the first IP address to the terminal, the first IP address is used as the care-of address, otherwise the non-3GPP access gateway address is used as the care-of address.

12. The method according to claim 7, wherein the anchor point between the access systems is The step of registering the terminal, determining the home address of the terminal, and sending the registration confirmation message to the non-3GPP access gateway further includes verifying, by the anchor point between the access systems, the reliability of the proxy mobile IP registration message to the authentication and authentication accounting server.

13. A non-3GPP access system registration system in an evolved network, comprising a non-3GPP access network providing access to the terminal: ^ an anchor point between the access systems for registering the terminal mobility, wherein Also includes:

14. The system of claim 13 further comprising:

And a terminal verification unit, located in the non-3GPP access gateway, for authenticating the terminal to the AAA server.

15. The system of claim 13, further comprising:

The IP address information obtaining unit is located at the non-3GPP access gateway, and is configured to acquire, by the AAA server, IP address information of an anchor point between the access systems corresponding to the terminal.

16. The system of claim 15 further comprising:

a comparison unit, located in the non-3GPP access gateway, configured to perform network prefix comparison with a non-3GPP access gateway IP address according to an IP address of an anchor point between the access systems, and determine a non-3GPP access network thereof For the local network or visit the network.

17. The system of claim 16, further comprising:

The first IP address allocation unit is located at the non-3GPP access gateway, and is configured to allocate the first IP address to the terminal as a care-of address when the non-3GPP access network is a visited network.

18. The system of claim 16 or 17, further comprising: An anchor point between the access systems is configured to allocate a home address information setting unit to the terminal, where the non-3GPP access gateway is configured to send a proxy mobile IP registration message to an anchor point between the access systems, and set whether to need to connect An anchor point between the systems assigns home address information to the terminal.

19. The system of claim 18, further comprising:

a second IP address obtaining unit, located at an anchor point between the access systems, configured to acquire a second IP address from the dynamic host configuration protocol server when the anchor point between the access systems needs to allocate a home address to the terminal The home address of the terminal.

20. The system of claim 13, further comprising:

The proxy mobile IP registration message reliability verification unit is located at the non-3GPP access gateway, and is configured to verify the reliability of the proxy mobile IP registration message to the authentication and authentication charging server.