CN101369912B - Customer equipment context updating method and apparatus - Google Patents
Customer equipment context updating method and apparatus Download PDFInfo
- Publication number
- CN101369912B CN101369912B CN2007101202091A CN200710120209A CN101369912B CN 101369912 B CN101369912 B CN 101369912B CN 2007101202091 A CN2007101202091 A CN 2007101202091A CN 200710120209 A CN200710120209 A CN 200710120209A CN 101369912 B CN101369912 B CN 101369912B
- Authority
- CN
- China
- Prior art keywords
- context
- management entity
- mobility management
- 3gpp
- evolution system
- 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.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 40
- GVVPGTZRZFNKDS-JXMROGBWSA-N geranyl diphosphate Chemical compound CC(C)=CCC\C(C)=C\CO[P@](O)(=O)OP(O)(O)=O GVVPGTZRZFNKDS-JXMROGBWSA-N 0.000 claims description 44
- 230000004044 response Effects 0.000 claims description 24
- 238000012545 processing Methods 0.000 claims description 19
- 230000005540 biological transmission Effects 0.000 claims description 7
- 230000000977 initiatory effect Effects 0.000 claims description 4
- 230000008569 process Effects 0.000 abstract description 22
- 230000011664 signaling Effects 0.000 abstract description 12
- 238000007726 management method Methods 0.000 description 90
- 238000013475 authorization Methods 0.000 description 12
- 230000004048 modification Effects 0.000 description 3
- 238000012986 modification Methods 0.000 description 3
- 238000012790 confirmation Methods 0.000 description 2
- 238000012217 deletion Methods 0.000 description 2
- 230000037430 deletion Effects 0.000 description 2
- 238000010586 diagram Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 230000007246 mechanism Effects 0.000 description 2
- 238000004321 preservation Methods 0.000 description 2
- 244000061520 Angelica archangelica Species 0.000 description 1
- 235000001287 Guettarda speciosa Nutrition 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 230000008878 coupling Effects 0.000 description 1
- 238000010168 coupling process Methods 0.000 description 1
- 238000005859 coupling reaction Methods 0.000 description 1
- 238000013502 data validation Methods 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 230000000737 periodic effect Effects 0.000 description 1
Images
Abstract
The invention discloses a method and a device for a user equipment UE to update a context of the UE during the shift of the user equipment between a 3GPP evolution system and a non-3GPP system. When the UE moves from the 3GPP evolution system to the non-3GPP system, the UE context of the UE is stored through the UE context update of the UE, and the UE state is arranged to a deadhesion state, thereby the problem that the user information is simultaneous present in the 3GPP evolution system and the non-3GPP system of the UE is avoided. Moreover after the UE moves back to the 3GPP evolution system from the non-3GPP system, a mobile management entity uses the stored the UE context, accelerates the process for establishing bearing fro the UE, accordingly reduces the network signaling overhead, lightens the network burden, simultaneously guarantees the consistency of the UE bearings of switching to the 3GPP evolution system and bearing the service quality (QoS) in the 3GPP evolution system before the switching.
Description
Technical field
The present invention relates to communication technical field, relate in particular to a kind of subscriber equipment (User Equipment, UE) method and apparatus of updating context.
Background technology
The 3GPP evolution system (System Architecture Evolution, SAE) in, non-3 GPP system (Non-3GPP) system can and the SAE system dispose jointly, for the terminal use, then have between two kinds of different systems frequent mobile problem.Intercommunication between non-3 GPP system and the 3GPP evolution system is a kind of relation of loose coupling, and the mobile management between the system is based on the mechanism of IP layer.When UE moves back to the 3GPP evolution system again after the 3GPP evolution system moves to non-3 GPP system, need to guarantee the consistency of service quality (QoS) of all IP carryings of UE, the message data in the time of should reducing the authentication of UE is simultaneously as far as possible accelerated the process of authentication.
In traditional 3GPP system, packet data protocol (PDP, Packet Data Protocol) context only just needs to activate when having data to transmit, and periodic position update mechanism is arranged in traditional 3GPP system, can guarantee that UE deletes corresponding UE context (UEContext) when leaving the 3GPP system.But the 3GPP evolution system is different, when UE is registered to the 3GPP evolution system, UE will activate at least one default bearer (Default Bearer), and might activate one or more other special-purpose SAE carrying, accordingly, will be assigned with one or more IP address.When UE leaves the 3GPP evolution system and moves to a non-3 GPP system, owing to there is not corresponding process to notify the Mobility Management Entity of former 3GPP evolution system (Mobility Management Entity, MME), therefore Mobility Management Entity and do not know current UE to leave the 3GPP evolution system and moved to non-3 GPP system will cause user profile simultaneous situation in 3GPP evolution system and non-3 GPP system of this UE like this.
After UE finishes access process in non-3 GPP system, home subscriber server (HomeSubscriber Server, HSS) can know that UE accesses to non-3 GPP system from former 3GPP evolution system, and notify this subscriber equipment of Mobility Management Entity in the former 3GPP evolution system to leave the 3GPP evolution system, it is invalid that the contextual state of UE of this UE of this Mobility Management Entity is set to, and deletes the UE context of this subscriber equipment.
Correspondingly, after subscriber equipment moved back to the 3GPP evolution system from non-3 GPP system, what it was carried out in the 3GPP evolution system adhered to (Attach) process as shown in Figure 1.Among Fig. 1: step 1～2 are for after this UE moves back to the 3GPP evolution system, current mobile management entity in the 3GPP evolution system for UE service (below be called new Mobility Management Entity, new MME) sends and adhere to request, step 3～5th, the authorizing procedure of carrying out between UE, Mobility Management Entity, the home subscriber server.Because when aforementioned this UE moves to non-3 GPP system from former 3GPP evolution system, mobile management entity in the former 3GPP evolution system (below be called old Mobility Management Entity, old MME) the UE context of this UE be set to invalid, so when it retracts the ID that the stylish Mobility Management Entity of 3GPP system can only obtain this UE, be international mobile subscriber identification code (IMSI, International Mobile Subscriber Identity), can not obtain other relevant UE contextual informations.Therefore, this UE need carry out authentication again in the 3GPP evolution system, set up the UE context, comprising: authentication five-tuple (Authentication Quintets), carrying be (bearer contexts) etc. above, could rebulid carrying in the 3GPP evolution system then.
When new Mobility Management Entity receives that UE's adheres to when request (Attach Request) afterwards, owing to do not store the UE context of this UE in this stylish Mobility Management Entity, the authorization data that can only use home subscriber server to produce in the step 5 of Fig. 1 carries out authentication (Authentication) again to subscriber equipment.When subscriber equipment continually between 3GPP system and non-3GPP evolution system when mobile, just will strengthen the signaling consumption of system, increase network burden, can't guarantee simultaneously subscriber equipment move before and move after the consistency of the service quality (QoS, Quality ofService) of carrying when returning the 3GPP evolution system again.
Summary of the invention
The invention provides a kind of customer equipment context updating method and device, realize that the user uses a small amount of Signalling exchange to set up carrying fast when mobile between 3GPP evolution system and non-3 GPP system.
The invention provides a kind of customer equipment context updating method, comprising:
After user equipment (UE) moved to non-3 GPP system from the 3GPP evolution system, network side home subscriber server notice Mobility Management Entity carried out the contextual renewal of UE;
Mobility Management Entity upgrades the UE context and preserves;
After described UE moved back to the 3GPP evolution system from non-3 GPP system, the current contextual situation of UE of preserving described UE according to this locality for the Mobility Management Entity of UE service was carried out the attachment flow that this UE inserts the 3GPP evolution system.
Home subscriber server gets access to UE initiates register requirement in non-3 GPP system after, determines this UE and moves to non-3 GPP system from the 3GPP evolution system.
Mobility Management Entity upgrades the UE context, and specifically comprise: the state of this UE of Mobility Management Entity is set to the attachment removal state; And identify this UE and move in the non-3 GPP system.
Mobility Management Entity returns UE updating context acknowledge message to home subscriber server after upgrading the UE context.
After UE moves back to the 3GPP evolution system from non-3 GPP system, current Mobility Management Entity for UE service detects the UE context that this UE is preserved in this locality, and the attachment flow that this UE inserts the 3GPP evolution system carried out in the UE context of this UE that preserves according to this locality.
After UE moves back to the 3GPP evolution system from non-3 GPP system, current Mobility Management Entity for the UE service detects the local UE context of not preserving this UE, then from the Mobility Management Entity of last time, obtain the UE context of this UE, use the UE context that obtains to carry out the attachment flow that this UE inserts the 3GPP evolution system for this UE service.
Obtain the UE context of UE being the Mobility Management Entity of UE service from the last time, specifically comprise:
Current Mobility Management Entity of serving for this UE to the last time for the Mobility Management Entity of UE service sends Mobility Management Entity MME context request message;
Last Mobility Management Entity for this UE service returns the MME context response information, carries the UE contextual information of local this UE that preserves in context response information.
The present invention also provides a kind of customer equipment context updating device, comprising: receiving element, processing unit, updating block and memory cell;
Receiving element is used to receive the UE updating context message of home subscriber server transmission and be notified to processing unit;
Processing unit is used for according to the UE updating context message that receives, and the update notifications unit upgrades the UE context of this UE of storing in the memory cell;
Updating block, the UE context of this UE that is used for memory cell is preserved upgrades;
Memory cell is used to preserve the UE context of this UE.
Above-mentioned customer equipment context updating device also comprises transmitting element;
Receiving element also is used to receive the MME context request message, and is notified to described processing unit;
Processing unit also is used for notifying described transmitting element to obtain the UE context from described memory cell according to the MME context request message that receives;
Transmitting element is used to send the UE context to the entity of initiating the MME context request message.
Above-mentioned customer equipment context updating device also comprises:
Acquiring unit is used to initiate the MME context request message, and receives the MME context response information of returning, and obtains the UE context that carries in the MME context response information, and the UE context that gets access to is sent to memory cell.
Updating block also is used for returning the renewal acknowledge message to processing unit after carrying out the UE updating context;
After processing unit also is used to receive the renewal acknowledge message, send the renewal acknowledge message to home subscriber server by transmitting element.
The customer equipment context management devices is integrated in the Mobility Management Entity in the 3GPP evolution system.
The invention provides a kind of in the process that UE moves between 3GPP evolution system and non-3 GPP system, contextual update method of the UE of UE in the 3GPP evolution system and device.When UE when the 3GPP evolution system moves to non-3 GPP system, upgrade (the UE state is set to the attachment removal state) and preserve the UE context by UE context UE, after UE moves back to the 3GPP evolution system from non-3 GPP system, the UE context that current Mobility Management Entity for UE service can use this locality (or from the 3GPP evolution system in the last Mobility Management Entity for this UE service) to preserve carries out authentication and carrying foundation, saved that this UE need carry out authentication by home subscriber server again in the prior art in the 3GPP evolution system, and rebulid the contextual Signalling exchange flow process of UE, thereby accelerated to set up the process of carrying for this UE, correspondingly reduced the expense of network signal, alleviated network burden, simultaneously because UE is identical before moving back to the UE context that uses behind the 3GPP evolution system and moving, therefore guaranteed the carrying that UE sets up after moving back to the 3GPP evolution system and move before the consistency of the service quality (QoS) of carrying.
Description of drawings
Fig. 1 carries out the Signalling exchange flow chart that adheres to when UE is from the non-3 GPP system access 3 GPP evolution system in the prior art;
After the UE that Fig. 2 provides for the embodiment of the invention inserts non-3 GPP system from the 3GPP evolution system, UE updating context Signalling exchange flow chart;
Fig. 3 carries out one of Signalling exchange flow chart that adheres to for the UE that the embodiment of the invention provides when non-3GPP inserts the 3GPP evolution system;
The UE that Fig. 4 provides for the embodiment of the invention carries out two of the Signalling exchange flow chart that adheres to when non-3GPP inserts the 3GPP evolution system;
One of UE updating context apparatus structure schematic diagram that Fig. 5 A provides for the embodiment of the invention;
Two of the UE updating context apparatus structure schematic diagram that Fig. 5 B provides for the embodiment of the invention.
Embodiment
Below in conjunction with accompanying drawing, elaborate UE between 3GPP evolution system and non-3 GPP system in the moving process with specific embodiment, the process that the UE context (UE Context) of UE in the 3GPP evolution system upgrades.
Embodiment 1:
When UE moves to non-3 GPP system from the 3GPP evolution system, and after finishing access process in the non-3 GPP system, in non-3 GPP system, set up IP and connected by the S2a/S2b/S2c interface.At this moment, the UE context of this UE of preserving in the Mobility Management Entity in former 3GPP evolution system is upgraded, the Signalling exchange flow process of renewal is seen Fig. 2.
Before step of updating begins, in former 3GPP evolution system, set up carrying between UE and the PDN Gateway (PDN GW).
Step 2, UE initiate authentication and authorization (Authentication) process;
After step 3, the authentication and authorization success, authentication, authorization and accounting server (Authentication, Authorization and Accounting Server, AAA server) passes through Wx
*Interface is initiated registration process to home subscriber server, and the angelica client server receives that home subscriber server knows that this UE has moved to non-3 GPP system from the 3GPP evolution system after the registration message of authentication, authorization and accounting server transmission;
Step 4, home subscriber server Mobility Management Entity in former 3GPP system sends the message of new and old UE context (Update old UE context), and the notice Mobility Management Entity upgrades the state of this UE;
The state of step 5, above-mentioned this UE of Mobility Management Entity is set to the state of attachment removal (Detached), identifying UE simultaneously moves in the non-3 GPP system, preserve the UE context of this UE, return new and old UE context to home subscriber server then and confirm (Update old UE contextACK) message;
Step 6, home subscriber server send the message of confirming registration (ConfirmRegister) to authentication, authorization and accounting server;
Step 7, above-mentioned Mobility Management Entity send deleting bearing request (Delete Bearer Request) message to gateway (Serving GW) and PDN Gateway, and notification service gateway and PDN Gateway are deleted the carrying of this UE in former 3GPP evolution system;
Step 8, gateway and PDN Gateway send the message that deleting bearing responds to Mobility Management Entity, and the notice Mobility Management Entity has been finished the deleting bearing operation.
When UE when non-3 GPP system moves back to the 3GPP evolution system, need to carry out and adhere to (Attach) process.In the 3GPP evolution system, current Mobility Management Entity for UE service receive that this UE sends adhere to request (Attach Request) message after, this Mobility Management Entity can be checked the local UE context of whether preserving this UE, and following two kinds of situations can appear in this moment:
First kind of situation, if the Mobility Management Entity and the UE that when UE leaves the 3GPP evolution system are the UE service are that the Mobility Management Entity management that UE serves is same Mobility Management Entity when non-3 GPP system moves back to the 3GPP evolution system, so in this Mobility Management Entity with regard to the UE context of in store this UE, can directly use the UE context of preserving in this Mobility Management Entity to proceed the attaching process of above-mentioned this UE in the 3GPP evolution system.Concrete attachment flow comprises as shown in Figure 3:
Step 2, eNodeB transmit this UE for the Mobility Management Entity of this UE service in the 3GPP evolution system the request of adhering to;
Check out the local UE context of preserving this UE for the Mobility Management Entity of this UE service in step 3, the 3GPP evolution system, then send identity request (Identity Request) message to this UE, UE returns identity response (Identity Response) message;
Carry out the authentication and authorization flow process between the Mobility Management Entity of step 4, UE, current service (MME), the user attaching server (HSS);
The Mobility Management Entity of step 5, current service sends deleting bearing request (Delete BearerRequest) message and gives gateway and PDN Gateway, the old carrying of this UE of request deletion, gateway and PDN Gateway have been deleted after the old carrying of this UE, return deleting bearing response (Delete BearerResponse) message and give the Mobility Management Entity of current service;
The Mobility Management Entity of step 6, current service sends to gateway and sets up default bearer request (Create Default Bearer Request) message, asks to set up default bearer for this UE;
Step 7, gateway send to PDN Gateway and set up default bearer request (Create DefaultBearer Request) message, and the request PDN Gateway is also set up default bearer for this UE;
Step 8, PDN Gateway and strategy and billing function entity (Policy and Charging RuleFunction, the Signalling exchange (PCRF Interaction) that carries out strategy and charging between PCRF);
Step 9, PDN Gateway are replied and are created default bearer response (Create Default Bearer Response) message to gateway;
Step 10, gateway send creates the Mobility Management Entity of default bearer response (Create Default Bearer Response) message to current service;
The Mobility Management Entity of step 11, current service sends and adheres to acceptance (Attach Accept) message to eNodeB;
Step 12, eNodeB send radio bearer to UE and set up request (Radio Bearer establishmentrequest) message;
Step 13, UE reply radio bearer and set up response (Radio Bearer establishment response) message to eNodeB;
Step 14, eNodeB adhere to the message of finishing (AttachComplete) for the Mobility Management Entity transmission of current service.
The step of solid line mark is this UE attachment flow necessary procedure in the 3GPP evolution system among Fig. 3, and the step that other dotted lines mark is the washability step.
Second kind of situation, in the 3GPP evolution system, current Mobility Management Entity for the UE service is judged the local UE context of not storing this UE, show that it is not same Mobility Management Entity that current Mobility Management Entity (new Mobility Management Entity) for the UE service leaves the Mobility Management Entity (old Mobility Management Entity) of serving for this UE before the 3GPP evolution system with UE, owing to preserve the UE context of this UE in the old Mobility Management Entity, so new Mobility Management Entity only need carry out next step attachment flow to the UE context that old Mobility Management Entity transmission request just can have been preserved, and the UE context that does not need to start from scratch and rebulid this UE.Its concrete flow process comprises as shown in Figure 4:
Step 2, eNodeB are to the current request of adhering to of transmitting this UE for the Mobility Management Entity (new Mobility Management Entity) of UE service;
Step 3, new Mobility Management Entity send the message of MME context request (MME Context Request) to old Mobility Management Entity, purpose is to obtain the UE context of this UE from old Mobility Management Entity, old Mobility Management Entity returns MME context response (MME ContextResponse) message and gives new Mobility Management Entity, comprises the UE context of this UE in this message;
Step 4, new Mobility Management Entity are sent the message of identity request (Identity Request) to this UE, and UE returns identity response (Identity Response) message to new Mobility Management Entity;
Carry out the authentication and authorization flow process between step 5, UE, new Mobility Management Entity (MME), the home subscriber server, because new mobile management entity obtains is the UE context of this UE of preserving in the old Mobility Management Entity, the authorization data that includes this UE in the above-mentioned UE context, new Mobility Management Entity can directly carry out authentication step to this UE, and need not to require home subscriber server to produce authorization data, thereby accelerated the speed of authentication;
Step 6, new Mobility Management Entity send deleting bearing request (Delete Bearer Request) message and give gateway and PDN Gateway, the carrying of this UE of request deletion, gateway and PDN Gateway have been deleted after the carrying of this UE, return deleting bearing response (Delete Bearer Response) message and give new Mobility Management Entity;
Step 7, new Mobility Management Entity send the message of scheduler (UpdateLocation) to home subscriber server, and the address of UE is upgraded in request;
Step 8, home network server are sent the message of cancellation UE address (CancelLocation) to old Mobility Management Entity, return cancellation Address Confirmation message (Cancel Location ACK) after old Mobility Management Entity has been cancelled and give home subscriber server;
Step 9, old Mobility Management Entity send request (the Delete Bearer Request) message of deleting bearing to gateway and PDN Gateway, after gateway and PDN Gateway have been deleted the carrying of this UE, return acknowledge message and give old Mobility Management Entity;
Step 10, network home server send the message of inserting contracted user's data (Insert Subscriber Data) for new Mobility Management Entity, and new Mobility Management Entity returns and inserts contracted user's data validation (Insert Subscriber Data ACK) message to the network home server;
Step 11, network home server send the message of upgrading UE Address Confirmation (Update Location ACK) to new Mobility Management Entity;
Step 12 to step 20 with respectively with Fig. 3 in step 6 identical to step 14, do not repeat them here.
Embodiment 2:
According to the contextual method of renewal UE in the 3GPP evolution system that embodiment 1 provides, present embodiment discloses a kind of UE updating context device, and its structure comprises shown in Fig. 5 A: receiving element, processing unit, updating block, memory cell; Wherein:
Receiving element 501 is used to receive the UE updating context message of home subscriber server transmission and be notified to processing unit 502;
Updating block 503, the UE context that is used for this UE that described memory cell 504 is preserved upgrades;
When above-mentioned UE updating context device received the MME context request message or needs to send the MME context request message, a preferable example was to increase transmitting element and acquiring unit on above-mentioned UE updating context device basic.Shown in Fig. 5 B, wherein:
Receiving element 501 also is used for the MME context request message of receiving entity or device transmission, and is notified to described processing unit 502;
Transmitting element 505 is used to send the UE context to the entity or the device of initiating the MME context request message;
After above-mentioned situation was meant that this device receives the MME context request message, the UE context that this locality is preserved sent to request contextual entity of UE or device.
Further described UE updating context device also comprises:
Acquiring unit 506, be used for preserving contextual entity of UE or device initiation MME context request message to other, the UE context of this UE of acquisition request, and receive the MME context response information return, after obtaining the UE context that carries in the MME context response information, the UE context that gets access to is sent to memory cell preserve.
Be because the UE context of this UE is not preserved in this locality when using acquiring unit 506, need obtain the UE context of this UE of its preservation for the related entities of this UE service from the last time.
Above-mentioned UE updating context device can be integrated in the Mobility Management Entity in the 3GPP evolution system.
Use the method and the device of UE updating context in the embodiment of the invention, this UE is from the attachment flow of non-3 GPP system access 3 GPP evolution system, owing to having preserved the UE context of this UE before leaving the 3GPP evolution system in the Mobility Management Entity old in the 3GPP evolution system, comprised the parameter about all bearer quality of service (QoS) of this UE before leaving the 3GPP system simultaneously in this UE context, like this, at UE when non-3 GPP system moves back to the 3GPP evolution system again, in attachment flow and the loading establishing process, can use the UE context of preservation to carry out authentication and carrying foundation, do not need to obtain again authorization data and carry out authentication, do not need to carry out yet and rebulid the contextual Signalling exchange flow process of UE, thereby accelerate the process that this UE sets up carrying, reduce signaling consumption.Because identical before UE moves back to the UE context that uses behind the 3GPP evolution system and moves, can guarantee that therefore this UE moves back to the service quality of the carrying behind the 3GPP evolution system and the consistency of the service quality that moves preceding carrying.
Obviously, those skilled in the art can carry out various changes and modification to the present invention and not break away from the spirit and scope of the present invention.Like this, if of the present invention these are revised and modification belongs within the scope of claim of the present invention and equivalent technologies thereof, then the present invention also is intended to comprise these changes and modification interior.
Claims (12)
1. a customer equipment context updating method is characterized in that, comprising:
After user equipment (UE) moved to non-3 GPP system from the 3GPP evolution system, network side home subscriber server notice Mobility Management Entity carried out the contextual renewal of described UE;
Described Mobility Management Entity upgrades described UE context and preserves;
After described UE moved back to the 3GPP evolution system from non-3 GPP system, the current contextual situation of UE of preserving described UE according to this locality for the Mobility Management Entity of UE service was carried out the attachment flow that this UE inserts the 3GPP evolution system.
2. the method for claim 1 is characterized in that, described home subscriber server gets access to described UE initiates register requirement in non-3 GPP system after, determines described UE and moves to non-3 GPP system from the 3GPP evolution system.
3. the method for claim 1 is characterized in that, described Mobility Management Entity upgrades the UE context, specifically comprises:
The state of the described UE of described Mobility Management Entity is set to the attachment removal state; And identify this UE and move in the non-3 GPP system.
4. method as claimed in claim 3 is characterized in that, also comprises:
After Mobility Management Entity upgrades described UE context, return UE updating context acknowledge message to described home subscriber server.
5. the method for claim 1, it is characterized in that, after described UE moves back to the 3GPP evolution system from non-3 GPP system, current Mobility Management Entity for UE service detects the UE context that this UE is preserved in this locality, and the attachment flow that this UE inserts the 3GPP evolution system carried out in the UE context of this UE that preserves according to this locality.
6. the method for claim 1, it is characterized in that, after described UE moves back to the 3GPP evolution system from non-3 GPP system, current Mobility Management Entity for the UE service detects the local UE context of not preserving described UE, obtain the UE context of described UE then being the Mobility Management Entity of described UE service, use the UE context that obtains to carry out the attachment flow that this UE inserts the 3GPP evolution system from the last time.
7. method as claimed in claim 6 is characterized in that, the described UE context that obtains described UE being the Mobility Management Entity of described UE service from the last time specifically comprises:
Current Mobility Management Entity of serving for this UE to the last time for the Mobility Management Entity of UE service sends Mobility Management Entity MME context request message;
The Mobility Management Entity of described last time for this UE service returns the MME context response information, carries the UE contextual information of local this UE that preserves in context response information.
8. a customer equipment context updating device is characterized in that, comprising: receiving element, processing unit, updating block and memory cell;
Described receiving element is used to receive the UE updating context message of home subscriber server transmission and be notified to described processing unit;
Described processing unit is used for notifying the UE context of this UE of described updating block to storing in the described memory cell to upgrade according to the UE updating context message that receives;
Described updating block, the UE context that is used for this UE that described memory cell is preserved upgrades;
Described memory cell is used to preserve the UE context of this UE.
9. device as claimed in claim 8 is characterized in that, also comprises transmitting element;
Described receiving element also is used to receive the MME context request message, and is notified to described processing unit;
Described processing unit also is used for notifying described transmitting element to obtain the UE context from described memory cell according to the MME context request message that receives;
Described transmitting element is used to send the UE context to the entity of initiating the MME context request message.
10. device as claimed in claim 9 is characterized in that, also comprises:
Acquiring unit is used to initiate the MME context request message, and receives the MME context response information of returning, and obtains the UE context that carries in the MME context response information, and the UE context that gets access to is sent to memory cell.
11. device as claimed in claim 10 is characterized in that, described updating block also is used for returning the renewal acknowledge message to described processing unit after carrying out the UE updating context;
Described processing unit sends described renewal acknowledge message by described transmitting element to described home subscriber server after also being used to receive the renewal acknowledge message.
12., it is characterized in that described customer equipment context management devices is integrated in the Mobility Management Entity in the 3GPP evolution system as the arbitrary described device of claim 8 to 11.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2007101202091A CN101369912B (en) | 2007-08-13 | 2007-08-13 | Customer equipment context updating method and apparatus |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2007101202091A CN101369912B (en) | 2007-08-13 | 2007-08-13 | Customer equipment context updating method and apparatus |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101369912A CN101369912A (en) | 2009-02-18 |
| CN101369912B true CN101369912B (en) | 2011-04-06 |
Family
ID=40413554
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2007101202091A Active CN101369912B (en) | 2007-08-13 | 2007-08-13 | Customer equipment context updating method and apparatus |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101369912B (en) |
Families Citing this family (19)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8045976B2 (en) | 2006-04-04 | 2011-10-25 | Aegis Mobility, Inc. | Mobility call management |
| US8160560B2 (en) | 2007-03-02 | 2012-04-17 | Aegis Mobility, Inc. | Management of mobile device communication sessions to reduce user distraction |
| CN101365230B (en) | 2007-08-07 | 2010-08-11 | 华为技术有限公司 | Customer separating method, system and apparatus when heterogeneous network switching/changing |
| CN101605315B (en) * | 2008-06-11 | 2011-05-18 | 大唐移动通信设备有限公司 | Method, system and device for detaching user terminal |
| CA2736131A1 (en) | 2008-09-05 | 2010-03-11 | Aegis Mobility, Inc. | Bypassing enhanced services |
| CA2758197A1 (en) * | 2009-04-09 | 2010-10-14 | Aegis Mobility, Inc. | Context based data mediation |
| US9480092B2 (en) | 2009-04-23 | 2016-10-25 | Qualcomm Incorporated | Establishing packet data network connectivity for local internet protocol access traffic |
| CN102026303A (en) * | 2009-09-21 | 2011-04-20 | 中兴通讯股份有限公司 | Method and system for controlling QoS of home base station |
| CN102164422A (en) * | 2010-02-24 | 2011-08-24 | 中兴通讯股份有限公司 | Method and system for releasing resources and base station |
| CN102204297B (en) * | 2011-05-10 | 2013-11-06 | 华为技术有限公司 | Method and device for updating user context |
| CN102333386B (en) * | 2011-10-20 | 2014-06-25 | 大唐移动通信设备有限公司 | Terminal attachment method and equipment |
| CN104144453B (en) * | 2013-05-10 | 2018-03-20 | 电信科学技术研究院 | A kind of context information management method and apparatus in heterogeneous network |
| KR101923399B1 (en) | 2014-01-30 | 2018-11-29 | 닛본 덴끼 가부시끼가이샤 | eNodeB, MME(Mobility Management Entity), METHOD OF eNodeB, AND METHOD OF MME |
| CN105376081A (en) * | 2014-08-22 | 2016-03-02 | 中兴通讯股份有限公司 | Service routing constraint reuse method and device |
| CN107113662B (en) | 2015-10-21 | 2020-08-25 | 华为技术有限公司 | Method, device and system for switching MEC (media Engineer) platform |
| WO2017139910A1 (en) * | 2016-02-15 | 2017-08-24 | Apple Inc. | Network initiated downlink data transmission for static and nomadic devices |
| CN110049484B (en) * | 2018-01-15 | 2020-12-15 | 华为技术有限公司 | Registration method and device for movement between systems |
| CN108683690B (en) * | 2018-08-27 | 2021-11-02 | 创新维度科技（北京）有限公司 | Authentication method, user equipment, authentication device, authentication server and storage medium |
| US11659380B1 (en) | 2021-05-05 | 2023-05-23 | T-Mobile Usa, Inc. | UE-capability-based system information block transmission |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1655536A (en) * | 2004-02-12 | 2005-08-17 | 三星电子株式会社 | Method for resuming header decompression in a multimedia broadcast /multicast service system |
| CN1697394A (en) * | 2004-05-12 | 2005-11-16 | 华为技术有限公司 | Method for updating routing area in operation of multimedia broadcast/multicast service |
| CN1997216A (en) * | 2006-01-03 | 2007-07-11 | 华为技术有限公司 | Method for user device switching in the long evolving network |
-
2007
- 2007-08-13 CN CN2007101202091A patent/CN101369912B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1655536A (en) * | 2004-02-12 | 2005-08-17 | 三星电子株式会社 | Method for resuming header decompression in a multimedia broadcast /multicast service system |
| CN1697394A (en) * | 2004-05-12 | 2005-11-16 | 华为技术有限公司 | Method for updating routing area in operation of multimedia broadcast/multicast service |
| CN1997216A (en) * | 2006-01-03 | 2007-07-11 | 华为技术有限公司 | Method for user device switching in the long evolving network |
Also Published As
| Publication number | Publication date |
|---|---|
| CN101369912A (en) | 2009-02-18 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101369912B (en) | Customer equipment context updating method and apparatus | |
| CN1934889B (en) | Method and communication system to allow barring a call of a roaming user after pdp context activation | |
| CN101978716B (en) | For the method that optimizing user equipment PDN (packet data network) connects | |
| CN103024931B (en) | A kind of method and apparatus of releasing bearing resource | |
| CN110073686B (en) | Session activation method, device and system | |
| CN101150838B (en) | A method and system for inter-system switching | |
| CN101969634B (en) | Method and system for synchronizing user data | |
| CN101296518A (en) | Circuit field service paging implementing method and apparatus | |
| CN105308994A (en) | Changing of subscriber identity at a mobile terminal using a cancel location message | |
| CN110138580B (en) | PDU session updating method and network side equipment | |
| EP2071892A2 (en) | Mobile communication system, location registration period defining node, mobile terminal, and location registration method in mobile communication | |
| CN101572862B (en) | Method and equipment for supporting intercommunication between 3G system and LTE system | |
| EP1871050A1 (en) | Wimax network, Wimax network element and method of handling QoS | |
| CN101790151B (en) | Deleting method and system of EPS load | |
| CN102045695B (en) | Method and system for acquiring information on MTC (Microsoft Technology Center) server address | |
| EP2209279B1 (en) | Method and system for processing a radio bearer under the idle mode signaling reduction (isr) mechanism | |
| CN101127652A (en) | A method, device and system for identifying access anchor of user terminal to external network | |
| CN100369527C (en) | Method of reporting and updating stored configuration parameter information by mobile terminal | |
| CN101325583B (en) | Method for registering gateway address and mobility management entity | |
| CN101868036A (en) | Method and system for controlling UE to access to network | |
| CN102378295A (en) | Method and system for bearer release | |
| CN100401848C (en) | Method for solving calling/called impact in wireless network | |
| CN101330720A (en) | Method for processing access user, user access system and equipment | |
| CN101448225B (en) | Method for realizing circuit switch domain terminating call and system thereof | |
| CN106714133B (en) | Recovery processing method and device for gateway |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| ASS | Succession or assignment of patent right |
Owner name: INST OF TELECOMMUNICATION SCIENCE AND TECHNOLGOY Free format text: FORMER OWNER: DATANG MOBILE COMMUNICATION EQUIPMENT CO., LTD. Effective date: 20110422 |
|
| C41 | Transfer of patent application or patent right or utility model | ||
| COR | Change of bibliographic data |
Free format text: CORRECT: ADDRESS; FROM: 100083 NO. 29, XUEYUAN ROAD, HAIDIAN DISTRICT, BEIJING TO: 100191 NO. 40, XUEYUAN ROAD, HAIDIAN DISTRICT, BEIJING |
|
| TR01 | Transfer of patent right |
Effective date of registration: 20110422 Address after: 100191 Haidian District, Xueyuan Road, No. 40, Patentee after: CHINA ACADEMY OF TELECOMMUNICATIONS TECHNOLOGY Address before: 100083 Haidian District, Xueyuan Road, No. 29, Patentee before: DATANG MOBILE COMMUNICATIONS EQUIPMENT Co.,Ltd. |
|
| CP01 | Change in the name or title of a patent holder |
Address after: 100191 No. 40, Haidian District, Beijing, Xueyuan Road Patentee after: CHINA ACADEMY OF TELECOMMUNICATIONS TECHNOLOGY Address before: 100191 No. 40, Haidian District, Beijing, Xueyuan Road Patentee before: CHINA ACADEMY OF TELECOMMUNICATIONS TECHNOLOGY |
|
| CP01 | Change in the name or title of a patent holder | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20210528 Address after: 100085 1st floor, building 1, yard 5, Shangdi East Road, Haidian District, Beijing Patentee after: DATANG MOBILE COMMUNICATIONS EQUIPMENT Co.,Ltd. Address before: 100191 No. 40, Haidian District, Beijing, Xueyuan Road Patentee before: CHINA ACADEMY OF TELECOMMUNICATIONS TECHNOLOGY |
|
| TR01 | Transfer of patent right |