Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TS 26.501  Word version:  17.3.0

Top   Top   Up   Prev   Next
1…   4…   4.2…   4.2.2…   4.3…   4.5…   4.6…   4.7…   5…   5.2…   5.3…   5.3.2   5.4…   5.5…   5.5.3…   5.6…   5.7…   5.7.3   5.7.4…   5.8   5.9…   5.10…   5.10.5   5.10.6   5.11…   6…   6.3…   6.5…   6.8   7…   8…   8.2   A…   A.3…   A.5…   A.7…   A.9   B…   B.3   C…   C.3   C.4   C.5   D…

 

4.5  5G Media Streaming architecture extensions for Edge Computing |R17|p. 27

4.5.1  Introductionp. 27

This clause defines an architecture that enables a 5GMS Application Provider to provision resources in the Edge DN for an application through the M1 interface by configuring an edge processing resource template.
Media processing in the edge may be achieved in one of two different ways at the application layer:
  1. Client-driven management. 5GMS-Aware Applications that are aware of the edge processing can directly request an edge resource and discover the EAS that is best suited to serve the application.
  2. AF-driven management. The 5GMS AF automatically allocates edge resources for new media streaming sessions on behalf of the application using information in the 5GMS Provisioning Session.
    An Edge-enabled 5GMS Client as defined in this clause leverages the SA6 Edge Computing capabilities defined in TS 23.558. Other realizations are possible, but are outside the scope of the present document.
Up

4.5.2  Extended 5GMS Architecture for Edge Computingp. 27

The 5GMS architecture is extended to add support for media processing in the edge. The extended architecture is an integration of the 5GMS architecture defined in the present document with the architecture for enabling Edge Applications defined in TS 23.558, and the Edge Computing management architecture defined in TS 28.538. The extended architecture is depicted in Figure 4.5.2-1.
Copy of original 3GPP image for 3GPP TS 26.501, Fig. 4.5.2-1: Reference edge-enabled 5GMS media architecture
Up
Based on the extended architecture, the following assumptions shall apply:
  1. A 5GMS AF that is edge-enabled shall support EES functionality including:
    • EDGE-1 API for supporting registration and provisioning of EEC functions, and discovery by them of EAS instances.
    • EDGE-3 API towards the EAS function of 5GMS AS instances.
    • EDGE-6 API for registering with an ECS function.
    • EDGE-9 API for media session relocation.
  2. A 5GMS AF that is edge-enabled shall be capable of determining (using information in the 5GMS Provisioning Session) whether a media streaming session meets the eligibility criteria for using edge resources.
  3. A 5GMS AF that is edge-enabled may perform compute resource allocation using the MnS-C interface.
  4. A 5GMS AS that is edge-enabled shall support EAS functionality including the EDGE-3 API for registration with the EES.
  5. A Media Session Handler that is edge-enabled should support EEC functionality including:
    • Invoking the EES function using the EDGE-1 API.
    • Invoking the ECS function using the EDGE-4 API.
    • EDGE-5 API exposed to the Application Client.
  6. A 5GMS-Aware Application that is edge-enabled shall support Application Client functionality and should invoke the ECS function using the EDGE-5 API.
The extended 5GMS architecture supports both client-driven as well as AF-driven management of the edge processing session.
The 5GMS Application Provider may request the deployment of edge resources as part of the Provisioning Session.
  • In the client-driven approach, the 5GMS-Aware Application and/or the Media Session Handler cover and locate a suitable 5GMS AS instance in the Edge DN.is aware of the support of edge processing in the network and takes steps, such as using the EDGE-5 APIs, to discover and locate a suitable 5GMS AS instance in the Edge DN.
  • In the AF-driven approach, the 5GMS Application Provider configures the 5GMS AF to automatically deploy edge processing for the media sessions of the corresponding Provisioning Session based on the provisioned edge processing resource template. The 5GMS-Aware Application may not be aware of the edge deployment and the EAS is discovered through other means, such as DNS resolution with support from the EASDF as specified in TS 23.548.
Up

4.5.3  Provisioning and Service Informationp. 28

The provisioning step allows a 5GMS Application Provider to configure information about its edge processing requirements for media streaming sessions.
The following information shall be configurable by the 5GMS Application Provider over reference point M1:
  • Condition for activation of edge processing, e.g. the traffic descriptors, application identifier, geographic location of the UE, etc.
  • Selection of client-driven or AF-driven management.
  • EAS profile information for each EAS that will serve the application, such as the service KPIs, geographical location, and service continuity support. The EAS profile is defined in clause 8.2.4 of TS 23.558.
  • Application context relocation tolerance and requirements.
For client-driven edge processing, an edge-enabled 5GMS AF shall support sharing any required configuration information about edge processing with the Media Session Handler through Service Access Information at reference point M5, and the EEC embedded in the Media Session Handler shall support processing this configuration information. This enables the EEC embedded in the Media Session Handler to request edge processing for a streaming session from the EES embedded in the 5GMS AF, realising reference point EDGE-1.
Up

4.5.4  Edge application context for 5GMS functionsp. 29

4.5.4.1  5GMS AF contextp. 29

The following application state may be subject to transfer during the application context relocation of an edge-deployed 5GMS AF instance:
  • The EEC context maintained by the EES, as defined in clause 8.2.8 of TS 23.558.
  • The session context maintained by the 5GMS AF, including the currently selected dynamic QoS and charging policy, any associated event subscriptions, the associated edge configuration, the consumption reporting configuration, QoE reporting configuration.
  • Other internal context information such as traffic identification and steering information to support dynamic QoS and charging policies, history of network assistance and dynamic policy.
Up

4.5.4.2  5GMS AS contextp. 29

The following application state may be subject to transfer during the application context relocation of an edge-deployed 5GMS AS instance:
  • The media stream context maintained by the 5GMS AS, which includes configuration for uplink streaming endpoint, remote control configuration, any collected QoE reports.

Up   Top   ToC