Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TS 26.512  Word version:  18.2.1

Top   Top   Up   Prev   Next
1…   4…   4.4…   5…   6…   11…   A…

 

5  Procedures for Uplink Media streamingp. 50

5.1  Generalp. 50

Uplink media streaming functional entities in the 5GMS System include the 5GMSu Application Provider, 5GMSu AF, 5GMSu AS and the UE. To make use of these other entities, the UE includes a 5GMSu-Aware Application that is provided by the 5GMSu Application Provider and a 5GMSu Client comprising the Media Session Handler and the Media Streamer.
The M1 Provisioning API enables the 5GMSu Application Provider to establish and manage the uplink media session handling and streaming options of the 5GMSu System.
The content egest interface at reference point M2u enables uplink media streaming content that has been sent by the 5GMSu Client to the 5GMSu AS at reference point M4u to be subsequently delivered to the 5GMSu Application Provider. Uplink media streaming media transfer from the 5GMSu AS to the 5GMSu Application Provider may be either pull-based and initiated by the 5GMSu Application Provider using the HTTP GET method, or push-based and initiated by the 5GMSu AS using the HTTP PUT method. The 5GMSu Application Provider's target endpoint for push-based streaming content delivery at reference point M2u is provided to the 5GMSu AF as part of the M1 Provisioning Session and this is passed to the 5GMSu AS as part of the M3u configuration procedures.
The 5GMSu AF, having been successfully provisioned at reference point M1u, sets up corresponding resources at a reference point M5u endpoint from which Service Access Information for uplink media streaming session management, metrics reporting, network assistance and request for policy and/or charging treatment may be retrieved using its provisioned external application identifier. Certain types of configuration and policy information accessed over reference point M5u by the Media Session Handler, such as uplink metrics reporting, QoS policy, or support for AF-based network assistance are further passed to the Media Streamer via the M7u API.
The 5GMSu-Aware Application initiates a new uplink media streaming session by launching the Media Stream Handler at reference point M6u using a 3GPP Service URL for 5GMS (see clause 4.8.3). The 3GPP Service URL indicates the external application identifier. This may be used to retrieve Service Access Information from the 5GMSu AF at reference point M5. Alternatively, if the 5GMSu-Aware Application has already acquired all necessary Service Access Information via private means at reference point M8, this may be supplied directly to the Media Session Handler at reference point M6u as additional parameters.
Based on a request from the 5GMSu-Aware Application or from the Media Streamer received over the M6u API, and based on the Service Access Information acquired from the 5GMSu AF via reference point M5u, the Media Session Handler sets up an uplink media streaming session with a unique media delivery session identifier. Upon successful session establishment, the Media Session Handler triggers the Media Streamer to begin uplink media streaming of media content to the 5GMSu AS over reference point M4u.
Subscription to status and other event notification services is offered by the Media Session Handler to the 5GMSu-Aware Application and to the Media Streamer via the UE media session handling APIs exposed by the Media Session Handler at reference point M6u.
Subscription to status and other event notification services is also offered by the Media Streamer to the 5GMSu-Aware Application and to the Media Session Handler via the UE media stream handling APIs exposed by the Media Player at reference point M11u.
Up

5.2  APIs relevant to Uplink Media Streamingp. 51

Table 5.2-1 summarises the APIs used to provision and use the various uplink media streaming features specified in TS 26.501.
5GMSu feature Abstract Relevant APIs
Interface API name Clause
Content protocols discoveryUsed by the 5GMSu Application Provider to query which content egest protocols are supported by 5GMSu AS(s).M1uContent Protocols Discovery API 7.5
Content publishingContent is contributed to the 5GMSu AS and published to 5GMSu Application Providers according to a Content Publishing Configuration associated with a Provisioning Session.M1uProvisioning Sessions API 7.2
Server Certificates Provisioning API 7.3
Content Preparation Templates Provisioning API 7.4
Content Publication Provisioning API 7.12
M2uHTTP pull-based content egest protocol 8.5
DASH-IF push-based content egest protocol 8.6
HTTP low-latency pull-based content egest protocol 8.7
M3uServer Certificates configuration API 9.2
Content Preparation Templates configuration API 9.3
Content Publication configuration API 9.5
M4u MPEG-DASH [4] or 3GP-DASH [37] 10
M5uService Access Information API 11.2
Metrics reportingThe 5GMSu Client uploads metrics reports to the 5GMSu AF according to a provisioned Metrics Reporting Configuration it obtains from the Service Access Information for its Provisioning Session.M1uProvisioning Sessions API 7.2
Metrics Reporting Provisioning API 7.8
M5uService Access Information API 11.2
Metrics Reporting API 11.4
Dynamic Policy invocationThe 5GMSu Client activates different traffic treatment policies selected from a set of Policy Templates configured in its Provisioning Session.M1uProvisioning Sessions API 7.2
Policy Templates Provisioning API 7.9
M5uService Access Information API 11.2
Dynamic Policies API 11.5
Network AssistanceThe 5GMSu Client requests bit rate recommendations and delivery boosts from the 5GMSu AF.M5uService Access Information API 11.2
Network Assistance API 11.6
Edge content processingEdge resources are provisioned for processing content in 5GMS uplink media streaming sessions.M1uProvisioning Sessions API 7.2
Edge Resources Provisioning API 7.10
M5uService Access Information API 11.2
UE data collection, reporting and exposureUE data related to uplink 5G Media Streaming is reported to the Data Collection AF instantiated in the 5GMSu AF for exposure to Event consumers.M1uEvent Data processing Provisioning API 7.11
R4Ndcaf_DataReporting service 17
R5, R6Naf_EventExposure service 18
Up

Up   Top   ToC