...
A service is the business entity that connects properties of the intended function with guaranties (SLA) and other business-related concepts. The term “service” and "service instance" is used interchangeable in the literature – sometimes to denote the blue-print or descriptor for how to create instances of that service, and sometimes to denote a particular instance (the word “instance” is simply omitted).
Comment: (Vladimir Y.) There is no definition of service in 28.801v1.3.0. So this is a new definition which is not really in the scope. Suggest to remove this part.
Comment (Peter): In both the 1.3.0 and 2.0.1 the sections 4.7 (High-level functional model of business roles) and 4.8 (Types of communication services) attempts at providing some notion of what a "service" can be, including specializations such as a "communication service". My current proposal summary is that we use the word "service" to mean the buisiness agreement, and use other words for describing the realization or implementation of such a service (such as the NSI, NSSI or NFs, or even fractions of a NF...)
A service instance is realized by one or more network slice instances (NSIs), that in turn may consits of network slice subnet instances (NSSIs).
Comment: (Vladimir Y.) Being an active contributor to 28.801, I'd agree that there were attempts to provide some notion of what a "service" can be e.g. classification of services, such as B2B, B2C etc. However there is no definition of service. My point is that this group is not right place to develop such definition. It's a business of 3GPP, and we are here not to fill the gaps left in 3GPP specifications.
Comment (Vladimir Y.) The definition of NSSI in 28.801 is different: includes recurrence.
A network slice subnet instance (NSSI) constituent may include NF(s) and other NSSI(s).
Comment (Vladimir Y.) How is the right hand side of the diagram relevant to the document?
Peter: It's an overview of the management layers described in section 4.10, and I included it in anticipation of a need to relate to these 3GPP specified management functions and their interfaces in our ONAP based realization. If we need it while writing this use case is yet to be decided...
Comment (Vladimir Y.) These are not "layers", simply interconnection between CSMF, NSMF and NSSMF which is not that important. If we want to address these functions in ONAP, some text is needed saying exactly that.
| Gliffy Diagram | ||||||
|---|---|---|---|---|---|---|
|
...