WO2012024989A1 - 承载释放方法及系统 - Google Patents
承载释放方法及系统 Download PDFInfo
- Publication number
- WO2012024989A1 WO2012024989A1 PCT/CN2011/077164 CN2011077164W WO2012024989A1 WO 2012024989 A1 WO2012024989 A1 WO 2012024989A1 CN 2011077164 W CN2011077164 W CN 2011077164W WO 2012024989 A1 WO2012024989 A1 WO 2012024989A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- bearer
- release
- management unit
- mobility management
- identifier
- Prior art date
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/12—Reselecting a serving backbone network switching or routing node
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/30—Connection release
- H04W76/34—Selective release of ongoing connections
Definitions
- the present invention relates to the field of communications, and in particular to a bearer release method and system.
- BACKGROUND OF THE INVENTION Worldwide Interoperability for Microwave Access (World Interoperability for Microwave Access, referred to as
- Evolved Packet Core It can provide higher transmission rate, shorter transmission delay, optimized packet, and support for evolved UTRAN (Evolved UTRAN, E-UTRAN for short), UTRAN, Wireless Local Area Network (WLAN) and Mobility management between other non-3GPP access networks.
- the current SAE architecture is shown in Figure 1.
- Evolved RAN Evolved RAN
- the network element included in the E-RAN is an eNodeB (Evolved NodeB) for providing radio resources for user access.
- Packet Data Network PDN
- the E-Packet Core provides lower latency and allows more wireless access systems to access.
- the network element includes the following: a Mobility Management Entity (MME): A control plane function entity, a server that temporarily stores user data, and is responsible for managing and storing a user equipment (User Equipment, UE for short) context (such as UE).
- MME Mobility Management Entity
- MME is the movement of the SAE system Management unit.
- the mobility management unit is an SGSN (Serving GPRS Support Node).
- the Serving Gateway is a user plane entity responsible for user plane data routing processing and terminating downlink data of UEs in idle (ECM_IDLE) state.
- ECM_IDLE idle
- the SGW is the anchor point of the internal user plane of the 3GPP system.
- PDN Gateway PGW for short
- the packet data network gateway (PDN Gateway, PGW for short) is responsible for the UE accessing the PDN gateway, assigning the user IP address, and
- the mobility anchor of 3GPP and non-3GPP access systems, the functions of the PGW also include policy implementation and charging support. Users can access multiple PGWs at the same time.
- the PCEF Policy and Charging Enforcement Function
- the Policy and Charging Rules Function is responsible for providing policy control and charging rules to the PCEF.
- the Home Subscriber Server (HSS) permanently stores user subscription data.
- the content stored in the HSS includes the IMSI (International Mobile Subscriber Identification) of the UE and the IP address of the PGW. Physically, the SGW and the PGW may be one.
- the EPC system user plane network element includes SGW and PGW. In order to save the user's air interface resources and power saving, the UE needs to be converted from the connected state to the idle state. This process is called the S1 release process in the E-UTRAN system, and is called the Iu release process in the GPRS process.
- the S1 release process includes the following steps: Step 201: The eNodeB detects that the UE needs to release the context, and the eNodeB sends a UE context release request message to the MME, where the message carries the release cause value. Step 202: The MME sends the message to the SGW.
- Step 203 The SGW deletes the address and the TEID of the stored eNodeB, and returns the release link to the MME.
- Step 204 The MME sends a UE context release instruction message to the eNodeB.
- Step 205 If the radio bearer connection (Radio Resource Connection, RRC for short) of the user has not been released, the eNodeB sends an RRC connection release request message to the UE.
- Radio bearer connection Radio Resource Connection, RRC for short
- Step 207 The eNodeB returns a UE context release complete message to the MME.
- IMS IP Multimedia Sub-System
- the PGW indicates whether the MME needs to release the part of the non-GBR bearer in the SI release process.
- the method includes the following steps: Step 301: The PCRF sends a PCC policy to the PGW. Step 302: The PGW sends a bearer setup request message to the SGW, where the message carries a QoS (Quality of Service), a Traffic Flow Template (TFT), a PGW user plane address, and a TEID.
- QoS Quality of Service
- TFT Traffic Flow Template
- Step 303 The SGW sends a bearer setup request message to the MME, where the bearer carries the QoS, carries the user plane address and TEID of the TFT, the SGW, and the charging identifier, and releases the bearer indication.
- Step 314 The MME allocates a bearer identifier to the bearer, and establishes a session management request, where the session management request includes a bearer QoS, a bearer identifier, and a bearer TFT.
- the MME sends a bearer setup request message to the eNodeB, where the message carries the session management request, and the bearer QoS, bearer identity, user plane address and TEID of the SGW.
- Step 305 The eNodeB sends an RRC connection reconfiguration message to the UE, where the message carries a radio bearer QoS, a session management request, and a radio bearer identifier.
- Step 306 The UE sends an RRC Connection Reconfiguration Complete message to the eNodeB.
- Step 307 The eNodeB sends a bearer setup response message to the MME, and carries the user plane address and the TEID of the eNodeB.
- Step 308 The UE non-access stratum establishes a session establishment response, and delivers the message to the eNodeB through a direct transmission message.
- step 310 the MME replies to the SGW with a bearer setup response message, where the message includes the bearer identifier, the user plane address and the TEID of the eNodeB, and the carrying of the release bearer indication, and the release bearer indication can enable the SGW to know whether the MME supports the S1 release process.
- the non-GBR bearer function is released.
- Step 311 The SGW replies to the PGW with a bearer setup response message, where the message includes the bearer identifier, the user plane address and the TEID of the SGW, and the bearer bearer indication, and the release bearer indication may enable the PGW to learn whether the MME supports the release during the S1 release process.
- the non-GBR bearer function Step 312, the PGW sends the IP session to the PCRF to modify successfully.
- the new mobility management unit cannot determine whether the non-GBR bearer release procedure needs to be initiated after the S1/Iu release process, because the PCRF maps some IMS voice services to On the non-GBR bearer, in order to make the service layer chargeable accurately, the PCRF needs to indicate through the PGW or SGW whether the mobile management unit needs to release the non-GBR bearer during the Sl/Iu release process. In this way, after the release of Sl/Iu, the business layer may have a problem of inaccurate billing.
- a primary object of the present invention is to provide a bearer release method and system for solving the above-mentioned UE moving to a new mobility management unit, and after the new mobility management unit performs the Sl/Iu release process, it is impossible to determine whether a non-need to be initiated.
- the GBR bearer release process causes the charging layer to be inaccurate in the service layer after the release of the Sl/Iu.
- a bearer release method is provided.
- the bearer release method includes: after the user equipment UE moves from the first mobility management unit to the second mobility management unit, the second mobility management unit acquires the release bearer identifier from the first mobility management unit; the second mobility management unit is configured according to The bearer identity is released to determine whether the non-guaranteed bit rate non-GBR bearer release is performed during the Sl/Iu release process.
- the method further includes: in the process of the bearer establishment or bearer modification of the UE under the first mobility management unit, the first mobility management unit from the policy and charging
- the release function identifier is obtained from the message sent by the rule function entity PCRF or the packet data gateway PGW.
- the obtaining, by the second mobility management unit, the release of the bearer identifier from the first mobility management unit comprises: the second mobility management unit in a context transfer with a tracking area update (TAU), a routing area update (RAU) or a handover procedure of the first mobility management unit Get the release bearer ID.
- the method further includes: the second mobility management unit selects a new serving gateway, and sends a bearer setup message to the new serving gateway, where the bearer setup message carries the release bearer flag
- the new service gateway sends a bearer modification message to the packet service gateway (PGW), where the bearer modification message carries the release bearer identifier.
- PGW packet service gateway
- the method further includes: if the bearer context in the serving gateway stores the release bearer identifier, and the second mobility management unit sends the bearer modification message to the serving gateway.
- the service gateway determines that the second mobility management unit does not support non-GBR bearer release during the Sl/Iu release process; the service gateway notifies the PGW that the second mobility management unit does not support the S1/Iu release process.
- Non GBR carrier release includes one of the following: a mobility management entity (MME), a serving GPRS support node
- the release bearer is identified as a separate unit of information.
- a load bearing release system includes: a UE, a first mobility management unit, and a second mobility management unit, wherein the second mobility management unit includes: an acquisition module, configured to move from the first mobility management unit to the second mobility of the UE After the management unit, the release bearer identifier is obtained from the first mobility management unit.
- the first determining module is configured to determine, according to the release bearer identifier, whether the non-GBR bearer release is performed during the S1/Iu release process.
- the first mobility management unit is configured to obtain the release bearer identifier from the message sent by the policy and charging rule function entity PCRF or the packet data gateway PGW in the process of the bearer establishment or bearer modification of the UE under the first mobility management unit.
- the acquisition module is configured to obtain the release bearer identity in a context transfer with a Tracking Area Update (TAU), a Routing Area Update (RAU), or a handover procedure of the first mobility management unit.
- TAU Tracking Area Update
- RAU Routing Area Update
- the second mobility management unit module further includes: a selection module, configured to select a new service gateway; the first sending module is configured to send a bearer setup message to the new serving gateway, where the bearer setup message carries the release bearer flag; the bearer release system further includes The service gateway, where the service gateway includes: a second sending module, configured to send a bearer modification message from the first sending module to the packet serving gateway (PGW), where the bearer modification message carries the release bearer identifier.
- PGW packet serving gateway
- the system further includes a service gateway, where the service gateway includes: a second determining module, configured to store a release bearer identifier in a bearer context in the serving gateway, and the second mobility management unit does not send the bearer modification message to the serving gateway When carrying the release bearer identifier, determining that the second mobility management unit does not support non-GBR bearer release during the Sl/Iu release process; the notification module is configured to determine, in the second determining module, that the second mobility management unit does not support release in the Sl/Iu When the non-GBR bearer release is performed in the process, the PGW second mobility management unit is notified that the non-GBR bearer release is not supported during the Sl/Iu release process.
- the service gateway includes: a second determining module, configured to store a release bearer identifier in a bearer context in the serving gateway, and the second mobility management unit does not send the bearer modification message to the serving gateway When carrying the release bearer identifier, determining that the second mobility management unit does not support
- the mobility management unit includes one of the following: MME, Serving GPRS Support Node (SGSN).
- the release bearer is identified as a separate unit of information.
- the second mobility management unit acquires the release bearer identifier from the first mobility management unit; the second mobility management unit determines whether the The non-guaranteed bit rate non-GBR bearer release during the Sl/Iu release process solves the above-mentioned UE moving to the new mobility management unit, and the new mobility management unit cannot determine whether it is necessary to initiate non-GBR after performing the Sl/Iu release process.
- FIG. 1 is a schematic diagram of a structure of an evolved packet network system according to the related art
- FIG. 2 is a signaling flowchart of S1 release according to the related art
- FIG. 2 is a signaling flowchart of S1 release according to the related art
- FIG. 3 is a signaling flowchart of bearer establishment according to the related art
- 4 is a flowchart of a bearer release method according to an embodiment of the present invention
- 5 is a flowchart of a bearer release method in which a UE moves to a new MME and the SGW does not change according to an embodiment of the present invention
- FIG. 6 is a UE moves to a new MME and a new MME selects a new SGW according to an embodiment of the present invention
- FIG. 7 is a flowchart of a method for releasing a bearer from a UE to a new MME according to an embodiment of the present invention
- FIG. 8 is a structural block diagram of a bearer release system according to an embodiment of the present invention
- 9 is a block diagram of a preferred structure of a bearer release system in accordance with an embodiment of the present invention.
- BEST MODE FOR CARRYING OUT THE INVENTION Hereinafter, the present invention will be described in detail with reference to the accompanying drawings. It should be noted that the embodiments in the present application and the features in the embodiments may be combined with each other without conflict.
- the present embodiment provides a method for releasing a bearer.
- FIG. 4 is a flowchart of a method for releasing a bearer according to an embodiment of the present invention. As shown in FIG.
- Step S402 When a UE moves from a first mobility management unit to After the second mobility management unit, the second mobility management unit acquires the release bearer identity from the first mobility management unit.
- Step S404 The second mobility management unit determines, according to the release bearer identifier, whether to perform non-guaranteed bit rate (non-GBR) bearer release in the S1/Iu release process. After the UE moves from the first mobility management unit to the second mobility management unit, the second mobility management unit acquires the release bearer identifier from the first mobility management unit, and determines whether the S1/Iu release process is performed according to the identifier.
- non-GBR non-guaranteed bit rate
- the non-GBR bearer release process is performed, and the UE is prevented from entering the new mobility management unit coverage area by the mobile device, and the new mobility management unit performs the S1/Iu release process, and cannot determine whether the non-GBR bearer release procedure needs to be initiated.
- the PCRF maps some IMS voice services to non-GBR bearers, in order to make the service layer charge accurately, the PCRF needs to indicate whether the mobility management unit needs to be released in Sl/Iu through the PGW or SGW during the new bearer or bearer modification process.
- the non-GBR bearer is released, so that the service layer may be inaccurate in charging after the release of the Sl/Iu, and the accuracy of the service layer charging is improved.
- the method further includes: in the process of the bearer establishment or bearer modification of the UE under the first mobility management unit, the first mobility management unit from the policy and charging rule function entity PCRF or the packet data gateway
- the release bearer identifier is obtained from the message sent by the PGW.
- the first mobility management unit obtains the release bearer identifier.
- Some preferred embodiments for obtaining the release bearer identifier from the first mobility management unit by the second mobility management unit in step S404 are described below.
- the second mobility management unit acquires the release bearer identifier in the context transfer of the Tracking Area Update (TAU), the Routing Area Update (RAU), or the handover procedure of the first mobility management unit.
- TAU Tracking Area Update
- RAU Routing Area Update
- the second mobility management unit obtains the release bearer identifier in multiple cases, which improves the flexibility and applicability of the method for acquiring the bearer identifier.
- the method further includes: the second mobility management unit selects a new serving gateway, and sends a bearer setup message to the new serving gateway, where the bearer setup message carries the release bearer flag; the new service gateway sends the packet to the packet gateway (PGW) Sending a bearer modification message, where the bearer modification message carries a release bearer identifier.
- PGW packet gateway
- the second mobility management unit selects a new serving gateway, the new serving gateway and the packet serving gateway acquire the release bearer identifier.
- the method further includes: if the release bearer identifier is stored in the bearer context in the serving gateway, and the bearer modification message sent by the second mobility management unit to the serving gateway does not carry the release bearer identifier, the serving gateway It is determined that the second mobility management unit does not support bearer release during the Sl/Iu release process; the serving gateway notifies the PGW that the second mobility management unit does not support bearer release during the Sl/Iu release process.
- the preferred embodiment implements that the release bearer identifier is stored in the serving gateway bearer context, and the identifier is not delivered to the serving gateway by the second mobility management unit, and the service gateway determines that the second mobility management unit does not support the Sl/Iu release process.
- the bearer release is made and the content is notified to the PGW.
- the mobility management unit comprises one of the following: MME, SGSN.
- the applicability of the application of the release bearer method is achieved.
- the release bearer is identified as a single information unit.
- the release of the bearer identifier is relatively simple to implement and the system overhead is relatively small.
- the method includes: In step 501, the UE moves to the E-UTRAN coverage area of the MME, and the tracking area update request message sent to the MME carries the capability of whether the UE supports the ISR, in addition to the GUTI allocated by the UE under the old MME.
- Step 502 The new MME finds the old MME according to the GUTI identifier, and sends a context request signaling to perform a context acquisition process.
- Step 503 The old MME sends the mobility management and bearer information of the user to the new MME, and carries the flag of whether the non-GBR bearer release is required to be delivered to the new MME during the release of the S1/Iu in the returned context response message.
- the label may be represented by a separate information element (Information Element, referred to as IE).
- Information Element Information Element, referred to as IE.
- the MME records whether the non-GBR bearer needs to be sent during the S1 release process sent by the PCRF/PGW.
- the release of the indication in order to trigger the bearer release procedure in the process of S1 release; the old MME needs to pass the above label to the new MME, and the old MME can use the presence or absence flag to notify the new MME whether the bearer release procedure needs to be triggered; the old MME can also The "1" in the IE is used to indicate that the new MME needs to trigger the bearer release procedure, and the "0" is used to indicate that the new MME does not need to trigger the bearer release procedure.
- Step 504 The new MME returns a context confirmation message to the old MME.
- Step 505 The new MME initiates an update bearer request to the SGW, where the request message carries the source GTP-C tunnel identifier and the destination GTP-C tunnel identifier, and the SGW updates the binding relationship of the bearer, the location information of the UE, and whether the message needs to carry itself. Supports triggering the non-GBR bearer release process during S1 release.
- Step 506 The SGW sends an update bearer request to the PGW, where the request message carries the location information of the UE. If the new MME does not support the non-GBR bearer release process during the S1 release process, the SGW needs to notify the PGW in the update bearer request message.
- step 507 the PGW updates its own context and returns update bearer response information to the SGW.
- step 508 The SGW returns an update bearer response to the new MME, and brings the destination GTP-C tunnel identifier, the address of the own, the address of the PGW, and the tunnel information specified by the SGW to the MME.
- step 509 the new MME notifies the change of the HSS location by the location update message.
- Step 510 The HSS sends location cancellation signaling to the old MME.
- step 511 the old MME returns a location cancellation response to the HSS.
- Step 512 the HSS confirms the location update of the new MME, and passes the user subscription data to the new
- Step 513 If the new MME confirms that the UE is valid in the current tracking area, send a tracking area update accept message to the UE. Step 514, if the new MME allocates a new GUTI identifier to the UE through the TAU process, then
- Embodiment 2 This embodiment combines the foregoing embodiments and preferred embodiments thereof.
- This embodiment provides a method for releasing a bearer
- FIG. 6 is a UE moving to a new MME and selecting a new MME according to an embodiment of the present invention.
- the method includes: Step 601: The UE moves to an E-UTRAN coverage area under the MME, where the tracking area update request message sent to the MME is carried in addition to the UE
- the GUTI allocated under the old MME also carries the capability of whether the UE supports ISR.
- the old MME sends the mobility management and bearer information of the user to the new MME, and carries the flag of the non-GBR bearer release to the new MME in the returned Context Response message.
- the flag may be represented by an IE.
- the MME records an indication of whether the non-GBR bearer needs to be released during the S1 release process sent by the PCRF/PGW, so as to be released during the S1 release process.
- the bearer release procedure is triggered; the old MME needs to pass the above-mentioned flag to the new MME, and the old MME can use the presence or absence flag to notify the new MME whether the bearer release procedure needs to be triggered; the old MME can also use the "1" in the IE to indicate the new MME.
- the bearer release procedure needs to be triggered.
- the "0" is used to indicate that the new MME does not need to trigger the bearer release procedure.
- the old MME can also use "0" in the IE to indicate that the new MME needs to trigger the bearer release procedure, and use "1" to indicate the new MME. There is no need to trigger a bearer release process.
- the new MME replies to the old MME with a context confirmation message.
- Step 605 The new MME initiates a session establishment request to the new SGW.
- the request message carries the source GTP-C tunnel identifier and the destination GTP-C tunnel identifier, the SGW control plane address and the TEID, and the location information of the UE. Supports triggering the non-GBR bearer release process during S1 release.
- Step 606 The SGW sends an update bearer request to the PGW, where the request message carries the location information of the UE. The message also needs to carry the self and the MME to support the non-GBR bearer release process during the S1 release process.
- the PGW updates its own context and returns update bearer response information to the SGW.
- Step 608 The SGW returns a session establishment response to the new MME, and brings the destination GTP-C tunnel identifier specified by the SGW, its own address, the address of the PGW, and the tunnel information to the MME.
- the new MME notifies the change of the HSS location by the location update message.
- the HSS sends location cancellation signaling to the old MME.
- the old MME returns a location cancellation response to the HSS.
- the HSS confirms the location update of the new MME, and passes the user subscription data to the new
- Step 613 If the new MME confirms that the UE is valid in the current tracking area, send a tracking area update accept message to the UE. Step 614, if the new MME allocates a new GUTI identifier to the UE through the TAU process, then
- the UE will return a tracking area update complete message to confirm to the MME.
- Step 615 The old MME sends a release session request message to the old SGW, informing the SGW to delete the context of the user.
- step 616 the old SGW returns a release session response message to the old MME.
- the UE is moved to the new MME coverage area as an example.
- the processing method is similar, and details are not described herein again.
- Embodiment 3 This embodiment combines the above-mentioned embodiments and preferred embodiments thereof, and this embodiment provides a method for releasing a bearer, and FIG.
- Step 701 The original eNodeB decides to initiate a handover between the eNodeB and the core network node to the new eNodeB.
- Step 702 The original eNodeB sends a handover request message to the old MME.
- Step 703 The old MME selects a new MME according to the MME selection function, and sends a node re-allocation request message to the new MME, where the message includes the address of the PGW and the uplink TEID, the address of the SGW, and the uplink TEID; and carries the S1/Iu in the message.
- the flag for triggering the release of the non-GBR bearer is required to be delivered to the new MME during the release process; preferably, the flag may be represented by a separate information element IE, and the MME records the PCRF/PGW sent during the bearer setup or bearer update process.
- the old MME needs to pass the above-mentioned flag to the new MME, and the old MME can notify the new MME with the presence or absence of the flag.
- Step 704 The new MME sends a session establishment request message to the SGW, where the request message carries the GTP-C tunnel identifier and the IP address of the PGW, and carries the QoS.
- Step 705 The SGW returns a session establishment response message to the MME, where the response message carries the GTP-C tunnel identifier of the SGW and its own address.
- Step 706 The new MME sends a handover request message to the new eNodeB, requesting to establish a UE context in the new eNodeB.
- Step 707 The new eNodeB sends a handover request acknowledgement message to the new MME.
- Step 708 The new MME sends a node re-allocation response message to the old MME.
- Step 709 The old MME sends a handover indication message to the original eNodeB.
- Step 710 The original eNodeB forwards the handover indication message to the UE.
- Step 711 After performing cell synchronization with the new eNodeB, the UE sends a handover confirmation message to the new eNodeB.
- Step 712 The new eNodeB sends a handover notification message to the new MME.
- Step 713 The new MME sends a message that the node re-allocation is completed to the old MME.
- Step 714 The old MME returns a confirmation message that the node re-allocation is completed to the new MME.
- Step 715 The new MME initiates an update bearer request to the SGW, where the request message carries the user plane tunnel identifier and the IP address of the new eNodeB.
- Step 716 The SGW sends an update bearer request to the PGW, and sends the SGW address information, the tunnel identifier information, and the location information of the UE to the PGW. The message also needs to carry the self and the MME to support the triggering the non-GBR bearer during the S1 release process. Release process.
- the PGW updates its own context and returns an update bearer response message to the SGW.
- Step 718 The SGW returns an update bearer response message to the new MME.
- the present embodiment provides a bearer release system. FIG.
- FIG. 8 is a structural block diagram of a bearer release system according to an embodiment of the present invention. As shown in FIG. 8, the system includes: a UE 82, a first mobility management unit 84, and a second mobile The management unit 86, wherein the second mobility management unit comprises: an obtaining module 862 and a first determining module 864.
- the second mobility management unit comprises: an obtaining module 862 and a first determining module 864.
- the obtaining module 862 is configured to acquire a release bearer identifier from the first mobility management unit after the UE moves from the first mobility management unit to the second mobility management unit; preferably, the obtaining module 862 is configured to be in the first mobility management unit Obtaining a release bearer identifier in a context transfer of the TAU, the RAU, or the handover process; the first determining module 864 is connected to the obtaining module 862, and configured to determine, according to the release bearer identifier acquired by the obtaining module 862, whether to perform non-guarantee during the release process of the Sl/Iu The bit rate non GBR bearer is released; the first mobility management unit 84 is configured to send from the policy and charging rule function entity PCRF or the packet data gateway PGW in the process of the bearer establishment or bearer modification of the UE under the first mobility management unit. Get the release bearer ID in the message.
- 9 is a block diagram showing a preferred structure of a bearer release system according to an embodiment of the present invention,
- the bearer release system further includes: a service gateway 88,
- the service gateway 88 includes: a second sending module 882, a second determining module 884, and a notification module 886.
- the second mobility management module 86 includes: a selecting module 866, configured to select a new serving gateway;
- the first sending module 868 is connected to the selecting module 866, and is configured to send a bearer setup message to the new serving gateway selected by the selecting module 866, where the bearer setup message carries the release bearer flag;
- the service gateway 88 includes: a second sending module 882, setting The bearer modification message is sent from the first sending module to the PGW, where the bearer modification message carries the release bearer identifier.
- the second determining module 884 is configured to store the release bearer identifier in the bearer context in the serving gateway, and the second mobile When the bearer modification message sent by the management unit does not carry the release bearer identifier, it is determined that the second mobility management unit does not support the bearer release in the S1/Iu release process; the notification module 886 is connected to the second determining module 884, and is set to The second determining module 884 determines that the second mobility management unit is not supported When the bearer release Sl / Iu release procedure, the PGW notifies the second mobile management unit does not support the bearer release Sl / Iu release process.
- the mobility management unit includes one of the following: an MME, an SGSN.
- the release bearer identifier is a single information unit.
- the second mobility management unit acquires the release bearer identifier from the first mobility management unit, and determines whether the release process is in the Sl/Iu according to the identifier.
- the non-GBR bearer release process is performed in the related art, and the UE does not determine whether the non-GBR bearer release process needs to be initiated after the UE moves to the new mobility management unit coverage area and the new mobility management unit performs the Sl/Iu release process.
- the PCRF maps certain IMS voice services to non-GBR bearers.
- the PCRF In order to make the service layer charge accurately, the PCRF needs to indicate whether the mobility management unit needs to be in Sl/Iu through the PGW or SGW during the new bearer or bearer modification process. During the release process, the non-GBR bearer is released, so that the service layer may be inaccurate in billing after the release of the Sl/Iu, and the accuracy of the service layer charging is improved.
- the above modules or steps of the present invention can be implemented by a general-purpose computing device, which can be concentrated on a single computing device or distributed over a network composed of multiple computing devices.
- the computing device may be implemented by program code executable by the computing device, such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein.
- the steps shown or described are performed, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps are fabricated as a single integrated circuit module.
- the invention is not limited to any specific combination of hardware and software.
- the above is only the preferred embodiment of the present invention, and is not intended to limit the present invention, and various modifications and changes can be made to the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and scope of the present invention are intended to be included within the scope of the present invention.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
本发明公开了一种承载释放方法及系统,该方法包括:当UE从第一移动管理单元移动至第二移动管理单元之后,第二移动管理单元从第一移动管理单元获取释放承载标识;第二移动管理单元根据释放承载标识确定是否在S1/Iu释放过程中进行nonGBR承载释放。通过本发明,提高了业务层计费的准确性。
Description
承载释放方法及系统 技术领域 本发明涉及通信领域, 具体而言, 涉及一种承载释放方法及系统。 背景技术 随着全球微波接入互通 (World Interoperability for Microwave Access, 简称为
WiMAX)的异军突起,第三代移动通信系统要保持其在移动通信领域的强有力的竞争 力,必须提高其网络性能和降低网络建设及运营成本。因此,第三代合作伙伴计划(3rd Generation Partnership Project, 简称为 3GPP) 的标准化工作组, 目前正致力于研究包 交换核心网 (Packet Switch Core, 简称为 PS Core) 和全球移动通信系统无线接入网 (Universal Mobile Telecommunication System Radio Access Network, 简称为 UTRAN) 的演进, 这个研究的课题叫做系统架构演进 (System Architecture Evolution, 简称为 SAE), 其目的是使得演进的分组网 (Evolved Packet Core, 简称 EPC) 可提供更高的 传输速率, 更短的传输延时, 优化分组, 及支持演进的 UTRAN (Evolved UTRAN, 简称为 E-UTRAN)、UTRAN、无线局域网(Wireless Local Area Network,简称为 WLAN) 及其他非 3GPP的接入网络之间的移动性管理。 目前 SAE的架构如图 1所示, 其中包含了如下网元: 演进的无线接入网 (Evolved RAN, 简称为 E-RAN): 可以提供更高的上 /下行速 率、更低的传输延迟和更加可靠的无线传输。 E-RAN中包含的网元是 eNodeB (Evolved NodeB, 演进节点 B), 用于为用户的接入提供无线资源。 分组数据网 (Packet Data Network, 简称为 PDN): 为用户提供业务的网络。 演进的分组网 (E-Packet Core), 提供了更低的延迟, 并允许更多的无线接入系统 接入。 其包含如下网元: 移动管理实体 (Mobility Management Entity, 简称为 MME): 控制面功能实体, 临时存储用户数据的服务器, 负责管理和存储用户设备(User Equipment, 简称为 UE) 的上下文 (比如 UE/用户标识, 移动性管理状态, 用户安全参数等), 为用户分配临时 标识, 当 UE驻扎在该跟踪区域或者该网络时, 负责对该用户进行鉴权; 处理 MME 和 UE之间的所有非接入层消息; 触发在 SAE系统的寻呼。 MME是 SAE系统的移动
管理单元。 在 UMTS系统中, 移动管理单元是 SGSN(Serving GPRS Support Node, 服 务 GPRS支持节点)。 服务网关(Serving Gateway, 简称为 SGW)是一个用户面实体, 负责用户面数据 路由处理, 终结处于空闲 (ECM_IDLE) 状态的 UE的下行数据。 管理和存储 UE的 SAE承载 (bearer) 上下文, 比如 IP承载业务参数和网络内部路由信息等。 SGW是 3GPP系统内部用户面的锚点, 一个用户在一个时刻只能有一个 SGW; 分组数据网网关 (PDN Gateway, 简称为 PGW), 负责 UE接入 PDN的网关, 分 配用户 IP地址, 同时是 3GPP和非 3GPP接入系统的移动性锚点, PGW的功能还包括 策略实施、计费支持。用户在同一时刻能够接入多个 PGW。 PCEF (Policy and Charging Enforcement Function, 策略与计费实施功能实体) 也位于 PGW中。 策略与计费规则功能实体 (Policy and Charging Rules Function, 简称为 PCRF) 负 责向 PCEF提供策略控制与计费规则。 归属用户服务器(Home Subscriber Server, 简称为 HSS)永久存储用户签约数据, HSS存储的内容包括 UE的 IMSI (International Mobile Subscriber Identification, 国际 移动用户识别码)、 PGW的 IP地址。 在物理上, SGW和 PGW可能合一。 EPC系统用户面网元包括 SGW和 PGW。 为了节省用户的空口资源和节电, 需要将 UE从连接状态转化为空闲状态, 这个 过程在 E-UTRAN系统中称为 S1释放流程, 在 GPRS过程中称为 Iu释放流程。 在 S1 释放流程过程中, 当释放原因是由于"用户不活动"时, 用户的保证比特率 (Guaranteed Bit Rate, 简称为 GBR)承载和 non GBR (非保证比特率) 承载都保留, 但是当释放原 因是由于其它原因时,移动管理实体只保留 non GBR承载,而 GBR承载都需要由 MME 发起释放。 S1释放过程如图 2所示, 包括以下步骤: 步骤 201, eNodeB检测到需要释放 UE的上下文, eNodeB向 MME发送 UE上下 文释放请求消息, 该消息中携带释放原因值; 步骤 202, MME向 SGW发送释放接入承载请求消息, 请求 SGW删除所存储的 eNodeB的地址和隧道端点标识 ( Tunnel Endpoint IDentifier, 简称为 TEID); 步骤 203, SGW删除所存储的 eNodeB的地址和 TEID, 并向 MME返回释放接入 承载响应消息。
步骤 204, MME向 eNodeB发送 UE上下文释放指令消息。 步骤 205, 如果用户的无线承载连接 (Radio Resource Connection, 简称为 RRC) 还没有被释放, eNodeB向 UE发送 RRC连接释放请求消息。 步骤 206, UE向 eNodeB返回 RRC连接释放响应消息。 步骤 207, eNodeB向 MME返回 UE上下文释放完成消息。 步骤 208, MME根据步骤 201中的释放原因值决定释放 GBR承载;如果步骤 201 中的释放原因为"用户不活动", MME不发起 GBR承载释放过程, 但是当步骤 201中 的释放原因为其它原因时, MME发起 GBR承载释放流程。 鉴于 PCRF会将某些 IP多媒体子系统 (IP Multimedia sub-System, 简称为 IMS)语 音业务映射到 non GBR承载上, 为了使业务层计费精确, PCRF会在新建承载或者承 载修改过程中需要通过 PGW, SGW指示 MME是否需要在 SI release过程中将该部分 non GBR承载进行释放, 如图 3所示, 包括以下步骤: 步骤 301, PCRF向 PGW发送 PCC策略。 步骤 302, PGW向 SGW发送承载建立请求消息,该消息中携带承载 QoS (Quality of Service, 服务质量), 承载业务流模板( Traffic Flow Template, 简称为 TFT), PGW 的用户面地址和 TEID,计费标识,另外如果将 IMS语音承载映射到 non GBR承载上, 还需要携带释放承载指示, 用于指示在 S1释放过程中由 MME对该 non GBR承载发 起承载释放过程。 步骤 303, SGW向 MME发送承载建立请求消息, 该消息中携带承载 QoS, 承载 TFT, SGW的用户面地址和 TEID, 计费标识, 释放承载指示。 步骤 304, MME为该承载分配一个承载标识, 并且建立会话管理请求, 会话管理 请求中包括承载 QoS,承载标识,承载 TFT; MME向 eNodeB发送承载建立请求消息, 该消息中携带会话管理请求, 承载 QoS, 承载标识, SGW的用户面地址和 TEID。 步骤 305, eNodeB向 UE发送 RRC连接重配置消息,该消息中携带无线承载 QoS, 会话管理请求, 无线承载标识。 步骤 306, UE向 eNodeB发送 RRC连接重配置完成消息。
步骤 307, eNodeB向 MME发送承载建立响应消息, 携带 eNodeB的用户面地址 禾口 TEID。 步骤 308, UE非接入层建立会话建立响应, 并通过直传消息传递给 eNodeB。 步骤 309, eNodeB通过上行直传消息将会话建立响应传递至 MME。 步骤 310, MME向 SGW回复承载建立响应消息, 消息中包括承载标识, eNodeB 的用户面地址和 TEID , 同时需要携带释放承载指示, 该释放承载指示可以使 SGW,PGW获知 MME是否支持在 S1释放过程中释放 non GBR承载功能。 步骤 311, SGW向 PGW回复承载建立响应消息, 消息中包括承载标识, SGW的 用户面地址和 TEID, 同时需要携带释放承载指示, 该释放承载指示可以使 PGW获知 MME是否支持在 S1释放过程中释放 non GBR承载功能; 步骤 312, PGW向 PCRF发送 IP会话修改成功。 但是如果 UE由于移动进入至新的移动管理单元覆盖区域, 新的移动管理单元进 行 Sl/Iu释放过程后, 无法确定是否需要发起 non GBR承载释放流程, 由于 PCRF会 将某些 IMS语音业务映射到 non GBR承载上, 为了使业务层计费精确, PCRF会在新 建承载或者承载修改过程中需要通过 PGW、 SGW指示移动管理单元是否需要在 Sl/Iu 释放过程中将该部分 non GBR承载进行释放, 这样 Sl/Iu释放后业务层会出现计费不 精确的问题。 发明内容 本发明的主要目的在于提供一种承载释放方法及系统, 以解决上述的 UE移动至 新的移动管理单元, 而新的移动管理单元进行 Sl/Iu释放过程后, 无法确定是否需要 发起 non GBR承载释放流程, 从而造成的 Sl/Iu释放后业务层会出现计费不精确的问 题。 为了实现上述目的, 根据本发明的一个方面, 提供了一种承载释放方法。 根据本发明的承载释放方法包括: 当用户设备 UE从第一移动管理单元移动至第 二移动管理单元之后, 第二移动管理单元从第一移动管理单元获取释放承载标识; 第 二移动管理单元根据释放承载标识确定是否在 Sl/Iu释放过程中进行非保证比特率 non GBR承载释放。
在第二移动管理单元从第一移动管理单元获取释放承载标识之前,还包括:在 UE 在第一移动管理单元下的承载建立或者承载修改的过程中, 第一移动管理单元从策略 与计费规则功能实体 PCRF或者分组数据网关 PGW发送的消息中获取释放承载标识。 第二移动管理单元从第一移动管理单元获取释放承载标识包括: 第二移动管理单 元在与第一移动管理单元的跟踪区更新(TAU)、路由区更新(RAU)或切换过程的上 下文传递中获取释放承载标识。 在第二移动管理单元从第一移动管理单元获取释放承载标识之后, 还包括: 第二 移动管理单元选择新服务网关, 并向新服务网关发送承载建立消息, 其中, 承载建立 消息携带释放承载标记; 新服务网关向分组服务网关 PGW发送承载修改消息, 其中, 承载修改消息携带释放承载标识。 在第二移动管理单元从第一移动管理单元获取释放承载标识之后, 还包括: 如果 服务网关中的承载上下文中存储了释放承载标识, 且第二移动管理单元向服务网关发 送的承载修改消息传递到没有携带释放承载标识, 则服务网关确定第二移动管理单元 不支持在 Sl/Iu释放过程中进行 non GBR承载释放; 服务网关通知 PGW第二移动管 理单元不支持在 Sl/Iu释放过程中进行 non GBR承载释放。 上述移动管理单元包括以下之一: 移动管理实体 (MME)、 服务 GPRS支持节点
释放承载标识为一个单独的信息单元。 为了实现上述目的, 根据本发明的另一方面, 提供了一种承载释放系统。 根据本发明的承载释放系统包括: UE、 第一移动管理单元、 第二移动管理单元, 其中, 第二移动管理单元包括: 获取模块, 设置为在 UE从第一移动管理单元移动至 第二移动管理单元之后, 从第一移动管理单元获取释放承载标识; 第一确定模块, 设 置为根据释放承载标识确定是否在 Sl/Iu释放过程中进行 non GBR承载释放。 第一移动管理单元设置为在 UE在第一移动管理单元下的承载建立或者承载修改 的过程中, 从策略与计费规则功能实体 PCRF或者分组数据网关 PGW发送的消息中 获取释放承载标识。 获取模块设置为在与第一移动管理单元的跟踪区更新(TAU)、路由区更新(RAU) 或切换过程的上下文传递中获取释放承载标识。
第二移动管理单元模块还包括: 选择模块, 设置为选择新服务网关; 第一发送模 块, 设置为向新服务网关发送承载建立消息, 其中, 承载建立消息携带释放承载标记; 承载释放系统还包括: 服务网关, 其中, 服务网关包括: 第二发送模块, 设置为向分 组服务网关 (PGW) 发送来自第一发送模块的承载修改消息, 其中, 承载修改消息携 带释放承载标识。 上述系统还包括服务网关, 其中, 服务网关包括: 第二确定模块, 设置为在服务 网关中的承载上下文中存储了释放承载标识, 且第二移动管理单元向服务网关发送的 承载修改消息中没有携带释放承载标识时, 确定第二移动管理单元不支持在 Sl/Iu释 放过程中进行 non GBR承载释放; 通知模块, 设置为在第二确定模块确定第二移动管 理单元不支持在 Sl/Iu释放过程中进行 non GBR承载释放时, 通知 PGW第二移动管 理单元不支持在 Sl/Iu释放过程中进行 non GBR承载释放。 移动管理单元包括以下之一: MME、 服务 GPRS支持节点 (SGSN)。 释放承载标识为一个单独的信息单元。 通过本发明, 采用当 UE从第一移动管理单元移动至第二移动管理单元之后, 第 二移动管理单元从第一移动管理单元获取释放承载标识; 第二移动管理单元根据释放 承载标识确定是否在 Sl/Iu释放过程中进行非保证比特率 non GBR承载释放, 解决了 上述的 UE移动至新的移动管理单元, 而新的移动管理单元进行 Sl/Iu释放过程后,无 法确定是否需要发起 non GBR承载释放流程, 从而造成 Sl/Iu释放后业务层会出现计 费不精确的问题, 进而达到了提高业务层计费准确性的效果。 附图说明 此处所说明的附图用来提供对本发明的进一步理解, 构成本申请的一部分, 本发 明的示意性实施例及其说明用于解释本发明, 并不构成对本发明的不当限定。 在附图 中: 图 1是根据相关技术的演进分组网络系统结构的示意图; 图 2是根据相关技术的 S1释放的信令流程图; 图 3是根据相关技术的承载建立的信令流程图; 图 4是根据本发明实施例的承载释放方法的流程图;
图 5是根据本发明实施例的 UE移动至新的 MME且 SGW没有发生变化的承载释 放方法的流程图; 图 6是根据本发明实施例的 UE移动至新的 MME且新的 MME选择新 SGW的承 载释放方法的流程图; 图 7是根据本发明实施例的 UE发生切换移动至新 MME的承载释放方法的流程 图; 图 8是根据本发明实施例的承载释放系统的结构框图; 以及 图 9是根据本发明实施例的承载释放系统的优选的结构框图。 具体实施方式 下文中将参考附图并结合实施例来详细说明本发明。 需要说明的是, 在不冲突的 情况下, 本申请中的实施例及实施例中的特征可以相互组合。 本实施例提供了一种承载释放方法, 图 4是根据本发明实施例的承载释放方法的 流程图, 如图 4所示, 该方法包括: 步骤 S402, 当 UE从第一移动管理单元移动至第二移动管理单元之后, 第二移动 管理单元从第一移动管理单元获取释放承载标识。 步骤 S404, 第二移动管理单元根据释放承载标识确定是否在 Sl/Iu释放过程中进 行非保证比特率 (non GBR) 承载释放。 通过上述步骤, 在 UE从第一移动管理单元移动至第二移动管理单元之后, 第二 移动管理单元从第一移动管理单元获取释放承载标识, 并根据上述标识确定是否在 Sl/Iu释放过程中进行 non GBR承载释放, 避免了相关技术中, UE由于移动进入至新 的移动管理单元覆盖区域, 且新的移动管理单元进行 Sl/Iu释放过程后, 无法确定是 否需要发起 non GBR承载释放流程, 由于 PCRF会将某些 IMS语音业务映射到 non GBR承载上, 为了使业务层计费精确, PCRF会在新建承载或者承载修改过程中需要 通过 PGW、 SGW指示移动管理单元是否需要在 Sl/Iu释放过程中将该部分 non GBR 承载进行释放, 这样 Sl/Iu释放后业务层会出现计费不精确的问题, 提高了业务层计 费的准确性。
优选地, 在步骤 S402之前, 上述方法还包括: 在 UE在第一移动管理单元下的承 载建立或者承载修改的过程中, 第一移动管理单元从策略与计费规则功能实体 PCRF 或者分组数据网关 PGW发送的消息中获取释放承载标识。 通过本优选实施例, 实现 了第一移动管理单元获取释放承载标识。 下面对步骤 S404 中第二移动管理单元从第一移动管理单元获取释放承载标识的 一些优选的实施方式进行说明。 第二移动管理单元在与第一移动管理单元的跟踪区更 新 (Tracking Area Update, 简称为 TAU)、 路由区更新 (Routing Area Update, 简称为 RAU)或切换过程的上下文传递中获取释放承载标识。通过本优选实施例的获取步骤, 实现了在多种情况下第二移动管理单元获取释放承载标识, 提高了获取承载标识方法 的灵活性和适用性。 优选地,在步骤 S402之后,上述方法还包括:第二移动管理单元选择新服务网关, 并向新服务网关发送承载建立消息, 其中, 承载建立消息携带释放承载标记; 新服务 网关向分组服务网关 (PGW) 发送承载修改消息, 其中, 承载修改消息携带释放承载 标识。 通过本优选实施例, 实现了在第二移动管理单元选择新服务网关情况下, 新服 务网关和分组服务网关获取释放承载标识。 优选地, 在步骤 S402之后, 上述方法还包括: 如果服务网关中的承载上下文中存 储了释放承载标识, 且第二移动管理单元向服务网关发送的承载修改消息没有携带释 放承载标识, 则服务网关确定第二移动管理单元不支持在 Sl/Iu释放过程中进行承载 释放;服务网关通知 PGW第二移动管理单元不支持在 Sl/Iu释放过程中进行承载释放。 本优选实施例实现了在服务网关承载上下文中存储了释放承载标识, 且该标识没有被 第二移动管理单元传递到服务网关,则该服务网关确定第二移动管理单元不支持 Sl/Iu 释放过程中进行承载释放并将该内容通知给 PGW。 优选地, 移动管理单元包括以下之一: MME、 SGSN。 通过该优选实施例, 实现 了释放承载方法应用的适用性。 优选地, 释放承载标识为一个单独的信息单元。 通过该优选实施例, 释放承载标 识实现起来比较简单, 且系统开销比较小。 实施例一 本实施例结合了上述实施例及其中的优选实施方式, 本实施例提供了一种释放承 载的方法,图 5是根据本发明实施例的 UE移动至新的 MME且 SGW没有发生变化的 承载释放方法的流程图, 如图 5所示, 该方法包括:
步骤 501, UE移动到 MME下的 E-UTRAN覆盖区, 在向 MME发送的跟踪区更 新请求消息中除了携带 UE在旧 MME下分配的 GUTI, 还要携带 UE是否支持 ISR的 能力。 步骤 502, 新 MME根据 GUTI标识找到旧 MME, 发送上下文请求信令进行上下 文获取过程。 步骤 503, 旧 MME将用户的移动管理和承载信息发送给新 MME, 并在返回的上 下文响应消息中携带 Sl/Iu释放过程中是否需要触发 non GBR承载释放的标记传递给 新的 MME。 优选地, 该标记可以用一个单独的信息单元 (Information Element, 简称为 IE)来表 示, 在承载建立或承载更新过程中, MME记录 PCRF/PGW发送过来的 S1释放过程 中是否需要将 non GBR承载释放的指示, 以便在 S1释放的过程中触发承载释放流程; 旧 MME需要将上述标记传递至新的 MME, 旧 MME可以用有无标记来通知新 MME 是否需要触发承载释放流程; 旧 MME也可以用 IE中的 "1"来指示新 MME需要触发 承载释放流程, 用 "0"来表示新 MME不需要触发承载释放流程。 步骤 504, 新 MME向旧 MME回复上下文确认消息。 步骤 505, 新 MME向 SGW发起更新承载请求, 请求消息中携带源 GTP-C隧道 标识和目的 GTP-C隧道标识, SGW更新承载的绑定关系, UE的位置信息, 该消息还 需要携带自身是否支持在 S1释放过程中触发 non GBR承载释放过程。 步骤 506, SGW向 PGW发送更新承载请求, 请求消息中携带 UE的位置信息; 如果新 MME不支持 S1释放过程中触发 non GBR承载释放过程, SGW需要在该更新 承载请求消息中通知 PGW。 步骤 507, PGW更新自己的上下文并向 SGW返回更新承载响应信息。 步骤 508, SGW向新 MME返回更新承载响应, 将 SGW指定的目的 GTP-C隧道 标识、 自身的地址以及 PGW的地址和隧道信息等带给 MME。 步骤 509, 新 MME通过位置更新消息通知 HSS位置的改变。 步骤 510, HSS向旧 MME发送位置取消信令。 步骤 511, 旧 MME向 HSS返回位置取消响应。
步骤 512, HSS 对新 MME 的位置更新进行确认, 并将用户签约数据传递至新
步骤 513, 如果新 MME确认 UE在当前的跟踪区内有效, 则向 UE发送跟踪区更 新接受消息。 步骤 514, 如果新 MME通过 TAU流程为 UE分配了一个新的 GUTI标识, 那么
UE会返回跟踪区更新完成消息向 MME进行确认。 需要说明的是, 本实施例中是以 UE移动至新的 MME覆盖区域为例说明的; 对 于 UE移动至新的 SGSN, 处理方法与其类似, 在此不再赘述。 实施例二 本实施例结合了上述实施例及其中的优选实施方式, 本实施例提供了一种释放承 载的方法,图 6是根据本发明实施例的 UE移动至新的 MME且新的 MME选择新 SGW 的承载释放方法的流程图, 如图 6所示, 该方法包括: 步骤 601, UE移动到 MME下的 E-UTRAN覆盖区, 在向 MME发送的跟踪区更 新请求消息中除了携带 UE在旧 MME下分配的 GUTI, 还要携带 UE是否支持 ISR的 能力。 步骤 602, 新 MME根据 GUTI标识找到旧 MME, 发送上下文请求信令进行上下 文获取过程。 步骤 603, 旧 MME将用户的移动管理和承载信息发送给新 MME, 并在返回的上 下文响应消息中携带 Sl/Iu释放过程中是否需要触发 non GBR承载释放的标记传递给 新的 MME。 优选地, 该标记可以用一个 IE来表示, 在承载建立或承载更新过程中, MME记 录 PCRF/PGW发送过来的 S1释放过程中是否需要将 non GBR承载释放的指示, 以便 在 S1释放的过程中触发承载释放流程; 旧 MME需要将上述标记传递至新的 MME, 旧 MME可以用有无标记来通知新 MME是否需要触发承载释放流程; 旧 MME也可 以用 IE中的 "1 "来指示新 MME需要触发承载释放流程, 用 "0"来表示新 MME不需要 触发承载释放流程; 旧 MME也可以用 IE中的 "0"来指示新 MME需要触发承载释放 流程, 用 "1 "来表示新 MME不需要触发承载释放流程。 步骤 604, 新 MME向旧 MME回复上下文确认消息。
步骤 605, 新 MME向新 SGW发起会话建立请求, 请求消息中携带源 GTP-C隧 道标识和目的 GTP-C隧道标识, SGW控制面地址和 TEID, UE的位置信息, 该消息 还需要携带自身是否支持在 S1释放过程中触发 non GBR承载释放过程。 步骤 606, SGW向 PGW发送更新承载请求, 请求消息中携带 UE的位置信息; 该消息还需要携带自身和 MME是否支持在 S1释放过程中触发 non GBR承载释放过 程。 步骤 607, PGW更新自己的上下文并向 SGW返回更新承载响应信息。 步骤 608, SGW向新 MME返回会话建立响应, 将 SGW指定的目的 GTP-C隧道 标识、 自身的地址以及 PGW的地址和隧道信息等带给 MME。 步骤 609, 新 MME通过位置更新消息通知 HSS位置的改变。 步骤 610, HSS向旧 MME发送位置取消信令。 步骤 611, 旧 MME向 HSS返回位置取消响应。 步骤 612, HSS 对新 MME 的位置更新进行确认, 并将用户签约数据传递至新
步骤 613, 如果新 MME确认 UE在当前的跟踪区内有效, 则向 UE发送跟踪区更 新接受消息。 步骤 614, 如果新 MME通过 TAU流程为 UE分配了一个新的 GUTI标识, 那么
UE会返回跟踪区更新完成消息向 MME进行确认。 步骤 615, 旧 MME向旧 SGW发送释放会话请求消息, 通知 SGW删除用户的上 下文。 步骤 616, 旧 SGW向旧 MME返回释放会话响应消息。 需要说明的是, 本实施例中是以 UE移动至新的 MME覆盖区域为例说明的; 对 于 UE移动至新的 SGSN, 处理方法与其类似, 在此不再赘述。
实施例三 本实施例结合了上述实施例及其中的优选实施方式, 本实施例提供了一种释放承 载的方法, 图 7是根据本发明实施例的 UE发生切换移动至新 MME的承载释放方法 的流程图, 如图 7所示, 该方法包括: 步骤 701, 原 eNodeB决定向新 eNodeB发起 eNodeB间、 核心网节点重分配的切 换。 步骤 702, 原 eNodeB向旧 MME发送切换请求消息。 步骤 703, 旧 MME根据 MME选择功能选择新 MME, 并向新 MME发送节点重 分配请求消息, 该消息中包括 PGW的地址和上行 TEID, SGW的地址和上行 TEID; 并在消息中携带 Sl/Iu释放过程中是否需要触发 non GBR承载释放的标记传递给新的 MME; 优选地, 该标记可以用一个单独的信息单元 IE来表示, 在承载建立或承载更新过 程中, MME记录 PCRF/PGW发送过来的 S1释放过程中是否需要将 non GBR承载释 放的指示, 以便在 S1释放的过程中触发承载释放流程; 旧 MME需要将上述标记传递 至新的 MME, 旧 MME可以用有无标记来通知新 MME是否需要触发承载释放流程; 旧 MME也可以用 IE中的 "1"来指示新 MME需要触发承载释放流程, 用 "0"来表示新 MME不需要触发承载释放流程;; 旧 MME也可以用 IE中的 "0"来指示新 MME需要 触发承载释放流程, 用 "1 "来表示新 MME不需要触发承载释放流程。 步骤 704, 新 MME向 SGW发送会话建立请求消息, 请求消息中携带, PGW的 GTP-C隧道标识和 IP地址, 承载 QoS等; 该消息还需要携带自身是否支持在 S1释放 过程中触发 non GBR承载释放过程。 步骤 705, SGW 向 MME返回会话建立响应消息, 响应消息中携带有 SGW 的 GTP-C隧道标识和自身的地址。 步骤 706, 新 MME向新 eNodeB发送切换请求消息, 请求在新 eNodeB中建立 UE上下文。 步骤 707, 新 eNodeB向新 MME发送切换请求确认消息。 步骤 708, 新 MME向旧 MME发送节点重分配响应消息。 步骤 709, 旧 MME向原 eNodeB发送切换指示消息。
步骤 710, 原 eNodeB将切换指示消息转发至 UE。 步骤 711, UE与新 eNodeB进行小区同步后, 向新 eNodeB发送切换确认消息。 步骤 712, 新 eNodeB向新 MME发送切换通知消息。 步骤 713, 新 MME向旧 MME发送节点重分配完成的消息。 步骤 714, 旧 MME向新 MME返回节点重分配完成的确认消息。 步骤 715, 新 MME向 SGW发起更新承载请求, 请求消息中携带新 eNodeB的用 户面隧道标识和 IP地址。 步骤 716, SGW向 PGW发送更新承载请求, 将 SGW的地址信息、 隧道标识信 息、 UE的位置信息等参数发送给 PGW; 该消息还需要携带自身和 MME是否支持在 S1释放过程中触发 non GBR承载释放过程。 步骤 717, PGW更新自身的上下文, 并向 SGW返回更新承载响应消息。 步骤 718, SGW向新 MME返回更新承载响应消息。 本实施例提供了一种承载释放系统, 图 8是根据本发明实施例的承载释放系统的 结构框图, 如图 8所示, 该系统包括: UE 82、 第一移动管理单元 84、 第二移动管理 单元 86, 其中, 第二移动管理单元包括: 获取模块 862和第一确定模块 864, 下面对 上述结构进行详细描述。 获取模块 862, 设置为在 UE从第一移动管理单元移动至第二移动管理单元之后, 从第一移动管理单元获取释放承载标识; 优选地, 获取模块 862设置为在与第一移动 管理单元的 TAU、 RAU或切换过程的上下文传递中获取释放承载标识; 第一确定模块 864,连接至获取模块 862, 设置为根据获取模块 862获取的释放承 载标识确定是否在 Sl/Iu释放过程中进行非保证比特率 non GBR承载释放; 第一移动管理单元 84, 设置为在 UE在第一移动管理单元下的承载建立或者承载 修改的过程中, 从策略与计费规则功能实体 PCRF或者分组数据网关 PGW发送的消 息中获取释放承载标识。 图 9是根据本发明实施例的承载释放系统的优选的结构框图, 第二移动管理模块
86包括: 选择模块 866、 第一发送模块 868, 该承载释放系统还包括: 服务网关 88,
其中服务网关 88包括: 第二发送模块 882、 第二确定模块 884和通知模块 886, 下面 对上述结构进行详细说明: 第二移动管理模块 86包括: 选择模块 866, 设置为选择新服务网关; 第一发送模 块 868,连接至选择模块 866, 设置为向选择模块 866选择的新服务网关发送承载建立 消息, 其中, 承载建立消息携带释放承载标记; 服务网关 88包括: 第二发送模块 882, 设置为向 PGW发送来自第一发送模块的 承载修改消息, 其中, 承载修改消息携带释放承载标识; 第二确定模块 884, 设置为 在服务网关中的承载上下文中存储了释放承载标识, 且第二移动管理单元向其发送的 承载修改消息没有携带释放承载标识时, 确定第二移动管理单元不支持在 Sl/Iu释放 过程中进行承载释放; 通知模块 886, 连接至第二确定模块 884, 设置为在第二确定模 块 884确定第二移动管理单元不支持在 Sl/Iu释放过程中进行承载释放时, 通知 PGW 第二移动管理单元不支持在 Sl/Iu释放过程中进行承载释放。 优选地, 上述移动管理单元包括以下之一: MME、 SGSN。 优选地, 上述释放承载标识为一个单独的信息单元。 通过上述实施例, 在 UE从第一移动管理单元移动至第二移动管理单元之后, 第 二移动管理单元从第一移动管理单元获取释放承载标识, 并根据上述标识确定是否在 Sl/Iu释放过程中进行 non GBR承载释放, 避免了相关技术中, UE由于移动进入至新 的移动管理单元覆盖区域, 且新的移动管理单元进行 Sl/Iu释放过程后, 无法确定是 否需要发起 non GBR承载释放流程, 由于 PCRF会将某些 IMS语音业务映射到 non GBR承载上, 为了使业务层计费精确, PCRF会在新建承载或者承载修改过程中需要 通过 PGW、 SGW指示移动管理单元是否需要在 Sl/Iu释放过程中将该部分 non GBR 承载进行释放, 这样 Sl/Iu释放后业务层会出现计费不精确的问题, 提高了业务层计 费的准确性。 显然, 本领域的技术人员应该明白, 上述的本发明的各模块或各步骤可以用通用 的计算装置来实现, 它们可以集中在单个的计算装置上, 或者分布在多个计算装置所 组成的网络上, 可选地, 它们可以用计算装置可执行的程序代码来实现, 从而, 可以 将它们存储在存储装置中由计算装置来执行, 并且在某些情况下, 可以以不同于此处 的顺序执行所示出或描述的步骤, 或者将它们分别制作成各个集成电路模块, 或者将 它们中的多个模块或步骤制作成单个集成电路模块来实现。 这样, 本发明不限制于任 何特定的硬件和软件结合。
以上所述仅为本发明的优选实施例而已, 并不用于限制本发明, 对于本领域的技 术人员来说, 本发明可以有各种更改和变化。 凡在本发明的精神和原则之内, 所作的 任何修改、 等同替换、 改进等, 均应包含在本发明的保护范围之内。
Claims
1. 一种承载释放方法, 包括:
当用户设备 UE从第一移动管理单元移动至第二移动管理单元之后, 所述 第二移动管理单元从所述第一移动管理单元获取释放承载标识;
所述第二移动管理单元根据所述释放承载标识确定是否在 Sl/Iu释放过程 中进行非保证比特率 non GBR承载释放。
2. 根据权利要求 1所述的方法, 其中, 在所述第二移动管理单元从所述第一移动 管理单元获取释放承载标识之前, 还包括:
在所述 UE 在所述第一移动管理单元下的承载建立或者承载修改的过程 中, 所述第一移动管理单元从策略与计费规则功能实体 PCRF或者分组数据网 关 PGW发送的消息中获取所述释放承载标识。
3. 根据权利要求 1所述的方法, 其中, 所述第二移动管理单元从所述第一移动管 理单元获取释放承载标识包括:
所述第二移动管理单元在与所述第一移动管理单元的跟踪区更新 TAU、路 由区更新 RAU或切换过程的上下文传递中获取所述释放承载标识。
4. 根据权利要求 1所述的方法, 其中, 在所述第二移动管理单元从所述第一移动 管理单元获取释放承载标识之后, 还包括:
所述第二移动管理单元选择新服务网关, 并向所述新服务网关发送承载建 立消息, 其中, 所述承载建立消息携带所述释放承载标记;
所述新服务网关向分组服务网关 PGW发送承载修改消息, 其中, 所述承 载修改消息携带所述释放承载标识。
5. 根据权利要求 1所述的方法, 其中, 在所述第二移动管理单元从所述第一移动 管理单元获取释放承载标识之后, 还包括:
如果服务网关中的承载上下文中存储了所述释放承载标识, 且所述第二移 动管理单元向所述服务网关发送的承载修改消息传递到没有携带所述释放承载 标识, 则所述服务网关确定所述第二移动管理单元不支持在 Sl/Iu释放过程中 进行 non GBR承载释放; 所述服务网关通知 PGW所述第二移动管理单元不支持在 Sl/Iu释放过程中 进行 non GBR承载释放。
6. 根据权利要求 1至 5中任一项所述的方法, 其中,
所述移动管理单元包括以下之一: 移动管理实体 MME、 服务通用分组无 线业务支持节点 SGSN。
7. 根据权利要求 1至 5中任一项所述的方法, 其中, 所述释放承载标识为一个单独的信息单元。
8. 一种承载释放系统, 包括: 用户设备 UE、 第一移动管理单元、 第二移动管理 单元,
其中, 所述第二移动管理单元包括:
获取模块, 设置为在所述 UE从所述第一移动管理单元移动至所述第二移 动管理单元之后, 从所述第一移动管理单元获取释放承载标识;
第一确定模块, 设置为根据所述释放承载标识确定是否在 Sl/Iu释放过程 中进行 non GBR承载释放。
9. 根据权利要求 8所述的承载释放系统, 其中,
所述第一移动管理单元设置为在所述 UE在所述第一移动管理单元下的承 载建立或者承载修改的过程中, 从策略与计费规则功能实体 PCRF或者分组数 据网关 PGW发送的消息中获取所述释放承载标识。
10. 根据权利要求 8所述的承载释放系统, 其中, 所述获取模块设置为在与所述第一移动管理单元的跟踪区更新 TAU、路由 区更新 RAU或切换过程的上下文传递中获取所述释放承载标识。
11. 根据权利要求 8所述的承载释放系统, 其中,
所述第二移动管理单元模块还包括:
选择模块, 设置为选择新服务网关;
第一发送模块, 设置为向所述新服务网关发送承载建立消息, 其中, 所述 承载建立消息携带所述释放承载标记;
所述承载释放系统还包括: 服务网关, 其中, 所述服务网关包括: 第二发送模块, 设置为向分组服务网关 PGW发送来自所述第一发送模块 的承载修改消息, 其中, 所述承载修改消息携带所述释放承载标识。
12. 根据权利要求 8所述的承载释放系统, 其中, 还包括服务网关, 其中, 所述服 务网关包括:
第二确定模块, 设置为在服务网关中的承载上下文中存储了所述释放承载 标识, 且所述第二移动管理单元向所述服务网关发送的承载修改消息中没有携 带所述释放承载标识时, 确定所述第二移动管理单元不支持在 Sl/Iu释放过程 中进行 non GBR承载释放;
通知模块, 设置为在所述第二确定模块确定所述第二移动管理单元不支持 在 Sl/Iu释放过程中进行 non GBR承载释放时, 通知 PGW所述第二移动管理 单元不支持在 Sl/Iu释放过程中进行 non GBR承载释放。
13. 根据权利要求 8至 12中任一项所述的承载释放系统, 其中, 所述移动管理单元包括以下之一: 移动管理实体 MME、 服务 GPRS支持 节点 SGSN。
14. 根据权利要求 8至 12中任一项所述的承载释放系统, 其中, 所述释放承载标识为一个单独的信息单元。
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201010267090.2A CN102378295B (zh) | 2010-08-23 | 2010-08-23 | 承载释放方法及系统 |
CN201010267090.2 | 2010-08-23 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2012024989A1 true WO2012024989A1 (zh) | 2012-03-01 |
Family
ID=45722875
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2011/077164 WO2012024989A1 (zh) | 2010-08-23 | 2011-07-14 | 承载释放方法及系统 |
Country Status (2)
Country | Link |
---|---|
CN (1) | CN102378295B (zh) |
WO (1) | WO2012024989A1 (zh) |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN103843430A (zh) * | 2012-09-27 | 2014-06-04 | 华为技术有限公司 | 一种寻呼的控制方法、装置、实体及网络设备 |
CN108370606A (zh) * | 2016-02-05 | 2018-08-03 | 捷开通讯(深圳)有限公司 | 早期连接释放 |
US20220191955A1 (en) * | 2013-10-31 | 2022-06-16 | Apple Inc. | Gateway Arrangements for Wireless Communication Networks |
Families Citing this family (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN109076496B (zh) * | 2016-05-03 | 2021-09-03 | 株式会社Kt | 用于改变终端连接状态的方法和装置 |
CN108810988B (zh) * | 2017-05-03 | 2020-12-01 | 华为技术有限公司 | 一种消息传输的方法及装置 |
WO2018201973A1 (zh) * | 2017-05-03 | 2018-11-08 | 华为技术有限公司 | 一种消息传输的方法及装置 |
CN109257779B (zh) | 2017-07-14 | 2024-09-17 | 华为技术有限公司 | 网络切换方法及装置 |
CN109041149B (zh) * | 2017-07-14 | 2020-01-03 | 华为技术有限公司 | 网络切换方法及装置 |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101296493A (zh) * | 2007-04-24 | 2008-10-29 | 华为技术有限公司 | 资源释放方法和网络设备 |
CN101742452A (zh) * | 2008-11-10 | 2010-06-16 | 华为技术有限公司 | 承载管理方法、相关设备及网络系统 |
CN101742576A (zh) * | 2008-11-07 | 2010-06-16 | 华为技术有限公司 | 恢复保留态gbr承载的方法及装置 |
-
2010
- 2010-08-23 CN CN201010267090.2A patent/CN102378295B/zh not_active Expired - Fee Related
-
2011
- 2011-07-14 WO PCT/CN2011/077164 patent/WO2012024989A1/zh active Application Filing
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101296493A (zh) * | 2007-04-24 | 2008-10-29 | 华为技术有限公司 | 资源释放方法和网络设备 |
CN101742576A (zh) * | 2008-11-07 | 2010-06-16 | 华为技术有限公司 | 恢复保留态gbr承载的方法及装置 |
CN101742452A (zh) * | 2008-11-10 | 2010-06-16 | 华为技术有限公司 | 承载管理方法、相关设备及网络系统 |
Non-Patent Citations (1)
Title |
---|
"General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access (Release 8)", 3GPP, 10 June 2010 (2010-06-10), pages 36 - 37, Retrieved from the Internet <URL:HTTP://3gpp.org/ftp/specs/archive/23.401/<23401-8a0.zip> * |
Cited By (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN103843430A (zh) * | 2012-09-27 | 2014-06-04 | 华为技术有限公司 | 一种寻呼的控制方法、装置、实体及网络设备 |
CN103843430B (zh) * | 2012-09-27 | 2018-06-26 | 华为技术有限公司 | 一种寻呼的控制方法、装置、实体及网络设备 |
US20220191955A1 (en) * | 2013-10-31 | 2022-06-16 | Apple Inc. | Gateway Arrangements for Wireless Communication Networks |
US11917701B2 (en) * | 2013-10-31 | 2024-02-27 | Apple Inc. | Gateway arrangements for wireless communication networks |
CN108370606A (zh) * | 2016-02-05 | 2018-08-03 | 捷开通讯(深圳)有限公司 | 早期连接释放 |
CN108370606B (zh) * | 2016-02-05 | 2022-05-06 | 捷开通讯(深圳)有限公司 | 早期连接释放 |
Also Published As
Publication number | Publication date |
---|---|
CN102378295A (zh) | 2012-03-14 |
CN102378295B (zh) | 2016-01-20 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US11889465B2 (en) | Paging cause value | |
JP6699800B2 (ja) | 方法、セッション管理機能ノード、ユーザプレーン機能ノード、ならびにセッション管理パラメータメンテナンス用ユーザ機器およびそのコンピュータ可読記録媒体 | |
CN102892109B (zh) | 一种实现ip地址属性通知的方法和系统 | |
US8855045B2 (en) | Method and system for controlling establishment of local IP access | |
US8582503B2 (en) | Method for indicating the bearer management of a serving gateway | |
US20110182244A1 (en) | Method for supporting context management by home node-b | |
WO2012024989A1 (zh) | 承载释放方法及系统 | |
WO2016180018A1 (zh) | 一种接入方法及相应的接入节点、终端和通信网络 | |
WO2011047589A1 (zh) | 网络连接建立方法及装置、pcc策略制定方法及系统 | |
JP2015527783A (ja) | 輻輳状態報告方法およびアクセス・ネットワーク装置 | |
WO2011157189A2 (zh) | 位置上报方法、设备和系统 | |
WO2011109938A1 (zh) | 无线接入网元信息上报方法、设备和系统 | |
CN106162759A (zh) | 决策服务质量QoS的方法、网络侧网元及系统 | |
EP4046461A1 (en) | Signaling delivery in a wireless network | |
WO2008154783A1 (fr) | Procédé pour établir un tunnel à partir de sgsn vers la passerelle de service | |
WO2017028637A1 (zh) | 网关的恢复处理方法及装置 | |
WO2016173283A1 (zh) | 一种接入业务网络的方法及装置、基站 | |
CN102761958B (zh) | 一种支持多接入的承载管理方法和系统 | |
CN101998364B (zh) | 一种对本地网际协议访问连接实施管理的方法及系统 | |
WO2012129997A1 (zh) | 本地访问连接的处理方法及装置 |
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: 11819364 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: 11819364 Country of ref document: EP Kind code of ref document: A1 |