WO2013174190A1

WO2013174190A1 - Routing selection method and functional network element

Info

Publication number: WO2013174190A1
Application number: PCT/CN2013/074627
Authority: WO
Inventors: 刘国燕; 尤建洁; 朱春晖; 吴瑟; 王霞; 余跃
Original assignee: 中兴通讯股份有限公司
Priority date: 2012-05-23
Filing date: 2013-04-24
Publication date: 2013-11-28
Also published as: CN103428800A

Abstract

Disclosed is a routing selection method, which is applied to a converged network of a WLAN access network and a 3GPP core network. A functional network element is arranged between the WLAN access network and the 3GPP core network. The method comprises: when UE accesses through a WLAN access network, a functional network element forwarding to an AAA an authentication request message sent by the UE, and forwarding to an access network element of the WLAN access network the authentication response message sent by the AAA; and/or the functional network element receiving an IP address request message sent by the access network element of the WLAN access network. Also disclosed at the same time is a functional network element. The present invention can conduct routing selection for 3GPP UE according to the type of the accessing UE and the service type, thereby reducing the access pressure of a 3GPP network.

Description

Routing method and function network element

The present invention relates to a routing technology, and in particular, to a routing method and a functional network element. Background technique

Evolved Universal Terrestrial Radio Access Network (E-UTRAN), Mobile Administration, Evolved Universal Terrestrial Radio Access Network (E-UTRAN), 3rd Generation Partnership Project (3GPP, 3rd Generation Partnership Project) The unit (MME, Mobility Management Entity), the Serving Gateway (S-GW), the Packet Data Network Gateway (P-GW), and the Home Subscriber Server (HSS).

1 is a schematic structural diagram of interworking between a 3GPP network and a non-3GPP network in the prior art. As shown in FIG. 1, the EPS supports interworking with a non-3GPP system, wherein interworking with a non-3GPP system is implemented through an S2a/b/c interface. The P-GW acts as an anchor between the 3GPP and the non-3GPP system. In the system architecture diagram of EPS, non-3GPP system access is divided into untrusted non-3GPP access and trusted non-3GPP access; wherein untrusted non-3GPP access requires evolved packet data gateway (ePDG, Evolved Packet) The Data Gateway is connected to the P-GW. The interface between the ePDG and the P-GW is S2b. The trusted non-3GPP access can be directly connected to the P-GW through the S2a interface. The S2a interface uses the PMIP protocol for information exchange. In addition, the S2c interface Provides user plane-related control and mobility support between the user set UE, User Equipment and the P-GW. The supported mobility management protocol is dual-stack mobile IPv6 (DSMIPv6, Moblie IPv6 Support for Dual Stack). Hosts and Routers), which can be used for untrusted non-3GPP and trusted non-3GPP access.

Currently, many operators believe that wireless local area networks (WLAN, Wireless Local Area) Network can be used as a trusted non-3GPP system. Therefore, the problem of interworking between UEs accessing EPS through trusted WLANs has gradually been taken seriously and research has begun, and related architectures have been generated in the prior art. 2 is a schematic diagram of the architecture of the UE accessing the EPC through the WLAN in the prior art. As shown in FIG. 2, one logical network element of the WLAN communicates with the P-GW of the 3GPP through the S2a interface, and the S2a interface supports the GTP (Generic Tunneling Protocol) / The PMIP (Proxy Mobile IP) protocol, but how the specific logical network elements inside the WLAN network support the interworking process with the P-GW, there is no clear technical solution.

In the related art, if the AC (Access Controller) / BNG (Boundary Network Node) supports the S2a interface, all AC/BNG devices need to be upgraded, which will have a greater impact on the live network. In order to solve this problem, a WLAN access gateway (for example, a Trusted WLAN Access Gateway (TWAG)) is introduced, and the 3GPP network can be implemented without a large-scale upgrade of the AC/BNG equipment. Access, which reduces the upgrade of the existing network. In addition, in the case where both the WLAN UE and the 3GPP UE exist simultaneously, how to ensure that it does not affect the related processes of the WLAN UE, there is no relevant research at present. Summary of the invention

In view of this, the main purpose of the present invention is to provide a routing method and a function network element, which can implement routing for an accessed 3GPP UE in a trusted WLAN and a 3GPP network convergence network, thereby reducing access of the 3GPP network. pressure.

In order to achieve the above object, the technical solution of the present invention is implemented as follows: a routing method applied to a wireless local area network WLAN access network and a network of a third generation partnership project 3GPP core network convergence; in the WLAN access network And a functional network element is disposed between the 3GPP core network; and the method includes:

When the user equipment UE accesses the WLAN access network, the function network element grants authentication The right charging AAA forwards the authentication request message sent by the UE, and forwards the authentication response message sent by the AAA to the access network element of the WLAN access network; and/or, the function network element receives the WLAN An IP address request message sent by the access network element of the access network.

The functional network element is located in the WLAN access network or the 3GPP core network.

The AAA is an AAA server or an AAA proxy of the WLAN access network, or an AAA server or an AAA proxy of the 3GPP core network.

A universal routing encapsulated GRE tunnel or a multi-protocol label switching MPLS tunnel is established between the functional network element and the access network element of the WLAN access network.

The method further includes:

The access network element of the WLAN access network determines whether the UE is a 3GPP UE according to an authentication type and/or a domain name of the UE, and determines a packet route.

The method further includes:

The access network element of the WLAN access network determines, according to the service type associated with the UE, whether to locally allocate an IP address for the UE.

The method further includes:

The access network element of the WLAN access network obtains the information of the service type of the decision from the AAA server or the AAA proxy of the 3GPP core network by using the authentication of the extended authentication protocol EAP.

The service type includes: allowing access to the 3GPP core network, and/or slotted service offloading, or denying access.

The access network element of the WLAN access network includes a border network node BNG/access controller AC.

The IP address request message is a DHCP message or a route request message.

When the function entity is connected to the AAA server or the AAA proxy of the WLAN access network, the function entity supports the collection of the charging information, and reports the AAA charging message to the AAA server of the WLAN access network or AAA agent. The AAA charging message includes a Radius charging message or a Diameter charging message. The WLAN access network includes an architecture network defined by a fixed broadband forum BBF. A routing method is applied to a network in which a WLAN access network and a 3GPP core network are integrated; a functional network element is configured in the fused network; and the method includes:

The function network element receives the authentication response message sent by the AAA, obtains the service type of the decision, and determines whether to allocate the local IP to the UE according to the service type information associated with the UE, and implements routing to the UE.

The AAA is an AAA server or an AAA proxy of the WLAN access network, or an AAA server of the 3GPP core network.

The functional network element is located in the WLAN access network or the 3GPP core network. The service type includes: allowing access to the 3GPP core network, and/or slotted service offloading, or denying access.

When the service type is a slotted service offload, the function network element allocates a local IP to the UE after receiving the IP address request message.

The IP address request message is a DHCP message or a route request message.

A functional network element is applied to a network in which a WLAN access network and a 3GPP core network are integrated; the functional network element includes: a receiving unit, a forwarding unit, and/or a sending unit, where:

a receiving unit, configured to receive an authentication request message sent by the UE when accessing the WLAN access network; and receiving an authentication response message sent by the AAA; and/or receiving the access network element of the WLAN access network IP address request message; and/or, receiving an AAA charging response message sent by an AAA server or an AAA proxy of the WLAN access network;

a forwarding unit, configured to forward the authentication request message to the AAA; and forward the authentication response message to an access network element of the WLAN access network;

The sending unit is configured to send an AAA charging request message to the AAA server or the AAA proxy of the WLAN access network. The WLAN access network access gateway is located in the WLAN access network or the 3GPP core network.

A GRE tunnel or an MPLS tunnel is established between the WLAN access network access gateway and the access network element of the WLAN access network.

The access network element of the WLAN access network includes a BNG/AC.

The AAA charging message includes a Radius charging message or a Diameter charging message.

A functional network element is applied to a network in which a WLAN access network and a 3GPP core network are integrated; the WLAN access network access gateway includes: a receiving unit, an obtaining unit, and a determining unit, where: the receiving unit is configured to receive the AAA The authentication response message sent;

Get the unit, set to get the business type of the decision;

And a determining unit, configured to determine, according to the service type information associated with the UE, whether to allocate a local IP to the UE, and implement routing to the UE.

The WLAN access network access gateway is located in the WLAN access network or the 3GPP core network.

The WLAN access network access gateway further includes:

The allocating unit is configured to allocate a local IP to the UE after the receiving unit receives the IP address request message, when the receiving unit receives the IP address request message.

In the present invention, active power is set between a network where a trusted WLAN and a 3GPP network are fused. When the UE accesses the trusted WLAN, the function network element forwards the authentication request message sent by the UE to the AAA server, and forwards the authentication sent by the AAA server to the access network element of the trusted WLAN. a response message; and/or, the function network element receives an IP address request message sent by the access network element of the trusted WLAN, and notifies the access network of the trusted WLAN by the IP address allocated by the 3GPP network for the UE The access network element of the WLAN performs routing according to the type of the UE. The invention can perform routing for the 3GPP UE according to the type and service type of the accessed UE, thereby alleviating the access pressure of the 3GPP network. DRAWINGS

1 is a schematic structural diagram of interworking between a 3GPP network and a non-3GPP network in the prior art; FIG. 2 is a schematic diagram of a structure in which a UE accesses an EPC through a WLAN in the prior art; FIG. 3 is a schematic diagram of a UE passing through a WLAN after introducing TWAG′ in the present invention; Schematic diagram of the architecture 1 of the S2a interface accessing the EPC;

4 is a flowchart of a UE connected to an EPC through a WLAN S2a interface according to an embodiment of the present invention;

FIG. 5 is a flowchart of a UE connected to an EPC through a WLAN S2a interface according to an embodiment of the present invention;

6 is a flowchart of a UE connected to an EPC through a WLAN S2a interface according to an embodiment of the present invention;

FIG. 7 is a schematic diagram of the architecture 2 of the UE accessing the EPC through the WLAN S2a interface after the introduction of the TWAG′ in the present invention;

FIG. 8 is a flowchart of a UE based on architecture 2 accessing an EPC through a WLAN S2a interface according to an embodiment of the present invention;

FIG. 9 is a flowchart of a UE based on architecture 2 accessing an EPC through a WLAN S2a interface according to an embodiment of the present invention;

FIG. 10 is a schematic diagram of a UE based on architecture 2 accessing through a WLAN S2a interface according to an embodiment of the present invention; EPC flow chart;

FIG. 11 is a flowchart of a UE accessing an EPC through a WLAN S2a interface according to an embodiment of the present invention; FIG. 12 is a flowchart of a UE accessing an EPC through a WLAN S2a interface according to an embodiment of the present invention; FIG. 13 is a functional network according to an embodiment of the present invention; Schematic diagram of the composition of the element;

FIG. 14 is a schematic structural diagram of another functional network element according to an embodiment of the present invention. detailed description

Example 1

In this embodiment, the architecture of the entire network when the UE accesses the EPC through the trusted WLAN is mainly described. The central idea of the architecture is to add a WLAN access gateway within the WLAN network to communicate with the control plane and user plane messages between the WLAN network and the EPC network.

The network element involved in the architecture differs from the network element involved in the existing access network accessing the existing 3GPP network in that a TWAG' is added to the WLAN network: TWAG' is responsible for the WLAN network and the EPC network. Interworking between control plane messages and user plane data. FIG. 3 is a schematic diagram of the architecture 1 of the UE accessing the EPC through the WLAN S2a interface after the introduction of the TWAG′ in the present invention. As shown in FIG. 3, the key interfaces involved in the network architecture are as follows: Interface C: Interface between TWAG' and BBF AAA. The interface is used to forward the authentication message sent by the BNG or BBF AAA, and the authentication success message sent by the BBF AAA can be used to trigger the establishment of a GTP/PMIP tunnel between the TWAG' and the P-GW of the EPC.

Interface D: is the interface between TWAG' and BNG. This interface is used to forward authentication messages, or DHCP messages, and user data sent by the BNG.

NOTE: The main logical network of the above architecture is for the BBF access architecture. Similarly, the above architecture is also applicable to the WLAN access network. The RG is replaced by an AP and the BNG is replaced by an AC.

Example 2

In this embodiment, the process of accessing the 3GPP EPC by the 3GPP UE through the WLAN is mainly described. The EAP authentication process needs to be forwarded to the WLAN AAA through the TWAG, and the AP/RG is used as the EAP Authenticator, AC/BNG and TWAG as the AAA proxy. This embodiment is executed when the traffic type that the AC/BNG receives the 3GPP AAA decision is to allow access to the EPC. 4 is a flowchart of a UE connected to an EPC through a WLAN S2a interface according to a first embodiment of the present invention. The process for a UE to access an EPC through a WLAN S2a interface includes the following steps:

Step 401: The UE performs a non-3GPP-specific process with the WLAN network element, for example, establishing a link, and the like;

Step 402: The UE may send an EAPOL-START message to the AP/RG to request authentication. Step 403-Step 404: The AP/RG acts as an EAP Authenticator and triggers an EAP authentication process to the UE. The UE carries the NAI in the EAP-RES/Identity message. After receiving the AAA-encapsulated EAP-RES/Identity message, the AC/BNG can determine whether it is a 3GPP UE according to the authentication type. If the authentication type is not EAP authentication, it is considered as a WLAN UE, and the WLAN UE access is performed. The process in the prior art of the WLAN network; otherwise, the domain name information in the NAI is obtained by parsing the message, and it is determined to be a 3GPP UE; or, the domain name can be used to determine that it is a 3GPP UE. If it is a 3GPP UE, the UE MAC address and the domain name information are associated with the corresponding GRE tunnel, and the association relationship is locally saved. Then, the message is encapsulated into the TWAG through the GRE tunnel, or forwarded to the TWAG according to the route. After receiving the GRE message, TWAG' removes the encapsulation of the GRE header, and then acts as an AAA proxy, forwards the decapsulated packet to WLAN AAA, and forwards it to 3GPP AAA via WLAN AAA.

NOTE: The above GRE tunnels can be replaced by other types of tunnels, such as MPLS. EAP authentication messages are directly transmitted through the tunnel and are not transmitted through the tunnel.

Step 405 - Step 407: Perform a subsequent EAP process. When the TWAG receives the EAP authentication success message, step 406 is performed. Wherein, TWAG' functions as step 403-step 404 as an AAA proxy or AAA relay. During the authentication process, AC/BNG obtains the service type authorized by 3GPP AAA. The service type includes: Allow access to EPC, and/or slotted services. Divert, or deny access. After the AC/BNG obtains the service type authorized by the 3GPP AAA, if the service type is allowed to access the EPC, the information may be bound to the UE MAC address, and the association relationship is locally saved. In this embodiment, the type of service is to allow access to the EPC. The AC/BNG may locally store the association between the service type and the UE MAC address to explicitly indicate that the type of service it supports is to allow access to the EPC, or may not save the association locally to implicitly describe the services it supports. The type is to allow access to the EPC.

If the GTP/PMIP tunnel establishment is triggered by the EAP authentication success message, step 408-411 is performed, and then the process proceeds to step 412. Otherwise, go directly to step 412 for execution.

Step 408-Step 413: After receiving the EAP authentication success message, the TWAG' requests the establishment of the GTP/PMIP tunnel to the P-GW, and also establishes an IP-CAN session with the PCRF, and performs P- between the HSS and the HSS. GW identification update. After receiving the create session response message or the proxy binding acknowledgement message, the TWAG sends an EAP authentication success message to the UE through the AC/BNG and the AP/RG.

Step 414 - Step 415: If the UE sends a DHCP request message, the AC/BNG receives the DHCP request message (which may be a DHCPv4 or DHCPv6 message) sent by the UE, and then finds the associated service type as the allowed access according to the UE MAC. The EPC then finds the associated GRE tunnel and encapsulates the message to the TWAG through the GRE tunnel. After receiving the GRE message, the TWAG' removes the encapsulation of the GRE header and then processes the DHCP request message.

If the GTP/PMIP tunnel establishment is triggered by the DHCP message, then steps 408-411 are performed, and then the process proceeds to step 416. Otherwise, go directly to step 416 for execution.

Step 416 - Step 417: Perform another DHCP process between the UE and the TWAG to allocate an IP address to the UE. At this time, you can also bind the IP address to the MAC address.

Step 418: If the UE sends a route request message, after receiving the route request message sent by the UE, the AC/BNG finds that the associated service type is allowed to access the EPC according to the UE MAC, and then finds the associated GRE tunnel through the GRE. The tunnel encapsulates the message to TWAG';TWAG' After receiving the GRE packet, the encapsulation of the GRE header is removed, and then the routing request message is processed.

If the GTP/PMIP tunnel establishment is triggered by the route request message, step 408-411 is performed, and then go to step 420 to continue execution. Otherwise, go directly to step 420 to continue.

Step 420 - Step 421: Perform the remaining process of the route confirmation message to allocate an IP address to the UE. At this time, you can also bind the IP address to the MAC address.

Generally, the BNG/AC supports the collection of the charging information based on the UE and reports it to the WLAN AAA for charging. In this embodiment, the TWAG can also support the collection of the charging information and report it to the WLAN. AAA performs billing. Therefore, when the TWAG' allocates an IP address to the UE (for example, in the case of TWAG, while performing step 417 or step 420), a charging request (start) message is sent to the WLAN AAA, and then the WLAN AAA replies to the charging response (start). Message. When the BNG/AC performs specific service offloading, the TWAG, the calculated charging information is the charging information of the related service data that the 3GPP UE accesses the EPC. When TWAG performs specific traffic offloading, the billing information is the total billing information or the independent billing information of the service data of the 3GPP UE accessing the EPC and the direct service offload. If the total charging information is sent, the TWAG, the charging request (start message) sent to the WLAN is sent when the TWAG' receives the first request for the IP address, for example: TWAG, receives the first A message requesting an IP address indicating its direct traffic offload, then the TWAG sends a charging request (start message) to the WLAN, and subsequently, the TWAG receives a message requesting an IP address, instructing it to allocate an IP from the PDN GW. Address, TWAG at this time, will not send a charging request (start message) to the WLAN; vice versa. If independent charging information is sent, the charging request (start message) is sent independently. These billing information can be used as a reference for billing bills between operators.

Step 422: When the BNG/AC receives the uplink data, it also finds the associated service type as EPC access according to the UE MAC or the UE IP address, and then finds the associated GRE tunnel, and then encapsulates the message through the GRE tunnel. After TWAG, TWAG' receives the GRE header, removes the encapsulation of the GRE header, encapsulates it through GTP or PMIP tunnel, and forwards it to the P-GW. When the BNG/AC receives the downlink data, it directly removes the encapsulation of the GRE header and forwards the packet to the packet.

UE.

In the present invention, when the TWAG receives the detachment related message of the UE leaving the network, it sends a charging request (termination) message to the WLAN AAA, and then the WLAN AAA replies with the charging response (terminating) message.

In addition to the Radius charging protocol, TWAG can also support the Diameter charging protocol, and the related message replaces the related charging message of the above Radius.

Example 3

In this embodiment, the process is similar to that in the second embodiment. The difference is that the AP/RG is not used as the EAP Authenticator, but the AC/BNG is used as the EAP Authenticator. The AP/RG cannot sense the related EAP authentication process. Other processes refer to the related description of Embodiment 2. For details, refer to the process shown in Figure 5. The details are as follows:

Step 501: The UE performs a non-3GPP-specific process with the WLAN network element, for example, establishing a link, and the like;

Step 502: The UE may send an EAPOL-START message to the AC/BNG to request authentication. Step 503-Step 504: The AC/BNG acts as an EAP authenticator, and triggers an EAP authentication process to the UE. The UE carries the NAI in the EAP-RES/Identity message. After receiving the AAA-encapsulated EAP-RES/Identity message, the AC/BNG can determine whether it is a 3GPP UE according to the authentication type. If the authentication type is not EAP authentication, it is considered as a WLAN UE, and the WLAN UE access is performed. The process in the prior art of the WLAN network; otherwise, the domain name information in the NAI is obtained by parsing the message, and it is determined to be a 3GPP UE; or, the domain name can be used to determine that it is a 3GPP UE. If it is a 3GPP UE, the UE MAC address and the domain name information are associated with the corresponding GRE tunnel, and the association relationship is locally saved. Then, the packet is encapsulated into the TWAG through the GRE tunnel, or forwarded to the TWAG according to the route. After receiving the GRE message, TWAG' removes the encapsulation of the GRE header, and as an AAA proxy, it will be decapsulated. The message is forwarded to WLAN AAA and forwarded to 3GPP AAA via WLAN AAA.

Step 505 - Step 507: Perform a subsequent EAP process. When the TWAG receives the EAP authentication success message, step 506 is performed. Among them, TWAG' functions as step 503-step 504, acting as an AAA proxy. During the authentication process, the AC/BNG obtains the service type authorized by the 3GPP AAA. The service type includes: allowing access to the EPC, and/or slotted service offload, or denying access. After the AC/BNG obtains the service type authorized by the 3GPP AAA, if the service type is allowed to access the EPC, the information may be bound to the UE MAC address, and the association relationship is locally saved. In this embodiment, the type of service is to allow access to the EPC. The AC/BNG may locally store the association between the service type and the UE MAC address to explicitly indicate that the type of service it supports is to allow access to the EPC, or may not save the association locally to implicitly describe the services it supports. The type is to allow access to the EPC.

If the GTP/PMIP tunnel establishment is triggered by the EAP authentication success message, step 508-511 is performed, and then the process proceeds to step 512. Otherwise, go directly to step 512 for execution.

Step 508 - Step 513: After receiving the EAP authentication success message, the TWAG' requests the establishment of the GTP/PMIP tunnel to the P-GW, and also establishes an IP-CAN session with the PCRF, and performs P- between the HSS and the HSS. GW identification update. After receiving the create session response message or the proxy binding acknowledgement message, the TWAG sends an EAP authentication success message to the UE through the AC/BNG and the AP/RG.

Step 514 - Step 515: If the UE sends a DHCP request message, the AC/BNG receives the DHCP request message (which may be a DHCPv4 or DHCPv6 message) sent by the UE, and then finds the associated service type as the allowed access according to the UE MAC. The EPC then finds the associated GRE tunnel and encapsulates the message to the TWAG through the GRE tunnel. After receiving the GRE message, the TWAG' removes the encapsulation of the GRE header and then processes the DHCP request message. If the GTP/PMIP tunnel establishment is triggered by the DHCP message, then steps 508-511 are performed, and then the process proceeds to step 516. Otherwise, go directly to step 516 for execution.

Step 516 - Step 517: Perform another DHCP process between the UE and the TWAG to allocate an IP address to the UE. In this case, you can also bind the IP address to the MAC address.

Step 518 - Step 519: If the UE sends a route request message, the AC/BNG receives

After the routing request message sent by the UE, the UE is found to be connected to the EPC according to the service type of the UE, and then the associated GRE tunnel is found, and the message is encapsulated into the TWAG by the GRE tunnel; the TWAG' receives the GRE message. After that, the encapsulation of the GRE header is removed, and then the routing request message is processed. If the GTP/PMIP tunnel establishment is triggered by the route request message, then step 408-511 is performed, and then go to step 520 to continue execution. Otherwise, go directly to step 520 to continue.

Step 520 - Step 521: Perform the remaining process of the route confirmation message to allocate an IP address to the UE. In this case, you can also bind the IP address to the MAC address.

Step 522: When the BNG/AC receives the uplink data, it also finds the associated service type as EPC access according to the UE MAC or the UE IP address, and then finds the associated GRE tunnel, and then encapsulates the message through the GRE tunnel. After TWAG, TWAG' receives the GRE header, removes the encapsulation of the GRE header, encapsulates it through GTP or PMIP tunnel, and forwards it to the P-GW.

When the BNG/AC receives the downlink data, it directly removes the encapsulation of the GRE header and forwards the packet to the packet.

UE.

In the present invention, the TWAG can also support the collection of charging information. For details, refer to the foregoing embodiment.

2 related description.

Example 4

In this embodiment, the process of directly performing slotted service offloading by the 3GPP UE through WLAN access is mainly described. The EAP authentication process needs to be forwarded to WLAN AAA through TWAG, AP/RG as EAP Authenticator, and AC/BNG and TWAG' as AAA agents. When the AC/BNG receives the service type authorized by the 3GPP AAA as a slotted service offloading operation, the implementation is performed. example. For details, refer to the process shown in Figure 6. The process includes the following steps:

Step 601 - Step 613: It is identical to Step 401 - Step 413. The AC/BNG, as an AAA proxy, obtains the service type authorized by the 3GPP AAA. The service type includes: EPC access, and/or slotted service offload, or denial of access. After the AC/BNG obtains the service type authorized by the 3GPP AAA, if the service type is a split service, the slotted service offload information is bound to the UE MAC address, and the association relationship is saved locally.

Step 614: Step 616: If the UE sends a DHCP request message, the AC/BNG receives the DHCP request message sent by the UE, and then determines to locally allocate the IP address allocation to the UE according to the slotted service offload information associated with the UE MAC address. Then, the remaining steps of the DHCP process are performed to complete the process of assigning an IP address to the UE. In this case, you can also bind the IP address to the MAC address.

Step 617: Step 618: If the UE sends a route request message, the AC/BNG receives the route request message sent by the UE, and determines to locally allocate the IP address to the UE according to the slotted service offload information associated with the UE MAC address. Then, an acknowledgment message is sent to the UE, and the process of allocating an IP address to the UE is completed. In this case, you can also bind the IP address to the MAC address.

Step 619: When the BNG/AC receives the uplink data, it also finds the associated service type as a slotted service offload according to the UE MAC or the source IP address, and then performs specific data forwarding.

When the BNG/AC receives downlink data, it forwards the packet directly to the UE.

The above embodiment is for the AP/RG as the EAP authenticator. If the AC/BNG is the EAP authenticator, then step 601-step 613 is replaced by step 501-step 513. The processing of the other steps is the same as that of this embodiment.

In this embodiment, the BNG/AC sends the charging information to the WLAN AAA, and the adopted protocol is an AAA charging protocol, including: a Radius charging protocol, or a Diameter charging protocol.

Example 5 In this embodiment, the difference from the flow of Embodiment 1 is that a TWAG' is added in the WLAN network: TWAG' has no interface interaction with the BBF AAA, and there is no STa interface between the BBF AAA and the 3GPP AAA, TWAG' and There is interface interaction between 3GPP AAA. Other functions refer to the related description of Embodiment 1. See Figure 7 for details.

Under the network architecture, the key interfaces involved are as follows:

Interface C: is the interface between TWAG' and 3GPPAAA. The interface is used to forward the authentication message sent by the BNG or BBF AAA, and the authentication success message sent by the BBF AAA can be used to trigger the establishment of a GTP/PMIP tunnel between the TWAG' and the P-GW of the EPC.

Under this architecture, the 3GPP UE's authentication is through BNG to TWAG, and then TWAG, forwarded to 3GPP AAA for the interaction of the authentication process. However, for the charging of the 3GPP UE in the BBF access network, the charging information is collected by the BNG, and then reported to the BBF AAA for local charging information statistics, and used for reconciliation with the charging information of the 3GPP core network; A Radius or Diameter billing protocol can be used between BNG and BBF AAA.

Example 6

In this embodiment, the procedure of the embodiment 2 is similar, except that the EAP authentication process between the TWAG and the 3GPP AAA does not need to be transited by the WLAN AAA, but directly communicates with each other. Other processes refer to the related description of Embodiment 2. For details, see the process shown in Figure 8. The details are as follows:

Step 801: The UE and the WLAN network element perform a non-3GPP-specific process, such as: link establishment, and the like; Step 802: The UE may send an EAPOL-START message to the AP/RG to request authentication. Step 803 - Step 804: The AP/RG acts as the ΕΑΡ Authenticator and triggers the ΕΑΡ authentication process to the UE. The UE carries the NAI in the EAP-RES/Identity message. After receiving the AAA-encapsulated EAP-RES/Identity message, the AC/BNG can determine whether it is a 3GPP UE according to the authentication type. If the authentication type is not EAP authentication, it is considered as a WLAN UE, and the WLAN UE access is performed. The process in the prior art of the WLAN network; otherwise, the domain name information in the NAI is obtained by parsing the message, and it is determined to be a 3GPP UE; or, the domain name can be used to determine that it is a 3GPP UE. If it is a 3GPP UE, the UE MAC address and the domain name information are associated with the corresponding GRE tunnel, and the association relationship is locally saved. Then, the message is encapsulated into the TWAG through the GRE tunnel, or forwarded to the TWAG according to the route. After receiving the GRE message, TWAG' removes the encapsulation of the GRE header and then forwards the decapsulated message to 3GPPAAA as an AAA proxy.

Step 805 - Step 807: Perform a subsequent EAP process. When the TWAG' receives the EAP authentication success message, step 806 is performed. Among them, TWAG' acts as step 803-step 804 as an AAA proxy. During the authentication process, the AC/BNG obtains the service type authorized by the 3GPP AAA. The service type includes: allowing access to the EPC, and/or slotted service offload, or denying access. After the AC/BNG obtains the service type authorized by the 3GPP AAA, if the service type is allowed to access the EPC, the information may be bound to the UE MAC address, and the association relationship is locally saved. In this embodiment, the type of service is to allow access to the EPC. The AC/BNG may locally store the association between the service type and the UE MAC address to explicitly indicate that the type of service it supports is to allow access to the EPC, or may not save the association locally to implicitly describe the services it supports. The type is to allow access to the EPC.

If the GTP/PMIP tunnel is triggered by the EAP authentication success message, the step is executed. Step 808 - step 811, and then go to step 812 to perform. Otherwise, go directly to step 812 for execution. Step 808 - Step 813: After receiving the EAP authentication success message, the TWAG' requests the establishment of the GTP/PMIP tunnel to the P-GW, and also establishes an IP-CAN session with the PCRF, and performs P- between the HSS and the HSS. GW identification update. After receiving the create session response message or the proxy binding acknowledgement message, the TWAG sends an EAP authentication success message to the UE through the AC/BNG and the AP/RG.

Step 814 - Step 815: If the UE sends a DHCP request message, the AC/BNG receives the DHCP request message (specifically, it may be a DHCPv4 or a DHCPv6 message), and then finds the associated service type as the allowed access according to the UE MAC. The EPC then finds the associated GRE tunnel and encapsulates the message to the TWAG through the GRE tunnel. After receiving the GRE message, the TWAG' removes the encapsulation of the GRE header and then processes the DHCP request message.

If the GTP/PMIP tunnel establishment is triggered by the DHCP message, then steps 808-811 are performed, and then go to step 816 for execution. Otherwise, go directly to step 816 for execution.

Step 816-Step 817: Perform another DHCP process between the UE and the TWAG to allocate an IP address to the UE. In this case, you can also bind the IP address to the MAC address.

Step 818-Step 819: If the UE sends a route request message, after receiving the route request message sent by the UE, the AC/BNG finds that the associated service type is allowed to access the EPC according to the UE MAC, and then finds the associated GRE tunnel. The packet is encapsulated by the GRE tunnel to the TWAG'; after receiving the GRE packet, the TWAG' removes the encapsulation of the GRE header and then processes the routing request message.

If the GTP/PMIP tunnel establishment is triggered by the route request message, then step 808 - step 811 is performed, and then go to step 820 to continue execution. Otherwise, go directly to step 820 to continue.

Step 820 - Step 821: Perform the remaining process of the route confirmation message to allocate an IP address to the UE. In this case, you can also bind the IP address to the MAC address.

Step 822: When the BNG/AC receives the uplink data, it also according to the UE MAC or the UE IP. Address, find the associated service type as EPC access, and then find the associated GRE tunnel, and then encapsulate the message to TWAG through the GRE tunnel; after receiving the GRE message, TWAG' removes the encapsulation of the GRE header and passes The GTP or PMIP tunnel is encapsulated and forwarded to the P-GW.

UE.

Example 7

In this embodiment, the process is similar to that in Embodiment 6. The difference is that the AP/RG is not used as the EAP Authenticator, but the AC/BNG is used as the EAP Authenticator. The AP/RG cannot sense the related EAP authentication process. Other processes refer to the related description of Embodiment 6. For details, see the process shown in Figure 9, including the following steps:

Step 901: The UE and the WLAN network element perform a non-3GPP specific process, such as: link establishment, etc.;

Step 902: The UE may send an EAPOL-START message to the AC/BNG to request authentication. Step 903-Step 904: The AC/BNG acts as an EAP authenticator, and triggers an EAP authentication process to the UE. The UE carries the NAI in the EAP-RES/Identity message. After receiving the AAA-encapsulated EAP-RES/Identity message, the AC/BNG can determine whether it is a 3GPP UE according to the authentication type. If the authentication type is not EAP authentication, it is considered as a WLAN UE, and the WLAN UE access is performed. The process in the prior art of the WLAN network; otherwise, the domain name information in the NAI is obtained by parsing the message, and it is determined to be a 3GPP UE; or, the domain name can be used to determine that it is a 3GPP UE. If it is a 3GPP UE, the UE MAC address and the domain name information are associated with the corresponding GRE tunnel, and the association relationship is locally saved. Then, the packet is encapsulated into the TWAG through the GRE tunnel, or forwarded to the TWAG according to the route. After receiving the GRE message, TWAG' removes the encapsulation of the GRE header and then forwards the decapsulated message to 3GPPAAA as an AAA proxy.

In the present invention, the above GRE tunnel can also be replaced by other types of tunnels, such as: MPLS, etc.; or, the EAP authentication message is directly transmitted through the routing mode and is not transmitted through the tunnel. Step 905: Step 907: Perform a subsequent EAP process. When the TWAG receives the EAP authentication success message, step 906 is performed. Among them, TWAG' acts as step 903-step 904 as an AAA proxy. During the authentication process, the AC/BNG obtains the service type authorized by the 3GPP AAA. The service type includes: allowing access to the EPC, and/or slotted service offload, or denying access. After the AC/BNG obtains the service type authorized by the 3GPP AAA, if the service type is allowed to access the EPC, the information may be bound to the UE MAC address, and the association relationship is locally saved. In this embodiment, the type of service is to allow access to the EPC. The AC/BNG may locally store the association between the service type and the UE MAC address to explicitly indicate that the type of service it supports is to allow access to the EPC, or may not save the association locally to implicitly describe the services it supports. The type is to allow access to the EPC.

If the GTP/PMIP tunnel establishment is triggered by the EAP authentication success message, then step 908-step 911 is performed, and then the process proceeds to step 912. Otherwise, go directly to step 912 for execution.

Step 908: Step 913: After receiving the EAP authentication success message, the TWAG' requests the P-GW to establish a GTP/PMIP tunnel, and also establishes an IP-CAN session with the PCRF, and performs P- between the HSS and the HSS. GW identification update. After receiving the create session response message or the proxy binding acknowledgement message, the TWAG sends an EAP authentication success message to the UE through the AC/BNG and the AP/RG.

Step 914 - Step 915: If the UE sends a DHCP request message, the AC/BNG receives the DHCP request message (specifically, it may be a DHCPv4 or a DHCPv6 message), and then finds the associated service type as the allowed access according to the UE MAC. The EPC then finds the associated GRE tunnel and encapsulates the message to the TWAG through the GRE tunnel. After receiving the GRE message, the TWAG' removes the encapsulation of the GRE header and then processes the DHCP request message.

If the GTP/PMIP tunnel establishment is triggered by the DHCP message, then steps 908-911 are performed, and then go to step 916 for execution. Otherwise, go directly to step 916 for execution. Step 916 - Step 917: Perform another process of DHCP between the UE and the TWAG, and allocate an IP address to the UE. In this case, you can also bind the IP address to the MAC address.

Step 918: Step 919: If the UE sends a route request message, the AC/BNG receives the route request message sent by the UE, and then finds the associated service type according to the UE MAC to allow access to the EPC, and then finds the associated GRE tunnel. The packet is encapsulated by the GRE tunnel to the TWAG'; after receiving the GRE packet, the TWAG' removes the encapsulation of the GRE header and then processes the routing request message.

If the GTP/PMIP tunnel establishment is triggered by the route request message, then step 908-step 911 is performed, and then go to step 920 to continue execution. Otherwise, go directly to step 920 to continue.

Step 920 - Step 921: Perform the remaining process of the route confirmation message to allocate an IP address to the UE. In this case, you can also bind the IP address to the MAC address.

Step 922: When the BNG/AC receives the uplink data, it also finds the associated service type as EPC access according to the UE MAC or the UE IP address, and then finds the associated GRE tunnel, and then encapsulates the message through the GRE tunnel. After TWAG, TWAG' receives the GRE header, removes the encapsulation of the GRE header, encapsulates it through GTP or PMIP tunnel, and forwards it to the P-GW.

UE.

Example 8

In this embodiment, the procedure is the same as that in the fourth embodiment. The difference is that the EAP authentication process between the TWAG and the 3GPP AAA does not need to be transited by the WLAN AAA, but directly communicates with each other. Other processes refer to the related description of Embodiment 4. For details, refer to the process shown in Figure 10. The process includes the following steps:

Step 1001 - Step 1013: The same as Step 401 - Step 413. The AC/BNG, as an AAA proxy, obtains the service type authorized by the 3GPP AAA. The service type includes: EPC access, and/or slotted service offload, or denial of access. Obtain 3GPP in AC/BNG After the AAA authorized service type, if the service type is a split service, the slotted service offload information is bound to the UE MAC address, and the association relationship is saved locally.

Step 1014: Step 1016: If the UE sends a DHCP request message, the AC/BNG receives the DHCP request message sent by the UE, and then determines to locally allocate the IP address to the UE according to the slotted service offload information associated with the UE MAC address. Then, the remaining steps of the DHCP process are performed to complete the process of assigning an IP address to the UE. In this case, you can also bind the IP address to the MAC address.

Step 1017: Step 1018: If the UE sends a route request message, after receiving the route request message sent by the UE, the AC/BNG decides to allocate the IP address allocation to the UE locally according to the slotted service offload information associated with the UE MAC address. Then, an acknowledgment message is sent to the UE, and the process of allocating an IP address to the UE is completed. In this case, you can also bind the IP address to the MAC address.

Step 1019: When the BNG/AC receives the uplink data, it also finds the associated service type as a slotted service offload according to the UE MAC or the source IP address, and then performs specific data forwarding.

The foregoing embodiment is directed to the AP/RG as an EAP Authenticator. If the AC/BNG is an EAP Authenticator, then Step 1001 - Step 1013 is replaced by Step 501 - Step 513. The processing of the other steps is the same as that of this embodiment.

Example 9

The embodiment is based on the architecture of the embodiment 1. In the slotted service offload scenario, the TWAG supports assigning a local IP address to the UE. For details, see the process shown in Figure 11. The process includes the following steps:

Step 1101 - Step 1113: It is identical to the foregoing steps 601 - 613.

Step 1114 - Step 1115: It is identical to the foregoing Step 614 - Step 615.

Step 1116 - Step 1117: If the UE sends a DHCP request message, the AC/BNG root The associated GRE tunnel is found according to the UE MAC address, and the message is sent to the TWAG' through the GRE tunnel. After receiving the GRE message, the TWAG' decapsulates and obtains the DHCP request message sent by the UE, and the slot is associated according to the UE MAC address. The service offload information determines that the IP address allocation is assigned to the UE locally. Then, the remaining steps of the DHCP process are performed to complete the process of assigning an IP address to the UE. At this time, TWAG can bind the IP address to the MAC address.

Step 1118 - Step 1121: If the UE sends a route request message, the AC/BNG receives the route request message sent by the UE, finds the associated GRE tunnel according to the UE MAC address, and sends a message to the TWAG' through the GRE tunnel. The packet is a Layer 2 packet that encapsulates the routing message. After receiving the GRE packet, the TWAG' obtains the Layer 2 packet and obtains the UE MAC address from the Layer 2 protocol header of the packet, and then associates the MAC address according to the UE. The slotted service offload information determines that the UE is assigned an IP address assignment. Then, an acknowledgment message is sent to the UE, and the process of allocating an IP address to the UE is completed. In this case, you can also bind the IP address to the MAC address.

Generally, the BNG/AC supports the collection of the charging information based on the UE and reports it to the WLAN AAA for charging. In this embodiment, the TWAG can also support the collection of the charging information and report it to the WLAN. AAA performs billing. Therefore, when TWAG' assigns an IP address to the UE (for example, at the same time as TWAG, when step 1116 or 1120 is performed), a charging request (start) message is sent to the WLAN AAA, and then the WLAN AAA replies to the charging response (start) message. In this implementation, the TWAG performs specific service offloading, and the TWAG, the calculated charging information is the total charging information or the independent charging information of the service data of the 3GPP UE accessing the EPC and the direct service offload. For details, refer to the related description of Embodiment 2. These billing information can be used as a billing reference between operators.

Step 1122: When the BNG/AC receives the uplink data, the associated GRE tunnel is found according to the UE MAC or the source IP address, and the packet is sent to the TWAG' through the GRE tunnel. The data packet can be the encapsulated Layer 2 datagram. After the GRE message is received, the TWAG obtains the GRE message, decapsulates the data packet, and then finds the data according to the UE MAC address or the UE IP address. The business type to which it is associated is a split traffic, and then specific data forwarding is performed.

When the TWAG receives the downlink data, it follows the reverse process of the uplink data forwarding path and forwards it to the UE.

The foregoing embodiment is directed to the AP/RG as an EAP authenticator. If the AC/BNG is an EAP authenticator, then step 1101 - step 1113 is replaced by step 501-513. The processing of the other steps is the same as that of this embodiment.

In this embodiment, when the TWAG' receives the detachment related message of the UE leaving the network, it sends a charging request (termination) message to the WLAN AAA, and then the WLAN AAA replies to the charging response (terminating) message.

Example 10

The embodiment is based on the architecture of the embodiment 2. In the slotted service offload scenario, the TWAG supports assigning a local IP address to the UE. For details, see the process shown in Figure 12. In this embodiment, the process is similar to that of the embodiment 9, except that the EAP authentication process between the TWAG' and the 3GPP AAA does not need to be transited by the WLAN AAA, but directly communicates with each other. For other procedures, refer to the related description of Embodiment 9. For details, refer to the process shown in Figure 12. The process includes the following steps: Step 1201 - Step 1213: The same as Step 1001 - Step 1013, refer to the foregoing Step 1001 - Step 1013.

Step 1214 - Step 1215: The same as the foregoing Step 1014 - Step 10115, see Step 1014 - Step 1015.

Step 1216 - Step 1217: If the UE sends a DHCP request message, the AC/BNG finds the associated GRE tunnel according to the UE MAC address, and sends the message to the TWAG' through the GRE tunnel. After receiving the GRE message, the TWAG' decapsulates the packet. After the DHCP request message sent by the UE, according to the slotted service offload information associated with the UE MAC address, the local UE is determined to be With IP address allocation. Then, the remaining steps of the DHCP process are performed to complete the process of assigning an IP address to the UE. At this time, TWAG can bind the IP address to the MAC address.

Step 1218 - Step 1221: If the UE sends a route request message, the AC/BNG receives the route request message sent by the UE, finds the associated GRE tunnel according to the UE MAC address, and sends a message to the TWAG' through the GRE tunnel. The packet is a Layer 2 packet that encapsulates the routing message. After receiving the GRE packet, the TWAG' obtains the Layer 2 packet and obtains the UE MAC address from the Layer 2 protocol header of the packet, and then associates the MAC address according to the UE. The slotted service offload information determines that the UE is assigned an IP address assignment. Then, an acknowledgment message is sent to the UE, and the process of allocating an IP address to the UE is completed. In this case, you can also bind the IP address to the MAC address.

Step 1222: When the BNG/AC receives the uplink data, the associated GRE tunnel is found according to the UE MAC or the source IP address, and the packet is sent to the TWAG' through the GRE tunnel. The data packet can be the encapsulated Layer 2 datagram. The TWAG, after receiving the GRE packet, decapsulates and obtains the data packet, and then finds the associated service type as a slotted service traffic according to the UE MAC address or the UE IP address, and then executes the specific service. Data forwarding.

The above embodiment is for the AP/RG as the EAP authenticator. If the AC/BNG is the EAP authenticator, then the step 1201 - step 1213 is replaced by the step 501 - step 513. The processing of the other steps is the same as that of this embodiment.

NOTE: The foregoing embodiment 2, 3, 6, and 7 only describe the scenario in which the service type is EPC access. The embodiments 4, 8, 9, and 10 only describe the scenario in which the service type is slotted. When the AAA authorization is both, the AC/BNG supports the combined operations of the above embodiments 2, 3, 6, 7 and the embodiments 4, 8, 9, 10.

FIG. 13 is a schematic structural diagram of a functional network element according to an embodiment of the present invention. As shown in FIG. 13, the functional network element in the embodiment of the present invention is applied to a trusted WLAN access network and a 3GPP core network. Specifically, the receiving unit 130 and the forwarding unit 131 and/or the transmitting unit (not shown in FIG. 13, dedicated to charging, are optional functional units), where:

The receiving unit 130 is configured to receive an authentication request message sent by the UE when accessing the WLAN access network, and receive an authentication response message sent by the AAA, and/or receive the access network element of the WLAN access network. Sending an IP address request message; and/or receiving an AAA charging response message sent by an AAA server or an AAA proxy of the WLAN access network;

The forwarding unit 131 is configured to forward the authentication request message to the AAA, and forward the authentication response message to an access network element of the WLAN access network;

The sending unit is configured to send an AAA charging request message to the AAA of the WLAN access network when the receiving unit 130 receives the AAA charging response message sent by the AAA server or the AAA proxy of the WLAN access network.

The access network element of the WLAN access network includes a BNG/AC.

Those skilled in the art will appreciate that the implementation functions of the various processing units in the functional network elements shown in Figure 13 can be understood with reference to the related description of the foregoing routing methods. Those skilled in the art should understand that the functions of the processing units in the functional network element shown in FIG. 13 can be implemented by a program running on the processor, or can be implemented by a specific logic circuit.

FIG. 14 is a schematic structural diagram of another functional network element according to an embodiment of the present invention. As shown in FIG. 14, the functional network element in the embodiment of the present invention is applied to a network in which a trusted WLAN access network and a 3GPP core network are integrated. The method includes: a receiving unit 140, an obtaining unit 141, and a determining unit 142, among them:

The receiving unit 140 is configured to receive an authentication response message sent by the AAA.

An obtaining unit 141, configured to obtain a business type of the decision;

The determining unit 142 is configured to determine, according to the service type information associated with the UE, whether to allocate a local IP to the UE, and implement routing to the UE.

Based on the function network element shown in FIG. 14, the example function network element further includes: an allocating unit (not shown in FIG. 14);

When the service type is a slotted service offload, after the receiving unit 140 receives the IP address request message, the allocating unit allocates a local IP to the UE.

Those skilled in the art will appreciate that the implementation functions of the various processing units in the functional network elements shown in Figure 14 can be understood with reference to the related description of the methods of routing described above. Those skilled in the art should understand that the functions of the processing units in the functional network element shown in FIG. 14 can be implemented by a program running on the processor, or can be implemented by a specific logic circuit.

The above is only the preferred embodiment of the present invention and is not intended to limit the scope of the present invention.

Claims

Claim

A routing method, which is applied to a wireless local area network WLAN access network and a third generation partnership project 3GPP core network convergence network; a functional network element is disposed between the WLAN access network and the 3GPP core network The method includes:

When the user equipment UE is accessed by the WLAN access network, the function network element forwards the authentication request message sent by the UE to the authentication and authorization charging AAA, and forwards the message to the access network element of the WLAN access network. An authentication response message sent by the AAA; and/or, the function network element receives an IP address request message sent by the access network element of the WLAN access network.

2. The method according to claim 1, wherein the functional network element is located in the WLAN access network or a 3GPP core network.

3. The method according to claim 1, wherein the AAA is an AAA server or an AAA proxy of the WLAN access network, or an AAA server or an AAA proxy of the 3GPP core network.

The method according to claim 1, wherein the function network element and the access network element of the WLAN access network establish a general route encapsulation GRE tunnel or a multi-protocol label switching MPLS tunnel.

5. The method according to claim 1, wherein the method further comprises:

6. The method according to claim 1, wherein the method further comprises:

7. The method according to claim 6, wherein the method further comprises:

The method according to claim 6 or 7, wherein the service type comprises: allowing access to the 3GPP core network, and/or slotted service offloading, or denying access.

The method according to any one of claims 1 to 8, wherein the access network element of the WLAN access network comprises a border network node BNG/access controller AC.

10. The method of claim 9, wherein the IP address request message is a DHCP message or a route request message.

The method according to claim 9, wherein, when the functional entity is connected to the AAA server or the AAA proxy of the WLAN access network, the function entity supports the collection of the charging information and reports the AAA charging message. An AAA server or AAA proxy to the WLAN access network.

The method of claim 11, wherein the AAA charging message comprises a Radius charging message or a Diameter charging message.

13. The method according to claim 9, wherein the WLAN access network comprises an architecture network defined by a fixed broadband forum BBF.

A routing method is applied to a network in which a WLAN access network and a 3GPP core network are integrated; a functional network element is disposed in the fused network; the method includes:

The method according to claim 14, wherein the AAA is an AAA server or an AAA proxy of the WLAN access network, or an AAA server of the 3GPP core network.

16. The method of claim 15, wherein the functional network element is located in the WLAN access network or the 3GPP core network.

17. The method according to claim 16, wherein the service type comprises: allowing access to the 3GPP core network, and/or slotted service offloading, or denying access.

The method according to claim 17, wherein, when the service type is a slotted service, the function network element allocates a local IP to the UE after receiving the IP address request message.

The method of claim 18, wherein the IP address request message is a DHCP message or a route request message.

A functional network element, which is applied to a network in which a WLAN access network and a 3GPP core network are integrated; the function network element includes: a receiving unit, a forwarding unit, and/or a sending unit, where:

And a sending unit, configured to send an AAA charging request message to an AAA server or an AAA proxy of the WLAN access network.

The WLAN access network access gateway according to claim 20, wherein the WLAN access network access gateway is located in the WLAN access network or a 3GPP core network.

The WLAN access network access gateway according to claim 20, wherein the AAA is an AAA server or an AAA proxy of the WLAN access network, or an AAA server or an AAA proxy of the 3GPP core network.

The WLAN access network access gateway according to claim 20, wherein a GRE tunnel or an MPLS tunnel is established between the WLAN access network access gateway and the access network element of the WLAN access network.

The WLAN access network access gateway according to any one of claims 20 to 23, wherein the access network element of the WLAN access network comprises a BNG/AC.

25. The method of claim 20 wherein the AAA charging message comprises Radius Billing message, or Diameter billing message.

A functional network element, which is applied to a network in which a WLAN access network and a 3GPP core network are integrated; the WLAN access network access gateway includes: a receiving unit, an obtaining unit, and a determining unit, where:

a receiving unit, configured to receive an authentication response message sent by the AAA;

Get the unit, set to get the business type of the decision;

The WLAN access network access gateway according to claim 26, wherein the AAA is an AAA server or an AAA proxy of the WLAN access network, or an AAA server or an AAA proxy of the 3GPP core network.

The WLAN access network access gateway according to claim 26, wherein the WLAN access network access gateway is located in the WLAN access network or the 3GPP core network.

The WLAN access network access gateway according to claim 26, wherein the service type comprises: allowing access to the 3GPP core network, and/or slotted service offloading, or denying access.

The WLAN access network access gateway according to claim 26, wherein the WLAN access network access gateway further comprises: