School of Specs CT1 — the group that writes what your…Quick start

How the work moves, and how to follow it · chapter 4 of 4 · 4 minutes

4 How to look at CT1's work yourself, and what the record does not say

Where the documents, meetings, office holders and specifications are published, how fresh the data is, and the questions this record cannot answer.

Built from §1 §2 §3.1 §3.2

4.1 What a document number already tells you

Every CT1 document is numbered C1-… and every CT1 meeting is C1- and a number, so the prefix alone says where a paper came from.

For each document the record keeps the meeting it was put to, who filed it, what kind of document it is, which specification it changes and what became of it C1-262074. That is the whole grid: who, when, to what, and with which outcome word.

4.2 Where to look it up

  • The CT1 file area on the 3GPP server holds every meeting folder, with its documents, agendas and reports [1]

  • CT1's documents are searchable meeting by meeting on whatthespec.net [2]

  • The meeting calendar there lists every meeting, held and planned [3]

  • The 3GPP list of office holders gives every term, not only the current four [4]

  • The 3GPP work plan is the list of work items every document points at [5]

Then there is the document itself, the only one of these that answers a technical question.

Start at the scope, which says what it covers and whom it binds §1; then the definitions §3.1 and the abbreviations §3.2, where a document's own wording beats the general 3GPP vocabulary; then the references, which list the other specifications whose text is pulled into this one §2.

4.3 How fresh this is

The newest CT1 document on record was uploaded on 2026-07-31 at 10:40:59, and it is filed under C1-162 [6] — a meeting that had not started when this course was written. 69 documents were already sitting under it [7]. Paper arrives weeks before the room does.

Not every specification can be read here, either: 157 of the 229 active ones have parsed text on this machine [8], and a clause can be quoted from those and from no others.

7181 CT1 documents carry no upload date at all [9]. Every "last twelve months" figure in this course counts dated rows only, while the all-time figures include the undated ones, so the two kinds of number cannot be divided into one another.

4.4 What the record does not say

  • No reason for anything. There is no agenda, no minutes and no debate behind the outcome word, so why CT1 postponed something is not knowable from here.

  • No text of the letters. The liaison figures in Who writes the words your phone actually sends count letters that crossed, and nothing of what any of them said is in this data.

  • Attendance for two meetings only — 172 people are listed for C1-161 [10] and 165 for C1-160 [11], both counted from the participant list inside the meeting's own report. No other meeting has one, so there is no trend to read.

  • The last meeting's report is not final. The C1-161 report is still a draft [12] where the C1-160 one is approved [13], so every C1-161 number in this course can still move. Say "the draft report of C1-161" or say nothing.

  • No votes, no objections, no tallies of any kind. Nothing here supports "approved by a majority" or "voted through".

  • No past office holders by name. 44 terms of office sit in the file behind the register [14], but only the four current holders are carried by name, so no earlier chair can be named from here.

  • Nothing from C1-162 onwards. Documents are being filed for it, the meeting has not happened, and nothing was agreed, revised or postponed there.

  • No comparison with other working groups. This record was built for CT1 alone and holds no counts for anybody else, so CT1 cannot be called the largest, busiest or fastest of anything.

  • No meaning behind the names. Work item names such as AmbientIoT-CT and MINT_Ph2 are stored exactly as the documents spell them, and what they stand for has to come out of a specification, not out of the record.

Where the numbers in this chapter come from

  1. The CT1 file area on the 3GPP server 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
  2. CT1 documents on whatthespec.net pygppe bin/useralarms/links.py:38 builds a meeting's document page this way; address checked against pygppe's source 2026-08-04
  3. The 3GPP meeting calendar on whatthespec.net pygppe bin/useralarms/links.py:42; address checked against pygppe's source 2026-08-04
  4. The CT1 list of office holders pygppe libs/pygpp/pygpp_officials.py:335 builds exactly this address for every group; address checked against pygppe's source 2026-08-04
  5. The 3GPP work plan pygppe libs/pygpp/pygpp_globals.py:133, glob['3gpp_wp_url']; address checked against pygppe's source 2026-08-04
  6. 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
  7. 69 documents are already filed under C1-162 rows in the pygppe document database, table tdoc where meeting='C1-162', read 2026-08-04
  8. 157 of 229 active CT1 specifications have parsed text on this machine folders under /var/www/whatthespec.net/data/friendlyspec/json/<specnum without dots> that match an active CT1 specification, counted 2026-08-04
  9. 7181 CT1 documents carry no upload date rows in the pygppe document database, table tdoc where meeting starts with 'C1-' and uploaded is empty, read 2026-08-04
  10. 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
  11. 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
  12. 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
  13. 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
  14. 44 CT1 terms of office are on record rows with Group='C1' in /var/www/whatthespec.net/data/database/api/officials.jsn, read 2026-08-04

Every source this course is built on

Check yourself

Answers appear when you pick one, with where they come from.

Q4.1 A CT1 meeting has just ended. What does the record tell you about why a document was postponed?

Q4.2 Which attendance figures exist in this data?

Q4.3 Why can a "last twelve months" number here never be compared straight to an all-time one?

Q4.4 Where does a specification say what its own terms mean?

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.