CN102378295B - Resource release method and system - Google Patents

Resource release method and system Download PDF

Info

Publication number
CN102378295B
CN102378295B CN201010267090.2A CN201010267090A CN102378295B CN 102378295 B CN102378295 B CN 102378295B CN 201010267090 A CN201010267090 A CN 201010267090A CN 102378295 B CN102378295 B CN 102378295B
Authority
CN
China
Prior art keywords
mobile management
management unit
carrying
gateway
message
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Expired - Fee Related
Application number
CN201010267090.2A
Other languages
Chinese (zh)
Other versions
CN102378295A (en
Inventor
卢飞
梁爽
朱春晖
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
ZTE Corp
Original Assignee
ZTE Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by ZTE Corp filed Critical ZTE Corp
Priority to CN201010267090.2A priority Critical patent/CN102378295B/en
Priority to PCT/CN2011/077164 priority patent/WO2012024989A1/en
Publication of CN102378295A publication Critical patent/CN102378295A/en
Application granted granted Critical
Publication of CN102378295B publication Critical patent/CN102378295B/en
Expired - Fee Related legal-status Critical Current
Anticipated expiration legal-status Critical

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

Abstract

The invention discloses a kind of resource release method and system, the method comprises: when user equipment (UE) is from after the first mobile management unit moves to the second mobile management unit, the second mobile management unit obtains releasing bearing mark from the first mobile management unit; Does second mobile management unit determine whether to carry out non-ensured bit rate non in S1/Iu dispose procedure according to releasing bearing mark? GBR carries release.By the present invention, improve the accuracy of operation layer charging.

Description

Resource release method and system
Technical field
The present invention relates to the communications field, in particular to a kind of resource release method and system.
Background technology
Along with global microwave access intercommunication (WorldInteroperabilityforMicrowaveAccess, referred to as WiMAX) sudden emergence, 3-G (Generation Three mobile communication system) will keep it in the strong competitiveness of moving communicating field, must improve its network performance and reduce networking and operation cost.Therefore, third generation partner program (3rdGenerationPartnershipProject, referred to as 3GPP) standardization effort group, just be devoted to research packet switch core net (PacketSwitchCore at present, referred to as PSCore) and global system for mobile communications wireless access network (UniversalMobileTelecommunicationSystemRadioAccessNetwork, referred to as UTRAN) evolution, the problem of this research is called System Architecture Evolution (SystemArchitectureEvolution, referred to as SAE), its objective is the Packet Based Network (EvolvedPacketCore making evolution, be called for short EPC) higher transmission rate can be provided, shorter transmission delay, optimize grouping, and support the UTRAN (EvolvedUTRAN of evolution, referred to as E-UTRAN), UTRAN, WLAN (wireless local area network) (WirelessLocalAreaNetwork, referred to as WLAN) and other non-3 gpp access network between mobile management.
The framework of current SAE as shown in Figure 1, wherein contains following network element:
The wireless access network (EvolvedRAN, referred to as E-RAN) of evolution: higher uplink/downlink speed, lower transmission delay and more reliable wireless transmission can be provided.The network element comprised in E-RAN is eNodeB (EvolvedNodeB, enode b), provides Radio Resource for the access for user.
Packet Data Network (PacketDataNetwork, referred to as PDN): for user provides the network of business.
The Packet Based Network (E-PacketCore) of evolution, provides lower delay, and allows more wireless access system to access.It comprises following network element:
Mobile management entity (MobilityManagementEntity, referred to as MME): chain of command functional entity, the server of interim storage user data, be in charge of and store context (such as UE/ user ID, the mobility management states of subscriber equipment (UserEquipment, referred to as UE), user security parameters etc.), for user distributes temporary mark, when UE quarters at this tracing area or this network, be responsible for carrying out authentication to this user; All non-access layer informations between process MME and UE; Trigger the paging in SAE system.MME is the mobile management unit of SAE system.In the umts system, mobile management unit is SGSN (ServingGPRSSupportNode, Serving GPRS Support Node).
Gateway (ServingGateway, referred to as SGW) is a user entity, is responsible for user face data route processing, and termination is in the downlink data of the UE of free time (ECM_IDLE) state.The SAE of management and storage UE carries (bearer) context, such as IP bearer service parameter and network internal routing iinformation etc.SGW is the anchor point in 3GPP internal system user face, and a user can only have a SGW a moment;
Packet data network gateway (PDNGateway, referred to as PGW), be responsible for the gateway that UE accesses PDN, distributing user IP address is the mobility anchor point of 3GPP and non-3 GPP access system simultaneously, and the function of PGW also comprises strategy enforcement, charging support.User can access multiple PGW at synchronization.PCEF (PolicyandChargingEnforcementFunction, functional entity is implemented in strategy and charging) is also arranged in PGW.
Strategy and charging regulation function entity (PolicyandChargingRulesFunction, referred to as PCRF) are responsible for providing policy control and charging regulation to PCEF.
Home subscriber server (HomeSubscriberServer, referred to as HSS) permanent storage user contracting data, the content that HSS stores comprises the IMSI (InternationalMobileSubscriberIdentification, international mobile subscriber identity) of UE, the IP address of PGW.
Physically, SGW and PGW may unify.EPC system user veil unit comprises SGW and PGW.
In order to save interface-free resources and the economize on electricity of user, need UE to be converted into idle condition from connection status, this process is called that in E-UTRAN system S1 discharges flow process, is called that Iu discharges flow process in GPRS process.Discharge in flowchart process at S1, when release cause is due to " user's inertia ", guarantee bit rate (the GuaranteedBitRate of user, referred to as GBR) carrying and nonGBR (non-ensured bit rate) carry all retain, but when release cause is due to other reason, mobile management entity only retains nonGBR carrying, and GBR carrying all needs to initiate release by MME.S1 dispose procedure as shown in Figure 2, comprises the following steps:
Step 201, eNodeB detects the context needing to discharge UE, and eNodeB sends UE context release request message to MME, carries release cause value in this message;
Step 202, MME sends release access bearer request message to SGW, and request SGW deletes address and the Tunnel End Point Identifier (TunnelEndpointIDentifier, referred to as TEID) of the eNodeB stored;
Step 203, SGW deletes address and the TEID of the eNodeB stored, and returns release access bearer response message to MME.
Step 204, MME sends UE context release order message to eNodeB.
Step 205, is not also released if the radio bearer of user connects (RadioResourceConnection, referred to as RRC), and eNodeB sends RRC Connection Release request message to UE.
Step 206, UE returns RRC connection release response message to eNodeB.
Step 207, eNodeB returns UE context Release complete to MME.
Step 208, MME determines release GBR carrying according to the release cause value in step 201; If the release cause in step 201 is " user's inertia ", MME does not initiate GBR and carries dispose procedure, but when the release cause in step 201 is other reason, MME initiates GBR carrying release flow process.
In view of PCRF can by some IP Multimedia System (IPMultimediasub-System, referred to as IMS) speech business is mapped in nonGBR carrying, in order to make operation layer charging accurate, PCRF can need to pass through PGW in newly-built carrying or bearing modification process, SGW indicates MME this part nonGBR carrying to be discharged the need of in S1release process, as shown in Figure 3, comprise the following steps:
Step 301, PCRF sends PCC strategy to PGW.
Step 302, PGW sends carrying to SGW and sets up request message, carrying QoS (QualityofService is carried in this message, service quality), bearer service flow template (TrafficFlowTemplate, referred to as TFT), the address, user face of PGW and TEID, charging identifier, if in addition IMS voice bearer is mapped in nonGBR carrying, also need to carry releasing bearing instruction, be used to indicate and by MME, initiation carrying dispose procedure carried to this nonGBR in S1 dispose procedure.
Step 303, SGW sends carrying to MME and sets up request message, carries carrying QoS in this message, the address, user face of carrying TFT, SGW and TEID, and charging identifier, releasing bearing indicates.
Step 304, MME distributes a bearing identification for this carrying, and sets up session management request, and session management request comprises carrying QoS, bearing identification, carrying TFT; MME sends carrying to eNodeB and sets up request message, carries session management request in this message, carrying QoS, bearing identification, the address, user face of SGW and TEID.
Step 305, eNodeB sends RRC to UE and connects reconfiguration message, carries radio bearer QoS, session management request, radio bearer identification in this message.
Step 306, UE sends RRC connection to eNodeB and has reshuffled message.
Step 307, eNodeB sends carrying to MME and sets up response message, carries address, user face and the TEID of eNodeB.
Step 308, UE Non-Access Stratum sets up session establishment response, and passes to eNodeB by direct-sending message.
Step 309, eNodeB by up direct-sending message by session establishment response pass to MME.
Step 310, MME replys carrying to SGW and sets up response message, message comprises bearing identification, the address, user face of eNodeB and TEID, need to carry releasing bearing instruction simultaneously, the instruction of this releasing bearing can make SGW, and PGW is known whether MME is supported in S1 dispose procedure and discharged nonGBR bearing function.
Step 311, SGW replys carrying to PGW and sets up response message, and message comprises bearing identification, the address, user face of SGW and TEID, need to carry releasing bearing instruction simultaneously, the instruction of this releasing bearing PGW can be made to know whether MME is supported in S1 dispose procedure discharges nonGBR bearing function;
Step 312, PGW sends the success of IP session modification to PCRF.
If but UE is owing to moving into new mobile management unit overlay area, after new mobile management unit carries out S1/Iu dispose procedure, cannot determine whether to need to initiate nonGBR carrying release flow process, because some IMS speech business can be mapped in nonGBR carrying by PCRF, in order to make operation layer charging accurate, PCRF can need to pass through PGW in newly-built carrying or bearing modification process, SGW indicates mobile management unit this part nonGBR carrying to be discharged the need of in S1/Iu dispose procedure, after such S1/Iu release, operation layer there will be the coarse problem of charging.
Summary of the invention
Main purpose of the present invention is to provide a kind of resource release method and system, new mobile management unit is moved to solve above-mentioned UE, and after new mobile management unit carries out S1/Iu dispose procedure, cannot determine whether to need to initiate nonGBR carrying release flow process, thus after the S1/Iu caused release, operation layer there will be the coarse problem of charging.
To achieve these goals, according to an aspect of the present invention, a kind of resource release method is provided.
Resource release method according to the present invention comprises: when user equipment (UE) is from after the first mobile management unit moves to the second mobile management unit, the second mobile management unit obtains releasing bearing mark from the first mobile management unit; According to releasing bearing mark, second mobile management unit determines whether that in S1/Iu dispose procedure, carry out non-ensured bit rate nonGBR carries release.
Further, before the second mobile management unit obtains releasing bearing mark from the first mobile management unit, also comprise: in the process of the carrying foundation of UE under the first mobile management unit or bearing modification, the first mobile management unit obtains releasing bearing and identifies from the message that strategy and charging regulation function entity PCRF or packet data gateway PGW send.
Further, the second mobile management unit obtains releasing bearing mark from the first mobile management unit and comprises: the second mobile management unit with the context transfer of the tracing section updating TAU of the first mobile management unit, routing area updating RAU or handoff procedure obtain releasing bearing and identify.
Further, after the second mobile management unit obtains releasing bearing mark from the first mobile management unit, also comprise: the second mobile management unit selects new gateway, and set up message to new gateway transmission carrying, wherein, carrying is set up message and is carried releasing bearing mark; New gateway sends bearing modification message to packet service gateway PGW, and wherein, bearing modification message carries releasing bearing mark.
Further, after the second mobile management unit obtains releasing bearing mark from the first mobile management unit, also comprise: if store releasing bearing mark in the bearer context in gateway, and the bearing modification Message Transmission that the second mobile management unit sends to gateway is not to carrying releasing bearing mark, then gateway is determined that the second mobile management unit is not supported in S1/Iu dispose procedure and is carried out nonGBR carrying release; Gateway notice PGW second mobile management unit is not supported in S1/Iu dispose procedure and carries out nonGBR carrying release.
Further, above-mentioned mobile management unit comprises one of following: mobile management entity MME, Serving GPRS Support Node SGSN.
Further, releasing bearing is designated an independent information unit.
To achieve these goals, according to a further aspect in the invention, a kind of carrying delivery system is provided.
Carrying delivery system according to the present invention comprises: user equipment (UE), the first mobile management unit, the second mobile management unit, wherein, second mobile management unit comprises: acquisition module, for at UE from after the first mobile management unit moves to the second mobile management unit, obtain releasing bearing mark from the first mobile management unit; First determination module, carries out nonGBR carrying release for determining whether according to releasing bearing mark in S1/Iu dispose procedure.
Further, first mobile management unit is used in the process of the carrying foundation of UE under the first mobile management unit or bearing modification, obtains releasing bearing and identify from the message that strategy and charging regulation function entity PCRF or packet data gateway PGW send.
Further, acquisition module be used for the context transfer of the tracing section updating TAU of the first mobile management unit, routing area updating RAU or handoff procedure in obtain releasing bearing and identify.
Further, the second mobile management unit also comprises: select module, for selecting new gateway; First sending module, sets up message for sending carrying to new gateway, and wherein, carrying is set up message and carried releasing bearing mark; Carrying delivery system also comprises: gateway, and wherein, gateway comprises: the second sending module, and for sending bearing modification message to packet service gateway PGW, wherein, bearing modification message carries releasing bearing mark.
Further, said system also comprises gateway, wherein, gateway comprises: the second determination module, for storing releasing bearing mark in the bearer context in gateway, and when not carrying releasing bearing mark in the bearing modification message that sends to gateway of the second mobile management unit, determine that the second mobile management unit is not supported in S1/Iu dispose procedure and carry out nonGBR carrying release; Notification module, for determine at the second determination module the second mobile management unit be not supported in S1/Iu dispose procedure carry out nonGBR carrying release time, notice PGW second mobile management unit is not supported in S1/Iu dispose procedure and carries out nonGBR carrying release.
Further, mobile management unit comprises one of following: mobile management entity MME, Serving GPRS Support Node SGSN.
Further, releasing bearing is designated an independent information unit.
By the present invention, adopt when user equipment (UE) is from after the first mobile management unit moves to the second mobile management unit, the second mobile management unit obtains releasing bearing from the first mobile management unit and identifies; According to releasing bearing mark, second mobile management unit determines whether that in S1/Iu dispose procedure, carry out non-ensured bit rate nonGBR carries release, solve above-mentioned UE and move to new mobile management unit, and after new mobile management unit carries out S1/Iu dispose procedure, cannot determine whether to need to initiate nonGBR carrying release flow process, thus after causing S1/Iu to discharge, operation layer there will be the coarse problem of charging, and then reach the effect improving operation layer billing accuracy.
Accompanying drawing explanation
Accompanying drawing described herein is used to provide a further understanding of the present invention, and form a application's part, schematic description and description of the present invention, for explaining the present invention, does not form inappropriate limitation of the present invention.In the accompanying drawings:
Fig. 1 is the schematic diagram of the evolution packet network system configuration according to correlation technique;
Fig. 2 is the signaling process figure discharged according to the S1 of correlation technique;
Fig. 3 is the signaling process figure set up according to the carrying of correlation technique;
Fig. 4 is the flow chart of the resource release method according to the embodiment of the present invention;
Fig. 5 moves to new MME according to the UE of the embodiment of the present invention and the flow chart of resource release method that do not change of SGW;
Fig. 6 moves to new MME according to the UE of the embodiment of the present invention and new MME selects the flow chart of the resource release method of new SGW;
Fig. 7 is the flow chart of the resource release method moving to new MME of switching according to the UE of the embodiment of the present invention;
Fig. 8 is the structured flowchart of the carrying delivery system according to the embodiment of the present invention; And
Fig. 9 is the preferred structured flowchart of the carrying delivery system according to the embodiment of the present invention.
Embodiment
Hereinafter also describe the present invention in detail with reference to accompanying drawing in conjunction with the embodiments.It should be noted that, when not conflicting, the embodiment in the application and the feature in embodiment can combine mutually.
Present embodiments provide a kind of resource release method, Fig. 4 is the flow chart of the resource release method according to the embodiment of the present invention, and as shown in Figure 4, the method comprises:
Step S402, when UE is from after the first mobile management unit moves to the second mobile management unit, the second mobile management unit obtains releasing bearing mark from the first mobile management unit.
Step S404, the second mobile management unit determines whether in S1/Iu dispose procedure, carry out non-ensured bit rate (nonGBR) carrying release according to releasing bearing mark.
Pass through above-mentioned steps, at UE from after the first mobile management unit moves to the second mobile management unit, second mobile management unit obtains releasing bearing mark from the first mobile management unit, and determine whether in S1/Iu dispose procedure, carry out nonGBR carrying release according to above-mentioned mark, avoid in correlation technique, UE is owing to moving into new mobile management unit overlay area, and after new mobile management unit carries out S1/Iu dispose procedure, cannot determine whether to need to initiate nonGBR carrying release flow process, because some IMS speech business can be mapped in nonGBR carrying by PCRF, in order to make operation layer charging accurate, PCRF can need to pass through PGW in newly-built carrying or bearing modification process, SGW indicates mobile management unit this part nonGBR carrying to be discharged the need of in S1/Iu dispose procedure, after such S1/Iu release, operation layer there will be the coarse problem of charging, improve the accuracy of operation layer charging.
Preferably, before step S402, said method also comprises: in the process of the carrying foundation of UE under the first mobile management unit or bearing modification, and the first mobile management unit obtains releasing bearing and identifies from the message that strategy and charging regulation function entity PCRF or packet data gateway PGW send.By this preferred embodiment, achieve the first mobile management unit and obtain releasing bearing mark.
Below to the second mobile management unit in step S404 from first mobile management unit obtain releasing bearing mark some be preferred embodiment described.Second mobile management unit is at the tracing section updating (TrackingAreaUpdate with the first mobile management unit, referred to as TAU), obtain releasing bearing mark in the context transfer of Routing Area Update (RoutingAreaUpdate, referred to as RAU) or handoff procedure.By the obtaining step of this preferred embodiment, achieve the second mobile management unit in several cases and obtain releasing bearing mark, improve the flexibility and applicability that obtain bearing identification method.
Preferably, after step S402, said method also comprises: the second mobile management unit selects new gateway, and sets up message to new gateway transmission carrying, and wherein, carrying is set up message and carried releasing bearing mark; New gateway sends bearing modification message to packet service gateway (PGW), and wherein, bearing modification message carries releasing bearing mark.By this preferred embodiment, achieve under the second mobile management unit selects new gateway situation, new gateway and packet service gateway obtain releasing bearing mark.
Preferably, after step S402, said method also comprises: if store releasing bearing mark in the bearer context in gateway, and the second mobile management unit to the bearing modification message that gateway sends do not carry releasing bearing mark, then gateway determine the second mobile management unit be not supported in S1/Iu dispose procedure carry out carrying discharge; Gateway notice PGW second mobile management unit is not supported in S1/Iu dispose procedure and carries out carrying release.This preferred embodiment achieves and store releasing bearing mark in service gateway bearing context, and this mark is not delivered to gateway by the second mobile management unit, then this gateway determines that the second mobile management unit does not support to carry out in S1/Iu dispose procedure carrying release and by this context notification to PGW.
Preferably, mobile management unit comprises one of following: MME, SGSN.By the preferred embodiment, achieve the applicability of releasing bearing method application.
Preferably, releasing bearing is designated an independent information unit.By the preferred embodiment, releasing bearing mark implements fairly simple, and overhead is smaller.
Embodiment one
The present embodiment combines above-described embodiment and preferred implementation wherein, present embodiments provide a kind of method of releasing bearing, Fig. 5 moves to new MME according to the UE of the embodiment of the present invention and the flow chart of resource release method that do not change of SGW, and as shown in Figure 5, the method comprises:
Step 501, UE moves to the E-UTRAN area of coverage under MME, except carrying the GUTI that UE distributes under old MME in the tracing section updating request message sent to MME, also will carry the ability whether UE supports ISR.
Step 502, new MME finds old MME according to GUTI mark, sends context request signaling and carries out context acquisition process.
Step 503, the mobile management of user and beared information are sent to new MME by old MME, and carry in the context response information returned in S1/Iu dispose procedure the need of triggering the marker passing of nonGBR carrying release to new MME.
Preferably, this mark can with an independent information unit (InformationElement, referred to as IE) represent, in carrying foundation or bearer update process, the need of the instruction by nonGBR carrying release in the S1 dispose procedure that MME record PCRF/PGW sends over, carry release flow process to trigger in the process of S1 release; Old MME needs above-mentioned marker passing unmarkedly can notify that new MME is the need of triggering carrying release flow process with having to new MME, old MME; Old MME also can indicate new MME to need to trigger carrying release flow process with " 1 " in IE, represent that new MME does not need to trigger carrying release flow process with " 0 ".
Step 504, new MME replys context acknowledgement message to old MME.
Step 505, new MME is to the request of SGW starting update load bearing, source GTP-C Tunnel Identifier and object GTP-C Tunnel Identifier is carried in request message, the binding relationship of SGW more new bearer, the positional information of UE, this message also need to carry self whether be supported in S1 dispose procedure trigger nonGBR carry dispose procedure.
Step 506, SGW sends more new bearer request to PGW, carries the positional information of UE in request message; If new MME does not support that triggering nonGBR in S1 dispose procedure carries dispose procedure, SGW needs to notify PGW in this renewal bearing request message.
Step 507, PGW upgrades the context of oneself and returns more new bearer response message to SGW.
Step 508, SGW returns more new bearer response to new MME, and the object GTP-C Tunnel Identifier of being specified by SGW, the address of self and the address of PGW and tunnel information etc. bring MME.
Step 509, new MME is by the change of location update message notice HSS position.
Step 510, HSS sends canceling position signaling to old MME.
Step 511, old MME cancels response to HSS home position.
Step 512, the location updating of HSS to new MME confirms, and user contracting data is passed to new MME.
Step 513, if new MME confirms that UE is effective in current tracking area, then sends tracing section updating to UE and accepts message.
Step 514, if new MME is that UE is assigned with a new GUTI mark by TAU flow process, so UE can upgrade message and has confirmed to MME in returning tracking district.
It should be noted that, be move to new MME overlay area for UE to illustrate in the present embodiment; Move to new SGSN for UE, processing method is similar with it, does not repeat them here.
Embodiment two
The present embodiment combines above-described embodiment and preferred implementation wherein, present embodiments provide a kind of method of releasing bearing, Fig. 6 moves to new MME according to the UE of the embodiment of the present invention and new MME selects the flow chart of the resource release method of new SGW, and as shown in Figure 6, the method comprises:
Step 601, UE moves to the E-UTRAN area of coverage under MME, except carrying the GUTI that UE distributes under old MME in the tracing section updating request message sent to MME, also will carry the ability whether UE supports ISR.
Step 602, new MME finds old MME according to GUTI mark, sends context request signaling and carries out context acquisition process.
Step 603, the mobile management of user and beared information are sent to new MME by old MME, and carry in the context response information returned in S1/Iu dispose procedure the need of triggering the marker passing of nonGBR carrying release to new MME.
Preferably, this mark can represent with an IE, set up in carrying or in bearer update process, the need of the instruction by nonGBR carrying release in the S1 dispose procedure that MME record PCRF/PGW sends over, carry release flow process to trigger in the process of S1 release; Old MME needs above-mentioned marker passing unmarkedly can notify that new MME is the need of triggering carrying release flow process with having to new MME, old MME; Old MME also can indicate new MME to need to trigger carrying release flow process with " 1 " in IE, represent that new MME does not need to trigger carrying release flow process with " 0 "; Old MME also can indicate new MME to need to trigger carrying release flow process with " 0 " in IE, represent that new MME does not need to trigger carrying release flow process with " 1 ".
Step 604, new MME replys context acknowledgement message to old MME.
Step 605, new MME sets up request to new SGW initiation session, source GTP-C Tunnel Identifier and object GTP-C Tunnel Identifier is carried in request message, SGW control plane address and TEID, the positional information of UE, this message also need to carry self whether be supported in S1 dispose procedure trigger nonGBR carry dispose procedure.
Step 606, SGW sends more new bearer request to PGW, carries the positional information of UE in request message; Whether this message also needs to carry self and MME and is supported in S1 dispose procedure and triggers nonGBR and carry dispose procedure.
Step 607, PGW upgrades the context of oneself and returns more new bearer response message to SGW.
Step 608, SGW returns session establishment response to new MME, and the object GTP-C Tunnel Identifier of being specified by SGW, the address of self and the address of PGW and tunnel information etc. bring MME.
Step 609, new MME is by the change of location update message notice HSS position.
Step 610, HSS sends canceling position signaling to old MME.
Step 611, old MME cancels response to HSS home position.
Step 612, the location updating of HSS to new MME confirms, and user contracting data is passed to new MME.
Step 613, if new MME confirms that UE is effective in current tracking area, then sends tracing section updating to UE and accepts message.
Step 614, if new MME is that UE is assigned with a new GUTI mark by TAU flow process, so UE can upgrade message and has confirmed to MME in returning tracking district.
Step 615, old MME sends releasing session request message to old SGW, and notice SGW deletes the context of user.
Step 616, old SGW returns releasing session response message to old MME.
It should be noted that, be move to new MME overlay area for UE to illustrate in the present embodiment; Move to new SGSN for UE, processing method is similar with it, does not repeat them here.
Embodiment three
The present embodiment combines above-described embodiment and preferred implementation wherein, present embodiments provide a kind of method of releasing bearing, Fig. 7 is the flow chart of the resource release method moving to new MME of switching according to the UE of the embodiment of the present invention, and as shown in Figure 7, the method comprises:
Step 701, former eNodeB determines to initiate between eNodeB to new eNodeB, the switching of core net node code reassignment.
Step 702, former eNodeB sends handover request message to old MME.
Step 703, old MME selects new MME according to MME selection function, and to new MME sending node code reassignment request message, and this message comprises the address of PGW and the address of up TEID, SGW and up TEID; And carry in the message in S1/Iu dispose procedure the need of triggering the marker passing of nonGBR carrying release to new MME;
Preferably, this mark can represent with an independent information unit IE, set up in carrying or in bearer update process, the need of the instruction by nonGBR carrying release in the S1 dispose procedure that MME record PCRF/PGW sends over, carry release flow process to trigger in the process of S1 release; Old MME needs above-mentioned marker passing unmarkedly can notify that new MME is the need of triggering carrying release flow process with having to new MME, old MME; Old MME also can indicate new MME to need to trigger carrying release flow process with " 1 " in IE, represent that new MME does not need to trigger carrying release flow process with " 0 "; ; Old MME also can indicate new MME to need to trigger carrying release flow process with " 0 " in IE, represent that new MME does not need to trigger carrying release flow process with " 1 ".
Step 704, new MME sends session establishment request message to SGW, carries, the GTP-C Tunnel Identifier of PGW and IP address in request message, carrying QoS etc.; This message also need to carry self whether be supported in S1 dispose procedure trigger nonGBR carry dispose procedure.
Step 705, SGW returns session establishment response message to MME, carries GTP-C Tunnel Identifier and the address of self of SGW in response message.
Step 706, new MME sends handover request message to new eNodeB, asks to set up UE context in new eNodeB.
Step 707, new eNodeB sends switching request acknowledgement message to new MME.
Step 708, new MME is to old MME sending node code reassignment response message.
Step 709, old MME sends switch indicating information to former eNodeB.
Step 710, switch indicating information is forwarded to UE by former eNodeB.
Step 711, after UE and new eNodeB carries out cell synchronous, sends switch acknowledgment message to new eNodeB.
Step 712, new eNodeB sends handoff notification message to new MME.
Step 713, the message that new MME completes to old MME sending node code reassignment.
Step 714, the acknowledge message that old MME completes to new MME return node code reassignment.
Step 715, new MME, to the request of SGW starting update load bearing, carries user face Tunnel Identifier and the IP address of new eNodeB in request message.
Step 716, SGW sends more new bearer request to PGW, and the parameters such as the positional information of the address information of SGW, tunnel identification information, UE are sent to PGW; Whether this message also needs to carry self and MME and is supported in S1 dispose procedure and triggers nonGBR and carry dispose procedure.
Step 717, PGW upgrades the context of self, and returns renewal bearing response message to SGW.
Step 718, SGW returns renewal bearing response message to new MME.
Present embodiments provide a kind of carrying delivery system, Fig. 8 is the structured flowchart of the carrying delivery system according to the embodiment of the present invention, as shown in Figure 8, this system comprises: UE82, the first mobile management unit 84, second mobile management unit 86, wherein, second mobile management unit comprises: acquisition module 862 and the first determination module 864, be described in detail said structure below.
Acquisition module 862, for for UE from after the first mobile management unit moves to the second mobile management unit, obtain releasing bearing mark from the first mobile management unit; Preferably, acquisition module 862 for TAU, RAU of the first mobile management unit or the context transfer of handoff procedure in obtain releasing bearing and identify;
First determination module 864, is connected to acquisition module 862, and the releasing bearing mark for obtaining according to acquisition module 862 determines whether that in S1/Iu dispose procedure, carry out non-ensured bit rate nonGBR carries release;
First mobile management unit 84, in the process of the carrying foundation of UE under the first mobile management unit or bearing modification, obtains releasing bearing and identifies from the message that strategy and charging regulation function entity PCRF or packet data gateway PGW send.
Fig. 9 is the preferred structured flowchart of the carrying delivery system according to the embodiment of the present invention, second mobile management module 86 comprises: select module 866, first sending module 868, this carrying delivery system also comprises: gateway 88, wherein gateway 88 comprises: the second sending module 882, second determination module 884 and notification module 886, is described in detail to said structure below:
Second mobile management module 86 comprises: select module 866, for selecting new gateway; First sending module 868, is connected to and selects module 866, and set up message for sending carrying to the new gateway selecting module 866 to select, wherein, carrying is set up message and carried releasing bearing mark;
Gateway 88 comprises: the second sending module 882, and for sending bearing modification message to packet service gateway PGW, wherein, bearing modification message carries releasing bearing mark; Second determination module 884, for storing releasing bearing mark in the bearer context in gateway, and the second mobile management unit to the bearing modification message that it sends do not carry releasing bearing mark time, determine the second mobile management unit be not supported in S1/Iu dispose procedure carry out carrying discharge; Notification module 886, be connected to the second determination module 884, for determine at the second determination module 884 second mobile management unit be not supported in S1/Iu dispose procedure carry out carrying release time, notice PGW second mobile management unit is not supported in S1/Iu dispose procedure and carries out carrying and discharge.
Preferably, above-mentioned mobile management unit comprises one of following: MME, SGSN.
Preferably, above-mentioned releasing bearing is designated an independent information unit.
Pass through above-described embodiment, at UE from after the first mobile management unit moves to the second mobile management unit, second mobile management unit obtains releasing bearing mark from the first mobile management unit, and determine whether in S1/Iu dispose procedure, carry out nonGBR carrying release according to above-mentioned mark, avoid in correlation technique, UE is owing to moving into new mobile management unit overlay area, and after new mobile management unit carries out S1/Iu dispose procedure, cannot determine whether to need to initiate nonGBR carrying release flow process, because some IMS speech business can be mapped in nonGBR carrying by PCRF, in order to make operation layer charging accurate, PCRF can need to pass through PGW in newly-built carrying or bearing modification process, SGW indicates mobile management unit this part nonGBR carrying to be discharged the need of in S1/Iu dispose procedure, after such S1/Iu release, operation layer there will be the coarse problem of charging, improve the accuracy of operation layer charging.
Obviously, those skilled in the art should be understood that, above-mentioned of the present invention each module or each step can realize with general calculation element, they can concentrate on single calculation element, or be distributed on network that multiple calculation element forms, alternatively, they can realize with the executable program code of calculation element, thus, they can be stored and be performed by calculation element in the storage device, and in some cases, step shown or described by can performing with the order be different from herein, or they are made into each integrated circuit modules respectively, or the multiple module in them or step are made into single integrated circuit module to realize.Like this, the present invention is not restricted to any specific hardware and software combination.
The foregoing is only the preferred embodiments of the present invention, be not limited to the present invention, for a person skilled in the art, the present invention can have various modifications and variations.Within the spirit and principles in the present invention all, any amendment done, equivalent replacement, improvement etc., all should be included within protection scope of the present invention.

Claims (14)

1. a resource release method, is characterized in that, comprising:
When user equipment (UE) is from after the first mobile management unit moves to the second mobile management unit, described second mobile management unit obtains releasing bearing mark from described first mobile management unit;
According to described releasing bearing mark, described second mobile management unit determines whether that in S1/Iu dispose procedure, carry out non-ensured bit rate nonGBR carries release.
2. method according to claim 1, is characterized in that, before described second mobile management unit obtains releasing bearing mark from described first mobile management unit, also comprises:
In the process of the carrying foundation of described UE under described first mobile management unit or bearing modification, described first mobile management unit obtains described releasing bearing and identifies from the message that strategy and charging regulation function entity PCRF or packet data network gateway PGW send.
3. method according to claim 1, is characterized in that, described second mobile management unit obtains releasing bearing mark from described first mobile management unit and comprises:
Described second mobile management unit with the context transfer of the tracing section updating TAU of described first mobile management unit, routing area updating RAU or handoff procedure in obtain described releasing bearing and identify.
4. method according to claim 1, is characterized in that, described second mobile management unit from described first mobile management unit obtain releasing bearing mark after, also comprise:
Described second mobile management unit selects new gateway, and sets up message to described new gateway transmission carrying, and wherein, described carrying is set up message and carried described releasing bearing mark;
Described new gateway sends bearing modification message to packet data network gateway PGW, and wherein, described bearing modification message carries described releasing bearing mark.
5. method according to claim 1, is characterized in that, described second mobile management unit from described first mobile management unit obtain releasing bearing mark after, also comprise:
If store described releasing bearing mark in the bearer context in gateway, and described second mobile management unit to the bearing modification message that described gateway sends do not carry described releasing bearing mark, then described gateway determine described second mobile management unit be not supported in S1/Iu dispose procedure carry out nonGBR carrying release;
Second mobile management unit described in described gateway notice packet Data Network Gateway PGW is not supported in S1/Iu dispose procedure and carries out nonGBR carrying release.
6. the method according to any one of claim 1-5, is characterized in that,
Described mobile management unit comprises one of following: mobile management entity MME, service universal grouping wireless business supporting node SGSN.
7. the method according to any one of claim 1-5, is characterized in that,
Described releasing bearing is designated an independent information unit.
8. carry a delivery system, it is characterized in that, comprising: user equipment (UE), the first mobile management unit, the second mobile management unit,
Wherein, described second mobile management unit comprises:
Acquisition module, at described UE from after described first mobile management unit moves to described second mobile management unit, obtain releasing bearing mark from described first mobile management unit;
First determination module, for determining whether to carry out nonGBR carrying release in S1/Iu dispose procedure according to described releasing bearing mark.
9. carrying delivery system according to claim 8, is characterized in that,
Described first mobile management unit is used in the process of the carrying foundation of described UE under described first mobile management unit or bearing modification, obtains described releasing bearing and identify from the message that strategy and charging regulation function entity PCRF or packet data network gateway PGW send.
10. carrying delivery system according to claim 8, is characterized in that,
Described acquisition module be used for the context transfer of the tracing section updating TAU of described first mobile management unit, routing area updating RAU or handoff procedure in obtain described releasing bearing and identify.
11. carrying delivery systems according to claim 8, is characterized in that,
Described second mobile management unit also comprises:
Select module, for selecting new gateway;
First sending module, sets up message for sending carrying to described new gateway, and wherein, described carrying is set up message and carried described releasing bearing mark;
Described carrying delivery system also comprises: gateway, and wherein, described gateway comprises:
Second sending module, for sending bearing modification message to packet data network gateway PGW, wherein, described bearing modification message carries described releasing bearing mark.
12. carrying delivery systems according to claim 8, is characterized in that, also comprise gateway, and wherein, described gateway comprises:
Second determination module, for storing described releasing bearing mark in the bearer context in gateway, and when not carrying described releasing bearing mark in the bearing modification message that sends to described gateway of described second mobile management unit, determine that described second mobile management unit is not supported in S1/Iu dispose procedure and carry out nonGBR carrying release;
Notification module, for determine at described second determination module described second mobile management unit be not supported in S1/Iu dispose procedure carry out nonGBR carrying release time, the second mobile management unit described in notice packet Data Network Gateway PGW be not supported in S1/Iu dispose procedure carry out nonGBR carrying release.
13. carrying delivery systems according to Claim 8 described in-12 any one, is characterized in that,
Described mobile management unit comprises one of following: mobile management entity MME, Serving GPRS Support Node SGSN.
14. carrying delivery systems according to Claim 8 described in-12 any one, is characterized in that,
Described releasing bearing is designated an independent information unit.
CN201010267090.2A 2010-08-23 2010-08-23 Resource release method and system Expired - Fee Related CN102378295B (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN201010267090.2A CN102378295B (en) 2010-08-23 2010-08-23 Resource release method and system
PCT/CN2011/077164 WO2012024989A1 (en) 2010-08-23 2011-07-14 Method and system for bearer release

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201010267090.2A CN102378295B (en) 2010-08-23 2010-08-23 Resource release method and system

Publications (2)

Publication Number Publication Date
CN102378295A CN102378295A (en) 2012-03-14
CN102378295B true CN102378295B (en) 2016-01-20

Family

ID=45722875

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201010267090.2A Expired - Fee Related CN102378295B (en) 2010-08-23 2010-08-23 Resource release method and system

Country Status (2)

Country Link
CN (1) CN102378295B (en)
WO (1) WO2012024989A1 (en)

Families Citing this family (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2014047825A1 (en) * 2012-09-27 2014-04-03 华为技术有限公司 Method, apparatus, entity and network device for controlling page
US9596628B2 (en) 2013-10-31 2017-03-14 Intel Corporation Gateway arrangements for wireless communication networks
GB2547028B (en) * 2016-02-05 2021-06-16 Tcl Communication Ltd Early connection release
CN109076496B (en) * 2016-05-03 2021-09-03 株式会社Kt Method and apparatus for changing connection state of terminal
CN108810988B (en) * 2017-05-03 2020-12-01 华为技术有限公司 Message transmission method and device
WO2018201973A1 (en) * 2017-05-03 2018-11-08 华为技术有限公司 Method and apparatus for message transmission
CN109257779A (en) 2017-07-14 2019-01-22 华为技术有限公司 Method for switching network and device
CN109257788B (en) * 2017-07-14 2021-06-22 华为技术有限公司 Network switching method and device

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101742452A (en) * 2008-11-10 2010-06-16 华为技术有限公司 Load bearing management method, relevant equipment and network system

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101296493B (en) * 2007-04-24 2013-02-13 华为技术有限公司 Resource releasing method and network appliance
CN101742576B (en) * 2008-11-07 2013-06-05 华为技术有限公司 Method and device for recovering reserved GBR load

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101742452A (en) * 2008-11-10 2010-06-16 华为技术有限公司 Load bearing management method, relevant equipment and network system

Also Published As

Publication number Publication date
CN102378295A (en) 2012-03-14
WO2012024989A1 (en) 2012-03-01

Similar Documents

Publication Publication Date Title
CN102378295B (en) Resource release method and system
CN102892109B (en) A kind of method and system for realizing IP address property notification
CN101969634B (en) Method and system for synchronizing user data
CN101459907B (en) Method for indicating service gateway bearing management
CN101282511B (en) Bearing processing method
CN100488170C (en) Update method of route trigger area in the packet wireless system
CN101166359B (en) Method for selecting management nodes in mobile communication system
CN102685921A (en) Dual-channel communication method and system
CN101325583B (en) Method for registering gateway address and mobility management entity
CN101330425B (en) Method for establishing tunnel from SGSN to service gateway
CN101448209B (en) Notification method of location information of user equipment of evolved packet system and system thereof
CN101505474B (en) Network side processing method in subscriber handover process, network element equipment and network system
CN101296496B (en) Method for preventing false resource release in tracing section updating or switching course
CN102905369B (en) User equipment calling method and system when mobile management unit fails or restarts
CN101448328B (en) Method for establishing default bearing
CN101959209B (en) Synchronization method and system for partial failure handling
CN104519538A (en) User equipment, and method, device and system for receiving request messages
CN103781041B (en) Charging synchronous method, apparatus and system
CN102014370B (en) Method and system for selecting IWP (Inter Working Proxy)
CN101203027A (en) System for selecting supervision node in mobile communication system
CN102065503A (en) Service gateway selection system and method
CN104144398B (en) A kind of realization method and system of callee function, HSS, SCC AS
CN101203028A (en) Method for searching of mobile communication system
CN102625411B (en) User's method for releasing of a kind of network element overload and system
CN102131177A (en) Method and system for releasing resources of user equipment (UE)

Legal Events

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

Granted publication date: 20160120

Termination date: 20190823

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