Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TR 23.700-48  Word version:  18.0.0

Top   Top   None   None   Next
1…   5…

 

1  Scopep. 12

The present document describes key issues and solutions for the phase 2 of the system enhancements for Edge Computing in 5GS.
Edge Computing is supported in 5GS since Rel-15. During Rel-17 FS_enh_EC study described in TR 23.748, further enhancements for supporting Edge Computing have been studied, including discovery and re-discovery of EAS, edge relocation etc. 4 key issues from FS_enh_EC study have been concluded and progressed in TS 23.548. Some other issues were raised during the Rel-17 study but not studied due to the time limitation in Rel-17.
This technical report will document the study of potential system enhancements for enhanced edge computing support, including:
  • improvements to roaming, to support access to EHE in a VPLMN (WT#1);
  • defining use cases that may benefit from exposure of additional data via the Local UPF/NEF including describing (on a high level) the characteristics of the data and data delivery to fulfil the use cases; investigating the solutions and their feasibility and suitability for improved network exposure of UE traffic related information to common Edge Application Server via Local UPF/NEF, such as network congestion status (WT#3);
  • investigating the potential need and solutions for supporting offload policies to match more granular sets of UE(s) without exposing operator-internal configurations to 3rd party AFs (WT#5);
  • investigating the potential need and solutions to influence of PSA-UPF and EAS (re)location for collection of UEs, e.g. in scenarios when UE(s) should use the same EAS and are not members of a pre-defined group (WT#6);
  • investigating potential impacts related to the GSMA Operator Platform Group work, and potential improvements related with 5GC and EHE being operated by different organizations (WT#7);
  • investigating the potential need and solutions to avoid the UE to switch the EC traffic away from the EC PDU Session and 5GS altogether, due to conflicting connectivity preferences in the device (e.g. via means outside of 3GPP connectivity, e.g. non-integrated Wifi) (WT#8);
  • investigating the potential solutions for the AF to be able to obtain/determine the DNAI that is associated to a certain selected EAS, for subsequent use with already defined services provided to the AF (WT#9).
Up

2  Referencesp. 12

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)".
[3]
TS 23.548: "5G System Enhancements for Edge Computing; Stage 2".
[4]
TR 23.748: "Study on enhancement of support for Edge Computing in 5G Core network (5GC)".
[5]
[6]
SP-210583: "Reply LS to GSMA Operator Platform Group on edge computing definition and integration", SA#92e.
[7]
RFC 5681:  "TCP Congestion Control".
[8]
TS 26.247: "Transparent end-to-end Packet-switched Streaming Service (PSS); Progressive Download and Dynamic Adaptive Streaming over HTTP (3GP-DASH)".
[9]
TS 23.502: "Procedures for the 5G System (5GS)".
[10]
TR 23.700-85: "Study on enhancement of 5G User Equipment (UE) policy".
→ to date, still a draft
[11]
TS 24.526: "User Equipment (UE) policies for 5G System (5GS); Stage 3".
[12]
TS 23.122: "Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode".
[13]
TS 23.503: "Policy and charging control framework for the 5G System (5GS)".
[14]
TS 38.415: "NG-RAN; PDU session user plane protocol".
[15]
TS 38.413: "NG-RAN; NG Application Protocol (NGAP)".
[16]
TS 23.003: "Numbering, addressing and identification".
[17]
TS 29.519: "Usage of the Unified Data Repository Service for Policy Data, Application Data and Structured Data for Exposure".
[18]
TS 29.503: "Unified Data Management Services".
[19]
TS 23.288: "Architecture enhancements for 5G System (5GS) to support network data analytics services".
[20]
S2-2203633: "LS on UPF selection based on DNAI", SA2#151e.
[21]
TR 23.700-60: "Study on XR (Extended Reality) and media services".
Up

3  Definitions of terms, symbols and abbreviationsp. 13

3.1  Termsp. 13

For the purposes of the present document, the terms given in TR 21.905, TS 23.501, TS 23.548 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.2Void

3.3  Abbreviationsp. 14

For the purposes of the present document, the abbreviations given in TR 21.905, TS 23.501, TS 23.548 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.
EACI
ECS Address Configuration Information
EDI
Edge Deployment Information
Up

4  Architectural assumptions and principlesp. 14

4.1  Architectural Assumptionsp. 14

Existing solutions defined in Rel-15, Rel-16 and Rel-17 will be considered as baseline in this study.
The architecture for support of Edge Computing in 5GC shall be based on the following architecture assumptions:
  • the architecture for Edge computing specified in Release 17 is used as basis for further potential enhancement;
  • the Edge Hosting Environment (EHE) can be under the control of the serving network operator or a 3rd party;
  • interconnectivity between EHEs of different operators cannot be assumed to be available for all deployments.
Up

4.2  Architectural Requirementsp. 14

  • The solutions should minimize the impact on the application layer.

Up   Top   ToC