Configuring 3GPP Specification Compliance for Interfaces

To configure the SMF interfaces in compliance with the 3GPP specifications, use the following sample configuration:

config 
   profile compliance profile_name 
       service { n1 | n2 | namf-comm | nchf-convergedcharging | nnrf-disc | nnrf-nfm | npcf-smpolicycontrol | nsmf-pdusession | nudm-sdm | nudm-uecm | threegpp23502 } 
          version { full version_format| spec spec_version| uri uri_version } 
          version-list version  version_name { full version_format | mode { active | offline } | spec  spec_version | uri  uri_version } 
          end 
       end 
   end 
Important

Service selection is based only on the specification version. In future releases, the full API version will be used.

NOTES:

  • service { n1 | n2 | namf-comm | nchf-convergedcharging | nnrf-disc | nnrf-nfm | npcf-smpolicycontrol | nsmf-pdusession | nudm-sdm | nudm-uecm | threegpp23502 } —Specify the service names as cited in the 3GPP TS 29.510 version 15.2.0, section 6.1.6.3.11.

    Note

    The compliance profile configuration for the nchf-convergedcharging service supports the 3GPP TS 29.510 version 15.4.0 specification. With this configured version, the SMF sends the subscriberIdentifier in the following format to CHF:

    "subscriberIdentifier":"imsi-123456789"

  • version —Specify the compliance version name to be configured. It allows configuring only one version at a time.

  • full version_format —Specify the API full version for each service in the following format:

    <Major-version>.<Minor-version>.<patch-version>.[alpha-<draft-number>]

    The format is specified in the 3GPP TS 29.501 version 15.2.0, section 4.3.1.1.

  • spec spec_version —Specify the 3GPP specification version number, which is one of the following values:

    • 15.0.0

    • 15.1.0

    • 15.2.0

    • 15.2.1

    • 15.3.0

    • 15.3.0.custom

    • 15.3.0.std

    • 15.4.0

    For example, to support 3GPP June 2019 specification compliance for the N7 (PCF) interface, configure the specification version as 15.4.0.

    The default version number depends on the SMF interface. For example, the default version is 15.2.0 for the N7 interface. Similarly, for the N10 interface, the default version is 15.2.1.

  • uri uri_version —Specify the API version URI for each service in the following format:

    v—Concatenated with a number, where the value can be both v1 and v2, or either v1 or v2.

    Examples:

    —For the compliance version 15.4.0 in the NRF configuration for the service type nudm-sdm, mandate the configuration of the uri-version in the version to v2. For the compliance version 15.2.1, this configuration is optional.

    —version v1: (- url: '{apiRoot}/nsmf-pdusession/v1').

  • version-list version version_name —Specify the list of compliance versions of the 3GPP specification. If the version-list version is configured with only one version, then both version and version-list version CLIs are considered for version selection logic for peer NFs. Both the CLIs version and version-list version allow configuring the same set of attributes.

    Note

    version-list version is supported for only for N1, N2, N7, N10, N11, N40, and Nnrf interfaces.

  • mode { active | offline } —Specify the status of configured 3GPP compliance versions. mode is an optional configuration under the CLI version-list version . The default value of mode is active . If version-list version is configured with two versions, then at least one version should be active .

Important

Configuring the 3GPP specification version value depends on the SMF interface. Not all the preceding versions are options for the SMF interfaces. Only a combination of the preceding versions exists as an option for the 3GPP version compliance configuration. For details on the compliance version, see the Standards Compliance section.

Important

The 15.3.0.custom spec version is customer specific and applicable only to the nchf-convergedcharging service. For more details, contact your Cisco account representative.

In this spec version, the MultipleUnitUsage attribute sends the usedUnitContainer field in lowercase. For all other spec versions, the MultipleUnitUsage attribute sends the UsedUnitContainer field in uppercase.

Important

The release version 2023.03.0 supports both version and version-list version CLIs. However, the version CLI will be discontinued from the future releases.