Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TS 38.300  Word version:  17.2.0

Top   Top   Up   Prev   Next
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.3.2…   9.2.3.3…   9.2.4…   9.2.6…   9.3…   10…   11…   15…   15.5…   16…   16.2…   16.3…   16.4…   16.9…   16.10…   16.12…   16.13…   16.14…   17…   18…   19…   A…   B…   C…

 

B  Deployment Scenariosp. 197

B.1  Supplementary Uplinkp. 197

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, Fig. B.1-1: Example of Supplementary Uplink
Up

B.2  Multiple SSBs in a carrierp. 197

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, Fig. B.2-1: Example of multiple SSBs in a carrier
Up

B.3  NR Operation with Shared Spectrum |R16|p. 198

NR Radio Access operating with shared spectrum channel access can support the following deployment scenarios:
  • Scenario A: Carrier aggregation between NR in licensed spectrum (SpCell) and NR in shared spectrum (SCell);
  • Scenario B: Dual connectivity between LTE in licensed spectrum and NR in shared spectrum (PSCell);
    • Scenario A.1: SCell is not configured with uplink (DL only);
    • Scenario A.2: SCell is configured with uplink (DL+UL).
  • Scenario C: NR in shared spectrum (PCell);
  • Scenario D: NR cell in shared spectrum and uplink in licensed spectrum;
  • Scenario E: Dual connectivity between NR in licensed spectrum (PCell) and NR in shared spectrum (PSCell).
Carrier aggregation of cells in shared spectrum is applicable to all deployment scenarios.
Up

B.4  Example implementation of Non-Terrestrial Networks |R17|p. 198

The following Figure illustrates an example implementation of an Non-Terrestrial Network for transparent NTN payload:
Reproduction of 3GPP TS 38.300, Fig. B.4-1: NTN based NG-RAN
Up
The gNB depicted in Figure B.4-1 may be subdivided into non-NTN infrastructure gNB functions and the NTN Service Link provisioning System. The NTN infrastructure may be thought of being subdivided into the NTN Service Link provisioning System and the NTN Control function. The NTN Service Link provisioning System may consist of one or more NTN payloads and NTN Gateways.
The NTN payload is embarked on a spaceborne (or airborne) vehicle, providing a structure, power, commanding, telemetry, attitude control for the satellite (resp. HAPS) and possibly an appropriate thermal environment, radiation shielding.
The NTN Service Link provisioning System maps the NR-Uu radio protocol over radio resources of the NTN infrastructure (e.g. beams, channels, Tx power).
The NTN control function controls the spaceborne (or airborne) vehicles as well as the radio resources of the NTN infrastructure (NTN payload(s) & NTN Gateway(s)). It provides control data, e.g. Ephemeris, to the non-NTN infrastructure gNB functions of the gNB.
Provision of NTN control data to the gNB is out of 3GPP scope.
At least the following NTN related parameters are expected to be provided by O&M to the gNB for its operation:
  1. Earth fixed beams: for each beam provided by a given NTN-payload:
    • The Cell identifier (NG and Uu) mapped to the beam;
    • The Cell's reference location (e.g. cell's center and range).
  2. Quasi Earth fixed beams: for each beam provided by a given NTN-payload:
    • The Cell identifier (NG and Uu) and time window mapped to a beam;
    • The Cell's/beam's reference location (e.g. cell's center and range);
    • The time window of the successive switch overs (feeder link, service link);
    • The identifier and time window of all serving satellites and NTN-Gateways.
  3. Earth moving beams: for each beam provided by a given NTN-payload:
    • The Uu Cell identifier mapped to a beam and mapping information to fixed geographical areas reported on NG, including information about the beams direction and motion of the beam's foot print on Earth;
    • Its elevation wrt NTN-payload;
    • Schedule of successive serving NTN-Gateways/gNBs;
    • Schedule of successive switch overs (feeder link, service link).
Up

Up   Top   ToC