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-62  Word version:  18.0.0

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

 

1  Scope  p. 9

The Technical Report studies on key issue description, solution and conclusion on the support of better integration of UPF into the 5GC SBA. The objectives include:
  • Study UPF event exposure service(s) registration/deregistration, and discovery via the NRF.
  • Study UPF event exposure service(s) that would support, e.g.:
    • Consumption of UPF exposure services by the PCF, NWDAF, CHF, NEF, Trusted AF and other NFs (if needed).
    • (To support the UPF exposure service, if needed) Use of SMF services, PCF services, NWDAF services, CHF services, NEF services, Trusted AF services by the UPF.
    • Relevant Event IDs.
  • Evaluate usage of UPF event exposure service(s) as defined in WT#2 also considering the architectural impacts.
This study shall maintain the Rel-17 backward compatibility on the N3, N6, N9, N4 interfaces.
Up

2  References  p. 9

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: "Policy and charging control framework for the 5G System (5GS); Stage 2".
[5]
TS 23.288: "Architecture enhancements for 5G System (5GS) to support network data analytics services".
[6]
TS 29.510: "Network Function Repository Services; Stage 3".
[7]
TS 23.548: "5G System Enhancements for Edge Computing; Stage 2".
[8]
TS 29.244: "Interface between the Control Plane and the User Plane nodes".
[9]
TS 29.514: "5G System; Policy Authorization Service; Stage 3".
[10]
TR 23.700-48: "5G System Enhancements for Edge Computing".
[11]
TS 24.519: " Time-Sensitive Networking (TSN) Application Function (AF) to Device-Side TSN Translator (DS-TT) and Network-Side TSN Translator (NW-TT) protocol aspects, Stage 3".
Up

3  Definitions of terms, symbols and abbreviations  p. 10

3.1  Terms  p. 10

For the purposes of the present document, the terms 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.

3.2  Symbols  p. 10

For the purposes of the present document, the following symbols apply:

3.3  Abbreviations  p. 10

For the purposes of the present document, the abbreviations given in TR 21.905 and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905.

4  Architectural Assumptions and Requirements  p. 10

4.1  Architectural Assumptions  p. 10

The architecture and framework as specified in TS 23.501, TS 23.502, and TS 23.503 are regarded as the baseline for the present study:
  • The SMF is responsible for controlling UPF packet processing.
  • The UPF can only expose 5GC information which is originated in the UPF.

4.2  Architectural Requirements  p. 10

Solutions shall build on the 5G System architectural principles as in TS 23.501, including flexibility and modularity for newly introduced functionalities:
  • The performance of UPF user plane traffic handling shall not be degraded due to mechanisms defined in this study.
  • The Rel-18 N6, N4 interface shall be based on the existing interface design and backward compatible. No impact is introduced on N3, N9 interfaces from this study.
  • The usage of direct UPF event exposure for exposure of some data when these data are already available via usage of SMF + N4 needs to be justified.
  • Some aspects as following should be considered when the solution evaluation is proposed:
  • The co-existence for the UPF supporting UPEAS feature and UPF supporting Rel-17 (i.e. not supporting the feature) should be considered.
Up

Up   Top   ToC