NSST (Network Slice Subnet Template)

sbnd f

dbfb

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 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) 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. Reference to an ETSI NFV IFA014 Network Service Descriptor which will be used to model an ETSI Network Service. The resource(s) described in the NSD are not described in the Service Descriptor. ServiceInstance is used to model the run time representation 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”. 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 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 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.