Everything this course is built on

Counted from the data 56

23 top-level agenda items cited

23 How it was counted: rows of the agenda table in SP-260361_SA112_Agenda_v2.md whose item number has no dot in it, read 2026-08-04 count:agenda-items

40 times the report says 'There were no contributions to this agenda item.'

40 How it was counted: occurrences of the sentence 'There were no contributions to this agenda item.' in SP-112_Draft_Report_v005.md. It counts sub-items as well as top-level items, read 2026-08-04 count:agenda-items-empty

346 documents at SA#112 cited

346 How it was counted: sqlite3 /var/www/whatthespec.net/data/database/api/api.sqlite "select count(*) from tdoc where meeting='SP-112';", read 2026-08-04 count:documents

120 documents of type 'CR pack' cited

120 How it was counted: sqlite3 /var/www/whatthespec.net/data/database/api/api.sqlite "select count(*) from tdoc where meeting='SP-112' and tdoctype='CR pack';", read 2026-08-04 count:type-cr-pack

53 documents of type 'WID new' cited

53 How it was counted: sqlite3 /var/www/whatthespec.net/data/database/api/api.sqlite "select count(*) from tdoc where meeting='SP-112' and tdoctype='WID new';", read 2026-08-04 count:type-wid-new

29 documents of type 'report'

29 How it was counted: sqlite3 /var/www/whatthespec.net/data/database/api/api.sqlite "select count(*) from tdoc where meeting='SP-112' and tdoctype='report';", read 2026-08-04 count:type-report

28 documents of type 'draft TR'

28 How it was counted: sqlite3 /var/www/whatthespec.net/data/database/api/api.sqlite "select count(*) from tdoc where meeting='SP-112' and tdoctype='draft TR';", read 2026-08-04 count:type-draft-tr

20 documents of type 'discussion'

20 How it was counted: sqlite3 /var/www/whatthespec.net/data/database/api/api.sqlite "select count(*) from tdoc where meeting='SP-112' and tdoctype='discussion';", read 2026-08-04 count:type-discussion

18 documents of type 'LS in'

18 How it was counted: sqlite3 /var/www/whatthespec.net/data/database/api/api.sqlite "select count(*) from tdoc where meeting='SP-112' and tdoctype='LS in';", read 2026-08-04 count:type-ls-in

14 documents of type 'CR'

14 How it was counted: sqlite3 /var/www/whatthespec.net/data/database/api/api.sqlite "select count(*) from tdoc where meeting='SP-112' and tdoctype='CR';", read 2026-08-04 count:type-cr

13 documents of type 'other'

13 How it was counted: sqlite3 /var/www/whatthespec.net/data/database/api/api.sqlite "select count(*) from tdoc where meeting='SP-112' and tdoctype='other';", read 2026-08-04 count:type-other

10 documents of type 'SID new'

10 How it was counted: sqlite3 /var/www/whatthespec.net/data/database/api/api.sqlite "select count(*) from tdoc where meeting='SP-112' and tdoctype='SID new';", read 2026-08-04 count:type-sid-new

9 documents of type 'SID revised'

9 How it was counted: sqlite3 /var/www/whatthespec.net/data/database/api/api.sqlite "select count(*) from tdoc where meeting='SP-112' and tdoctype='SID revised';", read 2026-08-04 count:type-sid-revised

20 different kinds of document

20 How it was counted: distinct values of tdoctype over the same 346 rows, read 2026-08-04 count:types

199 documents ended the meeting 'approved' cited

199 How it was counted: sqlite3 /var/www/whatthespec.net/data/database/api/api.sqlite "select count(*) from tdoc where meeting='SP-112' and status='approved';", read 2026-08-04 count:status-approved

68 documents ended the meeting 'noted' cited

68 How it was counted: sqlite3 /var/www/whatthespec.net/data/database/api/api.sqlite "select count(*) from tdoc where meeting='SP-112' and status='noted';", read 2026-08-04 count:status-noted

60 documents ended the meeting 'revised' cited

60 How it was counted: sqlite3 /var/www/whatthespec.net/data/database/api/api.sqlite "select count(*) from tdoc where meeting='SP-112' and status='revised';", read 2026-08-04 count:status-revised

5 documents ended the meeting 'postponed' cited

5 How it was counted: sqlite3 /var/www/whatthespec.net/data/database/api/api.sqlite "select count(*) from tdoc where meeting='SP-112' and status='postponed';", read 2026-08-04 count:status-postponed

4 documents ended the meeting 'endorsed' cited

4 How it was counted: sqlite3 /var/www/whatthespec.net/data/database/api/api.sqlite "select count(*) from tdoc where meeting='SP-112' and status='endorsed';", read 2026-08-04 count:status-endorsed

4 documents ended the meeting 'partially approved' cited

4 How it was counted: sqlite3 /var/www/whatthespec.net/data/database/api/api.sqlite "select count(*) from tdoc where meeting='SP-112' and status='partially approved';", read 2026-08-04 count:status-partially-approved

2 documents ended the meeting 'merged' cited

2 How it was counted: sqlite3 /var/www/whatthespec.net/data/database/api/api.sqlite "select count(*) from tdoc where meeting='SP-112' and status='merged';", read 2026-08-04 count:status-merged

2 documents ended the meeting 'withdrawn' cited

2 How it was counted: sqlite3 /var/www/whatthespec.net/data/database/api/api.sqlite "select count(*) from tdoc where meeting='SP-112' and status='withdrawn';", read 2026-08-04 count:status-withdrawn

1 document ended the meeting 'agreed' cited

1 How it was counted: sqlite3 /var/www/whatthespec.net/data/database/api/api.sqlite "select count(*) from tdoc where meeting='SP-112' and status='agreed';", read 2026-08-04 count:status-agreed

1 document ended the meeting 'replied to' cited

1 How it was counted: sqlite3 /var/www/whatthespec.net/data/database/api/api.sqlite "select count(*) from tdoc where meeting='SP-112' and status='replied to';", read 2026-08-04 count:status-replied-to

162 documents carry no release cited

162 How it was counted: sqlite3 /var/www/whatthespec.net/data/database/api/api.sqlite "select count(*) from tdoc where meeting='SP-112' and (release is null or release='');", read 2026-08-04 count:release-no-release

140 documents belong to Rel-20 cited

140 How it was counted: sqlite3 /var/www/whatthespec.net/data/database/api/api.sqlite "select count(*) from tdoc where meeting='SP-112' and release='Rel-20';", read 2026-08-04 count:release-rel-20

26 documents belong to Rel-19 cited

26 How it was counted: sqlite3 /var/www/whatthespec.net/data/database/api/api.sqlite "select count(*) from tdoc where meeting='SP-112' and release='Rel-19';", read 2026-08-04 count:release-rel-19

11 documents belong to Rel-21 cited

11 How it was counted: sqlite3 /var/www/whatthespec.net/data/database/api/api.sqlite "select count(*) from tdoc where meeting='SP-112' and release='Rel-21';", read 2026-08-04 count:release-rel-21

5 documents belong to Rel-18

5 How it was counted: sqlite3 /var/www/whatthespec.net/data/database/api/api.sqlite "select count(*) from tdoc where meeting='SP-112' and release='Rel-18';", read 2026-08-04 count:release-rel-18

2 documents belong to Rel-17

2 How it was counted: sqlite3 /var/www/whatthespec.net/data/database/api/api.sqlite "select count(*) from tdoc where meeting='SP-112' and release='Rel-17';", read 2026-08-04 count:release-rel-17

66 documents came from SA WG5 cited

66 How it was counted: 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 count:source-sa-wg5

57 documents came from SA WG3 cited

57 How it was counted: 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 count:source-sa-wg3

41 documents came from SA WG6 cited

41 How it was counted: 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 count:source-sa-wg6

33 documents came from SA WG2 cited

33 How it was counted: 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 count:source-sa-wg2

28 documents came from SA WG4 cited

28 How it was counted: 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 count:source-sa-wg4

62 different sources submitted documents cited

62 How it was counted: 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 count:sources

689 individual change requests cited

689 How it was counted: the crspec column of every CR and CR pack row of tdoc for meeting='SP-112', split on spaces and counted. Each token is one change request against one specification, read 2026-08-04 count:crs

114 specifications were changed cited

114 How it was counted: distinct tokens of the crspec column over the same CR and CR pack rows, read 2026-08-04 count:cr-specs

487 change requests in packs belong to Rel-20 cited

487 How it was counted: the crrelease field of every entry of the crsinpack list inside the line column of tdoc for meeting='SP-112', read 2026-08-04 count:cr-release-rel-20

143 change requests in packs belong to Rel-19 cited

143 How it was counted: the crrelease field of every entry of the crsinpack list inside the line column of tdoc for meeting='SP-112', read 2026-08-04 count:cr-release-rel-19

36 change requests in packs belong to Rel-18

36 How it was counted: the crrelease field of every entry of the crsinpack list inside the line column of tdoc for meeting='SP-112', read 2026-08-04 count:cr-release-rel-18

7 change requests in packs belong to Rel-17

7 How it was counted: the crrelease field of every entry of the crsinpack list inside the line column of tdoc for meeting='SP-112', read 2026-08-04 count:cr-release-rel-17

284 of the 346 documents get a paragraph of their own in the report cited

284 How it was counted: distinct document numbers matching the pattern 'SP-nnnnnn (' at the start of a line in SP-112_Draft_Report_v005.md. The rest appear only in the annex tables, read 2026-08-04 count:report-narrated

The report's own document list holds 346 entries

346 How it was counted: the '346 Entries' line closing the matching annex table of SP-112_Draft_Report_v005.md, read 2026-08-04 count:report-documents

568 people registered for the meeting cited

568 How it was counted: the '568 Entries' line closing the matching annex table of SP-112_Draft_Report_v005.md, read 2026-08-04 count:registrations

365 people checked in and so kept their voting rights cited

365 How it was counted: the '365 Entries' line closing the matching annex table of SP-112_Draft_Report_v005.md, read 2026-08-04 count:checked-in

110 people registered to attend online cited

110 How it was counted: the '110 Entries' line closing the matching annex table of SP-112_Draft_Report_v005.md, read 2026-08-04 count:online

18 incoming liaison statements cited

18 How it was counted: the '18 Entries' line closing the matching annex table of SP-112_Draft_Report_v005.md, read 2026-08-04 count:ls-in

2 outgoing liaison statements cited

2 How it was counted: the '2 Entries' line closing the matching annex table of SP-112_Draft_Report_v005.md, read 2026-08-04 count:ls-out

26 specifications and reports were approved cited

26 How it was counted: the '26 Entries' line closing the matching annex table of SP-112_Draft_Report_v005.md, read 2026-08-04 count:specs-approved

6 specifications and reports were noted for information cited

6 How it was counted: the '6 Entries' line closing the matching annex table of SP-112_Draft_Report_v005.md, read 2026-08-04 count:specs-information

120 change-request packs

120 How it was counted: the '120 Entries' line closing the matching annex table of SP-112_Draft_Report_v005.md, read 2026-08-04 count:cr-packs-listed

30 new work items and study items were approved cited

30 How it was counted: the '30 Entries' line closing the matching annex table of SP-112_Draft_Report_v005.md, read 2026-08-04 count:wids-approved

11 work items and study items were updated cited

11 How it was counted: the '11 Entries' line closing the matching annex table of SP-112_Draft_Report_v005.md, read 2026-08-04 count:wids-updated

No work item exception sheets were approved

0 How it was counted: annex F.2 of SP-112_Draft_Report_v005.md, which reads 'No entries found.', read 2026-08-04 count:exception-sheets

224 of the meeting's documents have a machine-written summary cited

224 How it was counted: rows of table tdoc_summaries in summaries.db where meeting_id='TSGS_112_Singapore_2026-06', read 2026-08-04 count:pygppe-tdoc-summaries

Meeting document 34

SP-260361 cited

Agenda for TSG SA#112 approved How it was counted: row name='SP-260361' of table tdoc in api.sqlite; the status is the value that column carries, not a paraphrase, read 2026-08-04 tdoc:SP-260361

SP-260362

Draft report of TSG SA meeting #111 approved How it was counted: row name='SP-260362' of table tdoc in api.sqlite; the status is the value that column carries, not a paraphrase, read 2026-08-04 tdoc:SP-260362

SP-260595

Release 21 Timeline agreed How it was counted: row name='SP-260595' of table tdoc in api.sqlite; the status is the value that column carries, not a paraphrase, read 2026-08-04 tdoc:SP-260595

SP-260697

LS on 6G terminology approved How it was counted: row name='SP-260697' of table tdoc in api.sqlite; the status is the value that column carries, not a paraphrase, read 2026-08-04 tdoc:SP-260697

SP-260655 cited

Reply LS on accessibility parameters in emergency communications approved How it was counted: row name='SP-260655' of table tdoc in api.sqlite; the status is the value that column carries, not a paraphrase, read 2026-08-04 tdoc:SP-260655

SP-260613 cited

[DRAFT] LS on study item on additional capabilities for emergency services merged How it was counted: row name='SP-260613' of table tdoc in api.sqlite; the status is the value that column carries, not a paraphrase, read 2026-08-04 tdoc:SP-260613

SP-260363 cited

LS from ETSI TC EMTEL: Accessibility parameters in emergency communications replied to How it was counted: row name='SP-260363' of table tdoc in api.sqlite; the status is the value that column carries, not a paraphrase, read 2026-08-04 tdoc:SP-260363

SP-260372

LS from SA WG2: LS on 6G Architecture Study Status noted How it was counted: row name='SP-260372' of table tdoc in api.sqlite; the status is the value that column carries, not a paraphrase, read 2026-08-04 tdoc:SP-260372

SP-260385

LS from NGMN Alliance: '6G Deployment Timeframe Considerations', Version 1.0 noted How it was counted: row name='SP-260385' of table tdoc in api.sqlite; the status is the value that column carries, not a paraphrase, read 2026-08-04 tdoc:SP-260385

SP-260382

LS from Utility Technology Council: Preserving a Day-1 6G Evolution Path for Gas and Water Metering and Long-Life LPWA Utility Devices noted How it was counted: row name='SP-260382' of table tdoc in api.sqlite; the status is the value that column carries, not a paraphrase, read 2026-08-04 tdoc:SP-260382

SP-260584

Ensuring a Secure by Design 6G System noted How it was counted: row name='SP-260584' of table tdoc in api.sqlite; the status is the value that column carries, not a paraphrase, read 2026-08-04 tdoc:SP-260584

SP-260643 cited

Ensuring a Secure by Design 6G System withdrawn How it was counted: row name='SP-260643' of table tdoc in api.sqlite; the status is the value that column carries, not a paraphrase, read 2026-08-04 tdoc:SP-260643

SP-260406

6G Specification Modernisation Study Item Report noted How it was counted: row name='SP-260406' of table tdoc in api.sqlite; the status is the value that column carries, not a paraphrase, read 2026-08-04 tdoc:SP-260406

SP-260407

3GPP TR 21.802 v1.2.0 noted How it was counted: row name='SP-260407' of table tdoc in api.sqlite; the status is the value that column carries, not a paraphrase, read 2026-08-04 tdoc:SP-260407

SP-260544

Views on Modernization of Spec Format & Procedures for 6G noted How it was counted: row name='SP-260544' of table tdoc in api.sqlite; the status is the value that column carries, not a paraphrase, read 2026-08-04 tdoc:SP-260544

SP-260600

Demonstrations and Trialling of Git and 3GPP FORGE for 3GPP specifications and CRs noted How it was counted: row name='SP-260600' of table tdoc in api.sqlite; the status is the value that column carries, not a paraphrase, read 2026-08-04 tdoc:SP-260600

SP-260679

Guidance on FS_6G_SPECS work endorsed How it was counted: row name='SP-260679' of table tdoc in api.sqlite; the status is the value that column carries, not a paraphrase, read 2026-08-04 tdoc:SP-260679

SP-260417 cited

New WID on Ultra Low Bitrate Speech Codec for Voice over GEO revised How it was counted: row name='SP-260417' of table tdoc in api.sqlite; the status is the value that column carries, not a paraphrase, read 2026-08-04 tdoc:SP-260417

SP-260696 cited

New WID on Ultra Low Bitrate Speech Codec for Voice over GEO approved How it was counted: row name='SP-260696' of table tdoc in api.sqlite; the status is the value that column carries, not a paraphrase, read 2026-08-04 tdoc:SP-260696

SP-260654 cited

New SID: Study on additional capabilities for emergency communications approved How it was counted: row name='SP-260654' of table tdoc in api.sqlite; the status is the value that column carries, not a paraphrase, read 2026-08-04 tdoc:SP-260654

SP-260663 cited

New WID on Post-quantum Cryptography Migration approved How it was counted: row name='SP-260663' of table tdoc in api.sqlite; the status is the value that column carries, not a paraphrase, read 2026-08-04 tdoc:SP-260663

SP-260664 cited

New WID on Withdrawal of Rel-18 and Rel-19 Specification of 256bit Cryptographic Algorithm ScHemes approved How it was counted: row name='SP-260664' of table tdoc in api.sqlite; the status is the value that column carries, not a paraphrase, read 2026-08-04 tdoc:SP-260664

SP-260690

New SID: Study on 3GPP Capability Exposure approved How it was counted: row name='SP-260690' of table tdoc in api.sqlite; the status is the value that column carries, not a paraphrase, read 2026-08-04 tdoc:SP-260690

SP-260685

New WID: Application enablement for satellite access enabled 5G services Phase 4 approved How it was counted: row name='SP-260685' of table tdoc in api.sqlite; the status is the value that column carries, not a paraphrase, read 2026-08-04 tdoc:SP-260685

SP-260692 cited

Presentation of Report to TSG: TR 23.700-19: 'Study on Integration of satellite components in the 5G architecture; Phase 4' (FS_5GSAT_Ph4_ARC) Version 2.0.0 approved How it was counted: row name='SP-260692' of table tdoc in api.sqlite; the status is the value that column carries, not a paraphrase, read 2026-08-04 tdoc:SP-260692

SP-260675

New WID: Service Based Management Architecture (SBMA) Phase 4 approved How it was counted: row name='SP-260675' of table tdoc in api.sqlite; the status is the value that column carries, not a paraphrase, read 2026-08-04 tdoc:SP-260675

SP-260656

New SID: Charging enhancements of Ambient power-enabled Internet of Things approved How it was counted: row name='SP-260656' of table tdoc in api.sqlite; the status is the value that column carries, not a paraphrase, read 2026-08-04 tdoc:SP-260656

SP-260604 cited

TR 21.919 v.2.1.0 on Release 19 Summary approved How it was counted: row name='SP-260604' of table tdoc in api.sqlite; the status is the value that column carries, not a paraphrase, read 2026-08-04 tdoc:SP-260604

SP-260606

3GPP Work Plan review at Plenary #112 revised How it was counted: row name='SP-260606' of table tdoc in api.sqlite; the status is the value that column carries, not a paraphrase, read 2026-08-04 tdoc:SP-260606

SP-260411 cited

CR process for the use of 3GPP Forge for normative specification attachments postponed How it was counted: row name='SP-260411' of table tdoc in api.sqlite; the status is the value that column carries, not a paraphrase, read 2026-08-04 tdoc:SP-260411

SP-260470 cited

Updated SA WG1 Terms of reference postponed How it was counted: row name='SP-260470' of table tdoc in api.sqlite; the status is the value that column carries, not a paraphrase, read 2026-08-04 tdoc:SP-260470

SP-260616

Summary for AIML_IMS-MED 'Media aspects for AI/ML in IMS services' endorsed How it was counted: row name='SP-260616' of table tdoc in api.sqlite; the status is the value that column carries, not a paraphrase, read 2026-08-04 tdoc:SP-260616

SP-260379 cited

Rel-19 CRs on Lawful Interception approved How it was counted: row name='SP-260379' of table tdoc in api.sqlite; the status is the value that column carries, not a paraphrase, read 2026-08-04 tdoc:SP-260379

SP-260387 cited

CR Pack on WI 5MBP3 partially approved How it was counted: row name='SP-260387' of table tdoc in api.sqlite; the status is the value that column carries, not a paraphrase, read 2026-08-04 tdoc:SP-260387

Agenda item 23

Agenda item 1: Opening of the Meeting Tuesday, 09 June 2026, 1400 local time

2 of the meeting's documents were handled under agenda item 1 2 How it was counted: the agenda table of SP-260361_SA112_Agenda_v2.md for the wording; rows of tdoc whose ainumber starts '1' for the count, read 2026-08-04 ai:1

Agenda item 2: Liaisons Statements

22 of the meeting's documents were handled under agenda item 2 22 How it was counted: the agenda table of SP-260361_SA112_Agenda_v2.md for the wording; rows of tdoc whose ainumber starts '2' for the count, read 2026-08-04 ai:2

Agenda item 3: Items for early consideration (Please contact the SA Chair in advance)

25 of the meeting's documents were handled under agenda item 3 25 How it was counted: the agenda table of SP-260361_SA112_Agenda_v2.md for the wording; rows of tdoc whose ainumber starts '3' for the count, read 2026-08-04 ai:3

Agenda item 4: Reporting from SA Working Groups, other TSGs, and Others

31 of the meeting's documents were handled under agenda item 4 31 How it was counted: the agenda table of SP-260361_SA112_Agenda_v2.md for the wording; rows of tdoc whose ainumber starts '4' for the count, read 2026-08-04 ai:4

Agenda item 5: Release Planning

3 of the meeting's documents were handled under agenda item 5 3 How it was counted: the agenda table of SP-260361_SA112_Agenda_v2.md for the wording; rows of tdoc whose ainumber starts '5' for the count, read 2026-08-04 ai:5

Agenda item 6: Work Item Descriptions, Study Item Descriptions, Specifications

80 of the meeting's documents were handled under agenda item 6 80 How it was counted: the agenda table of SP-260361_SA112_Agenda_v2.md for the wording; rows of tdoc whose ainumber starts '6' for the count, read 2026-08-04 ai:6

Agenda item 7: Specifications

31 of the meeting's documents were handled under agenda item 7 31 How it was counted: the agenda table of SP-260361_SA112_Agenda_v2.md for the wording; rows of tdoc whose ainumber starts '7' for the count, read 2026-08-04 ai:7

Agenda item 8: Study on 3GPP AI/ML Consistency Alignment (FS_AIML_CAL)

0 of the meeting's documents were handled under agenda item 8 0 How it was counted: the agenda table of SP-260361_SA112_Agenda_v2.md for the wording; rows of tdoc whose ainumber starts '8' for the count, read 2026-08-04 ai:8

Agenda item 9: Study on Modernization of Specification Format and Procedures for 6G (FS_6GSpecs)

11 of the meeting's documents were handled under agenda item 9 11 How it was counted: the agenda table of SP-260361_SA112_Agenda_v2.md for the wording; rows of tdoc whose ainumber starts '9' for the count, read 2026-08-04 ai:9

Agenda item 10: Rel-10 and pre Rel-10 CRs

0 of the meeting's documents were handled under agenda item 10 0 How it was counted: the agenda table of SP-260361_SA112_Agenda_v2.md for the wording; rows of tdoc whose ainumber starts '10' for the count, read 2026-08-04 ai:10

Agenda item 11: Rel-11 CRs

0 of the meeting's documents were handled under agenda item 11 0 How it was counted: the agenda table of SP-260361_SA112_Agenda_v2.md for the wording; rows of tdoc whose ainumber starts '11' for the count, read 2026-08-04 ai:11

Agenda item 12: Rel-12 CRs

0 of the meeting's documents were handled under agenda item 12 0 How it was counted: the agenda table of SP-260361_SA112_Agenda_v2.md for the wording; rows of tdoc whose ainumber starts '12' for the count, read 2026-08-04 ai:12

Agenda item 13: Rel-13 CRs

0 of the meeting's documents were handled under agenda item 13 0 How it was counted: the agenda table of SP-260361_SA112_Agenda_v2.md for the wording; rows of tdoc whose ainumber starts '13' for the count, read 2026-08-04 ai:13

Agenda item 14: Rel-14 CRs

0 of the meeting's documents were handled under agenda item 14 0 How it was counted: the agenda table of SP-260361_SA112_Agenda_v2.md for the wording; rows of tdoc whose ainumber starts '14' for the count, read 2026-08-04 ai:14

Agenda item 15: Rel-15 CRs

1 of the meeting's documents were handled under agenda item 15 1 How it was counted: the agenda table of SP-260361_SA112_Agenda_v2.md for the wording; rows of tdoc whose ainumber starts '15' for the count, read 2026-08-04 ai:15

Agenda item 16: Rel-16 CRs

0 of the meeting's documents were handled under agenda item 16 0 How it was counted: the agenda table of SP-260361_SA112_Agenda_v2.md for the wording; rows of tdoc whose ainumber starts '16' for the count, read 2026-08-04 ai:16

Agenda item 17: Rel-17 CRs

7 of the meeting's documents were handled under agenda item 17 7 How it was counted: the agenda table of SP-260361_SA112_Agenda_v2.md for the wording; rows of tdoc whose ainumber starts '17' for the count, read 2026-08-04 ai:17

Agenda item 18: Rel-18 CRs

17 of the meeting's documents were handled under agenda item 18 17 How it was counted: the agenda table of SP-260361_SA112_Agenda_v2.md for the wording; rows of tdoc whose ainumber starts '18' for the count, read 2026-08-04 ai:18

Agenda item 19: Rel-19 CRs

40 of the meeting's documents were handled under agenda item 19 40 How it was counted: the agenda table of SP-260361_SA112_Agenda_v2.md for the wording; rows of tdoc whose ainumber starts '19' for the count, read 2026-08-04 ai:19

Agenda item 20: Rel-20 CRs

63 of the meeting's documents were handled under agenda item 20 63 How it was counted: the agenda table of SP-260361_SA112_Agenda_v2.md for the wording; rows of tdoc whose ainumber starts '20' for the count, read 2026-08-04 ai:20

Agenda item 21: Project Management & TSG SA owned specifications

13 of the meeting's documents were handled under agenda item 21 13 How it was counted: the agenda table of SP-260361_SA112_Agenda_v2.md for the wording; rows of tdoc whose ainumber starts '21' for the count, read 2026-08-04 ai:21

Agenda item 22: Any Other Business

0 of the meeting's documents were handled under agenda item 22 0 How it was counted: the agenda table of SP-260361_SA112_Agenda_v2.md for the wording; rows of tdoc whose ainumber starts '22' for the count, read 2026-08-04 ai:22

Agenda item 23: Close of Meeting Friday, 12 June 2026, 1730 local time (or earlier)

0 of the meeting's documents were handled under agenda item 23 0 How it was counted: the agenda table of SP-260361_SA112_Agenda_v2.md for the wording; rows of tdoc whose ainumber starts '23' for the count, read 2026-08-04 ai:23

Quoted wording 18

'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).' cited

Who ran the meeting. The chair's surname is spelt 'Jaine' here and 'Jain' elsewhere in the same report — the draft has not been proof-read. 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). How it was counted: 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 quote:officials

'The agenda was reviewed and approved.' cited

The plenary approved its own agenda before doing anything else. The agenda was reviewed and approved. How it was counted: 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 quote:agenda-approved

'The report of meeting SA#111 was approved.' cited

The previous plenary's report was approved at this one; the status line under the same document says 'Not concluded.' The report of meeting SA#111 was approved. How it was counted: 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 quote:sa111-report

'SP-260595 was presented in the Joint session and was agreed.' cited

The Release 21 timeline was agreed in the joint session with TSG RAN, not in the SA plenary alone. SP-260595 was presented in the Joint session and was agreed. How it was counted: 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 quote:rel21-timeline

'conclusion: checkpoint in Dec.26 for RAN-CN other than connectivity services.'

A checkpoint date the plenary set for itself on the radio-to-core split. conclusion: checkpoint in Dec.26 for RAN-CN other than connectivity services. How it was counted: 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 quote:rel21-checkpoint

'SA WG2 were asked to develop 6G interface names and naming convention, especially for RAN -CN interfaces and report to TSGs in September 2026.'

A task handed to SA WG2 with a reporting date. SA WG2 were asked to develop 6G interface names and naming convention, especially for RAN -CN interfaces and report to TSGs in September 2026. How it was counted: 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 quote:6g-interface-names

'Qualcomm objected to this decision.' cited

A recorded objection to the interface-naming task. 3GPP works by consensus, so an objection is written down rather than voted away. Qualcomm objected to this decision. How it was counted: 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 quote:qualcomm-objection

'It was decided to use '6GC or 6G CN'.'

How the plenary settled the name of the 6G core network. It was decided to use '6GC or 6G CN'. How it was counted: 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 quote:6gc-naming

'This new WID was approved.' cited

The Ultra Low Bitrate Speech Codec work item was approved after a long argument about AI training data. This new WID was approved. How it was counted: 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 quote:ulbc-wid-approved

'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.' cited

The plenary pushed the legal question about AI training data up to the Project Co-ordination Group. 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. How it was counted: 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 quote:ulbc-legal

'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.' cited

Every terms-of-reference update was held over so all six groups can 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. How it was counted: 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 quote:tor-postponed

'This Welcome slides Template was endorsed.'

Endorsed, not approved — a weaker word the plenary uses for things that are not specification text. This Welcome slides Template was endorsed. How it was counted: 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 quote:welcome-slide

'- Continue with trial of separated ASN.1 in FS_6GSpecs'

What the plenary told the specification-modernisation study to do next. - Continue with trial of separated ASN.1 in FS_6GSpecs How it was counted: 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 quote:6gspecs-asn1

'Interested companies are encouraged to demonstrate the use of Forge for 3GPP specifications (e.g. 38.331).'

The plenary encouraged a git-based trial without committing to it. Interested companies are encouraged to demonstrate the use of Forge for 3GPP specifications (e.g. 38.331). How it was counted: 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 quote:6gspecs-forge

'This was endorsed.'

The chair's guidance document on the modernisation study was endorsed. This was endorsed. How it was counted: 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 quote:6gspecs-endorsed

'Care should be taken to agree or endorse CRs against frozen releases in the working group level, especially given the existing commercial deployments.'

The principle the plenary noted about changing releases that are closed. Care should be taken to agree or endorse CRs against frozen releases in the working group level, especially given the existing commercial deployments. How it was counted: 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 quote:frozen-releases

'This was postponed.' cited

The change to the change-request process for 3GPP Forge did not go through at this meeting. This was postponed. How it was counted: 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 quote:forge-cr-postponed

'The meeting was then closed.' cited

How the report records the end of the plenary. The meeting was then closed. How it was counted: 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 quote:close

Specification 12

TS 23.482

Functional architecture and information flows for AIML Enablement Service 46 change requests at SA#112 How it was counted: tokens equal to '23.482' in the crspec column of the CR and CR pack rows of tdoc; the title from table spec of spec_catalog.sqlite, read 2026-08-04 spec:23.482

TS 23.502

Procedures for the 5G System (5GS) 38 change requests at SA#112 How it was counted: tokens equal to '23.502' in the crspec column of the CR and CR pack rows of tdoc; the title from table spec of spec_catalog.sqlite, read 2026-08-04 spec:23.502

TS 23.369

Architecture support for Ambient power-enabled Internet of Things; Stage 2 33 change requests at SA#112 How it was counted: tokens equal to '23.369' in the crspec column of the CR and CR pack rows of tdoc; the title from table spec of spec_catalog.sqlite, read 2026-08-04 spec:23.369

TS 23.501 cited

System architecture for the 5G System (5GS) 29 change requests at SA#112 How it was counted: tokens equal to '23.501' in the crspec column of the CR and CR pack rows of tdoc; the title from table spec of spec_catalog.sqlite, read 2026-08-04 spec:23.501

TS 28.312

Management and orchestration; Intent driven management services for mobile networks 29 change requests at SA#112 How it was counted: tokens equal to '28.312' in the crspec column of the CR and CR pack rows of tdoc; the title from table spec of spec_catalog.sqlite, read 2026-08-04 spec:28.312

TS 28.552 cited

Management and orchestration; 5G performance measurements 29 change requests at SA#112 How it was counted: tokens equal to '28.552' in the crspec column of the CR and CR pack rows of tdoc; the title from table spec of spec_catalog.sqlite, read 2026-08-04 spec:28.552

TS 23.503

Policy and charging control framework for the 5G System (5GS); Stage 2 24 change requests at SA#112 How it was counted: tokens equal to '23.503' in the crspec column of the CR and CR pack rows of tdoc; the title from table spec of spec_catalog.sqlite, read 2026-08-04 spec:23.503

TS 23.288

Architecture enhancements for 5G System (5GS) to support network data analytics services 23 change requests at SA#112 How it was counted: tokens equal to '23.288' in the crspec column of the CR and CR pack rows of tdoc; the title from table spec of spec_catalog.sqlite, read 2026-08-04 spec:23.288

TS 23.228

IP Multimedia Subsystem (IMS); Stage 2 22 change requests at SA#112 How it was counted: tokens equal to '23.228' in the crspec column of the CR and CR pack rows of tdoc; the title from table spec of spec_catalog.sqlite, read 2026-08-04 spec:23.228

TS 28.561

Management and orchestration; Management aspects of Network Digital Twins 19 change requests at SA#112 How it was counted: tokens equal to '28.561' in the crspec column of the CR and CR pack rows of tdoc; the title from table spec of spec_catalog.sqlite, read 2026-08-04 spec:28.561

TS 23.433

Service Enabler Architecture Layer for Verticals (SEAL); Data Delivery enabler for vertical applications 18 change requests at SA#112 How it was counted: tokens equal to '23.433' in the crspec column of the CR and CR pack rows of tdoc; the title from table spec of spec_catalog.sqlite, read 2026-08-04 spec:23.433

TS 28.541

Management and orchestration; 5G Network Resource Model (NRM); Stage 2 and stage 3 18 change requests at SA#112 How it was counted: tokens equal to '28.541' in the crspec column of the CR and CR pack rows of tdoc; the title from table spec of spec_catalog.sqlite, read 2026-08-04 spec:28.541

Page on the standards body's own site 5

The SA#112 document folder cited

Everything the meeting produced, as 3GPP publishes it: agenda, report, and one zip file per document How it was counted: the line beginning Tdocweblocation= in the meeting's own TdocsByAgenda.md, read 2026-08-04 page:sa112-folder

SP-260361, the SA#112 agenda, version 2 cited

The agenda document: the deadlines, the twenty-three agenda items, the day-by-day time plan and the meeting's own rules doc:sa112-agenda

SP-112 draft meeting report, version 0.0.5 cited

The secretary's report of the meeting. Its own cover says 'Status: Draft - for comment', so nothing in it is final v0.0.5, Draft - for comment doc:sa112-draft-report

TdocsByAgenda, the SA#112 document list cited

Every document of the meeting listed under the agenda item it belongs to, with its type, its source and its result doc:sa112-tdocs-by-agenda

Welcome to TSG SA, revision 1 cited

The chair's welcome pack: where the agenda, the document list, the chair's notes and the draft report live during a meeting doc:sa112-welcome

Meeting 1

3GPP TSG SA#112 cited

3GPPSA#112 — 3GPP SA ordinary plenary, Singapore, 2026-06-09 to 2026-06-12 SP-112 How it was counted: row id=60797 of table meetings in portal_meetings.sqlite, read 2026-08-04 meeting:SP-112

Summary 1

The machine-written summary of SA#112 on whatthespec.net cited

A summary of this meeting written by a language model, not by 3GPP. Usable as a pointer, never as evidence of what was decided qwen3.6:35b How it was counted: row meeting_id='TSGS_112_Singapore_2026-06' of table meeting_summaries in summaries.db, generated 2026-07-02T13:43:43Z by model qwen3.6:35b, read 2026-08-04 summary:sa112-pygppe

Nothing here matches that. Try a shorter word.