CN102143539B - Method and system for acquiring context of terminal - Google Patents
Method and system for acquiring context of terminal Download PDFInfo
- Publication number
- CN102143539B CN102143539B CN201010111065.5A CN201010111065A CN102143539B CN 102143539 B CN102143539 B CN 102143539B CN 201010111065 A CN201010111065 A CN 201010111065A CN 102143539 B CN102143539 B CN 102143539B
- Authority
- CN
- China
- Prior art keywords
- context
- terminal
- information
- target
- message
- 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
Landscapes
- Mobile Radio Communication Systems (AREA)
Abstract
The invention discloses a method and system for acquiring context of a terminal, which can be used for accurately acquiring the context of the terminal between eNBs (evolved Node B). The method comprises the following steps of: transmitting a request message for acquiring the context of the terminal to a source base station if a target base station to which a target cell, selected by the terminal during RRC (radio resource control) reconstruction, belongs does not have the context information of the terminal, wherein the request message comprises context matching information, a short media access control integrity verification value (short MAC-I) and evolved cell global identifier (ECGI) of an RRC reconstruction trial cell; matching the context of the terminal according to the context matching information in the request message for acquiring the context information of the terminal and verifying the context of the terminal through the short MAC-I by the source base station after the source base station receives the request message for acquiring the context information of the terminal; and if the verification is successful, judging that the context of the terminal exists and returning a response message to the target base station, wherein the response message carries the context information of the terminal.
Description
Technical field
The present invention relates to radio honeycomb communication system, more particularly, relate to a kind of acquisition methods and system of terminal contexts.
Background technology
LTE (Long Term Evolution, long evolving system) network is by E-UTRAN (EvolvedUniversal Terrestrial Radio Access, Global land wireless access) base station (Evolved NodeB, referred to as eNB) and evolution packet switching center (Evolved Packet Core, referred to as EPC) composition, network flattening.Wherein E-UTRAN comprises the set of the eNB be connected by S1 interface with EPC, connects between eNB by X2 interface.S1, X2 are logic interfacing.An EPC can manage one or more eNB, and an eNB also can be controlled by multiple EPC, and an eNB can manage one or more community (cell).
In LTE system, subscriber equipment (User Equipment, referred to as UE) namely terminal, after the safe mode of Access Layer activates, when meeting in following condition one:
1) Radio Link Failure (Radio Link Failure, referred to as RLF);
2) handoff failure (Handover Failure);
3) handoff failure (Mobility from E-UTRA Failure) from E-UTRA to different system;
4) integrity checking failure (Integrity Check Failure);
5) RRC connects reconfiguration failure (RRC Connection Reconfiguration Failure),
UE can carry out RRC (Radio Resource Control, wireless heterogeneous networks) re-establish, UE, when carrying out RRC and re-establishing, is obtain Target cell by cell selection procedure, and re-establishes request message to the target BS transmission RRC at place, Target cell.UE re-establishes in request message at RRC, can with terminal iidentification (UE Identity), comprise: UE is at Radio Network Temporary Identifier (the Cell Radio Network Temporary Identifier of community, referred to as C-RNTI), short MAC (Media Access Control, media interviews control) integrity verification value (short Medium AccessControl integrity protection, referred to as shortMAC-I) and cell physical address (PhysicalCell Identity, referred to as PCI).Wherein, under the scene of handoff failure, C-RNTI distributes in the cell-of-origin that UE switches, and is then distribute in the community of triggering RRC reconstruction under other scenes; Under the scene of handoff failure, PCI refers to the physical address of the cell-of-origin switched, and then refers to the physical address triggering the community that RRC rebuilds under other scenes; The calculating of shortMAC-I adopts (scene of handoff failure) of the cell-of-origin switched or triggering KRRCint key (key that RR signaling integrality calculates) and the protection algorithm integrallty of the community that RRC rebuilds; input when calculating shortMAC-I comprises: the Cell Global Identity (Evolved CellGlobal Identifier, referred to as ECGI) of PCI, C-RNTI and evolution.The output that these three parameters input algorithms obtain by UE is exactly shortMAC-I.The shortMAC-I of base station side is also same algorithm, or is obtained (scene at handoff failure) by hand off signaling flow process.Base station, after the RRC receiving UE re-establishes message, is verified UE by whether the shortMAC-I that compares shortMAC-I in message and to calculate with base station or preserve is consistent, if unanimously, is then proved to be successful.Wherein, PCI, C-RNTI re-establish in request message at above-mentioned RRC and carry, and the ECGI of the ECGI Target cell that to be UE selected when RRC rebuilds.
Switch in handoff procedure failure time, if source base station does not receive UE release message and switching timer there is not time-out, then can retain the contextual information of user; And if target BS before the success of wait UE Stochastic accessing or timer do not have time-out, then can retain the contextual information of user.When other RRC re-establishes, if it is not same eNB with source eNB (eNB belonging to the Serving cell of UE before RRC re-establishes request) that UE carries out the target eNB (RRC re-establishes the eNB belonging to the Target cell of request selecting) that RRC re-establishes, and target eNB does not exist the contextual information (UEcontext) of this UE, then RRC re-establishes trial meeting failure.
In prior art, in order to improve the success rate that RRC re-establishes, be improve to the method that source eNB obtains UE context the success rate that RRC re-establishes by target eNB.Current a kind of existing method obtains request by UE context to obtain with responding process, and namely target eNB sends UE context to source eNB and obtains request message, wherein comprises the C-RNTI of UE in cell-of-origin and the PCI of cell-of-origin.If source eNB exists the context of this UE, then return UE context to target eNB and obtain response message, wherein comprise the context information content of UE; If source eNB does not exist the context of this UE, then return UE context to target eNB and obtain failed message.
There are the following problems for said method: obtain in request message at UE context and only identify UE with C-RNTI and PCI, may cause confusion, because C-RNTI distributes in a community, if eNB You Liangge community, source is all assigned with this C-RNTI value simultaneously, and the PCI of the Liang Ge community of source eNB is identical, then source eNB cannot differentiate this UE is actually for which community.Equally, it is also like this for obtaining failed message for UEcontext acquisition response message and UE context, target eNB may have sent UE context to multiple source base station and obtain request message in PCI confusion situation, also need to know obtain comprise in response message be the context of which UE or obtain which UE failed message is for.
The problems referred to above may cause RRC to re-establish procedure failure, and then affect network performance.
Summary of the invention
The technical problem to be solved in the present invention is to provide a kind of acquisition methods and system of terminal contexts, can realize Obtaining Accurate UE context information between eNB, improves the success rate that RRC re-establishes, thus improves network performance.
In order to solve the problem, the invention provides a kind of acquisition methods of terminal contexts, described method comprises:
Terminal carries out wireless heterogeneous networks (RRC) if the target BS belonging to Target cell selected when re-establishing does not have the contextual information of described terminal, then send the request message obtaining terminal context information to source base station, in this request message, comprise context matches information, short media interviews control integrity verification value (shortMAC-I) and RRC rebuilds the Cell Global Identity (ECGI) attempting community;
After described source base station receives the request message of described acquisition terminal context information, the context of terminal according to described context matches information matches wherein, and the context of described terminal is verified by described shortMAC-I, if be proved to be successful, and the context of described terminal exists, then return response message to described target BS, in this response message, carry the contextual information of described terminal.
Further, if the context of described terminal does not exist or verify that the context of described terminal is failed by described shortMAC-I, then described source base station returns failed message to described target BS, carry failure cause in this failed message, described failure cause is that context does not exist or terminal authentication failure.
Further, in described response message, at least comprise described context matches information, also comprise described shortMAC-I and/or described RRC and rebuild the ECGI attempting community;
After described target BS receives described response message, the context of described terminal is mated according to described context matches information wherein, and rebuild by described shortMAC-I wherein and/or described RRC the context that the ECGI attempting community verifies described terminal, if be proved to be successful, then carried out RRC according to the contextual information of the described terminal in described response message and re-establish flow process.
Further, in described failed message, at least comprise described context matches information, or also comprise the ECGI that described shortMAC-I and/or described RRC rebuilds trial community;
After described target BS receives described failed message, the context of described terminal is mated according to described context matches information wherein, and rebuild by described shortMAC-I wherein and/or described RRC the context that the ECGI attempting community verifies described terminal, if be proved to be successful, then determine according to described failure cause the contextual flow process initiating to obtain described terminal whether again.
Further, described context matches information comprises the Radio Network Temporary Identifier (C-RNTI) of described terminal in cell-of-origin and the physical address (PCI) of described cell-of-origin.
Further, described terminal carries out RRC when re-establishing, and send RRC to described target BS and re-establish request message, described RRC re-establishes in request message the PCI information comprising cell-of-origin;
Described target BS matches described source base station according to the PCI information that the RRC received re-establishes in request message, if match multiple source base station, then described target BS sends the request message of described acquisition terminal context information to the multiple source base stations matched.
Further, the specific identifier that described target BS is described terminal distribution is also comprised in described request message;
After described source base station receives the request message of described acquisition terminal context information, in the response message returned or failed message, at least comprise the specific identifier that described target BS distributes, or also to comprise described source base station be the corresponding specific identifier of described terminal distribution;
After target BS receives described response message or failed message, identify described terminal according to the specific identifier that described target BS wherein distributes.
Further, the specific identifier of described target BS to be the specific identifier of described terminal distribution and described source base station be described terminal distribution comprises X2 interface application protocol identification or S1 interface application protocol identification or things number.
Present invention also offers the acquisition methods of another kind of terminal contexts, described method comprises:
If the target BS belonging to Target cell that terminal carries out selecting when RRC re-establishes does not have the contextual information of described terminal, then send the request message obtaining terminal context information to source base station, in this request message, comprise context matches information, shortMAC-I and RRC rebuilds the ECGI attempting community;
After described source base station receives the request message of described acquisition terminal context information, the context of terminal according to described context matches information matches wherein, and the context of described terminal is verified by described shortMAC-I, if be proved to be successful, and the context of described terminal exists, then when allowing described terminal switch or incision Target cell, returning response message to described target BS, in this response message, carrying the contextual information of described terminal.
Further, if the context failure that the context of described terminal does not exist, shortMAC-I verifies described terminal, cell-of-origin forbid that to Target cell switching or Target cell are the communities of described terminal disables incision, then described source base station returns failed message to described target BS, carry failure cause in this failed message, described failure cause is that context does not exist, terminal authentication failed, forbids switching or forbid incision.
Present invention also offers a kind of acquisition system of terminal contexts, the RRC being applied to terminal re-establishes, and described system comprises the target BS that source base station and terminal carry out selecting when RRC re-establishes, wherein:
Described target BS is used for, receive RRC that terminal sends when re-establishing request, if there is no the contextual information of described terminal, the PCI information then re-established in request message according to described RRC matches described source base station, and the request message obtaining terminal context information is sent to described source base station, comprise context matches information in this request message, shortMAC-I and RRC rebuilds the ECGI attempting community;
Described source base station is used for, after receiving the request message of described acquisition terminal context information, the context of terminal according to described context matches information matches wherein, and the context of described terminal is verified by described shortMAC-I, if be proved to be successful, the context of described terminal exist, then return response message to described target BS, in this response message, carry the contextual information of described terminal; If verify that the context failure of described terminal or the context of described terminal do not exist, then return failed message to described target BS, carry failure cause in this failed message, described failure cause is that context does not exist or terminal authentication failure.
Further, described source base station also for, in the described response message returned or described failed message, comprise described context matches information, and described shortMAC-I and/or described RRC rebuild the ECGI attempting community;
Described target BS also for, after receiving described response message, the context of described terminal is mated according to described context matches information wherein, and rebuild by described shortMAC-I wherein and/or described RRC the context that the ECGI attempting community verifies described terminal, if be proved to be successful, then carried out RRC according to the contextual information of the described terminal in described response message and re-establish flow process; After receiving described failed message, the context of described terminal is mated according to described context matches information wherein, and rebuild by described shortMAC-I wherein and/or described RRC the context that the ECGI attempting community verifies described terminal, if be proved to be successful, then determine according to described failure cause the contextual flow process initiating to obtain described terminal whether again.
Further, described target BS also for, for described terminal distribution specific identifier and be included in the request message of described acquisition terminal context information; And, after receiving response message or failed message, identify described terminal according to the specific identifier that described target BS wherein distributes;
Described source base station also for, after receiving the request message of described acquisition terminal context information, in the response message returned or failed message, at least comprise the specific identifier that described target BS distributes, or also to comprise the specific identifier distributed according to described target BS be the corresponding specific identifier of described terminal distribution.
Present invention also offers the acquisition system of another kind of terminal contexts, the RRC being applied to terminal re-establishes, and described system comprises the target BS that source base station and terminal carry out selecting when RRC re-establishes, wherein:
Described target BS is used for, receive RRC that terminal sends when re-establishing request, if there is no the contextual information of described terminal, the PCI information then re-established in request message according to described RRC matches described source base station, and the request message obtaining terminal context information is sent to described source base station, comprise context matches information in this request message, shortMAC-I and RRC rebuilds the ECGI attempting community;
Described source base station is used for, after receiving the request message of described acquisition terminal context information, the context of terminal according to described context matches information matches wherein, and the context of described terminal is verified by described shortMAC-I, if be proved to be successful, the context of described terminal exist, and allow described terminal switch or incision Target cell, then return response message to described target BS, in this response message, carry the contextual information of described terminal; If verify that the context of described terminal context that is failed, described terminal does not exist, cell-of-origin forbids that to Target cell switching or Target cell are the communities of described terminal disables incision, then return failed message to described target BS, carry failure cause in this failed message, described failure cause is that context does not exist, terminal authentication failed, forbids switching or forbid incision.
Further, described source base station also for, in the described response message returned or described failed message, comprise described context matches information, and described shortMAC-I and/or described ECGI;
Described target BS also for, after receiving described response message, the context of described terminal is mated according to described context matches information wherein, and rebuild by described shortMAC-I wherein and/or described RRC the context that the ECGI attempting community verifies described terminal, if be proved to be successful, then carried out RRC according to the contextual information of the described terminal in described response message and re-establish flow process; After receiving described failed message, the context of described terminal is mated according to described context matches information wherein, and rebuild by described shortMAC-I wherein and/or described RRC the context that the ECGI attempting community verifies described terminal, if be proved to be successful, then determine according to described failure cause the contextual flow process initiating to obtain described terminal whether again.
Further, described target BS also for, for described terminal distribution specific identifier and be included in the request message of described acquisition terminal context information; And, after receiving response message or failed message, identify described terminal according to the specific identifier that described target BS wherein distributes;
Described source base station also for, after receiving the request message of described acquisition terminal context information, in the response message returned or failed message, at least comprise the specific identifier that described target BS distributes, or also to comprise the specific identifier distributed according to described target BS be the corresponding specific identifier of described terminal distribution.
Adopt the present invention program, make can obtain UE context accurately between base station, thus improve the success rate that RRC re-establishes, improve wireless network performance, better experience to user.
Accompanying drawing explanation
Fig. 1 is the contextual information successful schematic flow sheet of target BS to source base station acquisition terminal of the embodiment of the present invention;
Fig. 2 is the schematic flow sheet of target BS to the contextual information failure of source base station acquisition terminal of the embodiment of the present invention.
Embodiment
Core concept of the present invention is, adopts the unique identification of terminal in the acquisition process of UE context, such as, use shortMAC-I to verify UE contextual information, and/or the specific identifier utilizing base station to distribute for UE is to mate UE context, etc.Like this, between target BS and source base station, can accurately obtain UE context, thus the success rate that RRC re-establishes can be improved.
Based on above-mentioned thought, the present invention adopts following technical proposals:
Terminal carries out wireless heterogeneous networks (RRC) if the target BS belonging to Target cell selected when re-establishing does not have the contextual information of described terminal, then send the request message obtaining UE context information to source base station, in this request message, comprise context matches information, shortMAC-I and RRC rebuilds the ECGI attempting community;
After source base station receives above-mentioned request message, mate UEcontext according to context matches information wherein, and verify UE context by shortMAC-I, if be proved to be successful, and this UE context exists, then return response message to target BS, carry UE context information.
Wherein, if source base station is according to shortMAC-I authentication failed, or UE context does not exist, then return failed message to target BS, carries failure cause.
Further, in the response message that source base station returns or failed message, at least also comprise context matches information, described shortMAC-I and/or described ECGI can also be comprised;
After target BS receives the described response message or failed message that source base station returns, UE context is mated according to context matches information wherein, and verify U Econtext by shortMAC-I and/or ECGI, after being proved to be successful, if response message, then carry out RRC according to the context of described terminal and re-establish flow process; If failed message, determine whether initiate UE context acquisition process again according to failure cause.
Wherein, described context matches information comprises the C-RNTI of UE in cell-of-origin, the PCI of cell-of-origin.
Described UE context information, refer to UE trigger before RRC re-establishes contextual information in the serving cells.
Further, UE is when carrying out RRC and re-establishing, and send RRC to described target BS and re-establish request message, this RRC re-establishes in request message the PCI information comprising cell-of-origin;
If target BS matches multiple source base station by the PCI information that described RRC re-establishes in request message, then send to the multiple base stations matched the request message obtaining UE context information.
Further, target BS send acquisition UE context information request message in can also comprise target BS be UE distribute specific identifier;
Source base station returns response message or failed message to target BS after receiving the request message of above-mentioned acquisition UE context information, comprises the specific identifier of the UE that target BS distributes, or also comprises the specific identifier that source base station is this UE distribution;
After target BS receives above-mentioned response message or failed message, the specific identifier according to the UE of target BS distribution wherein identifies UE context.
Further, the specific identifier of described UE can be X2AP id (X2 Application ProtocolIdentifier, X2 interface application protocol identification) and/or S1AP id (S1 Application ProtocolIdentifier, S1 interface application protocol identification) and/or transaction number (Transaction Identifier, referred to as TI).
Wherein, described cell-of-origin refers to that UE carries out the Serving cell before RRC re-establishes, Target cell refers to that RRC re-establishes in program and selects to carry out the community that RRC re-establishes trial, and the base station belonging to cell-of-origin is source base station, and the base station belonging to Target cell is target BS.
Further, the failure cause in above-mentioned failed message comprises: authentication failed, UE Context do not exist.
In addition, alternatively, source base station can also be arranged to: even if be proved to be successful, and there is UE Context, but when if cell-of-origin forbids that to Target cell switching or Target cell are the communities of described terminal disables incision, then will return failed message, now, the failure cause carried in failed message is that cell-of-origin forbids that to Target cell switching or Target cell are the communities etc. of described terminal disables incision.
For LTE system, in conjunction with the drawings and the specific embodiments the enforcement of technical solution of the present invention will be described in further detail below.
In LTE system, UE triggers after RRC re-establishes in the cell-a of eNB-a, carries out community selection, and UE selects the cell-b in eNB-b to carry out RRC as Target cell to re-establish.Then UE sends RRC and re-establishes request message to eNB-b, rebuilds the ECGI attempting community cell-b in this message containing UE at the C-RNTI of cell-of-origin cell-a, PCI, RRC of cell-of-origin cell-a, and shortMAC-I.ENB-b receives this RRC and re-establishes request message, if do not have the context information of this UE in eNB-b, then eNB-b can initiate UE context acquisition process.
Embodiment one
Adopt PCI, C-RNTI and shortMAC-I to carry out unique identification UE in the present embodiment, see Fig. 1 and Fig. 2, receive RRC and re-establish the target BS of request message when obtaining UE Context information, specifically comprise the steps:
Step 101, eNB-b sends message 1 to eNB-a, acquisition request UE context, comprise UE in message 1 and rebuild at the C-RNTI of cell-of-origin cell-a, PCI, shortMAC-I and RRC of cell-of-origin cell-a the Cell Global Identity ECGI attempting community cell-b, alternatively, the indication information etc. of acquisition request UE Context can also be comprised;
In this step, eNB-b re-establishes the base station eNB-a of the PCI information determination acquisition request UE context in message according to the RRC received, if eNB-b has matched multiple base station according to PCI information, then sends message 1 to all base stations matched;
Step 102, eNB-a receives the message 1 of acquisition request UE context, UE context is mated according to PCI and C-RNTI wherein, if have shortMAC-I in message 1, then verify this UE context with shortMAC-I, whether the shortMAC-I value namely compared in message 1 is consistent with shortMAC-I value corresponding in base station, if two values are consistent, then represent and is proved to be successful.If be proved to be successful, and in eNB-a, there is corresponding UE Context information, then eNB-a sends message 2 and returns UE Context information to eNB-b, at least comprise UE Context information, the C-RNTI of UE at cell-of-origin cell-a, the PCI of cell-of-origin cell-a in message 2, also comprise shortMAC-I and/or RRC and rebuild the Cell Global Identity ECGI etc. attempting community cell-b; If authentication failed, or checking is consistent, but UE Context information does not exist, then eNB-a sends message 3 and returns UE Context acquisition failed message to eNB-b, the C-RNTI of UE at cell-of-origin cell-a, the PCI of cell-of-origin cell-a can be comprised in message 3, also comprise the Cell Global Identity ECGI of shortMAC-I (in message 1) and/or cell-b, and failure cause, this failure cause is that UE Context does not exist or terminal authentication failure;
In addition, according to the embody rule strategy of base station, if cell-a to cell-b forbids community that the community cell-b switched, RRC re-establishes is that UE forbids the situation that the community etc. cut does not allow RRC to rebuild, transmission message 3 is returned UE Context to eNB-b and obtains failed message by eNB-a, even if shortMAC-I value is consistent, and there is UE Context information, now, failure cause switches or forbids incision etc. for forbidding.
Step 103, if eNB-b receives message 2, then according to PCI, C-RNTI wherein, and ECGI and/or shortMAC-I determines UE Context, namely carry out UE Context checking, if authentication failed, then abandon this message 2, if be proved to be successful, then eNB-b is according to the UE context information content obtained in message 2, carries out the flow process that RRC re-establishes; If eNB-b receives message 3, according to PCI, C-RNTI wherein, and ECGI and/or shortMAC-I determines UE Context, namely UE Context checking is carried out, if be proved to be successful, determine whether initiating UE context acquisition process again according to failure cause wherein, if authentication failed, then abandon message 3.
Embodiment two
See Fig. 1 and Fig. 2, the UE context acquisition process of the present embodiment specifically comprises the steps:
Step 201, eNB-b sends message 1 to eNB-a, acquisition request UE context, comprises UE and rebuild at the C-RNTI of cell-of-origin cell-a, PCI, shortMAC-I and RRC of cell-of-origin cell-a the ECGI attempting community cell-b, and eNB-b is the special mark I that UE distributes in message 1;
Wherein, eNB-b is the special mark I that UE distributes is a mark unique in eNB-b, and eNB-b receives the message containing this mark, can unique index to specific UE.
Described special mark I can be X2AP id (X2 application protocol identifier, X2 interface application protocol identification) and or S1AP id (S1 application protocol identifier, S1 interface application protocol identification) and or transaction number (Transaction identifier).Wherein, message 1 is transmitted by X2, the special mark I of UE can be X2AP id and or transaction number; Message 1 is transmitted by S1 mouth, and the special mark I of UE can be S1AP id and or transaction number.
In addition, the indication information etc. of acquisition request UE Context can also be comprised in message 1;
Step 202, eNB-a receives the message 1 of acquisition request UE context, UE context is mated according to PCI and C-RNTI wherein, if have shortMAC-I in message 1, then verify this UE with shortMAC-I, eNB-a can also distribute the special mark II of UE corresponding with it according to the special mark I of UE, if checking is consistent, and there is corresponding UE Context information in eNB-a, then eNB-a sends message 2 and returns UE Context information to eNB-b, the special mark II of special mark I and/or UE containing UE Context information, UE in message 2, if checking is consistent, but UE Context information does not exist, or cell-a to cell-b community forbids that the community cell-b switched or RRC re-establishes is the community that UE forbids cutting, or authentication failed, then eNB-a sends message 3 and returns UEContext acquisition failure response to eNB-b, the special mark I of failure cause and UE is comprised in message 3, the special mark II of UE can also be comprised, this failure cause can be that UE Context does not exist, terminal authentication failure, cell-a to cell-b forbids community switching, the community cell-b that RRC re-establishes is the community etc. that UE forbids cutting,
Wherein, eNB-b sends the message of the special mark I distributed containing UE to eNB-a, eNB-a can distribute one at the inner unique special mark II of eNB-a for this UE, special mark I containing UE in the message that follow-up this UE between eNB-b and eNB-a is correlated with and identify II specially, eNB-b and eNB-a receiving message just can according to the special mark I of UE with or identify II specially and uniquely determine specific UE.
If message 2 is transmitted by X2, the special mark II of UE can be X2AP id and/or transaction number; If message 2 is transmitted by S1 mouth, the special mark II of UE can be S1AP id and/or transaction number.
If message 3 is transmitted by X2, the special mark II of UE can be X2AP id and/or transaction number; Message 3 is transmitted by S1 mouth, and the special mark II of UE can be S1AP id and/or transaction number.
Step 203, if eNB-b receives message 2, then identifies the context of UE, and according to the UE context information obtained in message 2, carries out the flow process that RRC re-establishes according to the special mark I of the wherein UE special mark II of UE (or together with); If eNB-b receives message 3, then identify the Context of UE according to the special mark I of special mark II and/or UE of UE wherein, and determine whether initiating UE context acquisition process again according to failure cause wherein.
Embodiment three
See Fig. 1 and Fig. 2, the UE context acquisition process of the present embodiment specifically comprises the steps:
Step 301, eNB-b sends message 1 to eNB-a, acquisition request UE context, comprises UE and rebuild at the C-RNTI of cell-of-origin cell-a, PCI, shortMAC-I and RRC of cell-of-origin cell-a the ECGI attempting community cell-b, and eNB-b is the special mark I that UE distributes in message 1;
The special mark I of described UE can be X2AP id (X2 application protocolidentifier, X2 interface application protocol identification) and or S1AP id (S1 application protocolidentifier, S1 interface application protocol identification) and or transaction number (Transaction identifier).Wherein, message 1 is transmitted by X2, the special mark I of UE can be X2AP id and or transaction number; Message 1 is transmitted by S1 mouth, and the special mark I of UE can be S1AP id and or transaction number.
In addition, the indication information etc. of acquisition request UE Context can also be comprised in message 1;
Step 302, eNB-a receives the message 1 of acquisition request UE context, UE context is mated according to PCI and C-RNTI wherein, and verify UEcontext according to the shortMAC-I in message 1, eNB-a can also distribute the special mark II of UE corresponding with it according to the special mark I of UE, if checking is consistent, and there is UE Context information, then eNB-a sends message 2 and returns UE Context information to eNB-b, containing UE Context information in message 2, UE is at the C-RNTI of cell-of-origin cell-a, the PCI of cell-of-origin cell-a, alternatively, the ECGI of shortMAC-I and/or cell-b can also be comprised in message 2, the special mark II of special mark I and/or UE of UE, if checking is consistent, but UE Context information does not exist or Cell-a to Cell-b community forbids that the community cell-b switched or RRC re-establishes is the community that UE forbids cutting, or authentication failed, then eNB-a sends message 3 and returns UE Context acquisition failure response to eNB-b, containing failure cause, the C-RNTI of UE at cell-of-origin cell-a, the PCI of cell-of-origin cell-a in message 3, the special mark I of ECGI, UE of shortMAC-I and/or cell-b, alternatively, the special mark II etc. of UE can also be comprised in message 2,
Failure cause wherein can be that UE Context does not exist, terminal authentication failed, cell-a to cell-b community forbids that the community cell-b switched, RRC re-establishes is the community etc. that UE forbids cutting.
Wherein, if message 2 is transmitted by X2, the special mark II of UE can be X2AP id and/or transaction number; If message 2 is transmitted by S1 mouth, the special mark II of UE can be S1APid and/or transaction number.
If message 3 is transmitted by X2, the special mark II of UE can be X2AP id and/or transaction number; Message 3 is transmitted by S1 mouth, and the special mark II of UE can be S1AP id and/or transaction number.
Step 303, if eNB-b receives message 2, then determine UE Context according to PCI, C-RNTI and shortMAC-I wherein and/or ECGI, namely carry out UE Context checking, if authentication failed, then abandon this message 2, if be proved to be successful, then identify the context of UE according to the special mark I of the wherein UE special mark II of UE (or together with), and according to the UE context information obtained in message 2, carry out the flow process that RRC re-establishes; If eNB-b receives message 3, then determine UE Context according to PCI, C-RNTI and shortMAC-I wherein, namely UE Context checking is carried out, if authentication failed, then abandon this message 2, if be proved to be successful, then identified the Context of UE according to the special mark I of special mark II and/or UE of UE wherein, and determine whether initiating UE context acquisition process again according to failure cause wherein.
Wherein, the message 1,2 and 3 in above-described embodiment can be that independently terminal contexts obtains request message, terminal contexts obtains response message, terminal contexts obtains failed message respectively, or other X2 mouth or S1 mouth message.
In addition, additionally provide a kind of acquisition system (not shown) of terminal contexts in the embodiment of the present invention, the RRC for terminal re-establishes, and this system comprises the target BS that source base station and terminal carry out selecting when RRC re-establishes, wherein:
Described target BS is used for, receive RRC that terminal sends when re-establishing request, if there is no the contextual information of described terminal, the PCI information then re-established in request message according to described RRC matches described source base station, and the request message obtaining terminal context information is sent to described source base station, comprise context matches information in this request message, shortMAC-I and RRC rebuilds the ECGI attempting community;
Described source base station is used for, after receiving the request message of described acquisition terminal context information, the context of terminal according to described context matches information matches wherein, and the context of described terminal is verified by described shortMAC-I, if be proved to be successful, the context of described terminal exist, then return response message to described target BS, in this response message, carry the contextual information of described terminal; If verify that the context failure of described terminal or the context of described terminal do not exist, then return failed message to described target BS, carry failure cause in this failed message, described failure cause is that context does not exist or terminal authentication failure.
Further, described source base station also for, in the described response message returned or described failed message, comprise described context matches information, and described shortMAC-I and/or described RRC rebuild the ECGI attempting community;
Described target BS also for, after receiving described response message, the context of described terminal is mated according to described context matches information wherein, and rebuild by described shortMAC-I wherein and/or described RRC the context that the ECGI attempting community verifies described terminal, if be proved to be successful, then carried out RRC according to the contextual information of the described terminal in described response message and re-establish flow process; After receiving described failed message, the context of described terminal is mated according to described context matches information wherein, and rebuild by described shortMAC-I wherein and/or described RRC the context that the ECGI attempting community verifies described terminal, if be proved to be successful, then determine according to described failure cause the contextual flow process initiating to obtain described terminal whether again.
Further, described target BS also for, for described terminal distribution specific identifier and be included in the request message of described acquisition terminal context information; And, after receiving response message or failed message, identify described terminal according to the specific identifier that described target BS wherein distributes;
Described source base station also for, after receiving the request message of described acquisition terminal context information, in the response message returned or failed message, at least comprise the specific identifier that described target BS distributes, or also to comprise the specific identifier distributed according to described target BS be the corresponding specific identifier of described terminal distribution.
In addition, additionally provide the acquisition system of another kind of terminal contexts in the embodiment of the present invention, the RRC being applied to terminal re-establishes, and this system comprises the target BS that source base station and terminal carry out selecting when RRC re-establishes, wherein:
Described target BS is used for, receive RRC that terminal sends when re-establishing request, if there is no the contextual information of described terminal, the PCI information then re-established in request message according to described RRC matches described source base station, and the request message obtaining terminal context information is sent to described source base station, comprise context matches information in this request message, shortMAC-I and RRC rebuilds the ECGI attempting community;
Described source base station is used for, after receiving the request message of described acquisition terminal context information, the context of terminal according to described context matches information matches wherein, and the context of described terminal is verified by described shortMAC-I, if be proved to be successful, the context of described terminal exist, and allow described terminal switch or incision Target cell, then return response message to described target BS, in this response message, carry the contextual information of described terminal; If verify that the context of described terminal context that is failed, described terminal does not exist, cell-of-origin forbids that to Target cell switching or Target cell are the communities of described terminal disables incision, then return failed message to described target BS, carry failure cause in this failed message, described failure cause is that context does not exist, terminal authentication failed, forbids switching or forbid incision.
Further, described source base station also for, in the described response message returned or described failed message, comprise described context matches information, and described shortMAC-I and/or described ECGI;
Described target BS also for, after receiving described response message, the context of described terminal is mated according to described context matches information wherein, and rebuild by described shortMAC-I wherein and/or described RRC the context that the ECGI attempting community verifies described terminal, if be proved to be successful, then carried out RRC according to the contextual information of the described terminal in described response message and re-establish flow process; After receiving described failed message, the context of described terminal is mated according to described context matches information wherein, and rebuild by described shortMAC-I wherein and/or described RRC the context that the ECGI attempting community verifies described terminal, if be proved to be successful, then determine according to described failure cause the contextual flow process initiating to obtain described terminal whether again.
Further, described target BS also for, for described terminal distribution specific identifier and be included in the request message of described acquisition terminal context information; And, after receiving response message or failed message, identify described terminal according to the specific identifier that described target BS wherein distributes;
Described source base station also for, after receiving the request message of described acquisition terminal context information, in the response message returned or failed message, at least comprise the specific identifier that described target BS distributes, or also to comprise the specific identifier distributed according to described target BS be the corresponding specific identifier of described terminal distribution.
Should be appreciated that and the foregoing is only the preferred embodiments of the present invention, be not limited to the present invention, for a person skilled in the art, the present invention can have various modifications and variations.Within the spirit and principles in the present invention all, any amendment done, equivalent replacement, improvement etc., all should be included within protection scope of the present invention.
Claims (16)
1. an acquisition methods for terminal contexts, is characterized in that, described method comprises:
If the target BS belonging to Target cell that terminal carries out selecting when radio resource control RRC re-establishes does not have the contextual information of described terminal, then send the request message obtaining terminal context information to source base station, in this request message, comprise context matches information, short media interviews control integrity verification value shortMAC-I and RRC rebuilds the Cell Global Identity ECGI attempting community;
After described source base station receives the request message of described acquisition terminal context information, the context of terminal according to described context matches information matches wherein, and the context of described terminal is verified by described shortMAC-I, if be proved to be successful, and the context of described terminal exists, then return response message to described target BS, in this response message, carry the contextual information of described terminal.
2. the method for claim 1, is characterized in that,
If the context of described terminal does not exist or verify that the context of described terminal is failed by described shortMAC-I, then described source base station returns failed message to described target BS, carry failure cause in this failed message, described failure cause is that context does not exist or terminal authentication failure.
3. the method for claim 1, is characterized in that,
At least comprise described context matches information in described response message, also comprise described shortMAC-I and/or described RRC and rebuild the ECGI attempting community;
After described target BS receives described response message, the context of described terminal is mated according to described context matches information wherein, and rebuild by described shortMAC-I wherein and/or described RRC the context that the ECGI attempting community verifies described terminal, if be proved to be successful, then carried out RRC according to the contextual information of the described terminal in described response message and re-establish flow process.
4. method as claimed in claim 2, is characterized in that,
At least comprise described context matches information in described failed message, or also comprise the ECGI that described shortMAC-I and/or described RRC rebuilds trial community;
After described target BS receives described failed message, the context of described terminal is mated according to described context matches information wherein, and rebuild by described shortMAC-I wherein and/or described RRC the context that the ECGI attempting community verifies described terminal, if be proved to be successful, then determine according to described failure cause the contextual flow process initiating to obtain described terminal whether again.
5. the method as described in claim 1,2,3 or 4, is characterized in that,
Described context matches information comprises the Radio Network Temporary Identifier C-RNTI of described terminal in cell-of-origin and the physical address PCI of described cell-of-origin.
6. the method as described in claim 1,2,3 or 4, is characterized in that,
Described terminal carries out RRC when re-establishing, and send RRC to described target BS and re-establish request message, described RRC re-establishes in request message the PCI information comprising cell-of-origin;
Described target BS matches described source base station according to the PCI information that the RRC received re-establishes in request message, if match multiple source base station, then described target BS sends the request message of described acquisition terminal context information to the multiple source base stations matched.
7. the method as described in claim 1,2,3 or 4, is characterized in that,
The specific identifier that described target BS is described terminal distribution is also comprised in described request message;
After described source base station receives the request message of described acquisition terminal context information, in the response message returned or failed message, at least comprise the specific identifier that described target BS distributes, or also to comprise described source base station be the corresponding specific identifier of described terminal distribution;
After target BS receives described response message or failed message, identify described terminal according to the specific identifier that described target BS wherein distributes.
8. method as claimed in claim 7, is characterized in that,
The specific identifier of described target BS to be the specific identifier of described terminal distribution and described source base station be described terminal distribution comprises X2 interface application protocol identification or S1 interface application protocol identification or things number.
9. an acquisition methods for terminal contexts, is characterized in that, described method comprises:
If the target BS belonging to Target cell that terminal carries out selecting when RRC re-establishes does not have the contextual information of described terminal, then send the request message obtaining terminal context information to source base station, in this request message, comprise context matches information, shortMAC-I and RRC rebuilds the ECGI attempting community;
After described source base station receives the request message of described acquisition terminal context information, the context of terminal according to described context matches information matches wherein, and the context of described terminal is verified by described shortMAC-I, if be proved to be successful, and the context of described terminal exists, then when allowing described terminal switch or incision Target cell, returning response message to described target BS, in this response message, carrying the contextual information of described terminal.
10. method as claimed in claim 9, is characterized in that,
If the context failure that the context of described terminal does not exist, shortMAC-I verifies described terminal, cell-of-origin forbid that to Target cell switching or Target cell are the communities of described terminal disables incision, then described source base station returns failed message to described target BS, carry failure cause in this failed message, described failure cause is that context does not exist, terminal authentication failed, forbids switching or forbid incision.
The acquisition system of 11. 1 kinds of terminal contexts, the RRC being applied to terminal re-establishes, and it is characterized in that, described system comprises the target BS that source base station and terminal carry out selecting when RRC re-establishes, wherein:
Described target BS is used for, receive RRC that terminal sends when re-establishing request, if there is no the contextual information of described terminal, the PCI information then re-established in request message according to described RRC matches described source base station, and the request message obtaining terminal context information is sent to described source base station, comprise context matches information in this request message, shortMAC-I and RRC rebuilds the ECGI attempting community;
Described source base station is used for, after receiving the request message of described acquisition terminal context information, the context of terminal according to described context matches information matches wherein, and the context of described terminal is verified by described shortMAC-I, if be proved to be successful, the context of described terminal exist, then return response message to described target BS, in this response message, carry the contextual information of described terminal; If verify that the context failure of described terminal or the context of described terminal do not exist, then return failed message to described target BS, carry failure cause in this failed message, described failure cause is that context does not exist or terminal authentication failure.
12. systems as claimed in claim 11, is characterized in that,
Described source base station also for, in the described response message returned or described failed message, comprise described context matches information, and described shortMAC-I and/or described RRC rebuild the ECGI attempting community;
Described target BS also for, after receiving described response message, the context of described terminal is mated according to described context matches information wherein, and rebuild by described shortMAC-I wherein and/or described RRC the context that the ECGI attempting community verifies described terminal, if be proved to be successful, then carried out RRC according to the contextual information of the described terminal in described response message and re-establish flow process; After receiving described failed message, the context of described terminal is mated according to described context matches information wherein, and rebuild by described shortMAC-I wherein and/or described RRC the context that the ECGI attempting community verifies described terminal, if be proved to be successful, then determine according to described failure cause the contextual flow process initiating to obtain described terminal whether again.
13. systems as described in claim 11 or 12, is characterized in that,
Described target BS also for, for described terminal distribution specific identifier and be included in the request message of described acquisition terminal context information; And, after receiving response message or failed message, identify described terminal according to the specific identifier that described target BS wherein distributes;
Described source base station also for, after receiving the request message of described acquisition terminal context information, in the response message returned or failed message, at least comprise the specific identifier that described target BS distributes, or also to comprise the specific identifier distributed according to described target BS be the corresponding specific identifier of described terminal distribution.
The acquisition system of 14. 1 kinds of terminal contexts, the RRC being applied to terminal re-establishes, and it is characterized in that, described system comprises the target BS that source base station and terminal carry out selecting when RRC re-establishes, wherein:
Described target BS is used for, receive RRC that terminal sends when re-establishing request, if there is no the contextual information of described terminal, the PCI information then re-established in request message according to described RRC matches described source base station, and the request message obtaining terminal context information is sent to described source base station, comprise context matches information in this request message, shortMAC-I and RRC rebuilds the ECGI attempting community;
Described source base station is used for, after receiving the request message of described acquisition terminal context information, the context of terminal according to described context matches information matches wherein, and the context of described terminal is verified by described shortMAC-I, if be proved to be successful, the context of described terminal exist, and allow described terminal switch or incision Target cell, then return response message to described target BS, in this response message, carry the contextual information of described terminal; If verify that the context of described terminal context that is failed, described terminal does not exist, cell-of-origin forbids that to Target cell switching or Target cell are the communities of described terminal disables incision, then return failed message to described target BS, carry failure cause in this failed message, described failure cause is that context does not exist, terminal authentication failed, forbids switching or forbid incision.
15. systems as claimed in claim 14, is characterized in that,
Described source base station also for, in the described response message returned or described failed message, comprise described context matches information, and described shortMAC-I and/or described ECGI;
Described target BS also for, after receiving described response message, the context of described terminal is mated according to described context matches information wherein, and rebuild by described shortMAC-I wherein and/or described RRC the context that the ECGI attempting community verifies described terminal, if be proved to be successful, then carried out RRC according to the contextual information of the described terminal in described response message and re-establish flow process; After receiving described failed message, the context of described terminal is mated according to described context matches information wherein, and rebuild by described shortMAC-I wherein and/or described RRC the context that the ECGI attempting community verifies described terminal, if be proved to be successful, then determine according to described failure cause the contextual flow process initiating to obtain described terminal whether again.
16. systems as described in claims 14 or 15, is characterized in that,
Described target BS also for, for described terminal distribution specific identifier and be included in the request message of described acquisition terminal context information; And, after receiving response message or failed message, identify described terminal according to the specific identifier that described target BS wherein distributes;
Described source base station also for, after receiving the request message of described acquisition terminal context information, in the response message returned or failed message, at least comprise the specific identifier that described target BS distributes, or also to comprise the specific identifier distributed according to described target BS be the corresponding specific identifier of described terminal distribution.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201010111065.5A CN102143539B (en) | 2010-02-02 | 2010-02-02 | Method and system for acquiring context of terminal |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201010111065.5A CN102143539B (en) | 2010-02-02 | 2010-02-02 | Method and system for acquiring context of terminal |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN102143539A CN102143539A (en) | 2011-08-03 |
| CN102143539B true CN102143539B (en) | 2015-04-01 |
Family
ID=44410696
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201010111065.5A Active CN102143539B (en) | 2010-02-02 | 2010-02-02 | Method and system for acquiring context of terminal |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN102143539B (en) |
Families Citing this family (15)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102333352B (en) * | 2011-09-19 | 2014-03-19 | 新邮通信设备有限公司 | Method for reducing handover delay in LTE (long term evolution) system |
| CN103037451B (en) * | 2011-10-03 | 2017-04-12 | 华为技术有限公司 | Radio resource control connection reconstruction method, user equipment and base station |
| CN103220736B (en) * | 2012-01-19 | 2016-12-14 | 联芯科技有限公司 | The reconstruction object cell selection method of RRC connection reconstruction and device |
| EP2801227B1 (en) * | 2012-01-27 | 2018-05-30 | Huawei Technologies Co., Ltd. | Mobility robustness optimisation for radio link failure |
| CN102740344B (en) * | 2012-06-20 | 2015-06-10 | 大唐移动通信设备有限公司 | Method and system for counting successful times of switching in long term evolution (LTE) system |
| CN103929828A (en) * | 2013-01-16 | 2014-07-16 | 普天信息技术研究院有限公司 | RRC connection reconstruction enhancement method |
| US9730264B2 (en) * | 2014-12-10 | 2017-08-08 | Telefonaktiebolaget L M Ericsson (Publ) | Systems and methods providing improved success rate for RRC connection reestablishments |
| CN106792928A (en) * | 2015-11-23 | 2017-05-31 | 中国移动通信集团公司 | A kind of method and device of accessing terminal to network |
| CN107295515B (en) * | 2016-04-01 | 2022-07-19 | 北京三星通信技术研究有限公司 | Method and device for supporting context recovery of User Equipment (UE) between base stations |
| CN107426720B (en) * | 2016-05-23 | 2023-02-17 | 上海中兴软件有限责任公司 | Cross-node mobile context transmission method, UE and network node |
| CN110049577B (en) * | 2018-01-15 | 2021-02-02 | 大唐移动通信设备有限公司 | Method and device for reestablishing Radio Resource Control (RRC) |
| CN110351894B (en) * | 2018-04-04 | 2024-06-18 | 北京三星通信技术研究有限公司 | Method and equipment for authenticating UE |
| CN113242578A (en) * | 2018-08-10 | 2021-08-10 | 华为技术有限公司 | Method and device for data transmission |
| CN111615188B (en) * | 2019-02-22 | 2021-10-01 | 华为技术有限公司 | Data transmission method, device and computer storage medium |
| CN114125963A (en) * | 2021-11-22 | 2022-03-01 | 中国电信股份有限公司 | Radio Resource Control (RRC) connection reestablishment method and device |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101483898A (en) * | 2008-01-07 | 2009-07-15 | 华为技术有限公司 | Method and apparatus for accelerating RRC connection establishment |
| CN101610554A (en) * | 2008-06-16 | 2009-12-23 | 华为技术有限公司 | Switching, location area updating, the method and system of setting up ISR, equipment between network |
-
2010
- 2010-02-02 CN CN201010111065.5A patent/CN102143539B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101483898A (en) * | 2008-01-07 | 2009-07-15 | 华为技术有限公司 | Method and apparatus for accelerating RRC connection establishment |
| CN101610554A (en) * | 2008-06-16 | 2009-12-23 | 华为技术有限公司 | Switching, location area updating, the method and system of setting up ISR, equipment between network |
Non-Patent Citations (1)
| Title |
|---|
| 《SON_MRO_UEcontext-stage2》;Nokia Siemens Networks;《3GPP TSG-RAN WG3 meeting#66-bis》;20100122;3-4页 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN102143539A (en) | 2011-08-03 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102143539B (en) | Method and system for acquiring context of terminal | |
| US11805454B2 (en) | Method and apparatus for mobility management | |
| CN111757557B (en) | Method for supporting access to closed network, UE, base station and readable storage medium | |
| US11758609B2 (en) | Radio resource control RRC message processing method, apparatus, and system | |
| CN102300278B (en) | A kind of decision method of handoff scenario and system | |
| CN102026165B (en) | Method and system for identifying terminal | |
| JP5142417B2 (en) | Handover method for link failure recovery, radio equipment and base station for implementing this method | |
| CN104185227B (en) | CSG access control method and system under dual-connection architecture | |
| CN101959262B (en) | Method and device for notifying handover failure indication information | |
| US8600353B2 (en) | Methods and arrangements for communication channel re-establishment | |
| CN102215485B (en) | Method for guaranteeing safety of multi-carrier switching or reconstructing in multi-carrier communication system | |
| CN101848536B (en) | Radio resource control connection reestablishment method and base station | |
| CN101998466B (en) | Method and system for judging unexpected switched scene | |
| WO2016061785A1 (en) | Radio resource control (rrc) connection method, reconnection method, and apparatus | |
| CN101998664A (en) | Method, system and equipment for reestablishing radio resource control connection | |
| CN101848553B (en) | Reestablishing method of RRC (Radio Resource Control) connection in LTE (Long Term Evolution) system and base station | |
| CN104581843A (en) | Method of Handling Handover for Network of Wireless Communication System and Communication Device Thereof | |
| CN103108403B (en) | Across base station RRC connection reconstructions method and system | |
| KR20190017026A (en) | Multiple connection communication method and device | |
| CN118265185A (en) | Method for supporting access to closed network, UE, base station and readable storage medium |
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 |