5 Information Object Classes

28.3083GPPInformation Service (IS)Quality of Experience (QoE) measurement collection Integration Reference Point (IRP)Release 17Telecommunication managementTS

Tools: ARFCN - Frequency Conversion for 5G NR/LTE/UMTS/GSM

5.1 Imported and associated information entities

5.1 Imported information entities and local labels

Label reference	Local label
TS 28.622 [5], information object class, Top	Top
TS 28.622 [5], information object class, IRPAgent	IRPAgent
TS 28.622 [5], information object class, GenericIRP	GenericIRP
TS 32.302 [6], information object class, NotificationIRP	NotificationIRP
TS 32.342 [7], information object class, FileTransferIRP	FileTransferIRP
TS 32.602 [8], information object class, ManagedEntity	ManagedEntity

5.2 Class diagram

5.2.1 Relationships

Figure 5.2.1.1

5.2.2 Inheritance

Figure 5.2.2.1

5.3 Class definitions

5.3.1 QMCJob

5.3.1.1 Definition

It represents a task that controls the QMC and collects data from the applications in the UE (i.e. collects the QMCReportContainer of multiple ManagedEntity instances). The QoEReference is a unique ID, which identifies the network request session that has been created by the QMCJob and activated to one or multiple ManagedEntity instance(s).

When a QMCJob is created, none of attributes be modified via the Itf-N:

– If for any reason the QMCIRP determines that a QMC session has been activated in its ManagedEntity(ies) the QMCIRP shall emit the "noitfyQMCSessionLocalActivation" notification to the subscribed IRPManagers to inform the active QMC Sessions. The IRPManagers can decide whether they deactivate the QMC session or keep the QMC session active. (E.g. if the QoEReference is colliding with an existing QMCJob’s QoEReference, the IRPManager may decide to immediately deactivate the QMC session in that ManagedEntity.)

The QMCJob shall use its information to activate and configure QMC session(s) in the requested ManagedEntity instance(s). When the QMCIRP determines that there are available QMCReport files, it shall emit a notification to all subscribed IRPManagers informing the availability of the files. The method and the notification of the available files is described in the File Transfer IRP (TS 32.342 [7]).

– If a QMCJob receives an indication from one of its ManagedEntity that starting a network request session is failed for any reason, the "notifyNetworkRequestSessionFailure" notification may be emitted to inform all subscribed IRPManagers that there was a network request session that was not started in the ManagedEntity.

Referenced TS	Requirement label	Comment
TS 28.404 [10]	REQ-EUSPC-CON-1
TS 28.404 [10]	REQ-EUSPC-CON-4
TS 28.404 [10]	REQ-EUSPC-CON-5
TS 28.307 [11]	REQ-EUSPC-FUN-1
TS 28.307 [11]	REQ-EUSPC-FUN-2

5.3.1.2 Attributes

Attribute name	Support Qualifier	isReadable	isWritable	isInvariant	isNotifyable
serviceType	M	T	T	T	F
areaScope	M	T	T	T	F
qoECollectionEntityAddress	M	T	T	T	F
pLMNTarget	M	T	T	T	F
qMCTarget	M	T	T	T	F
qoEReference	M	T	T	T	F
qMCConfigurationFile	M	T	T	T	F

5.3.1.3 Attribute constraints

None.

5.3.1.4 Notifications

The common notifications defined in clause 5.5 are valid for this IOC, without exceptions or additions.

5.3.1.5 State diagram

None.

5.3.2 QMCRecord

5.3.2.1 Definition

TQMCRecord is the representation of the files containing the information from the network request session.

5.3.2.2 Attributes

Attribute name	Visibility	Support Qualifier	Read Qualifier	Write Qualifier
fileName	+	M	M	–

5.3.3 QMCIRP

5.3.3.1 Definition

QMCIRP is the representation of the QMC management capabilities specified by the present document. This IOC inherits from ManagedGenericIRP IOC specified in TS 32.312 [12].

5.3.4 ManagedEntity

5.3.4.1 Definition

For area based QMC the ManagedEntity represents the role that can be played by an instance of the following IOCs:

– UtranCell

– E-UtranCell

5.4 Information relationship definitions

5.4.1 relation-qMCIRP-qMCJob (M)

5.4.1.1 Definition

This represents the relationship between QMCIRP and the QMCJob.

5.4.1.2 Roles

Name	Definition
theQMCIRP	It represents the QMCIRP
theQMCJobList	It represents the QMCJobList

5.4.2 relation-qMCJob-managedEntity (M)

5.4.2.1 Definition

This represents the relationship between QMCJob and the ManagedEntity.

5.4.2.2 Roles

Name	Definition
theManagedEntity	The ManagedEntity, when playing this role, represents the actual network resource instance, where a network request session is activated.
theQMCJob	It represents the QMCJob

5.4.3 relation-qMCJob-qMCRecord (M)

5.4.3.1 Definition

This represents the relationship between QMCJob and the QMCRecord.

5.4.3.2 Roles

Name	Definition
theQMCJob	It represents the QMCJob
theQMCRecord	It represents the QMCRecord.

5.5 Attribute definitions

5.5.1 Attribute properties

Attribute Name	Documentation and Allowed Values	Properties
serviceType	It identifies an individual UE for a specified end user service/end user service type. allowedValues: DASH (0), MTSI (1)	type: Integer multiplicity: 1 isOrdered: N/A isUnique: N/A defaultValue: None isNullable: False
areaScope	The area scope parameter defines the area in terms of cells or Tracking Area/Routing Area/Location Area where the QMC shall take place. allowedValues: 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.	type: String multiplicity: 1..* isOrdered: N/A isUnique: True defaultValue: None isNullable: False
qoECollectionEntityAddress	It indicates the IP address to which the QMC records shall be transferred. Ipv4 or Ipv6 address(es) may be used. allowedValues: N/A	type: String multiplicity: 1 isOrdered: N/A isUnique: N/A defaultValue: None isNullable: False
pLMNTarget	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.	type: PLMNId multiplicity: 1 isOrdered: N/A isUnique: N/A defaultValue: None isNullable: False
qMCTarget	The QMC target parameter specifies it the QMC is area based or individual UE based. – Area based QMC (0) NOTE: Individual UE based QMC is not supported in this release. allowedValues: …	type: Integer multiplicity: 1 isOrdered: N/A isUnique: N/A defaultValue: None isNullable: False
qoEReference	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.	type: String multiplicity: 1 isOrdered: N/A isUnique: N/A defaultValue: None isNullable: False
qMCConfigurationFile	The QMC configuration file is a container that is specified in TS 26.247 and TS 26.114 allowedValues: N/A	type: String multiplicity: 1 isOrdered: N/A isUnique: N/A defaultValue: None isNullable: False

Attribute Name

Documentation and Allowed Values

Properties

serviceType

It identifies an individual UE for a specified end user service/end user service type.

allowedValues: DASH (0), MTSI (1)

type: Integer

multiplicity: 1

isOrdered: N/A

isUnique: N/A

defaultValue: None

isNullable: False

areaScope

The area scope parameter defines the area in terms of cells or Tracking Area/Routing Area/Location Area where the QMC shall take place.

allowedValues:

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.

type: String

multiplicity: 1..*

isOrdered: N/A

isUnique: True

defaultValue: None

isNullable: False

qoECollectionEntityAddress

It indicates the IP address to which the QMC records shall be transferred. Ipv4 or Ipv6 address(es) may be used.

allowedValues: N/A

type: String

multiplicity: 1

isOrdered: N/A

isUnique: N/A

defaultValue: None

isNullable: False

pLMNTarget

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.

type: PLMNId

multiplicity: 1

isOrdered: N/A

isUnique: N/A

defaultValue: None

isNullable: False

qMCTarget

The QMC target parameter specifies it the QMC is area based or individual UE based.

– Area based QMC (0)

NOTE: Individual UE based QMC is not supported in this release.

allowedValues: …

type: Integer

multiplicity: 1

isOrdered: N/A

isUnique: N/A

defaultValue: None

isNullable: False

qoEReference

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.

type: String

multiplicity: 1

isOrdered: N/A

isUnique: N/A

defaultValue: None

isNullable: False

qMCConfigurationFile

The QMC configuration file is a container that is specified in TS 26.247 and TS 26.114

allowedValues: N/A

type: String

multiplicity: 1

isOrdered: N/A

isUnique: N/A

defaultValue: None

isNullable: False