Versions Compared

Old Version 10

changes.mady.by.user Borislav Glozman

Saved on

compared with

New Version Current

changes.mady.by.user Priyadharshini B

Saved on

Key

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

...

  1. RAN NFs are assumed to be instantiated apriori. So in case of RAN NSSI creation, the step involving RAN NF instantiation shall be skipped.

  2. RAN NSST will be a nested service composing RAN-NF NSST, TN-FH and TN-MH NSSTs. This shall be revisited beyond Guilin

5. Transport Slicing

  1. FH and MH NSST and Slice Profile attributes shall be simply the same as BH attributes for G-release.

  2. Transport NSSMF shall always be invoked via the NSSMF adaptor (whether it is called by NSMF or RAN NSSMF).

  3. The endpoints for connecting RAN and Core (i.e., BH) shall be configured via UUI and provided to TN NSSMF. The endpoints for FH and MH are assumed to be not needed (i.e., pre-configured) because RAN NFs are already instantiated in the preparation phase.

...