Tech-invite  3GPPspace  IETF RFCs  SIP
index  21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x

Content for  TS 26.501  Word version:  18.0.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.2…   6.3…   6.5…   6.8…   7…   8…   8.2   A…   A.3…   A.5…   A.7…   A.9   A.10   A.11   A.12   A.13   A.14   A.15   B…   B.3   C…   C.3   C.4   C.5   D… 
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.3 UE data processing for 5GMS  4.7.4 Event exposure of 5GMS UE data 
...

 

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

4.7.1  Reference architecture instantiation  p. 35

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)
Up
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.
Up

4.7.2  UE data reporting for 5GMS  p. 36

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

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:
  1. 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.
  2. 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.
  3. 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.
  4. 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.
  5. The procedures defined in clause 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.
Up

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

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:
  1. 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.

4.7.3  UE data processing for 5GMS  p. 37

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

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 streamingYesYesYesYesYes (NOTE 1)Yes (NOTE 1)Yes (NOTE 1)Yes (NOTE 1)Yes (NOTE 1)
Consumption of downlink media streamingYesYesYesYesYes (NOTE 2)NoNoNoNo
Downlink dynamic policy invocationsYesYesYesYesYes (NOTE 3)NoNoNoNo
AF-based downlink Network Assistance invocationsYesYesYesYesYes (NOTE 3)NoNoNoNo
Downlink media streaming access activityYesYesYesYesYes (NOTE 2)NoNoNoNo
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).
Up

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

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 invocationsYesYesYesYesYes (NOTE)NoNoNoNo
NOTE:
Number of invocations within the scope of the applicable restriction dimension(s).
Up

4.7.4  Event exposure of 5GMS UE data  p. 38

4.7.4.1  Event exposure for downlink media streaming UE data  p. 38

The following types of events are exposed by the Data Collection AF instantiated in the 5GMSd AF:
  1. QoE metrics for downlink media streaming reported by the Media Session Handler to the Data Collection AF instantiated in the 5GMSd AF.
  2. Consumption of downlink media streaming reported by the Media Session Handler to the Data Collection AF instantiated in the 5GMSd AF.
  3. Invocations of downlink dynamic policies in the 5GMSd AF by the Media Session Handler.
  4. Invocations of AF-based downlink Network Assistance in the 5GMSd AF by the Media Session Handler.
  5. Downlink media streaming access activity reported by the 5GMSd AS to the Data Collection AF instantiated in the 5GMSd AF.
High-level procedures for downlink media streaming event exposure are defined in clause 5.11.3.
Up

4.7.4.2  Event exposure for uplink media streaming UE data  p. 38

The following types of events are exposed by the Data Collection AF instantiated in the 5GMSd AF:
  1. Invocations of AF-based uplink Network Assistance in the 5GMSd AF by the Media Session Handler.
    High-level procedures for uplink media streaming event exposure are defined in clause 6.8.3.

Up   Top   ToC