Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Comment: (Vladimir Y.) Some of terms and concepts used in the text below are not defined in 3GPP or assume too specific implementation or cannot be easily interpreted (marked by red). They should be replaced with terms / concepts defined in 3GPP and/or generalized. The terms "PLMN" and the label "PLMN-ID" are misleading as slice instances and their RAN or CN components are not separated PLMNs

Question (Peter L): Why would these terms be misleading? Why could not the RAN and CN cmponents 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?

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.

...