IP Library › Granted Patent US 12,245,056
Granted Patent B2
US 12,245,056 · App. 17/706,557 · Granted Mar 4, 2025

Methods, systems, and computer readable media for supporting circuit breaker design pattern at consumer network function (NF)

Inventors: Jay Rajput (Bangalore, IN); Virendra Singh (Bangalore, IN); Ankit Srivastava (Uttar Pradesh, IN)
Assignee: ORACLE INTERNATIONAL CORPORATION
H04W24/04H04L45/22H04L67/02H04L67/56
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,245,056
App. No.
17/706,557
Granted
Mar 4, 2025
Kind
B2
Abstract

A method for error information propagation from an SCP to a NF to support a circuit breaker design at the consumer NF includes receiving, at the SCP and from the consumer NF, a first SBI service request message. The method further includes attempting, by the SCP, to forward the first SBI service request to N producer NF instances. The method further includes detecting, by the SCP, an error involving the N producer NF instances. The method further includes performing, by the SCP, successful alternate routing of the first SBI service request message to an (N+1) th producer NF instance. The method further includes receiving, by the SCP, a success response message from the (N+1) th producer NF instance. The method further includes propagating, by the SCP, with the success response message and to the consumer NF, error information regarding the N producer NF instances.

Claims (34)

1. A method for error information propagation from a service communication proxy (SCP) to a consumer network function (NF) to support a circuit breaker design at the consumer NF, the method comprising:

receiving, at the SCP and from the consumer NF, a first service based interface (SBI) service request message;

attempting, by the SCP, to forward the first SBI service request to N producer NF instances, N being an integer of at least one;

detecting, by the SCP, an error involving the N producer NF instances;

performing, by the SCP, successful alternate routing of the first SBI service request message to an (N+1) th producer NF instance;

receiving, by the SCP, a success response message from the (N+1) th producer NF instance; and

propagating, by the SCP, with the success response message and to the consumer NF, error information regarding the N producer NF instances.

2. The method of claim 1 , wherein the first SBI service request comprises a subsequent SBI request including a 3gpp-Sbi-Target-apiRoot header identifying one of the N producer NF instances and a routing binding indication identifying an NF set of which the N and (N+1) th producer NF instances are members.

3. The method of claim 2 , wherein performing alternate routing of the first SBI request includes selecting the (N+1) th producer NF instance from the NF set.

4. The method of claim 1 , wherein detecting an error involving the N producer NF instances includes receiving an error response from at least one of the N producer NF instances.

5. The method of claim 1 , wherein detecting an error regarding the N producer NF instances includes detecting a response timeout at the SCP for at least one of the N producer NF instances.

6. The method of claim 1 , wherein propagating the error information with the success response message includes adding a custom header including the error information to the success response message.

7. The method of claim 1 , wherein the error information includes information identifying each of the N producer NF instances.

8. The method of claim 1 , wherein the error information includes a hypertext transfer protocol (HTTP) status code generated by at least one of the N producer NF instances and transmitted to the SCP in response to the first SBI request message.

9. The method of claim 1 , comprising using, by the consumer NF, the error information to implement the circuit breaker design pattern.

10. The method of claim 9 , wherein using the error information to implement the circuit breaker design pattern includes selecting, in a manner that excludes each of the N producer NF instances, the (N+1) th producer NF instance as a target for a second SBI service request, generating the second SBI service request including a 3gpp-Sbi-Target-apiRoot header identifying the (N+1) th producer NF instance, and transmitting the second SBI service request to the SCP.

11. A system for error information propagation from a service communication proxy (SCP) to a consumer network function (NF) to support a circuit breaker design at the consumer NF, the system comprising:

an SCP including at least one processor; and

an error detector/propagator implemented by the at least one processor for receiving, from the consumer NF, a first service based interface (SBI) service request message, attempting, by the SCP, to forward the first SBI service request to N producer NF instances, N being an integer at least one, detecting an error involving the N producer NF instances, performing successful alternate routing of the first SBI service request message to an (N+1) th producer NF instance, receiving a success response message from the (N+1) th producer NF instance, and propagating, with the success response message and to the consumer NF, error information regarding the N producer NF instances.

12. The system of claim 11 , wherein the first SBI service request comprises a subsequent SBI request including a 3gpp-Sbi-Target-apiRoot header identifying one of the N producer NF instances and a routing binding indication identifying an NF set of which the N and (N+1) th producer NF instances are members.

13. The system of claim 12 , wherein the error detector/propagator is configured to perform alternate routing of the first SBI request by selecting the (N+1) th producer NF instance from the NF set.

14. The system of claim 11 , wherein the error detector/propagator is configured to detect the error involving the N producer NF instances by receiving an error response from at least one of the N producer NF instances.

15. The system of claim 11 , wherein the error detector/propagator is configured to detect the error involving the N producer NF instances by detecting a response timeout at the SCP for at least one of the N producer NF instances.

16. The system of claim 11 , wherein the error detector/propagator is configured to propagate the error information with the success response message by adding a custom header including the error information to the success response message.

17. The system of claim 11 , wherein the error information includes information identifying each of the N producer NF instances.

18. The system of claim 11 , wherein the error information includes a hypertext transfer protocol (HTTP) status code generated by at least one of the N producer NF instances and transmitted to the SCP in response to the first SBI request message.

19. The system of claim 11 , wherein the error information is usable by the consumer NF to implement the circuit breaker design pattern.

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

receiving, at a service communication proxy (SCP) and from a consumer network function (NF), a first service based interface (SBI) service request message;

attempting, by the SCP, to forward the first SBI service request to N producer NF instances, N being an integer of at least one;

detecting, by the SCP, an error involving the N producer NF instances;

performing, by the SCP, successful alternate routing of the first SBI service request message to an (N+1) th producer NF instance;

receiving, by the SCP, a success response message from the (N+1) th producer NF instance; and

propagating, by the SCP, with the success response message and to the consumer NF, error information regarding the N producer NF instances.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 29, 2022
From: RAJPUT, JAY; SINGH, VIRENDRA; SRIVASTAVA, ANKIT
To: ORACLE INTERNATIONAL CORPORATION
Reel/Frame 059422/0805 →
Continuity (1)
Related Publication 20230308908A1 · Sep 28, 2023
References Cited (31)
US 10764214B1 · Plenderleith · 2020 [cited by examiner]
US 11290549B2 · Krishan · 2022 [cited by applicant]
US 11831732B2 · Singh · 2023 [cited by examiner]
US 20210092005A1 · Kaul · 2021 [cited by examiner]
US 20210306203A1 · Landais · 2021 [cited by examiner]
US 20220224589A1 · Das · 2022 [cited by examiner]
US 20220224760A1 · Foti et al. · 2022 [cited by applicant]
US 20220330085A1 · Li · 2022 [cited by examiner]
US 20220345379A1 · Li · 2022 [cited by examiner]
US 20220393971A1 · Bartolome Rodrigo · 2022 [cited by examiner]
US 20230147549A1 · Singh et al. · 2023 [cited by applicant]
US 20230291818A1 · Yang · 2023 [cited by examiner]
CN 115243278A · 2022 [cited by examiner]
Notice of Allowance and Fees Due for U.S. Appl. No. 17/524,711 (Aug. 24, 2023). [cited by applicant]
Non-Final Office Action for U.S. Appl. No. 17/524,711 (Apr. 19, 2023). [cited by applicant]
Non-Final Office Action for U.S. Appl. No. 17/524,711 (Oct. 5, 2022). [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.3.0, pp. 1-258 (Sep. 2021). [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.3.0, pp. 1-271 (Sep. 2021). [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; 5G System; Principles and Guidelines for Services Definition; Stage 3 (Release 17),” 3GPP TS 29.501, V17.3.1, pp. 1-78 (Sep.… [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; System architecture for the 5G System (5GS); Stage 2 (Release 17),” 3GPP TS 23.501, V17.2.0, pp. 1-542 (Sep. 2021). [cited by applicant]
“Circuit Breaker Pattern,” Azure Architecture Center, Microsoft Docs, pp. 1-14 (Mar. 9, 2022). [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; System architecture for the 5G System (5GS); Stage 2 (Release 17),” 3GPP TS 23.501, V17.3.0, pp. 1-559 (Dec. 2021). [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Procedures for the 5G System (5GS); Stage 2 (Release 17),” 3GPP TS 23.502, V17.2.1, pp. 1-712 (Sep. 2021). [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.4.0, pp. 1-109 (S… [cited by applicant]
Nygard, “Circuit Breaker,” Release It!, 2nd Edition, pp. 1-3 (Jan. 30, 2018). [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Security architecture and procedures for 5G system (Release 18)”, 3GPP TS 33.501, V18.5.0, pp. 1-330 (Mar. 2024). [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 18)”, 3GPP TS 29.500, V18.5.0, pp. 1-150 (M… [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; 5G System; Network Function Repository Services; Stage 3 (Release 18)”, 3GPP TS 29.510, V18.5.0, pp. 1-382 (Dec. 2023). [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; System architecture for the 5G System (5GS); Stage 2 (Release 18)”, 3GPP TS 23.501, V18.4.0, pp. 1-706 (Dec. 2023). [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; 5G System; Unified Data Management Services; Stage 3 (Release 18)”, 3GPP TS 29.503, V18.4.0, pp. 1-660 (Dec. 2023). [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; 5G System; Network Function Repository Services; Stage 3 (Release 18)”, 3GPP TS 29.510, V18.4.0, pp. 1-399 (Sep. 2023). [cited by applicant]