CN1968493A - Lossless repositioning method - Google Patents
Lossless repositioning method Download PDFInfo
- Publication number
- CN1968493A CN1968493A CNA2005101149512A CN200510114951A CN1968493A CN 1968493 A CN1968493 A CN 1968493A CN A2005101149512 A CNA2005101149512 A CN A2005101149512A CN 200510114951 A CN200510114951 A CN 200510114951A CN 1968493 A CN1968493 A CN 1968493A
- Authority
- CN
- China
- Prior art keywords
- packet
- reorientation
- pdcp
- user side
- rlc
- 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
Landscapes
- Mobile Radio Communication Systems (AREA)
Abstract
The invention relates to a method for redirecting without damage, wherein said method comprises that: 1, at the PDCP of user and source RNC, presetting the sending data pack counter and receiving data pack counter, to calculate out the RLC sending data pack number and the RLC receiving data pack number; (2), when there is redirection, source RNC sends the stored counted value of receiving data pack counter to the user; (3), when the redirection is end, user PDCP sends the failed data pack to the target RNC. With said invention, it can transmit data in redirection without damage. And the invention resets the trigger condition of redirection, as when RNC-ID changes, UE redirects, to improve trigger accuracy; when RLC of UE needs to rebuild SRB2, stores the SN serial number of present SRB2, therefore, when redirection fails, it can switch back to source RNC.
Description
Technical field
The present invention relates to the communications field, relate in particular to the method that a kind of UE of realization (user terminal) supports harmless reorientation.
Background technology
In the cell mobile communication systems, because single base station limited coverage area, therefore, when user terminal in the process of conversation when a sub-district enters the another one sub-district, in order to guarantee communication continuity, system will transfer to this user terminal and getting in touch of former sub-district foundation on the new sub-district, and Here it is switches.Not only can between the different districts under the same base station controller, switch, but also can on different system, different base station controller, switch.When switching, change base station controller when user terminal, just need carry out the reorientation operation of UE.
In the TDD/CDMA mobile communication system, switch in the process of Target RNC, SRNS (SRNS Serving Radio Network Subsystem) reorientation equally also takes place at source RNC (radio network controller).Its repositioning process is as follows:
At first, the RRC of source RNC (radio resource control layer) sends reorientation message to the RLC of source RNC (wireless chain control layer), so that the RLC of indication source RNC is set to " STOP " state, and, the RRC of source RNC sends reorientation message to the PDCP of source RNC (packet data protocol convergence sublayer), does not obtain RLC established data bag so that PDCP will send and cached data packet is transferred on the RNC together;
Then, when UE receives the physical channel reconfiguration message of source RNC transmission, detect and whether carry DL_CounterSynchronisationInfo (down-going synchronous counter) in this reconfiguration message or new U-RNT (UTRAN side Radio Network Temporary Identifier symbol) is arranged in the RB reconfiguration message, if UE just assert that being redirected trigger condition sets up;
Then, the PDCP layer that the RLC of UE end is set to " STOP " state and local terminal begins data cached, and indication rebulids SRB2 to the RRC of UE to RLC, and the indication physical layer is carried out and switched;
At last, after Target RNC detected UE, UE reshuffled to Target RNC transmission physical channel and finishes message.And the RRC of UE sends RB2 to RLC respectively and rebuilds upright message, so that PDCP receives that this message begins later on to send business datum to RLC, and then the communicating by letter of beginning and Target RNC.
There is following problem in above-mentioned redirection process:
(1) in redirection process, can't accomplish the harmless transmission of high level data
Switch in the process of Target RNC at source RNC, the RLC entity of source RNC will be set to " stop " state, at this moment hold the data that send over from UE, and the RNC side all cannot correctly receive, after UE and Target RNC were set up corresponding RLC entity, data could correctly send and receive again.As seen the RLC entity stop the back to rebuilt during this period of time within, RLC can't guarantee the harmless transmission of high level data.
But for the speech business of delay sensitive, Packet Service is higher to the accuracy requirement of transfer of data.For fear of losing or invalid transmission of high level data, needing in case of necessity increases more protection to grouped data, so that realize the free of losses transmission of data, reduces the number of retransmissions of data.But, can't accomplish the data lossless transmission in the existing SRNC repositioning process, can not satisfy the demand of existing business, particularly Packet Service.
(2) there is the inaccurate technological deficiency of triggering in existing reorientation on UE
Carry DL_CounterSynchronisationInfo or have new U-RNTI just to think the establishment of relocation trigger condition in the RB reconfiguration message in receiving reconfiguration message as long as current UE end signaling surface protocol is regulation UE, the UE end begins to carry out the reorientation operation.Whether but not discussing needs the RNC-ID that resolves among the new U-RNTI to change.In fact, some special circumstances may occur, for example the RNT1 of a RNC is overtime unavailable, also may upgrade RNT1 with the RB reconfiguration message, but do not consider above-mentioned situation during existing relocation trigger, cause thus to be redirected and trigger inaccurate situation and take place.
When (three) there is handoff failure in existing repositioning process, if UE can not return the technological deficiency UE in repositioning process that cuts and switch to Target cell, can not be synchronous with Target cell, return when cutting process because UE RE-ESTABLISH SRB2 (setting up the SRB2 link) in reorientation, the news network side joint of finishing that causes back cutting can not receive, and can not realize back cutting.
Summary of the invention
The object of the present invention is to provide a kind of method of harmless reorientation, with solve in the prior art the RLC entity stop the back to rebuilt during this period of time within, RLC can't guarantee the technical problem of the harmless transmission of high level data.
For addressing the above problem, the invention discloses a kind of method of harmless reorientation, comprising:
(1) sets in advance transmission packet counter and receive the packet counter at the packet data protocol convergence sublayer PDCP of user side and source radio network controller RNC, be used for adding up respectively to the wireless chain control layer RLC of local terminal sending the number of packet and the number of reception local terminal RLC packet;
(2) when reorientation takes place, count value in the reception packet counter that source RNC preserves local terminal sends to user side, and the PDCP that the count value in the reception packet counter that user side is sent according to source RNC obtains local terminal has sent which packet does not send success in the packet that does not obtain confirming;
(3) after reorientation was finished, the PDCP of user side was sent to Target RNC with the successful packet that do not send that obtains in the step (2).
Step (2) also comprises: physical channel reshuffle finish after, count value in the reception packet counter that user side is preserved local terminal sends to Target RNC, and the PDCP that the count value in the reception packet counter that Target RNC is sent according to user side obtains local terminal has sent which packet does not send success in the packet that does not obtain confirming; Step (3) also comprises: the PDCP of Target RNC is sent to user side with the successful packet of described transmission.
The PDCP that user side obtains local terminal in the step (2) does not send successful packet and further is: if the count value UL_Receive_Sn in the reception packet counter that receives is in transmit queue scope, then the PDCP of user side will be in the transmit queue sequence of data packet number discharge smaller or equal to the packet of UL_Receive_Sn, simultaneously sequence of data packet number is moved into formation to be sent foremost greater than the packet of UL_Receive_Sn; If the count value UL_Receive_Sn in the reception packet counter that receives is not in transmit queue scope, then the packet in the transmit queue all moves into formation to be sent foremost.
Step (2) also comprises the determining step that carries out the relocation trigger condition before: user side is after receiving the physical channel reconfiguration message, judge whether base station controller identifier RNC-ID changes, if then user side is carried out the reorientation operation, otherwise user side is not carried out the reorientation operation.
The present invention also comprises: source RNC is by predefined in order to show whether the trigger fields indication user side that whether needs to carry out harmless reorientation can't harm the reorientation operation in the physical channel reconfiguration message.
Source RNC is the RRC that the count value in the reception packet counter of local terminal preservation is sent to user side by the physical channel reconfiguration message in the step (2), and the RRC of user side sends the PDCP that RELOCATION REQUEST message is sent to the count value in the reception packet counter of source RNC end local terminal by the PDCP to local terminal.Receive the RELOCATION REQUEST message of local terminal RRC transmission as PDCP after, high-rise data that send of buffer memory local terminal and no longer past RLC send data.
The middle user side of step (2) carries out the reorientation operation and also comprises: the RRC of user side need rebuild upright Signaling Radio Bearer SRB2 to the RLC of local terminal transmission configuration messages indication RLC, and disposes the physical layer of local terminal so that physical layer is carried out switching.
The present invention also comprises: behind the upright success message of reconstruction of synchronous reporting message that receives the physical layer transmission and RLC transmission, the RRC of user side reshuffles to Target RNC transmission physical channel and finishes message.After RLC receives and rebuilds upright SRB2 indication, preserve the sequence number SN that will send protocol Data Unit PDU of current SRB2.The RRC of user side finishes message to the PDCP of local terminal transmission reorientation after waiting for a Transmission Time Interval TTI.When the RRC of user side determine to Target RNC send physical channel reshuffle finish message and confirmed to receive by Target RNC after, RRC sends a starting command to PDCP, starts PDCP and restarts to send data to RLC.
Compared with prior art, the present invention has the following advantages: at first, the invention discloses a kind of no damage relocation method, realize the harmless transmission of data, satisfy business, the particularly demand of Packet Service.
Second, the trigger condition of the reorientation that the present invention resets: if RNC-ID changes, then UE will carry out the reorientation operation, avoid simple and cause that as the trigger condition of reorientation triggering inaccurate incident takes place, and has promptly improved the accuracy that triggers according in the physical channel reconfiguration message whether new-U-RNT1 being arranged.
The 3rd, the RLC of UE of the present invention need rebuild when founding SRB2, and RLC preserves the sequence number SN that current SRB2 will send protocol Data Unit PDU, so that after the reorientation failure takes place, can return smoothly and switch to source RNC.
The 4th, before finishing message, must guarantee that the RLC volume reconstruction stands successfully, so after the RLC volume reconstruction stands successfully by the time, just send this message after TTI of RRC wait just to PDCP to PDCP transmission reorientation.Thereby the data that further guaranteed PS territory (core network packet-domain) can not lost.
Description of drawings
Fig. 1 is the structural representation that the TD-SCDMA communication system of reorientation takes place;
Fig. 2 is the architecture of the air interface protocol of above-mentioned communication node employing;
Fig. 3 is the flow chart of no damage relocation method of the present invention;
Fig. 4 is count value and the sending direction schematic diagram of the PDCP of the PDCP of UE and source RNC;
Fig. 5 is harmless reorientation specific implementation flow chart.
Embodiment
Below in conjunction with accompanying drawing, specify the present invention.
See also Fig. 1, it is the structural representation of the TD-SCDMA communication system of generation reorientation.When UE changed RNC when switching, UE not only needed to carry out handover operation, and also had the distinctive operation of reorientation.That is, UE moves to another sub-district (target NodeB) and source NodeB and target NodeB not when the same RNC from a sub-district (source NodeB) in communication process, and it is UE and the communicating by letter of Target RNC that UE and communicating by letter of source RNC need reorientation.
See also Fig. 2, it is the architecture of the air interface protocol of above-mentioned communication node employing.This air interface protocol system mainly is divided into three layers, lowermost layer be physical layer (PHY) L1; Being positioned on the physical layer is data link layer L2, it comprises media access control layer (MAC) and wireless chain control layer (RLC), from user plane, it also comprises the packet data protocol convergence sublayer (PDCP) of handling Packet Service and is used to handle the broadcast/multi broadcast control sublayer (BMC) of broadcast/multi broadcast business; Being positioned on the data link layer is radio resource control layer L3, and it mainly comprises wireless network control layer (RRC).See that vertically protocol architecture is divided into the control plane and a user plane that is used to send data message of be used to transmit control signal (signaling).The agreement of control plane comprises the RRC agreement; The agreement of user plane comprises MAC, RLC, PDCP, BMC.
See also Fig. 3, it is for the flow chart of no damage relocation method of the present invention.It comprises:
S110: set in advance transmission packet counter and receive the packet counter at the PDCP of user side (UE) and source RNC, be used for adding up respectively to the RLC of local terminal sending the number of packet and the number of reception local terminal RLC packet;
S120: when reorientation takes place, count value in the reception packet counter that source RNC preserves local terminal sends to user side, and the PDCP that the count value in the reception packet counter that user side is sent according to source RNC obtains local terminal has sent which packet does not send success in the packet that does not obtain confirming;
S130: after reorientation was finished, the PDCP of user side was sent to Target RNC with the successful packet that do not send that obtains among the step S120.
Switch in the process of Target RNC at source RNC,, can not receive the data that send over from user side though the RLC of source RNC will be set to " stop " state.But by above-mentioned reorientation flow process, safeguard two count values that send the packet counter and receive the packet counter at the PDCP of user side and source RNC, each PDCP sends a packet to the RLC of local terminal, the count value that sends in the packet counter adds 1, receive a packet from the RLC of local terminal, the count value that receives in the packet counter adds 1.Under normal circumstances, can not lose because the AM pattern (affirmation mode) of RLC guarantees the data transmission, two ends independently count value can be consistent.When reorientation took place, the count value of the reception packet that the PDCP of source RNC only need preserve local terminal was passed to user side by the RRC signaling, and user side just can know and sent the packet that do not obtain confirming which really spreads out of which does not send success.User side will not send successful packet and be placed on formation to be sent, so that after the reorientation success, these packets are sent to Target RNC,
Usually, when triggering the UE end and carry out redirect operation, source RNC sends the physical channel reconfiguration message to UE, after UE finishes physical channel and reshuffles, sends physical channel to Target RNC and reshuffles and finish message.In the present invention, after physical channel is reshuffled and is finished, count value in the reception packet counter that user side is preserved local terminal sends to Target RNC, and the PDCP that the count value in the reception packet counter that Target RNC is sent according to user side obtains local terminal has sent which packet does not send success in the packet that does not obtain confirming; After the reorientation success, the PDCP of Target RNC is sent to user side with the successful packet of described transmission.By above-mentioned steps, really realize the data lossless redirect operation.
Support the function of harmless SRNS reorientation, must be configured to submit to according to the order of sequence (in-sequencedelivery), affirmation mode (acknowledged mode), SDU (Service Data Unit) not to abandon under the prerequisite of (SDUno-discard) at RLC carries out, mainly realize, guarantee by two mechanism by the PDCP layer:
1) synchronizing process sends to the opposite end with Send_SN (sending the packet count value);
2) mutual count value during reorientation is issued the opposite end with Receive_SN (receiving the packet count value);
In each PDCP entity of UE and RNC, safeguard Send_SN and Receive_SN count value, be respectively applied for the packet of each transmission and reception in this entity is counted, see shown in Figure 4, describe for clear, add that in front UL (UpLink) and DL (DownLink) prefix give differentiating uplink and downlink.Promptly, two count values of the PDCP of UE are respectively UL_Send_SN (sending the count value of packet) and DL_Receive_SN (receiving the count value of packet), and two count values of the PDCP of RNC are respectively DL_Send_SN (sending the count value of packet) and UL_Receive_SN (receiving the count value of packet).
In order to save bandwidth, count value does not need by channel mutual usually in data transmission procedure.After above behavior example, two ends were made as unanimity (when sending or receiving first packet, being made as 0 value) with initial value, UL_Send_SN and UL_Receive_SN counted respectively at two ends, did not carry out mutual.Only just can be when the SN parameter step-out of two ends with the synchronous SN value of in-band signalling mode (Send_SN is sent to the opposite end, and the opposite end is made as the Send_SN value that receives with the Receive_SN of oneself).Under the normal condition, only need to rely on the reliable transmission of rlc layer just can guarantee that UL_Send_SN is consistent with UL_Receive_SN, and DL_Send_SN is consistent with DL_Receive_SN.
Safeguard Send_SN and two count values of Receive_SN at the PDCP layer, after RLC sends a packet, Send_SN is added 1 at every turn, receive a packet from rlc layer and then Receive_SN is added 1.Under normal situation, because guaranteeing the data transmission, the affirmation pattern of RLC can not lose, two ends independently count value can be consistent.When reorientation takes place when, the PDCP layer only need be passed to the opposite end by the RRC signaling with Receive_SN separately, the opposite end just can know and sent the packet that do not obtain confirming which has really spread out of which does not send success, and will not send successful packet and put into formation to be sent.After reorientation is finished, the packet in the formation to be sent can be sent, thereby realize the data lossless reorientation.
The prerequisite of finishing harmless reorientation by mutual count value is the unanimity that guarantees the two ends count value before reorientation, guarantee by RLC, when the RLC operate as normal under the AM pattern, can guarantee that data do not have to lose to send to the opposite end, thus two ends count value unanimity.Not enough or when the RLC buffer memory owing to other reason resets or rebuilds immediately, need the RRC of notice local terminal, then by RRC notice PDCP triggering synchronous process, with the Send_SN assignment of local terminal Receive_SN to the opposite end.Below just specify harmless repositioning process with an embodiment.
See also Fig. 5, it is harmless reorientation realization flow figure.Changed RNC when UE is switching, reorientation will take place in UE so.Its process is as follows:
(1) source RNC stresses position fixing process
The RRC of source RNC sends CRLC_CONFIG_Req (re-positioning request) instruction to the RLC of source RNC earlier, and indication RLC enters " stop " state; Then, the RRC of source RNC sends CPDCP_RELOC_Req (re-positioning request) instruction to the PDCP of source RNC, and indication PDCP stops to send data to RLC, and preserves the reception packet count value DL_Send_SN of PDCP layer; Subsequently, after the PDCP of source RNC finishes the indication of CPDCP_RELOC_Req command request, send CPDCP_RELOC_Conf (relocation response) instruction to the RRC of source RNC; At last, the RRC of source RNC sends physical channel to UE and reshuffles (PHYSICAL CHANNEL RECONFIGURATION) message, and by core net forwarding SRNS context, such as, but sending of preserving of PDCP layer do not obtain packet that RLC confirms and other packet of buffer memory is transferred on the purpose RNC together.
In the physical channel reconfiguration message, determine the trigger condition of reorientation by the identifier that the RNC-ID field is set at Target RNC.And the present invention also preestablishes the trigger fields that a UE end can be discerned in the physical channel reconfiguration message, in order to indicate whether to need to carry out harmless reorientation.If the trigger fields that UE end obtains is a state of activation, then the PDCP of UE does not send successful packet and retransmits, otherwise PDCP does not send the re-transmission of successful packet.Rb-Identity such as appointment in the physical channel reconfiguration message is that RB and its attribute of before having set up the PS territory is: losslessSRNS-RelocSupport Supported, think that then trigger fields is to support the state of activation of harmless reorientation.If trigger fields for supporting the state of activation of harmless reorientation, is then being passed through this message, the reception packet count value DL_Send_SN that the PDCP of source RNC can also be preserved is sent to UE.
(2) UE end repositioning process
(1) UE end judges whether earlier to carry out whether the reorientation of reorientation and employing is that harmless reorientation UE receives the physical channel reconfiguration message.If carrying IE:new-U-RNTI (being RNC-ID) in the message just can judge RNC and want to allow UE carry out reorientation by this message.When reorientation takes place must be to have changed RNC.Whether belonging to same RNC so the RRC of UE at first resolves the RNC at srnc_Identity and the present place of UE, is same RNC if judge, and UE will not carry out the operation of reorientation so, otherwise UE just needs to carry out the reorientation operation.By this trigger condition, overcome in the prior art as long as carry DL_CounterSynchronisationInfo in the physical channel reconfiguration message or in the RB reconfiguration message, have new U-RNTI just to think that the relocation trigger condition satisfies, the incident that causes thus when the overtime inaccurate trigger re-positioning of situation such as unavailable of the RNT1 of RNC takes place, and trigger condition promptly of the present invention improves the accuracy that triggers.
After determining to carry out the reorientation operation, the UE end is resolved IE:dl-CounterSynchronisationInfo again, if the rb-Identity of appointment is that RB and its attribute of before having set up the PS territory is: losslessSRNS-RelocSupport Supported in the message, UE thinks that then trigger fields is a state of activation, begins to carry out the operation of harmless reorientation.
(2) the physical channel reconfiguration message that receives when the RRC of UE basis judges that needs can't harm when resetting operation, and RRC will carry out following operation:
(21) RRC of UE sends CRLC-CONFIG-Req (re-positioning request) instruction to the RLC of UE earlier, and indication RLC enters " stop " state, sends data no longer for source RNC; Send CPDCP-RELOC-Req (re-positioning request) instruction to the PDCP of UE then, indication PDCP begins the high-rise data that send of buffer memory and no longer sends data toward RLC, and, in this instruction, the RRC of UE is sent to the UL-Receive-SN of the PDCP preservation of the source RNC of acquisition the PDCP of UE.The PDCP of UE carries out respective handling according to the UL_Receive_SN numerical values recited to transmit queue: if UL_Receive_SN is in transmit queue scope, then the PDCP of user side will be in the transmit queue sequence of data packet number discharge smaller or equal to the packet of UL_Receive_Sn, simultaneously sequence of data packet number is moved into formation to be sent foremost greater than the packet of UL_Receive_Sn.If the UL_Receive_SN value is not in transmit queue scope, then will be packet in the transmit queue all move into formation to be sent foremost, need finish the synchronizing process that PDCP is triggered in the back at repositioning process simultaneously, promptly send the UL_Send_SN of the first packet of formation to be sent.The PDCP of UE returns the CPCP-CONFIG-Req instruction to after transmit queue carries out respective handling to the RRC of UE.
(22) RRC also carries out three kinds of configuration operations:
Operation one, RRC sends CPCP-CONFIG-Req (configuration) message to PDCP earlier, PDCP " uplink receive SN (Receive sequence number of up link) " is given in indication, be used to indicate which data of PDCP of UE side to send successfully, which data sends failure, and the DL_receive_SN effect that sends to RNC with the UE side is the same.
Operation two, RRC sends the professional RB (Radio Link) that configuration messages (CRLC-CONFIG-Req) indication RLC need rebuild upright SRB2 and stop other all SRB1, SRB2, SRB4 and all AM (affirmation), UM (non-affirmation) to RLC.Need rebuild at RLC under the situation of upright SRB2, RLC preserves the sequence number SN that current SRB2 will send protocol Data Unit PDU earlier.SN is used for the order that identification data sends, and according to the order that data send, this sequence number SN adds up successively.If physical layer switches to the Target cell failure, UE returns and cuts, and RLC does not preserve SN number, if will cause UE when waiting for the network side affirmation step-out to take place, UE will enter IDLE (free time) pattern.For head it off, if the present invention proposes RRC and rebuilds upright SRB2, the current SN that will send protocol Data Unit PDU of the temporary transient preservation of RLC, if switch unsuccessful, take place back to cut, RLC will use the SN that preserves to send the reorientation failed message to source RNC, and UE just can return the sub-district continuation communication that source RNC is administered like this.
Operation three, RRC configures physical layer allow physical layer carry out switching.
(3) when above-mentioned three operations whens success all, RRC can receive the response message that PDCP, RLC and physical layer are returned, and RRC can send physical channel to Target RNC and reshuffle and finish message.Switch to reporting synchronously of new sub-district if just receive physical layer, and do not receive that RRC rebuilds success message, even the physical channel that RRC sends is reshuffled and finished message and also can be abandoned by RLC.
RRC sends physical channel to Target RNC and reshuffles when finishing message, the count value DL_Receive_SN of the reception packet counter of the PDCP of local terminal can be sent to Target RNC by this message.Target RNC obtains the information that source RNC sends in advance, but does not obtain DL_Send_SN and the UL_Receive_SN that the PDCP of other packet, the source RNC of packet that RLC confirms and buffer memory preserves as sending of preserving of the PDCP layer of source RNC.The data processing that Target RNC transmits according to the DL_Receive_SN that obtains and the source RNC that obtains in advance is transmit queue: if DL_Receive_SN is in transmit queue scope, then discharge sequence of data packet in the transmit queue number packet, simultaneously sequence of data packet number is moved into formation to be sent foremost greater than the packet of DL_Receive_SN less than DL_Receive_SN; If the DL_Receive_SN value is not in transmit queue scope, then will be packet in the transmit queue all move into formation to be sent foremost, need finish the synchronizing process that PDCP is triggered in the back at repositioning process simultaneously, promptly send the DL_Send_SN of the first packet of formation to be sent.
(4) after UE confirms that RRC message that reorientation is finished has been acknowledged receipt of by opposite end RLC entity, RRC will rebuild this RLC entity, and be made as " continue " state; Meanwhile, RRC sends the self-defining P_RRC_PDCP_RELOC_COMP primitive of interlayer to the PDCP entity, makes it restart to send data to RLC.Because the internal memory of UE is less, PDCP can only a limited number of upper layer datas of buffer memory, so PDCP stops the time that data send and will lack in harmless repositioning process as far as possible.But the opportunity that in the agreement data that restart PDCP is sent is explanation not, so in the implementation procedure of this programme, increased the interlayer primitive of self-defining and a RRC, with the data transmission of in good time startup PDCP.
In addition, before finishing message, must guarantee that the RLC volume reconstruction stands successfully, finish message so just send reorientation after just RRC waits for a TTI after the RLC volume reconstruction stands successfully by the time to PDCP to PDCP transmission reorientation.Rebuild upright (or continue) message and finish message if send for respectively simultaneously the RLC entity to PDCP transmission reorientation, PDCP receives that this message just begins later on to send business datum to RLC immediately, if RLC does not also rebuild upright finishing now, these frame data of PDCP will be dropped.This patent proposes UE after the affirmation of receiving the harmless reorientation of network side, needs also to wait for that a TTI just sends reorientation to PDCP and finishes message.
More than disclosed only be several specific embodiment of the present invention, but the present invention is not limited thereto, any those skilled in the art can think variation all should drop in protection scope of the present invention.
Claims (12)
1, a kind of method of harmless reorientation is characterized in that, comprising:
(1) sets in advance transmission packet counter and receive the packet counter at the packet data protocol convergence sublayer PDCP of user side and source radio network controller RNC, be used for adding up respectively to the wireless chain control layer RLC of local terminal sending the number of packet and the number of reception local terminal RLC packet;
(2) when reorientation takes place, count value in the reception packet counter that source RNC preserves local terminal sends to user side, and the PDCP that the count value in the reception packet counter that user side is sent according to source RNC obtains local terminal has sent which packet does not send success in the packet that does not obtain confirming;
(3) after reorientation was finished, the PDCP of user side was sent to Target RNC with the successful packet that do not send that obtains in the step (2).
2, the method for harmless heavy position as claimed in claim 1 is characterized in that,
Step (2) also comprises: physical channel reshuffle finish after, count value in the reception packet counter that user side is preserved local terminal sends to Target RNC, and the PDCP that the count value in the reception packet counter that Target RNC is sent according to user side obtains local terminal has sent which packet does not send success in the packet that does not obtain confirming;
Step (3) also comprises: the PDCP of Target RNC is sent to user side with the successful packet of described transmission.
3, the method for harmless reorientation as claimed in claim 1 is characterized in that, the PDCP that the middle user side of step (2) obtains local terminal does not send successful packet and further is:
If the count value UL_Receive_Sn in the reception packet counter that receives is in transmit queue scope, then the PDCP of user side will be in the transmit queue sequence of data packet number discharge smaller or equal to the packet of UL_Receive_Sn, simultaneously sequence of data packet number is moved into formation to be sent foremost greater than the packet of UL_Receive_Sn;
If the count value UL_Receive_Sn in the reception packet counter that receives is not in transmit queue scope, then the packet in the transmit queue all moves into formation to be sent foremost.
4, the method for harmless reorientation as claimed in claim 1 is characterized in that, step (2) also comprises the determining step that carries out the relocation trigger condition before:
User side judges whether base station controller identifier RNC-ID changes after receiving the physical channel reconfiguration message, if then user side is carried out the reorientation operation, otherwise user side is not carried out the reorientation operation.
5, the method for harmless reorientation as claimed in claim 4, it is characterized in that, also comprise: source RNC is by predefined in order to show whether the trigger fields indication user side that whether needs to carry out harmless reorientation can't harm the reorientation operation in the physical channel reconfiguration message.
6, the method for harmless reorientation as claimed in claim 1, it is characterized in that, source RNC is the RRC that the count value in the reception packet counter of local terminal preservation is sent to user side by the physical channel reconfiguration message in the step (2), and the RRC of user side sends the PDCP that RELOCATION REQUEST message is sent to the count value in the reception packet counter of source RNC end local terminal by the PDCP to local terminal.
7, the method for harmless reorientation as claimed in claim 6 is characterized in that, after PDCP receives the RELOCATION REQUEST message that local terminal RRC sends, and high-rise data that send of buffer memory local terminal and no longer toward RLC transmission data.
8, the method for harmless reorientation as claimed in claim 1 is characterized in that, the middle user side of step (2) carries out the reorientation operation and also comprises:
The RRC of user side sends configuration messages indication RLC to the RLC of local terminal need rebuild upright Signaling Radio Bearer SRB2, and the physical layer of configuration local terminal is switched so that physical layer is carried out.
9, the method for harmless reorientation as claimed in claim 8, it is characterized in that, also comprise: behind the upright success message of reconstruction of synchronous reporting message that receives the physical layer transmission and RLC transmission, the RRC of user side reshuffles to Target RNC transmission physical channel and finishes message.
10, the method for harmless reorientation as claimed in claim 8 is characterized in that, after RLC receives and rebuilds upright SRB2 indication, preserves the sequence number SN that will send protocol Data Unit PDU of current SRB2.
11, the method for harmless reorientation as claimed in claim 8 is characterized in that, after RLC rebuild successfully, the RRC of user side finished message to the PDCP of local terminal transmission reorientation after waiting for a Transmission Time Interval TTI.
12, the method for harmless reorientation as claimed in claim 8, it is characterized in that, when the RRC of user side determine to Target RNC send physical channel reshuffle finish message and confirmed to receive by Target RNC after, RRC sends a starting command to PDCP, starts PDCP and restarts to send data to RLC.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CNB2005101149512A CN100431390C (en) | 2005-11-16 | 2005-11-16 | Lossless repositioning method |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CNB2005101149512A CN100431390C (en) | 2005-11-16 | 2005-11-16 | Lossless repositioning method |
Publications (2)
Publication Number | Publication Date |
---|---|
CN1968493A true CN1968493A (en) | 2007-05-23 |
CN100431390C CN100431390C (en) | 2008-11-05 |
Family
ID=38076970
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CNB2005101149512A Active CN100431390C (en) | 2005-11-16 | 2005-11-16 | Lossless repositioning method |
Country Status (1)
Country | Link |
---|---|
CN (1) | CN100431390C (en) |
Cited By (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2010048850A1 (en) * | 2008-10-31 | 2010-05-06 | 华为技术有限公司 | Method and apparatus for data packets transmission and reception, and processing method and system |
CN101848489A (en) * | 2009-03-25 | 2010-09-29 | 中兴通讯股份有限公司 | Sending/receiving method and device of PDU (Protocol Data Unit) |
CN101933280A (en) * | 2008-02-01 | 2010-12-29 | Lg电子株式会社 | Be used to send the mobile communication system and the method for PDCP status report |
CN102158303A (en) * | 2010-02-11 | 2011-08-17 | 中兴通讯股份有限公司 | Method and user equipment for re-establishing uplink |
CN103179614A (en) * | 2008-06-20 | 2013-06-26 | Lg电子株式会社 | Method of processing HARQ by considering measurement gap |
WO2014110786A1 (en) * | 2013-01-18 | 2014-07-24 | 华为技术有限公司 | Data transmission method and device |
CN108243468A (en) * | 2016-12-23 | 2018-07-03 | 夏普株式会社 | User mobility method and apparatus |
USRE48291E1 (en) | 2008-06-20 | 2020-10-27 | Lg Electronics Inc. | Method of delivering a PDCP data unit to an upper layer |
CN112789946A (en) * | 2018-11-22 | 2021-05-11 | 深圳市欢太科技有限公司 | Method and device for releasing RRC connection and mobile terminal |
Family Cites Families (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN1235346C (en) * | 2001-12-12 | 2006-01-04 | 华为技术有限公司 | Method for improving route repeat liability of access server |
CN1481096A (en) * | 2002-09-05 | 2004-03-10 | 深圳市中兴通迅股份有限公司上海第二 | Method for switching between CDMA2000 system and wireless local area network system |
EP1545143B1 (en) * | 2002-09-24 | 2011-06-15 | Fujitsu Limited | Packet transferring and transmitting method and mobile communication system |
DE60326401D1 (en) * | 2003-12-30 | 2009-04-09 | Ericsson Telefon Ab L M | METHOD AND SYSTEM FOR RECOVERING THE CONTEXT OF DATA PACKAGE FLOWS |
-
2005
- 2005-11-16 CN CNB2005101149512A patent/CN100431390C/en active Active
Cited By (13)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101933280A (en) * | 2008-02-01 | 2010-12-29 | Lg电子株式会社 | Be used to send the mobile communication system and the method for PDCP status report |
CN103179614B (en) * | 2008-06-20 | 2016-09-07 | Lg电子株式会社 | The method of transmitting pdcp data unit to upper layer |
CN103179614A (en) * | 2008-06-20 | 2013-06-26 | Lg电子株式会社 | Method of processing HARQ by considering measurement gap |
USRE48291E1 (en) | 2008-06-20 | 2020-10-27 | Lg Electronics Inc. | Method of delivering a PDCP data unit to an upper layer |
WO2010048850A1 (en) * | 2008-10-31 | 2010-05-06 | 华为技术有限公司 | Method and apparatus for data packets transmission and reception, and processing method and system |
CN101848489A (en) * | 2009-03-25 | 2010-09-29 | 中兴通讯股份有限公司 | Sending/receiving method and device of PDU (Protocol Data Unit) |
CN101848489B (en) * | 2009-03-25 | 2014-02-05 | 中兴通讯股份有限公司 | Sending/receiving method and device of PDU (Protocol Data Unit) |
CN102158303A (en) * | 2010-02-11 | 2011-08-17 | 中兴通讯股份有限公司 | Method and user equipment for re-establishing uplink |
WO2014110786A1 (en) * | 2013-01-18 | 2014-07-24 | 华为技术有限公司 | Data transmission method and device |
CN108243468A (en) * | 2016-12-23 | 2018-07-03 | 夏普株式会社 | User mobility method and apparatus |
CN108243468B (en) * | 2016-12-23 | 2021-09-21 | 夏普株式会社 | User mobility method and device |
US11736987B2 (en) | 2016-12-23 | 2023-08-22 | Sharp Kabushiki Kaisha | User mobility method and device |
CN112789946A (en) * | 2018-11-22 | 2021-05-11 | 深圳市欢太科技有限公司 | Method and device for releasing RRC connection and mobile terminal |
Also Published As
Publication number | Publication date |
---|---|
CN100431390C (en) | 2008-11-05 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US11582650B2 (en) | Methods and system for performing handover in a wireless communication system | |
EP2095663B1 (en) | Transfer of buffered data from a source base station to a target base station | |
CN1968493A (en) | Lossless repositioning method | |
CN1247002C (en) | Method for determining triggering time for synchronizing program of PDCP | |
EP2225902B1 (en) | Mobile communication system and method for processing handover procedure thereof | |
CN100345396C (en) | Method for performing a handoff in a mobile communication system | |
KR101037342B1 (en) | Method of handling random access procedure failure and related communication device | |
JP4965958B2 (en) | Cell / carrier switching and switchback control during RRC connection | |
KR102196939B1 (en) | Appartus and method for data synchronization in cloud cell communication system | |
JP2003522493A (en) | Operating method of mobile radio network | |
CN102257757A (en) | A method and apparatus for processing control message which requests retransmitting data | |
CN1520057A (en) | Short distance radio communication system and its switching processing method | |
CN101001446A (en) | Switching method and system | |
US20240056927A1 (en) | Device and method for preventing potential errors that may occur when performing daps handover in next-generation mobile communication system | |
CN101765169B (en) | Switching method in base station | |
CN101175319B (en) | Method for switch-over between new and old configuration of wireless network controller | |
CN102238625B (en) | Method and device for switching among carriers | |
CN101188853A (en) | A method for switching status in mobile communication system | |
WO2023231001A1 (en) | Methods and apparatus to improve ue experience during inter-du inter-cell beam management | |
CN102238657A (en) | Switch processing method, device and system | |
KR101272417B1 (en) | Data transmitting method in mobile communication system | |
CN101330762A (en) | Implementing method capable of supporting nondestructive relocation | |
WO2008052451A1 (en) | The accessing network, accessing method and the base station in mobile communication system |
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 |