In addition to the requirements and test cases in TS 33.117, clause 4.2.2
, an SCP shall satisfy the following:
It is assumed for the purpose of the present SCAS that an SCP conforms to all mandatory security-related provisions pertaining to an SCP in:
Security procedures pertaining to an SCP are typically embedded in NF/NF indirect communication, delegated discovery, message forwarding and routing, and are hence assumed to be tested together with them in interoperability testing at PLMN level, shared-slice level and slice-specific level.
According to TS 23.501
, although the SCP is not a Network Function instance and does not expose services itself, it still needs to support service-based interface. Therefore, the general baseline requirements supported by all Network Functions (NF) utilizing Service-Based Interfaces (SBI) as defined in TS 33.117, clause 18.104.22.168
shall also be applicable to the SCP network product class. This clause contains SCP-specific adaptations to the general SBI requirements and related test cases.
There are no SCP-specific additions to clause 22.214.171.124.2 of TS 33.117
The SCP is not a network function instance and does not provide any services to any consumer NF. It supports OAuth 2.0 based service access authorization for NF service access, but it does not verify access tokens as NF producers do. Therefore, the requirements and test cases in clause 126.96.36.199.3 of TS 33.117
are not applicable to the SCP network product class.