Canonical Atlas record

TS 36.181

Evolved Universal Terrestrial Radio Access (E-UTRA); Satellite Access Node conformance testing

Responsible WGR4
StatusUnder change control
Initial releaseRel-18
Selected releaseRel-19
Latest indexed version19.4.0
Series36
TypeTS

Release evolution

Compare evidence between releases

Use indexed version, Work Item and Change Request evidence to see what changed around this specification. This is an evidence trail, not a clause-by-clause normative diff.

Release ledger

Version · WI · CR evidence by release

Rel-1818.10.06 WI43 CRs · 22 approved
Rel-1919.4.04 WI18 CRs · 11 approved

Rel-19 snapshot

Work affecting this release

18 indexed Change Requests · 4 connected Work Items.

Showing 12 CR records from the available cross-release sample. Browse release CR records (JSON) →

CR 0042 rev.2 — (LTE_NBIOT_eMTC_NTN_req-Perf) CR to TS 36.181 on clarification of the frequency error test requirement

CR 0044 — (LTE_NBIOT_eMTC_NTN_req-Perf) CR to TS 36.181 on corrections of table numbering for the modulation quality test requirement

CR 0035 rev.1 — Big CR: Introduction of SAN demodulation requirements for IoT-NTN Phase 3

CR 0034 rev.1 — CR to TS36.181 Introduction of 5G broadcast over GSO band

CR 0040 rev.1 — CR on the performance conformance testing for TS 36.181 - IoT_NTN_TDD

CR 0039 — CR on RF conformance testing for TS 36.181 - IoT_NTN_TDD

CR 0038 — CR to TS 181: Removal of [] for NB-IoT requirements

CR 0033 — (LTE_NBIOT_eMTC_NTN_req-Perf)Correction CR on IoT NTN requirement in 36.181

CR 0030 — Channel Model Parameters Annex F update for 36.181 TC 8.5 - Rel 19

CR 0028 — Missing Correlation Matrix info (8.2 TC; 36.181; Rel 19)

CR 0025 — CR to TS 36.181: Introduction of IoT-NTN band 252

CR 0036 — Draft CR to TS 36.181: SAN conformance requirements for BOG feature (LTE-based 5G broadcast operation over geosynchronous satellite)

Version history

Indexed versions

Showing 20 of 20 indexed versions.

19.4.0Rel-19RAN#1122026-07-03
18.10.0Rel-18RAN#1122026-07-03
19.3.0Rel-19RAN#1112026-03-27
18.9.0Rel-18RAN#1112026-03-27
19.2.0Rel-19RAN#1102026-01-09
18.8.0Rel-18RAN#1102026-01-09
19.1.0Rel-19RAN#1092025-10-05
18.7.0Rel-18RAN#1092025-10-05
19.0.0Rel-19RAN#1082025-06-23
18.6.0Rel-18RAN#1072025-03-28
18.5.0Rel-18RAN#1052024-09-24
18.4.0Rel-18RAN#1042024-07-10
18.3.0Rel-18RAN#1032024-04-05
18.2.0Rel-18RAN#1022024-01-08
18.1.0Rel-18RAN#1012023-09-29
18.0.0Rel-18RAN#1002023-06-30
1.0.0Rel-18 · pre-approvalRAN#1002023-06-30
0.2.0Rel-18 · pre-approvalRAN4#1072023-06-08
0.1.0Rel-18 · pre-approvalRAN4#106-bis-e2023-06-08
0.0.1Rel-18 · pre-approvalRAN4#1062023-06-08

Atlas classifications

Meaning and provenance

No Atlas classifications have been attached yet.

Work Items

Standards work connected to TS 36.181

IoT_NTN_FDD_LS_band-Perf

Perf. part: Introduction of FDD LTE band (L+S band) for IoT NTN operation

Rel-18parsed
IoT_NTN_extLband-Perf

Perf. part: Introduction of the Extended L-band (UL 1668-1675MHz, DL 1518-1525MHz) for IoT NTN

Rel-18parsed
LTE_NBIOT_eMTC_NTN_req

NB-IoT/eMTC Core and Perf requirements for NTN

Rel-18parsed
LTE_NBIoT_eMTC_NTN_req-Core

Core part: NB-IoT (Narrowband IoT)/eMTC (enhanced Machine Type Communication) core & performance requirements for Non-Terrestrial Networks (NTN)

Rel-18parsed
LTE_NBIoT_eMTC_NTN_req-Perf

Perf. part: NB-IoT (Narrowband IoT)/eMTC (enhanced Machine Type Communication) core & performance requirements for Non-Terrestrial Networks (NTN)

Rel-18official
TEI18

(Small) Technical Enhancements and Improvements for Rel-18

Rel-18parsed
IoT_NTN_FDD_S_band-Perf

Perf. part: Introduction of another IoT-NTN S-band (MSS band 2000-2020 MHz UL and 2180-2200 MHz DL)

Rel-19parsed
IoT_NTN_Ph3-Perf

Perf. part: Non-Terrestrial Networks (NTN) for Internet of Things (IoT) Phase 3

Rel-19parsed
IoT_NTN_TDD-Perf

Perf. part: Introduction of IoT-NTN TDD mode

Rel-19parsed
LTE_band_5G_bcast_GSO-Perf

Perf. part: New LTE band for 5G broadcast for region 3 utilizing a geosynchronous satellite

Rel-19parsed

Knowledge graph

Related standards

No graph edges indexed yet. The graph API is available at this JSON endpoint.