WO2014169781A1

WO2014169781A1 - Method and system for terminating connection by user

Info

Publication number: WO2014169781A1
Application number: PCT/CN2014/075158
Authority: WO
Inventors: 周星月; 尤建洁
Original assignee: 中兴通讯股份有限公司
Priority date: 2013-04-16
Filing date: 2014-04-11
Publication date: 2014-10-23
Also published as: CN104113930A; CN104113930B

Abstract

A method and system for terminating a connection by a user, the method comprising: a Residential Gateway (RG) of a fixed network, upon receiving information of terminating a connection from a User Equipment (UE), requests connection termination from an Access Network (AN) of an international standards organization Broadband Forum (BBF), and the Access Network (AN) of the Broadband Forum (BBF) releases the resource information allocated for the UE. In an embodiment of the present invention, when the UE initiates termination of a connection, a network side releases the resource information related to the UE in a timely manner, thus saving network resource.

Description

Method and system for realizing user termination connection

Technical field

The present invention relates to mobile communication technologies, and more particularly to a method and system for implementing user termination connections in a fixed network. Background technique

With the increasing maturity and popularity of wireless local area network (WLAN) access technologies and the demand for high-speed wireless access by users, domestic and foreign operators are vigorously developing WLAN services. As a means of diversion of 2G and 3G, WLAN services are becoming more and more important. WLAN access is a supplementary access method for fixed networks. How to effectively grasp and manage the access of users through WLAN has become the key to developing WLAN value-added services. At the same time, this will help operators to optimize their networks.

The 3rd Generation Partnership Project (EPS) evolved packet system (EPS, Evolved Packet System) by the Evolved Universal Terrestrial Radio Access Network (E-UTRAN, Evolved Universal Terrestrial Radio Access Network) Mobile Management Unit (MME, Mobility Management Entity), Serving Gateway (S-GW), Packet Data Network Gateway (P-GW, Packet Data Network Gateway, also referred to as PDN-GW), Home Subscriber Server (HSS, The Home Subscriber Server ), Policy and Charging Rules Function (PCRF) entity and other supporting nodes.

At present, the International Standards Organization Broadband Forum (BBF, Broadband Forum) and 3GPP are working on the standardization of Fixed Network and Mobile Network Convergence (FMC), including 3GPP User Equipment (UE, User Equipment) through residential Gateway (RG, Residential Gateway) authentication, address allocation, and policy control from BBF network access. FIG. 1 is a schematic diagram of a fixed network composition of the related art, as shown in FIG. 1. During the authentication process, the 3GPP UE acts as the 802. IX client to initiate access authentication to the RG. At this time, the RG acts as the 802. IX authenticator and the remote authentication dial in user service (RADIUS). Authentication, Authorization, Accounting (AAA, Authentication Authorization Accounting) server (that is, the trusted WLAN authentication authorized charging agent) (TWAP, Trusted WLAN AAA Proxy)) initiates an authentication request. In the address request process, the address request message initiated by the 3GPP UE requests an IP address from the PDN-GW via a broadband network gateway device (BNG, Broadband Network Gateway). The S2a session is established between the BNG and the PDN-GW, and is implemented by a General Packet Radio Service Tunneling Protocol (GTP, GPRS Tunneling Protocol, where GPRS is a general packet radio service) or a Proxy Mobile Internet Protocol (PMIP) tunnel.

RADIUS is a client/server (C/S) architecture protocol. Its client is initially a network access server (NAS, Net Access Server). Now any computer running RADIUS client software can become a RADIUS client. end. The RADIUS protocol authentication mechanism is flexible, and can use multiple methods such as password authentication protocol (PAP), peer-to-peer protocol query authentication handshake protocol (CHAP), or Unix login authentication. RADIUS is an extensible protocol, and all the work it does is based on a vector of attribute length values Attribute-Length-Value. RADIUS also supports vendors to extend vendor-specific attributes. Because the RADIUS protocol is simple and clear, it can be expanded, so it has been widely used, including ordinary telephone Internet access, asymmetric digital subscriber loop (ADSL) Internet access, residential broadband Internet access, IP telephony, and virtual private dial-up network services based on dial-up users (VPDN, Virtual Private Dialup Networks), mobile phone prepaid services, etc. The IEEE 802. lx standard is a port-based standard for access authentication for wireless networks and RADIUS for authentication. The RADIUS proxy (Proxy) provides routing of RADIUS messages between the RADIUS Client Access server and the RADIUS server that performs user authentication, authorization, and accounting for connection attempts.

In the related art, each user BNG needs to establish an S2a session with the PDN-GW. In order to support the scenario in the existing network, all BNG devices need to be upgraded, which has a great impact on the existing network. In order to solve this problem, a fixed network access gateway is currently referenced, for example, a trusted WLAN access gateway (T WAG, Trusted WLAN Access Gateway), a schematic diagram of the network structure after the introduction of T WAG is shown in Figure 1. After the introduction of the fixed-line access gateway, there is no need to perform a large-scale upgrade of the BNG equipment, thereby minimizing the impact on the existing network.

In the related art, the user equipment may send a de-association notification message or a deregistration notification message defined by IEEE Std 802.11 to the AP/RG (common AP and RG in the BBF network) to terminate the connection. However, in the prior art, the AP/RG cannot notify the network side to delete the connection association information related to the user equipment. Interest, causing a waste of network resources on hold.

Summary of the invention

The present invention provides a method and system for implementing a user termination connection. When a user equipment initiates a termination connection, the network side can release resource information related to the user equipment in time, thereby saving network resources.

In order to solve the above technical problem, the present invention discloses a method for implementing a user termination connection, including: after receiving the termination connection information of the user equipment, the residential gateway RG requests termination of the connection to the BBF access network of the International Standards Organization Broadband Forum;

The BBF access network releases resource information allocated for the user equipment.

The RG requests the BBF access network to terminate the connection as: The RG sends an accounting termination message to the BBF access network, or creates a new termination notification message.

The RG requests the BBF access network to terminate the connection as:

Sending, by the RG, a charging stop request to the trusted WLAN access gateway TWAG in the BBF access network, where the charging stop request carries a user identifier and/or a session identifier; the TWAG to the BBF access network The TWAP authorization authorization charging agent TWAP sends a charging stop request, and the charging stop request carries the user identifier, and/or the session identifier, and/or the IP address of the user equipment; the TWAP returns the charging to the TWAG Stop responding; TWAG returns a billing stop response to RG.

The resource information allocated by the BBF access network for the user equipment is:

The TWAG in the BBF access network interacts with the packet data network gateway PDN-GW in the BBF access network to move the Internet Protocol/General Packet Radio Service Tunneling Protocol PMIP/GTP signaling, delete the S2a session, and release the GTP/PMIP tunnel. .

The method also includes accessing the user equipment before;

After the authentication and authorization in the user equipment is successfully accessed, the method further includes: the RG is

The TWAG sends a charging start request carrying a user identifier and/or a session identifier;

After the accessing the PMIP/GTP command in the user equipment, establishing the S2a session and the PMIP/GTP tunnel, the method further includes: sending, by the TWAG, the TWAP to carry the user identifier and/or Or a session identifier, and a charging start request for an IP address successfully assigned to the user equipment;

The TWAP returns a charging start response to the TWAG, and the TWAG returns a charging start port to the RG.

The RG requests the BBF access network to terminate the connection as:

The RG sends a termination notification message to the TWAG in the BBF access network, where the termination notification message carries a session/connection termination indication, and a user identifier and/or a session identifier; the TWAG accesses the BBF after receiving the termination notification. The TWAP in the network sends a charging stop request, and the charging stop request carries a user identifier and/or a session identifier.

The TWAP returns a charging stop response to the TWAG, and the TWAG returns a final acknowledgement message to the RG; the TWAG interacts with the PDN-GW in the BBF access network to exchange PMIP/GTP signaling, deletes the S2a session, and releases the GTP/PMIP tunnel. .

The method further includes: accessing the user equipment; after accessing the interactive PMIP/GTP command in the user equipment, establishing an S2a session and a PMIP/GTP tunnel, the method further includes:

The TWAG sends a charging start request carrying the user identifier and/or the session identifier and the IP address successfully assigned to the user equipment to the TWAP; the TWAP returns the charging start port to the TWAG.

The method also includes accessing the user equipment before;

After the access authorization in the user equipment is successful, the method further includes: sending, by the RG, a charging start request carrying a user identifier and/or a session identifier to the TWAP, where the TWAP returns a charging start response to the RG;

After the accessing the PMIP/GTP command in the user equipment, establishing the S2a session and the PMIP/GTP tunnel, the method further includes: sending, by the TWAG in the BBF access network, the user identifier and/or the session identifier to the TWAP, And an accounting start request for the IP address successfully assigned to the user equipment; the TWAP returns a charging start response to the TWAG;

At the same time, after receiving the charging start request sent by the RG and the TWAG respectively, the TWAP associates or binds the corresponding session according to the user identifier carried in the message. The RG requests the termination of the connection to the BBF access network as follows: The RG sends a charging stop request to the TWAP in the BBF access network, where the charging stop request carries the user identifier and/or the session identifier.

The TWAP returns a charging stop response to the RG; the TWAP initiates a remote user dialing authentication system RADIUS interrupt connection request to the TWAG in the BBF access network according to the association or binding result saved by the TWAP;

The TWAG in the BBF access network initiates a charging stop request to the TWAP, and the TWAP returns a charging stop response to the TWAG;

The TWAG interacts with the PDN-GW in the BBF access network to remove PMIP/GTP signaling, deleting

S2a session, releasing the GTP/PMIP tunnel.

The method also includes accessing the user equipment before;

After the accessing the PMIP/GTP command in the user equipment, establishing the S2a session and the PMIP/GTP tunnel, the method further includes: sending, by the TWAG in the BBF access network, the user identifier and/or the session identifier to the TWAP, And an accounting start request for the IP address successfully assigned to the user equipment; the TWAP returns a charging start response to the TWAG.

The RG requests the termination of the connection to the BBF access network as follows: the RG sends a termination notification message to the TWAP in the BBF access network, where the termination notification message carries the session/connection termination indication, and the user identifier and/or the session identifier. ;

The TWAP associates or binds the user pointed to in the termination notification message from the RG

The user pointed to in the billing start request sent by TWAG.

Returning, by the TWAP, a termination confirmation message to the RG; the TWAP initiating a RADIUS interrupt connection request to the TWAG in the BBF access network according to the association or binding result saved by the TWAP; the TWAG initiating a charging stop request to the TWAP, TWAP returns a charging stop response to TWAG;

The TWAG exchanges PMIP/GTP signaling with the PDN-GW in the BBF access network, deletes the S2a session, and releases the GTP/PMIP tunnel. The present invention also provides a system for implementing a user termination connection, including at least a user equipment, an RG, and a BBF access network, where

RG, set to: receive the terminating connection information from the user equipment, request the terminal connection to the BBF access network; and set the BBF access network to: release the resource information allocated for the user who terminates the connection.

The BBF access network includes at least TWAG, PDN-GW, and TWAP;

The RG is configured to: receive the terminating connection information from the user equipment, send a charging stop request to the TWAG, and carry the user identifier and/or the session identifier in the charging stop request;

TWAP, set to: return the charging stop response to TWAG;

TWAG, configured to: send a charging stop request to the TWAP, carry the user identifier, and/or the session identifier, and/or the IP address of the user equipment in the charging stop request; return a charging stop response to the RG; receive the The TWAP charging stops responding, interacts with the PDN-GW for PMIP/GTP signaling, deletes the S2a session, and releases the GTP/PMIP tunnel.

The RG is further configured to: after the access authorization in the user equipment is successfully accessed, send a charging start request carrying the user identifier and/or the session identifier to the TWAP; the TWAP is further set to: Returning the charging start response; returning the charging start response to the TWAP;

The TWAG is further configured to: after accessing the PMIP/GTP command in the user equipment, establish an S2a session and a PMIP/GTP tunnel, and then identify the IMSI and/or the session identifier by using a charging start request, and The IP address successfully assigned by the user equipment is sent to the TWAP.

The BBF access network includes at least TWAG, PDN-GW, and TWAP;

The RG is configured to: receive termination connection information from the user equipment, and send a termination notification message to the TWAG, where the termination notification message carries a session/connection termination indication, and a user identifier and/or a session identifier;

TWAG, configured to: receive the termination notification, send a charging stop request to the TWAP, carry the user identifier and/or the session identifier in the charging stop request; return a final confirmation message to the RG; and interact with the PDN-GW for PMIP/GTP signaling , delete the S2a session, release the GTP/PMIP tunnel;

TWAP, set to: Return the billing stop response to TWAG.

The TWAG is further configured to: access an interactive PMIP/GTP command in the user equipment, After the S2a session and the PMIP/GTP tunnel are established, the charging start request is sent to the TWAP carrying the user identifier and/or the session identifier, and the IP address successfully assigned to the user equipment;

The TWAP is further configured to: return a charging start response to the TWAG.

The BBF access network includes at least TWAG, PDN-GW, and TWAP;

The RG is further configured to: after the access authorization in the user equipment is successfully accessed, send, to the TWAP, a charging start request that carries a user identifier and/or a session identifier;

The TWAP is configured to: return a charging start response to the RG; return a charging start response to the TWAG; receive the charging start request sent from the RG and the TWAG, respectively, according to the user identifier associated or bound in the message Conversation

The TWAG is configured to: after accessing the PMIP/GTP command in the user equipment, establishing an S2a session and a PMIP/GTP tunnel, requesting the user identifier and/or the session identifier through the charging start request, and the user equipment The successfully assigned IP address is sent to TWAP.

The RG is further configured to: receive the terminating connection information from the user equipment, send a charging stop request to the TWAP, and carry the user identifier and/or the session identifier in the charging stop request;

The TWAP is further configured to: return a charging stop response to the RG; stop responding according to the self-storage fee;

The TWAG is further configured to: initiate a charging stop request to the TWAP; interact with the PDN-GW for PMIP/GTP signaling, delete the S2a session, and release the GTP/PMIP tunnel.

The BBF access network includes at least TWAG, PDN-GW, and TWAP;

The TWAG is configured to: after accessing the PMIP/GTP command in the user equipment, establish an S2a session and a PMIP/GTP tunnel, send the user identifier and/or the session identifier to the WRAP, and succeed for the user equipment. The billing start request of the assigned IP address;

The TWAP is set to: return a charging start response to the TWAG.

The RG is further configured to: receive termination connection information from the user equipment, and send a termination notification message to the TWAP, where the termination notification message carries a session/connection termination indication, and a user identifier and/or a session identifier; The TWAP is further configured to: return a termination confirmation message to the RG; associate or bind the user pointed to in the termination notification message from the RG and the user pointed to in the charging start request sent by the TWAG; according to the self The saved association or binding result, initiates a RADIUS interrupt connection request to the TWAG; returns a charging stop response to the TWAG;

The technical solution of the present application provides that the residential gateway in the fixed network receives the terminal connection information of the user equipment, and then requests the BBF access network to terminate the connection, and the BBF access network releases the resource information allocated for the user equipment. When the user equipment initiates the terminating connection, the network side releases the resource information related to the user equipment in time, thereby saving network resources. BRIEF abstract

The drawings are intended to provide a further understanding of the invention, and are intended to be illustrative of the invention. In the drawing:

1 is a schematic diagram of the composition of a fixed network in the related art;

2 is a flowchart of a method for implementing a user termination connection according to an embodiment of the present invention;

3 is a schematic flowchart of a first embodiment of implementing a user termination connection according to the present invention;

4 is a schematic flowchart of a second embodiment of implementing a user termination connection according to the present invention;

FIG. 5 is a schematic flowchart diagram of a third embodiment of implementing a user termination connection according to the present invention; FIG.

6 is a schematic flowchart of a fourth embodiment of implementing a user termination connection according to the present invention;

FIG. 7 is a schematic structural diagram of a system for implementing a user termination connection according to an embodiment of the present invention. Preferred embodiment of the invention

2 is a flowchart of a method for implementing a user termination connection according to the present invention. As shown in FIG. 2, the method of the present invention includes the following steps:

Step 200: After receiving the terminal connection information of the user equipment, the residential gateway accesses the BBF access network. Request to terminate the connection.

In this step, the RG receives the termination connection information of the user equipment, that is, the de-association notification message or the cancellation notification message defined by IEEE Std 802.11. The RG may request termination of the connection to the BBF access network through an existing charging termination message or a new termination notification message.

According to whether TWAG is used as the RADIUS proxy, the implementation of the RG to terminate the connection to the BBF access network in this step includes the following two methods:

In the first mode, when the TWAG is used as the RADIUS proxy, the RG requests the BBF access network to terminate the connection.

When the RG requests termination of the connection to the BBF access network through the existing charging termination message, the RG sends an Accounting Stop Request (Accounting-Stop Request) to the TWAG, and the charging stop request carries a user identifier such as an International Mobile Subscriber Identity ( The IMSI) and/or the session identifier, the TWAG sends a charging stop request to the TWAP, and the charging stop request carries the user identifier, and/or the session identifier, and/or the IP address of the user equipment. In this manner, in order to improve the entire access process, the existing user equipment access process further includes: After the authentication and authorization succeeds, the RG sends a user identifier, such as an International Mobile Subscriber Identity (IMSI), to the TWAG. And/or session-initiated charging start request; after interacting with the PMIP/GTP command, establishing an S2a session and a PMIP/GTP tunnel, the TWAG requests the user identity such as an International Mobile Subscriber Identity (IMSI) and/or session through a charging start request. The identifier, and the IP address successfully assigned to the user equipment are sent to the TWAP; after that, the TWAP returns a charging start response to the TWAG, and the TWAG returns a charging start response to the RG.

When the RG requests termination of the connection to the BBF access network by creating a new termination notification message, the RG sends a termination notification message to the TWAG, and the termination notification message carries a session/connection termination indication, and a user identifier such as an International Mobile Subscriber Identity (IMSI) and / or session identifier; After receiving the termination notification, the TWAG sends a charging stop request to the TWAP, and the charging stop request carries a user identifier such as an International Mobile Subscriber Identity (IMSI) and/or a session identifier. In this way, in order to improve the entire access process, the existing user equipment access process further includes: After the interaction of the PMIP/GTP command, establishing the S2a session and the PMIP/GTP tunnel, the TWAG starts the request through the charging. The user identity, such as an International Mobile Subscriber Identity (IMSI) and/or session identifier, and the IP address successfully assigned to the user equipment are sent to the TWAP; thereafter, the TWAP returns a billing start response to the TWAG.

In the second mode, during the access process of the user equipment, the RG directly interacts with the TWAP, that is, When TWAG is used as the RADIUS proxy, the implementation of the RG to terminate the connection to the BBF access network includes:

When the RG requests termination of the connection to the BBF access network through the existing charging termination message, the RG sends a charging stop request to the TWAP, and the charging stop request carries a user identifier such as an International Mobile Subscriber Identity (IMSI) and/or a session. Logo. In this manner, in order to improve the entire access process, the existing user equipment access process further includes: after the authentication and authorization succeeds, the RG sends the user identifier, such as an International Mobile Subscriber Identity (IMSI), to the TWAP. And/or the charging start request of the session identifier, the TWAP returns a charging start response to the RG; after the PMIP/GTP command is established, the S2a session and the PMIP/GTP tunnel are established, the TWAG requests the user identity as an international mobile user through the charging start request. An identification code (IMSI) and/or a session identifier, and an IP address successfully assigned to the user equipment are sent to the TWAP; thereafter, the TWAP returns a billing start response to the TWAG.

When the RG requests termination of the connection to the BBF access network by creating a new termination notification message, the RG sends a termination notification message to the TWAP, and the termination notification message carries a session/connection termination indication, and a user identifier such as an International Mobile Subscriber Identity (IMSI) and / or session ID. In this way, in order to improve the entire access process, the existing user equipment access process further includes: After the interaction of the PMIP/GTP command, establishing the S2a session and the PMIP/GTP tunnel, the TWAG starts the request through the charging. The user identifier, such as an International Mobile Subscriber Identity (IMSI) and/or session identifier, and the IP address successfully assigned to the user equipment are sent to the TWAP; after that, the TWAP returns the billing start port to the TWAG.

Step 201: The BBF access network releases resource information allocated for the user equipment.

When the RG sends a charging stop request to the TWAP via the TWAG, the step specifically includes: the TWAP returns an accounting stop response (Accouting-Stop Ack) to the TWAG; the TWAG returns a charging stop response to the RG; after that, the TWAG interacts with the PDN-GW. The PMIP/GTP signaling, the S2a session is deleted, and the GTP/PMIP tunnel is released. The specific implementation is not limited to the scope of protection of the present invention, and details are not described herein again.

When the RG sends a termination notification message to the TWAG, the step specifically includes: the TWAP returns a charging stop response to the TWAG, and the TWAG returns a final confirmation message to the RG; after that, the TWAG interacts with the PDN-GW to perform PMIP/GTP signaling, and deletes the S2a session. The GTP/PMIP tunnel is released, and the specific implementation is a technical means used by those skilled in the art, and is not intended to limit the scope of the present invention. I won't go into details here.

When the RG sends a charging stop request to the TWAP, the step specifically includes: the TWAP returns a charging stop response to the RG; the TWAP initiates a RADIUS Disconnect request to the TWAG, and the TWAG initiates an accounting stop request to the TWAP, the TWAP The TWAG returns the charging stop response. After that, the TWAG exchanges the PMIP/GTP signaling with the PDN-GW, deletes the S2a session, and releases the GTP/PMIP tunnel. The specific implementation is a technical means used by those skilled in the art, and is not used to limit the protection of the present invention. The scope is not repeated here; finally, TWAG returns a RADIUS interrupt connection response to TWAP.

When the RG sends a termination notification message to the TWAP, the step specifically includes: the TWAP returns a final confirmation message to the RG; the TWAP initiates a RADIUS Disconnect request to the TWAG, and the TWAG initiates an accounting stop request to the TWAP, and the TWAP returns to the TWAG. The charging stops responding. After that, the TWAG exchanges the PMIP/GTP signaling with the PDN-GW, deletes the S2a session, and releases the GTP/PMIP tunnel. The specific implementation is a technical means that is well-known to those skilled in the art, and is not intended to limit the scope of the present invention. This is not repeated here; finally, TWAG returns a RADIUS interrupt connection response to TWAP.

FIG. 3 is a schematic flowchart of a first embodiment of implementing a user termination connection according to the present invention. In the first embodiment, a mobile network user equipment (UE) is attached from a fixed network, and a UE performs an access authentication process, and an access node device of a fixed network. It is operated by the RG, and the RG is an authentication point and has a WLAN access point (AP, Access Point) function. After the authentication and authorization succeeds, the TWAG establishes an S2a session to the PDN-GW for the user equipment, and completes the connection of the user equipment to the 3GPP core network. In the first embodiment, the TWAG acts as a RADIUS proxy to route RADIUS messages to the TWAP for the user equipment, and the RG requests the BBF access network to terminate the connection through the existing charging termination message. As shown in Figure 3, the specific implementation is as follows:

Step 300: The user equipment discovers that the RG-covered wireless network performs an initial attach connection to the RG. Step 301: The user equipment initiates an extended authentication protocol (EAP) authentication and authorization to the RG, and the network side negotiates a packet connection of the 3GPP core network or a structured small world coverage network (NSWO) connection according to the user identifier, network capability, and subscription information (by TWAG). Bypass direct access to the internet).

Step 302: After the authentication and authorization succeeds, the RG sends a charging start request to the TWAG, where With a user ID such as IMSI, and/or session ID.

Step 303: The user equipment initiates a DHCP procedure to the TWAG to request an IP address to be assigned. Step 304: The PMIP/GTP signaling is exchanged between the TWAG and the PDN-GW to establish an S2a session and a PMIP/GTP tunnel, and the PDN-GW allocates an IP address of the user equipment, such as an IPv4/IPv6 address, to the TWAG.

Step 305: The TWAG sends a DHCP response message to the user equipment, and sends an IP address assigned by the PDN-GW.

Step 306 to step 307: The TWAG determines, according to the user identifier and/or the session identifier in the charging start request from the RG received in step 302, that the user access attribute is the user equipment of the mobile network and is connected back to the mobile core to which it belongs. The TWAG sends a charging start request carrying the user identity and/or the session identifier and the assigned IP address to the TWAP; the TWAP returns a charging start response to the TWAG after receiving the charging start request.

Step 308: The TWAG returns a charging start response corresponding to step 302 to the RG. This completes the establishment of the packet data connection.

Step 309: The user equipment sends a final connection request to the RG, for example, to associate the message.

( Disassociation ) Terminates the connection between the user equipment and the RG.

Step 310: The RG (that is, the RADIUS client) sends a RADIUS accounting stop request to the TWAG (that is, the RADIUS proxy).

Step 311 to Step 312: The TWAG and the TWAP (ie, the BBF AAA server) exchange RADIUS accounting stop request and the charging stop response.

It should be noted that, in step 310 to step 312, the RG sends a charging stop request to the trusted WLAN access gateway TWAG in the BBF access network, where the charging stop request carries the user identifier and/or the session identifier. The TWAG sends a charging stop request to the TWAP in the BBF access network, where the charging stop request carries the user identifier, and/or the session identifier, and/or the IP address of the user equipment.

Step 313: The TWAG returns to the RG the charging stop response corresponding to step 310.

Step 314: The TWAG and the PDN-GW exchange PMIP/GTP signaling, delete the S2a session, and release the GTP/PMIP tunnel. In this step, according to the user identifier carried in the delivered message, delete The S2a session established by the corresponding user equipment releases the GTP/PMIP tunnel. The specific implementations are not limited to the scope of protection of the present invention, and will not be further described herein.

4 is a schematic flowchart of a second embodiment of implementing a user termination connection according to the present invention. In the second embodiment, a mobile network user equipment UE is attached from a fixed network, and a UE performs an access authentication process. The access node device of the fixed network is used by the RG. Acting, and RG is the authentication point, with WLAN AP function. After the authentication and authorization succeeds, the TWAG establishes an S2a session to the PDN-GW for the user equipment, and completes the connection of the user equipment to the 3GPP core network. In the second embodiment, the TWAG acts as a RADIUS proxy to route RADIUS messages to the TWAP for the user equipment, and the RG requests the BBF access network to terminate the connection by creating a new termination notification message. As shown in Figure 4, the specific implementation is as follows:

Step 400: The user equipment discovers that the RG-covered wireless network performs an initial attach connection to the RG. Step 401: The user equipment initiates an extended authentication protocol (EAP) authentication and authorization to the RG, and the network side negotiates a packet connection of the 3GPP core network or a structured small world overlay network (NSWO) connection according to the user identifier, network capability, and subscription information (by TWAG). Bypass direct access to the internet).

Step 402: The user equipment initiates a DHCP process to the TWAG to request an IP address to be assigned. Step 403: Interacting PMIP/GTP signaling between the TWAG and the PDN-GW to establish an S2a session,

For the PMIP/GTP tunnel, the PDN-GW assigns the IP address of the user equipment such as the IPv4/IPv6 address to the TWAG.

Step 404: The TWAG sends a DHCP response message to the user equipment, and sends an IP address assigned by the PDN-GW.

Step 405 to step 406: The TWAG sends a charging start request carrying the user identifier and/or the session identifier and the assigned IP address to the TWAP; the TWAP returns a charging start response to the TWAG after receiving the charging start request message. This completes the establishment of the packet data connection.

Step 407: The user equipment sends a terminating connection request to the RG, for example, a disassociation message (Disassociation) to terminate the connection between the user equipment and the RG.

Step 408: The RG sends a termination notification message to the TWAG (ie, RADIUS Proxy) to notify

TWAG terminates the session. The termination notification message may be a RADIUS message, and the termination notification message carries a session/connection termination indication, and a user identifier such as an IMSI and/or a session identifier. Steps 409 to 410: Interworking RADIUS between TWAG and TWAP (BBF AAA) The billing stop request and billing stop responding.

Step 411: The TWAG returns a final confirmation message corresponding to step 408 to the RG.

Step 412: The TWAG and the PDN-GW exchange PMIP/GTP signaling, delete the S2a session, and release the GTP/PMIP tunnel. In this step, the S2a session established by the corresponding user equipment is deleted according to the user identifier carried in the message, and the GTP/PMIP tunnel is released. The specific implementations of the present invention are not intended to limit the scope of protection of the present invention, and are not described herein again.

FIG. 5 is a schematic flowchart of a third embodiment of implementing a user termination connection according to the present invention. As shown in FIG. 5, a mobile network user equipment UE is attached from a fixed network, and a UE performs an access authentication process, and an access network device of a fixed network is used by an RG. Acting, and RG is the authentication point, with WLAN AP function. After the authentication and authorization succeeds, the TWAG establishes an S2a session to the PDN-GW for the user equipment, and completes the connection of the user equipment to the 3GPP core network. In the third embodiment, there is no RADIUS Proxy between RG and TWAP. In the connection establishment process, TWAP receives RADIUS accounting request messages from the RG and TWAG for the same user equipment. The difference between the two RADIUS accounting request messages is that the RADIUS accounting request message from the TWAG is also It carries the IP address assigned to the user equipment. Assume that the RG requests the BBF access network to terminate the connection through the existing charging termination message. The specific implementation is as follows:

Step 500 to Step 501: The user equipment discovers that the RG-covered wireless network is initially attached to the RG. The user equipment initiates EAP authentication and authorization to the RG, and the network side negotiates a packet connection or a NSWO connection (directly accessing the Internet by TWAG bypass) of the 3GPP core network according to the user identifier, network capability, and subscription information.

Step 502 to step 503: After the authentication and authorization succeeds, the RG sends a charging start request to the TWAP, where the user identifier and/or the session identifier are carried.

Step 504: The user equipment initiates a DHCP procedure to the TWAG to request an IP address to be assigned. Step 505: The RADIUS access request and the RADIUS access accept message are exchanged between the TWAG and the TWAP.

Step 506: The TWAG and the PDN GW exchange PMIP/GTP signaling, establish an S2a session, a PMIP/GTP tunnel, and the PDN-GW allocates an IP address of the user equipment, such as an IPv4/IPv6 address, to the TWAG. Step 507: The TWAG sends a DHCP response message to the user equipment, and sends an IP address allocated by the PDN-GW.

Step 508 to step 509: The TWAG sends a charging start request carrying the user identifier and/or the session identifier and the assigned IP address to the TWAP; the TWAP returns a charging start response to the TWAG after receiving the charging start request. This completes the establishment of the packet data connection.

At the same time, after receiving the charging start request sent by the RG and the TWAG, the TWAP associates or binds the two sessions according to the user identifier; thus, when the subsequent TWAP receives the charging stop request from the RG, the TWAP A RADIUS interrupt connection request to the same user currently initiating the terminating session can be sent to the TWAG according to the local association or binding result.

Step 510: The user equipment sends a terminating connection request to the RG, for example, the association message terminates the connection between the user equipment and the RG.

Step 511 to step 512: The RG sends a RADIUS accounting stop request carrying the user identifier and/or the session identifier to the TWAP, and the TWAP returns a charging stop response to the RG.

Step 513: The TWAP sends the user equipment identifier or the session identifier carried in the RADIUS accounting stop request from the RG to the TWAG after the RADIUS interrupt connection request is sent. Here, the TWAP can send a RADIUS interrupt connection request to the TWAG to the same user who initiated the termination session according to the local association or binding result.

Step 514 to step 515: The TBAG and the TWAP exchange an accounting stop request and a charging stop response to terminate the charging.

Step 516: The TWAG and the PDN-GW exchange PMIP/GTP signaling, delete the S2a session, and release the GTP/PMIP tunnel. In this step, the S2a session established by the corresponding user equipment is deleted according to the user identifier carried in the message, and the GTP/PMIP tunnel is released. The specific implementations of the present invention are not intended to limit the scope of protection of the present invention, and are not described herein again.

Step 517: The TWAG returns a RADIUS interrupt connection response corresponding to step 513 to the TWAP. FIG. 6 is a schematic flowchart of a fourth embodiment of implementing a user termination connection according to the present invention. As shown in FIG. 6, a mobile network user equipment UE is attached from a fixed network, and a UE performs an access authentication process, and an access network device of a fixed network is used by an RG. Acting, and RG is the authentication point, with WLAN AP function. After the authentication and authorization succeeds, TWAG establishes an S2a session to the PDN-GW for the user equipment. The connection of the device to the 3GPP core network. In the third embodiment, there is no RADIUS Proxy between RG and TWAP. Assume that the RG requests the BBF access network to terminate the connection by creating a new termination notification message. The specific implementation is as follows:

Step 600 to Step 610: The user equipment discovers that the RG-covered wireless network is initially attached to the RG. The user equipment initiates EAP authentication and authorization to the RG, and the network side negotiates a packet connection or a NSWO connection (directly accessing the Internet by TWAG bypass) of the 3GPP core network according to the user identifier, network capability, and subscription information.

Step 602: The user equipment initiates a DHCP process to the TWAG to request an IP address to be assigned. Step 603: The RADIUS access request and the RADIUS access accept message are exchanged between the TWAG and the TWAP.

Step 604: The PMIP/GTP signaling is exchanged between the TWAG and the PDN-GW to establish an S2a session and a PMIP/GTP tunnel, and the PDN-GW allocates an IP address of the user equipment, such as an IPv4/IPv6 address, to the TWAG.

Step 605: The TWAG sends a DHCP response message to the user equipment, and sends an IP address assigned by the PDN-GW.

Step 606 to step 607: The TWAG sends a charging start request carrying the user identifier and/or the session identifier and the assigned IP address to the TWAP; the TWAP returns a charging start response to the TWAG after receiving the charging start request message. This completes the establishment of the packet data connection.

Step 608: The user equipment sends a terminating connection request to the RG, for example, a Disassociation message to terminate the connection between the user equipment and the RG.

Step 609 to step 610: The RG sends a RADIUS termination notification message to the TWAP to notify the TWAG to terminate the session. After receiving the RADIUS termination notification message, the TWAP returns a RADIUS termination confirmation message to the RG.

In this step, the TWAP associates or binds the termination notification message from the RG with the charging start request from the TWAG, that is, the TWAP points the user pointed to in the termination notification message from the RG and the charging start request sent by the TWAG. The user associates; thus, the TWAP can send a RADIUS interrupt connection request to the TWAG to the same user currently initiating the terminating session according to the local association or binding result. Step 611: The TWAP carries the user equipment identifier or the session identifier carried in the RADIUS accounting stop request from the RG, and sends the RADIUS interrupt request to the TWAG. Here, the TWAP can send a RADIUS interrupt connection request to the TWAG to the same user that currently initiates the terminating session according to the local association or binding result.

Step 612 to step 613: The charging stop request and the charging stop response are exchanged between the TWAG and the TWAP to terminate the charging.

Step 614: The TWAG and the PDN-GW exchange PMIP/GTP signaling, delete the S2a session, and release the GTP/PMIP tunnel. In this step, the S2a session established by the corresponding user equipment is deleted according to the user identifier carried in the message, and the GTP/PMIP tunnel is released. The specific implementations of the present invention are not intended to limit the scope of protection of the present invention, and are not described herein again.

Step 615: The TWAG returns a RADIUS interrupt connection response corresponding to step 513 to the TWAP. The present invention further provides a system for implementing a user termination connection, and a schematic diagram of a component structure thereof is shown in FIG. 7 , which includes at least a user equipment, an RG, and a BBF access network, where

The RG is configured to receive the terminating connection information from the user equipment, and request the terminal connection to the BBF access network. The BBF access network is used to release resource information allocated for the user who terminates the connection.

The BBF access network includes at least TWAG, PDN-GW, and TWAP, specifically,

The RG is configured to receive the terminating connection information from the user equipment, and send a charging stop request to the TWAG, where the charging stop request carries a user identifier such as an IMSI and/or a session identifier;

TWAP, used to return a charging stop response to the TWAG;

TWAG, configured to send a charging stop request to the TWAP, where the charging stop request carries the user identifier, and/or the session identifier, and/or the IP address of the user equipment; returns a charging stop response to the RG; receives the TWAP from the TWAP The charging stops responding, interacts with the PDN-GW for PMIP/GTP signaling, deletes the S2a session, and releases the GTP/PMIP tunnel.

In this way, in order to improve the entire access process, the existing user equipment access process further includes:

The RG is further configured to send, to the TWAP, a charging start request that carries a user identifier, such as an IMSI and/or a session identifier, after the authentication and authorization succeeds; TWAP, which is also used to return a charging start response to the RG; return a charging start response to the TWAP;

TWAG is also used to send the user identity IMSI and/or session identifier and the IP address successfully assigned to the user equipment to the TWAP through the charging start request after the interaction of the PMIP/GTP command, the establishment of the S2a session and the PMIP/GTP tunnel.

Or,

The RG is configured to receive the terminating connection information from the user equipment, and send a termination notification message to the TWAG, where the termination notification message carries a session/connection termination indication, and a user identifier such as an IMSI and/or a session identifier;

The TWAG is configured to receive a termination notification, send a charging stop request to the TWAP, and carry a user identifier such as an IMSI and/or a session identifier in the charging stop request; return a final confirmation message to the RG; and interact with the PDN-GW of the TWAG/PMIP/ GTP signaling, deleting the S2a session, releasing the GTP/PMIP tunnel;

TWAP, used to return the charging stop response to TWAG.

The TWAG is also used to send the user identifier, such as the IMSI and/or the session identifier, and the IP address successfully assigned to the user equipment to the TWAP through the charging start request after the interaction of the PMIP/GTP command, the establishment of the S2a session and the PMIP/GTP tunnel. ;

TWAP is also used to return a billing start response to TWAG.

Or,

The RG is further configured to send, to the TWAP, a charging start request that carries a user identifier, such as an IMSI and/or a session identifier, after the authentication and authorization succeeds;

TWAP is also used to return a charging start response to the RG; return a charging start response to the TWAG; receive a charging start request sent from the RG and the TWAG, respectively, and associate or bind the corresponding session according to the user identifier carried in the message. ; The TWAG is also used to send the user identifier, such as the IMSI and/or the session identifier, and the IP address successfully assigned to the user equipment to the TWAP through the charging start request after the interaction of the PMIP/GTP command, the establishment of the S2a session and the PMIP/GTP tunnel. ₀

In the process of implementing the user termination, the RG is configured to receive the terminating connection information from the user equipment, and send an accounting stop request to the TWAP, where the charging stop request carries a user identifier such as an IMSI and/or a session identifier.

TWAP, used to return a charging stop response to the RG; initiate a RADIUS interrupt connection request to the TWAG according to the association or binding result saved by itself; and return a charging stop response to the TWAG;

The TWAG is used to initiate a charging stop request to the TWAP; interact with the PDN-GW to perform PMIP/GTP signaling, delete the S2a session, and release the GTP/PMIP tunnel.

Or,

TWAP is also used to return a billing start response to TWAG.

In the process of implementing the user termination, the RG is configured to receive the termination connection information from the user equipment, send a termination notification message to the TWAP, and carry the session/connection termination indication, and the user identifier, such as the IMSI and/or the session identifier, in the termination notification message. ;

TWAP, used to return a finalization confirmation message to the RG; associating or binding the user pointed to in the termination notification message from the RG with the user pointed to in the charging start request sent by the TWAG; according to the association or binding saved by the self As a result, a RADIUS interrupt connection request is initiated to the TWAG; a charging stop response is returned to the TWAG;

The above is only a preferred embodiment of the present invention and is not intended to limit the scope of the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present invention, All should be included in the scope of protection of the present invention.

Industrial applicability

The technical solution of the present application provides that the residential gateway in the fixed network receives the terminal connection information of the user equipment, and then requests the BBF access network to terminate the connection, and the BBF access network releases the resource information allocated for the user equipment. When the user equipment initiates the terminating connection, the network side releases the resource information related to the user equipment in time, thereby saving network resources.

Claims

Claim

1. A method for implementing a user termination connection, comprising:

After receiving the terminating connection information of the user equipment, the RG requests the terminal to the international standard organization broadband BBF access network to terminate the connection;

2. The method according to claim 1, wherein the RG requests the BBF access network to terminate the connection: the RG sends a charging termination message to the BBF access network, or creates a new termination notification message.

3. The method according to claim 1, wherein the RG requests a termination connection to the BBF access network as:

The RG to the trusted wireless local area network WLAN access gateway in the BBF access network

The TWAG sends a charging stop request, and the charging stop request carries a user identifier and/or a session identifier; the TWAG sends a charging stop request to the trusted WLAN authentication and authorization charging agent TWAP in the BBF access network, The charging stop request carries a user identifier, and/or a session identifier, and/or an IP address of the user equipment; the TWAP returns a charging stop response to the TWAG; and the TWAG returns a charging stop response to the RG.

The method according to claim 3, wherein the releasing the resource information allocated by the BBF access network for the user equipment comprises:

The method according to claim 3 or 4, wherein the method further comprises accessing the user equipment;

After the authentication and authorization of the access to the user equipment is successful, the method further includes: sending, by the RG, a charging start request that carries a user identifier and/or a session identifier to the TWAG;

Establishing an S2a session and establishing an interactive PMIP/GTP command in the user equipment

After the PMIP/GTP tunnel, the method further includes: sending, by the TWAG, a charging start request that carries the user identifier and/or the session identifier, and the IP address successfully allocated by the user equipment to the TWAP; The TWAP returns a charging start response to the TWAG, and the TWAG returns the charging start port to the RG.

6. The method according to claim 1, wherein the RG requests a termination connection to the BBF access network as:

The method according to claim 6, wherein the BBF access network releases resource information allocated for the user equipment, including:

The method according to claim 6 or 7, wherein the method further comprises: accessing the user equipment; interacting with the PMIP/GTP command in the user equipment, establishing an S2a session and

After the PMIP/GTP tunnel, it also includes:

The method according to claim 1, wherein the method further comprises accessing the user equipment;

After the PMIP/GTP tunnel, the method further includes: the TWAG in the BBF access network sending, to the TWAP, a charging start request that carries a user identifier and/or a session identifier, and an IP address successfully allocated for the user equipment; TWAG returns the billing start response; At the same time, after receiving the charging start request sent by the RG and the TWAG respectively, the TWAP associates or binds the corresponding session according to the user identifier carried in the message.

10. The method according to claim 9, wherein the RG requests a termination connection to the BBF access network to: the RG sends a charging stop request to the TWAP in the BBF access network, and carries the charging stop request in the charging stop request. There is a user ID and/or a session ID.

The method of claim 10, wherein the releasing the resource information allocated by the BBF access network for the user equipment comprises:

The TWAG interacts with the PDN-GW in the BBF access network to exchange PMIP/GTP signaling, deletes the S2a session, and releases the GTP/PMIP tunnel.

12. The method according to claim 1, wherein the method further comprises accessing the user equipment before;

13. The method according to claim 12, wherein the RG requests a termination connection to the BBF access network to: the RG sends a termination notification message to the TWAP in the BBF access network, and the session is carried in the termination notification message. / Connection termination indication, and user identification and/or session identification; the TWAP association or binding the user pointed to in the termination notification message from the RG and the user pointed to in the charging start request sent by the TWAG.

The method according to claim 13, wherein the releasing the resource information allocated by the BBF access network for the user equipment comprises:

The TWAP returns a final confirmation message to the RG; the TWAP saves according to the self Associating or binding the result, initiating a RADIUS interrupt connection request to the TWAG in the BBF access network; the TWAG initiating a charging stop request to the TWAP, and the TWAP returns a charging stop response to the TWAG;

15. A system for realizing a user termination connection, comprising at least a user equipment, a residential gateway RG, an international standard organization broadband forum BBF access network, wherein

RG, set to: receive the terminating connection information from the user equipment, and request the BBF access network to terminate the connection;

The BBF access network is set to: Release the resource information allocated for the user who terminates the connection.

The system according to claim 15, wherein the BBF access network comprises at least a wireless local area network WLAN access gateway TWAG, a packet data network gateway PDN-GW, and a WLAN authentication and authorization charging agent TWAP;

TWAP, set to: return the charging stop response to TWAG;

TWAG, configured to: send a charging stop request to the TWAP, carry the user identifier, and/or the session identifier, and/or the IP address of the user equipment in the charging stop request; return a charging stop response to the RG; receive the The TWAP charging stops responding, interacting with the PDN-GW to move the Internet Protocol/General Packet Radio Service Tunneling Protocol PMIP/GTP signaling, deleting the S2a session, and releasing the GTP/PMIP tunnel.

17. The system of claim 16 wherein

The RG is further configured to: after the access authorization in the user equipment is successfully accessed, send a charging start request carrying the user identifier and/or the session identifier to the TWAP;

The TWAP is further configured to: return a charging start response to the RG; return a charging start to the TWAP;

The TWAG is further configured to: access an interactive PMIP/GTP command in the user equipment, After the S2a session and the PMIP/GTP tunnel are established, the user identity IMSI and/or the session identifier and the IP address successfully assigned to the user equipment are sent to the TWAP through the charging start request.

The system according to claim 15, wherein the BBF access network includes at least TWAG, PDN-GW, and TWAP;

TWAP, set to: Return the billing stop response to TWAG.

19. The system of claim 18, wherein

The TWAG is further configured to: after accessing the interactive PMIP/GTP command in the user equipment, after establishing an S2a session and a PMIP/GTP tunnel, sending, to the TWAP, carrying the user identifier and/or the session identifier, and the user The charging start request of the IP address successfully assigned by the device;

The system according to claim 15, wherein the BBF access network includes at least TWAG, PDN-GW, TWAP;

The TWAG is configured to: after accessing the PMIP/GTP command in the user equipment, establish an S2a session and a PMIP/GTP tunnel, and use the charging start request to set the user identifier and/or the session identifier, and the user equipment The successfully assigned IP address is sent to TWAP.

21. The system of claim 20, wherein The RG is further configured to: receive termination connection information from the user equipment, send a charging stop request to the TWAP, and carry the user identifier and/or the session identifier in the charging stop request;

The TWAG is configured to: after the accessing the PMIP/GTP command in the user equipment, establish an S2a session and a PMIP/GTP tunnel, send the user identifier and/or the session identifier to the WRAP, and succeed for the user equipment. The billing start request of the assigned IP address;

The TWAP is set to: return a charging start response to the TWAG.

23. The system of claim 22, wherein

The RG is further configured to: receive termination connection information from the user equipment, send a termination notification message to the TWAP, and carry the session/connection termination indication, and the user identifier and/or the session identifier in the termination notification message;

The TWAP is further configured to: return a termination confirmation message to the RG; associate or bind the user pointed to in the termination notification message from the RG and the user pointed to in the charging start request sent by the TWAG; according to the self The saved association or binding result, initiates a RADIUS interrupt connection request to the TWAG; returns a charging stop response to the TWAG;