4.6 Mandatory, Optional and Conditional qualifiers

32.1503GPPIntegration Reference Point (IRP) Concept and definitionsRelease 17Telecommunication managementTS

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

Note: Void.

This subclause defines a number of terms used to qualify the relationship between the Information Service, the Solution Sets and their impact on the IRP implementations. The qualifiers defined in this clause are used to qualify IRPAgent behaviour only. This is considered sufficient for the specification of the IRPs.

Additional qualifier definitions are specified in 3GPP TS 32.156 “Model Repertoire” [18].

IS specifications define IOC attributes, interfaces, operations, notifications, operation parameters and notification parameters. They can have the following support/read/write qualifiers: M, O, CM, CO, C.

Definition of qualifier M (Mandatory):

– Used for items that shall be supported.

Definition of qualifier O (Optional):

– Used for items which may or may not be supported.

Definition of qualifier CM (Conditional-Mandatory):

– Used for items that are mandatory under certain conditions, specifically:

– All items having the support qualifier CM shall have a corresponding constraint defined in the IS specification. If the specified constraint is met then the items shall be supported. Definition of qualifier CO (Conditional-Optional):

– Used for items that are optional under certain conditions, specifically:

– All items having the support qualifier CO shall have a corresponding constraint defined in the IS specification. If the specified constraint is met, then the items may be supported.

Definition of qualifier C (SS-Conditional):

– Used for items that are only applicable for certain but not all Solutions Sets (SSs).

SS specifications define the SS-equivalents of the IS-defined IOC attributes, operations, notifications, operation parameters and notification parameters. These SS-equivalents can have the following support/read/write qualifiers: M, O, CM and CO.

The mapping of the qualifiers of IS-defined constructs to the qualifiers of the corresponding SS-constructs is defined as follows:

– For qualifier M, O, CM and CO, each IS-defined item (operation and notification, input and output parameter of operations, input parameter of notifications, information relationship and information attribute) shall be mapped to its equivalent(s) in all SSs. Mapped equivalent(s) shall have the same qualifier as the IS-defined qualifier.

– For qualifier C, each IS-defined item shall be mapped to its equivalent(s) in at least one SS. Mapped equivalent(s) can have support qualifier M or O.

Table 4.6 defines the semantics of qualifiers of the Interface IRP SS equivalents, in terms of support from the IRPAgent perspective.

Table 4.6: Semantics for Mandatory, Optional and Conditional qualifiers used in Solution Sets

Mapped SS Equivalent	Mandatory	Optional	Conditional-Mandatory (CM)	Conditional-Optional (CO)
Mapped notification equivalent	The IRPAgent shall generate the notification.	The IRPAgent may or may not generate it.	The IRPAgent shall generate this notification if the constraint described in the IS for this item is satisfied.	The IRPAgent may choose whether or not to generate it. If the IRPAgent chooses to generate it, the constraint described in the IS for this notification must be satisfied.
Mapped operation equivalent	The IRPAgent shall support it.	The IRPAgent may or may not support this operation. If the IRPAgent does not support this operation, the IRPAgent shall reject the operation invocation with a reason indicating that the IRPAgent does not support this operation. The rejection, together with a reason, shall be returned to the IRPManager.	The IRPAgent shall support this operation if the constraint described in the IS for this item is satisfied.	The IRPAgent may support this operation if the constraint described in the IS for this item is satisfied.
Input parameter of the mapped operation equivalent	The IRPAgent shall accept and behave according to its value.	The IRPAgent may or may not support this input parameter. If the IRPAgent does not support this input parameter and if it carries meaning (i.e. it does not carry no-information semantics), the IRPAgent shall reject the invocation with a reason (that it does not support the parameter). The rejection, together with the reason, shall be returned to the IRPManager.	The IRPAgent shall accept and behave according to its value if the constraint described in the IS for this item is satisfied.	The IRPAgent may accept and behave according to its value if the constraint described in the IS for this item is satisfied.
Input parameter of mapped notification equivalent AND output parameter of mapped operation equivalent	The IRPAgent shall supply this parameter.	The IRPAgent may supply this parameter.	The IRPAgent shall supply this parameter if the constraint described in the IS for this item is satisfied.	The IRPAgent may supply this parameter if the constraint described in the IS for this item is satisfied.
Mapped IOC attribute equivalent	The IRPAgent shall support it.	The IRPAgent may support it.	The IRPAgent shall support this attribute if the constraint described in the IS for this item is satisfied.	The IRPAgent may support this attribute if the constraint described in the IS for this item is satisfied.