...
I can continue, but prefer to stop at this point. I think we should follow the concepts clearly defined and agreed in the relevant SDOs. It would be bad idea to deviate from 3GPP / NGMN definitions and/or invent our own definitions.
(Peter L) The point here is not to invent any new definitions at all - the point is to describe a slice related management use case using the RAN, CN and TN technologies we already have, in order to expand the capabilities of ONAP (or show that they are already sufficient). We are not here to develop the CN, TN or RAN, right?
However, as ONAP has a slightly different structure and functional composition than what is described by NGNM or 3GPP, we effectively do work with ONAP specific definitions in some management areas.
Gliffy name Cell Planning
Comment: (Vladimir Y.) The text under the figure says that the blue cells are shared between NSSI RAN1 and RAN2. On the figure itself, blue is marked as RAN1 and red as RAN2, i.e. blue is not shared between RAN1 and RAN2. Which one is right?
Goal for this Use Case:
To show that ONAP can be used to desgn and deploy the Service 2 in a new CN and selected portion of a RAN currently providing Service 1 using NSI A, see Figure 1 and Figure 2.
...