NSST (Network Slice Subnet Template)

sbnd f

dbfb

Enables specifying any kind of relationships between ServiceOrderItems The type of relationship such as contains, relies on.

An association between two ServiceOrders. A categorization of the relationship, such as bulk, parent/child, and so forth.

An implementation of composite Service corresponding to a ServiceCompositeDescriptor.

Describe the nested relationship between multiple Serive Descriptors.

An implementation of atomic Service corresponding to a ServicecAtomicDescriptor.

Resource components of constituting a serivce descriptor.

Resource instance components of constituting a serivce instance.

Resource instance components of constituting a serivce instance.

Resource components of constituting a serivce descriptor.

Some Questions: 1. Do we have a business need to have multiple service catalogs? - 2. Do we have a need to have a service descriptor in a given catalog multiple times for different time periods? - 3. How do we handle moving a descriptor from a test catalog to a production catalog? - 4. What is the attachment class? Presently, SDC stores the descriptor directly in the catalog. I don't think SDC uses the SID Characteristic patern. Removed recursive associations, given we are using the composite/atomic pattern. Do we need this diagram? Option 1 Option 2 NST (Network Slice Template) The Nfpd class associates traffic flow criteria to a list of descriptors associated to the connection points and service access points to be visited by traffic flows matching these criteria. Identifies this nfpd class within a VNFFGD. Provides an NFP classification and selection rule. The rule may be expressed as a criteria constructed out of atomic assertions linked by Boolean operators AND, OR and NOT. NOTE: Examples of atomic assertions are assertions on packet header fields’ values, date and time ranges, etc. References the descriptor of a connection point to be traversed by the traffic flows matching the criteria. This shall be a connection point attached to one of the constituent VNFs and PNFs of the parent VNFFG, or a SAP of one of the constituent nested NSs of the parent VNFFG. NOTE: When multiple values are provided, the order is significant and specifies the sequence of connection points to be traversed. This is an abstract proxy class, allowing to provide reference to either NsProfile or VnfProfile. The Dependencies class provides indications on the order in which VNFs associated to different VNF Profiles and/or nested NSs associated to different NS Profiles are to be instantiated. References a VnfProfile or NsProfile. NOTE: NFV Management and Orchestration functions shall instantiate VNFs from the VnfProfile and/or nested NSs from the NsProfile referenced in the primary attribute before instantiating VNFs from the VnfProfile and/or nested NSs from the NsProfile referenced in the secondary attribute. References a VnfProfile or NsProfile. NOTE: NFV Management and Orchestration functions shall instantiate VNFs from the VnfProfile and/or nested NSs from the NsProfile referenced in the primary attribute before instantiating VNFs from the VnfProfile and/or nested NSs from the NsProfile referenced in the secondary attribute Provides information on a Service Access Point (SAP) of a NS ServiceDescriptor is used to model the design time representation of a service. Constant identifier of the service model. Versioned identifier of the service model (this uuid is changed for every major version of the service) The name of the service model designed. The description of the service model designed. A predefined list which identifies the construct's category. There is a predefined list of service categories. The service model version. An optional string field defining a generic type (like category) of the service. E.g. this field can be used for defining the service as “TRANSPORT”. An optional string field for shortcode that defines the function that the service is providing. E.g. “MISVPN” or “AIM”. The icon path of the service. Describe whether this service descriptor is shared or not in the service design. Includes a list of events and corresponding management scripts performed for the Service. ServiceInstance is used to model the run time representation of a service. Uniquely identifies this instance of a service. Uniquely identifies this instance of a service. The name assigned to the service-instance. An optional string field defining a generic type (like category) of the service. E.g. this field can be used for defining the service as “TRANSPORT”. An optional string field for shortcode that defines the function that the service is providing. E.g. “MISVPN” or “AIM”. URL to endpoint where more details can be gotten. Orchestration status of the service instance. Describe NS instance staus: instantiating(creating the Networek Service instance), active(the existed Network Service instance is under using), terminating(the existed Network Service instance stops using) or etc(healing and other possible status). Record the number of services that are using this service instance. Note: This attribute can be used when a service instance is prepared to be deleted, the detected number will help to find how many services are using this instance. If number is greater than 1, it shows this instance is used by other service(s), otherwise it can be deleted. ServcieCompositeDescriptor is used to model the design time representation of a service component or network service. Describe the nested relationship between multiple Service Descriptors. An implementation of composite Service corresponding to a ServiceCompositeDescriptor. Resource components of constituting a serivce descriptor. A type of Request that represents a Customer Order's products decomposed into the services through which the products are realized. Unique identifier for Interaction. ID given by the order requester and only understandable by him (to facilitate his searches afterwards). It could an order number reference from the triggering system (OM) A way that can be used by order requester to prioritize orders in Service Order Narrative that explains the interaction and details about the interaction, such as why the interaction is taking place. Used to categorize the order - Requester valued it and this category can be useful for the Service Order Management system and/or requester (e.g. "broadband", "TV option”,). State of the order The date on which an interaction is closed or completed. The date that was requested to start processing the order. The date on which an interaction is closed or completed. The date on which an interaction is expected to be completed. The date on which an interaction is started. Contact attached to the order to send back information regarding this order Reference to ServiceOrderItem The date the order was placed. The purpose for the ServiceOrder expressed in terms of a ServiceSpecification or a Service. Identifier of the line item (generally it is a sequence number 01, 02, 03, ...). The action to take for an InteractionItem, such as add, change, remove. State of the order item: described in the state machine diagram. This is the requested state. Quantity of an interaction item involved in an interaction. An implementation of atomic Service corresponding to a ServicecAtomicDescriptor. Resource components of constituting a serivce descriptor. Resource instance components of constituting a service instance. A ServiceCandidate (ServiceCatalogItem) is an entity that makes a ServiceSpecification available to a catalog. A ServiceCandidate and its associated ServiceSpecification may be “published” (made visible) in any number of ServiceCatalogs, or in none. One ServiceSpecification can be composed of other ServiceSpecifications. These ServiceSpecifications may also be published. A unique identifier for the ServiceCandidate A word or phrase that a ServiceCandidate is known and distinguished from other ServiceCandidates. A narrative that explains the ServiceCandidate. The period of time during which the ServiceCandidate is applicable. The condition at which the ServiceCandidate exists such as planned, active and Obsolete. A ServiceCatalog is a collection of ServiceCandidates representing ServiceSpecifications. ServiceCandidates define the underlying services that support a ProductOffering. ServiceCandidates are exposed to one or more Product Catalogs to be utilized to configure one or more ProductOfferings. ServiceCandidates can be exposed to one or more Service Catalogs to be utilized or incorporated in one or more ServiceCandidates. A collection may consist of similar ServiceCandidates, such as a collection of broadband ServiceCatalogCandidates or a collection of wireless ServiceCatalogCandidates. A Service Catalog contents can expose a collection of ServiceCandidates to be utilized internal/external to an enterprise. Resource instance components of constituting a service instance. A quality or distinctive feature that defines an entity, including the name of this feature (attribute), and the type of the actual value. Name of dynamic characteristic (attribute). Type of the dynamic characteristic value. The value of a given ServiceCharacteristic The value of a given ServiceCharacteristic The SAPD class specifies the information used to instantiate the service access points of an NS. A Sapd inherits from the Cpd class. All attributes of the Cpd are also attributes of the Sapd. Specify whether the SAP address assignment is under the responsibility of management and orchestration functions or not. If it is set to True, management and orchestration functions are responsible for assigning addresses to the access points instantiated from this SAPD. References the descriptor of VNF or PNF external connection points the SAPs instantiated from this SAPD are mapped to. References the descriptor of the NS VL instance to which the SAP instantiated from this SAPD connects to. Constant identifier of the service model. Versioned identifier of the service model (this uuid is changed for every major version of the service) The name of the service model designed. The description of the service model designed. A predefined list which identifies the construct's category. There is a predefined list of service categories. The service model version. An optional string field defining a generic type (like category) of the service. E.g. this field can be used for defining the service as “TRANSPORT”. An optional string field for shortcode that defines the function that the service is providing. E.g. “MISVPN” or “AIM”. The icon path of the service. Identifier of this NSD class. It globally uniquely identifies an instance of the NSD Identifies the designer of the NSD. Identifies the version of the NSD. Provides the human readable name of the NSD. Identifies an NSD in a version independent manner. This attribute is invariant across versions of NSD. Specifies a rule to trigger a scaling action on a NS instantiated according to the NSD. NOTE 1: The rule is based on a combination of assertions on the values of virtualised resource-related performance metrics and VNF Indicators identified by the monitoredInfo attribute. NOTE 2: There may be multiple data sources (each identified as monitoredInfo) per rule Identifies either a virtualised resource-related performance metric or a VNF Indicator. Provides a life cycle management script written in a Domain Specific Language (DSL). A composition of Network Functions and defined by its functional and behavioural specification. NOTE: The Network Service (NS) contributes to the behaviour of the higher layer service, which is characterized by at least performance, dependability, and security specifications. The end-to-end network service behaviour is the result of the combination of the individual network function behaviours as well as the behaviours of the network infrastructure composition mechanism. Identifier of this NetworkService, identifying the NS instance. Human readable name of the NS instance. Human readable description of the NS instance Reference to consistituent VNFs and PNFs on this NS. NOTE: Cardinality of zero is only valid for a non-instantiated NS. Information on the VLs of this NS. NOTE: Cardinality of zero is only valid for a non-instantiated NS. Information on the SAPs of this NS. Reference to information on nested NSs of this NS. Information on the VNFFGs of this NS. A set of BBS case specific properties information, which are needed for BBS service with the function realization. A set of Slicing case specific properties information, which are needed for network slicing service with the function realization. A unique identifier of property of network slice related requirement should be supported by the network slice instance. This parameter specifies the requirements to the NSI in terms of the scenarios defined in the TS 22.261 [28], such as Experienced data rate, Area traffic capacity (density) information of UE density. It is a structure containing the following elements: - list of perfRequirements Depending on the sST value, the list of perfRequirements will be - list of eMBBPerfReq or - list of uRLLCPerfReq or - list of mIoTPerfReq NOTE: the list of mIoTPerfReq is not addressed in the present document. This parameter specifies the S-NSSAI list to be supported by the new NSI to be created or the existing NSI to be re-used. An attribute specifies whether the resources to be allocated to the network slice instance may be shared with another network slice instance(s). AllowedValues: shared, non-shared. An attribute specifies the maximum number of UEs may simultaneously access the network slice instance. This parameter specifies the slice/service type for a ServiceProfile. An attribute specifies the packet transmission latency (millisecond) through the RAN, CN, and TN part of 5G network and is used to evaluate utilization performance of the end-to-end network slice instance. See clause 6.3.1 of 28.554. List of unique identities for PLMN. An attribute specifies the mobility level of UE accessing the network slice instance. See 6.2.1 of TS 22.261. AllowedValues: stationary, nomadic, restricted mobility, fully mobility. An attribute specifies a list of TrackingAreas where the NSI can be selected. This parameter specifies the availability requirement for an network slice instance, expressed as a percentage. The set of GSMA defined GST properties for network slicing service fuction realization. The set of 3GPP defined SliceProfile for network slicing subnet service fuction realization. A unique identifier of the property of network slice subnet related requirement should be supported by the network slice subnet instance. An attribute specifies whether the resources to be allocated to the network slice subnet instance may be shared with another network slice subnet instance(s). AllowedValues: shared, non-shared. The set of 3GPP defined ServiceProfile for network slicing service function realization. A unique identifier of property of network slice related requirement should be supported by the network slice instance. This parameter specifies the S-NSSAI list to be supported by the new NSI to be created or the existing NSI to be re-used. List of unique identities for PLMN. This parameter specifies the requirements to the NSI in terms of the scenarios defined in the TS 22.261 [28], such as Experienced data rate, Area traffic capacity (density) information of UE density. It is a structure containing the following elements: - list of perfRequirements Depending on the sST value, the list of perfRequirements will be - list of eMBBPerfReq or - list of uRLLCPerfReq or - list of mIoTPerfReq NOTE: the list of mIoTPerfReq is not addressed in the present document. An attribute specifies the maximum number of UEs may simultaneously access the network slice instance. An attribute specifies a list of TrackingAreas where the NSI can be selected. An attribute specifies the packet transmission latency (millisecond) through the RAN, CN, and TN part of 5G network and is used to evaluate utilization performance of the end-to-end network slice instance. See clause 6.3.1 of 28.554. An attribute specifies the mobility level of UE accessing the network slice instance. See 6.2.1 of TS 22.261. AllowedValues: stationary, nomadic, restricted mobility, fully mobility. An attribute specifies whether the resources to be allocated to the network slice instance may be shared with another network slice instance(s). AllowedValues: shared, non-shared. This parameter specifies the slice/service type for a ServiceProfile. This parameter specifies the availability requirement for an network slice instance, expressed as a percentage. A set of CCVPN case specific properties information, which are needed for CCVPN service with the function realization. A set of CCVPN case specific properties information, which are needed for CCVPN service with the function realization. The VirtualLinkToLevelMapping datatype specifies the profile to be used for a VL involved in a given NS level and bitrate requirements. Identifies the profile to be used for a VL involved in an NS level. Specifies the bit rate requirements for the NS level. NOTE: It shall be in the range of minBitrateRequirements - maxBitrateRequirements, as specified in the referenced VirtualLinkProfile. A base / value business entity used to represent a period of time, between two timepoints An instant of time, starting at the TimePeriod Notes: If null, then represents to the beginning of time An instant of time, ending at the TimePeriod: Notes: If null, then represents to the end of time A way that can be used by order requester to prioritize orders in Service Order Management system (from 0 to 4: 0 is the highest priority, and 4 the lowest). It could be for example valued by BSS based on customer order requested priority. The LifeCycleManagementScript information element specifies a script for the service. Describes Service lifecycle event(s) or an external stimulus detected on an orchestrator reference point. Describes Service lifecycle event(s) or an external stimulus detected on an orchestrator reference point. Describes the transition Service lifecycle event(s) that cannot be mapped to any of the enumerated values defined for the event attribute. Includes a Service LCM script (e.g. written in a DSL) triggered to react to one of the events listed in the event attribute. Defines the domain specific language (i.e. the type) of script that is provided. Types of scripts could include bash, python, etc. Array of KVP requirements with the key as the parameter name and the value as the parameter that need to be passed as an input to the script. Note: The scriptInput values are passed to the scripts in addition to the parameters received in the operation invocation request or indicator value change.