Everything this course is built on

Work item 155

5GSAT

Stage 1 of 5GSAT How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 5GSAT, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/800048/SP-180326.md wi:5GSAT

5GSATB

5G system with satellite backhaul How it was counted: the 5 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 5GSATB, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/970056/SP-230111_clean_S2-2303823_5GSATB.md wi:5GSATB

5GSATB_CH

Charging aspects of Satellite Backhaul in 5GS How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 5GSATB_CH, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/1020024/SP-240266_S5-240549_was SP-231707_revised WID on charging aspects of Satellite Backhaul in 5GS_cl.md wi:5GSATB_CH

5GSATB_OAM

Management aspects of 5G system supporting satellite backhaul How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 5GSATB_OAM, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/1020029/SP-231708 was SP-231445 New WID on management aspects of 5G system supporting satellite backhaul_clean.md wi:5GSATB_OAM

5GSAT_ARCH

Integration of satellite components in the 5G architecture How it was counted: the 2 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 5GSAT_ARCH, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/890034/SP-191335 was SP-191101_New WID 5GSAT_ARCH_S2-1912749.md wi:5GSAT_ARCH

5GSAT_ARCH-CT cited

CT aspects of 5GC architecture for satellite networks How it was counted: the 5 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 5GSAT_ARCH-CT, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/911030/CP-210149-cl.md wi:5GSAT_ARCH-CT

5GSAT_Ph2

Satellite access Phase 2 How it was counted: the 4 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 5GSAT_Ph2, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/989998/SP-230109_clean_S2-2303910_WID_5GSAT_Ph2.md wi:5GSAT_Ph2

5GSAT_Ph2_CH

Charging aspects of 5GSAT How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 5GSAT_Ph2_CH, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/1010018/SP-231152 New WID on charging aspects of Satellite Access in 5GS.md wi:5GSAT_Ph2_CH

5GSAT_Ph3

Satellite access Phase 3 How it was counted: the 2 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 5GSAT_Ph3, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/1020058/SP-230516.md wi:5GSAT_Ph3

5GSAT_Ph3-ARC

Integration of satellite components in the 5G architecture Phase 3 How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 5GSAT_Ph3-ARC, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/1040027/SP-241386_SP-241289_SP-240986_cl_S2-2408685.md wi:5GSAT_Ph3-ARC

5GSAT_Ph3-CH

Charging aspects of satellite access Phase 3 How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 5GSAT_Ph3-CH, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/1070014/SP-250365 was SP-250117 Charging aspects of satellite access Phase 3_cl.md wi:5GSAT_Ph3-CH

5GSAT_Ph3_ARCH

CT aspects of integration of satellite components in the 5G architecture Phase 3 How it was counted: the 4 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 5GSAT_Ph3_ARCH, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/1050019/CP-250134.md wi:5GSAT_Ph3_ARCH

5GSAT_Ph3_App

Application enablement for satellite access Phase 3 How it was counted: the 4 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 5GSAT_Ph3_App, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/1040077/SP-241690_cl_Rev_WID_application_enablement_for_satellite_access_Ph3.md wi:5GSAT_Ph3_App

5GSAT_Ph3_SEC

Security Aspects of 5G Satellite Access Phase 3 How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 5GSAT_Ph3_SEC, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/1060065/SP-241780 New WID on Security Aspects of 5G Satellite Access Phase 3.md wi:5GSAT_Ph3_SEC

5GSAT_Ph4

Satellite access - Phase 4 How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 5GSAT_Ph4, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day wi:5GSAT_Ph4

5GSAT_Ph4-APP

Application enablement for satellite access enabled 5G services Phase 4 How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 5GSAT_Ph4-APP, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/1120101/SP-260547_new_WID_on_5GSAT_Ph4_APP.md wi:5GSAT_Ph4-APP

5GSAT_Ph4-ARC

Stage 2 of Integration of satellite components in the 5G architecture Phase 4 How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 5GSAT_Ph4-ARC, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/1100033/SP-251703_clean-was-SP-251671-was-SP-251344_S2-2511312_New WID-5GSAT_Ph4_ARC.md wi:5GSAT_Ph4-ARC

5GSAT_Ph4-CT

CT aspects for integration of satellite components in the 5G Phase 4 How it was counted: the 4 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 5GSAT_Ph4-CT, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/1120018/CP-261281.md wi:5GSAT_Ph4-CT

5GSAT_Ph4-REQ

Stage 1 for Satellite access - Phase 4 How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 5GSAT_Ph4-REQ, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/1060071/SP-250386.md wi:5GSAT_Ph4-REQ

5GSAT_Ph4-SEC

Security Aspects of 5G Satellite Access Phase 4 How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 5GSAT_Ph4-SEC, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/1120094/SP-260668_ SEcurity Satellite Ph4-cl.md wi:5GSAT_Ph4-SEC

ANSS

Stage 1 for ANSS for LCS How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly ANSS, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day wi:ANSS

FS_5GSAT

Study on using Satellite Access in 5G How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly FS_5GSAT, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/770002/SP-170702.md wi:FS_5GSAT

FS_5GSATB

Study on Support of Satellite Backhauling in 5GS How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly FS_5GSATB, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/940060/SP-211639_was_SP-211602_was_SP-211317_rev06_clean.md wi:FS_5GSATB

FS_5GSAT_ARCH

Study on architecture aspects for using satellite access in 5G How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly FS_5GSAT_ARCH, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/800026/SP-181253_rev_SP-181112_S2-1813347_FS_5GSAT_ARCH_clean.md wi:FS_5GSAT_ARCH

FS_5GSAT_CH

Study on charging aspects of Satellite in 5GS How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly FS_5GSAT_CH, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/980028/SP-221162 New SID on Satellite charging.md wi:FS_5GSAT_CH

FS_5GSAT_MO

Study on management and orchestration aspects with integrated satellite components in a 5G network How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly FS_5GSAT_MO, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/830025/SP-190138 New SID Study on management and orchestration aspects with integrated satellite components in a 5G networks.md wi:FS_5GSAT_MO

FS_5GSAT_Ph2

Study on 5GC enhancement for satellite access Phase 2 How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly FS_5GSAT_Ph2, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/940074/SP-211651_was_SP-211616_was_SP-211331_rev04_clean.md wi:FS_5GSAT_Ph2

FS_5GSAT_Ph3

Study on satellite access - Phase 3 How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly FS_5GSAT_Ph3, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/960016/SP-220679.md wi:FS_5GSAT_Ph3

FS_5GSAT_Ph3_ARCH

Study on Integration of satellite components in the 5G architecture Phase 3 How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly FS_5GSAT_Ph3_ARCH, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/1010033/SP-231199_was1194_was1184_was1169_was1043_wasS2-2310027.md wi:FS_5GSAT_Ph3_ARCH

FS_5GSAT_Ph3_App

Study on application enablement for Satellite access enabled 5G Services How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly FS_5GSAT_Ph3_App, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/1020053/SP-240296_cl_Revised_SID_on_application_enablement_for_Satellite_access_enabled_5G_services.md wi:FS_5GSAT_Ph3_App

FS_5GSAT_Ph3_CH

Study on charging aspects of satellite access Phase 3 How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly FS_5GSAT_Ph3_CH, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/1040014/SP-240980 was SP-240703 New SID on charging aspects of satellite access Phase 3_cl.md wi:FS_5GSAT_Ph3_CH

FS_5GSAT_Ph3_SEC

Study on Security Aspects of 5G Satellite Access Phase 3 How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly FS_5GSAT_Ph3_SEC, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/1020044/SP-240232 Revised Study on Security Aspects of 5G Satellite Access Phase 3-cl.md wi:FS_5GSAT_Ph3_SEC

FS_5GSAT_Ph4

Study on satellite access - Phase 4 How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly FS_5GSAT_Ph4, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/1030042/SP-241824_clean.md wi:FS_5GSAT_Ph4

FS_5GSAT_Ph4_APP

Study on application enablement for satellite access enabled 5G services Phase 4 How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly FS_5GSAT_Ph4_APP, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/1080027/SP-250874_was_250586_Study on application enablement for satellite access enabled 5G services Ph4-v2.md wi:FS_5GSAT_Ph4_APP

FS_5GSAT_Ph4_ARC

Study on Integration of satellite components in the 5G architecture Phase 4 How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly FS_5GSAT_Ph4_ARC, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/1070011/SP-250787_was_766_was_SP-250400_Revised SID-5GSAT_ARC Phase 4-cl.md wi:FS_5GSAT_Ph4_ARC

FS_5GSAT_Ph4_CH

Study on Charging Aspects of satellite access phase 4 How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly FS_5GSAT_Ph4_CH, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/1100012/SP-251664 was SP-251363_was_S5-255419 New SID on Charging Aspects of satellite access phase 4.md wi:FS_5GSAT_Ph4_CH

FS_5GSAT_Ph4_SEC

Study on Security Aspects of Satellite Access in 5G Phase 4 How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly FS_5GSAT_Ph4_SEC, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/1090022/SP-251244 New SID on Security Aspects of 5G Satellite Access Phase 4.md wi:FS_5GSAT_Ph4_SEC

FS_5GSAT_Sec

Study on Security Aspects of Satellite Access How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly FS_5GSAT_Sec, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/970028/SP-220875 New SID on Security Aspects of Satellite Access.md wi:FS_5GSAT_Sec

FS_IMT2020_SAT_eval

Study on self-evaluation towards the IMT-2020 submission of the 3GPP Satellite Radio Interface Technology How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly FS_IMT2020_SAT_eval, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/991030/RP-231945 Revised SID IMT-2020 Satellite cl.md wi:FS_IMT2020_SAT_eval

FS_IoT_NTN

Study on Management Aspects of IoT NTN Enhancements How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly FS_IoT_NTN, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/960026/SP-220490 New SID on Management Aspects of IoT NTN Enhancement.md wi:FS_IoT_NTN

FS_LTE_NBIOT_eMTC_NTN

Study on NB-IoT/eMTC support for NTN How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly FS_LTE_NBIOT_eMTC_NTN, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/860033/RP-202689-SID-NBIoT NTN.md wi:FS_LTE_NBIOT_eMTC_NTN

FS_NR_NTN_GNSS_resilient

Study on GNSS resilient NR-NTN operation How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly FS_NR_NTN_GNSS_resilient, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/1080071/RP-253137 was 1933 New SID on GNSS resilient NR-NTN op_v09.md wi:FS_NR_NTN_GNSS_resilient

FS_NR_NTN_netw_verif_UE_loc

Study on requirements and use cases for network verified UE location for Non-Terrestrial-Networks (NTN) in NR How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly FS_NR_NTN_netw_verif_UE_loc, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/960091/RP-221820 R18 SID Nwk verified UE loc_req_v04_clean.md wi:FS_NR_NTN_netw_verif_UE_loc

FS_NR_NTN_solutions

Study on solutions for NR to support non-terrestrial networks (NTN) How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly FS_NR_NTN_solutions, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/800099/RP-190710_SID NR-NTN solutions_v61.md wi:FS_NR_NTN_solutions

FS_NR_nonterr_nw cited

Study on NR to support non-terrestrial networks How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly FS_NR_nonterr_nw, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/750040/RP-171450 SID RAN NR support NTN v1.5.md wi:FS_NR_nonterr_nw

FS_NTN_OAM_Ph2

Study on Management Aspects of NTN Phase 2 How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly FS_NTN_OAM_Ph2, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/1020013/SP-231733 was SP-231423 Study on Management Aspects of NTN Phase 2_clean.md wi:FS_NTN_OAM_Ph2

FS_ULBC

Study on Ultra Low Bitrate Speech Codec How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly FS_ULBC, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/1070055/SP-250635.md wi:FS_ULBC

IMSSat

IMS access via Digital Video Broadcast - Return Channel via Satellite (DVB-RCS2) How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly IMSSat, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/570027/SP-120543.md wi:IMSSat

IMSSat-SA1

Stage 1 for IMS access via DVB-RCS2 How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly IMSSat-SA1, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/570127/SP-120543.md wi:IMSSat-SA1

INS_SAT

Indirect Network Sharing on Satellite Access Network How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly INS_SAT, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/1050105/SP-241393.md wi:INS_SAT

IoT_NTN_FDD_LS_band

Introduction of FDD LTE band (L+S band) for IoT NTN operation How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly IoT_NTN_FDD_LS_band, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/991043/RP-241353 Revised WID on IoT NTN new band_cl.md wi:IoT_NTN_FDD_LS_band

IoT_NTN_FDD_LS_band-Core

Core part: Introduction of FDD LTE band (L+S band) for IoT NTN operation How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly IoT_NTN_FDD_LS_band-Core, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/991143/RP-241353 Revised WID on IoT NTN new band_cl.md wi:IoT_NTN_FDD_LS_band-Core

IoT_NTN_FDD_LS_band-Perf

Perf. part: Introduction of FDD LTE band (L+S band) for IoT NTN operation How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly IoT_NTN_FDD_LS_band-Perf, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/991243/RP-241353 Revised WID on IoT NTN new band_cl.md wi:IoT_NTN_FDD_LS_band-Perf

IoT_NTN_FDD_LS_band-UEConTest

UE Conformance - Introduction of FDD LTE band (L+S band) for IoT NTN operation How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly IoT_NTN_FDD_LS_band-UEConTest, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/1040109/RP-242992_Revised WI_UE Conformance - Introduction of FDD LTE band (L+S band) for IoT NTN operation.md wi:IoT_NTN_FDD_LS_band-UEConTest

IoT_NTN_FDD_S_band

Introduction of another IoT-NTN S-band (MSS band 2000-2020 MHz UL and 2180-2200 MHz DL) How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly IoT_NTN_FDD_S_band, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/1040130/RP-251820 Revised WID IoT_NTN_FDD_S_band_cl.md wi:IoT_NTN_FDD_S_band

IoT_NTN_FDD_S_band-Core

Core part: Introduction of another IoT-NTN S-band (MSS band 2000-2020 MHz UL and 2180-2200 MHz DL) How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly IoT_NTN_FDD_S_band-Core, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/1041130/RP-251820 Revised WID IoT_NTN_FDD_S_band_cl.md wi:IoT_NTN_FDD_S_band-Core

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) How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly IoT_NTN_FDD_S_band-Perf, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/1042130/RP-251820 Revised WID IoT_NTN_FDD_S_band_cl.md wi:IoT_NTN_FDD_S_band-Perf

IoT_NTN_FDD_S_band-UEConTest

UE Conformance - Introduction of another IoT-NTN S-band (MSS band 2000-2020 MHz UL and 2180-2200 MHz DL) How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly IoT_NTN_FDD_S_band-UEConTest, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/1090061/RP-253692_Revised WID_IoT_NTN_FDD_S_band-UEConTest.md wi:IoT_NTN_FDD_S_band-UEConTest

IoT_NTN_Ph3

Non-Terrestrial Networks (NTN) for Internet of Things (IoT) Phase 3 (for LTE) How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly IoT_NTN_Ph3, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/1020096/RP-252504 WID Rev R19 IOT-NTN cl.md wi:IoT_NTN_Ph3

IoT_NTN_Ph3-Core

Core part: Non-Terrestrial Networks (NTN) for Internet of Things (IoT) Phase 3 How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly IoT_NTN_Ph3-Core, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/1021096/RP-252504 WID Rev R19 IOT-NTN cl.md wi:IoT_NTN_Ph3-Core

IoT_NTN_Ph3-Perf

Perf. part: Non-Terrestrial Networks (NTN) for Internet of Things (IoT) Phase 3 How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly IoT_NTN_Ph3-Perf, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/1032087/RP-252504 WID Rev R19 IOT-NTN cl.md wi:IoT_NTN_Ph3-Perf

IoT_NTN_Ph3_plus_CT1-UEConTest

UE Conformance - Non-Terrestrial Networks (NTN) for Internet of Things (IoT) Phase 3 plus CT1 aspects How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly IoT_NTN_Ph3_plus_CT1-UEConTest, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/1120131/RP-261221 New WID on UE Conformance IoT-NTN Ph3 plus CT1.md wi:IoT_NTN_Ph3_plus_CT1-UEConTest

IoT_NTN_Ph4

NTN for IoT Phase 4 How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly IoT_NTN_Ph4, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/1080090/RP-253813 Revised WID on Non-Terrestrial Networks (NTN) for Internet of Things (IoT) Phase 4_cl.md wi:IoT_NTN_Ph4

IoT_NTN_Ph4-Core

Core part: NTN for IoT Phase 4 How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly IoT_NTN_Ph4-Core, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/1081090/RP-253813 Revised WID on Non-Terrestrial Networks (NTN) for Internet of Things (IoT) Phase 4_cl.md wi:IoT_NTN_Ph4-Core

IoT_NTN_TDD

Introduction of IoT-NTN TDD mode How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly IoT_NTN_TDD, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/1050123/RP-252935 Revised WID on introduction of IoT-NTN TDD_cl.md wi:IoT_NTN_TDD

IoT_NTN_TDD-Core

Core part: Introduction of IoT-NTN TDD mode How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly IoT_NTN_TDD-Core, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/1051123/RP-252935 Revised WID on introduction of IoT-NTN TDD_cl.md wi:IoT_NTN_TDD-Core

IoT_NTN_TDD-Perf

Perf. part: Introduction of IoT-NTN TDD mode How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly IoT_NTN_TDD-Perf, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/1052123/RP-252935 Revised WID on introduction of IoT-NTN TDD_cl.md wi:IoT_NTN_TDD-Perf

IoT_NTN_TDD-UEConTest

UE Conformance - Introduction of IoT-NTN TDD mode How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly IoT_NTN_TDD-UEConTest, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/1100037/RP-253382 New WID on UE Conformance IoT-NTN TDD.md wi:IoT_NTN_TDD-UEConTest

IoT_NTN_enh

IoT (Internet of Things) NTN (non-terrestrial network) enhancements How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly IoT_NTN_enh, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/941004/RP-241351 rev WID_R18_IoT_NTN_enh_cl.md wi:IoT_NTN_enh

IoT_NTN_enh-Core

Core part: IoT (Internet of Things) NTN (non-terrestrial network) enhancements How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly IoT_NTN_enh-Core, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/940104/RP-241351 rev WID_R18_IoT_NTN_enh_cl.md wi:IoT_NTN_enh-Core

IoT_NTN_enh-Perf

Perf. Part: IoT (Internet of Things) NTN (non-terrestrial network) enhancements How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly IoT_NTN_enh-Perf, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/950284/RP-241351 rev WID_R18_IoT_NTN_enh_cl.md wi:IoT_NTN_enh-Perf

IoT_NTN_enh_plus_CT1-UEConTest

UE Conformance - IoT (Internet of Things) NTN (non-terrestrial network) enhancements plus CT1 aspects How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly IoT_NTN_enh_plus_CT1-UEConTest, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/1030073/RP-241949 Revised WID on UE Conformance - IoT NTN enh plus CT1-cl.md wi:IoT_NTN_enh_plus_CT1-UEConTest

IoT_NTN_extLband

Introduction of the Extended L-band (UL 1668-1675MHz, DL 1518-1525MHz) for IoT NTN How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly IoT_NTN_extLband, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/991041/RP-240741_was_RP-233856_IoT_NTN_extLband_WID-cl.md wi:IoT_NTN_extLband

IoT_NTN_extLband-Core

Core part: Introduction of the Extended L-band (UL 1668-1675MHz, DL 1518-1525MHz) for IoT NTN How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly IoT_NTN_extLband-Core, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/991141/RP-240741_was_RP-233856_IoT_NTN_extLband_WID-cl.md wi:IoT_NTN_extLband-Core

IoT_NTN_extLband-Perf

Perf. part: Introduction of the Extended L-band (UL 1668-1675MHz, DL 1518-1525MHz) for IoT NTN How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly IoT_NTN_extLband-Perf, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/991241/RP-240741_was_RP-233856_IoT_NTN_extLband_WID-cl.md wi:IoT_NTN_extLband-Perf

IoT_NTN_extLband-UEConTest

UE Conformance - Introduction of the Extended L-band (UL 1668-1675MHz, DL 1518-1525MHz) for IoT NTN How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly IoT_NTN_extLband-UEConTest, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/1040110/RP-241355.md wi:IoT_NTN_extLband-UEConTest

IoT_SAT_ARCH_EPS

Architecture support for NB-IoT/eMTC Non-Terrestrial Networks in EPS How it was counted: the 5 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly IoT_SAT_ARCH_EPS, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/930019/SP-211306_clean_S2-2109198cl was S2-2108825r03 was S2-2107580 was SP-211124 R17 WID IoT NTN EPS.md wi:IoT_SAT_ARCH_EPS

IoT_SAT_UEConTest

UE conformance test for NB-IoT/eMTC Non-Terrestrial Networks in EPS How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly IoT_SAT_UEConTest, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/1050016/CP-242075.md wi:IoT_SAT_UEConTest

LTE_NBIOT_eMTC_NTN

NB-IoT/eMTC support for Non-Terrestrial Networks How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly LTE_NBIOT_eMTC_NTN, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/920069/RP-211601 was RP-211573 1534 1457 Rel-17 WID-IoT NTN.md wi:LTE_NBIOT_eMTC_NTN

LTE_NBIOT_eMTC_NTN-Core

Core part: NB-IoT/eMTC support for Non-Terrestrial Networks How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly LTE_NBIOT_eMTC_NTN-Core, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/920169/RP-211601 was RP-211573 1534 1457 Rel-17 WID-IoT NTN.md wi:LTE_NBIOT_eMTC_NTN-Core

LTE_NBIOT_eMTC_NTN_plus_EPS-UEConTest

UE Conformance - NB-IoT/eMTC support for Non-Terrestrial Networks (NTN) including EPS aspects How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly LTE_NBIOT_eMTC_NTN_plus_EPS-UEConTest, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/960087/RP-233250cl.md wi:LTE_NBIOT_eMTC_NTN_plus_EPS-UEConTest

LTE_NBIOT_eMTC_NTN_req

NB-IoT/eMTC Core and Perf requirements for NTN How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly LTE_NBIOT_eMTC_NTN_req, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/950074/RP-223437_clean.md wi:LTE_NBIOT_eMTC_NTN_req

LTE_NBIOT_eMTC_NTN_req-UEConTest

UE Conformance - NB-IoT (Narrowband IoT)/eMTC (enhanced Machine Type Communication) core & performance requirements for Non-Terrestrial Networks (NTN) How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly LTE_NBIOT_eMTC_NTN_req-UEConTest, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/981034/RP-240147-cl.md wi:LTE_NBIOT_eMTC_NTN_req-UEConTest

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) How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly LTE_NBIoT_eMTC_NTN_req-Core, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/950174/RP-221556 cl was RP-220938.md wi:LTE_NBIoT_eMTC_NTN_req-Core

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) How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly LTE_NBIoT_eMTC_NTN_req-Perf, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/950274/RP-223437_clean.md wi:LTE_NBIoT_eMTC_NTN_req-Perf

LTE_TN_NR_NTN_HO

E-UTRA TN (Terrestrial Network) to NR NTN handover enhancements How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly LTE_TN_NR_NTN_HO, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/1080091/RP-252890.md wi:LTE_TN_NR_NTN_HO

LTE_TN_NR_NTN_HO-Core

Core part: E-UTRA TN to NR NTN handover enhancements How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly LTE_TN_NR_NTN_HO-Core, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/1081091/RP-252890.md wi:LTE_TN_NR_NTN_HO-Core

LTE_TN_NR_NTN_HO-Perf

Perf. Part: E-UTRA TN to NR NTN handover enhancements How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly LTE_TN_NR_NTN_HO-Perf, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/1082091/RP-252890.md wi:LTE_TN_NR_NTN_HO-Perf

LTE_TN_NR_NTN_mob

Inter-RAT mode mobility support from E-UTRAN TN to NR NTN How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly LTE_TN_NR_NTN_mob, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/1030076/RP-240924 R19 E-UTRAN to NR-NTN mob enh_v14.md wi:LTE_TN_NR_NTN_mob

LTE_TN_NR_NTN_mob-Core

Core part: Inter-RAT mode mobility support from E-UTRAN TN to NR NTN How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly LTE_TN_NR_NTN_mob-Core, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/1031076/RP-240924 R19 E-UTRAN to NR-NTN mob enh_v14.md wi:LTE_TN_NR_NTN_mob-Core

LTE_TN_NR_NTN_mob-UEConTest

UE Conformance - Inter-RAT mobility support from E-UTRAN TN to NR NTN How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly LTE_TN_NR_NTN_mob-UEConTest, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/1100031/RP-253151 New WID on UE Conformance ¿C Inter-RAT mode mobility support from E-UTRAN TN to NR NTN.md wi:LTE_TN_NR_NTN_mob-UEConTest

LTE_band_246_5G_bcast_GSO_BWs

Adding new channel bandwidths for LTE band 246 for 5G broadcast for region 3 utilizing geosynchronous satellite How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly LTE_band_246_5G_bcast_GSO_BWs, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/1110101/RP-261484 Revised New WID for new BWs for BOG_clean.md wi:LTE_band_246_5G_bcast_GSO_BWs

LTE_band_246_5G_bcast_GSO_BWs-Core

Core part: Adding new channel bandwidths for LTE band 246 for 5G broadcast for region 3 utilizing geosynchronous satellite How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly LTE_band_246_5G_bcast_GSO_BWs-Core, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/1111101/RP-261484 Revised New WID for new BWs for BOG_clean.md wi:LTE_band_246_5G_bcast_GSO_BWs-Core

LTE_band_246_5G_bcast_GSO_BWs-Perf

Perf. part: Adding new channel bandwidths for LTE band 246 for 5G broadcast for region 3 utilizing geosynchronous satellite How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly LTE_band_246_5G_bcast_GSO_BWs-Perf, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/1112101/RP-261484 Revised New WID for new BWs for BOG_clean.md wi:LTE_band_246_5G_bcast_GSO_BWs-Perf

LTE_band_5G_bcast_GSO

New LTE band for 5G broadcast for region 3 utilizing a geosynchronous satellite How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly LTE_band_5G_bcast_GSO, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/1070064/RP-253395.md wi:LTE_band_5G_bcast_GSO

LTE_band_5G_bcast_GSO-Core

Core part: New LTE band for 5G broadcast for region 3 utilizing a geosynchronous satellite How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly LTE_band_5G_bcast_GSO-Core, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/1071064/RP-253395.md wi:LTE_band_5G_bcast_GSO-Core

LTE_band_5G_bcast_GSO-Perf

Perf. part: New LTE band for 5G broadcast for region 3 utilizing a geosynchronous satellite How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly LTE_band_5G_bcast_GSO-Perf, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/1072064/RP-253395.md wi:LTE_band_5G_bcast_GSO-Perf

L_Band_LTE_ATC_MSS

Adding L-Band (Band 24) LTE for Ancillary Terrestrial Component (ATC) of Mobile Satellite Service (MSS) in North America How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly L_Band_LTE_ATC_MSS, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/470010/RP-101284_Coversheet for L-Band WID.md wi:L_Band_LTE_ATC_MSS

L_Band_LTE_ATC_MSS-Core

Core part: Adding L-Band (Band 24) LTE for ATC of MSS in North America How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly L_Band_LTE_ATC_MSS-Core, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/470110/RP-101284_Coversheet for L-Band WID.md wi:L_Band_LTE_ATC_MSS-Core

L_Band_LTE_ATC_MSS-Perf

Perf. part: Adding L-Band (Band 24) LTE for ATC of MSS in North America How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly L_Band_LTE_ATC_MSS-Perf, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/470210/RP-101284_Coversheet for L-Band WID.md wi:L_Band_LTE_ATC_MSS-Perf

L_Band_LTE_ATC_MSS-UEConTest

Test part: Adding L-Band (Band 24) LTE for ATC of MSS in North America How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly L_Band_LTE_ATC_MSS-UEConTest, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/510015/RP-110777_Markup.md wi:L_Band_LTE_ATC_MSS-UEConTest

MPS_Sat

MPS support in 3GPP system with satellite How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly MPS_Sat, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/1060072/SP-241823.md wi:MPS_Sat

NR_IoT_NTN_req_Ph2

Enhanced requirements for NR NTN and IoT NTN Phase 2 How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly NR_IoT_NTN_req_Ph2, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/1090070/RP-253834 Revised WID NR_IoT_NTN_req_Ph2_cl.md wi:NR_IoT_NTN_req_Ph2

NR_IoT_NTN_req_Ph2-Core

Core part: Enhanced requirements for NR NTN and IoT NTN Phase 2 How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly NR_IoT_NTN_req_Ph2-Core, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/1091070/RP-253834 Revised WID NR_IoT_NTN_req_Ph2_cl.md wi:NR_IoT_NTN_req_Ph2-Core

NR_IoT_NTN_req_Ph2-Perf

Perf. part: Enhanced requirements for NR NTN and IoT NTN Phase 2 How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly NR_IoT_NTN_req_Ph2-Perf, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/1092070/RP-253834 Revised WID NR_IoT_NTN_req_Ph2_cl.md wi:NR_IoT_NTN_req_Ph2-Perf

NR_IoT_NTN_req_test_enh

Enhanced requirements and test methodology for NR NTN and IoT NTN How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly NR_IoT_NTN_req_test_enh, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/1030086/RP-252076 Revised WID on NR_IoT_NTN_req_test_enh_cl.md wi:NR_IoT_NTN_req_test_enh

NR_IoT_NTN_req_test_enh-Core

Core part: Enhanced requirements and conductive test methodology for NR NTN and IoT NTN How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly NR_IoT_NTN_req_test_enh-Core, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/1031086/RP-252076 Revised WID on NR_IoT_NTN_req_test_enh_cl.md wi:NR_IoT_NTN_req_test_enh-Core

NR_IoT_NTN_req_test_enh-Perf

Perf. Part: Enhanced requirements and conductive test methodology for NR NTN and IoT NTN How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly NR_IoT_NTN_req_test_enh-Perf, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/1032086/RP-252076 Revised WID on NR_IoT_NTN_req_test_enh_cl.md wi:NR_IoT_NTN_req_test_enh-Perf

NR_IoT_NTN_req_test_enh-UEConTest

UE Conformance - Enhanced requirements and conductive test methodology for NR NTN and IoT NTN How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly NR_IoT_NTN_req_test_enh-UEConTest, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/1090063/RP-252575 RAN5 WID.md wi:NR_IoT_NTN_req_test_enh-UEConTest

NR_NTN_CBW_30MHz

30 MHz Channel Bandwidth for NR NTN (non-terrestrial networks) in FR1 (frequency range 1) How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly NR_NTN_CBW_30MHz, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/1000060/RP-232647 was 2594 was 1567 New WID 30 MHz Ch BW NR NTN FR1 v10.md wi:NR_NTN_CBW_30MHz

NR_NTN_CBW_30MHz-Core

Core part: 30 MHz Channel Bandwidth for NR NTN (non-terrestrial networks) in FR1 (frequency range 1) How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly NR_NTN_CBW_30MHz-Core, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/1001060/RP-232647 was 2594 was 1567 New WID 30 MHz Ch BW NR NTN FR1 v10.md wi:NR_NTN_CBW_30MHz-Core

NR_NTN_GNSS_resilient

GNSS (Global Navigation Satellite System) resilient NR-NTN (Non-Terrestrial Networks) operation How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly NR_NTN_GNSS_resilient, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/1120122/RP-261568 was 1553 New WID on GNSS resilient NR-NTN op_v03.md wi:NR_NTN_GNSS_resilient

NR_NTN_GNSS_resilient-Core

Core part: GNSS resilient NR-NTN operation How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly NR_NTN_GNSS_resilient-Core, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/1121122/RP-261568 was 1553 New WID on GNSS resilient NR-NTN op_v03.md wi:NR_NTN_GNSS_resilient-Core

NR_NTN_GNSS_resilient-Perf

Perf. Part: GNSS resilient NR-NTN operation How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly NR_NTN_GNSS_resilient-Perf, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/1122122/RP-261568 was 1553 New WID on GNSS resilient NR-NTN op_v03.md wi:NR_NTN_GNSS_resilient-Perf

NR_NTN_IoT_NTN_ext_guard

Extended guard band for NR NTN and IoT NTN How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly NR_NTN_IoT_NTN_ext_guard, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/1120124/RP-261532 WID Extended guardband for NR IoT NTN.md wi:NR_NTN_IoT_NTN_ext_guard

NR_NTN_IoT_NTN_ext_guard-Core

Core part: Extended guard band for NR NTN and IoT NTN How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly NR_NTN_IoT_NTN_ext_guard-Core, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/1121124/RP-261532 WID Extended guardband for NR IoT NTN.md wi:NR_NTN_IoT_NTN_ext_guard-Core

NR_NTN_Ku_bands

Introduction of Ku bands for NR NTN How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly NR_NTN_Ku_bands, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/1040135/RP-252911_WID revision for the NTN Ku band cl.md wi:NR_NTN_Ku_bands

NR_NTN_Ku_bands-Core

Core part: Introduction of Ku bands for NR NTN How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly NR_NTN_Ku_bands-Core, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/1041135/RP-252911_WID revision for the NTN Ku band cl.md wi:NR_NTN_Ku_bands-Core

NR_NTN_Ku_bands-Perf

Perf. part: Introduction of Ku bands for NR NTN How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly NR_NTN_Ku_bands-Perf, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/1042135/RP-252911_WID revision for the NTN Ku band cl.md wi:NR_NTN_Ku_bands-Perf

NR_NTN_LSband

Introduction of the satellite L-/S-band for NR How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly NR_NTN_LSband, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/981043/RP-234043 NTN LSband WID_cl.md wi:NR_NTN_LSband

NR_NTN_LSband-Core

Core part: Introduction of the satellite L-/S-band for NR How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly NR_NTN_LSband-Core, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/981143/RP-234043 NTN LSband WID_cl.md wi:NR_NTN_LSband-Core

NR_NTN_LSband-Perf

Perf. part: Introduction of the satellite L-/S-band for NR How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly NR_NTN_LSband-Perf, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/981243/RP-234043 NTN LSband WID_cl.md wi:NR_NTN_LSband-Perf

NR_NTN_Ph3

Non-Terrestrial Networks (NTN) for NR Phase 3 How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly NR_NTN_Ph3, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/1020097/RP-251954 was 243300 Rel-19 WID NR NTN phase 3_v12.md wi:NR_NTN_Ph3

NR_NTN_Ph3-Core

Core part: Non-Terrestrial Networks (NTN) for NR Phase 3 How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly NR_NTN_Ph3-Core, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/1021097/RP-251954 was 243300 Rel-19 WID NR NTN phase 3_v12.md wi:NR_NTN_Ph3-Core

NR_NTN_Ph3-Perf

Perf. part: Non-Terrestrial Networks (NTN) for NR Phase 3 How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly NR_NTN_Ph3-Perf, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/1022097/RP-251954 was 243300 Rel-19 WID NR NTN phase 3_v12.md wi:NR_NTN_Ph3-Perf

NR_NTN_Ph3-UEConTest

UE Conformance - Non-Terrestrial Networks (NTN) for NR Phase 3 How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly NR_NTN_Ph3-UEConTest, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/1110090/RP-261450_revised WID on UE Conformance - Non-Terrestrial Networks (NTN) for NR Phase 3.md wi:NR_NTN_Ph3-UEConTest

NR_NTN_Sband

Introduction of another NR NTN S-band (MSS band 2000-2020 MHz UL and 2180-2200 MHz DL) How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly NR_NTN_Sband, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/1040129/RP-250488 rev_WID_NR_NTN_Sband_cl.md wi:NR_NTN_Sband

NR_NTN_Sband-Core

Core part: Introduction of another NR NTN S-band (MSS band 2000-2020 MHz UL and 2180-2200 MHz DL) How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly NR_NTN_Sband-Core, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/1041129/RP-250488 rev_WID_NR_NTN_Sband_cl.md wi:NR_NTN_Sband-Core

NR_NTN_Sband-Perf

Perf. part: Introduction of another NR NTN S-band (MSS band 2000-2020 MHz UL and 2180-2200 MHz DL) How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly NR_NTN_Sband-Perf, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/1042129/RP-250488 rev_WID_NR_NTN_Sband_cl.md wi:NR_NTN_Sband-Perf

NR_NTN_combinedLband

New NR NTN bands to support Extended L-band and combined MSS L-band and Extended L-band ranges How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly NR_NTN_combinedLband, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/1040134/RP-252893 - Revised WID NR_NTN_combinedLband-rm.md wi:NR_NTN_combinedLband

NR_NTN_combinedLband-Core

Core part: Introduction of new NR NTN bands to support the Extended L-band (UL 1668-1675MHz, DL 1518-1525MHz) and the combined MSS L-band and Extended L-band ranges (UL 1626.5-1660.5 MHz and 1668-1675 MHz, DL 1518-1559 MHz) How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly NR_NTN_combinedLband-Core, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/1041134/RP-252893 - Revised WID NR_NTN_combinedLband-rm.md wi:NR_NTN_combinedLband-Core

NR_NTN_combinedLband-Perf

STOPPED - Perf. part: Introduction of new NR NTN bands to support the Extended L-band (UL 1668-1675MHz, DL 1518-1525MHz) and the combined MSS L-band and Extended L-band ranges (UL 1626.5-1660.5 MHz and 1668-1675 MHz, DL 1518-1559 MHz) How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly NR_NTN_combinedLband-Perf, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/1042134/RP-252893 - Revised WID NR_NTN_combinedLband-rm.md wi:NR_NTN_combinedLband-Perf

NR_NTN_enh

NR NTN (Non-Terrestrial Networks) enhancements How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly NR_NTN_enh, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/941006/RP-240779 R18 WID NR_NTN_enh_v23.md wi:NR_NTN_enh

NR_NTN_enh-Core

Core part: NR NTN (Non-Terrestrial Networks) enhancements How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly NR_NTN_enh-Core, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/941106/RP-232669 R18 WID NR_NTN_enh_v19.md wi:NR_NTN_enh-Core

NR_NTN_enh-Perf

Perf. part: NR NTN (Non-Terrestrial Networks) enhancements How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly NR_NTN_enh-Perf, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/941206/RP-232669 R18 WID NR_NTN_enh_v19.md wi:NR_NTN_enh-Perf

NR_NTN_enh_plus_CT-UEConTest

UE Conformance - NR NTN (non-Terrestrial Networks) enhancements plus CT aspects How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly NR_NTN_enh_plus_CT-UEConTest, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/1050130/RP-251230_revised WID on UE Conformance - NR NTN (Non-Terrestrial Networks) enhancements_plusCTaspects.md wi:NR_NTN_enh_plus_CT-UEConTest

NR_NTN_solutions cited

Solutions for NR to support non-terrestrial networks (NTN) How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly NR_NTN_solutions, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/860046/RP-220208_WID NR-NTN_for Rel-17 v6.3.md wi:NR_NTN_solutions

NR_NTN_solutions-Core

Core part: Solutions for NR for NTN How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly NR_NTN_solutions-Core, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/860146/RP-221169_WID NR-NTN_for Rel-17 v6.3.md wi:NR_NTN_solutions-Core

NR_NTN_solutions-Perf

Perf. Part: Solutions for NR for NTN How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly NR_NTN_solutions-Perf, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/860246/RP-222556_WID NR-NTN_for Rel-17 v6.4.md wi:NR_NTN_solutions-Perf

NR_NTN_solutions_plus_CT-UEConTest

UE Conformance - Solutions for NR to support non-terrestrial networks (NTN) plus CT aspects How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly NR_NTN_solutions_plus_CT-UEConTest, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/960074/RP-251228_revised WID_NR_NTN_Solutions.md wi:NR_NTN_solutions_plus_CT-UEConTest

NTN_OAM_Ph2

Management Aspects of NTN Phase 2 How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly NTN_OAM_Ph2, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/1060016/SP-250514 was S5-252022 Rel-19 Revised WID on Management Aspects of NTN Phase 2_cl.md wi:NTN_OAM_Ph2

NTN_OAM_Ph3-OAM

Management Aspects of NTN Phase 3 How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly NTN_OAM_Ph3-OAM, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/1110043/SP-260312 New WID on Management Aspects of NTN Phase 3.md wi:NTN_OAM_Ph3-OAM

NTN_bands_Features_R20

Introduction of the higher power classes, 3MHz channel bandwidth and eRedCap for the existing NR/IoT NTN bands How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly NTN_bands_Features_R20, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/1100051/RP-253841 WID NTN_Bands_Features_R20.md wi:NTN_bands_Features_R20

NTN_bands_Features_R20-Core

Core part: Introduction of the higher power classes, 3MHz channel bandwidth and eRedCap for the existing NR/IoT NTN bands How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly NTN_bands_Features_R20-Core, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/1101051/RP-253841 WID NTN_Bands_Features_R20.md wi:NTN_bands_Features_R20-Core

OAM_NTN

Management Aspects of NTN How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly OAM_NTN, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/990033/SP-230183 New WID on Management Aspects of NTN.md wi:OAM_NTN

PWS_NTN

Support for PWS in Satellite E-UTRAN and Satellite NG-RAN How it was counted: the 3 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly PWS_NTN, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/1070009/CP-251222_cl.md wi:PWS_NTN

SCVS

5G system with satellite access to Support Control and/or Video Surveillance How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly SCVS, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/920034/SP-210527.md wi:SCVS

S_Band_LTE_ATC_MSS

Adding 2 GHz band LTE FDD (Band 23) for Ancillary Terrestrial Component (ATC) of Mobile Satellite Service (MSS) in North America How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly S_Band_LTE_ATC_MSS, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/470009/RP-110775 S-band WID - core part (clean).md wi:S_Band_LTE_ATC_MSS

S_Band_LTE_ATC_MSS-Core

Core part: Adding 2 GHz band LTE FDD (Band 23) for ATC of MSS in North America How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly S_Band_LTE_ATC_MSS-Core, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/470109/RP-110775 S-band WID - core part (clean).md wi:S_Band_LTE_ATC_MSS-Core

S_Band_LTE_ATC_MSS-Perf

Perf. part: Adding 2 GHz band LTE FDD (Band 23) for ATC of MSS in North America How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly S_Band_LTE_ATC_MSS-Perf, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/470209/RP-110775 S-band WID - core part (clean).md wi:S_Band_LTE_ATC_MSS-Perf

S_Band_LTE_ATC_MSS-UEConTest

Test part: Adding 2 GHz band LTE FDD (Band 23) for ATC of MSS in North America How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly S_Band_LTE_ATC_MSS-UEConTest, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/520012/RP-110623.md wi:S_Band_LTE_ATC_MSS-UEConTest

TEI20_QoS_MWAB_SAT

QoS aspect of MWAB using Satellite How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly TEI20_QoS_MWAB_SAT, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/1120035/SP-260326_SP-260300_S2-2601637_TEI20_SAT_Backhaul_WID_clean.md wi:TEI20_QoS_MWAB_SAT

TEI20_QoS_MWAB_SAT-ARC

QoS aspect of MWAB using Satellite How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly TEI20_QoS_MWAB_SAT-ARC, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/1110027/SP-260326_SP-260300_S2-2601637_TEI20_SAT_Backhaul_WID_clean.md wi:TEI20_QoS_MWAB_SAT-ARC

TEI20_QoS_MWAB_SAT-CT

CT Aspects for QoS aspects of MWAB using satellite How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly TEI20_QoS_MWAB_SAT-CT, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/1120001/CP-261016.md wi:TEI20_QoS_MWAB_SAT-CT

ULBC-MED

Ultra Low Bitrate Speech Codec for IMS Voice Call over NB-IoT NTN via GEO Satellite How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly ULBC-MED, read on 2026-08-05; the days are that row's millisecond stamps read as UTC days, and the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite the same day; its classification, leadership and targets from the work item description /var/www/whatthespec.net/data/data/wis/1120096/SP-260696.md wi:ULBC-MED

Meeting document 115

CP-210149

Revised WID on CT aspects of 5GC architecture for satellite networks How it was counted: the row of table `tdoc` named CP-210149, which is the value of `hyperlink` on a work plan row of this subject — the document the work plan itself points at for that work item, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:CP-210149

CP-213273

New Rel-17 WID on IoT NTN support for EPS How it was counted: the row of table `tdoc` named CP-213273, which is the value of `hyperlink` on a work plan row of this subject — the document the work plan itself points at for that work item, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:CP-213273

CP-232131

Revised WID on 5GSATB How it was counted: the row of table `tdoc` named CP-232131, which is the value of `hyperlink` on a work plan row of this subject — the document the work plan itself points at for that work item, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:CP-232131

CP-240269

Revised WID on 5GC/EPC enhancement for satellite access Phase 2 How it was counted: the row of table `tdoc` named CP-240269, which is the value of `hyperlink` on a work plan row of this subject — the document the work plan itself points at for that work item, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:CP-240269

CP-242075

UE conformance test for NB-IoT/eMTC Non-Terrestrial Networks in EPS How it was counted: the row of table `tdoc` named CP-242075, which is the value of `hyperlink` on a work plan row of this subject — the document the work plan itself points at for that work item, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:CP-242075

CP-243071

New WID on CT aspects for application enablement for satellite access Phase 3 How it was counted: the row of table `tdoc` named CP-243071, which is the value of `hyperlink` on a work plan row of this subject — the document the work plan itself points at for that work item, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:CP-243071

CP-250134

Revised WID on CT aspects of integration of satellite components in the 5G architecture Phase 3 How it was counted: the row of table `tdoc` named CP-250134, which is the value of `hyperlink` on a work plan row of this subject — the document the work plan itself points at for that work item, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:CP-250134

CP-251222

Revised WID on support for PWS over IoT NTN How it was counted: the row of table `tdoc` named CP-251222, which is the value of `hyperlink` on a work plan row of this subject — the document the work plan itself points at for that work item, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:CP-251222

CP-261016

CT Aspects for QoS aspects of MWAB using satellite How it was counted: the row of table `tdoc` named CP-261016, which is the value of `hyperlink` on a work plan row of this subject — the document the work plan itself points at for that work item, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:CP-261016

CP-261281

New WID on CT aspects for integration of satellite components in the 5G Phase 4 How it was counted: the row of table `tdoc` named CP-261281, which is the value of `hyperlink` on a work plan row of this subject — the document the work plan itself points at for that work item, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:CP-261281

RP-101284

Updated WID for the L_BAND_LTE_ATC_MSS WI How it was counted: the row of table `tdoc` named RP-101284, which is the value of `hyperlink` on a work plan row of this subject — the document the work plan itself points at for that work item, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:RP-101284

RP-110623

WI proposal for UE Conformance Test Aspects – Adding 2 GHz band LTE FDD (band 23) for ATC of MSS in North America How it was counted: the row of table `tdoc` named RP-110623, which is the value of `hyperlink` on a work plan row of this subject — the document the work plan itself points at for that work item, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:RP-110623

RP-110775

Adding 2 GHz band LTE for ATC of MSS in North America How it was counted: the row of table `tdoc` named RP-110775, which is the value of `hyperlink` on a work plan row of this subject — the document the work plan itself points at for that work item, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:RP-110775

RP-110777

Updated WID for Conformance Test part: Adding L-Band (Band 24) LTE for ATC of MSS in North America How it was counted: the row of table `tdoc` named RP-110777, which is the value of `hyperlink` on a work plan row of this subject — the document the work plan itself points at for that work item, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:RP-110777

RP-171450 cited

Revised SID: Study on NR to support Non-Terrestrial Networks How it was counted: the row of table `tdoc` named RP-171450, which is the value of `hyperlink` on a work plan row of this subject — the document the work plan itself points at for that work item, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:RP-171450

RP-190710

Revised SID for Study on solutions for NR to support non-terrestrial networks (NTN) How it was counted: the row of table `tdoc` named RP-190710, which is the value of `hyperlink` on a work plan row of this subject — the document the work plan itself points at for that work item, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:RP-190710

RP-202689

Revised SID: Study on NB-Io/eMTC support for Non-Terrestrial Network How it was counted: the row of table `tdoc` named RP-202689, which is the value of `hyperlink` on a work plan row of this subject — the document the work plan itself points at for that work item, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:RP-202689

RP-211601

New Rel-17 WID on NB-IoT/eMTC support for Non-Terrestrial Networks How it was counted: the row of table `tdoc` named RP-211601, which is the value of `hyperlink` on a work plan row of this subject — the document the work plan itself points at for that work item, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:RP-211601

RP-220208

Revised WID: Solutions for NR to support non-terrestrial networks (NTN) How it was counted: the row of table `tdoc` named RP-220208, which is the value of `hyperlink` on a work plan row of this subject — the document the work plan itself points at for that work item, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:RP-220208

RP-221169

Solutions for NR to support non-terrestrial networks (NTN) How it was counted: the row of table `tdoc` named RP-221169, which is the value of `hyperlink` on a work plan row of this subject — the document the work plan itself points at for that work item, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:RP-221169

RP-221556

Revised WI: NB-IoT/eMTC core & performance requirements for Non-Terrestrial Networks How it was counted: the row of table `tdoc` named RP-221556, which is the value of `hyperlink` on a work plan row of this subject — the document the work plan itself points at for that work item, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:RP-221556

RP-221820

New SI: Study on requirements and use cases for network verified UE location for Non-Terrestrial-Networks (NTN) in NR How it was counted: the row of table `tdoc` named RP-221820, which is the value of `hyperlink` on a work plan row of this subject — the document the work plan itself points at for that work item, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:RP-221820

RP-222556

Revised WID: Solutions for NR to support non-terrestrial networks (NTN) How it was counted: the row of table `tdoc` named RP-222556, which is the value of `hyperlink` on a work plan row of this subject — the document the work plan itself points at for that work item, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:RP-222556

RP-223437

Revised WI: NB-IoT (Narrowband IoT)/eMTC (enhanced Machine Type Communication) core & performance requirements for Non-Terrestrial Networks (NTN) How it was counted: the row of table `tdoc` named RP-223437, which is the value of `hyperlink` on a work plan row of this subject — the document the work plan itself points at for that work item, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:RP-223437

RP-231945

Revised SID: Study on self-evaluation towards the IMT-2020 submission of the 3GPP Satellite Radio Interface Technology How it was counted: the row of table `tdoc` named RP-231945, which is the value of `hyperlink` on a work plan row of this subject — the document the work plan itself points at for that work item, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:RP-231945

RP-232647

Revised WID: 30 MHz Channel Bandwidth for NR NTN in FR1 How it was counted: the row of table `tdoc` named RP-232647, which is the value of `hyperlink` on a work plan row of this subject — the document the work plan itself points at for that work item, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:RP-232647

RP-232669

Revised WID: NR NTN (Non-Terrestrial Networks) enhancements How it was counted: the row of table `tdoc` named RP-232669, which is the value of `hyperlink` on a work plan row of this subject — the document the work plan itself points at for that work item, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:RP-232669

RP-233250

Revised WID: UE Conformance - NB-IoT/eMTC support for Non-Terrestrial Networks (NTN) including EPS aspects How it was counted: the row of table `tdoc` named RP-233250, which is the value of `hyperlink` on a work plan row of this subject — the document the work plan itself points at for that work item, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:RP-233250

RP-234043

Revised WID on Introduction of the satellite L-/S-band How it was counted: the row of table `tdoc` named RP-234043, which is the value of `hyperlink` on a work plan row of this subject — the document the work plan itself points at for that work item, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:RP-234043

RP-240147

Revised WID: UE Conformance - NB-IoT (Narrowband IoT)/eMTC (enhanced Machine Type Communication) core & performance requirements for Non-Terrestrial Networks (NTN) How it was counted: the row of table `tdoc` named RP-240147, which is the value of `hyperlink` on a work plan row of this subject — the document the work plan itself points at for that work item, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:RP-240147

RP-240741

Revised WID: Introduction of the Extended L-band (UL 1668-1675MHz, DL 1518-1525MHz) for IoT NTN How it was counted: the row of table `tdoc` named RP-240741, which is the value of `hyperlink` on a work plan row of this subject — the document the work plan itself points at for that work item, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:RP-240741

RP-240779

Revised WID: NR NTN (Non-Terrestrial Networks) enhancements How it was counted: the row of table `tdoc` named RP-240779, which is the value of `hyperlink` on a work plan row of this subject — the document the work plan itself points at for that work item, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:RP-240779

RP-240924

Revised WID: Inter RAT mobility support from E-UTRAN TN to NR-NTN How it was counted: the row of table `tdoc` named RP-240924, which is the value of `hyperlink` on a work plan row of this subject — the document the work plan itself points at for that work item, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:RP-240924

RP-241351

Revised WID: IoT (Internet of Things) NTN (non-terrestrial network) enhancements How it was counted: the row of table `tdoc` named RP-241351, which is the value of `hyperlink` on a work plan row of this subject — the document the work plan itself points at for that work item, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:RP-241351

RP-241353

Revised WID: Introduction of FDD LTE band (L+S band) for IoT NTN operation How it was counted: the row of table `tdoc` named RP-241353, which is the value of `hyperlink` on a work plan row of this subject — the document the work plan itself points at for that work item, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:RP-241353

RP-241355

New WID: UE Conformance - Introduction of the Extended L-band (UL 1668-1675MHz, DL 1518-1525MHz) for IoT NTN How it was counted: the row of table `tdoc` named RP-241355, which is the value of `hyperlink` on a work plan row of this subject — the document the work plan itself points at for that work item, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:RP-241355

RP-241949

Revised WID on UE Conformance - IoT NTN enhancements plus CT1 aspects How it was counted: the row of table `tdoc` named RP-241949, which is the value of `hyperlink` on a work plan row of this subject — the document the work plan itself points at for that work item, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:RP-241949

RP-242992

Revised WI: UE Conformance - Introduction of FDD LTE band (L+S band) for IoT NTN operation How it was counted: the row of table `tdoc` named RP-242992, which is the value of `hyperlink` on a work plan row of this subject — the document the work plan itself points at for that work item, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:RP-242992

RP-250488

Revised WID on Introduction of another NR-NTN S-band (MSS band 2000-2020 MHz UL and 2180-2200 MHz DL) How it was counted: the row of table `tdoc` named RP-250488, which is the value of `hyperlink` on a work plan row of this subject — the document the work plan itself points at for that work item, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:RP-250488

RP-251228

Revised WID on UE Conformance – Solutions for NR to support non-terrestrial networks (NTN) plus CT aspects How it was counted: the row of table `tdoc` named RP-251228, which is the value of `hyperlink` on a work plan row of this subject — the document the work plan itself points at for that work item, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:RP-251228

RP-251820

Revised WID: Introduction of another IoT-NTN S-band (MSS band 2000-2020 MHz UL and 2180-2200 MHz DL) How it was counted: the row of table `tdoc` named RP-251820, which is the value of `hyperlink` on a work plan row of this subject — the document the work plan itself points at for that work item, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:RP-251820

RP-251954

Non-Terrestrial Networks (NTN) for NR Phase 3 How it was counted: the row of table `tdoc` named RP-251954, which is the value of `hyperlink` on a work plan row of this subject — the document the work plan itself points at for that work item, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:RP-251954

RP-252076

Revised WID on enhanced requirements and conductive test methodology for NR NTN and IoT NTN How it was counted: the row of table `tdoc` named RP-252076, which is the value of `hyperlink` on a work plan row of this subject — the document the work plan itself points at for that work item, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:RP-252076

RP-252504

Revised WI: Non-Terrestrial Networks (NTN) for Internet of Things (IoT) Phase 3 How it was counted: the row of table `tdoc` named RP-252504, which is the value of `hyperlink` on a work plan row of this subject — the document the work plan itself points at for that work item, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:RP-252504

RP-252575

New WID on UE Conformance - Enhanced requirements and conductive test methodology for NR NTN and IoT NTN How it was counted: the row of table `tdoc` named RP-252575, which is the value of `hyperlink` on a work plan row of this subject — the document the work plan itself points at for that work item, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:RP-252575

RP-252890

Revised WID on E-UTRA TN to NR NTN handover enhancements How it was counted: the row of table `tdoc` named RP-252890, which is the value of `hyperlink` on a work plan row of this subject — the document the work plan itself points at for that work item, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:RP-252890

RP-252893

Revised WID: Core part: Introduction of new NR NTN bands to support the Extended L-band (UL 1668-1675MHz, DL 1518-1525MHz) and the combined MSS L-band and Extended L-band ranges (UL 1626.5-1660.5 MHz and 1668-1675 MHz, DL 1518-1559 MHz) How it was counted: the row of table `tdoc` named RP-252893, which is the value of `hyperlink` on a work plan row of this subject — the document the work plan itself points at for that work item, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:RP-252893

RP-252911

Revised WID: Introduction of Ku bands for NR NTN How it was counted: the row of table `tdoc` named RP-252911, which is the value of `hyperlink` on a work plan row of this subject — the document the work plan itself points at for that work item, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:RP-252911

RP-252935

Revised WID for introduction of IoT-NTN TDD mode How it was counted: the row of table `tdoc` named RP-252935, which is the value of `hyperlink` on a work plan row of this subject — the document the work plan itself points at for that work item, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:RP-252935

RP-253137

Revised SID: Study on GNSS (Global Navigation Satellite System) resilient NR-NTN (Non-Terrestrial Networks) operation How it was counted: the row of table `tdoc` named RP-253137, which is the value of `hyperlink` on a work plan row of this subject — the document the work plan itself points at for that work item, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:RP-253137

RP-253382

New WID: UE Conformance - Introduction of IoT-NTN TDD mode How it was counted: the row of table `tdoc` named RP-253382, which is the value of `hyperlink` on a work plan row of this subject — the document the work plan itself points at for that work item, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:RP-253382

RP-253395

Revised WID: New LTE band for 5G broadcast for region 3 utilizing geosynchronous satellite How it was counted: the row of table `tdoc` named RP-253395, which is the value of `hyperlink` on a work plan row of this subject — the document the work plan itself points at for that work item, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:RP-253395

RP-253692

Revised WID: UE Conformance - Introduction of another IoT-NTN S-band (MSS band 2000-2020 MHz UL and 2180-2200 MHz DL) How it was counted: the row of table `tdoc` named RP-253692, which is the value of `hyperlink` on a work plan row of this subject — the document the work plan itself points at for that work item, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:RP-253692

RP-253813

Revised WID: Non-Terrestrial Networks (NTN) for Internet of Things (IoT) Phase 4 How it was counted: the row of table `tdoc` named RP-253813, which is the value of `hyperlink` on a work plan row of this subject — the document the work plan itself points at for that work item, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:RP-253813

RP-260283

Revised WID: Non-Terrestrial Networks (NTN) for NR Phase 3 How it was counted: the row of table `tdoc` named RP-260283, which is the value of `hyperlink` on a work plan row of this subject — the document the work plan itself points at for that work item, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:RP-260283

RP-260518

Revised WI: Non-Terrestrial Networks (NTN) for Internet of Things (IoT) Phase 3 How it was counted: the row of table `tdoc` named RP-260518, which is the value of `hyperlink` on a work plan row of this subject — the document the work plan itself points at for that work item, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:RP-260518

RP-260520

Revised WID on UE Conformance - NR NTN (Non-Terrestrial Networks) enhancements How it was counted: the row of table `tdoc` named RP-260520, which is the value of `hyperlink` on a work plan row of this subject — the document the work plan itself points at for that work item, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:RP-260520

RP-260573

WID revision for Enh. requirements and conductive test methodology for NR NTN and IoT NTN How it was counted: the row of table `tdoc` named RP-260573, which is the value of `hyperlink` on a work plan row of this subject — the document the work plan itself points at for that work item, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:RP-260573

RP-260769

Revised WID: New LTE band for 5G broadcast for region 3 utilizing geosynchronous satellite How it was counted: the row of table `tdoc` named RP-260769, which is the value of `hyperlink` on a work plan row of this subject — the document the work plan itself points at for that work item, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:RP-260769

RP-260883

Revised WID on UE Conformance - Inter-RAT mobility support from E-UTRAN TN to NR NTN How it was counted: the row of table `tdoc` named RP-260883, which is the value of `hyperlink` on a work plan row of this subject — the document the work plan itself points at for that work item, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:RP-260883

RP-261083

Revised WID: Non-Terrestrial Networks (NTN) for Internet of Things (IoT) Phase 4 How it was counted: the row of table `tdoc` named RP-261083, which is the value of `hyperlink` on a work plan row of this subject — the document the work plan itself points at for that work item, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:RP-261083

RP-261221

New WID on UE Conformance - Introduction of Non-Terrestrial Networks (NTN) for Internet of Things (IoT) Phase 3 plus CT1 aspects How it was counted: the row of table `tdoc` named RP-261221, which is the value of `hyperlink` on a work plan row of this subject — the document the work plan itself points at for that work item, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:RP-261221

RP-261450

Revised WID on UE Conformance - Non-Terrestrial Networks (NTN) for NR Phase 3 plus CT1 aspects How it was counted: the row of table `tdoc` named RP-261450, which is the value of `hyperlink` on a work plan row of this subject — the document the work plan itself points at for that work item, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:RP-261450

RP-261484

Revised WID: dding new channel bandwidths for LTE band 246 for 5G broadcast for region 3 utilizing geosynchronous satellite How it was counted: the row of table `tdoc` named RP-261484, which is the value of `hyperlink` on a work plan row of this subject — the document the work plan itself points at for that work item, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:RP-261484

RP-261532

New WID: Extended guard band for NR and IoT NTN How it was counted: the row of table `tdoc` named RP-261532, which is the value of `hyperlink` on a work plan row of this subject — the document the work plan itself points at for that work item, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:RP-261532

RP-261551

Revised WID for Introduction of the higher power classes, 3MHz channel bandwidth and (e)RedCap for the existing NR/IoT NTN bands How it was counted: the row of table `tdoc` named RP-261551, which is the value of `hyperlink` on a work plan row of this subject — the document the work plan itself points at for that work item, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:RP-261551

RP-261563

Revised WI: Enhanced requirements for NR NTN and IoT NTN Phase 2 How it was counted: the row of table `tdoc` named RP-261563, which is the value of `hyperlink` on a work plan row of this subject — the document the work plan itself points at for that work item, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:RP-261563

RP-261568

New WID on GNSS (Global Navigation Satellite System) resilient NR-NTN (Non-Terrestrial Networks) operation How it was counted: the row of table `tdoc` named RP-261568, which is the value of `hyperlink` on a work plan row of this subject — the document the work plan itself points at for that work item, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:RP-261568

SP-120543

WID for IMS access via Digital Video Broadcast - Return Channel via Satellite (DVB-RCS2) (IMSSat) How it was counted: the row of table `tdoc` named SP-120543, which is the value of `hyperlink` on a work plan row of this subject — the document the work plan itself points at for that work item, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-120543

SP-170702

New WID on Study on using Satellite Access in 5G (FS_5GSAT) How it was counted: the row of table `tdoc` named SP-170702, which is the value of `hyperlink` on a work plan row of this subject — the document the work plan itself points at for that work item, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-170702

SP-180326

New WID on Integration of Satellite Access in 5G (5GSAT) How it was counted: the row of table `tdoc` named SP-180326, which is the value of `hyperlink` on a work plan row of this subject — the document the work plan itself points at for that work item, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-180326

SP-181253

Update to FS_5GSAT_ARCH: Study on architecture aspects for using satellite access in 5G How it was counted: the row of table `tdoc` named SP-181253, which is the value of `hyperlink` on a work plan row of this subject — the document the work plan itself points at for that work item, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-181253

SP-190138

New Study on management and orchestration aspects with integrated satellite components in a 5G network How it was counted: the row of table `tdoc` named SP-190138, which is the value of `hyperlink` on a work plan row of this subject — the document the work plan itself points at for that work item, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-190138

SP-191335

New WID: Integration of satellite systems in the 5G architecture (Proposed for Rel-17, 5GSAT_ARCH) How it was counted: the row of table `tdoc` named SP-191335, which is the value of `hyperlink` on a work plan row of this subject — the document the work plan itself points at for that work item, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-191335

SP-210527

New WID on SCVS (5G system with satellite access to Support Control and/or Video Surveillance) How it was counted: the row of table `tdoc` named SP-210527, which is the value of `hyperlink` on a work plan row of this subject — the document the work plan itself points at for that work item, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-210527

SP-210528

New WID on 5GSATB (5G system with satellite backhaul) How it was counted: the row of table `tdoc` named SP-210528, which is the value of `hyperlink` on a work plan row of this subject — the document the work plan itself points at for that work item, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-210528

SP-211306

Revised WID: 'Architecture support for NB-IoT/eMTC Non-Terrestrial Networks in EPS' [IoT_SAT_ARCH_EPS]. How it was counted: the row of table `tdoc` named SP-211306, which is the value of `hyperlink` on a work plan row of this subject — the document the work plan itself points at for that work item, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-211306

SP-211639

New SID: Study on 5G System with Satellite Backhaul How it was counted: the row of table `tdoc` named SP-211639, which is the value of `hyperlink` on a work plan row of this subject — the document the work plan itself points at for that work item, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-211639

SP-211651

New SID: Study on satellite access Phase 2 How it was counted: the row of table `tdoc` named SP-211651, which is the value of `hyperlink` on a work plan row of this subject — the document the work plan itself points at for that work item, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-211651

SP-220490

New SID on Management Aspects of IoT NTN Enhancements How it was counted: the row of table `tdoc` named SP-220490, which is the value of `hyperlink` on a work plan row of this subject — the document the work plan itself points at for that work item, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-220490

SP-220679

New SID on satellite access - Phase 3 (FS_5GSAT_Ph3) How it was counted: the row of table `tdoc` named SP-220679, which is the value of `hyperlink` on a work plan row of this subject — the document the work plan itself points at for that work item, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-220679

SP-220875

New Study on Security Aspects of Satellite Access How it was counted: the row of table `tdoc` named SP-220875, which is the value of `hyperlink` on a work plan row of this subject — the document the work plan itself points at for that work item, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-220875

SP-221162

New Study on charging aspects of Satellite in 5GS How it was counted: the row of table `tdoc` named SP-221162, which is the value of `hyperlink` on a work plan row of this subject — the document the work plan itself points at for that work item, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-221162

SP-230109

Revised WID: 5GC/EPC enhancement for satellite access Phase 2 (5GSAT_Ph2). How it was counted: the row of table `tdoc` named SP-230109, which is the value of `hyperlink` on a work plan row of this subject — the document the work plan itself points at for that work item, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-230109

SP-230111

WID update for 5GSATB How it was counted: the row of table `tdoc` named SP-230111, which is the value of `hyperlink` on a work plan row of this subject — the document the work plan itself points at for that work item, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-230111

SP-230183

New WID on Management Aspects of NTN How it was counted: the row of table `tdoc` named SP-230183, which is the value of `hyperlink` on a work plan row of this subject — the document the work plan itself points at for that work item, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-230183

SP-230516

New WID on Satellite access - Phase 3 (5GSAT_Ph3) How it was counted: the row of table `tdoc` named SP-230516, which is the value of `hyperlink` on a work plan row of this subject — the document the work plan itself points at for that work item, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-230516

SP-231152

New WID on charging aspects of Satellite Access in 5GS. How it was counted: the row of table `tdoc` named SP-231152, which is the value of `hyperlink` on a work plan row of this subject — the document the work plan itself points at for that work item, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-231152

SP-231199

New SID on Study on Integration of satellite components in the 5G architecture Phase III. How it was counted: the row of table `tdoc` named SP-231199, which is the value of `hyperlink` on a work plan row of this subject — the document the work plan itself points at for that work item, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-231199

SP-231708

New WID on management aspects of 5G system supporting satellite backhaul How it was counted: the row of table `tdoc` named SP-231708, which is the value of `hyperlink` on a work plan row of this subject — the document the work plan itself points at for that work item, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-231708

SP-231733

New SID: Study on Management Aspects of NTN Phase 2 How it was counted: the row of table `tdoc` named SP-231733, which is the value of `hyperlink` on a work plan row of this subject — the document the work plan itself points at for that work item, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-231733

SP-240232

Revised SID on Security Aspects of 5G Satellite Access Phase 3 How it was counted: the row of table `tdoc` named SP-240232, which is the value of `hyperlink` on a work plan row of this subject — the document the work plan itself points at for that work item, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-240232

SP-240266

Revised WID on charging aspects of Satellite Backhaul in 5GS How it was counted: the row of table `tdoc` named SP-240266, which is the value of `hyperlink` on a work plan row of this subject — the document the work plan itself points at for that work item, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-240266

SP-240296

Revised SID on application enablement for Satellite access enabled 5G services How it was counted: the row of table `tdoc` named SP-240296, which is the value of `hyperlink` on a work plan row of this subject — the document the work plan itself points at for that work item, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-240296

SP-240980

New SID on charging aspects of satellite access Phase 3 How it was counted: the row of table `tdoc` named SP-240980, which is the value of `hyperlink` on a work plan row of this subject — the document the work plan itself points at for that work item, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-240980

SP-241386

Revised WID on Integration of satellite components in the 5G architecture Phase 3 How it was counted: the row of table `tdoc` named SP-241386, which is the value of `hyperlink` on a work plan row of this subject — the document the work plan itself points at for that work item, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-241386

SP-241393

New mini WID on Network Sharing on Satellite Access Network How it was counted: the row of table `tdoc` named SP-241393, which is the value of `hyperlink` on a work plan row of this subject — the document the work plan itself points at for that work item, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-241393

SP-241690

Revised WID on Satellite access enabled 5G services How it was counted: the row of table `tdoc` named SP-241690, which is the value of `hyperlink` on a work plan row of this subject — the document the work plan itself points at for that work item, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-241690

SP-241780

New WID on Security Aspects of 5G Satellite Access Phase 3 How it was counted: the row of table `tdoc` named SP-241780, which is the value of `hyperlink` on a work plan row of this subject — the document the work plan itself points at for that work item, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-241780

SP-241823

New mini WID on MPS when access to EPC/5GC is Satellite How it was counted: the row of table `tdoc` named SP-241823, which is the value of `hyperlink` on a work plan row of this subject — the document the work plan itself points at for that work item, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-241823

SP-241824

Revised SID on Study on satellite access - Phase 4 How it was counted: the row of table `tdoc` named SP-241824, which is the value of `hyperlink` on a work plan row of this subject — the document the work plan itself points at for that work item, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-241824

SP-250365

New WID on charging aspects of satellite access Phase 3 How it was counted: the row of table `tdoc` named SP-250365, which is the value of `hyperlink` on a work plan row of this subject — the document the work plan itself points at for that work item, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-250365

SP-250386

Revised WID on Stage 1 for Satellite access - Phase 4 (5GSAT_Ph4-REQ) How it was counted: the row of table `tdoc` named SP-250386, which is the value of `hyperlink` on a work plan row of this subject — the document the work plan itself points at for that work item, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-250386

SP-250514

Revised WID on Management Aspects of NTN Phase 2 How it was counted: the row of table `tdoc` named SP-250514, which is the value of `hyperlink` on a work plan row of this subject — the document the work plan itself points at for that work item, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-250514

SP-250635

Revised Study on Ultra Low Bitrate Speech Codec How it was counted: the row of table `tdoc` named SP-250635, which is the value of `hyperlink` on a work plan row of this subject — the document the work plan itself points at for that work item, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-250635

SP-250787

Revised SID on Study on Integration of satellite components in the 5G architecture Phase 4 How it was counted: the row of table `tdoc` named SP-250787, which is the value of `hyperlink` on a work plan row of this subject — the document the work plan itself points at for that work item, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-250787

SP-250874

New SID on enhancements to application enablement for satellite access enabled 5G services Phase 4 How it was counted: the row of table `tdoc` named SP-250874, which is the value of `hyperlink` on a work plan row of this subject — the document the work plan itself points at for that work item, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-250874

SP-251244

New Study on Security Aspects of Satellite Access in 5G Phase 4 How it was counted: the row of table `tdoc` named SP-251244, which is the value of `hyperlink` on a work plan row of this subject — the document the work plan itself points at for that work item, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-251244

SP-251664

New SID: Study on Charging Aspects of satellite access phase 4 How it was counted: the row of table `tdoc` named SP-251664, which is the value of `hyperlink` on a work plan row of this subject — the document the work plan itself points at for that work item, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-251664

SP-260312

New WID: Management Aspects of NTN Phase 3 How it was counted: the row of table `tdoc` named SP-260312, which is the value of `hyperlink` on a work plan row of this subject — the document the work plan itself points at for that work item, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-260312

SP-260326

New TEI20 WID on Support of Satellite Backhaul for MWAB How it was counted: the row of table `tdoc` named SP-260326, which is the value of `hyperlink` on a work plan row of this subject — the document the work plan itself points at for that work item, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-260326

SP-260423

Revised WID on Integration of satellite components in the 5G architecture Phase 4 How it was counted: the row of table `tdoc` named SP-260423, which is the value of `hyperlink` on a work plan row of this subject — the document the work plan itself points at for that work item, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-260423

SP-260547

New WID: Application enablement for satellite access enabled 5G services Phase 4 How it was counted: the row of table `tdoc` named SP-260547, which is the value of `hyperlink` on a work plan row of this subject — the document the work plan itself points at for that work item, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-260547

SP-260668

New WID: Security Aspects of 5G Satellite Access Phase 4 How it was counted: the row of table `tdoc` named SP-260668, which is the value of `hyperlink` on a work plan row of this subject — the document the work plan itself points at for that work item, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-260668

SP-260696

New WID on Ultra Low Bitrate Speech Codec for Voice over GEO How it was counted: the row of table `tdoc` named SP-260696, which is the value of `hyperlink` on a work plan row of this subject — the document the work plan itself points at for that work item, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-260696

Counted from the data 114

35306 Satellites meeting documents cited

35306 How it was counted: rows of the tdoc table whose `winame` column names, as a whole word, one of the 155 acronyms this subject's rule selects, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:sat-tdocs

155 Satellites work item acronyms cited

155 How it was counted: distinct acronyms over the 183 work plan rows this subject's rule selects, asked of /var/www/whatthespec.net/data/database/api/wp.sqlite on 2026-08-05 count:sat-acronyms

183 Satellites rows in the work plan cited

183 How it was counted: rows of table `item` selected by this subject's rule, out of 9495 rows in the whole work plan, asked of /var/www/whatthespec.net/data/database/api/wp.sqlite on 2026-08-05 count:sat-workplan-rows

116 of the acronyms carry a completion value of 1 cited

116 How it was counted: acronyms whose outermost work plan row has `percentcomplete` exactly '1', which is what the work plan writes when the plan for that row is complete; it says nothing about any other row, asked of /var/www/whatthespec.net/data/database/api/wp.sqlite on 2026-08-05 count:sat-completed-rows

4346 documents carrying the work item NR_NTN_solutions-Core

4346 How it was counted: rows of the tdoc table whose work item column names NR_NTN_solutions-Core as a whole word; the first and last meeting are those of its earliest and latest upload time, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:tdocs:NR_NTN_solutions-Core

3249 documents carrying the work item NR_NTN_enh-Core

3249 How it was counted: rows of the tdoc table whose work item column names NR_NTN_enh-Core as a whole word; the first and last meeting are those of its earliest and latest upload time, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:tdocs:NR_NTN_enh-Core

2807 documents carrying the work item NR_NTN_Ph3-Core

2807 How it was counted: rows of the tdoc table whose work item column names NR_NTN_Ph3-Core as a whole word; the first and last meeting are those of its earliest and latest upload time, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:tdocs:NR_NTN_Ph3-Core

1427 documents carrying the work item IoT_NTN_Ph3-Core

1427 How it was counted: rows of the tdoc table whose work item column names IoT_NTN_Ph3-Core as a whole word; the first and last meeting are those of its earliest and latest upload time, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:tdocs:IoT_NTN_Ph3-Core

1386 documents carrying the work item IoT_NTN_enh-Core

1386 How it was counted: rows of the tdoc table whose work item column names IoT_NTN_enh-Core as a whole word; the first and last meeting are those of its earliest and latest upload time, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:tdocs:IoT_NTN_enh-Core

1008 documents carrying the work item NR_NTN_solutions_plus_CT-UEConTest

1008 How it was counted: rows of the tdoc table whose work item column names NR_NTN_solutions_plus_CT-UEConTest as a whole word; the first and last meeting are those of its earliest and latest upload time, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:tdocs:NR_NTN_solutions_plus_CT-UEConTest

912 documents carrying the work item 5GSAT_ARCH-CT

912 How it was counted: rows of the tdoc table whose work item column names 5GSAT_ARCH-CT as a whole word; the first and last meeting are those of its earliest and latest upload time, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:tdocs:5GSAT_ARCH-CT

862 documents carrying the work item 5GSAT_Ph3_ARCH

862 How it was counted: rows of the tdoc table whose work item column names 5GSAT_Ph3_ARCH as a whole word; the first and last meeting are those of its earliest and latest upload time, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:tdocs:5GSAT_Ph3_ARCH

810 documents carrying the work item 5GSAT_Ph2

810 How it was counted: rows of the tdoc table whose work item column names 5GSAT_Ph2 as a whole word; the first and last meeting are those of its earliest and latest upload time, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:tdocs:5GSAT_Ph2

794 documents carrying the work item FS_NR_NTN_solutions

794 How it was counted: rows of the tdoc table whose work item column names FS_NR_NTN_solutions as a whole word; the first and last meeting are those of its earliest and latest upload time, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:tdocs:FS_NR_NTN_solutions

781 documents carrying the work item NR_NTN_solutions

781 How it was counted: rows of the tdoc table whose work item column names NR_NTN_solutions as a whole word; the first and last meeting are those of its earliest and latest upload time, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:tdocs:NR_NTN_solutions

778 documents carrying the work item NR_NTN_solutions-Perf

778 How it was counted: rows of the tdoc table whose work item column names NR_NTN_solutions-Perf as a whole word; the first and last meeting are those of its earliest and latest upload time, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:tdocs:NR_NTN_solutions-Perf

689 documents carrying the work item LTE_NBIOT_eMTC_NTN

689 How it was counted: rows of the tdoc table whose work item column names LTE_NBIOT_eMTC_NTN as a whole word; the first and last meeting are those of its earliest and latest upload time, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:tdocs:LTE_NBIOT_eMTC_NTN

673 documents carrying the work item LTE_NBIOT_eMTC_NTN-Core

673 How it was counted: rows of the tdoc table whose work item column names LTE_NBIOT_eMTC_NTN-Core as a whole word; the first and last meeting are those of its earliest and latest upload time, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:tdocs:LTE_NBIOT_eMTC_NTN-Core

579 documents carrying the work item FS_5GSAT_Ph4_ARC

579 How it was counted: rows of the tdoc table whose work item column names FS_5GSAT_Ph4_ARC as a whole word; the first and last meeting are those of its earliest and latest upload time, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:tdocs:FS_5GSAT_Ph4_ARC

553 documents carrying the work item LTE_NBIOT_eMTC_NTN_req-UEConTest

553 How it was counted: rows of the tdoc table whose work item column names LTE_NBIOT_eMTC_NTN_req-UEConTest as a whole word; the first and last meeting are those of its earliest and latest upload time, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:tdocs:LTE_NBIOT_eMTC_NTN_req-UEConTest

545 documents carrying the work item FS_LTE_NBIOT_eMTC_NTN

545 How it was counted: rows of the tdoc table whose work item column names FS_LTE_NBIOT_eMTC_NTN as a whole word; the first and last meeting are those of its earliest and latest upload time, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:tdocs:FS_LTE_NBIOT_eMTC_NTN

534 documents carrying the work item NR_IoT_NTN_req_test_enh-Core

534 How it was counted: rows of the tdoc table whose work item column names NR_IoT_NTN_req_test_enh-Core as a whole word; the first and last meeting are those of its earliest and latest upload time, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:tdocs:NR_IoT_NTN_req_test_enh-Core

533 documents carrying the work item 5GSAT_Ph3-ARC

533 How it was counted: rows of the tdoc table whose work item column names 5GSAT_Ph3-ARC as a whole word; the first and last meeting are those of its earliest and latest upload time, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:tdocs:5GSAT_Ph3-ARC

518 documents carrying the work item IoT_SAT_ARCH_EPS

518 How it was counted: rows of the tdoc table whose work item column names IoT_SAT_ARCH_EPS as a whole word; the first and last meeting are those of its earliest and latest upload time, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:tdocs:IoT_SAT_ARCH_EPS

508 documents carrying the work item 5GSAT_ARCH

508 How it was counted: rows of the tdoc table whose work item column names 5GSAT_ARCH as a whole word; the first and last meeting are those of its earliest and latest upload time, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:tdocs:5GSAT_ARCH

486 documents carrying the work item NR_NTN_enh

486 How it was counted: rows of the tdoc table whose work item column names NR_NTN_enh as a whole word; the first and last meeting are those of its earliest and latest upload time, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:tdocs:NR_NTN_enh

442 documents carrying the work item FS_5GSAT_Ph3_ARCH

442 How it was counted: rows of the tdoc table whose work item column names FS_5GSAT_Ph3_ARCH as a whole word; the first and last meeting are those of its earliest and latest upload time, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:tdocs:FS_5GSAT_Ph3_ARCH

411 documents carrying the work item NR_NTN_Ku_bands-Core

411 How it was counted: rows of the tdoc table whose work item column names NR_NTN_Ku_bands-Core as a whole word; the first and last meeting are those of its earliest and latest upload time, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:tdocs:NR_NTN_Ku_bands-Core

359 documents carrying the work item FS_5GSAT_ARCH

359 How it was counted: rows of the tdoc table whose work item column names FS_5GSAT_ARCH as a whole word; the first and last meeting are those of its earliest and latest upload time, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:tdocs:FS_5GSAT_ARCH

354 documents carrying the work item IoT_NTN_TDD-Core

354 How it was counted: rows of the tdoc table whose work item column names IoT_NTN_TDD-Core as a whole word; the first and last meeting are those of its earliest and latest upload time, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:tdocs:IoT_NTN_TDD-Core

344 documents carrying the work item LTE_NBIoT_eMTC_NTN_req-Perf

344 How it was counted: rows of the tdoc table whose work item column names LTE_NBIoT_eMTC_NTN_req-Perf as a whole word; the first and last meeting are those of its earliest and latest upload time, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:tdocs:LTE_NBIoT_eMTC_NTN_req-Perf

341 documents carrying the work item LTE_NBIoT_eMTC_NTN_req-Core

341 How it was counted: rows of the tdoc table whose work item column names LTE_NBIoT_eMTC_NTN_req-Core as a whole word; the first and last meeting are those of its earliest and latest upload time, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:tdocs:LTE_NBIoT_eMTC_NTN_req-Core

330 documents carrying the work item FS_NR_NTN_GNSS_resilient

330 How it was counted: rows of the tdoc table whose work item column names FS_NR_NTN_GNSS_resilient as a whole word; the first and last meeting are those of its earliest and latest upload time, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:tdocs:FS_NR_NTN_GNSS_resilient

330 documents carrying the work item LTE_NBIOT_eMTC_NTN_plus_EPS-UEConTest

330 How it was counted: rows of the tdoc table whose work item column names LTE_NBIOT_eMTC_NTN_plus_EPS-UEConTest as a whole word; the first and last meeting are those of its earliest and latest upload time, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:tdocs:LTE_NBIOT_eMTC_NTN_plus_EPS-UEConTest

326 documents carrying the work item NR_NTN_enh-Perf

326 How it was counted: rows of the tdoc table whose work item column names NR_NTN_enh-Perf as a whole word; the first and last meeting are those of its earliest and latest upload time, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:tdocs:NR_NTN_enh-Perf

325 documents carrying the work item FS_ULBC

325 How it was counted: rows of the tdoc table whose work item column names FS_ULBC as a whole word; the first and last meeting are those of its earliest and latest upload time, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:tdocs:FS_ULBC

319 documents carrying the work item 5GSAT_Ph3_App

319 How it was counted: rows of the tdoc table whose work item column names 5GSAT_Ph3_App as a whole word; the first and last meeting are those of its earliest and latest upload time, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:tdocs:5GSAT_Ph3_App

317 documents carrying the work item FS_5GSAT_Ph3_SEC

317 How it was counted: rows of the tdoc table whose work item column names FS_5GSAT_Ph3_SEC as a whole word; the first and last meeting are those of its earliest and latest upload time, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:tdocs:FS_5GSAT_Ph3_SEC

277 documents carrying the work item FS_5GSAT_Ph4

277 How it was counted: rows of the tdoc table whose work item column names FS_5GSAT_Ph4 as a whole word; the first and last meeting are those of its earliest and latest upload time, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:tdocs:FS_5GSAT_Ph4

272 documents carrying the work item IoT_NTN_enh

272 How it was counted: rows of the tdoc table whose work item column names IoT_NTN_enh as a whole word; the first and last meeting are those of its earliest and latest upload time, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:tdocs:IoT_NTN_enh

227 documents carrying the work item NR_IoT_NTN_req_test_enh-Perf

227 How it was counted: rows of the tdoc table whose work item column names NR_IoT_NTN_req_test_enh-Perf as a whole word; the first and last meeting are those of its earliest and latest upload time, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:tdocs:NR_IoT_NTN_req_test_enh-Perf

208 documents carrying the work item 5GSATB

208 How it was counted: rows of the tdoc table whose work item column names 5GSATB as a whole word; the first and last meeting are those of its earliest and latest upload time, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:tdocs:5GSATB

205 documents carrying the work item FS_5GSAT_Ph3

205 How it was counted: rows of the tdoc table whose work item column names FS_5GSAT_Ph3 as a whole word; the first and last meeting are those of its earliest and latest upload time, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:tdocs:FS_5GSAT_Ph3

205 documents carrying the work item NR_NTN_enh_plus_CT-UEConTest

205 How it was counted: rows of the tdoc table whose work item column names NR_NTN_enh_plus_CT-UEConTest as a whole word; the first and last meeting are those of its earliest and latest upload time, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:tdocs:NR_NTN_enh_plus_CT-UEConTest

204 documents carrying the work item 5GSAT_Ph4-ARC

204 How it was counted: rows of the tdoc table whose work item column names 5GSAT_Ph4-ARC as a whole word; the first and last meeting are those of its earliest and latest upload time, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:tdocs:5GSAT_Ph4-ARC

195 documents carrying the work item FS_5GSAT_Ph3_App

195 How it was counted: rows of the tdoc table whose work item column names FS_5GSAT_Ph3_App as a whole word; the first and last meeting are those of its earliest and latest upload time, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:tdocs:FS_5GSAT_Ph3_App

193 documents carrying the work item FS_5GSAT_Ph2

193 How it was counted: rows of the tdoc table whose work item column names FS_5GSAT_Ph2 as a whole word; the first and last meeting are those of its earliest and latest upload time, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:tdocs:FS_5GSAT_Ph2

190 documents carrying the work item NR_NTN_Ph3

190 How it was counted: rows of the tdoc table whose work item column names NR_NTN_Ph3 as a whole word; the first and last meeting are those of its earliest and latest upload time, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:tdocs:NR_NTN_Ph3

185 documents carrying the work item NR_IoT_NTN_req_Ph2-Core

185 How it was counted: rows of the tdoc table whose work item column names NR_IoT_NTN_req_Ph2-Core as a whole word; the first and last meeting are those of its earliest and latest upload time, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:tdocs:NR_IoT_NTN_req_Ph2-Core

179 documents carrying the work item FS_IMT2020_SAT_eval

179 How it was counted: rows of the tdoc table whose work item column names FS_IMT2020_SAT_eval as a whole word; the first and last meeting are those of its earliest and latest upload time, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:tdocs:FS_IMT2020_SAT_eval

164 documents carrying the work item IoT_NTN_Ph4-Core

164 How it was counted: rows of the tdoc table whose work item column names IoT_NTN_Ph4-Core as a whole word; the first and last meeting are those of its earliest and latest upload time, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:tdocs:IoT_NTN_Ph4-Core

164 documents carrying the work item NR_NTN_LSband-Core

164 How it was counted: rows of the tdoc table whose work item column names NR_NTN_LSband-Core as a whole word; the first and last meeting are those of its earliest and latest upload time, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:tdocs:NR_NTN_LSband-Core

160 documents carrying the work item IoT_NTN_TDD

160 How it was counted: rows of the tdoc table whose work item column names IoT_NTN_TDD as a whole word; the first and last meeting are those of its earliest and latest upload time, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:tdocs:IoT_NTN_TDD

159 documents carrying the work item IoT_NTN_enh_plus_CT1-UEConTest

159 How it was counted: rows of the tdoc table whose work item column names IoT_NTN_enh_plus_CT1-UEConTest as a whole word; the first and last meeting are those of its earliest and latest upload time, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:tdocs:IoT_NTN_enh_plus_CT1-UEConTest

150 documents carrying the work item NR_IoT_NTN_req_test_enh-UEConTest

150 How it was counted: rows of the tdoc table whose work item column names NR_IoT_NTN_req_test_enh-UEConTest as a whole word; the first and last meeting are those of its earliest and latest upload time, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:tdocs:NR_IoT_NTN_req_test_enh-UEConTest

145 documents carrying the work item NR_NTN_Ph3-Perf

145 How it was counted: rows of the tdoc table whose work item column names NR_NTN_Ph3-Perf as a whole word; the first and last meeting are those of its earliest and latest upload time, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:tdocs:NR_NTN_Ph3-Perf

124 documents carrying the work item FS_NR_nonterr_nw cited

124 How it was counted: rows of the tdoc table whose work item column names FS_NR_nonterr_nw as a whole word; the first and last meeting are those of its earliest and latest upload time, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:tdocs:FS_NR_nonterr_nw

120 documents carrying the work item FS_5GSAT_Ph3_CH

120 How it was counted: rows of the tdoc table whose work item column names FS_5GSAT_Ph3_CH as a whole word; the first and last meeting are those of its earliest and latest upload time, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:tdocs:FS_5GSAT_Ph3_CH

120 documents carrying the work item FS_5GSAT_Ph4_SEC

120 How it was counted: rows of the tdoc table whose work item column names FS_5GSAT_Ph4_SEC as a whole word; the first and last meeting are those of its earliest and latest upload time, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:tdocs:FS_5GSAT_Ph4_SEC

120 documents carrying the work item IoT_NTN_Ph3

120 How it was counted: rows of the tdoc table whose work item column names IoT_NTN_Ph3 as a whole word; the first and last meeting are those of its earliest and latest upload time, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:tdocs:IoT_NTN_Ph3

115 documents carrying the work item FS_NTN_OAM_Ph2

115 How it was counted: rows of the tdoc table whose work item column names FS_NTN_OAM_Ph2 as a whole word; the first and last meeting are those of its earliest and latest upload time, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:tdocs:FS_NTN_OAM_Ph2

111 documents carrying the work item FS_5GSATB

111 How it was counted: rows of the tdoc table whose work item column names FS_5GSATB as a whole word; the first and last meeting are those of its earliest and latest upload time, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:tdocs:FS_5GSATB

109 documents carrying the work item 5GSAT

109 How it was counted: rows of the tdoc table whose work item column names 5GSAT as a whole word; the first and last meeting are those of its earliest and latest upload time, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:tdocs:5GSAT

103 documents carrying the work item IoT_NTN_Ph4

103 How it was counted: rows of the tdoc table whose work item column names IoT_NTN_Ph4 as a whole word; the first and last meeting are those of its earliest and latest upload time, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:tdocs:IoT_NTN_Ph4

12603 Satellites documents of type discussion

12603 How it was counted: Satellites documents whose `tdoctype` column is exactly 'discussion', asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:type-discussion

10374 Satellites documents of type CR

10374 How it was counted: Satellites documents whose `tdoctype` column is exactly 'CR', asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:type-cr

4374 Satellites documents of type pCR

4374 How it was counted: Satellites documents whose `tdoctype` column is exactly 'pCR', asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:type-pcr

2192 Satellites documents of type draftCR

2192 How it was counted: Satellites documents whose `tdoctype` column is exactly 'draftCR', asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:type-draftcr

1712 Satellites documents of type other

1712 How it was counted: Satellites documents whose `tdoctype` column is exactly 'other', asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:type-other

1407 Satellites documents of type LS out

1407 How it was counted: Satellites documents whose `tdoctype` column is exactly 'LS out', asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:type-ls-out

898 Satellites documents of type LS in

898 How it was counted: Satellites documents whose `tdoctype` column is exactly 'LS in', asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:type-ls-in

478 Satellites documents of type CR pack

478 How it was counted: Satellites documents whose `tdoctype` column is exactly 'CR pack', asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:type-cr-pack

7768 Satellites documents whose outcome word is noted

7768 How it was counted: Satellites documents whose `status` column is exactly 'noted', asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:status-noted

7054 Satellites documents whose outcome word is revised

7054 How it was counted: Satellites documents whose `status` column is exactly 'revised', asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:status-revised

5615 Satellites documents whose outcome word is not treated

5615 How it was counted: Satellites documents whose `status` column is exactly 'not treated', asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:status-not-treated

4298 Satellites documents whose outcome word is agreed

4298 How it was counted: Satellites documents whose `status` column is exactly 'agreed', asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:status-agreed

3461 Satellites documents whose outcome word is available

3461 How it was counted: Satellites documents whose `status` column is exactly 'available', asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:status-available

2365 Satellites documents whose outcome word is approved

2365 How it was counted: Satellites documents whose `status` column is exactly 'approved', asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:status-approved

550 meetings have had Satellites documents on the table cited

550 How it was counted: distinct values of the meeting column over these documents, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:meetings

R4-116 handled 555 Satellites documents, more than any other meeting cited

555 How it was counted: Satellites documents grouped by meeting, largest first, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:busiest-meeting

141 Satellites documents marked Rel-15

141 How it was counted: Satellites documents whose release column is Rel-15, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:release-rel-15

1226 Satellites documents marked Rel-16

1226 How it was counted: Satellites documents whose release column is Rel-16, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:release-rel-16

8846 Satellites documents marked Rel-17

8846 How it was counted: Satellites documents whose release column is Rel-17, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:release-rel-17

10362 Satellites documents marked Rel-18

10362 How it was counted: Satellites documents whose release column is Rel-18, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:release-rel-18

10927 Satellites documents marked Rel-19

10927 How it was counted: Satellites documents whose release column is Rel-19, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:release-rel-19

2576 Satellites documents marked Rel-20

2576 How it was counted: Satellites documents whose release column is Rel-20, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:release-rel-20

1226 Satellites documents carry no release at all

1226 How it was counted: Satellites documents whose release column is empty, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:release-none

74 Satellites documents filed in 2017

74 How it was counted: Satellites documents whose upload time starts 2017, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:year-2017

328 Satellites documents filed in 2018

328 How it was counted: Satellites documents whose upload time starts 2018, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:year-2018

918 Satellites documents filed in 2019

918 How it was counted: Satellites documents whose upload time starts 2019, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:year-2019

650 Satellites documents filed in 2020

650 How it was counted: Satellites documents whose upload time starts 2020, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:year-2020

3198 Satellites documents filed in 2021

3198 How it was counted: Satellites documents whose upload time starts 2021, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:year-2021

4784 Satellites documents filed in 2022

4784 How it was counted: Satellites documents whose upload time starts 2022, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:year-2022

5619 Satellites documents filed in 2023

5619 How it was counted: Satellites documents whose upload time starts 2023, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:year-2023

7679 Satellites documents filed in 2024

7679 How it was counted: Satellites documents whose upload time starts 2024, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:year-2024

8109 Satellites documents filed in 2025

8109 How it was counted: Satellites documents whose upload time starts 2025, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:year-2025

2890 Satellites documents filed in 2026

2890 How it was counted: Satellites documents whose upload time starts 2026, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:year-2026

the earliest of these documents went up on 2017-05-27

2017-05-27 How it was counted: the smallest upload time over the Satellites documents. This is where the store begins, not where the work began, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:first-upload

the newest of them went up on 2026-07-31

2026-07-31 How it was counted: the largest upload time over the Satellites documents, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:last-upload

1057 Satellites documents carry no upload time

1057 How it was counted: Satellites documents whose upload column is empty, which is why the per-year counts do not add up to the total, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:undated

Huawei, HiSilicon filed 2287 Satellites documents cited

2287 How it was counted: Satellites documents grouped by the source column, largest first; the column is the name the document spelled, so one company under two spellings counts twice and none was resolved to a parent, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:filer-huawei-hisilicon

Ericsson filed 2184 Satellites documents cited

2184 How it was counted: Satellites documents grouped by the source column, largest first; the column is the name the document spelled, so one company under two spellings counts twice and none was resolved to a parent, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:filer-ericsson

CATT filed 2076 Satellites documents

2076 How it was counted: Satellites documents grouped by the source column, largest first; the column is the name the document spelled, so one company under two spellings counts twice and none was resolved to a parent, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:filer-catt

Qualcomm Incorporated filed 1337 Satellites documents

1337 How it was counted: Satellites documents grouped by the source column, largest first; the column is the name the document spelled, so one company under two spellings counts twice and none was resolved to a parent, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:filer-qualcomm-incorporated

Samsung filed 1285 Satellites documents

1285 How it was counted: Satellites documents grouped by the source column, largest first; the column is the name the document spelled, so one company under two spellings counts twice and none was resolved to a parent, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:filer-samsung

Nokia, Nokia Shanghai Bell filed 1043 Satellites documents

1043 How it was counted: Satellites documents grouped by the source column, largest first; the column is the name the document spelled, so one company under two spellings counts twice and none was resolved to a parent, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:filer-nokia-nokia-shanghai-bell

OPPO filed 848 Satellites documents

848 How it was counted: Satellites documents grouped by the source column, largest first; the column is the name the document spelled, so one company under two spellings counts twice and none was resolved to a parent, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:filer-oppo

MediaTek Inc. filed 846 Satellites documents

846 How it was counted: Satellites documents grouped by the source column, largest first; the column is the name the document spelled, so one company under two spellings counts twice and none was resolved to a parent, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:filer-mediatek-inc

2664 different names appear as the writer of one of them cited

2664 How it was counted: distinct values of the source column over these documents, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:companies

102 specifications this work touches cited

102 How it was counted: catalogue rows for every specification named by at least 30 Satellites documents, and for every one whose own title says satellite or NTN and which at least one document or work item of this subject points at, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05 count:affected-specs

149 more specifications are named by fewer documents than the register keeps

149 How it was counted: specifications named by at least one and fewer than 30 Satellites documents and by no work item of this subject; left out because a handful of documents is as likely a filing mistake as a real link, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:thin-spec-links

3599 active 3GPP specifications altogether cited

3599 How it was counted: catalogue rows whose active column is yes, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05 count:all-active-specs

6568 documents name satellites or NTN in their title and carry no work item cited

6568 How it was counted: documents whose title contains "satellite", "non-terrestrial" or "NTN" and whose work item column is empty — every plenary approval document among them, and every proposal filed before a work item existed, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:unlabelled

5663 documents say satellite or GNSS and belong to other work cited

5663 How it was counted: documents whose title contains "satellite" or "GNSS" but neither "non-terrestrial" nor "NTN", and which carry some other work item — satellite navigation and positioning above all, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:other-satellite-work

Specification 102

TS 22.261 cited

Service requirements for the 5G system How it was counted: the catalogue row and every stored version of 22.261, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite and the upload day from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite, same day spec:22.261

TR 22.822

Study on using satellite access in 5G How it was counted: the catalogue row and every stored version of 22.822, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite and the upload day from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite, same day spec:22.822

TR 22.865

Study on satellite access - Phase 3 How it was counted: the catalogue row and every stored version of 22.865, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite and the upload day from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite, same day spec:22.865

TR 22.887

Feasibility Study on satellite access - Phase 4 How it was counted: the catalogue row and every stored version of 22.887, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite and the upload day from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite, same day spec:22.887

TS 23.041

Technical realization of Cell Broadcast Service (CBS) How it was counted: the catalogue row and every stored version of 23.041, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite and the upload day from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite, same day spec:23.041

TS 23.122

Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode How it was counted: the catalogue row and every stored version of 23.122, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite and the upload day from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite, same day spec:23.122

TS 23.228

IP Multimedia Subsystem (IMS); Stage 2 How it was counted: the catalogue row and every stored version of 23.228, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite and the upload day from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite, same day spec:23.228

TS 23.401

General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access How it was counted: the catalogue row and every stored version of 23.401, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite and the upload day from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite, same day spec:23.401

TS 23.434

Service Enabler Architecture Layer for Verticals (SEAL); Functional architecture and information flows How it was counted: the catalogue row and every stored version of 23.434, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite and the upload day from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite, same day spec:23.434

TS 23.501

System architecture for the 5G System (5GS) How it was counted: the catalogue row and every stored version of 23.501, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite and the upload day from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite, same day spec:23.501

TS 23.502

Procedures for the 5G System (5GS) How it was counted: the catalogue row and every stored version of 23.502, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite and the upload day from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite, same day spec:23.502

TS 23.503

Policy and charging control framework for the 5G System (5GS); Stage 2 How it was counted: the catalogue row and every stored version of 23.503, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite and the upload day from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite, same day spec:23.503

TS 23.558

Architecture for enabling Edge Applications How it was counted: the catalogue row and every stored version of 23.558, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite and the upload day from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite, same day spec:23.558

TS 23.682

Architecture enhancements to facilitate communications with packet data networks and applications How it was counted: the catalogue row and every stored version of 23.682, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite and the upload day from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite, same day spec:23.682

TR 23.700-01

Study on application enablement for Satellite access enabled 5G Services How it was counted: the catalogue row and every stored version of 23.700-01, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite and the upload day from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite, same day spec:23.700-01

TR 23.700-02

Study of application enablement for satellite access enabled 5G services Phase 4 How it was counted: the catalogue row and every stored version of 23.700-02, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite and the upload day from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite, same day spec:23.700-02

TR 23.700-19

Study on Integration of satellite components in the 5G architecture; Phase 4 How it was counted: the catalogue row and every stored version of 23.700-19, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite and the upload day from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite, same day spec:23.700-19

TR 23.700-27

Study on 5G System with Satellite Backhaul How it was counted: the catalogue row and every stored version of 23.700-27, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite and the upload day from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite, same day spec:23.700-27

TR 23.700-28

Study on Integration of satellite components in the 5G architecture; Phase 2 How it was counted: the catalogue row and every stored version of 23.700-28, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite and the upload day from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite, same day spec:23.700-28

TR 23.700-29

Study on integration of satellite components in the 5G architecture; Phase 3 How it was counted: the catalogue row and every stored version of 23.700-29, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite and the upload day from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite, same day spec:23.700-29

TR 23.737

Study on architecture aspects for using satellite access in 5G How it was counted: the catalogue row and every stored version of 23.737, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite and the upload day from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite, same day spec:23.737

TS 24.229

IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 How it was counted: the catalogue row and every stored version of 24.229, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite and the upload day from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite, same day spec:24.229

TS 24.301

Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 How it was counted: the catalogue row and every stored version of 24.301, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite and the upload day from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite, same day spec:24.301

TS 24.501

Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 How it was counted: the catalogue row and every stored version of 24.501, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite and the upload day from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite, same day spec:24.501

TS 24.546

Configuration management - Service Enabler Architecture Layer for Verticals (SEAL); Protocol specification How it was counted: the catalogue row and every stored version of 24.546, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite and the upload day from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite, same day spec:24.546

TS 24.548

Network Resource Management - Service Enabler Architecture Layer for Verticals (SEAL); Protocol specification How it was counted: the catalogue row and every stored version of 24.548, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite and the upload day from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite, same day spec:24.548

TR 24.821

Study on PLMN selection for satellite access How it was counted: the catalogue row and every stored version of 24.821, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite and the upload day from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite, same day spec:24.821

TR 26.940

Study on Ultra Low Bit rate Speech Codecs How it was counted: the catalogue row and every stored version of 26.940, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite and the upload day from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite, same day spec:26.940

TS 27.007

AT command set for User Equipment (UE) How it was counted: the catalogue row and every stored version of 27.007, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite and the upload day from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite, same day spec:27.007

TS 28.541

Management and orchestration; 5G Network Resource Model (NRM); Stage 2 and stage 3 How it was counted: the catalogue row and every stored version of 28.541, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite and the upload day from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite, same day spec:28.541

TR 28.808

Study on management and orchestration aspects of integrated satellite components in a 5G network How it was counted: the catalogue row and every stored version of 28.808, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite and the upload day from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite, same day spec:28.808

TR 28.841

Study on management aspects of Internet of Things (IoT) Non-Terrestrial Networks (NTN) enhancements How it was counted: the catalogue row and every stored version of 28.841, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite and the upload day from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite, same day spec:28.841

TR 28.844

Study on charging aspects of satellite in the 5G System (5GS) How it was counted: the catalogue row and every stored version of 28.844, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite and the upload day from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite, same day spec:28.844

TR 28.846

Study on charging aspects of satellite access phase 3 How it was counted: the catalogue row and every stored version of 28.846, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite and the upload day from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite, same day spec:28.846

TR 28.874

Study on Management Aspects of NTN Phase 2 How it was counted: the catalogue row and every stored version of 28.874, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite and the upload day from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite, same day spec:28.874

TR 28.894

Study on charging aspects of satellite access phase 4 How it was counted: the catalogue row and every stored version of 28.894, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite and the upload day from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite, same day spec:28.894

TS 29.512

5G System; Session Management Policy Control Service; Stage 3 How it was counted: the catalogue row and every stored version of 29.512, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite and the upload day from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite, same day spec:29.512

TS 29.514

5G System; Policy Authorization Service; Stage 3 How it was counted: the catalogue row and every stored version of 29.514, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite and the upload day from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite, same day spec:29.514

TS 29.549

Service Enabler Architecture Layer for Verticals (SEAL); Application Programming Interface (API) specification; Stage 3 How it was counted: the catalogue row and every stored version of 29.549, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite and the upload day from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite, same day spec:29.549

TS 29.571

5G System; Common Data Types for Service Based Interfaces; Stage 3 How it was counted: the catalogue row and every stored version of 29.571, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite and the upload day from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite, same day spec:29.571

TS 32.255

Telecommunication management; Charging management; 5G data connectivity domain charging; Stage 2 How it was counted: the catalogue row and every stored version of 32.255, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite and the upload day from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite, same day spec:32.255

TS 33.401

3GPP System Architecture Evolution (SAE); Security architecture How it was counted: the catalogue row and every stored version of 33.401, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite and the upload day from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite, same day spec:33.401

TR 33.700-28

Study on security aspects of satellite access How it was counted: the catalogue row and every stored version of 33.700-28, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite and the upload day from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite, same day spec:33.700-28

TR 33.700-29

Study on security aspects of 5G satellite access in the 5G architecture phase 3 How it was counted: the catalogue row and every stored version of 33.700-29, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite and the upload day from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite, same day spec:33.700-29

TR 33.700-30

Study on security aspects of satellite access in 5G phase 4 How it was counted: the catalogue row and every stored version of 33.700-30, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite and the upload day from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite, same day spec:33.700-30

TS 36.102

Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception for satellite access How it was counted: the catalogue row and every stored version of 36.102, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite and the upload day from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite, same day spec:36.102

TS 36.108 cited

Evolved Universal Terrestrial Radio Access (E-UTRA); Satellite Access Node radio transmission and reception How it was counted: the catalogue row and every stored version of 36.108, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite and the upload day from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite, same day spec:36.108

TS 36.133

Evolved Universal Terrestrial Radio Access (E-UTRA); Requirements for support of radio resource management How it was counted: the catalogue row and every stored version of 36.133, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite and the upload day from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite, same day spec:36.133

TS 36.181

Evolved Universal Terrestrial Radio Access (E-UTRA); Satellite Access Node conformance testing How it was counted: the catalogue row and every stored version of 36.181, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite and the upload day from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite, same day spec:36.181

TS 36.213

Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures How it was counted: the catalogue row and every stored version of 36.213, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite and the upload day from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite, same day spec:36.213

TS 36.300

Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 How it was counted: the catalogue row and every stored version of 36.300, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite and the upload day from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite, same day spec:36.300

TS 36.304

Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode How it was counted: the catalogue row and every stored version of 36.304, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite and the upload day from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite, same day spec:36.304

TS 36.306

Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio access capabilities How it was counted: the catalogue row and every stored version of 36.306, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite and the upload day from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite, same day spec:36.306

TS 36.307

Evolved Universal Terrestrial Radio Access (E-UTRA); Requirements on User Equipments (UEs) supporting a release-independent frequency band How it was counted: the catalogue row and every stored version of 36.307, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite and the upload day from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite, same day spec:36.307

TS 36.321

Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC) protocol specification How it was counted: the catalogue row and every stored version of 36.321, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite and the upload day from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite, same day spec:36.321

TS 36.331

Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification How it was counted: the catalogue row and every stored version of 36.331, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite and the upload day from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite, same day spec:36.331

TS 36.413

Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) How it was counted: the catalogue row and every stored version of 36.413, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite and the upload day from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite, same day spec:36.413

TS 36.423

Evolved Universal Terrestrial Radio Access Network (E-UTRAN); X2 Application Protocol (X2AP) How it was counted: the catalogue row and every stored version of 36.423, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite and the upload day from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite, same day spec:36.423

TS 36.508

Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Packet Core (EPC); Common test environments for User Equipment (UE) conformance testing How it was counted: the catalogue row and every stored version of 36.508, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite and the upload day from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite, same day spec:36.508

TS 36.521-2

Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) conformance specification; Radio transmission and reception; Part 2: Implementation Conformance Statement (ICS) How it was counted: the catalogue row and every stored version of 36.521-2, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite and the upload day from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite, same day spec:36.521-2

TS 36.521-3

Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) conformance specification; Radio transmission and reception; Part 3: Radio Resource Management (RRM) conformance testing How it was counted: the catalogue row and every stored version of 36.521-3, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite and the upload day from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite, same day spec:36.521-3

TS 36.521-4

Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) conformance specification; Radio transmission and reception; Part 4: Satellite access Radio Frequency (RF) and performance Conformance Testing How it was counted: the catalogue row and every stored version of 36.521-4, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite and the upload day from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite, same day spec:36.521-4

TS 36.523-1

Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Packet Core (EPC); User Equipment (UE) conformance specification; Part 1: Protocol conformance specification How it was counted: the catalogue row and every stored version of 36.523-1, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite and the upload day from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite, same day spec:36.523-1

TS 36.523-2

Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Packet Core (EPC); User Equipment (UE) conformance specification; Part 2: Implementation Conformance Statement (ICS) proforma specification How it was counted: the catalogue row and every stored version of 36.523-2, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite and the upload day from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite, same day spec:36.523-2

TS 36.523-3

Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Packet Core (EPC); User Equipment (UE) conformance specification; Part 3: Test suites How it was counted: the catalogue row and every stored version of 36.523-3, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite and the upload day from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite, same day spec:36.523-3

TR 36.763 cited

Study on Narrow-Band Internet of Things (NB-IoT) / enhanced Machine Type Communication (eMTC) support for Non-Terrestrial Networks (NTN) How it was counted: the catalogue row and every stored version of 36.763, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite and the upload day from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite, same day spec:36.763

TR 36.764

LTE IoT NTN operating bands How it was counted: the catalogue row and every stored version of 36.764, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite and the upload day from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite, same day spec:36.764

TR 36.811

Evolved Universal Terrestrial Radio Access (E-UTRA); Adding 2 GHz band LTE Frequency Division Duplex (FDD) (Band 23) for Ancillary Terrestrial Component (ATC) of Mobile Satellite Services (MSS) in North America How it was counted: the catalogue row and every stored version of 36.811, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite and the upload day from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite, same day spec:36.811

TR 36.903

Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Derivation of test tolerances for Radio Resource Management (RRM) conformance tests How it was counted: the catalogue row and every stored version of 36.903, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite and the upload day from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite, same day spec:36.903

TR 37.911

Study on self-evaluation towards the IMT-2020 submission of the 3GPP Satellite Radio Interface Technology How it was counted: the catalogue row and every stored version of 37.911, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite and the upload day from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite, same day spec:37.911

TS 38.101-5 cited

NR; User Equipment (UE) radio transmission and reception; Part 5: Satellite access Radio Frequency (RF) and performance requirements How it was counted: the catalogue row and every stored version of 38.101-5, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite and the upload day from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite, same day spec:38.101-5

TS 38.108 cited

NR; Satellite Access Node radio transmission and reception How it was counted: the catalogue row and every stored version of 38.108, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite and the upload day from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite, same day spec:38.108

TS 38.133

NR; Requirements for support of radio resource management How it was counted: the catalogue row and every stored version of 38.133, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite and the upload day from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite, same day spec:38.133

TS 38.181 cited

NR; Satellite Access Node conformance testing How it was counted: the catalogue row and every stored version of 38.181, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite and the upload day from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite, same day spec:38.181

TS 38.211

NR; Physical channels and modulation How it was counted: the catalogue row and every stored version of 38.211, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite and the upload day from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite, same day spec:38.211

TS 38.212

NR; Multiplexing and channel coding How it was counted: the catalogue row and every stored version of 38.212, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite and the upload day from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite, same day spec:38.212

TS 38.213

NR; Physical layer procedures for control How it was counted: the catalogue row and every stored version of 38.213, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite and the upload day from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite, same day spec:38.213

TS 38.214

NR; Physical layer procedures for data How it was counted: the catalogue row and every stored version of 38.214, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite and the upload day from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite, same day spec:38.214

TS 38.300

NR; NR and NG-RAN Overall description; Stage-2 How it was counted: the catalogue row and every stored version of 38.300, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite and the upload day from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite, same day spec:38.300

TS 38.304

NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state How it was counted: the catalogue row and every stored version of 38.304, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite and the upload day from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite, same day spec:38.304

TS 38.306

NR; User Equipment (UE) radio access capabilities How it was counted: the catalogue row and every stored version of 38.306, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite and the upload day from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite, same day spec:38.306

TS 38.307

NR; Requirements on User Equipments (UEs) supporting a release-independent frequency band How it was counted: the catalogue row and every stored version of 38.307, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite and the upload day from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite, same day spec:38.307

TS 38.321

NR; Medium Access Control (MAC) protocol specification How it was counted: the catalogue row and every stored version of 38.321, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite and the upload day from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite, same day spec:38.321

TS 38.331

NR; Radio Resource Control (RRC); Protocol specification How it was counted: the catalogue row and every stored version of 38.331, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite and the upload day from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite, same day spec:38.331

TS 38.413

NG-RAN; NG Application Protocol (NGAP) How it was counted: the catalogue row and every stored version of 38.413, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite and the upload day from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite, same day spec:38.413

TS 38.423

NG-RAN; Xn Application Protocol (XnAP) How it was counted: the catalogue row and every stored version of 38.423, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite and the upload day from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite, same day spec:38.423

TS 38.508-1

5GS; User Equipment (UE) conformance specification; Part 1: Common test environment How it was counted: the catalogue row and every stored version of 38.508-1, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite and the upload day from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite, same day spec:38.508-1

TS 38.508-2

5GS; User Equipment (UE) conformance specification; Part 2: Common Implementation Conformance Statement (ICS) proforma How it was counted: the catalogue row and every stored version of 38.508-2, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite and the upload day from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite, same day spec:38.508-2

TS 38.521-5

NR; User Equipment (UE) conformance specification; Radio transmission and reception; Part 5: Satellite access Radio Frequency (RF) and performance How it was counted: the catalogue row and every stored version of 38.521-5, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite and the upload day from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite, same day spec:38.521-5

TS 38.522

NR; User Equipment (UE) conformance specification; Applicability of radio transmission, radio reception and radio resource management test cases How it was counted: the catalogue row and every stored version of 38.522, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite and the upload day from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite, same day spec:38.522

TS 38.523-1

5GS; User Equipment (UE) conformance specification; Part 1: Protocol How it was counted: the catalogue row and every stored version of 38.523-1, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite and the upload day from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite, same day spec:38.523-1

TS 38.523-2

5GS; User Equipment (UE) conformance specification; Part 2: Applicability of protocol test cases How it was counted: the catalogue row and every stored version of 38.523-2, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite and the upload day from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite, same day spec:38.523-2

TS 38.523-3

5GS; User Equipment (UE) conformance specification; Part 3: Protocol Test Suites How it was counted: the catalogue row and every stored version of 38.523-3, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite and the upload day from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite, same day spec:38.523-3

TS 38.533

NR; User Equipment (UE) conformance specification; Radio Resource Management (RRM) How it was counted: the catalogue row and every stored version of 38.533, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite and the upload day from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite, same day spec:38.533

TR 38.741

Non-Terrestrial Networks (NTN) L-/S-band for NR How it was counted: the catalogue row and every stored version of 38.741, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite and the upload day from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite, same day spec:38.741

TR 38.742

Study on GNSS (Global Navigation Satellite System) resilient NR-NTN (Non-Terrestrial Networks) operation How it was counted: the catalogue row and every stored version of 38.742, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite and the upload day from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite, same day spec:38.742

TR 38.811 cited

Study on New Radio (NR) to support non-terrestrial networks How it was counted: the catalogue row and every stored version of 38.811, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite and the upload day from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite, same day spec:38.811

TR 38.821 cited

Solutions for NR to support Non-Terrestrial Networks (NTN) How it was counted: the catalogue row and every stored version of 38.821, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite and the upload day from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite, same day spec:38.821

TR 38.863

Non-terrestrial networks (NTN) related RF and co-existence aspects How it was counted: the catalogue row and every stored version of 38.863, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite and the upload day from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite, same day spec:38.863

TR 38.882

Study on requirements and use cases for network verified UE location for Non-Terrestrial-Networks (NTN) in NR How it was counted: the catalogue row and every stored version of 38.882, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite and the upload day from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite, same day spec:38.882

TR 38.903

NR; Derivation of test tolerances and measurement uncertainty for User Equipment (UE) conformance test cases How it was counted: the catalogue row and every stored version of 38.903, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite and the upload day from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite, same day spec:38.903

TR 38.905

NR; Derivation of test points for radio transmission and reception User Equipment (UE) conformance test cases How it was counted: the catalogue row and every stored version of 38.905, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the document counts come from /var/www/whatthespec.net/data/database/api/api.sqlite and the upload day from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite, same day spec:38.905

Quoted wording 99

the scope of 22.865

The present document describes use cases and aspects related to enhancements of the 5G system over satellite, including: Store and Forward (S&F) Satellite operation for delay-tolerant communication service How it was counted: clause 1 of the parsed text at /var/www/whatthespec.net/data/friendlyspec/json/22865/19.2.0/, read 2026-08-05 quote:scope:22.865

the scope of 22.887 cited

The present document describes use cases and aspects related to enhancements of the 5G system over satellite, including: multi-orbit satellite access for multiple services How it was counted: clause 1 of the parsed text at /var/www/whatthespec.net/data/friendlyspec/json/22887/20.0.0/, read 2026-08-05 quote:scope:22.887

the scope of 23.700-01

The present document is a technical report capturing the study on application enablement for Satellite access enabled 5G Services over 3GPP networks. The aspects of the study include identifying architecture requirements, supporting architecture for satellite access enabled 3GPP services and application enablers (either by defining new functional model or by enhancing existing functional model), and corresponding solutions. How it was counted: clause 1 of the parsed text at /var/www/whatthespec.net/data/friendlyspec/json/23700-01/19.0.0/, read 2026-08-05 quote:scope:23.700-01

the scope of 23.700-02

The present document is a technical report capturing the study on enhancement to application enablement for Satellite access enabled 5G Services over 3GPP networks. The aspects of the study include identifying architecture requirements, supporting architecture for satellite access enabled 3GPP services and application enablers, and corresponding solutions. How it was counted: clause 1 of the parsed text at /var/www/whatthespec.net/data/friendlyspec/json/23700-02/1.1.0/, read 2026-08-05 quote:scope:23.700-02

the scope of 23.700-19

The scope of this Technical Report is to study the following aspects: Support of IMS voice call over NB-IoT NTN via GEO satellite connecting to EPC. How it was counted: clause 1 of the parsed text at /var/www/whatthespec.net/data/friendlyspec/json/23700-19/20.0.0/, read 2026-08-05 quote:scope:23.700-19

the scope of 23.700-29

The scope of this Technical Report is to study the following aspects of 5GS/EPS integrating of satellite component in Release 19, including: Regenerative payload generic architecture: How it was counted: clause 1 of the parsed text at /var/www/whatthespec.net/data/friendlyspec/json/23700-29/19.0.0/, read 2026-08-05 quote:scope:23.700-29

the scope of 28.846

The present document studies on charging aspects of satellite access Phase 3 based on the TS 22.261 [2] and TR 23.700-29 [3]: This study item is to investigate the following aspects of the satellite access: How it was counted: clause 1 of the parsed text at /var/www/whatthespec.net/data/friendlyspec/json/28846/19.1.0/, read 2026-08-05 quote:scope:28.846

the scope of 28.874

The present document studies the management aspects of NTN in R19. It mainly investigates use cases, potential requirements and potential solutions of NTN management. How it was counted: clause 1 of the parsed text at /var/www/whatthespec.net/data/friendlyspec/json/28874/19.1.0/, read 2026-08-05 quote:scope:28.874

the scope of 28.894

The present document studies on charging aspects of satellite access Phase 4 based on the TS 22.261[2] and based on ongoing study with TR 23.700-19 [3]: This study item is to investigate charging for IMS voice call over GEO via NB-IoT NTN connecting to EPC and charging for UE-satellite-UE communication related to services other than IMS via NGSO satellite access. How it was counted: clause 1 of the parsed text at /var/www/whatthespec.net/data/friendlyspec/json/28894/0.3.0/, read 2026-08-05 quote:scope:28.894

the scope of 33.700-29

The present document studies the security and privacy aspects of 5G satellite access phase 3. It is comprised of the following parts: Identify and study the security and privacy key issues of the regenerative payload generic architecture in 5GS/EPS. How it was counted: clause 1 of the parsed text at /var/www/whatthespec.net/data/friendlyspec/json/33700-29/19.1.0/, read 2026-08-05 quote:scope:33.700-29

the scope of 33.700-30

The present document studies the security mechanisms that permit an authenticated UE to exchange NAS messages with multiple satellites without performing UE authentication or key negotiation (NAS SMC) between the UE and satellites in split-MME architecture for Store and Forward Satellite operation. How it was counted: clause 1 of the parsed text at /var/www/whatthespec.net/data/friendlyspec/json/33700-30/20.0.1/, read 2026-08-05 quote:scope:33.700-30

the scope of 36.102

The present document establishes the minimum RF characteristics and minimum performance requirements for E-UTRA User Equipment (UE) operating satellite access. How it was counted: clause 1 of the parsed text at /var/www/whatthespec.net/data/friendlyspec/json/36102/19.4.0/, read 2026-08-05 quote:scope:36.102

the scope of 36.108

The present document establishes the minimum RF characteristics and minimum performance requirements of Satellite Access Node (SAN) supporting: standalone NB-IoT operation, or How it was counted: clause 1 of the parsed text at /var/www/whatthespec.net/data/friendlyspec/json/36108/19.4.0/, read 2026-08-05 quote:scope:36.108

the scope of 36.181

The present document specifies the Radio Frequency (RF) test methods and conformance requirements for Satellite Access Node (SAN) type 1-H and SAN type 1-O, supporting: standalone NB-IoT operation, or How it was counted: clause 1 of the parsed text at /var/www/whatthespec.net/data/friendlyspec/json/36181/19.4.0/, read 2026-08-05 quote:scope:36.181

the scope of 36.521-4

The present document specifies the measurement procedures for the conformance test of E-UTRA User Equipment (UE) supporting satellite access operation that contains RF and Performance requirements. Conformance test for the support of RRM (Radio Resource Management) are specified in TS 36.521-3 [16]. How it was counted: clause 1 of the parsed text at /var/www/whatthespec.net/data/friendlyspec/json/36521-4/19.2.0/, read 2026-08-05 quote:scope:36.521-4

the scope of 36.764

The present document is a technical report for LTE IoT NTN operating bands. How it was counted: clause 1 of the parsed text at /var/www/whatthespec.net/data/friendlyspec/json/36764/19.1.0/, read 2026-08-05 quote:scope:36.764

the scope of 37.911

The present document reports on the self-evaluation results for meeting the requirements defined by ITU in Report ITU-R M.2514 [2]. How it was counted: clause 1 of the parsed text at /var/www/whatthespec.net/data/friendlyspec/json/37911/19.0.0/, read 2026-08-05 quote:scope:37.911

the scope of 38.101-5 cited

The present document establishes the minimum RF and performance requirements for NR User Equipment (UE) supporting satellite access operation. How it was counted: clause 1 of the parsed text at /var/www/whatthespec.net/data/friendlyspec/json/38101-5/20.0.0/, read 2026-08-05 quote:scope:38.101-5

the scope of 38.108 cited

The present document establishes the minimum RF characteristics and minimum performance requirements of NR and NB-IoT operation in NTN NR in-band Satellite Access Node (SAN). How it was counted: clause 1 of the parsed text at /var/www/whatthespec.net/data/friendlyspec/json/38108/19.4.0/, read 2026-08-05 quote:scope:38.108

the scope of 38.181 cited

The present document specifies the Radio Frequency (RF) test methods and conformance requirements for NR Satellite Access Node (SAN) type 1-H, SAN type 1-O and SAN type 2-O. The document also specifies the RF test methods and conformance requirements for NB-IoT operation in NTN NR in-band SAN type 1-H and SAN type 1-O. How it was counted: clause 1 of the parsed text at /var/www/whatthespec.net/data/friendlyspec/json/38181/19.4.0/, read 2026-08-05 quote:scope:38.181

the scope of 38.521-5

The present document specifies the measurement procedures for the conformance test of the NR User Equipment (UE) supporting satellite access operation that contains RF and Performance requirements. How it was counted: clause 1 of the parsed text at /var/www/whatthespec.net/data/friendlyspec/json/38521-5/19.2.0/, read 2026-08-05 quote:scope:38.521-5

the scope of 38.741

The present document is a technical report for the work item of the NTN L-S-band. How it was counted: clause 1 of the parsed text at /var/www/whatthespec.net/data/friendlyspec/json/38741/19.1.0/, read 2026-08-05 quote:scope:38.741

the scope of 38.742

This technical report addresses the study of GNSS (Global Navigation Satellite System) resilient operation in NR-NTN (Non-Terrestrial Networks), targeting Release 20 enhancements. The objective is to evaluate and define solutions to ensure NR-NTN functionality in scenarios where GNSS is temporarily unavailable while maintaining service. How it was counted: clause 1 of the parsed text at /var/www/whatthespec.net/data/friendlyspec/json/38742/20.0.0/, read 2026-08-05 quote:scope:38.742

the scope of 38.863

The present document covers the RF and co-existence aspects of the work item “Solutions for NR to support non-terrestrial networks (NTN)” [2] How it was counted: clause 1 of the parsed text at /var/www/whatthespec.net/data/friendlyspec/json/38863/19.4.0/, read 2026-08-05 quote:scope:38.863

"satellite" as 38.108 defines it cited

satellite: A space-borne vehicle embarking a transparent payload, or a regenerative payload telecommunication transmitter, placed into Low-Earth Orbit (LEO) or Geostationary Earth Orbit (GEO). How it was counted: clause 3.1 of the parsed text at /var/www/whatthespec.net/data/friendlyspec/json/38108/19.4.0/, read 2026-08-05 quote:term:satellite

"Satellite Access Node" as 38.108 defines it cited

Satellite Access Node: node providing NR user plane and control plane protocol terminations towards NTN satellite capable UE, and connected via the NG interface to the 5GC. It encompasses a transparent payload on board a NTN platform, with satellite-gateway and gNB functions. How it was counted: clause 3.1 of the parsed text at /var/www/whatthespec.net/data/friendlyspec/json/38108/19.4.0/, read 2026-08-05 quote:term:satellite-access-node

"non-terrestrial networks" as 38.108 defines it cited

non-terrestrial networks: Networks, or segments of networks, using an airborne or space-borne vehicle to embark a transmission equipment relay node or SAN. How it was counted: clause 3.1 of the parsed text at /var/www/whatthespec.net/data/friendlyspec/json/38108/19.4.0/, read 2026-08-05 quote:term:non-terrestrial-networks

"feeder link" as 38.108 defines it cited

feeder link: Wireless link between satellite-gateway and satellite. How it was counted: clause 3.1 of the parsed text at /var/www/whatthespec.net/data/friendlyspec/json/38108/19.4.0/, read 2026-08-05 quote:term:feeder-link

"satellite-gateway" as 38.108 defines it cited

satellite-gateway: An earth station or gateway is located at the surface of Earth, and providing sufficient RF power and RF sensitivity for accessing to the satellite. How it was counted: clause 3.1 of the parsed text at /var/www/whatthespec.net/data/friendlyspec/json/38108/19.4.0/, read 2026-08-05 quote:term:satellite-gateway

"Geostationary Earth Orbit" as 38.108 defines it cited

Geostationary Earth Orbit: Circular orbit at 35,786 km above the Earth's equator and following the direction of the Earth's rotation. An object in such an orbit has an orbital period equal to the Earth's rotational period and thus appears motionless, at a fixed position in the sky, to ground observers. How it was counted: clause 3.1 of the parsed text at /var/www/whatthespec.net/data/friendlyspec/json/38108/19.4.0/, read 2026-08-05 quote:term:geostationary-earth-orbit

"Service link" as 38.863 defines it cited

Service link: Radio link between satellite and UE How it was counted: clause 3.1 of the parsed text at /var/www/whatthespec.net/data/friendlyspec/json/38863/19.4.0/, read 2026-08-05 quote:term:service-link

"Transparent payload" as 38.863 defines it cited

Transparent payload: Payload that changes the frequency carrier of the UL/DL RF signal, filters and amplifies it before transmitting it on the DL/UL, respectively. How it was counted: clause 3.1 of the parsed text at /var/www/whatthespec.net/data/friendlyspec/json/38863/19.4.0/, read 2026-08-05 quote:term:transparent-payload

"Regenerative payload" as 38.742 defines it cited

Regenerative payload: payload that transforms and amplifies an uplink RF signal before transmitting it on the downlink. The transformation of the signal refers to digital processing that may include demodulation, decoding, re-encoding, re-modulation and/or filtering. How it was counted: clause 3.1 of the parsed text at /var/www/whatthespec.net/data/friendlyspec/json/38742/20.0.0/, read 2026-08-05 quote:term:regenerative-payload

"Satellite beam" as 38.742 defines it

Satellite beam: A beam generated by an antenna on-board a satellite. How it was counted: clause 3.1 of the parsed text at /var/www/whatthespec.net/data/friendlyspec/json/38742/20.0.0/, read 2026-08-05 quote:term:satellite-beam

"satellite access" as 22.887 defines it cited

satellite access: direct connectivity between the UE and the satellite. How it was counted: clause 3.1 of the parsed text at /var/www/whatthespec.net/data/friendlyspec/json/22887/20.0.0/, read 2026-08-05 quote:term:satellite-access

"Very Small Aperture Terminal (VSAT)" as 22.887 defines it

Very Small Aperture Terminal (VSAT): is a small-sized earth station used to transmit and receive data, voice and video over a satellite communication network, excluding broadcast television How it was counted: clause 3.1 of the parsed text at /var/www/whatthespec.net/data/friendlyspec/json/22887/20.0.0/, read 2026-08-05 quote:term:very-small-aperture-terminal-vsat

"Resilient Notification" as 22.887 defines it

Resilient Notification: in the context of this study, it refers to a highly reliable mechanism that delivers notifications directly to user devices, such as smartphones, when in poor conditions in satellite access. How it was counted: clause 3.1 of the parsed text at /var/www/whatthespec.net/data/friendlyspec/json/22887/20.0.0/, read 2026-08-05 quote:term:resilient-notification

"Serving satellite" as 23.700-19 defines it

Serving satellite: a satellite providing the satellite access to a UE (e.g. providing the serving cell(s)). Depending on the orbit, the serving satellite is covering a given geographic area for a limited period of time. How it was counted: clause 3.1 of the parsed text at /var/www/whatthespec.net/data/friendlyspec/json/23700-19/20.0.0/, read 2026-08-05 quote:term:serving-satellite

"UE-Satellite-UE Communication" as 23.700-19 defines it

UE-Satellite-UE Communication: refers to a communication between UEs under the coverage of one or more serving satellites, using satellite access without the user traffic transiting through the ground segment. How it was counted: clause 3.1 of the parsed text at /var/www/whatthespec.net/data/friendlyspec/json/23700-19/20.0.0/, read 2026-08-05 quote:term:ue-satellite-ue-communication

"NTN Gateway" as 23.700-19 defines it

NTN Gateway: an earth station located at the surface of the earth, providing connectivity to the NTN payload using the feeder link. An NTN Gateway is a TNL node. How it was counted: clause 3.1 of the parsed text at /var/www/whatthespec.net/data/friendlyspec/json/23700-19/20.0.0/, read 2026-08-05 quote:term:ntn-gateway

"NTN" as 38.108 spells it out cited

NTN Non-Terrestrial Network How it was counted: clause 3.3 of the parsed text at /var/www/whatthespec.net/data/friendlyspec/json/38108/19.4.0/, read 2026-08-05 quote:abbr:ntn

"SAN" as 38.108 spells it out cited

SAN Satellite Access Node How it was counted: clause 3.3 of the parsed text at /var/www/whatthespec.net/data/friendlyspec/json/38108/19.4.0/, read 2026-08-05 quote:abbr:san

"GEO" as 38.108 spells it out cited

GEO Geostationary Earth Orbiting How it was counted: clause 3.3 of the parsed text at /var/www/whatthespec.net/data/friendlyspec/json/38108/19.4.0/, read 2026-08-05 quote:abbr:geo

"LEO" as 38.108 spells it out cited

LEO Low Earth Orbiting How it was counted: clause 3.3 of the parsed text at /var/www/whatthespec.net/data/friendlyspec/json/38108/19.4.0/, read 2026-08-05 quote:abbr:leo

the objective of NR_NTN_solutions-Core

The work item aims to specify the enhancements identified for NR NTN (non-terrestrial networks) especially LEO and GEO with implicit compatibility to support HAPS (high altitude platform station) and ATG (air to ground) scenarios according to the following principles: FDD is assumed for core specification work for NR-NTN. How it was counted: section 4 of the work item description /var/www/whatthespec.net/data/data/wis/860146/RP-221169_WID NR-NTN_for Rel-17 v6.3.md, read 2026-08-05 quote:objective:NR_NTN_solutions-Core

why NR_NTN_solutions-Core was proposed

Non-terrestrial networks refer to networks, or segments of networks, using an airborne or spaceborne vehicle for transmission: Spaceborne vehicles: Satellites (including Low Earth Orbiting (LEO) satellites, Medium Earth Orbiting (MEO) satellites, Geostationary Earth Orbiting (GEO) satellites as well as Highly Elliptical Orbiting (HEO) satellites) How it was counted: section 3 of the work item description /var/www/whatthespec.net/data/data/wis/860146/RP-221169_WID NR-NTN_for Rel-17 v6.3.md, read 2026-08-05 quote:why:NR_NTN_solutions-Core

the objective of NR_NTN_enh-Core

The work item aims at specifying enhancements for NG-RAN based NTN (Non-Terrestrial Networks) according to the following assumptions with implicit compatibility to support HAPS (High Altitude Platform Station) and ATG (Air To Ground) scenarios: GSO (Geo Synchronous Orbit) and NGSO (Non Geo Synchronous Orbit). NGSO includes Low Earth Orbit (LEO) and Medium Earth Orbit (MEO). How it was counted: section 4 of the work item description /var/www/whatthespec.net/data/data/wis/941106/RP-232669 R18 WID NR_NTN_enh_v19.md, read 2026-08-05 quote:objective:NR_NTN_enh-Core

why NR_NTN_enh-Core was proposed

In Release 17, a work item was carried out to define solutions enabling New Radio and NG-RAN to support Non-Terrestrial Networks (NTN): Transparent payload based GSO and NGSO network scenarios addressing at least 3GPP power class 3 UE with GNSS capability in both Earth fixed and/or moving cell configurations How it was counted: section 3 of the work item description /var/www/whatthespec.net/data/data/wis/941106/RP-232669 R18 WID NR_NTN_enh_v19.md, read 2026-08-05 quote:why:NR_NTN_enh-Core

the objective of NR_NTN_Ph3-Core

The work item aims at specifying further enhancements for NG-RAN based NTN (Non-Terrestrial Networks) with the following assumptions: GSO (Geo Synchronous Orbit) and NGSO (Non-Geo Synchronous Orbit). NGSO includes Low Earth Orbit (LEO) and Medium Earth Orbit (MEO). How it was counted: section 4 of the work item description /var/www/whatthespec.net/data/data/wis/1021097/RP-251954 was 243300 Rel-19 WID NR NTN phase 3_v12.md, read 2026-08-05 quote:objective:NR_NTN_Ph3-Core

why NR_NTN_Ph3-Core was proposed

In Release 17, a work item was carried out to define solutions enabling New Radio and NG-RAN to support Non-Terrestrial Networks (NTN). Then, Release 18 introduced enhancements for NR NTN. How it was counted: section 3 of the work item description /var/www/whatthespec.net/data/data/wis/1021097/RP-251954 was 243300 Rel-19 WID NR NTN phase 3_v12.md, read 2026-08-05 quote:why:NR_NTN_Ph3-Core

the objective of IoT_NTN_Ph3-Core

The aim of this WI is enhancement of IoT-NTN with the following objectives: Support of Store&Forward (S&F) satellite operation with full eNB as regenerative payload, therefore: How it was counted: section 4 of the work item description /var/www/whatthespec.net/data/data/wis/1021096/RP-252504 WID Rev R19 IOT-NTN cl.md, read 2026-08-05 quote:objective:IoT_NTN_Ph3-Core

why IoT_NTN_Ph3-Core was proposed cited

IoT-NTN has been specified in 3GPP RAN Rel-17, since then been optimised in Rel-18 and commercial deployment are ongoing at the moment. Based on real deployment or deployment plans further evolution of IoT-NTN is needed. How it was counted: section 3 of the work item description /var/www/whatthespec.net/data/data/wis/1021096/RP-252504 WID Rev R19 IOT-NTN cl.md, read 2026-08-05 quote:why:IoT_NTN_Ph3-Core

the objective of IoT_NTN_enh-Core

The work item aims to specify further enhancements for E-UTRA (LTE-RAN) based NTN (non-terrestrial networks) according to the following assumptions: GEO and NGSO (LEO and MEO). How it was counted: section 4 of the work item description /var/www/whatthespec.net/data/data/wis/940104/RP-241351 rev WID_R18_IoT_NTN_enh_cl.md, read 2026-08-05 quote:objective:IoT_NTN_enh-Core

why IoT_NTN_enh-Core was proposed

In Release 17, a work item is carried out to enable NB-IoT and eMTC to support Non-Terrestrial Networks (NTN) under the following assumptions: Transparent payload based GEO and NGSO network scenarios addressing at least 3GPP power class 3 UE with GNSS capability in both Earth fixed &/or moving cell configurations. How it was counted: section 3 of the work item description /var/www/whatthespec.net/data/data/wis/940104/RP-241351 rev WID_R18_IoT_NTN_enh_cl.md, read 2026-08-05 quote:why:IoT_NTN_enh-Core

the objective of NR_NTN_solutions_plus_CT-UEConTest

The objective of this WI is to enable UE conformance testing for the corresponding Rel17 NR NTN solutions WI which includes the following areas: Protocol test cases for NR NTN solutions How it was counted: section 4 of the work item description /var/www/whatthespec.net/data/data/wis/960074/RP-251228_revised WID_NR_NTN_Solutions.md, read 2026-08-05 quote:objective:NR_NTN_solutions_plus_CT-UEConTest

the objective of 5GSAT_ARCH-CT

Study phase (CT1 only): The objective of the study phase is to study the issues and propose solutions related to PLMN selection for satellite access as mandated by SA1 requirements. The issues to be studied may include: How it was counted: section 4 of the work item description /var/www/whatthespec.net/data/data/wis/911030/CP-210149-cl.md, read 2026-08-05 quote:objective:5GSAT_ARCH-CT

why 5GSAT_ARCH-CT was proposed

SA1 has introduced the requirements for the integration of satellite access into 5G system in TS 22.261. SA2 has concluded the study item on the architecture for satellite access and documented the issues and conclusions in TR 23.737. How it was counted: section 3 of the work item description /var/www/whatthespec.net/data/data/wis/911030/CP-210149-cl.md, read 2026-08-05 quote:why:5GSAT_ARCH-CT

the objective of 5GSAT_Ph3_ARCH

The objective of this work is to specify the CT aspects of integration of satellite components in the 5G architecture Phase 3 in order to enhance the CT WGs specifications based on the stage-2 requirements. Normative work to be developed by SA WGs and RAN WGs which may impact CT WGs will be considered as soon as those are available. How it was counted: section 4 of the work item description /var/www/whatthespec.net/data/data/wis/1050019/CP-250134.md, read 2026-08-05 quote:objective:5GSAT_Ph3_ARCH

why 5GSAT_Ph3_ARCH was proposed

Integration of satellite components in the 5G architecture Phase 3 is a Rel-19 SA WGs work item which impacts the CT WGs. The SA2 WG has studied Key Issue 1 “Support of Regenerative-based satellite access”, Key Issue 2 “Support of Store and Forward Satellite operation” and Key Issue 3 “Support of UE-satellite-UE communication” in Study on Integration of satellite components in the 5G architecture Phase III (unique ID 1010033) with results and conclusions documented in TR 23.700-29 which also provides guidance on required normative work In SA#104 in June 2024, SA agreed on a normative Rel-19 WID on integration of satellite components in the 5G architecture Phase 3 (), which includes the conclusions for Key Issue 2 "Support of Store and Forward satellite operation" and Key Issue 3 "Support of UE-Satellite-UE communication". How it was counted: section 3 of the work item description /var/www/whatthespec.net/data/data/wis/1050019/CP-250134.md, read 2026-08-05 quote:why:5GSAT_Ph3_ARCH

the objective of 5GSAT_Ph2

The objective of this work item is to specify architectural enhancements of 5G System (5GS) and Evolved Packet System(EPS) to support satellite discontinuous coverage as per conclusions reached within TR 23.700-28 (clause 8), in order to provide solutions on identified key issues in TR 23.700-28 (clause 5). Conclusions reached within TR 23.700-28 (clause 8) on the following aspects: How it was counted: section 4 of the work item description /var/www/whatthespec.net/data/data/wis/989998/SP-230109_clean_S2-2303910_WID_5GSAT_Ph2.md, read 2026-08-05 quote:objective:5GSAT_Ph2

why 5GSAT_Ph2 was proposed

This work item aims at specifying system enhancements to support satellite discontinuous coverage. The related solutions have been documented in the TR 23.700-28. How it was counted: section 3 of the work item description /var/www/whatthespec.net/data/data/wis/989998/SP-230109_clean_S2-2303910_WID_5GSAT_Ph2.md, read 2026-08-05 quote:why:5GSAT_Ph2

the objective of FS_NR_NTN_solutions

The objectives for this study item are, based on the outcomes of the TR 38.811, to study a set of necessary features/adaptations enabling the operation of NR protocol in non-terrestrial networks for 3GPP Release 16 with a priority on satellite access. UAS (including HAPS) based access could be considered as a special case of non-terrestrial access with lower delay/Doppler value and variation rate. How it was counted: section 4 of the work item description /var/www/whatthespec.net/data/data/wis/800099/RP-190710_SID NR-NTN solutions_v61.md, read 2026-08-05 quote:objective:FS_NR_NTN_solutions

the objective of LTE_NBIOT_eMTC_NTN cited

The objective of this Work Item is to specify support of NB-IoT and eMTC over NTN. Work on both NB-IoT and eMTC will start in August 2021 meetings. How it was counted: section 4 of the work item description /var/www/whatthespec.net/data/data/wis/920069/RP-211601 was RP-211573 1534 1457 Rel-17 WID-IoT NTN.md, read 2026-08-05 quote:objective:LTE_NBIOT_eMTC_NTN

why LTE_NBIOT_eMTC_NTN was proposed cited

IoT operation is critical in remote areas with low/no cellular connectivity for many different industries, including e.g.: Transportation (maritime, road, rail, air) & logistics How it was counted: section 3 of the work item description /var/www/whatthespec.net/data/data/wis/920069/RP-211601 was RP-211573 1534 1457 Rel-17 WID-IoT NTN.md, read 2026-08-05 quote:why:LTE_NBIOT_eMTC_NTN

the objective of FS_5GSAT_Ph4_ARC

The study items below aim at investigating on further 3GPP core network functions enhancements to support satellite access with the following work tasks: WT-1: IMS voice call over GEO via NB-IoT NTN connecting to EPC How it was counted: section 4 of the work item description /var/www/whatthespec.net/data/data/wis/1070011/SP-250787_was_766_was_SP-250400_Revised SID-5GSAT_ARC Phase 4-cl.md, read 2026-08-05 quote:objective:FS_5GSAT_Ph4_ARC

why FS_5GSAT_Ph4_ARC was proposed

Integration of satellite components into 5GS has been studied in Rel 16, Rel 17, Rel 18 and Rel-19. Now SA1 is developing TR 22.887 to capture a set of new use cases and potential service requirements: How it was counted: section 3 of the work item description /var/www/whatthespec.net/data/data/wis/1070011/SP-250787_was_766_was_SP-250400_Revised SID-5GSAT_ARC Phase 4-cl.md, read 2026-08-05 quote:why:FS_5GSAT_Ph4_ARC

the objective of LTE_NBIOT_eMTC_NTN_req-UEConTest

The objective of this work item is to enable UE RF/RRM/Demod conformance testing for Rel-18 NB-IoT/eMTC core & performance requirements for NTN. As per the Core WID (Rel-18 NB-IoT/eMTC core & performance requirements for NTN), all core and performance requirements specified as part of the Core WI shall be Release-independent from Rel-17. How it was counted: section 4 of the work item description /var/www/whatthespec.net/data/data/wis/981034/RP-240147-cl.md, read 2026-08-05 quote:objective:LTE_NBIOT_eMTC_NTN_req-UEConTest

the objective of FS_LTE_NBIOT_eMTC_NTN

This Study will evaluate and confirm solutions to address the minimum necessary specifications for NB-IoT and eMTC according to the following objectives. The first objective of this Study is to identify scenarios applicable to NB-IoT/eMTC [RAN1, RAN2], including: How it was counted: section 4 of the work item description /var/www/whatthespec.net/data/data/wis/860033/RP-202689-SID-NBIoT NTN.md, read 2026-08-05 quote:objective:FS_LTE_NBIOT_eMTC_NTN

the objective of NR_IoT_NTN_req_test_enh-Core

The objectives of core part for enhanced requirements and test methodology for NR and IoT NTN include: High power UE (HPUE) for NTN How it was counted: section 4 of the work item description /var/www/whatthespec.net/data/data/wis/1031086/RP-252076 Revised WID on NR_IoT_NTN_req_test_enh_cl.md, read 2026-08-05 quote:objective:NR_IoT_NTN_req_test_enh-Core

why NR_IoT_NTN_req_test_enh-Core was proposed

This work item targets at the enhanced requirements and test methodology for NR-NTN (Non-Terrestrial Networks) and IoT-NTN (NB-IoT and eMTC based NTN) in NR-NTN frequency range 1 (FR1-NTN) and frequency range for LTE bands. The following working areas are included. How it was counted: section 3 of the work item description /var/www/whatthespec.net/data/data/wis/1031086/RP-252076 Revised WID on NR_IoT_NTN_req_test_enh_cl.md, read 2026-08-05 quote:why:NR_IoT_NTN_req_test_enh-Core

the objective of 5GSAT_Ph3-ARC

The objective of this work item is to produce normative specifications fulfilling the results of the feasibility study as documented in the conclusions section of TR 23.700-29 v 1.0.0 for each of the three key issues investigated. For Key Issue 2 (WT2) "Support of Store and Forward satellite operation" How it was counted: section 4 of the work item description /var/www/whatthespec.net/data/data/wis/1040027/SP-241386_SP-241289_SP-240986_cl_S2-2408685.md, read 2026-08-05 quote:objective:5GSAT_Ph3-ARC

why 5GSAT_Ph3-ARC was proposed

Integration of satellite components into EPS and 5GS has been studied in Rel 16, Rel 17 and 18. As part of Rel-19, SA1 developed a TR 22.865 that captures a set of use cases and potential service requirements related to the 5G system with satellite access considering new capabilities: How it was counted: section 3 of the work item description /var/www/whatthespec.net/data/data/wis/1040027/SP-241386_SP-241289_SP-240986_cl_S2-2408685.md, read 2026-08-05 quote:why:5GSAT_Ph3-ARC

the objective of IoT_SAT_ARCH_EPS

This Work Item covers the following objectives to introduce minimum essential functionality to support NB-IoT and eMTC over Non-Terrestrial Networks in EPS using 5GSAT_ARCH solutions as baseline: Functionality to support NTN for NB-IoT and eMTC for transparent payload based scenarios, including: How it was counted: section 4 of the work item description /var/www/whatthespec.net/data/data/wis/930019/SP-211306_clean_S2-2109198cl was S2-2108825r03 was S2-2107580 was SP-211124 R17 WID IoT NTN EPS.md, read 2026-08-05 quote:objective:IoT_SAT_ARCH_EPS

the objective of 5GSAT_ARCH

The main objective of the work item is to produce normative specifications based on the conclusions identified in TR 23.737 v1.3.0 (clause 8) under the following key issues: Mobility Management with large coverage areas. How it was counted: section 4 of the work item description /var/www/whatthespec.net/data/data/wis/890034/SP-191335 was SP-191101_New WID 5GSAT_ARCH_S2-1912749.md, read 2026-08-05 quote:objective:5GSAT_ARCH

why 5GSAT_ARCH was proposed

TSG SA has approved an allocated time units for the completion of the FS_5GSAT_ARCH Work Item in the Release 17 time frame. The Study Item identified a number of impacts on the Core Network and associated procedures, and SA WG2 should implement changes in their TSs to support the integration of satellite components in the 5G system architecture. How it was counted: section 3 of the work item description /var/www/whatthespec.net/data/data/wis/890034/SP-191335 was SP-191101_New WID 5GSAT_ARCH_S2-1912749.md, read 2026-08-05 quote:why:5GSAT_ARCH

the objective of FS_5GSAT_Ph3_ARCH

The study aims at investigating further 3GPP core network function enhancements to support satellite with the following architectural assumptions: Inter Satellite Link capability by default supported as a transport link (not in the scope of 3GPP standards to specify). How it was counted: section 4 of the work item description /var/www/whatthespec.net/data/data/wis/1010033/SP-231199_was1194_was1184_was1169_was1043_wasS2-2310027.md, read 2026-08-05 quote:objective:FS_5GSAT_Ph3_ARCH

the objective of NR_NTN_Ku_bands-Core

Use the regulation requirements in ITU Regions 1, 2 and 3 to identify relevant adjacent band co-existence scenarios for NTN Ku Band covering the following frequency ranges, considering targeted deployment scenarios: For ITU regions 1 and 3: How it was counted: section 4 of the work item description /var/www/whatthespec.net/data/data/wis/1041135/RP-252911_WID revision for the NTN Ku band cl.md, read 2026-08-05 quote:objective:NR_NTN_Ku_bands-Core

why NR_NTN_Ku_bands-Core was proposed

The Ku band is allocated for primary satellite use for ITU regions 1, 2 and 3. Consequently, this WID introduces the Ku band into 3GPP specifications according to the ITU definitions in Table 1 and Table 2. How it was counted: section 3 of the work item description /var/www/whatthespec.net/data/data/wis/1041135/RP-252911_WID revision for the NTN Ku band cl.md, read 2026-08-05 quote:why:NR_NTN_Ku_bands-Core

the objective of IoT_NTN_TDD-Core

The work item aims to specify enhancements for NB-IoT NTN to enable NTN operation with a NB-IoT TDD mode leveraging commonalities with half-duplex NB-IoT FDD NTN, by defining a new NB-IoT TDD mode for NTN based on minimum necessary changes to the NB-IoT NTN FDD frame structure and procedures for the NB-IoT operation in the targeted unpaired MSS allocated band (TN deployment is not expected in this band). The feature is not intended to be applicable to existing 3GPP bands. How it was counted: section 4 of the work item description /var/www/whatthespec.net/data/data/wis/1051123/RP-252935 Revised WID on introduction of IoT-NTN TDD_cl.md, read 2026-08-05 quote:objective:IoT_NTN_TDD-Core

why IoT_NTN_TDD-Core was proposed

This Work Item Description proposes the introduction of a new feature that allows the operator to use the radio resources in a periodic subset of the UL and DL subframes in N radio frames to achieve TDD operation in the SAN (Satellite Access Node) and IoT NTN UE, thus limiting power consumption. This feature allows extending 3GPP NB-IoT NTN operation with support for additional NGSO satellite system. How it was counted: section 3 of the work item description /var/www/whatthespec.net/data/data/wis/1051123/RP-252935 Revised WID on introduction of IoT-NTN TDD_cl.md, read 2026-08-05 quote:why:IoT_NTN_TDD-Core

the objective of LTE_NBIoT_eMTC_NTN_req-Perf

The objective of this Work Item is to specify RF and RRM requirements for NB-IoT and eMTC operation over NTN functionality defined in the Rel-17 LTE_NBIOT_eMTC_NTN work item, covering the following aspects: 1. Specification of RF requirements for Satellite Access Node (SAN) and UE including the following [RAN4]: How it was counted: section 4 of the work item description /var/www/whatthespec.net/data/data/wis/950274/RP-223437_clean.md, read 2026-08-05 quote:objective:LTE_NBIoT_eMTC_NTN_req-Perf

why FS_NR_NTN_GNSS_resilient was proposed

UEs compatible with Rel-17/18/19 and supporting NTN access are expected to be equipped with GNSS (Global Navigation Satellite System). These UEs should support uplink time and frequency pre-compensation based on their GNSS-acquired position. How it was counted: section 3 of the work item description /var/www/whatthespec.net/data/data/wis/1080071/RP-253137 was 1933 New SID on GNSS resilient NR-NTN op_v09.md, read 2026-08-05 quote:why:FS_NR_NTN_GNSS_resilient

the objective of LTE_NBIOT_eMTC_NTN_plus_EPS-UEConTest

The objective of this work item is to enable UE conformance testing for Rel-17 NB-IoT/eMTC support for Non-Terrestrial Networks (NTN) including EPS aspects WI corresponding to the WID on LTE_NBIOT_eMTC_NTN with Unique identifier 920069 and the WID on IoT_SAT_ARCH_EPS with Unique identifier 940001. How it was counted: section 4 of the work item description /var/www/whatthespec.net/data/data/wis/960087/RP-233250cl.md, read 2026-08-05 quote:objective:LTE_NBIOT_eMTC_NTN_plus_EPS-UEConTest

the objective of FS_ULBC

The objective of this study is to develop recommendations for potential normative work on an ultra-low bit rate codec with primary application for voice over GEO. Specifically, the following objectives are identified: How it was counted: section 4 of the work item description /var/www/whatthespec.net/data/data/wis/1070055/SP-250635.md, read 2026-08-05 quote:objective:FS_ULBC

why FS_ULBC was proposed

3GPP SA1 has studied the use case IMS Voice Call Using GEO Access, and the results are documented in TR 22.887. Normative service requirements and KPIs on IMS voice call using GEO satellite access will be introduced in TS 22.261 at TSG#107. How it was counted: section 3 of the work item description /var/www/whatthespec.net/data/data/wis/1070055/SP-250635.md, read 2026-08-05 quote:why:FS_ULBC

the objective of 5GSAT_Ph3_App

The SA6 objectives of this work item include the following: 1. Develop Stage 2 normative technical specification for specifying satellite access enabled 5G services, based on the conclusions captured in 3GPP TR 23.700-01. How it was counted: section 4 of the work item description /var/www/whatthespec.net/data/data/wis/1040077/SP-241690_cl_Rev_WID_application_enablement_for_satellite_access_Ph3.md, read 2026-08-05 quote:objective:5GSAT_Ph3_App

why 5GSAT_Ph3_App was proposed

A substantial justification appears in the study item description of the parent feature in SP-240296 (FS_5GSAT_Ph3_App) and applies to this work item description. How it was counted: section 3 of the work item description /var/www/whatthespec.net/data/data/wis/1040077/SP-241690_cl_Rev_WID_application_enablement_for_satellite_access_Ph3.md, read 2026-08-05 quote:why:5GSAT_Ph3_App

the objective of FS_5GSAT_Ph3_SEC

The objective is to study the security and privacy aspects of 5G satellite access phase 3. Ensure that security solutions are aligned with the work in SA2, RANs and SA1. How it was counted: section 4 of the work item description /var/www/whatthespec.net/data/data/wis/1020044/SP-240232 Revised Study on Security Aspects of 5G Satellite Access Phase 3-cl.md, read 2026-08-05 quote:objective:FS_5GSAT_Ph3_SEC

why FS_5GSAT_Ph3_SEC was proposed

According to the SA’s Satellite SID proposal (SP-231199) agreed at the SA Meeting #101and the scope of TR 23.700-29, SA2 will study the following topics: Regenerative payload generic architecture. How it was counted: section 3 of the work item description /var/www/whatthespec.net/data/data/wis/1020044/SP-240232 Revised Study on Security Aspects of 5G Satellite Access Phase 3-cl.md, read 2026-08-05 quote:why:FS_5GSAT_Ph3_SEC

the objective of FS_5GSAT_Ph4

The objectives of this study are the following: to identify the gaps and potential new service requirements related to enhanced support for emergency communications and mission critical services using satellite access How it was counted: section 4 of the work item description /var/www/whatthespec.net/data/data/wis/1030042/SP-241824_clean.md, read 2026-08-05 quote:objective:FS_5GSAT_Ph4

why FS_5GSAT_Ph4 was proposed

New capabilities for satellite access such as Store and Forward Satellite operation and UE-Satellite-UE communication have been addressed in SA1 5GSat phase 3 for Release 19. First commercial deployments of 5G based satellite are happening and several new use cases for satellite access or enhancements are to be addressed still in the context of 5G advanced (i.e. in Release 20). How it was counted: section 3 of the work item description /var/www/whatthespec.net/data/data/wis/1030042/SP-241824_clean.md, read 2026-08-05 quote:why:FS_5GSAT_Ph4

the objective of 5GSATB

The objective of this work item is to specify architectural enhancements of 5G System to support satellite backhaul as per conclusions reached within TR 23.700-27 (clause 8). The detailed objectives are as follows: How it was counted: section 4 of the work item description /var/www/whatthespec.net/data/data/wis/970056/SP-230111_clean_S2-2303823_5GSATB.md, read 2026-08-05 quote:objective:5GSATB

why 5GSATB was proposed

This work item aims at specifying system enhancements to support dynamical satellite backhaul, UPF on-board enabled edge computing and local data switching in 5G system. The related solutions have been documented in the TR 23.700-27. How it was counted: section 3 of the work item description /var/www/whatthespec.net/data/data/wis/970056/SP-230111_clean_S2-2303823_5GSATB.md, read 2026-08-05 quote:why:5GSATB

the objective of FS_5GSAT_Ph3

The objectives of this study are to study new use cases and related regulatory requirements and identify new potential service requirements and enhancement for 5G system over satellite, including: Operation with intermittent/temporary satellite connectivity for delay-tolerant communication service How it was counted: section 4 of the work item description /var/www/whatthespec.net/data/data/wis/960016/SP-220679.md, read 2026-08-05 quote:objective:FS_5GSAT_Ph3

why FS_5GSAT_Ph3 was proposed

TS22.261 has some requirements for satellite access and satellite backhaul in the 5G system. RAN WGs have defined satellite-enabled NG-RAN. How it was counted: section 3 of the work item description /var/www/whatthespec.net/data/data/wis/960016/SP-220679.md, read 2026-08-05 quote:why:FS_5GSAT_Ph3

the objective of NR_NTN_enh_plus_CT-UEConTest

The objective of this work item is to enable UE conformance testing for the Rel-18 NTN enhancements WI which includes analysing the requirements, creation of corresponding test cases by defining the test environment, special conformance testing function, test procedure, message contents, MU/TT analysis, associated PICS, applicability and updating the relevant conformance specifications. The conformance testing aspects for this WI would consist of below areas: How it was counted: section 4 of the work item description /var/www/whatthespec.net/data/data/wis/1050130/RP-251230_revised WID on UE Conformance - NR NTN (Non-Terrestrial Networks) enhancements_plusCTaspects.md, read 2026-08-05 quote:objective:NR_NTN_enh_plus_CT-UEConTest

why NR_NTN_enh_plus_CT-UEConTest was proposed

In Release 17, a work item was carried out to define solutions enabling NR and NG-RAN to support Non-Terrestrial Networks (NTN): Transparent payload based GSO and NGSO network scenarios addressing 3GPP power class 3 UE in both Earth fixed and/or moving cell configurations. How it was counted: section 3 of the work item description /var/www/whatthespec.net/data/data/wis/1050130/RP-251230_revised WID on UE Conformance - NR NTN (Non-Terrestrial Networks) enhancements_plusCTaspects.md, read 2026-08-05 quote:why:NR_NTN_enh_plus_CT-UEConTest

the objective of 5GSAT_Ph4-ARC

The objective of this work item is to produce normative specifications fulfilling the results of the feasibility study as documented in the conclusions section of TR 23.700-19 (clause 8). The detailed objectives include: How it was counted: section 4 of the work item description /var/www/whatthespec.net/data/data/wis/1100033/SP-251703_clean-was-SP-251671-was-SP-251344_S2-2511312_New WID-5GSAT_Ph4_ARC.md, read 2026-08-05 quote:objective:5GSAT_Ph4-ARC

why 5GSAT_Ph4-ARC was proposed

Integration of satellite components into EPS and 5GS has been studied in Rel 16, Rel 17, Rel 18 and 19. As part of Rel-20, SA1 developed a TR 22.887 that captures a set of use cases and potential service requirements related to the 5G system with satellite access considering new capabilities: How it was counted: section 3 of the work item description /var/www/whatthespec.net/data/data/wis/1100033/SP-251703_clean-was-SP-251671-was-SP-251344_S2-2511312_New WID-5GSAT_Ph4_ARC.md, read 2026-08-05 quote:why:5GSAT_Ph4-ARC

Meeting 68

CP-101

3GPPCT#101 How it was counted: the row of table `meeting` whose code is CP-101, asked of /var/www/whatthespec.net/data/database/api/meeting_resolve.sqlite on 2026-08-05; its days and place from table `meetings` in /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite where the id is 41043 meeting:CP-101

CP-103

3GPPCT#103 How it was counted: the row of table `meeting` whose code is CP-103, asked of /var/www/whatthespec.net/data/database/api/meeting_resolve.sqlite on 2026-08-05; its days and place from table `meetings` in /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite where the id is 60296; the number registered from table `meeting` in /var/www/whatthespec.net/data/database/api/participants.sqlite meeting:CP-103

CP-105

3GPPCT#105 How it was counted: the row of table `meeting` whose code is CP-105, asked of /var/www/whatthespec.net/data/database/api/meeting_resolve.sqlite on 2026-08-05; its days and place from table `meetings` in /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite where the id is 60300; the number registered from table `meeting` in /var/www/whatthespec.net/data/database/api/participants.sqlite meeting:CP-105

CP-106

3GPPCT#106 How it was counted: the row of table `meeting` whose code is CP-106, asked of /var/www/whatthespec.net/data/database/api/meeting_resolve.sqlite on 2026-08-05; its days and place from table `meetings` in /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite where the id is 60303; the number registered from table `meeting` in /var/www/whatthespec.net/data/database/api/participants.sqlite meeting:CP-106

CP-107

3GPPCT#107 How it was counted: the row of table `meeting` whose code is CP-107, asked of /var/www/whatthespec.net/data/database/api/meeting_resolve.sqlite on 2026-08-05; its days and place from table `meetings` in /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite where the id is 60572; the number registered from table `meeting` in /var/www/whatthespec.net/data/database/api/participants.sqlite meeting:CP-107

CP-108

3GPPCT#108 How it was counted: the row of table `meeting` whose code is CP-108, asked of /var/www/whatthespec.net/data/database/api/meeting_resolve.sqlite on 2026-08-05; its days and place from table `meetings` in /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite where the id is 60575; the number registered from table `meeting` in /var/www/whatthespec.net/data/database/api/participants.sqlite meeting:CP-108

CP-112

3GPPCT#112 How it was counted: the row of table `meeting` whose code is CP-112, asked of /var/www/whatthespec.net/data/database/api/meeting_resolve.sqlite on 2026-08-05; its days and place from table `meetings` in /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite where the id is 60795; the number registered from table `meeting` in /var/www/whatthespec.net/data/database/api/participants.sqlite meeting:CP-112

CP-91-e

3GPPCT#91-e How it was counted: the row of table `meeting` whose code is CP-91-e, asked of /var/www/whatthespec.net/data/database/api/meeting_resolve.sqlite on 2026-08-05; its days and place from table `meetings` in /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite where the id is 39405 meeting:CP-91-e

CP-94-e

3GPPCT#94-e How it was counted: the row of table `meeting` whose code is CP-94-e, asked of /var/www/whatthespec.net/data/database/api/meeting_resolve.sqlite on 2026-08-05; its days and place from table `meetings` in /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite where the id is 60222 meeting:CP-94-e

R4-105

3GPPRAN4#105 How it was counted: the row of table `meeting` whose code is R4-105, asked of /var/www/whatthespec.net/data/database/api/meeting_resolve.sqlite on 2026-08-05; its days and place from table `meetings` in /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite where the id is 39944 meeting:R4-105

R4-109

3GPPRAN4#109 How it was counted: the row of table `meeting` whose code is R4-109, asked of /var/www/whatthespec.net/data/database/api/meeting_resolve.sqlite on 2026-08-05; its days and place from table `meetings` in /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite where the id is 39978 meeting:R4-109

R4-110

3GPPRAN4#110 How it was counted: the row of table `meeting` whose code is R4-110, asked of /var/www/whatthespec.net/data/database/api/meeting_resolve.sqlite on 2026-08-05; its days and place from table `meetings` in /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite where the id is 60388; the number registered from table `meeting` in /var/www/whatthespec.net/data/database/api/participants.sqlite meeting:R4-110

R4-111

3GPPRAN4#111 How it was counted: the row of table `meeting` whose code is R4-111, asked of /var/www/whatthespec.net/data/database/api/meeting_resolve.sqlite on 2026-08-05; its days and place from table `meetings` in /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite where the id is 60416; the number registered from table `meeting` in /var/www/whatthespec.net/data/database/api/participants.sqlite meeting:R4-111

R4-112

3GPPRAN4#112 How it was counted: the row of table `meeting` whose code is R4-112, asked of /var/www/whatthespec.net/data/database/api/meeting_resolve.sqlite on 2026-08-05; its days and place from table `meetings` in /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite where the id is 60430; the number registered from table `meeting` in /var/www/whatthespec.net/data/database/api/participants.sqlite meeting:R4-112

R4-113

3GPPRAN4#113 How it was counted: the row of table `meeting` whose code is R4-113, asked of /var/www/whatthespec.net/data/database/api/meeting_resolve.sqlite on 2026-08-05; its days and place from table `meetings` in /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite where the id is 60458; the number registered from table `meeting` in /var/www/whatthespec.net/data/database/api/participants.sqlite meeting:R4-113

R4-114

3GPPRAN4#114 How it was counted: the row of table `meeting` whose code is R4-114, asked of /var/www/whatthespec.net/data/database/api/meeting_resolve.sqlite on 2026-08-05; its days and place from table `meetings` in /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite where the id is 60587; the number registered from table `meeting` in /var/www/whatthespec.net/data/database/api/participants.sqlite meeting:R4-114

R4-115 cited

3GPPRAN4#115 How it was counted: the row of table `meeting` whose code is R4-115, asked of /var/www/whatthespec.net/data/database/api/meeting_resolve.sqlite on 2026-08-05; its days and place from table `meetings` in /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite where the id is 60596; the number registered from table `meeting` in /var/www/whatthespec.net/data/database/api/participants.sqlite meeting:R4-115

R4-116 cited

3GPPRAN4#116 How it was counted: the row of table `meeting` whose code is R4-116, asked of /var/www/whatthespec.net/data/database/api/meeting_resolve.sqlite on 2026-08-05; its days and place from table `meetings` in /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite where the id is 60601; the number registered from table `meeting` in /var/www/whatthespec.net/data/database/api/participants.sqlite meeting:R4-116

R4-117 cited

3GPPRAN4#117 How it was counted: the row of table `meeting` whose code is R4-117, asked of /var/www/whatthespec.net/data/database/api/meeting_resolve.sqlite on 2026-08-05; its days and place from table `meetings` in /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite where the id is 60610; the number registered from table `meeting` in /var/www/whatthespec.net/data/database/api/participants.sqlite meeting:R4-117

R4-118

3GPPRAN4#118 How it was counted: the row of table `meeting` whose code is R4-118, asked of /var/www/whatthespec.net/data/database/api/meeting_resolve.sqlite on 2026-08-05; its days and place from table `meetings` in /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite where the id is 60728; the number registered from table `meeting` in /var/www/whatthespec.net/data/database/api/participants.sqlite meeting:R4-118

R4-119

3GPPRAN4#119 How it was counted: the row of table `meeting` whose code is R4-119, asked of /var/www/whatthespec.net/data/database/api/meeting_resolve.sqlite on 2026-08-05; its days and place from table `meetings` in /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite where the id is 60730; the number registered from table `meeting` in /var/www/whatthespec.net/data/database/api/participants.sqlite meeting:R4-119

RP-101

3GPPRAN#101 How it was counted: the row of table `meeting` whose code is RP-101, asked of /var/www/whatthespec.net/data/database/api/meeting_resolve.sqlite on 2026-08-05; its days and place from table `meetings` in /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite where the id is 39914 meeting:RP-101

RP-102

3GPPRAN#102 How it was counted: the row of table `meeting` whose code is RP-102, asked of /var/www/whatthespec.net/data/database/api/meeting_resolve.sqlite on 2026-08-05; its days and place from table `meetings` in /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite where the id is 39915 meeting:RP-102

RP-103

3GPPRAN#103 How it was counted: the row of table `meeting` whose code is RP-103, asked of /var/www/whatthespec.net/data/database/api/meeting_resolve.sqlite on 2026-08-05; its days and place from table `meetings` in /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite where the id is 60294; the number registered from table `meeting` in /var/www/whatthespec.net/data/database/api/participants.sqlite meeting:RP-103

RP-104

3GPPRAN#104 How it was counted: the row of table `meeting` whose code is RP-104, asked of /var/www/whatthespec.net/data/database/api/meeting_resolve.sqlite on 2026-08-05; its days and place from table `meetings` in /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite where the id is 60298; the number registered from table `meeting` in /var/www/whatthespec.net/data/database/api/participants.sqlite meeting:RP-104

RP-105

3GPPRAN#105 How it was counted: the row of table `meeting` whose code is RP-105, asked of /var/www/whatthespec.net/data/database/api/meeting_resolve.sqlite on 2026-08-05; its days and place from table `meetings` in /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite where the id is 60301; the number registered from table `meeting` in /var/www/whatthespec.net/data/database/api/participants.sqlite meeting:RP-105

RP-106

3GPPRAN#106 How it was counted: the row of table `meeting` whose code is RP-106, asked of /var/www/whatthespec.net/data/database/api/meeting_resolve.sqlite on 2026-08-05; its days and place from table `meetings` in /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite where the id is 60304; the number registered from table `meeting` in /var/www/whatthespec.net/data/database/api/participants.sqlite meeting:RP-106

RP-107

3GPPRAN#107 How it was counted: the row of table `meeting` whose code is RP-107, asked of /var/www/whatthespec.net/data/database/api/meeting_resolve.sqlite on 2026-08-05; its days and place from table `meetings` in /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite where the id is 60573; the number registered from table `meeting` in /var/www/whatthespec.net/data/database/api/participants.sqlite meeting:RP-107

RP-108

3GPPRAN#108 How it was counted: the row of table `meeting` whose code is RP-108, asked of /var/www/whatthespec.net/data/database/api/meeting_resolve.sqlite on 2026-08-05; its days and place from table `meetings` in /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite where the id is 60576; the number registered from table `meeting` in /var/www/whatthespec.net/data/database/api/participants.sqlite meeting:RP-108

RP-109

3GPPRAN#109 How it was counted: the row of table `meeting` whose code is RP-109, asked of /var/www/whatthespec.net/data/database/api/meeting_resolve.sqlite on 2026-08-05; its days and place from table `meetings` in /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite where the id is 60579; the number registered from table `meeting` in /var/www/whatthespec.net/data/database/api/participants.sqlite meeting:RP-109

RP-110

3GPPRAN#110 How it was counted: the row of table `meeting` whose code is RP-110, asked of /var/www/whatthespec.net/data/database/api/meeting_resolve.sqlite on 2026-08-05; its days and place from table `meetings` in /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite where the id is 60582; the number registered from table `meeting` in /var/www/whatthespec.net/data/database/api/participants.sqlite meeting:RP-110

RP-111

3GPPRAN#111 How it was counted: the row of table `meeting` whose code is RP-111, asked of /var/www/whatthespec.net/data/database/api/meeting_resolve.sqlite on 2026-08-05; its days and place from table `meetings` in /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite where the id is 60793; the number registered from table `meeting` in /var/www/whatthespec.net/data/database/api/participants.sqlite meeting:RP-111

RP-112

3GPPRAN#112 How it was counted: the row of table `meeting` whose code is RP-112, asked of /var/www/whatthespec.net/data/database/api/meeting_resolve.sqlite on 2026-08-05; its days and place from table `meetings` in /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite where the id is 60796; the number registered from table `meeting` in /var/www/whatthespec.net/data/database/api/participants.sqlite meeting:RP-112

RP-50

3GPPRAN#50 How it was counted: the row of table `meeting` whose code is RP-50, asked of /var/www/whatthespec.net/data/database/api/meeting_resolve.sqlite on 2026-08-05; its days and place from table `meetings` in /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite where the id is 27016 meeting:RP-50

RP-52

3GPPRAN#52 How it was counted: the row of table `meeting` whose code is RP-52, asked of /var/www/whatthespec.net/data/database/api/meeting_resolve.sqlite on 2026-08-05; its days and place from table `meetings` in /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite where the id is 28173 meeting:RP-52

RP-76 cited

3GPPRAN#76 How it was counted: the row of table `meeting` whose code is RP-76, asked of /var/www/whatthespec.net/data/database/api/meeting_resolve.sqlite on 2026-08-05; its days and place from table `meetings` in /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite where the id is 31942 meeting:RP-76

RP-83

3GPPRAN#83 How it was counted: the row of table `meeting` whose code is RP-83, asked of /var/www/whatthespec.net/data/database/api/meeting_resolve.sqlite on 2026-08-05; its days and place from table `meetings` in /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite where the id is 19636 meeting:RP-83

RP-90-e

3GPPRAN#90-e How it was counted: the row of table `meeting` whose code is RP-90-e, asked of /var/www/whatthespec.net/data/database/api/meeting_resolve.sqlite on 2026-08-05; its days and place from table `meetings` in /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite where the id is 38732 meeting:RP-90-e

RP-92-e

3GPPRAN#92-e How it was counted: the row of table `meeting` whose code is RP-92-e, asked of /var/www/whatthespec.net/data/database/api/meeting_resolve.sqlite on 2026-08-05; its days and place from table `meetings` in /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite where the id is 39340 meeting:RP-92-e

RP-95-e

3GPPRAN#95-e How it was counted: the row of table `meeting` whose code is RP-95-e, asked of /var/www/whatthespec.net/data/database/api/meeting_resolve.sqlite on 2026-08-05; its days and place from table `meetings` in /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite where the id is 60235 meeting:RP-95-e

RP-96

3GPPRAN#96 How it was counted: the row of table `meeting` whose code is RP-96, asked of /var/www/whatthespec.net/data/database/api/meeting_resolve.sqlite on 2026-08-05; its days and place from table `meetings` in /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite where the id is 39909 meeting:RP-96

RP-97-e

3GPPRAN#97-e How it was counted: the row of table `meeting` whose code is RP-97-e, asked of /var/www/whatthespec.net/data/database/api/meeting_resolve.sqlite on 2026-08-05; its days and place from table `meetings` in /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite where the id is 60332 meeting:RP-97-e

RP-98-e

3GPPRAN#98-e How it was counted: the row of table `meeting` whose code is RP-98-e, asked of /var/www/whatthespec.net/data/database/api/meeting_resolve.sqlite on 2026-08-05; its days and place from table `meetings` in /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite where the id is 60464 meeting:RP-98-e

SP-100

3GPPSA#100 How it was counted: the row of table `meeting` whose code is SP-100, asked of /var/www/whatthespec.net/data/database/api/meeting_resolve.sqlite on 2026-08-05; its days and place from table `meetings` in /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite where the id is 60010 meeting:SP-100

SP-101

3GPPSA#101 How it was counted: the row of table `meeting` whose code is SP-101, asked of /var/www/whatthespec.net/data/database/api/meeting_resolve.sqlite on 2026-08-05; its days and place from table `meetings` in /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite where the id is 60011 meeting:SP-101

SP-102

3GPPSA#102 How it was counted: the row of table `meeting` whose code is SP-102, asked of /var/www/whatthespec.net/data/database/api/meeting_resolve.sqlite on 2026-08-05; its days and place from table `meetings` in /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite where the id is 60012 meeting:SP-102

SP-103

3GPPSA#103 How it was counted: the row of table `meeting` whose code is SP-103, asked of /var/www/whatthespec.net/data/database/api/meeting_resolve.sqlite on 2026-08-05; its days and place from table `meetings` in /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite where the id is 60295; the number registered from table `meeting` in /var/www/whatthespec.net/data/database/api/participants.sqlite meeting:SP-103

SP-104

3GPPSA#104 How it was counted: the row of table `meeting` whose code is SP-104, asked of /var/www/whatthespec.net/data/database/api/meeting_resolve.sqlite on 2026-08-05; its days and place from table `meetings` in /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite where the id is 60299; the number registered from table `meeting` in /var/www/whatthespec.net/data/database/api/participants.sqlite meeting:SP-104

SP-105

3GPPSA#105 How it was counted: the row of table `meeting` whose code is SP-105, asked of /var/www/whatthespec.net/data/database/api/meeting_resolve.sqlite on 2026-08-05; its days and place from table `meetings` in /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite where the id is 60302; the number registered from table `meeting` in /var/www/whatthespec.net/data/database/api/participants.sqlite meeting:SP-105

SP-106

3GPPSA#106 How it was counted: the row of table `meeting` whose code is SP-106, asked of /var/www/whatthespec.net/data/database/api/meeting_resolve.sqlite on 2026-08-05; its days and place from table `meetings` in /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite where the id is 60305; the number registered from table `meeting` in /var/www/whatthespec.net/data/database/api/participants.sqlite meeting:SP-106

SP-107

3GPPSA#107 How it was counted: the row of table `meeting` whose code is SP-107, asked of /var/www/whatthespec.net/data/database/api/meeting_resolve.sqlite on 2026-08-05; its days and place from table `meetings` in /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite where the id is 60574; the number registered from table `meeting` in /var/www/whatthespec.net/data/database/api/participants.sqlite meeting:SP-107

SP-108

3GPPSA#108 How it was counted: the row of table `meeting` whose code is SP-108, asked of /var/www/whatthespec.net/data/database/api/meeting_resolve.sqlite on 2026-08-05; its days and place from table `meetings` in /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite where the id is 60577; the number registered from table `meeting` in /var/www/whatthespec.net/data/database/api/participants.sqlite meeting:SP-108

SP-109

3GPPSA#109 How it was counted: the row of table `meeting` whose code is SP-109, asked of /var/www/whatthespec.net/data/database/api/meeting_resolve.sqlite on 2026-08-05; its days and place from table `meetings` in /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite where the id is 60580; the number registered from table `meeting` in /var/www/whatthespec.net/data/database/api/participants.sqlite meeting:SP-109

SP-110

3GPPSA#110 How it was counted: the row of table `meeting` whose code is SP-110, asked of /var/www/whatthespec.net/data/database/api/meeting_resolve.sqlite on 2026-08-05; its days and place from table `meetings` in /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite where the id is 60583; the number registered from table `meeting` in /var/www/whatthespec.net/data/database/api/participants.sqlite meeting:SP-110

SP-111

3GPPSA#111 How it was counted: the row of table `meeting` whose code is SP-111, asked of /var/www/whatthespec.net/data/database/api/meeting_resolve.sqlite on 2026-08-05; its days and place from table `meetings` in /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite where the id is 60794; the number registered from table `meeting` in /var/www/whatthespec.net/data/database/api/participants.sqlite meeting:SP-111

SP-112

3GPPSA#112 How it was counted: the row of table `meeting` whose code is SP-112, asked of /var/www/whatthespec.net/data/database/api/meeting_resolve.sqlite on 2026-08-05; its days and place from table `meetings` in /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite where the id is 60797; the number registered from table `meeting` in /var/www/whatthespec.net/data/database/api/participants.sqlite meeting:SP-112

SP-57

3GPPSA#57 How it was counted: the row of table `meeting` whose code is SP-57, asked of /var/www/whatthespec.net/data/database/api/meeting_resolve.sqlite on 2026-08-05; its days and place from table `meetings` in /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite where the id is 28526 meeting:SP-57

SP-77

3GPPSA#77 How it was counted: the row of table `meeting` whose code is SP-77, asked of /var/www/whatthespec.net/data/database/api/meeting_resolve.sqlite on 2026-08-05; its days and place from table `meetings` in /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite where the id is 31947 meeting:SP-77

SP-80

3GPPSA#80 How it was counted: the row of table `meeting` whose code is SP-80, asked of /var/www/whatthespec.net/data/database/api/meeting_resolve.sqlite on 2026-08-05; its days and place from table `meetings` in /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite where the id is 18664 meeting:SP-80

SP-82

3GPPSA#82 How it was counted: the row of table `meeting` whose code is SP-82, asked of /var/www/whatthespec.net/data/database/api/meeting_resolve.sqlite on 2026-08-05; its days and place from table `meetings` in /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite where the id is 18671 meeting:SP-82

SP-83

3GPPSA#83 How it was counted: the row of table `meeting` whose code is SP-83, asked of /var/www/whatthespec.net/data/database/api/meeting_resolve.sqlite on 2026-08-05; its days and place from table `meetings` in /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite where the id is 19637 meeting:SP-83

SP-86

3GPPSA#86 How it was counted: the row of table `meeting` whose code is SP-86, asked of /var/www/whatthespec.net/data/database/api/meeting_resolve.sqlite on 2026-08-05; its days and place from table `meetings` in /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite where the id is 19646 meeting:SP-86

SP-92-e

3GPPSA#92-e How it was counted: the row of table `meeting` whose code is SP-92-e, asked of /var/www/whatthespec.net/data/database/api/meeting_resolve.sqlite on 2026-08-05; its days and place from table `meetings` in /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite where the id is 39610 meeting:SP-92-e

SP-94-e

3GPPSA#94-e How it was counted: the row of table `meeting` whose code is SP-94-e, asked of /var/www/whatthespec.net/data/database/api/meeting_resolve.sqlite on 2026-08-05; its days and place from table `meetings` in /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite where the id is 60223 meeting:SP-94-e

SP-96

3GPPSA#96 How it was counted: the row of table `meeting` whose code is SP-96, asked of /var/www/whatthespec.net/data/database/api/meeting_resolve.sqlite on 2026-08-05; its days and place from table `meetings` in /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite where the id is 60006 meeting:SP-96

SP-97-e

3GPPSA#97-e How it was counted: the row of table `meeting` whose code is SP-97-e, asked of /var/www/whatthespec.net/data/database/api/meeting_resolve.sqlite on 2026-08-05; its days and place from table `meetings` in /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite where the id is 60337 meeting:SP-97-e

SP-98-e

3GPPSA#98-e How it was counted: the row of table `meeting` whose code is SP-98-e, asked of /var/www/whatthespec.net/data/database/api/meeting_resolve.sqlite on 2026-08-05; its days and place from table `meetings` in /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite where the id is 60465 meeting:SP-98-e

SP-99

3GPPSA#99 How it was counted: the row of table `meeting` whose code is SP-99, asked of /var/www/whatthespec.net/data/database/api/meeting_resolve.sqlite on 2026-08-05; its days and place from table `meetings` in /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite where the id is 60009 meeting:SP-99

Wg 18

CT1 cited

TSG CT WG1 How it was counted: documents whose work item acronym is one of the 155 Satellites acronyms and whose meeting code begins C1-; the full name is the row of table `entity` in /var/www/whatthespec.net/data/database/api/wts3.sqlite, and the short one the table in /var/www/whatthespec.net/pygppe/site/shared/groups_catalog.php, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 wg:C1

CT3

TSG CT WG3 How it was counted: documents whose work item acronym is one of the 155 Satellites acronyms and whose meeting code begins C3-; the full name is the row of table `entity` in /var/www/whatthespec.net/data/database/api/wts3.sqlite, and the short one the table in /var/www/whatthespec.net/pygppe/site/shared/groups_catalog.php, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 wg:C3

CT4

TSG CT WG4 How it was counted: documents whose work item acronym is one of the 155 Satellites acronyms and whose meeting code begins C4-; the full name is the row of table `entity` in /var/www/whatthespec.net/data/database/api/wts3.sqlite, and the short one the table in /var/www/whatthespec.net/pygppe/site/shared/groups_catalog.php, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 wg:C4

CT6

TSG CT WG6 How it was counted: documents whose work item acronym is one of the 155 Satellites acronyms and whose meeting code begins C6-; the full name is the row of table `entity` in /var/www/whatthespec.net/data/database/api/wts3.sqlite, and the short one the table in /var/www/whatthespec.net/pygppe/site/shared/groups_catalog.php, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 wg:C6

CT

TSG CT How it was counted: documents whose work item acronym is one of the 155 Satellites acronyms and whose meeting code begins CP-; the full name is the row of table `entity` in /var/www/whatthespec.net/data/database/api/wts3.sqlite, and the short one the table in /var/www/whatthespec.net/pygppe/site/shared/groups_catalog.php, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 wg:CP

RAN1 cited

TSG RAN WG1 How it was counted: documents whose work item acronym is one of the 155 Satellites acronyms and whose meeting code begins R1-; the full name is the row of table `entity` in /var/www/whatthespec.net/data/database/api/wts3.sqlite, and the short one the table in /var/www/whatthespec.net/pygppe/site/shared/groups_catalog.php, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 wg:R1

RAN2 cited

TSG RAN WG2 How it was counted: documents whose work item acronym is one of the 155 Satellites acronyms and whose meeting code begins R2-; the full name is the row of table `entity` in /var/www/whatthespec.net/data/database/api/wts3.sqlite, and the short one the table in /var/www/whatthespec.net/pygppe/site/shared/groups_catalog.php, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 wg:R2

RAN3 cited

TSG RAN WG3 How it was counted: documents whose work item acronym is one of the 155 Satellites acronyms and whose meeting code begins R3-; the full name is the row of table `entity` in /var/www/whatthespec.net/data/database/api/wts3.sqlite, and the short one the table in /var/www/whatthespec.net/pygppe/site/shared/groups_catalog.php, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 wg:R3

RAN4 cited

TSG RAN WG4 How it was counted: documents whose work item acronym is one of the 155 Satellites acronyms and whose meeting code begins R4-; the full name is the row of table `entity` in /var/www/whatthespec.net/data/database/api/wts3.sqlite, and the short one the table in /var/www/whatthespec.net/pygppe/site/shared/groups_catalog.php, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 wg:R4

RAN5 cited

TSG RAN WG5 How it was counted: documents whose work item acronym is one of the 155 Satellites acronyms and whose meeting code begins R5-; the full name is the row of table `entity` in /var/www/whatthespec.net/data/database/api/wts3.sqlite, and the short one the table in /var/www/whatthespec.net/pygppe/site/shared/groups_catalog.php, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 wg:R5

RAN cited

TSG RAN How it was counted: documents whose work item acronym is one of the 155 Satellites acronyms and whose meeting code begins RP-; the full name is the row of table `entity` in /var/www/whatthespec.net/data/database/api/wts3.sqlite, and the short one the table in /var/www/whatthespec.net/pygppe/site/shared/groups_catalog.php, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 wg:RP

SA1 cited

TSG SA WG1 How it was counted: documents whose work item acronym is one of the 155 Satellites acronyms and whose meeting code begins S1-; the full name is the row of table `entity` in /var/www/whatthespec.net/data/database/api/wts3.sqlite, and the short one the table in /var/www/whatthespec.net/pygppe/site/shared/groups_catalog.php, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 wg:S1

SA2 cited

TSG SA WG2 How it was counted: documents whose work item acronym is one of the 155 Satellites acronyms and whose meeting code begins S2-; the full name is the row of table `entity` in /var/www/whatthespec.net/data/database/api/wts3.sqlite, and the short one the table in /var/www/whatthespec.net/pygppe/site/shared/groups_catalog.php, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 wg:S2

SA3 cited

TSG SA WG3 How it was counted: documents whose work item acronym is one of the 155 Satellites acronyms and whose meeting code begins S3-; the full name is the row of table `entity` in /var/www/whatthespec.net/data/database/api/wts3.sqlite, and the short one the table in /var/www/whatthespec.net/pygppe/site/shared/groups_catalog.php, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 wg:S3

SA4

TSG SA WG4 How it was counted: documents whose work item acronym is one of the 155 Satellites acronyms and whose meeting code begins S4-; the full name is the row of table `entity` in /var/www/whatthespec.net/data/database/api/wts3.sqlite, and the short one the table in /var/www/whatthespec.net/pygppe/site/shared/groups_catalog.php, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 wg:S4

SA5 cited

TSG SA WG5 How it was counted: documents whose work item acronym is one of the 155 Satellites acronyms and whose meeting code begins S5-; the full name is the row of table `entity` in /var/www/whatthespec.net/data/database/api/wts3.sqlite, and the short one the table in /var/www/whatthespec.net/pygppe/site/shared/groups_catalog.php, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 wg:S5

SA6

TSG SA WG6 How it was counted: documents whose work item acronym is one of the 155 Satellites acronyms and whose meeting code begins S6-; the full name is the row of table `entity` in /var/www/whatthespec.net/data/database/api/wts3.sqlite, and the short one the table in /var/www/whatthespec.net/pygppe/site/shared/groups_catalog.php, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 wg:S6

SA

TSG SA How it was counted: documents whose work item acronym is one of the 155 Satellites acronyms and whose meeting code begins SP-; the full name is the row of table `entity` in /var/www/whatthespec.net/data/database/api/wts3.sqlite, and the short one the table in /var/www/whatthespec.net/pygppe/site/shared/groups_catalog.php, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 wg:SP

Release 9

Rel-10

8 work plan rows of this subject are planned for Rel-10 How it was counted: the `release` field of the 183 work plan rows of this subject, counted for Rel-10, asked of /var/www/whatthespec.net/data/database/api/wp.sqlite on 2026-08-05 release:Rel-10

Rel-12

2 work plan rows of this subject are planned for Rel-12 How it was counted: the `release` field of the 183 work plan rows of this subject, counted for Rel-12, asked of /var/www/whatthespec.net/data/database/api/wp.sqlite on 2026-08-05 release:Rel-12

Rel-15

1 work plan rows of this subject are planned for Rel-15 How it was counted: the `release` field of the 183 work plan rows of this subject, counted for Rel-15, asked of /var/www/whatthespec.net/data/database/api/wp.sqlite on 2026-08-05 release:Rel-15

Rel-16

2 work plan rows of this subject are planned for Rel-16 How it was counted: the `release` field of the 183 work plan rows of this subject, counted for Rel-16, asked of /var/www/whatthespec.net/data/database/api/wp.sqlite on 2026-08-05 release:Rel-16

Rel-17

23 work plan rows of this subject are planned for Rel-17 How it was counted: the `release` field of the 183 work plan rows of this subject, counted for Rel-17, asked of /var/www/whatthespec.net/data/database/api/wp.sqlite on 2026-08-05 release:Rel-17

Rel-18

47 work plan rows of this subject are planned for Rel-18 How it was counted: the `release` field of the 183 work plan rows of this subject, counted for Rel-18, asked of /var/www/whatthespec.net/data/database/api/wp.sqlite on 2026-08-05 release:Rel-18

Rel-19

58 work plan rows of this subject are planned for Rel-19 How it was counted: the `release` field of the 183 work plan rows of this subject, counted for Rel-19, asked of /var/www/whatthespec.net/data/database/api/wp.sqlite on 2026-08-05 release:Rel-19

Rel-20

41 work plan rows of this subject are planned for Rel-20 How it was counted: the `release` field of the 183 work plan rows of this subject, counted for Rel-20, asked of /var/www/whatthespec.net/data/database/api/wp.sqlite on 2026-08-05 release:Rel-20

Rel-8

1 work plan rows of this subject are planned for Rel-8 How it was counted: the `release` field of the 183 work plan rows of this subject, counted for Rel-8, asked of /var/www/whatthespec.net/data/database/api/wp.sqlite on 2026-08-05 release:Rel-8

Nothing here matches that. Try a shorter word.