Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TR 23.740  Word version:  16.0.0

Top   Top   None   None   Next
1…   5…

 

1  ScopeWord‑p. 7

The scope of this Technical Report is:
  • Identify, prioritize and study the practical non-roaming and roaming deployment scenarios and system impacts when the 5GS is not able to support all possible combination of S-NSSAIs for the UE, and the aspects of mutually exclusive access to Network Slices.
  • Study the possible enhancement for the Network Slicing interworking with EPC for Connected and Idle modes.
  • Study how to provide Network Slice Access authentication and authorization specific for the Network Slice Access authorization that uses User Identities and Credentials different from the 3GPP SUPI and that takes place after the primary authentication which is still required between the UE and the 5GS for PLMN access authorization and authentication.
Up

2  References

The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
  • References are either specific (identified by date of publication, edition number, version number, etc.) or non specific.
  • For a specific reference, subsequent revisions do not apply.
  • For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1]
TR 21.905: "Vocabulary for 3GPP Specifications".
[2]
TS 23.501: "System Architecture for the 5G System; Stage 2".
[3]
TS 23.502: "Procedures for the 5G System; Stage 2".
[4]
TS 23.503: "Policy and Charging Control Framework for the 5G System; Stage 2".
[5]
TS 38.300: "NR and NG-RAN Overall Description; Stage 2".
[6]
TS 33.501: "Security architecture and procedures for 5G system".
[7]
TS 23.682: "Architecture enhancements to facilitate communications with packet data networks and applications".
Up

3  Definitions and abbreviations

3.1  Definitions

For the purposes of the present document, the terms and definitions given in TR 21.905 and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905.
Mutually Exclusive Access to Network Slices:
The access to Network Slices is considered to be mutually exclusive for a UE when their respective S-NSSAIs are both present in the UE's subscription and the UE is prevented from accessing both S-NSSAIs simultaneously.
Up

3.2  AbbreviationsWord‑p. 8

For the purposes of the present document, the abbreviations given in TR 21.905 apply.

4  Architectural Assumptions and Requirements

For Mutually Exclusive Access to Network Slices the following assumptions apply:
  • It is assumed that the support of mutually exclusive access to network slices uses Rel-15 network slicing feature as the baseline.
  • Support of the Mutually Exclusive Access to Network Slices in a PLMN shall not impact Rel-15 5G UEs' behaviour.
  • The network operator shall be able to ensure that the UE is prevented to access Network Slices which are mutually exclusive for that UE.
  • It is assumed that a UE supporting mutually exclusive access to network slices shall be able to operate in a Rel-15 5GS.
  • Rel-16 5G UE and core may support Mutually Exclusive Access to Network Slices.
For interworking for slicing between EPC and 5GC the following assumptions apply:
  • It is assumed that the interworking for slicing between EPC and 5GC uses Rel-15 solution as the basis.
  • The interworking for slicing between EPC and 5GC shall not impact Rel-15 5G UEs behaviour.
  • The system shall support slicing interworking between EPC and 5GC for roaming case when the PGW-C+SMF is Rel-15.
Up

Up   Top   ToC