Abstract:
The present invention relates to transmissions and retransmissions of packet data, particularly ciphered data, in a communications system. Especially, it relates to radio link transmissions and avoidance of deciphering failures in a cellular mobile radio system, particularly a Universal Mobile Telecommunications System, UMTS, or WCDMA system.

Description:
TECHNICAL FIELD OF THE INVENTION  
       [0001]     The present invention relates to transmissions and retransmissions of packet data in a communications system. Especially, it relates to radio link transmissions and avoidance of deciphering failures in a cellular mobile radio system, particularly a Universal Mobile Telecommunications System, UMTS, or WCDMA system.  
       BACKGROUND AND DESCRIPTION OF RELATED ART  
       [0002]     In many radio communications system, such as UMTS, ciphering or encryption protects user data and signaling confidentiality. For detection of transmission errors data is also protected by an error detecting code. For this purpose a cyclic redundancy check code or CRC-code is used.  
         [0003]     Within this patent application, a radio network controller, RNC, is understood as a network element including an RRM (Radio Resource Management) entity. The RNC is connected to a fixed network. Node B is a logical node responsible for radio transmission/reception in one or more cells to/from a User Equipment. A base station, BS, is a physical entity representing Node B.  
         [0004]     With reference to  FIG. 1 , base stations &lt;&lt;BS  1 &gt;&gt; and &lt;&lt;BS  2 &gt;&gt; are physical entities representing Nodes B &lt;&lt;Node B  1 &gt;&gt; and &lt;&lt;Node B  2 &gt;&gt; respectively. &lt;&lt;Node B  1 &gt;&gt; and &lt;&lt;Node B  2 &gt;&gt; terminate the air interface, called Uu interface within UMTS, between UE and respective Node B towards the radio network controller &lt;&lt;RNC&gt;&gt;. &lt;&lt;RNC&gt;&gt; is connected to a fixed network &lt;&lt;Network&gt;&gt;.  
         [0005]     In  FIG. 1 , the base stations are connected to the same radio network controller RNC. However, this specification also covers the exemplary situation where the base stations are connected to different RNCs. In UMTS, the RLC protocol is terminated in a serving RNC, SRNC, responsible for interconnecting the radio access network of UMTS to a core network.  
         [0006]     3 rd  Generation Partnership Project (3GPP): Technical Specification Group Radio Access Network, Radio Interface Protocol Architecture, 3GPP TS 25.301 v3.6.0, France, September 2000, describes an overall protocol structure of a Universal Mobile Telecommunications System (UMTS). There are three protocol layers: 
        physical layer, layer  1  or L 1 ,     data link layer, layer  2  or L 2 , and     network layer, layer  3  or L 3 .        
 
         [0010]     Layer  2 , L 2 , and layer  3 , L 3  are divided into Control and User Planes. Layer  2  consists of two sub-layers, RLC and MAC, for the Control Plane and four sub-layers, BMC, PDCP, RLC and MAC, for the User Plane. The acronyms BMC, PDCP, RLC and MAC denote Broadcast/Multicast Control, Packet Data Convergence Protocol, Radio Link Control and Medium Access Control respectively.  
         [0011]      FIG. 2  displays a simplified UMTS layers  1  and  2  protocol structure for a Uu Stratum, UuS, or Radio Stratum, between a user equipment UE and a Universal Terrestrial Radio Access Network, UTRAN.  
         [0012]     Radio Access Bearers, RABs, are associated with the application for transportation of services between core network, CN, and user equipment, UE, through a radio access network. Each RAB is associated with quality attributes such as service class, guaranteed bit rate, transfer delay, residual BER, and traffic handling priority. An RAB may be assigned one or more Radio Bearers, RBs, being responsible for the transportation between UTRAN and UE. For each mobile station there may be one or several RBs representing a radio link comprising one or more channels between UE and UTRAN. Data flows (in the form of segments) of the RBs are passed to respective Radio Link Control, RLC, entities which amongst other tasks buffer the received data segments. There is one RLC entity for each RB. In the RLC layer, RBs are mapped onto respective logical channels. A Medium Access Control, MAC, entity receives data transmitted in the logical channels and further maps logical channels onto a set of transport channels. In accordance with subsection 5.3.1.2 of the 3GPP technical specification MAC should support service multiplexing e.g. for RLC services to be mapped on the same transport channel. In this case identification of multiplexing is contained in the MAC protocol control information.  
         [0013]     Transport channels are finally mapped to a single physical channel which has a total bandwidth allocated to it by the network. In frequency division duplex mode, a physical channel is defined by code, frequency and, in the uplink, relative phase (I/Q). In time division duplex mode a physical channel is defined by code, frequency, and timeslot. As further described in subsection 5.2.2 of the 3GPP technical specification the L 1  layer is responsible for error detection on transport channels and indication to higher layer, FEC encoding/decoding and interleaving/deinterleaving of transport channels.  
         [0014]     Segmentation and reassembly of data units are performed between different protocol layers as schematically illustrated in  FIG. 3 .  
         [0015]     A MAC protocol data unit, MAC PDU, also called transport block, TB, is the basic unit passed down to L 1  from MAC layer.  
         [0016]     A number of MAC PDUs shown in  FIG. 3  shall comprise a transport block set. Note, however, that in all cases a transport block set need not necessarily match with an RLC SDU. The span of a transport block set can be smaller or larger than an RLC SDU.  
         [0017]     Transport blocks, TBs, passed to L 1  from MAC at the same time instance and using the same transport channel form a transport block set.  
         [0018]     A higher layer PDU can be reassembled by simply concatenating all RLC PDUs included in a transport block set as implied by the used transport format.  
         [0019]     A transmission time interval, TTI, is defined as the interarrival time of Transport Block Sets, i.e. the time it should take to transmit a transport block set.  
         [0020]     A transport format is defined as a format offered by L 1  to MAC for the delivery of a Transport Block Set during a Transmission Time Interval on a Transport Channel, and is a combination of encodings, interleaving, bit rate and mapping onto physical channels.  
         [0021]     3 rd  Generation Partnership Project (3GPP): Technical Specification Group Radio Access Network, Multiplexing and channel coding (FDD), 3GPP TS 25.212 v4.4.0, France, March 2002, describes different generator polynomials of CRC-codes used in UMTS. The respective generator polynomials are 
 
 g   24 ( x )=1+ x+x   5   +x   6   +x   23   +x   24 , 
 
 g   16 ( x )=1+ x   5   +x   12   +x   16 , 
 
 g   12 ( x )=1+ x+x   2   +x   3   +x   11   +x   12 , 
 
 g   8 ( x )=1+ x+x   3   +x   4   +x   7   +x   8 . 
 
         [0022]     The respective number of parity bits in the resulting code word equals the exponent of the highest power term of the respective generator polynomial. Which CRC-code to use for each Transport Channel, TrCH, is signaled from protocol layers above L 2 /MAC layer.  
         [0023]     3 rd  Generation Partnership Project (3GPP): Technical Specification Group Radio Access Network, Radio Link Control (RLC) protocol specification, 3GPP TS 25.322 v4.4.0, France, March 2002, specifies the RLC protocol. The RLC layer provides three services to the higher layers: 
        transparent data transfer service,     unacknowledged data transfer service, and     acknowledged data transfer service, 
 
 in the sequel referred to as transparent mode, TM, unacknowledged mode, UM, and acknowledged mode, AM, respectively. 
       
 
         [0027]     The 3GPP specification describes in chapter 9 elements for peer-to-peer communication. No RLC overhead is added for transparent mode data protocol data units, TMD-PDUs. Unacknowledged mode data protocol data units, UMD-PDUs, and acknowledged mode protocol data units, AMD-PDUs, are sequentially numbered. The sequence number, SN, parameter comprises 12 bits for AMD-PDUs and 7 bits for UMD-PDUs. SN is a modulo-integer sequence number, where the integer equals 4096 and 128 for AM and UM respectively. A hyper frame number indicator, HFNI, indicates a hyper frame number, HFN, to the peer entity. With the aid of this field HFN of UE and UTRAN, respectively, can be synchronized. Section 9.7.3 of the 3GPP specification describes SDU discard function for acknowledged, unacknowledged, and transparent modes.  
         [0028]     3rd Generation Partnership Project (3GPP): Technical Specification Group Services and System Aspects, 3G Security, Security Architecture, 3GPP TS 33.102 v4.3.0, France, December 2001, shows 3G security architecture. Four security features are provided with respect to confidentiality of data on a network access link: 
        cipher algorithm agreement,     cipher key agreement,     confidentiality of user data, and     confidentiality of signaling data.        
 
         [0033]     Section 6.4.8 of the 3GPP technical specification describes initialization of synchronization for ciphering and integrity protection. HFN and SN are initialized. HFN and SN form a COUNT-C variable, the 32-bit values of which are input to the ciphering algorithm. Section 6.6.4.1 of the 3GPP technical specification reveals the composition of COUNT-C in UMTS. HFN is incremented each SN cycle.  
         [0034]     International Patent Application WO0156249 reveals synchronization of encrypted data by means of sequence numbers. The sequence numbers are unencrypted and unencoded. Missing sequence numbers are used to detect lost data packets. A requirement of stream encryption algorithms is that the transmitting side and the receiving side be synchronized.  
         [0035]     None of the cited documents above discloses a method and system for exploring the inherent redundancy of the unencoded sequence numbers SNs, for avoidance of cipher synchronization failure and whereby the redundancy of CRC-encoded data can be reduced. Particularly, none of the cited documents reveals a method and system of disregarding erroneous sequence numbers or a method and system of HFN update, reducing the risk of erroneous HFN update due to SN containing one or more transmission errors or lost SNs.  
       SUMMARY OF THE INVENTION  
       [0036]     HFN is normally not transmitted over air, with initialization being one important exception. HFN is updated in both transmitter and receiver each time SN recycles.  
         [0037]     When SN is subject to transmission errors or when a data packet carrying an SN is lost there is risk of erroneous updating of HFN. Prior art reveals solution for acknowledged mode making use or error detection of encoded data for ordering retransmission. However, for unacknowledged mode this option is not available. Further, for many applications, particularly real-time applications it is desirable to use low-redundancy error detecting codes or, in some cases, no error detecting code.  
         [0038]     Consequently, it is an object of this invention to provide a method and system keeping synchronism in case of lost or erroneous SNs without relying on a CRC error detecting code.  
         [0039]     It is also an object to detect lost or erroneous sequence numbers, SNs.  
         [0040]     A further object is to leave HFN unaffected by lost or erroneous SNs.  
         [0041]     Finally, it is an object to introduce a mechanism for eliminating the effect of occasional erroneous or lacking SNs.  
         [0042]     These objects are met by the invention, which is particularly well suited for a Universal Mobile Telecommunications System, UMTS, disregarding SNs considered invalid when determining HFNs.  
         [0043]     Preferred embodiments of the invention, by way of examples, are described with reference to the accompanying drawings below. 
     
    
     BRIEF DESCRIPTION OF THE DRAWINGS  
       [0044]      FIG. 1  shows communication between a UE and a base station involved in a connection between an RNC and the UE.  
         [0045]      FIG. 2  displays a layered protocol structure, according to prior art, in a radio communications system.  
         [0046]      FIG. 3  schematically illustrates segmentation and reassembly of data units for different protocol layers.  
         [0047]      FIG. 4  illustrates a basic method of updating HFN at receiver side upon receipt of PDUs.  
         [0048]      FIG. 5  shows a block diagram illustrating a first embodiment of the invention comparing a prediction estimate and received sequence number.  
         [0049]      FIG. 6  shows a flow chart illustrating a first embodiment of the invention.  
         [0050]      FIG. 7  illustrates a second embodiment of the invention, considering PDUs within a sliding decision-window.  
         [0051]      FIG. 8  shows three cases with exemplary sequences illustrating the second embodiment.  
     
    
     DESCRIPTION OF PREFERRED EMBODIMENTS  
       [0052]     With reference to  FIG. 1 , encrypted or ciphered data is transmitted over the radio interface between &lt;&lt;UE/Client Device&gt;&gt; and &lt;&lt;BS  2 /Node B  2 &gt;&gt;. In uplink direction &lt;&lt;BS  2 /Node B  2 &gt;&gt; represents the receiver side of the radio interface and in downlink direction receiver side is represented by &lt;&lt;UE/Client Device&gt;&gt; and &lt;&lt;BS  2 /Node B  2 &gt;&gt; is on the transmitter side. Encrypted or ciphered data is transmitted from the transmitter side to the receiver side in protocol data units, PDUS.  
         [0053]     On the transmitter side it is a trivial matter to increase HFN as a sequence number counter starts a new cycle. However, this is not the case on the receiver side. First, the receiver side should use the same HFN as the transmitter side. Second, during PDU transmissions some PDUs may be lost. The receiver side should nevertheless use correct HFN and update HFN correctly in order not to loose synchronism.  
         [0054]      FIG. 4  shows a basic method of updating HFN at receiver side upon receipt of PDUs, each PDU including a sequence number, SN. According to the method a new cycle of sequence numbers is assumed to be started when the most recently received sequence number, SN i , is less than the sequence number, SN i-1 , of the PDU received consecutively preceding the most recently received PDU. Not restricting HFN to increase only at sequence number 0, the basic method updates HFN correctly also if one or more PDUs are lost during transmission.  
         [0055]     A basic method, e.g. as described above in relation to  FIG. 4 , does not necessarily increase HFN correctly in case of transmission errors. Since transmitter side increases HFN irrespective of whether it is increased at receiving side, this could result in lost synchronism between transmitting and receiving sides.  
         [0056]      FIG. 5  shows a block diagram and  FIG. 6  shows a flow chart illustrating a first embodiment of the invention where sequence numbers are purged from a, real or fictitious, list according to the condition 
   SN   n   &gt;SN   n-1 +Δ max ( mod I ), where  (1)  Δ max   =N   TTI   ·TB   max +δ,  (2)  
 prior to determining HFN with a basic method, such as the method described in relation to  FIG. 4 , at the receiver side. In equation (1) I=4096 for acknowledged mode and I=128 for unacknowledged mode when applied to UMTS according to cited 3GPP specification. SN n  is the sequence number with list index n and SN n-1  is the sequence number of the PDU received immediately preceding a remaining PDU with sequence number SN n . In  FIG. 6 , the modulus operation of equation (1) has not been indicated for reasons of readability. Calculation modulo I in equation (1) relies on the cyclic characteristic of the sequence numbers. When the cycle length of the sequence numbers changes, so does I. In equation (2), N TTI  is the number of transmission time intervals, TTIs, when no data is received and TB max  is the maximum number of transport blocks in the transport format, TF, of the corresponding transport channel. After proper disregarding of one or more erroneous sequence numbers, in  FIG. 6  illustrated by purging the sequence number from a list arranged according to arrival time, the remaining sequence numbers are used as input for basic updating of HFN. 
 
         [0057]     Disregarding an SN as regards deciphering synchronization does not imply that the corresponding PDU necessarily is discarded from RLC. Nor does it imply that the PDU is not discarded. Preferably, according to the invention corresponding PDU is not discarded from RLC.  
         [0058]     By adding a term, δ=2, in equation (2) one RLC discard operation or RLC reconfiguration is allowed between two consecutively received PDUs. For each disregarded SN, δ is increased by 1. When an SN is not disregarded, δ is reset to 2.  
         [0059]     The first embodiment of the invention can, alternatively, be considered as a prediction of the next received sequence number, considering lost PDUs. In  FIG. 5  sequence numbers &lt;&lt;SNs&gt;&gt; as received are input to a prediction entity &lt;&lt;Prediction&gt;&gt; and an optional storage element &lt;&lt;Buffer&gt;&gt; allowing for time alignment of received data with predicted data as need be. The greater the number of lost PDUS, estimated from the number of transmission time intervals with no received PDUs and the maximum number of transport blocks in the transport format, the greater the prediction interval of sequence numbers to come. If the next sequence number is not within the prediction interval it is disregarded. In  FIG. 5  this is performed in entity &lt;&lt;Cmp &amp; Purge&gt;&gt;. The purged sequence of sequence numbers &lt;&lt;Purged SNs&gt;&gt; is then fed to basic HFN update, e.g. an entity operating according to the updating described in relation to  FIG. 4 .  
         [0060]     If, e.g., a transmitted sequence of sequence numbers is . . . 5, 6, 7, 8, 9, 10, 11, . . . and the received sequence is . . . 5, 6, 7, 8, 65, 10, 11, . . . and there are no TTIs with no data, then initially Δ max =2 according to equation (2). As 6−5=12, 7−6=12 and 8−7=12, no purging will occur until 65−8=57&gt;2, in the next interval. The sequence number transmitted as 9 and received as 65 will be purged, and thereafter treated like a lost sequence number. Consequently Δ max  is set to 3, as indicated by equation (2). At receipt of sequence number 10, the prediction disregards the received sequence number 65 and the comparison yields 10−8=23. Consequently sequence number 10 will remain and be transferred for basic HFN updating. At receipt of sequence number 11, it is again noted that no TTI is lost since reception of sequence number 10, and Δ max  is reset to 2. As 11−10=12, sequence number 11 will not be disregarded.  
         [0061]     If, for the same transmitted sequence as in the preceding paragraph, a smaller sequence number, e.g. 2, were received in place of transmitted 9, the comparison would yield, with exemplary modulo 128 calculus (I=128), 2-8=122&gt;2 and the erroneously received sequence number disregarded similarly to the case of an erroneously received sequence number 65 in the paragraph above.  
         [0062]     According to a second embodiment, PDUs within a sliding decision-window spanning over at least four consecutively received PDUs are considered, when increasing HFN. In an algorithm of increasing HFN not considering erroneous or lost SNs, such as the algorithm described above, an indicated increase of HFN is disregarded, if the HFN would not be increased also if any one of the sequence numbers of the sliding decision-window were disregarded. This is illustrated in the flowchart of  FIG. 7 . PDUs within a decision window comprising M+1 PDUs are considered at decision time-interval of PDU i, i.e. PDUs with sequence numbers, SNs, in the interval [i−M,i] are considered. One SN or PDU is disregarded among the M+1 considered PDUs. In  FIG. 7 , the SN of the most recently received PDU is disregarded first. However, any scheme for disregarding the SNs or PDUs would apply as well, only it guarantees the possibility of disregarding any one of the SNs of PDUs within the decision window as need be. If HFN should not be increased according to a basic method of updating HFN, with a sequence number of one PDU being disregarded, HFN is left unincreased. The receiver then proceeds with the next SN/PDU, restarting the flow chart at time interval i+1. However, if HFN would be increased if the SN of the most recently received PDU were disregarded and not all PDUs&#39; SNs have been disregarded once, the SN of next PDU within the decision window is disregarded. This repeats until the SNs of all M+1 PDUs within the decision window have been disregarded once for the final decision at interval i or an HFN update according to the basic method does not increase HFN. If HFN should be increased according to the basic method of updating when each one of the SNs/PDUs within the decision window is disregarded, the HFN is updated. Otherwise it is not.  
         [0063]     As for the first embodiment, disregarding an SN/PDU as regards deciphering synchronization does not imply that the corresponding PDU necessarily is discarded from RLC in the second embodiment. Nor does it imply that the PDU is not discarded. Preferably, according to the invention corresponding PDU is not discarded from RLC.  
         [0064]      FIG. 8  shows three cases with exemplary sequences illustrating the second embodiment. In the first two cases, A and B, an exemplary transmitted sequence of SNs is . . . 5, 6, 7, 8, 9, 10, . . . in decimal notion. However, in case A the transmitted SN 9 is erroneously received as 2 and in case B it is erroneously received as 65. Assuming that a basic HFN updating at the receiving side increases HFN whenever an SN is smaller than the preceding SN, this would erroneously increase HFN in time interval T 1  in case A and in time interval T 2  for case B. This would also affect deciphering of a substantial amount of subsequent PDUs due to lost synchronization. According to the second embodiment of the invention, this erroneous updating is eliminated at the cost of omitted decoding of only one PDU by considering all PDUs within the sliding decision-window. In  FIG. 8 a  window size equal to 5 is illustrated.  
         [0065]     For case A, at time interval T 1 , the erroneous updating of HFN is circumvented according to the second embodiment of the invention, since if the most recently received PDU with sequence number 2 is disregarded, no updating of HFN would occur in time interval T 1 . Further, when sliding the decision window one step to the right for making a decision in time interval T 2 , again disregarding the sequence number 2 of time interval T 1 , no updating of HFN would occur.  
         [0066]     In case B, erroneous updating of HFN in time interval T 2  is circumvented. Again, time interval T 1  is within the decision window and disregarding the sequence number 65 of the PDU received in time interval T 1  would result in HFN not being incremented in time interval T 2 .  
         [0067]     In case C, no transmission error of received PDUs is assumed. However PDUs with sequence numbers 127, 0, 1 and 2 have been lost. Again assuming that HFN is updated when the preceding SN is greater than the current SN, HFN would not be updated in time interval T 1 , as it would according to a basic method, such as the one illustrated in  FIG. 4 , but in time interval T 2 , since disregarding the sequence number received in time-interval T 1  would result in HFN not being increased in accordance with case A.  
         [0068]     If, in the second embodiment of the invention, the window size spanned over less than four PDUs, HFN would not be increased correctly. If, e.g., the window size spanned only three PDUs for the exemplary sequence of case C in  FIG. 8 , disregarding sequence number 3 at time interval T 1  or disregarding sequence number 126 at time interval T 2  would leave HFN unchanged, and synchronization would be lost. Preferably the window size spans over exactly four SNs (PDUs).  
         [0069]     Preferably, all system elements, such as UEs and RNCs in UMTS, where applicable operate according to the invention. However, the invention can also be used in systems also including some equipment, such as UEs and RNCs, not operating according to the invention.  
         [0070]     Some exemplary features and characteristics of the invention are listed below.  
         [0071]     1. A method of failure avoidance when synchronizing a transceiver end and a receiver end by means of transmitted sequence numbers, each sequence number not necessarily being further error protected, the method characterized in that a received sequence number considered erroneous according to a predetermined criterion is disregarded.  
         [0072]     2. The method according to characteristic 1 characterized in that the criterion comprises arranging of sequence numbers according to their time of arrival and purging of received sequence numbers not being within a prediction interval as determined from earlier received and non-purged one or more sequence numbers and number of one or more transmission time intervals with no data received between consecutively received sequence numbers.  
         [0073]     3. The method according to characteristic 2 characterized in that the transmission time intervals are weighted by the maximum number of transmission blocks of the transport format.  
         [0074]     4. The method according to characteristic 3 characterized in that an integer is added to the weighted number of transmission intervals.  
         [0075]     5. The method according to any of characteristics 2-4 characterized in that a received sequence number being greater than an estimated greatest sequence number allowed is disregarded.  
         [0076]     6. The method according to any of characteristics 2-4 characterized in that a received sequence number not being greater than an estimated greatest sequence number allowed is not disregarded.  
         [0077]     7. The method according to any of characteristics 1-6 characterized in that the purged sequence of sequence numbers is passed to updating of a hyper frame number.  
         [0078]     8. The method according to characteristic 7 characterized in that the hyper frame number is updated according to a basic method.  
         [0079]     9. The method according to characteristic 1 characterized in that the criterion comprises arranging of received sequence numbers according to their time of arrival and for each decision interval sequentially disregard each one of the received sequence numbers within a decision window comprising consecutively received sequence numbers.  
         [0080]     10. The method according to characteristic 9 characterized in that the decision window spans over an integer number of consecutively received sequence numbers starting with the sequence number of the decision interval.  
         [0081]     11. The method according to characteristic 9 or 10 characterized in that the decision window spans over an integer number of consecutively received sequence numbers starting with the sequence number of the most recently received sequence number.  
         [0082]     12. The method according to any of characteristics 9-11 characterized in that the decision window spans over at least four consecutively received sequence numbers.  
         [0083]     13. The method according to any of characteristics 9-12 characterized in that for each disregarded sequence number a candidate hyper frame updating is undertaken.  
         [0084]     14. The method according to characteristic 13 characterized in that the candidate hyper frame updating is undertaken according to a basic method.  
         [0085]     15. The method according to characteristic 13 or 14 characterized in that if, for any one disregarded sequence number within the decision window, the candidate hyper frame number updating results in a non-increased hyper frame number, no further sequence number is disregarded and no further candidate HFN updating is undertaken for the decision interval.  
         [0086]     16. The method according to any of characteristics 13-15 characterized in that if, for any one disregarded sequence number within the decision window, the candidate hyper frame number updating results in a non-increased hyper frame number, the hyper frame number of the decision interval is set equal to the hyper frame number of the preceding decision interval.  
         [0087]     17. The method according to any of characteristic 13 or 14 characterized in that if, for all each one of the disregarded sequence numbers within the decision window, the candidate hyper frame number updating results in the same hyper frame number, this candidate hyper frame number is decided to be the hyper frame number of the decision interval.  
         [0088]     18. The method according to any of characteristic 13 or 14 characterized in that if, for all each one of the disregarded sequence numbers within the decision window, the candidate hyper frame number updating results in a hyper frame number increase, the hyper frame number of the decision interval is set equal to the hyper frame number of the preceding decision interval increased by one.  
         [0089]     19. The method according to characteristics 8 or 14 characterized in that the basic method increases a hyper frame number if, when comparing two received sequence numbers, the most recent of the two sequence numbers is less than the other sequence number.  
         [0090]     20. The method according to characteristic 19 characterized in that the comparison is made modulo an integer, the integer being equal to the cycle length of transmitted sequence numbers.  
         [0091]     21. The method according to any of characteristics 1-20 characterized in that it is a method of avoiding cipher synchronization failure.  
         [0092]     22. The method according to any of characteristics 1-21 characterized in that it allows for reduction of redundancy being added to payload.  
         [0093]     23. An element for receiving one or more transmitted sequence numbers synchronizing to a transceiver end by means of the transmitted sequence numbers, each sequence number not necessarily being further error protected, the element characterized by processing means for disregarding one or more sequence numbers considered erroneous.  
         [0094]     24. The element according to characteristic 23 characterized in that the disregarding of one or more sequence numbers reduces or eliminates the risk of synchronization failure.  
         [0095]     25. The element according to characteristic 23 or 24 characterized in that the processing means disregards sequence numbers in accordance with the method in any of characteristics 1-22.  
         [0096]     26. An element for receiving one or more transmitted sequence numbers each sequence number not necessarily being further error protected, the element characterized by prediction means for prediction of a most recent sequence number from one or more earlier sequence numbers and comparison means for comparing the predicted sequence number with a received counterpart and for conditionally disregarding the received sequence number being the prediction counterpart.  
         [0097]     27. The element according to characteristic 26 characterized by the comparison means conditionally disregarding the received sequence number being the prediction counterpart if it exceeds a threshold value.  
         [0098]     28. The element according to characteristic 27 characterized in that the threshold value is determined including as a parameter number of transmission time intervals with no received data since consecutively formerly received sequence number was received.  
         [0099]     29. The element according to characteristic 28 characterized in that the number of transmission time intervals are weighted with a factor equal to the maximum number of transmission blocks of a current transport format.  
         [0100]     30. The element according to characteristic 29 characterized by the comparison means comprising transfer means for transferring the non-disregarded sequence numbers to an entity of basic hyper frame number updating.  
         [0101]     31. The element according to characteristic 30 characterized by the entity of basic hyper frame number updating updates one or more hyper frame numbers according to the method in characteristic 19 or 20.  
         [0102]     32. The element according to any of characteristics 23-31 characterized in that the element is included in or is a radio network controller.  
         [0103]     33. The element according to any of characteristics 23-31 characterized in that the element is included in or is a user equipment.  
         [0104]     34. The element according to any of characteristics 23-33 characterized in that the element is an element of UMTS or a WCDMA system.  
         [0105]     35. A radio communications system characterized by means for carrying out the method in any of characteristics 1-22.  
         [0106]     36. A radio communications system characterized by one or more elements according to any of characteristics 23-34.  
         [0107]     A person skilled in the art readily understands that the receiver and transmitter properties of a BS or a UE are general in nature. The use of concepts such as BS, UE or RNC within this patent application is not intended to limit the invention only to devices associated with these acronyms. It concerns all devices operating correspondingly, or being obvious to adapt thereto by a person skilled in the art, in relation to the invention. As an explicit non-exclusive example the invention relates to mobile stations without a subscriber identity module, SIM, as well as user equipment including one or more SIMs. Further, protocols and layers are referred to in close relation with UMTS and Internet terminology. However, this does not exclude applicability of the invention in other systems with other protocols and layers of similar functionality. As a non-exclusive example, the invention applies for radio resource management interfacing of a connection protocol application layer as well as interfacing of a connection protocol transport layer, such as TCP.  
         [0108]     The invention is not intended to be limited only to the embodiments described in detail above. Changes and modifications may be made without departing from the invention. It covers all modifications within the scope of the following claims.