CN101883430A - Radio resource control (RRC) connection reestablishment method - Google Patents
Radio resource control (RRC) connection reestablishment method Download PDFInfo
- Publication number
- CN101883430A CN101883430A CN 201010210868 CN201010210868A CN101883430A CN 101883430 A CN101883430 A CN 101883430A CN 201010210868 CN201010210868 CN 201010210868 CN 201010210868 A CN201010210868 A CN 201010210868A CN 101883430 A CN101883430 A CN 101883430A
- Authority
- CN
- China
- Prior art keywords
- message
- rab
- nas
- rrc
- reconfiguration
- 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.)
- Granted
Links
Images
Abstract
The invention discloses a radio resource control (RRC) connection reestablishment method. The method comprises the following steps that: in the application scenarios needing the transmission of a network attached storage (NAS) message, evolution node B (eNB) sends an RRC connection reestablishment message comprising a downlink NAS message to user equipment (UE); the UE carries an uplink NAS message in an RRC connection reestablishment completion message returned by the eNB after completing processing the RRC connection reestablishment; and eNB fills the uplink NAS message returned by the UE to an S1 interface message to send the message to a mobile management entity (MME). By the RRC connection reestablishment method of the invention, the transmission of the NAS message is completed through the RRC connection reestablishment completion message and the S1 interface message so as to avoid singly transmitting other messages used for the transmission of the NAS message, save null interface resources and the S1 interface resource and improve the resource utilization efficiency of a communication system.
Description
Technical field
The present invention relates to mobile communication technology, particularly relate to a kind of Radio Resource control (RRC) and connect method for reconfiguration.
Background technology
Long Term Evolution (Long Term Evolution, LTE) wireless network is the network of a flattening, wherein, evolved universal mobile communication system wireless access network (EvolvedUTRAN, E-UTRAN) by base station (Evolved Node Base, eNB) and the evolution packet switching center (Evolved Packet Core EPC) forms.Compare with 3G technology, the variation of LTE network maximum is that (Radio Access NetWork, (Radio NetWork controller RNC), has reduced network delay to wireless access network RAN) partly to have removed radio network controller.In E-UTRAN, a plurality of eNB form set, link to each other by a S1 interface with EPC, link to each other by X2 interface between each eNB.
Third generation partner program (3GPP) RRC protocol description the RRC of LTE system connect reconfiguration course, being used to revise RRC connects, this process specifically is applied among the several scenes, for example, foundation, modification, releasing wireless loading (RB), switching between the eNB or in eNB, and preparing, revise, discharging measurement etc.Connect in the various application scenarioss of reconfiguration course at RRC, have in the several scenes all and need between the eNB of E-UTRAN and UE, transmit Non-Access Stratum (NAS) specific messages.Table 1 connects the application scenarios tabulation of reconfiguration course for RRC, as shown in table 1, reconfiguration course is applied to connect (Attach) flow process, evolution RAB (E-RAB) sets up process and the E-RAB modification process all need transmit NAS message between eNB and UE when RRC connects, and the E-RAB dispose procedure also might transmit NAS message between eNB and UE, wherein, eNB is descending NAS message to the NAS message of UE transmission, and eNB carries descending NAS transmission of messages and gives UE in RRC connection reconfiguration message.
Fig. 1 is the signaling process figure that RRC connects method for reconfiguration in the prior art.As shown in Figure 1, eNB is connected the detailed process of reshuffling with RRC between the UE and comprises in the prior art
Table 1:RRC connects the tabulation of reconfiguration course application scenarios
| RRC connects the reconfiguration course application scenarios | RRC connects reconfiguration message and whether carries descending NAS message | Whether UE needs to reply up NAS message |
| The Attach flow process | Need | Need |
| E-RAB sets up | Need | Need |
| E-RAB revises | Need | Need |
| E-RAB discharges | Optional | Carry descending NAS message if RRC connects reconfiguration message, then needed the up NAS response of UE |
| RRC connects the reconfiguration course application scenarios | RRC connects reconfiguration message and whether carries descending NAS message | Whether UE needs to reply up NAS message |
| In the eNB/switch between eNB | Do not need | Do not need |
| The service request flow process | Do not need | Do not need |
Step 101:eNB sends RRC to UE and connects reconfiguration message, be RRCConnection Reconfiguration, when RRC connects reconfiguration course and is applied to the scene of the needs exchange NAS message described in the table 1, can carry descending NAS message among the RRC Connection Reconfiguration and direct transfer to UE.
Step 102:UE finishes RRC and connects reconfiguration process, connects to reshuffle to eNB answer RRC and finishes message, be i.e. RRC Connection Reconfiguration Complete.
Step 103:UE replys uplink message to eNB, i.e. UL InformationTransfer, with this message as the response of UE to NAS message among the RRC Connection Reconfiguration.
By said process as seen, 36331 and 36413 technical specifications according to existing 3GPP, after RRC connection reconfiguration course is finished, UE needs at first to reply RRCConnection Reconfiguration Complete to eNB, transmit at needs under the application scenarios of NAS message, UE also needs to continue to reply UL Information Transfer to eUB, in order to the up NAS message of independent transmission after replying RRC Connection Reconfiguration Complete.And, connect in the method for reconfiguration at existing RRC, after above-mentioned steps 103, similarly, eNB also need be after replying formerly the interface related response message of S1 to Mobility Management Entity (MME), continuation is replied up NAS message transfer to MME, i.e. Uplink NAS Transport is in order to the up NAS message of independent transmission.Because need to formerly control messages and NAS message all adopt respectively one independently message reply, this has not only increased the complexity of the processing procedure of UE and eNB, what is more important, also waste valuable interface-free resources and S1 interface resource, reduced the level of resources utilization of communication system.
Summary of the invention
The invention provides a kind of RRC and connect method for reconfiguration, adopt this method can improve the resource utilization of communication system.
For achieving the above object, technical scheme of the present invention is achieved in that
The invention discloses a kind of radio resource control RRC connection reconfiguration method, comprising:
Base station eNB sends RRC to user equipment (UE) and connects reconfiguration message, and described RRC connects in the reconfiguration message and comprises descending non access stratum NAS message;
UE finishes RRC and connects reconfiguration process, connects to reshuffle to eNB answer RRC and finishes message, and described RRC connection is reshuffled to finish and comprised up NAS message in the message;
The RRC connection that eNB replys UE is reshuffled the up NAS message of finishing in the message and is filled up in the S1 interface message, and this S1 interface message is sent to Mobility Management Entity MME.
Described RRC connects to reshuffle in the structure of finishing message and comprises: the NAS specific messages;
Described NAS specific messages is optional structure.
Described RRC connects method for reconfiguration and is applied to connect flow process, and then described S 1 interface message is that initial context is set up response message;
And/or,
Described RRC connection method for reconfiguration is applied to evolution RAB E-RAB and sets up process, and then described S1 interface message is that E-RAB sets up response message;
And/or,
Described RRC connects method for reconfiguration and is applied to the E-RAB modification process, and then described S1 interface message is that E-RAB revises response message;
And/or,
Described RRC connects method for reconfiguration and is applied to the E-RAB dispose procedure, and then described S1 interface message is that E-RAB discharges response message.
Described initial context is set up in the structure of response message and is comprised: Non-Access Stratum Packet Data Unit NAS-PDU;
Described NAS-PDU is optional structure.
Described initial context is set up in the structure of response message and comprised: E-RAB sets up tabulation;
Described E-RAB sets up in the tabulation and comprises: E-RAB sets up the project information element set;
Described E-RAB sets up in the project information element set and comprises: NAS-PDU.
Described E-RAB sets up in the structure of response message and comprises: NAS-PDU;
Described NAS-PDU is essential structure.
Described E-RAB sets up in the structure of response message and comprises: E-RAB sets up tabulation;
Described E-RAB sets up in the tabulation and comprises: E-RAB sets up the project information element set;
Described E-RAB sets up in the project information element set and comprises: NAS-PDU.
Comprise in the structure of described E-RAB modification response message: NAS-PDU;
Described NAS-PDU is essential structure.
Comprise in the structure of described E-RAB modification response message: E-RAB revises tabulation;
Described E-RAB revises in the tabulation and comprises: E-RAB revises project information element group;
Described E-RAB revises in the project information element group and comprises: NAS-PDU.
Comprise in the structure of described E-RAB release response message: NAS-PDU;
Described NAS-PDU is optional structure.
By above summary of the invention as seen, carrying out RRC under the application scenarios of needs transmission NAS message connects when reshuffling, UE is after finishing RRC connection reconfiguration process, connect to reshuffle to finish at the RRC that replys to eNB and carry up NAS message in the message, after eNB receives, should up NAS message be carried in the S1 interface message and send to MME, thereby connecting to reshuffle by RRC finishes the transmission that message and S1 interface message are finished NAS message, therefore do not need to send separately the message that other is used for the NAS transmission of messages, thereby saved interface-free resources and S1 interface resource, improved the level of resources utilization of communication system.
Description of drawings
Fig. 1 is the signaling process figure that RRC connects method for reconfiguration in the prior art;
Fig. 2 connects the signaling process figure of method for reconfiguration for the present invention first preferred embodiment RRC;
Fig. 3 connects the signaling process figure of method for reconfiguration for the present invention second preferred embodiment RRC.
Embodiment
In order to make the purpose, technical solutions and advantages of the present invention clearer, describe the present invention below in conjunction with the drawings and specific embodiments.
Basic thought of the present invention is, transmit at needs under the application scenarios of NAS message, connect in the reconfiguration course at RRC, eNB carries descending NAS message in the RRC connection reconfiguration message that sends to UE, UE is after finishing RRC connection reconfiguration process, connect to reshuffle to finish at the RRC that replys to eNB and carry up NAS message in the message, eNB is carried at up NAS message in the S1 interface message and sends to MME.
Enumerate a preferred embodiment below RRC connection method for reconfiguration of the present invention is carried out brief description.Fig. 2 connects the signaling process figure of method for reconfiguration for the present invention first preferred embodiment RRC.As shown in Figure 2, this method may further comprise the steps.
Step 201:eNB sends RRC to UE and connects reconfiguration message, and promptly RRCConnection Reconfiguration comprises descending NAS message in this message.
Step 202:UE finishes RRC and connects reconfiguration process, connects to reshuffle to eNB answer RRC and finishes message, and promptly RRC Connection Reconfiguration Complete comprises up NAS message in this message.
In this step, to finish message and carry up NAS message in order to realize connecting to reshuffle by RRC, need reshuffle the structure of finishing message to existing RRC connection makes amendment, reshuffle on the basis of finishing message structure in existing RRC connection, add a new structure, that is: NAS specific messages, this NAS specific messages is optional structure, a kind of preferred implementation is that the NAS private message types meets the definition of 36331 agreements.
The RRC connection that step 203:eNB replys UE is reshuffled the up NAS message of finishing in the message and is filled up in the S1 interface message, and this S1 interface message is sent to MME.
In this step, for the S1 interface message of carrying NAS, the RRC shown in the table 1 connects the S1 interface message that adopts in the various scenes of reconfiguration course application and has nothing in common with each other.Might need to transmit in the application scenarios of NAS four kinds shown in the table 1: be applied to the Attach flow process if RRC connects method for reconfiguration, then the S1 interface message is that initial context is set up response message.If RRC connection method for reconfiguration is applied to E-RAB and sets up process, then the S1 interface message is that E-RAB sets up response message.Be applied to the E-RAB modification process if RRC connects method for reconfiguration, then the S1 interface message is that E-RAB revises response message.Be applied to the E-RAB dispose procedure if RRC connects method for reconfiguration, then the S1 interface message is that E-RAB discharges response message.
Correspondingly, in order to realize carrying up NAS message, also need the structure of existing above-mentioned S1 message is made amendment by above-mentioned S1 message.
Table 2 is set up the structure list of response message for the initial context of the embodiment of the invention.Referring to table 2, to set up response message identical with initial context of the prior art, the initial context of the embodiment of the invention is set up and is comprised following structure in the response message: type of message (Message Type), the S1 applying portion identify label of MME side UE (MME UES1AP ID), the S1 applying portion identify label of eNB side UE (eNB UE S1AP ID), E-RAB sets up tabulation (E-RAB Setup List), E-RAB sets up failure tabulation (E-RABFailed to Setup List) and key diagnosis (Criticality Diagnostics), wherein, same as the prior art is, E-RAB sets up in the tabulation and comprises that E-RAB sets up project information element set (E-RAB Setup Item IEs), this E-RAB sets up and comprises following structure in the project information element set: E-RAB identify label (E-RAB ID), transport layer address (TransportLayer Address) and general packet radio service tunnel agreement (GPRS Tunnellingprotocol, GTP) tunnel termination point identification (GTP-TEID).Unlike the prior art be that in the embodiment of the invention, initial context is set up in the structure of response message and also comprised Non-Access Stratum Packet Data Unit (NAS-PDU).NAS-PDU is optional structure, is included in E-RAB and sets up in the project information element set.A kind of preferred implementation is that the information element type of NAS-PDU meets the 9.2.3.5 joint definition of 36413 agreements.
The initial context of table 2. embodiment of the invention is set up the structure list of response message
| Information element/group name claims | Type | Span | Information element type and normative reference | Semantic description | Key | Distribute key |
| ??Message?Type | Essential | ??9.2.1.1 | Be | Refusal | ||
| ??MME?UE?S1AP?ID | Essential | ??9.2.3.3 | Be | Ignore | ||
| ??eNB?UE?S1AP?ID | Essential | ??9.2.3.4 | Be | Ignore | ||
| ??E-RAB?Setup?List | Essential | Be | Ignore | |||
| ??＞E-RAB?Setup??Item?IEs | The maximum of 1 to E-RAB number | Each | Ignore | |||
| ??＞＞E-RAB?ID | Essential | ??9.2.1.2 | ||||
| ??＞＞Transport??Layer?Address | Essential | ??9.2.2.1 | ||||
| ??＞＞GTP-TEID | Essential | ??9.2.2.2 | ||||
| ??＞＞NAS-PDU | Optional | ??9.2.3.5 | ||||
| ??E-RAB?Failed?to??Setup?List | Optional | ??E-RAB??List??9.2.1.36 | An E-RAB ID can only be in one of them appearance of E-RAB Setup List IE or E-RAB Failed to Setup List | Be | Ignore | |
| ??Criticality??Diagnostics | Optional | ??9.2.1.21 | Be | Ignore |
Table 3 is set up the structure list of response message for the E-RAB of the embodiment of the invention.Referring to table 3, to set up response message identical with E-RAB of the prior art, the E-RAB of the embodiment of the invention sets up and comprises following structure in the response message: type of message (Message Type), the S1 applying portion identify label of MME side UE (MME UE S1AP ID), the S1 applying portion identify label of eNB side UE (eNB UE S1AP ID), E-RAB sets up tabulation (E-RAB Setup List), E-RAB sets up failure tabulation (E-RAB Failed to SetupList) and key diagnosis (Criticality Diagnostics), wherein, same as the prior art is, E-RAB sets up in the tabulation and comprises that E-RAB sets up project information element set (E-RAB Setup Item IEs), this E-RAB sets up and comprises following structure in the project information element set: E-RAB identify label (E-RAB ID), transport layer address (Transport LayerAddress) and general packet radio service tunnel agreement (GPRS Tunnellingprotocol, GTP) tunnel termination point identification (GTP-TEID).Unlike the prior art be that in the embodiment of the invention, E-RAB sets up in the structure of response message and also comprises NAS-PDU.Set up in the response message at E-RAB, NAS-PDU is essential structure, is included in E-RAB and sets up in the project information element set.A kind of preferred implementation is that the information element type of NAS-PDU meets the 9.2.3.5 joint definition of 36413 agreements.
The E-RAB of table 3. embodiment of the invention sets up the structure list of response message
| Information element/group name claims | Type | Span | Information element type and normative reference | Semantic description | Key | Distribute key |
| ??Message?Type | Essential | ??9.2.1.1 | Be | Refusal | ||
| ??MME?UE?S1AP?ID | Essential | ??9.2.3.3 | Be | Ignore | ||
| ??eNB?UE?S1AP?ID | Essential | ??9.2.3.4 | Be | Ignore | ||
| ??E-RAB?Setup?List | Optional | Be | Ignore | |||
| ??＞E-RAB?Setup??Item?IEs | The maximum of 1 to E-RAB number | Each | Ignore | |||
| ??＞＞E-RAB?ID | Essential | |||||
| ??＞＞Transport??Layer?Address | Essential | ??9.2.2.1 | ||||
| ??＞＞GTP-TEID | Essential | ??9.2.2.2 | ??eNB?TEID | |||
| ??＞＞NAS-PDU | Essential | ??9.2.3.5 | ||||
| ??E-RAB?Failed?to??Setup?List | Optional | ??E-RAB??List??9.2.1.36 | An E-RAB ID can only be in one of them appearance of E-RAB Setup List IE or E-RAB Failed to Setup List | Be | Ignore | |
| ??Criticality??Diagnostics | Optional | ??9.2.1.21 | Be | Ignore |
Table 4 is the structure list that the E-RAB of the embodiment of the invention revises response message.Referring to table 4, identical with E-RAB modification response message of the prior art, the E-RAB of the embodiment of the invention revises and comprises following structure in the response message: type of message (Message Type), the S1 applying portion identify label of MME side UE (MME UE S1AP ID), the S1 applying portion identify label of eNB side UE (eNB UE S1AP ID), E-RAB revises tabulation (E-RAB Modify List), E-RAB revises failure tabulation (E-RAB Failed toModify List) and key diagnosis (Criticality Diagnostics), wherein, same as the prior art is, E-RAB revises and comprises in the tabulation that E-RAB revises project information element group (E-RAB Modify Item IEs), and this E-RAB revises and comprises following structure in the project information element group: E-RAB identify label (E-RAB ID).Unlike the prior art be that in the embodiment of the invention, E-RAB revises in the structure of response message and also comprises NAS-PDU.Set up in the response message at E-RAB, NAS-PDU is essential structure, is included in E-RAB and revises in the project information element group.A kind of preferred implementation is that the information element type of NAS-PDU meets the 9.2.3.5 joint definition of 36413 agreements.
The E-RAB of table 4. embodiment of the invention revises the structure list of response message
| Information element/group name claims | Type | Span | Information element type and normative reference | Semantic description | Key | Distribute key |
| ??Message?Type | Essential | ??9.2.1.1 | Be | Refusal | ||
| ??MME?UE?S1AP?ID | Essential | ??9.2.3.3 | Be | Ignore | ||
| ??eNB?UE?S1AP?ID | Essential | ??9.2.3.4 | Be | Ignore | ||
| ??E-RAB?Modify?List | Optional | Be | Ignore | |||
| ??＞E-RAB?Modify??Item?IEs | The maximum of 1 to E-RAB number | Each | Ignore | |||
| ??＞＞E-RAB?ID | Essential | ??9.2.1.2 | ||||
| ??＞＞NAS-PDU | Essential | ??9.2.3.5 | ||||
| ??E-RAB?Failed?to??Modify?List | Optional | ??E-RAB??List??9.2.1.36 | An E-RAB ID can only be in one of them appearance of E-RAB Setup List IE or E-RAB Failed to Setup List | Be | Ignore | |
| ??Criticality??Diagnostics | Optional | ??9.2.1.21 | Be | Ignore |
Table 5 is the structure list that the E-RAB of the embodiment of the invention discharges response message.Referring to table 5, identical with E-RAB release response message of the prior art, the E-RAB of the embodiment of the invention discharges and comprises following structure in the response message: type of message (Message Type), the S1 applying portion identify label of MME side UE (MME UE S1AP ID), the S1 applying portion identify label of eNB side UE (eNB UE S1AP ID), E-RAB discharges tabulation (E-RAB Release List), the tabulation of E-RAB release failure (E-RAB Failed toRelease List) and key diagnosis (Criticality Diagnostics), wherein, E-RAB discharges and comprises in the tabulation that E-RAB discharges project information element set (E-RAB Release ItemIEs).Unlike the prior art be that in the embodiment of the invention, E-RAB discharges in the structure of response message and also comprises NAS-PDU.Discharge in the response message at E-RAB, NAS-PDU is optional structure.A kind of preferred implementation is that the information element type of NAS-PDU meets the 9.2.3.5 joint definition of 36413 agreements.
The E-RAB of table 5. embodiment of the invention discharges the structure list of response message
| Information element/group name claims | Type | Span | Information element type and normative reference | Semantic description | Key | Distribute key |
| ??Message?Type | Essential | ??9.2.1.1 | Be | Refusal | ||
| ??MME?UE?S1AP?ID | Essential | ??9.2.3.3 | Be | Ignore | ||
| ??eNB?UE?S1AP?ID | Essential | ??9.2.3.4 | Be | Ignore | ||
| ??E-RAB?Release?List | Optional | Be | Ignore | |||
| ??＞E-RAB?Release??Item?IEs | The maximum of 1 to E-RAB number | Each | Ignore | |||
| ??＞＞E-RAB?ID | Essential | ??9.2.1.2 | ||||
| ??E-RAB?Failed?to??Release?List | Optional | ??E-RAB??List??9.2.1.36 | An E-RAB ID can only be in one of them appearance of E-RAB Release List IE or E-RAB Fai1ed to Release List | Be | Ignore | |
| ??NAS-PDU | Optional | ??9.2.3.5 | Be | Ignore | ||
| ??Criticality??Diagnostics | Optional | ??9.2.1.21 | Be | Ignore |
More than by first preferred embodiment RRC of the present invention is connected the situation of reconfiguration course under various application scenarioss and is illustrated, below by second preferred embodiment, for the Attach flow process is an example, illustrate that RRC of the present invention connects the concrete application process of method for reconfiguration with the application scenarios.
Fig. 3 connects the signaling process figure of method for reconfiguration for the present invention second preferred embodiment RRC.In this preferred embodiment, be example, illustrate that RRC connects the detailed process of reshuffling with the Attach flow process.As shown in Figure 3, the RRC of the embodiment of the invention connects the application reshuffle in the Attach flow process and specifically may further comprise the steps.
Step 301:UE sends RRC connection request message, i.e. RRC ConnectionRequest to eNB.
Step 302:eNB replys the RRC connection to UE and sets up message, i.e. RRC ConnectionSetup.
Step 303:UE replys RRC connection setup complete message, i.e. RRCConnection Setup Complete to eNB.Carry NAS message in this message, this NAS message is connection request message, i.e. Attach Request.
The process that above-mentioned steps step 301 inserts for UE at random to step 303.
After step 304:eNB receives RRC Connection Setup Complete, be filled up to the NAS message of wherein carrying in the S1 interface message and send to MME.This NAS message is Attach Request; This S1 interface message is an initial UE information, i.e. Initial UEMessage.
After step 305:MME received the S1 interface message, if the context of this UE not in the MME, then MME initiated authorizing procedure, sends descending NAS message by eNB to UE, and this NAS message is authentication request message, i.e. Authentication Request.
After the success of step 306:UE authentication, reply up NAS message to MME, this NAS message is authentication response message, i.e. Authentication Response.
After step 307:MME receives Authentication Response, initiate initial context and set up flow process, send initial context to eNB and set up request message, be InitialContext Setup Request, wherein comprise descending NAS message, this descending NAS message is for accepting message, i.e. Attach Accept.
After step 308:eNB receives Initial Context Setup Request, initiate the security configuration flow process, send Security Mode Command message, i.e. S ecurity ModeCommand to UE.
Step 309:UE replys safe mode to eNB and finishes message, be i.e. Security Mode Complete after the security configuration success.
After step 310:eNB receives Security Mode Complete, send RRC to UE and connect reconfiguration message, promptly RRC Connection Reconfiguration wherein carries descending NAS message, this NAS message is for accepting message, i.e. Attach Accept.
After step 311:UE received RRC Connection Reconfiguration, the RRC entity of UE inside carried out RRC and connects the relevant treatment of reshuffling, and descending NAS message Attach Accept was sent to the NAS entity of UE inside.After the NAS entity handles finishes, reply up NAS message to the RRC entity, this NAS message is finished message, i.e. AttachComplete for connecting.The RRC entity is filled up to RRC with this NAS message and connects to reshuffle to finish and send to eNB in the message, and RRC connects and reshuffles that to finish message be RRC ConnectionReconfiguration Complete.This RRC connects to reshuffle and finishes message and adopt improved message structure, that is, RRC in the prior art connects and reshuffles on the basis of the message structure of finishing message, and increase a new structure: NAS specific messages, this structure are optional structure.
After step 312:eNB receives RRC Connection Reconfiguration Complete, reply initial context to MME and set up response message, be Initial Context SetupResponse, comprise the NAS message of carrying in the RRC Connection Reconfiguration Complete message in this message, i.e. Attach Complete.This initial context is set up response message and is adopted improved message structure, and concrete message structure is as described above shown in the table 2.
By above embodiment as seen, carrying out RRC under the application scenarios of needs transmission NAS message connects when reshuffling, eNB carries descending NAS message in the RRC connection reconfiguration message that sends to UE, UE is after finishing RRC connection reconfiguration process, connect to reshuffle to finish at the RRC that replys to eNB and carry up NAS message in the message, eNB is carried at up NAS message in the S1 interface message and sends to MME.Reshuffle the message structure of finishing message and S1 interface message and improve because RRC connected, in above-mentioned message, carry NAS message, finish the NAS transmission of messages, therefore do not need again to send NAS message separately with other interacting message, thereby saved interface-free resources and S1 interface resource, improved the level of resources utilization of communication system.
The above only is preferred embodiment of the present invention, and is in order to restriction the present invention, within the spirit and principles in the present invention not all, any modification of being made, is equal to replacement, improvement etc., all should be included within the scope of protection of the invention.
Claims (10)
1. a radio resource control RRC connection reconfiguration method is characterized in that, comprising:
Base station eNB sends RRC to user equipment (UE) and connects reconfiguration message, and described RRC connects in the reconfiguration message and comprises descending non access stratum NAS message;
UE finishes RRC and connects reconfiguration process, connects to reshuffle to eNB answer RRC and finishes message, and described RRC connection is reshuffled to finish and comprised up NAS message in the message;
The RRC connection that eNB replys UE is reshuffled the up NAS message of finishing in the message and is filled up in the S1 interface message, and this S1 interface message is sent to Mobility Management Entity MME.
2. RRC according to claim 1 connects method for reconfiguration, it is characterized in that,
Described RRC connects to reshuffle in the structure of finishing message and comprises: the NAS specific messages;
Described NAS specific messages is optional structure.
3. RRC according to claim 1 connects method for reconfiguration, it is characterized in that,
Described RRC connects method for reconfiguration and is applied to connect flow process, and then described S1 interface message is that initial context is set up response message;
And/or,
Described RRC connection method for reconfiguration is applied to evolution RAB E-RAB and sets up process, and then described S1 interface message is that E-RAB sets up response message;
And/or,
Described RRC connects method for reconfiguration and is applied to the E-RAB modification process, and then described S1 interface message is that E-RAB revises response message;
And/or,
Described RRC connects method for reconfiguration and is applied to the E-RAB dispose procedure, and then described S1 interface message is that E-RAB discharges response message.
4. RRC according to claim 3 connects method for reconfiguration, it is characterized in that,
Described initial context is set up in the structure of response message and is comprised: Non-Access Stratum Packet Data Unit NAS-PDU;
Described NAS-PDU is optional structure.
5. RRC according to claim 4 connects method for reconfiguration, it is characterized in that,
Described initial context is set up in the structure of response message and comprised: E-RAB sets up tabulation;
Described E-RAB sets up in the tabulation and comprises: E-RAB sets up the project information element set;
Described E-RAB sets up in the project information element set and comprises: NAS-PDU.
6. RRC according to claim 3 connects method for reconfiguration, it is characterized in that,
Described E-RAB sets up in the structure of response message and comprises: NAS-PDU;
Described NAS-PDU is essential structure.
7. RRC according to claim 6 connects method for reconfiguration, it is characterized in that,
Described E-RAB sets up in the structure of response message and comprises: E-RAB sets up tabulation;
Described E-RAB sets up in the tabulation and comprises: E-RAB sets up the project information element set;
Described E-RAB sets up in the project information element set and comprises: NAS-PDU.
8. RRC according to claim 3 connects method for reconfiguration, it is characterized in that,
Comprise in the structure of described E-RAB modification response message: NAS-PDU;
Described NAS-PDU is essential structure.
9. RRC according to claim 8 connects method for reconfiguration, it is characterized in that,
Comprise in the structure of described E-RAB modification response message: E-RAB revises tabulation;
Described E-RAB revises in the tabulation and comprises: E-RAB revises project information element group;
Described E-RAB revises in the project information element group and comprises: NAS-PDU.
10. RRC according to claim 1 connects method for reconfiguration, it is characterized in that,
Comprise in the structure of described E-RAB release response message: NAS-PDU;
Described NAS-PDU is optional structure.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2010102108686A CN101883430B (en) | 2010-06-28 | 2010-06-28 | Radio resource control (RRC) connection reestablishment method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2010102108686A CN101883430B (en) | 2010-06-28 | 2010-06-28 | Radio resource control (RRC) connection reestablishment method |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101883430A true CN101883430A (en) | 2010-11-10 |
| CN101883430B CN101883430B (en) | 2012-07-04 |
Family
ID=43055265
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2010102108686A Active CN101883430B (en) | 2010-06-28 | 2010-06-28 | Radio resource control (RRC) connection reestablishment method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101883430B (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2015172376A1 (en) * | 2014-05-16 | 2015-11-19 | 华为技术有限公司 | Method and device for accessing network by user equipment of voice service |
| CN105101312A (en) * | 2014-05-15 | 2015-11-25 | 中兴通讯股份有限公司 | Method and apparatus for upward data processing |
| CN110719621A (en) * | 2018-07-11 | 2020-01-21 | 大唐移动通信设备有限公司 | Processing method and device for non-access stratum (NAS) message transmission |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2008116128A2 (en) * | 2007-03-19 | 2008-09-25 | Qualcomm Incorporated | Selective phase connection establishment |
| CN101686563A (en) * | 2008-09-23 | 2010-03-31 | 三星电子株式会社 | Method for releasing resources in mobile communication system |
| CN101742576A (en) * | 2008-11-07 | 2010-06-16 | 华为技术有限公司 | Method and device for recovering reserved GBR load |
-
2010
- 2010-06-28 CN CN2010102108686A patent/CN101883430B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2008116128A2 (en) * | 2007-03-19 | 2008-09-25 | Qualcomm Incorporated | Selective phase connection establishment |
| CN101686563A (en) * | 2008-09-23 | 2010-03-31 | 三星电子株式会社 | Method for releasing resources in mobile communication system |
| CN101742576A (en) * | 2008-11-07 | 2010-06-16 | 华为技术有限公司 | Method and device for recovering reserved GBR load |
Non-Patent Citations (1)
| Title |
|---|
| 《3GPP TS 36.331 V9.3.0 (2010-06)》 20100618 3GPP TSG RAN Evolved Universal Terrestrial Radio Access (E-UTRA);Radio Resource Control (RRC);Protocol specification(Release 9) , 1 * |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105101312A (en) * | 2014-05-15 | 2015-11-25 | 中兴通讯股份有限公司 | Method and apparatus for upward data processing |
| CN105101312B (en) * | 2014-05-15 | 2019-11-19 | 南京中兴软件有限责任公司 | A kind of method and device of upstream data processing |
| WO2015172376A1 (en) * | 2014-05-16 | 2015-11-19 | 华为技术有限公司 | Method and device for accessing network by user equipment of voice service |
| CN110719621A (en) * | 2018-07-11 | 2020-01-21 | 大唐移动通信设备有限公司 | Processing method and device for non-access stratum (NAS) message transmission |
| CN110719621B (en) * | 2018-07-11 | 2020-10-02 | 大唐移动通信设备有限公司 | Processing method and device for non-access stratum (NAS) message transmission |
Also Published As
| Publication number | Publication date |
|---|---|
| CN101883430B (en) | 2012-07-04 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101541093B (en) | Method and device for establishing and maintaining interface connection | |
| CN104581843B (en) | For the processing delivering method and its communication device of the network-side of wireless communication system | |
| US9055442B2 (en) | Method and system for realizing integrity protection | |
| CN102158901B (en) | Method for performing terminal operation configuration at network side and network side device | |
| CN101848536B (en) | Radio resource control connection reestablishment method and base station | |
| US10595239B2 (en) | Data transmission method and device | |
| CN103052038B (en) | One sets up the contextual method and system of group calling, base station, cluster EPC | |
| CN113163512B (en) | Method for establishing radio bearer and base station | |
| CN101951689B (en) | Radio resource control (RRC) connection reestablishment method and base station | |
| CN104349505A (en) | Method of radio bearer establishment in dual connectivity | |
| CN103178938B (en) | Signaling optimization processing method, equipment and system | |
| CN102638900B (en) | Method and device for establishing connection | |
| CN102457825A (en) | Transmission method of data and equipment | |
| CN103782644B (en) | Information transferring method and system, agent equipment, the access device of back haul link | |
| CN107231623A (en) | A kind of data dispatching method, base station and system | |
| CN103428645A (en) | System and device for achieving cluster service | |
| CN101355785B (en) | Method and system for transmitting non-access layer information during switching procedure | |
| CN103874151A (en) | Load transferring method and equipment used during layered network organization | |
| WO2021026704A1 (en) | Wireless communication method and device | |
| CN103945470A (en) | Switching method, source communication node and target communication node | |
| CN104468312A (en) | Wireless relay station and method and system for connecting wireless relay station to core network | |
| US10212750B2 (en) | Method and device for establishing a dual connectivity between a user equipment and a MeNB and a SeNB, by providing the user equipment history information | |
| CN103428668A (en) | Tracking area updating method and device | |
| CN101272315A (en) | Packet data package transmission method, system and network appliance | |
| CN101883430B (en) | Radio resource control (RRC) connection reestablishment method |
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 | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20170831 Address after: 100070, No. 188, building 25, No. eighteen, South Fourth Ring Road, Fengtai District, Beijing, 1, 101 Patentee after: Beijing Haiyun Technology Co. Ltd. Address before: 510663, No. 3, color road, Science City, Guangzhou Development Zone, Guangdong Patentee before: New Post Communication Equipment Co., Ltd. |
|
| TR01 | Transfer of patent right |