CN101197817A - Method for updating packet data protocol context - Google Patents
Method for updating packet data protocol context Download PDFInfo
- Publication number
- CN101197817A CN101197817A CNA2006101618717A CN200610161871A CN101197817A CN 101197817 A CN101197817 A CN 101197817A CN A2006101618717 A CNA2006101618717 A CN A2006101618717A CN 200610161871 A CN200610161871 A CN 200610161871A CN 101197817 A CN101197817 A CN 101197817A
- Authority
- CN
- China
- Prior art keywords
- pdp context
- ggsn
- sgsn
- tunnel
- rnc
- 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.)
- Pending
Links
Images
Landscapes
- Mobile Radio Communication Systems (AREA)
Abstract
The invention discloses a method for updating the context of a packet data protocol, which is used, in a one-tunnel architecture, PDPs in one-tunnel mode. The method comprises the step that when requiring updating the context, an SGSN sends a mobile station (MS) identifier to a GGSN which consequently uses the received MS identifier to position the context of the PDP and to update the information in the context of the PDP. As a result, errors of location of the context of the PDP can be avoided, even if the context of the PDP is not available on the GGSN, thereby the SGSN can notice the uncommon condition of an upstream tunnel failure on a user plane between an access network and a core network, thereby avoiding the errors of data forwarding, accounting, etc. The method of the invention, compared with the prior method, requires no upgrading of RNC, thereby easily avoiding the technical problem due to the data upstream tunnel failure on a user plane between the access network and the core network, saving labor and money.
Description
Technical field
The present invention relates to moving communicating field, refer to especially a kind of under tunnel (OneTunnel/Direct Tunnel) framework of single tunnel/directly, the contextual method of update packet data protocol (PDP, Packet DataProtocol).
Background technology
Along with HRPD (high rate packet data) inserts (HSPA, High Speed Packet Access) and IP Multimedia System (IMS, IP Multimedia Subsystem) introduce third generation collaborative project (3GPP) network, user plane data traffic has bigger growth.In order to improve the network investment of 3GPP data transmission in network performance and minimizing operator, the 3GPP tissue proposes the network architecture of One Tunnel/Direct Tunnel, and this paper is designated hereinafter simply as One Tunnel.
In the One Tunnel network architecture, by the radio network controller (RNC in Access Network, Radio Network Controller) and the Gateway GPRS Support Node (GGSN in the core net, Gateway GPRS Support Node) directly sets up user's face tunnel between, replace existing RNC and Serving GPRS Support Node (SGSN, Serving GPRS Support Node) and two sections tunnels setting up between SGSN and the GGSN, peeled off the user plane functions of SGSN node, increased investment the dilatation of SGSN user's face thereby saved network user's surface current amount that operator brings for reply HSPA.
Fig. 1 is the schematic diagram of existing a kind of One Tunnel framework, as shown in Figure 1, for reduce influence as far as possible to existing network, SGSN still keeps the function as the user's face under the scenes such as roamer, prepaid user, promptly under aforementioned scene, in order to reduce change to GGSN, can not adopt the OneTunnel mode to set up user's face, set up user's face and continue to use traditional approach.Therefore, shown in heavy line among Fig. 1, the most of flow of user's face adopts One Tunnel directly to arrive GGSN through RNC, and shown in fine line among Fig. 1, the fraction flow still from RNC via SGSN to GGSN.
In the 3GPP system, portable terminal (MS) must activate the bearer channel that PDP sets up the transmission data before carrying out data service.After activating the PDP success, in the SGSN of the RNC of MS, Access Network, core net and GGSN, all set up corresponding user's face context.For MS, user's face context comprises a PDP Context, includes the information of a corresponding RAB (RAB, Radio Access Bearer) in this PDP Context; For RNC, user's face context has only a RAB; SGSN and MS be equity fully, also is a PDP Context, and comprises the information of a RAB; For GGSN, user's face context then is a PDP Context, but does not comprise the information of RAB.
Transfer of data between user's face of Access Network and core net adopts GPRS Tunnel Protocol (GTP, GPRS Tunneling Protocol) technology.When GTP tunnel one end is received the grouped data that send the opposite end, can navigate to user's face context according to tunnel end sign (TEID, the Tunnel End ID) information in the outer field GTP head of grouped data, again according to the routing iinformation of preserving in user's face context, forwarding packet data.Because node reset or other abnormal conditions, the node of GTP tunnel one end may discharge user's face context, like this, when it receives from the data that send the GTP tunnel opposite end, be that can't to navigate to corresponding user's face contextual, thereby can't normally transmit the grouped data of receiving, the data of receiving can only be abandoned.Simultaneously, according to the GTP protocol requirement, receive that the GTP packet but can't the contextual network node of consumer positioning face, also will send miscue (Error Indication) message to the opposite end, notice tunnel, opposite end lost efficacy, and did not send data to this tunnel again.
According to code requirement, receive the network element node of miscue message, can discharge corresponding user's face context usually.Fig. 2 a is the flow chart that existing GGSN handles wrong indication, shown in Fig. 2 a, may further comprise the steps:
Step 200a:GGSN sends downlink data (DownLink Data) to SGSN.
In this step, after GGSN receives user's downlink data, navigate to corresponding PDP Context, and, downlink data is carried out the GTP encapsulation and sends to corresponding GTP tunnel according to the routing iinformation in this PDP Context.
Step 201a:SGSN receives downlink data, if the consumer positioning face is transmitted the PDP Context failure, is that GGSN returns miscue message to the GTP tunnel source end that sends this GTP packet then.
After step 202a:GGSN receives wrong Indication message, delete the promptly corresponding PDP Context of user's face context of the correspondence of self storing.
Fig. 2 b is the flow chart that existing RNC handles wrong indication, shown in Fig. 2 a, may further comprise the steps:
Step 200b:RNC sends upstream data (UpLink Data) to SGSN.
In this step, after RNC receives user's upstream data, navigate to corresponding RAB, and, the up certificate of number is carried out the GTP encapsulation and sent to corresponding GTP tunnel according to the routing iinformation in the PDP Context of preserving.
Step 201b:SGSN receives up GTP packet, if the failure of consumer positioning face forwarding contexts is that RNC returns miscue message to the GTP tunnel source end that sends this GTP packet then.
After step 202b:RNC receives wrong Indication message, discharge the promptly corresponding RAB of user's face context of self correspondence.
As mentioned above, under One Tunnel framework, the tunnel of user's face only is based upon a section between RNC and the GGSN.Because unusually as resetting, discharged user's face context, the RNC and the uplink tunnel between the GGSN that can cause being correlated with lost efficacy as GGSN.After the uplink tunnel inefficacy that occurs between Access Network and the core net, all can trigger SGSN usually and initiate the process of renewal PDP Context to GGSN, this process roughly comprises:
SGSN sends to GGSN and upgrades PDP Context request (Update PDP Context Request) message, initiates the PDP context modification process.Carry the user plane information of need upgrading in this renewal PDP Context request message, such as the IP address of downlink tunnel, TEID, service quality (QoS) information etc.; After GGSN receives and upgrades the PDP Context request message, extract the effective information that upgrades in the PDP Context request message, upgrade the information in the PDP Context corresponding with TEID, and return and carry the renewal PDP Context response (Update PDP Context Response) of upgrading the result, if upgrade failure, then return the renewal PDP Context response of carrying failure cause.
Protocol specification according to GTP V1 version, in the cell that upgrades the PDP Context request message, user's permanent identification (IMSI) is that condition is optional, have only when not having in the GTP message header effectively to identify the TEID of PDP Context, SGSN just can carry IMSI in upgrading the PDP Context request message, so that GGSN locatees PDP Context according to IMSI, and usually, GGSN utilizes the corresponding PDP Context in TEID location in the GTP head that upgrades the PDP Context request message.
Because GGSN can guarantee that the TEID that distributes under same user's face IP address is unique, therefore, locating PDP Context by TEID under the normal condition is mistake can not occur.But, under the situation of user's face upstream data tunnel failure, owing to discharged PDP Context unusually on the GGSN, originally the GGSN IP address, chain of command tunnel and the TEID that distribute to this PDP Context may distribute to other newly-established PDP Context again, like this, GGSN only locatees PDP Context according to the TEID in the GTP head that upgrades the PDP Context request message and following two kinds of results may occur:
(1) location is less than PDP Context.At this moment, GGSN returns the failure cause that shows user's face uplink tunnel inefficacy between Access Network and the core net and gives SGSN, the existence that SGSN is just noted abnormalities, thus notice MS carries out deexcitation PDP Context process;
(2) location of mistake is to other PDP Context.Because IP address, chain of command tunnel and TEID that original GGSN distributes to this PDP Context distribute to other newly-established PDP Context again, make GGSN upgrade the information of other user's PDP Context mistakenly, thereby cause the data forwarding mistake, the consequence that billing error etc. are serious.
In sum, under One Tunnel framework, because the uplink tunnel inefficacy between RNC and the GGSN can cause the inconsistent of user's face contextual information on each network entity of MS, RNC, SGSN and GGSN: the PDP Context in the last corresponding fail data of GGSN tunnel is released; The RAB in the last corresponding fail data of RNC tunnel is released; The last corresponding PDP Context of MS also exists, but the RAB information that wherein comprises is disarmed state; The last corresponding PDP Context of SGSN still exists, and the RAB information that wherein comprises also is effective status.And these are inconsistent, and especially PDP Context inconsistent between SGSN and the GGSN upgrades the process of PDP Context among the GGSN and brought security breaches to SGSN.
In addition, owing to do not have user's face data tunnel between SGSN and the GGSN, have only the tunnel of chain of command, like this, the unusual release of PDP Context among the GGSN is in time found in the miscue that SGSN can not adopt the detection mechanism that provides by user's face GTP tunnel in the traditional network architecture or GGSN to return.Simultaneously, receive the miscue of GGSN at RNC after, after discharging the RAB of the correspondence of self storing, can only initiate service request or RNC initiation Iu connection dispose procedure by MS, trigger SGSN and initiate to upgrade the PDP Context process, thereby finally detect the abnormal conditions that GGSN has discharged PDP Context to GGSN.But as previously mentioned, because SGSN in the renewal PDP Context request that GGSN sends, does not normally carry IMSI's, at this moment, the PDP Context that SGSN upgrades among the GGSN may bring potential safety hazard on the contrary, causes more abominable consequences such as billing error.
In order to address the above problem, present solution mainly is after RNC receives from the indication of the mistake of GGSN, RNC judges it is when adopting user's face that One Tunnel mode sets up, and takes place unusually with specific reasons notice SGSN, and MS initiates deexcitation PDP Context process by the SGSN notice.Whether this scheme needs RNC can distinguish user's face context to adopt One Tunnel mode to set up, and after the mistake indication of receiving GGSN, on the local method basis that discharges RAB at present, further notifies SGSN.That is to say that RNC must carry out software upgrading in order to support the processing after user's face uplink tunnel lost efficacy between the Access Network and core net under the One Tunnel framework.Outside, for supporting One Tunnel framework, also need the Iu interface netting mode between RNC and the GGSN is changed, be to realize between RNC and the GGSN that IP can reach, for this reason, or RNC upgrading support Iu interface IPization, or between RNC and GGSN, dispose the ip router of supporting that ATM inserts, as shown in Figure 3, Fig. 3 is the One Tunnel configuration diagram of disposing the ip router of supporting ATM between RNC and the GGSN.Could set up the GTP tunnel of user's face like this between RNC and the GGSN, heavy line represents to transmit single tunneling data among Fig. 3.
In the practical application, the network evolution scheme is different because of operator, the wireless access network of at present a lot of networks has been upgraded and has been supported HSPA technology and Iu interface IPization, perhaps plan to support the ip router of ATM to support One Tunnel by disposing, for these networks, if introduce One Tunnel framework, will need upgrade to RNC just to solving technical problems such as the data forwarding mistake brought because of user's face upstream data tunnel failure between Access Network and the core net and billing error.And RNC is in network in the Access Network, and quantity is many, and the upgrading difficulty to RNC can expend a large amount of manpower and financial resources, realizes that difficulty is bigger.
Summary of the invention
In view of this, main purpose of the present invention is to provide a kind of method of update packet data protocol contexts, can avoid technical problems such as the data forwarding mistake brought because of user's face upstream data tunnel failure between Access Network and the core net and billing error simply.
For achieving the above object, technical scheme of the present invention specifically is achieved in that
A kind of method of update packet data protocol PDP Context, under single tunnel/direct tunnel OneTunnel/Direct Tunnel framework, for the PDP Context that adopts single tunnel style to set up, this method may further comprise the steps:
A. Serving GPRS Support Node SGSN sends to Gateway GPRS Support Node GGSN with the mobile terminal MS sign when PDP Context is upgraded in request;
B.GGSN utilizes the MS mark location PDP Context receive and upgrades information in this PDP Context.
As seen from the above technical solution, under One Tunnel framework, when SGSN of the present invention upgrades PDP Context in request, the MS sign is sent to GGSN, GGSN utilizes the MS mark location PDP Context that receives and upgrades information in this PDP Context.Like this, even the situation of GGSN location of mistake PDP Context occurs, because SGSN is when PDP Context is upgraded in request in the inventive method, the MS sign has been sent to GGSN, GGSN can further utilize MS sign to determine the correctness of the PDP Context that navigated to by TEID, avoided location of mistake to PDP Context, guaranteed that SGSN can find the existence of the abnormal conditions that user's face uplink tunnel lost efficacy between Access Network and the core net, initiate deexcitation PDP Context flow process, the PDP Context of notice MS deexcitation correspondence, SGSN self also discharges corresponding PDP Context.Afterwards,, can activate PDP again, like this, avoid consequences such as data forwarding mistake, billing error if MS need carry out data service.
The inventive method is compared with existing method, does not need RNC is upgraded, and has avoided the technical problem brought because of user's face upstream data tunnel failure between Access Network and the core net simply, has saved manpower and financial resources.
Description of drawings
Fig. 1 is the schematic diagram of existing a kind of One Tunnel framework;
Fig. 2 a is the flow chart that existing GGSN handles wrong indication;
Fig. 2 b is the flow chart that existing RNC handles wrong indication;
Fig. 3 is the One Tunnel configuration diagram of disposing the ip router of supporting ATM between RNC and the GGSN;
Fig. 4 is the flow chart that SGSN of the present invention upgrades PDP Context;
Fig. 5 is the flow chart that Iu of the present invention connects the embodiment that discharges;
Fig. 6 is the flow chart that MS of the present invention rebuilds the embodiment of RAB.
Embodiment
Core concept of the present invention is: when SGSN upgrades PDP Context in request, the MS sign is sent to GGSN, GGSN utilizes the MS mark location PDP Context that receives and upgrades information in this PDP Context.
For making purpose of the present invention, technical scheme and advantage clearer, below with reference to the accompanying drawing preferred embodiment that develops simultaneously, the present invention is described in more detail.
Fig. 4 is the flow chart that SGSN of the present invention upgrades PDP Context, and as shown in Figure 4, the inventive method may further comprise the steps:
Step 400:SGSN sends the renewal PDP Context request message that carries the MS sign to GGSN.
In this step, upgrade carrying the user plane information that needs renewal in the PDP Context request message, such as IP address, TEID, the QoS etc. of downlink tunnel, and the MS sign is as IMSI.
Step 401:GGSN upgrades the information in the corresponding PDP Context, returns and upgrades the PDP Context response.
In this step, even GGSN navigates to PDP Context according to TEID, also need further to check the MS sign of this PDP Context correspondence as IMSI whether with renewal PDP Context request message in carry consistent, if consistent, then will upgrade the result and upgrade successful indication being carried at the renewal PDP Context and returning to SGSN in responding; If it is inconsistent, then determine not navigate to PDP Context, GGSN returns and shows that corresponding PDP Context is that the failure cause that user's face uplink tunnel lost efficacy between Access Network and the core net is given SGSN not existing on the GGSN, make SGSN find the existence of the abnormal conditions that user's face uplink tunnel lost efficacy between Access Network and the core net, thereby notify MS to carry out deexcitation PDP Context process.
The TEID no-fix of carrying in according to described renewal PDP Context request message at described GGSN is during to PDP Context, consistent with existing method, GGSN returns and shows that corresponding PDP Context is that the failure cause that user's face uplink tunnel lost efficacy between Access Network and the core net is given SGSN not existing on the GGSN.
Need to prove, in this step, also can directly adopt the MS sign to locate PDP Context as IMSI, promptly search with upgrade the PDP Context request message in the consistent PDP Context of MS sign that carries, if find, the then normal corresponding information that upgrades the PDP Context that navigates to, and will upgrade successful result's indication and be carried at the renewal PDP Context and return to SGSN in responding; If do not find, then determine not navigate to PDP Context, GGSN returns to SGSN and shows corresponding PDP Context non-existent failure cause on GGSN.
From step 401 as seen, under One Tunnel framework, even the situation of GGSN location of mistake PDP Context occurs, because SGSN is when PDP Context is upgraded in request in the inventive method, the MS sign has been sent to GGSN, GGSN can further utilize MS sign to determine the correctness of the PDP Context that navigated to by TEID, avoided location of mistake to PDP Context, guaranteed that SGSN can find the existence of the abnormal conditions that user's face uplink tunnel lost efficacy between Access Network and the core net, initiate deexcitation PDP Context flow process, the PDP Context of notice MS deexcitation correspondence, SGSN self also discharges corresponding PDP Context.Afterwards,, can activate PDP again, like this, avoid consequences such as data forwarding mistake, billing error if MS need carry out data service.
The inventive method is compared with existing method, does not need RNC is upgraded, and has avoided the technical problem brought because of user's face upstream data tunnel failure between Access Network and the core net simply, has saved manpower and financial resources.
Further, under One Tunnel framework, set up the PDP of user's face for One Tunnel mode, the RAB that uplink tunnel inefficacy between RNC and the GGSN can cause RNC to go up corresponding fail data tunnel is released, though and corresponding PDP Context exists on the MS, the RAB information that wherein comprises is disarmed state.
After RAB discharged, if corresponding MS does not have other RAB to be present on the RNC, the RNC further decision Iu that discharges this MS connected, and set up the PDP of user's face for One Tunnel mode, will trigger SGSN and initiate renewal PDP Context process to GGSN.Fig. 5 is the flow chart that Iu of the present invention connects the embodiment that discharges, and as shown in Figure 5, Iu connects dispose procedure and may further comprise the steps:
Step 500:RNC sends Iu to SGSN and connects the request of discharging (Iu Release Request).
Step 501a～step 501b: set up the PDP of user's face for One Tunnel mode, SGSN initiates to upgrade the PDP Context process, to rebuild the tunnel between SGSN and the GGSN.This step specific implementation no longer repeats as shown in Figure 4 here.
It is emphasized that SGSN initiates deexcitation PDP Context flow process so if the corresponding PDP Context of the renewal that GGSN returns response indication does not exist, notice MS deexcitation PDP Context, SGSN self also discharges corresponding PDP Context.Avoided location of mistake, guaranteed that SGSN can find the existence of the abnormal conditions that user's face uplink tunnel lost efficacy between Access Network and the core net, has avoided consequences such as data forwarding mistake, billing error PDP Context.
Step 502:SGSN sends Iu to RNC and connects release command (Iu Release Command), and notice RNC discharges Iu and connects.
Step 503～step 504: also exist corresponding Radio Resource control (RRC) to connect if discharge the Iu connection, RNC notice MS discharges this RRC and connects (Release RRC connection), and MS returns and discharges RRC connection affirmation (Release RRC connection Ack).
Step 505:RNC sends Iu connection release to SGSN and finishes (Iu Release Completion) message, and notice SGSN finishes Iu and connects dispose procedure.
Another kind of situation is, after RAB is released, if also there is other RAB in corresponding MS, so, RNC can not initiate Iu and connect dispose procedure, but, guarantee that SGSN can find the existence of the abnormal conditions that user's face uplink tunnel lost efficacy between Access Network and the core net by MS deexcitation PDP Context process or RAB process of reconstruction.
Wherein, after MS carried out deexcitation PDP Context process, no longer there were corresponding user's face context in MS, SGSN and RNC, also just do not have contextual inconsistent problem.Follow-uply activate PDP again before portable terminal need transmit data, like this, user's face uplink tunnel Problem of Failure is also just eliminated immediately between Access Network and the core net, and this and existing realization are in full accord.
For rebuilding the RAB process, Fig. 6 is the flow chart that MS of the present invention rebuilds the embodiment of RAB, and as shown in Figure 6, among the present invention, MS rebuilds RAB and may further comprise the steps:
Step 600～step 602:MS sends RRC to RNC and connects foundation (RRC ConnectionSetup) message, and request RNC sets up RRC and connects.MS sends service request (ServiceRequest) message to SGSN, and the request core net is that MS self rebuilds RAB.In the service request procedure, can also comprise that SGSN carries out security process, to MS authentication or startup encryption etc.
This step belongs to prior art, and specific implementation can no longer describe in detail here referring to related protocol.
Step 603: the PDP that sets up user's face for One Tunnel mode, SGSN initiates PDP context modification (SGSN-Initiated PDP Context Modification) process, the IMSI that comprises the user is to check corresponding PDP normal presence whether on GGSN.This step specific implementation no longer repeats as shown in Figure 4 here.
It is emphasized that SGSN initiates deexcitation PDP Context flow process so if the corresponding PDP Context of the renewal that GGSN returns response indication does not exist, notice MS deexcitation PDP Context, SGSN self also discharges corresponding PDP Context.Avoided location of mistake, guaranteed that SGSN can find the existence of the abnormal conditions that user's face uplink tunnel lost efficacy between Access Network and the core net, has avoided consequences such as data forwarding mistake, billing error PDP Context.If carried out the PDP Context process of deexcitation here, then withdraw from the flow process of present embodiment.
This step can be omitted.
Step 604: for all PDP Contexts that are in state of activation, SGSN initiates RAB to RNC and sets up (RAB Setup Procedure) process, and indication RNC finishes the foundation of RAB.
If the user's face that adopts One Tunnnel mode to set up, the initiation RAB that SGSN issues sets up user's face IP address and the TEID that carries GGSN in the message.
Step 605: if SGSN is the service request that receives under connection status from MS, then SGSN sends service to MS and accepts (Service Accept) message.
Step 606: if variation has taken place the QoS of the RAB that sets up in the step 604, according to the agreement regulation, SGSN can initiate the PDP context modification process to GGSN, notifies the QoS after MS and GGSN change respectively.
Set up the PDP of user's face for adopting One Tunnel mode, SGSN also needs to initiate the PDP context modification process to GGSN, the IP address and the TEID of the downlink data tunnel of RNC distribution are notified to GGSN, provide an One Tunnel to indicate to GGSN simultaneously, what the employing of newly-established tunnel was described is One Tunnel mode.
Set up the PDP of user's face for One Tunnel mode, if there is not execution in step 603 before the SGSN, then SGSN also need carry user ID such as IMSI in the renewal PDP Context request that sends to GGSN, like this, if the corresponding PDP Context of the renewal that GGSN returns response indication does not exist, SGSN initiates deexcitation PDP Context flow process so, notice MS deexcitation PDP Context, and SGSN self also discharges corresponding PDP Context.Avoided location of mistake, guaranteed that SGSN can find the existence of the abnormal conditions that user's face uplink tunnel lost efficacy between Access Network and the core net, has avoided consequences such as data forwarding mistake, billing error PDP Context.
Equally, if the corresponding PDP Context of the renewal that GGSN returns in this step response indication does not exist, then SGSN initiates the PDP Context flow process of deexcitation, withdraws from the flow process of present embodiment afterwards.
Certainly, no matter whether step 603 is carried out, and can set up RAB, and when perhaps the service quality QoS of the RAB that foundation is good changed, execution in step 606 promptly adopted method shown in Figure 4 to revise PDP Context.
Step 607:MS sends ascending packet data by setting up good RAB.
The above is preferred embodiment of the present invention only, is not to be used to limit protection scope of the present invention, all any modifications of being made within the spirit and principles in the present invention, is equal to replacement, improvement etc., all should be included within protection scope of the present invention.
Claims (11)
1. the method for a update packet data protocol PDP Context, under the tunnel OneTunnel/Direct Tunnel framework of single tunnel/directly, the PDP Context for adopting single tunnel style to set up is characterized in that this method may further comprise the steps:
A. Serving GPRS Support Node SGSN sends to Gateway GPRS Support Node GGSN with the mobile terminal MS sign when PDP Context is upgraded in request;
B.GGSN utilizes the MS mark location PDP Context receive and upgrades information in this PDP Context.
2. method according to claim 1 is characterized in that, comprises before this method: radio network controller (RNC) sends Iu to described SGSN and connects the request of release.
3. method according to claim 1 is characterized in that, comprises before this method: described MS sends the radio resource control RRC connection to RNC and sets up message, and request RNC sets up RRC and connects; Described MS sends service request information to SGSN, and the request core net is rebuild RAB RAB for self.
4. method according to claim 3 is characterized in that, after the described step B, this method also comprises: described SGSN initiates RAB to RNC and sets up process and set up RAB;
Change if set up the service quality QoS of good RAB, and GGSN described in the step B utilizes the MS mark location PDP Context that receives, then described SGSN upgrades PDP Context according to the existing procedure request.
5. method according to claim 1 is characterized in that, comprises before this method: described SGSN initiates RAB to RNC and sets up process; Setting up RAB, execution in step A when perhaps the service quality QoS of the RAB that foundation is good changes.
6. according to claim 1,2,3 or 5 described methods, it is characterized in that described MS sign is carried to be upgraded in the PDP Context request message.
7. method according to claim 6 is characterized in that, described step B specifically comprises:
When the tunnel end sign TEID that described GGSN carries in according to described renewal PDP Context request message navigates to PDP Context, the MS sign that GGSN judges the PDP Context correspondence navigate to whether with upgrade the PDP Context request message in carry consistent, if it is consistent, the then normal corresponding information that upgrades the PDP Context that navigates to, and will upgrade successful result's indication and be carried at the renewal PDP Context and return to SGSN in responding; If inconsistent, then determine not navigate to PDP Context, GGSN returns to SGSN and shows corresponding PDP Context non-existent failure cause on GGSN.
8. method according to claim 7, it is characterized in that, this method also comprises: the TEID no-fix of carrying in according to described renewal PDP Context request message at described GGSN is during to PDP Context, and GGSN returns and shows that corresponding PDP Context non-existent failure cause on GGSN gives SGSN.
9. method according to claim 6 is characterized in that, described step B specifically comprises:
Described GGSN search with upgrade the PDP Context request message in the consistent PDP Context of MS sign that carries, if find, the then normal corresponding information that upgrades the PDP Context that navigates to, and will upgrade successful result's indication and be carried at the renewal PDP Context and return to SGSN in responding; If do not find, then determine not navigate to PDP Context, GGSN returns to SGSN and shows corresponding PDP Context non-existent failure cause on GGSN.
10. according to claim 7,8 or 9 described methods, it is characterized in that, this method also comprises: described SGSN learns that corresponding PDP Context is not after existing on the GGSN, notice MS carries out deexcitation PDP Context process, and simultaneously described SGSN discharges the PDP Context of the corresponding described MS that self stores.
11. method according to claim 1 is characterized in that, described MS is designated user's permanent identification IMSI.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNA2006101618717A CN101197817A (en) | 2006-12-05 | 2006-12-05 | Method for updating packet data protocol context |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNA2006101618717A CN101197817A (en) | 2006-12-05 | 2006-12-05 | Method for updating packet data protocol context |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN101197817A true CN101197817A (en) | 2008-06-11 |
Family
ID=39547967
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CNA2006101618717A Pending CN101197817A (en) | 2006-12-05 | 2006-12-05 | Method for updating packet data protocol context |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101197817A (en) |
Cited By (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2010063236A1 (en) * | 2008-12-02 | 2010-06-10 | 华为技术有限公司 | Communication network, communication apparatus and communication method |
| CN101997836A (en) * | 2009-08-13 | 2011-03-30 | 西门子（中国）有限公司 | Method and device for operating packet data protocol context |
| WO2011063543A1 (en) * | 2009-11-24 | 2011-06-03 | Telefonaktiebolaget L M Ericsson (Publ) | Overcharging prevention by unsent downlink data volume record technical field |
| WO2012103756A1 (en) * | 2011-02-01 | 2012-08-09 | 中兴通讯股份有限公司 | Method for obtaining a terminal context, method for location management, system and network element |
| WO2012126320A2 (en) * | 2012-03-09 | 2012-09-27 | 华为技术有限公司 | Method, device and system for processing abnormal data transmission |
| CN101753638B (en) * | 2009-12-08 | 2013-08-14 | 华为技术有限公司 | Control method, device and communication system of direct tunnel |
| CN103369710A (en) * | 2012-03-31 | 2013-10-23 | 中国移动通信集团公司 | Method, system and device for establishing direct tunnel |
| CN103491575A (en) * | 2012-04-17 | 2014-01-01 | 特克特朗尼克公司 | Session-aware gtpv1 load balancing |
| CN110024423A (en) * | 2016-11-30 | 2019-07-16 | 华为技术有限公司 | A kind of processing method of error indication, equipment and system |
-
2006
- 2006-12-05 CN CNA2006101618717A patent/CN101197817A/en active Pending
Cited By (19)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2010063236A1 (en) * | 2008-12-02 | 2010-06-10 | 华为技术有限公司 | Communication network, communication apparatus and communication method |
| US8854968B2 (en) | 2008-12-02 | 2014-10-07 | Huawei Technologies Co., Ltd. | Communication network, device, and method |
| CN101997836A (en) * | 2009-08-13 | 2011-03-30 | 西门子（中国）有限公司 | Method and device for operating packet data protocol context |
| WO2011063543A1 (en) * | 2009-11-24 | 2011-06-03 | Telefonaktiebolaget L M Ericsson (Publ) | Overcharging prevention by unsent downlink data volume record technical field |
| CN102726020A (en) * | 2009-11-24 | 2012-10-10 | 爱立信(中国)通信有限公司 | Overcharging prevention by unsent downlink data volume record technical field |
| US8982790B2 (en) | 2009-11-24 | 2015-03-17 | Telefonaktiebolaget L M Ericsson (Publ) | Overcharging prevention by unsent downlink data volume record |
| CN101753638B (en) * | 2009-12-08 | 2013-08-14 | 华为技术有限公司 | Control method, device and communication system of direct tunnel |
| WO2012103756A1 (en) * | 2011-02-01 | 2012-08-09 | 中兴通讯股份有限公司 | Method for obtaining a terminal context, method for location management, system and network element |
| WO2012126320A2 (en) * | 2012-03-09 | 2012-09-27 | 华为技术有限公司 | Method, device and system for processing abnormal data transmission |
| WO2012126320A3 (en) * | 2012-03-09 | 2013-02-21 | 华为技术有限公司 | Method, device and system for processing abnormal data transmission |
| CN102742314B (en) * | 2012-03-09 | 2015-01-07 | 华为技术有限公司 | Method, device and system for processing abnormal data transmission |
| CN102742314A (en) * | 2012-03-09 | 2012-10-17 | 华为技术有限公司 | Method,device and system for processing abnormal data transmission |
| CN103369710A (en) * | 2012-03-31 | 2013-10-23 | 中国移动通信集团公司 | Method, system and device for establishing direct tunnel |
| CN103369710B (en) * | 2012-03-31 | 2016-12-14 | 中国移动通信集团公司 | A kind of set up the method for direct access, system and equipment |
| CN103491575A (en) * | 2012-04-17 | 2014-01-01 | 特克特朗尼克公司 | Session-aware gtpv1 load balancing |
| CN103491575B (en) * | 2012-04-17 | 2018-12-25 | 网络搜索系统德克萨斯有限责任公司 | Session perceives GTPv1 load balance |
| CN110024423A (en) * | 2016-11-30 | 2019-07-16 | 华为技术有限公司 | A kind of processing method of error indication, equipment and system |
| CN110024423B (en) * | 2016-11-30 | 2021-06-01 | 华为技术有限公司 | Error indication processing method, device and system |
| US11108734B2 (en) | 2016-11-30 | 2021-08-31 | Huawei Technologies Co., Ltd. | Error indication processing and system, and device |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101197817A (en) | Method for updating packet data protocol context | |
| CN101563948B (en) | Arrangement and method relating to direct tunnelling in connection with handover in a communications network | |
| US7283497B2 (en) | Method for transferring a tunnel between nodes in GPRS system | |
| CN100388816C (en) | Wlan as a logical support node for hybrid coupling in an interworking between wlan and a mobile communications system | |
| CN101422064B (en) | Fast handoff support for wireless networks | |
| CN102282889B (en) | Gateway relocation in communication networks | |
| CN101541097B (en) | Method, device and system for recovering bearing | |
| US8270942B2 (en) | Method for the interception of GTP-C messages | |
| EP2533481B1 (en) | Tunnel management method, tunnel management apparatus, and communications system | |
| CN101730072B (en) | Packet data web gateway identification saving method and system in multi-access scene | |
| CN101248629A (en) | Reserved bearing | |
| CN101547168A (en) | Equipment reset notification method and equipment reset notification system, service and grouped data gateway and mobile management network element | |
| CN105338653A (en) | Method and equipment supporting UE bearing recovery | |
| CN101588548A (en) | Method and system for accessing communication data and access gateway | |
| CN103747502A (en) | Method and system for processing GTP tunnel | |
| CN102036304B (en) | Method for providing maximum transmission unit length for terminal and packet switch gateway | |
| CN101300857A (en) | Radio bearer management in a cellular communication system | |
| US8116272B2 (en) | Method for dealing with the packet domain gateway support node errors | |
| CN105376814A (en) | Call preservation on handover | |
| US20110122839A1 (en) | Inter-bss packet-switched handover | |
| EP2061264B1 (en) | A method and system for acquiring that sgsn has started single tunnel by ggsn in a packet domain | |
| CN103428801B (en) | A kind of method and apparatus of realizing route management | |
| CN101415013B (en) | Method for identifying endpoint designation data packet | |
| CN103548413A (en) | System and method for preventing deadlock in direct tunnel release | |
| EP2320697B1 (en) | Method for switching msc-pool inter offices |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C02 | Deemed withdrawal of patent application after publication (patent law 2001) | ||
| WD01 | Invention patent application deemed withdrawn after publication |
Open date: 20080611 |