1 Introduction
This document provides information about how to configure the services and manageable objects in Oracle Communications Cloud Native Core, Service Communication Proxy (SCP) using Representational State Transfer Application Programming Interfaces (REST APIs).
The core network in 5G follows a service-based architecture, where network functions provide services that can be utilized using REST APIs by other functions. This allows the adoption of web-scale technologies and software that are used by different organizations in the telecommunications network.
SCP provides routing, load balancing, rate limiting, static
configuration, dynamic discovery, and so on, functionalities to other 5G
Network Functions (NFs). For more information about SCP functionalities and
features, see Oracle Communications Cloud Native Core, Service Communication Proxy User
Guide.
Note:
- The performance and capacity of the SCP system may vary based on the call model, feature or interface configuration, network conditions, and underlying CNE and hardware environment.
- The following terms are not used interchangeably in this
document. They define SCP’s routing behavior for
different scenarios:
- Alternate Routing: This term is used for the scenarios when SCP sends a request to an upstream producer and does not receive a successful response from the target upstream producer NF due to a request timeout, an error response, and so on. In such cases, SCP selects another equivalent available producer NF and performs routing to that producer NF. This routing to another equivalent available producer NF after the initial or prior routing failure is referred to as alternate routing.
- Reselection: This term is used when SCP selects an alternate producer NF different from the initially selected producer NF, without attempting to send the request to the initially selected producer NF.