ass GNBDUFunction GNBCUUPFunction GNBCUCPFunction ExternalIMFs <<names>> <<names>> aInformationObjectClassx aInformationObjectClassx NRCelIDU NRCelICU Figure 6.5.4 gNB (en-gNB) NRM for all deployment scenarios (Source: Reproduced by permission of © 3GPP). Table 6.5.2 IOCs for the RAN components. Information object class Description GNBDUFunction Represents the logical function DU of gNB or en-gNB GNBCUCPFunction Represents the logical function CU-CP of gNB and en-gNB GNBCUUPFunction Represents the logical function CU-UP of gNB or en-gNB Table 6.5.3 IOCs for the DU components. Information object class Description NRCellCU Represents the information required by CU that is responsible for the management of inter-cell mobility and neighbor relations via ANR NRCellDU Represents the information of a cell known by DU such as information of the resources realizing the cell NRSectorCarrier Represents the resources of each transmission point included in the cell. 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 The standard also identifies the necessary endpoints required for the representation of gNB and en-gNB, of all deployment scenarios. The endpoints however depend on the split scenario. Taking the example of the gNB-DU, Table 6.5.4 provides three different endpoint definitions for three different split scenarios. 6.5.7 O-RAN Alliance Management Architecture As mentioned in Chapter 4, in addition to 3GPP, the O-RAN Alliance also works on defining a number of NG-RAN architectures; for example, low-level gNB split (described 6 Enabling Technologies Table 6.5.4 Endpoints IOCs. Endpoint requirement Endpoint requirement for three-split for two-split Endpoint requirement Req. role deployment scenario deployment scenario for non-split deployment scenario <<IOC>>EP_XnC, IOC EP_XnC, <<IOC>EP_XnC, <<IOC>>EP_NgC <<IOC>>EP_NgC, <<IOC>>EP_NgC, <<IOC>>EP_F1C, IOC>