Edit an existing Network Slice Template.

You can view the network slice template. You can edit or delete the existing network slice template.

Prerequisites

Ensure that you have permission to edit the network slice template.

Procedure

  1. Log in to the VMware Telco Cloud Automation web interface.
  2. Select Catalog > Network Slicing and select the network slicing function.
  3. Click the Slice Template tab.
  4. Click the symbol against the network slicing template and select the operation from the list.
    • To instantiate the network slice template, select Instantiate.
    • To delete the service order, select Delete.
    • To edit the service order, select Edit.
  5. To edit the network slice template, select Edit.
    System shows Edit Network Slice Template page.
  6. To view the general properties, click General Properties tab. It shows the following details:
    • Name - Name of the network slice template.
    • Description - Description of the network slice template.
    • Template version - Version number of the network slice template.
  7. To view the profile details, click Profile tab. The profile tab shows following parameters
    • General settings - Shows the general parameters related to the network slice.
      • Slice/Service Type - Defines the service type related to a network slice. Select the value from the drop-down menu.
        • 1 - eMBB - Enhanced Mobile Broadband.
        • 2 - uRLLC - Ultra Reliable Low Latency Communications.
        • 3 - mIOT/mMTC - Massive Internet of Things/ Massive Machine Type Communications.
        • 4 - custom - Custom service type created by customer.
      • Activity Factor - Percentage of simultaneously active user equipments to the total active user equipments.
      • Allowed Jitter - Maximum allowed time variation.
      • Availability - Availability of the network slice service. The value is in percentage.
      • Coverage Area - The coverage area of the network slice.
      • Latency - Packet transmission latency between the network slice. The value is in milli seconds.
      • Maximum Device Speed - Maximum transmission speed that the network slice can support.
      • Maximum no of UEs - Maximum number of user equipments that can simultaneously access the network.
      • Network Slice Sharing Indicator - Whether the service can share the network slice.
        • Shared - Services can share the network slice.
        • Non-shared - Services cannot share the network slice.
      • Reliability - Reliability of the network slice. The value is in percentage. Value range is 0 to 100.
      • Survival Time - The time interval for which an application can survive without accessing the message. The value is in milli seconds. You can also provide multiple comma seperated time intervals.
      • UE Mobility Level - The mobility level of the user equipments that the network slice supports.
        • Stationary - Network slice supports only stationary user equipments.
        • Nomadic - Network slice supports only user equipments which has intermittent availability.
        • Restricted Mobility - Network slice supports user equipments restricted mobility.
        • Fully Mobility - Network slice supports user equipments with complete mobility.
    • PLMN Information (public land mobile networks) - Shows the parameters related to the public land mobile networks.
      • Mobile Country Code (MCC) - Mobile country code of the country.
      • Mobile Network Code (MNC) - Mobile network code of the country.
    • S-NSSAI (Single – Network Slice Selection Assistance Information) - Shows the parameters required to uniquely identify a Network Slice.
      • Slice/Service Type - The service type associated with the network slice.
        • 1 - eMBB - Enhanced Mobile Broadband.
        • 2 - uRLLC - Ultra Reliable Low Latency Communications.
        • 3 - mIOT/mMTC - Massive Internet of Things/ Massive Machine Type Communications.
        • 4 - custom - Custom service type created by customer.
      • Slice Differentiator - The value used to differentiate between network slices. If the parameter is not needed, set the value to FFFFFF.
    • Delay Tolerance - Shows the parameters related to delay requirements in a network slice.
      • Category - Criteria to categorize the network slice through common attributes.
        • Character - Characterize a slice. For example throughput, latency, Application Program Interfaces, etc.
        • Scalability - Provide information about the scalability of the slice. For example number of UEs.
      • Tagging - You can use the tags as labels attached to the attributes to give additional information about the nature of each attribute. Each attribute could have multiple tags. The following tags apply to the character attributes:
        • Performance - Specify the KPIs supported by a slice. Performance related attributes are relevant before the slice is instantiated.
        • Function - Specify functionality provided by the slice. Function related attributes are relevant before the slice is instantiated.
        • Operation - Specify which methods are provided to the NSC in order to control and manage the slice. These attributes are relevant after the slice is instantiated.
      • Exposure - The way the attributes interact with the network slice consumer can be used for tagging:
        • API - These attributes provide an API in order to get access to the slice capabilities.
        • KPI - These attributes provide certain performance capabilities, for example throughput and delay.
    • Deterministic Communication - This attribute defines if the network slice supports deterministic communication for periodic UE traffic. Periodic traffic refers to the type of traffic with periodic transmissions.
      • Category - Criteria to categorize the network slice through common attributes.
        • Character - Characterize a slice. For example throughput, latency, Application Program Interfaces, etc.
        • Scalability - Provide information about the scalability of the slice. For example number of UEs.
      • Tagging - You can use the tags as labels attached to the attributes to give additional information about the nature of each attribute. Each attribute could have multiple tags. The following tags apply to the character attributes:
        • Performance - Specify the KPIs supported by a slice. Performance related attributes are relevant before the slice is instantiated.
        • Function - Specify functionality provided by the slice. Function related attributes are relevant before the slice is instantiated.
        • Operation - Specify which methods are provided to the NSC in order to control and manage the slice. These attributes are relevant after the slice is instantiated.
      • Exposure - The way the attributes interact with the network slice consumer can be used for tagging:
        • API - These attributes provide an API in order to get access to the slice capabilities.
        • KPI - These attributes provide certain performance capabilities, for example throughput and delay.
      • Availability - This parameter describes if the network slice supports deterministic communication.
      • Periodicity List - This parameter provides a list of periodicities supported by the network slice. This parameter must be present when the “Availability” is set to Supported.
    • Downlink Throughput per Network Slice - This attribute relates to the aggregated data rate in downlink for all UEs together in the network slice.
      • Category - Criteria to categorize the network slice through common attributes.
        • Character - Characterize a slice. For example throughput, latency, Application Program Interfaces, etc.
        • Scalability - Provide information about the scalability of the slice. For example number of UEs.
      • Tagging - You can use the tags as labels attached to the attributes to give additional information about the nature of each attribute. Each attribute could have multiple tags. The following tags apply to the character attributes:
        • Performance - Specify the KPIs supported by a slice. Performance related attributes are relevant before the slice is instantiated.
        • Function - Specify functionality provided by the slice. Function related attributes are relevant before the slice is instantiated.
        • Operation - Specify which methods are provided to the NSC in order to control and manage the slice. These attributes are relevant after the slice is instantiated.
      • Exposure - The way the attributes interact with the network slice consumer can be used for tagging:
        • API - These attributes provide an API in order to get access to the slice capabilities.
        • KPI - These attributes provide certain performance capabilities, for example throughput and delay.
      • Guaranteed Downlink Throughput per Network Slice - Minimum required download speed that the network slice provides.
      • Maximum Downlink Throughput per Network Slice - Maximum download speed that the network slice provides.
    • Downlink Throughput per Network Slice ( for UE) - This attribute describes the maximum data rate supported by the network slice per UE in downlink.
      • Category - Criteria to categorize the network slice through common attributes.
        • Character - Characterize a slice. For example throughput, latency, Application Program Interfaces, etc.
        • Scalability - Provide information about the scalability of the slice. For example number of UEs.
      • Tagging - You can use the tags as labels attached to the attributes to give additional information about the nature of each attribute. Each attribute could have multiple tags. The following tags apply to the character attributes:
        • Performance - Specify the KPIs supported by a slice. Performance related attributes are relevant before the slice is instantiated.
        • Function - Specify functionality provided by the slice. Function related attributes are relevant before the slice is instantiated.
        • Operation - Specify which methods are provided to the NSC in order to control and manage the slice. These attributes are relevant after the slice is instantiated.
      • Exposure - The way the attributes interact with the network slice consumer can be used for tagging:
        • API - These attributes provide an API in order to get access to the slice capabilities.
        • KPI - These attributes provide certain performance capabilities, for example throughput and delay.
      • Guaranteed Downlink Throughput Per UE per Slice - Minimum required download speed for each active user equipment that the network slice provides.
      • Maximum Downlink Throughput Per UE per Slice - Maximum download speed for each active user equipment that the network slice provides.
    • KQIs and KPIs
      • Category - Criteria to categorize the network slice through common attributes.
        • Character - Characterize a slice. For example throughput, latency, Application Program Interfaces, etc.
        • Scalability - Provide information about the scalability of the slice. For example number of UEs.
      • Tagging - You can use the tags as labels attached to the attributes to give additional information about the nature of each attribute. Each attribute could have multiple tags. The following tags apply to the character attributes:
        • Performance - Specify the KPIs supported by a slice. Performance related attributes are relevant before the slice is instantiated.
        • Function - Specify functionality provided by the slice. Function related attributes are relevant before the slice is instantiated.
        • Operation - Specify which methods are provided to the NSC in order to control and manage the slice. These attributes are relevant after the slice is instantiated.
      • Exposure - The way the attributes interact with the network slice consumer can be used for tagging:
        • API - These attributes provide an API in order to get access to the slice capabilities.
        • KPI - These attributes provide certain performance capabilities, for example throughput and delay.
      • List of KQIs and KPIs - Name of the list of KPIs and KQIs to monitor the performance of the network.
    • Maximum Number of Connections per Slice
      • Category - Criteria to categorize the network slice through common attributes.
        • Character - Characterize a slice. For example throughput, latency, Application Program Interfaces, etc.
        • Scalability - Provide information about the scalability of the slice. For example number of UEs.
      • Tagging - You can use the tags as labels attached to the attributes to give additional information about the nature of each attribute. Each attribute could have multiple tags. The following tags apply to the character attributes:
        • Performance - Specify the KPIs supported by a slice. Performance related attributes are relevant before the slice is instantiated.
        • Function - Specify functionality provided by the slice. Function related attributes are relevant before the slice is instantiated.
        • Operation - Specify which methods are provided to the NSC in order to control and manage the slice. These attributes are relevant after the slice is instantiated.
      • Exposure - The way the attributes interact with the network slice consumer can be used for tagging:
        • API - These attributes provide an API in order to get access to the slice capabilities.
        • KPI - These attributes provide certain performance capabilities, for example throughput and delay.
      • Maximum Number of Concurrent Sessions - Maximum number of simultaneous sessions that the network slice can support.
    • Maximum Supported Packet Size - This attribute describes the maximum packet size supported by the network slice.
      • Category - Criteria to categorize the network slice through common attributes.
        • Character - Characterize a slice. For example throughput, latency, Application Program Interfaces, etc.
        • Scalability - Provide information about the scalability of the slice. For example number of UEs.
      • Tagging - You can use the tags as labels attached to the attributes to give additional information about the nature of each attribute. Each attribute could have multiple tags. The following tags apply to the character attributes:
        • Performance - Specify the KPIs supported by a slice. Performance related attributes are relevant before the slice is instantiated.
        • Function - Specify functionality provided by the slice. Function related attributes are relevant before the slice is instantiated.
        • Operation - Specify which methods are provided to the NSC in order to control and manage the slice. These attributes are relevant after the slice is instantiated.
      • Exposure - The way the attributes interact with the network slice consumer can be used for tagging:
        • API - These attributes provide an API in order to get access to the slice capabilities.
        • KPI - These attributes provide certain performance capabilities, for example throughput and delay.
      • Maximum Packet Size - Maximum packet size allowed in the network slice.
    • Overall User Density - This attribute describes the maximum number of connected and/or accessible devices per unit area (per km2) supported by the network slice.
      • Category - Criteria to categorize the network slice through common attributes.
        • Character - Characterize a slice. For example throughput, latency, Application Program Interfaces, etc.
        • Scalability - Provide information about the scalability of the slice. For example number of UEs.
      • Tagging - You can use the tags as labels attached to the attributes to give additional information about the nature of each attribute. Each attribute could have multiple tags. The following tags apply to the character attributes:
        • Performance - Specify the KPIs supported by a slice. Performance related attributes are relevant before the slice is instantiated.
        • Function - Specify functionality provided by the slice. Function related attributes are relevant before the slice is instantiated.
        • Operation - Specify which methods are provided to the NSC in order to control and manage the slice. These attributes are relevant after the slice is instantiated.
      • Exposure - The way the attributes interact with the network slice consumer can be used for tagging:
        • API - These attributes provide an API in order to get access to the slice capabilities.
        • KPI - These attributes provide certain performance capabilities, for example throughput and delay.
      • Overall User Density - The user device density that the network device can handle. The value is in number of users per square kilometer.
    • Uplink Throughput per Network Slice - This attribute relates to the aggregated data rate in uplink for all UEs together in the network slice (this is not per UE).
      • Category - Criteria to categorize the network slice through common attributes.
        • Character - Characterize a slice. For example throughput, latency, Application Program Interfaces, etc.
        • Scalability - Provide information about the scalability of the slice. For example number of UEs.
      • Tagging - You can use the tags as labels attached to the attributes to give additional information about the nature of each attribute. Each attribute could have multiple tags. The following tags apply to the character attributes:
        • Performance - Specify the KPIs supported by a slice. Performance related attributes are relevant before the slice is instantiated.
        • Function - Specify functionality provided by the slice. Function related attributes are relevant before the slice is instantiated.
        • Operation - Specify which methods are provided to the NSC in order to control and manage the slice. These attributes are relevant after the slice is instantiated.
      • Exposure - The way the attributes interact with the network slice consumer can be used for tagging:
        • API - These attributes provide an API in order to get access to the slice capabilities.
        • KPI - These attributes provide certain performance capabilities, for example throughput and delay.
      • Guaranteed Uplink Throughput per Slice - Minimum required upload speed that the network slice provides.
      • Maximum Uplink Throughput per Slice - Maximum upload speed that the network slice provides.
    • Uplink Throughput per Network Slice per UE - This attribute describes the maximum data rate supported by the network slice per UE in uplink.
      • Category - Criteria to categorize the network slice through common attributes.
        • Character - Characterize a slice. For example throughput, latency, Application Program Interfaces, etc.
        • Scalability - Provide information about the scalability of the slice. For example number of UEs.
      • Tagging - You can use the tags as labels attached to the attributes to give additional information about the nature of each attribute. Each attribute could have multiple tags. The following tags apply to the character attributes:
        • Performance - Specify the KPIs supported by a slice. Performance related attributes are relevant before the slice is instantiated.
        • Function - Specify functionality provided by the slice. Function related attributes are relevant before the slice is instantiated.
        • Operation - Specify which methods are provided to the NSC in order to control and manage the slice. These attributes are relevant after the slice is instantiated.
      • Exposure - The way the attributes interact with the network slice consumer can be used for tagging:
        • API - These attributes provide an API in order to get access to the slice capabilities.
        • KPI - These attributes provide certain performance capabilities, for example throughput and delay.
      • Guaranteed Uplink Throughput Per UE per Slice - Minimum required upload speed for each active user equipment that the network slice provides.
      • Maximum Uplink Throughput Per UE per Slice - Maximum upload speed for each active user equipment that the network slice provides.
      User Management Openness - This attribute describes the capability for the NSC to manage their users or groups of users’ network services and corresponding requirements.
      • Category - Criteria to categorize the network slice through common attributes.
        • Character - Characterize a slice. For example throughput, latency, Application Program Interfaces, etc.
        • Scalability - Provide information about the scalability of the slice. For example number of UEs.
      • Tagging - You can use the tags as labels attached to the attributes to give additional information about the nature of each attribute. Each attribute could have multiple tags. The following tags apply to the character attributes:
        • Performance - Specify the KPIs supported by a slice. Performance related attributes are relevant before the slice is instantiated.
        • Function - Specify functionality provided by the slice. Function related attributes are relevant before the slice is instantiated.
        • Operation - Specify which methods are provided to the NSC in order to control and manage the slice. These attributes are relevant after the slice is instantiated.
      • Exposure - The way the attributes interact with the network slice consumer can be used for tagging:
        • API - These attributes provide an API in order to get access to the slice capabilities.
        • KPI - These attributes provide certain performance capabilities, for example throughput and delay.
      • User Management Openness Support - Whether the network slice allows the NSC to manage the users or groups of users.
    • V2X Communication Models (Vehicular-to-Everything) - Shows the parameters related to the exchange of information between vehicle and infrastructure (V2I) or between vehicles (V2V).
      • Category - Criteria to categorize the network slice through common attributes.
        • Character - Characterize a slice. For example throughput, latency, Application Program Interfaces, etc.
        • Scalability - Provide information about the scalability of the slice. For example number of UEs.
      • Tagging - You can use the tags as labels attached to the attributes to give additional information about the nature of each attribute. Each attribute could have multiple tags. The following tags apply to the character attributes:
        • Performance - Specify the KPIs supported by a slice. Performance related attributes are relevant before the slice is instantiated.
        • Function - Specify functionality provided by the slice. Function related attributes are relevant before the slice is instantiated.
        • Operation - Specify which methods are provided to the NSC in order to control and manage the slice. These attributes are relevant after the slice is instantiated.
      • Exposure - The way the attributes interact with the network slice consumer can be used for tagging:
        • API - These attributes provide an API in order to get access to the slice capabilities.
        • KPI - These attributes provide certain performance capabilities, for example throughput and delay.
      • V2X Communication Mode - Whether the network slice supports V2X mode.
        • Supported - Network slice supports V2X mode.
        • Not Supported - Network slice does not support V2X mode.
  8. To configure the topology, click Topology tab.
    The Topology tab shows the following details of the network function associated with the network slicing function:
    • Network Slice Subnet - It represents the management aspects of a set of Managed Functions and the required resources.
      • General Settings - You can modify the parameters related to the general settings of the network slice template.
      • PLMN Information - You can modify the parameters related to PLMN parameters of the network slice template.
      • Performance Requirements - You can modify the parameters related to the performance settings of the network slice template.
      • S-NSSAI - You can modify the parameters related to the Single – Network Slice Selection Assistance Information of the network slice template.
    • Network Slice Structure - It represents the network functions and network services associated with the network slice.
      • Add Subnet - You can create a subnet within a network slice. You can add separate network functions and network services to each subnet.
        1. To create a subnet in a network slice, click Add Subnet. Add the following details on the Create Network Slice Subnet Template page.
          • Name - Name of the network slice subnet.
          • Description - Description of the network slice subnet.
        2. Click Add to save the details.
      • Add Descriptor - It represents the network functions and network services associated with the network slice.
        1. To add a network function or a network service, click on the Add Descriptor and select Add Network Service or Add Network Function.

          When you select Add Network Service, the Select Network Service For Network Slice Template page appears. When you select Add Network Function, the Select Network Function For Network Slice Template page appears.

        2. Select the network service or the network function that you want to add and click Select.