CN102137435B - Method, device and system for processing data - Google Patents
Method, device and system for processing data Download PDFInfo
- Publication number
- CN102137435B CN102137435B CN201010526833.3A CN201010526833A CN102137435B CN 102137435 B CN102137435 B CN 102137435B CN 201010526833 A CN201010526833 A CN 201010526833A CN 102137435 B CN102137435 B CN 102137435B
- Authority
- CN
- China
- Prior art keywords
- hfn
- data
- update time
- current
- data receiver
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W56/00—Synchronisation arrangements
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
The embodiment of the invention discloses a method, device and system for processing data. The method comprises the following steps: acquiring update time of RX_SN and current RX_HFN; when the update time of the RX_SN exceeds a preset threshold, judging whether the current RX_HFN is synchronized with TX_HFN of a data sender; and if not, synchronizing the TX_HFN with the RX_HFN. By utilizing the method, the device and the system, an abnormal link can be discovered and recovered timely so that the TX_HFN of the data sender is resynchronized with the RX_HFN of a data receiver within a short time, thus avoiding data loss caused by failure in timely discovery of asynchronization between the TX_HFN and the RX_HFN, and being beneficial to enhancing data transmission reliability and user experience.
Description
Technical field
The present invention relates to communication technical field, be specifically related to data processing method, device and system.
Background technology
Long Term Evolution (LTE, Long Term Evolution) user plane protocol layer comprises: data convergence protocol (PDCP, Packet Data Convergence Protocol) layer, wireless link are controlled (RLC, Radio Link Control) layer, media access control (MAC, Medium Access Control) layer and physical layer (PHY, Physical Layer) layer, referring to Fig. 1 a.Wherein, the head compression of Internet protocol (IP, Internet Protocol) packet, the encryption and decryption of data, timer retransmit when abandoning, re-establishing and the operations such as processing of reordering mainly occur in PDCP layer, as follows:
The transmit leg of PDCP to the IP packet receiving be encrypted, processing such as head compression etc., and add PDCP head, to form the protocol Data Unit (PDU, Protocol Data Unit) of PDCP, then PDCP PDU is sent to recipient; Recipient receives after this PDCP PDU, from PDCP PDU head, obtains PDCP sequence number (SN, Sequence Number), deletes PDCP PDU head, and according to PDCP sequence number to data be decrypted, the processing such as decompression, then submit to upper strata.
It is closely related that the encryption and decryption of the service data unit of PDCP agreement (SDU, Service Data Unit) is processed the state variable relevant with PDCP transmit leg and recipient.Wherein, the state variable of transmit leg comprises transmitting Sequence Number (TX_SN) of next PDCP PDU and transmits Sequence Number upset counting (TX_HFN); Recipient's state variable comprises receive sequence number (RX_SN) and the receive sequence number upset counting (RX_HFN) of next PDCP PDU.The transmit leg of PDCP sends to ，You lower floor of lower floor the SDU after encrypting and submits to recipient by wireless link, so that the recipient of PDCP upgrades RX_SN and RX_HFN.
Due at non-confirmation (UM, Unacknowledged Mode) under pattern, there is not the HARQ (ARQ under affirmation mode, Automatic Repeat reQuest) handling process, if so there is loss of data in bottom, RLC just cannot obtain in time the information of loss of data and carry out retransmission process, so, if the SDU that PDCP transmit leg sends is because some reason cannot arrive PDCP recipient, PDCP receives conveniently cannot upgrade RX_HFN, causes the TX_HFN of data receiver and data receiver's RX_HFN to upgrade asynchronous.
In the research and practice process to prior art, inventor finds, it is asynchronous that TX_HFN and RX_HFN upgrade, the further loss that will cause data deciphering mistake and data, in this case, only have by the time user to find data exception, or Application inspection to receive data exception time, just likely carry out recovery and the reconstruction of link.But, due in data, be lost to user or application program find data exception carry out the recovery of link and rebuild between need the regular hour, so will lose mass data during this period, greatly reduce reliability and the user that number passes and experience.
Summary of the invention
The embodiment of the present invention provides a kind of data processing method, device and system, can find in time that link is abnormal, improves number and passes reliability.
, comprising:
Data receiver obtains update time and the current RX_HFN of RX_SN;
Whether exceed preset threshold value the update time that judges described RX_SN;
If exceed preset threshold value the update time of described RX_SN, judge whether described current RX_HFN synchronizes with the TX_HFN of data receiver;
If asynchronous, synchronous described TX_HFN and RX_HFN.
, comprising:
Acquiring unit, for obtaining update time and the current RX_HFN of RX_SN;
Judging unit, for judging whether exceed preset threshold value the update time of the RX_SN that acquiring unit gets;
Authentication unit, when determining that at judging unit exceed preset threshold value the update time of described RX_SN, judges whether described current RX_HFN synchronizes with the TX_HFN of data transmitting equipment;
Lock unit, when determining that at authentication unit the TX_HFN of current RX_HFN and data transmitting equipment is asynchronous, synchronous described TX_HFN and RX_HFN.
, comprise data transmitting equipment and above-mentioned data receiver; Wherein, this data transmitting equipment, for sending data to this data receiver.
The technical scheme of the embodiment of the present invention, the update time of RX_SN and current RX_HFN are obtained in employing, when exceed preset threshold value the update time of RX_SN, judge whether current RX_HFN synchronizes with the TX_HFN of data receiver, determining when asynchronous, synchronously this TX_HFN and RX_HFN.Adopt this scheme, can find in time that link is abnormal and in time link be recovered, the TX_HFN of data receiver and data receiver's RX_HFN can be re-started synchronously at short notice, the generation of the event of data loss causing while avoiding failing to find in time because TX_HFN is asynchronous with RX_HFN, is conducive to improve number and passes reliability and user's experience.
Accompanying drawing explanation
In order to be illustrated more clearly in the technical scheme in the embodiment of the present invention, below the accompanying drawing of required use during embodiment is described is briefly described, apparently, accompanying drawing in the following describes is only some embodiments of the present invention, for those of ordinary skills, do not paying under the prerequisite of creative work, can also obtain according to these accompanying drawings other accompanying drawing.
Fig. 1 a is the schematic diagram of user plane protocol layer in LTE system;
Fig. 1 b is the flow chart of the data processing method that provides of the embodiment of the present invention;
Fig. 2 a is the flow chart of the data processing method that provides of the embodiment of the present invention;
Fig. 2 b is the structural representation of a kind of PDCP PDU;
Fig. 3 a is the structural representation of the data receiver that provides of the embodiment of the present invention;
Fig. 3 b is another structural representation of the data receiver that provides of the embodiment of the present invention;
Fig. 4 is the structural representation of the data handling system that provides of the embodiment of the present invention.
Embodiment
Below in conjunction with the accompanying drawing in the embodiment of the present invention, the technical scheme in the embodiment of the present invention is clearly and completely described, obviously, described embodiment is only the present invention's part embodiment, rather than whole embodiment.Embodiment based in the present invention, those of ordinary skills, not making the every other embodiment obtaining under creative work prerequisite, belong to the scope of protection of the invention.
The embodiment of the present invention provides a kind of data processing method, device and system.Below be elaborated respectively.In a plurality of embodiment provided by the invention, the Unacknowledged Mode of mainly take describes as example.
Embodiment mono-,
The present embodiment is described the angle from data receiver, and this data receiver is as data receiver.It can be specifically the data receiver (can be understood as PDCP layer itself) of the PDCP layer in long evolving system; In addition, the data receiver in the embodiment of the present invention can be specifically the data transmitting equipment of the PDCP layer in long evolving system, and between this data receiver and data receiver, adopts Unacknowledged Mode to carry out data input and data output.For convenience, hereinafter referred to as the data receiver of PDCP layer, be PDCP receiving equipment, the data transmitting equipment of PDCP layer is PDCP transmitting apparatus.
The method comprises: data receiver obtains update time and the current RX_HFN of RX_SN; Whether exceed preset threshold value the update time that judges RX_SN; If exceed preset threshold value the update time of this RX_SN, judge whether current RX_HFN synchronizes with the TX_HFN of data receiver; If asynchronous, synchronous TX_HFN and RX_HFN.
Referring to Fig. 1 b, idiographic flow can be as follows:
101, data receiver obtains update time and the current RX_HFN of RX_SN;
Such as, can obtain the renewal duration T_HFN that puts T_SN2, last RX_HFN the update time of putting T_SN1, this RX_SN update time and the current RX_HFN of last RX_SN.
Wherein, the update time of RX_SN is for putting update time of putting T_SN2 and last RX_SN update time of this RX_SN the poor of T_SN1.
Whether exceed preset threshold value the update time of the RX_SN 102, getting in determining step 101, if so, performs step 103, and if not, flow process finishes.
For example, if obtained the renewal duration T_HFN that puts T_SN2, last RX_HFN the update time of putting T_SN1, this RX_SN update time and the current RX_HFN of last RX_SN in step 101, can judge the update time point of this RX_SN and the update time of last RX_SN point difference, whether be greater than the first preset fixed value, or whether this difference is greater than the preset proportion value of the renewal duration of last RX_HFN.If put the difference of putting with the update time of last RX_SN the update time of this RX_SN, be greater than the first preset fixed value, or, if this difference is greater than the preset proportion value of the renewal duration of last RX_HFN, exceed preset threshold value the update time of definite RX_SN, otherwise, if this difference is not more than preset proportion value or first fixed value of the renewal duration of RX_HFN, do not exceed preset threshold value the update time of definite RX_SN.
Wherein, the first fixed value and preset proportion value can be set and adjust according to the demand of practical application.
In addition, in the statement of the embodiment of the present invention related " flow process finishes ", can be understood as and finish this flow process, and enter next similarly handling process.
103,, when exceed preset threshold value the update time of RX_SN, judge whether current RX_HFN synchronizes with the TX_HFN of data receiver, and if so, flow process finishes, and if not, performs step 104;
Because RX_HFN is a part of the key parameter PDCP counting (COUNT) of SDU encryption and decryption processing, if the current RX_HFN of data receiver makes mistakes, such as the TX_HFN of the current RX_HFN of data receiver and data receiver is asynchronous, the data that decrypt (hereinafter referred to as data decryption) also can be made mistakes, if data decryption is correct, show that current RX_HFN synchronizes with the TX_HFN of data receiver; So, can judge whether current RX_HFN synchronizes with the TX_HFN of data receiver by the correctness of checking data decryption.
Specific implementation can be as follows: the data that this is received are decrypted, and obtain data decryption; Correctness to this data decryption is verified, if be proved to be successful, shows that current link is normal, represents that TX_HFN and the current RX_HFN of data receiver of data receiver is synchronous, so flow process finishes; Otherwise, if authentication failed determines that the TX_HFN of (or being called judgement) current RX_HFN and data receiver is asynchronous, need to perform step 104.Wherein, the data here can be SDU data.
104, the TX_HFN of synchrodata transmit leg and data receiver's RX_HFN;
Specifically can adopt following any one method:
(1) reporting links is abnormal, triggers application program or radio resource control (RRC, Radio Resource Control) equipment TX_HFN and RX_HFN are carried out synchronously, process ends after completing; Or,
(2) first current RX_HFN is upgraded, such as current RX_HFN is added to 1, then return and carry out deciphering and verification step, the data that according to the RX_HFN after upgrading, this received are deciphered again, again the data decryption after being deciphered, then the correctness of the data decryption after the new deciphering of counterweight is verified.If still fail to be proved to be successful in preset checking number of times, reporting links is abnormal, triggers application program or RRC equipment the TX_HFN of data receiver and data receiver's RX_HFN is re-started synchronously, process ends after completing.
Wherein, application program or RRC equipment re-start synchronous correlation technique to the TX_HFN of data receiver and data receiver's RX_HFN and can, referring to prior art, not repeat them here.Wherein, RRC equipment can be understood as rrc layer (this rrc layer is the upper strata of PDCP layer), such as, data receiver's rrc layer, this rrc layer can be realized the TX_HFN of data receiver and data receiver's RX_HFN is re-started synchronously.In addition, application program can be the application program in computer, this application program can re-start synchronously the TX_HFN of data receiver and data receiver's RX_HFN, or, this application program can be by link being recovered and rebuilding, so that the TX_HFN of data receiver and data receiver's RX_HFN is re-started synchronously.
It should be noted that, this preset checking number of times can arrange according to the actual treatment ability of each equipment in network, for example, if the actual treatment ability of each equipment is stronger in network, checking number of times suitably can be increased, by data receiver, voluntarily RX_HFN be upgraded, thereby under the prerequisite of RX_HFN that guarantees to upgrade in time, omit reporting links mistake and repair the flow processs such as link, reaching the object of saving Radio Resource; And if the actual treatment ability of each equipment is general in network, checking number of times suitably can be reduced, to guarantee the RX_HFN that can upgrade in time, guarantee that TX_HFN and RX_HFN's is synchronous.
For example, general, can verify that number of times is set to 2 times, if secondary authentication failed can be used RLC link extremely to report mechanism report RX_HFN to upgrade abnormal.Specifically can be as follows:
After current RX_HFN is upgraded, the data that data receiver receives this according to the RX_HFN after upgrading are deciphered again, and the correctness of the data after the new deciphering of counterweight is carried out secondary checking (referring to step 104), if secondary authentication failed, data receiver no longer upgrades voluntarily to RX_HFN, but it is abnormal to use existing RLC link extremely to report mechanism report RX_HFN to upgrade, and triggers application program or RRC equipment TX_HFN and RX_HFN are re-started synchronously.
Certainly, if be proved to be successful, show that RX_HFN is updated successfully in preset checking number of times, represent that data receiver and the current state variable of data receiver are synchronous, flow process can finish.
As from the foregoing, the present embodiment adopts and obtains the update time of RX_SN and current RX_HFN, when exceed preset threshold value the update time of RX_SN, judges whether current RX_HFN synchronizes with the TX_HFN of data receiver, determining when asynchronous, synchronously this TX_HFN and RX_HFN.Adopt this scheme, can be under Unacknowledged Mode, find that in time link is abnormal and in time link recovered, the TX_HFN of data receiver and data receiver's RX_HFN can be re-started synchronously at short notice, the generation of the event of data loss causing while avoiding failing to find in time because TX_HFN is asynchronous with RX_HF, is conducive to improve number and passes reliability and user's experience.
Embodiment bis-,
According to the described method of embodiment mono-, below will be described in further detail for example.
In the present embodiment, correctness with by checking data decryption is judged to whether current RX_HFN synchronizes with the TX_HFN of data receiver, and checking number of times is to describe for example for twice, wherein, data are specially SDU data, data receiver is specially PDCP receiving equipment (being the data receiver of PDCP layer), and this PDCP receiving equipment has configured the decryption processing of non-NULL algorithm.Referring to Fig. 2 a, idiographic flow can be as follows:
201, PDCP receiving equipment receives SDU data, and puts T_SN2 the update time of putting T_SN1 and this RX_SN update time of recording last RX_SN, and the renewal duration T_HFN and the current RX_HFN that record last RX_HFN.
202, the SDU data that the deciphering parameter that PDCP receiving equipment provides according to PDCP receives this are decrypted, and obtain data decryption;
Wherein, deciphering parameter can comprise the parameters such as key, COUNT value, bearing identification and data transfer direction, and RX_HFN is part of COUNT value.Concrete decryption method can, referring to prior art, not repeat them here.
203, PDCP receiving equipment judges and puts the difference of putting T_SN1 update time of T_SN2 and last RX_S N the update time of this RX_SN, whether is greater than the preset proportion value of the renewal duration of last RX_HFN, if so, performs step 204; If not, according to flow process of the prior art, continue subsequent operation.
Such as, this ratio value can be set as 1/8th, and PDCP receiving equipment can judge whether " T_SN2-T_SN1 > T_HFN/8 " sets up.
At this, using " T_HFN/8 " as preset threshold value, reason is as follows:
As shown in Figure 2 b, this figure is under Unacknowledged Mode, the structural representation of a kind of PDCP PDU.From Fig. 2 b, can find out, the bit of PDCP SN (bit) length is 7 bits, if because timer expiry abandons and in lower-layer protocols because the PDCP PDU quantity that abandons continuously of other reasons surpassed this PDU type in the SN maximum that can represent: 128, just there will be the state variable TX_SN of PDCP transmitting apparatus and the state variable RX_SN of PDCP receiving equipment to upgrade nonsynchronous situation.
Such as, before there is packet loss, the value of the state variable RX_SN of PDCP receiving equipment is 37, the value of RX_HFN is 111, in several biography processes, the data packet number that lower-layer protocols is lost has reached 129, now PDCP transmitting apparatus state variable TX_SN be updated to next TX_HFN(now TX_HFN value be 112) corresponding TX_SN(now the value of TX_SN be 38), but the state variable RX_SN of PDCP receiving equipment still rests on a corresponding RX_SN value of RX_HFN: 37.When PDCP receiving equipment receives follow-up data, because described RX_HFN update condition is discussed by discontented football association, so PDCP receiving equipment does not upgrade RX_HFN, the encryption parameter that causes PDCP receiving equipment to use when the deciphering parameter of the SDU data that calculate and PDCP transmitting apparatus are encrypted these data is inconsistent, thus the error in data that PDCP receiving equipment is decrypted.
So, at this, using " T_HFN/8 " as preset threshold value, object is whether the data packet number of losing for checking has surpassed the maximum that SN can represent, if surpassed, show deciphering after SDU data may make mistakes, so follow-up, it is done to further checking (referring to step 204) to state variable is re-started synchronously.
It should be noted that, only provided the structural representation of a kind of PDCP PDU in Fig. 2 b, should be understood that, the method is equally applicable to the PDCP PDU of other structures, and above-mentioned " preset threshold value " also needs correspondingly to adjust according to practical application.
Wherein, step 202 and 203 execution are in no particular order.
204, PDCP receiving equipment is verified the correctness of the data decryption obtaining in step 202, if be proved to be successful, flow process finishes; If authentication failed, performs step 205.
It should be noted that, optional, when being verified, can also to this data decryption, whether be further corresponding data decryption after RX_HFN upgrades, if so, show that RX_HFN is updated successfully, can point out user RX_HFN to be updated successfully, flow process finishes; If not, flow process directly finishes.
205, PDCP receiving equipment upgrades current RX_HFN, such as RX_HFN is added to 1, then performs step 206.
206, the SDU data that PDCP receiving equipment receives this according to the RX_HFN after upgrading are deciphered again, then perform step 207;
It should be noted that, what process that (being encryption and decryption processing) used due to the current Access Layer encryption and decryption of LTE system is symmetric key system, so, the SDU data that receive for PDCP receiving equipment, if use identical parameter to be decrypted these SDU data, and the SDU data after deciphering are encrypted again, can obtain and the identical data of SDU data that receive.That is to say, although the SDU data that this received in step 202 are deciphered, but, if after checking, find the SDU error in data after deciphering, the SDU data after this deciphering can be re-started to encryption again, the SDU data before being deciphered so that PDCP receiving equipment according to the RX_HFN after upgrading the SDU data before to this deciphering again decipher.
207, the correctness of the SDU data after the new deciphering of PDCP receiving equipment counterweight is verified, if be proved to be successful, show that RX_HFN is updated successfully, the renewal of the RX_HFN of the TX_HFN of current PDCP transmitting apparatus and PDCP receiving equipment is synchronous, so flow process can finish; If authentication failed, performs step 208.
208, PDCP receiving equipment uses existing RLC link extremely to report machine-processed reporting links abnormal, triggers application program or RRC equipment the state variable of the RX_HFN of the TX_HFN of PDCP transmitting apparatus and PDCP receiving equipment is re-started synchronously, and flow process finishes.
Wherein, RRC equipment can be understood as rrc layer, such as, data receiver's rrc layer, this rrc layer can be realized the RX_HFN of the TX_HFN of PDCP transmitting apparatus and PDCP receiving equipment is re-started synchronously.In addition, application program can be the application program in computer, this application program can re-start synchronously the RX_HFN of the TX_HFN of PDCP transmitting apparatus and PDCP receiving equipment, or, this application program can be by link being recovered and rebuilding, so that the RX_HFN of the TX_HFN of PDCP transmitting apparatus and PDCP receiving equipment is re-started synchronously.Wherein, application program or RRC equipment re-start synchronous correlation technique to the RX_HFN of the TX_HFN of PDCP transmitting apparatus and PDCP receiving equipment and can, referring to prior art, not repeat them here.
It should be noted that, if in certain RX_HFN renewal process once, longer situation update time does not occur between two RX_SN, current RX_HFN can be upgraded to duration T_HFN as the basis of follow-up judgement.When number biography (abbreviation of transfer of data) just starts, the several continuous SN starting most can be upgraded to duration mean value and be multiplied by the SN space of PDCP as the initial estimate of this RX_HFN renewal.
As from the foregoing, the present embodiment adopts and to put T_SN2 the update time of putting T_SN1 and this RX_SN update time record last RX_SN, and record the renewal duration T_HFN of last RX_HFN and current RX_HFN, then the SDU data that according to current RX_HFN, this received are decrypted, and at T_SN2-T_SN1 > during T_HFN/8, correctness to the SDU data after deciphering is verified, with this, determine whether current RX_HFN is updated successfully, thus determine PDCP transmit leg and the current state variable of PDCP recipient whether synchronous.
Adopt this scheme, can be under Unacknowledged Mode, find that in time link is abnormal and in time link recovered, the TX_HFN of PDCP transmitting apparatus and the RX_HFN of PDCP receiving equipment can be re-started synchronously at short notice, the generation of the event of data loss causing while avoiding failing to find in time because TX_HFN is asynchronous with RX_HFN, be conducive to improve number and pass reliability, on the other hand, owing to having improved the reliability of several biographies, so can avoid occurring that number passes the situation that extremely causes the waste of a large amount of air-link resources, being conducive to improve user experiences.
Further, owing to can data correctness being verified, so can also effectively detect the invalid data that the invader that eats dishes without rice or wine provides, the number that promotes user's face passes fail safe.
Embodiment tri-,
In order to implement better above method, the embodiment of the present invention also correspondingly provides a kind of data receiver, and as data receiver, referring to Fig. 3 a, this data receiver comprises acquiring unit 301, judging unit 302, authentication unit 303, lock unit 304;
Acquiring unit 301, for obtaining update time and the current RX_HFN of RX_SN;
Judging unit 302, for judging whether exceed preset threshold value the update time of the RX_SN that acquiring unit 301 gets;
Because RX_HFN is a part of the key parameter PDCP COUNT of SDU encryption and decryption processing, if the current RX_HFN of data receiver makes mistakes, such as the TX_HFN of the current RX_HFN of data receiver and data receiver is asynchronous, data decryption also can be made mistakes, if data decryption is correct, show that current RX_HFN synchronizes with the TX_HFN of data receiver.
So, can judge whether current RX_HFN synchronizes with the TX_HFN of data receiver by the correctness of checking data decryption.Referring to Fig. 3 b, this data receiver can also comprise decrypting device 305.
Wherein, referring to Fig. 3 b, lock unit 304 can comprise renewal subelement 3041 and report subelement 3042;
The SDU data that can be received this according to the RX_HFN upgrading after subelement 3041 upgrades by decrypting device 305 are deciphered again, then by the correctness of the SDU data after the new deciphering of authentication unit 303 counterweights, are verified;
A kind of implementation is as follows:
For example, upgrade subelement 3041, specifically for current RX_HFN is added to 1, then return and carry out deciphering and verification step.
For example, if preset checking number of times is 2 times, report subelement 3042, specifically for when the secondary authentication failed, use RLC link extremely to report mechanism report RX_HFN to upgrade abnormal.
Wherein, RRC equipment can be understood as rrc layer, such as, data receiver's rrc layer, this rrc layer can be realized the RX_HFN of the TX_HFN of data transmitting equipment and data receiver is re-started synchronously.In addition, application program can be the application program in computer, this application program can re-start synchronously the RX_HFN of the TX_HFN of data transmitting equipment and data receiver, or, this application program can be by link being recovered and rebuilding, so that the RX_HFN of the TX_HFN of data transmitting equipment and data receiver is re-started synchronously.Wherein, application program or RRC equipment re-start synchronous correlation technique to the RX_HFN of the TX_HFN of data transmitting equipment and data receiver and can, referring to prior art, not repeat them here.
Referring to Fig. 3 b, wherein, judging unit 302 can comprise comparison subelement 3021 and judgment sub-unit 3022;
Acquiring unit 301, specifically for obtaining renewal duration and the current RX_HFN of some update time of last RX_SN, some update time of this RX_SN, last RX_HFN;
Compare subelement 3021, for the difference of putting T_SN1 the update time of putting T_SN2 and last RX_SN update time of this RX_SN that acquiring unit 301 is got, compare with the preset proportion value of the renewal duration of last RX_HFN or the first preset fixed value; Wherein, this preset proportion value specifically can be made as 1/8th;
In such cases, authentication unit 303, for when judgment sub-unit 3022 determines that exceed preset threshold value the update time of RX_SN, the correctness of the data decryption that decrypting device 305 is obtained is verified.
If relatively subelement 3031 determine these RX_SN update time point with last RX_SN update time point poor, be not more than the first preset fixed value, or be not more than the preset proportion value of the renewal duration of last RX_HFN, such as 1/8th, when T_SN2-T_SN1≤T_HFN/8, according to flow process of the prior art, continue subsequent operation.
The concrete enforcement of above unit can, referring to embodiment above, not repeat them here.
As from the foregoing, the acquiring unit 301 of the data receiver that the present embodiment provides can adopt and obtain the update time of RX_SN and current RX_HFN, then when judging unit 302 determines that exceed preset threshold value the update time of RX_SN, by authentication unit 303, judge whether current RX_HFN synchronizes with the TX_HFN of data receiver, determining when asynchronous, by synchronous this TX_HFN of lock unit 304 and RX_HFN.Adopt this scheme, can be under Unacknowledged Mode, find that in time link is abnormal and in time link recovered, the RX_HFN of data transmitting equipment TX_HFN and data receiver can be re-started synchronously at short notice, the generation of the event of data loss causing while avoiding failing to find in time because TX_HFN is asynchronous with RX_HF, be conducive to improve number and pass reliability, on the other hand, owing to having improved the reliability of several biographies, so can avoid occurring that number passes the situation that extremely causes the waste of a large amount of air-link resources, be conducive to improve user and experience.
Further, owing to can data correctness being verified, so can also effectively detect the invalid data that the invader that eats dishes without rice or wine provides, the number that promotes user's face passes fail safe.
Embodiment tetra-,
Accordingly, the embodiment of the present invention also provides a kind of data handling system, referring to Fig. 4, comprises any data receiver 300 that data transmitting equipment 400 and the above embodiment of the present invention provide;
Whether data receiver 300, for obtaining update time and the current RX_HFN of RX_SN, exceed preset threshold value the update time that judges RX_SN; If exceed preset threshold value the update time of this RX_SN, judge whether current RX_HFN synchronizes with the TX_HFN of data transmitting equipment 400; If asynchronous, synchronous TX_HFN and RX_HFN.
Such as, data receiver 300 can obtain the renewal duration T_HFN that puts T_SN2, last RX_HFN the update time of putting T_SN1, this RX_SN update time and the current RX_HFN of last RX_SN; The update time of RX_SN is for putting update time of putting T_SN2 and last RX_SN update time of this RX_SN the poor of T_SN1.If put the difference of putting with the update time of last RX_SN the update time of this RX_SN, be greater than the first preset fixed value, or, if this difference is greater than the preset proportion value of the renewal duration of last RX_HFN, exceed preset threshold value the update time of definite RX_SN, otherwise, if this difference is not more than preset proportion value or first fixed value of the renewal duration of RX_HFN, do not exceed preset threshold value the update time of definite RX_SN.
Further, can judge whether current RX_HFN synchronizes with the TX_HFN of data transmitting equipment 400 by the correctness of checking data decryption; That is:
Now, data transmitting equipment 400, for sending SDU data to data receiver 300.
Wherein, data receiver 300 can be specifically the data receiver of the PDCP layer in long evolving system; In addition, data transmitting equipment 400 can be specifically the data transmitting equipment of the PDCP layer in long evolving system, and adopts Unacknowledged Mode to carry out data input and data output between this data receiver 300 and data transmitting equipment 400.
The concrete enforcement of above unit can, referring to embodiment above, not repeat them here.
To for example the execution flow process of this data handling system be made to schematic illustration below, as follows:
Step 0, data transmitting equipment 400 send SDU data to data receiver 300.
The SDU data that the deciphering parameter that step 2, data receiver 300 provide according to PDCP receives this are decrypted, and obtain data decryption;
Wherein, deciphering parameter can comprise the parameters such as key, COUNT value, bearing identification and data transfer direction, and RX_HFN is part of COUNT value.
Such as, this ratio value can be set as 1/8th, and PDCP receiving equipment can judge whether " T_SN2-T_SN1 > T_HFN/8 " sets up.
Wherein, the execution of step 2 and step 3 in no particular order.
The correctness of the data decryption obtaining in step 4,300 pairs of steps 2 of data receiver verifies, if be proved to be successful, flow process finishes; If authentication failed, performs step 5.
It should be noted that, optional, when being verified, can also to this data decryption, whether be further corresponding data decryption after RX_HFN upgrades, if so, show that RX_HFN is updated successfully, can point out user RX_HFN to be updated successfully, flow process finishes; If not, flow process directly finishes.
The SDU data that step 6, data receiver 300 receive this according to the RX_HFN after upgrading are deciphered again, then perform step 7.
The correctness of the SDU data after step 7, the new deciphering of data receiver counterweight is verified, if be proved to be successful, show that RX_HFN is updated successfully, the renewal of the RX_HFN of the TX_HFN of current data transmitting apparatus 400 and data receiver 300 is synchronous, so flow process can finish; If authentication failed, performs step 8.
To sum up, the data receiver 300 of the data handling system that the present embodiment provides can adopt and obtain the update time of RX_SN and current RX_HFN, then the SDU data that according to current RX_HFN, this received are decrypted, and when exceed preset threshold value the update time of RX_SN, correctness to the SDU data after deciphering is verified, with this, determine whether current RX_HFN is updated successfully, thereby whether the current state variable of specified data transmitting apparatus 400 and data receiver 300 is synchronous.Adopt this scheme, can be under Unacknowledged Mode, find that in time link is abnormal and in time link recovered, the state variable of data transmitting equipment 400 and data receiver 300 can be re-started synchronously at short notice, the generation of the event of data loss causing while avoiding failing to find in time because TX_HFN is asynchronous with RX_HF, be conducive to improve number and pass reliability, on the other hand, owing to having improved the reliability of several biographies, so can avoid occurring that number passes the situation that extremely causes the waste of a large amount of air-link resources, being conducive to improve user experiences.
Further, owing to can data correctness being verified, so can also effectively detect the invalid data that the invader that eats dishes without rice or wine provides, the number that promotes user's face passes fail safe.
One of ordinary skill in the art will appreciate that all or part of step in the whole bag of tricks of above-described embodiment is to come the hardware that instruction is relevant to complete by program, this program can be stored in a computer-readable recording medium, storage medium can comprise: read-only memory (ROM, Read Only Memory), random access memory (RAM, Random Access Memory), disk or CD etc.
The data processing method above embodiment of the present invention being provided, device and system are described in detail, applied specific case herein principle of the present invention and execution mode are set forth, the explanation of above embodiment is just for helping to understand method of the present invention and core concept thereof; , for one of ordinary skill in the art, according to thought of the present invention, all will change in specific embodiments and applications, in sum, this description should not be construed as limitation of the present invention meanwhile.
Claims (10)
1. a data processing method, is characterized in that, comprising:
Data receiver obtains update time and the current receive sequence number upset counting RX_HFN of receive sequence number;
Whether exceed preset threshold value the update time that judges described receive sequence number;
If exceed preset threshold value the update time of described receive sequence number, judge whether described current RX_HFN synchronizes with the upset counting TX_HFN that transmits Sequence Number of data receiver;
If asynchronous, synchronous described TX_HFN and RX_HFN;
Wherein, the update time and the current RX_HFN that described in, obtain receive sequence number comprise: the renewal duration and the current RX_HFN that obtain some update time of last receive sequence number, some update time of this receive sequence number, last RX_HFN;
Exceed preset threshold value and comprise the update time of described receive sequence number: if put the difference of putting with the update time of last receive sequence number the update time of this receive sequence number, be greater than the first preset fixed value, or, if described difference is greater than the preset proportion value of the renewal duration of last RX_HFN, exceed preset threshold value the update time of definite receive sequence number.
2. method according to claim 1, is characterized in that, described judge whether current RX_HFN synchronizes with the TX_HFN of data receiver before, also comprise:
The data that this is received are decrypted, and obtain data decryption;
, describedly judge whether current RX_HFN is synchronizeed and comprised with the TX_HFN of data receiver: the correctness to described data decryption is verified, if authentication failed determines that the TX_HFN of current RX_HFN and data receiver is asynchronous.
3. method according to claim 2, is characterized in that, when authentication failed, synchronous TX_HFN and RX_HFN comprise:
Reporting links is abnormal, triggers application program or radio resource control RRC equipment TX_HFN and RX_HFN are carried out synchronously; Or,
When authentication failed, current RX_HFN is upgraded, and return and carry out described deciphering and described verification step; If still fail to be proved to be successful in preset checking number of times, reporting links is abnormal, triggers application program or RRC equipment TX_HFN and RX_HFN are carried out synchronously.
4. method according to claim 3, is characterized in that, described current RX_HFN is upgraded and comprised:
Current RX_HFN is added to 1.
5. according to the method described in claim 1 to 4 any one, it is characterized in that,
Described data receiver is the data receiver of the data convergence protocol PDCP layer in long evolving system, described data receiver is the data transmitting equipment of the PDCP layer in long evolving system, and adopts Unacknowledged Mode to carry out data input and data output between described data receiver and described data receiver.
6. a data receiver, is characterized in that, comprising:
Acquiring unit, for obtaining update time and the current receive sequence number upset counting RX_HFN of receive sequence number;
Judging unit, for judging whether exceed preset threshold value the update time of the receive sequence number that acquiring unit gets;
Authentication unit, when determining that at judging unit exceed preset threshold value the update time of described receive sequence number, judges whether the upset counting TX_HFN that transmits Sequence Number of described current RX_HFN and data transmitting equipment synchronizes;
Lock unit, when determining that at authentication unit the TX_HFN of current RX_HFN and data transmitting equipment is asynchronous, synchronous described TX_HFN and RX_HFN;
Wherein, described judging unit comprises comparison subelement and judgment sub-unit;
Described acquiring unit, specifically for obtaining renewal duration and the current RX_HFN of some update time of last receive sequence number, some update time of this receive sequence number, last RX_HFN;
Described relatively subelement, for the difference of putting T_SN1 the update time of putting T_SN2 and last RX_SN update time of this RX_SN that acquiring unit is got, compare with the preset proportion value of the renewal duration of last RX_HFN or the first preset fixed value;
Judgment sub-unit, for at subelement relatively, determine this RX_SN update time point with on once RX_SN update time point poor, be greater than the first preset fixed value, or, while being greater than the preset proportion value of renewal duration of last RX_HFN, exceed preset threshold value the update time of determining receive sequence number.
7. data receiver according to claim 6, is characterized in that, also comprises decrypting device, for the data that this is received, is decrypted, and obtains data decryption;
, described authentication unit, verifies specifically for the correctness of data decryption that decrypting device is obtained, if authentication failed determines that the TX_HFN of current RX_HFN and data transmitting equipment is asynchronous.
8. data receiver according to claim 7, is characterized in that,
Described lock unit, when determining that at authentication unit the TX_HFN of current RX_HFN and data transmitting equipment is asynchronous, reporting links is abnormal, triggers application program or radio resource control RRC equipment TX_HFN and RX_HFN are carried out synchronously.
9. data receiver according to claim 7, is characterized in that, described lock unit comprises renewal subelement and reports subelement;
Upgrade subelement, for when the authentication unit authentication failed, current RX_HFN is upgraded, and trigger that described decrypting device is carried out deciphering again and described authentication unit is carried out checking again;
Report subelement, if still fail to be proved to be successful for authentication unit in the checking number of times preset, reporting links is abnormal, triggers application program or RRC equipment TX_HFN and RX_HFN are carried out synchronously.
10. a data handling system, is characterized in that, comprises any data receiver described in data transmitting equipment and claim 6 to 9;
Described data transmitting equipment, for sending data to described data receiver.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201010526833.3A CN102137435B (en) | 2010-10-21 | 2010-10-21 | Method, device and system for processing data |
| PCT/CN2011/080992 WO2012051946A1 (en) | 2010-10-21 | 2011-10-19 | Data processing method, apparatus and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201010526833.3A CN102137435B (en) | 2010-10-21 | 2010-10-21 | Method, device and system for processing data |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN102137435A CN102137435A (en) | 2011-07-27 |
| CN102137435B true CN102137435B (en) | 2014-01-22 |
Family
ID=44297070
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201010526833.3A Active CN102137435B (en) | 2010-10-21 | 2010-10-21 | Method, device and system for processing data |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN102137435B (en) |
| WO (1) | WO2012051946A1 (en) |
Families Citing this family (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102137435B (en) * | 2010-10-21 | 2014-01-22 | 上海华为技术有限公司 | Method, device and system for processing data |
| CN104079371B (en) * | 2013-03-27 | 2018-05-08 | 成都鼎桥通信技术有限公司 | A kind of data communications method, equipment and system |
| CN104168640A (en) * | 2013-05-17 | 2014-11-26 | 中兴通讯股份有限公司 | Reception end PDCP layer HFN out-off-step recovering method and device |
| CN103607261B (en) * | 2013-11-22 | 2017-06-23 | 大唐移动通信设备有限公司 | A kind of data transmission method and device |
| US10028311B2 (en) * | 2014-04-22 | 2018-07-17 | Lg Electronics Inc. | Method for processing received PDCP PDUs for D2D communication system and device therefor |
| KR102202894B1 (en) * | 2014-08-28 | 2021-01-14 | 삼성전자 주식회사 | Apparatus and method for handling packet loss in a mobile communication system |
| CN108347308A (en) * | 2017-01-22 | 2018-07-31 | 成都鼎桥通信技术有限公司 | The method of reseptance and device of point multipoint message traffic |
| CN109150353B (en) * | 2018-07-25 | 2020-01-14 | 安徽江淮汽车集团股份有限公司 | Timing method and system for vehicle-mounted TBOX of electric vehicle |
| CN113225748A (en) * | 2020-01-17 | 2021-08-06 | 普天信息技术有限公司 | Hyper frame number out-of-step detection method and device |
| CN111510278B (en) * | 2020-04-26 | 2023-01-13 | Oppo广东移动通信有限公司 | Hyper frame number HFN synchronization method, terminal and storage medium |
| CN111865820B (en) * | 2020-07-10 | 2023-06-27 | 锐迪科微电子科技（上海）有限公司 | Data transmission method, device, receiving end, communication system, equipment and medium |
Family Cites Families (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2006217100A (en) * | 2005-02-02 | 2006-08-17 | Nec Corp | Decoding processing system and method thereof, and mobile communication system using same |
| TWM357138U (en) * | 2007-09-28 | 2009-05-11 | Interdigital Patent Holdings | Wireless transmit receive unit |
| US8208498B2 (en) * | 2007-10-30 | 2012-06-26 | Qualcomm Incorporated | Methods and systems for HFN handling at inter-base station handover in mobile communication networks |
| CN101686494B (en) * | 2008-09-22 | 2012-07-04 | 电信科学技术研究院 | Method and device for processing packets by packet data convergence protocol (PDCP) layer |
| CN101729377A (en) * | 2008-10-30 | 2010-06-09 | 华为技术有限公司 | Hyper frame number (HFN) informing method, device and system |
| CN102137435B (en) * | 2010-10-21 | 2014-01-22 | 上海华为技术有限公司 | Method, device and system for processing data |
-
2010
- 2010-10-21 CN CN201010526833.3A patent/CN102137435B/en active Active
-
2011
- 2011-10-19 WO PCT/CN2011/080992 patent/WO2012051946A1/en active Application Filing
Also Published As
| Publication number | Publication date |
|---|---|
| WO2012051946A1 (en) | 2012-04-26 |
| CN102137435A (en) | 2011-07-27 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102137435B (en) | Method, device and system for processing data | |
| US11218477B2 (en) | Encryption key updates in wireless communication systems | |
| CN101940017B (en) | Operation of control protocol data units in packet data convergence protocol | |
| CN110999523A (en) | Method and user equipment for reconnecting a radio resource control connection with a radio access network node | |
| JP2021503842A (en) | Methods and equipment for handling asynchronous buffers | |
| JP4945564B2 (en) | Mobile communication system and radio communication method | |
| US20140112157A1 (en) | Method and apparatus for sending packet, updating and maintaining hyper frame number, and processing data | |
| CN110192399B (en) | Re-establishing radio resource control connections | |
| CN101878615A (en) | Authentication in the communication system during swap data | |
| CN108924964A (en) | Guarantee the method and user equipment of continuity | |
| CN102137441B (en) | method, device and system for data transmission | |
| CN108886713B (en) | Data transmission method, data receiving equipment and data sending equipment | |
| WO2007148635A1 (en) | Radio communication device and method used in mobile communication system | |
| US20080101608A1 (en) | Method and apparatus for handling protocol error in a wireless communications system | |
| US20080137574A1 (en) | Method and apparatus for handling data delivery in a wireless communications system | |
| WO2024032742A1 (en) | Service processing method and apparatus, device, storage medium, and program product | |
| WO2017194161A1 (en) | Method and system for loss mitigation during device to device communication mode switching | |
| CN101207463A (en) | Method and apparatus for renovating protocol error in a wireless communications system | |
| US8631313B2 (en) | Method of error detection for wireless transmission | |
| CN115118526A (en) | VR device data migration method | |
| CN109803257A (en) | A kind of security information update method and access network equipment | |
| JP2009044673A (en) | Radio apparatus, radio communication system, and radio information notification method | |
| EP2648436B1 (en) | Method and device for synchronizing uplink encryption parameters in unacknowledged mode | |
| KR20080044148A (en) | Apparatus and method for pdcp reset in mobile telecommunication system | |
| KR101808537B1 (en) | Networlk device and control method thereof |
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 |