CN101394657B - Mobility management method and system - Google Patents
Mobility management method and system Download PDFInfo
- Publication number
- CN101394657B CN101394657B CN2007101221834A CN200710122183A CN101394657B CN 101394657 B CN101394657 B CN 101394657B CN 2007101221834 A CN2007101221834 A CN 2007101221834A CN 200710122183 A CN200710122183 A CN 200710122183A CN 101394657 B CN101394657 B CN 101394657B
- Authority
- CN
- China
- Prior art keywords
- communication system
- subscriber equipment
- context
- 3gpp
- 3gpp 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
Images
Landscapes
- Mobile Radio Communication Systems (AREA)
Abstract
The invention discloses a mobility management method, which is used for maintaining service continuity when different systems move under an SAE architecture and saving system resources. The method comprises the following steps: after user equipment moves from a first communication system to a second communication system, establishing a context of the second communication system for the user equipment, and reserving the context of the first communication system of the user equipment; and in the downlink data transmission process, the context of the second communication system is preferentially used according to the configuration information. The invention also discloses a system architecture.
Description
Technical field
The present invention relates to the communications field, particularly relate to motion management method and system.
Background technology
Along with to the going deep into of communication network research, except to wireless access network evolution study, also to carry out the research of system architecture aspect evolution, and with its be defined as System Architecture Evolution (System Architecture Evolution, SAE).Support third generation partnership plan (3GPP) system and non-3GPP (NON-3GPP) system owing to require the SAE system architecture; Then there is the frequent problem that moves between different system for the terminal use;, UE require the SAE system architecture need keep business continuance when frequently switching in non 3gpp and 3gpp system simultaneously; Reduce handover delay as far as possible, set up control plane and the user plane of UE fast.
About existing non 3GPP system; As subscriber equipment (User Equipment; When UE) getting into the non3GPP system, UE can carry out (Attach) process of access in inserting non 3GPP systematic procedure, set up non 3GPP and carry; On packet data network gateway (Packet Data Network Gate Way, PDN GW), set up simultaneously the user plane context (UE Context) of the non 3GPP system of this UE.When UE withdrawed from non 3GPP system, UE can carry out in leaving non 3GPP systematic procedure and leave (detach) process, deletes corresponding user plane context.
About existing 3GPP system; When UE got into the 3GPP system to leave (detached) state, UE can carry out the Attach process in inserting the 3GPP systematic procedure, set up 3GPP and carry; Simultaneously at mobile management entity (Mobility Management Entity; MME) set up the control plane context on, on gateway (Serving Gate Way, Serving GW) and PDN GW, set up the user plane context of the 3GPP system of this UE.When UE withdrawed from the 3GPP system with the detached state, UE can carry out the detach process in leaving the 3GPP systematic procedure, deletion control corresponding plane context and user plane context.When UE withdraws from the 3GPP system with idle (IDLE) state, can keep control plane context and user plane context for UE.When UE gets into the 3GPP system with idle (IDLE) state, can directly use the control plane context and the user plane context of reservation.Wherein, detached STA representation UE is in states such as shutdown, attachment removal.IDLE STA representation UE is in idle condition, does not have professional transfer of data.
If UE moves between 3GPP system and NON-3GPP system with the detached state; Then need frequent Attach process and the detach process carried out; Set up and the deletion context, increase the signaling burden, also increased the handover delay between 3GPP system and the non 3GPP system simultaneously.If UE moves between 3GPP system and NON-3GPP system with the IDLE state; Then on PDN GW, there are the user plane context of 3GPP system and the user plane context of NON-3GPP system simultaneously; This moment, how PDN GW did not know this datagram of route can't to realize business continuance.
Summary of the invention
The embodiment of the invention provides a kind of motion management method and system, keeps professional continuity when being used to realize move between different system under the SAE framework, and saves system resource.
A kind of motion management method may further comprise the steps:
After subscriber equipment moves to the second communication system from first communication system,, and keep the context of first communication system of said subscriber equipment for said subscriber equipment is set up the context of second communication system;
In the downlink data transmission process, preferentially use the context of second communication system according to configuration information.
When subscriber equipment when the second communication system moves back to first communication system, subscriber equipment can send location update message, carries the renewal reason, according to the context that upgrades reason deletion second communication system.
A kind of mobility management systems comprises:
PDN Gateway; Be used for after subscriber equipment moves to the NON-3GPP system from the 3GPP system; Set up the user plane context of NON-3GPP system for said subscriber equipment; The user plane context that keeps the 3GPP system of said subscriber equipment, and in the up-downgoing data transmission procedure, preferentially use the user plane context of NON-3GPP system according to configuration information;
Gateway is used at subscriber equipment from still keeping the user plane context of its 3GPP system after the 3GPP system is left;
Mobile management entity MME is used at subscriber equipment from still keeping the control plane context of its 3GPP system after the 3GPP system is left.
When UE when a communication system moves to another communication system; The embodiment of the invention is through keeping context and the preferential context that uses another communication system in the said communication system; Solved in another communication system, have a plurality of contexts and can't route data the problem of newspaper; And needn't delete the context in the said communication system, reduce the signaling burden.
Description of drawings
Fig. 1 is the main method flow chart of mobile management in the embodiment of the invention;
Fig. 2 is the sketch map of system architecture in the embodiment of the invention;
Fig. 3 is the concrete grammar flow chart of the mobile management when the 3GPP system moves to the NON-3GPP system of UE in the embodiment of the invention;
The concrete grammar flow chart that Fig. 4 adopts clocking method to carry out mobile management for UE in the embodiment of the invention when the 3GPP system moves to the NON-3GPP system;
Fig. 5 is the concrete grammar flow chart of the mobile management when the NON-3GPP system is moved back into the 3GPP system of UE in the embodiment of the invention;
Fig. 6 is the structure chart of MME in the embodiment of the invention.
Embodiment
When UE moves between two communication systems; The embodiment of the invention is through keeping the frequent execution that context in the communication system reduces Attach process and detach process, and it is chaotic to avoid that through the preferential context of selecting another communication system in another communication system context takes place on PDN GW.
Context in the present embodiment comprises the control plane context and the user plane context of each communication system.Zone in the present embodiment comprises lane place, route district and tracking area (Tracking Area; TA) etc.; Corresponding area identification comprises Location Area Identification, Routing Area Identifier and tracking area identification (Tracking Area ID) etc., and present embodiment is that example describes with TA.
Referring to Fig. 1, the main flow process of motion management method is following in the present embodiment:
Step 101: switch between mobile initiation system, carrying out knowing in the handoff procedure between system that UE moves to the second communication system from first communication system based on UE.
Step 102: after UE moves to the second communication system from first communication system,, and keep the context of first communication system of said UE for said UE sets up the context of second communication system.
Step 103: in the up-downgoing data transmission procedure, preferentially use the context of second communication system according to configuration information.
Present embodiment is that 3GPP system, second communication system are that the NON-3GPP system is that example is elaborated with first communication system.
Referring to Fig. 2, system architecture comprises MME, Serving GW and PDN GW in the present embodiment.MME, Serving GW and PDN GW are functional entity, can perhaps be present in other physical entity respectively as an independently physical entity existence.
MME is used for mobile management, and storage UE identifies, control plane context, mobility management states, the TA of UE in the 3GPP system tabulates (List) etc.When UE leaves the 3GPP system, the mobility management states of UE in the 3GPP system is changed to the IDLE state, keep the control plane context.When UE gets back to the 3GPP system, send bearer update request message (Update Bearer Request) to Serving GW.MME also is used for when UE leaves the 3GPP system, picking up counting; When the preset time UE of arrival does not get back to the 3GPP system; The mobility management states of UE in the 3GPP system is changed to the detached state, deleting control plane context, and notice Serving GW deletion user plane context.When UE got into the 3GPP system in overtime back, notice UE carried out the Attach process.
Serving GW is used for being responsible for user plane processing, storage UE user plane context, the user plane support of switching between evolution base station under the 3GPP system.After receiving Attach request message (Request), for UE is based upon the user plane context in the 3GPP system, and to PDN GW forwarding Attach Request.Receive the Update Bearer Request that MME sends, and be transmitted to PDN GW.Receive the detach Request that MME sends, delete the user plane context in the 3GPP system, and detach Request is transmitted to PDN GW.
PDN GW is used to provide user plane support between system, and the user plane of handling between different access systems is switched, the user plane context of storage UE in 3GPP system and NON-3GPP system.According to the system banner among the Attach Request that receives is that UE sets up corresponding user plane context; According to the user plane context of the deletion UE of the system banner among the detach Request that receives under corresponding communication system; And according to the UpdateBearer Request that receives, the user plane context of deletion UE in the NON-3GPP system.In the downlink data transmission process, preferentially use the user plane context of NON-3GPP system according to configuration information.
Referring to Fig. 3, the idiographic flow of the motion management method of UE when the 3GPP system moves to the NON-3GPP system is following in the present embodiment:
Attach Request is sent in step 301:UE start back, and request inserts the 3GPP system, sets up the 3GPP system bearing.
Step 302:MME is that UE is based upon the control plane context in the 3GPP system according to the Attach Request that receives, and transmits Attach Request to Serving GW.And MME is UE distribution T A ID.
Step 303:Serving GW is that UE is based upon the user plane context in the 3GPP system according to the Attach Request that receives, and transmits Attach Request to PDN GW.
Step 304:PDN GW is that UE is based upon the user plane context in the 3GPP system according to the Attach Request that receives.
Mobile the causing between communication system of step 305:UE switched.Also can be that network environment changes, cause UE to communicate between system and switch.Can continue step 306 and step 308 simultaneously.
Step 306:UE sends Attach Request, and request inserts the NON-3GPP system, sets up the NON-3GPP system bearing.Because the user plane context of this UE not in the NON-3GPP system; Explain and be not the carrying of UE foundation with the NON-3GPP system; Perhaps cancelled the carrying of UE and NON-3GPP system; So can think that this UE shows as the detached state in the NON-3GPP system, need to send Attach Request.
Step 307:PDN GW is that UE is based upon the user plane context in the NON-3GPP system according to the Attach Request that receives.
Step 308: based on moving of UE, MME is changed to the IDLE state with the mobility management states of UE in the 3GPP system.Because UE leaves the 3GPP system with the IDLE state, and the mobility management states in the 3GPP system is changed to the IDLE state, so need not delete user plane context and control plane context in the 3GPP system.
Step 309: through step 307 and 308; Exist UE user plane context in NON-3GPP system and 3GPP system among the PDN GW this moment; In the downlink data transmission process, PDN GW preferentially uses the user plane context of NON-3GPP system according to configuration information.
Solved UE when the NON-3GPP system through above flow process, PDN GW stores a plurality of user plane contexts and problem that can't the route data newspaper.And when UE gets back to the 3GPP system,,, signaling burden and handover delay have been reduced so need not rebulid user plane context and control plane context because the mobility management states of UE in the 3GPP system is changed to the IDLE state.This method is applicable to UE frequent situation about moving between NON-3GPP system and 3GPP system.
Do not return user plane context in the 3GPP system and the control plane context long-term existence that the 3GPP system is caused for fear of UE, take memory space, after step 305, can continue step 310, referring to shown in Figure 4.
Step 310:MME picks up counting.MME can pick up counting according to (leave) request message that leaves that UE sends, and perhaps picks up counting according to mobility management states being changed to the IDLE state.
Step 311: UE gets back to the 3GPP system before reaching preset time, and then MME stops timing, and with timing clear 0.Continue the mobile management flow process of UE when the NON-3GPP system is moved back into the 3GPP system, referring to embodiment shown in Figure 5.
Step 312: UE does not get back to the 3GPP system when reaching preset time, and then MME is changed to the detached state with the mobility management states of UE in the 3GPP system.Continue step 313.
Wherein, MME can be regularly with the time and the preset time of time ratio of timing to determining whether to reach preset, perhaps MME starts the timer timing, receives the triggering of timer to confirm the time that reaches preset.
The control plane context of step 313:MME deletion UE in the 3GPP system, and to Serving GW transmission detach Request.
Step 314:Serving GW deletes the user plane context of UE in the 3GPP system according to the detach Request that receives, and transmits detach Request to PDN GW.
Step 315:PDN GW is according to the user plane context of detach Request deletion UE in the 3GPP system of receiving.
Referring to Fig. 5, the idiographic flow of the motion management method of UE when the NON-3GPP system is moved back into the 3GPP system is following in the present embodiment:
Mobile the causing between communication system of step 501:UE switched.
Step 502:UE is according to the TA ID of mobility management states of preserving in the 3GPP system (being the IDLE state) and preservation; Send tracing section updating request message (TAU Request), and the reason that causes TAU among the TAU Request is changed to NON-3GPP system mobility.
After step 503:MME receives TAU Request, because NON-3GPP system mobility is checked the local control plane context that whether has UE, perhaps check the mobility management states of UE in the 3GPP system according to causing the former of TAU.If having control plane context or the mobility management states of UE is the IDLE state, continue step 508; If not having the control plane context of UE or mobility management states is the detached state, continue step 504.
Step 504:MME sends TAU Response to UE, refusal TAU.
Step 505:UE sends Attach Request after receiving TAU Response, and request inserts the 3GPP system, sets up the 3GPP system bearing.
Step 506:MME is that UE is based upon the control plane context in the 3GPP system according to Attach Request; Serving GW is that UE is based upon the user plane context in the 3GPP system according to Attach Request, and PDN GW is that UE is based upon the user plane context in the 3GPP system according to Attach Request.Detailed process is referring to step 302-304.
Step 507:PDN GW deletes the user plane context of UE in the NON-3GPP system simultaneously according to Attach Request.Promptly cancel the carrying of UE in the NON-3GPP system.
PDN GW sends Attach Response through Serving GW and MME to UE.
Step 508:MME sends Update Bearer Request message to Serving GW, and notice Serving GWUE has got back to the 3GPP system.
Step 509:Serving GW transmits Update Bearer Request to PDN GW, and notice PDNGWUE has got back to the 3GPP system.
Step 510:PDN GW deletes the user plane context of UE in non 3GPP system according to the Update Bearer Request that receives, and sends Update Bearer Response message to Serving GW.
Step 511:Serving GW transmits Update Bearer Response message to MME.
Step 512:MME sends TAUResponse message according to the Update Bearer Response message of receiving to UE.
Step 513: in the downlink data transmission process; PDN GW preferentially uses the user plane context of NON-3GPP system according to configuration information; Because the user plane context of NON-3GPP system is deleted in step 507 and step 510, so PDN GW is according to the user plane context route data newspaper of 3GPP system.
Solved UE when the 3GPP system through above flow process, PDN GW stores a plurality of user plane contexts and problem that can't the route data newspaper.
Referring to Fig. 6, MME comprises first interface unit 601, mobility management unit 602, memory cell 603 and second interface unit 604 in the present embodiment.
MME also comprises timer, and this figure is not shown, and timer is used for when UE leaves the 3GPP system, picking up counting, and when arriving the preset time, triggers the mobility management states that mobility management unit 602 is upgraded UE.
Present embodiment when the 3GPP system, keeps the context of 3GPP system with UE, the context of deletion NON-3GPP system is the description that example is carried out.Also can work as UE and when the NON-3GPP system, keep the context of NON-3GPP system, the context of deletion 3GPP system, then require preferentially to use the context of 3GPP system in the configuration information.When UE leaves the NON-3GPP system, make UE not initiate the detach process, perhaps refuse the detach process, just can realize keeping the context of NON-3GPP system through modes such as mobility management states or transmission message are set.Because the context of 3GPP system comprises user plane context and control plane context at present; Need to set up or at least two contexts of deletion; The context of NON-3GPP system includes only the user plane context; Only need to set up or delete a context, so keep the context of 3GPP system, the contextual better effects if of deletion NON-3GPP system.Present embodiment also is applicable to the mobile management between other communication system, especially about context management of subscriber equipment etc.
When UE when a communication system moves to another communication system; The embodiment of the invention is through keeping context and the preferential context that uses another communication system in the said communication system; Solved in another communication system, have a plurality of contexts and can't route data the problem of newspaper; And needn't delete the context in the said communication system, reduce the signaling burden.When UE when another communication system is moved back into a said communication system; The embodiment of the invention is through the context in another communication system of deletion; Solved in a said communication system, have a plurality of contexts and can't route data the problem of newspaper; And when UE gets back to a said communication system, need not rebulid the context of a said communication system, reduce signaling burden and handover delay.The embodiment of the invention further adopts timing mode control to keep the contextual time the said communication system when a communication system moves to another communication system at UE, avoids UE not get back to a said communication system and but keeps the contextual situation in the said communication system for a long time.
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, belong within the scope of claim of the present invention and equivalent technologies thereof if of the present invention these are revised with modification, then the present invention also is intended to comprise these changes and modification interior.
Claims (14)
1. a motion management method is characterized in that, may further comprise the steps:
After subscriber equipment moves to the second communication system from first communication system,, and keep the context of first communication system of said subscriber equipment for said subscriber equipment is set up the context of second communication system;
In the downlink data transmission process, preferentially use the context of second communication system according to configuration information.
2. the method for claim 1 is characterized in that, the access request message that sends according to said subscriber equipment is the context that said subscriber equipment is set up the second communication system.
3. method as claimed in claim 2 is characterized in that, after said subscriber equipment moves to the second communication system, sends the access request message to the second communication system.
4. the method for claim 1; It is characterized in that; After said subscriber equipment moves to the second communication system; The mobility management states of said subscriber equipment in first communication system is changed to idle condition, and keeps the context of first communication system of said subscriber equipment according to this idle condition.
5. method as claimed in claim 4; It is characterized in that; Pick up counting after first communication system moves to the second communication system at subscriber equipment, and the mobility management states of the said subscriber equipment of maintenance in first communication system is idle condition before arriving the preset time.
6. method as claimed in claim 5 is characterized in that, when arriving preset time and said subscriber equipment and do not get back to first communication system, the mobility management states of said subscriber equipment in first communication system is changed to the state of leaving.
7. method as claimed in claim 6 is characterized in that, leaves the context that state is deleted first communication system of said subscriber equipment according to said.
8. like each described method among the claim 1-7; It is characterized in that; Also comprise step: after said subscriber equipment is got back to first communication system from the second communication system, delete the context of the second communication system of said subscriber equipment according to the request message that said subscriber equipment sends.
9. method as claimed in claim 8 is characterized in that, deletes the context of the second communication system of said subscriber equipment according to the access request message that said subscriber equipment sends; Perhaps
That carries in the area update request message according to said subscriber equipment transmission causes that upgrading reason deletes the context of the second communication system of said subscriber equipment.
10. method as claimed in claim 9; It is characterized in that; Sending zone update inquiry information when the mobility management states of said subscriber equipment in being informed in first communication system is idle condition, the mobility management states in being informed in first communication system are sent when leaving state and are inserted request message.
11. method as claimed in claim 10; It is characterized in that; Pick up counting after first communication system moves to the second communication system at subscriber equipment; When arriving the area update request message of receiving said subscriber equipment transmission after the preset time, upgrade response message through the sending zone and notify its mobility management states in first communication system of said subscriber equipment for leaving state, said subscriber equipment is sent insert request message.
12. method as claimed in claim 9 is characterized in that, the access request message that sends according to said subscriber equipment is the context that said subscriber equipment is set up first communication system.
13. the method for claim 1 is characterized in that, first communication system is the 3GPP system, and the second communication system is a non-3 GPP system.
14. a mobility management systems is characterized in that, comprising:
PDN Gateway; Be used for after subscriber equipment moves to the NON-3GPP system from the 3GPP system; Set up the user plane context of NON-3GPP system for said subscriber equipment; The user plane context that keeps the 3GPP system of said subscriber equipment, and in the downlink data transmission process, preferentially use the user plane context of NON-3GPP system according to configuration information;
Gateway is used at subscriber equipment from still keeping the user plane context of its 3GPP system after the 3GPP system is left;
Mobile management entity MME is used at subscriber equipment from still keeping the control plane context of its 3GPP system after the 3GPP system is left.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2007101221834A CN101394657B (en) | 2007-09-21 | 2007-09-21 | Mobility management method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2007101221834A CN101394657B (en) | 2007-09-21 | 2007-09-21 | Mobility management method and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101394657A CN101394657A (en) | 2009-03-25 |
| CN101394657B true CN101394657B (en) | 2012-05-23 |
Family
ID=40494679
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2007101221834A Active CN101394657B (en) | 2007-09-21 | 2007-09-21 | Mobility management method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101394657B (en) |
Families Citing this family (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| RU2495548C2 (en) * | 2009-04-24 | 2013-10-10 | Хуавэй Текнолоджиз Ко., Лтд. | Method, device and mobile communication system for providing uninterrupted service |
| WO2011085580A1 (en) | 2010-06-28 | 2011-07-21 | 华为技术有限公司 | Service implementing method, device and system |
| CN104144453B (en) * | 2013-05-10 | 2018-03-20 | 电信科学技术研究院 | A kind of context information management method and apparatus in heterogeneous network |
| BR112019013937A2 (en) | 2017-01-06 | 2020-02-11 | Huawei Technologies Co., Ltd. | METHOD OF AUTOMATIC CHANGE OF NETWORK AND RELATED DEVICE |
| EP3611967A4 (en) * | 2017-09-27 | 2020-04-01 | Guangdong Oppo Mobile Telecommunications Corp., Ltd. | Access link management method, device, storage medium, and system |
| CN110167002B (en) * | 2018-02-13 | 2021-01-29 | 华为技术有限公司 | Method, device and system for updating position |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1941993A (en) * | 2005-10-01 | 2007-04-04 | 华为技术有限公司 | Method for controlling mobile-terminal text |
| CN1997216A (en) * | 2006-01-03 | 2007-07-11 | 华为技术有限公司 | Method for user device switching in the long evolving network |
-
2007
- 2007-09-21 CN CN2007101221834A patent/CN101394657B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1941993A (en) * | 2005-10-01 | 2007-04-04 | 华为技术有限公司 | Method for controlling mobile-terminal text |
| 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 |
|---|---|
| CN101394657A (en) | 2009-03-25 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US12022429B2 (en) | Managing connection states for communications devices | |
| CN104994575B (en) | Method for updating user equipment position information | |
| CN102638856B (en) | Method of mobile communication, mobile communication system and access entity | |
| CN101296518B (en) | Circuit field service paging implementing method and apparatus | |
| AU705282B2 (en) | Updating subscriber data of a mobile communication system | |
| CN101577962B (en) | Method for realizing update of incidence relation and corresponding terminal | |
| CN101136835B (en) | Bearer establishment method in idle mode | |
| CN101540990B (en) | Method and system for paging user in paging blind zone | |
| CN101282511B (en) | Bearing processing method | |
| CN101374342B (en) | Method for detaching user equipment | |
| CN101369912B (en) | Customer equipment context updating method and apparatus | |
| CN101394657B (en) | Mobility management method and system | |
| CN101674223B (en) | Gateway equipment load processing method, network equipment and network system | |
| CN102083048A (en) | Method and device for processing paging message under idle condition signaling optimized and activated state | |
| CN101291531B (en) | Updating method for tracing area list | |
| CN103814622A (en) | Communication system, communication method and communication program | |
| CN101754373B (en) | Operating indication method, service gateway and core network system | |
| CN102647762B (en) | SGW(Serving Gateway)-relocated ping-pong switch processing method and device | |
| CN101296496B (en) | Method for preventing false resource release in tracing section updating or switching course | |
| CN101150781B (en) | Called recovery method, device and system for mobile switching center pool | |
| CN101448225B (en) | Method for realizing circuit switch domain terminating call and system thereof | |
| CN102647761B (en) | Processing method and device for SGW (Serving Gateway) redirected X2 switching | |
| CN101610462B (en) | Data message sending method, device and communication system | |
| CN110313195B (en) | Communication method and device | |
| CN108307465B (en) | Connection control method and device for light connection user equipment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| 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 |
|
| TA01 | Transfer of patent application right |
Effective date of registration: 20110422 Address after: 100191 Haidian District, Xueyuan Road, No. 40, Applicant after: CHINA ACADEMY OF TELECOMMUNICATIONS TECHNOLOGY Address before: 100083 Haidian District, Xueyuan Road, No. 29, Applicant before: DATANG MOBILE COMMUNICATIONS EQUIPMENT Co.,Ltd. |
|
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| CP01 | Change in the name or title of a patent holder | ||
| 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 |
|
| TR01 | Transfer of patent right | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20210601 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 |