How the work actually happens · chapter 9 of 14 · 7 minutes
9 One CT1 meeting, by the numbers
The rhythm of CT1's meeting calendar, how much paper one meeting absorbs, what came out of the last one, and why its report cannot yet be quoted as final.
9.1 The rhythm
CT1 has 184 meetings listed, held and planned together [1].
172 of them had started by 2026-08-04 [2], and the earliest one the meetings database holds started 2005-04-25 [3]. That is where the store begins and not where CT1 begins: the group grew out of CN1 CT1 — Mobility, call control, session management (WG1_mm-cc-sm_ex-CN1), and earlier meetings existed without being in this data. 133 meetings have documents attached to them [4].
The last six held and the next three planned show the shape of a year:
| Meeting | Dates | Where | State |
|---|---|---|---|
| C1-156 | 2025-08-25 to 2025-08-29 | Gothenburg Metropolitan Area | held C1-156 |
| C1-157 | 2025-10-13 to 2025-10-17 | Sophia-Antipolis | held C1-157 |
| C1-158 | 2025-11-17 to 2025-11-21 | Dallas | held C1-158 |
| C1-159 | 2026-02-09 to 2026-02-13 | India | held C1-159 |
| C1-160 | 2026-04-13 to 2026-04-17 | Valletta | held C1-160 |
| C1-161 | 2026-05-18 to 2026-05-22 | China | held C1-161 |
| C1-162 | 2026-08-24 to 2026-08-28 | Prague | planned C1-162 |
| C1-163 | 2026-10-12 to 2026-10-16 | Prague | planned C1-163 |
| C1-164 | 2026-11-16 to 2026-11-20 | Calgary | planned C1-164 |
Every one of those runs Monday to Friday, five days. That is visible in the dates and nowhere else in the data — no schedule, no agenda and no session plan is in the register.
The locations move around the world and are recorded at whatever precision the calendar used: "Dallas" and "Valletta" are cities, "India" and "China" are countries, "Gothenburg Metropolitan Area" is neither.
9.2 How much arrives
617 documents were put to C1-161 [5], and 172 people are listed as taking part [6].
Those two numbers together are the whole problem of a working group meeting. Between them the participants have to reach a common position on all 617 documents [5], in five days, without a vote.
The meeting before it, C1-160, lists 165 participants [7].
Those are the only two attendance figures that exist anywhere in this data, so no trend can be described from them — that limit and the reason for it are in What this record cannot tell you.
9.3 What came out of C1-161
C1-161, held 2026-05-18 to 2026-05-22 C1-161, is the last meeting with both a report and a full document record [8].
Each of its 617 documents carries an outcome word:
| Outcome | How many |
|---|---|
| revised | 259 [9] |
| agreed | 174 [10] |
| postponed | 70 [11] |
| noted | 53 [12] |
| merged | 33 [13] |
| withdrawn | 19 [14] |
Two things about that table are worth more than the numbers in it.
More documents were revised than agreed. A revision comes back with a new number, so the same problem occupies several document numbers before it settles. A count of documents is not a count of problems solved.
The six do not add up to 617. Two further outcome words appear in the data, "approved" and "endorsed", and the register carries no count for either. The remainder therefore cannot be recovered by subtraction, and nothing in this course does so.
9.4 The new work agreed at C1-161
Nine new or revised work items were agreed at that meeting [16], against five at C1-160 [17].
A WID is a work item description, the document that opens a piece of work; a SID is a study item description, which opens a study instead.
The nine, each with the company that brought it:
-
New WID on CT aspects of Ambient power-enabled Internet of Things – Phase 2, from Huawei, HiSilicon C1-262440
-
New WID on CT aspects of ProSe Phase 4, from NIST C1-262442
-
New WID on CT aspects of Short Message Service to Emergency Response Centre, from Apple (Guizhou) C1-262554
-
New SID on Protocol Enhancements for Emergency Call Robustness, from Google C1-262596
-
New WID on Protocol development for Enhanced MC Features Phase 2, from UK Home Office C1-262597
-
New SID on miscellaneous functions and services for 6G System, from OPPO and Qualcomm Incorporated C1-262610
-
New WID on Next Generation Real time Communication services Phase 3, from China Mobile C1-262611
-
New WID on CT aspects for integration of satellite components in the 5G Phase 4, from CATT and vivo C1-262612
-
New WID on CT aspects for application enablement aspects for MMTel Phase 2, from China Mobile Com. Corporation C1-262617
Two things stand out of that list. Six of the nine carry "Phase 2", "Phase 3" or "Phase 4" in the title, so most new work at that meeting was a continuation rather than a fresh subject.
And the filers are not all equipment makers: NIST, the UK Home Office and Google appear beside Huawei, HiSilicon, CATT and China Mobile.
C1-160 agreed five in the same way C1-261459, C1-261460, C1-261599, C1-261602, C1-261603. Two of those five carry titles that turn up again at C1-161 — the ambient IoT phase 2 work item, and the study item on 6G, the second time under different filers.
9.5 What one agreed change request looks like
Seven agreed change requests from C1-161 are in the register, one for each specification that meeting changed most:
| Document | Changes | From |
|---|---|---|
| C1-262074 | TS 24.501 | Nokia C1-262074 |
| C1-262254 | TS 24.301 | SHARP C1-262254 |
| C1-262227 | TS 24.369 | Nokia C1-262227 |
| C1-262258 | TS 24.554 | SHARP C1-262258 |
| C1-262144 | TS 24.548 | Huawei, HiSilicon C1-262144 |
| C1-262343 | TS 24.558 | Huawei, HiSilicon C1-262343 |
| C1-262064 | TS 24.379 | Ericsson C1-262064 |
All seven carry the word "correction" in their title.
That is seven documents out of 2835 change requests in the year [18], so it says nothing about the rest — but it does show the texture of an ordinary agreed CR, and the path one of them takes afterwards is traced in From a document number to a published version.
9.6 The next meeting has already started collecting
69 documents are already filed under C1-162 [19], a meeting planned for 2026-08-24 C1-162. The newest CT1 document on record was uploaded 2026-07-31 at 10:40:59, and it is one of them [20].
That is what makes the freshness of this data easy to state: the record is current to within days, and it already contains paperwork for a meeting that has not happened. Nothing about C1-162 or any later meeting may be described as decided, agreed or postponed, because nobody has met yet.
It also shows the rhythm between meetings. C1-161 ended on 2026-05-22 C1-161 and C1-162 begins on 2026-08-24 C1-162.
That is three months in which 69 documents have already been filed [19]. The meeting is where documents get an outcome word, not where the work is done.
9.7 Where this meets the rest of the course
What the meeting is spending its time on across a whole year is The work items that fill a CT1 year. Who it writes to between meetings is Who CT1 writes to, and what the letters count. How to find any of these documents yourself is Following CT1 yourself.
Where the numbers in this chapter come from
- 184 CT1 meetings are listed, held and planned rows in the pygppe meetings database, table meetings where tb='3GPP CT 1', read 2026-08-04
- 172 CT1 meetings had started by 2026-08-04 rows in the pygppe meetings database, table meetings where tb='3GPP CT 1' and start_day <= '2026-08-04', read 2026-08-04
- the earliest CT1 meeting on record started 2005-04-25 minimum start_day in the pygppe meetings database, table meetings where tb='3GPP CT 1', read 2026-08-04
- 133 CT1 meetings have documents on record distinct meeting in the pygppe document database, table tdoc where meeting starts with 'C1-', read 2026-08-04
- 617 documents were put to C1-161 rows in the pygppe document database, table tdoc where meeting='C1-161', read 2026-08-04
- 172 people are listed as taking part in C1-161 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
- 165 people are listed as taking part in C1-160 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
- CT1 meeting report C1-161 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
- 259 documents came out of C1-161 as 'revised' rows in the pygppe document database, table tdoc where meeting='C1-161' and status='revised', read 2026-08-04
- 174 documents were agreed at C1-161 rows in the pygppe document database, table tdoc where meeting='C1-161' and status='agreed', read 2026-08-04
- 70 documents came out of C1-161 as 'postponed' rows in the pygppe document database, table tdoc where meeting='C1-161' and status='postponed', read 2026-08-04
- 53 documents came out of C1-161 as 'noted' rows in the pygppe document database, table tdoc where meeting='C1-161' and status='noted', read 2026-08-04
- 33 documents came out of C1-161 as 'merged' rows in the pygppe document database, table tdoc where meeting='C1-161' and status='merged', read 2026-08-04
- 19 documents came out of C1-161 as 'withdrawn' rows in the pygppe document database, table tdoc where meeting='C1-161' and status='withdrawn', read 2026-08-04
- CT1 meeting report C1-160 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
- 9 new or revised work items were agreed at C1-161 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
- 5 new or revised work items were agreed at C1-160 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
- 2835 CT1 documents of kind 'CR' uploaded on or after 2025-08-04 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
- 69 documents are already filed under C1-162 rows in the pygppe document database, table tdoc where meeting='C1-162', read 2026-08-04
- the newest CT1 document on record was uploaded 2026-07-31 10:40:59, for meeting C1-162 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
Check yourself
Answers appear when you pick one, with where they come from.
Q9.1 How many documents were put to meeting C1-161?
617 documents at one meeting. 174 is how many of them came out agreed, and 4235 is the whole group's document count for the year. 617 documents were put to C1-161
Q9.2 What is the state of the C1-161 meeting report?
The C1-161 report is a draft, so its numbers can still change. The C1-160 report is approved. CT1 meeting report C1-161
Q9.3 How many people are listed as taking part in C1-161?
172 at C1-161 and 165 at C1-160. 415 is a different number — the organisations that filed at least one document across the whole year. 172 people are listed as taking part in C1-161
Q9.4 How many new or revised work items were agreed at C1-161?
Nine at C1-161, against five at the meeting before it. Nineteen is the number of documents withdrawn at C1-161. 9 new or revised work items were agreed at C1-161
Q9.5 Where is CT1 meeting C1-164 planned to be held?
C1-162 and C1-163 are both planned for Prague; C1-164 is Calgary. Valletta is where C1-160 was held in April 2026. C1-164
This chapter was written against TS 24.501 version 20.0.0, and built from a source register generated 2026-08-04. A newer version of the document may say something else.