Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TR 23.700-49  Word version:  19.0.0

Top   Top   None   None   Next
1…   5…

 

1  Scopep. 9

The present document describes key issues and solutions for the phase 3 of the system enhancements for Edge Computing in 5GS.
This technical report will document the study of potential system enhancements for enhanced edge computing support, including:
  • Whether and how to support more efficient Edge Hosting Environment information management and related EAS Discovery:
    • Handle the edge network and EAS related information (e.g. UPF and EAS deployment information, DNAIs) locally with less impact to 5GC central NFs (e.g. central SMF) to address more flexible EAS (re)discovery/(re)selection, local UPF (re)selection.
    • Whether and how to take into account N6 Delay between the local PSA and EAS for local UPF and EAS (re)selection.
  • Whether and how to support traffic sent to/from PSA after being processed by Edge Hosting Environment, e.g. when there is no communication possibility between the local part of the DN and central part of the DN (e.g. due to usage of private IP address, lack of secure tunnel); whether and how to support traffic being routed between two EASs located in two different Edge Environments when there is no pre-established communication path between the two local part of the DNs.
Up

2  Referencesp. 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)".
[3]
TS 23.502: "Procedures for the 5G System (5GS)".
[4]
TS 23.503: "Policy and charging control framework for the 5G System (5GS)".
[5]
TS 23.548: "5G System Enhancements for Edge Computing; Stage 2".
[6]
TS 23.288: "Architecture enhancements for 5G System (5GS) to support network data analytics services".
[7]
RFC 792:  "Internet Control Message Protocol".
[8]
RFC 4443:  "Internet Control Message Protocol (ICMPv6) for the Internet Protocol Version 6 (IPv6) Specification".
[9]
TS 28.538: "Management and orchestration; Edge Computing Management".
[10]
RFC 4656:  "A One-way Active Measurement Protocol (OWAMP)".
[11]
RFC 5357:  "A Two-Way Active Measurement Protocol (TWAMP)".
[12]
RFC 8762:  "Simple Two-Way Active Measurement Protocol".
[13]
RFC 9484:  "Proxying IP in HTTP".
Up

3  Definitions of terms and abbreviationsp. 10

3.1  Termsp. 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  Abbreviationsp. 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 Principlesp. 10

4.1  Architecture Assumptionsp. 10

The architecture in this study should be based on the following assumptions:
  • The existing architecture and procedures for Edge computing as specified in TS 23.501, TS 23.502, TS 23.503 and TS 23.548 are used as baseline for further potential enhancement;
  • Roaming is not considered in this study;
  • The Edge Hosting Environment (EHE) is under the control of the network of serving PLMN or a 3rd party.
Up

4.2  Architectural Requirementsp. 10

The solutions should minimize the impact on the application layer if possible.

Up   Top   ToC