# US 12,225,493 B2 · Methods, systems, and computer readable media for providing service-based interface (SBI) support for network functions (NFs) not supporting SBI service operations > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 12,225,493 B2 - Document ID: US12225493B2 - Status: Granted - Kind: B2 - Application number: 17/219,366 - Filed: 2021-03-31 - Published: 2022-10-06 - Granted: 2025-02-11 - Earliest claimed: 2021-03-31 - Assignees: Oracle International Corporation - Applicants: Oracle International Corporation - Inventors: Ankit Srivastava; Avinash Jha; Anup Shivarajapura; Venkatesh Aravamudhan - Web page: https://patentgrep.com/patent/US12225493B2 ## CPC - H04L 41/0226: Mapping or translating multiple network management protocols - H04W 60/04: using triggered events - H04L 67/10: in which an application is distributed across nodes in the network (software deployment G06F8/60; multiprogramming arrangements G06F9/46) - H04L 67/2866: Architectures; Arrangements - H04L 67/30: Profiles - H04L 67/535: {Tracking the activity of the user (network monitoring arrangements H04L43/00; recording of computer activity G06F11/34)} - H04L 67/55: Push-based network services - H04L 69/40: for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection (management of faults, events, alarms or notifications in data switching networks H04L41/06) - H04W 4/20: Services signaling; Auxiliary data signalling, i.e. transmitting data via a non-traffic channel - H04W 8/005: {Discovery of network devices, e.g. terminals} - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) - H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72) ## Abstract A method for providing service based interface (SBI) support for network elements (NEs) not supporting SBI service operations includes receiving SBI configuration parameters for an NE not supporting SBI service operations. The method further includes establishing a connection with the NE not supporting SBI service operations. The method further includes registering, with a network function (NF) repository function (NRF) and using the SBI configuration parameters, the NE not supporting SBI service operations. The method further includes monitoring, over the connection, status of the NE not supporting SBI service operations. The method further includes updating, with the NRF, the status of the NE not supporting SBI service operations. ## Claims ### Claim 1 A method for providing service based interface (SBI) support for network elements (NEs) not supporting SBI service operations, the method comprising: receiving SBI configuration parameters for an NE not supporting SBI service operations; establishing a connection with the NE not supporting SBI service operations; registering, with a network function (NF) repository function (NRF) and using the SBI configuration parameters, the NE not supporting SBI service operations, wherein registering the NE not supporting SBI service operations includes performing an NFRegister service operation with the NRF on behalf of the NE not supporting SBI service operations; monitoring, over the connection, status of the NE not supporting SBI service operations; and updating, with the NRF, the status of the NE not supporting SBI service operations. ### Claim 2 (depends on 1) The method of claim 1 wherein receiving SBI configuration parameters includes receiving NF profile parameters for creating an NF profile for the NE not supporting SBI service operations. ### Claim 3 (depends on 1) The method of claim 1 wherein performing the NFRegister service operation includes transmitting, to the NRF, a hypertext transfer protocol (HTTP) PUT message including an NF profile for the NE not supporting SBI service operations. ### Claim 4 (depends on 1) The method of claim 1 wherein establishing a connection with the NE not supporting SBI service operations includes establishing a transport layer connection between an interworking function (IWF) and the NE not supporting SBI service operations. ### Claim 5 (depends on 4) The method of claim 4 wherein monitoring the status of the NE not supporting SBI service operations includes exchanging, by the IWF and over the connection, Diameter watchdog messages with the NE not supporting SBI service operations. ### Claim 6 (depends on 1) The method of claim 1 wherein updating, with the NRF, the status of the NE not supporting SBI service operations with the NRF includes performing an NF Heart-Beat service operation with the NRF on behalf of the NE not supporting SBI service operations. ### Claim 7 (depends on 6) The method of claim 6 wherein monitoring the status of the NE not supporting SBI service operations includes detecting, using a native protocol of the NE not supporting SBI service operations, that the NE not supporting SBI service operations is available, and wherein performing the NF Heart-Beat service operation includes sending a hypertext transfer protocol (HTTP) PATCH message to the NRF within a heart-beat interval and indicating a replace operation on an nfStatus attribute of an NF profile of the NE not supporting SBI service operations and a value of the nfStatus attribute as REGISTERED. ### Claim 8 (depends on 1) The method of claim 1 wherein updating, with the NRF, the status of the NE not supporting SBI service operations includes performing an NFUpdate service operation with the NRF on behalf of the NE not supporting SBI service operations. ### Claim 9 (depends on 8) The method of claim 8 wherein monitoring the status of the NE not supporting SBI service operations includes detecting unreachability of the NE not supporting SBI service operations using a native protocol of the NE not supporting SBI service operations and wherein performing the NFUpdate service operation on behalf of the NE not supporting SBI service operations includes sending a hypertext transfer protocol (HTTP) PATCH message to the NRF indicating a replace operation on an nfStatus attribute of an NF profile of the NE not supporting SBI service operations and a value of the nfStatus attribute as UNDISCOVERABLE. ### Claim 10 A system for providing service based interface (SBI) support for network elements (NEs) not supporting SBI service operations, the system comprising: a cloud native core console (CNCC) for receiving SBI configuration parameters for an NE not supporting SBI service operations and registering, with a network function (NF) repository function (NRF) and using the SBI configuration parameters, the NE not supporting SBI service operations, wherein the CNCC is configured to register the NE not supporting SBI service operations by performing an NFRegister service operation with the NRF on behalf of the NE not supporting SBI service operations; an interworking function (IWF) for establishing a connection with the NE not supporting SBI service operations and monitoring, over the connection, status of the NE not supporting SBI service operations; and wherein the CNCC is configured to update, with the NRF and based on the status monitored by the IWF, the status of the NE not supporting SBI service operations. ### Claim 11 (depends on 10) The system of claim 10 wherein the CNCC is configured to receive NF profile parameters for creating an NF profile for the NE not supporting SBI service operations. ### Claim 12 (depends on 10) The system of claim 10 wherein the CNCC is configured to perform the NFRegister service operation by transmitting, to the NRF, a hypertext transfer protocol (HTTP) PUT message including an NF profile for the NE not supporting SBI service operations. ### Claim 13 (depends on 10) The system of claim 10 wherein the connection with the NE not supporting SBI service operations comprises a transport layer connection. ### Claim 14 (depends on 13) The system of claim 13 wherein the IWF is configured to monitor the status of the NE not supporting SBI service operations by exchanging, over the connection, Diameter watchdog messages with the NE not supporting SBI service operations. ### Claim 15 (depends on 10) The system of claim 10 wherein the CNCC is configured to update, with the NRF, the status of the NE not supporting SBI service operations with the NRF by performing an NF Heart-Beat service operation with the NRF on behalf of the NE not supporting SBI service operations. ### Claim 16 (depends on 15) The system of claim 15 wherein the IWF is configured to monitor the status of the NE not supporting SBI service operations by detecting, using a native protocol of the NE not supporting SBI service operations, that the NE not supporting SBI service operations is available, and wherein the CNCC is configured to perform the NF Heart-Beat service operation by sending a hypertext transfer protocol (HTTP) PATCH message to the NRF within a heart-beat interval and indicating a replace operation on an nfStatus attribute of an NF profile of the NE not supporting SBI service operations and a value of the nfStatus attribute as REGISTERED. ### Claim 17 (depends on 10) The system of claim 10 wherein the IWF is configured to monitor the status of the NE not supporting SBI service operations by detecting unreachability of the NE not supporting SBI service operations using a native protocol of the NE not supporting SBI service operations and wherein the CNCC is configured to update the status of the NE not supporting SBI service operations by performing an NFUpdate service operation on behalf of the NE not supporting SBI service operations including sending a hypertext transfer protocol (HTTP) PATCH message to the NRF indicating a replace operation on an nfStatus attribute of an NF profile of the NE not supporting SBI service operations and a value of the nfStatus attribute as UNDISCOVERABLE. ### Claim 18 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 service based interface (SBI) configuration parameters for a network element (NE) not supporting SBI service operations; establishing a connection with the NE not supporting SBI service operations; registering, with a network function (NF) repository function (NRF) and using the SBI configuration parameters, the NE not supporting SBI service operations, wherein registering the NE not supporting SBI service operations includes performing an NFRegister service operation with the NRF on behalf of the NE not supporting SBI service operations; monitoring, over the connection, status of the NE not supporting SBI service operations; and updating, with the NRF, the status of the NE not supporting SBI service operations.