Method, system, and computer readable medium for providing service based interface (SBI) support for network functions (NFs) that do not support SBI service operation - Patents.com

Abstract

A method for providing Service Based Interface (SBI) support for network elements (NEs) that do not support SBI service operation includes receiving SBI configuration parameters for a NE that does not support SBI service operation. The method further includes establishing a connection with the NE that does not support SBI service operation. The method further includes registering the NE that does not support SBI service operation with a Network Function (NF) Repository Function (NRF) using the SBI configuration parameters. The method further includes monitoring a status of the NE that does not support SBI service operation via the connection. The method further includes updating the status of the NE that does not support SBI service operation with the NRF.

Description

[Technical field]

[0001] Priority claim This application claims the benefit of priority to U.S. Patent Application No. 17 / 219,366, filed March 31, 2021, the disclosure of which is incorporated by reference herein in its entirety.

[0002] Technical Field The subject matter described herein relates to interoperability in communication networks. More specifically, the subject matter described herein relates to a method, a system, and a computer-readable medium for providing SBI support for an NF that does not support SBI service operation. [Background technology]

[0003] background In a 5G telecommunications network, a network function that provides a service is called a producer network function (NF) or an NF service producer. A network function that consumes a service is called a consumer NF or an NF service consumer. A network function can be a producer NF, a consumer NF, or both, depending on whether the network function is consuming, producing, or consuming and producing a service. The terms "producer NF" and "NF service producer" are used interchangeably herein. Similarly, the terms "consumer NF" and "NF service consumer" are used interchangeably herein.

[0004] A given producer NF may have many service endpoints, which are points of contact for one or more NF instances hosted by the producer NF. A service endpoint is identified by a combination of an Internet Protocol (IP) address and port number, or a fully qualified domain name that resolves to an IP address and port number on the network node hosting the producer NF. An NF instance is an instance of a producer NF that provides a service. A given producer NF may include two or more NF instances. Also, note that multiple NF instances can share the same service endpoint.

[0005] Producer NFs register with a Network Function Repository Function (NRF). The NRF maintains service profiles of available NF instances that identify the services supported by each NF instance. The terms "service profile" and "NF profile" are used interchangeably herein. Consumer NFs can subscribe to receive information about producer NF instances that have registered with the NRF.

[0006] In addition to consumer NFs, another type of network node that can be subscribed to receive information about NF service instances is the Service Communication Proxy (SCP). SCPs subscribe with the NRF and obtain reachability and service profile information about producer NF service instances. Consumer NFs connect to the Service Communication Proxy, which load balances traffic between producer NF service instances that provide the requested service or route traffic directly to the destination producer NF instance.

[0007] In addition to the SCP, another example of an intermediate proxy node that routes traffic between producer and consumer NFs is the Security Edge Protection Proxy (SEPP). A SEPP is a network node used to protect the control plane traffic exchanged between different 5G Public Land Mobile Networks (PLMNs). As such, the SEPP performs message filtering, policing and topology hiding for all Application Programming Interface (API) messages sent between PLMNs.

[0008] One problem in 5G communication networks occurs when interacting with network functions that do not support SBI service operations. In 5G networks, the service-based interface is the interface through which 5G network elements, called NFs, communicate with each other. Third Generation Partnership Project (3GPP) standards, such as 3GPP Technical Specification (TS) 29.510, define operations called service operations carried over SBI. Examples of service operations include the NFRegister service, which allows an NF to register its identity with an NF repository function, the NFUpdate operation, which allows an NF to update its status with the NRF, and the NF Heart-Beat operation, which is a subset of the NFUpdate operation and allows an NF to periodically communicate its availability to the NRF. Another NF service operation is the NFDiscover service operation, which allows other NFs to discover the identities and other attributes of NFs registered with the NRF.

[0009] In non-5G networks, there is no concept of registering network elements or network functions with the NRF. However, it may be desirable to interact with non-SBI network elements, such as 4G / 5G equipment identity registers (EIRs), application functions (AFs), or application servers (ASs), that do not support SBI service operation. It may also be necessary to provide updates on the status of such nodes to the 5G NF. However, since non-SBI NEs do not communicate using SBI service operation, there is no capability to inform the 5G NF of the identity or status of non-SBI NEs.

[0010] In light of the above and other drawbacks, a need exists for a method, system, and computer-readable medium for providing SBI support to NEs that do not support SBI service operation. Summary of the Invention

[0011] overview A method is provided for providing Service Based Interface (SBI) support for a network element (NE) that does not support SBI service operation, the method including receiving SBI configuration parameters for the NE that does not support SBI service operation. The method includes establishing a connection with the NE that does not support SBI service operation. The method further includes registering the NE that does not support SBI service operation in a network function (NF) repository function (NRF) using the SBI configuration parameters. The method further includes monitoring a status of the NE that does not support SBI service operation via the connection. The method further includes updating the status of the NE that does not support SBI service operation in the NRF.

[0012] According to another aspect of the subject matter described herein, receiving the SBI configuration parameters includes receiving NF profile parameters for creating an NF profile for a NE that does not support SBI service operation.

[0013] According to another aspect of the subject matter described in this specification, registering a NE that does not support SBI service operation includes performing an NFRegister service operation using an NRF on behalf of the NE that does not support SBI service operation.

[0014] According to another aspect of the subject matter described herein, performing the NFRegister service operation includes sending a HyperText Transfer Protocol (HTTP) PUT message to the NRF including an NF profile for a NE that does not support the SBI service operation.

[0015] According to another aspect of the subject matter described in this specification, establishing a connection with a NE that does not support SBI service operation includes establishing a transport layer connection between an interworking function (IWF) and the NE that does not support SBI service operation.

[0016] According to another aspect of the subject matter described in this specification, monitoring the status of the NE that does not support SBI service operation includes exchanging Diameter watchdog messages with the NE that does not support SBI service operation, by the IWF, over the connection.

[0017] According to another aspect of the subject matter described herein, updating the status of a NE that does not support SBI service operation in the NRF includes performing NF Heart-Beat service operation using the NRF on behalf of the NE that does not support SBI service operation.

[0018] According to another aspect of the subject matter described herein, monitoring the status of the NE that does not support the SBI service operation includes detecting that the NE that does not support the SBI service operation is available using a native protocol of the NE that does not support the SBI service operation, and performing the NF Heart-Beat service operation includes sending a HyperText Transfer Protocol (HTTP) PATCH message to the NRF within the heartbeat interval and indicating a replace operation on an nfStatus attribute of an NF profile of the NE that does not support the SBI service operation and a value of the nfStatus attribute as REGISTERED.

[0019] According to another aspect of the subject matter described in this specification, updating the status of a NE that does not support SBI service operation in the NRF includes performing an NFUpdate service operation using the NRF on behalf of the NE that does not support SBI service operation.

[0020] According to another aspect of the subject matter described herein, monitoring the status of the NE that does not support the SBI service operation includes detecting unreachability of the NE that does not support the SBI service operation using a native protocol of the NE that does not support the SBI service operation, and performing an NFUpdate service operation on behalf of the NE that does not support the SBI service operation 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 that does not support the SBI service operation and a value of the nfStatus attribute as UNDISCOVERABLE.

[0021] According to another aspect of the subject matter described herein, a system for providing Service Based Interface (SBI) support for a network element (NE) that does not support SBI service operation includes a cloud native core console (CNCC) for receiving SBI configuration parameters for the NE that does not support SBI service operation and registering the NE that does not support SBI service operation in a network function (NF) repository function (NRF) using the SBI configuration parameters. The system further includes an interworking function (IWF) for establishing a connection with the NE that does not support SBI service operation and monitoring a status of the NE that does not support SBI service operation via the connection. The CNCC is configured to update a status of the NE that does not support SBI service operation in the NRF based on the status monitored by the IWF.

[0022] According to another aspect of the subject matter described herein, a CNCC is configured to receive NF profile parameters for creating an NF profile for a NE that does not support SBI service operation.

[0023] According to another aspect of the subject matter described in this specification, the CNCC is configured to register an NE that does not support SBI service operation by performing an NFRegister service operation using the NRF on behalf of the NE that does not support SBI service operation.

[0024] According to another aspect of the subject matter described herein, the CNCC is configured to perform an NFRegister service operation by sending, to the NRF, a HyperText Transfer Protocol (HTTP) PUT message including an NF profile for a NE that does not support the SBI service operation.

[0025] According to another aspect of the subject matter described herein, the connection with the NE that does not support SBI service operation includes a transport layer connection.

[0026] According to another aspect of the subject matter described in this specification, the IWF is configured to monitor the status of the NE that does not support SBI service operation by exchanging Diameter watchdog messages with the NE that does not support SBI service operation over the connection.

[0027] According to another aspect of the subject matter described in this specification, the CNCC is configured to update the status of the NE that does not support the SBI service operation in the NRF by performing an NF Heart-Beat service operation using the NRF on behalf of the NE that does not support the SBI service operation.

[0028] According to another aspect of the subject matter described herein, the IWF is configured to monitor the status of the NE that does not support the SBI service operation by detecting that the NE that does not support the SBI service operation is available using a native protocol of the NE, and the CNCC is configured to perform an NF Heart-Beat service operation by sending a HyperText Transfer Protocol (HTTP) PATCH message to the NRF within the heartbeat interval and indicating a REPLACE operation on an nfStatus attribute of an NF profile of the NE that does not support the SBI service operation and a value of the nfStatus attribute as REGISTERED.

[0029] According to another aspect of the subject matter described in this specification, the IWF is configured to monitor the status of the NE that does not support the SBI service operation by detecting unreachability of the NE that does not support the SBI service operation using a native protocol of the NE that does not support the SBI service operation, and the CNCC is configured to update the status of the NE that does not support the SBI service operation by performing an NFUpdate service operation on behalf of the NE that does not support the SBI service operation, the NFUpdate service operation 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 that does not support the SBI service operation and a value of the nfStatus attribute as UNDISCOVERABLE.

[0030] According to another aspect of the subject matter described herein, a non-transitory computer-readable medium having executable instructions stored thereon, the instructions, when executed by a processor of a computer, control the computer to perform steps including receiving Service Based Interface (SBI) configuration parameters for a network element (NE) that does not support SBI service operation. The steps further include establishing a connection with the NE that does not support SBI service operation. The steps further include registering the NE that does not support SBI service operation with a network function (NF) repository function (NRF) using the SBI configuration parameters. The steps further include monitoring, via the connection, a status of the NE that does not support SBI service operation. The steps further include updating the status of the NE that does not support SBI service operation in the NRF.

[0031] The subject matter described herein may be implemented in software in combination with hardware and / or firmware. For example, the subject matter described herein may be implemented in software executed by a processor. In one exemplary embodiment, the subject matter described herein may be implemented using a non-transitory computer-readable medium having computer-executable instructions stored thereon, which, when executed by a processor of a computer, control the computer to perform steps. Exemplary computer-readable media suitable for implementing the subject matter described herein include non-transitory computer-readable media, such as, for example, disk memory devices, chip memory devices, programmable logic devices, and application specific integrated circuits. In addition, computer-readable media implementing the subject matter described herein may be located on a single device or computing platform, or may be distributed across multiple devices or computing platforms. [Brief description of the drawings]

[0032] [Figure 1] FIG. 1 is a network diagram illustrating an example 5G system network architecture. [Figure 2A] A message flow diagram showing example messages exchanged for an NFRegister service operation. [Figure 2B] A message flow diagram showing example messages exchanged for NFUpdate or NF Heart-Beat service operation. [Diagram 3] 1 is a block diagram illustrating example components for providing SBI support for a NE that does not support SBI service operation. [Figure 4] FIG. 1 is a network diagram showing the provision of SBI support for a 4G / 5G EIR that does not support SBI service operation. [Diagram 5]FIG. 1 is a network diagram showing the provision of SBI support for a 4G / 5G AF or AS that does not support SBI service operation. [Figure 6] A message flow diagram showing example messages exchanged when performing NFRegister, NFUpdate, and NF Heart-Beat service operations on behalf of a NE that does not support SBI service operations. [Figure 7] 11 is a flowchart illustrating an example process for providing SBI support for a NE that does not support SBI service operation. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0033] Detailed Description FIG. 1 is a block diagram illustrating an example 5G system network architecture. The architecture of FIG. 1 includes an NRF 100 and an SCP 101, which may be located in the same Home Public Mobile Network (HPLMN). As described above, the NRF 100 may maintain a profile of available producer NF service instances and their supported services, and may enable consumer NFs or SCPs to subscribe to and be notified of new / updated producer NF service instance registrations. The SCP 101 may also support service discovery and selection of producer NF instances. The SCP 101 may perform load balancing of connections between consumer and producer NFs.

[0034] The NRF 100 is a repository for NFs or service profiles of producer NF instances. To communicate with a producer NF instance, a consumer NF or SCP needs to obtain the NF or service profile of the producer NF instance from the NRF 100. The NF or service profile is a JavaScript object notation (JSON) data structure defined in 3GPP TS 29.510. The NF or service profile definition includes at least one of a fully qualified domain name (FQDN), an Internet Protocol (IP) version 4 (IPv4) address, or an IP version 6 (IPv6) address.

[0035] In Figure 1, any of the network functions can be a consumer NF, a producer NF, or both, depending on whether the network function is requesting a service, providing a service, or requesting and providing a service. In the illustrated example, the NFs include a PCF 102 that performs policy-related operations in the network, a User Data Management (UDM) function 104 that manages user data, and an Application Function (AF) 106 that provides application services.

[0036] 1 further includes a Session Management Function (SMF) 108 that manages sessions between an Access and Mobility Management Function (AMF) 110 and the PCF 102. The AMF 110 performs mobility management operations similar to those performed by a Mobility Management Entity (MME) in 4G networks. An Authentication Server Function (AUSF) 112 performs authentication services for user equipment (UE) seeking access to the network, such as user equipment (UE) 114.

[0037] The Network Slice Selection Function (NSSF) 116 provides network slicing services for devices that want to access specific network functions and features associated with a network slice. The Network Exposure Function (NEF) 118 provides an Application Programming Interface (API) for application functions that want to obtain information about Internet of Things (IoT) devices and other UEs attached to the network. The NEF 118 performs a function similar to the Service Capability Exposure Function (SCEF) in 4G networks.

[0038] The Radio Access Network (RAN) 120 connects the User Equipment (UE) 114 to the network via wireless links. The Radio Access Network 120 may be accessed using a g-NodeB (gNB) (not shown in FIG. 1) or other wireless access points. The User Plane Function (UPF) 122 may support various proxy functions for user plane services. One example of such a proxy function is a Multi-Path Transmission Control Protocol (MPTCP) proxy function. The UPF 122 may also support a performance measurement function that may be used by the UE 114 to obtain network performance measurements. Also illustrated in FIG. 1 is a Data Network (DN) 124, through which the UE accesses data network services, such as Internet services.

[0039] The SEPP 126 filters incoming traffic from another PLMN and performs topology hiding for traffic leaving the home PLMN. The SEPP 126 may communicate with a SEPP in a foreign PLMN that manages security for the foreign PLMN. Traffic between NFs in different PLMNs may thereby traverse two SEPP functions, one for the home PLMN and the other for the foreign PLMN.

[0040] As mentioned above, one problem that may arise in a 5G network is that an NF that does not support SBI service operation cannot communicate its identity to the 5G NF and update its status with the 5G NF by communicating with the NRF over the SBI. Examples of non-SBI NEs for which use cases may exist in a 5G network include the EIR, AF, and AS mentioned above, a policy control function (PCF), a home subscriber server (HSS), a home location register (HLR), or other non-SBI network elements that need to interface with an NF in a 5G network.

[0041] An example of an SBI service operation that may be desirable to provide on behalf of a non-SBI NE is the NFRegister service operation. FIG. 2A is a message flow diagram illustrating example messages that may be exchanged when performing the NFRegister service operation. The NFRegister service operation is defined in 3GPP TS 29.510. The NFRegister service operation is used to register an NF with an NRF by providing the NRF with an NF profile of the requesting NF. This NF profile is a data structure that describes the NF, the services offered by the NF, and an identity for communicating with the NF. When an NF successfully invokes the NFRegister service operation, the NRF marks the requesting NF as available to be discovered by other NFs. The NFRegister service operation is also used to register services associated with existing NF instances. The NFRegister service operation is also used to register NRF information and other information, which is used to forward or redirect service discovery requests.

[0042] Referring to the message flow of FIG. 2A, in line 1, a requesting NF service consumer 200 sends an HTTP PUT message to the NRF 100. The HTTP PUT message contains a uniform resource identifier (URI) of a resource representing the NF instance. This URI is determined by the NF instance. The variable "nfInstanceId" represents an identifier provided by the NF service consumer 200 that is globally unique inside the PLMN of the NRF 100 in which the NF is registered. The format of the NF instance ID is a Universal Unique Identifier (UUID) version 4 as described in Internet Engineering Task Force (IETF) Request for Comments (RFC) 4122.

[0043] The payload body of the PUT request contains a representation of the NF instance to be created. In the example of Figure 2A, that representation is specified by an NF profile. An NF profile is a data structure that contains the attributes shown in Table 1 below. TIFF2024512670000002.tif216163

[0044] TIFF2024512670000003.tif238163

[0045] TIFF2024512670000004.tif235163

[0046] TIFF2024512670000005.tif223163

[0047] TIFF2024512670000006.tif230163

[0048] TIFF2024512670000007.tif244163

[0049] TIFF2024512670000008.tif223163

[0050] TIFF2024512670000009.tif255163

[0051] TIFF2024512670000010.tif192163

[0052] TIFF2024512670000011.tif255163

[0053] TIFF2024512670000012.tif250163

[0054] TIFF2024512670000013.tif214163

[0055] TIFF2024512670000014.tif159163

[0056] Table 1: NF profile attributes The NF profile includes attributes that describe the 5G network function that is registered, as shown in Table 1. The 5G network function is configured or programmed to include the NF profile. However, non-SBI NEs do not have an NF profile and therefore cannot register their identity with the NRF 100.

[0057] In line 2a of FIG. 2A, upon successful registration of the NF instance 200, the NRF 100 returns a 201 Created message. The payload body of the 201 Created message contains a representation of the created resource and the location header of the response contains the URI of the created resource. In addition, the NRF 100 returns a heartbeat timer containing the expected number of seconds between two consecutive heartbeat messages from the NF instance 200 to the NRF 100. The representation of the created resource can be a complete NF profile or an NF profile including the mandatory attributes of the NF profile and any attributes that the NRF 100 has added or modified.

[0058] In line 2b, in case of failure or redirection, if the registration of the NF instance 200 fails at the NRF 100 due to an error in the encoding of the NF profile JSON object, the NRF 100 returns a 4xx bad request status code with a problem details element providing error details if the registration of the NF instance fails at the NRF 100 due to an internal error. The NRF 100 returns a 5xx internal server error status code with a problem details element providing error details. In case of redirection, the NRF 100 returns a 3xx status code including a location header with a URI pointing to an endpoint of another NRF service instance.

[0059] Other SBI service operations that may be desirable to perform on behalf of non-SBI NEs include the NFUpdate service operation and the NF Heart-Beat service operation, which is a special type of NFUpdate service operation. Figure 2B is a message flow diagram illustrating example messages exchanged for an NFUpdate service operation. The NFUpdate service operation updates the profile of an NF that was previously registered at the NRF by providing the NRF with the updated NF profile of the requesting NF. The NFUpdate service operation can apply to the entire profile of the NF (complete replacement of the existing profile with a new profile) or can apply to only a subset of the profile's parameters (including adding / removing / replacing services to the NF profile).

[0060] When using the NFUpdate service operation to perform an NF Heart-Beat service operation, a previously registered NF periodically contacts the NRF to indicate that the NF is still operational. The time interval at which the NRF is contacted is deployment specific and is returned by the NRF to the NF service consumer as a result of successful registration. If the NRF detects that a given NF has not updated its profile for a configurable amount of time (longer than the heartbeat interval), the NRF changes the NF's status to SUSPENDED and considers the NF and its services no longer discoverable by other NFs via the NFDiscovery service. The NRF notifies NFs subscribed to receive notification of NF profile changes that the NF status has changed to SUSPENDED.

[0061] If the NRF modifies the heartbeat interval value of a given currently registered NF instance (e.g., as a result of an Operations, Administration and Maintenance (OA&M) action), it shall return the new value to the registered NF in the response of the next periodic heartbeat interaction received from that NF, until which time the NRF shall apply the heartbeat check procedure according to the original interval value.

[0062] As shown by line 1 in Figure 2B, in performing an NFUpdate service operation, the NF service consumer 200 sends an HTTP PATCH request to a resource URI representing an NF instance. If the NFUpdate service operation is being used for an NF Heart-Beat service, the payload body of the PATCH request includes a "replace" operation on the "nfStatus" attribute of the NF profile of the NF instance, and the value of the nfStatus attribute is set to "REGISTERED" or "UNDISCOVERABLE" depending on whether the NF is reachable or not.

[0063] In addition, the NF service consumer 200 may also provide load information of the NF and / or associated NF services. The provision of such load information may be limited by the NF via appropriate configuration (e.g., granularity thresholds) to avoid notification of small load variations.

[0064] 2B, line 2a, upon success, the NRF 100 returns a 204 No Content message. The NRF 100 may also want to reply with a 200 OK message with the full NF profile if the NRF 100 determines that the NF profile has changed significantly, for example since the last heartbeat, and send the new profile to the NF service consumer 200.

[0065] In line 2b of Figure 2B, upon failure or redirection, if the NF instance identified by nfInstanceID is not found in the list of registered NF instances in the NRF's database, the NRF 100 returns a "404 Not Found" status code with a ProblemDetails IE providing details of the error. When a redirection occurs, the NRF 100 returns a 3xx status code that includes a location header with a URI that points to the endpoint of another NRF service instance.

[0066] Because non-SBI NEs do not support the service operations shown in Figures 2A and 2B, the subject matter described herein provides mechanisms for performing those service operations on behalf of non-SBI NEs. Figure 3 illustrates example components of a system for performing SBI service operations, such as the NFRegister, NFUpdate, and NF Heart-Beat service operations described above with respect to Figures 2A and 2B, on behalf of NEs that do not support SBI service operations. With reference to Figure 3, a cloud native core console (CNCC) 300 receives configuration information, which in the illustrated example is an equipment identity register (EIR) or application function (AF), from an operator 302 for a non-SBI NE 304. The CNCC 300 includes an NF management service 306 including an NFRegister module 308 that performs the NFRegister service described above on behalf of the non-SBI NE 304, an NFUpdate module 310 that performs the NFUpdate service operation described above on behalf of the non-SBI NE 304, and an NF Heart-Beat module 312 that performs the NF Heart Beat service operation described above on behalf of the non-SBI NE 304.

[0067] CNCC 300 further includes a CNCC Core 314 that receives non-SBI NE configuration parameters from Operator 302 and stores the non-SBI NE configuration parameters in memory as a non-SBI module 316. The non-SBI NE configuration parameters may be NF profile parameters such as those shown in Table 1, and CNCC 300 may use the received parameters to create an NF profile for the non-SBI NE 304. CNCC 300 further includes a CNCC Identity Access Management (IAM) module 321 that performs authentication and authorization functions of CNCC 300, such as creating and assigning roles to users.

[0068] The system illustrated in Figure 3 further includes a non-SBI NE Interworking Function (IWF) 320 that interfaces directly with non-SBI NEs, such as NE 304, and also communicates with CNCC Core 314. The non-SBI NE IWF 320 includes an auditor 322 that monitors the status of the non-SBI NE 304 and communicates status updates to CNCC Core 314. Modules 308, 310 and 312 may be triggered by status updates to update the NF profile of the non-SBI NE 304 with NRF 100. NRF 100 includes an application programming interface (API) 324 defined in 3GPP TS 29.510, including the messages and parameters described above with respect to Figures 2A and 2B.

[0069] In performing an NFRegister service operation, the NFRegister module 308 receives configuration parameters from the operator 302, creates an NF profile for the non-SBI NE 304, and transmits the NF profile to the NRF 100 using the message flow shown in Figure 2A. In performing an NFUpdate service operation, the NF update module 310 may be triggered by the non-SBI NE IWF 320 receiving or detecting an update in one or more parameters of the NF profile of the non-SBI NE 304, and updates the NF profile using the NFUpdate service operation described above with respect to Figure 2B.

[0070] The NF Heart-Beat module 312 may maintain the status of the non-SBI NE 304 with the NRF 100 using the NF Heart-Beat service operations described above based on the results of the monitoring of the non-SBI NE 304 performed by the auditor 322. In an example where the non-SBI NE 304 implements the Diameter protocol as described in IETF RFC6733, the auditor 322 may use Diameter watchdog message exchange to monitor the status of the non-SBI NE 304. Using the Diameter watchdog procedure, the auditor 322 may send a Diameter watchdog request to the non-SBI NE 304. Upon sending the Diameter watchdog request, the auditor 322 starts a Diameter watchdog timer and waits for a Diameter watchdog response from the non-SBI NE 304. If the auditor 322 receives a Diameter watchdog response from the non-SBI NE 304 before the timer expires, the auditor 322 may reset the Diameter watchdog timer and update the CNCC core 314 indicating that the non-SBI NE 304 is available, and the NF Heart-Beat module 312 may deliver a Heart-Beat status message to the NRF 100 using the NFUpdate service operation. If the auditor 322 does not receive a response to the Diameter watchdog request before the Diameter watchdog timer expires, the auditor 322 may notify the CNCC core 314, which causes the NFUpdate module 310 and / or the NF Heart-Beat module 312 to update the reachability status (indicating UNDISCOVERABLE) of the non-SBI NE 304 with the NRF 100 utilizing the NFUpdate and / or NF Heart-Beat procedures described above.

[0071] 3 may be implemented using at least one processor 326 and memory 328. For example, CNCC 300 and IWF 320 may be implemented using computer-executable instructions stored in memory 328 and executed by processor 326. Also, note that CNCC 300 and IWF 320 may be located on the same or different computing platforms.

[0072] 4 illustrates an example where the 5G AMF 110 needs to communicate with the 4G / 5G EIR 400, for example to verify or obtain the UE's International Mobile Equipment Identification Number (IMEI). The 4G / 5G EIR 400 may communicate with other network elements utilizing a non-SBI interface, such as a Diameter interface. The IWF 320 may communicate with the 4G / 5G EIR 400 using a native non-SBI interface protocol implemented by the 4G / 5G EIR 400, may communicate with the AMF 110 using an SBI protocol, and may communicate with the CNCC 300 using an SBI or proprietary interface protocol. Using Diameter as an example, the IWF 320 may translate between Diameter and HTTP for messaging between the AMF 110 and the 4G / 5G EIR 400.

[0073] In the illustrated example, the operator 302 may create a configuration for 4G / 5G EIR 400 with CNCC 300. In response to receiving the configuration parameters, CNCC 300 may create an NF profile for 4G / 5G EIR 400 and register the NF profile NRF 100. The NF profile may include a suitable subset of all or some of the NF profile attributes illustrated above in Table 1. The IWF 320 may monitor the status of 4G / 5G EIR 400 using a Diameter watchdog or other suitable procedure and notify CNCC 300 of the current status of 4G / 5G EIR 400. Upon receiving notification of the status of 4G / 5G EIR 400, CNCC 300 may update the status of the NF profile for 4G / 5G EIR 400 in NRF 100 using one of the SBI service operations described above. If the AMF 110 is subscribed to receive notifications of changes in the NF profile of the 4G / 5G EIR 400, the NRF 100 notifies the AMF 110 when a change or update to the NF profile occurs.

[0074] FIG. 5 illustrates another use case for CNCC 300 and IWF 320. In FIG. 5, an operator 302 may configure parameters for 4G / 5G AF 500 with CNCC 300. CNCC 300 may create an NF profile for 4G / 5G AF 500 and register the profile in NRF 100. 5G NFs such as AMF 110, PCF 102, SEPP 126, SMF 108, NSSF 116, and AUSF 112 may subscribe with NRF 100 to receive updates regarding the status of AF 500. IWF 320 monitors the status of AF 500 and communicates the status to CNCC 300. IWF 320 may also translate between message formats used in 5G Core with those compatible with AF 500. For example, IWF320 may perform HTTP to Diameter conversion for messages directed to AF500 and Diameter to HTTP conversion for messages directed from AF500 to the 5G core.

[0075] FIG. 6 is a message flow diagram illustrating performing NFRegister, NF Heart-Beat, and NFUpdate service operations on behalf of a non-SBI network element. With reference to FIG. 6, in step 1, a user, such as network operator 302, configures a new consumer (or producer) NF as a non-SBI network element. The parameters entered by network operator 302 may be parameters shown or indicated as mandatory in the above NF profile in Table 1. The following are examples of parameters that may be configured for a non-SBI NE: Parameters: - Name:nfInstanceID Location:Path Condition: True Description: The unique ID of the NF instance to register. Schema: $ref:TS29571_CommonData.yaml# / components / schemas / NfInstanceId' - Name: Content-Encoding Location: Header Description: Content-Encoding as described in IETF RFC7231 Schema: Type: String - Name:Accept-Encoding Location: Header Description: Accept-Encoding as described in IETF RFC 7231 Schema: Type: String requestBody: content: application / json: Schema: $ref:'# / components / schemas / NFProfile' Condition: True In step 2, after receiving the configuration for the non-SBI network element 304, the CNCC 300 notifies the IWF 320 of the newly configured non-SBI network element. The details include information such as an IP address or domain name, enabling the IWF 320 to initiate a connection with the non-SBI network element 304.

[0076] In step 3, the IWF 320 establishes a connection with the non-SBI network element 304. In one example, the connection is a transport layer connection, such as a Transmission Control Protocol (TCP) or Stream Control Transmission Protocol (SCTP) connection. In step 4, the IWF 320 notifies the CNCC 300 that the connection was successfully established.

[0077] In step 5, upon receiving notification from the IWF 320 of successful connection establishment with the non-SBI network element 304, the CNCC 300 executes an NFRegister service operation with the NRF 100 with sufficient details to reach the non-SBI network element 304. Executing the NFRegister procedure may include sending an HTTP PUT message to the NRF 100 with relevant parameters as described above with respect to FIG. 2A. In step 6, the NRF 100 responds indicating whether the registration was successful. This response may be any of the responses described above with respect to FIG. 2A.

[0078] In step 7, the IWF 320 monitors the status of the non-SBI network element 304. Monitoring the status of the non-SBI network element 304 may include exchanging heartbeat messages with the non-SBI network element 304 in the native protocol of the non-SBI network element 304. In one example, the heartbeat message may be a Diameter watchdog message as described above. In another example, if the non-SBI network element 304 implements SS7 or Sigtran messaging, the heartbeat message may be a message transfer part (MTP) level 3 user adaptation layer (M3UA) heartbeat message. If the non-SBI network element 304 implements Session Initiation Protocol (SIP), the heartbeat message may be a SIP heartbeat or equivalent message.

[0079] In step 8, the IWF 320 sends a status message to the CNCC 300 indicating that the non-SBI network element 304 is up or available. In step 9 of the message flow diagram, the CNCC 300 performs an NF Heart-Beat service operation on behalf of the non-SBI network element 304. Performing the NF Heart-Beat service operation may include sending an HTTP PATCH message to the NRF 100 indicating that the non-SBI network element 304 is available, as described above with respect to FIG. 2B. In step 10 of the message flow diagram, the NRF 100 responds to the CNCC 300 indicating whether the NF Heart-Beat service operation was successful or whether the operation failed.

[0080] In step 11 of this message flow diagram, Diameter watchdog messaging between the non-SBI network element 304 and the IWF 320 fails. For example, the non-SBI network element 304 may fail to respond to a Diameter watchdog request message within a timeout period. In response to detecting the Diameter watchdog messaging failure, the IWF 320 in step 12 sends a notification to the CNCC 300 indicating the unavailability of the non-SBI network element 304.

[0081] At line 13 of the message flow diagram, the CNCC 300 performs an NFUpdate service operation on behalf of the non-SBI network element 304 to the NRF 100 indicating that the non-SBI network element 304 is down or paused. In an alternative example, an NF Heart-Beat service operation may be used to indicate that the non-SBI network element 304 is down. At line 14 of the message flow diagram, the NRF 100 responds to the CNCC 300 with a success or failure response depending on whether the service operation was successful.

[0082] 7 is a flow chart illustrating a method for providing service-based interface (SBI) support for NEs that do not support SBI service operation. Referring to FIG. 7, in step 700, the process includes receiving SBI configuration parameters for NEs that do not support SBI service operation. For example, the CNCC 300 may receive the SBI configuration parameters from the operator 302, which may include NF profile parameters for creating an NF profile that enables 5G NFs to discover and subscribe to receive notifications about non-SBI NEs.

[0083] In step 702, the process includes establishing a connection with a NE that does not support SBI service operation. For example, after receiving the configuration parameters, the CNCC 300 may instruct the IWF 320 to create a connection with the non-SBI NE 304. In response to the instruction, the IWF 320 may create a transport layer connection, such as a TCP or SCTP connection, with the non-SBI NE 304.

[0084] In step 704, the process includes registering NEs that do not support SBI service operation with a Network Function (NF) Repository Function (NRF) using the SBI configuration parameters. For example, the CNCC 300 may perform an NFRegister service operation to convey the NF profile of the non-SBI network element 304 to the NRF 100.

[0085] In step 706, the process includes monitoring the status of the NE that does not support SBI service operation over the connection. For example, the IWF 320 may monitor the status of the non-SBI NE 304 using the non-SBI NE 304's native protocol. If the native protocol is Diameter, the IWF 320 may monitor the status of the non-SBI NE 304 using Diameter watchdog messaging. If the native protocol is SS7 over Sigtran, the IWF 320 may monitor the status using M3UA messages. If the native protocol is SIP, the IWF 320 may monitor the status using SIP messages.

[0086] In step 708, the process includes updating the status of the NEs that do not support SBI service operation in the NRF. For example, the CNCC 300 may use NFUpdate or NF Heart Beat service operation to communicate the availability status of the non-SBI NEs 304 to the NRF 100.

[0087] Exemplary advantages of the subject matter described herein include enabling non-SBI NEs to register with the NRF, so that NFs can discover and receive status updates regarding non-SBI NEs. Another advantage to providing a CNCC and IWF to perform SBI service operations on behalf of non-SBI NEs is that each non-SBI NE does not need to be configured to support SBI service operations. The solution thereby provides scalability and configuration efficiency advantages over approaches in which each non-SBI NE is configured to support SBI service operations.

[0088] The disclosure of each of the following references is hereby incorporated by reference in its entirety into this specification.

[0089] References 1. 3 rd 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 (2020-12). twenty three rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Numbering, addressing and identification; (Release 17), 3GPP TS 23.003 V17.0.0 (2020-12). 3.3 rdGeneration Partnership Project; Technical Specification Group Core Network and Terminals; 5G System; Technical Realization of the Service Based Architecture; Stage 3 (Release 17), 3GPP TS 29.500 V17.1.0 (2020-12). 4. 3 rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; 5G System; Restoration Procedures (Release 16), 3GPP TS 23.527 V16.5.0 (2020-12). 5. Fajardo, et al., “Diameter Base Protocol,” IETF RFC 6733 (October 2012); 6. Leach, et. al., “A Universally Unique Identifier (UUID) URN Namespace,” IETF RFC 4122 (July 2005). 7. Bray, T., “The JavaScript Object Notation (JSON) Data Interchange Format,” IETF RFC 8259 (December 2017). 8. Fielding, R. and Reschke, J., “Hypertext Transfer Protocol (HTTP / 1.1: Semantics and Content,” IETF RFC 7321(June 2014). It will be understood that various details of the subject matter described herein can be changed without departing from the scope of the subject matter described herein. Moreover, the above description is intended to be illustrative and not limiting, as the subject matter described herein is defined by the claims set forth below.

Claims

1. A method for providing Service Based Interface (SBI) support for a network element (NE) that does not support SBI service operation, comprising: receiving SBI configuration parameters for an NE that does not support SBI service operation; Establishing a connection with the NE that does not support SBI service operation; registering the NE that does not support SBI service operation with a Network Function (NF) Repository Function (NRF) using the SBI configuration parameters; monitoring, via said connection, a status of said NE that does not support SBI service operation; and updating in the NRF the status of the NE that does not support SBI service operation.

2. The method of claim 1 , wherein receiving SBI configuration parameters includes receiving NF profile parameters for creating an NF profile for the NE that does not support SBI service operation.

3. The method of claim 1 or 2, wherein registering the NE that does not support SBI service operation includes performing an NFRegister service operation with the NRF on behalf of the NE that does not support SBI service operation.

4. 4. The method of claim 3, wherein performing the NFRegister service operation includes sending a HyperText Transfer Protocol (HTTP) PUT message to the NRF including an NF profile for the NE that does not support an SBI service operation.

5. The method according to any one of claims 1 to 4, wherein establishing a connection with the NE that does not support SBI service operation includes establishing a transport layer connection between an interworking function (IWF) and the NE that does not support SBI service operation.

6. The method of claim 5 , wherein monitoring the status of the NE that does not support SBI service operation includes exchanging Diameter watchdog messages with the NE that does not support SBI service operation by the IWF over the connection.

7. The method according to any one of claims 1 to 6, wherein updating the status of the NE that does not support SBI service operation using the NRF in the NRF includes performing NF Heart-Beat service operation using the NRF on behalf of the NE that does not support SBI service operation.

8. 8. The method of claim 7, wherein monitoring the status of the NE that does not support SBI service operation includes detecting that the NE that does not support SBI service operation is available using a native protocol of the NE that does not support SBI service operation, and performing the NF Heart-Beat service operation includes sending a HyperText Transfer Protocol (HTTP) PATCH message to the NRF within a heartbeat interval and indicating a REPLACE operation on an nfStatus attribute of an NF profile of the NE that does not support SBI service operation and a value of the nfStatus attribute as REGISTERED.

9. A method according to any one of claims 1 to 8, wherein updating the status of the NE that does not support SBI service operation in the NRF includes performing an NFUpdate service operation using the NRF on behalf of the NE that does not support SBI service operation.

10. 10. The method of claim 9, wherein monitoring the status of the NE that does not support SBI service operation includes detecting unreachability of the NE that does not support SBI service operation using a native protocol of the NE that does not support SBI service operation, and performing the NFUpdate service operation on behalf of the NE that does not support SBI service operation 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 that does not support SBI service operation and a value of the nfStatus attribute as UNDISCOVERABLE.

11. 1. A system for providing Service Based Interface (SBI) support for a network element (NE) that does not support SBI service operation, comprising: A cloud native core console (CNCC) for receiving SBI configuration parameters for a NE that does not support SBI service operation, and registering the NE that does not support SBI service operation in a network function (NF) repository function (NRF) using the SBI configuration parameters; an Interworking Function (IWF) for establishing a connection with the NE that does not support SBI service operation and monitoring a status of the NE that does not support SBI service operation via the connection; The CNCC is configured to update the status of the NE that does not support SBI service operation in the NRF based on the status monitored by the IWF.

12. The system of claim 11 , wherein the CNCC is configured to receive NF profile parameters for creating an NF profile for the NE that does not support SBI service operation.

13. The system of claim 11 or 12, wherein the CNCC is configured to register the NE that does not support SBI service operation by performing an NFRegister service operation with the NRF on behalf of the NE that does not support SBI service operation.

14. 14. The system of claim 13, wherein the CNCC is configured to perform the NFRegister service operation by sending, to the NRF, a HyperText Transfer Protocol (HTTP) PUT message including an NF profile for the NE that does not support an SBI service operation.

15. The system according to any one of claims 11 to 14, wherein the connection with the NE that does not support SBI service operation includes a transport layer connection.

16. The system of claim 15, wherein the IWF is configured to monitor the status of the NE that does not support SBI service operation by exchanging Diameter watchdog messages with the NE that does not support SBI service operation over the connection.

17. The system according to any one of claims 11 to 16, wherein the CNCC is configured to update the status of the NE that does not support SBI service operation in the NRF by performing NF Heart-Beat service operation using the NRF on behalf of the NE that does not support SBI service operation.

18. 18. The system of claim 17, wherein the IWF is configured to monitor the status of the NE that does not support SBI service operation by detecting that the NE that does not support SBI service operation is available using a native protocol of the NE, and 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 heartbeat interval and indicating a REPLACE operation on an nfStatus attribute of an NF profile of the NE that does not support SBI service operation and a value of the nfStatus attribute as REGISTERED.

19. The system of any one of claims 11 to 18, wherein the IWF is configured to monitor the status of the NE that does not support SBI service operation by detecting unreachability of the NE that does not support SBI service operation using a native protocol of the NE that does not support SBI service operation, and the CNCC is configured to update the status of the NE that does not support SBI service operation by performing the NFUpdate service operation on behalf of the NE that does not support SBI service operation, the NFUpdate service operation including sending to the NRF a Replace operation on an nfStatus attribute of an NF profile of the NE that does not support SBI service operation and a HyperText Transfer Protocol (HTTP) PATCH message indicating the value of the nfStatus attribute as UNDISCOVERABLE.

20. A program for causing a computer to execute a method according to any one of claims 1 to 10.

Images