IP Library Granted Patent US 12,192,764
Granted Patent B2
US 12,192,764 · App. 17/198,740 · Granted Jan 7, 2025

Methods, systems, and computer readable media for delegated authorization at security edge protection proxy (SEPP)

Inventors: Jay Rajput (Bangalore, IN); Virendra Singh (Bangalore, IN); Ankit Srivastava (Uttar Pradesh, IN)
Assignee: ORACLE INTERNATIONAL CORPORATION
H04W12/084H04L63/0281H04L67/56H04W8/18H04W84/042
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,192,764
App. No.
17/198,740
Granted
Jan 7, 2025
Kind
B2
Abstract

A method for delegated authorization at a security edge protection proxy (SEPP) includes intercepting, from a consumer network function (NF) that does not support access token based authorization, a service based interface (SBI) service request for accessing a service provided by a producer NF that requires access token based authorization. The method further includes operating as an access token authorization client to obtain a first access token on behalf of the consumer NF. The method further includes using the first access token to enable the consumer NF to access the service provided by the first producer NF. The SEPP may also operate as an access token authorization server on behalf of an NRF that does not support access-token-based authorization.

Claims (57)

1. A method for delegated authorization at a security edge protection proxy (SEPP), the method comprising:

at a SEPP including at least one processor and a memory:

intercepting, by the SEPP and from a first consumer network function (NF) separate from the SEPP and that does not support access-token-based authorization, a first service based interface (SBI) service request lacking an access token and for accessing a service provided by a first 5G producer NF that requires access-token-based authorization;

operating, by the SEPP, as an access token authorization client proxy to obtain a first access token on behalf of the first consumer NF, wherein operating as the access token authorization client proxy includes signaling, by the SEPP and with an NF repository function (NRF) that operates as an access token authorization server, to obtain the first access token from the NRF, wherein the NRF is a 5G NRF separate from the SEPP that stores NF profiles of producer NFs registered with the NRF and signaling with the NRF to obtain the first access token includes:

generating, by the SEPP, an access token request on behalf of the first consumer NF;

transmitting the access token request from the SEPP to the 5G NRF that is separate from the SEPP; and

receiving, by the SEPP and from the 5G NRF that is separate from the SEPP and upon successful validation of the access token request by the 5G NRF, an access token response including the first access token; and

using the first access token to enable the first consumer NF to access the service provided by the first producer NF, wherein using the first access token to access the service provided by the first producer NF includes inserting, the first access token in the first SBI request and forwarding, by the SEPP, the first SBI request to the first producer NF.

2. The method of claim 1 wherein generating the access token request includes extracting values for at least some attributes to be included in the access token request from a user agent header of the first SBI service request.

3. The method of claim 2 wherein extracting values for at least some of the attributes includes extracting an NF instance ID of the first consumer NF from the user agent header of the first SBI service request.

4. The method of claim 1 wherein using the first access token to enable the first consumer NF to access the service provided by the first producer NF includes:

receiving, by the SEPP, an SBI service response from the first producer NF; and

forwarding, by the SEPP, the SBI service response to the first consumer NF.

5. The method of claim 1 comprising:

receiving, by the SEPP and from a second consumer NF separate from the SEPP, an access token request;

operating, by the SEPP, as an access token authorization server proxy on behalf of an NRF that does not support access token authorization in response to the access token request from the second consumer NF; and

signaling, by the SEPP and with the second consumer NF and a second producer NF to enable the second consumer NF to access a service provided by the second producer NF.

6. The method of claim 5 wherein operating as an access token authorization server proxy comprises:

generating, by the SEPP and in response to the access token request, a second access token; and

transmitting, by the SEPP and to the second consumer NF, an access token response including the second access token.

7. The method of claim 6 wherein signaling, by the SEPP and with the second producer NF to enable the second consumer NF to access the service provided by the second producer NF includes:

receiving, by the SEPP and from the second consumer NF, a second SBI service request including the second access token;

removing, by the SEPP, the second access token from the second SBI service request;

forwarding, by the SEPP, the second SBI service request to the second producer NF;

receiving, by the SEPP, an SBI service response from the second producer NF; and

forwarding, by the SEPP, the SBI service response to the second consumer NF.

8. The method of claim 6 wherein generating the second access token includes generating an OAuth 2.0 access token comprising a dummy access token with syntactically correct claims.

9. A system for delegated authorization at a security edge protection proxy (SEPP), the system comprising:

a SEPP including at least one processor and a memory; and

an access token authorization client proxy implemented by the at least one processor for intercepting, from a first consumer network function (NF) separate from the SEPP and that does not support access-token-based authorization, a first service based interface (SBI) service request lacking an access token and for accessing a service provided by a first producer NF that requires access-token-based authorization, obtaining the first access token on behalf of the first consumer NF, and using the first access token to enable the first consumer NF to access the service provided by the first producer NF, wherein obtaining the first access token on behalf of the first consumer NF includes signaling with an NF repository function (NRF) that operates as an access token authorization server, to obtain the first access token from the NRF, wherein the NRF is a 5G NRF separate from the SEPP that stores NF profiles of producer NFs registered with the NRF and signaling with the NRF to obtain the first access token includes:

forwarding request to additional separate NRF, If required, for validation;

generating an access token request on behalf of the first consumer NF;

transmitting the access token request to the NRF; and

receiving, from the NRF, an access token response including the first access token and the access token authorization client proxy is further configured for using the first access token to access the service provided by the first producer NF by inserting, the first access token in the first SBI request and forwarding, the first SBI request to the first producer NF.

10. The system of claim 9 wherein the access token authorization client proxy is configured to generate the access token request by extracting values for at least some attributes to be included in the access token request from a user agent header of the first SBI service request.

11. The system of claim 10 wherein the values extracted by the access token authorization client proxy include an NF instance ID of the first consumer NF from the user agent header of the first SBI service request.

12. The system of claim 9 wherein the access token authorization client proxy is configured to use the first access token to enable the first consumer NF to access the service by:

receiving an SBI service response from the first producer NF; and

forwarding the SBI service response to the first consumer NF.

13. The system of claim 9 comprising an access token authorization server proxy executable by the at least one processor for receiving, from a second consumer NF separate from the SEPP, an access token request; operating as an access token authorization server on behalf of an NRF that does not support access token authorization in response to the access token request from the second consumer NF; and signaling with the second consumer NF and a second producer NF to enable the second consumer NF to access a service provided by the second producer NF.

14. The system of claim 13 wherein, in operating as the access token authorization server, the access token authorization server proxy is configured to:

generate, in response to the access token request, a second access token; and

transmit, to the second consumer NF, an access token response including the second access token.

15. The system of claim 13 wherein the access token authorization server proxy is configured to signal with the second consumer NF and the second producer NF to enable the second consumer NF to access the service provided by the second producer NF by:

receiving, from the second consumer NF, a second SBI service request including the second access token;

removing the second access token from the second SBI service request;

forwarding the SBI service request to the second producer NF;

receiving an SBI service response from the second producer NF; and

forwarding the SBI service response to the second consumer NF.

16. A non-transitory computer readable medium having stored thereon executable instructions that when executed by a processor of a computer controls the computer to perform steps comprising:

intercepting, by a security edge protection proxy (SEPP) and from a consumer network function (NF) separate from the SEPP and that does not support access token based authorization, a service based interface (SBI) service request lacking an access token and for accessing a service provided by a producer NF that requires access token based authorization;

operating, by the SEPP, as an access token authorization client proxy to obtain a first access token on behalf of the consumer NF, wherein operating as the access token authorization client proxy includes signaling, by the SEPP and with an NF repository function (NRF) that operates as an access token authorization server, to obtain the first access token from the NRF, wherein the NRF is a 5G NRF separate from the SEPP that stores NF profiles of producer NFs registered with the NRF and signaling with the NRF to obtain the first access token includes:

forwarding request to additional separate NRF, if required, for validation;

generating, by the SEPP, an access token request on behalf of the first consumer NF;

transmitting the access token request from the SEPP to the NRF; and

receiving, by the SEPP and from the NRF, an access token response including the first access token; and

using the first access token to enable the consumer NF to access the service provided by the producer NF, wherein using the first access token to access the service provided by the first producer NF includes inserting, by the SEPP, the first access token in the first SBI request and forwarding, by the SEPP, the first SBI request to the first producer NF.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 15, 2021
From: RAJPUT, JAY; SINGH, VIRENDRA; SRIVASTAVA, ANKIT
To: ORACLE INTERNATIONAL CORPORATION
Reel/Frame 055587/0375 →
Continuity (1)
Related Publication 20220295282A1 · Sep 15, 2022
References Cited (25)
US 7512973B1 · Chan · 2009 [cited by examiner]
US 11032270B1 · Tsarfati · 2021 [cited by examiner]
US 11641356B2 · Fujii · 2023 [cited by examiner]
US 11811747B2 · Singh et al. · 2023 [cited by applicant]
US 20200127994A1 · Kukreja · 2020 [cited by examiner]
US 20210297942A1 · S Bykampadi et al. · 2021 [cited by applicant]
US 20220086734A1 · Aggarwal et al. · 2022 [cited by applicant]
US 20220201487A1 · Minokuchi et al. · 2022 [cited by applicant]
US 20220294775A1 · Singh et al. · 2022 [cited by applicant]
EP 3955515A1 · 2022 [cited by applicant]
WO WO2020208913A1 · 2020 [cited by applicant]
WO WO2020221956A1 · 2020 [cited by applicant]
WO WO2022191932A1 · 2022 [cited by applicant]
Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration for International Application No. PCT/US2022/014087 (Apr. 14, 2022). [cited by applicant]
Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration for International Application No. PCT/US2022/014084 (Apr. 14, 2022). [cited by applicant]
Nokia et al., “Re-using of access token in indirect communication with delegated discovery,” 3GPP TSG-SA3 Meeting#101-e, pp. 1-4 (Nov. 9, 2020 to Nov. 20, 2020). [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; 5G System; Technical Realization of Service Based Architecture; Stage 3 (Release 17),” 3GPP TS 29.500, V17.1.0, pp. 1-90 (De… [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Security architecture and procedures for 5G system (Release 17),” 3GPP TS 33.501, V17.0.0, pp. 1-253 (Dec. 2020). [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; 5G System; Network Function Repository Services; Stage 3 (Release 17),” 3GPP TS 29.510, V17.0.0, pp. 1-229 (Dec. 2020). [cited by applicant]
Fielding et al., “Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content,” Internet Engineering Task Force (IETF), RFC 7231, pp. 1-102 (Jun. 2014). [cited by applicant]
Hardt, “The OAuth 2.0 Authorization Framework,” Internet Engineering Task Force (IETF), RFC 6749, pp. 1-77 (Oct. 2012). [cited by applicant]
Commonly-Assigned, Co-pending U.S. Appl. No. 17/198,815 for “Methods, Systems, and Computer Readable Media for Delegated Authorization at Service Communications Proxy (SCP),” (Unpublished, filed Mar. 11, 2021). [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; System architecture for the 5G System (5GS); Stage 2 (Release 16),” 3GPP TS 23.501, V16.7.0, pp. 1-450 (Dec. 2020). [cited by applicant]
Notice of Allowance and Fee(s) Due/Examiner Initiated Interview Summary for U.S. Appl. No. 17/198,815 (Jul. 10, 2023). [cited by applicant]
Non-Final Office Action for U.S. Appl. No. 17/198,815 (Mar. 16, 2023). [cited by applicant]
Cited By (1)
US 12,483,890