WO2008009227A1

WO2008009227A1 - A method for the user equipment accessing the telecommunication system and the telecommunication system

Info

Publication number: WO2008009227A1
Application number: PCT/CN2007/070252
Authority: WO
Inventors: Ming Li; Lan Liu; Peng Zhang; Huadong Hu
Original assignee: Huawei Technologies Co., Ltd.
Priority date: 2006-07-11
Filing date: 2007-07-06
Publication date: 2008-01-24
Also published as: CN101106812A; CN101106812B

Abstract

A method for the user equipment accessing the telecommunication system and the telecommunication system include that the network side sets up the default bearer for the UE which accesses via the non-3GPP access network during the network side registration. The access user via the non-3GPP access network can be enabled to possess the function of “online forever”. For different scenario, the default bearer can be setup for the UE accessed via the non-3GPP access network by the SAE anchor of the home network and/or the visit network. If the non-3GPP access network for accessing the UE is unreliable, setup the secure tunnel between the gateway of the non-3GPP access network and the ASE anchor to ensure the information safety. It's required to allocate the service address for the UE during the registration and then IMS registration can be launched after the registration.

Description

TECHNICAL FIELD The present invention relates to the field of communications, and in particular, to a hybrid networking of a 3rd Generation Partnership Project ("3GPP") system and a non-3GPP system.

Background of the invention

At present, in order to significantly improve the ability of 3G to provide value-added services and promote network convergence, under the leadership of the International Standards Organization, the global industry is accelerating the research on broadband wireless technologies with higher bandwidth and stronger business capabilities.

Considering the rapid development of broadband wireless communication technologies such as WiMAX, 3GPP needs to propose its own standards, participate in the competition of broadband wireless communication technologies, and ensure the competitiveness of 3GPP systems in the next 10 years or even longer. 3GPP officially established the Long Term Evolution (LTE) research project in December 2004. The goal of the clear research project is to develop 3GPP wireless access technologies toward "high data rate, low latency and optimized packet data applications." "The direction of evolution.

While carrying out LTE research work, 3GPP initiated the System Architecture Evolution (SAE) research project, which was led by the SA2 (Service & System Aspects WG2) working group and RAN3. There is a close relationship between LTE and SAE, and together, the overall evolution of the 3GPP system is built.

It can be seen that the work of an access technology evolution 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.

In the evolution of the above packet technology, the most important parts involved 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 related to the present invention that need to be satisfied by the evolved network architecture 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 be the user. The delay of data is minimized. Third, the definition of each functional module in the evolved network architecture should avoid overlapping or duplication of functions to avoid unnecessary signaling interaction and delay.

As shown in FIG. 1 , the Evolved Packet Core mainly includes a Mobility Management Entity (MME), a User Plane Entity (UPE), and an 3GPP Anchor. ) and SAE Anchor four logic function modules.

The MME is responsible for the mobility management of the control plane, including user context and mobility state management. Temporary identity, security function, etc., which corresponds to the current universal mobile communication system (Universal Mobile

Telecommunications System (abbreviated as "UMTS") The control plane part of the Serving GPRS Support Node (SGSN).

The UPE is responsible for initiating paging for downlink data in idle state, managing and storing IP bearer parameters and routing information in the network, etc., which corresponds to the data plane portion of the SGSN within the current UMTS system.

3GPP Anchor is a user plane anchor point between different access systems in the 3GPP system;

SAE Anchor is the user plane anchor between the 3GPP access system and the non-3GPP system in SAE.

SAE Anchor and 3GPP Anchor are collectively referred to as user plane anchors between different access systems (Inter Access

System Anchor, referred to as "Inter AS Anchor" I "IASA").

It should be noted that ^∞1 30??1?8^^" refers to various access systems based on 1?, and not defined by the 3GPP organization, which may be WiMax, ADSL, and the like.

So far, the function and existence of each interface in Figure 1 has not been finalized yet, in addition, MME,

It is also undetermined how the four functional modules of UPE, 3GPP Anchor, and SAE Anchor are combined in the corresponding entities.

The SAE system architecture is briefly described above, and the roaming in SAE is further explained below.

In order to optimize the routing of data transmission for roaming users, the SAE standard requires that user-side data routing in the roaming area can take two forms: "Home routed" routing and "Local Breakout" routing.

The SAE roaming framework of the routing method of "Home routed" is shown in Figure 2. With this routing method, in the visited place, the user's data needs to be returned to the home network before entering the packet data network (Packet Data Network, referred to as "PDN"). ).

The SAE roaming framework of the "Local Breakout" routing method is shown in Figure 3. With this routing method, the user's data can directly enter the PDN network from the visited place.

In addition, it should be pointed out that in order to increase the support for the voice service and improve the connection speed of the mobile device, when the user attaches to the network in the SAE system, a bearer connection is established with the network to implement the "always on" function of the user. The bearer connection is called the "default bearer."

On the other hand, Wireless Local Area Network (WLAN) is a widely-used wireless access system, which refers to the application of wireless communication technology to interconnect computer devices to form a network system that can communicate with each other and realize resource sharing. . It uses radio frequency (Radio Frequency) technology to replace the local area network of old twisted-pair copper wires. The wireless LAN no longer uses a communication cable to connect the computer to the network, but wirelessly makes the construction of the network and the movement of the terminal more flexible. According to the 802.11b standard, WLAN provides 11 Mbps, which is 200 times higher than fixed dial-up Internet access (56K). It can perform WWW browsing, sending and receiving EMAIL, Enjoy online movies, download files and work.

In order to enable users of WLAN to access the 3GPP system more conveniently and use various services in the 3GPP system, 3GPP has established an Interworking Wireless Local Area Network ("IWLAN") project.

The mission of the IWLAN project is to study the interworking between WLAN and 3GPP systems, aiming to enable users of 3GPP systems to access 3GPP systems via WLAN. According to the latest research results of 3GPP, the architecture is applicable not only to WLAN access systems, but also to any IP-based access such as WiMAX and Asymmetric Digital Subscriber Line (ADSL). the way. Figure 4 shows the architecture of the IWLAN system.

However, there is currently no method for establishing a default bearer for a UE accessing from a non-3GPP access system, so UEs accessing from a non-3GPP access system are currently unable to acquire the "always on" capability.

Summary of the invention

The present invention provides a communication system and a method for a user equipment to access a communication system, so that a user accessing from a non-3GPP access system can also obtain an "always on" function.

To achieve the above objective, the present invention provides a method for a user equipment to access a communication system, including: the user equipment accesses a 3GPP core network through a non-3rd generation partner project 3GPP access system, and the 3GPP core network performs the user equipment Registering, and establishing a default bearer for the user equipment accessed through the non-3GPP access system during the registration process.

The step of establishing a default bearer for the user equipment in the registration process includes the following sub-steps: the user equipment initiates authentication to the authentication device of the 3GPP core network by using the gateway of the non-3GPP access system Authentication request;

After the authentication device successfully authenticates the user equipment, the anchor device in the 3GPP core network establishes a default bearer for the user equipment between the gateway device and the gateway.

In addition, in the method, if the user equipment directly accesses the home 3GPP core network through the gateway of the non-3GPP access system, the anchor device in the home 3GPP core network establishes a defect for the user equipment. Provincial bearer.

In addition, in the method, if the user equipment directly accesses the visited 3GPP core network through the gateway of the non-3GPP access system, and accesses the service in the home 3GPP core network through the visited 3GPP core network, The anchor device in the 3GPP core network establishes a default bearer for the user equipment, or establishes a default bearer for the user equipment by the anchor device in the visited 3GPP core network and the anchor device in the home 3GPP core network. In addition, in the method, if the user equipment directly accesses the visited 3GPP core network through the gateway of the non-3GPP access system, and accesses the service in the visited 3GPP core network, it is visited by the 3GPP core network. The anchor device establishes a default bearer for the user equipment.

In addition, in the method, the method further includes the following steps:

The 3GPP core network determines whether the non-3GPP access system can be trusted in the registration process, and if not trusted, establishes a security tunnel between the gateway of the non-3GPP access system and the anchor device, the default The bearer transmits data through the secure tunnel.

In addition, in the method, the method further includes the following steps:

In the registration process, a service address is assigned to the user equipment.

Further in the method, the device for assigning a service address to the user equipment is one of: a gateway in the non-3GPP access system, a home subscription subscriber server/authentication authorization and accounting server, or an anchor device.

In addition, in the method, the method further includes the following steps:

After the registration process ends, the user equipment initiates an IP multimedia subsystem registration process through the default bearer.

The present invention further provides a communication system, including a user equipment and a network side, where the network side further includes: a non-3GPP access system, configured to access the user equipment;

The 3GPP core network is configured to register a user equipment accessed by the non-3GPP access system, and establish a default bearer for the user equipment in the registration process.

The non-3GPP access system further includes a gateway, configured to initiate an authentication authentication request to the authentication device of the 3GPP core network when the user equipment accesses the non-3GPP access system.

The gateway further includes means for establishing a secure tunnel between the gateway and an anchor device of the 3GPP core network when the non-3GPP access system is not trusted by the 3GPP core network, the secure tunnel is used for carrying The default bearer.

The 3GPP core network also includes:

An authentication device, configured to authenticate the user equipment according to the authentication request of the gateway; and the anchor device is configured to: after the authentication device is successfully authenticated, the anchor device and the A default bearer is established between the gateways for the user equipment.

Further in the system, the user equipment includes means for initiating an IP Multimedia Subsystem registration procedure through the default bearer after the registration process is completed. By comparison, it can be found that the main difference between the technical solution of the present invention and the prior art is that

In the process of registering the UE accessed by the 3GPP access system, a default bearer is established for the UE. Thereby, the UE can obtain the function of "always online" in all access systems of the SAE, including the access system of 3GPP and the access system of non-3GPP.

In different scenarios, the default bearer can be established by the SAE Anchor in different networks for UEs accessing from non-3GPP access systems. In a non-roaming scenario, the default bearer is established by the SAE Anchor of the home network. In the roaming scenario of accessing the home network service, the default bearer is established by the SAE Anchor of the home network, or the SAE Anchor of the home network and the SAE Anchor of the visited network cooperate to construct a default bearer. In the roaming scenario of accessing the visited network service, the default bearer is built by the SAE Anchor of the visited network. By selecting the most suitable SAE Anchor to establish a default bearer, the route carrying the route is shorter, and the UE is served with higher efficiency.

If the non-3GPP access system is not trustworthy, a security tunnel needs to be established between the gateway of the non-3GPP access system and the SAE Anchor at the time of registration, and the default bearer is placed in the secure tunnel for transmission, or the default bearer. The data is encapsulated and transmitted in a secure tunnel to ensure the security of the communication information.

In the registration process, the UE needs to be assigned a service address to ensure that the UE can use the service normally.

According to requirements, after the registration process is finished, the UE can also register with the Internet Multimedia Subsystem (IMS) by using the established default bearer, so that the services provided by the IMS can be used. BRIEF DESCRIPTION OF THE DRAWINGS

1 is a prior art SAE network architecture;

2 is a SAE roaming architecture of a "Home routed" routing method in the prior art;

3 is a SAE roaming architecture of a "Local Breakout" routing method in the prior art;

4 is a schematic diagram of an IWLAN system architecture in the prior art;

6 is a system structural diagram of a UE accessing a communication network in a non-roaming scenario according to the inventive principle; FIG. 7 is a schematic diagram of a UE accessing a communication network in a non-roaming scenario according to the inventive principle;

FIG. 8 is a structural diagram of a system when a UE accesses a SAE system through a home network in a scenario of "Home Routed" roaming according to the principles of the present invention;

9 is a schematic diagram of a UE accessing a SAE system through a home network in a "Home Routed" roaming scenario according to the inventive principle;

10 is a UE accessing a SAE through a visited network in a "Home Routed" roaming scenario according to the inventive principle System structure diagram at the time of system;

11 is a schematic diagram of a UE accessing a SAE system through a visited network in a "Home Routed" roaming scenario according to the inventive principle;

FIG. 12 is a structural diagram of a system when a UE accesses a SAE system through a visited network in a scenario of "Local Breakout" roaming according to the inventive principle;

13 is a schematic diagram of a UE accessing a SAE system through a visited network in a "Local Breakout" roaming scenario according to the inventive principle;

14 is a system structural diagram of a UE accessing a communication network according to a first embodiment of the present invention;

15 is a flowchart of a method for a UE to access a communication network according to a first embodiment of the present invention;

16 is a flowchart of a method for a UE to access a communication network according to a second embodiment of the present invention;

17 is a flowchart of a method for a UE to access a communication network according to a third embodiment of the present invention;

18 is a flowchart of a method for a UE to access a communication network according to a fourth embodiment of the present invention;

19 is a flowchart of a method for a UE to access a communication network according to a fifth embodiment of the present invention;

20 is a flowchart of a method for a UE to access a communication network according to a sixth embodiment of the present invention;

21 is a system structural diagram of a UE accessing a communication network according to a seventh embodiment of the present invention;

22 is a flowchart of a method for a UE to access a communication network according to a seventh embodiment of the present invention;

23 is a flowchart of a method for a UE to access a communication network according to an eighth embodiment of the present invention;

24 is a flowchart of a method for a UE to access a communication network according to a ninth embodiment of the present invention;

25 is a flowchart of a method for a UE to access a communication network according to a tenth embodiment of the present invention;

26 is a flowchart of a method for a UE to access a communication network according to an eleventh embodiment of the present invention;

27 is a flowchart of a method for a UE to access a communication network according to a twelfth embodiment of the present invention;

28 is a system structural diagram of a UE accessing a communication network according to a thirteenth embodiment of the present invention;

29 is a flowchart of a method for a UE to access a communication network according to a thirteenth embodiment of the present invention;

30 is a flowchart of a method for a UE to access a communication network according to a fourteenth embodiment of the present invention;

31 is a flowchart of a method for a UE to access a communication network according to a fifteenth embodiment of the present invention;

32 is a flowchart of a method for a UE to access a communication network according to a sixteenth embodiment of the present invention;

33 is a flowchart of a method for a UE to access a communication network according to a seventeenth embodiment of the present invention;

FIG. 34 is a flowchart of a method for a UE to access a communication network according to an eighteenth embodiment of the present invention; FIG.

35 is a system structural diagram of a UE accessing a communication network according to a nineteenth embodiment of the present invention;

36 is a flowchart of a method for a UE to access a communication network according to a nineteenth embodiment of the present invention; 37 is a flowchart of a method for a UE to access a communication network according to a twentieth embodiment of the present invention; FIG. 38 is a flowchart of a method for a UE to access a communication network according to a twenty-first embodiment of the present invention; FIG. 40 is a flowchart of a method for a UE to access a communication network according to a twenty-third embodiment of the present invention; FIG. 5 is a second diagram of a method for accessing a communication network by a UE according to a twenty-third embodiment of the present invention; A flowchart of a method for a UE of a fourteenth embodiment to access a communication network.

Selling the way of applying the invention

In order to make the objects, technical solutions and advantages of the present invention more comprehensible, the present invention will be further described in detail with reference to the accompanying drawings.

When the UE accesses the SAE network through the system defined by the non-3GPP, the network side can register it and establish a default bearer. The present invention is applicable to registering and establishing a default bearer for a UE accessing the SAE network through a system defined by the non-3GPP in different scenarios. The following descriptions are made according to different scenarios:

In a non-roaming scenario, the UE accesses the network through a non-3GPP defined system, and then accesses the SAE system through the GW. The system architecture is shown in FIG. 6.

The access system defined by the non-3GPP is connected to the evolved packet core network in the SAE system through the S2 interface. If the non-3GPP access system is trusted for the SAE system, the S2 interface is considered to be secure; The 3GPP access system is untrustworthy for the δΑΕ system, and the S2 interface is considered to be insecure. A secure tunnel needs to be established between the GW and the SAE Anchor before establishing the default bearer. Among them, how the combination of MME, UPE, 3GPP Anchor and SAE Anchor is undecided in the figure.

The process of the UE registering and establishing the SAE default bearer in the non-roaming scenario is as shown in FIG. 7. In step 701, the UE first accesses the access system defined by the non-3GPP.

Then, in step 702, the UE queries the address of the available GW. The specific query method is the same as that in the prior art, and details are not described herein again.

Next, proceeding to step 703, the UE initiates a bearer setup request to the available GW.

Then, in step 704, after receiving the request, the GW initiates an authentication authentication request to the HSS/Authentication^Authorization, Account ("AAA") instead of the UE.

Next, proceeding to step 705, the HSS/AAA performs authentication authentication on the UE according to the authentication authentication request, and returns the result to G^, and returns the QoS related information of the default bearer of the UE. If the system requires the UE to perform IMS registration after the registration is completed, the HSS/AAA also needs to return the address of the P-CSCF and use the corresponding standard bit to indicate that IMS registration is required.

If the non-3GPP access system is untrustworthy for the SAE system, then proceed to step 706 to build

Replacement page Establish a secure tunnel from the GW to the SAE Anchor; if the non-3GPP access system is trusted for the SAE system, this step can be omitted. Since the process of establishing the security tunnel is independent of the process of establishing a default bearer by the UE, the step may also be performed during the process of establishing the bearer between the UE and the GW, or after the process of establishing the bearer.

Then, in step 707, the SAE system establishes a default bearer between the GW and the SAE Anchor, and sends the QoS parameters of the default bearer of the UE to each node. In the process of establishing the default bearer, the UE is also assigned a service address, which may be allocated by the GW, allocated by the HSS/AAA Server, or allocated by the SAE Anchor.

Then, in step 708, the GW sends a bearer setup response to the UE, and carries the service address allocated to the UE in step 707 in the response. If the system confirms in step 705 that the UE needs to perform IMS registration after the registration is completed and obtains from the HSS/AAA. The address of the P-CSCF is carried in the response at the same time.

After receiving the bearer setup response from the GW, if the UE still needs to perform IMS registration, the UE then proceeds to step 709 after the SAE registration is completed, initiates an IMS registration process through the address of the P-CSCF, and registers in the IMS.

The process of registering and establishing a default bearer in the "Home Routed" roaming scenario is described below. In the "Home Routed" roaming scenario, the UE has two ways to access the SAE system through the non-3GPP access system: one way is to access the SAE system directly through the home network to access the services in the home network; It accesses the SAE system through the visited network, and then accesses the services in the home network through the home network.

When the UE accesses the SAE system through the home network, its system structure is as shown in FIG. 8. The UE accesses the SAE Anchor in the home network through the GW from the S2 interface. If the non-3GPP defined access system in which the UE is located is trusted for the SAE system, the S2 interface is considered to be secure; if the non-3GPP defined access system is untrustworthy for the SAE system, then The S2 interface is insecure. Before establishing the default bearer, you need to establish a secure tunnel between the GW and the SAE Anchor in the home network. Among them, how the combination of MME, UPE, 3GPP Anchor and SAE Anchor is undecided.

In the "Home Routed" roaming scenario, when the UE accesses the SAE system through the home network, the process of the UE registering and establishing the default bearer is as shown in FIG. 9. In step 901, the UE first accesses the access defined by the non-3GPP. system.

Next, proceeding to step 902, the UE queries the address of the available GW.

Then, proceeding to step 903, the UE initiates a bearer setup request to the queried available GW.

Next, proceeding to step 904, the GW initiates an authentication authentication request to the HSS/AAA server (HSS/AAA Server) in the home network by using the AAA Service Proxy in the visited network instead of the UE.

Then, proceeding to step 905, the HSS/AAA server in the home network authenticates the UE, and returns the result to the GW through the AAA Server Proxy in the visited network, and returns the default bearer of the UE to the GW. QoS related information. If the system requires the UE to perform IMS registration after registration is complete, the HSS/AAA also needs to return the address of the P-CSCF and use the corresponding standard bit to indicate that IMS registration is required.

Next, proceeding to step 906, if the non-3GPP defined access system is untrustworthy for the SAE system, establishing a secure tunnel from the GW to the SAE Anchor in the home network; if the non-3GPP access system is for the SAE system If it is trustworthy, you can omit this step. Since the establishment process of the security tunnel is independent of the process of establishing a default bearer by the UE, the step may also be performed during the establishment of the bearer between the UE and the GW, or after the process of establishing the bearer.

Then, the process proceeds to step 907, and the default bearer between the GW and the SAE anchor in the home network is established, and the QoS parameters of the default bearer of the UE are sent to each node. In the process of establishing the default bearer, the UE is also assigned a service address, which may be allocated by the GW, allocated by the AAA Server Proxy in the visited network, or allocated by the S AE Anchor in the home network.

Then, in step 908, the GW sends a bearer setup response to the UE, where the response carries the service address allocated to the UE in step 907. If the system confirms in step 905 that the UE needs to perform IMS registration after the registration is completed and obtains from the HSS/AAA. The address of the P-CSCF is carried in the response at the same time.

After receiving the bearer setup response from the GW, if the UE still needs to perform IMS registration, the UE then proceeds to step 909 after the SAE registration is completed, initiates an IMS registration process through the address of the P-CSCF, and registers in the IMS.

The following describes the situation in which the UE accesses the SAE system by visiting the network in the "Home Routed" roaming scenario.

In this scenario, the UE accessing the access system defined by the non-3GPP defined in the visited network accesses the SAE Anchor in the visited network from the S2 through the GW, and then accesses the SAE Anchor in the home network. The system structure is as shown in FIG. 10. Shown: The combination of MME, UPE, 3GPP Anchor and SAE Anchor is undecided. In the figure, if the non-3GPP access system is trusted for the SAE system, the S2 interface is considered to be secure; if the non-3GPP access system is untrustworthy for the SAE system, the S2 interface is considered to be Insecure, a secure tunnel needs to be established between the GW and the SAE Anchor in the visited network before establishing the default bearer.

In this scenario, the process of the UE registering and establishing the default bearer is as shown in FIG. 11. In step 1101, the UE accesses the non-3GPP access system.

Next, proceeding to step 1102, the UE queries the address of the available GW.

Next, proceeding to step 1103, the UE initiates a bearer setup request to the available GW.

Then, proceeding to step 1104, the GW replaces the UE by accessing the AAA Server Proxy in the network to the home network. The HSS/AAA Server initiates an authentication authentication request.

Then, in step 1105, the HSS/AAA Server in the home network authenticates the UE, and returns the result to the GW through the AAA Server Proxy in the visited network, and also returns the QoS related information that the UE carries by default. Moreover, if the system requires the UE to perform IMS registration after the registration is completed, the ijHSS/AAA also needs to return the address of the P-CSCF, and uses the corresponding standard bit to indicate that IMS registration is required.

Next, proceeding to step 1106, if the non-3GPP defined access system is untrustworthy for the SAE system, establishing a secure tunnel from the GW to the SAE Anchor in the visited network; if the non-3GPP access system is for the SAE system If the process of establishing a secure tunnel is independent of the process of establishing a default bearer by the UE, the step may also be performed during the bearer establishment process of the UE and the GW, or may be established in the bearer process. After the process is carried out.

Then, the process proceeds to step 1107, and the default bearer between the SAE anchor in the visited network and the SAE anchor in the home network is established, and the QoS parameters of the default bearer of the UE are sent to each node. In the process of establishing the default bearer, the UE is also assigned a service address, which may be allocated by the GW, allocated by the AAA Server Proxy in the visited network, or allocated by the S AE Anchor in the home network.

Then, in step 1108, the GW sends a bearer setup response to the UE, where the response carries the service address allocated to the UE in step 1107. If the system confirms in step 1105 that the UE needs to perform IMS registration after the registration is completed and obtains from the HSS/AAA The address of the P-CSCF is carried in the response at the same time.

After receiving the bearer setup response from the GW, if the UE still needs to perform IMS registration, the UE then proceeds to step 1109 after the SAE registration is completed, initiates an IMS registration process through the address of the P-CSCF, and registers in the IMS.

The following describes the procedure for the UE to register and establish a default bearer in the "Local Breakout" roaming scenario. In the "Local Breakout" roaming scenario, the UE accesses the SAE Ancho in the visited network through the access system defined by the non-3GPP to access the services in the visited network. The system architecture is shown in Figure 12.

In Figure 12, how the combinations of MME, UPE, 3GPP Anchor and SAE Anchor are undecided. The non-3GPP-defined access system where the UE is located is connected to the SAE Anchor in the visited network through the GW from the S2 interface. If the non-3GPP defined access system is trustworthy for the SAE system, the S2 interface is considered to be secure; if the non-3GPP defined access system is untrustworthy for the SAE system, the S2 interface is considered It is not secure, then a secure tunnel needs to be established between the GW and the SAE Anchor in the visited network before establishing the default bearer.

The process of the UE registering and establishing the default bearer in the roaming scenario of "Local Breakout" is as shown in FIG. 13. In step 1301, the UE accesses the access system defined by the non-3GPP. Next, proceeding to step 1302, the UE queries the address of the available GW.

Next, proceeding to step 1303, the UE initiates a bearer setup request to the available GW.

Then, proceeding to step 1304, the GW initiates an authentication authentication request to the HSS/AAA Server in the home network by using the AAA Server Proxy in the visited network instead of the UE.

Then, in step 1305, the HSS/AAA Server in the home network authenticates the UE, and returns the result to the GW through the AAA Server Proxy in the visited network, and returns the QoS related to the default bearer of the UE. information. If the system requires the UE to perform IMS registration after the registration is completed, the HSS/AAA also needs to return the address of the P-CSCF and use the corresponding standard bit to indicate that IMS registration is required.

Next, proceeding to step 1306, if the non-3GPP defined access system is untrustworthy for the SAE system, establishing a secure tunnel from the GW to the SAE Anchor in the home network; if the non-3GPP access system is for the SAE system If it is trustworthy, you can omit this step. Since the establishment process of the security tunnel is independent of the process of establishing a default bearer by the UE, the step may also be performed during the establishment of the bearer between the UE and the GW, or after the process of establishing the bearer.

Then, the process proceeds to step 1307, and the default bearer between the GW and the SAE anchor in the visited network is established, and the QoS parameters of the default bearer of the UE are sent to each node. In the process of establishing the default bearer, the UE is also assigned a service address, which may be allocated by the GW, allocated by the AAA Server Proxy in the visited network, or allocated by the S AE Anchor in the visited network.

Then, in step 1308, the GW sends a bearer setup response to the UE, where the response carries the service address allocated to the UE in step 1307. If the system confirms in step 1305 that the UE needs to perform IMS registration after the registration is completed and obtains from the HSS/AAA. The address of the P-CSCF is carried in the response at the same time.

After receiving the bearer setup response from the GW, if the UE still needs to perform IMS registration, the UE then proceeds to step 1309 after the SAE registration is completed, and initiates an IMS registration process through the address of the P-CSCF to register in the IMS.

The first embodiment of the present invention will now be described in accordance with the principles of the invention.

In this embodiment, the UE is in a non-roaming scenario, the accessed non-3GPP access system is an IWLAN, and the IWLAN is trusted for the SAE system, the GW connected to the IWLAN is a PDG, and the service address of the UE is from the PDG. provide.

The system architecture of this embodiment is shown in Figure 14, where the combination of MME, UPE, PDG, 3GPP Anchor and SAE Anchor is undecided.

As shown in FIG. 15, in step 1501, the UE accesses the IWLAN access system. Then, the process proceeds to step 1502. The UE queries the address of the available PDG. The specific query method is the same as that in the prior art, and details are not described herein again.

Next, proceeding to step 1503, the UE initiates a bearer setup request to the available PDG.

Next, proceeding to step 1504, the PDG initiates an authentication authentication request to the HSS/AAA instead of the UE.

Then, proceeding to step 1505, the HSS/AAA authenticates the UE, and returns the result to the PDG, and returns the QoS related information of the default bearer of the UE. If the system requires the UE to perform IMS registration after registration is complete, the HSS/AAA also needs to return the address of the P-CSCF and use the corresponding standard bits to indicate that IMS registration is required.

Next, proceeding to step 1506, the PDG locally allocates a service address to the UE.

Then, proceeding to step 1507, the PDG sends a bearer setup request to the SAE Anchor, where the QoS parameters of the default bearer of the UE are carried.

Next, proceeding to step 1508, the SAE Anchor sends a bearer setup response to the PDG indicating that the corresponding resource has been successfully allocated.

Then, proceeding to step 1509, the PDG sends a bearer setup response to the UE, where the response carries the service address allocated for the UE. If the system confirms in step 1505 that the UE needs to perform IMS registration after registration is completed and the address of the P-CSCF is obtained from HSS/AAA, the address is carried in the response.

After receiving the bearer setup response from the GW, if the UE still needs to perform IMS registration, the UE proceeds to step 1510 after the SAE registration is completed, and initiates an IMS registration process for the UE to allocate the service address in step 1506, in the IMS. registered.

The second embodiment of the present invention is substantially the same as the first embodiment, except that in the first embodiment, the service address of the UE is provided by the PDG. In the embodiment, the service address of the UE is used by the HHS/AAA Server. provide.

Specifically, as shown in FIG. 16, the steps 1601 to 1605 are similar to the steps 1501 to 1505, and are not described herein again.

In step 1606, the PDG interacts with the HHS/AAA Server, and the HHS/AAA Server allocates the UE's service address.

Steps 1607 to 1610 are similar to steps 1507 to 1510, and are not described herein again.

The third embodiment of the present invention is substantially the same as the first embodiment, except that in the first embodiment, the service address of the UE is provided by the PDG; and in the embodiment, the service address of the UE is provided by the SAE Anchor.

Specifically, as shown in FIG. 17, step 1701 - step 1705 is similar to step 1501 - step 1505, and details are not described herein again. In step 1706, the PDG sends a bearer setup request to the SAE Anchor, where the QoS parameters of the default bearer of the UE are carried.

Then, proceeding to step 1707, after receiving the bearer setup request, the SAE Anchor allocates the service address of the UE. Then, in step 1708, the SAE anchor sends a bearer setup response to the PDG, indicating that the corresponding resource has been successfully allocated, and the service address of the allocated UE is sent to the PDG through the response.

Step 1709 and step 1710 are similar to steps 1509 and 1510, and are not described herein again.

The application scenario of the fourth embodiment of the present invention is substantially the same as that of the first embodiment. The UE is also in a non-roaming scenario, and the non-3GPP access system is also an IWLAN. However, the IWLAN is untrustworthy for the SAE system, and the gateway is also a PDG. The service address of the UE is provided by the PDG. The system architecture of this embodiment is the same as that of the first embodiment, as shown in FIG. 14, in which how the combinations of MME, UPE, PDG, 3GPP Anchor and SAE Anchor are undecided.

The specific implementation manner is shown in FIG. 18. In step 1801, the UE accesses the IWLAN access system.

Next, proceeding to step 1802, the UE queries the address of the available PDG.

Next, proceeding to step 1803, the UE initiates a bearer setup request to the available PDG.

Next, proceeding to step 1804, the PDG initiates an authentication authentication request to the HSS/AAA instead of the UE.

Then, proceeding to step 1805, the HSS/AAA performs authentication authentication on the UE, and returns the result to the PDG, and returns the QoS related information of the default bearer of the UE. If the system requires the UE to perform IMS registration after the registration is completed, Then the HSS/AAA also needs to return the address of the P-CSCF and use the corresponding standard bit to indicate that IMS registration is required.

Next, proceeding to step 1806, the PDG locally allocates a service address to the UE.

Next, proceed to step 1807 to establish a secure tunnel from the PDG to the SAE Anchor.

Then, proceeding to step 1808, the PDG sends a bearer setup request to the SAE Anchor, where the QoS parameters of the default bearer of the UE are carried.

Next, proceeding to step 1809, the SAE Anchor sends a bearer setup response to the PDG indicating that the corresponding resource has been successfully allocated.

Then, proceeding to step 1810, the PDG sends a bearer setup response to the UE, where the response carries the service address allocated for the UE. If the system confirms in step 1805 that the UE needs to perform IMS registration after the registration is completed and the address of the P-CSCF is obtained from the HSS/AAA, the address is also carried in the response.

After receiving the bearer setup response from the GW, if the UE still needs to perform IMS registration, the UE proceeds to step 1811 after the SAE registration is completed, and initiates an IMS registration process for the UE to allocate the service address in step 1806, and performs the IMS registration process in the IMS. registered. The fifth embodiment of the present invention is substantially the same as the fourth embodiment, except that in the fourth embodiment, the service address of the UE is provided by the PDG. In the embodiment, the service address of the UE is used by the HHS/AAA Server. provide.

Specifically, as shown in FIG. 19, step 1901 to step 1905 are similar to steps 1801 to 1805, and are not described herein again.

In step 1906, the PDG interacts with the HHS/AAA Server, and the HHS/AAA Server allocates the UE's service address.

Steps 1907 to 1911 are similar to steps 1807 to 1811, and are not described herein again.

The sixth embodiment of the present invention is substantially the same as the fourth embodiment, except that in the fourth embodiment, the service address of the UE is provided by the PDG; and in the embodiment, the service address of the UE is provided by the SAE Anchor.

Specifically, as shown in FIG. 20, step 2001-step 2005 is similar to step 1801 to step 1805, and is not described here.

In step 2006, a secure tunnel is established between the PDG and the SAE Anchor.

Then, in step 2007, the PDG sends a bearer setup request to the SAE Anchor, where the QoS parameters of the default bearer of the UE are carried.

Then, in step 2008, after receiving the bearer setup request, the SAE Anchor allocates the service address of the UE. Then, in step 2009, the SAE anchor sends a bearer setup response to the PDG, indicating that the corresponding resource has been successfully allocated, and the service address of the allocated UE is sent to the PDG through the response.

Steps 2010 and 2011 are similar to steps 1810 and 1811, and are not described here.

Next, a seventh embodiment of the present invention will be described.

In this embodiment, the UE is in a "Home Routed" roaming scenario, the UE accesses the SAE system through the home network, and the non-3GPP defined access system currently accessed by the UE is IWLAN, and the IWLAN is trusted for the SAE system. The GW connected to the IWLAN is a PDG, and the service address of the UE is provided by the PDG.

The system architecture of this embodiment is shown in Figure 21, where the combination of MME, UPE, PDG, 3GPP Anchor and SAE Anchor is undecided.

The specific implementation is shown in FIG. 22. In step 2201, the UE accesses the IWLAN access system.

Then, in step 2202, the UE queries the address of the available PDG. The specific query method is the same as that in the prior art, and details are not described herein again.

Next, proceeding to step 2203, the UE initiates a bearer setup request to the available PDG.

Then, proceeding to step 2204, the PDG initiates an authentication authentication request to the HSS/AAA Server in the home network by using the AAA Server Proxy in the visited network instead of the UE. Then, in step 2205, the HSS/AAA server in the home network authenticates the UE, and returns the result to the PDG through the AAA Server Proxy in the visited network, and also returns the QoS related information of the default bearer of the UE. If the system requires the UE to perform IMS registration after registration is completed, the HSS/AAA also needs to return the address of the P-CSCF and use the corresponding standard bit to indicate that IMS registration is required.

Next, proceeding to step 2206, the PDG allocates a service address to the UE.

Then, proceeding to step 2207, the PDG sends a bearer setup request to the SAE Anchor in the home network, where the QoS parameters of the default bearer of the UE are carried.

Then, proceeding to step 2208, the SAE Anchor in the home network sends a bearer setup response to the PDG indicating that the corresponding resource has been successfully allocated.

Then, proceeding to step 2209, the PDG sends a bearer setup response to the UE, and carries the service address allocated for the UE in the response. If the system confirms in step 2205 that the UE needs to perform IMS registration after the registration is completed and the address of the P-CSCF is obtained from the HSS/AAA, the address is carried in the response at the same time.

After receiving the bearer setup response from the GW, if the UE still needs to perform IMS registration, the UE proceeds to step 2210 after the SAE registration is completed, and initiates an IMS registration process for the UE to allocate the service address in step 2206, and performs the IMS registration process in the IMS. registered.

The eighth embodiment of the present invention is substantially the same as the seventh embodiment, except that in the seventh embodiment, the service address of the UE is provided by the PDG. In the embodiment, the service address of the UE is used by the HHS/AAA Server. provide.

Specifically, as shown in FIG. 23, steps 2301 to 2305 are similar to steps 2201 to 2205, and are not described herein again.

In step 2306, the PDG communicates with the AAA Server Proxy in the visited network, and the service address of the UE is allocated by the AAA Server Proxy in the visited network.

Step 2307 - Step 2310 is similar to Step 2207 - Step 2210, and details are not described herein again.

The ninth embodiment of the present invention is substantially the same as the seventh embodiment except that in the seventh embodiment, the service address of the UE is provided by the PDG. In the present embodiment, the service address of the UE is provided by the SAE Anchor.

Specifically, as shown in FIG. 24, steps 2401 to 2405 are similar to steps 2201 to 2205, and are not described herein again.

In step 2406, the PDG sends a bearer setup request to the SAE Anchor in the home network, where the QoS parameters of the default bearer of the UE are carried.

Then, proceeding to step 2407, after receiving the bearer setup request, the SAE Anchor in the home network allocates the service address of the UE. Then, in step 2408, the SAE anchor in the home network sends a bearer setup response to the PDG, indicating that the corresponding resource has been successfully allocated, and the service address of the allocated UE is sent to the PDG through the response.

Step 2409 and step 2410 are similar to steps 2209 and 2210, and are not described herein again.

The application scenario of the tenth embodiment of the present invention is substantially the same as that of the seventh embodiment. The UE is also in the "Home Routed" roaming scenario. The UE also accesses the SAE system through the home network. The non-3GPP access system is also the IWLAN, and the gateway is also the PDG. The service address of the UE is also provided by the PDG, the difference being that the IWLAN is untrustworthy for the SAE system.

The system architecture of this embodiment is the same as that of the seventh embodiment, as shown in FIG. 21, in which how the combinations of MME, UPE, PDG, 3GPP Anchor and SAE Anchor are undecided.

A specific implementation manner is shown in FIG. 25. In step 2501, the UE accesses the IWLAN access system.

Next, proceeding to step 2502, the UE queries the address of the available PDG.

Next, proceeding to step 2503, the UE initiates a bearer setup request to the available PDG.

Then, proceeding to step 2504, the PDG initiates an authentication authentication request to the HSS/AAA Server in the home network by using the AAA Server Proxy in the visited network instead of the UE.

Then, in step 2505, the HSS/AAA server in the home network authenticates the UE, and returns the result to the PDG through the AAA Server Proxy in the visited network, and returns the QoS related information of the default bearer of the UE. If the system requires the UE to perform IMS registration after registration is completed, the HSS/AAA also needs to return the address of the P-CSCF and use the corresponding standard bit to indicate that IMS registration is required.

Next, proceeding to step 2506, the PDG allocates a service address to the UE.

Next, proceed to step 2507 to establish a secure tunnel from the PDG to the SAE Anchor in the home network. Then, proceeding to step 2508, the PDG sends a bearer setup request to the SAE Anchor in the home network, where the QoS parameters of the default bearer of the UE are carried.

Then, proceeding to step 2509, the SAE Anchor in the home network sends a bearer setup response to the PDG indicating that the corresponding resource has been successfully allocated.

Then, proceeding to step 2510, the PDG sends a bearer setup response to the UE, where the response carries the service address allocated for the UE. If the system confirms in step 2505 that the UE needs to perform IMS registration after the registration is completed and the address of the P-CSCF is obtained from the HSS/AAA, the address is carried in the response at the same time.

After the UE receives the bearer setup response from the GW, if the IMS registration is still required, the UE proceeds to step 2511 after the SAE registration is completed, and initiates the IMS registration process for the UE to allocate the service address in step 2506, and performs the IMS registration process in the IMS. registered. The eleventh embodiment of the present invention is substantially the same as the tenth embodiment, except that in the tenth embodiment, the service address of the UE is provided by the PDG. In the present embodiment, the service address of the UE is HHS/AAA. Server provided.

Specifically, as shown in FIG. 26, steps 2601 to 2605 are similar to steps 2501 to 2505, and are not described herein again.

In step 2606, the PDG communicates with the AAA Server Proxy in the visited network, and the service address of the UE is allocated by the AAA Server Proxy in the visited network.

Step 2607 - Step 2611 is similar to step 2507 - step 2511, and details are not described herein again.

The twelfth embodiment of the present invention is substantially the same as the tenth embodiment, except that in the tenth embodiment, the service address of the UE is provided by the PDG; and in the embodiment, the service address of the UE is provided by SAE Anchor. .

Specifically, as shown in FIG. 27, steps 2701 to 2705 are similar to steps 2501 to 2505, and are not described herein again.

In step 2706, a secure tunnel is established from the PDG to the SAE Anchor in the home network.

Then, proceeding to step 2707, the PDG sends a bearer setup request to the SAE Anchor in the home network, where the QoS parameters of the default bearer of the UE are carried.

Then, proceeding to step 2708, after receiving the bearer setup request, the SAE Anchor in the home network allocates the service address of the UE.

Then, in step 2709, the SAE anchor in the home network sends a bearer setup response to the PDG, indicating that the corresponding resource has been successfully allocated, and the service address of the allocated UE is sent to the PDG through the response.

Step 2710, step 2711 is similar to step 2510 and step 2511, and details are not described herein again.

The thirteenth embodiment of the present invention is substantially the same as the seventh embodiment, except that in the seventh embodiment, the UE accesses the SAE system through the home network. In the embodiment, the UE accesses the SAE system through the visited network.

The system architecture of this embodiment is shown in Figure 28, where the combination of MME, UPE, PDG, 3GPP Anchor and SAE Anchor is undecided.

The specific implementation manner is shown in FIG. 29. In step 2901, the UE accesses the IWLAN access system.

Then, the process proceeds to step 2902, and the UE queries the address of the available PDG. The specific query method is the same as that in the prior art, and details are not described herein again.

Next, proceeding to step 2903, the UE initiates a bearer setup request to the available PDG.

Then, proceeding to step 2904, the PDG initiates an authentication authentication request to the HSS/AAA Server in the home network by using the AAA Server Proxy in the visited network instead of the UE. Then, in step 2905, the HSS/AAA Server in the home network authenticates the UE, and returns the result to the PDG through the AAA Server Proxy in the visited network, and also returns the QoS related information of the default bearer of the UE. If the system requires the UE to perform IMS registration after registration is completed, the HSS/AAA also needs to return the address of the P-CSCF and use the corresponding standard bit to indicate that IMS registration is required.

Next, proceeding to step 2906, the PDG allocates a service address to the UE.

Then, proceeding to step 2907, the PDG sends a bearer setup request to the SAE Anchor in the home network by using the S AE Anchor in the visited network, where the QoS parameters of the default bearer of the UE are carried.

Then, proceeding to step 2908, the SAE Anchor in the home network sends a bearer setup response to the PDG through the SAE Anchor in the visited network, indicating that the corresponding resource has been successfully allocated.

Then, proceeding to step 2909, the PDG sends a bearer setup response to the UE, and the service address assigned by the downlink network to the UE. If the system confirms in step 2905 that the UE needs to perform IMS registration after the registration is completed and the address of the P-CSCF is obtained from the HSS/AAA, the address is carried in the response at the same time.

After receiving the bearer setup response from the GW, if the UE still needs to perform IMS registration, the UE proceeds to step 2910 after the SAE registration is completed, and initiates an IMS registration process for the UE to allocate the service address in step 2906, in the IMS. registered.

The fourteenth embodiment of the present invention is substantially the same as the thirteenth embodiment, except that in the thirteenth embodiment, the service address of the UE is provided by the PDG. In the present embodiment, the service address of the UE is provided by the HHS. /AAA Server is available.

Specifically, as shown in FIG. 30, steps 3001 to 3005 are similar to steps 2901 to 2905, and are not described herein again.

In step 3006, the PDG interacts with the AAA Server Proxy in the visited network, and is visited by the visited network.

The AAA Server Proxy allocates the service address of the UE.

Steps 3007 to 3010 are similar to steps 2907 to 2910, and are not described herein again.

The fifteenth embodiment of the present invention is substantially the same as the thirteenth embodiment, except that in the thirteenth embodiment, the service address of the UE is provided by the PDG. In the present embodiment, the service address of the UE is determined by the SAE. Provided by Anchor.

Specifically, as shown in FIG. 31, steps 3101 to 3105 are similar to steps 2901 to 2905, and are not described herein again.

In step 3106, the PDG sends a bearer setup request to the S AE Anchor in the home network through the S AE Anchor in the visited network, where the QoS parameters of the default bearer of the UE are carried. Then, proceeding to step 3107, after receiving the bearer setup request, the SAE Anchor in the home network allocates the service address of the UE.

Then, in step 3108, the SAE anchor in the home network sends a bearer setup response to the PDG through the SAE Anchor in the visited network, indicating that the corresponding resource has been successfully allocated, and the service address of the allocated UE is sent to the PDG through the response.

Step 3109 and step 3110 are similar to steps 2909 and 2910, and are not described herein again.

The application scenario of the sixteenth embodiment of the present invention is substantially the same as that of the thirteenth embodiment. The UE is also in the "Home Routed" roaming scenario, and the UE also accesses the SAE system through the visited network. The non-3GPP access system is also IWLAN, and the gateway is the same. For PDG, the service address of the UE is also provided by the PDG, the difference being that the IWLAN is untrustworthy for the SAE system.

The system architecture of this embodiment is the same as that of the thirteenth embodiment, as shown in FIG. 28, in which how the combinations of MME, UPE, PDG, 3GPP Anchor, and SAE Anchor are undecided.

The specific implementation is shown in FIG. 32. In step 3201, the UE accesses the IWLAN access system.

Next, proceeding to step 3202, the UE queries the address of the available PDG.

Then, proceeding to step 3203, the UE initiates a bearer setup request to the available PDG.

Then, proceeding to step 3204, the PDG initiates an authentication authentication request to the HSS/AAA Server in the home network by using the AAA Server Proxy in the visited network instead of the UE.

Then, in step 3205, the HSS/AAA Server in the home network authenticates the UE, and returns the result to the PDG through the AAA Server Proxy in the visited network, and also returns the QoS related information of the default bearer of the UE. If the system requires the UE to perform IMS registration after the registration is completed, the HSS/AAA also needs to return the address of the P-CSCF and use the corresponding standard bit to indicate that IMS registration is required.

Next, proceeding to step 3206, the PDG allocates a service address to the UE.

Next, proceed to step 3207 to establish a secure tunnel from the PDG to the SAE Anchor in the visited network. Then, proceeding to step 3208, the PDG sends a bearer setup request to the SAE Anchor in the home network by using the S AE Anchor in the visited network, where the QoS parameters of the default bearer of the UE are carried.

Then, proceeding to step 3209, the SAE Anchor in the home network sends a bearer setup response to the PDG through the SAE Anchor in the visited network, indicating that the corresponding resource has been successfully allocated.

Then, proceeding to step 3210, the PDG sends a bearer setup response to the UE, where the response carries the service address allocated for the UE. If the system confirms in step 3205 that the UE needs to perform IMS registration after registration is completed and the address of the P-CSCF is obtained from HSS/AAA, then the address is carried in the response at the same time. After receiving the bearer setup response from the GW, if the UE still needs to perform IMS registration, the UE proceeds to step 3211 after the SAE registration is completed, and initiates an IMS registration process for the UE to allocate the service address in step 3206, and performs the IMS registration process in the IMS. registered.

The seventeenth embodiment of the present invention is substantially the same as the sixteenth embodiment, except that in the sixteenth embodiment, the service address of the UE is provided by the PDG. In the present embodiment, the service address of the UE is provided by the HHS. /AAA Server is available.

Specifically, as shown in FIG. 33, steps 3301 to 3305 are similar to steps 3201 to 3205, and are not described herein again.

In step 3306, the PDG interacts with the AAA Server Proxy in the visited network, and is visited by the visited network.

The AAA Server Proxy allocates the service address of the UE.

Step 3307 - Step 3311 is similar to Step 3207 - Step 3211, and details are not described herein again.

The eighteenth embodiment of the present invention is substantially the same as the sixteenth embodiment, except that in the sixteenth embodiment, the service address of the UE is provided by the PDG. In the present embodiment, the service address of the UE is SAE. Provided by Anchor.

Specifically, as shown in FIG. 34, steps 3401 to 3405 are similar to steps 3201 to 3205, and are not described herein again.

In step 3406, a secure tunnel is established from the PDG to the SAE Anchor in the visited network.

Then, proceeding to step 3407, the PDG sends a bearer setup request to the SAE Anchor in the home network by using the S AE Anchor in the visited network, where the QoS parameters of the default bearer of the UE are carried.

Then, in step 3408, after receiving the bearer setup request, the SAE Anchor in the home network allocates the service address of the UE.

Then, in step 3409, the SAE anchor in the home network sends a bearer setup response to the PDG through the SAE anchor in the visited network, indicating that the corresponding resource has been successfully allocated, and the service address of the allocated UE is sent to the PDG through the response.

Step 3410, step 3411 is similar to step 3210 and step 3211, and details are not described herein again.

Next, a nineteenth embodiment of the present invention will be described.

In this embodiment, the UE is in a "Local Breakout" roaming scenario, and the non-3GPP defined access system currently accessed by the UE is an IWLAN, and the IWLAN is trusted for the SAE system, and the GW connected to the IWLAN is a PDG. The service address of the UE is provided by the PDG.

The system architecture of this embodiment is shown in Figure 35, where MME, UPE, PDG, 3 GPP Anchor, and SAE How Anchor is combined is undecided.

The specific implementation is shown in FIG. 36. In step 3601, the UE accesses the IWLAN access system.

Then, the process proceeds to step 3602, and the UE queries the address of the available PDG. The specific query method is the same as that in the prior art, and details are not described herein again.

Next, proceeding to step 3603, the UE initiates a bearer setup request to the available PDG.

Next, proceeding to step 3604, the PDG initiates an authentication authentication request to the HSS/AAA Server in the home network by using the AAA Server Proxy in the visited network instead of the UE.

Then, in step 3605, the HSS/AAA Server in the home network authenticates the UE, and returns the result to the PDG through the AAA Server Proxy in the visited network, and also returns the QoS related information that the UE carries by default. If the system requires the UE to perform IMS registration after the registration is completed, the HSS/AAA also needs to return the address of the P-CSCF and use the corresponding standard bit to indicate that IMS registration is required.

Next, proceeding to step 3606, the PDG allocates a service address to the UE.

Next, proceeding to step 3607, the PDG sends a bearer setup request to the SAE Anchor in the visited network, where the QoS parameters of the default bearer of the UE are carried.

Then, proceeding to step 3608, the SAE Anchor in the visited network sends a bearer setup response to the PDG indicating that the corresponding resource has been successfully allocated.

Then, proceeding to step 3609, the PDG sends a bearer setup response to the UE, where the response carries the service address allocated for the UE. If the system confirms in step 3605 that the UE needs to perform IMS registration after the registration is completed and the address of the P-CSCF is obtained from the HSS/AAA, the address is carried in the response at the same time.

After receiving the bearer setup response from the GW, if the UE still needs to perform IMS registration, the UE proceeds to step 3610 after the SAE registration is completed, and initiates an IMS registration process for the UE to allocate the service address in step 3606, in the IMS. registered.

The twentieth embodiment of the present invention is substantially the same as the nineteenth embodiment, except that in the nineteenth embodiment, the service address of the UE is provided by the PDG. In the present embodiment, the service address of the UE is provided by the HHS. /AAA Server is available.

Specifically, as shown in FIG. 37, steps 3701 to 3705 are similar to steps 3601 to 3605, and are not described herein again.

In step 3706, the PDG communicates with the AAA Server Proxy in the visited network, and the service address of the UE is allocated by the AAA Server Proxy in the visited network.

Step 3707 - Step 3710 is similar to Step 3607 - Step 3610, and details are not described herein again. The twenty-first embodiment of the present invention is substantially the same as the nineteenth embodiment, except that in the nineteenth embodiment, the service address of the UE is provided by the PDG. In the present embodiment, the service address of the UE is Provided by SAE Anchor.

Specifically, as shown in FIG. 38, steps 3801 to 3805 are similar to steps 3601 to 3605, and are not described herein again.

In step 3806, the PDG sends a bearer setup request to the SAE Anchor in the visited network, where the QoS parameters of the default bearer of the UE are carried.

Then, in step 3807, after receiving the bearer setup request, the SAE Anchor in the visited network allocates the service address of the UE.

Then, in step 3808, the SAE anchor in the visited network sends a bearer setup response to the PDG, indicating that the corresponding resource has been successfully allocated, and the service address of the allocated UE is sent to the PDG through the response.

Step 3809 and step 3810 are similar to steps 3609 and 3610, and are not described herein again.

The application scenario of the twenty-second embodiment of the present invention is substantially the same as that of the nineteenth embodiment. The UE is also in the "Local Breakout" roaming scenario, the non-3GPP access system is also the IWLAN, and the gateway is also the PDG, and the service address of the UE is also The PDG provides the difference that IWLAN is untrustworthy for the SAE system.

The system architecture of this embodiment is the same as that of the nineteenth embodiment, as shown in FIG. 35, in which how the combinations of MME, UPE, PDG, 3GPP Anchor and SAE Anchor are undecided.

The specific implementation manner is shown in FIG. 39. In step 3901, the UE accesses the IWLAN access system.

Next, proceeding to step 3902, the UE queries the address of the available PDG.

Next, proceeding to step 3903, the UE initiates a bearer setup request to the available PDG.

Then, proceeding to step 3904, the PDG initiates an authentication authentication request to the HSS/AAA Server in the home network by using the AAA Server Proxy in the visited network instead of the UE.

Then, in step 3905, the HSS/AAA Server in the home network authenticates the UE, and returns the result to the PDG through the AAA Server Proxy in the visited network, and also returns the QoS related information of the default bearer of the UE. If the system requires the UE to perform IMS registration after the registration is completed, the HSS/AAA also needs to return the address of the P-CSCF and use the corresponding standard bit to indicate that IMS registration is required.

Then, proceeding to step 3906, the PDG allocates a service address to the UE;

Next, proceed to step 3907 to establish a secure tunnel from the PDG to the SAE Anchor in the visited network. Then, proceeding to step 3908, the PDG sends a bearer setup request to the SAE Anchor in the visited network, where the QoS parameters of the default bearer of the UE are carried. Then, proceeding to step 3909, the SAEAnchor in the visited network sends a bearer setup response to the PDG, indicating that the corresponding resource has been successfully allocated.

Then, proceeding to step 3910, the PDG sends a bearer setup response to the UE, and carries the service address allocated for the UE in the response. If the system confirms in step 3905 that the UE needs to perform IMS registration after the registration is completed and the address of the P-CSCF is obtained from the HSS/AAA, the address is carried in the response at the same time.

After the UE receives the bearer setup response from the GW, if the IMS registration is still required, the UE proceeds to step 3911 after the SAE registration is completed, and initiates an IMS registration process for the UE to allocate the service address in step 3906, and performs the IMS registration process in the IMS. registered.

The twenty-third embodiment of the present invention is substantially the same as the twenty-second embodiment, except that in the twenty-second embodiment, the service address of the UE is provided by the PDG; The address is provided by HHS/AAA Server.

Specifically, as shown in FIG. 40, step 4001 to step 4005 are similar to steps 3901 to 3905, and are not described herein again. . '

In step 4006, the PDG interacts with the AAA Server Proxy in the visited network, and is visited by the visited network.

The AAA Server Proxy allocates the service address of the UE.

Step 4007 - Step 4011 is similar to Step 3907 - Step 3911, and details are not described herein again.

The twenty-fourth embodiment of the present invention is substantially the same as the twenty-second embodiment, except that in the twenty-second embodiment, the service address of the UE is provided by the PDG. In the present embodiment, the service of the UE is Address by SAE

Provided by Anchor.

Specifically, as shown in FIG. 5, steps 4101 to 4105 are similar to steps 3901 to 3905, and are not described herein again.

In step 4106, a secure tunnel is established from the PDG to the S AE Anchor in the visited network.

Then, proceeding to step 4107, the PDG sends a bearer setup request to the SAE Anchor in the visited network, where the QoS parameters of the default bearer of the UE are carried.

Then, proceeding to step 4108, after receiving the bearer setup request, the SAE Anchor in the visited network allocates the service address of the UE.

Then, in step 4109, the SAE anchor in the visited network sends a bearer setup response to the PDG, indicating that the corresponding resource has been successfully allocated, and the service address of the allocated UE is sent to the PDG through the response.

Step 4110 and step 4111 are similar to steps 3910 and 3911, and are not described herein again.

In addition to IWLAN, the present invention can also be applied to other non-3GPP access systems, such as microwave access.

twenty three

Replacement page Worldwide Interoperability for Microwave Access ("WiMAX") system, 3GPP2 access system, Asymmetric Digital Subscriber Line (ADSL), and so on.

While the invention has been illustrated and described with reference to the preferred embodiments of the present invention The spirit and scope of the invention.

Claims

Rights request

A method for a user equipment to access a communication system, comprising:

The user equipment accesses the 3GPP core network through the non-3rd generation partner project 3GPP access system;

The 3GPP core network registers the user equipment, and establishes a default bearer for the user equipment accessed through the non-3GPP access system during the registration process.

The method for the user equipment to access the communication system according to claim 1, wherein the step of establishing a default bearer for the user equipment in the registration process comprises the following sub-steps:

The user equipment initiates an authentication authentication request to the authentication device of the 3GPP core network by using the gateway of the non-3GPP access system;

The method for accessing a communication system of a user equipment according to claim 2, wherein if the user equipment directly accesses the home 3GPP core network through a gateway of the non-3GPP access system, An anchor device in the 3GPP core network establishes a default bearer for the user equipment.

The method for accessing a communication system by a user equipment according to claim 2, wherein if the user equipment directly accesses a visited 3GPP core network through a gateway of the non-3GPP access system, and accesses the The 3GPP core network accesses the services in the 3GPP core network, and the anchor device in the home 3GPP core network establishes a default bearer for the user equipment, or is visited by the anchor device in the 3GPP core network and the home 3GPP core network. The anchor devices jointly establish a default bearer for the user equipment.

The method for accessing a communication system of a user equipment according to claim 2, wherein if the user equipment directly accesses a 3GPP core network through a gateway of the non-3GPP access system, and accesses the visit The services in the 3GPP core network are established by the anchor device in the 3GPP core network to establish a default bearer for the user equipment.

The method for accessing a communication system by a user equipment according to claim 1, further comprising the steps of:

The method for accessing a communication system of a user equipment according to claim 1, further comprising the steps of:

8. The method for accessing a communication system by a user equipment according to claim 7, wherein the device for assigning a service address to the user equipment is one of the following:

The gateway in the non-3GPP access system, the home subscription subscriber server/authentication authorization and accounting server, or the anchor device.

The method of claim 1, wherein the method further comprises:

10. A communication system, comprising:

a non-3GPP access system, configured to access user equipment;

The communication system according to claim 10, wherein the non-3GPP access system further comprises a gateway, configured to: when the user equipment accesses the non-3GPP access system, to the 3GPP core network Initiate an authentication request.

The communication system according to claim 11, wherein the 3GPP core network further includes: an authentication device, configured to perform authentication and authentication on the user equipment according to the authentication authentication request of the gateway; The device is configured to establish a default bearer between the anchor device and the gateway according to the authentication device after the authentication device is successfully authenticated.

13. The communication system according to claim 12, wherein the gateway further comprises an anchor for the gateway and the 3GPP core network when the non-3GPP access system is not trusted by the 3GPP core network. A unit for establishing a secure tunnel between the point devices, where the secure tunnel is used to carry the default bearer.

The communication system according to any one of claims 10 to 13, wherein the user equipment further comprises: after the registration process ends, initiating IP multimedia subsystem registration by using the default bearer The unit of the process.