SCP provides the following two configuration interfaces:

• Signaling Interface
  • Signaling interface is exposed by SCP data plane (i.e. SCP Worker) and this interface will be used to receive all 5G signaling traffic.
• Config Interface
  • Config interface is exposed by SCP control plane (i.e. SCPC-Config) and this interface is used to receive all SCP configuration traffic.

SCP Signaling Service

• FQDN
  • Consumer NFs may use SCP Signaling service's FQDN to send the 5G signaling traffic to SCP for routing.
  • K8S service FQDN will be of the form as below
    • fqdn = scp-worker.<namespace>.<domain> where, namespace is K8S namespace as provided during helm installation, and domain is as provided in helm chart (values.yaml) while installation.
    • If user NFs are deployed outside of K8S cluster, then operator need to make sure that this fqdn is resolvable by consumer NFs.
    • Operator can specify the public or K8s-cluster fqdn of SCP in helm chart (values.yaml, scpInfo.fqdn" = scp-worker.<namespace>.<domain>) during installation.
• IP Address
  • Consumer NFs may use SCP Signaling service's IP Address to send the 5G signaling traffic to SCP for routing.
  • <global.publicSignalingIP>, as provided in helm chart (values.yaml) while installation.
• Port
  • Consumer NFs need port info along with fqdn/ip address to send the 5G signaling traffic to SCP for routing.
  • Port is <global.publicSignalingPort> as provided in helm chart (values.yaml) while SCP installation.

SCP Config Service

• FQDN
  • Operator may use SCP Config service's FQDN to configure the SCP for routing.
  • K8S service FQDN will be of the form as below
    • fqdn = scpc-config-svc.<namespace>.<domain> where, namespace is K8S namespace as provided during helm installation, and domain is as provided in helm chart (values.yaml) while installation.
    • Operator need to make sure that this fqdn is resolvable, if operating from outside of K8S cluster.
• IP Address
  • Consumer NFs may use SCP Config service's IP Address to configure the SCP for routing.
  • <scpc-soothsayer.configService.publicConfigIP>, as provided in helm chart (values.yaml) while installation.
• Port
  • Operator needs port info along with fqdn/ip address to configure the SCP for routing.
  • Port is 8081 i.e. fixed port (not configurable).