1 Why a group of groups needs a meeting of its own

1.1 The problem a plenary solves

3GPP's work on services and system architecture is split across six working groups. The split is real: each group drafts its own text, in its own meetings, on its own subjects.

At this meeting all six were named in one breath, when their terms of reference were held over so that they could be compared side by side: "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." ^[2]

Splitting the work is the only way to get it done, and it leaves two things that no group can do for itself. Nobody inside a group can sign off that group's own output. And a decision that crosses two groups — a name, a date, an interface — has no home.

A plenary is the answer to both. It is a meeting whose business is other meetings' business.

You can see that in who sent the paper. The five busiest senders at this meeting were all working groups.

• SA WG5, 66 documents ^[3]
• SA WG3, 57 ^[4]
• SA WG6, 41 ^[5]
• SA WG2, 33 ^[6]
• SA WG4, 28 ^[7]

Across the whole meeting 62 different sources submitted something ^[8]. A source is a working group or a company, and one entry may name several, so the number counts signatures rather than organisations.

1.2 What SA#112 was

The meeting was 3GPP TSG SA#112 — an ordinary plenary of TSG SA, the meeting the SA working groups report into, held in Singapore from 9 to 12 June 2026. Four days.

"Ordinary" is the meeting type the 3GPP portal records for it, not a comment on how eventful it was. It handled 346 documents ^[9].

The meeting is run out of one public folder ^[10], and four files in it do the running: the agenda, the document list, the chair's welcome pack and the secretary's report ^[11]. Chapter How to follow a plenary yourself opens each of them.

1.3 Who ran it, and who was in the room

The draft report of the meeting records the officials in one sentence ^[12]. The chair was Puneet Jain of Intel. The vice chairs were Tao Sun of China Mobile, LaeYoung Kim of LG Electronics and Johannes Achter of Deutsche Telekom. The secretary was Maurice Pope of MCC.

MCC is the support staff. The same initials sign the work plan review SP-260606 and the specifications manager's change request SP-260411 at this meeting, which is a fair picture of what the role covers: the paperwork, not the positions.

Attendance splits three ways, and the split matters:

• 568 people registered ^[13]
• 365 checked in ^[14]
• 110 registered to attend online ^[15]

Checking in is not a formality. It is what keeps a member company's voting rights alive, which is why the checked-in number is the one worth quoting and the registration number is not.

1.4 The four days

The agenda fixes the clock as well as the content. Item 1 is the opening, on Tuesday 9 June 2026 at 1400 local time ^[16]. Item 23 is the close, on Friday 12 June at 1730 or earlier ^[17].

Between those two the meeting worked through 23 top-level items in order ^[18], with one deliberate escape hatch: item 3, "items for early consideration" ^[19]. Anything the chair has agreed in advance can be pulled forward into that item, which is why the biggest cross-group business of SA#112 — the Release 21 timeline, the 6G naming decisions, the codec argument — is recorded there rather than under the items whose titles you would expect.

Twenty-five documents went through early consideration. That is a plenary admitting that its own running order is not the order the important things arrive in.

1.5 What the plenary actually decided

Four kinds of decision run through this one meeting, and the rest of the course is mostly those four:

• Work may start. 30 new work and study items were approved ^[20] and 11 existing ones updated ^[21] — chapter The new work — what the plenary let start.

• Text is finished. 26 specifications and reports were approved ^[22], with 6 more noted for information ^[23].

• Corrections go in. 689 change requests arrived in packs and singly ^[24], landing on 114 specifications ^[25] — chapter The change requests — 689 of them, in packs.

• Letters are answered. 18 came in ^[26] and 2 went out ^[27] — chapter The post — who wrote to 3GPP, and who 3GPP wrote back to.

None of that is drafting. Every one of those decisions is about paper somebody else wrote.

1.6 It does not sit alone

A plenary is not the top of the tree, and SA#112 shows it twice.

The Release 21 timeline was not settled by TSG SA on its own. The draft report records that "SP-260595 was presented in the Joint session and was agreed." ^[1] — a joint session held with the radio plenary, TSG RAN. The document itself is SP-260595, and the status word it ended with is "agreed", not "approved".

The meeting also wrote outwards. The letter fixing 6G terminology went out to the working groups of the other two TSGs SP-260697, and the plenary settled the name of the 6G core network in one line: "It was decided to use '6GC' or '6G CN'." ^[28]

And it pushed one question further up. On the legal side of training an AI speech model the report records "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." ^[29] The Project Co-ordination Group sits above the plenary, and this is what it looks like when a meeting decides something is not its to decide.

1.7 What a plenary cannot do

Three limits show up plainly in this one meeting, and they say as much about the institution as the decisions do.

• It cannot draft. Not one line of specification text was written at SA#112. What arrived was other people's text and other people's proposals, and what left was a status word against each of them.

• It cannot decide what is not its own. The legal question about training data went upwards. The Release 21 timeline was settled with the radio plenary rather than alone SP-260595.

• It cannot outvote anybody. 3GPP works by consensus, and this record carries no vote count anywhere. When a decision was contested, what the report did was write the objection down beside it: "Qualcomm objected to this decision." ^[30]

That last one is the hardest habit for a newcomer. A plenary decision is not a majority. It is a chair judging that the room has stopped arguing, with any remaining objection recorded rather than counted.

1.8 How it opens and how it ends

It opens by deciding what it is going to do. The report's whole account of that is one sentence: "The agenda was reviewed and approved." ^[31] Only after that does anything else happen, which is why chapter How to read a plenary agenda treats the agenda as the index to everything.

The last agenda item is the close, and the report's account of it is again one sentence: "The meeting was then closed." ^[32] Between those two sentences sit four days, 23 agenda items and every decision in this course.

1.9 Where this leads

The next chapter is the meeting as arithmetic — how many documents, of what kind, from whom, ending in which word: SA#112 as arithmetic.

Everything in this course rests on the register of sources built from the meeting's own files, and on the secretary's report, which is a draft and says so on its cover ^[33]. Chapter The report is a draft, and it shows is about that report and how far it can be trusted.