4.2.1 Class diagram for gNB and en-gNB

28.5413GPP5G Network Resource Model (NRM)Management and orchestrationStage 2 and stage 3TS

4.2.1.1 Relationships

This clause depicts the set of classes (e.g. IOCs) that encapsulates the information relevant for this gNB and en-gNB. For the UML semantics, see 3GPP TS 32.156 [43]. Subsequent clauses provide more detailed specification of various aspects of these classes.

The model fragments are for management representation of gNB and en-gNB for all NG-RAN deployment scenario as listed below.

– Non-split NG-RAN deployment scenario, represents the gNB defined in TS 38.401[4]. In this scenario, a gNB is represented by a combination of a GNBCUCPFunction, one or more GNBCUUPFunctions and one or more GNBDUFunctions.

– 2-split NG-RAN deployment scenario, represents the gNB consist of gNB-CU and gNB-DU defined in TS 38.401[4] clause 6.1.1. In this scenario, a gNB-CU is represented by a combination of a GNBCUCPFunction and one or more GNBCUUPFunctions, whereas a gNB-DU is represented by a GNBDUFunction.

– 3-split NG-RAN deployment scenario, represents the gNB consist of gNB-CU-CP, gNB-CU-UP and gNB-DU defined in TS 38.401[4] clause 6.1.2. In this scenario, a gNB-CU-CP is represented by a GNBCUCPFunction, a gNB-CU-UP is represented by a GNBCUUPFunction, and a gNB-DU is represented by a GNBDUFunction.

Figure 4.2.1.1-1: NRM for all deployment scenarios

Figure 4.2.1.1-2: NRM for EPs for all deployment scenarios

Figure 4.2.1.1-3: NRM for <<IOC>>NRSectorCarrier,<<IOC>>BWP, and <<IOC>> BWPSet for all deployment scenarios

Figure 4.2.1.1-4: Cell Relation view for all deployment scenarios

NOTE 1: The above NRM fragment uses SubNetwork to hold both NR and LTE external entities and frequencies.

Figure 4.2.1.1-5: Cell Relation view for all deployment scenarios

NOTE 2: The above NRM fragment uses NRNetwork to hold NR external entities and frequency and using EUtraNetwork to hold LTE external entities and frequency. The NRNetwork and EUtraNetwork are subclasses of SubNetwork (defined in TS 28.622 [30]) with no additional attributes. The reason using NRNetwork and EUtraNetwork is for a clean separation of NR external entities and frequency and LTE external entities and frequency.

Figure 4.2.1.1-6: NRM fragment for abstract RRM Policies

Figure 4.2.1.1-6a: NRM fragment for RRMPolicyRatio

Figure 4.2.1.1-7: NRM fragment to support RIM

The Figure 4.2.1.1-8 shows the NRM fragment for pre-configured 5QIs in NG-RAN.

Figure 4.2.1.1-8: NRM fragment for pre-configured 5QIs in NG-RAN

NOTE 3: Configurable5QISet containment is defined to support multiple deployment scenarios. See clause 5.3.75 for details.

Figure 4.2.1.1-9: NRM fragment for DANR Management

Figure 4.2.1.1-10: NRM fragment for DES Management

Figure 4.2.1.1-11: NRM fragment for DRACH Management

Figure 4.2.1.1-12: NRM fragment for DMRO Management

Figure 4.2.1.1-13: NRM fragment for DPCI Management

Figure 4.2.1.1-14: NRM fragment for CES Management

Figure 4.2.1.1-15: NRM fragment for CPCI Management

The Figure 4.2.1.1-16 shows the NRM fragment for dynamic 5QIs in NG-RAN.

Figure 4.2.1.1-16: NRM fragment for dynamically assigned 5QIs in NG-RAN

Figure 4.2.1.1-17: NRM NG-RAN MOCN network sharing with multiple cell identity

Figure 4.2.1.1-18: NRM for F1 related EPs to support individual F1 interface for NG-RAN MOCN network sharing with multiple cell identity broadcast scenario

Figure 4.2.1.1-19: NRM fragment for DLBO Management

Figure 4.2.1.1-20: NRM fragment for CCO Management

4.2.1.2 Inheritance

Figure 4.2.1.2-1: Inheritance Hierarchy

Figure 4.2.1.2-2: Inheritance Hierarchy