Tech-invite  3GPPspace  IETFspace
21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x

Content for  TR 23.700-63  Word version:  19.0.0

Top   Top   None   None   Next
1…   5… 
1 Scope  2 References  3 Definitions of terms and abbreviations  3.1 Terms  3.2 Abbreviations  4 Architectural Assumptions and Requirements  4.1 Architectural Assumptions  4.2 Architectural Requirements 
...

 

1  Scope  p. 7

This Technical Report continues the study on key issue description, solution and conclusion on UPF enhancement for Exposure and SBA Phase 2.
The scopes include the following aspects:
  • Study potential enhancements on UPF selection to discover UPF with specific user plane functionalities, e.g. NAT, Packet inspection, etc.;
  • Study potential enhancements on UPF event exposure service to optimize the procedures related to UPF data collection, e.g. direct/indirect subscription of the UPF via control plane from application;
  • Study potential enhancements to support the AF instruction via 5GC to UPF for packet inspection (e.g. UPF detection of certain IP header, HTTP header, etc.) for UL/DL traffic, as well as report collection of the indicated packet inspection from UPF.
Up

2  References  p. 7

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 (5GS); Stage 2".
[3]
TS 23.502: "Procedures for the 5G System; Stage 2".
[4]
TS 23.503: "Policies and Charging control framework for the 5G System; Stage 2".
[5]
TS 29.510: "5G System; Network function repository services; Stage 3".
[6]
TS 29.244: "Interface between the Control Plane and the User Plane nodes".
[7]
TS 23.548: "5G System Enhancements for Edge Computing; Stage 2".
[8]
TS 26.531: "Data Collection and Reporting; General Description and Architecture".
[9]
TS 29.564: "5G System; User Plane Function Services; Stage 3".
[10]
TS 29.500: "5G System; Technical Realization of Service Based Architecture; Stage 3".
[11]
TS 23.288: "Architecture enhancements for 5G System (5GS) to support network data analytics services".
Up

3  Definitions of terms and abbreviations  p. 7

3.1  Terms  p. 7

For the purposes of the present document, the terms given in TR 21.905 and the following apply.

3.2  Abbreviations  p. 8

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

4  Architectural Assumptions and Requirements  p. 8

4.1  Architectural Assumptions  p. 8

  • The architecture and framework as specified in TS 23.501, TS 23.502, and TS 23.503 are regarded as the baseline for this study.
  • User plane architecture changes are outside of scope and user plane architecture as defined in TS 23.501 will be taken as a basis.
  • The functional split in 5GS between UPF and other functional entities remains unchanged.
  • Selection of the UPF for the PDU Session remains an SMF functionality, not replicated in any other NF.
  • Functionalities of other NFs, for example, the NEF functionality to authorize requests from the Application Functions are not replicated in UPF.
Up

4.2  Architectural Requirements  p. 8

The following architectural requirements are applicable to this study:
  • Solutions shall build on the 5G System architectural principles as defined in TS 23.501, including flexibility and modularity for newly introduced functionalities.
  • UPF event exposure service registration/deregistration and discovery as defined in Release-18 will be taken as basis.
  • Indirect subscription of UPF event exposure via SMF can use either PFCP message or SBI interface based on the event type.
  • The performance of UPF user plane traffic handling shall not be degraded due to mechanisms defined in this study.
  • No impact is introduced on N3, N9 interfaces for this study.
  • The N4, N6 interfaces are based on the existing interface design and remain backward compatible.
  • Any new mechanisms compared to the Rel. 18 UPEAS need to be justified.
  • The co-existence for the UPF supporting new functionality included in this study and UPF supporting previous release should be considered.
Up

Up   Top   ToC