5 Quality of Experience (QoE) measurement management parameters
28.4053GPPControl and configurationQuality of Experience (QoE) measurement collectionRelease 18Telecommunication managementTS
5.1 QoE collection entity address (M)
This is a parameter which defines the IP address to which the QMC records shall be transferred. Ipv4 or Ipv6 address(es) may be used.
5.2 QoE reference (M)
The QoE reference parameter specify the network request session. The QoE reference shall be globally unique therefore it is composed as follows:
MCC+MNC+QMC ID, where the MCC and MNC are coming with the QMC activation request from the management system to identify one PLMN containing the management system, and QMC ID is a 3 byte Octet String.
The QMC ID is generated by the management system or the operator.
It is used to identify the QoE measurement collection job in the traffic nodes and in the measurement collection centre.
5.3 PLMN target (CM)
This parameter defines the PLMN for which sessions shall be selected in the network request session in case of area based QMC when several PLMNs are supported in the RAN (this means that shared cells and not shared cells are allowed for the specified PLMN. Furthermore, several PLMNs can be used for not shared RAN cases as well as for shared RAN cases.). Only the sessions may be selected where the PLMN that the UE reports as selected PLMN is the same as the PLMN Target.
Note that the PLMN Target might differ from the PLMN specified in the Network Request Session Id, as that specifies the PLMN that is containing the management system requesting the Network Request Session from the NE.
The parameter is mandatory if network sharing is deployed.
5.4 Area scope (CM)
The area scope parameter defines the area in terms or cells or Tracking Area/Routing Area/Location Area where the QMC shall take place. If the parameter is not present the QMC shall be done throughout the PLMN specified in PLMN target.
The area scope parameter in UMTS is either:
– List of cells, identified by CGI. Maximum 32 CGI can be defined.
– List of Routing Area, identified by RAI. Maximum of 8 RAIs can be defined.
– List of Location Area, identified by LAI. Maximum of 8 LAIs can be defined.
The area scope parameter in LTE is either:
– list of cells, identified by E-UTRAN-CGI. Maximum 32 CGI can be defined.
– List of Tracking Area, identified by TAC. Maximum of 8 TAC can be defined.
The area scope parameter in NR is either:
– list of cells, identified by N-CGI. Maximum 32 NCGI can be defined.
– List of Tracking Area, identified by TAC. Maximum of 8 TAC can be defined.
The parameter is mandatory if area based QMC is requested.
5.5 QMC configuration file (container) (M)
The QMC configuration file is a container that is specified in Annex L of TS 26.247 [6], clause 16.5 of TS 26.114[7] or clause 9.4 of TS 26.118 [13].
The corresponding parameter name for this container in Radio Resource Control (RRC) Protocol specification is measConfigAppLayerContainer in case of NR and LTE, see TS 38.331 [11], TS 25.331 [4] or "Container for application layer measurement configuration" in case of UTRAN, see TS 36.331 [8]
For NR, the QMC configuration file parameter in the management interface defines the location of the container..
5.6 QMC target (M)
The QMC target parameter specifies it the QMC is area based or individual UE based.
– Area based QMC (0)
– Individual UE based QMC (1)
NOTE: Void.
5.7 Recording session id (M)
This parameter shall be a 2 byte octet string. The recording session id shall be the same for the whole session in the application, while for each different session in the application the recording session id shall be changed. The recording session id is generated by the application in the UE.
It is used in the measurement collection centre to identify which session within a UE has collected information in the application.
5.8 Service type (M)
Which kind of service that shall be recorded.
– DASH (0)
– MTSI (1)
– VR (2)
DASH measurements are specified in [6]. MTSI measurements are specific in [7]. VR measurements are specified in TS 26.118 [13].
5.9 Slice scope (CM)
This parameter contains a list of S-NSSIAs (Single Network Slice Selection Assistance Information). A Network Slice end to end is identified by S-NSSAI.
5.10 QoE Target (CM)
This parameter specifies the target object (individual UE) for the QMC in case of signalling based QMC. The qoETarget parameter shall be able to carry "IMSI” or "SUPI".
5.11 jobId (O)
This parameter presents the job identifier of a QMCJob instance. The jobId can be used to associate multiple QMCJob instances.
5.12 Available RAN visible QoE metrics (O)
This parameter indicate available RAN visible QoE metrics to the gNB. The list of available RAN visible metrics are outside the legacy QoE configuration file. This parameter is optional and is valid for NR only.
The gNB configures the RAN visible QoE measurement to collect all or some of the available RAN visible QoE metrics, where the indication of metric availability is received from the OAM or the 5GC. Available RAN visible QoE Metrics are: "Application Layer Buffer Level List" and "Playout Delay for Media Startup".
The RAN visible QoE measurements are supported for the DASH streaming and VR services.
5.13 MDT Alignment information (O)
This parameter indicates the MDT measurements with which alignment of QoE measurement is required. This parameter is optional and is valid for NR only.
The gNB may activate the MDT measurements upon/after receiving the MDT activation message from the OAM.
The gNB includes time stamp information to the QoE measurement reports to enable the correlation of corresponding measurement results of MDT and QoE at the MCE/TCE. In addition, the gNB includes the MDT session identifiers (Trace Reference and Trace Recording Session Reference) in the corresponding QoE measurement report.
Annex A (informative):
Change history
|
Change history |
|||||||
|
Date |
Meeting |
TDoc |
CR |
Rev |
Cat |
Subject/Comment |
New version |
|
2020-07 |
SA#88e |
Upgrade to version under change control |
16.0.0 |
||||
|
2021-09 |
SA#93e |
SP-210883 |
0001 |
– |
F |
Aligning with RAN specifications 36.331 and 25.331 |
16.1.0 |
|
2021-12 |
SA#94e |
SP-211454 |
0004 |
1 |
F |
Corrent the description of QoE reference and PLMN target |
16.2.0 |
|
2021-12 |
SA#94e |
SP-211453 |
0003 |
1 |
B |
Adding Signalling Based Activation for UTRAN and LTE |
17.0.0 |
|
2022-03 |
SA#95e |
SP-220181 |
0005 |
– |
B |
Adding Management Based Activation and Temporary stop and restart during RAN overload in NR |
17.1.0 |
|
2022-03 |
SA#95e |
SP-220181 |
0008 |
B |
Update to include NR and adding VR |
17.1.0 |
|
|
2022-06 |
SA#96 |
SP-220500 |
0011 |
1 |
F |
Adding missing parameters and updating definition |
17.2.0 |
|
2022-09 |
SA#97e |
SP-220850 |
0012 |
– |
F |
Align Requirements of handling QMC during RAN overload to RAN specifications |
17.3.0 |
|
2022-09 |
SA#97e |
SP-220855 |
0014 |
1 |
B |
Adding Signalling Based Activation for NR |
18.0.0 |
|
2022-09 |
SA#97e |
SP-220855 |
0015 |
1 |
B |
Handling of QoE measurement collection at handover in NR |
18.0.0 |
|
2022-12 |
SA#98e |
SP-221167 |
0017 |
2 |
F |
Clean up |
18.1.0 |
|
2022-12 |
SA#98e |
SP-221176 |
0018 |
1 |
F |
Management based activation in NR correction for SBMA |
18.1.0 |
|
2022-12 |
SA#98e |
SP-221176 |
0019 |
– |
B |
Add MDT alignment Information and RAN visible QoE Metrics to Handling QMC at Handover |
18.1.0 |
|
2022-12 |
SA#98e |
SP-221176 |
0021 |
– |
B |
Definition of parameters MDT Alignment Information and Available RAN Visible QoE Metrics |
18.1.0 |