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.
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 Metrics Collection & Reporting and Consumption Collection & Reporting subfunctions.
-
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:
R1
This reference point is not instantiated in the 5GMS architecture.
M1
Provisioning of data collection and reporting features in the Data Collection AF.
R2
This reference point is not instantiated in the 5GMS architecture. Instead, it is 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.
M5
Direct data reporting by the Direct Data Collection Client to the Data Collection AF, via the Media Session Handler and 5GMS AF.
R3
This reference point is not instantiated in the 5GMS architecture.
R4
Media streaming access reporting by the 5GMS AS to the Data Collection AF.
R5
Event exposure by the Data Collection AF to subscribing NWDAF [23] instances.
R6
Event exposure by the Data Collection AF to subscribing Event Consumer AF instances in the 5GMS Application Provider.
R7
This reference point is not instantiated in the 5GMS architecture.
M6
Configuration of 5GMS-related data reporting by the 5GMS-Aware Application.
R8
This reference point is not instantiated in the 5GMS architecture.
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.
|
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) | No | No | No | 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).
|
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.
|
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) | No | No | No | No |
NOTE:
Number of invocations within the scope of the applicable restriction dimension(s).
|