1 What a plenary of 3GPP SA is, and what it can decide

1.1 Why the meeting has to exist

The SA working groups do the drafting. A plenary is where they bring finished work to be signed off, and where 3GPP answers letters from other standards bodies.

That is a narrow job, and it is worth being exact about how narrow. A plenary does not write specification text. It takes documents other people wrote and decides what happens to each one.

Everything in this course is read out of the paperwork of a single meeting. It is not a description of how 3GPP always works, and nothing here should be turned into one.

1.2 The meeting itself

SA#112 was an ordinary plenary of 3GPP SA, held in Singapore over four days, from 9 June 2026 to 12 June 2026 3GPP TSG SA#112.

568 people registered for it ^[4] and 365 checked in ^[5]. The two numbers are not interchangeable — checking in is what keeps a member company's voting rights alive.

110 of those registrations were for attending online ^[6].

The whole meeting is run from four files in one folder ^[7] — the agenda, the document list, the chair's welcome pack and the secretary's report ^[8].

Everything this course says about what was decided comes out of the last of those four, and that file is a draft: its own cover reads "Status: Draft - for comment" ^[9].

1.3 Who ran it

The people in the chairs are named on the record, with the company each one comes from.

That sentence is also the first warning this course gives about its own source. The chair's surname appears as "Jaine" here and as "Jain" elsewhere in the same report. Do not treat a spelling in a draft as authoritative.

1.4 The meeting starts by approving itself

Before any document is handled, the plenary settles what it is going to handle.

That is not a formality worth skipping over. The agenda is the filing system for everything that follows: every document at the meeting sits under one of its items, and a document that has no agenda item has nowhere to be discussed.

The other opening job is the previous meeting's report, and at SA#112 that is where the record first trips over itself. The narrative under agenda item 1.5 reads "The report of meeting SA#111 was approved."; the status line under the same document reads "Not concluded." ^[10]

Both statements are in the same draft. The honest thing to do with a contradiction like that is to report both halves of it, or neither — never the half that reads better.

1.5 It does not sit alone

SA is one of 3GPP's three top-level groups, and some decisions at this meeting were made across them rather than inside SA alone.

Two things at this meeting show that plainly:

• The Release 21 timeline was not settled by SA. It was settled in a joint session with TSG RAN, the group on the radio side — "SP-260595 was presented in the Joint session and was agreed." ^[11]

• The letter fixing 6G terminology went out to the working groups of the other two top-level groups, not only to SA's own SP-260697

1.6 What a plenary hands back

Four kinds of thing leave the room, and all four are visible in this meeting's own numbers.

• Work started. 30 new work items and study items were approved ^[12], and 11 existing ones were updated ^[13]

• Documents finished. 26 specifications and technical reports were approved ^[14]; 6 more were only noted for information ^[15] — a weaker outcome, and a different one

• Corrections put to the meeting. 689 individual change requests ^[16], landing on 114 different specifications ^[17] — what arrived, not what passed, since four packs came out only partially approved ^[18]

• Post answered. 18 liaison statements — letters from other standards bodies — came in ^[19], and 2 went out ^[20]

One kind of thing did not leave the room at all: no work item exception sheets were approved. That annex of the report reads "No entries found." ^[21]

1.7 What a plenary cannot do

Three limits sit on that list, and all three are visible in this meeting's own paperwork.

It does not publish. "Approved" here means approved by TSG SA. Each of the 26 specifications and reports approved here still has to be produced and put on the server, and nothing in this data says when that happened.

It cannot settle everything in the room. The work item on an AI-based speech codec was approved, and the legal question about the data used to train the model went up to the Project Co-ordination Group rather than being answered ^[22].

Its last word is not written yet. The chair's final notes are published after the meeting closes, and they are not in this data at all ^[23]. What this course reads is the draft report and the document list, nothing more.

1.8 And then it stops

The record ends the way it started, in one line.

Between those two sentences sit 346 documents ^[24]. The next chapter counts them.