IP Library › Granted Patent US 12,568,366
Granted Patent B2
US 12,568,366 · App. 18/056,650 · Granted Mar 3, 2026

Method and wireless network for application-specific authorization for network services in wireless network

Inventors: Rajavelsamy Rajadurai (Bangalore, IN); Nivedya Parambath Sasi (Bangalore, IN); Rohini Rajendran (Bangalore, IN)
Assignee: Samsung Electronics Co., Ltd.
H04W12/06H04W12/043
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,568,366
App. No.
18/056,650
Granted
Mar 3, 2026
Kind
B2
Abstract

The disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. Accordingly, embodiments herein disclose a method performed by an application function (AF) server, the method comprises receiving, from a terminal, a first request message including an user equipment (UE) service identifier (ID), transmitting, to an authorization server, a second request message for request association information of the terminal, the second request message including a terminal ID, receiving, from the authorization server, the association information of the terminal, in case that the association information is retrieved based on the terminal ID and performing to verify whether the UE service ID is associated with the terminal ID in the association information of the terminal.

Claims (53)

1 . A method performed by a message service within a 5 th generation system (MSGin5G) server, the method comprises:

receiving, from a terminal, a registration request message including a terminal service identifier (ID);

receiving, from an authentication and key management for applications (AKMA) anchor function (AAnF) entity, a terminal ID that is used for retrieving association information of the terminal;

retrieving, from a configuration management server or an MSGin5G configuration function, the association information of the terminal based on the received terminal ID; and

verifying whether the terminal service ID included in the registration request message is associated with the terminal ID included in the retrieved association information.

2 . The method of claim 1 , further comprises comprising:

providing, to the terminal, an access for a service based on a result of the verification.

3 . The method of claim 1 , wherein the association information of the terminal is retrieved based on the terminal ID received from the AAnF entity.

4 . The method of claim 1 , wherein verifying comprises:

verifying whether the terminal service ID included in the registration request message is associated with the terminal ID included in the retrieved association information.

5 . The method of claim 1 , wherein the terminal ID comprises a subscription permanent identifier (SUPI) or a generic public subscription identifier (GPSI).

6 . The method of claim 1 , further comprising performing an authorization operation for the terminal by retrieving an association between the terminal service ID and the terminal ID, wherein the terminal is an MSGin5G terminal.

7 . The method of claim 1 , wherein an association between the terminal service ID and the terminal ID is maintained by the configuration management server or the MSGin5G configuration function.

8 . A message service within a 5 th generation system (MSGin5G) server, the MSGin5G server comprises:

a transceiver; and

at least one processor operably coupled to the transceiver, the at least one processor configured to:

receive, from a terminal via the transceiver, a registration request message including a terminal service identifier (ID),

receive, from an authentication and key management for applications (AKMA) anchor function (AAnF) entity via the transceiver, a terminal ID that is used for retrieving obtaining association information of the terminal,

retrieve, from a configuration management server or an MSGin5G configuration function via the transceiver, the association information of the terminal based on the received terminal ID, and

verify whether the terminal service ID included in the registration request message is associated with the terminal ID included in the retrieved association information.

9 . The MSGin5G server of claim 8 , wherein the at least one processor is further configured to:

provide, to the terminal, an access for a service based on a result of the verification.

10 . The MSGin5G server of claim 8 , wherein the association information of the terminal is retrieved based on the terminal ID received from the AAnF entity.

11 . The MSGin5G server of claim 8 , wherein the at least one processor is further configured to:

verify whether the terminal service ID included in the registration request message is associated with the terminal ID included in the retrieved association information.

12 . The MSGin5G server of claim 8 , wherein the terminal ID comprises a subscription permanent identifier (SUPI) or a generic public subscription identifier (GPSI).

13 . The MSGin5G server of claim 8 , wherein the at least one processor is further configured to perform an authorization operation for the terminal by retrieving an association between the terminal service ID and the terminal ID, and

wherein the terminal is an MSGin5G terminal.

14 . The MSGin5G server of claim 8 , wherein an association between the terminal service ID and the terminal ID is maintained by the configuration management server or the MSGin5G configuration function.

15 . A method performed by a terminal, the method comprises:

transmitting, to a message service within a 5 th generation system (MSGin5G) server, a registration request message including a terminal service identifier (ID); and

receiving, from the MSGin5G server, a response message including information indicating whether an access to a service is provided,

wherein a terminal ID is transmitted from an authentication and key management for applications (AKMA) anchor function (AAnF) entity to the MSGin5G server, and the terminal ID is used for retrieving association information of the terminal,

wherein the association information of the terminal is retrieved from a configuration management server or an MSGin 5 G configuration function based on the terminal ID, and

wherein whether the terminal service ID included in the registration request message is associated with the terminal ID included in the retrieved association information is verified.

16 . The method of claim 15 , wherein the access to the service is provided based on a result of the verification,

wherein the association information of the terminal is retrieved based on the terminal ID received from the AAnF entity,

wherein whether the terminal service ID included in the registration request message is associated with the terminal ID included in the retrieved association information is verified, and

wherein the terminal ID comprises a subscription permanent identifier (SUPI) or a generic public subscription identifier (GPSI).

17 . The method of claim 15 , wherein an association between the terminal service ID and the terminal ID is maintained by the configuration management server or the MSGin5G configuration function.

18 . A terminal, the terminal comprises:

a transceiver; and

at least one processor operably coupled to the transceiver, the at least one processor configured to:

transmit, to a message service within a 5 th generation system (MSGin5G) an server via the transceiver, a registration request message including a terminal service identifier (ID); and

receive, from the MSGin5G server via the transceiver, a response message including information indicating whether an access to a service is provided,

wherein a terminal ID is transmitted from an authentication and key management for applications (AKMA) anchor function (AAnF) entity to the MSGin5G server, the terminal ID being used for retrieving association information of the terminal,

wherein the association information of the terminal is retrieved from a configuration management server or an MSGin 5 G configuration function based on the terminal ID, and

wherein whether the terminal service ID included in the registration request message is associated with the terminal ID included in the retrieved association information is verified.

19 . The terminal of claim 18 , wherein the access to the service is provided based on a result of the verification,

wherein the association information of the terminal is retrieved based on the terminal ID received from the AAnF entity,

wherein whether the terminal service ID included in the registration request message is associated with the terminal ID included in the retrieved association information is verified, and

wherein the terminal ID comprises a subscription permanent identifier (SUPI) or a generic public subscription identifier (GPSI).

20 . The terminal of claim 18 , wherein an association between the terminal service ID and the terminal ID is maintained by the configuration management server or the MSGin5G configuration function.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 17, 2022
From: RAJADURAI, RAJAVELSAMY; SASI, NIVEDYA PARAMBATH; RAJENDRAN, ROHINI
To: SAMSUNG ELECTRONICS CO., LTD
Reel/Frame 061817/0063 →
Priority Claims (2)
IN 202141053378 · Nov 19, 2021 · national
IN 202141053378 · Oct 28, 2022 · national
Continuity (1)
Related Publication 20230164553A1 · May 25, 2023
References Cited (47)
US 10306432B2 · Suh · 2019 [cited by examiner]
US 20110256850A1 · Selander · 2011 [cited by examiner]
US 20140141763A1 · Suh · 2014 [cited by examiner]
US 20150133124A1 · Lim · 2015 [cited by examiner]
US 20190116179A1 · Xu · 2019 [cited by examiner]
US 20190274086A1 · Cui · 2019 [cited by examiner]
US 20200359218A1 · Lee · 2020 [cited by examiner]
US 20210274345A1 · Wang · 2021 [cited by examiner]
US 20220109964A1 · Pattan et al. · 2022 [cited by applicant]
US 20230037031A1 · Wang · 2023 [cited by examiner]
US 20230164553A1 · Rajadurai · 2023 [cited by examiner]
US 20230354013A1 · Li · 2023 [cited by examiner]
US 20240064510A1 · Karakoc · 2024 [cited by examiner]
US 20240098500A1 · Pateromichelakis · 2024 [cited by examiner]
US 20240276217A1 · Wang · 2024 [cited by examiner]
US 20240298176A1 · Divvi · 2024 [cited by examiner]
US 20240349049A1 · Huang · 2024 [cited by applicant]
US 20240356742A1 · Tsiatsis · 2024 [cited by examiner]
CN 113225176A · 2021 [cited by examiner]
CN 114071510B · 2025 [cited by examiner]
JP 2024530949A · 2024 [cited by applicant]
WO 2020226454A1 · 2020 [cited by applicant]
WO 2021138309A1 · 2021 [cited by applicant]
WO 2023016420A1 · 2023 [cited by applicant]
3GPP TR 33.839, 3rd Generation Partnership Project (Year: 2021). [cited by examiner]
NPL Search History (Year: 2024). [cited by examiner]
Khan, Mohsin et al., “AKMA: Delegated Authentication System of 5G”, IEEE Communications Standards Magazine | Sep. 2021, pp. 56-61. (Year: 2021). [cited by examiner]
Nguyen, Van-Linh et al., “Security and privacy for 6G: A survey on prospective technologies and challenges”, arXiv:2108.11861v2 [cs.CR] Sep. 1, 2021, pp. 1-45. (Year: 2021). [cited by examiner]
Khan, Mohsin et al., “Privacy Preserving AKMA in 5G”, SSR'19: Proceedings of the 5th ACM Workshop on Security Standardisation Research Workshop pp. 45-56. (Year: 2019). [cited by examiner]
M. Jones et al., “Internet Engineering Task Force (IETF)—JSON Web Signature (JWS),” ISSN: 2070-1721, RFC 7515, May 2015, 59 pages. [cited by applicant]
M. Jones et al., “Internet Engineering Task Force (IETF)—JSON Web Token (JWT),” ISSN: 2070-1721, RFC 7519, May 2015, 30 pages. [cited by applicant]
J. Richer, “Internet Engineering Task Force (IETF)—OAuth 2.0 Token Introspection,” ISSN: 2070-1721, RFC 7662, Oct. 2015, 17 pages. [cited by applicant]
3GPP TS 23.434 V17.3.0 (Sep. 2021) Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Service Enabler Architecture Layer for Verticals (SEAL); Functio… [cited by applicant]
3GPP TS 33.535 V17.4.0 (Dec. 2021) Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Authentication and Key Management for Applications (AKMA) based … [cited by applicant]
3GPP TS 33.501 V16.9.0 (Dec. 2021); Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Security architecture and procedures for 5G system (Release 16)… [cited by applicant]
International Search Report and Written Opinion of the International Searching Authority dated Feb. 23, 2023, in connection with International Application No. PCT/KR2022/017930, 7 pages. [cited by applicant]
3GPP TR 33.839 V0.8.0 (Oct. 2021) Technical Report; 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on security aspects of enhancement of support for edge computing i… [cited by applicant]
Samsung, “Authentication and Authorization between 5GMSGS Client and MSGin5G server,” 3GPP TSG-SA3 Meeting #101-e, S3-203239, e-meeting, Nov. 9-20, 2020, 3 pages. [cited by applicant]
Samsung, “CR to living document: Authorization of MSG client,” 3GPP TSG-SA3 Meeting #105-e, S3-214220, e-meeting, Nov. 8-19, 2021, 2 pages. [cited by applicant]
Supplementary European Search Report dated Aug. 29, 2024, in connection with European Patent Application No. 22896005.0, 14 pages. [cited by applicant]
Examination report issued Sep. 24, 2024, in connection with Indian Patent Application No. 202141053378, 6 pages. [cited by applicant]
Samsung, “Authentication and authorization for MSGinSG UE,” 3GPP TSG-SA3 Meeting #102-e. e-meeting, Jan. 2021, S3-210579 (Revision of S3-210455), 3 pages. [cited by applicant]
Samsung, “Authentication and Authorization between SGMSGS Client and MSGinSG server,” 3GPP TSG-SA3 Meeting #101-e, e-meeting, Nov. 2020, S3-203365 (Revision of S3-203239), 3 pages. [cited by applicant]
3GPP TS 33.434 V16.2.0 (Mar. 2021), Technical Specification, 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Security aspects of Service Enabler Architecture Layer (SEAL) f… [cited by applicant]
Office Action dated Mar. 25, 2025, in connection with Japanese application No. 2024-524737, 12 pages. [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on security aspects of the message Service for MIoT over the 5G System (MSGin5G)”, 3GPP TR 33.862 V0.7.0, Sep. 2021, … [cited by applicant]
Office Action dated Jul. 11, 2025, in connection with Korean application No. 10-2024-7003986, 6 pages. [cited by applicant]