5.6 Consumption reporting
26.5013GPP5G Media Streaming (5GMS)General description and architectureRelease 18TS
5.6.1 Consumption reporting procedure
Figure 5.6-1: Consumption reporting
Steps:
The first phase is the initialisation phase:
1: The 5GMSd-Aware Application is started.
2: A media content item is selected.
3: The 5GMSd-Aware Application triggers the Media Session Handler to start content playback. The Media Player Entry is provided.
4: The 5GMSd AF initializes the parameters for the consumption reporting configuration (e.g. frequency).
5: The Media Session Handler triggers consumption reporting.
6: The Media Session Handler starts the Media Player with the Media Player Entry.
The second phase is media playback:
The user preferences may be changed:
7: The 5GMSd-Aware Application selects/changes the user preferences.
8: The Media Player transmits consumption reporting user preferences to the Media Session Handler.
When media is playing, the consumption reporting parameters may be updated.
9: The 5GMSd AF updates the consumption reporting parameters.
When media is playing:
10: The Media Player regularly accesses to the media content.
11: In case of changes to the consumed media properties, the Media Player transmits the changes to the Media Session Handler.
12: The Media Session Handler regularly sends report(s) to the 5GMSd AF.
The last phase is to stop the media:
13: The 5GMSd-Aware Application triggers the Media Session Handler to stop content playback.
14: The Media Session Handler stops consumption reporting.
15: The Media Session Handler may send final consumption report(s) to the 5GMSd AF.
17: The Media Session Handler stops the Media Player.
5.6.2 Consumption reporting parameters
Table 4.2.3‑2 describes the parameters used in step 4 of clause 5.6.1.
Table 5.6.2-2 below describes the additional parameters used in steps 13 or 16 of clause 5.6.1.
Table 5.6.2-2: Additional consumption reporting parameters
Parameters |
Description |
Media Player Entry pointer |
Identify the Media Player Entry. In the case of DASH, the Media Player Entry pointer can be a URL of the MPD. |
Consumption reporting client ID |
Identify the identifier of the UE that consumes the data. |
Location type |
Identify the UE location type. This parameter is only used when the location reporting is enabled for the UE or for the Downlink Streaming session with a condition that the UE allows to share its location within operator’s trust domain. The location type can be CGI, ECGI or NCGI as defined in TS 23.003 [9]. |
Location |
Identify the UE location. This parameter is only used when location reporting is enabled for the UE or for the Downlink Streaming session, and when the UE allows its location to be shared within the Network Operator’s trust domain. |
Media consumed |
Identifies the media consumed. In the case of DASH, the AdaptationSet@id may be used. |
Start time |
The time when media consumption started. |
Duration |
The duration of media consumption relative to the start time. |
5.6.3 Triggering consumption reporting
If consumption reporting is supported and activated, the 5GMSd Client shall send a consumption report when any of the following conditions is met:
– Start of 5GMS consumption of a Downlink Streaming session;
– Stop of 5GMS consumption of a Downlink Streaming session;
– Upon determining the need to report ongoing 5GMS consumption
– Reports are sent at periodic intervals determined by the reporting interval attribute of the consumption reporting configuration specified in Table 4.2.3‑2.
– Upon determining a location change if location reporting is requested by the 5GMSd AF and is allowed to be reported by the UE.
NOTE: Whenever a consumption report is sent, the 5GMSd Client is expected to reset its corresponding reporting interval timer to the value of that attribute and begin countdown of the timer. Whenever the 5GMSd Client stops consumption of the same session, it is expected to disable its corresponding reporting interval timer.