4.3 Class definitions
28.5413GPP5G Network Resource Model (NRM)Management and orchestrationStage 2 and stage 3TS
4.3.1 GNBDUFunction
4.3.1.1 Definition
For non-split NG-RAN deployment scenario, this IOC together with GNBCUCPFunction IOC and GNBCUUPFunction IOC provide the management of gNB defined in clause 6.1.1 in 3GPP TS 38.401 [4].
For 2-split and 3-split NG-RAN architecture, this IOC provides the management representation of gNB-DU defined in clause 6.1.1 in 3GPP TS 38.401 [4].
The following table identifies the necessary end points required for the representation of gNB and en-gNB, of all deployment scenarios.
|
Req Role |
End point requirement for 3-split deployment scenario |
End point requirement for 2-split deployment scenario |
End point requirement for Non-split deployment scenario |
|
gNB |
<<IOC>>EP_F1C, <<IOC>>EP_F1U |
<<IOC>>EP_F1C, <<IOC>>EP_F1U |
None. |
|
en-gNB |
<<IOC>>EP_F1C, <<IOC>>EP_F1U |
<<IOC>>EP_F1C, <<IOC>>EP_F1U |
None. |
4.3.1.2 Attributes
The GNBDUFunction IOC includes attributes inherited from ManagedFunction IOC (defined in TS 28.622[30]) and the following attributes:
|
Attribute name |
S |
isReadable |
isWritable |
isInvariant |
isNotifyable |
|
gNBDUId |
M |
T |
T |
F |
T |
|
gNBDUName |
O |
T |
T |
F |
T |
|
gNBId |
CM |
T |
T |
F |
T |
|
gNBIdLength |
CM |
T |
T |
F |
T |
|
rimRSReportConf |
O |
T |
F |
T |
T |
|
Attribute related to role |
|||||
|
configurable5QISetRef |
O |
T |
T |
F |
T |
|
dynamic5QISetRef |
O |
T |
F |
F |
T |
4.3.1.3 Attribute constraints
None.
4.3.1.4 Notifications
The common notifications defined in subclause 4.5 are valid for this IOC, without exceptions or additions.
4.3.2 GNBCUCPFunction
4.3.2.1 Definition
For non-split NG-RAN deployment scenario, this IOC together with GNBCUUPFunction IOC and GNBDUFunction IOC provide the management representation of gNB defined in clause 6.1.1 in 3GPP TS 38.401 [4].
For 2-split NG-RAN deployment scenario, this IOC together with GNBCUUPFunction IOC provide management representation of the gNB-CU defined in clause 6.1.1 in 3GPP TS 38.401 [4].
For 3-split NG-RAN deployment scenario, this IOC provides management representation of gNB-CU-CP defined in clause 6.1.2 in 3GPP TS 38.401 [4].
The following table identifies the necessary end points required for the representation of gNB and en-gNB, of all deployment scenarios.
|
Req Role |
End point requirement for 3-split deployment scenario |
End point requirement for 2-split deployment scenario |
End point requirement for Non-split deployment scenario |
|
gNB |
<<IOC>>EP_XnC, <<IOC>>EP_NgC, <<IOC>>EP_F1C, <<IOC>>EP_E1. |
<<IOC>>EP_XnC, <<IOC>>EP_NgC, <<IOC>>EP_F1C. |
<<IOC>>EP_XnC, <<IOC>>EP_NgC. |
|
en-gNB |
<<IOC>>EP_X2C, <<IOC>>EP_F1C, <<IOC>>EP_E1. |
<<IOC>>EP_X2C, <<IOC>>EP_F1C. |
<<IOC>>EP_X2C. |
4.3.2.2 Attributes
The GNBCUCPFunction IOC includes attributes inherited from ManagedFunction IOC (defined in TS 28.622[30]) and the following attributes:
|
Attribute name |
S |
isReadable |
isWritable |
isInvariant |
isNotifyable |
|
gNBId |
M |
T |
T |
F |
T |
|
gNBIdLength |
M |
T |
T |
F |
T |
|
gNBCUName |
O |
T |
T |
F |
T |
|
pLMNId |
M |
T |
T |
T |
T |
|
x2BlockList |
CM |
T |
T |
F |
T |
|
x2AllowList |
CM |
T |
T |
F |
T |
|
xnBlockList |
M |
T |
T |
F |
T |
|
xnAllowList |
M |
T |
T |
F |
T |
|
x2HOBlockList |
CM |
T |
T |
F |
T |
|
XnHOBlockList |
M |
T |
T |
F |
T |
|
mappingSetIDBackhaulAddressList |
CM |
T |
T |
F |
T |
|
tceIDMappingInfoList |
CM |
T |
T |
F |
T |
|
dDAPSHOControl |
CM |
T |
T |
F |
T |
|
dCHOControl |
CM |
T |
T |
F |
T |
|
Attribute related to role |
|||||
|
configurable5QISetRef |
O |
T |
T |
F |
T |
|
dynamic5QISetRef |
O |
T |
F |
F |
T |
4.3.2.3 Attribute constraints
|
Name |
Definition |
|
x2BlockList |
Condition: Multi-Radio Dual Connectivity with the EPC (see TS 37.340 [9] clause 4.1.2) is supported. |
|
x2AllowList |
Condition: Multi-Radio Dual Connectivity with the EPC (see TS 37.340 [9] clause 4.1.2) is supported. |
|
x2HOBlockList |
Condition: Multi-Radio Dual Connectivity with the EPC (see TS 37.340 [9] clause 4.1.2) is supported. |
|
mappingSetIDBackhaulAddressList |
Condition: Remote Interference Management function is supported. |
|
tceIDMappingInfolist |
Condition: MDT Function is supported. |
|
dDAPSHOControl |
Condition: DAPS is supported. |
|
dCHOControl |
Condition: CHO is supported. |
4.3.2.4 Notifications
The common notifications defined in subclause 4.5 are valid for this IOC, without exceptions or additions.
4.3.3 GNBCUUPFunction
4.3.3.1 Definition
For non-split NG-RAN deployment scenario, this IOC together with GNBCUCPFunction IOC and GNBDUFunction IOC provide the management representation of gNB defined in clause 6.1.1 in 3GPP TS 38.401 [4].
For 2-split NG-RAN deployment scenario, this IOC together with GNBCUCPFunction IOC provide management representation of gNB-CU defined in clause 6.1.1 in 3GPP TS 38.401 [4].
For 3-split NG-RAN deployment scenario, this IOC provides management representation of gNB-CU-UP defined in clause 6.1.2 in 3GPP TS 38.401 [4].
The following table identifies the necessary end points required for the representation of gNB and en-gNB, of all deployment scenarios.
|
Req Role |
End point requirement for 3-split deployment scenario |
End point requirement for 2-split deployment scenario |
End point requirement for Non-split deployment scenario |
|
gNB |
<<IOC>>EP_XnU, <<IOC>>EP_NgU, <<IOC>>EP_F1U, <<IOC>>EP_E1. |
<<IOC>>EP_XnU, <<IOC>>EP_NgU, <<IOC>>EP_F1U. |
<<IOC>>EP_XnU, <<IOC>>EP_NgU. |
|
en-gNB |
<<IOC>>EP_X2U, <<IOC>>EP_S1U, <<IOC>>EP_F1U, <<IOC>>EP_E1. |
<<IOC>>EP_X2U, <<IOC>>EP_S1U, <<IOC>>EP_F1U. |
<<IOC>>EP_X2U, <<IOC>>EP_S1U. |
4.3.3.2 Attributes
The GNBCUUPFunction IOC includes attributes inherited from ManagedFunction IOC (defined in TS 28.622[30]) and the following attributes:
|
Attribute name |
S |
isReadable |
isWritable |
isInvariant |
isNotifyable |
|
gNBCUUPId |
M |
T |
F |
T |
T |
|
pLMNInfoList |
M |
T |
T |
F |
T |
|
gNBId |
M |
T |
T |
F |
T |
|
gNBIdLength |
M |
T |
T |
F |
T |
|
Attribute related to role |
|||||
|
configurable5QISetRef |
O |
T |
T |
F |
T |
|
dynamic5QISetRef |
O |
T |
F |
F |
T |
4.3.3.3 Attribute constraints
None.
4.3.3.4 Notifications
The common notifications defined in subclause 4.5 are valid for this IOC, without exceptions or additions.
4.3.4 NRCellCU
4.3.4.1 Definition
This IOC represents the part of NR cell information that is responsible for the management of inter-cell mobility and neighbour relations via ANR.
4.3.4.2 Attributes
The NRCellCU IOC includes attributes inherited from ManagedFunction IOC (defined in TS 28.622[30]) and the following attributes:
|
Attribute name |
S |
isReadable |
isWritable |
isInvariant |
isNotifyable |
|
cellLocalId |
M |
T |
T |
F |
T |
|
pLMNInfoList |
M |
T |
T (Note) |
F |
T |
|
Attribute related to role |
|||||
|
nRFrequencyRef |
M |
T |
F |
F |
T |
|
NOTE: Whether the attribute "pLMNId" in the PLMNInfo can be writable depends on the implementation. |
|||||
Note 1: Void.
Note 2: Void.
4.3.4.3 Void
4.3.4.4 Notifications
The common notifications defined in subclause 4.5 are valid for this IOC, without exceptions or additions.
4.3.5 NRCellDU
4.3.5.1 Definition
This IOC represents the part of NR cell information that describes s the specific resources instances.
An NR cell transmits SS/PBCH block and always requires downlink transmission at a certain carrier frequency with a certain channel bandwidth. Transmission may be performed from multiple sector-carriers using different transmission points, and these may be configured with different carrier frequencies and channel bandwidths, as long as they are aligned to the cell’s downlink resource grids as defined in subclause 4.4 in TS 38.211 [32]. The values of arfcnDL and bSChannelBwDL attributes define the resource grids which each sector-carrier needs to be aligned to. See subclauses 5.3 and 5.4.2 of TS 38.104 [12] for definitions of BS channel bandwidth and NR-ARFCN, respectively.
An NR cell requires an uplink in order to provide initial access. In case of TDD, the values of arfcnUL and bSChannelBwUL have to always be set to the same values as for the corresponding DL attributes. For both FDD and TDD, the arfcnUL and bSChannelBwUL define uplink resource grids to which each sector-carrier needs to align to.
An NR cell can in addition be configured with a supplementary uplink, which has its own arfcnSUL and bSChannelBwSUL, which define resource grids for supplementary uplink sector-carriers.
Each of downlink, uplink and supplementary uplink (if configured) need an initial bandwidth part (BWP), which defines resources to be used by UEs during and immediately after initial access. Additional BWPs can be either configured or calculated by gNB internally and be applied to UEs dynamically by gNB based on e.g. UE capability and bandwidth need of each UE.
BWPs are configured individually (bWPRef) or via sets (bWPSetRef).
NOTE: Void
4.3.5.2 Attributes
The NRCellDU IOC includes attributes inherited from ManagedFunction IOC (defined in TS 28.622[30]) and the following attributes:
|
Attribute name |
S |
isReadable |
isWritable |
isInvariant |
isNotifyable |
|
cellLocalId |
CM |
T |
T |
F |
T |
|
operationalState |
M |
T |
F |
F |
T |
|
administrativeState |
M |
T |
T |
F |
T |
|
cellState |
M |
T |
F |
F |
T |
|
pLMNInfoList |
CM |
T |
T |
F |
T |
|
nPNIdentityList |
CM |
T |
T |
F |
T |
|
nRPCI |
M |
T |
T |
F |
T |
|
nRTAC |
CM |
T |
T |
F |
T |
|
arfcnDL |
M |
T |
T |
F |
T |
|
arfcnUL |
CM |
T |
T |
F |
T |
|
arfcnSUL |
CM |
T |
T |
F |
T |
|
bSChannelBwDL |
M |
T |
T |
F |
T |
|
rimRSMonitoringStartTime |
O |
T |
T |
F |
T |
|
rimRSMonitoringStopTime |
O |
T |
T |
F |
T |
|
rimRSMonitoringWindowDuration |
O |
T |
T |
F |
T |
|
rimRSMonitoringWindowStartingOffset |
O |
T |
T |
F |
T |
|
rimRSMonitoringWindowPeriodicity |
O |
T |
T |
F |
T |
|
rimRSMonitoringOccasionInterval |
O |
T |
T |
F |
T |
|
rimRSMonitoringOccasionStartingOffset |
O |
T |
T |
F |
T |
|
ssbFrequency |
CM |
T |
T |
F |
T |
|
ssbPeriodicity |
M |
T |
T |
F |
T |
|
ssbSubCarrierSpacing |
CM |
T |
T |
F |
T |
|
ssbOffset |
M |
T |
T |
F |
T |
|
ssbDuration |
M |
T |
T |
F |
T |
|
bSChannelBwUL |
CM |
T |
T |
F |
T |
|
bSChannelBwSUL |
CM |
T |
T |
F |
T |
|
Attribute related to role |
|||||
|
nRSectorCarrierRef |
M |
T |
T |
F |
T |
|
bWPRef |
M |
T |
T |
F |
T |
|
nRFrequencyRef |
CO |
T |
T |
F |
T |
|
choice |
|||||
|
> bWPRef |
CM |
T |
T |
F |
T |
|
> bWPSetRef |
CM |
T |
T |
F |
T |
|
victimSetRef |
CM |
T |
T |
F |
T |
|
aggressorSetRef |
O |
T |
T |
F |
T |
|
Note 1: No state propagation is implied. Note 2: Void |
|||||
4.3.5.3 Attribute constraints
|
Name |
Definition |
|
arfcnUL S |
Condition: The cell has an uplink (FDD or TDD) |
|
arfcnSUL S |
Condition: The cell has a supplementary uplink |
|
nPNIdentityList S |
Condition: The cell is a NPN-only cell (see TS 38.331 [54]). |
|
bSChannelBwUL S |
Condition: The cell has an uplink (FDD or TDD) |
|
bSChannelBwSUL S |
Condition: The cell has a supplementary uplink |
|
nRFrequencyRef S |
Condition: Non-split deployment scenario is supported |
|
ssbFrequency S |
Condition: nRFrequencyRef is not used. |
|
ssbSubCarrierSpacing S |
Condition: nRFrequencyRef is not used. |
|
victimSetRef S |
Condition: RIM feature is supported |
|
bWPRef S |
Condition: BWP sets are not supported. |
|
bWPSetRef S |
Condition: BWP sets are supported. |
4.3.5.4 Notifications
The common notifications defined in subclause 4.5 are valid for this IOC, without exceptions or additions.
4.3.6 NRSectorCarrier
4.3.6.1 Definition
This <<IOC>>NRSectorCarrier represents the resources of each transmission point associated to corresponding cell(s). These in general have different physical locations (of the antennae), and possibly different frequencies or bandwidths. The UE is not directly aware of which NRSectorCarrier resources the network uses for its connection.
An NR sector-carrier can have downlink, uplink or both as specified by txDirection. Attributes related to unavailable direction (DL or UL) shall not be set.
Additional NRSectorCarriers not directly associated to one cell only can also be configured.
If a value of arfcnDL, arfcnUL, bSChannelBwDL or bSChannelBwUL can be derived unambiguously from the referring cell, then that attribute needs not be present. That will not be possible if the NRSectorCarrier is used for supplementary uplink, if it is not directly associated to a cell, or if the sector-carrier uses only a part of the cell’s channel bandwidth. Thus, at least in those cases the applicable attributes have to be present and their values need to be set.
4.3.6.2 Attributes
The NRSectorCarrier IOC includes attributes inherited from ManagedFunction IOC (defined in TS 28.622[30]) and the following attributes:
|
Attribute name |
S |
isReadable |
isWritable |
isInvariant |
isNotifyable |
|
txDirection |
M |
T |
T |
F |
T |
|
configuredMaxTxPower |
CM |
T |
T |
F |
T |
|
configuredMaxTxEIRP |
CM |
T |
T |
F |
T |
|
arfcnDL |
CM |
T |
T |
F |
T |
|
arfcnUL |
CM |
T |
T |
F |
T |
|
bSChannelBwDL |
CM |
T |
T |
F |
T |
|
bSChannelBwUL |
CM |
T |
T |
F |
T |
|
attribute related to role |
|||||
|
sectorEquipmentFunctionRef |
M |
T |
T |
F |
T |
4.3.6.3 Attribute constraints
|
Name |
Definition |
|
configuredMaxTxPower |
Condition: The sector-carrier has a downlink. Configuration of Tx power at antenna port reference point is supported. |
|
configuredMaxTxEIRP |
Condition: The sector-carrier has a downlink. Configuration of emitted isotropic radiated power is supported. |
|
arfcnDL |
Condition: The sector-carrier has a downlink AND the value differs from the referring cell’s value of arfcnDL. |
|
arfcnUL |
Condition: The sector-carrier has an uplink AND the value differs from the referring cell’s value of arfcnUL. |
|
bSChannelBwDL |
Condition: The sector-carrier has a downlink AND the value differs from the referring cell’s value of bSChannelBwDL. |
|
bSChannelBwUL |
Condition: The sector-carrier has an uplink AND the value differs from the referring cell’s value of bSChannelBwUL. |
4.3.6.4 Notifications
The common notifications defined in subclause 4.5 are valid for this IOC, without exceptions or additions.
4.3.7 BWP
4.3.7.1 Definition
This IOC represents a bandwidth part (BWP) defined in 3GPP TS 38.211 [32], subclause 4.4.5. A bandwidth part is related to downlink, uplink or supplementary uplink resource grids, and is defined by its subcarrier spacing (SCS), cyclic prefix and location and size related to the common resource grid for the applicable SCS.
A BWP can be either an initial BWP used for initial access, or other ("regular") BWP configured for relevant UEs that support the BWP’s characteristics.
4.3.7.2 Attributes
The BWP IOC includes attributes inherited from ManagedFunction IOC (defined in TS 28.622[30]) and the following attributes:
|
Attribute name |
S |
isReadable |
isWritable |
isInvariant |
isNotifyable |
|
bwpContext |
M |
T |
T |
F |
T |
|
isInitialBwp |
M |
T |
T |
F |
T |
|
subCarrierSpacing |
M |
T |
T |
F |
T |
|
cyclicPrefix |
M |
T |
T |
F |
T |
|
startRB |
M |
T |
T |
F |
T |
|
numberOfRBs |
M |
T |
T |
F |
T |
4.3.7.3 Attribute constraints
None.
4.3.7.4 Notifications
The common notifications defined in subclause 4.5 are valid for this IOC, without exceptions or additions.
4.3.8 EP_E1
4.3.8.1 Definition
This IOC represents the local end point of the logical link, supporting E1 interface between gNB-CU-CP and gNB-CU-UP. The E1 interface is defined in 3GPP TS 38.401 [4].
4.3.8.2 Attributes
The EP_E1 IOC includes attributes inherited from EP_RP IOC (defined in TS 28.622[30]) and the following attributes:
|
Attribute name |
S |
isReadable |
isWritable |
isInvariant |
isNotifyable |
|
localAddress |
O |
T |
T |
F |
T |
|
remoteAddress |
O |
T |
T |
F |
T |
4.3.8.3 Attribute constraints
None.
4.3.8.4 Notifications
The common notifications defined in subclause 4.5 are valid for this IOC, without exceptions or additions.
4.3.9 EP_XnU
4.3.9.1 Definition
This IOC represents the one end-point of a logical link supporting the Xn user plane (Xn-U) interface. The Xn-U interface provides non-guaranteed delivery of user plane PDUs between two NG-RAN nodes. The user plane PDUs are carried on GTP-U/UDP/IP/Data link layer/Physical layer stack. See subclause 7.2 of 3GPP TS 38.420 [6].
4.3.9.2 Attributes
The EP_XnU IOC includes attributes inherited from EP_RP IOC (defined in TS 28.622[30]) and the following attributes:
|
Attribute name |
S |
isReadable |
isWritable |
isInvariant |
isNotifyable |
|
localAddress |
O |
T |
T |
F |
T |
|
remoteAddress |
O |
T |
T |
F |
T |
4.3.9.3 Attribute constraints
None.
4.3.9.4 Notifications
The common notifications defined in subclause 4.5 are valid for this IOC, without exceptions or additions.
4.3.10 EP_NgC
4.3.10.1 Definition
This IOC represents the local end point of the control plane interface (NG-C) between the gNB and AMF. The transport network layer is built on IP transport. For the reliable transport of signalling messages, SCTP is added on top of IP. The application layer signalling protocol is referred to as NG-AP (NG Application Protocol).
3GPP TS 38.470 [7] noted that "one gNB-CU and a set of gNB-DUs are visible to other logical nodes as a gNB or an en-gNB where the gNB terminates the Xn and the NG interfaces, and the en-gNB terminates the X2 and the S1-U interfaces".
4.3.10.2 Attributes
The EP_NgC IOC includes attributes inherited from EP_RP IOC (defined in TS 28.622[30]) and the following attributes:
|
Attribute name |
S |
isReadable |
isWritable |
isInvariant |
isNotifyable |
|
localAddress |
O |
T |
T |
F |
T |
|
remoteAddress |
O |
T |
T |
F |
T |
4.3.10.3 Attribute constraints
None.
4.3.10.4 Notifications
The common notifications defined in subclause 4.5 are valid for this IOC, without exceptions or additions.
4.3.11 EP_NgU
4.3.11.1 Definition
This IOC represents the local end point of the NG user plane (NG-U) interface between the gNB and UPF. The interface provides non‑guaranteed delivery of user plane PDUs between the gNB and UPF. GTP-U is baseline for this interface.
3GPP TS 38.470 [7] noted that "one gNB-CU and a set of gNB-DUs are visible to other logical nodes as a gNB or an en-gNB where the gNB terminates the Xn and the NG interfaces, and the en-gNB terminates the X2 and the S1-U interfaces".
4.3.11.2 Attributes
The EP_NgU IOC includes attributes inherited from EP_RP IOC (defined in TS 28.622[30]) and the following attributes:
|
Attribute name |
S |
isReadable |
isWritable |
isInvariant |
isNotifyable |
|
localAddress |
O |
T |
T |
F |
T |
|
remoteAddress |
O |
T |
T |
F |
T |
|
Attribute related to role |
|||||
|
epTransportRef |
O |
T |
F |
F |
T |
4.3.11.3 Attribute constraints
None.
4.3.11.4 Notifications
The common notifications defined in subclause 4.5 are valid for this IOC, without exceptions or additions.
4.3.12 EP_F1C
4.3.12.1 Definition
This IOC represents the local end point of the control plane interface (F1-C) between the gNB-DU and gNB-CU or gNB-CU-CP. The transport network layer is based on IP transport with the SCTP on top of IP. The application layer signalling protocol is referred to as NG-AP (NG Application Protocol). See subclause 7.1 of 3GPP TS 38.470 [7].
3GPP TS 38.470 [7] noted that "one gNB-CU and a set of gNB-DUs are visible to other logical nodes as a gNB or an en-gNB where the gNB terminates the Xn and the NG interfaces, and the en-gNB terminates the X2 and the S1-U interfaces".
4.3.12.2 Attributes
The EP_F1C IOC includes attributes inherited from EP_RP IOC (defined in TS 28.622[30]) and the following attributes:
|
Attribute name |
S |
isReadable |
isWritable |
isInvariant |
isNotifyable |
|
localAddress |
O |
T |
T |
F |
T |
|
remoteAddress |
O |
T |
T |
F |
T |
4.3.12.3 Attribute constraints
None.
4.3.12.4 Notifications
The common notifications defined in subclause 4.5 are valid for this IOC, without exceptions or additions.
4.3.13 EP_F1U
4.3.13.1 Definition
This IOC represents the local end point of the user plane interface (F1-U) between the gNB-DU and gNB-CU or gNB-CU-UP. The transport network layer is based on IP transport, with the UDP and GTP-U on top of IP.
3GPP TS 38.470 [7] noted that "one gNB-CU and a set of gNB-DUs are visible to other logical nodes as a gNB or an en-gNB where the gNB terminates the Xn and the NG interfaces, and the en-gNB terminates the X2 and the S1-U interfaces".
4.3.13.2 Attributes
The EP_F1U IOC includes attributes inherited from EP_RP IOC (defined in TS 28.622[30]) and the following attributes:
|
Attribute name |
S |
isReadable |
isWritable |
isInvariant |
isNotifyable |
|
localAddress |
O |
T |
T |
F |
T |
|
remoteAddress |
O |
T |
T |
F |
T |
|
attribute related to role |
|||||
|
epTransportRef |
O |
T |
F |
F |
T |
4.3.13.3 Attribute constraints
None.
4.3.13.4 Notifications
The common notifications defined in subclause 4.5 are valid for this IOC, without exceptions or additions.
4.3.14 EP_S1U
4.3.14.1 Definition
This IOC represents the local end point of the logical link, supporting S1-U interface towards a S-GW node. The S1-U interface is defined in 3GPP TS 36.410 [14].
4.3.14.2 Attributes
The EP_S1U IOC includes attributes inherited from EP_RP IOC (defined in TS 28.622[30]) and the following attributes:
|
Attribute name |
S |
isReadable |
isWritable |
isInvariant |
isNotifyable |
|
localAddress |
O |
T |
T |
F |
T |
|
remoteAddress |
O |
T |
T |
F |
T |
4.3.14.3 Attribute constraints
None.
4.3.14.4 Notifications
The common notifications defined in subclause 4.5 are valid for this IOC, without exceptions or additions.
4.3.15 EP_X2C
4.3.15.1 Definition
This IOC represents the local end point of the logical link, supporting X2-C application protocols used in EN-DC, to a neighbour eNB or en-gNB node, which is defined in 3GPP TS 36.423 [15]. EN-DC is defined in 3GPP TS 37.340 [9].
4.3.15.2 Attributes
The EP_X2C IOC includes attributes inherited from EP_RP IOC (defined in TS 28.622[30]) and the following attributes:
|
Attribute name |
S |
isReadable |
isWritable |
isInvariant |
isNotifyable |
|
localAddress |
O |
T |
T |
F |
T |
|
remoteAddress |
O |
T |
T |
F |
T |
4.3.15.3 Attribute constraints
None.
4.3.15.4 Notifications
The common notifications defined in subclause 4.5 are valid for this IOC, without exceptions or additions.
4.3.16 EP_X2U
4.3.16.1 Definition
This IOC represents the local end-point of a logical link supporting the X2 user plane (X2-U) interface used in EN-DC, which is defined in 3GPP TS 36.425 [16].
4.3.16.2 Attributes
The EP_X2U IOC includes attributes inherited from EP_RP IOC (defined in TS 28.622[30]) and the following attributes:
|
Attribute name |
S |
isReadable |
isWritable |
isInvariant |
isNotifyable |
|
localAddress |
O |
T |
T |
F |
T |
|
remoteAddress |
O |
T |
T |
F |
T |
4.3.16.3 Attribute constraints
None.
4.3.16.4 Notifications
The common notifications defined in subclause 4.5 are valid for this IOC, without exceptions or additions.
4.3.17 EP_XnC
4.3.17.1 Definition
This IOC represents the local gNB node end point of the logical link, supporting Xn Application protocols, to a neighbour NG-RAN node (including gNB and ng-eNB). The Xn Application PDUs are carried over SCTP/IP/Data link layer/Physical layer stack. See subclause 7 of 3GPP TS 38.420 [6].
4.3.17.2 Attributes
The EP_XnC IOC includes attributes inherited from EP_RP IOC (defined in TS 28.622[30]) and the following attributes:
|
Attribute name |
S |
isReadable |
isWritable |
isInvariant |
isNotifyable |
|
localAddress |
O |
T |
T |
F |
T |
|
remoteAddress |
O |
T |
T |
F |
T |
4.3.17.3 Attribute constraints
None
4.3.17.4 Notifications
The common notifications defined in subclause 4.5 are valid for this IOC, without exceptions or additions.
4.3.18 ExternalGNBCUCPFunction
4.3.18.1 Definition
This IOC represents the properties, known by the management function, of a GNBCUCPFunction managed by another management function. For more information about GNBCUCPFunction, see subclause 4.3.2.
4.3.18.2 Attributes
The ExternalGNBCUCPFunction includes attributes inherited from ManagedFunction IOC (defined in TS 28.622[30]) and the following attributes:
|
Attribute name |
S |
isReadable |
isWritable |
isInvariant |
isNotifyable |
|
gNBId |
M |
T |
T |
F |
T |
|
gNBIdLength |
M |
T |
T |
F |
T |
|
pLMNId |
M |
T |
T |
F |
T |
4.3.18.3 Attribute constraints
None.
4.3.18.4 Notifications
The common notifications defined in subclause 4.5 are valid for this IOC, without exceptions or additions.
4.3.19 ExternalGNBCUUPFunction
4.3.19.1 Definition
This IOC represents the properties, known by the management function, of a GNBCUUPFunction managed by another management function. For more information about GNBCUUPFunction, see subclause 4.3.3.
4.3.19.2 Attributes
The ExternalGNBCUUPFunction includes attributes inherited from ManagedFunction IOC (defined in TS 28.622[30]) and the following attributes:
|
Attribute name |
S |
isReadable |
isWritable |
isInvariant |
isNotifyable |
|
gNBId |
M |
T |
T |
F |
T |
|
gNBIdLength |
M |
T |
T |
F |
T |
4.3.19.3 Attribute constraints
None.
4.3.19.4 Notifications
The common notifications defined in subclause 4.5 are valid for this IOC, without exceptions or additions.
4.3.20 ExternalGNBDUFunction
4.3.20.1 Definition
This IOC represents the properties, known by the management function, of a GNBDUFunction managed by another management function. For more information about GNBDUFunction, see subclause 4.3.1.
4.3.20.2 Attributes
The ExternalGNBDUFunction includes attributes inherited from ManagedFunction IOC (defined in TS 28.622[30]) and the following attributes:
|
Attribute name |
S |
isReadable |
isWritable |
isInvariant |
isNotifyable |
|
gNBId |
M |
T |
T |
T |
T |
|
gNBIdLength |
M |
T |
T |
F |
T |
4.3.20.3 Attribute constraints
None.
4.3.20.4 Notifications
The common notifications defined in subclause 4.5 are valid for this IOC, without exceptions or additions.
4.3.21 ExternalUPFFunction
4.3.21.1 Definition
This IOC represents the properties, known by the management function, of a UPFFunction managed by another management function. For more information about UPFFunction, see subclause 5.3.3.
4.3.21.2 Attributes
The ExternalUPFFunction includes attributes inherited from ManagedFunction IOC (defined in TS 28.622[30]) and the following attributes:
|
Attribute name |
S |
isReadable |
isWritable |
isInvariant |
isNotifyable |
4.3.21.3 Attribute constraints
None.
4.3.21.4 Notifications
The common notifications defined in subclause 4.5 are valid for this IOC, without exceptions or additions.
4.3.22 ExternalAMFFunction
4.3.22.1 Definition
This IOC represents the properties, known by the management function, of an AMFFunction managed by another management function. For more information about AMFFunction, see subclause 5.3.
4.3.22.2 Attributes
The ExternalAMFFunction includes attributes inherited from ManagedFunction IOC (defined in TS 28.622[30]) and the following attributes:
|
Attribute name |
S |
isReadable |
isWritable |
isInvariant |
isNotifyable |
4.3.22.3 Attribute constraints
None
4.3.22.4 Notifications
The common notifications defined in subclause 4.5 are valid for this IOC, without exceptions or additions.
4.3.23 Void
4.3.24 ENBFunction <<ProxyClass>>
4.3.24.1 Definition
This IOC represents an <<IOC>>ENBFunction and <<IOC>>ExternalENBFunction.
4.3.24.2 Attributes
See that defined in <<IOC>>ENBFunction and <<IOC>>ExternalENBFunction.
4.3.24.3 Attribute constraints
See that defined in <<IOC>>ENBFunction and <<IOC>>ExternalENBFunction.
4.3.24.4 Notifications
See respective IOCs.
4.3.25 GNBCUCPFunction <<ProxyClass>>
4.3.25.1 Definition
This IOC represents an <<IOC>>GNBCUCPFunction and <<IOC>>ExternalGNBCUCPFunction.
4.3.25.2 Attributes
See that defined in <<IOC>>GNBCUCPFunction and <<IOC>>ExternalGNBCUCPFunction.
4.3.25.3 Attribute constraints
See respective IOCs.
4.3.25.4 Notifications
See respective IOCs.
4.3.26 GNBCUUPFunction <<ProxyClass>>
4.3.26.1 Definition
This IOC represents an <<IOC>>GNBCUUPFunction and <<IOC>>ExternalGNBCUUPFunction.
4.3.26.2 Attributes
See that defined in <<IOC>>GNBCUUPFunction and <<IOC>>ExternalGNBCUUPFunction.
4.3.26.3 Attribute constraints
See that defined in <<IOC>>GNBCUUPFunction and <<IOC>>ExternalGNBCUUPFunction.
4.3.26.4 Notifications
See respective IOCs.
4.3.27 GNBDUFunction <<ProxyClass>>
4.3.27.1 Definition
This IOC represents an <<IOC>>GNBDUFunction and <<IOC>>ExternalGNBDUFunction.
4.3.27.2 Attributes
See that defined in <<IOC>>GNBDUFunction and <<IOC>>ExternalGNBDUFunction.
4.3.27.3 Attribute constraints
See that defined in <<IOC>>GNBDUFunction and <<IOC>>ExternalGNBDUFunction.
4.3.27.4 Notifications
See respective IOCs.
4.3.28 ServingGWFFunction <<ProxyClass>>
4.3.28.1 Definition
This IOC represents an <<IOC>>ServingGWFFunction and <<IOC>>ExternalServingGWFunction.
4.3.28.2 Attributes
See that defined in <<IOC>>ServingGWFunction and <<IOC>>ExternalServingGWFunction.
4.3.28.3 Attribute constraints
See that defined in <<IOC>>ServingGWFunction and <<IOC>>ExternalServingGWFunction.
4.3.28.4 Notifications
See respective IOCs.
4.3.29 UPFFunction <<ProxyClass>>
4.3.29.1 Definition
This IOC represents an <<IOC>>UPFFunction and <<IOC>>ExternalUPFFunction.
4.3.29.2 Attributes
See that defined in <<IOC>>UPFFunction and <<IOC>>ExternalUPFFunction.
4.3.29.3 Attribute constraints
See that defined in <<IOC>>UPFFunction and <<IOC>>ExternalUPFFunction.
4.3.29.4 Notifications
See respective IOCs.
4.3.30 AMFFunction <<ProxyClass>>
4.3.30.1 Definition
This IOC represents an <<IOC>>AMFFunction and <<IOC>>ExternalAMFFunction.
4.3.30.2 Attributes
See that defined in <<IOC>>AMFFunction and <<IOC>>ExternalAMFFunction.
4.3.30.3 Attribute constraints
See that defined in <<IOC>>AMFFunction and <<IOC>>ExternalAMFFunction.
4.3.30.4 Notifications
See respective IOCs.
4.3.31 Void
4.3.32 NRCellRelation
4.3.32.1 Definition
This IOC represents a neighbour cell relation from a source cell to a target cell, where the target cell is an NRCellCU or ExternalNRCellCU instance.
The source cell can be a NRCellCU instance. This is the case for an Intra-NR neighbour cell relation.
The source cell can be a EUtranGenericCell instance. This is the case for Inter-LTE-NR neighbour cell relation, from E-UTRAN to NR. See 3GPP TS 28.658 [19].
Neighbour cell relations are unidirectional.
4.3.32.2 Attributes
The NRCellRelation IOC includes attributes inherited from Top IOC (defined in TS 28.622[30]) and the following attributes:
|
Attribute name |
S |
isReadable |
isWritable |
isInvariant |
isNotifyable |
|
nRTCI |
O |
T |
T |
F |
T |
|
cellIndividualOffset |
M |
T |
T |
F |
T |
|
isRemoveAllowed |
CM |
T |
T |
F |
T |
|
isHOAllowed |
CM |
T |
T |
F |
T |
|
isESCoveredBy |
CM |
T |
T |
F |
T |
|
isENDCAllowed |
CM |
T |
T |
F |
T |
|
isMLBAllowed |
CM |
T |
T |
F |
T |
|
attribute related to role |
|||||
|
nRFreqRelationRef |
M |
T |
T |
F |
T |
|
adjacentNRCellRef |
M |
T |
T |
F |
T |
4.3.32.3 Attribute constraints
|
Name |
Definition |
|
isRemoveAllowed |
Condition: ANR function is supported in the source cell. |
|
isHOAllowed |
Condition: ANR function is supported in the source cell. |
|
isESCoveredBy |
Condition: Energy Saving function is supported. |
|
isENDCAllowed |
Condition: Multi-Radio Dual Connectivity with the EPC (see TS 37.340 [9] clause 4.1.2) is supported. |
|
isMLBAllowed |
Condition: MLB function is supported in the source cell. |
4.3.32.4 Notifications
The common notifications defined in subclause 4.5 are valid for this IOC, without exceptions or additions.
4.3.33 NRFreqRelation
4.3.33.1 Definition
This IOC, together with the target NRFrequency, represents the frequency properties applicable to the referencing NRCellRelation.
4.3.33.2 Attributes
The NRFreqRelation IOC includes attributes inherited from Top IOC (defined in TS 28.622[30]) and the following attributes:
|
Attribute name |
S |
isReadable |
isWritable |
isInvariant |
isNotifyable |
|
offsetMO |
O |
T |
T |
F |
F |
|
blockListEntry |
O |
T |
T |
F |
F |
|
blockListEntryIdleMode |
O |
T |
T |
F |
F |
|
cellReselectionPriority |
O |
T |
T |
F |
F |
|
cellReselectionSubPriority |
O |
T |
T |
F |
F |
|
pMax |
O |
T |
T |
F |
F |
|
qOffsetFreq |
O |
T |
T |
F |
F |
|
qQualMin |
O |
T |
T |
F |
F |
|
qRxLevMin |
M |
T |
T |
F |
F |
|
threshXHighP |
M |
T |
T |
F |
F |
|
threshXHighQ |
CM |
T |
T |
F |
F |
|
threshXLowP |
M |
T |
T |
F |
F |
|
threshXLowQ |
CM |
T |
T |
F |
F |
|
tReselectionNr |
M |
T |
T |
F |
F |
|
tReselectionNRSfHigh |
O |
T |
T |
F |
F |
|
tReselectionNRSfMedium |
O |
T |
T |
F |
F |
|
attribute related to role |
|||||
|
nRFrequencyRef |
M |
T |
T |
F |
F |
4.3.33.3 Attribute constraints
|
Name |
Definition |
|
threshXHighQ |
Condition: RSRQ used in SIB4. |
|
threshXLowQ |
Condition: RSRQ used in SIB4. |
4.3.33.4 Notifications
The common notifications defined in subclause 4.5 are valid for this IOC, without exceptions or additions.
4.3.34 Void
4.3.35 ExternalNRCellCU
4.3.35.1 Definition
This abstract IOC represents the properties of an NRCellCU controlled by another Management Service Provider. This IOC contains necessary attributes for inter-system and intra-system handover. It also contains a subset of the attributes of related IOCs controlled by Management Service Provider. The way to maintain consistency between the attribute values of these IOCs is outside the scope of the present document.
4.3.35.2 Attributes
The ExternalNRCellCU IOC includes attributes inherited from ManagedFunction IOC (defined in TS 28.622[30]) and the following attributes:
|
Attribute name |
S |
isReadable |
isWritable |
isInvariant |
isNotifyable |
|
cellLocalId |
M |
T |
T |
F |
T |
|
nRPCI |
M |
T |
T |
F |
T |
|
plmnIdList |
M |
T |
T |
F |
T |
|
attribute related to role |
|||||
|
nRFrequencyRef |
M |
T |
T |
F |
T |
4.3.35.3 Attribute constraints
None.
4.3.35.4 Notifications
The common notifications defined in subclause 4.5 are valid for this IOC, without exceptions or additions.
4.3.36 RRMPolicyRatio
4.3.36.1 Definition
This IOC represents the properties of RRMPolicyRatio. RRMPolicyRatio is one realization of abstract RRMPolicy_ IOC. RRMPolicyRatio has three attributes, apart from those inherited (DN, resourceType, rRMPolicyMemberList).
Figure 4.3.36-1 Structure of RRMPolicyRatio
– The attribute rRMPolicyMaxRatio defines the maximum resource usage quota for the associated rRMPolicyMemberList, including at least one of shared resources, prioritized resources and dedicated resources. The sum of the ‘rRMPolicyMaxRatio’ values assigned to all RRMPolicyRatio(s) name-contained by same MangedEntity can be greater than 100.
– The attribute rRMPolicyMinRatio defines the minimum resource usage quota for the associated RRMPolicyMemberList, including at least one of prioritized resources and dedicated resources, which means the resources quota that need to be guaranteed for use by the associated rRMPolicyMemberList. The sum of the ‘rRMPolicyMinRatio’ values assigned to all RRMPolicyRatio(s) name-contained by same MangedEntity shall be less or equal 100.
– The attribute rRMPolicyDedicatedRatio defines the dedicated resource usage quota for the RRMPolicyMemberList, including dedicated resources. The sum of the ‘rRMPolicyDedicatedRatio’ values assigned to all RRMPolicyRatio(s) name-contained by same MangedEntity shall be less or equal 100.
The following are the definition for above mentioned three resource categories:
– Shared resources: means the resources that are shared with other rRMPolicyMemberList(s) (i.e. the rRMPolicyMemberList(s) defined in RRMPolicyRatio(s) name-contained by the same ManagedEntity). The shared resources are not guaranteed for use by the associated rRMPolicyMemberList. The shared resources quota is represented by [rRMPolicyMaxRatio-rRMPolicyMinRatio].
– Priortized resources: means the resources are preferentially used by the associated RRMPolicyMemberList. These resources are guaranteed for use by the associated RRMPolicyMemberList when it needs to use them. When not used, these resources may be used by other rRMPolicyMemberList(s) (i.e. the rRMPolicyMemberList(s) defined in RRMPolicyRatio(s) name-contained by the same ManagedEntity). The prioritized resources quota is represented by [rRMPolicyMinRatio-rRMPolicyDedicatedRatio]
– Dedicated resources: means the resources are dedicated for use by the associated RRMPolicyMemberList. These resources can not be shared even if the associated RRMPolicyMember does not use them. The Dedicated resources quota is represented by [rRMPolicyDedicatedRatio].
NOTE: The resources shown in Figure 4.3.36-1 could be reserved or allocated for user and bearer related requests, e.g. a user connection, a PDU session, etc., if the user is entitled to use the allocated resources according the ratios defined above.
4.3.36.2 Attributes
The RRMPolicyRatio IOC includes attributes inherited from RRMPolicy_ IOC (defined in clause 4.3.43) and the following attributes:
|
Attribute name |
S |
isReadable |
isWritable |
isInvariant |
isNotifyable |
|
rRMPolicyMaxRatio |
M |
T |
T |
F |
T |
|
rRMPolicyMinRatio |
M |
T |
T |
F |
T |
|
rRMPolicyDedicatedRatio |
O |
T |
T |
F |
T |
4.3.36.3 Attribute constraints
None
4.3.36.4 Notifications
The common notifications defined in subclause 4.5 are valid for this IOC, without exceptions or additions.
4.3.37 S-NSSAI <<dataType>>
4.3.37.1 Definition
This data type represents an S-NSSAI. An NSSAI is a set of supported S-NSSAI(s), an S-NSSAI is comprised of an SST (Slice/Service type) and an optional SD (Slice Differentiator) field, (See TS 23.003 [13]).
4.3.37.2 Attributes
|
Attribute name |
S |
isReadable |
isWritable |
isInvariant |
isNotifyable |
|
sST |
M |
T |
T |
F |
T |
|
sD |
O |
T |
T |
F |
T |
4.3.37.3 Attribute constraints
None
4.3.37.4 Notifications
The subclause 4.5 of the <<IOC>> using this <<dataType>> as one of its attributes, shall be applicable.
4.3.38 NRFrequency
4.3.38.1 Definition
This IOC represents certain NR frequency properties.
4.3.38.2 Attributes
The NRFrequency IOC includes attributes inherited from Top IOC (defined in TS 28.622[30]) and the following attributes:
|
Attribute name |
S |
isReadable |
isWritable |
isInvariant |
isNotifyable |
|
absoluteFrequencySSB |
M |
T |
T |
F |
T |
|
sSBSubCarrierSpacing |
M |
T |
T |
F |
T |
|
multiFrequencyBandListNR |
O |
T |
F |
F |
T |
4.3.38.3 Attribute constraints
None.
4.3.38.4 Notifications
The common notifications defined in subclause 4.5 are valid for this IOC, without exceptions or additions.
4.3.39 CommonBeamformingFunction
4.3.39.1 Definition
This <<IOC>>CommonBeamformingFunction represents common beamforming functionality (eg: SSB beams) for the NRSectorCarrier.
The CommonBeamformingFunction provides capability to configure the advanced antenna for a sector carrier. The configuration capability is provided by selection of coverageShape, digitalTilt and digitalAzimuth. These attributes represent the wanted coverage area and radiation pattern on a sector carrier related to an antenna transmission point.
This configuration capability assumes the system shall handle configuration of SSB beams within the sector carrier. Individual SSB beams within a sector carrier cannot be independently configured as this depends on many conditions and constraints, for instance TDD patterns, allocations of PRACH occasions, SIB1 and mobility considerations.
The associated <<IOC>> Beam provides information beam direction and beam width for the associated SSB beams as a result of the configuration. The beams addressed in this definition are the common beams. There may be more than one beam per CommonBeamformingFunction for the NRSectorCarrier.
4.3.39.2 Attributes
The CommonBeamformingFunction IOC includes attributes inherited from Top IOC (defined in TS 28.622[30]) and the following attributes:
|
Attribute name |
S |
isReadable |
isWritable |
isInvariant |
isNotifyable |
|
coverageShape |
M |
T |
T |
F |
T |
|
digitalTilt |
M |
T |
T |
F |
T |
|
digitalAzimuth |
M |
T |
T |
F |
T |
4.3.39.3 Attribute constraints
None.
4.3.39.4 Notifications
The common notifications defined in subclause 4.5 are valid for this IOC, without exceptions or additions.
4.3.40 Beam
4.3.40.1 Definition
This <<IOC>>Beam represents the per-Beam information required for, e.g. beam performance management utilizing measurements generated in the RAN. TS 38.104 [12] relates to beam transmission, TS 38.215 [55] to beam measurements, and TS 38.331 [54] to reporting of those measurements and associated beam failure Information Elements, clauses 5.5.3, 5.5.5.2, 6.3.2. 6.2.2.
Measurements on common beams may be correlated with associated spatial beam information to assist use cases like troubleshooting performance problems, or SON functions like Coverage & Capacity Optimization.
<<IOC>>Beam can have spatial attributes of horizontal/azimuth (ie: Phi φ-axis) and vertical/tilt (ie: Theta θ-axis) beam pointing direction and beam width attributes. There may be more than one beam per CommonBeamformingFunction for an NRSectorCarrier. Informational note, beam direction and width are characteristics—a representation—of directional energy vectors.
4.3.40.2 Attributes
|
Attribute name |
S |
isReadable |
isWritable |
isInvariant |
isNotifyable |
|
beamIndex |
M |
T |
F |
F |
T |
|
beamType |
O |
T |
F |
F |
T |
|
beamAzimuth |
CM |
T |
F |
F |
T |
|
beamTilt |
CM |
T |
F |
F |
T |
|
beamHorizWidth |
CM |
T |
F |
F |
T |
|
beamVertWidth |
CM |
T |
F |
F |
T |
4.3.40.3 Attribute constraints
The Beam IOC includes attributes inherited from Top IOC (defined in TS 28.622[30]) and the following attributes:
|
Name |
Definition |
|
beamAzimuth S |
Condition: The beamType is "SSB-BEAM" and Supported by Equipment |
|
beamTilt S |
Condition: The beamType is "SSB-BEAM" and Supported by Equipment |
|
beamHorizWidth S |
Condition: The beamType is "SSB-BEAM" and Supported by Equipment |
|
beamVertWidth S |
Condition: The beamType is "SSB-BEAM" and Supported by Equipment |
4.3.41 PLMNInfo <<dataType>>
4.3.41.1 Definition
This <<dataType>> represents the PLMN supported by the <<IOC>> using this <<dataType>> as one of its attributes. In case of network slicing feature is supported, this <<dateType>> also represents the S-NSSAI in the PLMN supported by the <<IOC>> using this <<dataType>> as one of its attributes.
4.3.41.2 Attributes
|
Attribute name |
S |
isReadable |
isWritable |
isInvariant |
isNotifyable |
|
pLMNId |
M |
T |
T |
F |
T |
|
sNSSAI |
CM |
T |
T |
F |
T |
4.3.41.3 Attribute constraints
|
Name |
Definition |
|
sNSSAI S |
Condition: Network slicing feature is supported. |
4.3.41.4 Notifications
The <<IOC>> using this <<dataType>> as one of its attributes, shall be applicable.
4.3.42 RRMPolicyMember <<dataType>>
4.3.42.1 Definition
This <<dataType>> represents an RRM Policy member that will be part of a rRMPolicyMemberList. A RRMPolicyMember is defined by its pLMNId and sNSSAI (S-NSSAI). The members in a rRMPolicyMemberList is assigned a specific amount of RRM resources based on settings in RRMPolicy_.
4.3.42.2 Attributes
|
Attribute name |
S |
isReadable |
isWritable |
isInvariant |
isNotifyable |
|
pLMNId |
M |
T |
T |
F |
T |
|
sNSSAI |
CM |
T |
T |
F |
T |
4.3.42.3 Attribute constraints
|
Name |
Definition |
|
sNSSAI S |
Condition: Network slicing is supported |
4.3.42.4 Notifications
The common notifications defined in subclause 4.5 are valid for this IOC, without exceptions or additions.
4.3.43 RRMPolicy_
4.3.43.1 Definition
This IOC represents the properties of an abstract RRMPolicy. The RRMPolicy_ IOC needs to be subclassed to be instantiated. It defines two attributes apart from those inherited from TOP IOC, the resourceType attribute defines type of resource (PRB, PRB in uplink, PRB in downlink,RRC connected users, DRB usage etc.) and the rRMPolicyMemberList attribute defines the RRMPolicyMember(s)that is subject to this policy. An RRM resource (defined in resourceType attribute) is located in NRCellDU, NRCellCU, GNBDUFunction, GNBCUCPFunction or in GNBCUUPFunction. The RRMPolicyRatio IOC is one realization of a RRMPolicy_ IOC, see the inheritance in Figure 4.2.1.2-1. This RRM framework allows adding new policies, both standardized or as vendor specific, by inheriting from the abstract RRMPolicy_ IOC.
4.3.43.2 Attributes
The RRMPolicy_ IOC have the following attributes, apart from those inherited from TOP IOC (defined in TS 28.622 [30]):
|
Attribute name |
S |
isReadable |
isWritable |
isInvariant |
isNotifyable |
|
resourceType |
M |
T |
T |
F |
T |
|
rRMPolicyMemberList |
M |
T |
T |
F |
T |
4.3.43.3 Attribute constraints
None.
4.3.43.4 Notifications
The common notifications defined in subclause 4.5 are valid for this IOC, without exceptions or additions.
4.3.44 RRMPolicyManagedEntity <<ProxyClass>>
4.3.44.1 Definition
This represents an <<IOC>>NRCellCU, or an <<IOC>>NRCellDU or an <<IOC>>GNBCUUPFunction, or an <<IOC>>GNBCUCPFunction, or an <<IOC>>GNBDUFunction.
If <<IOC>>NRCellCU is used, which means that a RRMPolicy shall be applied to an RRM resource in the NRCellCU. The possible RRM resource(s) owned by NRCellCU is defined in the resourceType attribute.
If <<IOC>>NRCellDU is used, which means that a RRMPolicy shall be applied to an RRM resource in the NRCellDU. The possible RRM resource(s) owned by NRCellDU is defined in the resourceType attribute.
If <<IOC>>GNBCUUPFunction is used, which means that a RRMPolicy shall be applied to an RRM resource in the GNBCUUPFunction. The possible RRM resource(s) owned by GNBCUUPFunction is defined in the resourceType attribute.
If <<IOC>>GNBCUCPFunction is used, which means that a RRMPolicy shall be applied to an RRM resource in the GNBCUCPFunction. The possible RRM resource(s) owned by GNBCUCPFunction is defined in the resourceType attribute.
If <<IOC>>GNBDUFunction is used, which means that a RRMPolicy shall be applied to an RRM resource in the GNBDUFunction. The possible RRM resource(s) owned by GNBDUFunction is defined in the resourceType attribute.
4.3.44.2 Attributes
See that defined in <<IOC>>NRCellCU, <<IOC>>NRCellDU, <<IOC>>GNBCUUPFunction, <<IOC>>GNBCUCPFunction or <<IOC>>GNBDUFunction.
4.3.44.3 Attribute constraints
See that defined in <<IOC>>NRCellCU, <<IOC>>NRCellDU, <<IOC>>GNBCUUPFunction, <<IOC>>GNBCUCPFunction, or <<IOC>>GNBDUFunction.
4.3.44.4 Notifications
See respective IOCs.
4.3.45 GNBCUCPNeighbour <<ProxyClass>>
4.3.45.1 Definition
This IOC represents an <<IOC>>GNBCUCPFunction, <<IOC>>ExternalGNBCUCPFunction, <<IOC>>ENBFunction and <<IOC>>ExternalENBFunction.
4.3.45.2 Attributes
See that defined in <<IOC>>GNBCUCPFunction, <<IOC>>ExternalGNBCUCPFunction, <<IOC>>ENBFunction and <<IOC>>ExternalENBFunction.
4.3.45.3 Attribute constraints
See that defined in <<IOC>>GNBCUCPFunction, <<IOC>>ExternalGNBCUCPFunction, <<IOC>>ENBFunction and <<IOC>>ExternalENBFunction.
4.3.45.4 Notifications
See respective IOCs.
4.3.46 GNBCUUPNeighbour <<ProxyClass>>
4.3.46.1 Definition
This IOC represents an <<IOC>>GNBCUUPFunction, <<IOC>>ExternalGNBCUUPFunction, <<IOC>>ENBFunction and <<IOC>>ExternalENBFunction.
4.3.46.2 Attributes
See that defined in <<IOC>>GNBCUUPFunction, <<IOC>>ExternalGNBCUUPFunction, <<IOC>>ENBFunction and <<IOC>>ExternalENBFunction.
4.3.46.3 Attribute constraints
See that defined in <<IOC>>GNBCUUPFunction, <<IOC>>ExternalGNBCUUPFunction, <<IOC>>ENBFunction and <<IOC>>ExternalENBFunction.
4.3.46.4 Notifications
See respective IOCs.
4.3.47 MappingSetIDBackhaulAddress <<dataType>>
4.3.47.1 Definition
This data type represents the properties describing the mapping relationship between set ID and backhaul address of gNB.
4.3.47.2 Attributes
|
Attribute name |
S |
isReadable |
isWritable |
isInvariant |
isNotifyable |
|
setID |
M |
T |
T |
F |
T |
|
backhaulAddress |
M |
T |
T |
F |
T |
4.3.47.3 Attribute constraints
None.
4.3.47.4 Notifications
The subclause 4.5 of the <<IOC>> using this <<dataType>> as one of its attributes, shall be applicable.
4.3.48 BackhaulAddress <<dataType>>
4.3.48.1 Definition
This data type represents the properties describing the backhaul address of gNB.
4.3.48.2 Attributes
|
Attribute name |
S |
isReadable |
isWritable |
isInvariant |
isNotifyable |
|
gNBId |
M |
T |
T |
F |
T |
|
tAI |
M |
T |
T |
F |
T |
4.3.48.3 Attribute constraints
None.
4.3.48.4 Notifications
The subclause 4.5 of the <<IOC>> using this <<dataType>> as one of its attributes, shall be applicable.
4.3.49 TAI <<dataType>>
4.3.49.1 Definition
This data type represents the properties describing the TAI of gNB, which is used to uniquely identify a Tracking Area.
4.3.49.2 Attributes
|
Attribute name |
S |
isReadable |
isWritable |
isInvariant |
isNotifyable |
|
pLMNId |
M |
T |
T |
F |
T |
|
nRTAC |
M |
T |
T |
F |
T |
4.3.49.3 Attribute constraints
None.
4.3.49.4 Notifications
The subclause 4.5 of the <<IOC>> using this <<dataType>> as one of its attributes, shall be applicable.
4.3.50 RimRSGlobal
4.3.50.1 Definition
This IOC is used to represent global/common Remote Interference Management (RIM) Reference Signal (RS) resource allocated for the whole network. Resource for RIM-RS transmission is defined by Sequence domain resource, Time domain resource and Frequency resource. The configure parameters of the RIM RS resource are applied to all Sets of RIM RS Resource across gNBs/cells in the network.
4.3.50.2 Attributes
The RimRSGlobal IOC includes attributes inherited from Top IOC (defined in TS 28.622[30]) and the following attributes:
|
Attribute name |
S |
isReadable |
isWritable |
isInvariant |
isNotifyable |
|
frequencyDomainPara |
M |
T |
T |
F |
T |
|
sequenceDomainPara |
M |
T |
T |
F |
T |
|
timeDomainPara |
M |
T |
T |
F |
T |
4.3.50.3 Attribute constraints
None.
4.3.50.4 Notifications
The common notifications defined in subclause 4.5 are valid for this IOC, without exceptions or additions.
4.3.51 FrequencyDomainPara <<dataType>>
4.3.51.1 Definition
This data type defines configuration parameters of frequency domain resource to support RIM RS.
4.3.51.2 Attributes
|
Attribute name |
S |
isReadable |
isWritable |
isInvariant |
isNotifyable |
|
rimRSSubcarrierSpacing |
M |
T |
T |
F |
T |
|
rIMRSBandwidth |
M |
T |
T |
F |
T |
|
nrofGlobalRIMRSFrequencyCandidates |
M |
T |
T |
F |
T |
|
rimRSCommonCarrierReferencePoint |
M |
T |
T |
F |
T |
|
rimRSStartingFrequencyOffsetIdList |
M |
T |
T |
F |
T |
4.3.51.3 Attribute constraints
None.
4.3.51.4 Notifications
The subclause 4.5 of the <<IOC>> using this <<dataType>> as one of its attributes, shall be applicable.
4.3.52 SequenceDomainPara <<dataType>>
4.3.52.1 Definition
This data type defines configuration parameters of sequence domain resource to support RIM RS.
4.3.52.2 Attributes
|
Attribute name |
S |
isReadable |
isWritable |
isInvariant |
isNotifyable |
|
nrofRIMRSSequenceCandidatesofRS1 |
M |
T |
T |
F |
T |
|
rimRSScrambleIdListofRS1 |
M |
T |
T |
F |
T |
|
nrofRIMRSSequenceCandidatesofRS2 |
O |
T |
T |
F |
T |
|
rimRSScrambleIdListofRS2 |
O |
T |
T |
F |
T |
|
enableEnoughNotEnoughIndication |
M |
T |
T |
F |
T |
|
RIMRSScrambleTimerMultiplier |
M |
T |
T |
F |
T |
|
RIMRSScrambleTimerOffset |
M |
T |
T |
F |
T |
4.3.52.3 Attribute constraints
None.
4.3.52.4 Notifications
The subclause 4.5 of the <<IOC>> using this <<dataType>> as one of its attributes, shall be applicable.
4.3.53 TimeDomainPara <<dataType>>
4.3.53.1 Definition
This data type defines configuration parameters of time domain resource to support RIM RS.
4.3.53.2 Attributes
|
Attribute name |
S |
isReadable |
isWritable |
isInvariant |
isNotifyable |
|
dlULSwitchingPeriod1 |
M |
T |
T |
F |
T |
|
M |
T |
T |
F |
T |
|
|
dlULSwitchingPeriod2 |
O |
T |
T |
F |
T |
|
symbolOffsetOfReferencePoint2 |
O |
T |
T |
F |
T |
|
totalnrofSetIdofRS1 |
M |
T |
T |
F |
T |
|
totalnrofSetIdofRS2 |
O |
T |
T |
F |
T |
|
nrofConsecutiveRIMRS1 |
M |
T |
T |
F |
T |
|
nrofConsecutiveRIMRS2 |
O |
T |
T |
F |
T |
|
consecutiveRIMRS1List |
M |
T |
T |
F |
T |
|
consecutiveRIMRS2List |
M |
T |
T |
F |
T |
|
enablenearfarIndicationRS1 |
O |
T |
T |
F |
T |
|
enablenearfarIndicationRS2 |
O |
T |
T |
F |
T |
4.3.53.3 Attribute constraints
None.
4.3.53.4 Notifications
The subclause 4.5 of the <<IOC>> using this <<dataType>> as one of its attributes, shall be applicable.
4.3.54 RimRSReportConf <<dataType>>
4.3.54.1 Definition
This data type defines RIM-RS reporting configuration.
4.3.54.2 Attributes
|
Attribute name |
S |
isReadable |
isWritable |
isInvariant |
isNotifyable |
|
reportIndicator |
M |
T |
T |
F |
T |
|
reportInterval |
M |
T |
T |
F |
T |
|
nrofRIMRSReportInfo |
M |
T |
T |
F |
T |
|
maxPropagationDelay |
O |
T |
T |
F |
T |
|
RimRSReportInfoList |
M |
T |
T |
F |
T |
4.3.54.3 Attribute constraints
None.
4.3.54.4 Notifications
The subclause 4.5 of the <<IOC>> using this <<dataType>> as one of its attributes, shall be applicable.
4.3.55 RimRSReportInfo <<dataType>>
4.3.55.1 Definition
This data type defines necessary reporting information derived from the detected RIM-RS, including
1) The detected set ID;
2) Propagation delay in number of OFDM symbols
3) Functionality of the RS (RS-1 or RS-2, Enough or Not enough mitigation for RS-1).
NOTE:
RS-1 is equivalent to RIM-RS type 1 (see 38.211 [32], subclause 7.4.1.6).
RS-2 is equivalent to RIM-RS type 2 (see 38.211 [32], subclause 7.4.1.6).
Enough mitigation for RS-1 means "Enough" / "Not enough" indication functionality is enabled for RIM RS-1 and RIM-RS type 1 is used to indicate ‘enough mitigation’ functionality.
Not enough mitigation for RS-1 means "Enough" / "Not enough" indication functionality is enabled for RIM RS-1 and RIM-RS type 1 is used to indicate ‘Not enough mitigation’ functionality.
4.3.55.2 Attributes
|
Attribute name |
S |
isReadable |
isWritable |
isInvariant |
isNotifyable |
|
detectedSetID |
M |
T |
T |
F |
T |
|
propagationDelay |
O |
T |
T |
F |
T |
|
functionalityOfRIMRS |
M |
T |
T |
F |
T |
4.3.55.3 Attribute constraints
None.
4.3.55.4 Notifications
The subclause 4.5 of the <<IOC>> using this <<dataType>> as one of its attributes, shall be applicable.
4.3.56 RimRSSet
4.3.56.1 Definition
This IOC is used to represent aggressor or victim Set organized by OAM. The RIM RS Resource is assigned to each Set, which is identified by triple indices set of <Time domain index, Frequency domain index, and Sequence index >. The triple indices set can be derived by setId attribute (See subclause 7.4.1.6 in TS 38.211 [32]).
4.3.56.2 Attributes
The RimRSSet IOC includes attributes inherited from Top IOC (defined in TS 28.622[30]) and the following
attributes:
|
Attribute name |
S |
isReadable |
isWritable |
isInvariant |
isNotifyable |
|
setId |
M |
T |
T |
F |
T |
|
setType |
M |
T |
T |
F |
T |
|
Attribute related to role |
|||||
|
nRCellDURef |
M |
T |
F |
F |
T |
4.3.56.3 Attribute constraints
None.
4.3.56.4 Notifications
The common notifications defined in subclause 4.5 are valid for this IOC, without exceptions or additions.
4.3.57 DANRManagementFunction
4.3.57.1 Definition
This IOC contains attributes to support the D-SON function of ANR Management (See clause 6.4.1.3 in TS 28.313 [57]).
4.3.57.2 Attributes
The DANRManagementFunction IOC includes attributes inherited from Top IOC (defined in TS 28.622[30]) and the following attributes:
|
Attribute name |
S |
isReadable |
isWritable |
isInvariant |
isNotifyable |
|
intrasystemANRManagementSwitch |
M |
T |
T |
F |
T |
|
intersystemANRManagementSwitch |
M |
T |
T |
F |
T |
4.3.57.3 Attribute constraints
None.
4.3.57.4 Notifications
The common notifications defined in subclause 4.5 are valid for this IOC, without exceptions or additions.
4.3.58 DESManagementFunction
4.3.58.1 Definition
This IOC represents the management capabilities of Distributed SON Energy Saving (ES) functions (see clause 6.2.3.0 in TS 28.310 [71]). This is provided for Energy Saving purposes.
NOTE: in the case where multiple DESManagementFunction MOIs exist at different levels of the containment tree, the DESManagementFunction MOI at the lower level overrides the DESManagementFunction MOIs at higher level(s) of the same containment tree.
4.3.58.2 Attributes
The DESManagementFunction IOC includes attributes inherited from Top IOC (defined in TS 28.622[30]) and the following attributes:
|
Attribute name |
S |
isReadable |
isWritable |
isInvariant |
isNotifyable |
|
desSwitch |
M |
T |
T |
F |
T |
|
intraRatEsActivationOriginalCellLoadParameters |
CM |
T |
T |
F |
T |
|
intraRatEsActivationCandidateCellsLoadParameters |
CM |
T |
T |
F |
T |
|
intraRatEsDeactivationCandidateCellsLoadParameters |
CM |
T |
T |
F |
T |
|
esNotAllowedTimePeriod |
O |
T |
T |
F |
T |
|
interRatEsActivationOriginalCellParameters |
CM |
T |
T |
F |
T |
|
interRatEsActivationCandidateCellParameters |
CM |
T |
T |
F |
T |
|
interRatEsDeactivationCandidateCellParameters |
CM |
T |
T |
F |
T |
|
energySavingState |
M |
T |
F |
F |
T |
|
isProbingCapable |
O |
T |
F |
F |
T |
4.3.58.3 Attribute constraints
|
Name |
Definition |
|
intraRatEsActivationOriginalCellLoadParameters S |
The condition is " the cell acts as an original cell". |
|
intraRatEsActivationCandidateCellsLoadParameters S |
The condition is " the cell acts as a candidate cell". |
|
intraRatEsDeactivationCandidateCellsLoadParameters S |
The condition is " the cell acts as a candidate cell". |
|
interRatEsActivationOriginalCellParameters CM S |
The condition is "The cell acts as an original cell". |
|
interRatEsActivationCandidateCellParameters CM S |
The condition is "The cell acts as a candidate cell". |
|
interRatEsDeactivationCandidateCellParameters CM S |
The condition is "The cell acts as a candidate cell". |
4.3.58.4 Notification
The common notifications defined in clause 4.5 are valid for this IOC, without exceptions or additions.
4.3.59 DRACHOptimizationFunction
4.3.59.1 Definition
This IOC contains attributes to support the D-SON function of RACH optimization (See clause 7.1.1 in TS 28.313 [57]).
NOTE: in the case where multiple DRACHOptimization MOIs exist at different levels of the containment tree, the DRACHOptimization MOI at the lower level overrides the DRACHOptimization MOIs at higher level(s) of the same containment tree.
4.3.59.2 Attributes
The DRACHOptimizationFunction IOC includes attributes inherited from Top IOC (defined in TS 28.622[30]) and the following attributes:
|
Attribute name |
S |
isReadable |
isWritable |
isInvariant |
isNotifyable |
|
ueAccProbilityDist |
M |
T |
T |
F |
T |
|
ueAccDelayProbilityDist |
M |
T |
T |
F |
T |
|
drachOptimizationControl |
M |
T |
T |
F |
T |
4.3.59.3 Attribute constraints
None.
4.3.59.4 Notifications
The common notifications defined in subclause 4.5 are valid for this IOC, without exceptions or additions.
4.3.60 DMROFunction
4.3.60.1 Definition
This IOC contains attributes to support the D-SON function of MRO (See clause 7.1.2 in TS 28.313 [57]).
NOTE In the case where multiple DMROFunction MOIs exist at different levels of the containment tree, the DMROFunction MOI at the lower level overrides the DMROFunction MOIs at higher level(s) of the same containment tree.
4.3.60.2 Attributes
The DMROFunction IOC includes attributes inherited from Top IOC (defined in TS 28.622[30]) and the following attributes:
|
Attribute name |
S |
isReadable |
isWritable |
isInvariant |
isNotifyable |
|
dmroControl |
M |
T |
T |
F |
T |
|
maximumDeviationHoTriggerLow |
M |
T |
T |
F |
T |
|
maximumDeviationHoTriggerHigh |
M |
T |
T |
F |
T |
|
minimumTimeBetweenHoTriggerChange |
M |
T |
T |
F |
T |
|
tstoreUEcntxt |
M |
T |
T |
F |
T |
4.3.60.3 Attribute constraints
None.
4.3.60.4 Notifications
The common notifications defined in subclause 4.5 are valid for this IOC, without exceptions or additions
4.3.61 DPCIConfigurationFunction
4.3.61.1 Definition
This IOC contains attributes to support the Distributed SON function of PCI configuration (See clause 7.1.3 in TS 28.313 [57]).
NOTE: in the case where multiple DPCIConfiguration MOIs exist at different levels of the containment tree, the DPCIConfiguration MOI at the lower level overrides the DPCIConfiguration MOIs at higher level(s) of the same containment tree.
4.3.61.2 Attributes
The DPCIConfigControlFunction IOC includes attributes inherited from Top IOC (defined in TS 28.622[30]) and the following attributes:
|
Attribute name |
S |
isReadable |
isWritable |
isInvariant |
isNotifyable |
|
dPciConfigurationControl |
M |
T |
T |
F |
T |
|
nRPciList |
M |
T |
T |
F |
T |
4.3.61.3 Attribute constraints
None.
4.3.61.4 Notifications
The common notifications defined in subclause 4.5 are valid for this IOC, without exceptions or additions.
4.3.62 CPCIConfigurationFunction
4.3.62.1 Definition
This IOC contains attributes to support the Centralized SON function of PCI configuration (see clause 7.2.1 in TS 28.313 [57]).
NOTE: In the case where multiple CPCIConfiguration MOIs exist at different levels of the containment tree, the CPCIConfiguration MOI at the lower level overrides the CPCIConfiguration MOIs at higher level(s) of the same containment tree.
4.3.62.2 Attributes
The CPCIConfigurationFunction IOC includes attributes inherited from Top IOC (defined in TS 28.622[30]) and the following attributes:
|
Attribute name |
S |
isReadable |
isWritable |
isInvariant |
isNotifyable |
|
cPciConfigurationControl |
M |
T |
T |
F |
T |
|
cSonPciList |
M |
T |
T |
F |
T |
4.3.62.3 Attribute constraints
None.
4.3.62.4 Notifications
The common notifications defined in subclause 4.5 are valid for this IOC, without exceptions or additions
4.3.63 CESManagementFunction
4.3.63.1 Definition
This IOC represents the management capabilities of Centralized SON Energy Saving (ES) functions. (see clause 6.2.2 of TS 28.310 [71]) This is provided for Energy Saving purposes.
NOTE: in the case where multiple CESManagementFunction MOIs exist at different levels of the containment tree, the CESManagementFunction MOI at the lower level overrides the CESManagementFunction MOIs at higher level(s) of the same containment tree.
4.3.63.2 Attributes
The CESManagementFunction IOC includes attributes inherited from Top IOC (defined in TS 28.622[30]) and the following attributes:
|
Attribute name |
S |
isReadable |
isWritable |
isInvariant |
isNotifyable |
|
cesSwitch |
M |
T |
T |
F |
T |
|
energySavingControl |
M |
T |
T |
F |
T |
|
energySavingState |
M |
T |
T |
F |
T |
|
intraRatEsActivationOriginalCellLoadParameters |
CM |
T |
T |
F |
T |
|
intraRatEsActivationCandidateCellsLoadParameters |
CM |
T |
T |
F |
T |
|
intraRatEsDeactivationCandidateCellsLoadParameters |
CM |
T |
T |
F |
T |
|
esNotAllowedTimePeriod |
O |
T |
T |
F |
T |
|
interRatEsActivationOriginalCellParameters |
CM |
T |
T |
F |
T |
|
interRatEsActivationCandidateCellParameters |
CM |
T |
T |
F |
T |
|
interRatEsDeactivationCandidateCellParameters |
CM |
T |
T |
F |
T |
4.3.63.3 Attribute constraints
|
Name |
Definition |
|
intraRatEsActivationOriginalCellLoadParameters S |
The condition is "Intra-RAT domain centralized SON energy saving is supported AND the cell acts as an original cell". |
|
intraRatEsActivationCandidateCellsLoadParameters S |
The condition is "Intra-RAT domain centralized SON energy saving is supported AND the cell acts as a candidate cell". |
|
intraRatEsDeactivationCandidateCellsLoadParameters S |
The condition is "Intra-RAT domain centralized SON energy saving is supported AND the cell acts as a candidate cell". |
|
interRatEsActivationOriginalCellParameters CM S |
The condition is "The cell acts as an original cell" AND inter-RAT domain centralized SON energy saving is supported. |
|
interRatEsActivationCandidateCellParameters CM S |
The condition is "The cell acts as a candidate cell" AND inter-RAT domain centralized SON energy saving is supported. |
|
interRatEsDeactivationCandidateCellParameters CM S |
The condition is "The cell acts as a candidate cell" AND inter-RAT domain centralized SON energy saving is supported. |
4.3.63.4 Notification
The common notifications defined in clause 4.5 are valid for this IOC, without exceptions or additions.
4.3.64 AddressWithVlan <<dataType>>
4.3.64.1 Definition
This data type represents the address including IP address and VLAN Id (e.g. localAddress of EP_NgC) used for initialization of the underlying transport.
4.3.64.2 Attributes
|
Attribute name |
S |
isReadable |
isWritable |
isInvariant |
isNotifyable |
|
iPAddress |
O |
T |
T |
F |
T |
|
vLANId |
O |
T |
T |
F |
T |
4.3.64.3 Attribute constraints
None
4.3.64.4 Notifications
The subclause 4.5 of the <<IOC>> using this <<dataType>> as one of its attributes, shall be applicable.
4.3.65 TceIDMappingInfo <<dataType>>
4.3.65.1 Definition
This data type represents the properties describing the mapping relationship between TCE ID, PLMN where TCE resides and IP address of TCE.
4.3.65.2 Attributes
|
Attribute name |
S |
isReadable |
isWritable |
isInvariant |
isNotifyable |
|
tceIPAddress |
M |
T |
T |
F |
T |
|
tceID |
M |
T |
T |
F |
T |
|
pLMNTarget |
M |
T |
T |
F |
T |
4.3.65.3 Attribute constraints
None.
4.3.65.4 Notifications
The subclause 4.5 of the <<IOC>> using this <<dataType>> as one of its attributes, shall be applicable.
4.3.66 NPNIdentity <<dataType>>
4.3.66.1 Definition
This <<dataType>> represents the NPN supported by the <<IOC>> using this <<dataType>> as one of its attributes in case of the cell is a NPN-only cell.
4.3.66.2 Attributes
|
Attribute name |
S |
isReadable |
isWritable |
isInvariant |
isNotifyable |
|
plmnid |
M |
T |
T |
F |
T |
|
cAGIdList |
CM |
T |
T |
F |
T |
|
nIDList |
CM |
T |
T |
F |
T |
NOTE: It is an ASN.1 CHOICE for a NPN-only cell to populate cAGIdList or nIDList, see TS 38.331 [54].
4.3.66.3 Attribute constraints
|
Name |
Definition |
|
cAGIdList S |
Condition: The cell is a NPN-only cell (see TS 38.331 [54]) in case of PNI-NPN. |
|
nIDList S |
Condition: The cell is a NPN-only cell (see TS 38.331 [54]) in case of SNPN. |
4.3.66.4 Notifications
The subclause 4.5 of the <<IOC>> using this <<dataType>> as one of its attributes, shall be applicable.
4.3.67 OperatorDU
4.3.67.1 Definition
This IOC contains attributes to support the NG-RAN Multi-Operator Core Network (NG-RAN MOCN) network sharing with multiple Cell Identity broadcast feature. An instance of OperatorDU <<IOC>> should be created and configured for each POP. When configured the attributes override those in parent GNBDUFunction instance.
The OperatorDU <<IOC>> is only used to support MOCN with multiple cell identity broadcast feature. If MOCN with multiple cell identity broadcast feature is not supported, is not used.
The following table identifies the necessary end points required for the representation of shared gNB and shared en-gNB, of all deployment scenarios.
|
Req Role |
End point requirement for 3-split deployment scenario |
End point requirement for 2-split deployment scenario |
End point requirement for Non-split deployment scenario |
|
Shared gNB |
<<IOC>>EP_F1C, <<IOC>>EP_F1U |
<<IOC>>EP_F1C, <<IOC>>EP_F1U |
None. |
|
Shared en-gNB |
<<IOC>>EP_F1C, <<IOC>>EP_F1U |
<<IOC>>EP_F1C, <<IOC>>EP_F1U |
None. |
For scenarios with an F1 interface supporting multiple PLMN broadcast, the values of the EP_F1C and EP_F1U attributes contained by different OperatorDU of the same GNBDUFunction should be same.
4.3.67.2 Attributes
The OperatorDU IOC includes attributes inherited from Top IOC (defined in TS 28.622[30]) and the following attributes:
|
Attribute name |
S |
isReadable |
isWritable |
isInvariant |
isNotifyable |
|
gNBId |
M |
T |
T |
F |
T |
|
gNBIdLength |
M |
T |
T |
F |
T |
4.3.67.3 Attribute Constraints
None
4.3.67.4 Notifications
The common notifications defined in clause 5.5 are valid for this IOC, without exceptions or additions.
4.3.68 NROperatorCellDU
4.3.68.1 Definition
The NROperatorCellDU <<IOC>> contains attributes to support operator specific cell level information (including cellLocalId, pLMNInfoList, nRTAC) to support NG-RAN Multi-Operator Core Network (NG-RAN MOCN) network sharing with multiple Cell Identity broadcast feature. An instance of NROperatorCellDU <<IOC>> should be created and configured for each POP. When configured the attributes override those in the associated NRCellDU instance.
The NROperatorCellDU <<IOC>> is only used to support MOCN with multiple cell identity broadcast feature. If the MOCN with multiple cell identity broadcast feature is not supported, this IOC is not used.
4.3.68.2 Attributes
The NROperatorCellDU IOC includes attributes inherited from Top IOC (defined in TS 28.622[30]) and the following attributes:
|
Attribute name |
S |
isReadable |
isWritable |
isInvariant |
isNotifyable |
|
cellLocalId |
M |
T |
T |
F |
T |
|
administrativeState |
M |
T |
T |
F |
T |
|
pLMNInfoList |
M |
T |
T |
F |
T |
|
nRTAC |
CM |
T |
T |
F |
T |
|
Attribute related to role |
|||||
|
nRCellDURef |
M |
T |
T |
F |
T |
4.3.68.3 Attribute Constraints
None
4.3.68.4 Notifications
The common notifications defined in clause 5.5 are valid for this IOC, without exceptions or additions.
4.3.69 DLBOFunction
4.3.69.1 Definition
This IOC contains attributes to support the D-SON function of LBO (See TS 28.313 [57]).
NOTE In the case where multiple DLBOFunction MOIs exist at different levels of the containment tree, the DLBOFunction MOI at the lower level overrides the DLBOFunction MOIs at higher level(s) of the same containment tree.
4.3.69.2 Attributes
The DLBOFunction IOC includes attributes inherited from Top IOC (defined in TS 28.622[30]) and the following attributes:
|
Attribute name |
S |
isReadable |
isWritable |
isInvariant |
isNotifyable |
|
dlboControl |
M |
T |
T |
F |
T |
|
maximumDeviationHoTriggerLow |
M |
T |
T |
F |
T |
|
maximumDeviationHoTriggerHigh |
M |
T |
T |
F |
T |
|
minimumTimeBetweenHoTriggerChange |
M |
T |
T |
F |
T |
4.3.69.3 Attribute constraints
None.
4.3.69.4 Notifications
The common notifications defined in subclause 4.5 are valid for this IOC, without exceptions or additions
4.3.70 CCOFunction
4.3.70.1 Definition
This IOC contains attributes to support the C-SON function of Capacity and Coverage optimization (See clause 7.2.3 in TS 28.313 [57]).
NOTE: in the case where multiple CCOFunction MOIs exist at different levels of the containment tree, the CCOFunction MOI at the lower level overrides the CCOFunction MOIs at higher level(s) of the same containment tree.
4.3.70.2 Attributes
The CCOFunction IOC includes attributes inherited from Top IOC (defined in TS 28.622[30]) and the following attributes:
|
Attribute Name |
S |
isReadable |
isWritable |
isInvariant |
isNotifyable |
|
cCOControl |
M |
T |
T |
F |
T |
4.3.70.3 Attribute constraints
None.
4.3.70.4 Notifications
The common notifications defined in sub clause 4.5 are valid for this IOC, without exceptions or additions.
4.3.71 CCOWeakCoverageParameters
4.3.71.1 Definition
This IOC represents the properties of CCOWeakCoverageParameters. CCOWeakCoverageParameters is one realization of abstract CCOParameters IOC.
4.3.71.2 Attributes
The IOC includes attributes inherited from CCOParameters IOC
4.3.71.3 Attribute constraints
None.
4.3.71.4 Notifications
The common notifications defined in sub clause 4.5 are valid for this IOC, without exceptions or additions.
4.3.72 CCOPilotPollutionParameters
4.3.72.1 Definition
This IOC represents the properties of CCOPilotPollutionParameters. CCOPilotPollutionParameters is one realization of abstract CCOParameters IOC.
4.3.72.2 Attributes
The IOC includes attributes inherited from CCOParameters IOC.
4.3.72.3 Attribute constraints
None.
4.3.72.4 Notifications
The common notifications defined in sub clause 4.5 are valid for this IOC, without exceptions or additions.
4.3.73 CCOOvershootCoverageParameters
4.3.73.1 Definition
This IOC represents the properties of CCOOvershootCoverageParameters. CCOOvershootCoverageParameters is one realization of abstract CCOParameters IOC.
4.3.73.2 Attributes
The CCOFunction IOC includes attributes inherited from CCOParameters IOC .
4.3.73.3 Attribute constraints
None.
4.3.73.4 Notifications
The common notifications defined in sub clause 4.5 are valid for this IOC, without exceptions or additions.
4.3.74 CCOParameters
4.3.74.1 Definition
This IOC represents the properties of an abstract CCOParameters. The CCOParameters IOC needs to be subclassed to be instantiated.
The CCOWeakCoverageParameters IOC, CCOPilotPollutionParameters IOC, CCOOvershootCoverageParameters IOC is the realization of a CCOParameters IOC, see the inheritance in Figure 4.2.1.2-x.
4.3.74.2 Attributes
The CCOParameters IOC includes attributes inherited from Top IOC (defined in TS 28.622[30]) and the following attributes:
|
Attribute Name |
S |
isReadable |
isWritable |
isInvariant |
isNotifyable |
|
downlinkTransmitPowerRange |
O |
T |
T |
F |
T |
|
antennaTiltRange |
O |
T |
T |
F |
T |
|
antennaAzimuthRange |
O |
T |
T |
F |
T |
|
digitalTiltRange |
O |
T |
T |
F |
T |
|
digitalAzimuthRange |
O |
T |
T |
F |
T |
|
coverageShapeList |
O |
T |
T |
F |
T |
4.3.74.3 Attribute constraints
None.
4.3.74.4 Notifications
The subclause 4.5 of the <<IOC>> using this <<dataType>> as one of its attributes, shall be applicable.
4.3.75 ParameterRange <<dataType>>
4.3.75.1 Definition
This data type represents the adjustment range for parameters.
4.3.75.2 Attributes
The data type includes the following attributes:
|
Attribute Name |
S |
isReadable |
isWritable |
isInvariant |
isNotifyable |
|
maxValue |
M |
T |
T |
F |
T |
|
minValue |
M |
T |
T |
F |
T |
4.3.75.3 Attribute constraints
None.
4.3.75.4 Notifications
The subclause 4.5 of the <<IOC>> using this <<dataType>> as one of its attributes, shall be applicable.
4.3.76 BWPSet
4.3.76.1 Definition
This IOC represents a set of bandwidth part (BWP) set.
The set contains references to all BWPs that can be used by one UE.
There are assumed to be up to 4 DL, 4 UL and 4 SUL BWP for a total of 12 BWP per set.
4.3.76.2 Attributes
The BWP IOC includes attributes inherited from Top IOC (defined in TS 28.622[30]) and the following attributes:
|
Attribute name |
S |
isReadable |
isWritable |
isInvariant |
isNotifyable |
|
bWPList |
M |
T |
T |
F |
T |
4.3.76.3 Attribute constraints
None.
4.3.76.4 Notifications
The common notifications defined in subclause 4.5 are valid for this IOC, without exceptions or additions.