Content for TS 26.501 Word version: 18.6.0

1… 4… 4.0.6… 4.1… 4.2… 4.2.2… 4.3… 4.4 4.5… 4.6… 4.7… 4.7.4… 4.8 4.9… 4.10… 5… 5.2… 5.2.4 5.2.5… 5.3… 5.3.2… 5.4… 5.5… 5.6… 5.7… 5.7.4… 5.7.8 5.8… 5.10… 5.10.5… 5.10.6… 5.11… 5.12… 5.12.4… 5.12.5… 6… 6.2… 6.2.2.2… 6.2.3… 6.3… 6.4… 6.8… 6.9… 6.9.5… 6.9.7 7… 8… 9… A… A.4… A.8 A.9 A.10 A.11 A.12 A.13 A.14 A.15… A.15.3… B… B.3 C… C.3 C.4 C.5 D… E…

4.7 Data collection, reporting and exposure for 5GMS 4.7.1 Reference architecture instantiation 4.7.2 UE data reporting for 5GMS 4.7.2.1 UE data reporting procedures for downlink media streaming 4.7.2.2 UE data reporting procedures for uplink media streaming 4.7.2.3 Common baseline parameters for UE data reporting 4.7.2.4 UE data reporting parameters for media streaming access activity 4.7.2.5 UE data reporting of ANBR-based Network Assistance invocations 4.7.3 UE data processing for 5GMS 4.7.3.1 UE data processing procedures for downlink media streaming 4.7.3.2 UE data processing procedures for uplink media streaming
...

4.7 Data collection, reporting and exposure for 5GMS |R17| p. 49

4.7.1 Reference architecture instantiation p. 49

The abstract data collection and reporting architecture defined in clause 4 of TS 26.531 and depicted in Figure 4.2-1 of TS 26.531 is instantiated in the 5G Media Streaming architecture as shown in Figure 4.7.1-1 and as defined below.

Copy of original 3GPP image for 3GPP TS 26.501, Fig. 4.7.1-1: Data collection and reporting architecture instantiation for 5G Media Streaming

Figure 4.7.1-1: Data collection and reporting architecture instantiation for 5G Media Streaming
(⇒ copy of original 3GPP image)

The functional elements in this instantiation are defined as follows:

The role of the Application Service Provider in the abstract architecture is played by the 5GMS Application Provider.
The Data Collection AF for 5G Media Streaming is instantiated in the 5GMS AF.
The Direct Data Collection Client for 5G Media Streaming is instantiated in the Media Session Handler. This takes logical responsibility for the UE data collection activities of the Metrics Collection & Reporting and Consumption Collection & Reporting subfunctions and the subsequent reporting of this UE data via reference point M5. It also takes logical responsibility for the logging of ANBR-based Network Assistance invocations by the Network Assistance subfunction and their subsequent reporting to the Data Collection AF instantiated in the 5GMS AF via reference point R2.
The Provisioning AF of the Application Service Provider is not instantiated in the 5GMS architecture. Data collection and reporting is instead provisioned using the procedures defined in the present document.
The Indirect Data Collection Client is not instantiated in the 5GMS architecture. Indirect reporting of UE data is outside the scope of 5G Media Streaming.
The role of the AS data collection client in the abstract reference architecture is played by 5GMS AS. This may be deployed as a trusted AS within the 5G System or deployed externally.
The Event Consumer AF is instantiated in the 5GMS Application Provider as a consumer of 5G Media Streaming events from the Data Collection AF.

The reference points as defined as follows in this instantiation:

This reference point is not instantiated in the 5GMS architecture.

Provisioning of data collection and reporting features in the Data Collection AF.

Direct data reporting by the Direct Data Collection Client to the Data Collection AF of ANBR-based Network Assistance invocations.

For the provision of QoE metrics and consumption reports, R2 is instead logically realised by the combination of the following components:

Internal interfaces between the Direct Data Reporting Client and its subordinate functions, namely Metrics Collection & Reporting and Consumption Reporting & Reporting.,
Internal interface between the Media Session Handler and its subordinate Direct Data Collection Client function.
Reference point M5, as defined below.
Internal interface between the 5GMS AF and its subordinate Data Collection AF function.

Direct data reporting by the Direct Data Collection Client to the Data Collection AF, via the Media Session Handler and 5GMS AF.

This reference point is not instantiated in the 5GMS architecture.

Media streaming access reporting by the 5GMS AS to the Data Collection AF.

Event exposure by the Data Collection AF to subscribing NWDAF (TS 23.288) instances.

Event exposure by the Data Collection AF to subscribing Event Consumer AF instances in the 5GMS Application Provider.

This reference point is not instantiated in the 5GMS architecture.

Configuration of 5GMS-related data reporting by the 5GMS-Aware Application.

This reference point is not instantiated in the 5GMS architecture.

4.7.2 UE data reporting for 5GMS p. 50

4.7.2.1 UE data reporting procedures for downlink media streaming p. 50

The following UE data reporting procedures are in scope for the instantiation of the abstract data collection and reporting architecture in the downlink 5GMS architecture:

The procedures defined in clause 5.5 shall be used by the Direct Data Collection Client instantiated in the Media Session Handler to report QoE metrics for downlink media streaming to the Data Collection AF instantiated in the 5GMSd AF.
The procedures defined in clause 5.6 shall be used by the Direct Data Collection Client instantiated in the Media Session Handler to report consumption of downlink media streaming to the Data Collection AF instantiated in the 5GMSd AF.
Invocations of the downlink dynamic policy procedures defined in clause 5.8 shall be logged by the 5GMSd AF and reported to its subordinate Data Collection AF.
Invocations of the AF-based downlink Network Assistance procedures defined in clause 5.9.2 shall be logged by the 5GMSd AF and reported to its subordinate Data Collection AF during active AF-based Network Assistance sessions.
The procedures defined in clauses 5.11.1 and 5.11.2 shall be used by the 5GMSd AS to report downlink media streaming access activity to the Data Collection AF instantiated in the 5GMSd AF via reference point R4. The UE data reports in this case shall include the parameters defined in clause 4.7.2.4.
The procedures defined in clauses 5.11.2A and 5.11.2B shall be used by the Direct Data Collection Client instantiated in the Media Session Handler to report invocations of the ANBR-based downlink Network Assistance procedures to the Data Collection AF instantiated in the 5GMSd AF via reference point R2. The UE data reports in this case shall include the parameters defined in clause 4.7.2.5.

4.7.2.2 UE data reporting procedures for uplink media streaming p. 50

The following UE data reporting procedures are in scope for the instantiation of the abstract data collection and reporting architecture in the uplink 5GMS architecture:

Invocations of the AF-based uplink Network Assistance procedures defined in clause 6.5 shall be logged by the 5GMSu AF and reported to its subordinate Data Collection AF during active AF-based Network Assistance sessions.
The procedures defined in clauses 6.8.2A and 6.8.2B shall be used by the Direct Data Collection Client instantiated in the Media Session Handler to report invocations of the ANBR-based uplink Network Assistance procedures to the Data Collection AF instantiated in the 5GMSu AF via reference point R2. The UE data reports in this case shall include the parameters defined in clause 4.7.2.5.
The procedures defined in clause 6.8.1 and 6.8.2 shall be used by the 5GMSu AS to report uplink media streaming access activity to the Data Collection AF instantiated in the 5GMSu AF via reference point R4. The UE data reports in this case shall include the parameters defined in clause 4.7.2.4.

4.7.2.3 Common baseline parameters for UE data reporting |R18| p. 51

The parameters defined in Table 4.7.2.3-1 below shall be included in UE data reports submitted by data collection clients to the Data Collection AF instantiated in the 5GMS AF in addition to the baseline parameters defined in clause 4.6.4 of TS 26.531 that are marked below with a grey background.

Table 4.7.2.3-1: Common baseline parameters for UE data reporting

Parameter	Cardinality	Description
External Application Identifier	1..1	Identifying the application to which the UE data report pertains.
Expedite directive	0..1	An indication that the report contains UE data requiring expedited processing by the Data Collection AF instantiated in the 5GMS AF.
Date-time	1..1	The date and time of the media streaming interaction.
UE identity	1..1	A unique identifier of the UE accessing the 5GMSd AS, such as its GPSI or the source IP address and port number of the Media Stream Handler at reference point M4.
Media delivery session identifier	1..1	A value, preferably nominated by the Media Session Handler, that uniquely identifies the media streaming session.
Data Network Name	0..1	Identifying the Data Network of the M4 media streaming session.
Slice identification	0..1	The S-NSSAI identifying the Network Slice of the M4 media streaming session.
UE location	0..1	The location of the UE for the data sample described by this record.

4.7.2.4 UE data reporting parameters for media streaming access activity |R18| p. 52

UE data reports for downlink media streaming access activity shall include the parameters specified in Table 4.7.2.4-1 below in addition to the baseline parameters defined in clause 4.7.2.3 that are marked below with a grey background.

Table 4.7.2.4-1: Downlink media streaming access activity reporting parameters

Parameter	Cardinality	Description
External Application Identifier	1..1	Identifying the application to which the UE data report pertains.
Expedite directive	0..1	An indication that the report contains UE data requiring expedited processing by the Data Collection AF instantiated in the 5GMSd AF.
Date-time	1..1	The date and time of the downlink media streaming access.
UE identity	1..1	A unique identifier of the UE accessing the 5GMSd AS, such as its GPSI or the source IP address and port number of the Media Player at reference point M4d.
Media delivery session identifier	1..1	A value nominated by the Media Session Handler and indicated by the Media Player in the M4d request that uniquely identifies the media streaming session, or otherwise an identifier nominated by the 5GMSd AS for the HTTP session on which the Media Player request was received for this downlink media streaming access.
Data Network Name	0..1	Identifying the Data Network of the M4d downlink media streaming session.
Slice identification	0..1	The S-NSSAI identifying the Network Slice of the M4d downlink media streaming session.
UE location	0..1	The location of the UE when media was downloaded from the 5GMSd AS.
5GMSd AS service endpoint	1..1	The service endpoint on the 5GMSd AS to which the Media Player is connected for this access, such as the server IP address and port number.
HTTP request method	1..1	The HTTP method used for this access.
HTTP request URL	1..1	The URL requested by the Media Player for this access.
HTTP request version	1..1	The HTTP version requested by the Media Player for this access.
HTTP request range	0..1	The value of the Range HTTP request header, if present for this access.
HTTP request size	1..1	The total number of bytes in the HTTP client request message from the Media Player for this access.
HTTP User Agent	0..1	A string describing the Media Player that made this access.
User identity	0..1	A string identifying the user that made the access.
Referrer URL	0..1	The URL that the Media Player reports being referred from.
Cache status	0..1	An indication of whether the 5GMSd AS is able to serve the requested URL from cache for this access (a hit) or whether there is a stale object cached (expired) or the requested URL is not present in cache (miss). For non-caching implementations of the 5GMSd AS, the status is miss for all accesses.
HTTP response code	1..1	The HTTP response code issued by the 5GMSd AS for this access.
HTTP response size	1..1	The total number of bytes returned by the 5GMSd AS in the HTTP response message for this access.
HTTP response body size	1..1	The number of bytes returned by the 5GMSd AS in the HTTP response body for this access.
HTTP response content type	0..1	The MIME content type of the HTTP response message returned by the 5GMSd AS for this access.
Processing latency	1..1	The time taken by the 5GMSd AS to respond to the Media Player request, measured from the first byte of the HTTP request being processed by the 5GMSd AS to the last byte of the response being sent.
Mean network round-trip time	1..1	A rolling mean average of the network round-trip time for the HTTP session on which the access was received.
Network round-trip time variance	1..1	The variance in the average network round-trip time for the HTTP session on which the access was received.
Transport congestion window size	1..1	The current size (in bytes) of the congestion window for the transport connection supporting the HTTP session on which the access was received.

UE data reports for uplink media streaming access activity shall include the parameters specified in Table 4.7.2.4-2 below in addition to the baseline parameters defined in clause 4.7.2.3 that are marked below with a grey background.

Table 4.7.2.4-2: Uplink media streaming access activity reporting parameters

Parameter	Cardinality	Description
External Application Identifier	1..1	Identifying the application to which the UE data report pertains.
Expedite directive	0..1	An indication that the report contains UE data requiring expedited processing by the Data Collection AF instantiated in the 5GMSu AF.
Date-time	1..1	The date and time of the uplink media streaming access.
UE identity	1..1	A unique identifier of the UE accessing the 5GMSu AS, such as its GPSI or the source IP address and port number of the Media Streamer at reference point M4u.
Media delivery session identifier	1..1	A value nominated by the Media Session Handler and indicated by the Media Streamer in the M4u request that uniquely identifies the media streaming session, or otherwise an identifier nominated by the 5GMSu AS for the HTTP session on which the Media Streamer request was received for this uplink media streaming access.
Data Network Name	0..1	Identifying the Data Network of the M4u uplink media streaming session.
Slice identification	0..1	The S-NSSAI identifying the Network Slice of the M4u uplink media streaming session.
UE location	0..1	The location of the UE when media was uploaded to the 5GMSu AS.
5GMSu AS service endpoint	1..1	The service endpoint on the 5GMSu AS to which the Media Streamer is connected for this access, such as the server IP address and port number.
HTTP request method	1..1	The HTTP method used for this access.
HTTP request URL	1..1	The URL requested by the Media Streamer for this access.
HTTP request version	1..1	The HTTP version requested by the Media Streamer for this access.
HTTP request range	0..1	The value of the Range HTTP request header, if present for this access.
HTTP request size	1..1	The total number of bytes in the HTTP client request message from the Media Streamer for this access.
HTTP request body size	1..1	The number of bytes supplied by the Media Streamer in the HTTP request body for this access.
HTTP request content type	0..1	The MIME content type of the HTTP request message supplied by the Media Streamer for this access.
HTTP User Agent	0..1	A string describing the Media Streamer that made this access.
User identity	0..1	A string identifying the user that made the access.
Referrer URL	0..1	The URL that the Media Streamer reports being referred from.
HTTP response code	1..1	The HTTP response code issued by the 5GMSu AS for this access.
HTTP response size	1..1	The total number of bytes returned by the 5GMSu AS in the HTTP response message for this access.
HTTP response body size	1..1	The number of bytes returned by the 5GMSu AS in the HTTP response body for this access.
HTTP response content type	0..1	The MIME content type of the HTTP response message returned by the 5GMSu AS for this access.
Processing latency	1..1	The time taken by the 5GMSu AS to respond to the Media Streamer request, measured from the first byte of the HTTP request being processed by the 5GMSu AS to the last byte of the response being sent.
Mean network round-trip time	1..1	A rolling mean average of the network round-trip time for the HTTP session on which the access was received.
Network round-trip time variance	1..1	The variance in the average network round-trip time for the HTTP session on which the access was received.
Transport congestion window size	1..1	The current size (in bytes) of the congestion window for the transport connection supporting the HTTP session on which the access was received.

4.7.2.5 UE data reporting of ANBR-based Network Assistance invocations |R18| p. 54

UE data reports for ANBR-based Network Assistance invocations shall include the parameters specified in Table 4.7.2.5-1 below in addition to the baseline parameters defined in clause 4.7.2.3 that are marked below with a grey background.

Table 4.7.2.5-1: ANBR-based Network Assistance reporting parameters

Parameter	Cardinality	Description
External Application Identifier	1..1	Identifying the application to which the UE data report pertains.
Expedite directive	0..1	An indication that the report contains UE data requiring expedited processing by the Data Collection AF instantiated in the 5GMS AF.
Date-time	1..1	The date and time of the Network Assistance invocation.
UE identity	1..1	A unique identifier of the UE accessing the 5GMSu AS, such as its GPSI or the source IP address and port number of the Media Stream Handler at reference point M4.
Media delivery session identifier	1..1	A value, preferably nominated by the Media Session Handler, that uniquely identifies the media streaming session.
Data Network Name	0..1	Identifying the Data Network of the M4 media streaming session.
Slice identification	0..1	The S-NSSAI identifying the Network Slice of the M4 media streaming session.
UE location	0..1	The location of the UE when Network Assistance was sought.
Recommended bit rate	1..1	The bit rate recommended by the RAN via the UE modem.

4.7.3 UE data processing for 5GMS p. 55

4.7.3.1 UE data processing procedures for downlink media streaming p. 55

The following restriction dimensions and aggregation functions defined in clause 4.5.2 of TS 26.531 may be provisioned in a Data Access Profile as part of a 5GMSd Provisioning Session and shall, as a consequence, be applied to reported UE data prior to exposing it to event consumers.

Table 4.7.3.1-1: Valid processing of downlink media streaming UE data by the Data Collection AF

	Restriction dimension			Aggregation function
	Time	User	Location	None	Count	Mean	Maximum	Minimum	Sum
QoE metrics for downlink media streaming	Yes	Yes	Yes	Yes	Yes (NOTE 1)	Yes (NOTE 1)	Yes (NOTE 1)	Yes (NOTE 1)	Yes (NOTE 1)
Consumption of downlink media streaming	Yes	Yes	Yes	Yes	Yes (NOTE 2)	No	No	No	No
Downlink dynamic policy invocations	Yes	Yes	Yes	Yes	Yes (NOTE 3)	No	No	No	No
AF-based downlink Network Assistance invocations	Yes	Yes	Yes	Yes	Yes (NOTE 3)	Yes (NOTE 4)	Yes (NOTE 4)	Yes (NOTE 4)	No
ANBR-based downlink Network Assistance invocations	Yes	Yes	Yes	Yes	Yes (NOTE 3)	Yes (NOTE 4)	Yes (NOTE 4)	Yes (NOTE 4)	No
Downlink media streaming access activity	Yes	Yes	Yes	Yes	Yes (NOTE 2)	No	No	No	No
NOTE 1: Aggregation functions applied individually to all exposed metrics within the scope of the applicable restriction dimension(s). NOTE 2: Number of downlink media streaming sessions within the scope of the applicable restriction dimension(s). NOTE 3: Number of invocations within the scope of the applicable restriction dimension(s). NOTE 4: Aggregation functions applied to bit rate recommendations within the scope of the applicable restriction dimension(s).

4.7.3.2 UE data processing procedures for uplink media streaming p. 56

The following restriction dimensions and aggregation functions defined in clause 4.5.2 of TS 26.531 may be provisioned in a Data Access Profile as part of a 5GMSu Provisioning Session and shall, as a consequence, be applied to reported UE data prior to exposing it to event consumers.

Table 4.7.3.2-1: Valid processing of uplink media streaming UE data by the Data Collection AF

	Restriction dimension			Aggregation function
	Time	User	Location	None	Count	Mean	Maximum	Minimum	Sum
AF-based uplink Network Assistance invocations	Yes	Yes	Yes	Yes	Yes (NOTE 1)	Yes (NOTE 2)	Yes (NOTE 2)	Yes (NOTE 2)	No
ANBR-based uplink Network Assistance invocations	Yes	Yes	Yes	Yes	Yes (NOTE 1)	Yes (NOTE 2)	Yes (NOTE 2)	Yes (NOTE 2)	No
Uplink media streaming access activity	Yes	Yes	Yes	Yes	Yes (NOTE 3)	No	No	No	No
NOTE 1: Number of invocations within the scope of the applicable restriction dimension(s). NOTE 2: Aggregation functions applied to bit rate recommendations within the scope of the applicable restriction dimension(s). NOTE 3: Number of uplink media streaming sessions within the scope of the applicable restriction dimension(s).