6 Specification level requirements
28.3073GPPQuality of Experience (QoE) measurement collection Integration Reference Point (IRP)Release 17RequirementsTelecommunication managementTS
6.1 Requirements
REQ-EUSPC-FUN-1: The IRPManager shall have a capability to request collection of QoE information per end user service/end user service type for a specified area.
REQ-EUSPC-FUN-2: The IRPManager shall have a capability to request the collection of QoE information to be stopped before the time for the NRS has expired.
REQ-EUSPC-FUN-3: The IRPAgent shall have a capability to notify the IRPManager when a collection of QoE information has been stopped before the time for the NRS has expired.
6.2 Actor roles
Please see respective use case.
6.3 Telecommunication resources
Please see respective use case.
6.4 Use cases
6.4.1 Activate collection measurement job for an area in UTRAN
|
Table 6.4.1-1: Activate collection measurement job for an area |
||
|---|---|---|
|
Use case stage |
Evolution/Specification |
<<Uses>> |
|
Goal |
To start collecting QoE information for an end user service type in a specified area. |
|
|
Actors and roles |
IRPManager: Request the start of collection of QoE information. |
|
|
Telecom resources |
The RNC and the UE |
|
|
Assumptions |
There are UEs that has the capability to provide the requested information in the specified area. |
|
|
Pre-conditions |
None. |
|
|
Begins when |
The IRPManager requests that a NRS shall be started. |
|
|
Step 1(M) |
An IRPAgent receives the request and forwards it to the appropriate RNC(s). |
|
|
Step 2 (M) |
The RNC starts a NRS for the specified area and start checking for UEs that supports QoE information collection. |
|
|
Step 3 (M) |
For UEs that support QoE information collection, the RNC starts a UERS and forwards the request of collection QoE information to the UE. See ref. 3GPP TS 25.331 [4]. |
|
|
Step 4 (M) |
When the requested end user service is started in the UE, it starts a RECS and records the requested information. |
|
|
Step 5 (M) |
The UE reports the recorded information to a collection centre via the RNC as long as the end user service session is active during the time for the NRS. |
|
|
Step 6 (M) |
When the end user service session ends the UE stops the RECS and reports the collected data to a collection centre via the RNC. |
|
|
Ends when |
When the time for the NRS elapses or when the IRPManager sends a request for de-activation. |
|
|
Exceptions |
||
|
Post-conditions |
None. |
|
|
Traceability |
REQ-EUSPC-FUN-1. |
|
|
NOTE: Steps 4, 5 and 6 are repeated in a NRS for every time a session that starts the requested end user service in the UE. |
||
NOTE: A similar use case is valid for LTE.
6.4.2 De-activate collection measurement job in UTRAN
|
Table 6.4.2-1: De-activate collection measurement job |
||
|---|---|---|
|
Use case stage |
Evolution/Specification |
<<Uses>> |
|
Goal |
To stop collecting more QoE information for an NRS before the time for the NRS has expired. |
|
|
Actors and roles |
IRPManager: Request to stop the collection of QoE information. |
|
|
Telecom resources |
The RAN node, HSS and the UE |
|
|
Assumptions |
None. |
|
|
Pre-conditions |
A NRS is started. |
|
|
Begins when |
The IRPManager requests that a NRS shall be stopped. |
|
|
Step 1 (M) |
An IRPAgent receives the request and forwards it to the RNC or the HSS. |
|
|
Step 2 (O) |
The HSS transfers the request to the RNC via the SGSN. |
|
|
Step 3 (M) |
The RNC node stops the NRS and informs the UE to not start new RECS. |
|
|
Step 4 (O) |
The RNC node informs HSS, via SGSN, that the NRS is stopped. |
|
|
Step 5 (O) |
The HSS stops the NRS. |
|
|
Ends when |
When the IRP Manager receives the notification that the NRS is stopped. |
|
|
Exceptions |
None. |
|
|
Post-conditions |
None. |
|
|
Traceability |
REQ-EUSPC-FUN-3 and REQ-EUSPC-FUN-4. |
|
NOTE: A similar use case is valid for LTE.
Annex A (informative):
Change history
|
Change history |
|||||||
|
Date |
Meeting |
TDoc |
CR |
Rev |
Cat |
Subject/Comment |
New version |
|
2017-10 |
SA5#115 |
S5-175398 |
R15 pCR 28.307-000 Introduction and Scope for QoE IRP requirements |
0.1.0 |
|||
|
2017-10 |
SA5#115 |
S5-175399 |
R15 pCR 28.307-000 Introduction of specification level use cases and requirements for QoE IRP requirements |
0.1.0 |
|||
|
2019-01 |
Sa5#123 |
S5-191296 |
Including DASH and MTSI in Scope |
0.2.0 |
|||
|
2019-01 |
Sa5#123 |
S5-191297 |
Restrict to UMTS and LTE |
0.2.0 |
|||
|
2020-03 |
SA5#129e |
S5-201388 |
Rapporteur’s clean up (using new TS template) |
0.3.0 |
|||
|
2020-03 |
SA5#129e |
S5-201394 |
Remove SBA |
0.3.0 |
|||
|
2020-03 |
SA5#129e |
EditHelp review |
0.4.0 |
||||
|
2020-06 |
EditHelp review (editorial changes only) |
0.4.1 |
|||||
|
2020-06 |
SA#88e |
SP-200474 |
Presented for information and approval |
1.0.0 |
|||
|
2020-07 |
SA#88e |
Upgrade to change control version |
16.0.0 |
||||
|
2022-03 |
– |
– |
– |
– |
– |
Update to Rel-17 version (MCC) |
17.0.0 |