1. Network Repository Function (NRF) Cloud Native User's Guide
  2. OCNRF Architecture

3 OCNRF Architecture

OCNRF comprises of various microservices deployed in Kubernetes based Cloud Native Environment (CNE, example: OCCNE). Some common services like logs or metrics data collection, analysis and graphs or charts visualization, and so on are provided by the environment. The microservices integrate with the environment and provide the necessary data.

Following are the components of OCNRF product:

  • NF Registration Microservice

    This microservice receives and handles the following service operations:

    • NFRegister service requests from the NFs
    • NFUpdate service requests from the NFs
    • NFDeregister service requests from the NFs
    • NFListRetrieval service requests from the NFs
    • NFProfileRetrieval service requests from the NFs
    • Heart-beat messages from the NFs
  • NF Subscription Microservice

    This microservice performs the following service operations:

    • receives and handles NFStatusSubscribe service requests from the NFs
    • receives and handles NFStatusUnsubscribe service requests from the NFs
    • sends NFStatusNotify service requests towards the subscribed NFs
  • NF Discover Microservice

    This microservice receives and handles the following service operations:

    • NFDiscover service requests from the NFs
  • NF AccessToken Microservice

    This microservice handles 3GPP defined AccessToken service operations. Oauth2.0 based token is provided by OCNRF according to inputs provided by consumer network function in access token request.

  • OCNRF Auditor Microservice

    This microservice is internal to OCNRF. This microservice performs the following tasks:

    • finds and deletes the expired subscription records
    • finds and deletes the profile records which have been SUSPENDED for a very long time
    • monitors the heart-beat expiry, mark the NF profiles as suspended and act appropriately on the suspended NF profiles
  • OCNRF Configuration Microservice

    This microservice is used to configure OCNRF. These configuration can be changed dynamically by a operator/user using REST based interface. This configuration data is managed by the OCNRF configuration service and is stored in a separate data store.

  • OCNRF Ingress Gateway Microservice

    This microservice is entry point for accessing OCNRF supported service operations.

  • OCNRF Egress Gateway Microservice

    This microservice is responsible to route OCNRF initiated egress messages to other NFs.

  • App Info Microservice

    This microservice is responsible to get the status of microservices related to NFManagement Service operations (that is NF Registration microservice, NF Subscription microservice, NRF Auditor microservice).

    NF Registration, NF Subscription, NRF Auditor microservices uses this microservice to get the status of other two microservices. In case any of service is found as down, status asking microservice will reject the incoming messages. This microservice is also responsible to fetch DB replication status whether it is active or not-active.