CN104113930A - Method of realizing termination connection, and system of realizing termination connection - Google Patents

Method of realizing termination connection, and system of realizing termination connection Download PDF

Info

Publication number
CN104113930A
CN104113930A CN201310131457.1A CN201310131457A CN104113930A CN 104113930 A CN104113930 A CN 104113930A CN 201310131457 A CN201310131457 A CN 201310131457A CN 104113930 A CN104113930 A CN 104113930A
Authority
CN
China
Prior art keywords
twag
twap
user equipment
user
pmip
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Granted
Application number
CN201310131457.1A
Other languages
Chinese (zh)
Other versions
CN104113930B (en
Inventor
周星月
尤建洁
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
ZTE Corp
Original Assignee
ZTE Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by ZTE Corp filed Critical ZTE Corp
Priority to CN201310131457.1A priority Critical patent/CN104113930B/en
Priority to PCT/CN2014/075158 priority patent/WO2014169781A1/en
Publication of CN104113930A publication Critical patent/CN104113930A/en
Application granted granted Critical
Publication of CN104113930B publication Critical patent/CN104113930B/en
Expired - Fee Related legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/2854—Wide area networks, e.g. public data networks
    • H04L12/2856—Access arrangements, e.g. Internet access
    • H04L12/2869—Operational details of access network equipments
    • H04L12/2898—Subscriber equipments
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
    • H04L12/1403—Architecture for metering, charging or billing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
    • H04L12/1425—Charging, metering or billing arrangements for data wireline or wireless communications involving dedicated fields in the data packet for billing purposes
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/50—Address allocation
    • H04L61/5007—Internet protocol [IP] addresses
    • H04L61/5014—Internet protocol [IP] addresses using dynamic host configuration protocol [DHCP] or bootstrap protocol [BOOTP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/66—Policy and charging system
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M2215/00—Metering arrangements; Time controlling arrangements; Time indicating arrangements
    • H04M2215/20—Technology dependant metering
    • H04M2215/2033—WLAN

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

The present invention relates to a method of realizing termination connection, and a system of realizing termination connection. The method comprises the steps of using a dwelling house gateway in a fixed network to receive the termination connection information of a user device, and then requesting the termination connection to a broadband forum (BBF) access network, and using the BBF access network to release the resource information distributed to the user device. According to the present invention, when the user device initiates the termination connection, the resource information correlated with the user device is released timely at a network side, thereby saving the network resources.

Description

Method and system for implementing user terminating connection
Technical Field
The present invention relates to mobile communication technology, and in particular, to a method and system for implementing user terminated connection in a fixed network.
Background
With the increasing maturity and popularity of Wireless Local Area Network (WLAN) access technology and the demand of users for high-speed wireless access, operators at home and abroad are actively developing WLAN services. The WLAN service plays an increasingly important role as a 2G and 3G offloading means. The WLAN access belongs to a supplementary access mode of a fixed network, and how to effectively master and manage the access condition of a user through the WLAN becomes a key for developing WLAN value-added services. At the same time, this will help the operator for network optimization.
The Evolved Packet System (EPS) of the third Generation Partnership Project (3 GPP) is composed of an Evolved Universal mobile telecommunications System Terrestrial Radio Access Network (E-UTRAN), a Mobility Management unit (MME), a serving Gateway (S-GW), a Packet Data Network Gateway (P-GW, Gateway, also abbreviated as PDN-GW), a Home Subscriber Server (HSS), a Policy and Charging Rules Function (PCRF), a Policy and Charging Function Entity, and other support nodes.
Currently, standardization work of Fixed network and Mobile network Convergence (FMC) is being performed by the Broadband Forum (BBF) and the 3GPP, and a related scenario includes authentication, address allocation and policy control of 3GPP User Equipment (UE) accessing from a BBF network through a Residential Gateway (RG). Fig. 1 is a schematic diagram of a conventional fixed network, as shown in fig. 1. In the Authentication process, the 3gpp ue serves as an 802.1X client, initiates access Authentication to the RG, and at this time, the RG serves as an 802.1X authenticator and a Remote Authentication Dial In User Service (RADIUS) client, and initiates an Authentication request to a BBF Authentication, authorization and accounting (AAA) server (i.e., a trusted WLAN Authentication and authorization agent (TWAP)). In the address request procedure, an address request message initiated by the 3GPP UE requests an IP address from the PDN-GW via a Broadband Network Gateway device (BNG). The session S2a is established between the BNG and the PDN-GW, and is implemented by a general packet radio service Tunneling Protocol (GTP) or a Proxy Mobile Internet Protocol (PMIP) tunnel.
RADIUS is a protocol of a client/Server (C/S) architecture, and its client is originally a Network Access Server (NAS), and any computer running RADIUS client software can now become a RADIUS client. The RADIUS protocol authentication mechanism is flexible, and can adopt various modes such as a Password Authentication Protocol (PAP), a point-to-point protocol challenge authentication handshake protocol (CHAP) or Unix login authentication and the like. RADIUS is an extensible protocol that does all work based on a vector of Attribute Length values Attribute-Length-Value. RADIUS also supports vendor-specific attributes. Because the RADIUS protocol is simple and clear and can be expanded, the method can be widely applied to services such as ordinary telephone internet access, Asymmetric Digital Subscriber Loop (ADSL) internet access, cell broadband internet access, IP telephone, Virtual Private Dial Network (VPDN) based on dial-up users, mobile phone prepayment and the like. The 802.1x standard proposed by IEEE is a port-based standard for access authentication to a wireless network, and a RADIUS protocol is also used for authentication. A RADIUS Proxy (Proxy) provides routing of RADIUS messages between a RADIUS client accessing a server and a RADIUS server that attempts to perform user authentication, authorization, and accounting for connections.
In the prior 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 large impact on the existing network, and in order to solve the problem, a fixed network Access Gateway, such as a Trusted WLAN Access Gateway (TWAG), is introduced, and a schematic diagram of a network structure after the TWAG is introduced is shown in fig. 1. After the fixed network access gateway is introduced, large-scale upgrading of BNG equipment is not needed, so that the influence on the existing network is reduced as much as possible.
In the prior art, the user equipment may send an IEEE std802.11 defined disassociation notification message or a deregistration notification message to an AP/RG (common AP and RG co-located in a 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 ue, which causes a waste of network resource suspension.
Disclosure of Invention
The invention provides a method and a system for realizing user terminal connection, when user equipment initiates terminal connection, a network side can release resource information related to the user equipment in time, thereby saving network resources.
In order to solve the technical problem, the invention discloses a method for realizing user termination connection, which comprises the following steps: after receiving the terminating connection information of the user equipment, the residential gateway RG requests a terminating connection to a BBF access network of an international standard organization broadband forum;
and the BBF access network releases the resource information distributed to the user equipment.
The method for the RG to request the termination connection to the BBF access network comprises the following steps: and the RG sends a charging termination message or a new termination notification message to the BBF access network.
The method for the RG to request the termination connection to the BBF access network comprises the following steps:
the RG sends an accounting stop request to a trusted WLAN access gateway TWAG in the BBF access network, wherein the accounting stop request carries a user identifier and/or a session identifier; the TWAG sends a charging stop request to a trusted WLAN authentication authorization charging proxy TWAP in the BBF access network, wherein the charging stop request carries a user identifier, and/or a session identifier, and/or an IP address of user equipment; the TWAP returns a charging stop response to the TWAG; the TWAG returns an accounting stop response to the RG.
The BBF access network releases the resource information allocated to the user equipment, including:
and the TWAG in the BBF access network and a packet data network gateway PDN-GW in the BBF access network interactively proxy mobile Internet protocol/general packet radio service tunneling protocol/GTP signaling, delete the S2a session and release a GTP/PMIP tunnel.
The method also comprises accessing the user equipment;
after the authentication and authorization for accessing the user equipment is successful, the method further comprises the following steps: the RG sends a charging start request carrying a user identifier and/or a session identifier to the TWAG;
after the interactive PMIP/GTP command accessed to the user equipment establishes the S2a session and the PMIP/GTP tunnel, the method further includes: the TWAG sends a charging start request carrying a user identifier and/or a session identifier and an IP address successfully allocated for user equipment to a TWAP;
and the TWAP returns a charging start response to the TWAG, and the TWAG returns the charging start response to the RG.
The method for the RG to request the termination connection to the BBF access network comprises the following steps:
the RG sends a termination notification message to a TWAG in a BBF access network, and the termination notification message carries a session/connection termination indication, a user identifier and/or a session identifier;
and the TWAG sends an accounting stop request to a TWAP in the BBF access network after receiving the termination notice, wherein the accounting stop request carries a user identifier and/or a session identifier.
The BBF access network releases the resource information allocated to the user equipment, including:
the TWAP returns a charging stop response to the TWAG, and the TWAG returns a terminating confirmation message to the RG; and the TWAG interacts PMIP/GTP signaling with PDN-GW in the BBF access network, deletes S2a conversation and releases a GTP/PMIP tunnel.
The method also comprises accessing the user equipment; after the interactive PMIP/GTP command accessed to the user equipment establishes the S2a session and the PMIP/GTP tunnel, the method further includes:
the TWAG sends a charging start request carrying a user identifier and/or a session identifier and an IP address successfully allocated for user equipment to a TWAP; and the TWAP returns a charging start response to the TWAG.
The method also comprises accessing the user equipment;
after the authentication and authorization for accessing the user equipment is successful, the method further comprises the following steps: the RG sends a charging start request carrying a user identifier and/or a session identifier to the TWAP, and the TWAP returns a charging start response to the RG;
after the interactive PMIP/GTP command accessed to the user equipment establishes the S2a session and the PMIP/GTP tunnel, the method further includes: the TWAG in the BBF access network sends a charging start request carrying a user identifier and/or a session identifier and an IP address successfully allocated for user equipment to a TWAP; the TWAP returns a charging start response to the TWAG;
and simultaneously, after receiving the charging start requests respectively sent by the RG and the TWAG, the TWAP associates or binds the corresponding session according to the user identification carried in the message.
The method for the RG to request the termination connection to the BBF access network comprises the following steps: the RG sends a charging stop request to a TWAP in a BBF access network, wherein the charging stop request carries a user identifier and/or a session identifier.
The BBF access network releases the resource information allocated to the user equipment, including:
the TWAP returns a charging stop response to the RG; the TWAP initiates a remote user dial-up authentication system RADIUS connection interruption request to a TWAG in a BBF access network according to the self-stored association or binding result;
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;
and the TWAG interacts PMIP/GTP signaling with PDN-GW in the BBF access network, deletes S2a conversation and releases a GTP/PMIP tunnel.
The method also comprises accessing the user equipment;
after the interactive PMIP/GTP command accessed to the user equipment establishes the S2a session and the PMIP/GTP tunnel, the method further includes: the TWAG in the BBF access network sends a charging start request carrying a user identifier and/or a session identifier and an IP address successfully allocated for user equipment to a TWAP; and the TWAP returns a charging start response to the TWAG.
The method for the RG to request the termination connection to the BBF access network comprises the following steps: the RG sends a termination notification message to a TWAP in a BBF access network, wherein the termination notification message carries a session/connection termination indication, a user identifier and/or a session identifier;
and the TWAP associates or binds 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 BBF access network releases the resource information allocated to the user equipment, including:
the TWAP returns a termination confirmation message to the RG; the TWAP initiates a RADIUS connection interruption request to a TWAG in a BBF access network according to the self-stored association or binding result;
the TWAG initiates a charging stop request to the TWAP, and the TWAP returns a charging stop response to the TWAG;
and the TWAG interacts PMIP/GTP signaling with PDN-GW in the BBF access network, deletes S2a conversation and releases a GTP/PMIP tunnel.
The invention also provides a system for realizing user terminating connection, which at least comprises user equipment, RG and BBF access networks, wherein,
the RG is used for receiving the terminating connection information from the user equipment and requesting the BBF access network for terminating connection; and the BBF access network is used for releasing the resource information allocated to the user requesting the terminating connection.
The BBF access network at least comprises TWAG, PDN-GW and TWAP;
the RG is used for receiving the terminating connection information from the user equipment and sending a charging stop request to the TWAG, wherein the charging stop request carries a user identifier and/or a session identifier;
the TWAP is used for returning a charging stop response to the TWAG;
the TWAG is used for sending an accounting stop request to the TWAP, wherein the accounting stop request carries a user identifier, and/or a session identifier, and/or an IP address of user equipment; returning a charging stop response to the RG; and receiving a charging stop response from the TWAP, interacting PMIP/GTP signaling with the PDN-GW, deleting the S2a session, and releasing a GTP/PMIP tunnel.
The RG is further configured to send a charging start request carrying a user identifier and/or a session identifier to the TWAP after the authentication and authorization for accessing the user equipment is successful; the TWAP is also used for returning a charging start response to the RG; returning a charging start response to the TWAP;
the TWAG is further configured to send the user identifier IMSI and/or the session identifier and the IP address successfully allocated to the user equipment to the TWAP through a charging start request after accessing the interactive PMIP/GTP command in the user equipment and establishing the S2a session and PMIP/GTP tunnel.
The BBF access network at least comprises TWAG, PDN-GW and TWAP;
the RG is used for receiving the terminating connection information from the user equipment and sending a terminating notification message to the TWAG, wherein the terminating notification message carries a session/connection terminating indication, a user identifier and/or a session identifier;
the TWAG is used for receiving the termination notice and sending an accounting stop request to the TWAP, wherein the accounting stop request carries a user identifier and/or a session identifier; returning a terminating confirmation message to the RG; PMIP/GTP signaling is interacted with PDN-GW, S2a conversation is deleted, and a GTP/PMIP tunnel is released;
and the TWAP is used for returning an accounting stop response to the TWAG.
The TWAG is further configured to send a charging start request carrying the user identifier and/or the session identifier and the IP address successfully allocated to the user equipment to the TWAP after accessing the interactive PMIP/GTP command in the user equipment and establishing the S2a session and PMIP/GTP tunnel;
the TWAP is also used for returning a charging start response to the TWAG.
The BBF access network at least comprises TWAG, PDN-GW and TWAP;
the RG is further configured to send a charging start request carrying a user identifier and/or a session identifier to the TWAP after authentication and authorization for accessing the user equipment is successful;
the TWAP is used for returning a charging start response to the RG; returning a charging start response to the TWAG; associating or binding corresponding sessions according to user identifications carried in the messages after receiving charging start requests respectively sent by the RG and the TWAG;
and the TWAG is used for sending the user identifier and/or the session identifier and the IP address successfully allocated to the user equipment to the TWAP through a charging start request after the user equipment is accessed to the interactive PMIP/GTP instruction in the user equipment and an S2a session and a PMIP/GTP tunnel are established.
The RG is further configured to receive terminating connection information from the user equipment, and send a charging stop request to the TWAP, where the charging stop request carries a user identifier and/or a session identifier;
the TWAP is also used for returning a charging stop response to the RG; initiating a RADIUS connection interruption request to the TWAG according to the self-stored association or binding result; returning a charging stop response to the TWAG;
the TWAG is also used for initiating a charging stop request to the TWAP; and PMIP/GTP signaling is interacted with the PDN-GW, the S2a conversation is deleted, and a GTP/PMIP tunnel is released.
The BBF access network at least comprises TWAG, PDN-GW and TWAP;
the TWAG is used for sending a charging start request carrying a user identifier and/or a session identifier and an IP address successfully allocated for the user equipment to the WRAP after an S2a session and a PMIP/GTP tunnel are established by accessing an interactive PMIP/GTP instruction in the user equipment;
and the TWAP is used for returning 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 also used for returning a terminating confirmation message to the RG; associating 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; initiating a RADIUS connection interruption request to the TWAG according to the self-stored association or binding result; returning a charging stop response to the TWAG;
the TWAG is also used for initiating a charging stop request to the TWAP; and PMIP/GTP signaling is interacted with the PDN-GW, the S2a conversation is deleted, and a GTP/PMIP tunnel is released.
The technical scheme includes that after receiving the terminating connection information of the user equipment, the residential gateway in the fixed network requests the BBF access network for terminating connection, and the BBF access network releases resource information allocated to 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.
Drawings
The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the invention and together with the description serve to explain the invention without limiting the invention. In the drawings:
FIG. 1 is a schematic diagram of a conventional fixed network;
FIG. 2 is a flowchart of a method for implementing a user terminated connection according to the present invention;
FIG. 3 is a flowchart illustrating a first embodiment of implementing a user terminated connection according to the present invention;
FIG. 4 is a flowchart illustrating a second embodiment of implementing a user terminated connection according to the present invention;
FIG. 5 is a flowchart illustrating a third embodiment of implementing a user terminated connection according to the present invention;
FIG. 6 is a flowchart illustrating a fourth embodiment of implementing a user terminated connection according to the present invention;
fig. 7 is a schematic diagram of a system structure for implementing the user terminated connection according to the present invention.
Detailed Description
Fig. 2 is a flowchart of a method for implementing user terminated connection according to the present invention, and as shown in fig. 2, the method of the present invention includes the following steps:
step 200: after receiving the terminating connection information of the user equipment, the residential gateway requests the BBF access network for terminating connection.
In this step, the RG receives the terminating connection information of the user equipment, which is the disassociation notification message or the logout notification message defined by IEEE std 802.11. The RG can request the BBF access network for terminating connection through the existing charging termination message or the new terminating notification message.
According to whether the TWAG is used as the RADIUS Proxy or not, the implementation that the RG requests the BBF access network to terminate the connection in the step comprises the following two modes:
in a first manner, when the TWAG is used as the RADIUS Proxy in the access process of the user equipment, the implementation that the RG requests the BBF access network to terminate the connection specifically includes:
when the RG requests the BBF access network to terminate connection through the existing charging termination message, the RG sends a charging-Stop Request (accounting-Stop Request) to the TWAG, where the charging-Stop Request carries a user identifier such as an International Mobile Subscriber Identity (IMSI) and/or a session identifier, and the TWAG sends a charging-Stop Request to the TWAP, where the charging-Stop Request carries the user identifier, and/or the session identifier, and/or an IP address of the user equipment. In this way, in order to improve the whole access process, the existing user equipment access process further includes: after the authentication and authorization are successful, the RG sends a charging start request carrying a user identifier, such as an International Mobile Subscriber Identity (IMSI) and/or a session identifier, to the TWAG; after interacting with the PMIP/GTP instruction and establishing the S2a session and the PMIP/GTP tunnel, the TWAG sends a user identifier, such as an International Mobile Subscriber Identity (IMSI) and/or a session identifier, and an IP address successfully allocated to the user equipment to the TWAP through a charging start request; and then, the TWAP returns a charging starting response to the TWAG, and the TWAG returns the charging starting response to the RG.
When the RG requests the BBF access network to terminate connection through newly establishing a terminating notification message, the RG sends the terminating notification message to the TWAG, and the terminating notification message carries a session/connection terminating indication and a user identifier such as an International Mobile Subscriber Identity (IMSI) and/or a session identifier; and the TWAG sends an accounting stop request to the TWAP after receiving the termination notice, wherein the accounting 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 whole access process, the existing user equipment access process further includes: after interacting with the PMIP/GTP instruction and establishing the S2a session and the PMIP/GTP tunnel, the TWAG sends a user identifier, such as an International Mobile Subscriber Identity (IMSI) and/or a session identifier, and an IP address successfully allocated to the user equipment to the TWAP through a charging start request; after that, the TWAP returns an accounting start response to the TWAG.
In a second way, when the RG directly interacts with the TWAP in the access process of the user equipment, that is, the TWAG is not used as the RADIUS Proxy, the implementation of the RG requesting the BBF access network to terminate the connection specifically includes:
when the RG requests the BBF access network to terminate connection 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 identifier. In this way, in order to improve the whole access process, the existing user equipment access process further includes: after the authentication and authorization are successful, the RG sends a charging start request carrying a user identifier, such as an International Mobile Subscriber Identity (IMSI) and/or a session identifier, to the TWAP, and the TWAP returns a charging start response to the RG; after interacting with the PMIP/GTP instruction and establishing the S2a session and the PMIP/GTP tunnel, the TWAG sends a user identifier, such as an International Mobile Subscriber Identity (IMSI) and/or a session identifier, and an IP address successfully allocated to the user equipment to the TWAP through a charging start request; after that, the TWAP returns an accounting start response to the TWAG.
When the RG requests the BBF access network to terminate connection through the newly-established 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 a session identifier. In this way, in order to improve the whole access process, the existing user equipment access process further includes: after interacting with the PMIP/GTP instruction and establishing the S2a session and the PMIP/GTP tunnel, the TWAG sends a user identifier, such as an International Mobile Subscriber Identity (IMSI) and/or a session identifier, and an IP address successfully allocated to the user equipment to the TWAP through a charging start request; after that, the TWAP returns an accounting start response to the TWAG.
Step 201: the BBF access network releases the resource information allocated to the user equipment.
When the RG sends the charging stop request to the TWAP via the TWAG, the step specifically includes: the TWAP returns a charging-stopping response (accounting-Stop Ack) to the TWAG; the TWAG returns a charging stop response to the RG; afterwards, the TWAG and the PDN-GW interact with PMIP/GTP signaling, delete the S2a session, and release the GTP/PMIP tunnel, which belongs to the technical means commonly used by those skilled in the art, and is not used to limit the protection scope of the present invention, and will not be described herein again.
When the RG sends the 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 termination confirmation message to the RG; afterwards, the TWAG and the PDN-GW interact with PMIP/GTP signaling, delete the S2a session, and release the GTP/PMIP tunnel, which belongs to the technical means commonly used by those skilled in the art, and is not used to limit the protection scope of the present invention, and will not be described herein again.
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 method comprises the following steps that a TWAP initiates a RADIUS connection interruption request (RADIUS SDisconnect request) to a TWAG, the TWAG initiates a charging stop request to the TWAP, the TWAP returns a charging stop response to the TWAG, then the TWAG interacts with a PDN-GW to send PMIP/GTP signaling, an S2a session is deleted, and a GTP/PMIP tunnel is released, and the specific implementation belongs to the technical means commonly used by technicians in the field, is not used for limiting the protection range of the invention, and is not described again; finally, the TWAG returns a RADIUS interrupt connection response to the TWAP.
When the RG sends a termination notification message to the TWAP, the step specifically includes: the TWAP returns a termination confirmation message to the RG; the method comprises the following steps that a TWAP initiates a RADIUS connection interruption request (RADIUS SDisconnect request) to a TWAG, the TWAG initiates a charging stop request to the TWAP, the TWAP returns a charging stop response to the TWAG, then the TWAG interacts with a PDN-GW to send PMIP/GTP signaling, an S2a session is deleted, and a GTP/PMIP tunnel is released, and the specific implementation belongs to the technical means commonly used by technicians in the field, is not used for limiting the protection range of the invention, and is not described again; finally, the TWAG returns a RADIUS interrupt connection response to the TWAP.
The process of the present invention is described in detail below with reference to specific examples.
Fig. 3 is a schematic flowchart of a first embodiment of implementing a user terminated connection according to the present invention, in the first embodiment, a mobile network User Equipment (UE) is attached from a fixed network, the UE performs an Access authentication procedure, an Access node device of the fixed network is served by an RG, and the RG is an authentication Point and has a WLAN Access Point (AP) function. And after the authentication and authorization are successful, 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 a first embodiment, the TWAG serves as a RADIUS Proxy, and routes a RADIUS message to the TWAP for the ue, and the RG requests the BBF access network to terminate the connection through an existing accounting termination message. As shown in fig. 3, the specific implementation is as follows:
step 300: the user equipment discovers a wireless network covered by the RG to make an initial attach connection to the RG.
Step 301: user equipment initiates an Extensible Authentication Protocol (EAP) authentication authorization to the RG, and a network side negotiates packet connection of a 3GPP core network or structured small world overlay Network (NSWO) connection (directly accessing the Internet by a TWAG bypass) according to user identification, network capability, subscription information and the like.
Step 302: after successful authentication and authorization, the RG sends an accounting start request to the TWAG, where the accounting start request carries a user identifier such as IMSI and/or a session identifier.
Step 303: the user equipment initiates a DHCP flow to the TWAG to request to allocate an IP address.
Step 304: PMIP/GTP signaling is interacted between the TWAG and the PDN-GW, an S2a conversation and a PMIP/GTP tunnel are established, and the PDN-GW allocates an IP address of the user equipment, such as an IPv4/IPv6 address, to the TWAG.
Step 305: and the TWAG sends a DHCP response message to the user equipment and issues an IP address distributed by the PDN-GW.
Step 306 to step 307: the TWAG judges that the user access attribute is the user equipment of the mobile network and connects back to the mobile core network to which the user access attribute belongs according to the user identifier and/or session identifier in the charging start request from the RG received in step 302, and then the TWAG sends the charging start request carrying the user identifier and/or session identifier and the allocated IP address to the TWAP; and 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 terminating connection request, such as a Disassociation message (Disassociation), to the RG to terminate the connection between the user equipment and the RG.
Step 310: the RG (i.e., RADIUS client) sends a RADIUS accounting stop request to the TWAG (i.e., RADIUS Proxy).
Step 311 to step 312: the RADIUS accounting stop request and accounting stop response are interacted between the TWAG and the TWAP (i.e., the BBF AAA server).
It should be noted that, in step 310 to step 312, the RG sends an accounting stop request to a trusted WLAN access gateway TWAG in the BBF access network, where the accounting stop request carries a user identifier and/or a session identifier; and the TWAG sends an accounting stop request to a TWAP in the BBF access network, wherein the accounting stop request carries a user identifier, and/or a session identifier, and/or an IP address of user equipment.
Step 313: the TWAG returns an accounting stop response corresponding to step 310 to the RG.
Step 314: PMIP/GTP signaling is interacted between the TWAG and the PDN-GW, the S2a conversation is deleted, and a GTP/PMIP tunnel is released. In this step, according to the user identifier carried in the transmitted message, the S2a session established by the corresponding user equipment is deleted, and the GTP/PMIP tunnel is released. The detailed implementation is the means commonly used by those skilled in the art, and is not used to limit the scope of the present invention, and will not be described herein.
Fig. 4 is a schematic flow chart of a second embodiment of implementing user terminated connection according to the present invention, in the second embodiment, a mobile network user equipment UE attaches to a fixed network, the UE performs an access authentication procedure, an access node device of the fixed network is served by an RG, and the RG is an authentication point and has a WLAN AP function. And after the authentication and authorization are successful, 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 serves as a RADIUS Proxy, and routes a RADIUS message to the TWAP for the user equipment, and the RG requests the BBF access network for terminating connection through a new terminating notification message. As shown in fig. 4, the specific implementation is as follows:
step 400: the user equipment discovers a wireless network covered by the RG to make an initial attach connection to the RG.
Step 401: user equipment initiates an Extensible Authentication Protocol (EAP) authentication authorization to the RG, and a network side negotiates packet connection of a 3GPP core network or structured small world overlay Network (NSWO) connection (directly accessing the Internet by a TWAG bypass) according to user identification, network capability, subscription information and the like.
Step 402: the user equipment initiates a DHCP flow to the TWAG to request to allocate an IP address.
Step 403: PMIP/GTP signaling is interacted between the TWAG and the PDN-GW, an S2a conversation and a PMIP/GTP tunnel are established, and the PDN-GW allocates an IP address of the user equipment, such as an IPv4/IPv6 address, to the TWAG.
Step 404: and the TWAG sends a DHCP response message to the user equipment and issues an IP address distributed by the PDN-GW.
Step 405 to step 406: the TWAG sends a charging start request carrying the user identification and/or the session identification and the allocated IP address to the TWAP; and 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, such as a Disassociation message (Disassociation), to the RG to terminate the connection between the user equipment and the RG.
Step 408: the RG sends a termination notification message to the TWAG (i.e., RADIUS Proxy) to notify the TWAG to terminate the session. The terminating notification message may be a RADIUS message, and a session/connection terminating indication and a subscriber identifier, such as an IMSI and/or a session identifier, are carried in the terminating notification message.
Step 409 to step 410: the TWAG interacts with TWAP (BBF AAA) with RADIUS accounting stop request and accounting stop response.
Step 411: the TWAG returns a termination acknowledgement message corresponding to step 408 to the RG.
Step 412: PMIP/GTP signaling is interacted between the TWAG and the PDN-GW, the S2a conversation is deleted, and a GTP/PMIP tunnel is released. In this step, according to the user identifier carried in the transmitted message, the S2a session established by the corresponding user equipment is deleted, and the GTP/PMIP tunnel is released. The detailed implementation is the means commonly used by those skilled in the art, and is not used to limit the scope of the present invention, and will not be described herein.
Fig. 5 is a schematic flowchart of a third embodiment of implementing user terminated connection according to the present invention, as shown in fig. 5, a mobile network user equipment UE attaches to a fixed network, the UE performs an access authentication procedure, an access node device of the fixed network is served by an RG, and the RG is an authentication point and has a WLAN AP function. And after the authentication and authorization are successful, 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 a third embodiment, there is no radius proxy between RG and TWAP. In the connection establishment process, the TWAP receives RADIUS accounting request messages from the RG and the TWAG for the same ue respectively, and the difference between the two RADIUS accounting request messages is that the RADIUS accounting request message from the TWAG also carries an IP address allocated to the ue. It is assumed that the RG requests the BBF access network to terminate the connection through the existing accounting-termination message. The concrete implementation is as follows:
step 500 to step 501: the user equipment discovers a wireless network covered by the RG to make an initial attach connection to the RG. User equipment initiates EAP authentication authorization to RG, and a network side negotiates packet connection or NSWO connection (TWAG bypass directly accesses to the Internet) of a 3GPP core network according to user identification, network capability, subscription information and the like.
Step 502 to step 503: after the authentication and authorization are successful, the RG sends a charging start request to the TWAP, where the charging start request carries a user identifier and/or a session identifier.
Step 504: the user equipment initiates a DHCP flow to the TWAG to request to allocate an IP address.
Step 505: the method comprises the steps that RADIUS access requests and RADIUS access acceptance messages are interacted between the TWAG and the TWAP.
Step 506: PMIP/GTP signaling is interacted between the TWAG and the PDN GW, an S2a conversation and a PMIP/GTP tunnel are established, and the PDN-GW allocates an IP address of the user equipment, such as an IPv4/IPv6 address, to the TWAG.
Step 507: and the TWAG sends a DHCP response message to the user equipment and issues an IP address distributed by the PDN-GW.
Step 508 to step 509: the TWAG sends a charging start request carrying the user identification and/or the session identification and the allocated IP address to the TWAP; and 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.
Meanwhile, 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 identification; thus, when the subsequent TWAP receives the charging stop request from the RG, the TWAP can send a RADIUS connection interruption request directed to the same user currently initiating the terminating session to the TWAG according to the local association or binding result.
Step 510: the user equipment sends a terminating connection request, such as a disassociation message, to the RG to terminate 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 identification and/or the session identification to the TWAP, and the TWAP returns an accounting stop response to the RG.
Step 513: and the TWAP carries the user equipment identifier or the session identifier carried in the RADIUS accounting stop request from the RG and sends the user equipment identifier or the session identifier to the TWAG after the RADIUS connection interruption request. Here, the TWAP can send a RADIUS interrupt connection request directed to the same user that currently initiated the terminating session to the TWAG according to the local association or binding result.
Step 514 to step 515: and interacting the charging stop request and the charging stop response between the TWAG and the TWAP to terminate charging.
Step 516: PMIP/GTP signaling is interacted between the TWAG and the PDN-GW, the S2a conversation is deleted, and a GTP/PMIP tunnel is released. In this step, according to the user identifier carried in the transmitted message, the S2a session established by the corresponding user equipment is deleted, and the GTP/PMIP tunnel is released. The detailed implementation is the means commonly used by those skilled in the art, and is not used to limit the scope of the present invention, and will not be described herein.
517: the TWAG returns a RADIUS interrupt connection response to the TWAP corresponding to step 513.
Fig. 6 is a schematic flowchart of a fourth embodiment of implementing user terminated connection according to the present invention, as shown in fig. 6, a mobile network user equipment UE attaches to a fixed network, the UE performs an access authentication procedure, an access node device of the fixed network is served by an RG, and the RG is an authentication point and has a WLAN AP function. And after the authentication and authorization are successful, 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 a third embodiment, there is no radius proxy between RG and TWAP. Suppose that the RG requests the BBF access network to terminate the connection through a new terminating notification message. The concrete implementation is as follows:
step 600 to step 610: the user equipment discovers a wireless network covered by the RG to make an initial attach connection to the RG. User equipment initiates EAP authentication authorization to RG, and a network side negotiates packet connection or NSWO connection (TWAG bypass directly accesses to the Internet) of a 3GPP core network according to user identification, network capability, subscription information and the like.
Step 602: the user equipment initiates a DHCP flow to the TWAG to request to allocate an IP address.
Step 603: the method comprises the steps that RADIUS access requests and RADIUS access acceptance messages are interacted between the TWAG and the TWAP.
Step 604: PMIP/GTP signaling is interacted between the TWAG and the PDN-GW, an S2a conversation and a PMIP/GTP tunnel are established, and the PDN-GW allocates an IP address of the user equipment, such as an IPv4/IPv6 address, to the TWAG.
Step 605: and the TWAG sends a DHCP response message to the user equipment and issues an IP address distributed by the PDN-GW.
Step 606 to step 607: the TWAG sends a charging start request carrying the user identification and/or the session identification and the allocated IP address to the TWAP; and 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, such as a Disassociation message (Disassociation), to the RG 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; and 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 terminating notification message from the RG with the charging start request from the TWAG, that is, the TWAP associates the user pointed to in the terminating notification message from the RG with the user pointed to in the charging start request sent by the TWAG; in this way, the TWAP can send a RADIUS connection interruption request directed to the same user currently initiating the terminating session to the TWAG according to the local association or binding result.
Step 611: and the TWAP carries the user equipment identifier or the session identifier carried in the RADIUS accounting stop request from the RG and sends the user equipment identifier or the session identifier to the TWAG after the RADIUS connection interruption request. Here, the TWAP can send a RADIUS interrupt connection request directed to the same user that currently initiated the terminating session to the TWAG according to the local association or binding result.
Step 612 to step 613: and interacting the charging stop request and the charging stop response between the TWAG and the TWAP to terminate charging.
Step 614: PMIP/GTP signaling is interacted between the TWAG and the PDN-GW, the S2a conversation is deleted, and a GTP/PMIP tunnel is released. In this step, according to the user identifier carried in the transmitted message, the S2a session established by the corresponding user equipment is deleted, and the GTP/PMIP tunnel is released. The detailed implementation is the means commonly used by those skilled in the art, and is not used to limit the scope of the present invention, and will not be described herein.
Step 615: the TWAG returns a RADIUS interrupt connection response to the TWAP corresponding to step 513.
Aiming at the method for realizing the user terminating connection, the invention also provides a system for realizing the user terminating connection, the schematic structural diagram of which is shown in fig. 7, the system at least comprises user equipment, RG and BBF access networks, wherein,
and the RG is used for receiving the terminating connection information from the user equipment and requesting the BBF access network for terminating connection. And the BBF access network is used for releasing the resource information allocated to the user requesting the terminating connection.
Wherein, the BBF access network at least comprises TWAG, PDN-GW, TWAP, concretely,
the RG is used for receiving the terminal connection information from the user equipment and sending an accounting stop request to the TWAG, wherein the accounting stop request carries a user identifier such as IMSI and/or a session identifier;
the TWAP is used for returning a charging stop response to the TWAG;
the TWAG is used for sending an accounting stop request to the TWAP, wherein the accounting stop request carries a user identifier, and/or a session identifier, and/or an IP address of user equipment; returning a charging stop response to the RG; and receiving a charging stop response from the TWAP, interacting PMIP/GTP signaling with the PDN-GW, deleting the S2a session, and releasing a GTP/PMIP tunnel.
In this way, in order to improve the whole access process, the existing user equipment access process further includes:
the RG is also used for sending a charging start request carrying a user identifier such as IMSI and/or a session identifier to the TWAP after the authentication and authorization are successful;
the TWAP is also used for returning a charging starting response to the RG; returning a charging start response to the TWAP;
and the TWAG is also used for sending the user identification IMSI and/or the session identification and the IP address successfully allocated for the user equipment to the TWAP through the charging start request after the PMIP/GTP instruction is interacted, and the S2a session and the PMIP/GTP tunnel are established.
Or,
the RG is used for receiving the terminating connection information from the user equipment and sending a terminating notification message to the TWAG, wherein the terminating notification message carries a session/connection terminating indication and a user identifier such as IMSI and/or a session identifier;
the TWAG is used for receiving the termination notice and sending an accounting stop request to the TWAP, wherein the accounting stop request carries a user identifier such as IMSI and/or a session identifier; returning a terminating confirmation message to the RG; the TWAG and the PDN-GW interact PMIP/GTP signaling, delete S2a conversation and release a GTP/PMIP tunnel;
and the TWAP is used for returning an accounting stop response to the TWAG.
In this way, in order to improve the whole access process, the existing user equipment access process further includes:
the TWAG is also used for sending the user identifier such as IMSI and/or session identifier and the IP address successfully distributed for the user equipment to the TWAP through the charging start request after the PMIP/GTP instruction is interacted and the S2a session and the PMIP/GTP tunnel are established;
and the TWAP is also used for returning an accounting start response to the TWAG.
Or,
in this way, in order to improve the whole access process, the existing user equipment access process further includes:
the RG is also used for sending a charging start request carrying a user identifier such as IMSI and/or a session identifier to the TWAP after the authentication and authorization are successful;
the TWAP is also used for returning a charging starting response to the RG; returning a charging start response to the TWAG; associating or binding corresponding sessions according to user identifications carried in the messages after receiving charging start requests respectively sent by the RG and the TWAG;
and the TWAG is also used for sending the user identification such as the IMSI and/or the session identification and the IP address successfully allocated for the user equipment to the TWAP through the charging start request after the PMIP/GTP instruction is interacted, the S2a session and the PMIP/GTP tunnel are established.
In the process of implementing user termination, the RG is used for receiving termination connection information from user equipment and sending a charging stop request to the TWAP, where the charging stop request carries a user identifier such as IMSI and/or a session identifier;
the TWAP is used for returning a charging stop response to the RG; initiating a RADIUS connection interruption request to the TWAG according to the self-stored association or binding result; returning a charging stop response to the TWAG;
the TWAG is used for initiating a charging stop request to the TWAP; and PMIP/GTP signaling is interacted with the PDN-GW, the S2a conversation is deleted, and a GTP/PMIP tunnel is released.
Or,
in this way, in order to improve the whole access process, the existing user equipment access process further includes:
the TWAG is also used for sending the user identifier such as IMSI and/or session identifier and the IP address successfully distributed for the user equipment to the TWAP through the charging start request after the PMIP/GTP instruction is interacted and the S2a session and the PMIP/GTP tunnel are established;
and the TWAP is also used for returning an accounting start response to the TWAG.
In the process of implementing user termination, the RG is 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 such as an IMSI and/or a session identifier;
the TWAP is used for returning a termination confirmation message to the RG; associating 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; initiating a RADIUS connection interruption request to the TWAG according to the self-stored association or binding result; returning a charging stop response to the TWAG;
the TWAG is used for initiating a charging stop request to the TWAP; and PMIP/GTP signaling is interacted with the PDN-GW, the S2a conversation is deleted, and a GTP/PMIP tunnel is released.
The above description is only a preferred example of the present invention, and is not intended to limit the scope of the present invention. Any modification, equivalent replacement, or improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.

Claims (23)

1. A method for implementing a user terminated connection, comprising:
after receiving the terminating connection information of the user equipment, the residential gateway RG requests a terminating connection to a BBF access network of an international standard organization broadband forum;
and the BBF access network releases the resource information distributed to the user equipment.
2. The method of claim 1, wherein the method for the RG to request the BBF access network to terminate the connection is: and the RG sends a charging termination message or a new termination notification message to the BBF access network.
3. The method of claim 1, wherein the method for the RG to request the BBF access network to terminate the connection is:
the RG sends an accounting stop request to a trusted WLAN access gateway TWAG in the BBF access network, wherein the accounting stop request carries a user identifier and/or a session identifier; the TWAG sends a charging stop request to a trusted WLAN authentication authorization charging proxy TWAP in the BBF access network, wherein the charging stop request carries a user identifier, and/or a session identifier, and/or an IP address of user equipment; the TWAP returns a charging stop response to the TWAG; the TWAG returns an accounting stop response to the RG.
4. The method of claim 3, wherein the BBF access network releasing the resource information allocated for the user equipment comprises:
and the TWAG in the BBF access network and a packet data network gateway PDN-GW in the BBF access network interactively proxy mobile Internet protocol/general packet radio service tunneling protocol/GTP signaling, delete the S2a session and release a GTP/PMIP tunnel.
5. The method of claim 3 or 4, further comprising, prior to the method, accessing the user equipment;
after the authentication and authorization for accessing the user equipment is successful, the method further comprises the following steps: the RG sends a charging start request carrying a user identifier and/or a session identifier to the TWAG;
after the interactive PMIP/GTP command accessed to the user equipment establishes the S2a session and the PMIP/GTP tunnel, the method further includes: the TWAG sends a charging start request carrying a user identifier and/or a session identifier and an IP address successfully allocated for user equipment to a TWAP;
and the TWAP returns a charging start response to the TWAG, and the TWAG returns the charging start response to the RG.
6. The method of claim 1, wherein the method for the RG to request the BBF access network to terminate the connection is:
the RG sends a termination notification message to a TWAG in a BBF access network, and the termination notification message carries a session/connection termination indication, a user identifier and/or a session identifier;
and the TWAG sends an accounting stop request to a TWAP in the BBF access network after receiving the termination notice, wherein the accounting stop request carries a user identifier and/or a session identifier.
7. The method of claim 6, wherein the BBF access network releasing the resource information allocated for the user equipment comprises:
the TWAP returns a charging stop response to the TWAG, and the TWAG returns a terminating confirmation message to the RG; and the TWAG interacts PMIP/GTP signaling with PDN-GW in the BBF access network, deletes S2a conversation and releases a GTP/PMIP tunnel.
8. The method of claim 6 or 7, further comprising, prior to the method, accessing the user equipment; after the interactive PMIP/GTP command accessed to the user equipment establishes the S2a session and the PMIP/GTP tunnel, the method further includes:
the TWAG sends a charging start request carrying a user identifier and/or a session identifier and an IP address successfully allocated for user equipment to a TWAP; and the TWAP returns a charging start response to the TWAG.
9. The method of claim 1, further comprising accessing the user equipment;
after the authentication and authorization for accessing the user equipment is successful, the method further comprises the following steps: the RG sends a charging start request carrying a user identifier and/or a session identifier to the TWAP, and the TWAP returns a charging start response to the RG;
after the interactive PMIP/GTP command accessed to the user equipment establishes the S2a session and the PMIP/GTP tunnel, the method further includes: the TWAG in the BBF access network sends a charging start request carrying a user identifier and/or a session identifier and an IP address successfully allocated for user equipment to a TWAP; the TWAP returns a charging start response to the TWAG;
and simultaneously, after receiving the charging start requests respectively sent by the RG and the TWAG, the TWAP associates or binds the corresponding session according to the user identification carried in the message.
10. The method of claim 9, wherein the method for the RG to request the terminating connection from the BBF access network comprises: the RG sends a charging stop request to a TWAP in a BBF access network, wherein the charging stop request carries a user identifier and/or a session identifier.
11. The method of claim 10, wherein the BBF access network releasing resource information allocated for the user equipment comprises:
the TWAP returns a charging stop response to the RG; the TWAP initiates a remote user dial-up authentication system RADIUS connection interruption request to a TWAG in a BBF access network according to the self-stored association or binding result;
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;
and the TWAG interacts PMIP/GTP signaling with PDN-GW in the BBF access network, deletes S2a conversation and releases a GTP/PMIP tunnel.
12. The method of claim 1, further comprising accessing the user equipment;
after the interactive PMIP/GTP command accessed to the user equipment establishes the S2a session and the PMIP/GTP tunnel, the method further includes: the TWAG in the BBF access network sends a charging start request carrying a user identifier and/or a session identifier and an IP address successfully allocated for user equipment to a TWAP; and the TWAP returns a charging start response to the TWAG.
13. The method of claim 12, wherein the method for the RG to request the terminating connection from the BBF access network comprises: the RG sends a termination notification message to a TWAP in a BBF access network, wherein the termination notification message carries a session/connection termination indication, a user identifier and/or a session identifier;
and the TWAP associates or binds 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.
14. The method of claim 13, wherein the BBF access network releasing resource information allocated for the user equipment comprises:
the TWAP returns a termination confirmation message to the RG; the TWAP initiates a RADIUS connection interruption request to a TWAG in a BBF access network according to the self-stored association or binding result;
the TWAG initiates a charging stop request to the TWAP, and the TWAP returns a charging stop response to the TWAG;
and the TWAG interacts PMIP/GTP signaling with PDN-GW in the BBF access network, deletes S2a conversation and releases a GTP/PMIP tunnel.
15. A system for implementing user terminated connections, comprising at least user equipment, RG, BBF access networks, wherein,
the RG is used for receiving the terminating connection information from the user equipment and requesting the BBF access network for terminating connection; and the BBF access network is used for releasing the resource information allocated to the user requesting the terminating connection.
16. The system of claim 15, wherein the BBF access network comprises at least TWAG, PDN-GW, TWAP;
the RG is used for receiving the terminating connection information from the user equipment and sending a charging stop request to the TWAG, wherein the charging stop request carries a user identifier and/or a session identifier;
the TWAP is used for returning a charging stop response to the TWAG;
the TWAG is used for sending an accounting stop request to the TWAP, wherein the accounting stop request carries a user identifier, and/or a session identifier, and/or an IP address of user equipment; returning a charging stop response to the RG; and receiving a charging stop response from the TWAP, interacting PMIP/GTP signaling with the PDN-GW, deleting the S2a session, and releasing a GTP/PMIP tunnel.
17. The system of claim 16,
the RG is further configured to send a charging start request carrying a user identifier and/or a session identifier to the TWAP after the authentication and authorization for accessing the user equipment is successful; the TWAP is also used for returning a charging start response to the RG; returning a charging start response to the TWAP;
the TWAG is further configured to send the user identifier IMSI and/or the session identifier and the IP address successfully allocated to the user equipment to the TWAP through a charging start request after accessing the interactive PMIP/GTP command in the user equipment and establishing the S2a session and PMIP/GTP tunnel.
18. The system of claim 15, wherein the BBF access network comprises at least TWAG, PDN-GW, TWAP;
the RG is used for receiving the terminating connection information from the user equipment and sending a terminating notification message to the TWAG, wherein the terminating notification message carries a session/connection terminating indication, a user identifier and/or a session identifier;
the TWAG is used for receiving the termination notice and sending an accounting stop request to the TWAP, wherein the accounting stop request carries a user identifier and/or a session identifier; returning a terminating confirmation message to the RG; PMIP/GTP signaling is interacted with PDN-GW, S2a conversation is deleted, and a GTP/PMIP tunnel is released;
and the TWAP is used for returning an accounting stop response to the TWAG.
19. The system of claim 18,
the TWAG is further configured to send a charging start request carrying the user identifier and/or the session identifier and the IP address successfully allocated to the user equipment to the TWAP after accessing the interactive PMIP/GTP command in the user equipment and establishing the S2a session and PMIP/GTP tunnel;
the TWAP is also used for returning a charging start response to the TWAG.
20. The system of claim 15, wherein the BBF access network comprises at least TWAG, PDN-GW, TWAP;
the RG is further configured to send a charging start request carrying a user identifier and/or a session identifier to the TWAP after authentication and authorization for accessing the user equipment is successful;
the TWAP is used for returning a charging start response to the RG; returning a charging start response to the TWAG; associating or binding corresponding sessions according to user identifications carried in the messages after receiving charging start requests respectively sent by the RG and the TWAG;
and the TWAG is used for sending the user identifier and/or the session identifier and the IP address successfully allocated to the user equipment to the TWAP through a charging start request after the user equipment is accessed to the interactive PMIP/GTP instruction in the user equipment and an S2a session and a PMIP/GTP tunnel are established.
21. The system of claim 20,
the RG is further configured to receive terminating connection information from the user equipment, and send a charging stop request to the TWAP, where the charging stop request carries a user identifier and/or a session identifier;
the TWAP is also used for returning a charging stop response to the RG; initiating a RADIUS connection interruption request to the TWAG according to the self-stored association or binding result; returning a charging stop response to the TWAG;
the TWAG is also used for initiating a charging stop request to the TWAP; and PMIP/GTP signaling is interacted with the PDN-GW, the S2a conversation is deleted, and a GTP/PMIP tunnel is released.
22. The system of claim 15, wherein the BBF access network comprises at least TWAG, PDN-GW, TWAP;
the TWAG is used for sending a charging start request carrying a user identifier and/or a session identifier and an IP address successfully allocated for the user equipment to the WRAP after an S2a session and a PMIP/GTP tunnel are established by accessing an interactive PMIP/GTP instruction in the user equipment;
and the TWAP is used for returning a charging start response to the TWAG.
23. The system of claim 22,
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 also used for returning a terminating confirmation message to the RG; associating 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; initiating a RADIUS connection interruption request to the TWAG according to the self-stored association or binding result; returning a charging stop response to the TWAG;
the TWAG is also used for initiating a charging stop request to the TWAP; and PMIP/GTP signaling is interacted with the PDN-GW, the S2a conversation is deleted, and a GTP/PMIP tunnel is released.
CN201310131457.1A 2013-04-16 2013-04-16 A kind of method and system for realizing user's termination connection Expired - Fee Related CN104113930B (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN201310131457.1A CN104113930B (en) 2013-04-16 2013-04-16 A kind of method and system for realizing user's termination connection
PCT/CN2014/075158 WO2014169781A1 (en) 2013-04-16 2014-04-11 Method and system for terminating connection by user

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201310131457.1A CN104113930B (en) 2013-04-16 2013-04-16 A kind of method and system for realizing user's termination connection

Publications (2)

Publication Number Publication Date
CN104113930A true CN104113930A (en) 2014-10-22
CN104113930B CN104113930B (en) 2019-02-15

Family

ID=51710522

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201310131457.1A Expired - Fee Related CN104113930B (en) 2013-04-16 2013-04-16 A kind of method and system for realizing user's termination connection

Country Status (2)

Country Link
CN (1) CN104113930B (en)
WO (1) WO2014169781A1 (en)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108934022A (en) * 2017-05-25 2018-12-04 华为技术有限公司 A kind of register method and device
CN110311934A (en) * 2018-03-22 2019-10-08 电信科学技术研究院有限公司 A kind of signaling connection method for releasing and communication device
CN115426139A (en) * 2021-11-19 2022-12-02 华为技术有限公司 Access control method based on SIM card information and communication device

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP6876232B2 (en) * 2016-09-26 2021-05-26 富士フイルムビジネスイノベーション株式会社 Image forming device and program

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102457847A (en) * 2010-10-21 2012-05-16 中兴通讯股份有限公司 Fixed network perception user access method and system thereof
CN102857585A (en) * 2011-06-30 2013-01-02 中兴通讯股份有限公司 Method and system for distributing address and executing strategy of BBF (Broadband Forum) network
CN102932915A (en) * 2011-08-08 2013-02-13 中兴通讯股份有限公司 Session establishment method and system
US20130089013A1 (en) * 2011-10-07 2013-04-11 Roberto David Carnero Ros Bng to pcrf mediation entity for bbf and 3gpp access interworking

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102457847A (en) * 2010-10-21 2012-05-16 中兴通讯股份有限公司 Fixed network perception user access method and system thereof
CN102857585A (en) * 2011-06-30 2013-01-02 中兴通讯股份有限公司 Method and system for distributing address and executing strategy of BBF (Broadband Forum) network
CN102932915A (en) * 2011-08-08 2013-02-13 中兴通讯股份有限公司 Session establishment method and system
US20130089013A1 (en) * 2011-10-07 2013-04-11 Roberto David Carnero Ros Bng to pcrf mediation entity for bbf and 3gpp access interworking

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108934022A (en) * 2017-05-25 2018-12-04 华为技术有限公司 A kind of register method and device
CN110311934A (en) * 2018-03-22 2019-10-08 电信科学技术研究院有限公司 A kind of signaling connection method for releasing and communication device
CN110311934B (en) * 2018-03-22 2020-10-20 电信科学技术研究院有限公司 Signaling connection release method and communication device
CN115426139A (en) * 2021-11-19 2022-12-02 华为技术有限公司 Access control method based on SIM card information and communication device

Also Published As

Publication number Publication date
WO2014169781A1 (en) 2014-10-23
CN104113930B (en) 2019-02-15

Similar Documents

Publication Publication Date Title
EP2244424B1 (en) A method for selecting a policy and charging rules function server on a non-roaming scene
JP5793812B2 (en) Method, network side device, user equipment, and network system for triggering data offload
US9167430B2 (en) Access method and system, and mobile intelligent access point
CN102457847B (en) A kind of method and system of fixed network perception user access
JP5903728B2 (en) Method and trusted gateway for WIFI terminal to access packet data PS service domain
US9113436B2 (en) Method and system for information transmission
WO2013107136A1 (en) Terminal access authentication method and customer premise equipment
US9544832B2 (en) Method, apparatus and system for policy control
WO2010081329A1 (en) Method and system for controlling network resources during service flow migrating procedure
WO2012094957A1 (en) Method and system for performing mobility management on mtc terminal
WO2012051897A1 (en) System and method for integrating fixed network with mobile network
WO2014176964A1 (en) Communication managing method and communication system
JP5972467B2 (en) Method and system for notifying location information of access network
WO2012003770A1 (en) System, device and method for user equipment to access mobile network
WO2010133107A1 (en) Method and system for home node b gateway forwarding messages to home node b
US20140177530A1 (en) Access method and system and mobile intelligent access point
CN104113930B (en) A kind of method and system for realizing user's termination connection
WO2012100611A1 (en) Method and system for accessing evolved packet system
CN103139914A (en) Resource control method and system on local unloaded data
WO2013107243A1 (en) Session establishing method and device
WO2012019506A1 (en) Method and system for implementing resource control in a fixed network and mobile network integration scenario
CN103024865B (en) A kind of core network access and network side initiate the method and system of attachment removal
CN102572932B (en) Method and system for achieving domestic base station network source differentiated management and control
WO2014071798A1 (en) Method for managing offload connection, radio-side network element and mobility management entity
WO2015054847A1 (en) Communication method, local gateway, base station, mme, and system

Legal Events

Date Code Title Description
C06 Publication
PB01 Publication
C10 Entry into substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant
CF01 Termination of patent right due to non-payment of annual fee

Granted publication date: 20190215

Termination date: 20200416

CF01 Termination of patent right due to non-payment of annual fee