# US 2018/0027512 A1 · Handling of Hyper Frame Number De-Synchronization Incidents

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2018/0027512 A1
- Document ID: US20180027512A1
- Status: Published application
- Kind: A1
- Application number: 15/547,959
- Filed: 2016-02-25
- Published: 2018-01-25
- Earliest claimed: 2015-02-26
- Assignees: Telefonaktiebolaget LM Ericsson (publ)
- Applicants: Telefonaktiebolaget LM Ericsson (publ)
- Inventors: Gunnar BERGQUIST; Samir SHAH
- Web page: https://patentgrep.com/patent/US20180027512A1

## CPC

- H04W 56/001: {Synchronization between nodes}
- H04W 56/00: Synchronisation arrangements
- H04W 72/1263: Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows
- H04W 74/002: {Transmission of channel access control information}
- H04W 74/0866: {using a dedicated channel for access}
- H04W 76/19: Connection re-establishment
- H04W 84/042: {Public Land Mobile systems, e.g. cellular systems}
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)

## Abstract

The present disclosure concerns radio communication. In one of its aspects, this disclosure presents a method of assisting a receiving side PDCP entity of a network to facilitate its handling of a HFN de-synchronization incident. The method is performed by an apparatus such as a UE and comprises: while a RRC connection is in progress; detecting (120), e.g. by means of a transmitting side PDCP entity of the UE, a condition indicative of the transmitting side PDCP entity experiencing a HFN de-synchronization or a risk of HFN de-synchronization; and in response thereto maintaining (130) the RRC connection and concurrently sending a control message to the receiving side PDCP entity, the control message comprising information that the RRC connection is lasting and, thus, unbroken as well as information that the transmitting side PDCP entity is experiencing the HFN de-synchronization or the risk of HFN de-synchronization. Hereby it is made possible to allow for a limited, or reduced, signaling when handling HFN de-synchronization incidents.

## Claims

### Claim 1

A method of assisting a receiving side Packet Data Convergence Protocol, PDCP, entity of a network to facilitate its handling of a Hyper Frame Number, HFN, de-synchronization incident, the method being performed by an apparatus, and comprising:
while a Radio Resource Control, RRC, connection is in progress;
detecting, by means of a transmitting side PDCP entity of the apparatus, a condition indicative of the transmitting side PDCP entity experiencing a HFN de-synchronization or experiencing a risk of HFN de-synchronization; and in response thereto
maintaining the RRC connection and concurrently sending a control message to the receiving side PDCP entity, the control message comprising information that the RRC connection is lasting and, thus, unbroken as well as information that the transmitting side PDCP entity is experiencing the HFN de-synchronization or the risk of HFN de-synchronization.

### Claim 2 (depends on 1)

The method according to claim 1, further comprising:
monitoring HFN de-synchronization or risk of HFN de-synchronization while the RRC connection is in progress.

### Claim 3 (depends on 1)

The method according to claim 1, the method comprising:
estimating a number of consecutive ciphered PDCP Packet Data Units, PDUs, that are lost,
comparing the estimated number of consecutive ciphered PDCP PDUs that are lost with a predefined threshold value, and
determining that there exists a condition indicative of the transmitting side PDCP entity experiencing a HFN de-synchronization or a risk of HFN de-synchronization in response to that the estimated number of consecutive ciphered PDCP PDUs that are lost is higher than the predefined threshold value.

### Claim 4 (depends on 1)

The method according to claim 1, further comprising:
including, into the control message, a report comprising details related to the experienced HFN de-synchronization or the experienced risk of HFN de-synchronization.

### Claim 5 (depends on 4)

The method according to claim 4, further comprising:
including, into the control message, information related to a proposed re-set action to be used by the receiving side PDCP entity.

### Claim 6 (depends on 1)

The method according to claim 1, wherein the control message is a PDCP control Protocol Data Unit, PDU.

### Claim 7 (depends on 1)

The method according to claim 1, further comprising:
triggering a RRC counterCheck procedure to verify that HFN synchronization has regained.

### Claim 8 (depends on 1)

The method according to claim 1, wherein the apparatus is a User Equipment, UE.

### Claim 9 (depends on 1)

Computer program, comprising instructions which, when executed on at least one processor, cause the at least one processor to carry out the method according to claim 1.

### Claim 10 (depends on 9)

A carrier comprising the computer program according to claim 9, wherein the carrier is one of an electronic signal, an optical signal, a radio signal, or a computer readable storage medium.

### Claim 11

An apparatus, for assisting a receiving side Packet Data Convergence Protocol, PDCP, entity of a network to facilitate its handling of a Hyper Frame Number, HFN, de-synchronization incident, the apparatus comprising:
a transmitting side PDCP entity:
a processor; and
a memory comprising instructions executable by the processor whereby the apparatus is operative to:
while a Radio Resource Control, RRC, connection is in progress;
detect, by means of the transmitting side PDCP entity, a condition indicative of the transmitting side PDCP entity experiencing a HFN de-synchronization or a risk of HFN de-synchronization; in response thereto
maintain the RRC connection and concurrently send, by means of the transmitting side PDCP entity, a control message to the receiving side PDCP entity, the control message comprising information that the RRC connection is lasting and, thus, unbroken as well as information that the transmitting side PDCP entity is experiencing the HFN de-synchronization or the risk of HFN de-synchronization.

### Claim 12 (depends on 11)

The apparatus according to claim 11, wherein the memory comprises instructions executable by the processor whereby the apparatus is operative to:
monitor HFN de-synchronization or risk of HFN de-synchronization while the RRC connection is in progress.

### Claim 13 (depends on 11)

The apparatus according to claim 11, wherein the memory comprises instructions executable by the processor whereby the apparatus is operative to:
estimate a number of consecutive ciphered PDCP Packet Data Units, PDUs, that are lost,
compare the estimated number of consecutive ciphered PDCP PDUs that are lost with a predefined threshold value, and
determine that there exists a condition indicative of the transmitting side PDCP entity experiencing a HFN de-synchronization or a risk of HFN de-synchronization in response to that the estimated number of consecutive ciphered PDCP PDUs that are lost is higher than the predefined threshold value.

### Claim 14 (depends on 11)

The apparatus according to claim 11, wherein the memory comprises instructions executable by the processor whereby the transmitting side PDCP entity is operative to:
include, into the control message, a report comprising details related to the experienced HFN de-synchronization or the experienced risk of HFN de-synchronization.

### Claim 15 (depends on 14)

The apparatus according to claim 14, wherein the memory comprises instructions executable by the processor whereby the transmitting side PDCP entity is operative to:
include, into the control message, information related to a proposed re-set action to be used by the receiving side PDCP entity.

### Claim 16 (depends on 11)

The apparatus according to claim 11, wherein the control message is control PDCP Protocol Data Unit, PDU.

### Claim 17 (depends on 11)

The apparatus according to claim 11, wherein the memory comprises instructions executable by the processor whereby the transmitting side PDCP entity is operative to:
trigger a RRC counterCheck procedure to verify that HFN synchronization has regained.

### Claim 18 (depends on 11)

The apparatus according to claim 11, wherein the apparatus is a User Equipment, UE.
