IP Library › Granted Patent US 12,598,459
Granted Patent B2
US 12,598,459 · App. 18/615,965 · Granted Apr 7, 2026

Method and apparatus for identifying security key in next generation mobile communication system

Inventors: Donggun Kim (Suwon-si, KR); Soenghun Kim (Suwon-si, KR)
Assignee: Samsung Electronics Co., Ltd.
H04W12/0433H04W12/037H04W12/106H04W12/45H04W76/11H04W76/27
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,598,459
App. No.
18/615,965
Granted
Apr 7, 2026
Kind
B2
Abstract

The disclosure relates to a communication scheme and system for converging a 5 th generation (5G) communication system for supporting a data rate higher than that of a 4 th generation (4G) system with an internet of things (IoT) technology. The disclosure is applicable to intelligent services (e.g., smart home, smart building, smart city, smart car or connected car, health care, digital education, retail, and security and safety-related services) based on the 5G communication technology and the IoT-related technology. The disclosure relates to a method and apparatus for allowing a base station to identify a ciphering key (COUNT value) for security enhancement.

Claims (60)

1 . A method performed by a terminal in a wireless communication system, the method comprising:

receiving, from a base station, a counter check message including a first list for at least one data radio bearer (DRB), the first list including an identity of a first DRB established for the terminal and a most significant bits (MSBs) value of a first count value associated with the first DRB, wherein the MSBs value of the first count value includes a MSBs value of a first uplink count value and a MSBs value of a first downlink count value; and

transmitting, to the base station as a response to the counter check message, a counter check response message including a second list,

wherein in case that, for at least one direction of uplink or downlink, a MSBs value of a second count value of the terminal associated with the first DRB is different from the MSBs value of the first count value associated with the first DRB in the first list, the second list includes the identity of the first DRB, a second uplink count value of the terminal associated with the first DRB, and a second downlink count value of the terminal associated with the first DRB,

wherein the second uplink count value of the terminal associated with the first DRB indicates a value of TX_NEXT−1 and the second downlink count value of the terminal associated with the first DRB indicates a value of RX_NEXT−1, and

wherein the TX_NEXT is a count value of a next packet data convergence protocol (PDCP) service data unit (SDU) to be transmitted and the RX_NEXT is a count value of a next PDCP SDU expected to be received.

2 . The method of claim 1 ,

wherein, in case that the first DRB is a uni-directional bearer configured for one direction of uplink or downlink and no count value exists for the other direction, a count value for the other direction is assumed to be 0.

3 . The method of claim 1 ,

wherein, in case that an identity of a second DRB established for the terminal is not included in the first list of the counter check message, the second list includes the identity of the second DRB, a third uplink count value of the terminal associated with the second DRB, and a third downlink count value of the terminal associated with the second DRB, and

wherein the third uplink count value of the terminal associated with the second DRB is set to a value of the TX_NEXT−1 and the third downlink count value of the terminal associated with the second DRB is set to a value of the RX_NEXT−1.

4 . The method of claim 1 ,

wherein, in case that an identity of a third DRB not established for the terminal is included in the first list of the counter check message, the second list includes the identity of the third DRB, and a fourth count value of the terminal associated with the third DRB having MSBs and least significant bits (LSBs), the MSBs being set identical to a corresponding MSBs value of a count value associated with the third DRB which is included in the first list of the counter check message, the LSBs being set to 0, and the fourth count value of the terminal associated with the third DRB including a fourth uplink count value associated with the third DRB and a fourth downlink count value associated with the third DRB.

5 . A method performed by a base station in a wireless communication system, the method comprising:

transmitting, to a terminal, a counter check message including a first list for at least one data radio bearer (DRB), the first list including an identity of a first DRB established for the terminal and a most significant bits (MSBs) value of a first count value associated with the first DRB, wherein the MSBs value of the first count value includes a MSBs value of a first uplink count value and a MSBs value of a first downlink count value; and

receiving, from the terminal as a response to the counter check message, a counter check response message including a second list,

wherein in case that, for at least one direction of uplink or downlink, a MSBs value of a second count value of the terminal associated with the first DRB is different from the MSBs value of the first count value associated with the first DRB in the first list, the second list includes the identity of the first DRB, a second uplink count value of the terminal associated with the first DRB, and a second downlink count value of the terminal associated with the first DRB,

wherein the second uplink count value of the terminal associated with the first DRB indicates a value of TX_NEXT−1 and the second downlink count value of the terminal associated with the first DRB indicates a value of RX_NEXT−1, and

wherein the TX_NEXT is a count value of a next packet data convergence protocol (PDCP) service data unit (SDU) to be transmitted and the RX_NEXT is a count value of a next PDCP SDU expected to be received.

6 . The method of claim 5 ,

wherein, in case that the first DRB is a uni-directional bearer configured for one direction of uplink or downlink and no count value exists for the other direction, a count value for the other direction is identified to be 0.

7 . The method of claim 5 ,

wherein, in case that an identity of a second DRB established for the terminal is not included in the first list of the counter check message, the second list includes the identity of the second DRB, a third uplink count value of the terminal associated with the second DRB, and a third downlink count value of the terminal associated with the second DRB, and

wherein the third uplink count value of the terminal associated with the second DRB is set to a value of the TX_NEXT−1 and the third downlink count value of the terminal associated with the second DRB is set to a value of the RX_NEXT−1.

8 . The method of claim 5 ,

wherein, in case that an identity of a third DRB not established for the terminal is included in the first list of the counter check message, the second list includes the identity of the third DRB, and a fourth count value of the terminal associated with the third DRB having MSBs and least significant bits (LSBs), the MSBs being set identical to a corresponding MSBs value of a count value associated with the third DRB which is included in the first list of the counter check message, the LSBs being set to 0, and the fourth count value of the terminal associated with the third DRB including a fourth uplink count value associated with the third DRB and a fourth downlink count value associated with the third DRB.

9 . A terminal in a wireless communication system, the terminal comprising:

a transceiver; and

a controller configured to:

receive, via the transceiver from a base station, a counter check message including a first list for at least one data radio bearer (DRB), the first list including an identity of a first DRB established for the terminal and a most significant bits (MSBs) value of a first count value associated with the first DRB, wherein the MSBs value of the first count value includes a MSBs value of a first uplink count value and a MSBs value of a first downlink count value, and

transmit, via the transceiver to the base station as a response to the counter check message, a counter check response message including a second list,

wherein in case that, for at least one direction of uplink or downlink, a MSBs value of a second count value of the terminal associated with the first DRB is different from the MSBs value of the first count value associated with the first DRB in the first list, the second list includes the identity of the first DRB, a second uplink count value of the terminal associated with the first DRB, and a second downlink count value of the terminal associated with the first DRB,

wherein the second uplink count value of the terminal associated with the first DRB indicates a value of TX_NEXT−1 and the second downlink count value of the terminal associated with the first DRB indicates a value of RX_NEXT−1, and

wherein the TX_NEXT is a count value of a next packet data convergence protocol (PDCP) service data unit (SDU) to be transmitted and the RX_NEXT is a count value of a next PDCP SDU expected to be received.

10 . The terminal of claim 9 ,

wherein, in case that the first DRB is a uni-directional bearer configured for one direction of uplink or downlink and no count value exists for the other direction, a count value for the other direction is assumed to be 0.

11 . The terminal of claim 9 ,

wherein, in case that an identity of a second DRB established for the terminal is not included in the first list of the counter check message, the second list includes the identity of the second DRB, a third uplink count value of the terminal associated with the second DRB, and a third downlink count value of the terminal associated with the second DRB, and

wherein the third uplink count value of the terminal associated with the second DRB is set to a value of the TX_NEXT−1 and the third downlink count value of the terminal associated with the second DRB is set to a value of the RX_NEXT−1.

12 . The terminal of claim 9 ,

wherein, in case that an identity of a third DRB not established for the terminal is included in the first list of the counter check message, the second list includes the identity of the third DRB, and a fourth count value of the terminal associated with the third DRB having MSBs and least significant bits (LSBs), the MSBs being set identical to a corresponding MSBs value of a count value associated with the third DRB which is included in the first list of the counter check message, the LSBs being set to 0, and the fourth count value of the terminal associated with the third DRB including a fourth uplink count value associated with the third DRB and a fourth downlink count value associated with the third DRB.

13 . A base station in a wireless communication system, the base station comprising:

a transceiver; and

a controller configured to:

transmit, via the transceiver to a terminal, a counter check message including a first list for at least one data radio bearer (DRB), the first list including an identity of a first DRB established for the terminal and a most significant bits (MSBs) value of a first count value associated with the first DRB, wherein the MSBs value of the first count value includes a MSBs value of a first uplink count value and a MSBs value of a first downlink count value, and

receive, via the transceiver from the terminal as a response to the counter check message, a counter check response message including a second list,

wherein in case that, for at least one direction of uplink or downlink, a MSBs value of a second count value of the terminal associated with the first DRB is different from the MSBs value of the first count value associated with the first DRB in the first list, the second list includes the identity of the first DRB, a second uplink count value of the terminal associated with the first DRB, and a second downlink count value of the terminal associated with the first DRB,

wherein the second uplink count value of the terminal associated with the first DRB indicates a value of TX_NEXT−1 and the second downlink count value of the terminal associated with the first DRB indicates a value of RX_NEXT−1, and

wherein the TX_NEXT is a count value of a next packet data convergence protocol (PDCP) service data unit (SDU) to be transmitted and the RX_NEXT is a count value of a next PDCP SDU expected to be received.

14 . The base station of claim 13 ,

wherein, in case that the first DRB is a uni-directional bearer configured for one direction of uplink or downlink and no count value exists for the other direction, a count value for the other direction is identified to be 0.

15 . The base station of claim 13 ,

wherein, in case that an identity of a second DRB established for the terminal is not included in the first list of the counter check message, the second list includes the identity of the second DRB, a third uplink count value of the terminal associated with the second DRB, and a third downlink count value of the terminal associated with the second DRB, and

wherein the third uplink count value of the terminal associated with the second DRB is set to a value of the TX_NEXT−1 and the third downlink count value of the terminal associated with the second DRB is set to a value of the RX_NEXT−1.

16 . The base station of claim 13 ,

wherein, in case that an identity of a third DRB not established for the terminal is included in the first list of the counter check message, the second list includes the identity of the third DRB, and a fourth count value of the terminal associated with the third DRB having MSBs and least significant bits (LSBs), the MSBs being set identical to a corresponding MSBs value of a count value associated with the third DRB which is included in the first list of the counter check message, the LSBs being set to 0, and the fourth count value of the terminal associated with the third DRB including a fourth uplink count value associated with the third DRB and a fourth downlink count value associated with the third DRB.

17 . The method of claim 1 , wherein the MSBs value of the second count value of the terminal includes a MSBs value of a second uplink count value of the terminal and a MSBs value of a second downlink count value of the terminal.

18 . The method of claim 5 , wherein the MSBs value of the second count value of the terminal includes a MSBs value of a second uplink count value of the terminal and a MSBs value of a second downlink count value of the terminal.

19 . The terminal of claim 9 , wherein the MSBs value of the second count value of the terminal includes a MSBs value of a second uplink count value of the terminal and a MSBs value of a second downlink count value of the terminal.

20 . The base station of claim 13 , wherein the MSBs value of the second count value of the terminal includes a MSBs value of a second uplink count value of the terminal and a MSBs value of a second downlink count value of the terminal.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 25, 2024
From: KIM, DONGGUN; KIM, SOENGHUN
To: SAMSUNG ELECTRONICS CO., LTD.
Reel/Frame 066892/0107 →
Priority Claims (2)
KR 10-2018-0112498 · Sep 19, 2018 · national
KR 10-2018-0127036 · Oct 23, 2018 · national
Continuity (4)
Continuation 17341176 · Jun 7, 2021
Continuation 16946446 · Jun 22, 2020
Continuation 16576605 · Sep 19, 2019
Related Publication 20240259796A1 · Aug 1, 2024
References Cited (49)
US 10432291B2 · Agiwal et al. · 2019 [cited by applicant]
US 10694377B2 · Kim et al. · 2020 [cited by applicant]
US 11032702B2 · Kim et al. · 2021 [cited by applicant]
US 20130259003A1 · Kwon et al. · 2013 [cited by applicant]
US 20150133135A1 · Zhang et al. · 2015 [cited by applicant]
US 20150341786A1 · Wang et al. · 2015 [cited by applicant]
US 20150350962A1 · Futaki et al. · 2015 [cited by applicant]
US 20160080339A1 · Zhang · 2016 [cited by examiner]
US 20160269945A1 · Jang et al. · 2016 [cited by applicant]
US 20160380779A1 · Sharma · 2016 [cited by examiner]
US 20170034756A1 · Faccin et al. · 2017 [cited by applicant]
US 20170367139A1 · Jang et al. · 2017 [cited by applicant]
US 20180083688A1 · Agiwal et al. · 2018 [cited by applicant]
US 20180098376A1 · Jang et al. · 2018 [cited by applicant]
US 20180199163A1 · Chen et al. · 2018 [cited by applicant]
US 20190053122A1 · Wu · 2019 [cited by applicant]
US 20190059124A1 · Wu · 2019 [cited by applicant]
US 20190149365A1 · Chatterjee et al. · 2019 [cited by applicant]
US 20190174466A1 · Zhang et al. · 2019 [cited by applicant]
US 20190191474A1 · Jin · 2019 [cited by examiner]
US 20190199503A1 · Son · 2019 [cited by applicant]
US 20190281587A1 · Zhang · 2019 [cited by examiner]
US 20200163130A1 · Hori et al. · 2020 [cited by applicant]
US 20210021437A1 · Qiao et al. · 2021 [cited by applicant]
US 20210328894A1 · Pelletier et al. · 2021 [cited by applicant]
CN 105979601A · 2016 [cited by applicant]
CN 107667559A · 2018 [cited by applicant]
CN 107926001A · 2018 [cited by applicant]
EP 3068182A1 · 2016 [cited by applicant]
EP 3182758A1 · 2017 [cited by applicant]
KR 1020120067937A · 2012 [cited by applicant]
KR 1020180035809A · 2018 [cited by applicant]
Decision of Patent dated May 27, 2024, in connection with Korean Application No. 10-2018-0127036, 4 pages. [cited by applicant]
Communication pursuant to Article 94(3) EPC dated Jul. 8, 2024, in connection with European Application No. 19862775.4, 8 pages. [cited by applicant]
Huawei, et al., “Counter check in LTE-NR DC,” R2-1707419, 3GPP TSG-RAN WG2 Meeting Ad hoc, Qingdao, China, Jun. 27-29, 2017, 2 pages. [cited by applicant]
ISA/KR, International Search Report and Written Opinion of the International Searching Authority, International Application No. PCT/KR2019/012173, Dec. 27, 2019, 8 pages. [cited by applicant]
3GPP TS 33.401 V15.4.0 (Jun. 2018) Technical Specification, 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3GPP System Architecture Evolution (SAE); Security architecture … [cited by applicant]
European Search Report issued Jul. 6, 2021, in connection with a counterpart European Patent Application No. 19862775.4, 11 pages. [cited by applicant]
Huawei et al., “Counter check in LTE-NR DC,” R2-1709438, 3GPP TSG-RAN WG2 Meeting #99, Berlin, Germany, Aug. 21-25, 2017, 2 pages. [cited by applicant]
Samsung Electronics, “Introduction of Counter Check Procedure,” R2-1812760,3GPP TSG-RAN WG2#103, Gothenburg, Sweden, Aug. 20-24, 2018, 4 pages. [cited by applicant]
3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Packet Data Convergence Protocol (PDCP) specification (Release 15) 3GPP TS 36.… [cited by applicant]
Samsung, “Introduction of increased number of E-UTRAN data bearers,” R2-1813090,3GPP TSG-RAN WG2#103, Gothenburg, Sweden, Aug. 20-24, 2018, 68 pages. [cited by applicant]
Office Action dated Jan. 12, 2023 in connection with Indian Patent Application No. 202137008345, 6 pages. [cited by applicant]
Communication pursuant to Article 94(3) EPC dated Apr. 24, 2023, in connection with European Patent Application No. 19862775.4, 6 pages. [cited by applicant]
Office Action dated Sep. 18, 2023, in connection with Korean Patent Application No. 10-2018-0127036, 9 pages. [cited by applicant]
Huawei et al., “Counter check in LTE-NR DC,” R2-1709438, 3GPP TSG-RAN WG2 Meeting #99, Berlin, Germany, Aug. 2017, 2 pages. [cited by applicant]
3GPP TS 38.323 V15.2.0 (Jun. 2018); Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Packet Data Convergence Protocol (PDCP) specification; (Release 15… [cited by applicant]
Notice of Allowance dated Jan. 4, 2024, in connection with Chinese Patent Application No. 201980061583.X, 7 pages. [cited by applicant]
Hearing Notice dated Jul. 17, 2025, in connection with Indian Application No. 202137008345, 2 pages. [cited by applicant]