IP Library › Granted Patent US 12,225,119
Granted Patent B2
US 12,225,119 · App. 17/011,698 · Granted Feb 11, 2025

Information sending method, key generation method, and apparatus

Inventors: He Li (Shanghai, CN); Jing Chen (Shanghai, CN)
Assignee: HUAWEI TECHNOLOGIES CO., LTD.
H04L9/0866H04L9/0819H04L9/088H04L9/3242
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,225,119
App. No.
17/011,698
Granted
Feb 11, 2025
Kind
B2
Abstract

An information sending method, a key generation method, and an apparatus, where a core network element first determines whether a terminal device needs to perform a key activation procedure, and then sends a first message to an access network element, where the first message indicates whether the access network element needs to send, to the terminal device, a second message to trigger the terminal device to perform the key activation procedure. After receiving the first message, the access network element determines, based on the first message, whether the second message needs to be sent to the terminal device, and sends the second message to the terminal device when the second message needs to be sent to the terminal device.

Claims (51)

1. An information sending method comprising:

sending, by an access network element and to an access and management function network element, a request message that comprises an explicit indication indicating whether an access stratum (AS) security mode command (SMC) procedure needs to be triggered;

receiving, by the access and management function network element, the request message;

determining, by the access and management function network element based on the explicit indication carried in the request message and based on a terminal device type of a terminal device, whether the AS SMC procedure is to be performed by:

determining that the AS SMC procedure needs to be performed when the terminal device type is an enhanced mobile broadband (eMBB) type; and

determining that the AS SMC procedure does not need to be performed when the terminal device type is one of a massive machine type of communication (mMTC) type or an ultra-reliable low latency communication (URLLC) type;

sending, by the access and management function network element and when the AS SMC procedure is to be performed, an initial context setup request message to the access network element, wherein the initial context setup request message carries a necessary parameter for performing the AS SMC procedure;

receiving, by the access network element, the necessary parameter from the access and management function network element; and

sending, by the access network element based on the necessary parameter from the access and management function network element, an AS SMC message to a terminal.

2. The information sending method of claim 1 , wherein the necessary parameter comprises a security context.

3. The information sending method of claim 1 , wherein the necessary parameter is a root key (KgNB).

4. The information sending method of claim 1 , wherein the necessary parameter triggers the AS SMC procedure.

5. An information sending method implemented by an access and management function network element, wherein the information sending method comprises:

receiving a request message from an access network element, wherein the request message comprises an explicit indication indicating whether an access stratum (AS) security mode command (SMC) procedure needs to be triggered;

determining, based on the explicit indication carried in the request message and based on a terminal device type of a terminal device, whether the AS SMC procedure is to be performed by:

determining that the AS SMC procedure needs to be performed when the terminal device type is an enhanced mobile broadband (eMBB) type; and

determining that the AS SMC procedure does not need to be performed when the terminal device type is one of a massive machine type of communication (mMTC) type or an ultra-reliable low latency communication (URLLC) type; and

sending, to the access network element and when the AS SMC procedure is to be performed, an initial context setup request message that carries a necessary parameter for performing the AS SMC procedure.

6. The information sending method of claim 5 , wherein the necessary parameter comprises a security context.

7. The information sending method of claim 5 , wherein the necessary parameter is a root key (KgNB).

8. The information sending method of claim 5 , wherein the necessary parameter triggers the AS SMC procedure.

9. An access and management function network element comprising: a communications interface; and

a processor coupled to the communications interface and configured to:

receive, using the communications interface, a request message from an access network element, wherein the request message comprises an explicit indication indicating whether an access stratum (AS) security mode command (SMC) procedure needs to be triggered;

determine, based on the explicit indication carried in the request message and based on a terminal device type of a terminal device, whether the AS SMC procedure is to be triggered by:

determining that the AS SMC procedure needs to be performed when the terminal device type is an enhanced mobile broadband (eMBB) type; and

determining that the AS SMC procedure does not need to be performed when the terminal device type is one of a massive machine type of communication (mMTC) type or an ultra-reliable low latency communication (URLLC) type; and

send, using the communications interface, to the access network element and when the AS SMC procedure is to be performed, an initial context setup request message, wherein the initial context setup request message carries a necessary parameter for performing the AS SMC procedure.

10. The access and management function network element of claim 9 , wherein the necessary parameter comprises a security context.

11. The access and management function network element of claim 9 , wherein the necessary parameter is a root key (KgNB).

12. A communication system comprising an access network element and an access and management function network element, wherein:

the access network element is configured to:

send, to the access and management function, a request message that comprises an explicit indication indicating whether an access stratum (AS) security mode command (SMC) procedure needs to be triggered;

the access and management function network element is configured to:

receive the request message;

determine, based on the explicit indication carried in the request message and based on a terminal device type of a terminal device, whether the AS SMC procedure is to be performed by:

determining that the AS SMC procedure needs to be performed when the terminal device type is an enhanced mobile broadband (eMBB) type; and

determining that the AS SMC procedure does not need to be performed when the terminal device type is one of a massive machine type of communication (mMTC) type or an ultra-reliable low latency communication (URLLC) type;

send, when the AS SMC procedure is to be performed, an initial context setup request message to the access network element, wherein the initial context setup request message carries a necessary parameter for performing the AS SMC procedure;

the access network element is further configured to:

receive the necessary parameter from the access and management function network element; and

send, based on the necessary parameter from the access and management function network element, an AS SMC message to a terminal.

13. The communication system of claim 12 , wherein the necessary parameter comprises at least one of a security context, a root key (KgNB), or the necessary parameter triggers the AS SMC procedure.

14. The information sending method of claim 1 , further comprising obtaining, by the access and management function network element, information related to the terminal device from one of a session management function (SMF) entity or a unified data management (UDM) entity, wherein determining based on the terminal device type of the terminal device, whether the AS SMC procedure needs to be performed, comprises determining, based on the request message and the information related to the terminal device, whether the AS SMC procedure needs to be performed.

15. The information sending method of claim 1 , further comprising determining, by the access and management function network element, the type of the terminal device based on at least one of a field in the request message, subscription information of the terminal device in a unified data management (UDM) entity, or location information of the terminal device sent by a policy control function (PCF) entity.

16. The information sending method of claim 1 , wherein determining whether the AS SMC procedure is to be performed comprises determining, by the access and management function network element, that bit information of the explicit indication matches a condition for the AS SMC procedure to be performed.

17. The information sending method of claim 1 , wherein the explicit indication indicates one of: the AS SMC procedure needs to be triggered, the AS SMC procedure is recommended to be triggered, or the AS SMC procedure does not need to be triggered.

18. The information sending method of claim 5 , further comprising obtaining, by the access and management function network element, information related to the terminal device from one of a session management function (SMF) entity or a unified data management (UDM) entity, wherein determining based on the terminal device type of the terminal device, whether the AS SMC procedure needs to be performed, comprises determining, based on the request message and the information related to the terminal device, whether the AS SMC procedure needs to be performed.

19. The information sending method of claim 5 , further comprising determining, by the access and management function network element, the type of the terminal device based on at least one of a field in the request message, subscription information of the terminal device in a unified data management (UDM) entity, or location information of the terminal device sent by a policy control function (PCF) entity.

20. The information sending method of claim 5 , wherein determining whether the AS SMC procedure is to be performed comprises determining, by the access and management function network element, that bit information of the explicit indication matches a condition for the AS SMC procedure to be performed.

21. The information sending method of claim 5 , wherein the explicit indication indicates one of: the AS SMC procedure needs to be triggered, the AS SMC procedure is recommended to be triggered, or the AS SMC procedure does not need to be triggered.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 16, 2024
From: LI, HE; CHEN, JING
To: HUAWEI TECHNOLOGIES CO., LTD.
Reel/Frame 069599/0544 →
Priority Claims (1)
CN 201810308232.1 · Apr 8, 2018 · national
Continuity (2)
Continuation PCTCN2019080159 · Mar 28, 2019
Related Publication 20200403788A1 · Dec 24, 2020
References Cited (39)
US 10531292B2 · Ben Henda · 2020 [cited by examiner]
US 10728757B2 · Wu · 2020 [cited by examiner]
US 11032701B2 · Yilmaz · 2021 [cited by examiner]
US 11770467B2 · Dai · 2023 [cited by examiner]
US 20100115275A1 · Suh · 2010 [cited by examiner]
US 20110136473A1 · Gupta et al. · 2011 [cited by applicant]
US 20110161661A1 · Medvinsky et al. · 2011 [cited by applicant]
US 20130007434A1 · King et al. · 2013 [cited by applicant]
US 20180041926A1 · Zhang · 2018 [cited by examiner]
US 20180083972A1 · Kim · 2018 [cited by examiner]
US 20190082325A1 · Muhanna · 2019 [cited by examiner]
US 20190253888A1 · Jerichow · 2019 [cited by examiner]
US 20190281029A1 · Zhang · 2019 [cited by examiner]
US 20200120501A1 · Ben Henda · 2020 [cited by examiner]
US 20220116843A1 · Velev · 2022 [cited by examiner]
CN 101505479A · 2009 [cited by applicant]
CN 101835156A · 2010 [cited by examiner]
CN 102843651A · 2012 [cited by applicant]
CN 102932784A · 2013 [cited by applicant]
CN 103813308A · 2014 [cited by applicant]
CN 105532026A · 2016 [cited by applicant]
CN 107005927A · 2017 [cited by applicant]
CN 107276971A · 2017 [cited by applicant]
EP 3582531A1 · 2019 [cited by examiner]
JP 2011530839A · 2011 [cited by applicant]
WO 0042491A1 · 2000 [cited by applicant]
WO 2010052920A1 · 2010 [cited by applicant]
WO 2013183971A1 · 2013 [cited by applicant]
Akshatha, N., et al., “A Centralized SDN Architecture for the 5G Cellular Network,” 2018 IEEE 5G World Forum (5GWF), Nov. 1, 2018, 6 pages. [cited by applicant]
Rapporteur (Nokia), “Security Update,” 3GPP TSG-RAN WG2 Meeting #101bis, Sanya, China, Apr. 16-20, 2018, R2-1804909, 6 pages. [cited by applicant]
3GPP TS 38.410 V0.8.0, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NG-RAN; NG general aspect and principles (Release 15),” Mar. 2018, 13 pages. [cited by applicant]
3GPP TS 23.501 V15.1.0, “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; System Architecture for the 5G System; Stage 2 (Release 15),” Mar. 2018, 201 pages. [cited by applicant]
3GPP TS 23.502 V15.1.0, “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Procedures for the 5G System; Stage 2 (Release 15),” Mar. 2018, 285 pages. [cited by applicant]
3GPP TS 33.501 V15.0.0, “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Security architecture and procedures for 5G system (Release 15),” Mar. 2018, 128 pages. [cited by applicant]
3GPP TS 38.413 V0.7.0, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NG-RAN; NG Application Protocol (NGAP) (Release 15),” Mar. 2018, 121 pages. [cited by applicant]
Nokia, et al, “Clause 6.4.2.2 Multiple active NAS connections in the same PLMN,” 3GPP TSG SA WG3 (Security) Meeting #90, S3-180400, Jan. 22-26, 2018, Gothenburg, Sweden, 2 pages. [cited by applicant]
Huawei, et al,“The value Unique NAS connection identifier,” 3GPP TSG SA WG3 (Security) Meeting #90BIS, S3-180646, Feb. 26-Mar. 2, 2018, San Diego, US, 1 pages. [cited by applicant]
Huawei, et al, “The value Unique NAS connection identifier”, 3GPP TSG SA WG3 (Security) Meeting #90BIS, 83-180881, Feb. 26-Mar. 2, 2018, San Diego, US, 1 pages. [cited by applicant]
Nokia, Motorola Mobility, Lenovo, Clean up of ENs in Clause 7.2.1 Authentication for Untrusted non-3GPP Access , 3GPP TSG SA WG3 (Security) Meeting #90Bis S3-180940, [online], Mar. 2, 2018, total 6 pages. [cited by applicant]