5.3 Provisioning Session for Media Streaming
26.5013GPP5G Media Streaming (5GMS)General description and architectureRelease 18TS
5.3.1 Domain model
The M1d baseline domain model is depicted in Figure 5.3.1-1 overleaf. It consists of a Provisioning Session, which contains at least one of the following:
– A Content Hosting Configuration,
– A Consumption Reporting Configuration which defines consumption measurement, logging, collection and reporting functionality,
– A Policy Template,
– A Metrics Reporting Configuration which defines QoE metrics measurement, logging, collection and reporting functionality,
– An Edge Resources Configuration specifying the requirements for edge processing as defined in TS 23.548 [15] and TS 23.558 [16] in support of the Provisioning Session, including eligibility criteria that indicate the circumstances in which edge computing is to be used for Media Streaming sessions associated with this Provisioning Session and parameters indicating the tolerance of the application for relocation of the Edge AS, or
– An Event Data Processing Configuration which contains data manipulation instructions to be performed on UE data by the Data Collection AF including, but not limited to, reporting format conversion, data normalisation, domain-specific anonymisation of data and (dis)aggregation of data into exposed events. This entity includes one or more Data Access Profiles, each one defining a specific access level for controlling the event information exposed to an event consumer.
Each Provisioning Session is uniquely identified within the 5GMS System by a Provisioning Session identifier.
When a certain 5GMS feature is selected, the 5GMSd AF compiles the resulting Service Access Information so that the 5GMSd Client can access the services via M4d and/or M5d.
Figure 5.3.1-1: M1d provisioning domain model
5.3.2 Baseline provisioning procedure
The present clause describes the baseline procedure to provision the features using the 5GMS System.
NOTE 1: SLA negotiations between the 5GMSd Application Provider and the 5GMS System provider are outside the scope of the present specification and are included in the figure below for illustrative purposes only.
Figure 5.3.2-1: High Level Procedure for provisioning the 5GMS System for downlink streaming sessions
Steps:
1. The 5GMSd Application Provider discovers the address (URL) of the 5GMSd AF (M1d) for Session Provisioning.
2. The 5GMSd Application Provider authenticates itself with the system. This procedure reuses existing authentication/authorization procedures, e.g. as defined for CAPIF [13].
3. The 5GMSd Application Provider creates a Provisioning Session, providing its 5GMSd Application Provider identifier as input. 5GMSd Application Provider queries the capabilities and authorized features.
4. The 5GMSd Application Provider specifies one or more 5GMSd features in the Provisioning Session. A set of authorized features is activated, such as content consumption measurement, logging, collection and reporting; QoE metrics measurement, logging, collection and reporting; dynamic policy; network assistance; and content hosting (including ingest).
When the content hosting feature is offered and selected, the 5GMS Application Provider configures the content hosting behaviour of the 5GMSd AS. This Content Hosting Configuration is specified in clause 5.4 and includes selecting the ingest protocol and format, caching and proxying of media objects, content preparation, access protection (e.g. URL signing) and indicating a target distribution area (e.g. through geofencing).
When the dynamic policy feature is offered and selected, the 5GMSd Application Provider specifies a set of policies which can be invoked for the unicast downlink streaming session. The UE becomes aware of the selected policies in the form of a list of valid Policy Template Ids.
When the content consumption measurement, logging, collection and reporting feature is offered and selected, the 5GMSd Application Provider indicates the desired reporting interval. When the 5GMSd Application Provider has delegated Service Access Information handling to the 5GMS System, then location reporting is also selected or de-selected.
When the QoE metrics measurement, logging, collection and reporting feature is offered and selected, the 5GMSd Application Provider provides configuration input on the QoE post processing. When the 5GMSd Application Provider has delegated Service Access Information handling to the 5GMS System, then more detailed metrics reporting is configured.
When the edge computing feature is offered and selected, the 5GMSd Application Provider provides one or more Edge Resources Configurations that can be used to support either client-driven management or Application Provider-driven management of edge resources associated with the Provisioning Session.
When the event data processing feature is offered and selected, the 5GMSd Application Provider provides one or more Event Data Processing Configurations that determine how, in the scope of the Provisioning Session, content consumption and QoE metrics collected from the UE and application logs collected from the 5GMSd AS are processed into events and exposed to subscribers.
5. When content hosting is desired, the 5GMSd AF interacts with the 5GMSd AS to allocate M2d resources and configure the ingest format. Then the 5GMSd AS responds with the M2d address. The 5GMSd AF selects the desired ingest format.
6. The 5GMSd AF compiles the Service Access Information. The Service Access Information contains access details and options such as the Provisioning Session identifier, M5d (Media Session Handling) addresses for content consumption reporting, QoE metrics reporting, dynamic policy, network assistance, etc. When content hosting is offered and has been selected in step 4, then also M4d (Media Streaming) information such as the DASH MPD is included.
7. The 5GMSd AF provides the results to the 5GMSd Application Provider.
a. When the 5GMSd Application Provider has selected full Service Access Information, then the results are provided in the form of addresses and configurations for M2d (Ingest), M5d (Media Session Handling) and M4d (Media Streaming).
b. When the 5GMSd Application Provider delegated the service access information handling to the 5GMS System, then a reference to the Service Access Information (e.g. an URL) is provided. The Media Session Handler fetches the full Service Access Information later from the 5GMSd AF.
8. When content hosting is offered and has been selected in step 4, the 5GMSd Application Provider can start supplying content at the M2d ingest interface. In the case of progressive download or on-demand DASH sessions, the 5GMSd Application Provider makes the content assets available. In the case of Live DASH streaming sessions, the 5GMSd Application Provider starts supplying the live content.
9. The 5GMSd Application Provider executes Service Announcement and updates the UEs (during the lifetime of the Provisioning Session).
Optional:
10. The 5GMSd Application Provider may update the Provisioning Session.
Depending on the parameters of the Provisioning Session:
11. The 5GMSd AF may send event-related or periodic notifications to the 5GMSd Application Provider.
According to schedule, or upon request:
12. The 5GMSd Application Provider may manually terminate the Provisioning Session (at any time). All associated resources are released. Content may be removed from the 5GMSd AS. The 5GMSd Application Provider may configure a schedule for Provisioning Session termination.
13. The 5GMSd AF sends a notification upon Provisioning Session termination.
The 5GMSd AF may request the creation or reuse of one or more network slices for distributing the content of the provisioned session. If more than one network slice is provisioned for the distribution of the content of a session, the list of allowed S‑NSSAIs shall be conveyed to the target UEs (e.g. through URSP or through M5d or M8d).
NOTE 2: The 5GMSd AS(s) serving the content are only accessible through the DNN(s) used by the network slice(s) provisioned for the distribution of that content.