CN101472350A

CN101472350A - Method, system and node for implementing load bearing deactivation of mobile communication system

Info

Publication number: CN101472350A
Application number: CNA2007100329004A
Authority: CN
Inventors: 陈喆; 周进怡; 刘岚; 于琦
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2007-12-27
Filing date: 2007-12-27
Publication date: 2009-07-01
Anticipated expiration: 2027-12-27
Also published as: CN101472350B; WO2009082952A1

Abstract

The embodiment of the invention discloses a method of bearing deactivation in a mobile communication system. The method comprises the following steps: receiving bearing deactivation requests, instructions of bearing types for the bearing deactivation are included in the bearing deactivation requests; the bearing types for the bearing deactivation are determined; and the corresponding bearing deactivation is performed to the bearing which needs the bearing deactivation according to the bearing types. The embodiment of the invention further discloses a network node, which comprises a receiving unit used for receiving the bearing deactivation requests of the network node transmitted in which the instructions of the bearing types for the bearing deactivation are included; a determining unit used for determining the bearing types for the bearing deactivation; and a deactivating unit used for the bearing deactivation according to the bearing types determined in the confirming unit. The embodiment of the invention further discloses a network node and a system, thereby realizing the process of respectively deleting special bearing and default bearing.

Description

A kind of method and system, node of realizing load bearing deactivation of mobile communication system

Technical field

The present invention relates to the mobile communications network field, relate in particular to a kind of method and system, network node of load bearing deactivation.

Background technology

Universal mobile telecommunications system (UMTS) is to adopt the 3-G (Generation Three mobile communication system) of broadband demal multiplex (MUX) access (WCDMA) air interface technologies, also the UMTS system is called the WCDMA communication system usually.The UMTS system comprises Radio Access Network (RAN) and core network (CN), and wherein: RAN is used for handling and wireless function associated, and voice call is connected with data in the CN processing UMTS system, and the exchange of realization and external network and routing function.

Gateway GPRS Support Node (GGSN) is as a basic Network Element Function entity, provides packet with route between the external data network and encapsulation.Serving GPRS Support Node (SGSN) is as a basic composition network element, and its significant feature is exactly the IP grouping of transmitting I/O for the travelling carriage of this SGSN coverage (MS).RAN is made up of radio network controller (RNC) and base station (NodeB).

Prior art comprises long-term evolving network (Long Term Evolved, LTE)/System Architecture Evolution network (System Architecture Evolved, SAE), the purpose of LTE provides a kind of network cheaply that can reduce time delay, raising user data rate, improved power system capacity and covering, use PS territory business, bearer network all is the IP carrying.

Following SAE evolution network framework and function thereof are described, in the packet-based core networks of evolution:

Mobility Management Entity (Mobility Management Entity, MME) function is to preserve the MM Context of UE, sign as the user, mobility management states, positional information etc., and to Non-Access Stratum (Non Access Stratum, NAS) signaling is handled, and is responsible for the safety of NAS signaling etc.

SAE GW (SAE gateway) comprise two parts gateway (Serving Gateway, SGW) and grouped data network gateway (PDN Gateway, PGW).SGW and PGW are two logic entities, may reside on the same or different physical entities.

Policy charging rule function (Policy and Charging Rules Function, PCRF) by the S7 interface to PGW as policy, billing enhancement function (Policy and Charging Enforcement Function, PCEF) delivering service quality (QoS) and charging policy control information etc.

Fig. 1 shows the structural representation of existing UMTS system and the fusion of SAE system, for existing UMTS system can be merged with the SAE system, the UMTS system must be upgraded to Release 8 versions, and therefore the fusion architecture between this system is called as R8 UMTS network.Wherein: subscriber equipment (UE) is by SGSN Access Service Network Gateway (SGW), be the UMTS system to UE this moment under the SGSN, and arrive grouped data network gateway (PGW) on the SGW is the SAE system, and UE inserts SGW by Mobility Management Entity (MME), and this moment, all nodes all belonged to the SAE system.

Because the SAE system supports UE to insert by the UMTS system, promptly UE can be linked into the SGW in the SAE system by RAN, the SGSN of UMTS system.And all there are the flow process of the relevant treatment load bearing deactivation of oneself in UMTS and SAE system, therefore need agree with at two kinds of system's boundarys (SGSN or SGW).Because the difference of default bearer and dedicated bearing is arranged in the SAE system, wherein: default bearer is article one carrying to an APN that user node is set up, and a user node can be connected to a plurality of APN, and each APN points to a PDN; Dedicated bearing is to have set up the default bearer every other carrying on this APN afterwards, and a default bearer can be corresponding to a plurality of dedicated bearings.Therefore in the load bearing deactivation flow process, need special consideration is carried out in the processing of two kinds of bearer types, in UMTS system and SAE system, the message and the parameter of carrying out deleting load-bearing are all different, load bearing deactivation in the UMTS system is all realized by PDP CONTEXT message, and be Bearer Context message in the SAE system, and in the process of R8UMTS mobile communication system bearing deletion, do not realize method at present about the deleting load-bearing of striding UMTS system and SAE system.

Summary of the invention

In view of above-mentioned existing in prior technology problem, the embodiment of the invention provides a kind of method and system, node of realizing load bearing deactivation of mobile communication system, carry out load bearing deactivation according to different bearer types, realized that the deexcitation of dedicated bearing keeps the load bearing deactivation of default bearer or all carryings.

In order to solve the problems of the technologies described above, the embodiment of the invention has proposed a kind of method that realizes load bearing deactivation of mobile communication system, and this method may further comprise the steps:

Receive the load bearing deactivation request, comprise the bearer types indication that to carry out load bearing deactivation in the described load bearing deactivation request;

Definite needs carry out the bearer types of load bearing deactivation;

According to bearer types corresponding load bearing deactivation is carried out in the carrying that needs carry out load bearing deactivation.

Accordingly, the embodiment of the invention has also proposed a kind of network node, comprising:

Receiving element is used to receive the load bearing deactivation request that sends to network node, comprises the bearer types indication that need carry out load bearing deactivation in the described load bearing deactivation request;

Determining unit is used for definite bearer types that will carry out load bearing deactivation;

The deexcitation unit is used for carrying out load bearing deactivation according to the bearer types that determining unit is determined.

Accordingly, the embodiment of the invention also provides a kind of network node, comprising:

Generation unit is used to determine to carry out the carrying of load bearing deactivation, generates the load bearing deactivation request;

Transmitting element is used for the load bearing deactivation request that generation unit generates is sent to the network decision node.

Accordingly, the embodiment of the invention has also proposed a kind of network system of load bearing deactivation of mobile communication system, and described network system comprises network requests node and network decision node, wherein:

Described network judging unit is used to receive the load bearing deactivation request that the network requests node sends, and to carry out the bearer types of load bearing deactivation in definite load bearing deactivation request, according to bearer types load bearing deactivation is carried out in the carrying that will carry out load bearing deactivation;

The network requests node is used to determine to carry out the carrying of load bearing deactivation, generates the load bearing deactivation request, and the load bearing deactivation request that generates is sent to the network decision node.

Implement the embodiment of the invention, realized the differentiation of the different network elements on the mobile communication system default bearer and dedicated bearing, and the method that the processing method of default bearer deletion or deletion dedicated bearing is kept default bearer.

Description of drawings

Fig. 1 is the structural representation that existing UMTS system and SAE system merge;

Fig. 2 is the R8 UMTS system diagram in the embodiment of the invention;

Fig. 3 is the structural representation of the SAE system in the embodiment of the invention;

Fig. 4 is the network requests node in the embodiment of the invention and the structural representation of network decision node;

Fig. 5 is the flow chart that the UE in the embodiment of the invention initiates the Detach flow process;

Fig. 6 is the first pass figure of the load bearing deactivation of the UE initiation in the embodiment of the invention;

Fig. 7 is second flow chart of the load bearing deactivation of the UE initiation in the embodiment of the invention;

Fig. 8 is the first pass figure of the Detach flow process of the SGW initiation in the embodiment of the invention;

Fig. 9 is second flow chart of the Detach flow process of the SGW initiation in the embodiment of the invention;

Figure 10 is the 3rd flow chart of the load bearing deactivation of the UE initiation in the embodiment of the invention;

Figure 11 is the 4th flow chart of the load bearing deactivation of the UE initiation in the embodiment of the invention;

Figure 12 is the 5th flow chart of the load bearing deactivation of the UE initiation in the embodiment of the invention;

Figure 13 is the first pass figure of the Detach flow process of the PGW initiation in the embodiment of the invention;

Figure 14 is second flow chart of the Detach flow process of the PGW initiation in the embodiment of the invention;

Figure 15 is the 6th flow chart of the load bearing deactivation of the UE initiation in the embodiment of the invention;

Figure 16 is the first pass figure of the load bearing deactivation of the SGSN initiation in the embodiment of the invention;

Figure 17 is second flow chart of the load bearing deactivation of the SGSN initiation in the embodiment of the invention;

Figure 18 is the 3rd flow chart of the load bearing deactivation of the SGSN initiation in the embodiment of the invention;

Figure 19 is the first pass figure of the load bearing deactivation of the PGW initiation in the embodiment of the invention;

Figure 20 is the first pass figure of the load bearing deactivation of the SGW initiation in the embodiment of the invention;

Figure 21 is the 7th flow chart of the load bearing deactivation of the UE initiation in the embodiment of the invention;

Figure 22 is the flow chart of the Detach flow process of the SGSN initiation in the embodiment of the invention;

Figure 23 is the 8th flow chart of the load bearing deactivation of the UE initiation in the embodiment of the invention;

Figure 24 is the 9th flow chart of the load bearing deactivation of the UE initiation in the embodiment of the invention;

Figure 25 is the tenth flow chart of the load bearing deactivation of the UE initiation in the embodiment of the invention;

Figure 26 is the 11 flow chart of the load bearing deactivation of the UE initiation in the embodiment of the invention;

Figure 27 is the 4th flow chart of the load bearing deactivation of the SGSN initiation in the embodiment of the invention;

Figure 28 is second flow chart of the load bearing deactivation of the PGW initiation in the embodiment of the invention;

Figure 29 is second flow chart of the load bearing deactivation of the SGW initiation in the embodiment of the invention;

Figure 30 is the 3rd flow chart of the load bearing deactivation of the PGW initiation in the embodiment of the invention;

Figure 31 is the flow chart of the load bearing deactivation of the MME initiation in the embodiment of the invention.

Embodiment

The embodiment of the invention provides a kind of method and system, node of realizing load bearing deactivation of mobile communication system, carry out load bearing deactivation according to different bearer types, realized the load bearing deactivation of dedicated bearing and keep default bearer and maybe load bearing deactivation is carried out in all carryings.

Describe the preferred embodiments of the present invention in detail below in conjunction with accompanying drawing.

At first see also Fig. 2, figure is the system diagram of the load bearing deactivation in the embodiment of the invention, the realization of this load bearing deactivation method is arranged in UMTS system and SAE system, in UMTS system and SAE system, the message of carrying out deleting load-bearing is different, and parameter wherein (among the UMTS be PDP CONTEXT and be Bearer Context in SAE) is also inconsistent, and in the process of the network deletion of R8UMTS system, should differentiating and processing to default bearer and dedicated bearing.Therefore, in the embodiment of the invention by providing two kinds of conversion plans can be so that finish smoothly at the load bearing deactivation of striding between UMTS system and the SAE system.In the deleting load-bearing that carries out the R8UMTS system, the embodiment of the invention provides the method for two kinds of message conversion, a kind of is in deleting load-bearing, and the SGW node of upstream SAE system carries out message conversion, and message transmitted is the UMTS form between SGW and SGSN; Another method is in deleting load-bearing, and the SGSN node of downstream UMTS system is responsible for carrying out message conversion, and the message format between SGW and SGSN is the message format of SAE.

Load bearing deactivation method in the embodiment of the invention can also realize in the SAE system, Fig. 3 illustrates another system diagram of the load bearing deactivation in the embodiment of the invention of knowing clearly, all provide different network elements to the differentiation of default bearer and dedicated bearing and the processing method that default bearer is deleted among above-mentioned Fig. 2 and Fig. 3, at least comprise a network requests node and a network decision node in this system diagram 2 and the system diagram 3, described network judging unit is used to receive the load bearing deactivation request that the network requests node sends, and to carry out the bearer types of load bearing deactivation in definite load bearing deactivation request, according to bearer types load bearing deactivation is carried out in the carrying that will carry out load bearing deactivation, this network requests node can be subscriber equipment in the UTMS system or SGSN; Or the subscriber equipment in the SAE system, Mobility Management Entity, gateway, strategy and charging regulation module, grouped data network gateway etc.Described network requests node is used to determine to carry out the carrying of load bearing deactivation, generate the load bearing deactivation request, and the load bearing deactivation request that generates sent to the network decision node, this networking decision node is subscriber equipment or the Serving GPRS Support Node in the UTMS system; Or the gateway in the SAE system, grouped data network gateway.

Fig. 4 shows the network requests node 21 in the embodiment of the invention and the structural representation of network decision node 10, wherein: network decision node 20 comprises receiving element 21, determining unit 22 and deexcitation unit 23, receiving element 21 is used to receive the load bearing deactivation request that network requests node 10 sends, this load bearing deactivation request comprises the bearer types indication that need carry out load bearing deactivation, and the bearer types of described deexcitation comprises dedicated bearing, default bearer or the last item default bearer; Determining unit 22 is used for determining to carry out the bearer types of load bearing deactivation; Deexcitation unit 23 is used for carrying out load bearing deactivation according to the bearer types that determining unit 22 is determined.Network requests node 10 comprises generation unit 11 and transmitting element 12, and wherein: generation unit 11 is used for carrying out according to decision the carrying of load bearing deactivation, generates the load bearing deactivation request; Transmitting element 12 is used for the load bearing deactivation request that generation unit 11 generates is sent to network decision node 20, when if this load bearing deactivation request occurs in the across a network system, when promptly this network requests node is SGSN or SGW, the load bearing deactivation request message that network requests node 10 sends need be changed, also be provided with a converting unit 13 among this SGSN or the SGW, be used to realize the load bearing deactivation request message conversion between UMTS and the SAE, UMTS load bearing deactivation request message in the load bearing deactivation request of generation unit 11 generations is converted to SAE load bearing deactivation request message, or when the notice downstream node is deleted corresponding bearer types, SAE load bearing deactivation message is converted into corresponding UMTS load bearing deactivation message.This converting unit 13 is used to realize the conversion of the load bearing deactivation request message between UMTS system and SAE system, after being converted into corresponding system message, information can be transmitted between interdepartmental system, the load bearing deactivation request message message of SAE is converted to the load bearing deactivation request message message of UMTS, or the load bearing deactivation request message message of UMTS is converted to the load bearing deactivation request message message of SAE.In concrete transfer process, if described load bearing deactivation request message contains when all carryings are carried out load bearing deactivation, the required parameter in the load bearing deactivation request message message of UMTS system is added in the load bearing deactivation request message message of SAE system; Perhaps the required parameter in the load bearing deactivation request message of UMTS system is converted to pairing required parameter in the load bearing deactivation request message of SAE system.

Be described in detail in the load bearing deactivation method that realizes in the R8 UMTS system below in conjunction with Fig. 5 to Figure 29.Flow chart 5 carries out the conversion of load bearing deactivation request message for the SGW node in the SAE system to flow process Figure 20, and when request message sent to corresponding network decision node, the conversion that need carry out in the SGW node between the message realized load bearing deactivation.

Fig. 5 is the attachment removal flow chart that the subscriber equipment (UE) in the embodiment of the invention is initiated, described attachment removal flow process is the Detach flow process that the corresponding network node is initiated, UE has known bearer types in the described process, and know that described bearer types is the last item default bearer, UE directly initiates the Detach flow process and realizes load bearing deactivation, and concrete steps are as follows:

Step S101: subscriber equipment (UE) sends Detach Request message to service GPRS support node (SGSN);

Step S102:SGSN receives the Detach Request message that UE sends, and sends Delete PDPcontest Request message to service webmaster (SGW);

Step S103:SGW receives the Delete PDP contest Request message that SGSN sends, and sends Delete Bearer Request message to grouped data network gateway (PGW);

Step S104:PGW receives the Delete Bearer Request message that SGW sends, and returns Delete Bearer Response message to SGW;

Carry out the mutual of information between step S105:PGW and strategy and the charging regulation module (PCRF), realize by the message among the PCRF Interaction;

Step S106:SGW receives the Delete Bearer Response message of returning, and sends Delete PDP contest Response message to SGSN;

Step S107:SGSN receives the Delete PDP contest Response message that SGW sends, and sends Detach Accent message to UE;

Step S108:, then discharge RAB if wireless network side has RAB (RAB).

By calling the Detach flow process that above-mentioned UE initiates, when UE know need load bearing deactivation be carried as the last item default bearer the time, can realize the deexcitation of R8 UMTS system bearing.

When UE initiated load bearing deactivation, UE knew bearer types, by the load bearing deactivation of SGW processing default bearer and dedicated bearing, can realize load bearing deactivation by the load bearing deactivation method that subscriber equipment shown in Figure 6 (UE) is initiated, and concrete steps are as follows:

Step S201:UE sends Deactivate PDP context Request (TI to SGSN, Teardown Ind, DBD) message, preserved the parameter of expression bearer types in this message, wherein: Teardown Ind is the dismounting sign, be to be used for identifying whether all being carried the sign of all deleting, i.e. load bearing deactivation; DBD is used for identifying the sign of whether all dedicated bearings all being deleted.If UE wants the deexcitation default bearer, Tearerdown Ind value is set to 1 in this message so, delete all carryings by the value representation of described setting, this value also can be represented by other self-defining numerical value or symbol, value representation UE by this parameter and setting wants all default bearers of deexcitation, if UE will delete all dedicated bearings that this PDN connects, the DBD value is set to 1 in this message so, delete all dedicated bearings by the value representation of described setting, this value also can be represented by other self-defining numerical value or symbol, value representation UE by this parameter and setting wants all dedicated bearings of deexcitation, the setting of the parameter value here and the message body of parameter can be carried out self-defining setting according to demand, and parameter by described setting and numerical value make it can satisfy all carryings of deletion and deletes all dedicated bearings;

Step S202:SGSN to SGW send Delete PDP context Request (TEID, NSAPI, Teardown Ind, DBD), wherein: TEID is a Tunnel End Point Identifier, NSAPI is a Network layer Service Access Point Identifier.If Teardown Ind parameter is set to delete all whens carrying in the message that UE sends, SGSN prepares all PDP Contexts of deexcitation so, if when DBD is set to delete all dedicated bearings, SGSN prepares all dedicated bearings of deexcitation so;

Step S203:SGW receives after the information of SGSN whether the Bearer ID that obtains according to NSAPI is the Bearer ID of default bearer, if the Bearer ID of default bearer, SGW will may mode handle this thing by following three kinds so:

A:SGW refuses this deexcitation request;

B:SGW prepares all carryings between SGW and the PGW are all deleted;

C:SGW deletes all dedicated bearings that this default bearer is associated.

The deexcitation of default bearer if SGW really admits a fault, when satisfying the C processing mode, SGW to PGW send Request Bearer Deactivation (Bearer ID, DBD).

If the message that step S202 sends has Tearerdown Ind parameter and value is all carryings of deletion, when satisfying the B processing mode, SGW can have two kinds of processing methods:

A) can use Ind, and it is changed to all carryings of deletion at this message the inside adding Tearerdown;

B) can Bearer ID be arranged to default bearer Bearer ID and without Tearerdown Ind.

After SGW was confirmed to be the deexcitation of default bearer, SGW sent Request BearerDeactivation (Bearer ID) message or Request Bearer Deactivation (Tearerdown Ind, BearerID) message to PGW.

Step S204: if disposed the PCC framework, it is mutual to carry out PCC;

Step S205:PGW sends Delete Bearer Request message to SGW, and (Bearer ID DBD) notifies SGW deleting bearing.If a) processing method of the among the step S203 has comprised Tearerdown Ind parameter in this message, replace Bearer ID parameter.SGW responds Delete BearerResponse () message to PGW.If the DBD value in the Delete Bearer Request message is 1, delete all dedicated bearings in all these PDN connections so;

Step S206:SGW sends Delete PDP Context response () message to SGSN, is 1 if the message among the S203 has the value of Teardown Ind, and SGSN deletes all carryings;

Step S207:SGSN sends response message Deactivate PDP Context Response to UE;

Step S208:, discharge RAB so if there is RAB in wireless side.

By need to determine the type of load bearing deactivation in UE, each network element in the system judges the bearer types of the deexcitation of needs, thereby deletes corresponding bearer types in network element.

When UE initiates load bearing deactivation, UE does not know bearer types, and SGW knows the type of carrying, and the processing deexcitation has response request to return to UE, can realize load bearing deactivation by the load bearing deactivation method that subscriber equipment shown in Figure 7 (UE) is initiated, concrete steps are as follows:

Step S301:UE sends Deactivate PDP context Request to SGSN, and (TI, TeardownInd), UE can not preserve the parameter of expression bearer types.UE is if all carryings of deexcitation, and Tearerdown Ind is set to delete all carryings in this message so;

Step S302:SGSN sends Delete PDP context Request (TEID, NSAPI, Teardown Ind) to SGW.If the message that UE sends comprises Teardown Ind, and value is 1, and SGSN prepares all PDP Contexts of deexcitation so;

Step S303: if SGW find UE request deexcitation be UE be not last carrying, SGW will have three kinds may modes handle this message so:

A:SGW refuses this deexcitation request;

B:SGW prepares all carryings between SGW and the PGW are all deleted;

C:SGW deletes all dedicated bearings that this default bearer is associated.

If SGW has received removal request, SGW judges to be the deexcitation of the last item default bearer, if the last item default bearer, SGW can select to refuse this deexcitation request so, perhaps directly call the Detach flow process that SGW initiates, the specific implementation flow chart as shown in Fig. 8 or Fig. 9, perhaps delete this carrying on all dedicated bearings and keep default bearer; Otherwise SGW sends out Delete PDPcontext Response to SGSN, has corresponding cause parameter in this message;

Step S304:SGSN sends out Deactivate PDP context Response to UE, has corresponding cause parameter in this message;

Step S305: if SGW is the Bearer ID of default bearer through the Bearer ID that NSAPI obtains, SGW sends Request Bearer Deactivation (Bearer ID to PGW, Tearerdown Ind, DBD), if SGW will delete all dedicated bearings of this IP/APN, so DBD is changed to all dedicated bearings of deletion;

Step S306: if disposed the PCC framework, PCRF issues the PCC strategy and gives PGW so;

Step S307:PGW sends Delete Bearer Request (Bearer ID) to SGW, if when containing Tearerdown Ind parameter in the message that receives, PGW can have two kinds of processing methods so:

Step S308:SGW is judged as the dedicated bearing deletion of all default bearers is kept default bearer, SGW issues a plurality of Delete PDP Context Request so, up to last Delete PDPContext Response message of receiving and after having deleted the dedicated bearing of all default bearers, just can carry out step S312.If the Bearer ID that the message that PGW sends comprises is the ID of a default bearer, SGW prepares the carrying of all IP/APN of deletion so, send Delete PDP context Request (NSAPI to SGSN then, Tearerdown Ind, DBD) message, and the Tearerdown Ind of the inside is set to delete all carryings;

Step S309: if the message that SGW sends comprises Tearerdown Ind and value is all carryings of deletion, SGSN prepares the carrying of all IP/APN of deletion so, then to UE send Deactivate PDP contextRequest (NSAPI, Tearerdown Ind, DBD);

Step S310: be all carryings of deletion if comprise Tearerdown Ind and value in the message that UE receives, UE deletes the carrying of all IP/APN so, sends Deactivate PDP contextRequest (NSAPI, Tearerdown Ind) to UE then;

Step S311: if the message that UE sends comprises Tearerdown Ind and value is all carryings of deletion, SGSN deletes all carryings so, otherwise delete the carrying of this NSAPI correspondence, send DeletePDP context Response (Bearer ID) to SGW then;

Step S312: if the Bearer ID of the message that SGSN sends is the Bearer ID of default bearer, SGW deletes all carryings, otherwise the carrying of SGW deletion Bearer ID correspondence sends Delete PDPcontext Response message to PGW then;

Step S313: if the request of this deleting bearing is initiated by the PCC system, PGW notifies this request of PCRF to be performed to PCRF transmission Provision Ack so;

Step S314:, after step S310 finishes, promptly can delete RAB so if there is the RAB carrying.

Fig. 8 is the flow chart of the Detach flow process that SGW initiates in the embodiment of the invention, and concrete steps are as follows:

Step S401:SGW sends Delete PDP context Request message to SGSN;

Step S402:SGSN sends Detach Request message to UE;

Step S403:SGW sends Delete Bearer Request message to PGW;

Step S404:PGW sends Delete Bearer Response message to SGW;

Step S405:PCRF and PGW carry out information interactive process between the PCRF Interaction;

Step S406:UE sends Detach Accent message to SGSN;

Step S407:SGSN sends Delete PDP context Response message to SGW;

Step S408:, then delete RAB if there is the RAB carrying.

Fig. 9 is another flow chart of the Detach flow process that SGW initiates in the embodiment of the invention, and concrete steps are as follows:

Step S501:SGW sends Initial Detach Request message to SGSN;

Step S502:SGSN sends Detach Request message to UE;

Step S503:SGSN sends Delete PDP context Request message to SGW;

Step S504:SGW sends Delete Bearer Request message to PGW;

Step S505:PGW sends Delete Bearer Response message to SGW;

Step S506:PCRF and PGW carry out information interactive process between the PCRF Interaction;

Step S507:SGW sends Delete PDP context Response message to SGSN;

Step S508: after step S502, UE can send Detach Accent message to SGSN;

Step S509:, then delete RAB if there is the RAB carrying.

When UE initiates load bearing deactivation, UE does not know bearer types, and SGW knows the type of carrying, and the processing deexcitation does not have response request to return to UE, can realize load bearing deactivation by the load bearing deactivation method that subscriber equipment shown in Figure 10 (UE) is initiated, concrete steps are as follows:

Step S601:UE sends Deactivate PDP context Request to SGSN, and (TI, TeardownInd), UE can not preserve the parameter of expression bearer types.UE is if all carryings of deexcitation, and Tearerdown Ind is set to delete all carryings in this message so;

Step S602:SGSN sends Delete PDP context Request (TEID, NSAPI, Teardown Ind) to SGW.If the message that UE sends comprises Teardown Ind, SGSN prepares all PDP Contexts of deexcitation so;

Step S603: if SGW is the Bearer ID of default bearer through the Bearer ID that NSAPI obtains, and be the last item default bearer, SGW can refuse so, the perhaps Detach flow process of directly initiating, the specific implementation flow chart is perhaps deleted all dedicated bearings on this carrying and is kept dedicated bearing as shown in Fig. 8 or Fig. 9.

To have three kinds may mode handle this thing if not the last item default bearer SGW:

A:SGW refuses this deexcitation request;

B:SGW prepares all carryings between SGW and the PGW are all deleted;

C:SGW deletes all dedicated bearings that this default bearer is associated.

If SGW prepares all carryings of deexcitation, call the load bearing deactivation that SGW initiates so, promptly carry out step S603 to step S612, wherein step S604 is identical to step S314 with step S305 among Fig. 7 to step S612.

When UE initiated load bearing deactivation, UE knew bearer types, by the load bearing deactivation of PGW processing default bearer and dedicated bearing, can realize load bearing deactivation by the load bearing deactivation method that subscriber equipment shown in Figure 11 is initiated, and concrete steps are as follows:

Step S701:UE sends Deactivate PDP context Request message to SGSN, and (TI, TeardownInd), UE preserves the parameter of expression bearer types.The value of this parameter comprises default bearer and dedicated bearing, if UE wants the deexcitation default bearer, Tearerdown Ind is set to delete all carryings in this message so;

Step S702:SGSN sends Delete PDP context Request message (TEID, NSAPI, Teardown Ind) to SGW, if the message that UE sends comprises Teardown Ind, SGSN prepares all PDP Contexts of deexcitation so;

Step S703:SGW sends Request Bearer Deactivation message (Bearer ID) to PGW, SGW obtains Bearer ID according to NSAPI, SGW prepares the deletion carrying relevant with Bearer ID, if the message of sending among the step S702 has Tearerdown Ind parameter and value is all carryings of deletion, SGW can have two kinds of processing methods so:

Step S704: if disposed the PCC framework, it is mutual to carry out PCC so;

Step S705: if PGW judges the Bearer ID that this Bearer ID is a default bearer, PGW will have three kinds may mode handle this thing so:

A:PGW refuses this deexcitation request;

B:PGW deletes all carryings of the IP/APN of this default bearer correspondence;

C:PGW deletes all dedicated bearings that this default bearer is associated.

PGW sends Delete Bearer Request (Bearer ID) to SGW and comes deleting bearing, if step S703 has adopted a) processing mode, also contains Tearerdown Ind parameter in this this message.

Step S706:SGW is according to the corresponding carrying of Bearer ID deletion, if the Bearer ID of the DeleteBearer Request (Bearer ID) that receives from PGW is the Bearer ID of default bearer, delete all carryings so, respond a Delete Bearer Response () message to PGW then, the carrying of PGW deletion Bearer ID correspondence;

Step S707:SGW sends out Delete PDP Context response () to SGSN.If the message among the step S702 has Teardown Ind, perhaps SGW knows it is the deletion default bearer, is the Tearerdown Ind value of this message 1 so, and SGSN deletes all carryings then.

Step S708:SGSN makes sound to UE and answers message Deactivate PDP Context Response (TI).

Step S709:, discharge RAB so if there is RAB in wireless side.

When UE initiates load bearing deactivation, UE does not know bearer types, and PGW knows the type of carrying, and handles the load bearing deactivation of default bearer and dedicated bearing by PGW, can realize load bearing deactivation by the load bearing deactivation method that subscriber equipment shown in Figure 12 is initiated, concrete steps are as follows:

Step S801:UE to SGSN send Deactivate PDP context Request (TI, TeardownInd), if UE wants all carryings of deexcitation, Tearerdown Ind is set to delete all carryings in this message so;

Step S802:SGSN sends Delete PDP context Request (TEID, NSAPI, Teardown Ind) to SGW, if the message that UE sends comprises Teardown Ind, SGSN prepares all PDP Contexts of deexcitation so;

Step S803:SGW sends Request Bearer Deactivation (Bearer ID) to PGW.SGW obtains Bearer ID according to NSAPI.SGW prepares the deletion carrying relevant with Bearer ID.If the message that step S802 sends has Tearerdown Ind parameter and value is all carryings of deletion, SGW can have two kinds of processing methods so:

Step S804: if disposed the PCC framework, PGW and PCRF carry out the PCC information interaction;

Step S805: if PGW judges the Bearer ID that this Bearer ID is a default bearer, PGW will have three kinds may mode handle this thing so:

A:PGW refuses this deexcitation request;

C:PGW deletes all dedicated bearings that this default bearer is associated.

If PGW continues deleting bearing, PGW judges whether it is last default bearer so, if, PGW can refuse so, perhaps directly enter and call the Detach that PGW initiates, flow chart as shown in Figure 13 or Figure 14, perhaps delete all dedicated bearings of this default bearer and keep this default bearer, if not last default bearer, call the load bearing deactivation flow process that PGW initiates so, promptly carry out step S805, send Delete Bearer Request message to SGW to step S812, described step S805 step S307 to step S812 and Fig. 7 is identical to step S314, repeats no more here.

Figure 13 is the flow chart of the Detach flow process that PGW initiates in the embodiment of the invention, and concrete steps are as follows:

Step S901:, carry out the PCC information interaction between PCRF and the PGW if when having the PCC framework;

Step S902:PGW sends Delete Bearer Request message to SGW;

Step S903:SGW sends Delete PDP context Request message to SGSN

Step S904:SGSN sends Detach Request message to UE;

Step S905:UE sends Detach Accent message to SGSN;

Step S906:SGSN sends Delete PDP contex Response message to SGW;

Step S907:SGW sends Delete Bearer Response message to PGW;

Step S908:, then delete RAB if there is the RAB carrying.

Figure 14 is another flow chart of the Detach flow process that PGW initiates in the embodiment of the invention, and concrete steps are as follows:

Step S1001:PGW sends Initial Detach Request message to SGW;

Step S1002:SGW sends Initial Detach Request message to SGSN;

Step S1003:SGSN sends Detach Request message to UE;

Step S1004:SGSN sends Delete PDP context Request message to SGW;

Step S1005:SGW sends Delete Bearer Request message to PGW;

Step S1006:PGW sends Delete Bearer Response message to SGW;

Step S1007:PCRF and PGW carry out information interactive process between the PCRF Interaction;

Step S1008:SGW sends Delete PDP context Response message to SGSN;

Step S1009: after step S1003, UE can send Detach Accent message to SGSN;

Step S1010:, then delete RAB if there is the RAB carrying.

When UE initiates load bearing deactivation, UE does not know bearer types, and PGW knows bearer types, and handles the load bearing deactivation of default bearer and dedicated bearing by PGW, can realize load bearing deactivation by the load bearing deactivation method that subscriber equipment shown in Figure 15 is initiated, concrete steps are as follows:

Step S1101:UE to SGSN send Deactivate PDP context Request (TI, TeardownInd), if UE wants all carryings of deexcitation, Tearerdown Ind is set to delete all carryings in this message so;

Step S1102:SGSN sends Delete PDP context Request (TEID, NSAPI, Teardown Ind) to SGW, if the message that UE sends comprises Teardown Ind, SGSN prepares all PDP Contexts of deexcitation so;

Step S1103:SGW sends Request Bearer Deactivation (Bearer ID) to PGW, and SGW obtains Bearer ID according to NSAPI, and SGW prepares the deletion carrying relevant with Bearer ID.If the message that step S1102 sends has Tearerdown Ind parameter and value is all carryings of deletion, SGW can have two kinds of processing methods so:

Step S1104: if disposed the PCC framework, it is mutual to carry out PCC so;

Step S1105: if PGW judges the Bearer ID that this Bearer ID is a default bearer, PGW will have three kinds may mode handle this thing so:

A:PGW refuses this deexcitation request;

C:PGW deletes all dedicated bearings that this default bearer is associated.

If PGW continues deleting bearing, judge whether it is last default bearer so, if, so directly call the Detach that PGW initiates, flow chart as shown in Figure 13 or Figure 14, if not, send Response Bearer Deactivation message to SGW so, and have the cause of response;

Step S1106:SGW sends Delete PDP Context Response message to SGSN, and has the cause of response;

Step S1107:SGSN sends Deactivate PDP Context Response message to UE, and has the cause of response;

Call the load bearing deactivation flow process that PGW initiates, carry out step S1108 to step S1116, the step S306 shown among its implementation procedure and Fig. 7 is identical to step S314, no longer too much gives unnecessary details here.

When SGSN initiated load bearing deactivation, SGW knew bearer types, and handled the load bearing deactivation of default bearer and dedicated bearing by SGW, the load bearing deactivation method realization load bearing deactivation that can initiate by SGSN shown in Figure 16, and concrete steps are as follows:

Step S1201:SGSN sends Delete PDP Context Request message (NSAPI, Tearerdown Ind) to SGW, if SGSN wants the deexcitation default bearer, TearerdownInd is set to delete all carryings in this message so;

Step S1202:SGW obtains Bearer ID according to the NSAPI of the Delete PDP Context Request that SGSN sends, detecting this carrying of wanting deexcitation is default bearer, if default bearer, and when being last default bearer, then call the Detach flow process that SGW initiates, the specific implementation flow chart is as shown in Fig. 8 or Fig. 9.

If it is default bearer that SGW detects the carrying that will activate, and is not last default bearer, SGW can have following several processing method:

A:SGW refuses this deexcitation request;

B:SGW prepares all carryings between SGW and the PGW are all deleted;

C:SGW deletes all dedicated bearings that this default bearer is associated.

SGW sends Request Bearer Deactivation message (Bearer ID) to PGW, if comprise TearerdownInd and value for deleting all carryings in article one message, promptly wants all carryings of deexcitation, and SGW can have two kinds of processing methods so:

Step S1203: if disposed the PCC framework, it is mutual to carry out PCC so;

Step S1204:PGW sends Delete Bearer Request (Bearer ID) to SGW, if adopted a) processing method among the step S1202, then also comprises Tearerdown Ind parameter in this message, the carrying of SGW deletion Bearer ID correspondence.

After step S1205:SGW receives Delete Bearer Request (Bearer ID) message of PGW transmission, send Delete PDP context Response (), the corresponding carrying of SGSN deletion to SGSN;

Step S1206:SGW sends Delete Bearer Response () to PGW after receiving Delete Bearer Request (Bearer ID) message that PGW sends, the carrying of PGW deletion Bearer ID correspondence, if PGW is confirmed to be the Bearer ID of default bearer, delete all carryings so;

Step S1207:SGSN sends out Deactivate PDP context Request (TI) message to UE;

Step S1208:UE sends Deactivate PDP context Accept message to SGSN;

Step S1209:, discharge RAB so if wireless side has the RAB carrying.

When SGSN initiated load bearing deactivation, PGW knew bearer types, and handled the load bearing deactivation of default bearer and dedicated bearing by PGW, the load bearing deactivation method realization load bearing deactivation that can initiate by SGSN shown in Figure 17, and concrete steps are as follows:

Step S1301:SGSN sends Delete PDP Context Request message (NSAPI, Tearerdown Ind) to SGW, if SGSN wants the deexcitation default bearer, TearerdownInd is set to delete all carryings in this message so;

Step S1302:SGW obtains Bearer ID according to the NSAPI of the Delete PDP Context Request that SGSN sends, and SGW sends Request Bearer Deactivation (Bearer ID) to PGW then;

If in step S1302 message, comprise TearerdownInd and value for all carryings of deletion, promptly want all carryings of deexcitation, SGW can have two kinds of processing methods so:

Step S1303: if disposed the PCC framework, it is mutual to carry out PCC so;

Step S1304: to want the carrying of deexcitation is default bearer if PGW detects, and when being last default bearer, then calls the Detach flow process of PGW initiation, and the specific implementation flow chart is as shown in Figure 13 or Figure 14.

If it is default bearer that PGW detects this carrying of wanting deexcitation, if, and be not last default bearer, PGW can have following three kinds of processing modes so:

A:PGW refuses this deexcitation request;

B:PGW prepares that PGW is gone up all carryings and deletes;

C:PGW deletes all dedicated bearings that this default bearer is associated.

The relative carrying of PGW deletion Bearer ID, and to SGW transmission Delete Bearer Request (BearerID), if adopted a) processing method among the step S1202, then also comprise Tearerdown Ind parameter in this message, the carrying of SGW deletion Bearer ID correspondence.

Step S1305:SGW sends Delete PDP context Response () to SGSN after receiving the Delete Bearer Request message of step S1204, if SGW has confirmed step S1304 deletion is default bearer or will be all deleting load-bearings, and SGW is changed to 1 to Teardown Ind in this message so.

Step S1306:SGW sends Delete Bearer Response () to PGW after receiving the Delete Bearer Request message of step S1204.The carrying of PGW deletion Bearer ID correspondence if PGW is confirmed to be the Bearer ID of default bearer, is deleted all carryings so;

Step S1307:SGSN sends out Deactivate PDP context Request (TI) message to UE;

Step S1308:UE sends Deactivate PDP context Accept (TI) to SGSN;

Step S1309:, discharge RAB so if wireless side has the RAB carrying.

When SGSN initiates load bearing deactivation, PGW knows bearer types, and handle the load bearing deactivation of default bearer and dedicated bearing by PGW, after SGW receives the Detete PDP Request message that SGSN sends, find deexcitation be carried as last default bearer the time, can realize load bearing deactivation by the load bearing deactivation method that SGSN shown in Figure 180 initiates, concrete steps are as follows:

Step S1401:SGSN sends Delete PDP Context Request message (NSAPI, Tearerdown Ind) to SGW, if SGSN wants the deexcitation default bearer, TearerdownInd is set to delete all carryings in this message so;

Step S1402:SGW receives last default bearer that is carried as of finding deexcitation after the Detete PDP Context Request message that SGSN sends, and replys Delete PDP ContextResponse message to SGSN, and has the error reason of response;

Step S1403 is the deleting load-bearing flow process of initiating by SGW to step S1412, and its implementation procedure is identical to step S314 with step S305 shown in Figure 7, repeats no more here.

When PGW initiated load bearing deactivation, PGW knew bearer types, and handled the load bearing deactivation of default bearer and dedicated bearing by PGW, the load bearing deactivation method realization load bearing deactivation that can initiate by PGW shown in Figure 19, and concrete steps are as follows:

Step S1501: if disposed the PCC framework, PCRF issues the PCC strategy and gives PGW so;

Step S1502:PGW sends Delete Bearer Request (Bearer ID) to SGW, if all carryings that this PDN of PGW animus cancellandi connects, PGW can have two kinds of processing methods so:

If it is last default bearer that PGW detects the carrying that will delete, so directly call the Detach flow process that PGW initiates, the flow chart as shown in Figure 13 or Figure 14; When if the detection default bearer is not last default bearer, also can the dedicated bearing of all these default bearers be deleted and the reservation default bearer by the SGW decision.

Step S1503: keep default bearer if the SGW decision is deleted the dedicated bearing of all default bearers surely, SGW issues a plurality of Delete PDP Context Request message and gives SGSN so, behind last the Delete PDP Context Response that receives, delete the dedicated bearing of all these default bearers, just can carry out step S1507.If the Bearer ID that the message that PGW sends comprises is the ID of a default bearer, SGW prepares the carrying of all IP/APN of deletion so, send Delete PDP contextRequest (NSAPI to SGSN then, Tearerdown Ind, DBD) also the Tearerdown Ind of the inside is set to delete all carryings;

Step S1504: if the message that SGW sends comprises Tearerdown Ind and value is all carryings of deletion, SGSN prepares the carrying of all IP/APN of deletion so, then to UE send Deactivate PDP contextRequest (NSAPI, Tearerdown Ind, DBD);

Step S1505: be all carryings of deletion if comprise Tearerdown Ind and value in the message that UE receives, UE deletes the carrying of all IP/APN so, sends Deactivate PDP contextRequest (NSAPI, Tearerdown Ind) to UE then;

Step S1506: if the message that UE sends comprises Tearerdown Ind and value is all carryings of deletion, SGSN deletes all carryings so, otherwise delete the carrying of this NSAPI correspondence, send Delete PDP context Response (Bearer ID) to SGW then

Step S1507: if the Bearer ID of the message that SGSN sends is the Bearer ID of default bearer, SGW deletes all carryings so, otherwise the carrying of SGW deletion Bearer ID correspondence sends Delete PDP context Response to PGW then;

Step S1508: if the request of this deleting bearing is initiated by the PCC system, PGW notifies this request of PCRF to be performed to PCRF transmission Provision Ack so;

Step S1509:, after step S1505 finishes, promptly can delete RAB so if there is the RAB carrying.

When SGW initiates load bearing deactivation, PGW knows bearer types, and handle the load bearing deactivation of default bearer and dedicated bearing by PGW, SGW know deexcitation be carried as last default bearer the time, can realize the deexcitation of carrying by the Detach flow process that SGW initiates, as Fig. 8 or flow chart shown in Figure 9.When the carrying that detects the deexcitation of wanting as SGW is not last default bearer, can realize load bearing deactivation by the load bearing deactivation method that SGW shown in Figure 20 initiates, concrete steps are as follows:

Step S1601: if the carrying of deexcitation is not last default bearer, so SGW to PGW send Request Bearer Deactivation (Bearer ID, Tearerdown Ind, DBD).If all dedicated bearings of this IP/APN of SGW animus cancellandi are changed to DBD all dedicated bearings of deletion so;

Step S1602 is to call the load bearing deactivation flow process that PGW initiates to step S1610, and the specific implementation step is identical to step S1509 with step S1501 among Figure 20, no longer too much gives unnecessary details here.

Flow process Figure 21 to flow process Figure 29 for when the message that carries out UMTS system and SAE system by SGSN is changed, when having request message to send to corresponding network decision node, need in the SGSN node, carry out the flow chart of the conversion realization load bearing deactivation between the message.

When UE initiated load bearing deactivation, UE knew bearer types, by the load bearing deactivation of SGSN processing default bearer and dedicated bearing, can realize load bearing deactivation by the load bearing deactivation method that subscriber equipment shown in Figure 21 (UE) is initiated, and concrete steps are as follows:

Step S1701: if UE knows is the last item default bearer, and UE directly calls the Detach flow process that UE initiates so, and particular flow sheet as shown in Figure 2.UE by NAS message to SGSN send DeactivatePDP context Request (Teardown Ind, TI).If UE wants all carryings of deexcitation, Tearerdown Ind is set to delete all carryings in this message so, and UE preserves the parameter of expression bearer types.The value of this parameter comprises default bearer and dedicated bearing.If UE wants the deexcitation default bearer, Tearerdown Ind is set to delete all carryings in this message so;

Step S1702:SGSN obtains BearerID according to the Delete PDP Context Request that SGSN sends, and detecting this carrying of wanting deexcitation is default bearer, if SGSN can have following three kinds of processing so:

A:SGSN refuses this deexcitation request;

B:SGSN prepares all carryings between SGW and the SGSN are all deleted;

C:SGSN deletes all dedicated bearings that this default bearer is associated.

Delete all carryings that this PDN connects if desired, SGSN sends Request BearerDeactivation to SGW, and (Bearer ID DBD), deletes all dedicated bearings that this default bearer is associated if desired, and SGSN is provided with DBD so.

If the last item default bearer, SGSN can handle so so:

A:SGSN refuses this deexcitation;

B:SGSN directly calls the Detach flow process, and the process of specific implementation is seen Figure 22;

C:SGSN deletes all dedicated bearings that this default bearer is associated.

No matter be to be to have brought Tearerdown Ind among default bearer or the step S1701 according to the carrying that Bearer ID obtains, SGSN has two kinds of methods to handle so:

Step S1703:SGW to PGW send Request Bearer Deactivation (Bearer ID, DBD).If adopted a) processing method in the step 1702, then also comprised Tearerdown Ind parameter in this message;

Step S1704: if disposed the PCC network, PGW will obtain the PCC strategy alternately with PCRF so, if there is not the PCC framework, PGW this locality produces the PCC strategy so;

Step S1705:PGW sends Delete Bearer Request (Bearer ID) to SGW, if step S1702 step has adopted a) method, contains Tearerdown Ind parameter in this message;

Step S1706:SGW returns Delete Bearer Response message to PGW;

Step S1707:SGW sends Delete Bearer Request (Bearer ID) to SGSN, if step S1702 step has adopted a) method, contains Tearerdown Ind parameter in this message;

Step S1708:SGSN sends Deactivate PDP context Reponse (TI) message to UE;

Step S1709:SGSN sends Delete Bearer Response () message to SGW;

Step S1710:, discharge the RAB carrying so if there is the RAB carrying in this UE;

Figure 22 shows the Detach flow process that SGSN initiates in the embodiment of the invention, and concrete steps are as follows:

Step S1801:SGSN sends Detach Request message to UE;

Step S1802:SGSN sends Delete PDP context Request message to SGW;

Step S1803:SGW receives the Delete PDP contest Request message that SGSN sends, and sends Delete Bearer Request message to grouped data network gateway (PGW);

Step S1804:PGW receives the Delete Bearer Request message that SGW sends, and returns Delete Bearer Response message to SGW;

Carry out the mutual of information between step S1805:PGW and strategy and the charging regulation module (PCRF), realize by the message among the PCRF Interaction;

Step S1806:SGW receives the Delete Bearer Response message of returning, and sends Delete PDP contest Response message to SGSN;

Step S1807:SGSN receives UE and sends Detach Accent message;

Step S1808:, then discharge RAB if wireless network side has RAB (RAB).

UE initiates load bearing deactivation, UE does not know bearer types, and SGSN knows bearer types, and handles the load bearing deactivation of default bearer and dedicated bearing by SGSN, can realize load bearing deactivation by the load bearing deactivation method that subscriber equipment shown in Figure 23 (UE) is initiated, concrete steps are as follows:

Step S1901:UE by NAS message to SGSN send Deactivate PDP contextRequest (Teardown Ind, TI), if UE wants all carryings of deexcitation, Tearerdown Ind is set to delete all carryings in this message so;

Step S1902:SGSN obtains Bearer ID according to the Delete PDP Context Request that UE sends, detecting this carrying of wanting deexcitation is default bearer, if default bearer and be not last carrying, SGSN can have following three kinds of processing modes so:

A:SGSN refuses this deexcitation request;

B:SGSN prepares all carryings between SGW and the SGSN are all deleted;

C:SGSN deletes all dedicated bearings that this default bearer is associated.

If deletion is last default bearer, SGSN can handle so so:

A1:SGSN refuses this deexcitation;

B1:SGSN directly enters and calls the Dettach flow process that SGSN initiates, and implementation procedure as shown in Figure 22;

C1:SGSN deletes all dedicated bearings that this default bearer is associated.

SGSN mails in the Request Bearer Deactivation message of SGW, no matter be to be that default bearer or step S1901 have brought Tearerdown Ind according to the carrying that Bearer ID obtains, SGSN has two kinds of methods to handle so:

Step S1903:SGSN sends Request Bearer Deactivation (Bearer ID) to SGW, if SGSN does not want all carryings of deexcitation, so according to the corresponding carrying of Bearer ID deletion;

SGW sends Request Bearer Deactivation (Bearer ID) message to PGW, as having adopted a) processing mode among the step S1902, then contains Tearerdown Ind parameter in this message.

Step S1904: if disposed the PCC framework, so PCRF will with PGW alternately to produce PCCrules;

Step 1905: if disposed the PCC network, PCRF produces strategy and gives PGW so, if there is not the PCC framework, PGW produces local policy so;

Step S1906:PGW sends Delete Bearer Request (Bearer ID) to SGW, and according to all carryings of Bearer ID preparation deletion, if PGW determines all carryings that this PDN of deexcitation connects but is not all load bearing deactivations that two kinds of methods are arranged so:

If PGW wants all dedicated bearings on all certain default bearers of deexcitation and keeps default bearer, PGW adds the DBD parameter in this message so, promptly Delete Bearer Request (Bearer ID, DBD).

Step S1907:SGW sends Delete Bearer Request, and (Bearer ID DBD), as having adopted a) processing mode among the step S1902, then contains Tearerdown Ind parameter in this message to SGSN;

Step S1908:SGSN sends Deactivate PDP Context Request (Teardown Ind to UE, TI), if have DBD in the step S1906 message, so SGSN send repeatedly this message to UE to guarantee to have deleted the dedicated bearing on all these default bearers;

Step S1909:UE sends Deactivate PDP Context Accept (TI) to SGSN;

Step S1910:SGSN has judged whether to delete the dedicated bearing on all these default bearers, if all deleted, SGSN sends Delete Bearer Response message to SGW so;

Step S1911:SGW sends Delete Bearer Response to PGW

Step S1912: if the request of this deleting bearing is initiated by the PCC system, PGW notifies this request of PCRF to be performed to PCRF transmission Provision Ack so.

Step S1913:, after step S1909 finishes, promptly can delete RAB so if there is the RAB carrying.

UE initiates load bearing deactivation, UE does not know bearer types, and SGSN knows bearer types, and handles the load bearing deactivation of default bearer and dedicated bearing by SGSN, can realize load bearing deactivation by the load bearing deactivation method that subscriber equipment shown in Figure 24 (UE) is initiated, concrete steps are as follows:

Step S2001:UE by NAS message to SGSN send Deactivate PDP contextRequest (Teardown Ind, TI), if UE wants all carryings of deexcitation, Tearerdown Ind is set to delete all carryings in this message so;

Step S2002:SGSN sends Deactivate PDP context Response to UE, has corresponding cause in this message;

Step S2003 is the load bearing deactivation flow process that SGSN initiates to step S2014, and implementation method is identical to step S1913 with the step S1902 described in Figure 24, no longer too much gives unnecessary details here.

UE initiates load bearing deactivation, and UE knows bearer types, and handles the load bearing deactivation of default bearer and dedicated bearing by PGW, the load bearing deactivation method realization load bearing deactivation that can initiate by subscriber equipment shown in Figure 25 (UE), and concrete steps are as follows:

Step S2101:UE sends Deactivate PDP contextRequest by NAS message to SGSN, and (UE preserves the parameter of expression bearer types for Teardown Ind, NSAPI) message.The value of this parameter comprises default bearer and dedicated bearing, if UE wants deexcitation default bearer or all carryings, Tearerdown Ind is set to delete all carryings in this message so;

Step S2102:SGSN obtains Bearer ID according to NSAPI, and SGSN sends RequestBearer Deactivation (Bearer ID) to SGW;

If delete all carryings that this PDN connects, no matter be to be to have brought Tearerdown Ind among default bearer or the step S2102 according to the carrying that Bearer ID obtains, SGSN has two kinds of methods to handle so:

Step S2103:SGW sends Request Bearer Deactivation (Bearer ID) message to PGW, if adopted a) kind method among the step S2102, then also comprises Tearerdown Ind parameter in this message.

Step S2104: if disposed the PCC network, PGW will obtain the PCC strategy alternately with PCRF so, if there is not the PCC framework, PGW this locality produces the PCC strategy so

The Request Bearer Deactivation (Bearer ID) that step S2105:PGW sends according to SGW, detecting this carrying of wanting deexcitation is default bearer, if PGW can have following several processing so:

A:PGW refuses this deexcitation request;

B:PGW prepares all carryings between SGW and the PGW are all deleted;

C:PGW keeps this default bearer, deletes this all dedicated bearings above default bearer.

PGW prepares according to the corresponding carrying of Bearer ID deletion, delete the last item default bearer if desired, so directly enter and call the Detach flow process that PGW initiates, as Fig. 8 or flow chart shown in Figure 9, perhaps this default bearer is kept these all dedicated bearings above default bearer of deletion, perhaps refusal deletion.

PGW sends Delete Bearer Request (Bearer ID) to SGW, and the carrying that the SGW deletion is relevant with Bearer ID if adopted a) kind method among the step S2102, then also comprises Tearerdown Ind parameter in this message.

Step S2106:SGW sends Delete Bearer Response (Bearer ID) to PGW, and the relevant carrying of PGW deletion Bearer ID if adopted a) kind method among the step S2102, then also comprises Tearerdown Ind parameter in this message;

Step S2107:SGW sends Delete Bearer Request (Bearer ID) to SGSN; If adopted a) kind method among the step S2102, then also comprise Tearerdown Ind parameter in this message;

Step S2108:SGSN to UE send Deactivate PDP context Reponse (Teardown Ind, TI);

Step S2109:SGSN sends Delete Bearer Response (Bearer ID) to SGW, if adopted a) kind method among the step S2102, then also comprises Tearerdown Ind parameter in this message;

Step S2110:, discharge the RAB carrying so if there is the RAB carrying in this UE.

UE initiates load bearing deactivation, UE does not know bearer types, and PGW knows bearer types, and handles the load bearing deactivation of default bearer and dedicated bearing by PGW, can realize load bearing deactivation by the load bearing deactivation method that subscriber equipment shown in Figure 26 (UE) is initiated, concrete steps are as follows:

Step S2201:UE sends Deactivate PDP contextRequest (Teardown Ind by NAS message to SGSN, NSAPI), if UE wants all carryings of deexcitation, Tearerdown Ind is set to delete all carryings in this message so;

Step S2202:SGSN obtains BearerID according to the Delete PDP Context Request that SGSN sends, and detecting this carrying of wanting deexcitation is default bearer,

The deexcitation of default bearer if SGSN really admits a fault, SGSN sends RequestBearer Deactivation (Bearer ID) to SGW so.SGSN obtains Bearer ID according to NSAPI.SGSN prepares according to the corresponding carrying of Bearer ID deletion.Delete all carryings if desired, no matter be to be that default bearer or step S2201 have brought Tearerdown Ind according to the carrying that Bearer ID obtains, SGSN has two kinds of methods to handle so:

Step S2203:SGW sends Request Bearer Deactivation (Bearer ID) to PGW, if adopted a) kind method among the step S2202, then also comprises Tearerdown Ind parameter in this message;

Step S2204:PGW detects whether will delete and is carried as default bearer, if PGW can have following several processing so:

A:PGW refuses this deexcitation request;

B:PGW prepares all carryings between SGW and the PGW are all deleted;

If PGW finds that this is the last item default bearer, to call the Detach flow process that PGW initiates so, as Fig. 9 or flow chart shown in Figure 10, perhaps keep this default bearer and delete this all dedicated bearings above default bearer, perhaps the deexcitation of refusal carrying.Otherwise enter step S2205 to step S2212, carry out the deexcitation flow process that PGW initiates, step S2204 is identical to step S1913 with the step S1905 shown in Figure 23 to step S2212, repeats no more here.

SGSN initiates load bearing deactivation, and Figure 27 shows the load bearing deactivation flow chart that SGSN initiates in the embodiment of the invention, and concrete steps are as follows:

Step S2301:SGSN sends Request Bearer Deactivation (Bearer ID) to SGW;

If SGSN does not want all carryings of deexcitation, so according to the corresponding carrying of Bearer ID deletion;

If all carryings of SGSN decision deexcitation have two kinds of methods so:

Step S2302:SGW sends Request Bearer Deactivation (Bearer ID) to PGW, if adopted a) kind method among the step S2301, then also comprises Tearerdown Ind parameter in this message;

Step S2303: if disposed the PCC framework, so PCRF will with PGW alternately to produce PCC rules

Step S2304 is the load bearing deactivation flow process that PGW initiates to step S2312, and its implementation procedure is identical to step S1913 with the step S1905 shown in Figure 23, repeats no more here.

After carrying out step S2303, if the carrying of deexcitation is not the last item default bearer, call the load bearing deactivation flow process that PGW initiates so, promptly carry out step S2304 to step 2312; Otherwise PGW has following processing method:

A:PGW refuses this deexcitation;

B:PGW directly enters and calls the Dettach flow process, as Figure 10 or flow process shown in Figure 11;

C:PGW deletes all dedicated bearings that this default bearer is associated.

PGW initiates load bearing deactivation, and Figure 28 shows the load bearing deactivation flow chart that PGW initiates in the embodiment of the invention, and concrete steps are as follows:

Step S2401: if disposed the PCC network, PCRF produces strategy and gives PGW so, if there is not the PCC framework, PGW produces local policy so;

Step S2402:PGW sends Delete Bearer Request (Bearer ID) to SGW, and according to all carryings of Bearer ID preparation deletion, if PGW determines all carryings that this PDN of deexcitation connects but is not all load bearing deactivations that two kinds of methods are arranged so:

If all carryings of PGW decision deexcitation so directly enter the Detach flow process that PGW initiates, shown in Fig. 9 or 10.

Step S2403:SGW sends Delete Bearer Request, and (Bearer ID DBD) gives SGSN, if adopted a) kind method among the step S2402, then also comprises Tearerdown Ind parameter in this message;

Step S2404:SGSN sends Deactivate PDP Context Request (Teardown Ind to UE, TI), if have DBD in the message that step S2403 sends, so SGSN send repeatedly this message to UE to guarantee to have deleted the dedicated bearing on all these default bearers;

Step S2405:UE sends Deactivate PDP Context Accept (TI) to SGSN;

Step S2406:SGSN has judged whether to delete the dedicated bearing on all these default bearers, if all deleted, SGSN sends Delete Bearer Response to SGW so;

Step S2407:SGW sends Delete Bearer Response to PGW;

Step S2408: if the request of this deleting bearing is initiated by the PCC system, PGW notifies this request of PCRF to be performed to PCRF transmission Provision Ack so;

Step S2409:, after step S2405 finishes, promptly can delete RAB so if there is the RAB carrying.

SGW initiates load bearing deactivation, and Figure 29 shows the load bearing deactivation flow chart that PGW initiates in the embodiment of the invention, and concrete steps are as follows:

Step S2501:SGW sends Request Bearer Deactivation to PGW, and (Bearer ID, DBD), SGW prepares the deletion carrying relevant with Bearer ID.If all carryings of SGW decision deexcitation have two kinds of methods so:

Step S2502 is to call the load bearing deactivation flow process that PGW initiates to step S2510, its implementation procedure is identical to step S2409 with the step S2401 described in Figure 25, if article one contain the DBD that is set to delete all dedicated bearings in the message, should delete all dedicated bearings on this default bearer in this flow process so and keep default bearer, no longer too much give unnecessary details here.

In the anti-activating method in existing SAE system, can carry the DBD parameter by increase, realize keeping default bearer by described parameter and delete all dedicated bearings, Figure 30 is the load bearing deactivation flow process that PGW initiates in the embodiment of the invention, and concrete steps are as follows:

Step S2601: if operator has disposed the PCC network, the triggering of PCC strategy will be deleted some carryings so, if do not dispose the PCC network, and certain carrying of PGW decision deletion so;

Step S2602:LPGW sends Delete Dedicated Bearer Request (Bearer ID to SGW, DBD, Teardown Ind), if PGW will delete all carryings, Teardown Ind so promptly is set, if PGW will delete the dedicated bearing of this carrying and all these PDN connections, PGW is provided with DBD so;

Step S2603:SGW sends Delete Dedicated Bearer Request (Bearer ID, DBD, Teardown Ind) to MME;

Step S2604:MME sends Deactivate Bearer Request (Bearer ID, DBD, Teardown Ind) to eNB;

Step S2605:eNB sends Radio Bearer Release Request (RB ID) to UE;

Step S2606:UE sends Radio Bearer Release Response (RB ID) to eNB;

Step S2607:eNB sends Deactivate Bearer Response to MME;

Step S2608:MME sends Delete Dedicated Bearer Response to SGW;

Step S2609:SGW sends Delete Dedicated Bearer Response to PGW;

Step S2610: if this delete procedure is triggered by PCC, PGW responds to PCRF transmission Provision Ack so.

Figure 31 is the load bearing deactivation flow process that MME initiates in the embodiment of the invention, and concrete steps are as follows:

Step S2701:MME sends Request Dedicated Bearer Deactivation (BearerID to SGW, DBD, Teardown Ind), if MME will delete all carryings, Teardown Ind so promptly is set, if MME will delete the dedicated bearing of this carrying and all these PDN connections, MME is provided with DBD so;

Step S2702:SGW sends Request Dedicated Bearer Deactivation (BearerID, DBD, Teardown Ind) to PGW;

Step S2601: if operator has disposed the PCC framework, PGW notifies the carrying that will delete so, carries out the dedicated bearing deexcitation flow process that PGW initiates, and carries out step S2602 to step S2610.

In sum, the method that provides by the embodiment of the invention has realized the load bearing deactivation of R8 UMTS system and SAE system, initiates the bearer types of required deletion by different network nodes, as deletes all carryings, promptly deletes default bearer; Or deletion dedicated bearing and keep default bearer, realized the load bearing deactivation between interdepartmental system, and realized deleting different bearer types according to dedicated bearing and default bearer dissimilar, if certain network node knows when the bearer types in the described load bearing deactivation request is the last item default bearer that the attachment removal flow process that can directly call this network node realizes load bearing deactivation.Realized that by described method the deletion dedicated bearing keeps default bearer in the SAE system.

Above disclosed only is a kind of preferred embodiment in the embodiment of the invention, can not limit the present invention's interest field certainly with this, and therefore the equivalent variations of doing according to claim of the present invention still belongs to the scope that the present invention is contained.

Claims

1, a kind of method that realizes load bearing deactivation of mobile communication system is characterized in that, this method may further comprise the steps:

Definite needs carry out the bearer types of load bearing deactivation;

2, the method for realization load bearing deactivation of mobile communication system as claimed in claim 1 is characterized in that, described bearer types is: the last item default bearer, default bearer or dedicated bearing.

3, the method for realization load bearing deactivation of mobile communication system as claimed in claim 2 is characterized in that, further comprises:

Network requests node decision the carrying out carrying of load bearing deactivation generates the load bearing deactivation request;

Described load bearing deactivation request is sent to the network decision node.

4, the method for realization load bearing deactivation of mobile communication system as claimed in claim 3 is characterized in that, described method is specially:

Described network decision node receives described load bearing deactivation request;

If when described network decision node determines that described bearer types is the last item default bearer, call the attachment removal flow process of this network decision node and carry out load bearing deactivation.

5, the method for realization load bearing deactivation of mobile communication system as claimed in claim 3 is characterized in that, described method is specially:

When if described network decision node determines that described bearer types is default bearer,, then load bearing deactivation is carried out in all carryings if accept described load bearing deactivation request; If do not accept described load bearing deactivation request, then refuse described load bearing deactivation request.

6, the method for realization load bearing deactivation of mobile communication system as claimed in claim 3 is characterized in that, described method is specially:

If when described network decision node determined that described bearer types is dedicated bearing, all dedicated bearings that default bearer is associated carried out load bearing deactivation.

7, as the method for each described realization load bearing deactivation of mobile communication system of claim 4 to 6, it is characterized in that, described load bearing deactivation request comes from UMTS, and when described load bearing deactivation request is sent to fringe node SGSN between UMTS and the SAE or gateway, the load bearing deactivation request of UMTS is converted to the load bearing deactivation request of SAE.

8, as the method for each described realization load bearing deactivation of mobile communication system of claim 4 to 6, it is characterized in that, described load bearing deactivation request comes from SAE, and described load bearing deactivation request be sent between UMTS and the SAE fringe node SGSN or during gateway, the load bearing deactivation request of SAE is converted to the load bearing deactivation request of UMTS.

9, the method for realization load bearing deactivation of mobile communication system as claimed in claim 7 is characterized in that, the load bearing deactivation request step that described load bearing deactivation request with UMTS is converted to SAE is specially:

If described load bearing deactivation request contains when all carryings are carried out load bearing deactivation, the required parameter in the load bearing deactivation request of UMTS system is added in the load bearing deactivation request of SAE system.

10, the method for realization load bearing deactivation of mobile communication system as claimed in claim 7 is characterized in that, the load bearing deactivation request step that described load bearing deactivation request with UMTS is converted to SAE is specially:

If described load bearing deactivation request contains when all carryings are carried out load bearing deactivation, the required parameter in the load bearing deactivation request of UMTS system is converted to pairing required parameter in the load bearing deactivation request of SAE system.

11, the method for realization load bearing deactivation of mobile communication system as claimed in claim 5 is characterized in that, described network decision node is carried out the load bearing deactivation step with all carryings and is specially:

If when described network decision node determines that described bearer types is default bearer, at first dedicated bearing is carried out load bearing deactivation, at last default bearer is carried out load bearing deactivation.

12, the method for realization load bearing deactivation of mobile communication system as claimed in claim 6, it is characterized in that, if described load bearing deactivation request is during from the SAE system, when the network decision node determines that described load bearing deactivation type is dedicated bearing, pairing this dedicated bearing of described SAE system is carried out load bearing deactivation.

13, a kind of network node is characterized in that, comprising:

14, a kind of network node is characterized in that, comprising:

15, network node as claimed in claim 14, it is characterized in that, described network node also comprises a converting unit, described converting unit is used to realize the load bearing deactivation request conversion between UMTS and the SAE, the load bearing deactivation request of SAE is converted to the load bearing deactivation request of UMTS, or the load bearing deactivation request of UMTS is converted to the load bearing deactivation request of SAE.

16, a kind of network system of load bearing deactivation of mobile communication system is characterized in that, described network system comprises network requests node and network decision node, wherein:

Described network requests node is used to determine to carry out the carrying of load bearing deactivation, generates the load bearing deactivation request, and the load bearing deactivation request that generates is sent to the network decision node.

17, network system as claimed in claim 16 is characterized in that, described network system is across a network system or the SAE system of UTMS and SAE.

As claim 16 or 17 described network systems, it is characterized in that 18, described network decision node determines to carry out the bearer types of load bearing deactivation, described network decision node is subscriber equipment or the SGSN in the UTMS system; Or

Described network decision node is gateway, the grouped data network gateway in the SAE system.

19, network system as claimed in claim 18 is characterized in that, the carrying of load bearing deactivation is carried out in described network requests node decision, and described network requests node is subscriber equipment or the SGSN in the UTMS system; Or

Described network requests node is subscriber equipment, Mobility Management Entity, gateway, strategy and charging regulation module, the grouped data network gateway in the SAE system.