US 11,924,795 B2
Ethernet protocol data unit (PDU) session—hyper frame number (HFN) resync
Sitaramanjaneyulu Kanamarlapudi, San Diego, CA (US); Arun Prasanth Balasubramanian, San Diego, CA (US); Feilu Liu, San Diego, CA (US); Suli Zhao, San Diego, CA (US); Vaibhav Kumar, Encinitas, CA (US); and Dan Gilboa Waizman, San Diego, CA (US)
Assigned to QUALCOMM Incorporated, San Diego, CA (US)
Filed by QUALCOMM Incorporated, San Diego, CA (US)
Filed on Nov. 30, 2021, as Appl. No. 17/538,756.
Prior Publication US 2023/0171727 A1, Jun. 1, 2023
Int. Cl. H04W 56/00 (2009.01); H04L 69/22 (2022.01); H04W 76/19 (2018.01); H04W 80/02 (2009.01)
CPC H04W 56/0055 (2013.01) [H04L 69/22 (2013.01); H04W 56/001 (2013.01); H04W 76/19 (2018.02); H04W 80/02 (2013.01)] 30 Claims
OG exemplary drawing
 
1. A method of wireless communication performed by a first network entity, the method comprising:
receiving, from a second network entity, an Ethernet frame over a wireless link, the Ethernet frame including an Ethernet header and an Ethernet payload;
determining, based, at least in part, on the Ethernet header of the Ethernet frame, whether a hyper frame number (HFN) synchronization failure in a current communication session between the first network entity and the second network entity has occurred, wherein a current HFN at the first network entity and a current HFN at the second network entity are not synchronized to each other when the HFN synchronization failure in the current communication session has occurred; and
performing, in response to a determination that the HFN synchronization failure has occurred, a resynchronization procedure to synchronize the current HFN at the first network entity to the current HFN at the second network entity.