Content for  TS 38.300  Word version:  16.3.0

Top   Top   Up   Prev   None
1…   4…   4.7…   5…   5.3…   5.4…   6…   6.2…   6.6…   7…   8…   9…   9.2.2…   9.2.3……   9.2.4…   9.2.6…   9.3…   10…   11…   15…   15.5…   16…   16.3   16.4…   17…   A…   B…


B  Deployment ScenariosWord‑p. 140

B.1  Supplementary Uplink

To improve UL coverage for high frequency scenarios, SUL can be configured (see TS 38.101-1). With SUL, the UE is configured with 2 ULs for one DL of the same cell as depicted on Figure B.1-1 below:
Reproduction of 3GPP TS 38.300, Figure B.1-1: Example of Supplementary Uplink

B.2  Multiple SSBs in a carrier

For a UE in RRC_CONNECTED, the BWPs configured by a serving cell may overlap in the frequency domain with the BWPs configured for other UEs by other cells within a carrier. Multiple SSBs may also be transmitted within the frequency span of a carrier used by the serving cell. However, from the UE perspective, each serving cell is associated to at most a single SSB. Figure B.2-1 below describes a scenario with multiple SSBs in a carrier, identifying two different cells (NCGI = 5, associated to SSB1, and NCGI = 6, associated to SSB3) with overlapping BWPs, and where RRM measurements can be configured to be performed by the UE on each of the available SSBs, i.e. SSB1, SSB2, SSB3 and SSB4.
Reproduction of 3GPP TS 38.300, Figure B.2-1: Example of multiple SSBs in a carrier

B.3  NR Operation with Shared Spectrum |R16|Word‑p. 141
NR Radio Access operating with shared spectrum channel access can support the following deployment scenarios:
  • Scenario A: Carrier aggregation between NR in licensed spectrum (PCell) and NR in shared spectrum (SCell);
  • Scenario B: Dual connectivity between LTE in licensed spectrum and NR in shared spectrum (PSCell);
  • Scenario C: NR in shared spectrum;
  • Scenario D: NR cell in shared spectrum and uplink in licensed spectrum;
  • Scenario E: Dual connectivity between NR in licensed spectrum and NR in shared spectrum.
Carrier aggregation of cells in shared spectrum is applicable to all deployment scenarios.

C  I-RNTI Reference ProfilesWord‑p. 142
The I-RNTI provides the new NG-RAN node a reference to the UE context in the old NG-RAN node. How the new NG-RAN node is able to resolve the old NG-RAN ID from the I-RNTI is a matter of proper configuration in the old and new NG-RAN node.
Table C-1 below provides some typical partitioning of a 40bit I-RNTI, assuming the following content:
  • UE specific reference: reference to the UE context within a logical NG-RAN node;
  • NG-RAN node address index: information to identify the NG-RAN node that has allocated the UE specific part;
  • PLMN-specific information: information supporting network sharing deployments, providing an index to the PLMN ID part of the Global NG-RAN node identifier.
Profile ID
UE specific reference
NG-RAN node address index (e.g., gNB ID, eNB ID)
RAT-specific information
PLMN-specific information

20 bits (~1 million values)
20 bits (~1 million values)
NG-RAN node address index may be very well represented by the LSBs of the gNB ID.
This profile may be applicable for any NG-RAN RAT.
20 bits (~1 million values)
16 bits (65.000 nodes)
4 bits (Max 16 PLMNs)
Max number of PLMN IDs broadcast in NR is 12.
This profile may be applicable for any NG-RAN RAT.
24 bits (16 million values)
16 bits (65.000 nodes)
Reduced node address to maximise addressable UE contexts.
This profile may be applicable for any NG-RAN RAT.


D  SPID ranges and mapping of SPID values to cell reselection and inter-RAT/inter frequency handover prioritiesWord‑p. 143
The SPID values are defined in Annex I of TS 36.300.
From the SPID reference values, only the SPID=253 also applies for 5GC.

E  NG-RAN Architecture for Radio Access Network Sharing with multiple cell ID broadcast (informative)Word‑p. 144
Each NG-RAN node serving a cell identified by a Cell Identity associated with either a subset of PLMNs, or a subset of SNPNs, or a subset of PNI-NPNs is connected to another NG-RAN node via a single Xn-C interface instance.
Each Xn-C interface instance is setup and removed individually.
Xn-C interface instances terminating at NG-RAN nodes which share the same physical radio resources may share the same signalling transport resources. If this option is applied:
  • Non-UE associated signalling is associated to an Xn-C interface instance by including an Interface Instance Indication in the XnAP message;
  • Node related, non-UE associated Xn-C interface signalling may provide information destined for multiple logical nodes in a single XnAP procedure instance once the Xn-C interface instance is setup;
  • A UE associated signalling connection is associated to an Xn-C interface instance by allocating values for the corresponding NG-RAN node UE XnAP IDs so that they can be mapped to that Xn-C interface instance.

$  Change history

Up   Top