Skip to main content
Standards

5G Broadcast - Standards Evolution

Release-by-release detail on the 3GPP work items, Change Requests and RAN meetings behind LTE-based 5G Broadcast.

This page is the detailed, release-by-release companion to Standards: 5G Broadcast: the work items, Change Requests and RAN meetings behind each release. See that page for the ETSI TS 103 720 overview, the full specification list and current capabilities. For acronyms used here, see the Glossary.

Technology & Analysis

The deeper technical treatment of 5G Broadcast delivery and receiver behaviour.

Software Tools

5G-MAG's reference tools implementing ETSI TS 103 720.

LTE-based 5G Broadcast is not a single 3GPP work item but the accumulation of several, each adding capability to the same LTE physical layer (the TS 36.xxx series). The normative 3GPP work item LTE_terr_bcast was approved at RAN#83 (March 2019); the Release 14 features it builds on predate it. See Standards: 5G Broadcast for how each 3GPP release maps to an ETSI TS 103 720 version.

Release-by-release summary​

3GPP ReleaseWork item (parent → children)Key additions
Rel-14Parent: 700032 EnTV
Children: 670010 Study, 720015 Architecture, 730052 Mobile Network Interface, 740049 Stage 3, 740060 Codec		1.25 kHz and 7.5 kHz subcarrier spacing (SCS); Cell Acquisition Subframe (CAS); MBMS-dedicated cell; 256-QAM for PMCH; MIB-MBMS; SIB1-MBMS
Rel-16Parent: 830076 LTE_terr_bcast
Children: 800091 Study, 830176 Core, 830276 Perf.		2.5 kHz and 0.37 kHz SCS; new reference-signal patterns; PDCCH Format 4 (aggregation level 16); MBSFN-AreaInfo-r16; Receive-Only Mode (ROM)
Rel-17Parent: 911020 LTE_terr_bcast_bands_part1
Child: 911120 Core		6/7/8 MHz PMCH channel bandwidths (30/35/40 PRB); Band 107 (612 to 652 MHz, downlink-only) named here, but its TS 36.101 band-table entry and receiver requirements were not written until Release 18 (see below).
Rel-18Parent: 920071 LTE_terr_bcast_bands_part2
Children: 920171 Core, 1050131 UE Conformance		Band 108 (470 to 698 MHz, receive-only) and Band 107's TS 36.101/36.104 entries and receiver requirements, both introduced and completed here (CR 6016 to CR 6067, August 2023 to December 2024; see below).
Rel-19Parent: 1060081 LTE_terr_bcast_Ph2
Children: 1061081 Core, 1062081 Perf.		PMCH time interleaving and frequency interleaving; cyclic shift; PMCH MCS tables 11.1-1 / 11.1-2; TBS scaling; extended SI periods; RRC v1900 extension chain
Rel-195GB_CASMuting: no dedicated WI; carried as a topic under the generic TEI19 work item codeCAS muting for PSS / SSS / PBCH; SIB1-MBMS v1900; new UE capability
Rel-19Parent: 1060080 LTE_terr_bcast_bands_sub_108
Child: 1061080 Core		Bands 112 (470 to 608 MHz) and 113 (606 to 698 MHz); RF specifications in TS 36.101; release-independent from Rel-17. A companion CR separately makes Bands 107/108 release-independent from Rel-17.

Release 14: the FeMBMS baseline​

Release 14 introduced Further enhanced MBMS (FeMBMS) under the EnTV work item (WI 700032; approved RAN#73, September 2016; completed RAN#76, June 2017). It is the foundation on which every later release builds. The defining change is the MBMS-dedicated cell, in which almost the whole carrier is given over to broadcast (up to about 97.5% of resources), and a device can receive content with no network registration or attach procedure needed.

Physical layer (TS 36.211):

  • Two new PMCH numerologies with extended cyclic prefix for large-area SFN (Single Frequency Network) deployment: 1.25 kHz SCS (about 200 microseconds CP, for high-power high-tower very large single-frequency networks) and 7.5 kHz SCS (about 33 microseconds CP).
  • The Cell Acquisition Subframe (CAS): one radio frame per 40 ms (SFN mod 4 == 0) uses 15 kHz SCS with the standard LTE cyclic prefix and carries PSS, SSS, PBCH, PCFICH, PDCCH and PDSCH. The CAS enables SIM-free reception because no USIM is needed for the radio layer. The remaining three frames per 40 ms period are fully allocated to PMCH. The CAS always occupies 15 or 25 PRB (3 or 5 MHz) regardless of the PMCH bandwidth, so a receiver bootstraps on the narrowband CAS and the SIBs then signal the wider PMCH bandwidth.
  • MBSFN reference-signal patterns (TS 36.211 clause 6.10.2.2) for 1.25 kHz and 7.5 kHz.

Physical layer procedures, scheduler and link adaptation (TS 36.213):

  • 256-QAM for PMCH, extending the MCS index range and the PMCH transport-block-size (TBS) table for higher spectral efficiency in good channel conditions.

RRC (TS 36.331):

  • MIB-MBMS (MasterInformationBlock-MBMS-r14) replaces the legacy MIB and is carried on PBCH in CAS frames.
  • SIB1-MBMS (SIB1-MBMS-r14) replaces the legacy SIB1 broadcast channel for MBMS-dedicated cells, carrying cell-access and MBMS scheduling information.
  • Shorter MCCH repetition and modification periods (down to one radio frame) via a v1430 extension to MBSFN-AreaInfo, enabling faster system-information update cycles for broadcast.

Architecture (TS 36.300):

  • The MBMS-dedicated cell mode allocates up to about 97.5% of carrier resources to broadcast (39 PMCH subframes plus 1 CAS subframe per 40 ms).

Release 16: LTE-based 5G Terrestrial Broadcast (normative)​

The normative LTE_terr_bcast-Core work item (WI 830176; approved RAN#83, March 2019; completed RAN#88-e, June 2020) is the point at which "LTE-based 5G Terrestrial Broadcast" becomes a defined 3GPP feature rather than a set of TV enhancements. The core CRs are TS 36.211 CR 0504 (R1-1913622, RAN#86, introduction), TS 36.213 CR 1294 (R1-1913624), TS 36.331 CR 4190 (R2-2001740) and TS 36.300 CR 1322 (R2-2010758). TS 36.211 then received seven further correction CRs under the same work item: CR 0512 (RAN#87-e), CR 0521 (RAN#87-e, later merged into another CR), CR 0534 rev1 (RAN#88-e), CR 0539 (R1-2007190, RAN#89-e, PBCH repetition correction), CR 0540 (R1-2007191, RAN#89-e, MBSFN region correction), CR 0547 (R1-2009422, RAN#90-e) and CR 0548 (R1-2009423, RAN#90-e, corrected the 0.37 kHz useful-symbol length, 41472 to 82944 samples) and, later still, CR 0557 (R1-2106355, RAN#92-e, editorial MBSFN naming cleanup).

Physical layer (TS 36.211):

  • Two further PMCH numerologies: 2.5 kHz SCS (about 100 microseconds CP, for mobile reception up to around 250 km/h) and 0.37 kHz SCS (about 300 microseconds CP, for very large high-power high-tower SFN areas with inter-site distances up to around 100 km). The 0.37 kHz numerology uses a 3 ms slot structure with two timeSeparation reference-signal variants (sl2 and sl4).
  • New MBSFN reference-signal patterns for the 2.5 kHz and 0.37 kHz numerologies (TS 36.211 clause 6.10.2.2).
  • PDCCH Format 4 (aggregation level 16, 16 CCEs) for more robust control-channel reception in broadcast-only cells.
  • PBCH repetition: the PBCH carrying MIB-MBMS is transmitted in every CAS subframe rather than only in subframe 0, enabling faster MIB acquisition without a return channel.

RRC (TS 36.331):

  • A new MBSFN-AreaInfo-r16 structure carrying subcarrierSpacingMBMS-r16 (now including the 2.5 kHz and 0.37 kHz values) and timeSeparation-r16.
  • Receive-Only Mode (ROM) information in SIB13 (MBMS-ROM-Info-r16), which lets a receiver be pointed to MBMS content on another carrier without a return channel.
  • A semi-static CFI field in MIB-MBMS (semiStaticCFI-MBMS-r16) so that the receiver can skip reading PCFICH.

Release 17: new channel bandwidths and Band 107​

The work item (LTE_terr_bcast_bands_part1-Core, WI 911120) was approved at RAN#91-e (September 2021), adding channel bandwidths that match the UHF broadcast channel rasters used across ITU Regions 1, 2 and 3. The introducing CRs themselves were approved later, at RAN#94-e and RAN#95-e (March 2022): TS 36.211 CR 0564 (R1-2112926, RAN#94-e) and TS 36.213 CR 1406 (R1-2112905, RAN#94-e); then TS 36.300 CR 1360 (RAN#95-e), TS 36.306 CR 1836 rev1 (UE capabilities, RAN#95-e), TS 36.331 CR 4750 rev2 (RAN#95-e) and CR 4780 (UE capabilities, RAN#95-e), TS 36.443 CR 0131 rev1 (RAN3, RAN#95-e) and TS 36.976 CR 0001 (Release 17 enhancements to the informative summary, RAN#95-e). A much later clarification CR, TS 36.300 CR 1406 rev1 ("Clarification on UE/BS requirements for LTE based 5G terrestrial broadcast"), was approved at RAN#105 (September 2024) — three years after the feature's introduction.

  • Three new PMCH channel bandwidths: 6 MHz (30 PRB), 7 MHz (35 PRB) and 8 MHz (40 PRB), signalled by the new pmch-Bandwidth-r17 field carried in SIB13. Its absence means the legacy LTE bandwidth applies.
  • New LTE Band 107: frequency range 612 to 652 MHz (UHF, downlink only), for terrestrial broadcast.
  • TBS and PMCH resource-allocation tables updated for 30, 35 and 40 PRB.

Band 107's own receiver RF performance requirements (reference sensitivity, adjacent-channel selectivity, decoder BLER/SNR) were not finalised within Release 17 itself: as described below, they were completed later, together with Band 108's, under the Release 18 work item.

Release 18: Band 108 (UHF, receive-only)​

Band 108 is formally standardised by the LTE_terr_bcast_bands_part2 work item (WI 920071; approved RAN#101, August 2023). This is a spectrum-layer change only, with no new PMCH numerologies and no MAC or RRC changes.

  • Band 108: frequency range 470 to 698 MHz (UHF, downlink only, receive-only), covering the full UHF broadcast band across ITU regions.
  • Sub-band definitions for channelised operation within 470 to 698 MHz were approved later, at RAN#106 (December 2024, RP-243268).

TS 36.101 support for this work item was built up across seven approved CRs, all under WI 920071, from August 2023 to June 2025:

CRTitleMeetingDateTarget version
6016 rev1 (R4-2314756)Introduction of 5G broadcast UHF bandsRAN#101August 202318.3.0
6031 rev1 (R4-2403850)Bracket removal (5G Broadcast)RAN#103March 202418.5.0
6039Correction of EARFCN for bands 107 and 108RAN#103March 202418.5.0
6044Feature-agnostic approach implementation, Rel-18RAN#103March 202418.5.0
6067 rev1 (R4-2419893)Adding missing performance requirements for 6/7/8 MHz channel bandwidthsRAN#106December 202418.8.0
6106Terminology alignment for LTE-based 5G terrestrial broadcastRAN#108June 202518.10.0
6107Terminology alignment for the LTE based 5G terrestrial broadcast featureRAN#108June 202519.2.0

TS 36.104's counterpart CR is CR 4979 rev1 (R4-2313909), approved alongside CR 6016.

The CR 6016 and 6039 titles ("Introduction of 5G broadcast UHF bands", plural, and "Correction of EARFCN for bands 107 and 108") indicate Band 107 and Band 108 share the same TS 36.101 band-table entries and were introduced and corrected together under this Release 18 work item, not under Release 17's. The substantive technical work was complete by CR 6067 (RAN#106, December 2024); the two remaining CRs (6106, 6107, RAN#108, June 2025) are terminology-only, with no functional change.

Release 19: PMCH Phase 2, CAS muting and new bands​

Release 19 comprises four broadcast work items:

PMCH Phase 2 (LTE_terr_bcast_Ph2, WI 1060081, completed December 2025) adds diversity and higher-order modulation to the PMCH. This is the broadest work item on this page: it introduced CRs across eight specifications (RAN1, RAN2 and RAN3), and several of those specifications received one or more follow-up correction CRs after the introducing CR, extending into 2026.

SpecIntroducing CRMeeting / dateFollow-up CRsLatest meeting / date
TS 36.211 (PHY channels)CR 0576 (R1-2505059)RAN#108, June 2025CR 0580 (corrections), CR 0584 (corrections, "-Core"), CR 0586 (parameter-name alignment)RAN#111, ~March 2026
TS 36.212 (multiplexing/coding)CR 0376 (R1-2504965)RAN#108, June 2025CR 0379 (corrections), CR 0381 (RRC parameter-name alignment)RAN#111, ~March 2026
TS 36.213 (scheduler/link adaptation)CR 1448 (R1-2504967)RAN#108, June 2025CR 1459 (RRC parameter-name alignment)RAN#111, ~March 2026
TS 36.300 (overall description)CR 1428 rev1 (R2-2506347)RAN#109, ~September 2025--
TS 36.306 (UE radio access capabilities)CR 1920 rev1 (R2-2506346)RAN#109, ~September 2025CR 1934 rev2 (correction on the capability)RAN#110, ~December 2025
TS 36.321 (MAC)CR 1593 rev2 (R2-2506348)RAN#109, ~September 2025--
TS 36.331 (RRC)CR 5143 rev1 (R2-2506344)RAN#109, ~September 2025CR 5168 rev3 (post-ASN.1-review corrections), CR 5186 rev3 (notification-configuration clarification)RAN#110, ~December 2025
TS 36.443 (M2AP, eNB-MCE interface)CR 0133 rev2 (R3-256051)RAN#109, ~September 2025CR 0135 rev2 (time-interleaving parameter correction), CR 0137 rev2 (general correction)RAN#110, ~December 2025

A companion RAN4 work item, LTE_terr_bcast_Ph2_demod, adds the receiver conformance-test side at TS 36.101: reference measurement channels and demodulation test cases for time-frequency interleaving (endorsed at RAN4#117 as CR 6129 and CR 6130), and a multi-path fading channel model with 50 Hz Doppler for the 1.25 kHz numerology (CR 6128). These were consolidated and approved as CR 6132 ("Big CR for LTE_terr_bcast_Ph2_demod", R4-2522723) at RAN#110, targeting v19.4.0.

The RAN#111 CRs (parameter-name alignment across TS 36.211/36.212/36.213) show the feature was still receiving corrections into 2026, after the work item's own December 2025 completion date; this is normal 3GPP maintenance behaviour, not a sign the feature is unstable.

  • PMCH time interleaving (TS 36.211 clause 6.5.3): a transport block is spread across N consecutive MBSFN subframes for time diversity, with a "depth" N and a scheduling "window" M (N less than or equal to M). Per the official Release 19 description, the design follows the same principles as NR TBoMS (Transport Block over Multiple Slots, an existing NR coverage-enhancement technique that spreads one transport block across several time units) and reuses the receiver's existing HARQ soft-combining building blocks to combine the interleaved copies. This is a design-reuse choice, not the introduction of real HARQ: broadcast still has no feedback channel and no retransmission request from the receiver.
  • PMCH cyclic shift (TS 36.211 clause 6.5.1): a per-subframe phase rotation, with different cells in an SFN using different values to reduce correlated interference at cell boundaries.
  • PMCH frequency interleaving (TS 36.211 clause 6.5.2): block interleaving of PMCH resource elements in frequency for extra diversity.
  • PMCH-specific MCS tables (TS 36.213 clause 11.1, Tables 11.1-1 and 11.1-2): a normal table (QPSK, 16-QAM, 64-QAM) and a higher-order table extending to 256-QAM, replacing the standard PDSCH MCS table for broadcast, with TBS scaling when time interleaving is active.
  • Extended SI scheduling periods (si-Periodicity-r19) that reduce CAS overhead for infrequently changing system information.
  • The Rel-19 PMCH parameters are carried in a new v1900 RRC extension group of MBSFNAreaConfiguration.
  • MAC and M2AP impacts (TS 36.321, TS 36.443): the work item also touches the MAC layer and the M2 interface between the eNB and the Multi-cell/multicast Coordination Entity (MCE), which is how time-interleaving parameters reach the MCE-side scheduling function; these are not covered in the physical-layer bullets above.

CAS muting (5GB_CASMuting) reduces the transmission rate of synchronisation and broadcast channels in MBMS-dedicated cells: only the first frames of each period carry PSS, SSS and PBCH, and the rest are freed for PMCH. It is carried under the generic TEI19 (Technical Enhancements and Improvements for Release 19) work item code, a shared code 3GPP uses for a batch of unrelated small Release 19 additions, so 5GB_CASMuting itself has no dedicated work-item number. It is introduced by TS 36.211 CR 0577 (R1-2506644, RAN1#122, restricting PBCH/PSS/SSS transmission to the active CAS period) and TS 36.331 CR 5139 (a new SystemInformationBlockType1-MBMS-v1900 carrying cas-MutingConfig-r19), with a companion UE capability cas-Muting-5GB-r19 added to TS 36.306 clause 4.3.37 (CR 1916 rev1, R2-2506343, RAN WG2 Meeting #131, Bengaluru, 25-29 August 2025). A rapporteur-correction CR, TS 36.331 CR 5162 (R2-2508281, RAN2#132), later added a missing TS 36.211 clause 6.11.2.2 (SSS) reference and fixed an ASN.1 class-0 issue in the same IE. The muting window is defined by parameters K_CAS (4 to 63) and N_CAS (2, 4, 8 or 16): the first 4·K_CAS frames of every 16·N_CAS-frame period carry PSS/SSS/PBCH, arranged so that PBCH accumulation frames always fall in the active period and MIB decodability is preserved.

The LTE_terr_bcast_bands_sub_108-Core work item (WI 1061080, parent feature WI 1060080), active 2024-09-14 to 2025-06-06 and completed at RAN#108 (June 2025, final status report RP-251141), defines two further receive-only UHF broadcast bands for early national and regional deployment: Band 112 (470 to 608 MHz) and Band 113 (606 to 698 MHz), both downlink only and using the Release 17 6/7/8 MHz PMCH bandwidths (no new numerologies). Core CRs include TS 36.101 CR 6105 rev2 (R4-2508786) and TS 36.104 (R4-2508787). Bands 112 and 113 are release-independent from Release 17 onwards via CR R4-2507471: a Release 17 or later receiver needs no Release 19 feature support to operate on them. A companion CR, R4-2508063, separately makes Bands 107 and 108 release-independent from Release 17 in the same way.

The fourth work item is unrelated to the terrestrial bands above: LTE_band_5G_bcast_GSO (WI 1070064, parent; children WI 1071064 "Core" and WI 1072064 "Perf.", active 3 March 2025 to 3 March 2026) defines a new LTE band for 5G broadcast delivered over a geosynchronous satellite, for ITU Region 3 (Asia-Pacific). Unlike the terrestrial bands, this feature ("Broadcast Over GSO", BOG, per the CR titles) touches a distinct, satellite-specific set of specifications: TS 36.102 (UE radio transmission and reception for satellite access), TS 36.108 (Satellite Access Node radio transmission and reception), TS 36.181 (Satellite Access Node conformance testing) and TS 36.307 (requirements for UEs supporting a release-independent frequency band). The band was introduced by CR 0078 to TS 36.102 and CR 0036 to TS 36.108 (both RAN#109), with performance and conformance-test CRs following at RAN#111 and RAN#112 (TS 36.102 CR 0122/0134/0135, TS 36.108 CR 0046/0052/0054, TS 36.181 CR 0034/0042, TS 36.307 CR 4514/4517).

References to verify

The per-release 3GPP CR numbers, TS clause references, meeting placements and band frequency ranges above are taken from an internal 5G-MAG standards-tracking document and were not all confirmed against the primary 3GPP record. A maintainer should verify these before relying on them: the 3GPP TS 36.211 / 36.212 / 36.213 / 36.300 / 36.331 / 36.101 / 36.104 / 36.306 / 36.443 / 36.976 CR numbers and their clauses (for example TS 36.211 CR 0504, 0512, 0521, 0534, 0539, 0540, 0547, 0548, 0557, 0564, 0576, 0577; TS 36.212 CR 0376; TS 36.213 CR 1294, 1406, 1448; TS 36.300 CR 1360, 1406; TS 36.331 CR 4190, 4750, 4780, 5139, 5143, 5162; TS 36.443 CR 0131; TS 36.976 CR 0001; TS 36.101 CR 6016, 6031, 6039, 6044, 6067, 6105, 6106, 6107; TS 36.104 CR 4979; TS 36.306 CR 1836, 1916) and RAN meeting numbers; and the Band 112 / 113 frequency ranges and their release placement. The Release 16 TS 36.211 correction-CR chain (0512 through 0557) was independently confirmed against the 3GPP CR portal filtered by WI 830076/800091/830176/830276, including two entries (CR 0512, CR 0534) not present in the internal roadmap document at all; their meeting numbers (RAN#87-e to RAN#92-e) are portal-verified but calendar dates for those specific meetings were not looked up beyond the two already-cited anchors (RAN#83 = March 2019, RAN#88-e = June 2020). Similarly, the Release 17 CR list above (TS 36.300/36.306/36.331/36.443/36.976) was independently confirmed against the CR portal filtered by WI 911020/911120; it shows the work item itself was approved at RAN#91-e (September 2021) but every introducing CR was approved later, at RAN#94-e or RAN#95-e (both independently confirmed as March 2022), with one clarification CR (TS 36.300 CR 1406 rev1) following three years later at RAN#105 (September 2024, independently confirmed). Band 107's frequency range (612 to 652 MHz) comes from an internal 5G-MAG implementation-tracking roadmap and is cross-checked against a public LTE band-plan reference, but not against the 3GPP TS 36.101 text itself (3gpp.org and etsi.org blocked automated access). The TS 36.101/36.104 CR history for Bands 107 and 108 (the table under "Release 18: Band 108" above) was checked against the 3GPP CR portal for CR numbers, titles, meetings and target versions; CR 6031 and CR 6067 were additionally verified in full against their source CR documents. CR 6016 and CR 6039's full text was not read, only their portal metadata, so the claim that they cover both bands together rests on their titles ("UHF bands", plural; "bands 107 and 108") rather than the clause text. The Release 19 release-independence CRs (R4-2508063 for Bands 107/108, R4-2507471 for Bands 112/113) are from the internal roadmap and were not independently verified against the 3GPP CR portal.

The LTE_band_5G_bcast_GSO (satellite broadcast) work item, its two children, and its full CR list across TS 36.102/36.108/36.181/36.307 were all independently verified directly against the 3GPP work item and CR portals, not sourced from the internal roadmap. One detail was not independently confirmed against a 3GPP-primary source: the operating band number and frequency range (reported elsewhere, outside 3gpp.org, as Band 246, 1467 to 1492 MHz) — this was not found in the CR titles themselves and should be checked against TS 36.101 or TS 36.102 directly before citing a specific frequency range on this page.

Work-item identifiers: every parent and child work item shown in the "Work item" column of the release-by-release table was independently verified directly against the 3GPP work item portal and cross-checked against the official 3GPP Release Description reports (TR 21.916 to TR 21.919). 5GB_CASMuting has no dedicated WI number by design: its CR (TS 36.306 CR 1916 rev1, R2-2506343) shows it is carried under the generic TEI19 work item code. Separately, note that the Release 18 section above cites RAN#106 (December 2024, RP-243268) for "sub-band definitions... within 470 to 698 MHz", and the Release 19 section cites the same RAN#106 meeting for the sub_108 work item producing Bands 112/113; these may describe the same meeting outcome under two different release placements and should be reconciled by someone with access to the RAN#106 report.

Correction (this pass): an earlier version of this page cited the LTE_terr_bcast_bands_sub_108-Core work item as "approved through RAN#115 (March 2026, report RP-251141)". That was wrong: RP-251141 is dated 2025 (the "25" prefix in 3GPP TDoc numbers denotes the submission year), and direct verification of the work item page confirmed its final status report RP-251141 is dated 6 June 2025 and its active end date is also 2025-06-06 — matching RAN#108 (June 2025), not RAN#115. This has been corrected above.

The PMCH Phase 2 CR table above was built from a full 3GPP CR-portal export for WI 1060081 covering CRs to eight specifications. CR numbers, titles and RAN meeting numbers in that table are as shown in the portal export. Exact calendar dates for RAN#109, RAN#110 and RAN#111 were not independently looked up (only RAN#101, RAN#103 and RAN#108 have been confirmed against a search result in this session) and are estimated by quarterly spacing from RAN#108 (June 2025); they are marked "~" in the table for that reason. TS 36.443's description as the "M2AP, eNB-MCE interface" spec comes from a web search of its title, not from reading the CR text itself.

Individual 3GPP Change Requests (CRs) are not linked directly: the CR search portal (portal.3gpp.org/ChangeRequests.aspx) requires a 3GPP delegate login for record-level detail. A filtered-by-work-item search link (using the workitem= query parameter) does work without login to reach the search results page itself, but the CR table contents still require authentication, so no such links are included here.

note

Refer to the Standards repository to contribute to this documentation.