Date: Fri, 29 Mar 2024 01:44:41 +0000 (UTC) Message-ID: <1696500960.13121.1711676681866@wiki.mef.net> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_13120_681567096.1711676681864" ------=_Part_13120_681567096.1711676681864 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
The LSO Operational Thread describes the user stories of LSO behavior as= well as the series of interactions among management entities, helping to e= xpress the vision of the LSO capabilities.
High level Operational Threads describe the user stories of LSO behavior= as well as the series of interactions among LSO management entities, helpi= ng to express the vision of the LSO capabilities. The interactions describe= d within each Operational Thread address the detailed involvement of the In= terface Reference Points in the LSO Reference Architecture.
The Service Provider identifies th= e need to introduce a new Product Offering. The requirements of the new Pro= duct Offering are determined and associated Product Specifications defining= the product details are created. The Product Offering is mapped into the s= upporting Service Specifications. New Service Specifications are also creat= ed if needed. The Product Offering is added to the Product Catalog and made= available for potential Customers.
The Service Provider begins a busi= ness relationship with Partner providers. The Product Offering capabilities= of each Partner are shared with the Service Provider, along with any assoc= iated billing information and quality objectives. Rules guiding the busines= s arrangement with the Partner may be codified within Policies. The Service= Provider may also map Service Specifications for Service Components to the= Product Offerings available from the Partner.
This Operational Thread addresses = the orchestration of activities associated with product ordering and servic= e activation within LSO for a Connectivity Service within the Provider doma= in and also addressing any Partner domain provided portion of the Product I= nstance. The Customer browses the Product Catalog and selects a Product Off= ering to order. LSO fulfills the order by selecting, assigning, configuring= and activating the appropriate Services and associated resources that supp= ort the ordered Product Instance. Service activation testing may be perform= ed to verify proper configuration.
The Customer initiates a request t= o dynamic control a permitted aspect of its Service (e.g. bandwidth change = or implementing traffic filtering controls, etc.). In the Service Provider = domain, LSO uses the defined service constraints and policies to determine = if the dynamic control request is permitted. If the dynamic control request= needs to be supported by a Service Component within a Partner domain, LSO = coordinates the changes needed to support the request with the Partner. In = addition, LSO effects the necessary changes within its own domain to servic= e the request. The Customer is also informed about the status of the reques= t.
The Customer wishes to view perfor= mance and fault information related to its Product Instances and associated= Services. In the Service Provider domain, LSO may receive fault and perfor= mance related information about each Service Component. This information is= used to determine the overall performance and status associated with the C= ustomer=E2=80=99s Services and Product Instances. LSO gathers the informati= on requested by the Customer and assembles it into a report. The Customer m= ay also request that reports be generated on a scheduled or exception basis= .
Trouble Reports related with the C= ustomer=E2=80=99s Product Instances and Services may be placed by the Custo= mer. In the Service Provider, LSO gathers and uses trouble and fault inform= ation related to the Customer=E2=80=99s Product Instances and Services and = associates it to the Trouble Report. LSO would also attempt to remedy the r= eported trouble by reconfiguring, reassigning, and / or rerouting aspects o= f the Service. LSO also indicates if manual intervention is required to res= olve the trouble, and tracks the status of any associated repair activities= to help determine trouble resolution status. The status of trouble resolut= ion is reported back to the Customer.
The Service Provider needs to dete= rmine if the SLS for a Service is being met. Service quality is analyzed by= gathering the necessary service performance related measurement and compar= ing these service performance metrics with the service quality objectives d= escribed in the SLS.
The Service Provider gathers relev= ant usage measurements and usage events in order to generate and provide a = bill to the Customer. LSO collects usage measurements, traffic measurements= , and service-related usage events (e.g., customer initiated changes in ser= vice bandwidth, etc.) describing the usage of Service Components and associ= ated resources. This information is correlated to specific Services and Pro= duct Instances. The appropriate business applications perform rating and bi= lling based on the usage information and business rules. Where Service Comp= onents have been used beyond their SLS commitments, exception reports may b= e generated. Note: Partner domains may also be involved in reporting usage = and generation of billing information.
The Service Provider needs to prov= ide security for its management and control mechanisms. In this Operational= Thread, LSO manages controlled access to management and control capabiliti= es, including authentication, authorization, and auditing within LSO and wi= th Partner and Customer domains.
The Customer Application Coordinat= or in the Customer domain manages the various service needs of the cloud ba= sed applications it is supporting. It may determine that additional capacit= y is needed between two data centers in order to provide for the demands of= the applications. The Customer Application Coordinator interacts with the = Service Provider to control the bandwidth of the Connectivity Services betw= een these two data centers.
DRAFT<= /p>