CT1 — the group that writes what your phone says · In depth

Everything this course is built on

354 sources, every one of them read out of a file or a database on the machine that built this site — never typed from memory. 149 of them are cited in the text; the rest are here so you can see what was available and was not used.

Built 2026-08-04 from: /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite, /var/www/whatthespec.net/data/database/api/api.sqlite, /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite, /var/www/whatthespec.net/data/database/api/officials.jsn, /var/www/whatthespec.net/data/data/meetings/ftp.3gpp.org/tsg_ct/WG1_mm-cc-sm_ex-CN1, /var/www/whatthespec.net/data/friendlyspec/json, /var/www/whatthespec.net/pygppe/site/api/admin/3gagenda-wgs.php, /var/www/whatthespec.net/pygppe/site/shared/groups_catalog.php

Specification 229

TS 03.68 cited: Voice Group Call Service (VGCS); Stage 2 spec:03.68
TS 03.69: Voice Broadcast Service (VBS); Stage 2 spec:03.69
TS 04.01: Mobile Station - Base Station System (MS - BSS) Interface General Aspects and Principles spec:04.01
TS 04.08 cited: Mobile radio interface layer 3 specification spec:04.08
TS 04.13: Performance Requirements on Mobile Radio Interface spec:04.13
TS 04.56: GSM Cordless Telephony System (CTS), (Phase 1) CTS Radio Interface Layer 3 Specification spec:04.56
TS 04.57: GSM Cordless Telephony System (CTS), (Phase 1) CTS CTS supervising system Layer 3 Specification spec:04.57
TS 04.64: General Packet Radio Service (GPRS); Mobile Station - Serving GPRS Support Node (MS-SGSN) Logical Link Control (LLC) layer specification spec:04.64
TS 04.65: General Packet Radio Service (GPRS); Mobile Station (MS) - Serving GPRS Support Node (SGSN); Subnetwork Dependent Convergence Protocol (SNDCP) spec:04.65
TS 04.68: Group Call Control (GCC) Protocol spec:04.68
TS 04.69: Broadcast Call Control (BCC) protocol spec:04.69
TS 09.08 cited: Application of the Base Station System Application Part (BSSAP) on the E-Interface spec:09.08
TR 21.904 cited: User Equipment (UE) capability requirements spec:21.904
TR 21.910: Multi-mode UE issues; categories, principles and procedures spec:21.910
TS 23.014: Support of Dual Tone Multi-Frequency (DTMF) signalling spec:23.014
TS 23.034: High Speed Circuit Switched Data (HSCSD); Stage 2 spec:23.034
TS 23.038: Alphabets and language-specific information spec:23.038
TR 23.039: Interface Protocols for the connection of Short Message Service Centers (SMSCs) to Short Message Entities (SMEs) spec:23.039
TS 23.040: Technical realization of the Short Message Service (SMS) spec:23.040
TS 23.041: Technical realization of Cell Broadcast Service (CBS) spec:23.041
TS 23.042: Compression algorithm for text messaging services spec:23.042
TS 23.108: Mobile radio interface layer 3 specification, core network protocols; Stage 2 spec:23.108
TS 23.122 cited: Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode spec:23.122
TS 23.218: IP Multimedia (IM) session handling; IM call model; Stage 2 spec:23.218
TS 23.259: Personal Network Management (PNM); Procedures and information flows; Stage 2 spec:23.259
TR 23.700-10 cited: Study on enhanced IP Multimedia Subsystem (IMS) to 5GC integration Phase 2; CT WG1 aspects spec:23.700-10
TR 23.712: Study on warning status reporting spec:23.712
TR 23.735: Study on enhancements of Public Warning System spec:23.735
TR 23.814: Separating RR and MM specific parts of the MS Classmark spec:23.814
TR 23.972: Circuit switched multimedia telephony spec:23.972
TS 24.002: GSM - UMTS Public Land Mobile Network (PLMN) Access Reference Configuration spec:24.002
TS 24.007 cited: Mobile radio interface signalling layer 3; General Aspects spec:24.007
TS 24.008 cited: Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 spec:24.008
TS 24.011: Point-to-Point (PP) Short Message Service (SMS) support on mobile radio interface spec:24.011
TS 24.103: Telepresence using the IP Multimedia (IM) Core Network (CN) Subsystem (IMS); Stage 3 spec:24.103
TS 24.105: Application specific Congestion control for Data Communication (ACDC) Management Object (MO) spec:24.105
TS 24.109: Bootstrapping interface (Ub) and network application function interface (Ua); Protocol details spec:24.109
TS 24.116: Stage 3 aspects of system architecture enhancements for TV services spec:24.116
TS 24.117: TV service configuration Management Object (MO) spec:24.117
TS 24.139: 3GPP system - fixed broadband access network interworking; Stage 3 spec:24.139
TS 24.141: Presence service using the IP Multimedia (IM) Core Network (CN) subsystem; Stage 3 spec:24.141
TS 24.147: Conferencing using the IP Multimedia (IM) Core Network (CN) subsystem; Stage 3 spec:24.147
TS 24.161: Network-Based IP Flow Mobility (NBIFOM); Stage 3 spec:24.161
TS 24.166: 3GPP IP Multimedia Subsystem (IMS) conferencing Management Object (MO) spec:24.166
TS 24.167: 3GPP IMS Management Object (MO); Stage 3 spec:24.167
TS 24.173: IMS Multimedia telephony communication service and supplementary services; Stage 3 spec:24.173
TS 24.174: Support of multi-device and multi-identity in the IP Multimedia Subsystem (IMS); Stage 3 spec:24.174
TS 24.175: Management Object (MO) for multi-device and multi-identity in the IP Multimedia Subsystem (IMS) spec:24.175
TS 24.182: IP Multimedia Subsystem (IMS) Customized Alerting Tones (CAT); Protocol specification spec:24.182
TS 24.183: IP Multimedia Subsystem (IMS) Customized Ringing Signal (CRS); Protocol specification spec:24.183
TS 24.186: IMS Data Channel applications; Protocol specification spec:24.186
TS 24.193 cited: 5G System;Access Traffic Steering, Switching and Splitting (ATSSS); Stage 3 spec:24.193
TS 24.196: Enhanced Calling Name (eCNAM) spec:24.196
TS 24.206: Voice call continuity between Circuit Switched (CS) and IP Multimedia Subsystem (IMS); Stage 3 spec:24.206
TS 24.216: Communication Continuity Management Object (MO) spec:24.216
TS 24.228: Signalling flows for the IP multimedia call control based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 spec:24.228
TS 24.229 cited: IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 spec:24.229
TS 24.230: IP multimedia call control protocol based on binary-encoded signalling spec:24.230
TS 24.234: 3GPP system to Wireless Local Area Network (WLAN) interworking; WLAN User Equipment (WLAN UE) to network protocols; Stage 3 spec:24.234
TS 24.235: 3GPP System to Wireless Local Area Network (WLAN) interworking Management Object (MO) spec:24.235
TS 24.237: IP Multimedia (IM) Core Network (CN) subsystem IP Multimedia Subsystem (IMS) service continuity; Stage 3 spec:24.237
TS 24.238: Session Initiation Protocol (SIP) based user configuration; Stage 3 spec:24.238
TS 24.239: Flexible Alerting (FA) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification spec:24.239
TS 24.244: Wireless LAN control plane protocol for trusted WLAN access to EPC; Stage 3 spec:24.244
TS 24.247: Messaging service using the IP Multimedia (IM) Core Network (CN) subsystem; Stage 3 spec:24.247
TS 24.250: Protocol for Reliable Data Service; Stage 3 spec:24.250
TS 24.257: Uncrewed Aerial System (UAS) Application Enabler (UAE) layer; Protocol aspects; Stage 3 spec:24.257
TS 24.259: Personal Network Management (PNM); Stage 3 spec:24.259
TS 24.275: Management Object (MO) for Basic Communication Part (BCP) of IMS Multimedia Telephony (MMTEL) communication service spec:24.275
TS 24.279: Combining Circuit Switched (CS) and IP Multimedia Subsystem (IMS) services; Stage 3 spec:24.279
TS 24.281: Mission Critical Video (MCVideo) signalling control; Protocol specification spec:24.281
TS 24.282: Mission Critical Data (MCData) signalling control; Protocol specification spec:24.282
TS 24.283: Mission Critical Location Management (MCLoc); Protocol Specification spec:24.283
TS 24.285: Allowed Closed Subscriber Group (CSG) list; Management Object (MO) spec:24.285
TS 24.286: IP Multimedia (IM) Core Network (CN) subsystem Centralized Services (ICS); Management Object (MO) spec:24.286
TS 24.292: IP Multimedia (IM) Core Network (CN) subsystem Centralized Services (ICS); Stage 3 spec:24.292
TS 24.294: IP Multimedia Subsystem (IMS) Centralized Services (ICS) protocol via I1 interface spec:24.294
TS 24.301 cited: Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 spec:24.301
TS 24.302: Access to the 3GPP Evolved Packet Core (EPC) via non-3GPP access networks; Stage 3 spec:24.302
TS 24.303: Mobility management based on Dual-Stack Mobile IPv6; Stage 3 spec:24.303
TS 24.304: Mobility management based on Mobile IPv4; User Equipment (UE) - foreign agent interface; Stage 3 spec:24.304
TS 24.305: Selective Disabling of 3GPP User Equipment Capabilities (SDoUE) Management Object (MO) spec:24.305
TS 24.312: Access Network Discovery and Selection Function (ANDSF) Management Object (MO) spec:24.312
TS 24.315: IP Multimedia Subsystem (IMS) Operator Determined Barring (ODB); Stage 3: protocol specification spec:24.315
TS 24.322: Tunnelling of IP Multimedia Subsystem (IMS) services over restrictive access networks; Stage 3 spec:24.322
TS 24.323: 3GPP IP Multimedia Subsystem (IMS) service level tracing Management Object (MO) spec:24.323
TS 24.327: Mobility between 3GPP Wireless Local Area Network (WLAN) interworking (I-WLAN) and 3GPP systems; General Packet Radio System (GPRS) and 3GPP I-WLAN aspects; Stage 3 spec:24.327
TS 24.333: Proximity-services (ProSe) Management Objects (MO) spec:24.333
TS 24.334: Proximity-services (ProSe) User Equipment (UE) to ProSe function protocol aspects; Stage 3 spec:24.334
TS 24.337: IP Multimedia (IM) Core Network (CN) subsystem IP Multimedia Subsystem (IMS) inter-UE transfer; Stage 3 spec:24.337
TS 24.341: Support of SMS over IP networks; Stage 3 spec:24.341
TS 24.368: Non-Access Stratum (NAS) configuration Management Object (MO) spec:24.368
TS 24.369 cited: Ambient IoT Non-Access-Stratum (AIoT NAS) protocol for 5G System (5GS); Stage 3 spec:24.369
TS 24.371: Web Real-Time Communications (WebRTC) access to the IP Multimedia (IM) Core Network (CN) subsystem (IMS); Stage 3; Protocol specification spec:24.371
TS 24.379 cited: Mission Critical Push To Talk (MCPTT) call control; Protocol specification spec:24.379
TS 24.380: Mission Critical Push To Talk (MCPTT) media plane control; Protocol specification spec:24.380
TS 24.381: Mission Critical Push To Talk (MCPTT) group management; Protocol specification spec:24.381
TS 24.382: Mission Critical Push To Talk (MCPTT) identity management; Protocol specification spec:24.382
TS 24.383: Mission Critical Push To Talk (MCPTT) Management Object (MO) spec:24.383
TS 24.384: Mission Critical Push To Talk (MCPTT) configuration management; Protocol specification spec:24.384
TS 24.385: V2X services Management Object (MO) spec:24.385
TS 24.386: User Equipment (UE) to V2X control function; protocol aspects; Stage 3 spec:24.386
TS 24.390: Unstructured Supplementary Service Data (USSD) using IP Multimedia (IM) Core Network (CN) subsystem IMS; Stage 3 spec:24.390
TS 24.391: Unstructured Supplementary Service Data (USSD) using IP Multimedia (IM) Core Network (CN) subsystem (IMS) Management Object (MO) spec:24.391
TS 24.392: Application enablement aspects for MMTel; Protocol specification spec:24.392
TS 24.403: TISPAN; IP Multimedia Call Control Protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP) Stage 3 [3GPP TS 24.229 (Release 7), modified] spec:24.403
TS 24.404: TISPAN; PSTN/ISDN simulation services: Communication Diversion (CDIV); Protocol specification spec:24.404
TS 24.405: TISPAN; PSTN/ISDN simulation services: Conference (CONF); Protocol specification spec:24.405
TS 24.406: TISPAN; PSTN/ISDN simulation services; Message Waiting Indication (MWI): Protocol specification spec:24.406
TS 24.407: TISPAN; PSTN/ISDN simulation services; Originating Identification Presentation (OIP) and Originating Identification Restriction (OIR); Protocol specification spec:24.407
TS 24.408: TISPAN; PSTN/ISDN simulation services Terminating Identification Presentation (TIP) and Terminating Identification Restriction (TIR); Protocol specification spec:24.408
TS 24.410: TISPAN; NGN Signalling Control Protocol; Communication HOLD (HOLD) PSTN/ISDN simulation services; Protocol specification spec:24.410
TS 24.411: TISPAN; PSTN/ISDN simulation services: Anonymous Communication Rejection (ACR) and Communication Barring (CB); Protocol specification spec:24.411
TS 24.416: TISPAN; PSTN/ISDN simulation services; Malicious Communication Identification (MCID); Protocol specification spec:24.416
TS 24.417: Management Object (MO) for Originating Identification Presentation (OIP) and Originating Identification Restriction (OIR) using IP Multimedia (IM) Core Network (CN) subsystem spec:24.417
TS 24.423: TISPAN; PSTN/ISDN simulation services; Extensible Markup Language (XML) Configuration Access Protocol (XCAP) over the Ut interface for Manipulating NGN PSTN/ISDN Simulation Services spec:24.423
TS 24.424: Management Object (MO) for Extensible Markup Language (XML) Configuration Access Protocol (XCAP) over the Ut interface for Manipulating Supplementary Services (SS) spec:24.424
TS 24.428: TISPAN; Common Basic Communication procedures; Protocol specification spec:24.428
TS 24.429: TISPAN; PSTN/ISDN simulation services: Explicit Communication Transfer (ECT); Protocol specification spec:24.429
TS 24.430: TISPAN; Presence Service Capability; Protocol Specification [3GPP TS 24.141 V7.0.0, modified and OMA-TS-Presence_SIMPLE-V1_0, modified] spec:24.430
TS 24.441: TISPAN; Messaging service using the IP Multimedia (IM) Core Network (CN) subsystem; Stage 3: Protocol specifications [Endorsement of 3GPP TS 24.247 Release 6] spec:24.441
TS 24.447: TISPAN; NGN IMS Supplementary Services; Advice Of Charge (AOC) spec:24.447
TS 24.451: TISPAN; Support of SMS and MMS over NGN IMS subsystem; Stage 3 [Endorsement of 3GPP TS 24.341 Release 7] spec:24.451
TS 24.454: TISPAN; PSTN/ISDN simulation services; Protocol specification Closed User Group (CUG) spec:24.454
TS 24.481: Mission Critical Services (MCS) group management; Protocol specification spec:24.481
TS 24.482: Mission Critical Services (MCS) identity management; Protocol specification spec:24.482
TS 24.483: Mission Critical Services (MCS) Management Object (MO) spec:24.483
TS 24.484: Mission Critical Services (MCS) configuration management; Protocol specification spec:24.484
TS 24.486: Vehicle-to-Everything (V2X) Application Enabler (VAE) layer; Protocol aspects; Stage 3 spec:24.486
TS 24.501 cited: Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 spec:24.501
TS 24.502 cited: Access to the 3GPP 5G Core Network (5GCN) via non-3GPP access networks spec:24.502
TS 24.503: TISPAN; IP Multimedia Call Control Protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP) Stage 3 [3GPP TS 24.229 (Release 7), modified] spec:24.503
TS 24.504: TISPAN; PSTN/ISDN simulation services: Communication Diversion (CDIV); Protocol specification spec:24.504
TS 24.505: TISPAN; PSTN/ISDN simulation services: Conference (CONF); Protocol specification spec:24.505
TS 24.508: TISPAN; PSTN/ISDN simulation services Terminating Identification Presentation (TIP) and Terminating Identification Restriction (TIR); Protocol specification spec:24.508
TS 24.514: Ranging based services and sidelink positioning in 5G system(5GS); Stage 3 spec:24.514
TS 24.516: TISPAN; PSTN/ISDN simulation services; Malicious Communication Identification (MCID); Protocol specification spec:24.516
TS 24.519: 5G System (5GS); Time-Sensitive Networking (TSN) Application Function (AF) to Device-Side TSN Translator (DS-TT) and Network-Side TSN Translator (NW-TT) protocol aspects; Stage 3 spec:24.519
TS 24.523: Core and enterprise Next Generation Network (NGN) interaction scenarios; Architecture and functional description spec:24.523
TS 24.524: Hosted enterprise services; Architecture, functional description and signalling spec:24.524
TS 24.525: Business trunking; Architecture and functional description spec:24.525
TS 24.526 cited: User Equipment (UE) policies for 5G System (5GS); Stage 3 spec:24.526
TS 24.528: TISPAN; Common Basic Communication procedures; Protocol specification spec:24.528
TS 24.529: TISPAN; PSTN/ISDN simulation services: Explicit Communication Transfer (ECT); Protocol specification spec:24.529
TS 24.535: 5G System (5GS); Device-Side Time Sensitive Networking (TSN) Translator (DS-TT) to Network-Side TSN Translator (NW-TT) protocol aspects; Stage 3 spec:24.535
TS 24.538: Enabling MSGin5G Service; Protocol specification spec:24.538
TS 24.539: 5G System (5GS); Network to TSN translator (TT) protocol aspects; Stage 3 spec:24.539
TS 24.542: Notification management - Service Enabler Architecture Layer for Verticals (SEAL); Protocol specification; spec:24.542
TS 24.543 cited: Data delivery management - Service Enabler Architecture Layer for Verticals (SEAL); Protocol Specification; spec:24.543
TS 24.544: Group Management - Service Enabler Architecture Layer for Verticals (SEAL); Protocol specification spec:24.544
TS 24.545: Location Management - Service Enabler Architecture Layer for Verticals (SEAL); Protocol specification spec:24.545
TS 24.546: Configuration management - Service Enabler Architecture Layer for Verticals (SEAL); Protocol specification spec:24.546
TS 24.547: Identity management - Service Enabler Architecture Layer for Verticals (SEAL); Protocol specification spec:24.547
TS 24.548 cited: Network Resource Management - Service Enabler Architecture Layer for Verticals (SEAL); Protocol specification spec:24.548
TS 24.549: Network slice capability enablement- Service Enabler Architecture Layer for Verticals (SEAL); Protocol specification; Stage 3 spec:24.549
TS 24.550: Digital asset, Spatial mapping and Spatial anchors server - Service Enabler Architecture Layer for Verticals (SEAL); Protocol specification; spec:24.550
TS 24.554 cited: Proximity-services (ProSe) in 5G System (5GS) protocol aspects; Stage 3 spec:24.554
TS 24.555: Proximity-services (ProSe) in 5G System (5GS); User Equipment (UE) policies; Stage 3 spec:24.555
TS 24.558 cited: Enabling Edge Applications; Protocol specification spec:24.558
TS 24.559: Application Data Analytics Enablement Service (ADAES); Stage 3 spec:24.559
TS 24.560: Artificial Intelligence Machine Learning (AIML) Services - Service Enabler Architecture Layer for Verticals (SEAL); Protocol Specification; Stage 3 spec:24.560
TS 24.571: 5G System (5GS); Control plane Location Services (LCS) procedures; Stage 3 spec:24.571
TS 24.572: 5G System (5GS); User plane Location Services (LCS) protocols and procedures; Stage 3 spec:24.572
TS 24.575: 5G System; Multicast/Broadcast UE pre-configuration Management Object (MO) spec:24.575
TS 24.577: Aircraft-to-Everything (A2X) services in 5G System (5GS); Protocol aspects; Stage 3 spec:24.577
TS 24.578: Aircraft-to-Everything (A2X) services in 5G System (5GS); UE policies spec:24.578
TS 24.581: Mission Critical Video (MCVideo) media plane control; Protocol specification spec:24.581
TS 24.582: Mission Critical Data (MCData) media plane control; Protocol specification spec:24.582
TS 24.583: Application layer support for Personal IoT Network (PINAPP); Stage 3 spec:24.583
TS 24.587 cited: Vehicle-to-Everything (V2X) services in 5G System (5GS); Stage 3 spec:24.587
TS 24.588 cited: Vehicle-to-Everything (V2X) services in 5G System (5GS); User Equipment (UE) policies; Stage 3 spec:24.588
TS 24.604: Communication Diversion (CDIV) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification spec:24.604
TS 24.605: Conference (CONF) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification spec:24.605
TS 24.606: Message Waiting Indication (MWI) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification spec:24.606
TS 24.607: Originating Identification Presentation (OIP) and Originating Identification Restriction (OIR) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification spec:24.607
TS 24.608: Terminating Identification Presentation (TIP) and Terminating Identification Restriction (TIR) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification spec:24.608
TS 24.610: Communication HOLD (HOLD) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification spec:24.610
TS 24.611: Anonymous Communication Rejection (ACR) and Communication Barring (CB) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification spec:24.611
TS 24.615: Communication Waiting (CW) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol Specification spec:24.615
TS 24.616: Malicious Communication Identification (MCID) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification spec:24.616
TS 24.623: Extensible Markup Language (XML) Configuration Access Protocol (XCAP) over the Ut interface for Manipulating Supplementary Services spec:24.623
TS 24.628: Common Basic Communication procedures using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification spec:24.628
TS 24.629: Explicit Communication Transfer (ECT) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification spec:24.629
TS 24.642: Completion of Communications to Busy Subscriber (CCBS) and Completion of Communications by No Reply (CCNR) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification spec:24.642
TS 24.647: Advice Of Charge (AOC) using IP Multimedia (IM) Core Network (CN) subsystem spec:24.647
TS 24.654: Closed User Group (CUG) using IP Multimedia (IM) Core Network (CN) subsystem, Protocol Specification spec:24.654
TR 24.801 cited: 3GPP System Architecture Evolution (SAE); CT WG1 aspects spec:24.801
TR 24.803: Study on telepresence using the IP Multimedia (IM) Core Network (CN) Subsystem (IMS); Stage 3 spec:24.803
TR 24.811: Study on the support for minimization of service interruption spec:24.811
TR 24.812: Study on MINT support in EPS for 5G-only national roaming UE spec:24.812
TR 24.819: Protocol impact from providing IMS services via fixed broadband; Stage-3 spec:24.819
TR 24.820: 3GPP system to fixed broadband access network interworking spec:24.820
TR 24.821: Study on PLMN selection for satellite access spec:24.821
TR 24.826: Study on impacts on signalling between User Equipment (UE) and core network from energy saving spec:24.826
TR 24.837: IP Multimedia (IM) Core Network (CN) subsystem inter-UE transfer enhancements; Stage 3 spec:24.837
TR 24.841: Presence service based on Session Initiation Protocol (SIP); Functional models, information flows and protocol details spec:24.841
TR 24.860 cited: Study on NAS protocol for 6G System spec:24.860
TS 24.861: Study on Miscellaneous functions and services for 6G System spec:24.861
TR 24.879: Combining Circuit-Switched (CS) calls and IP Multimedia Subsystem (IMS) sessions spec:24.879
TR 24.880: Media server control using the IP Multimedia (IM) Core Network (CN) subsystem; Stage 3 spec:24.880
TR 24.883: Mission Critical (MC) systems connection to Land Mobile Radio (LMR) systems; Stage-3 spec:24.883
TR 24.890 cited: CT WG1 aspects of 5G; System Phase 1 spec:24.890
TR 24.930: Signalling flows for the session setup in the IP Multimedia core network Subsystem (IMS) based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 spec:24.930
TR 24.969: Business trunking; Next Generation Corporate Network (NGCN) - Next Generation Network (NGN) interfaces implementation guide spec:24.969
TR 24.980: Minimum requirements for support of MCPTT service over the Gm reference point spec:24.980
TS 27.005: Use of Data Terminal Equipment - Data Circuit terminating Equipment (DTE - DCE) interface for Short Message Service (SMS) and Cell Broadcast Service (CBS) spec:27.005
TS 27.007: AT command set for User Equipment (UE) spec:27.007
TS 27.103: Wide Area Network Synchronization spec:27.103
TR 27.903 cited: Discussion of synchronization standards spec:27.903
TS 29.016: General Packet Radio Service (GPRS); Serving GPRS Support Node (SGSN) - Visitors Location Register (VLR); Gs interface network service specification spec:29.016
TS 29.018: General Packet Radio Service (GPRS); Serving GPRS Support Node (SGSN) - Visitors Location Register (VLR); Gs interface layer 3 specification spec:29.018
TS 29.118: Mobility Management Entity (MME) - Visitor Location Register (VLR) SGs interface specification spec:29.118
TS 29.379: Mission Critical Push To Talk (MCPTT) call control interworking with Land Mobile Radio (LMR) systems; Stage-3 spec:29.379
TS 29.380: Mission Critical Push To Talk (MCPTT) media plane control interworking with Land Mobile Radio (LMR) systems; Stage 3 spec:29.380
TS 29.582: Mission Critical Data (MCData) interworking with Land Mobile Radio (LMR) systems; Stage 3 spec:29.582
TR 29.846 cited: Multimedia Broadcast/Multicast Service (MBMS); CN1 procedure description spec:29.846
TR 29.847: Conferencing based on SIP, SDP, and other protocols; Functional models, information flows and protocol details spec:29.847
TR 29.994: Recommended infrastructure measures to overcome specific Mobile Station (MS) and User Equipment (UE) faults spec:29.994
TS 43.068: Voice Group Call Service (VGCS); Stage 2 spec:43.068
TS 43.069: Voice Broadcast Service (VBS); Stage 2 spec:43.069
TS 44.001: Mobile Station - Base Station System (MS - BSS) interface; General aspects and principles spec:44.001
TS 44.013: Performance requirements on the mobile radio interface spec:44.013
TS 44.056: GSM Cordless Telephony System (CTS), Phase 1; CTS radio interface layer 3 specification spec:44.056
TS 44.057: GSM Cordless Telephony System (CTS), Phase 1; CTS supervising system layer 3 specification spec:44.057
TS 44.064: Mobile Station - Serving GPRS Support Node (MS-SGSN); Logical Link Control (LLC) Layer Specification spec:44.064
TS 44.065: Mobile Station (MS) - Serving GPRS Support Node (SGSN); Subnetwork Dependent Convergence Protocol (SNDCP) spec:44.065
TS 44.068: Group Call Control (GCC) protocol spec:44.068
TS 44.069: Broadcast Call Control (BCC) protocol spec:44.069
TS 49.008: Application of the Base Station System Application Part (BSSAP) on the E interface spec:49.008

Counted from the data 81

229 active CT1 specifications cited: 229 How it was counted: rows in the pygppe specification catalogue, table spec where wg='C1' and active='yes', read 2026-08-04 count:ct1-active-specs
16 active CT1 specifications in the 23 series cited: 16 How it was counted: rows in the pygppe specification catalogue, table spec where wg='C1' and active='yes' and specnum starts with '23', read 2026-08-04 count:ct1-active-specs-series-23
175 active CT1 specifications in the 24 series cited: 175 How it was counted: rows in the pygppe specification catalogue, table spec where wg='C1' and active='yes' and specnum starts with '24', read 2026-08-04 count:ct1-active-specs-series-24
30 active CT1 technical reports (TR) cited: 30 How it was counted: rows in the pygppe specification catalogue, table spec where wg='C1' and active='yes' and type='TR', read 2026-08-04 count:ct1-active-tr
199 active CT1 technical specifications (TS) cited: 199 How it was counted: rows in the pygppe specification catalogue, table spec where wg='C1' and active='yes' and type='TS', read 2026-08-04 count:ct1-active-ts
174 documents were agreed at C1-161 cited: 174 How it was counted: rows in the pygppe document database, table tdoc where meeting='C1-161' and status='agreed', read 2026-08-04 count:ct1-agreed-C1-161
71679 CT1 documents of kind 'CR' over the whole record cited: 71679 How it was counted: rows in the pygppe document database, table tdoc where meeting starts with 'C1-' and tdoctype='CR', read 2026-08-04 count:ct1-cr
2835 CT1 documents of kind 'CR' uploaded on or after 2025-08-04 cited: 2835 How it was counted: rows in the pygppe document database, table tdoc where meeting starts with 'C1-' and tdoctype='CR' and uploaded >= '2025-08-04', read 2026-08-04 count:ct1-cr-year
2447 CT1 documents change 23.122 (Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode), over the whole record cited: 2447 How it was counted: rows in the pygppe document database, table tdoc where meeting starts with 'C1-' and crspec='23.122'; rank 4 of the whole group, read 2026-08-04 count:ct1-crspec-all-23.122
3413 CT1 documents change 24.229 (IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3), over the whole record cited: 3413 How it was counted: rows in the pygppe document database, table tdoc where meeting starts with 'C1-' and crspec='24.229'; rank 3 of the whole group, read 2026-08-04 count:ct1-crspec-all-24.229
5422 CT1 documents change 24.301 (Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3), over the whole record cited: 5422 How it was counted: rows in the pygppe document database, table tdoc where meeting starts with 'C1-' and crspec='24.301'; rank 2 of the whole group, read 2026-08-04 count:ct1-crspec-all-24.301
2364 CT1 documents change 24.379 (Mission Critical Push To Talk (MCPTT) call control; Protocol specification), over the whole record cited: 2364 How it was counted: rows in the pygppe document database, table tdoc where meeting starts with 'C1-' and crspec='24.379'; rank 5 of the whole group, read 2026-08-04 count:ct1-crspec-all-24.379
15623 CT1 documents change 24.501 (Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3), over the whole record cited: 15623 How it was counted: rows in the pygppe document database, table tdoc where meeting starts with 'C1-' and crspec='24.501'; rank 1 of the whole group, read 2026-08-04 count:ct1-crspec-all-24.501
2064 CT1 documents change 24.554 (Proximity-services (ProSe) in 5G System (5GS) protocol aspects; Stage 3), over the whole record cited: 2064 How it was counted: rows in the pygppe document database, table tdoc where meeting starts with 'C1-' and crspec='24.554'; rank 6 of the whole group, read 2026-08-04 count:ct1-crspec-all-24.554
144 CT1 documents change 23.122 (Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode), in the twelve months to 2026-08-04 cited: 144 How it was counted: rows in the pygppe document database, table tdoc where meeting starts with 'C1-' and crspec='23.122' and uploaded >= '2025-08-04'; rank 6 of the whole group, read 2026-08-04 count:ct1-crspec-year-23.122
499 CT1 documents change 24.301 (Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3), in the twelve months to 2026-08-04 cited: 499 How it was counted: rows in the pygppe document database, table tdoc where meeting starts with 'C1-' and crspec='24.301' and uploaded >= '2025-08-04'; rank 1 of the whole group, read 2026-08-04 count:ct1-crspec-year-24.301
430 CT1 documents change 24.369 (Ambient IoT Non-Access-Stratum (AIoT NAS) protocol for 5G System (5GS); Stage 3), in the twelve months to 2026-08-04 cited: 430 How it was counted: rows in the pygppe document database, table tdoc where meeting starts with 'C1-' and crspec='24.369' and uploaded >= '2025-08-04'; rank 3 of the whole group, read 2026-08-04 count:ct1-crspec-year-24.369
498 CT1 documents change 24.501 (Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3), in the twelve months to 2026-08-04 cited: 498 How it was counted: rows in the pygppe document database, table tdoc where meeting starts with 'C1-' and crspec='24.501' and uploaded >= '2025-08-04'; rank 2 of the whole group, read 2026-08-04 count:ct1-crspec-year-24.501
143 CT1 documents change 24.543 (Data delivery management - Service Enabler Architecture Layer for Verticals (SEAL); Protocol Specification;), in the twelve months to 2026-08-04 cited: 143 How it was counted: rows in the pygppe document database, table tdoc where meeting starts with 'C1-' and crspec='24.543' and uploaded >= '2025-08-04'; rank 7 of the whole group, read 2026-08-04 count:ct1-crspec-year-24.543
125 CT1 documents change 24.548 (Network Resource Management - Service Enabler Architecture Layer for Verticals (SEAL); Protocol specification), in the twelve months to 2026-08-04 cited: 125 How it was counted: rows in the pygppe document database, table tdoc where meeting starts with 'C1-' and crspec='24.548' and uploaded >= '2025-08-04'; rank 8 of the whole group, read 2026-08-04 count:ct1-crspec-year-24.548
162 CT1 documents change 24.554 (Proximity-services (ProSe) in 5G System (5GS) protocol aspects; Stage 3), in the twelve months to 2026-08-04 cited: 162 How it was counted: rows in the pygppe document database, table tdoc where meeting starts with 'C1-' and crspec='24.554' and uploaded >= '2025-08-04'; rank 5 of the whole group, read 2026-08-04 count:ct1-crspec-year-24.554
165 CT1 documents change 24.860 (Study on NAS protocol for 6G System), in the twelve months to 2026-08-04 cited: 165 How it was counted: rows in the pygppe document database, table tdoc where meeting starts with 'C1-' and crspec='24.860' and uploaded >= '2025-08-04'; rank 4 of the whole group, read 2026-08-04 count:ct1-crspec-year-24.860
197 CT1 documents of kind 'discussion' uploaded on or after 2025-08-04 cited: 197 How it was counted: rows in the pygppe document database, table tdoc where meeting starts with 'C1-' and tdoctype='discussion' and uploaded >= '2025-08-04', read 2026-08-04 count:ct1-discussion-year
2507 CT1 documents of kind 'LS in' over the whole record cited: 2507 How it was counted: rows in the pygppe document database, table tdoc where meeting starts with 'C1-' and tdoctype='LS in', read 2026-08-04 count:ct1-ls-in
7 incoming liaison statements from CT4 in the twelve months to 2026-08-04 cited: 7 How it was counted: rows in the pygppe document database, table tdoc where meeting starts with 'C1-', uploaded >= '2025-08-04', tdoctype='LS in' and the other group is 'CT4', read 2026-08-04 count:ct1-ls-in-from-ct4
15 incoming liaison statements from RAN2 in the twelve months to 2026-08-04 cited: 15 How it was counted: rows in the pygppe document database, table tdoc where meeting starts with 'C1-', uploaded >= '2025-08-04', tdoctype='LS in' and the other group is 'RAN2', read 2026-08-04 count:ct1-ls-in-from-ran2
39 incoming liaison statements from SA2 in the twelve months to 2026-08-04 cited: 39 How it was counted: rows in the pygppe document database, table tdoc where meeting starts with 'C1-', uploaded >= '2025-08-04', tdoctype='LS in' and the other group is 'SA2', read 2026-08-04 count:ct1-ls-in-from-sa2
10 incoming liaison statements from SA3 in the twelve months to 2026-08-04 cited: 10 How it was counted: rows in the pygppe document database, table tdoc where meeting starts with 'C1-', uploaded >= '2025-08-04', tdoctype='LS in' and the other group is 'SA3', read 2026-08-04 count:ct1-ls-in-from-sa3
135 CT1 documents of kind 'LS in' uploaded on or after 2025-08-04 cited: 135 How it was counted: rows in the pygppe document database, table tdoc where meeting starts with 'C1-' and tdoctype='LS in' and uploaded >= '2025-08-04', read 2026-08-04 count:ct1-ls-in-year
3002 CT1 documents of kind 'LS out' over the whole record cited: 3002 How it was counted: rows in the pygppe document database, table tdoc where meeting starts with 'C1-' and tdoctype='LS out', read 2026-08-04 count:ct1-ls-out
8 outgoing liaison statements to CT4 in the twelve months to 2026-08-04 cited: 8 How it was counted: rows in the pygppe document database, table tdoc where meeting starts with 'C1-', uploaded >= '2025-08-04', tdoctype='LS out' and the other group is 'CT4', read 2026-08-04 count:ct1-ls-out-to-ct4
44 outgoing liaison statements to RAN2 in the twelve months to 2026-08-04 cited: 44 How it was counted: rows in the pygppe document database, table tdoc where meeting starts with 'C1-', uploaded >= '2025-08-04', tdoctype='LS out' and the other group is 'RAN2', read 2026-08-04 count:ct1-ls-out-to-ran2
5 outgoing liaison statements to SA1 in the twelve months to 2026-08-04 cited: 5 How it was counted: rows in the pygppe document database, table tdoc where meeting starts with 'C1-', uploaded >= '2025-08-04', tdoctype='LS out' and the other group is 'SA1', read 2026-08-04 count:ct1-ls-out-to-sa1
19 outgoing liaison statements to SA2 in the twelve months to 2026-08-04 cited: 19 How it was counted: rows in the pygppe document database, table tdoc where meeting starts with 'C1-', uploaded >= '2025-08-04', tdoctype='LS out' and the other group is 'SA2', read 2026-08-04 count:ct1-ls-out-to-sa2
108 CT1 documents of kind 'LS out' uploaded on or after 2025-08-04 cited: 108 How it was counted: rows in the pygppe document database, table tdoc where meeting starts with 'C1-' and tdoctype='LS out' and uploaded >= '2025-08-04', read 2026-08-04 count:ct1-ls-out-year
the earliest CT1 meeting on record started 2005-04-25 cited: 2005-04-25 How it was counted: minimum start_day in the pygppe meetings database, table meetings where tb='3GPP CT 1', read 2026-08-04 count:ct1-meetings-first
172 CT1 meetings had started by 2026-08-04 cited: 172 How it was counted: rows in the pygppe meetings database, table meetings where tb='3GPP CT 1' and start_day <= '2026-08-04', read 2026-08-04 count:ct1-meetings-held
184 CT1 meetings are listed, held and planned cited: 184 How it was counted: rows in the pygppe meetings database, table meetings where tb='3GPP CT 1', read 2026-08-04 count:ct1-meetings-listed
33 documents came out of C1-161 as 'merged' cited: 33 How it was counted: rows in the pygppe document database, table tdoc where meeting='C1-161' and status='merged', read 2026-08-04 count:ct1-merged-C1-161
5 new or revised work items were agreed at C1-160 cited: 5 How it was counted: rows of Annex D (List of agreed/approved new and revised Work Items) in the meeting report at /var/www/whatthespec.net/data/data/meetings/ftp.3gpp.org/tsg_ct/WG1_mm-cc-sm_ex-CN1/TSGC1_160_Malta/Report/CT1_160_meeting_report/CT1_160_meeting_report.md, counted 2026-08-04 count:ct1-new-workitems-C1-160
9 new or revised work items were agreed at C1-161 cited: 9 How it was counted: rows of Annex D (List of agreed/approved new and revised Work Items) in the draft meeting report at /var/www/whatthespec.net/data/data/meetings/ftp.3gpp.org/tsg_ct/WG1_mm-cc-sm_ex-CN1/TSGC1_161_Dalian/Report/Draft_CT1_161_meeting_report_v100/Draft_CT1_161_meeting_report_v100.md, counted 2026-08-04 count:ct1-new-workitems-C1-161
the newest CT1 document on record was uploaded 2026-07-31 10:40:59, for meeting C1-162 cited: 2026-07-31 10:40:59 How it was counted: the largest uploaded value in the pygppe document database, table tdoc where meeting starts with 'C1-'; the document is C1-263067, read 2026-08-04 count:ct1-newest-document
53 documents came out of C1-161 as 'noted' cited: 53 How it was counted: rows in the pygppe document database, table tdoc where meeting='C1-161' and status='noted', read 2026-08-04 count:ct1-noted-C1-161
4 CT1 office holders have no end date on record cited: 4 How it was counted: rows with Group='C1' and an empty End field in /var/www/whatthespec.net/data/database/api/officials.jsn, read 2026-08-04 count:ct1-officials-current
44 CT1 terms of office are on record cited: 44 How it was counted: rows with Group='C1' in /var/www/whatthespec.net/data/database/api/officials.jsn, read 2026-08-04 count:ct1-officials-terms
165 people are listed as taking part in C1-160 cited: 165 How it was counted: rows of Annex H (List of participants) in the meeting report at /var/www/whatthespec.net/data/data/meetings/ftp.3gpp.org/tsg_ct/WG1_mm-cc-sm_ex-CN1/TSGC1_160_Malta/Report/CT1_160_meeting_report/CT1_160_meeting_report.md, counted 2026-08-04 count:ct1-participants-C1-160
172 people are listed as taking part in C1-161 cited: 172 How it was counted: rows of Annex H (List of participants) in the draft meeting report at /var/www/whatthespec.net/data/data/meetings/ftp.3gpp.org/tsg_ct/WG1_mm-cc-sm_ex-CN1/TSGC1_161_Dalian/Report/Draft_CT1_161_meeting_report_v100/Draft_CT1_161_meeting_report_v100.md, counted 2026-08-04 count:ct1-participants-C1-161
9772 CT1 documents of kind 'pCR' over the whole record cited: 9772 How it was counted: rows in the pygppe document database, table tdoc where meeting starts with 'C1-' and tdoctype='pCR', read 2026-08-04 count:ct1-pcr
563 CT1 documents of kind 'pCR' uploaded on or after 2025-08-04 cited: 563 How it was counted: rows in the pygppe document database, table tdoc where meeting starts with 'C1-' and tdoctype='pCR' and uploaded >= '2025-08-04', read 2026-08-04 count:ct1-pcr-year
70 documents came out of C1-161 as 'postponed' cited: 70 How it was counted: rows in the pygppe document database, table tdoc where meeting='C1-161' and status='postponed', read 2026-08-04 count:ct1-postponed-C1-161
259 documents came out of C1-161 as 'revised' cited: 259 How it was counted: rows in the pygppe document database, table tdoc where meeting='C1-161' and status='revised', read 2026-08-04 count:ct1-revised-C1-161
136 CT1 documents of kind 'SID new' uploaded on or after 2025-08-04 cited: 136 How it was counted: rows in the pygppe document database, table tdoc where meeting starts with 'C1-' and tdoctype='SID new' and uploaded >= '2025-08-04', read 2026-08-04 count:ct1-sid-new-year
150 CT1 documents from CATT in the twelve months to 2026-08-04: 150 How it was counted: rows in the pygppe document database, table tdoc where meeting starts with 'C1-', uploaded >= '2025-08-04' and source='CATT'; rank 5 of 6, read 2026-08-04 count:ct1-source-year-catt
338 CT1 documents from Ericsson in the twelve months to 2026-08-04 cited: 338 How it was counted: rows in the pygppe document database, table tdoc where meeting starts with 'C1-', uploaded >= '2025-08-04' and source='Ericsson'; rank 2 of 6, read 2026-08-04 count:ct1-source-year-ericsson
447 CT1 documents from Huawei, HiSilicon in the twelve months to 2026-08-04 cited: 447 How it was counted: rows in the pygppe document database, table tdoc where meeting starts with 'C1-', uploaded >= '2025-08-04' and source='Huawei, HiSilicon'; rank 1 of 6, read 2026-08-04 count:ct1-source-year-huawei-hisilicon
317 CT1 documents from Nokia in the twelve months to 2026-08-04 cited: 317 How it was counted: rows in the pygppe document database, table tdoc where meeting starts with 'C1-', uploaded >= '2025-08-04' and source='Nokia'; rank 3 of 6, read 2026-08-04 count:ct1-source-year-nokia
221 CT1 documents from Samsung in the twelve months to 2026-08-04: 221 How it was counted: rows in the pygppe document database, table tdoc where meeting starts with 'C1-', uploaded >= '2025-08-04' and source='Samsung'; rank 4 of 6, read 2026-08-04 count:ct1-source-year-samsung
126 CT1 documents from ZTE in the twelve months to 2026-08-04: 126 How it was counted: rows in the pygppe document database, table tdoc where meeting starts with 'C1-', uploaded >= '2025-08-04' and source='ZTE'; rank 6 of 6, read 2026-08-04 count:ct1-source-year-zte
415 different organisations put a document to CT1 in the twelve months to 2026-08-04 cited: 415 How it was counted: distinct source in the pygppe document database, table tdoc where meeting starts with 'C1-' and uploaded >= '2025-08-04', read 2026-08-04 count:ct1-sources-year
157 of 229 active CT1 specifications have parsed text on this machine cited: 157 How it was counted: folders under /var/www/whatthespec.net/data/friendlyspec/json/<specnum without dots> that match an active CT1 specification, counted 2026-08-04 count:ct1-specs-parsed
149 active CT1 specifications have a Rel-18 version cited: 149 How it was counted: distinct specnum in the catalogue table spec_version joined to spec where wg='C1', active='yes' and release='Rel-18', read 2026-08-04 count:ct1-specs-rel-18
154 active CT1 specifications have a Rel-19 version cited: 154 How it was counted: distinct specnum in the catalogue table spec_version joined to spec where wg='C1', active='yes' and release='Rel-19', read 2026-08-04 count:ct1-specs-rel-19
31 active CT1 specifications have a Rel-20 version cited: 31 How it was counted: distinct specnum in the catalogue table spec_version joined to spec where wg='C1', active='yes' and release='Rel-20', read 2026-08-04 count:ct1-specs-rel-20
237 specifications listed against CT1 cited: 237 How it was counted: rows in the pygppe specification catalogue, table spec where wg='C1', read 2026-08-04 count:ct1-specs-total
133 CT1 meetings have documents on record cited: 133 How it was counted: distinct meeting in the pygppe document database, table tdoc where meeting starts with 'C1-', read 2026-08-04 count:ct1-tdoc-meetings
617 documents were put to C1-161 cited: 617 How it was counted: rows in the pygppe document database, table tdoc where meeting='C1-161', read 2026-08-04 count:ct1-tdocs-C1-161
69 documents are already filed under C1-162 cited: 69 How it was counted: rows in the pygppe document database, table tdoc where meeting='C1-162', read 2026-08-04 count:ct1-tdocs-C1-162
7181 CT1 documents carry no upload date cited: 7181 How it was counted: rows in the pygppe document database, table tdoc where meeting starts with 'C1-' and uploaded is empty, read 2026-08-04 count:ct1-tdocs-no-upload-date
105699 CT1 documents on record cited: 105699 How it was counted: rows in the pygppe document database, table tdoc where meeting starts with 'C1-', read 2026-08-04 count:ct1-tdocs-total
4235 CT1 documents in the twelve months to 2026-08-04 cited: 4235 How it was counted: rows in the pygppe document database, table tdoc where meeting starts with 'C1-' and uploaded >= '2025-08-04', read 2026-08-04 count:ct1-tdocs-year
CT1 documents on record run from 2005 to 2026 cited: 2005-2026 How it was counted: minimum and maximum of the year field inside the stored JSON record in the pygppe document database, table tdoc where meeting starts with 'C1-', read 2026-08-04 count:ct1-tdocs-year-span
87 CT1 documents of kind 'WID new' uploaded on or after 2025-08-04 cited: 87 How it was counted: rows in the pygppe document database, table tdoc where meeting starts with 'C1-' and tdoctype='WID new' and uploaded >= '2025-08-04', read 2026-08-04 count:ct1-wid-new-year
19 documents came out of C1-161 as 'withdrawn' cited: 19 How it was counted: rows in the pygppe document database, table tdoc where meeting='C1-161' and status='withdrawn', read 2026-08-04 count:ct1-withdrawn-C1-161
8 CT1 specifications no longer active cited: 8 How it was counted: rows in the pygppe specification catalogue, table spec where wg='C1' and active<>'yes', read 2026-08-04 count:ct1-withdrawn-specs
142 CT1 documents for the work item 5G_ProSe_Ph3 in the twelve months to 2026-08-04 cited: 142 How it was counted: rows in the pygppe document database, table tdoc where meeting starts with 'C1-', uploaded >= '2025-08-04' and winame='5G_ProSe_Ph3'; rank 6 of 6, read 2026-08-04 count:ct1-workitem-year-5g-prose-ph3
192 CT1 documents for the work item 5GSAT_Ph3_ARCH in the twelve months to 2026-08-04 cited: 192 How it was counted: rows in the pygppe document database, table tdoc where meeting starts with 'C1-', uploaded >= '2025-08-04' and winame='5GSAT_Ph3_ARCH'; rank 3 of 6, read 2026-08-04 count:ct1-workitem-year-5gsat-ph3-arch
420 CT1 documents for the work item AmbientIoT-CT in the twelve months to 2026-08-04 cited: 420 How it was counted: rows in the pygppe document database, table tdoc where meeting starts with 'C1-', uploaded >= '2025-08-04' and winame='AmbientIoT-CT'; rank 1 of 6, read 2026-08-04 count:ct1-workitem-year-ambientiot-ct
170 CT1 documents for the work item FS_6G_NAS_CT in the twelve months to 2026-08-04 cited: 170 How it was counted: rows in the pygppe document database, table tdoc where meeting starts with 'C1-', uploaded >= '2025-08-04' and winame='FS_6G_NAS_CT'; rank 5 of 6, read 2026-08-04 count:ct1-workitem-year-fs-6g-nas-ct
172 CT1 documents for the work item MINT_Ph2 in the twelve months to 2026-08-04 cited: 172 How it was counted: rows in the pygppe document database, table tdoc where meeting starts with 'C1-', uploaded >= '2025-08-04' and winame='MINT_Ph2'; rank 4 of 6, read 2026-08-04 count:ct1-workitem-year-mint-ph2
200 CT1 documents for the work item TEI19 in the twelve months to 2026-08-04 cited: 200 How it was counted: rows in the pygppe document database, table tdoc where meeting starts with 'C1-', uploaded >= '2025-08-04' and winame='TEI19'; rank 2 of 6, read 2026-08-04 count:ct1-workitem-year-tei19
219 named work items received CT1 documents in the twelve months to 2026-08-04 cited: 219 How it was counted: distinct winame in the pygppe document database, table tdoc where meeting starts with 'C1-' and uploaded >= '2025-08-04', read 2026-08-04 count:ct1-workitems-year

Meeting document 21

C1-261459 cited: New WID on CT aspects of Ambient power-enabled Internet of Things – Phase 2 How it was counted: row in the pygppe document database, table tdoc, where name='C1-261459'; listed in Annex D of the C1-160 meeting report, read 2026-08-04 tdoc:C1-261459
C1-261460 cited: New WID on CT aspects of FRMCS Phase 6 How it was counted: row in the pygppe document database, table tdoc, where name='C1-261460'; listed in Annex D of the C1-160 meeting report, read 2026-08-04 tdoc:C1-261460
C1-261599 cited: New WID on CT aspects of SEAL data delivery enabler for vertical applications Phase 3 How it was counted: row in the pygppe document database, table tdoc, where name='C1-261599'; listed in Annex D of the C1-160 meeting report, read 2026-08-04 tdoc:C1-261599
C1-261602 cited: New WID on CT aspects of Slice-based N3IWF selection for 5G ProSe Layer-3 UE-to-Network Relay How it was counted: row in the pygppe document database, table tdoc, where name='C1-261602'; listed in Annex D of the C1-160 meeting report, read 2026-08-04 tdoc:C1-261602
C1-261603 cited: New SID on miscellaneous functions and services for 6G System How it was counted: row in the pygppe document database, table tdoc, where name='C1-261603'; listed in Annex D of the C1-160 meeting report, read 2026-08-04 tdoc:C1-261603
C1-262064 cited: Location-info XML schema correction How it was counted: lowest-numbered agreed change request to 24.379 at C1-161 in the pygppe document database, table tdoc, read 2026-08-04 tdoc:C1-262064
C1-262074 cited: Corrections related to the handling of congestion and routing failure cases when receiving CIoT user data container How it was counted: lowest-numbered agreed change request to 24.501 at C1-161 in the pygppe document database, table tdoc, read 2026-08-04 tdoc:C1-262074
C1-262144 cited: Correction to incorrect attribute definition for SU_MbmsResourceManagement API How it was counted: lowest-numbered agreed change request to 24.548 at C1-161 in the pygppe document database, table tdoc, read 2026-08-04 tdoc:C1-262144
C1-262227 cited: Correction on misaligned naming How it was counted: lowest-numbered agreed change request to 24.369 at C1-161 in the pygppe document database, table tdoc, read 2026-08-04 tdoc:C1-262227
C1-262254 cited: Correction of the UE states while the T3451 is running How it was counted: lowest-numbered agreed change request to 24.301 at C1-161 in the pygppe document database, table tdoc, read 2026-08-04 tdoc:C1-262254
C1-262258 cited: Correction for the messages regarding the prose additional parameters announcement How it was counted: lowest-numbered agreed change request to 24.554 at C1-161 in the pygppe document database, table tdoc, read 2026-08-04 tdoc:C1-262258
C1-262343 cited: Corrections on the Eees_AppContextRelocation API How it was counted: lowest-numbered agreed change request to 24.558 at C1-161 in the pygppe document database, table tdoc, read 2026-08-04 tdoc:C1-262343
C1-262440 cited: New WID on CT aspects of Ambient power-enabled Internet of Things – Phase 2 How it was counted: row in the pygppe document database, table tdoc, where name='C1-262440'; listed in Annex D of the C1-161 meeting report, read 2026-08-04 tdoc:C1-262440
C1-262442 cited: New WID on CT aspects of ProSe Phase 4 How it was counted: row in the pygppe document database, table tdoc, where name='C1-262442'; listed in Annex D of the C1-161 meeting report, read 2026-08-04 tdoc:C1-262442
C1-262554 cited: New WID on CT aspects of Short Message Service to Emergency Response Centre How it was counted: row in the pygppe document database, table tdoc, where name='C1-262554'; listed in Annex D of the C1-161 meeting report, read 2026-08-04 tdoc:C1-262554
C1-262596 cited: New SID on Protocol Enhancements for Emergency Call Robustness How it was counted: row in the pygppe document database, table tdoc, where name='C1-262596'; listed in Annex D of the C1-161 meeting report, read 2026-08-04 tdoc:C1-262596
C1-262597 cited: New WID on Protocol development for Enhanced MC Features Phase 2 How it was counted: row in the pygppe document database, table tdoc, where name='C1-262597'; listed in Annex D of the C1-161 meeting report, read 2026-08-04 tdoc:C1-262597
C1-262610 cited: New SID on miscellaneous functions and services for 6G System How it was counted: row in the pygppe document database, table tdoc, where name='C1-262610'; listed in Annex D of the C1-161 meeting report, read 2026-08-04 tdoc:C1-262610
C1-262611 cited: New WID on Next Generation Real time Communication services Phase 3 How it was counted: row in the pygppe document database, table tdoc, where name='C1-262611'; listed in Annex D of the C1-161 meeting report, read 2026-08-04 tdoc:C1-262611
C1-262612 cited: New WID on CT aspects for integration of satellite components in the 5G Phase 4 How it was counted: row in the pygppe document database, table tdoc, where name='C1-262612'; listed in Annex D of the C1-161 meeting report, read 2026-08-04 tdoc:C1-262612
C1-262617 cited: New WID on CT aspects for application enablement aspects for MMTel Phase 2 How it was counted: row in the pygppe document database, table tdoc, where name='C1-262617'; listed in Annex D of the C1-161 meeting report, read 2026-08-04 tdoc:C1-262617

Meeting 9

C1-156 cited: 3GPPCT1#156 How it was counted: row in the pygppe meetings database, table meetings where tb='3GPP CT 1' and id='60636', read 2026-08-04 meeting:C1-156
C1-157 cited: 3GPPCT1#157 How it was counted: row in the pygppe meetings database, table meetings where tb='3GPP CT 1' and id='60649', read 2026-08-04 meeting:C1-157
C1-158 cited: 3GPPCT1#158 How it was counted: row in the pygppe meetings database, table meetings where tb='3GPP CT 1' and id='60652', read 2026-08-04 meeting:C1-158
C1-159 cited: 3GPPCT1#159 How it was counted: row in the pygppe meetings database, table meetings where tb='3GPP CT 1' and id='60738', read 2026-08-04 meeting:C1-159
C1-160 cited: 3GPPCT1#160 How it was counted: row in the pygppe meetings database, table meetings where tb='3GPP CT 1' and id='60739', read 2026-08-04 meeting:C1-160
C1-161 cited: 3GPPCT1#161 How it was counted: row in the pygppe meetings database, table meetings where tb='3GPP CT 1' and id='60740', read 2026-08-04 meeting:C1-161
C1-162 cited: 3GPPCT1#162 How it was counted: row in the pygppe meetings database, table meetings where tb='3GPP CT 1' and id='60741', read 2026-08-04 meeting:C1-162
C1-163 cited: 3GPPCT1#163 How it was counted: row in the pygppe meetings database, table meetings where tb='3GPP CT 1' and id='60742', read 2026-08-04 meeting:C1-163
C1-164 cited: 3GPPCT1#164 How it was counted: row in the pygppe meetings database, table meetings where tb='3GPP CT 1' and id='60743', read 2026-08-04 meeting:C1-164

Page on the standards body's own site 7

The CT1 file area on the 3GPP server cited: Every CT1 meeting folder, its documents, agendas and reports. How it was counted: pygppe builds this address from its own group table (libs/pygpp_storage_core/pygpp_storage_core/wgs.py, key CT1, field http_base); address checked against pygppe's source 2026-08-04 page:ct1-file-area
The CT1 list of office holders cited: Chair, vice chairs and secretary, term by term. How it was counted: pygppe libs/pygpp/pygpp_officials.py:335 builds exactly this address for every group; address checked against pygppe's source 2026-08-04 page:ct1-officials-history
The CT1 mirror area on the 3GPP server cited: The folder pygppe itself mirrors CT1 from. How it was counted: pygppe group table, key CT1, field sync_http (libs/pygpp_storage_core/pygpp_storage_core/wgs.py:335); address checked against pygppe's source 2026-08-04 page:ct1-sync-area
The 3GPP specification status report cited: The page the specification catalogue used here is built from. How it was counted: pygppe libs/pygpp/pygpp_globals.py:134, glob['3gpp_specs_url']; address checked against pygppe's source 2026-08-04 page:spec-status-report
The 3GPP work plan cited: The list of work items every group's documents point at. How it was counted: pygppe libs/pygpp/pygpp_globals.py:133, glob['3gpp_wp_url']; address checked against pygppe's source 2026-08-04 page:work-plan
CT1 documents on whatthespec.net cited: The searchable document list this register was counted from. How it was counted: pygppe bin/useralarms/links.py:38 builds a meeting's document page this way; address checked against pygppe's source 2026-08-04 page:wts-ct1-documents
The 3GPP meeting calendar on whatthespec.net cited: Every meeting of every group, held and planned. How it was counted: pygppe bin/useralarms/links.py:42; address checked against pygppe's source 2026-08-04 page:wts-meetings

Official 4

CT1 Chair: CHAPONNIERE, Lena cited: CHAPONNIERE, Lena, Qualcomm How it was counted: the row with Group='C1', Position='Chair' and no End date in /var/www/whatthespec.net/data/database/api/officials.jsn, read 2026-08-04 official:c1-chair-chaponniere-lena
CT1 Secretary: BIONDIC, Nevenka cited: BIONDIC, Nevenka, (3GPP Support) How it was counted: the row with Group='C1', Position='Secretary' and no End date in /var/www/whatthespec.net/data/database/api/officials.jsn, read 2026-08-04 official:c1-secretary-biondic-nevenka
CT1 Vice Chair: AGHILI, Behrouz cited: AGHILI, Behrouz, Apple How it was counted: the row with Group='C1', Position='Vice Chair' and no End date in /var/www/whatthespec.net/data/database/api/officials.jsn, read 2026-08-04 official:c1-vice-chair-aghili-behrouz
CT1 Vice Chair: WON, Sung Hwan cited: WON, Sung Hwan, Nokia How it was counted: the row with Group='C1', Position='Vice Chair' and no End date in /var/www/whatthespec.net/data/database/api/officials.jsn, read 2026-08-04 official:c1-vice-chair-won-sung-hwan

Report 2

CT1 meeting report C1-160 cited: Meeting ReportforTSG CT WG1meeting: 160 How it was counted: the Markdown conversion pygppe keeps at /var/www/whatthespec.net/data/data/meetings/ftp.3gpp.org/tsg_ct/WG1_mm-cc-sm_ex-CN1/TSGC1_160_Malta/Report/CT1_160_meeting_report/CT1_160_meeting_report.md, read 2026-08-04 report:C1-160
CT1 meeting report C1-161 cited: DRAFT Meeting ReportforTSG CT WG1meeting: 161 How it was counted: the Markdown conversion pygppe keeps at /var/www/whatthespec.net/data/data/meetings/ftp.3gpp.org/tsg_ct/WG1_mm-cc-sm_ex-CN1/TSGC1_161_Dalian/Report/Draft_CT1_161_meeting_report_v100/Draft_CT1_161_meeting_report_v100.md, read 2026-08-04 report:C1-161

Working group 1

CT1 — Mobility, call control, session management (WG1_mm-cc-sm_ex-CN1) cited: 3GPP CT WG1, the core-network protocol group whose documents, specifications and meetings this register is built from How it was counted: the CT1 entry of pygppe's group table in /var/www/whatthespec.net/pygppe/site/api/admin/3gagenda-wgs.php (field label) and the group map in /var/www/whatthespec.net/pygppe/site/shared/groups_catalog.php; the codes are the ones spec_catalog.spec.wg ('C1'), api.sqlite tdoc.meeting ('C1-…') and portal_meetings.meetings.tb ('3GPP CT 1') actually use, read 2026-08-04 group:ct1