IP Library › Granted Patent US 12,603,782
Granted Patent B2
US 12,603,782 · App. 17/285,991 · Granted Apr 14, 2026

Integrity protection schemes in mobile communication

Inventors: Anand Raghawa Prasad (Tokyo, JP); Sander De Kievit (Tokyo, JP); Hironori Ito (Tokyo, JP); Takahito Yoshizawa (Tokyo, JP)
Assignee: NEC CORPORATION
H04L9/3242H04L69/22H04L69/324H04W12/106H04L2209/80
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,603,782
App. No.
17/285,991
Granted
Apr 14, 2026
Kind
B2
Abstract

This invention introduces methods and mechanisms of partial integrity protection in mobile systems. A device comprising: a memory configured to store instructions; and a processor configured to execute the instructions to: generate a representation value based on protocol data unit (PDU) header data and payload data of a PDU; generate a message authentication code based on the representation value; and include the message authentication code in the PDU.

Claims (26)

1 . A User Equipment (UE) comprising:

a memory configured to store instructions; and

a processor configured to execute the instructions to:

generate a Packet Data Convergence Protocol (PDCP) data Protocol Data Unit (PDU); and

perform transmission of the PDCP data PDU to a receiver using a radio interface,

wherein a format of the PDCP data PDU is arranged in order of a Sequence Number (SN), security information, and data, and

wherein the security information comprises a plurality of bits and indicates that integrity protection is used or not, and the security information further indicates to derive two or more parameters indicating protection of the data.

2 . The UE of claim 1 , wherein the security information indicates that no integrity protection is used when the security information comprises a zero value.

3 . The UE of claim 1 , wherein the format of the PDCP data PDU is arranged in order of the SN, the security information, the data, and a Message Authentication Code for Integrity (MAC-I).

4 . The UE of claim 1 , wherein the security information further indicates, by the plurality of bits, information other than whether a Message Authentication Code (MAC) is used.

5 . A method of a User Equipment (UE), the method comprising:

generating a Packet Data Convergence Protocol (PDCP) data Protocol Data Unit (PDU); and

performing transmission of the PDCP data PDU to a receiver using a radio interface,

wherein a format of the PDCP data PDU is arranged in order of a Sequence Number (SN), security information, and data, and

wherein the security information comprises a plurality of bits and indicates that integrity protection is used or not, and the security information further indicates to derive two or more parameters indicating protection of the data.

6 . The method of claim 5 , wherein the security information indicates that no integrity protection is used when the security information comprises a zero value.

7 . The method of claim 5 , wherein the format of the PDCP data PDU is arranged in order of the SN, the security information, the data, and a Message Authentication Code for Integrity (MAC-I).

8 . The method of claim 5 , wherein the security information further indicates, by the plurality of bits, information other than whether a Message Authentication Code (MAC) is used.

9 . A method of a Radio Access Network (RAN) node, the method comprising:

generating a Packet Data Convergence Protocol (PDCP) data Protocol Data Unit (PDU); and

performing transmission of the PDCP data PDU to a User Equipment (UE),

wherein a format of the PDCP data PDU is arranged in order of a Sequence Number (SN), security information, and data, and

wherein the security information comprises a plurality of bits and indicates that integrity protection is used or not, and the security information further indicates to derive two or more parameters indicating protection of the data.

10 . The method of claim 9 , wherein the security information indicates that no integrity protection is used when the security information comprises a zero value.

11 . The method of claim 9 , wherein the format of the PDCP data PDU is arranged in order of the SN, the security information, the data, and a Message Authentication Code for Integrity (MAC-I).

12 . The method of claim 9 , wherein the security information further indicates, by the plurality of bits, information other than whether a Message Authentication Code (MAC) is used.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 2, 2022
From: PRASAD, ANAND RAGHAWA; DE KIEVIT, SANDER; ITO, HIRONORI; YOSHIZAWA, TAKAHITO
To: NEC CORPORATION
Reel/Frame 058863/0828 →
Priority Claims (1)
EP 18204195 · Nov 2, 2018 · regional
Continuity (1)
Related Publication 20210385090A1 · Dec 9, 2021
References Cited (33)
US 9585008B2 · Hsu · 2017 [cited by examiner]
US 10038701B2 · Yi · 2018 [cited by examiner]
US 20050235145A1 · Slick · 2005 [cited by examiner]
US 20100067698A1 · Hahn · 2010 [cited by examiner]
US 20100157904A1 · Ho · 2010 [cited by examiner]
US 20100202613A1 · Ray · 2010 [cited by examiner]
US 20100293372A1 · Fischer · 2010 [cited by examiner]
US 20110085471A1 · Zhang · 2011 [cited by examiner]
US 20110188408A1 · Yi · 2011 [cited by examiner]
US 20140313988A1 · Hsu · 2014 [cited by examiner]
US 20170149567A1 · Moskal · 2017 [cited by applicant]
US 20180146467A1 · Kim · 2018 [cited by examiner]
US 20180234873A1 · Tenny · 2018 [cited by examiner]
US 20200068391A1 · Liu · 2020 [cited by examiner]
US 20200205003A1 · Ingale · 2020 [cited by examiner]
US 20200404553A1 · Lovlekar · 2020 [cited by examiner]
US 20210051482A1 · Ito et al. · 2021 [cited by applicant]
US 20210385090A1 · Prasad · 2021 [cited by examiner]
EP 3527000B1 · 2022 [cited by examiner]
WO 2019159788A1 · 2019 [cited by applicant]
International Search Report of PCT Application No. PCT/JP2019/043082 mailed Jan. 8, 2020. [cited by applicant]
Written Opinion of the International Searching Authority of PCT Application No. PCT/JP2019/043082 mailed Jan. 8, 2020. [cited by applicant]
Ericsson, “[E126] Protection of user data in EDT”, 3GPP TSG-RAN WG2 #103, R2-1812265, Gothenburg, Sweden, Aug. 20-24, 2018. [cited by applicant]
Ericsson, “Remaining security aspects for EDT”, 3GPP TSG-RAN WG2 #102, R2-1807801, Busan, Republic of Korea, May 21-25, 2018. [cited by applicant]
NEC, “New solution for data rate limitation of integrity protection in UP DRB”, 3GPP TSG-SA WG3 Meeting #94Ad-Hoc, S3-190651, Stockholm, Sweden, Mar. 11-15, 2019. [cited by applicant]
NEC Corporation invention disclosure, “Integrity protection for user plane data in 5G network”, Filing #5050000034, Nov. 2, 2018, pp. 1-7. [cited by applicant]
NEC Corporation invention disclosure, “Efficient integrity protection”, filing #5050000050, Sep. 18, 2018. [cited by applicant]
Lenovo, Motorola Mobility, “Achieving higher data rates for UP IP”, 3GPP TSG SA WG3 (Security) Meeting #92 ad-hoc, S3-182942, Harbin, China, Sep. 24-28, 2018. [cited by applicant]
3GPP RAN2, “UE capability related to integrity protection of DRBs”, 3GPP TSG SA WG3 (Security) Meeting #91Bis, S3-181650 , La Jolla, US, May 21-25, 2018. [cited by applicant]
3rd Generation Partnership Project, “Technical Specification Group Services and System Aspects, System Architecture for the 5G System, Stage2 (Release 15)”, 3GPP TS 23.501 V15.3.0 (Sep. 2018), pp. 1-226. [cited by applicant]
3rd Generation Partnership Project, “Technical Specification Group Services and System Aspects, Procedures for the 5G System, Stage2 (Release 15)”, 3GPP TS 23.502 V15.3.0 (Sep. 2018), pp. 1-329. [cited by applicant]
3rd Generation Partnership Project, “Technical Specification Group Services and System Aspects, Security architecture and procedures for 5G system (Release 15)”, 3GPP TS 33.501 V15.2.0 (Sep. 2018), pp. 1-176. [cited by applicant]
3rd Generation Partnership Project, “Technical Specification Group Radio Access Network, NR, Packet Data Convergence Protocol (PDCP) specification (Release 15)”, 3GPP TS 38.323 V15.3.0 (Sep. 2018), pp. 1-26. [cited by applicant]