What are the programmable functions of the TSC?

Overview

The following figure displays a high-level overview of the user programmable components of the TSC.

Figure 1-7: High-level view of programmable portions of TSC

The IETF NBI payload can be found here:

https://www.ietf.org/archive/id/draft-ietf-teas-ietf-network-slice-nbi-yang-03.html

See the Network Developer Portal for information about the supported elements of the IETF NBI YANG model.

Mapping artifacts

The various elements of slice realization require parameter adaptation and mapping, mostly accomplished using mapping artifacts. Mapping is performed by:

• matching ServiceTemplateName in operator-preferences.json to the name of the service intent used to realize slice services

• importing release-specific mapping artifacts, obtainable from Nokia support, as described in How do I setup TSC?

Features

This section describes specific information about key TSC features.

N:1 mapping of slice services to resources

The NSP can map slice related intent to a dedicated LSP, or multiple intents that have the same SLO/SLE requirements onto a shared LSP. Configuration of this feature is performed in the operator-preferences.json intent type file. An example of the relevant section is the following:

"Lsp": {

    "Isolation": false,

    "Protection": false,

    "SignalingType": "sr-te",

    "PrimaryPathPriority": "1",

    "SecondaryPathPriority": "2"

}

See Obtain and set operator preferences for more information about the operator-preferences.json intent type file.

LSP isolation

In operator-preferences.json, operators can set the Isolation parameter to “true” to enable dedicated LSPs per slice service, or set it to “false” and reuse existing LSPs. The default setting is “false”.

Path protection

The Protection parameter provides protection for LSP paths. When set to “true”, LSPs are deployed and even reused with primary and secondary paths. When set to “false”, LSPs have a primary path only. The default setting is “false”.

Signaling type

The SignalingType parameter allows operators to choose the LSP signaling type. The options are “rsvp” and “sr-te”. The default is “sr-te”.

Path priority

Operators can set the PrimaryPathPriority and SecondaryPathPriority levels for LSP paths using these parameters. The default for PrimaryPathPriority is “1” and the default for SecondaryPathPriority is “2”.