...
Question (Peter L): Why would these terms be misleading? Why could not the RAN and CN components relate to two separate PLMNs? If we do not discriminate based on PLMN it will become much harder to find RAN products to use to demonstrate this UC. Could you please suggest an alternative for which there exists support in at least some existing RAN and CN implementation?
Comment: (Vladimir Y.) Here is the list:
1. PLMN-ID in 3GPP is not used to identify the slice (certainly it is used to identify the PLMN)
3GPP did not develop (yet?) the concept of how two slice instances can relate to two different PLMNs. I personally like this idea, but ...
2. "Existing CN" and "new CN" literally mean that there are two Core Networks. Probably the point is that there are two NSSIs that consist of CN NFs.
3. "It is known from ONAP R1 how to instantiate and deploy a minimal viable CN" - probably means that R1 ONAP will have sufficient functionality to support deployment of 3GPP Core Network. If this is the statement, it needs some explanation. For example, probably LCM of VNFs will be supported. The LCM of NSs (in terms of ETSI NFV) - I don't know; will appreciate reference that confirms. Same question about support of signaling transfer, about OAM functionality. Many questions probably cannot be answered simply because R1 is not sufficiently documented.
4. Use of VLAN tagging on backhaul connections needs at least explanation or reference. VLAN tagging after all is a LAN technique while backhaul typically is WAN.
5. Relation between slicing support and RAN sharing is not defined in 3GPP. There is a reference in 28.801 to RAN sharing as an example of B2B2X type of service, but relation of that to slicing is not defined.
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.
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.
...