Tech-invite3GPPspaceIETF RFCsSIP

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…


5.5  Metrics collection and reportingp. 50

5.5.1  Generalp. 50

Metrics collection and reporting can be done in different ways, depending on the relationship between the Application Provider and the 5GMS System operator. The following clauses show simplified signalling examples for two different use-cases.

5.5.2  RAN-based reporting procedurep. 50

In the first use-case, shown in Figure 5.5.2-1 below, the 5GMS System operator controls the metrics collection and reporting using the RAN-based configuration method. In this case the metrics are configured via the RAN and the control plane, independent of 5GMS functional support.
Copy of original 3GPP image for 3GPP TS 26.501, Fig. 5.5.2-1: Metrics collection and reporting via RAN-based configuration
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, which metrics to collect, and how metrics shall be reported. If per-slice metrics collection and reporting is supported, a slice scope may be present in the metrics configuration, indicating the specific slice instance(s) for metrics collection and reporting.
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 collection and reporting for the UE. 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 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 8a.
If a slice scope is included in the metrics configuration set, the Media Session Handler shall check the running slice which is carrying the current media streaming (e.g. via the AT Command +CGDCONT [24] or the specific traffic mapping with URSP [4]). If the running slice is within the slice scope, the metrics collection and reporting shall be excuted. Additionally, the running slice shall also be included into the metrics reports.
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) along with the measurement resolution interval). The metrics reporting interval timer is activated in the Media Session Handler.
Step 12.
Media is delivered and rendered, and...
Step 13.
...more media is delivered...
Step 14.
The configured metrics reporting interval has elapsed, 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 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 control plane.
Step 21a.
The OAM may determine the per-slice QoE metrics based on the metrics reports and the slice scope.
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   Top   ToC