Granted Patent B2

US 12,562,986 · App. 17/824,313 · Granted Feb 24, 2026

Inventor: Rajiv Krishan (Bangalore, IN)

Assignee: ORACLE INTERNATIONAL CORPORATION

H04L45/745H04L45/26H04L61/4511H04L69/22

Abstract

Claims (42)

1 . A method for optimized multi-domain service communication proxy (SCP) routing, the method comprising:

receiving, at a first SCP, a service based interface (SBI) request for requesting service provided by a producer network function (NF);

performing, by the first SCP, a reverse lookup to determine producer NF identification information;

modifying the SBI request to include the producer NF identification information;

determining an SCP domain of the producer NF;

routing the SBI request to a second SCP in a path for reaching the SCP domain of the producer NF; and

at the second SCP, receiving the SBI request including the producer NF identification information, determining that IP endpoint or fully qualified domain (FQDN) information in a 3gpp-Sbi-Target-apiRoot header of the SBI request matches IP endpoint or FQDN information in an NF profile or NF service profile of the producer NF obtained or located using the producer NF identification information and routing the SBI request without performing the reverse lookup.

2 . The method of claim 1 wherein performing the reverse lookup includes reading an FQDN of the producer NF from a 3gpp-Sbi-Target-apiRoot header of the SBI request, using the FQDN of the producer NF to locate an NF profile or an NF service profile of the producer NF, and obtaining the producer NF identification information from the NF profile or the NF service profile.

3 . The method of claim 2 wherein performing the reverse lookup includes using a service name and version from a path header of the SBI request to locate the NF profile or the NF service profile.

4 . The method of claim 2 wherein obtaining the producer NF identification information from the NF profile or the NF service profile includes obtaining an NF instance identifier of the producer NF from the NF profile and a service instance identifier of the producer NF from the NF profile or the NF service profile and wherein modifying the SBI request to include the producer NF identification information includes modifying the SBI request to include the NF instance identifier and the service instance identifier of the producer NF.

5 . The method of claim 1 wherein performing the reverse lookup includes performing the reverse lookup in a producer profile database local to the first SCP.

6 . The method of claim 5 comprising, in response to failing to locate the NF profile or the NF service profile in the producer profile database local to the first SCP, obtaining the NF or service profile from an NF repository function (NRF) using an NF discovery service operation.

7 . The method of claim 1 wherein modifying the SBI request to include the producer NF identification information includes creating at least one custom header including the producer NF identification information and adding the at least one custom header to the SBI request.

8 . The method of claim 1 wherein determining a domain of the producer NF includes reading an SCP domain identifier from an scpDomains attribute of an NF profile of the producer NF and wherein routing the SBI request includes obtaining a list of domains for reaching the SCP domain of the producer NF and identifying the second SCP as a next-hop SCP from the list.

9 . A system for optimized multi-domain service communication proxy (SCP) routing, the system comprising:

a first SCP including at least one processor and a memory;

an optimized multi-domain SCP router implemented by the at least one processor for receiving, at a first SCP, a service based interface (SBI) request for requesting service provided by a producer network function (NF), performing a reverse lookup to determine producer NF identification information, modifying the SBI request to include the producer NF identification information, determining an SCP domain of the producer NF, and routing the SBI request to or towards a domain of the producer NF; and

a second SCP for receiving the SBI request including the producer NF identification information, determining that IP endpoint or fully qualified domain (FQDN) information in a 3gpp-Sbi-Target-apiRoot header of the SBI request does not match IP endpoint or FQDN information in an NF or service profile obtained or located using the producer NF identification information of the producer NF and, in response, performing the reverse lookup.

10 . The system of claim 9 wherein, in performing the reverse lookup, the optimized multi-domain SCP router is configured to read an FQDN of the producer NF from a 3gpp-Sbi-Target-apiRoot header of the SBI request, use the FQDN of the producer NF to locate an NF profile or an NF service profile of the producer NF, and obtain the producer NF identification information from the NF profile or the NF service profile.

11 . The method of claim 10 wherein, in performing the reverse lookup, he optimized multi-domain SCP router is configured to use a service name and version from a path header of the SBI request.

12 . The system of claim 10 wherein, in obtaining the producer NF identification information from the NF profile or the NF service profile, the optimized multi-domain SCP router is configured to obtain an NF instance identifier of the producer NF from the NF profile and a service instance identifier of the producer NF from the NF profile or the NF service profile, and, in modifying the SBI request to include the producer NF identification information, the optimized multi-domain SCP router is configured to modify the SBI request to include the NF instance identifier and the service instance identifier of the producer NF.

13 . The system of claim 9 wherein the optimized multi-domain SCP router is configured to perform the reverse lookup in producer profile database local to the first SCP or obtain the profile or the NF service profile using an NF discovery service operation.

14 . The system of claim 9 wherein, in modifying the SBI request to include the producer NF identification information, the optimized multi-domain SCP router is configured to create at least one custom header including the producer NF identification information and add the at least one custom header to the SBI request.

15 . The system of claim 9 wherein, in determining a domain of the producer NF, the optimized multi-domain SCP router is configured to read an SCP domain identifier from an scpDomains attribute of an NF profile of the producer NF and, in routing the SBI request, the optimized multi-domain SCP router is configured to obtain a list of domains for reaching the SCP domain of the producer NF and identify a second SCP as a next-hop SCP from the list.

16 . A method for optimized multi-domain service communication proxy (SCP) routing, the method comprising:

receiving, at a first SCP, a service based interface (SBI) request for requesting service provided by a producer network function (NF);

performing, by the first SCP, a reverse lookup to determine producer NF identification information;

modifying the SBI request to include the producer NF identification information;

determining an SCP domain of the producer NF;

routing the SBI request to a second SCP in a path for reaching the SCP domain of the producer NF; and

at the second SCP, receiving the SBI request including the producer NF identification information, determining that IP endpoint or fully qualified domain (FQDN) information in a 3gpp-Sbi-Target-apiRoot header of the SBI request does not match IP endpoint or FQDN information in an NF or service profile obtained or located using the producer NF identification information of the producer NF and, in response, performing the reverse lookup.

17 . A system for optimized multi-domain service communication proxy (SCP) routing, the system comprising:

a first SCP including at least one processor and a memory;

an optimized multi-domain SCP router implemented by the at least one processor for receiving, at a first SCP, a service based interface (SBI) request for requesting service provided by a producer network function (NF), performing a reverse lookup to determine producer NF identification information, modifying the SBI request to include the producer NF identification information, determining an SCP domain of the producer NF, and routing the SBI request to or towards a domain of the producer NF; and

a second SCP for receiving the SBI request including the producer NF identification information, determining that IP endpoint or fully qualified domain (FQDN) information in a 3gpp-Sbi-Target-apiRoot header of the SBI request does not match IP endpoint or FQDN information in an NF or service profile obtained or located using the producer NF identification information of the producer NF and, in response, performing the reverse lookup.

18 . One or more non-transitory computer readable media having stored thereon executable instructions that when executed by one or more processors of one or more computers control the one or more computers to perform steps comprising:

receiving, at a first service communication proxy (SCP), a service based interface (SBI) request for requesting service provided by a producer network function (NF);

performing, by the first SCP, a reverse lookup to determine producer NF identification information;

modifying the SBI request to include the producer NF identification information;

determining an SCP domain of the producer NF;

routing the SBI request to a second SCP in a path for reaching the SCP domain of the producer NF; and

at the second SCP, receiving the SBI request including the producer NF identification information, determining that IP endpoint or fully qualified domain FQDN) information in a 3gpp-Sbi-Target-apiRoot header of the SBI request matches IP endpoint or FQDN information in an NF profile or NF service profile of the producer NF obtained or located using the producer NF identification information and routing the SBI request without performing the reverse lookup.

Assignments (1)

Continuity (1)

References Cited (35)