Every question of this course

Q1.1 How long was SA#112, and where was it held?

• Two weeks in Singapore, June 2026
• Four days online only, June 2026
• Four days in Singapore, June 2026

An ordinary plenary of 3GPP SA, 9 to 12 June 2026, in Singapore. 110 of the registrations were for attending online, so it was not an online-only meeting. 3GPP TSG SA#112

Q1.2 What does a plenary do that the working groups do not?

• It signs off finished work and answers letters from other standards bodies
• It runs the tests that prove a feature works
• It writes the specification text

The groups draft. The plenary decides what happens to what they bring, and handles the post from outside 3GPP. SP-112 draft meeting report, version 0.0.5

Q1.3 568 people registered and 365 checked in. Why is the second number the important one?

• Only people who check in may submit documents
• The first number counts guests as well
• Checking in is what keeps a member company's voting rights alive

Registering is not enough on its own. Checking in is tied to keeping voting rights. 365 people checked in and so kept their voting rights

Q1.4 What is the first thing the meeting does?

• Approves its own agenda
• Hears the working groups report
• Reads the letters from other standards bodies

The record says "The agenda was reviewed and approved." before anything else is dealt with. 'The agenda was reviewed and approved.'

Q2.1 How many documents were handled at SA#112, and how many were approved?

• 346 handled, 199 approved
• 199 handled, 68 approved
• 689 handled, 346 approved

346 documents, of which 199 ended the meeting approved, 68 noted and 60 revised. 199 documents ended the meeting 'approved'

Q2.2 What does the status "noted" mean?

• Approved with comments
• Read and filed, with no decision taken
• Sent back to be rewritten

Noted is the weakest of the ten outcomes. 68 documents ended there and none of them changed anything. 68 documents ended the meeting 'noted'

Q2.3 Which release was being written at the time of this meeting?

• Release 19
• Release 20
• Release 21

140 documents carry Release 20 and 487 change requests in packs belong to it. Release 19 was being finished off; Release 21 had only a timeline. 140 documents belong to Rel-20

Q2.4 The data holds both 689 and 673 change requests. What should you do?

• Use 689, the larger and therefore fuller count
• Say which of the two you mean, because they answer different questions
• Treat the difference as an error in the record

689 comes from splitting the specification column of every change request and pack; 673 is the sum of the four release counts, which look only inside packs. 689 individual change requests

Q3.1 What are the four things to read about a document at a plenary?

• Its release, its price, its status and its date
• Its number, its length, its language and its author
• Its agenda item, its type, its sender and its result

Those four are what the meeting's document list carries for every paper, and together they say what was asked and what was answered. TdocsByAgenda, the SA#112 document list

Q3.2 SP-260417 was revised and SP-260696 was approved. What is the relationship?

• The first is the work item and the second is its report
• They are two different work items
• They are the same work item, first and second attempt

Both are the new work item description on the ultra low bitrate speech codec for voice over satellite. Only the second number was approved. SP-260696

Q3.3 SP-260379 is one document number. How many change requests does it carry?

• One
• Six
• Twenty-three

It is a pack — 23 separate change requests filed under a single number. Counting packs and counting changes give very different totals. SP-260379

Q3.4 A pack ends the meeting "partially approved". What does that tell you?

• It will be finished at the next meeting
• Some of the changes inside it went through and some did not
• It was approved but has not been published

That is what SP-260387 came out as. "The pack was approved" is a claim to check rather than assume. SP-260387

Q4.1 Which file is the quickest way to see what a whole meeting did?

• The document list
• The chair's welcome pack
• The agenda

It puts every document under its agenda item with the type, the sender and the result, so the outcome of the meeting is on one page. TdocsByAgenda, the SA#112 document list

Q4.2 Why may nothing from this meeting's report be called final or official?

• Because it was written by a language model
• Because 3GPP never publishes final reports
• Because the file is version 0.0.5 and its cover says "Status: Draft - for comment"

The right form of words is "the draft report of the meeting records that…". The machine-written summary is a separate thing again, and is not evidence either. SP-112 draft meeting report, version 0.0.5

Q4.3 284 of the 346 documents get a paragraph of their own in the report. What about the other 62?

• They appear only as rows in the annex tables
• They were not handled at the meeting
• They are covered in the chair's notes

For those 62 a table row is the only evidence of what happened to them. 284 of the 346 documents get a paragraph of their own in the report

Q4.4 What does this data say about what the meeting means for a network operator?

• It says which operators supported each decision
• Nothing — no deployment dates, no product impact, no market view
• It gives deployment dates for Release 20

It is a meeting's paperwork and nothing more. It also carries no vote counts and no per-company positions. 346 documents at SA#112