3GPP Scout / Specifications

Specification

3GPP TS 38.300: NR; NR and NG-RAN Overall Description; Stage 2

Published 2026-11-05Updated 2026-11-05

At a glance

Title
NR; NR and NG-RAN Overall Description; Stage 2
Newest version
V19.4.0 (Rel-19)
Versions indexed
8
Newest per release
Rel-15: V15.23.0 (2026-07-01); Rel-16: V16.22.0 (2026-07-01); Rel-17: V17.17.0 (2026-07-01); Rel-18: V18.11.0 (2026-09-25); Rel-19: V19.4.0 (2026-09-25)

In plain words

TS 38.300 provides "an overview and overall description of the NG-RAN", focusing on the radio interface protocol architecture of NR connected to 5GC. Its overview says gNBs and ng-eNBs interconnect over Xn and connect to 5GC through NG interfaces. Companion specifications in the 38 series specify details of the radio interface protocols. V19.4.0 includes corrections on optional DRB setup for NCR-MT in RRC state transition and co-existence of CLTM with network triggered PSCell change.

Source: 3GPP TS 38.300 V19.4.0, clause 1. © 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). Official text: https://www.3gpp.org/ftp/Specs/archive/38_series/38.300/38300-j40.zip

Newest version in each release

ReleaseNewest versionIn the archiveTSG meeting
Rel-19V19.4.02026-09-25TSG RAN #113
Rel-18V18.11.02026-09-25TSG RAN #113
Rel-17V17.17.02026-07-01TSG RAN #112
Rel-16V16.22.02026-07-01TSG RAN #112
Rel-15V15.23.02026-07-01TSG RAN #112

Source: 3GPP specification archive, versions indexed by 3GPP Scout. Each version links its official file.

Change requests in V19.4.0

V19.4.0 of TS 38.300 includes 7 CRs.

CRCategorySubjectSourceWorking group meetingTSG TDoc
CR 1176ACorrection on optional DRB setup for NCR-MT in RRC state transitionChina Telecom, ZTE, Nokia, CATTRAN2 #135RP-262142
CR 1180FCorrection on co-existence of CLTM with network triggered PSCell changeNECRAN2 #135RP-262144
CR 1189 rev 2FCorrections on stage 2 applicability reporting procedure frameworkZTE Corporation, OPPO, SanechipsRAN2 #135RP-262143
CR 1192ACorrection on PDU set QoS parameters in target gNBR3 (NEC, Huawei, China Telecom, Lenovo, Ericsson, Qualcomm, Samsung, ZTE, Nokia, CMCC)RAN2 #135RP-262142
CR 1193FCorrection on NR Femto awareness at CNR3 (Huawei, CATT, Samsung, Ericsson, China Telecom, Lenovo, Qualcomm, Nokia, CMCC, ZTE)RAN2 #135RP-262144
CR 1195ACorrection on non-homogeneous support of PDU set based handlingR3 (Samsung, Huawei, NEC, ZTE, Ericsson, Nokia)RAN2 #135RP-262142
CR 1196FL3 HO with LTM configuration keptR3 (Samsung, Ericsson, Google, LG Electronics, Nokia, Lenovo, ZTE, Ofinno, Qualcomm, Huawei)RAN2 #135RP-262144

Source: 3GPP CR database.

Meetings behind the latest versions

Working group meetings that agreed the CRs in V19.4.0, V18.11.0:

Plenary meetings:

  • TSG RAN #113 approved V19.4.0 (Rel-19)
  • TSG RAN #112 approved V19.3.0 (Rel-19)
  • TSG RAN #110 approved V19.1.0 (Rel-19)

Source: 3GPP CR database and specification archive, as indexed by 3GPP Scout.

Clauses changed in V19.4.0

8 clauses changed or added in V19.4.0. Each clause number opens Scout on that clause.

ClauseTitleChangeCRs
9.2.3.2.1C-Plane HandlingchangedCR 1196
4.10.2.2AMFchangedCR 1193
9.2.1.3State TransitionschangedCR 1176
9.2.3.7.1GeneralchangedCR 1180
16.15.2AwarenesschangedCR 1192
22.2.3Applicability ReportingchangedCR 1189
GAnnex G (informative): Components of Mobility Latencychanged
16.15.5Non-Homogeneous support of PDU set based handling in NG-RANchangedCR 1195

Source: 3GPP Scout comparison of this version with the one before it.

Sources

  1. 3GPP TS 38.300 V19.4.0, clause 1. © 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). Official text: https://www.3gpp.org/ftp/Specs/archive/38_series/38.300/38300-j40.zip
  2. 3GPP TS 38.300 V19.4.0, clause 4.1. © 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). Official text: https://www.3gpp.org/ftp/Specs/archive/38_series/38.300/38300-j40.zip
  3. 3GPP CR database.

How this page was made

The facts box and the tables come straight from the 3GPP specification archive and CR database as indexed by 3GPP Scout. An AI model (GPT-6 Luna) wrote the paragraph and named the source of each sentence. Code checked every quote word for word against the stored source text and every number against the cited source. A second AI model from another company (Claude Opus 5.5) reviewed the paragraph against the same sources. The 3GPP documents themselves govern.