School of Specs Inside one plenary: TSG SA#112Quick start

A week in one room · chapter 1 of 4 · 4 minutes

1 What happens when a few hundred engineers meet for a week

SA#112 in Singapore, June 2026 — who was there, who ran it, and what a meeting like this is actually for.

1.1 The meeting

3GPP SA met in Singapore for four days, from 9 June 2026 to 12 June 2026. The record calls it an ordinary plenary — a regular meeting of the whole group, number 112 in the series 3GPP TSG SA#112.

568 people registered for it [4] and 365 checked in [5]. Those are different acts: checking in is what keeps a member company's voting rights alive.

110 of the registrations were for attending online [6].

1.2 What such a meeting is for

The detailed drafting is not done here. It is done in the SA working groups, over months, and the plenary is where they bring finished work to be signed off.

The plenary's second job is the post. Other standards bodies write to 3GPP and 3GPP writes back — 18 letters came in at this meeting [7] and 2 went out [8].

1.3 Who brings the work

62 different senders submitted something to this meeting [9]. The five busiest are all SA working groups, and no single company comes close to them.

Sender Documents
SA WG5 66 [10]
SA WG3 57 [11]
SA WG6 41 [12]
SA WG2 33 [13]
SA WG4 28 [14]

There are six such groups, SA WG1 to SA WG6 [15]. Each works through the year on its own subject and arrives at the plenary carrying the result.

What a group works on can be read off the specifications its changes land on, and this record says no more than that: SA WG5 owns TS 28.552, "5G performance measurements" TS 28.552; SA WG2 owns TS 23.501, the architecture of the 5G system TS 23.501.

1.4 Who ran it

The people in the chairs are named in the record, each with the company they come from.

That one sentence carries a warning as well as four names. The chair's surname is spelt "Jaine" there and "Jain" elsewhere in the same document, because the document is a draft that has not been proof-read.

1.5 How the week runs

It opens by settling what it is going to do.

From there everything is handled under one of 23 numbered agenda items [16], and the whole meeting is run from four files kept in one folder [17]: the agenda, the list of documents, the chair's welcome pack and the secretary's report [18].

It ends as plainly as it began.

1.6 What is not decided in the room

Some things a plenary of this kind does not settle on its own, and this meeting shows two of them.

Decisions made with the other groups. SA is one of 3GPP's three top-level groups. The Release 21 timeline was not settled by SA — it was agreed in a joint session with TSG RAN, the radio side [19].

Questions pushed upwards. A 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 instead of being answered here [20].

1.7 One meeting is one meeting

Everything in this course comes out of the paperwork of this single meeting, and the narrative part of that paperwork — the secretary's report — is a draft. Its own cover reads "Status: Draft - for comment" [21].

So nothing here is a description of how 3GPP always works. It is a description of what happened at one meeting, as one draft records it.

Where the numbers in this chapter come from

  1. 'The TSG SA Chair was Mr. Puneet Jaine (Intel), The Vice Chairs were Dr. Tao Sun (China Mobile), Ms. LaeYoung Kim (LG Electronics) and Mr. Johannes Achter (Deutsche Telekom). The Secretary was Mr. Maurice Pope (MCC).' found character for character in SP-112_Draft_Report_v005.md, which is a draft and says so on its cover, read 2026-08-04
  2. 'The agenda was reviewed and approved.' found character for character in SP-112_Draft_Report_v005.md, which is a draft and says so on its cover, read 2026-08-04
  3. 'The meeting was then closed.' found character for character in SP-112_Draft_Report_v005.md, which is a draft and says so on its cover, read 2026-08-04
  4. 568 people registered for the meeting the '568 Entries' line closing the matching annex table of SP-112_Draft_Report_v005.md, read 2026-08-04
  5. 365 people checked in and so kept their voting rights the '365 Entries' line closing the matching annex table of SP-112_Draft_Report_v005.md, read 2026-08-04
  6. 110 people registered to attend online the '110 Entries' line closing the matching annex table of SP-112_Draft_Report_v005.md, read 2026-08-04
  7. 18 incoming liaison statements the '18 Entries' line closing the matching annex table of SP-112_Draft_Report_v005.md, read 2026-08-04
  8. 2 outgoing liaison statements the '2 Entries' line closing the matching annex table of SP-112_Draft_Report_v005.md, read 2026-08-04
  9. 62 different sources submitted documents distinct values of source over the same 346 rows. A source is a working group or a company, and one entry may name several, read 2026-08-04
  10. 66 documents came from SA WG5 sqlite3 /var/www/whatthespec.net/data/database/api/api.sqlite "select count(*) from tdoc where meeting='SP-112' and source="SA WG5";", read 2026-08-04
  11. 57 documents came from SA WG3 sqlite3 /var/www/whatthespec.net/data/database/api/api.sqlite "select count(*) from tdoc where meeting='SP-112' and source="SA WG3";", read 2026-08-04
  12. 41 documents came from SA WG6 sqlite3 /var/www/whatthespec.net/data/database/api/api.sqlite "select count(*) from tdoc where meeting='SP-112' and source="SA WG6";", read 2026-08-04
  13. 33 documents came from SA WG2 sqlite3 /var/www/whatthespec.net/data/database/api/api.sqlite "select count(*) from tdoc where meeting='SP-112' and source="SA WG2";", read 2026-08-04
  14. 28 documents came from SA WG4 sqlite3 /var/www/whatthespec.net/data/database/api/api.sqlite "select count(*) from tdoc where meeting='SP-112' and source="SA WG4";", read 2026-08-04
  15. '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.' found character for character in SP-112_Draft_Report_v005.md, which is a draft and says so on its cover, read 2026-08-04
  16. 23 top-level agenda items rows of the agenda table in SP-260361_SA112_Agenda_v2.md whose item number has no dot in it, read 2026-08-04
  17. The SA#112 document folder the line beginning Tdocweblocation= in the meeting's own TdocsByAgenda.md, read 2026-08-04
  18. Welcome to TSG SA, revision 1
  19. 'SP-260595 was presented in the Joint session and was agreed.' found character for character in SP-112_Draft_Report_v005.md, which is a draft and says so on its cover, read 2026-08-04
  20. '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.' found character for character in SP-112_Draft_Report_v005.md, which is a draft and says so on its cover, read 2026-08-04
  21. SP-112 draft meeting report, version 0.0.5

Every source this course is built on

Check yourself

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

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

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

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

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

This chapter was built from a source register generated 2026-08-04. A fresher build of the register may hold different numbers.