CN102378295A - Method and system for bearer release - Google Patents
Method and system for bearer release Download PDFInfo
- Publication number
- CN102378295A CN102378295A CN2010102670902A CN201010267090A CN102378295A CN 102378295 A CN102378295 A CN 102378295A CN 2010102670902 A CN2010102670902 A CN 2010102670902A CN 201010267090 A CN201010267090 A CN 201010267090A CN 102378295 A CN102378295 A CN 102378295A
- Authority
- CN
- China
- Prior art keywords
- mobile management
- management unit
- gateway
- carrying
- releasing
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
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
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
The invention discloses a method and system for bearer release. The method comprises the steps: after UE (User Equipment) is moved from a first mobile management unit to a second mobile management unit, the second mobile management unit obtains a bearer release identifier from the first mobile management unit; the second mobile management unit determines whether to conduct a non-GBR (Guaranteed Bit Rate) bearer release in a S1/Iu release process according to the bearer release identifier. According to the method and system for bearer release, disclosed by the invention, the accuracy of service layer billing is improved.
Description
Technical field
The present invention relates to the communications field, in particular to a kind of carrying method for releasing and system.
Background technology
Along with global microwave access intercommunication (World Interoperability for MicrowaveAccess; Abbreviate WiMAX as) sudden emergence; 3-G (Generation Three mobile communication system) will keep its strong competitiveness at moving communicating field, must improve its network performance and reduce networking and operation cost.Therefore, the standardization effort group of third generation partner program (3rd GenerationPartnership Project abbreviates 3GPP as); Just be devoted to study packet switch core net (Packet Switch Core at present; Abbreviate PS Core as) and the evolution of global system for mobile communications wireless access network (Universal Mobile Telecommunication SystemRadio Access Network abbreviates UTRAN as), the problem of this research is called System Architecture Evolution (System Architecture Evolution; Abbreviate SAE as); Its objective is and make the Packet Based Network (Evolved Packet Core is called for short EPC) of evolution higher transmission rate can be provided, shorter transmission delay; Optimize and divide into groups; And the mobile management between the access network of UTRAN (Evolved UTRAN abbreviates E-UTRAN as), UTRAN, WLAN (Wireless Local Area Network abbreviates WLAN as) and other non-3GPP of support evolution.
The framework of SAE is as shown in Figure 1 at present, has wherein comprised following network element:
The wireless access network of evolution (Evolved RAN abbreviates E-RAN as): can provide higher on/downstream rate, lower transmission delay and wireless transmission more reliably.The network element that comprises among the E-RAN is eNodeB (Evolved NodeB, an enode b), and the access that is used to the user provides Radio Resource.
Packet Data Network's (Packet Data Network abbreviates PDN as): for the user provides professional network.
The Packet Based Network of evolution (E-Packet Core) provides lower delay, and allows more wireless access system to insert.It comprises following network element:
Mobile management entity (Mobility Management Entity abbreviates MME as): chain of command functional entity, the server of interim storaging user data; The context of being in charge of and storing subscriber equipment (User Equipment abbreviates UE as) is (such as UE/ ID, mobility management states; User security parameters etc.); For the user distributes temporary mark, when UE quarters at this tracing area or this network, be responsible for this user is carried out authentication; Handle all non-access layer informations between MME and the UE; Triggering is in the paging of SAE system.MME is the mobile management unit of SAE system.In the UMTS system, mobile management unit is SGSN (Serving GPRS Support Node, a Serving GPRS Support Node).
Gateway (Serving Gateway abbreviates SGW as) is a user entity, is responsible for the user face data route and handles, 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 of 3GPP internal system user plane, and a user can only have a SGW a moment;
Packet data network gateway (PDN Gateway abbreviates PGW as) is responsible for the gateway that UE inserts PDN, and distributing user IP address is the mobility anchor point of 3GPP and non-3GPP connecting system simultaneously, and the function of PGW comprises that also strategy is implemented, charging is supported.The user can insert a plurality of PGW at synchronization.PCEF (Policy and ChargingEnforcement Function, the strategy and the enforcement functional entity that charges) also is arranged in PGW.
Strategy is responsible for to PCEF policy control and charging regulation being provided with charging regulation function entity (Policy and Charging Rules Function abbreviates PCRF as).
Home subscriber server (Home Subscriber Server; Abbreviate HSS as) the permanent storage user contracting data; The content of HSS storage comprises the IMSI (InternationalMobile Subscriber Identification, international mobile subscriber identity) of UE, the IP address of PGW.
Physically, SGW and PGW possibly unify.EPC system user veil unit comprises SGW and PGW.
Interface-free resources and economize on electricity in order to save the user need be converted into idle condition from connection status with UE, and this process is called the S1 release flow in the E-UTRAN system, in the GPRS process, are called the Iu release flow.In S1 release flow process; When release cause is because when " user's inertia "; User's assurance bit rate (Guaranteed Bit Rate abbreviates GBR as) carries to carry with non GBR (non-ensured bit rate) and all keeps, still when release cause be during owing to other reason; Mobile management entity only keeps non GBR and carries, and GBR carries and need initiated to discharge by MME.The S1 dispose procedure is as shown in Figure 2, may further comprise the steps:
Step 201, eNodeB detects the context that needs to discharge UE, and eNodeB sends the UE context to MME and discharges request message, carries the release cause value in this message;
Step 202, MME sends to SGW and discharges the access bearer request message, address and the Tunnel End Point Identifier (Tunnel EndpointIDentifier abbreviates TEID as) of the eNodeB that request SGW deletion is stored;
Step 203, SGW deletes address and the TEID of the eNodeB that is stored, and returns release access bearer response message to MME.
Step 204, MME sends UE context release order message to eNodeB.
Step 205 also is not released if user's radio bearer connects (Radio ResourceConnection abbreviates RRC as), and eNodeB sends RRC to UE and connects the release request message.
Step 206, UE returns RRC connection release response message to eNodeB.
Step 207, eNodeB returns UE context Release complete to MME.
Step 208, decision discharges the GBR carrying to MME according to the release cause value in the step 201; If the release cause in the step 201 is " user's inertia ", MME does not initiate GBR and carries dispose procedure, but when the release cause in the step 201 was other reason, MME initiated GBR and carries release flow.
In view of PCRF can be with some IP Multimedia System (IP Multimediasub-System; Abbreviating IMS as) speech business is mapped in the non GBR carrying; In order to make the operation layer charging accurately, PCRF can need in newly-built carrying or bearing modification process through PGW, and whether SGW indication MME need discharge this part nonGBR carrying in S1 release process; As shown in Figure 3, may further comprise the steps:
Step 301, PCRF sends the PCC strategy to PGW.
Step 302, PGW sends to carry to SGW and sets up request message, carries in this message and carries QoS (Quality of Service; Service quality), bearer service flow template (TrafficFlow Template abbreviates TFT as); User plane address and the TEID of PGW, charging identifier is if be mapped to the IMS voice bearer in the non GBR carrying in addition; Also need carry the releasing bearing indication, be used in reference to be shown in the S1 dispose procedure and this nonGBR is carried initiation carrying dispose procedure by MME.
Step 303, SGW sends to carry to MME and sets up request message, carries in this message and carries QoS, carries TFT, user plane address and the TEID of SGW, charging identifier, releasing bearing indication.
Step 304, MME distributes a bearing identification for this carries, and sets up the session management request, comprises in the session management request carrying QoS, and bearing identification carries TFT; MME sends to carry to eNodeB and sets up request message, carries the session management request in this message, carries QoS, bearing identification, user plane address and the TEID of SGW.
Step 305, eNodeB sends RRC to UE and connects reconfiguration message, carries radio bearer QoS in this message, session management request, radio bearer sign.
Step 306, UE sends the RRC connection to eNodeB and reshuffles completion message.
Step 307, eNodeB sends to carry to MME and sets up response message, carries user plane address and the TEID of eNodeB.
Step 308, UE Non-Access Stratum are set up session and are set up response, and pass to eNodeB through direct-sending message.
Step 309, eNodeB sets up response pass to MME through up direct-sending message with session.
Step 310; MME replys to carry to SGW and sets up response message; Comprise bearing identification in the message, user plane address and the TEID of eNodeB need carry the releasing bearing indication simultaneously; This releasing bearing indication can make SGW, and PGW knows whether MME is supported in release non GBR bearing function in the S1 dispose procedure.
Step 311; SGW replys to carry to PGW and sets up response message, comprises bearing identification in the message, user plane address and the TEID of SGW; Need carry the releasing bearing indication simultaneously, this releasing bearing indication can make PGW know whether MME is supported in release non GBR bearing function in the S1 dispose procedure;
Step 312, PGW sends the success of IP session modification to PCRF.
If but UE is owing to move into new mobile management unit overlay area; After new mobile management unit carries out the S1/Iu dispose procedure; Can't determine whether that needing to initiate nonGBR carries release flow; Because PCRF can be mapped to some IMS speech business in the nonGBR carrying; For operation layer is chargeed accurately, whether PCRF can need need discharge this part non GBR carrying in the S1/Iu dispose procedure through PGW, SGW indication mobile management unit in newly-built carrying or bearing modification process, and coarse problem of chargeing can appear in S1/Iu release back operation layer like this.
Summary of the invention
Main purpose of the present invention is to provide a kind of carrying method for releasing and system; Move to new mobile management unit to solve above-mentioned UE; And after new mobile management unit carries out the S1/Iu dispose procedure; Can't determine whether that needing to initiate non GBR carries release flow, coarse problem of chargeing can appear in operation layer thereby the S1/Iu that causes discharges the back.
To achieve these goals, according to an aspect of the present invention, a kind of carrying method for releasing is provided.
Carrying method for releasing according to the present invention comprises: when user equipment (UE) after first mobile management unit moves to second mobile management unit, second mobile management unit obtains releasing bearing sign from first mobile management unit; Second mobile management unit determines whether in the S1/Iu dispose procedure, to carry out non-ensured bit rate non GBR according to the releasing bearing sign and carries release.
Further; Second mobile management unit obtains the releasing bearing sign from first mobile management unit before; Also comprise: the carrying of UE under first mobile management unit set up or the process of bearing modification in, first mobile management unit obtains the releasing bearing sign from the message that strategy and charging regulation function entity PCRF or packet data gateway PGW send.
Further, second mobile management unit obtains releasing bearing sign from first mobile management unit and comprises: second mobile management unit with the context transfer of tracing section updating TAU, routing area updating RAU or the handoff procedure of first mobile management unit obtain the releasing bearing sign.
Further; Second mobile management unit obtained the releasing bearing sign from first mobile management unit after, also comprise: second mobile management unit was selected new gateway, and sent carrying to new gateway and set up message; Wherein, carrying is set up message and is carried the releasing bearing mark; New gateway sends bearing modification message to packet service gateway PGW, and wherein, bearing modification message is carried the releasing bearing sign.
Further; Second mobile management unit obtains the releasing bearing sign from first mobile management unit after; Also comprise: if stored the releasing bearing sign in the bearer context in the gateway; And the bearing modification message that second mobile management unit sends to gateway is delivered to and does not carry the releasing bearing sign, and then gateway is confirmed that second mobile management unit is not supported in and carried out non GBR in the S1/Iu dispose procedure and carry and discharge; Gateway notice PGW second mobile management unit is not supported in and carries out non GBR carrying release in the S1/Iu dispose procedure.
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), first mobile management unit, second mobile management unit; Wherein, Second mobile management unit comprises: acquisition module; Be used at UE after first mobile management unit moves to second mobile management unit, obtain the releasing bearing sign from first mobile management unit; First determination module is used for determining whether that according to the releasing bearing sign carrying out non GBR at the S1/Iu dispose procedure carries release.
Further; First mobile management unit is used for setting up the perhaps process of bearing modification in the carrying of UE under first mobile management unit, from the message of strategy and charging regulation function entity PCRF or packet data gateway PGW transmission, obtains the releasing bearing sign.
Further, acquisition module is used for obtaining the releasing bearing sign with the context transfer of tracing section updating TAU, routing area updating RAU or the handoff procedure of first mobile management unit.
Further, the second mobile management unit module also comprises: select module, be used to select new gateway; First sending module is used for sending carrying to new gateway and sets up message, and wherein, carrying is set up message and carried the releasing bearing mark; Carrying delivery system also comprises: gateway, and wherein, gateway comprises: second sending module, be used for sending bearing modification message from first sending module to packet service gateway PGW, wherein, bearing modification message is carried the releasing bearing sign.
Further; Said system also comprises gateway; Wherein, gateway comprises: second determination module is used in the bearer context of gateway, having stored the releasing bearing sign; And when second mobile management unit did not carry the releasing bearing sign in the bearing modification message that gateway sends, confirming that second mobile management unit is not supported in carried out non GBR and carries and discharge in the S1/Iu dispose procedure; Notification module is used for confirming that at second determination module second mobile management unit is not supported in the S1/Iu dispose procedure and carries out non GBR when carry discharging, and notice PGW second mobile management unit is not supported in and carries out non GBR in the S1/Iu dispose procedure and carry and discharge.
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.
Through the present invention, adopt when user equipment (UE) after first mobile management unit moves to second mobile management unit, second mobile management unit obtains releasing bearing from first mobile management unit and identifies; Second mobile management unit determines whether in S 1/Iu dispose procedure, to carry out non-ensured bit rate non GBR according to the releasing bearing sign and carries release; Solve above-mentioned UE and moved to new mobile management unit; And after new mobile management unit carries out the S1/Iu dispose procedure; Can't determine whether that needing to initiate non GBR carries release flow, coarse problem of chargeing can occur thereby cause S1/Iu to discharge the back operation layer, and then reach the effect that improves the operation layer billing accuracy.
Description of drawings
Accompanying drawing described herein is used to provide further understanding of the present invention, constitutes the application's a part, and illustrative examples of the present invention and explanation thereof are used to explain the present invention, do not constitute improper qualification of the present invention.In the accompanying drawings:
Fig. 1 is the sketch map according to the evolution packet network system configuration of correlation technique;
Fig. 2 is the signaling process figure according to the S1 release of correlation technique;
Fig. 3 is the signaling process figure that sets up according to the carrying of correlation technique;
Fig. 4 is the flow chart according to the carrying method for releasing of the embodiment of the invention;
Fig. 5 is the flow chart that the UE according to the embodiment of the invention moves to the carrying method for releasing that new MME and SGW do not change;
Fig. 6 is that the UE according to the embodiment of the invention moves to the flow chart that new MME and new MME select the carrying method for releasing of new SGW;
Fig. 7 is the switch flow chart of the carrying method for releasing that moves to new MME of the UE according to the embodiment of the invention;
Fig. 8 is the structured flowchart according to the carrying delivery system of the embodiment of the invention; And
Fig. 9 is the preferred construction block diagram according to the carrying delivery system of the embodiment of the invention.
Embodiment
Hereinafter will and combine embodiment to specify the present invention with reference to accompanying drawing.Need to prove that under the situation of not conflicting, embodiment and the characteristic among the embodiment among the application can make up each other.
Present embodiment provides a kind of carrying method for releasing, and Fig. 4 is the flow chart according to the carrying method for releasing of the embodiment of the invention, and is as shown in Figure 4, and this method comprises:
Step S402, when UE after first mobile management unit moves to second mobile management unit, second mobile management unit obtains releasing bearing sign from first mobile management unit.
Step S404, second mobile management unit determines whether in the S1/Iu dispose procedure, to carry out non-ensured bit rate (non GBR) according to the releasing bearing sign and carries release.
Pass through above-mentioned steps; At UE after first mobile management unit moves to second mobile management unit; Second mobile management unit obtains the releasing bearing sign from first mobile management unit, and determines whether in the S1/Iu dispose procedure, to carry out non GBR carrying release according to above-mentioned sign, has avoided in the correlation technique; UE is owing to move into new mobile management unit overlay area; And after new mobile management unit carries out the S1/Iu dispose procedure, can't determine whether that needing to initiate non GBR carries release flow, because PCRF can be mapped to some IMS speech business in the non GBR carrying; For operation layer is chargeed accurately; Whether PCRF can need need discharge this part non GBR carrying in the S1/Iu dispose procedure through PGW, SGW indication mobile management unit in newly-built carrying or bearing modification process, and coarse problem of chargeing can appear in operation layer after S1/Iu discharged like this, had improved the accuracy that operation layer charges.
Preferably; Before step S402; Said method also comprises: the carrying of UE under first mobile management unit set up or the process of bearing modification in, first mobile management unit obtains the releasing bearing sign from the message that strategy and charging regulation function entity PCRF or packet data gateway PGW send.Through this preferred embodiment, realized that first mobile management unit obtains the releasing bearing sign.
Some that obtain the releasing bearing sign from first mobile management unit in the face of second mobile management unit among the step S404 down preferred embodiment describe.Second mobile management unit with tracing section updating (the Tracking Area Update of first mobile management unit; Abbreviate TAU as), obtain the releasing bearing sign in the context transfer of Routing Area Update (Routing Area Update abbreviates RAU as) or handoff procedure.Through the obtaining step of this preferred embodiment, realized that second mobile management unit obtains the releasing bearing sign under multiple situation, improved flexibility and the applicability of obtaining the bearing identification method.
Preferably, after step S402, said method also comprises: second mobile management unit is selected new gateway, and sends carrying to new gateway and set up message, and wherein, carrying is set up message and carried the releasing bearing mark; New gateway sends bearing modification message to packet service gateway (PGW), and wherein, bearing modification message is carried the releasing bearing sign.Through this preferred embodiment, to have realized selecting under the new gateway situation at second mobile management unit, new gateway and packet service gateway obtain the releasing bearing sign.
Preferably; After step S402; Said method also comprises: if stored the releasing bearing sign in the bearer context in the gateway; And the bearing modification message that second mobile management unit sends to gateway is not carried the releasing bearing sign, and then gateway is confirmed that second mobile management unit is not supported in the S1/Iu dispose procedure and carried release; Gateway notice PGW second mobile management unit is not supported in the S1/Iu dispose procedure and carries release.This preferred embodiment has realized in the service gateway bearing context, having stored the releasing bearing sign; And this sign is not delivered to gateway by second mobile management unit, and then this gateway is confirmed that second mobile management unit is not supported to carry in the S1/Iu dispose procedure and discharged and give PGW with this context notification.
Preferably, mobile management unit comprises one of following: MME, SGSN.Through the preferred embodiment, realized the applicability that the releasing bearing method is used.
Preferably, releasing bearing is designated an independent information unit.Through the preferred embodiment, the releasing bearing sign implements fairly simple, and overhead is smaller.
Embodiment one
Present embodiment has combined the foregoing description and preferred implementation wherein; Present embodiment provides a kind of method of releasing bearing; Fig. 5 is the flow chart that the UE according to the embodiment of the invention moves to the carrying method for releasing that new MME and SGW do not change, and as shown in Figure 5, this method comprises:
Step 501, UE moves to the E-UTRAN area of coverage under the MME, in the tracing section updating request message that sends to MME, except carry the GUTI that UE distributes under old MME, also will carry the ability whether UE supports ISR.
Step 502, new MME finds old MME according to the GUTI sign, sends the context request signaling and carries out the context acquisition process.
Step 503, old MME sends to new MME with user's mobile management and beared information, and in the context response information of returning, carries and whether need trigger the mark that non GBR carry to discharge in the S1/Iu dispose procedure and pass to new MME.
Preferably; This mark can be used an independent information unit (InformationElement; Abbreviate IE as) represent; In carrying foundation or bearer update process, whether need non GBR be carried the indication that discharges in the S1 dispose procedure that MME record PCRF/PGW sends over, so that release flow is carried in triggering in the process that S1 discharges; Old MME need be passed to new MME with above-mentioned mark, and old MME can unmarkedly notify new MME whether need trigger the carrying release flow with having; Old MME also can use " 1 " among the IE to indicate new MME need trigger the carrying release flow, representes that with " 0 " new MME need not trigger the carrying release flow.
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; Carry source GTP-C Tunnel Identifier and purpose GTP-C Tunnel Identifier in the request message; SGW is the binding relationship of new bearer more, and whether the positional information of UE, this message also need carry self to be supported in and trigger non GBR carrying dispose procedure in the S1 dispose procedure.
Step 506, SGW sends more new bearer request to PGW, carries the positional information of UE in the request message; Do not carry dispose procedure if new MME does not support to trigger in the S1 dispose procedure non GBR, SGW need upgrade at this and notify PGW in 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 the new bearer response to new MME, brings MME with the purpose GTP-C Tunnel Identifier of SGW appointment, self address and the tunnel information etc. of address and PGW.
Step 509, new MME is through the change of location update message notice HSS position.
Step 510, HSS sends the canceling position signaling to old MME.
Step 511, old MME is to HSS home position cancellation response.
Step 512, HSS upgrades the position of new MME and confirms, and user contracting data is passed to new MME.
Step 513, effective in current tracking area if new MME confirms UE, then send tracing section updating and accept message to UE.
Step 514, if new MME is that UE has distributed a new GUTI sign through the TAU flow process, UE can returning tracking district renewal completion message confirm to MME so.
Need to prove, be that to move to new MME overlay area with UE be example explanation in the present embodiment; Move to new SGSN for UE, processing method is similar with it, repeats no more at this.
Embodiment two
Present embodiment has combined the foregoing description and preferred implementation wherein; Present embodiment provides a kind of method of releasing bearing; Fig. 6 is that the UE according to the embodiment of the invention moves to the flow chart that new MME and new MME select the carrying method for releasing of new SGW, and as shown in Figure 6, this method comprises:
Step 601, UE moves to the E-UTRAN area of coverage under the MME, in the tracing section updating request message that sends to MME, except carry the GUTI that UE distributes under old MME, also will carry the ability whether UE supports ISR.
Step 602, new MME finds old MME according to the GUTI sign, sends the context request signaling and carries out the context acquisition process.
Step 603, old MME sends to new MME with user's mobile management and beared information, and in the context response information of returning, carries and whether need trigger the mark that non GBR carry to discharge in the S1/Iu dispose procedure and pass to new MME.
Preferably; This mark can be represented with an IE; In carrying foundation or bearer update process, whether need non GBR be carried the indication that discharges in the S1 dispose procedure that MME record PCRF/PGW sends over, so that release flow is carried in triggering in the process that S1 discharges; Old MME need be passed to new MME with above-mentioned mark, and old MME can unmarkedly notify new MME whether need trigger the carrying release flow with having; Old MME also can use " 1 " among the IE to indicate new MME need trigger the carrying release flow, representes that with " 0 " new MME need not trigger the carrying release flow; Old MME also can use " 0 " among the IE to indicate new MME need trigger the carrying release flow, representes that with " 1 " new MME need not trigger the carrying release flow.
Step 604, new MME replys context acknowledgement message to old MME.
Step 605; New MME sets up request to new SGW initiation session; Carry source GTP-C Tunnel Identifier and purpose GTP-C Tunnel Identifier in the request message; SGW control plane address and TEID, whether the positional information of UE, this message also need carry self to be supported in and trigger non GBR carrying dispose procedure in the S1 dispose procedure.
Step 606, SGW sends more new bearer request to PGW, carries the positional information of UE in the request message; Whether this message also need carry self to be supported in MME and trigger non GBR carrying dispose procedure in the S1 dispose procedure.
Step 607, PGW upgrades the context of oneself and returns more new bearer response message to SGW.
Step 608, SGW returns session to new MME and sets up response, brings MME with the purpose GTP-C Tunnel Identifier of SGW appointment, self address and the tunnel information etc. of address and PGW.
Step 609, new MME is through the change of location update message notice HSS position.
Step 610, HSS sends the canceling position signaling to old MME.
Step 611, old MME is to HSS home position cancellation response.
Step 612, HSS upgrades the position of new MME and confirms, and user contracting data is passed to new MME.
Step 613, effective in current tracking area if new MME confirms UE, then send tracing section updating and accept message to UE.
Step 614, if new MME is that UE has distributed a new GUTI sign through the TAU flow process, UE can returning tracking district renewal completion message confirm to MME so.
Step 615, old MME sends to old SGW and discharges conversation request message, notice SGW deletion user's context.
Step 616, old SGW returns to old MME and discharges conversational response message.
Need to prove, be that to move to new MME overlay area with UE be example explanation in the present embodiment; Move to new SGSN for UE, processing method is similar with it, repeats no more at this.
Embodiment three
Present embodiment has combined the foregoing description and preferred implementation wherein; Present embodiment provides a kind of method of releasing bearing; Fig. 7 is the switch flow chart of the carrying method for releasing that moves to new MME of the UE according to the embodiment of the invention, and as shown in Figure 7, this method comprises:
Step 701, former eNodeB determines the switching to new eNodeB initiates between eNodeB, core net node heavily distributes.
Step 702, former eNodeB sends handoff request message to old MME.
Step 703, old MME selects new MME according to the MME selection function, and to the heavy allocation request message of new MME sending node, comprises address and the up TEID of PGW in this message, the address of SGW and up TEID; And in message, carry and whether need trigger the mark that non GBR carry to discharge in the S1/Iu dispose procedure and pass to new MME;
Preferably; This mark can be represented with an independent information unit IE; In carrying foundation or bearer update process; Whether need non GBR be carried the indication that discharges in the S1 dispose procedure that MME record PCRF/PGW sends over, carry release flow so that in the process that S1 discharges, trigger; Old MME need be passed to new MME with above-mentioned mark, and old MME can unmarkedly notify new MME whether need trigger the carrying release flow with having; Old MME also can use " 1 " among the IE to indicate new MME need trigger the carrying release flow, representes that with " 0 " new MME need not trigger the carrying release flow; Old MME also can use " 0 " among the IE to indicate new MME need trigger the carrying release flow, representes that with " 1 " new MME need not trigger the carrying release flow.
Step 704, new MME sends session to SGW and sets up request message, carries in the request message, and QoS etc. is carried in the GTP-C Tunnel Identifier of PGW and IP address; Whether this message also need carry self to be supported in and trigger non GBR carrying dispose procedure in the S1 dispose procedure.
Step 705, SGW returns session to MME and sets up response message, carries the GTP-C Tunnel Identifier of SGW and the address of self in the response message.
Step 706, new MME sends handoff request message to new eNodeB, and request is set up the UE context in new eNodeB.
Step 707, new eNodeB sends switching request acknowledgement message to new MME.
Step 708, new MME is to the heavy assignment response message of old MME sending node.
Step 709, old MME sends switch indicating information to former eNodeB.
Step 710, former eNodeB is forwarded to UE with switch indicating information.
Step 711, UE sends switch acknowledgment message to new eNodeB after carrying out cell synchronizing with new eNodeB.
Step 712, new eNodeB sends handoff notification message to new MME.
Step 713, the message that new MME has heavily assigned to old MME sending node.
Step 714, the affirmation message that old MME has heavily assigned to new MME return node.
Step 715, new MME carries user plane Tunnel Identifier and the IP address of new eNodeB to the request of SGW starting update load bearing in the request message.
Step 716, SGW sends more new bearer request to PGW, and the parameters such as positional information of the address information of SGW, tunnel identification information, UE are sent to PGW; Whether this message also need carry self to be supported in MME and trigger non GBR carrying dispose procedure in the S1 dispose procedure.
Step 717, PGW upgrades the context of self, and returns the renewal bearing response message to SGW.
Step 718, SGW returns the renewal bearing response message to new MME.
Present embodiment provides a kind of carrying delivery system; Fig. 8 is the structured flowchart according to the carrying delivery system of the embodiment of the invention; As shown in Figure 8, this system comprises: UE 82, first mobile management unit 84, second mobile management unit 86, wherein; Second mobile management unit comprises: the acquisition module 862 and first determination module 864 are described in detail in the face of said structure down.
Acquisition module 862 is used for UE after first mobile management unit moves to second mobile management unit, obtains the releasing bearing sign from first mobile management unit; Preferably, acquisition module 862 is used for obtaining the releasing bearing sign with the context transfer of TAU, RAU or the handoff procedure of first mobile management unit;
First determination module 864 is connected to acquisition module 862, and the releasing bearing sign that is used for obtaining according to acquisition module 862 determines whether that carrying out non-ensured bit rate non GBR at the S1/Iu dispose procedure carries release;
First mobile management unit 84 is used for setting up the perhaps process of bearing modification in the carrying of UE under first mobile management unit, from the message of strategy and charging regulation function entity PCRF or packet data gateway PGW transmission, obtains the releasing bearing sign.
Fig. 9 is the preferred construction block diagram according to the carrying delivery system of the embodiment of the invention; The 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: second sending module 882, second determination module 884 and notification module 886 are elaborated in the face of said structure down:
The second mobile management module 86 comprises: select module 866, be used to select new gateway; First sending module 868 is connected to selection module 866, is used for sending carrying to the new gateway of selecting module 866 to select and sets up message, and wherein, carrying is set up message and carried the releasing bearing mark;
Gateway 88 comprises: second sending module 882, be used for sending bearing modification message from first sending module to packet service gateway PGW, and wherein, bearing modification message is carried the releasing bearing sign; Second determination module 884; Be used in the bearer context of gateway, having stored the releasing bearing sign; And second mobile management unit does not carry releasing bearing when sign to the bearing modification message of its transmission, confirms that second mobile management unit is not supported in the S1/Iu dispose procedure to carry release; Notification module 886; Be connected to second determination module 884; Be used for confirming that at second determination module 884 second mobile management units are not supported in the S1/Iu dispose procedure and carry when discharging, notice PGW second mobile management unit is not supported in the S1/Iu dispose procedure and carries release.
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 the foregoing description; At UE after first mobile management unit moves to second mobile management unit; Second mobile management unit obtains the releasing bearing sign from first mobile management unit, and determines whether in the S1/Iu dispose procedure, to carry out non GBR carrying release according to above-mentioned sign, has avoided in the correlation technique; UE is owing to move into new mobile management unit overlay area; And after new mobile management unit carries out the S1/Iu dispose procedure, can't determine whether that needing to initiate non GBR carries release flow, because PCRF can be mapped to some IMS speech business in the non GBR carrying; For operation layer is chargeed accurately; Whether PCRF can need need discharge this part non GBR carrying in the S1/Iu dispose procedure through PGW, SGW indication mobile management unit in newly-built carrying or bearing modification process, and coarse problem of chargeing can appear in operation layer after S1/Iu discharged like this, had improved the accuracy that operation layer charges.
Obviously, it is apparent to those skilled in the art that above-mentioned each module of the present invention or each step can realize with the general calculation device; They can concentrate on the single calculation element; Perhaps be distributed on the network that a plurality of calculation element forms, alternatively, they can be realized with the executable program code of calculation element; Thereby; Can they be stored in the storage device and carry out, and in some cases, can carry out step shown or that describe with the order that is different from here by calculation element; Perhaps they are made into each integrated circuit modules respectively, perhaps a plurality of modules in them or step are made into the single integrated circuit module and realize.Like this, the present invention is not restricted to any specific hardware and software combination.
The above is merely the preferred embodiments of the present invention, is not limited to the present invention, and for a person skilled in the art, the present invention can have various changes and variation.All within spirit of the present invention and principle, any modification of being done, be equal to replacement, improvement etc., all should be included within protection scope of the present invention.
Claims (14)
1. one kind carries method for releasing, it is characterized in that, comprising:
When user equipment (UE) after first mobile management unit moves to second mobile management unit, said second mobile management unit obtains releasing bearing sign from said first mobile management unit;
Said second mobile management unit determines whether in the S1/Iu dispose procedure, to carry out non-ensured bit rate non GBR according to said releasing bearing sign and carries release.
2. method according to claim 1 is characterized in that, said second mobile management unit obtains the releasing bearing sign from said first mobile management unit before, also comprises:
The carrying of said UE under said first mobile management unit set up or the process of bearing modification in, said first mobile management unit obtains said releasing bearing sign from the message that strategy and charging regulation function entity PCRF or packet data gateway PGW send.
3. method according to claim 1 is characterized in that, said second mobile management unit obtains the releasing bearing sign from said first mobile management unit and comprises:
Said second mobile management unit with the context transfer of tracing section updating TAU, routing area updating RAU or the handoff procedure of said first mobile management unit in obtain said releasing bearing sign.
4. method according to claim 1 is characterized in that, said second mobile management unit obtains the releasing bearing sign from said first mobile management unit after, also comprises:
Said second mobile management unit is selected new gateway, and sends carrying to said new gateway and set up message, and wherein, said carrying is set up message and carried said releasing bearing mark;
Said new gateway sends bearing modification message to packet service gateway PGW, and wherein, said bearing modification message is carried said releasing bearing sign.
5. method according to claim 1 is characterized in that, said second mobile management unit obtains the releasing bearing sign from said first mobile management unit after, also comprises:
If stored said releasing bearing sign in the bearer context in the gateway; And the bearing modification message that said second mobile management unit sends to said gateway is delivered to and does not carry said releasing bearing sign, and then said gateway is confirmed that said second mobile management unit is not supported in and carried out nonGBR in the S1/Iu dispose procedure and carry and discharge;
Said second mobile management unit of said gateway notice PGW is not supported in and carries out non GBR carrying release in the S1/Iu dispose procedure.
6. according to each described method of claim 1-5, it is characterized in that,
It is one of following that said mobile management unit comprises: mobile management entity MME, service universal grouping wireless business supporting node SGSN.
7. according to each described method of claim 1-5, it is characterized in that,
Said releasing bearing is designated an independent information unit.
8. one kind carries delivery system, it is characterized in that, comprising: user equipment (UE), first mobile management unit, second mobile management unit,
Wherein, said second mobile management unit comprises:
Acquisition module is used at said UE after said first mobile management unit moves to said second mobile management unit, obtains the releasing bearing sign from said first mobile management unit;
First determination module is used for determining whether that according to said releasing bearing sign carrying out non GBR at the S1/Iu dispose procedure carries release.
9. carrying delivery system according to claim 8 is characterized in that,
Said first mobile management unit is used for setting up the perhaps process of bearing modification in the carrying of said UE under said first mobile management unit, from the message of strategy and charging regulation function entity PCRF or packet data gateway PGW transmission, obtains said releasing bearing sign.
10. carrying delivery system according to claim 8 is characterized in that,
Said acquisition module is used for obtaining said releasing bearing sign with the context transfer of tracing section updating TAU, routing area updating RAU or the handoff procedure of said first mobile management unit.
11. carrying delivery system according to claim 8 is characterized in that,
The said second mobile management unit module also comprises:
Select module, be used to select new gateway;
First sending module is used for sending carrying to said new gateway and sets up message, and wherein, said carrying is set up message and carried said releasing bearing mark;
Said carrying delivery system also comprises: gateway, and wherein, said gateway comprises:
Second sending module is used for sending the bearing modification message from said first sending module to packet service gateway PGW, and wherein, said bearing modification message is carried said releasing bearing sign.
12. carrying delivery system according to claim 8 is characterized in that, also comprises gateway, wherein, said gateway comprises:
Second determination module; Be used in the bearer context of gateway, having stored said releasing bearing sign; And when said second mobile management unit did not carry said releasing bearing sign in the bearing modification message that said gateway sends, confirming that said second mobile management unit is not supported in carried out non GBR and carries and discharge in the S1/Iu dispose procedure;
Notification module; Be used for confirming that at said second determination module said second mobile management unit is not supported in the S1/Iu dispose procedure and carries out non GBR when carry discharging that said second mobile management unit of notice PGW is not supported in and carries out non GBR in the S1/Iu dispose procedure and carry and discharge.
13. each described carrying delivery system is characterized in that according to Claim 8-12,
It is one of following that said mobile management unit comprises: mobile management entity MME, Serving GPRS Support Node SGSN.
14. each described carrying delivery system is characterized in that according to Claim 8-12, said releasing bearing is designated an independent information unit.
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 true CN102378295A (en) | 2012-03-14 |
CN102378295B 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) |
Cited By (7)
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 |
CN107889176A (en) * | 2013-10-31 | 2018-04-06 | 英特尔Ip公司 | The gateway arrangement of cordless communication network |
WO2018201973A1 (en) * | 2017-05-03 | 2018-11-08 | 华为技术有限公司 | Method and apparatus for message transmission |
CN108810988A (en) * | 2017-05-03 | 2018-11-13 | 华为技术有限公司 | A kind of method and device of message transmission |
CN109076496A (en) * | 2016-05-03 | 2018-12-21 | 株式会社Kt | For changing the method and apparatus of terminal connection status |
CN109257788A (en) * | 2017-07-14 | 2019-01-22 | 华为技术有限公司 | Method for switching network and device |
US10939345B2 (en) | 2017-07-14 | 2021-03-02 | Huawei Technologies Co., Ltd. | Network handover method and network device |
Families Citing this family (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
GB2547028B (en) * | 2016-02-05 | 2021-06-16 | Tcl Communication Ltd | Early connection release |
Citations (1)
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)
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 |
-
2010
- 2010-08-23 CN CN201010267090.2A patent/CN102378295B/en not_active Expired - Fee Related
-
2011
- 2011-07-14 WO PCT/CN2011/077164 patent/WO2012024989A1/en active Application Filing
Patent Citations (1)
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 |
Non-Patent Citations (1)
Title |
---|
3GPP GROUP: "《3GPP TS 23.401 V8.10.0》", 30 June 2010 * |
Cited By (11)
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 |
CN107889176A (en) * | 2013-10-31 | 2018-04-06 | 英特尔Ip公司 | The gateway arrangement of cordless communication network |
US11917701B2 (en) | 2013-10-31 | 2024-02-27 | Apple Inc. | Gateway arrangements for wireless communication networks |
CN109076496A (en) * | 2016-05-03 | 2018-12-21 | 株式会社Kt | For changing the method and apparatus of terminal connection status |
WO2018201973A1 (en) * | 2017-05-03 | 2018-11-08 | 华为技术有限公司 | Method and apparatus for message transmission |
CN108810988A (en) * | 2017-05-03 | 2018-11-13 | 华为技术有限公司 | A kind of method and device of message transmission |
CN108810988B (en) * | 2017-05-03 | 2020-12-01 | 华为技术有限公司 | Message transmission method and device |
CN109257788A (en) * | 2017-07-14 | 2019-01-22 | 华为技术有限公司 | Method for switching network and device |
US10939345B2 (en) | 2017-07-14 | 2021-03-02 | Huawei Technologies Co., Ltd. | Network handover method and network device |
CN109257788B (en) * | 2017-07-14 | 2021-06-22 | 华为技术有限公司 | Network switching method and device |
US11323933B2 (en) | 2017-07-14 | 2022-05-03 | Huawei Technologies Co., Ltd. | Network handover method and network device |
Also Published As
Publication number | Publication date |
---|---|
WO2012024989A1 (en) | 2012-03-01 |
CN102378295B (en) | 2016-01-20 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US9713042B2 (en) | Method and system for notifying attribute of IP address and SGW | |
CN101459907B (en) | Method for indicating service gateway bearing management | |
EP2515560B1 (en) | Method and system for synchronizing user data | |
CN101282511B (en) | Bearing processing method | |
CN102378295B (en) | Resource release method and system | |
CN102595373A (en) | Method and system capable of achieving mobile management to MTC terminals | |
CN101572862B (en) | Method and equipment for supporting intercommunication between 3G system and LTE system | |
CN101959175A (en) | Realization method and system for establishing local IP (Internal Protocol) access connection | |
CN101730073B (en) | Method and system for acquiring user contracting data | |
CN101730193B (en) | Method and system for selecting gateway node | |
CN101577970B (en) | Method for releasing wireless resources | |
CN101448209B (en) | Notification method of location information of user equipment of evolved packet system and system thereof | |
CN102014434B (en) | Load re-distribution method and system for service gateway | |
CN102088795A (en) | SIPTO (Selected IP Traffic Offload) realization method and mobility management control node device | |
CN101448328B (en) | Method for establishing default bearing | |
CN101959209B (en) | Synchronization method and system for partial failure handling | |
CN102014370B (en) | Method and system for selecting IWP (Inter Working Proxy) | |
CN102065503A (en) | Service gateway selection system and method | |
CN101203027A (en) | System for selecting supervision node in mobile communication system | |
CN104144398B (en) | A kind of realization method and system of callee function, HSS, SCC AS | |
CN102625411B (en) | User's method for releasing of a kind of network element overload and system | |
CN101959275A (en) | Informing method and device for determining service gateway and topological relation for user terminal | |
CN101203028A (en) | Method for searching of mobile communication 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 | ||
CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20160120 Termination date: 20190823 |