Inside one plenary: TSG SA#112 · In depth
Every question of this course
All 60 questions on one page, in the order the chapters come. Pick an answer and it tells you at once whether you were right and where the answer lives.
1 Why a group of groups needs a meeting of its own
Q1.1 What does checking in at a 3GPP plenary do for a member company?
568 people registered and 365 checked in, and checking in is what keeps a member company's voting rights alive. 365 people checked in and so kept their voting rights
Q1.2 How long did SA#112 last and where was it held?
The meeting ran in Singapore from 9 to 12 June 2026, and 110 of the 568 registrations were for attending online rather than in the room. 3GPP TSG SA#112
Q1.3 Where was the Release 21 timeline settled?
The draft report records that SP-260595 was presented in the joint session and was agreed, so it was not TSG SA's decision alone. 'SP-260595 was presented in the Joint session and was agreed.'
Q1.4 Which five sources sent the most documents to SA#112?
SA WG5 sent 66, SA WG3 57, SA WG6 41, SA WG2 33 and SA WG4 28. No single company comes close. 66 documents came from SA WG5
Q1.5 What is the first thing the plenary decides?
The draft report records that the agenda was reviewed and approved before anything else was handled. 'The agenda was reviewed and approved.'
2 SA#112 as arithmetic
Q2.1 How many documents were handled at SA#112?
346 documents, and the report's own annex table closes with the same figure, so two independent counts agree. 346 documents at SA#112
Q2.2 The ten status words account for how many of the meeting's documents?
Approved 199, noted 68, revised 60, postponed 5, endorsed 4, partially approved 4, merged 2, withdrawn 2, agreed 1 and replied to 1 add up to exactly 346. 199 documents ended the meeting 'approved'
Q2.3 The change requests of this meeting can be counted two ways, and the two totals differ. Why are both right?
689 comes from splitting the specification column of every change request and pack; the four release counts added together only look inside packs, so they come to less. 689 individual change requests
Q2.4 What is the largest single kind of document at this meeting?
120 of the 346 documents are change-request packs, against 53 new work item descriptions, the next biggest kind. 120 documents of type 'CR pack'
Q2.5 How many of the meeting's documents carry no release at all?
162 documents carry no release — agendas, reports, liaison statements and project management. A plenary is not only about releases. 162 documents carry no release
3 How to read a plenary agenda
Q3.1 Which three agenda items carried most of the meeting's documents?
Item 6 took 80 documents, item 20 took 63 and item 19 took 40 — the three biggest items of the meeting. Agenda item 6: Work Item Descriptions, Study Item Descriptions, Specifications
Q3.2 How many times does the draft report say "There were no contributions to this agenda item."?
40 times, counting sub-items as well as top-level ones. The agenda is built for every possible meeting, not for this one. 40 times the report says 'There were no contributions to this agenda item.'
Q3.3 Agenda item 20 handled 63 documents. How many documents of the meeting belong to Release 20?
Item 20 is the bin for Rel-20 change requests only. Rel-20 documents of every kind number 140. 140 documents belong to Rel-20
Q3.4 What is agenda item 3 for?
Item 3 is "Items for early consideration (Please contact the SA Chair in advance)", and it took 25 documents at this meeting. Agenda item 3: Items for early consideration (Please contact the SA Chair in advance)
Q3.5 Which agenda items are reserved for change requests to a single named release?
Items 10 through 20 are one bin per release, from pre-Rel-10 up to Rel-20. Agenda item 20: Rel-20 CRs
4 The kinds of document, and the ten words that decide them
Q4.1 A document ends the meeting "noted". What was decided about it?
Noted means read and filed, with no decision taken. It is neither acceptance nor rejection, and 68 documents ended that way. 68 documents ended the meeting 'noted'
Q4.2 SP-260417 was revised and SP-260696 was approved. What is the relationship?
Revised means superseded by a new document number. They are one work item on the ultra low bitrate speech codec, and only the second one was approved. SP-260696
Q4.3 What does "endorsed" say that "approved" does not?
Endorsed means supported, but what is endorsed is not specification text. The chair's guidance on the modernisation study is the example. SP-260679
Q4.4 A change-request pack comes out "partially approved". What do you know?
Partially approved means part of the pack went through. The status word tells you the pack was split; it does not tell you where. SP-260387
Q4.5 What happened to the Nokia draft reply on emergency services, SP-260613?
It was a rival draft of the same reply and ended "merged" — folded into another document. Two documents ended the meeting merged. SP-260613
5 Release planning — the timeline, the checkpoint and the names
Q5.1 How many documents were handled under the release planning agenda item?
Agenda item 5 drew three documents. The Release 21 timeline itself was reached through early consideration and settled in the joint session. Agenda item 5: Release Planning
Q5.2 What checkpoint did the plenary set itself?
The draft report records the conclusion as a checkpoint in Dec.26 for RAN-CN other than connectivity services. 'conclusion: checkpoint in Dec.26 for RAN-CN other than connectivity services.'
Q5.3 What did the plenary decide to call the 6G core network?
The draft report records that it was decided to use "6GC" or "6G CN". 'It was decided to use '6GC or 6G CN'.'
Q5.4 What did the plenary say about change requests against frozen releases?
The report notes that care should be taken to agree or endorse CRs against frozen releases at the working group level, especially given existing commercial deployments. 'Care should be taken to agree or endorse CRs against frozen releases in the working group level, especially given the existing commercial deployments.'
Q5.5 How many documents at this meeting belong to Release 21?
Eleven. Release 21 exists at this meeting as a timeline and very little else, against 140 documents for Release 20. 11 documents belong to Rel-21
6 The new work — what the plenary let start
Q6.1 How many new work items and study items were approved at SA#112?
30 new work items and study items were approved, and 11 existing ones were updated. 30 new work items and study items were approved
Q6.2 What did the plenary do about the legal question on AI training data for the speech codec?
The new WID was approved, and the report records that the TSG SA chair is to inform PCG on the issue of 3GPP involvement and legal requirements related to the training dataset. 'TSG SA Chair to inform PCG on this issue of 3GPP involvement and legal requirements related to the dataset needed to train the AI model specific to 3GPP work.'
Q6.3 How did the argument about modernising the specification format end?
The study report and its draft TR were both noted, and the chair's guidance was endorsed — continue the separated ASN.1 trial, and interested companies are encouraged to demonstrate Forge. 'This was endorsed.'
Q6.4 How many work item exception sheets were approved?
The annex of the draft report listing approved exception sheets reads "No entries found." No work item exception sheets were approved
Q6.5 Why were the working groups' terms of reference postponed?
The report records the decision to ask SA WG4, WG5 and WG6 to also submit terms of reference to the next meeting, with WG1, WG2 and WG3 free to update or re-submit theirs. 'It was decided to ask SA WG4, SA WG5 and SA WG6 to also submit ToRs to the next TSG SA meeting and SA WG1, SA WG2 and SA WG3 may update or re-submit the same ToR proposals.'
7 The change requests — 689 of them, in packs
Q7.1 How many separate change requests reached SA#112, counting every token in the specification column?
689 individual change requests, landing on 114 specifications. 120 is the number of packs they mostly travelled in. 689 individual change requests
Q7.2 Which specification took the most change requests at this meeting?
TS 23.482 took 46, ahead of TS 23.502 with 38 and TS 23.369 with 33. TS 23.501 took 29. TS 23.482
Q7.3 How many separate change requests does the single document SP-260379 carry?
SP-260379, the Rel-19 lawful interception pack, carries 23 change requests under one document number and one approval. SP-260379
Q7.4 Which release took the most change requests inside packs?
487 of the change requests inside packs belong to Rel-20, against 143 for Rel-19, 36 for Rel-18 and 7 for Rel-17. 487 change requests in packs belong to Rel-20
Q7.5 How many specifications were touched by change requests at this meeting?
114 distinct specifications appear in the specification column of the meeting's change requests and packs. 114 specifications were changed
8 The post — who wrote to 3GPP, and who 3GPP wrote back to
Q8.1 How many liaison statements came in and how many went out at SA#112?
18 incoming liaison statements and 2 outgoing ones, with 22 documents in total handled under the liaison agenda item. 18 incoming liaison statements
Q8.2 Which incoming letter was the only one answered?
One document of the whole meeting carries the status "replied to" — the ETSI TC EMTEL letter. The reply is SP-260655. SP-260363
Q8.3 What did the Utility Technology Council write to 3GPP about?
Its letter is titled "Preserving a Day-1 6G Evolution Path for Gas and Water Metering and Long-Life LPWA Utility Devices", and it was noted. SP-260382
Q8.4 What happened to the second draft of the emergency-services reply?
A rival draft of the same reply, written by a different company, ended "merged" — folded into the document that went out. SP-260613
Q8.5 Almost every incoming letter ended with which status?
Noted — read and filed, no decision taken. 68 documents of the meeting ended that way and only one letter was replied to. 68 documents ended the meeting 'noted'
9 Release 20 at this meeting, and what the numbers will not say
Q9.1 How many of the meeting's documents belong to Release 20?
140 documents carry Rel-20, against 26 for Rel-19 and 11 for Rel-21. 63 is the number handled under the Rel-20 change-request agenda item, and 487 is the change requests inside packs. 140 documents belong to Rel-20
Q9.2 Which group of documents is larger than Release 20's at this meeting?
162 documents carry no release — agendas, reports, liaison statements, project management. A plenary is not only about releases. 162 documents carry no release
Q9.3 What can you conclude from TS 23.482 having 46 change requests and TS 23.501 having 29?
The count is of change requests. Nothing in this record says how large any one of them is, so the only supported reading is the number of separate corrections submitted. TS 23.482
Q9.4 What does this record say about what any of this means for a network operator?
The data is a meeting's paperwork. There are no deployment dates, no product impact and no market view anywhere in it. 346 documents at SA#112
Q9.5 Release 19 at this meeting shows 26 documents and 143 change requests in packs. What does that pattern mean?
The change requests keep coming while new documents thin out, and TR 21.919, the report summarising every Release 19 feature, was approved at this meeting. SP-260604
10 The report is a draft, and it shows
Q10.1 What does the cover of the SA#112 meeting report say about its status?
The file is SP-112_Draft_Report_v005 and its own cover page gives its status as "Draft - for comment", so nothing in it may be called the official record. SP-112 draft meeting report, version 0.0.5
Q10.2 The draft report says the SA#111 report was approved. What does the status line under the same document say?
The narrative under agenda item 1.5 reads "The report of meeting SA#111 was approved." while the status line under the same document reads "Not concluded." Report both or neither. 'The report of meeting SA#111 was approved.'
Q10.3 How many of the meeting's 346 documents get a paragraph of their own in the report?
284 are narrated. The other 62 appear only as a row in an annex table, so a row is the only evidence of what happened to them. 284 of the 346 documents get a paragraph of their own in the report
Q10.4 What does the report record when a decision is contested?
There is no vote count anywhere in the report. Where the interface-naming decision was contested it records "Qualcomm objected to this decision." and nothing about anyone else's position. 'Qualcomm objected to this decision.'
Q10.5 How should the 224 machine-written document summaries be used?
They are written by a language model, not by 3GPP. They are worth citing as a summary and may never be the source of a claim about what was decided. The machine-written summary of SA#112 on whatthespec.net
11 How to follow a plenary yourself
Q11.1 Which file is the fastest way to see what a meeting did?
TdocsByAgenda lists every document under the agenda item it belongs to, with its type, its source and its result — the whole meeting as one table. TdocsByAgenda, the SA#112 document list
Q11.2 SP-260417 and SP-260696 have the same title. What should you look at?
A document number is not a decision. The first was revised and the second approved; only the status column tells you which one carries the outcome. SP-260417
Q11.3 What does the agenda document carry besides the list of agenda items?
SP-260361 version 2 carries the deadlines, the 23 agenda items, the hour-by-hour time plan and the meeting's own rules on how to request a document number. SP-260361, the SA#112 agenda, version 2
Q11.4 A document appears in the annex table but nowhere in the report's narrative. What do you have?
284 of the 346 documents get a paragraph of their own; for the other 62 the annex row is the only evidence. 284 of the 346 documents get a paragraph of their own in the report
Q11.5 Where do the documents themselves live?
The meeting folder holds the agenda, the report and one zip file per document number. The SA#112 document folder
12 What this record does not tell you
Q12.1 Why can no statement about SA#112 call anything "the official record"?
The file is a draft and says so on its own cover, so the correct wording is "the draft report of the meeting records that…". SP-112 draft meeting report, version 0.0.5
Q12.2 What does this data say about what SA#112 means for a network operator?
The data is a meeting's paperwork and nothing more. Any operator consequence would have to come from somewhere else entirely. 346 documents at SA#112
Q12.3 26 specifications and reports were approved. What does that not tell you?
Approved here means approved by TSG SA. A specification still has to be produced by the support team and put on the server, and nothing in this data says when. 26 specifications and reports were approved
Q12.4 Why does this course have no clause map, glossary or version history?
A course built on SA#112 stands on a source register rather than a document. It may name a specification and link to it, and that is all. The SA#112 document folder
Q12.5 Where are the chair's final notes for this meeting?
The agenda says the chair's notes are published after the meeting closes. They are not in the material behind this course, so nothing here can say what they contain. SP-260361, the SA#112 agenda, version 2