WO2008144991A1 - Procédé de mise en oeuvre et système de communications pour sauvegarder l'adresse d'un point d'ancrage de réseau à un serveur de réseau - Google Patents

Procédé de mise en oeuvre et système de communications pour sauvegarder l'adresse d'un point d'ancrage de réseau à un serveur de réseau Download PDF

Info

Publication number
WO2008144991A1
WO2008144991A1 PCT/CN2007/071260 CN2007071260W WO2008144991A1 WO 2008144991 A1 WO2008144991 A1 WO 2008144991A1 CN 2007071260 W CN2007071260 W CN 2007071260W WO 2008144991 A1 WO2008144991 A1 WO 2008144991A1
Authority
WO
WIPO (PCT)
Prior art keywords
network
address
pdn
anchor
terminal
Prior art date
Application number
PCT/CN2007/071260
Other languages
English (en)
Chinese (zh)
Inventor
Jian Zhang
Wenruo Zhu
Lan Liu
Sihong Zhou
Yanglai Shuai
Haining Wang
Original Assignee
Huawei Technologies Co., Ltd.
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
Priority claimed from CN200710140572XA external-priority patent/CN101316440B/zh
Application filed by Huawei Technologies Co., Ltd. filed Critical Huawei Technologies Co., Ltd.
Publication of WO2008144991A1 publication Critical patent/WO2008144991A1/fr
Priority to US12/550,867 priority Critical patent/US8244242B2/en
Priority to US13/551,376 priority patent/US8483686B2/en
Priority to US13/915,877 priority patent/US9271250B2/en
Priority to US14/990,216 priority patent/US9756596B2/en
Priority to US15/660,064 priority patent/US10264543B2/en
Priority to US16/360,562 priority patent/US10869291B2/en
Priority to US17/100,173 priority patent/US11490350B2/en

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/54—Store-and-forward switching systems 
    • H04L12/56—Packet switching systems
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
    • H04W60/04—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration using triggered events
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/06—Registration at serving network Location Register, VLR or user mobility server
    • H04W8/065—Registration at serving network Location Register, VLR or user mobility server involving selection of the user mobility server

Definitions

  • the terminal After attaching to an access network, the terminal will select a network anchor to connect to the external packet data network (PDN, Packet Data Network).
  • PDN Packet Data Network
  • the IP address used by the terminal will be assigned by the network anchor or by the external PDN network. provide.
  • the network side entity can obtain the address of the network anchor point by using an Access Point Name (APN), and in the non-3GPP access technology, the terminal can be connected at the terminal.
  • the APN obtained when the authentication is obtained or obtained through the access authentication obtains the address of the network anchor to the domain name server (DNS, Domin Name Server). It can be seen that the way to obtain the network anchor address between different access technologies is different.
  • DNS Domin Name Server
  • a person skilled in the art proposes an idea to save the address of the network anchor obtained in an access network in the network server, when the terminal switches from the access network.
  • the address of the network anchor point is obtained from the network server, so that the terminal can obtain the address of the same network anchor point regardless of which network is switched, thereby ensuring the user. The data will not be lost.
  • the terminal initiates attaching or initiates bearer establishment, and the network side selects a network anchor point;
  • the network anchor allocates a first bearer context to the terminal or in a process in which the network anchor establishes a connection with the terminal for the first time, the network side registers the address of the network anchor to the network server.
  • the embodiment of the invention further provides a communication system, including:
  • connection establishment entity configured to establish a connection with the terminal for the first time by the network anchor point
  • An address registration entity is configured to register an address of the network anchor to the network server in a process in which the network anchor establishes a connection with the terminal for the first time.
  • Another technical problem to be solved by embodiments of the present invention is to provide an address of a network anchor point.
  • the implementation method and the communication system are deleted from the network server to provide a feasible technical solution for deleting the address of the network anchor from the network server, and propose a scenario in which the network side server entity initiates the bearer deletion and gives relevant specific Process.
  • An embodiment of the present invention provides an implementation method for deleting an address of a network anchor from a network server, including:
  • the network server deregisters the address of the network anchor.
  • the embodiment of the invention further provides a communication system, including:
  • Another technical problem to be solved by the embodiments of the present invention is to provide a method for implementing the terminal to retire the network, to provide a feasible technical solution for the terminal to quit the network, and to provide a specific process for the terminal to quit the network.
  • FIG. 5 is a flowchart of a fourth preferred embodiment of an implementation method for saving an address of a network anchor point to a network server according to the present invention
  • FIG. 7 is a flowchart of a sixth preferred embodiment of an implementation method for saving an address of a network anchor point to a network server according to the present invention.
  • FIG. 9 is a flowchart of an eighth preferred embodiment of an implementation method for saving an address of a network anchor point to a network server according to the present invention.
  • 15 is a flowchart of a fifth preferred embodiment of an implementation method for deleting an address of a network 4 seed point from a network server according to the present invention.
  • 16 is a flowchart of a sixth preferred embodiment of an implementation method for deleting an address of a network 4 seed point from a network server according to the present invention
  • FIG. 18 is a flowchart of an eighth preferred embodiment of an implementation method for deleting an address of a network 4 seed point from a network server according to the present invention.
  • FIG. 19 is a flowchart of a ninth preferred embodiment of an implementation method for deleting an address of a network 4 seed point from a network server according to the present invention.
  • Step S202 The evolved base station (eNodeB) forwards the attach request to the new MME (new MME), and the attach request carries the identifier of one cell. Specifically, the eNodeB may query the address of the MME from the selected network identifier and the S-TMSI. If the MME cannot be inferred, an MME may be selected.
  • IMSI International Mobile Subscriber Identity
  • S-TMSI S-Temporary Mobile Subscriber Identity
  • TAI Tracking Area Identity
  • Step S202 The evolved base station (eNodeB) forwards the attach request to the new MME (new MME), and the attach request carries the identifier of one cell. Specifically, the eNodeB may query the address of the MME from the selected network identifier and the S-TMSI. If the MME cannot be inferred, an MME may be selected.
  • Step S203 The new MME sends an identifier request to the original MME (old MME).
  • the old MME can provide IMSI to respond to the identification request (Identification Response).
  • the S-TMSI and the MME identifying the UE have changed, and the new MME may send the S-TMSI and the old TAI to the old MME to request the IMSI.
  • Step S204 If neither the new MME nor the old MME identify the UE, the new MME sends an identity request to the UE to request the IMSI, and the UE may provide the IMSI to the new MME to respond to the identity request.
  • Step S205 If the context of the UE does not exist in the network, an authentication message (Authentication) needs to be enforced.
  • Authentication an authentication message
  • Step S206 If there are some bearer contexts of the active state related to the UE in the new MME, the new MME needs to send a Delete Bearer Request to the relevant gateway (such as the PDN GW in the figure), and the related gateway can respond.
  • the Delete Bearer Response is deleted, so that the new MME deletes the bearer context.
  • Step S212 The new MME sends a Create Default Bearer Request to the selected Serving GW, where the default bearer request may include the context identifiers of the IMSI and the new MME.
  • Step S216 a If the UE subscribes to the non-3GPP mobility capability, the new MME may register the address of the PDN GW and the corresponding APN to the HSS. Of course, the new MME may also set the address of the PDN GW according to its own configuration parameters. Registered to the HSS to maintain business continuity when the UE switches between the 3GPP network and the non-3GPP network. Specifically, when obtained from step S211a After taking the address of a group of PDN GWs, new ⁇ will select an appropriate PDN GW according to the description in step S211a. After the bearer between the Serving GW and the PDN GW is successfully established, the new MME can set a selected PDN GW address. The flag is registered to the HSS to indicate that this PDN GW has been selected by the new MME as the user PDN anchor.
  • Step S218 The eNodeB sends a radio bearer setup request (Radio Bearer Establishment)
  • Step S219 The UE sends a Radio Bearer Establishment Response (Radio Bearer Establishment Response) to the eNodeB.
  • the UE may also send an attach complete message to the eNodeB.
  • the attach accept message may be included in the radio bearer setup response, and vice versa, the radio bearer
  • the setup response can also be included in the attach accept message.
  • Step S220 The eNodeB forwards the attach complete message to the new MME, where the attach complete message may be included in the control message of the S1-MME interface, and the control message also includes the downlink tunnel information.
  • Step S221 The new MME sends an Update Bearer Request message to the Serving GW, where the Update Bearer Request message may include an eNodeB address, a downlink tunnel parameter, and the like.
  • Step S222 The Serving GW returns an Update Bearer Response message (Update Bearer Response) to the new MME.
  • different bearers may be triggered by different network side entities, for example, a pre-established virtual personal network. (VPN, Virtual Private Network) scenario, proprietary signaling bearer, etc.
  • These network side entities may be MME, Serving GW, PCRF, PDN GW, etc. Therefore, it is also necessary to register the address of the PDN GW selected when establishing a new bearer. To the HSS. In this way, the addresses of the PDN GWs of different bearers need to be saved in the HSS, and the addresses of the PDN GWs selected by different bearers may be different.
  • HSS HSS and authentication, authorization, and accounting (AAA, Authority, Authentication,
  • the foregoing MME may be equivalent to an access gateway entity such as an ePDG, an Access Serving Network Gateway (ASN GW, Access Serving Network Gateway), etc., after the bearer is successfully established, These entities register the address of the PDN GW with the AAA server.
  • an access gateway entity such as an ePDG, an Access Serving Network Gateway (ASN GW, Access Serving Network Gateway), etc.
  • the MME since the MME is a control plane entity and has an interface with the HSS, the MME can select the relevant PDN GW for the first time when the UE selects the relevant PDN GW by using the parameters configured by itself.
  • the address of a good PDN GW is registered in the HSS.
  • Step S311a The new MME selects an appropriate PDN GW according to information such as APN or FQDN.
  • the policy of selecting the PDN GW can be based on the APN mode, and refer to the UPE pool configuration, the PDN GW location relationship, the device load, the operator's subscription information, and the roaming protocol.
  • the HSS can also provide a set of PDN GW addresses.
  • the new MME can directly select the appropriate PDN GW according to the configuration of the UPE pool, the location relationship of the PDN GW, the device load, the operator's subscription information, and the roaming agreement.
  • Step S312 The new MME sends a setup default bearer request to the Serving GW, where the establishing the default bearer request may include a parameter for registering the address of the PDN GW to the HSS/SPR, where the parameter indicates that the PDN GW selects the selected PDN GW through the PCC system.
  • the address is registered in the HSS/SPR.
  • the parameters are optional, ie the PDN GW can directly configure the relevant options to ensure that the address of the PDN GW is registered to the HSS/SPR/AAA through the PCC system.
  • an associated attribute value pair (AVP, Attribute Value Pair) attribute may be added to trigger the PCRF to register the address of the PDN GW to the HSS/SPR, as follows:
  • ⁇ CC-Request>:: ⁇ Diameter Header: 272, REQ, PXY >
  • Origin-State-Id Origin-State-Id ]
  • Bearer-Identifier [ Bearer-Operation ]
  • Termination-Cause [ Termination-Cause ]
  • Step S314a The PCRF may initiate a process of acquiring the subscription data of the UE to the HSS/SPR, and register the address of the PDN GW to the HSS/SPR. In addition, if the PCRF has the subscription data of the UE, the PCRF may only initiate the process of registering the address of the PDN GW to the HSS/SPR.
  • the foregoing MME may be equivalent to an access gateway entity such as ePDG, ASN GW, etc., and after the bearer is successfully established, the PDN GW may use the PCC system to the HSS/AAA/SPR server. Register the address of the PDN GW.
  • the PDN GW address is registered to the HSS/SPR
  • the APN information also needs to be registered with the PDN GW to the HSS/SPR.
  • the HSS shall store the correspondence between the APN and the PDN GW.
  • Steps S401-S411, these steps are the same as steps S201-S211 shown in Fig. 2.
  • Step S411a The new MME selects an appropriate PDN GW according to information such as APN or FQDN.
  • the policy of selecting the PDN GW can be based on the APN mode, and refer to the UPE pool configuration, the PDN GW location relationship, the device load, the operator's subscription information, and the roaming protocol.
  • the HSS can also provide a set of PDN GW addresses.
  • the new MME can directly select the appropriate PDN GW according to the configuration of the UPE pool, the location relationship of the PDN GW, the device load, the operator's subscription information, and the roaming agreement.
  • this step is optional, for example, when the UE in the active state switches from the non-3GPP network to the 3GPP network or when the 3GPP network first attaches, the HSS only provides a unique PDN GW address to the new MME.
  • new MME needs to determine whether to trigger the PDN GW to register its own address to
  • the condition of the HSS/SPR may be based on the subscription data of the UE or the parameter configured by the new MME itself.
  • Step S412 The new MME sends a setup default bearer request to the Serving GW, where the establishment of the default bearer request may include a parameter for registering the address of the PDN GW to the HSS/SPR.
  • the parameters are optional, that is, the PDN GW can directly configure the relevant option parameters to ensure that its own address is directly registered to the HSS/SPR/AAA.
  • Step S413 The Serving GW establishes a new entity in the EPS bearer table, and transparently transmits the default 7-load request sent by the new MME to the PDN GW.
  • Step S414 The PDN GW registers its own address to the HSS/AAA, and the HSS/AAA returns the phase. The indication of the off is given to the PDN GW.
  • Steps S415-S422 may be the same as steps S215-S222 of FIG. 2, except that, in step S412, the establishment of the default bearer request sent by the new MME to the Serving GW includes a parameter for registering the address of the PDN GW to the HSS/SPR. Then, the setup default bearer response message in steps S415 and S416 may include parameters for successfully registering the PDN GW to the HSS/SPR.
  • the foregoing MME may be equivalent to an access gateway entity such as ePDG, ASN GW, etc., after the bearer is successfully established, the PDN GW may directly register its own address with the HSS/AAA server. .
  • Step S503 The SGSN sends a PDP context request message to the Serving GW, where the Activate PDP context request message may include the address of the PDN GW and the APN information, and may also include an indication of whether the PDN GW needs to register its own address to the HSS. It should be noted that this indication is optional.
  • Step S504 The Serving GW sends a SAE (System Architecture Evolution) request (Create SAE Bearer Request) to the PDN GW, where the activated SAE bearer request may include information such as a registration indicator bit and an APN.
  • SAE System Architecture Evolution
  • Step S504a The PDN GW requests the PCC rule from the V/H PCRF.
  • the establishment of the SAE bearer response may include a PDN GW successfully registered to
  • Step S506 The Serving GW returns a Create PDP context response to the SGSN, where the PDP context response may include a parameter that the PDN GW successfully registers with the HSS.
  • Step S507 The SGSN returns an Active PDP context accept message to the UE.
  • step S502 the selection of the PDG GW address may also be by Serving.
  • the GW performs the selection.
  • the SGSN sends a message to the Serving GW to establish a bearer request, which only includes the address of the APN or a group or a PDN GW.
  • the Serving GW may select the PDN GW according to some conditions.
  • a parameter may also be added in step S504 to instruct the PDN GW to register its own address into the HSS/AAA server.
  • the address of the PDN GW is registered by the SGSN to the HSS. This embodiment contains a scene of Local breakout.
  • Step S601 The UE sends an Activate Packet Data Protocol Context Request message to the SGSN.
  • Step S602 The SGSN selects the related Serving GW and the PDN GW according to the subscription data of the UE and the APN information carried in the activated PDP context request message.
  • Step S603 The SGSN sends a PDP context request message to the Serving GW, where the PDP context request message may include the address of the PDN GW and the APN information.
  • the PDN GW may also be selected by the Serving GW according to the APN information and other conditions.
  • the SGSN may also provide a set of PDN GW addresses, and the Serving GW integrates some conditions such as load, network configuration, etc. to select the PDN GW.
  • Step S604 The Serving GW sends a setup SAE bearer request to the PDN GW, where the activated SAE bearer request may include the APN information or the address of the PDN GW.
  • Step S604a The PDN GW can interact with the PCRF to obtain a PCC rule.
  • Step S605 The PDN GW returns a setup SAE bearer response to the Serving GW.
  • Step S606 The Serving GW returns a PDP context response message to the SGSN, where the message may include a PDN W address if the address is selected by the Serving GW.
  • Step S607 The SGSN may determine whether the address of the PDN GW needs to be registered to the HSS according to the subscription data of the UE, whether the UE has a non-3GPP mobility capability, or a parameter configured by itself.
  • the address of the PDN GW may be obtained by the SGSN by querying the APN information, or may be provided by the Serving GW in step S606.
  • the PDN GW address is registered to the HSS/SPR
  • the APN information also needs to be registered with the PDN GW to the HSS/SPR.
  • the HSS shall store the correspondence between the APN and the PDN GW.
  • Step S702 The SGSN selects the related Serving GW and the PDN GW according to the APN information, and determines whether the PCC system is triggered to register the address of the PDN GW to the HSS/SPR, and the determined condition may be based on the subscription data of the UE or the parameter configured by the SGSN itself. In addition, the SGSN may also determine whether to register the address of the PDN GW to the HSS/SPR through the PCC system by directly determining the configuration parameters on the PDN GW.
  • the SGSN can select the Serving GW and the PDN GW by using the DNS query mode according to the APN information, the parameters configured by itself, or the subscription data of the UE. For example, the Serving GW and the PDN GW are selected by two DNS query methods. In addition, the SGSN provides the address information of the PDN GW to the Serving GW;
  • the Serving GW may select the PDN GW by using the DNS query mode according to the parameters configured by itself or the subscription data of the UE. For example, the SGSN may provide the APN information to the Serving GW, and the Serving GW queries the DNS system to obtain the PDN GW information.
  • Step S703 The SGSN sends an activation PDP context request message to the Serving GW, where the activation PDP context request message includes a parameter for registering the address of the PDN GW to the HSS/SPR, and is used to indicate that the address of the PDN GW is registered to the HSS through the PCC system. /SPR.
  • the parameters are optional.
  • the PDN GW can also be selected by the Serving GW according to information such as APN.
  • Step S704a An interaction process involving the PCRF, where the Local breakout scenario is included.
  • the PDN GW When the PDN GW is located at the roaming place, it can interact with the H-PCRF through the V-PCRF.
  • Step S704b The PCRF may initiate a process of acquiring the subscription data of the UE to the HSS/SPR, and register the address of the PDN GW to the HSS/SPR. If the PCRF has subscription data for the UE, the PCRF only initiates the process of registering the address of the PDN GW to the HSS/SPR.
  • Step S705 The PDN GW returns an activated SAE bearer response to the Serving GW, where the response message may include a parameter identifier for successful registration.
  • Step S706 The Serving GW returns an Activate PDP context response message to the SGSN, where the response message may include a parameter identifier for successful registration.
  • Step S707 The SGSN returns an Activate PDP context accept message to the UE.
  • FIG. 8 , FIG. 9 and FIG. 10 respectively describe how to implement the process of registering the address of the PDN GW to the HSS/SPR when the terminal initiates the bearer setup in the SAE/LTE access network.
  • the PDN GW address is registered to the HSS/SPR
  • the APN information also needs to be registered with the PDN GW to the HSS/SPR.
  • the HSS shall store the correspondence between the APN and the PDN GW.
  • Step S801 The UE initiates an activation SAE bearer request.
  • Step S802 The new MME selects a PDN GW, where the scenario includes multiple PDNs.
  • Step S803 - S806 Perform a bearer establishment process on the core network side.
  • Step S807 The new MME initiates the process of registering the address of the PDN GW to the HSS.
  • the new MME may determine whether the registration process needs to be initiated according to the subscription data of the UE, the capability of the UE, or the parameters configured by the UE. .
  • Step S808 The new MME returns an active SAE bearer request response, and the activated SAE bearer request response may include configuration parameters of the relevant wireless side and related uplink tunnel configuration information.
  • eNodeB The message contains parameters for establishing an air interface radio bearer. The eNodeB will establish an associated radio bearer according to the provided parameters for establishing a radio bearer.
  • Step S809 - S810 Establish a radio bearer process.
  • Step S811 The eNodeB sends an Update Bearer Request to the new MME, where the update bearer request may include information about the relevant downlink tunnel between the eNodeB and the Serving GW.
  • Step S814 The Serving GW returns an Update Bearer Response (Update Bearer Response) to the new MME.
  • the scenario in which the UE initiates a service on the non-3GPP network such as a scenario of multiple PDNs and multiple home agents (HAs) may be included, such that the MME is equivalent to the ePDG.
  • An access control plane gateway entity such as the ASN GW may register the address of the PDN GW directly with the HSS/AAA/SPR server by an entity such as the ePDG or the ASN GW after the bearer is successfully established. If the AAA and the HSS are separate entities, the address of the registered PDN GW can be passed from the AAA to the HSS.
  • the UE initiates the establishment of the service of the external PDN GW network for the first time in the SAE/LTE access network, the address of the PDN GW is registered to the HSS through the PCC system.
  • This embodiment contains a scenario of Local breakout.
  • Step S901 The UE initiates an activation SAE bearer request.
  • Step S902 The new MME selects one PDN GW.
  • Step S903 The new MME sends a setup SAE bearer request to the Serving GW, where the activated SAE bearer request may include the address of the selected PDN GW.
  • Step S905 The PDN GW can interact with the PCRF to obtain a default PCC rule set for the UE.
  • the PDN GW When the PDN GW is located at the roaming place, it will interact with the H-PCRF through the V-PCRF.
  • Step S906 The PDN GW returns an activated SAE bearer request response to the Serving GW, where the activated SAE bearer request response may include QoS information.
  • Step S907 The Serving GW returns an activated SAE bearer request response to the new MME, where the activated SAE bearer request response may include the quality of service information.
  • Step S908 The new MME returns a process of activating the SAE bearer request response and configuring the configuration RB to the UE.
  • Step S910 The eNodeB sends a radio bearer setup request to the UE.
  • Step S911 The UE returns a radio bearer setup response to the eNodeB.
  • Step S912 The eNodeB sends an update bearer request to the new MME.
  • Step S914 The new MME sends an update bearer request to the Serving GW.
  • Step S915 The Serving GW returns an update bearer response to the new MME.
  • the scenario that the UE initiates a service on the non-3GPP network such as a scenario of multiple PDNs and multiple HAs, may be included, such that the MME is equivalent to the ePDG, the ASN GW, and the like.
  • the access control plane gateway entity may register the address of the PDN GW with the HSS/AAA/SPR server by the PDN GW through the PCC system after the bearer is successfully established. If the AAA and the HSS are separate entities, the address of the registered PDN GW can be passed from the AAA to the HSS.
  • the PDN GW directly registers its own address to the HSS. This embodiment contains a scene of Local breakout.
  • Step S1002 The new MME selects a PDN GW.
  • Step S1003 The new MME sends an activation SAE bearer request to the Serving GW, where the activated SAE bearer request may include the address of the selected PDN GW.
  • Step S1004 The Serving GW sends an Activate SAE Bearer Request to the PDN GW, where the Activate SAE Bearer Request may include the address of the selected PDN GW.
  • Step S 1005a If the UE first establishes a bearer to the PDN GW, the PDN GW registers its own address directly to the HSS/SPR.
  • Step S1007 The Serving GW returns an active SAE bearer request response to the new MME, and the activated SAE bearer request response may include the quality of service information.
  • Step S1008 The new MME returns a process of activating the SAE bearer request response and configuring the wireless bearer to the UE.
  • Step S1012 The eNodeB sends an update bearer request to the new MME.
  • Step S1013 The eNodeB returns an active SAE bearer request response to the UE.
  • Step S1015 The Serving GW returns an update bearer response to the new MME.
  • a scenario in which a UE initiates a service on a non-3GPP network such as a scenario of multiple PDNs and multiple HAs, may be included, such that the MME is equivalent to an ePDG, an ASN GW, or the like.
  • the access control plane gateway entity can directly register its own address to the HSS/AAA/SPR by the PDN GW after the bearer is successfully established. If AAA and HSS are separate entities, the address of the registered PDN GW can be passed from AAA to the HSS.
  • the PDN GW address is registered to the HSS/SPR
  • the APN information also needs to be registered with the PDN GW to the HSS/SPR.
  • the HSS shall store the correspondence between the APN and the PDN GW.
  • the present invention also provides an embodiment of a communication system.
  • a communication system provided by the embodiment of the present invention includes: a bearer context assigning entity, configured to allocate a first bearer context to a terminal by a network anchor point; and an address registration entity, configured to register an address of the network anchor point to the network server.
  • the address registration entity is further configured to: when the access network supports multiple packet data networks PDN, or the network anchor points correspond to multiple PDNs, connect the network anchor points The ingress identification APN is registered to the web server.
  • the address registration entity is: a mobility management entity, or a serving GPRS support node, or an access network entity, or an entity in the network anchor, or policy control and charging system.
  • the current service of the terminal may need to be terminated, correspondingly, saved in The address of the PDN GW in the HSS can also be deleted.
  • the present invention also provides a technical solution for deleting the address of the network anchor from the network server.
  • FIG. 11 , FIG. 12 and FIG. 13 respectively describe how to delete the address of the PDN GW from the HSS when the terminal initiates bearer deletion in the SAE/LTE access network.
  • Step S1101 The UE initiates a Deactivate SAE Bearer Request.
  • Step S1102 The new MME sends a deactivation SAE bearer request to the Serving GW, where the deactivated SAE bearer request may include information indicating that the PDN GW deregisters the PDN GW address in the HSS/SPR through the PCC system.
  • Step S1103 The Serving GW sends a deactivated SAE bearer request to the PDN GW, where the deactivated SAE bearer request may include information indicating that the PDN GW deregisters the PDN GW address in the HSS/SPR through the PCC system.
  • the deregistration message triggering the PDN GW may be provided by the MME or by the Serving GW, or the PDN GW may decide to initiate the behavior of deregistering the PDN GW address through the PCC system according to the network configuration.
  • Step S1104 The PDN GW interacts with the PCRF to release related binding information.
  • Step S1105 The PDN GW returns a Deactive SAE Bearer Response to the Serving GW. If the deactivated SAE bearer request in step S1102 includes an indication, the deactivated SAE bearer response may also include a successful deregistration. Instructions. Step SI 106: The Serving GW returns a deactivated SAE bearer response to the new MME, where the message may include an indication of successful deregistration.
  • Step S1107 The new MME returns a deactivated SAE bearer response to the UE.
  • the embodiment shown in FIG. 11 may include a scenario in which the UE ends the service in the non-3GPP network, for example, a scenario of multiple PDNs and multiple HAs.
  • all services on the PDN GW are completed, all services may be ended.
  • the address of the PDN GW is deregistered by the PDN GW to the HSS/AAA/SPR server through the PCC system. If AAA and HSS are separate entities, the deregistered parameters or information can be passed to the HSS by AAA.
  • the PDN GW when all bearers on the PDN GW for the UE are released, the PDN GW directly deletes its own address stored in the HSS/SPR.
  • Step S1201 The UE initiates a deactivation of the SAE bearer request.
  • Step S1202 The new MME sends a deactivation SAE bearer request to the Serving GW, where the deactivated SAE bearer request may include information indicating that the PDN GW directly deregisters the self address in the HSS/SPR.
  • Step S1204 The PDN GW interacts with the PCRF to release related binding information. This step is optional and includes a Local breakout scenario, ie, interacting with the HPCRF via the VPCRF.
  • Step S1204a The PDN GW directly deregisters the self address (Unregister PDN GW to HSS) in the HSS/SPR. Before de-registration, the PDN GW can determine whether it needs to directly de-register its own address in the HSS/SPR according to the received indication information or its own configured parameters.
  • Step S1205 The PDN GW returns a deactivated SAE bearer response to the Serving GW. If the deactivated SAE bearer request in step S1202 includes an indication, the deactivated SAE bearer response may also include an indication of successful deregistration.
  • Step S1207 The new MME returns a deactivated SAE bearer response to the UE.
  • the embodiment shown in FIG. 12 may include a scenario in which the UE ends the service in the non-3GPP network, for example, a scenario of multiple PDNs and multiple HAs.
  • the UE may The PDN GW directly deregisters its own address with the HSS/AAA/SPR server. If AAA and HSS are separate entities, the parameters or information for deregistration can be
  • AAA is passed to the HSS.
  • the MME deletes the address of the PDN GW stored in the HSS/SPR.
  • Step S1301 The UE initiates a deactivation of the SAE bearer request.
  • Step S1302 The new MME sends a deactivation SAE bearer request to the Serving GW.
  • Step S1303 The Serving GW sends a deactivated SAE bearer request to the PDN GW.
  • Step S1304 The PDN GW interacts with the PCRF to release related binding information. This step is optional and includes a Local breakout scenario, ie, interacting with the HPCRF via the VPCRF.
  • Step S1306a The new MME de-registers the address of the PDN GW in the HSS/SPR. Before the solution is released, the new MME can determine whether the address of the PDN GW in the HSS/SPR needs to be deregistered according to the subscription data of the UE or the parameters configured by itself.
  • FIG. 14 , FIG. 15 and FIG. 16 respectively describe how to delete the address of the PDN GW from the HS S when the MME initiates the bearer deletion process.
  • Step S1401 The new MME sends a deactivation SAE bearer request to the Serving GW.
  • the deactivated SAE bearer request may include a message indicating that the PDN GW is to deregister the PDN GW address in the HSS.
  • the new MME may determine whether it is necessary to send the indication to the Serving GW according to the subscription data of the UE or the parameters configured by itself.
  • Step S1402 The Serving GW sends a deactivated SAE bearer request to the PDN GW.
  • Step S1403 The PDN GW interacts with the PCRF to release the related binding information.
  • This step is optional and includes a Local breakout scenario, ie, interacting with the HPCRF via the VPCRF.
  • Step S1405 The PDN GW returns a deactivated SAE bearer response to the Serving GW. If the deactivated SAE bearer request of step S1401 contains an explicit indication, the deactivated SAE bearer response may also contain an indication of successful deregistration.
  • Step S1406 The Serving GW returns a deactivated SAE bearer response to the new MME. An indication of successful deregistration can be included in the message.
  • the original HSS saves the mapping between the PDN GW and the APN.
  • the deregistration process of the PDN GW also includes deleting the mapping between the PDN GW address and the APN stored in the HSS/SPR.
  • the MME deletes the address of the PDN GW stored in the HSS/AAA/SPR.
  • Step S1501 The new MME sends a deactivate SAE bearer request to the Serving GW.
  • Step S1502 The Serving GW sends a deactivated SAE bearer request to the PDN GW.
  • Step S1503 The PDN GW interacts with the PCRF to release the related binding information. This step is optional and includes a Local breakout scenario, ie, interacting with the HPCRF via the VPCRF.
  • Step S1504 The PDN GW returns a deactivated SAE bearer response to the Serving GW.
  • Step S1505 The Serving GW returns a deactivated SAE bearer response to the new MME.
  • Step S1506 The new MME de-registers the address of the PDN GW in the HSS/SPR. Before the solution is released, the new MM can determine whether the address of the PDN GW needs to be unregistered with the HSS/SPR according to the subscription data of the UE or the parameters configured by itself.
  • Step S 1507 The new MME sends a deactivated SAE bearer request to the UE.
  • the new MME may also instruct the eNodeB to release the associated radio bearer.
  • this indication may also be sent after step S1501.
  • Step S1508 The UE returns a deactivated SAE bearer response to the new MME.
  • the embodiment shown in FIG. 15 may include a scenario in which the UE ends the service in the non-3GPP network, such as a scenario of multiple PDNs and multiple HAs, and may also include an ePDG and an ASN GW.
  • the entity initiates the bearer deletion process when the PDN GW completes all the services of the UE, the entity corresponding to the MME, such as the ePDG and the ASN GW, can deregister the address of the PDN GW to the HSS/AAA/SPR server. If the AAA and the HSS are separate entities, then the parameters or information for the deregistration need to be passed from the AAA to the HSS.
  • Step S1601 The new MME sends a deactivation SAE bearer request to the Serving GW.
  • the deactivated SAE bearer request may include information indicating that the PDN GW de-registers the PDN GW address in the HSS/SPR through interaction with the PCC system.
  • the new MME may also determine whether the indication needs to be sent to the Serving GW according to the subscription data of the UE or the parameters configured by itself.
  • Step S1603 The PDN GW interacts with the PCRF to release the related binding information.
  • This step is optional and includes a Local breakout scenario, ie, interacting with the HPCRF via the VPCRF.
  • the PDN GW can also determine whether it is necessary to trigger the PCC system to deregister the address of the PDN GW in the HSS/SPR according to the received indication information or the parameters configured by itself.
  • Step S1604 The PCRF interacts with the HSS/SPR to deregister the address of the PDN GW in the HSS/SPR.
  • Step S1605 The PDN GW returns a deactivated SAE bearer response to the Serving GW. If the deactivated SAE bearer request of step S1601 includes an explicit indication, the deactivated SAE bearer response may also include an indication of successful deregistration.
  • Step S 1607 The new MME sends a deactivated SAE bearer request to the UE.
  • the new MME may also instruct the eNodeB to release the associated radio bearer.
  • this indication may also be sent after step S1601.
  • the deregistration process of the PDN GW further includes deleting the PDN GW address and the APN correspondence stored in the HSS/SPR.
  • FIG. 17, FIG. 18, and FIG. 19 respectively describe how to delete the address of the PDN GW from the HSS when the bearer deletion process is initiated by the network side in the SAE/LTE access network.
  • the PDN GW when all the bearers on the PDN GW for the UE are released, the PDN GW directly deletes the own address stored in the HSS/SPR.
  • Step S1701 The PCRF provides PCC Decision Provision to the PDN GW.
  • Step S1702 The PDN GW triggers a bearer deletion procedure according to the received PCC information. In this step, the PDN GW sends a deactivation SAE bearer request to the Serving GW.
  • Step S1703 The Serving GW sends a deactivate SAE bearer request to the MME.
  • Step S1704 The MME notifies the eNodeB to delete the related bearer (Deactive Bearer Request).
  • Step S1706 The UE removes the related uplink data flow template, and returns a Deactive Radio Bearer Response to the eNodeB.
  • Step S1707 The eNodeB returns a Deactivate Bearer Response to the MME.
  • Step S1708 The MME returns a deactivated SAE bearer response to the Serving GW.
  • the Serving GW may also provide an indication that the PDN GW de-registers the address information of the PDN GW to the HSS/AAA according to the indication provided by the Serving GW.
  • the original HSS saves the mapping between the PDN GW and the APN.
  • the deregistration process of the PDN GW also includes deleting the mapping between the PDN GW address and the APN stored in the HSS/SPR.
  • the embodiment shown in FIG. 17 may include a scenario in which the UE ends the service on the non-3GPP network, such as a scenario of multiple PDNs and multiple HAs, and may also include a bearer deletion scenario initiated by the PDN GW, when the PDN GW is used.
  • the PDN GW can directly deregister its own address to the HSS/AAA/SPR server. If the AAA and HSS are separate entities, the parameters or information for the deregistration need to be passed from the AAA to the HSS.
  • Step S 1801 The PCRF provides PCC information to the PDN GW.
  • Step S1802 The PDN GW triggers a bearer deletion procedure according to the received PCC information.
  • the PDN GW sends a deactivation SAE bearer request to the Serving GW.
  • Step S1803 The Serving GW sends a deactivate SAE bearer request to the MME.
  • Step S1804 The MME notifies the eNodeB to delete the related bearer.
  • Step S1805 The eNodeB sends a deactivated radio bearer request to the UE.
  • Step S1807 The eNodeB returns a deactivation bearer response to the MME.
  • Step S1808 The MME returns a deactivated SAE bearer response to the Serving GW.
  • Step S1809 The Serving GW returns a deactivated SAE bearer response to the PDN GW.
  • Step S1810 The PDN GW returns an acknowledgement of the relevant PCC information to the PCRF, and triggers the PCRF to deregister the address of the PDN GW to the HSS/SPR.
  • the PDN GW may trigger the PCRF to initiate the deregistration process according to the parameters configured by itself or the deactivated SAE bearer response returned by the MME in step S1808.
  • the MME may according to the subscription data of the UE and itself.
  • the configured parameters determine whether the address of the PDN GW is to be registered in the HSS/SPR through interaction with the PCC system.
  • the original HSS saves the mapping between the PDN GW and the APN.
  • the deregistration process of the PDN GW also includes deleting the mapping between the PDN GW address and the APN stored in the HSS/SPR.
  • the embodiment shown in FIG. 18 may include a scenario in which the UE ends the service in the non-3GPP network, such as a scenario of multiple PDNs and multiple HAs, and may also include a bearer deletion scenario initiated by the PDN GW, where the UE is on the PDN GW.
  • the PDN GW can deregister the address of the PDN GW from the PSC GW to the HSS/AAA/SPR server through the PCC system. If AAA and HSS are separate entities, then the de-registered parameters or information need to be passed from AAA to the HSS.
  • the MME deletes the address of the PDN GW stored in the HSS/SPR.
  • Step S1901 The PCRF provides PCC information to the PDN GW.
  • Step S1902 The PDN GW triggers a bearer deletion procedure according to the received PCC information.
  • the PDN GW sends a deactivation SAE bearer request to the Serving GW.
  • Step S1903 The Serving GW sends a deactivate SAE bearer request to the MME.
  • Step S1904 The MME notifies the eNodeB to delete the related bearer.
  • Step S1905 The eNodeB sends a deactivated radio bearer request to the UE.
  • Step S1906 The UE removes the related uplink data flow template, and returns deactivation to the eNodeB. Wireless bearer response.
  • Step S1907 The eNodeB returns a deactivation bearer response to the MME.
  • Step S1908 The MME returns a deactivated SAE bearer response to the Serving GW.
  • Step S1908a The MME de-registers the address of the PDN GW in the HSS/SPR. Before de-registration, the MME may determine, according to the subscription data of the UE and the parameters configured by itself, whether the address of the PDN GW in the HSS/SPR is required to be MME-resolved.
  • Step S1910 The PDN GW returns an acknowledgement of the relevant PCC information to the PCRF, and triggers the PCRF to deregister the address of the PDN GW to the HSS/SPR.
  • the original HSS saves the mapping between the PDN GW and the APN.
  • the deregistration process of the PDN GW also includes deleting the PDN saved in the HSS/SPR.
  • the embodiment shown in FIG. 19 may include a scenario in which the UE ends the service on the non-3GPP network, such as a scenario of multiple PDNs and multiple HAs, and may also include a bearer deletion scenario initiated by the PDN GW, where the UE is on the PDN GW.
  • the address corresponding to the MME such as ePDG and ASN GW, can be used to deregister the address of the PDN GW to the HSS/AAA/SPR server.
  • Step S2101 The PCRF provides PCC information to the PDN GW.
  • Step S2103 The Serving GW sends a Delete PDP context Request to the SGSN.
  • Step S2105 The UE returns a Delete PDP context Response to the SGSN.
  • Step S2106 The SGSN returns a delete PDP context response to the Serving GW.
  • Step S2106a The SGSN de-registers the address of the PDN GW saved in the HSS/SPR.
  • Step S2107 The SGSN returns a deactivated SAE bearer response to the PDN GW.
  • Step S2108 The PDN GW returns a PCC information confirmation to the PCRF.
  • the PCRF can go directly to the bearer deletion process initiated by the network side entity such as PCRF.
  • the PDN-GW address associated with the registration in HSS/AAA/SPR The specific process is basically the same as the embodiment mentioned in the present document and will not be described here.
  • Step S2001 The HSS/AAA/SPR sends a deactivate SAE bearer request to the new MME.
  • Step S2003 The Serving GW sends a deactivated SAE bearer request to the PDN GW.
  • Step S2006 The Serving GW returns a deactivated SAE bearer response to the new MME.
  • the bearer deletion process initiated by the HSS may have de-registered the information of the relevant PDN GW, and the process of de-registering different entities may be optional.
  • Step S2007 The new MME sends a deactivated SAE bearer request to the UE.
  • the new MME may also instruct the eNodeB to release the associated radio bearer.
  • this indication may also be sent after step S2002.
  • Step S2008 The UE returns a deactivated SAE bearer response to the new MME.
  • the embodiment shown in FIG. 20 may include a scenario in which the UE ends the service in the non-3GPP network, and the bearer release process may be initiated by the network side service entity, such as the HSS and the AAA, and the ePDG, the ASN GW, and the like are equivalent.
  • the entity of the MME or the PDN GW may deregister the address of the PDN GW to the HSS/AAA/SPR server, and may also decrypt the address of the registered PDN GW through the PCC system. If AAA and HSS are separate entities, then the de-registered parameters or information need to be passed from AAA to the HSS.
  • the present invention also provides an embodiment of a communication system.
  • An embodiment of the present invention provides a communication system, including: an address deletion notification entity, configured to send a notification for deleting an address of the network anchor point when the network anchor point is no longer serving a certain terminal, where the network anchor The address of the point has been previously registered to the web server; the deregistration entity is configured to deregister the address of the network anchor according to the notification of the address deletion notification entity.
  • the de-registration entity is further configured to delete the access point identifier when an access point corresponding to the anchor point identifies that the APN has been registered to the network server.
  • the address deletion notification entity is: a mobility management entity, or a serving GPRS support node, or an access network entity, or an entity in the network anchor, or policy control and charging system.
  • the telecommunications network has established a complete network management and control mechanism.
  • the resources allocated to the user need to be released in time, including the wireless channel, the bearer, and various tunnels.
  • the PDN GW saved in the HSS The related management information such as the address is also deleted.
  • the present invention also provides a technical solution for retiring the terminal.
  • Fig. 22, Fig. 23, Fig. 24, Fig. 25, Fig. 26, Fig. 27, and Fig. 28 respectively describe the flow of the terminal exiting the network when the terminal accesses through the non-3GPP access network.
  • the network revocation process initiated by the UE.
  • the UE accesses two PDNs at the same time, the UE uses HoAl to access the PDN1 identified by the APN1, and the UE uses the HoA2 to access the PDN2 identified by the APN2.
  • the UE initiated the network retreat process includes:
  • Step 2201 The access gateway/ePDG receives the release tunnel request message sent by the UE, and the message may carry a parameter such as a UE address.
  • Step 2202 The access gateway/ePDG sends a binding update message to the PDN GW.
  • the lifetime parameter is set to 0, and the care-of address parameter is set to HoAl, indicating that all bindings corresponding to HoAl are to be logged out.
  • Step 2203 The PDN GW notifies the AAA/HSS to deregister the PDN GW address information corresponding to the APN1.
  • step 2203 the access gateway /ePDG may also notify the AAA/HSS to deregister the PDN GW address information.
  • step 2203 can be performed simultaneously with steps 2202 and 2204.
  • Step 2204 The PDN GW sends a binding update confirmation message to the access gateway /ePDG, and confirms that all bindings corresponding to HoAl are deleted.
  • the PDN GW and the access gateway /ePDG delete the binding indicated in step 2202.
  • Step 2205 The access gateway/ePDG sends a binding update message to the PDN GW.
  • the lifetime parameter is set to 0, and the care-of address parameter is set to HoA2, indicating that all bindings corresponding to HoA2 are to be logged out.
  • Step 2206 The PDN GW notifies the AAA/HSS to deregister the PDN GW address information corresponding to the APN2.
  • the access gateway/ePDG may also notify the AAA/HSS to deregister the PDN GW address information.
  • step 2206 can be performed simultaneously with steps 2205, 2207.
  • Step 2207 The PDN GW sends a binding update confirmation message to the access gateway/ePDG, and confirms that all bindings corresponding to HoA2 are deleted.
  • the PDN GW and the Access Gateway/ePDG delete the binding indicated by step 2205.
  • Step 2208 The access gateway /ePDG replies to the UE with a release tunnel acknowledgement message. If the UE indicates that the reason for the network disconnection is in the release tunnel request message, step 2208 may not be performed.
  • the resource release process is performed to release resources between the UE and the access gateway /ePDG.
  • steps 2201, 2208 may be to release the tunnel request/acknowledgement message.
  • the connection between the UE and the access gateway is Layer 3, such as an IP-based connection
  • steps 2201, 2208 may be a layer 3 based trigger/acknowledgement message or trigger/acknowledgement process, or access technology. Specific triggering process.
  • the binding and PDN GW address information corresponding to each HoA may be sequentially released according to the method in this embodiment.
  • the above method of deregistering PDN GW address information with HoA granularity is also applicable to other embodiments.
  • the network exit process initiated by the access gateway /ePDG As shown in Figure 23, it includes:
  • Step 2301 The access gateway /ePDG sends a release tunnel request message to the UE, requesting to release the tunnel.
  • the message may include parameters such as the reason for the release.
  • Step 2302 The UE replies to the access gateway /ePDG to release the tunnel acknowledgement message, performs a resource release process, and releases the tunnel resource and the access network resource between the UE and the access gateway/ePDG.
  • the access gateway /ePDG may directly perform the resource release process without notifying the UE, that is, steps 2301 and 2302 are not executed.
  • steps 2301, 2302 may be a release tunnel request/acknowledgement message; if the UE and the access gateway are connected by Layer 3, such as IP-based Connect, then steps 2301, 2302 can be a layer 3 based trigger/acknowledgement message or trigger/acknowledgement process, or an access technology specific triggering process.
  • Layer 3 such as IP-based Connect
  • Step 2303 The access gateway /ePDG sends a binding update message to the PDN GW.
  • the lifetime of the message is 0, and the care-of address parameter is set to the home address, indicating that all the bindings of the home address are to be logged off.
  • Step 2304 The PDN GW replies to the access gateway/ePDG with a binding update confirmation message.
  • the PDN GW and the access gateway/ePDG delete the binding indicated in step 3.
  • Step 2305 The PDN GW notifies the AAA/HSS to deregister the PDN GW address information.
  • the original AAA/HSS will maintain the mapping between the PDN GW and the APN.
  • the deregistration process of the PDN GW also includes deleting the PDN GW address and the APN correspondence stored in the AAA/HSS.
  • the network retreating process initiated by the PDN GW.
  • Step 2401 The PDN GW sends a binding revocation indication message to the access gateway/ePDG, where the message may include the following parameters: UE identifier, revocation reason, revocation type, and the like.
  • Step 2402 The access gateway /ePDG sends a release tunnel request message to the UE, and the message may include parameters such as a release reason.
  • Step 2403 The UE replies to the access gateway /ePDG to release the tunnel acknowledgement message, and performs a resource release process to release resources between the UE and the access gateway /ePDG.
  • the access gateway /ePDG may directly perform the resource release process without notifying the UE, that is, steps 24202 and 2403 are not executed.
  • steps 2402, 2403 may be to release the tunnel request/acknowledgement message. If the UE and the access gateway are Layer 3 (L3) connections, such as IP-based connections, then steps 2402, 2403 may be a layer 3 based trigger/acknowledgement or trigger/acknowledgement process, or access technology specific Trigger process.
  • L3 Layer 3
  • Step 2404 The access gateway /ePDG replies to the PDN GW with a binding revocation acknowledgement message, and the access gateway /ePDG and the PDN GW delete all the bindings indicated in step 1.
  • Step 2405 The PDN GW notifies the AAA/HSS to deregister the PDN GW address information.
  • the original AAA/HSS will maintain the mapping between the PDN GW and the APN.
  • the deregistration process of the PDN GW also includes deleting the PDN GW address and the APN correspondence stored in the AAA/HSS.
  • Step 2405 may also notify the AAA/HSS to cancel the association information by the access gateway/ePDG. Specifically, in the embodiment shown in FIG. 25, the TLS/HSS initiates a network retreat procedure to the PDN GW.
  • Step 2501 The AAA/HSS sends a session suspension message to the PDN GW, and the message may include the following parameters: UE identity, abort reason, abort type, and the like.
  • Step 2503 The access gateway sends a release tunnel request message to the UE.
  • Step 2504 The UE replies to the access gateway with a release tunnel acknowledgement message.
  • the access network specific resource release process is performed to release the access network resources.
  • the access gateway /ePDG may directly perform the resource release process without notifying the UE, that is, steps 2503 and 2504 are not performed.
  • Step 2505 The access gateway replies to the PDN GW with a binding revocation confirmation message.
  • the access gateway and PDN GW delete all the bindings indicated in step 2502.
  • Step 2506 The PDN GW notifies the AAA/HSS to deregister the PDN GW address information.
  • the original AAA/HSS will maintain the mapping between the PDN GW and the APN.
  • the deregistration process of the PDN GW also includes deleting the PDN GW address and the APN correspondence stored in the AAA/HSS.
  • the TLS/HSS initiates a network revocation process to the access gateway/ePDG. As shown in Figure 26, it includes:
  • Step 2601 The AAA/HSS sends a session abort message to the ePDG, and the message includes the following parameters:
  • Step 2602 The access gateway /ePDG sends a release tunnel request message to the UE, and the message may include parameters such as a release reason.
  • Step 2603 The UE replies to the access gateway/ePDG to release the tunnel acknowledgement message, and performs resource release. The process releases resources between the UE and the access gateway/ePDG.
  • the access gateway /ePDG may directly perform the resource release process without notifying the UE, that is, steps 2602 and 2603 are not performed.
  • steps 2602, 2603 may be to release the tunnel request/acknowledgement message. If the UE and the access gateway are Layer 3 (Layer 3) connections, such as IP-based connections, then steps 2602, 2603 may be a layer 3 based trigger/acknowledgement or trigger/acknowledgement process, or access technology specific Trigger process.
  • Layer 3 Layer 3
  • Step 2604 The access gateway /ePDG sends a binding update message to the PDN GW.
  • the lifetime of the message is 0, and the care-of address parameter is set to the home address, indicating that all the bindings of the home address are to be logged off.
  • Step 2605 The PDN GW replies to the ePDG with a binding update confirmation message.
  • the PDN GW and the Access Gateway /ePDG delete all the bindings indicated in step 2604.
  • Step 2606 The access gateway /ePDG replies to the AAA/HSS with a session abort acknowledgement message.
  • the AAA/HSS After receiving the message, the AAA/HSS deregisters the associated information, such as the PDN GW address information that provides the UE with the service. If the network supports multiple PDNs for the same terminal, the original AAA/HSS will store the mapping between the PDN GW and the APN. At this time, the AAA/HSS will also delete the saved PDN GW address and APN correspondence.
  • CMIP Co-CoA mode
  • CMIP is a terminal-based mobile IP technology, that is, a technology that requires the terminal to participate in the binding process of the mobile IP.
  • CMIP is divided into two modes: foreign agent care-of address mode (FA-CoA mode) and collocated care-of address mode (Co-CoA mode).
  • FA-CoA mode foreign agent care-of address mode
  • Co-CoA mode collocated care-of address mode
  • the care-of address of the terminal is the IP address of the access link mobile agent.
  • the two endpoints of the mobile IP tunnel are the access link mobile agent and the home link mobile agent.
  • the care-of address of the terminal is the terminal IP address obtained by some means.
  • the two endpoints of the mobile IP tunnel are the terminal and the home link mobile agent respectively, and the access link mobile agent only serves as the ordinary route.
  • the role, that is, the mobile agent may not be deployed in the access link.
  • Step 2701 The PDN GW receives the binding update request message sent by the UE, where the lifetime of the message is 0, and the care-of address parameter is set to the home address, indicating that all bindings of the home address are cancelled.
  • Step 2702 The PDN GW feeds back a binding update confirmation message to the UE.
  • the UE and the PDN GW release the binding relationship between the home address and the care-of address, and release the CMIP tunnel.
  • the original AAA/HSS will maintain the mapping between the PDN GW and the APN.
  • the deregistration process of the PDN GW also includes deleting the PDN GW address and the APN correspondence stored in the AAA/HSS.
  • Step 2704a The PDN GW notifies the access gateway /ePDG to release the access link resources. Or after step 2703, the AAA/HSS notifies the access gateway/ePDG to release the access link resources (steps)
  • the original AAA/HSS will maintain the mapping between the PDN GW and the APN.
  • the deregistration process of the PDN GW also includes deleting the PDN GW address and the APN correspondence stored in the AAA/HSS.
  • Step 2703 and step 2705 are two ways to delete the associated information on the AAA/HSS, and one of the options is selected.
  • Step 2801 The PDN GW sends a binding revocation indication to the UE.
  • Step 2802 The UE feeds back a binding confirmation message to the PDN GW.
  • Step 2803 The PDN GW notifies the AAA/HSS to deregister the PDN GW address information.
  • the original AAA/HSS will maintain the mapping between the PDN GW and the APN.
  • the deregistration process of the PDN GW also includes deleting the PDN GW address and the APN correspondence stored in the AAA/HSS.
  • Step 2804a The PDN GW notifies the access gateway /ePDG to release the access link resources. Or after step 2803, the access gateway /ePDG is notified by the AAA/HSS to release the access link resources (step 2804b).
  • Step 2803 and step 2805 are two ways to delete the associated information on the AAA/HSS, and one of the options is selected.
  • FIG. 29, FIG. 30, FIG. 31, and FIG. 32 respectively describe the flow of the terminal exiting the network when the terminal accesses the evolved 3GPP core network through 3GPP.
  • Step 2901 The Serving GW sends a network revocation request message to the MME, and the message may include parameters such as a UE identifier, a network revocation reason, and a network revocation type.
  • Step 2902 The MME sends a network revocation request message to the eNodeB, where the message may include parameters such as a UE identifier, a reason for retiring the network, and a type of the network to be retired.
  • Step 2904 The UE replies to the eNodeB with a retiring confirmation message.
  • the radio resources between the UE and the eNodeB are released.
  • the eNodeB may directly release the radio resource without notifying the UE, that is, steps 2903 and 2904 are not performed.
  • Step 2905 The eNodeB replies to the MME with a reply to the network.
  • Step 2906 The MME returns a retiring confirmation message to the Serving GW.
  • Step 2907 The Serving GW sends a binding update message to the PDN GW.
  • the lifetime of the message is 0, and the care-of address parameter is set to the home address, indicating that all bindings of the home address are cancelled.
  • Step 2908 The PDN GW notifies the AAA/HSS to deregister the PDN GW address information.
  • the PDN GW may be instructed to delete all the bindings corresponding to all the HoAs of the UE, and then the PDN GW notifies the AAA in step 2908.
  • the HSS de-registers all the PDN GW address information of the UE.
  • the PDN GW may be notified to delete the binding corresponding to each HoA in turn according to the method in Embodiment 22, and the PDN GW sequentially notifies the AAA/HSS to de-register each APN correspondingly.
  • PDN GW address information may also be notified by the Serving GW or the MME that the AAA/HSS de-registers the PDN GW information.
  • Step 2909 The PDN GW replies to the Serving GW with a Binding Update Confirm message.
  • the PDN GW and serving GW delete all the bindings indicated in step 2907.
  • the network retreating process initiated by the PDN GW or the AAA/HSS As shown in Figure 30, it includes:
  • Step 3001a The PDN GW sends a binding revocation indication message to the serving GW, and the message may include the following parameters: UE identifier, revocation reason, revocation type, and the like.
  • the first step is that the AAA/HSS sends a back-off indication message to the PDN GW (step 3001b), and the PDN GW sends a binding revocation indication message to the serving GW.
  • Step 3002 The serving GW sends a network revocation request message to the MME, and the message may include parameters such as a UE identifier, a network revocation reason, and a network revocation type.
  • Step 3003 The MME sends a network revocation request message to the eNodeB, where the message may include parameters such as a UE identifier, a network revocation reason, and a network revocation type.
  • Step 3004 The eNodeB sends a network revocation request message to the UE, where the message may include a reason for retiring the network, a type of network retreat, and the like.
  • Step 3005 The UE replies to the eNodeB with a retiring confirmation message. Release the radio resources between the UE and the eNodeB.
  • the eNodeB may directly release the radio resource without notifying the UE. That is, step 3004 is not performed.
  • Step 3006 The eNodeB replies to the MME with a retiring confirmation message.
  • Step 3007 The MME returns a retiring confirmation message to the serving GW.
  • Step 3008 The serving GW replies to the PDN GW with a binding confirmation message.
  • the PDN GW and the serving GW delete all the bindings indicated in step 3001.
  • the original AAA/HSS will save the mapping between the PDN GW and the APN.
  • the deregistration process of the PDN GW also includes deleting the AAA/HSS. Correspondence between the PDN GW address and the APN.
  • the step 3009 may also notify the AAA/HSS to deregister the PDN GW address information by the serving GW or the MME.
  • the network exit process initiated by the MME As shown in Figure 31, it includes:
  • Step 3101 The MME sends a network revocation request message to the eNodeB, where the message may include parameters such as a UE identifier, a reason for retiring the network, and a type of the network to be retired.
  • Step 3102 The eNodeB sends a network revocation request message to the UE, where the message may include a network revocation reason, a network revocation type, and the like.
  • Step 3103 The UE replies to the eNodeB with a retiring confirmation message.
  • the radio resources between the UE and the eNodeB are released.
  • the eNodeB may directly release the radio resource without notifying the UE, that is, steps 3102 and 3103 are not performed.
  • Step 3104 The eNodeB replies to the MME with a retiring confirmation message.
  • Step 3105 The MME sends a retiring request message to the serving GW.
  • Step 3106 The serving GW sends a binding update message to the PDN GW.
  • the lifetime of the message is 0, and the care-of address parameter is set to the home address, indicating that all bindings of the home address are cancelled.
  • the original AAA/HSS will maintain the mapping between the PDN GW and the APN.
  • the deregistration process of the PDN GW also includes deleting the PDN GW address and the APN correspondence stored in the AAA/HSS.
  • Step 3108 The PDN GW replies to the serving GW with a binding update confirmation message.
  • the PDN GW and serving GW delete all the bindings indicated in step 3106.
  • Step 3109 The serving GW replies to the MME with a retiring confirmation message.
  • the network exit process initiated by the UE includes: Step 3201:
  • the eNodeB receives the network revocation request message sent by the UE, and the message may include parameters such as a UE identifier, a reason for retiring the network, and a type of the network to be retired.
  • Step 3202 The eNodeB sends a network revocation request message to the MME, where the message may include parameters such as a UE identifier, a reason for retiring the network, and a type of the egress.
  • Step 3203 The MME sends a network revocation request message to the Serving GW, where the message may include parameters such as a UE identifier, a network revocation reason, and a network revocation type.
  • Step 3204 The Serving GW sends a binding update request to the PDN GW.
  • the lifetime of the message is 0, and the care-of address parameter is set to the home address, indicating that all bindings of the home address are cancelled.
  • Step 3205 The PDN GW notifies the AAA/HSS to deregister the PDN GW address information.
  • the original AAA/HSS will maintain the mapping between the PDN GW and the APN.
  • the deregistration process of the PDN GW also includes deleting the PDN GW address and the APN correspondence stored in the AAA/HSS.
  • Step 3205 may also notify the AAA/HSS to deregister the PDN GW address information by the Serving GW or the MME.
  • Step 3206 The PDN GW replies to the Serving GW with a binding update confirmation message.
  • the Serving GW and PDN GW delete all the bindings indicated in step 4.
  • Step 3207 The Serving GW replies to the MME with a reply confirmation message.
  • Step 3208 The MME returns a network confirmation message to the eNodeB, and releases the resource between the eNodeB and the Serving GW.
  • Step 3209 The eNodeB replies to the UE with a network acknowledgment message, and releases the radio resource.
  • the foregoing network retreat scheme is a method for releasing resources for releasing a network by using a terminal in a network that is integrated with a broadband wireless access and a mobile communication network.
  • a terminal needs to disconnect from the network, or When the network wants to disconnect from the terminal, it can release network resources in time, make up the management control mechanism of the evolved network, and improve resource utilization.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'invention concerne un procédé de mise en oeuvre pour sauvegarder l'adresse d'un point d'ancrage de réseau à un serveur de réseau, comprenant les étapes suivantes : le terminal initie une demande de rattachement ou une demande d'établissement de support, et le côté réseau sélectionne un ancrage de réseau; au cours du procédé pendant lequel le point d'ancrage distribue le premier contexte de support au terminal ou crée une connexion avec le terminal à un premier moment, le côté réseau enregistre l'adresse du point d'ancrage de réseau avec le serveur de réseau. Un procédé de mise en oeuvre pour supprimer l'adresse de l'ancrage réseau du serveur de réseau comprend les étapes suivantes : pendant le processus de support de suppression initié par le terminal ou l'entité du côté réseau, ledit côté réseau notifie au serveur de réseau de supprimer l'adresse du point d'ancrage de réseau qui a été enregistrée sur le serveur et ne sert plus le terminal; le serveur supprime l'enregistrement de l'adresse du point d'ancrage de réseau. L'invention concerne également un système de communications.
PCT/CN2007/071260 2007-05-28 2007-12-18 Procédé de mise en oeuvre et système de communications pour sauvegarder l'adresse d'un point d'ancrage de réseau à un serveur de réseau WO2008144991A1 (fr)

Priority Applications (7)

Application Number Priority Date Filing Date Title
US12/550,867 US8244242B2 (en) 2007-05-28 2009-08-31 Method and communication system for storing address of network anchor point to network server
US13/551,376 US8483686B2 (en) 2007-05-28 2012-07-17 Method and communication system for deleting address of network anchor point from network server
US13/915,877 US9271250B2 (en) 2007-05-28 2013-06-12 Method and communication system for storing address of network anchor point to network server
US14/990,216 US9756596B2 (en) 2007-05-28 2016-01-07 Method and communication system for storing address of network anchor point to network server
US15/660,064 US10264543B2 (en) 2007-05-28 2017-07-26 Method and communication system for storing address of network anchor point to network server
US16/360,562 US10869291B2 (en) 2007-05-28 2019-03-21 Method and communication system for storing address of network anchor point to network server
US17/100,173 US11490350B2 (en) 2007-05-28 2020-11-20 Method and communication system for storing address of network anchor point to network server

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
CN200710074594.0 2007-05-28
CN200710074594 2007-05-28
CN200710140572.X 2007-08-13
CN200710140572XA CN101316440B (zh) 2007-05-28 2007-08-13 网络锚点的地址保存到网络服务器的实现方法及通信系统

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US12/550,867 Continuation US8244242B2 (en) 2007-05-28 2009-08-31 Method and communication system for storing address of network anchor point to network server

Publications (1)

Publication Number Publication Date
WO2008144991A1 true WO2008144991A1 (fr) 2008-12-04

Family

ID=40074557

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2007/071260 WO2008144991A1 (fr) 2007-05-28 2007-12-18 Procédé de mise en oeuvre et système de communications pour sauvegarder l'adresse d'un point d'ancrage de réseau à un serveur de réseau

Country Status (1)

Country Link
WO (1) WO2008144991A1 (fr)

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100067462A1 (en) * 2008-05-15 2010-03-18 Harris Stratex Networks Operating Corporation Systems and Methods for Data Path Control in a Wireless Network
WO2010128165A3 (fr) * 2009-05-08 2010-12-29 Nokia Siemens Networks Oy Procédé et appareil configurés pour fournir des services de branchement local avec un seul apn
CN101959170A (zh) * 2009-07-20 2011-01-26 中国移动通信集团江苏有限公司 一种用于gprs业务的用户辅助方法和装置
CN102238521A (zh) * 2010-04-27 2011-11-09 中兴通讯股份有限公司 业务授权方法、装置及系统
CN103179545A (zh) * 2011-12-26 2013-06-26 中国移动通信集团江苏有限公司 提升用户分组业务体验的方法及系统
CN111246527A (zh) * 2015-08-17 2020-06-05 华为技术有限公司 一种更新用户面网关的方法及装置

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1567894A (zh) * 2003-06-17 2005-01-19 华为技术有限公司 无线局域网和移动网互通情况下查询路由的方法
CN1744761A (zh) * 2004-09-04 2006-03-08 华为技术有限公司 一种多个运营商共享无线接入网的方法
CN1878103A (zh) * 2005-06-07 2006-12-13 华为技术有限公司 全球微波接入互操作网接入互联网协议多媒体子域的方法

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1567894A (zh) * 2003-06-17 2005-01-19 华为技术有限公司 无线局域网和移动网互通情况下查询路由的方法
CN1744761A (zh) * 2004-09-04 2006-03-08 华为技术有限公司 一种多个运营商共享无线接入网的方法
CN1878103A (zh) * 2005-06-07 2006-12-13 华为技术有限公司 全球微波接入互操作网接入互联网协议多媒体子域的方法

Cited By (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100067462A1 (en) * 2008-05-15 2010-03-18 Harris Stratex Networks Operating Corporation Systems and Methods for Data Path Control in a Wireless Network
US8948084B2 (en) * 2008-05-15 2015-02-03 Telsima Corporation Systems and methods for data path control in a wireless network
US9961609B2 (en) 2008-05-15 2018-05-01 Telsima Corporation Systems and methods for data path control in a wireless network
WO2010128165A3 (fr) * 2009-05-08 2010-12-29 Nokia Siemens Networks Oy Procédé et appareil configurés pour fournir des services de branchement local avec un seul apn
US9078161B2 (en) 2009-05-08 2015-07-07 Nokia Solutions And Networks Oy Method and apparatus configured to provide local breakout services with a single APN
CN101959170A (zh) * 2009-07-20 2011-01-26 中国移动通信集团江苏有限公司 一种用于gprs业务的用户辅助方法和装置
CN102238521A (zh) * 2010-04-27 2011-11-09 中兴通讯股份有限公司 业务授权方法、装置及系统
CN103179545A (zh) * 2011-12-26 2013-06-26 中国移动通信集团江苏有限公司 提升用户分组业务体验的方法及系统
CN111246527A (zh) * 2015-08-17 2020-06-05 华为技术有限公司 一种更新用户面网关的方法及装置
CN111246527B (zh) * 2015-08-17 2023-11-17 华为技术有限公司 一种更新用户面网关的方法及装置

Similar Documents

Publication Publication Date Title
CN102695294B (zh) 网络锚点的地址删除方法及通信系统
JP5499170B2 (ja) 課金システム及び課金の方法
JP5044020B2 (ja) Ｌｔｅシステムにおいて、ユーザ静的ｉｐアドレスのアドレッシングをサポートする方法、システムおよび装置
WO2013010415A1 (fr) Procédé, système et sgw pour réaliser une notification d'attributs d'adresse ip
WO2009117891A1 (fr) Procédé d'enregistrement et équipement de connexion à un réseau de données par paquet
US8582503B2 (en) Method for indicating the bearer management of a serving gateway
WO2009121251A1 (fr) Procédé, système et appareil permettant de mettre en œuvre l’optimisation du routage
US8873510B2 (en) Gateway selection method, apparatus and system during heterogeneous network handover
WO2007087745A1 (fr) Procédé et système pour la mise en oeuvre d'acheminement de données de l'utilisateur itinérant
WO2009097772A1 (fr) Procédé de commande, système de communication et dispositif correspondant pour une libération de ressource
WO2007076729A1 (fr) Procede de transfert intercellulaire pour utilisateur mobile et dispositif et systeme de communication et dispositif reseau a evolution
WO2008131681A1 (fr) Procédé, système et appareil de mise en œuvre d'un service de sous-système multimédia ip dans un réseau visité
WO2007147345A1 (fr) Procédé de sélection d'entité plan utilisateur du côté réseau et d'entité plan contrôle
WO2007109955A1 (fr) Procédé d'utilisation de l'adresse ip d'un utilisateur itinérant et terminal utilisateur destiné à cet effet
WO2011153750A1 (fr) Procédé et système de synchronisation de données d'utilisateur
WO2008144991A1 (fr) Procédé de mise en oeuvre et système de communications pour sauvegarder l'adresse d'un point d'ancrage de réseau à un serveur de réseau
WO2010124551A1 (fr) Procédé et système pour préserver un identifiant de passerelle de réseau par paquets dans un scénario d'accès multiples
WO2011054294A1 (fr) Procede d'installation de connexion et equipement associe
WO2012024989A1 (fr) Procédé et système pour une libération de porteuse
WO2012142889A1 (fr) Procédé de sélection de passerelle, et dispositif et système pour sa mise en œuvre
CN102123493A (zh) 分组数据网络连接的注册方法及装置
WO2012013103A1 (fr) Procédé et système de rapport d'identité de passerelle
WO2010012241A1 (fr) Procédé de réalisation d'interaction d'informations et nœud de stockage de données souscrites par utilisateur
WO2007128242A1 (fr) Procédé et système d'enregistrement côté réseau plutôt que terminal
WO2010031317A1 (fr) Procédé et appareil de traitement pour le support d'optimisation de routage

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 07846086

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 07846086

Country of ref document: EP

Kind code of ref document: A1