G.1 Property

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

The properties of an IOC (including SupportIOC) are specified in terms of the following:

  1. An IOC attribute(s) including its semantics and syntax, its legal value ranges and support qualifications. The IOC attributes are not restricted to Configuration Management but also include those related to, for example, 1) Performance Management (i.e., measurement types), 2) Trace Management and 3) Accounting Management.
  2. The non-attribute-specific behaviour associated with an IOC (see Note 1).

NOTE 1: As an example, the Link between MscServerFunction and CsMgwFunction is optional. It is mandatory if the MscServerFunction instance belongs to one ManagedElement instance while the CsMgwFunction instance belongs to another ManagedElement instance. This Link behaviour is a non-attribute-specific behaviour. It is expected that this behaviour, like others, will be inherited.

  1. An IOC relationship(s) with another IOC(s).
  2. An IOC notification type(s) and their qualifications.
  3. An IOC’s relation with its parents (see Note 2). There are three mutually exclusive cases:

1) The IOC can have any parent. In UML diagram, the class has a parent Any.

2) The IOC is abstract and all of the possible parent(s) have been designated and whether subclass IOCs can be designated as a root IOC. In UML diagram, the class has zero or more possible parents of specific classes (except Any).

3) The IOC is concrete and all of the possible parent(s) have been designated and whether the IOC can be designated as a root IOC. In UML diagram, the class has one or more possible parents of specific classes (except Any.)

An IOC instance is either a root IOC or it has one and only one parent. Only 3GPP SA5 may designate an IOC class as a potential root IOC. Currently, only SubNetwork, ManagedElement or MeContext IOCs can be root IOCs.

NOTE 2: The parent and child relation in this clause is the parent name-containing the child relation.

  1. An IOC’s relation with its children. There are three mutually exclusive cases:

1) An IOC shall not have any children (name-containment relation) IOCs. In UML diagram, the class has no child.

2) An IOC can have children IOC(s). The maximum number of instances per children IOC (including their subclasses) can be specified. An IOC may designate that vendor specific objects are not allowed as children IOCs. In UML diagram, the class has a child Any.

3) An IOC can only have the specific children IOC(s) (or their subclasses). The maximum number of instances per children IOC (including their subclasses) can be specified. An IOC may designate that vendor specific objects are not allowed as children IOCs. In UML diagram, the class has one or more children of specific classes (except Any).

  1. Whether An IOC can be instantiated or not (i.e., whether An IOC is an abstract IOC).
  2. An attribute for naming purpose.