Tech-invite3GPPspecsSIPRFCs
Overview21222324252627282931323334353637384‑5x

Content for  TS 26.501  Word version:  16.5.0

Top   Top   Up   Prev   Next
1…   4…   4.2…   4.3…   5…   5.2…   5.3…   5.4…   5.5…   5.6…   5.7…   5.8   5.9…   6…   6.3…   7…   A…   B…

 

5.5  Metrics collection and reportingWord‑p. 40

5.5.1  General

Metrics collection and reporting can be done in different ways, depending on the relationship between the Service Provider and the Network Operator. The following clauses show simplified signalling examples for two different use-cases.

5.5.2  Out-of-band-controlled reporting procedure

In the first use-case, shown in Figure 5.5.2-1 below, the MNO is controlling the metrics reporting using the out-of-band configuration and reporting option. In this case the metrics are configured via the RAN and the 5G control plane.
[not reproduced yet]
Figure 5.5.2-1: Metrics collection using the out-of-band 5G control plane option
Up
The different steps are explained below:
Step 1.
Overall metrics configuration is done on the network level, for instance defining which geographical areas that shall have metrics collection active, and how often metrics shall be reported.
Step 2.
The metrics configuration(s) is/are sent from the OAM to the RAN, which does not forward that information to the UE at this stage.
Step 3.
Time passes, and it is assumed that the UE moves around during that period.
Step 4.
The UE enters an area (cell, location area, etc.,) which is inside the geographical constraint. This is discovered by the RAN, and it now needs to activate metrics reporting for the UE.
Step 5.
The actual metrics configuration is sent from the RAN to the Media Session Handler, via the 5G control plane.
Step 6.
Additional time passes, and the UE has a metrics configuration, but no streaming session has started.
Step 7.
A streaming session is started.
Step 8.
The session setup is done in conjunction with signalling transactions (not shown here).
Step 9.
A new metrics collection job is created in the Media Player.
Step 10.
A reference to the new metrics collection job is returned.
Step 11.
The configuration for the metrics collection job is sent to the Media Player (i.e. which metrics should be measured).
Step 12.
Media is delivered and rendered, and...
Step 13.
...more media is delivered...
Step 14.
The configured metrics reporting interval has passed, and the Media Session Handler now requests the collected metrics from the Media Player.
Step 15.
The Media Player returns the collected metrics.
Step 16.
The metrics are reported via the 5G control plane.
Step 17.
The session continues...
Step 18.
more media is delivered, and then the session is finished.
Step 19.
The Media Session Handler requests the final metrics collected.
Step 20.
The Media Player returns the final collected metrics.
Step 21.
The metrics are reported to the OAM via the 5G control plane.
Step 22.
The metrics collection job is deleted.
Step 23.
Time passes, the UE moves around.
Step 24.
The UE leaves the geographical area specified by the metrics configuration.
Step 25.
The RAN sends metrics (de)configuration to the UE, to stop future metrics collection.
Up

5.5.3  In-band-controlled reporting procedureWord‑p. 42
The second use-case, shown in figure 5.5.3-1 below, illustrates a scenario where the metrics collection is configured in-band. Thus, together with the media, there are metadata which describe how metrics shall be collected and how they shall be reported. The Media OAM and 5GMSd AS functions can both be either trusted or untrusted (but not mixed).
[not reproduced yet]
Figure 5.5.3-1: Metrics collection using the in-band metadata option
Up
The different steps are explained below:
Step 1.
The content servers are set up, including any metrics configuration.
Step 2.
If the Media OAM and 5GMSd AS are located in a trusted domain, metadata regarding the metrics collection and reporting are sent to the 5GMSd AS.
Step 3.
Time passes during which no streaming session is active...
Step 4.
A streaming session starts.
Step 5.
The App and the Media Session Handler initialize a new session.
Step 6.
The Media Player requests any metadata from the 5GMSd AS which is needed for downloading the media content.
Step 7.
Metadata is returned to the Media Player and also forwarded to the Media Session Handler and (potentially) to the App.
Step 8.
A new metrics job is created in the Media Player.
Step 9.
A reference to the new metrics job is returned.
Step 10.
Based on the metadata, the configuration for the metrics collection job is sent to the Media Player (i.e. specifying which metrics should be measured).
Step 11.
The streaming session is running.
Step 12.
Media is delivered and rendered, and...
Step 13.
more media is delivered...
Step 14.
The configured metrics reporting interval has passed, and the Media Session Handler now requests the collected metrics from the Media Player.
Step 15.
The Media Player returns the collected metrics.
Step 16.
The metrics are reported according to the reporting method defined in the configuration, for instance HTTP upload.
Step 17.
The session continues...
Step 18.
more media is delivered, and then the session is finished.
Step 19.
The Media Session Handler requests the final metrics collected.
Step 20.
The Pedia Player returns the final collected metrics.
Step 21.
The metrics are reported.
Step 22.
The metrics collection job is deleted.
Up

5.5.4  Metrics collection configuration parametersWord‑p. 43
Table 4.2.3-4 in clause 4.2.3 describes the metrics collection configuration parameters used in step 5 of Figure 5.5.2-1 and step 7 of Figure 5.5.3-1. Note that some of the parameters are only relevant for a specific reporting option, as shown in Table 5.5.4-1 below.
Parameters
Out-of-band-controlled reporting
In-band-controlled reporting

Server address
-
X
DNN
-
X
Reporting interval
X
X
Sample percentage
X
X
Streaming source filter
X
-
Metrics
X
X


Up   Top   ToC