Everything this course is built on

Counted from the data 121

3,928 3GPP specifications in the catalogue cited

3928 How it was counted: rows in table `spec` of the pygppe specification catalogue, read from /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-04 count:specs-total

2,149 of them are Technical Specifications cited

2149 How it was counted: rows in table `spec` where type='TS', read from /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-04 count:specs-ts

1,778 of them are Technical Reports cited

1778 How it was counted: rows in table `spec` where type='TR', read from /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-04 count:specs-tr

3,599 specifications are marked still maintained cited

3599 How it was counted: rows in table `spec` where active='yes', read from /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-04 count:specs-active

329 specifications are marked no longer maintained cited

329 How it was counted: rows in table `spec` where active='no', read from /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-04 count:specs-inactive

685 specifications carry the group code S5 cited

685 How it was counted: rows in table `spec` where wg='S5', read from /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-04 count:specs-group-s5

458 specifications carry the group code R4 cited

458 How it was counted: rows in table `spec` where wg='R4', read from /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-04 count:specs-group-r4

343 specifications carry the group code S3 cited

343 How it was counted: rows in table `spec` where wg='S3', read from /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-04 count:specs-group-s3

321 specifications carry the group code S2 cited

321 How it was counted: rows in table `spec` where wg='S2', read from /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-04 count:specs-group-s2

303 specifications carry the group code S4 cited

303 How it was counted: rows in table `spec` where wg='S4', read from /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-04 count:specs-group-s4

256 specifications carry the group code S1 cited

256 How it was counted: rows in table `spec` where wg='S1', read from /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-04 count:specs-group-s1

237 specifications carry the group code C1 cited

237 How it was counted: rows in table `spec` where wg='C1', read from /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-04 count:specs-group-c1

236 specifications carry the group code C4 cited

236 How it was counted: rows in table `spec` where wg='C4', read from /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-04 count:specs-group-c4

200 specifications carry the group code RP cited

200 How it was counted: rows in table `spec` where wg='RP', read from /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-04 count:specs-group-rp

20,793 specification-and-release pairs cited

20793 How it was counted: rows in table `spec_version`, one per specification per release, read from /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-04 count:spec-versions

19 named releases cited

19 How it was counted: distinct values of `release` in table `spec_version`, leaving out 'Rel-unknown', read from /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-04 count:releases

1,629,643 meeting documents recorded cited

1629643 How it was counted: rows in table `tdoc` of the pygppe meeting-document database, read from /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-04 count:tdocs-total

516,809 of them are change requests cited

516809 How it was counted: rows in table `tdoc` where tdoctype='CR', read from /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-04 count:tdocs-cr

159,055 of them are pseudo change requests, for documents not yet under change control cited

159055 How it was counted: rows in table `tdoc` where tdoctype='pCR', read from /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-04 count:tdocs-pcr

47,474 of them are liaison statements sent to another group cited

47474 How it was counted: rows in table `tdoc` where tdoctype='LS out', read from /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-04 count:tdocs-ls-out

11,595 of them are new work item descriptions cited

11595 How it was counted: rows in table `tdoc` where tdoctype='WID new', read from /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-04 count:tdocs-wid-new

5,532 of them are new study item descriptions cited

5532 How it was counted: rows in table `tdoc` where tdoctype='SID new', read from /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-04 count:tdocs-sid-new

97,521 meeting documents ended with the status "approved" cited

97521 How it was counted: rows in table `tdoc` where status='approved', read from /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-04 count:tdocs-status-approved

16,137 meeting documents ended with the status "not pursued" cited

16137 How it was counted: rows in table `tdoc` where status='not pursued', read from /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-04 count:tdocs-status-not-pursued

1,543,066 of them carry an upload date, running from 2015 to 2026 cited

1543066 How it was counted: rows in table `tdoc` whose `uploaded` field starts with a year; the span is the first and last year holding more than 100 rows, which leaves out two stray rows dated before 1910, read from /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-04 count:tdocs-dated

4,371 of them are 3GPP meetings, from 1998-12-07 to 2028-06-13 cited

4371 How it was counted: rows in table `meetings` whose body name starts '3GPP'; the span is the earliest and latest start date among them, read from /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite on 2026-08-04. The latest dates are meetings already scheduled, not meetings held count:meetings-3gpp

27 3GPP bodies hold a meeting series of their own cited

27 How it was counted: distinct body names starting '3GPP' in table `meetings`; the list is every one of them, smallest included, because only the larger ones get an entry of their own in this register, read from /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite on 2026-08-04 count:3gpp-bodies

331 3GPP meetings were held in 2024 and 2025 cited

331 How it was counted: meetings in table `meetings` whose body name starts '3GPP' and whose start date falls between 2024-01-01 and 2025-12-31, read from /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite on 2026-08-04 count:load-meetings

86,887 delegate registrations were recorded across them cited

86887 How it was counted: the sum of Registeredf2f and RegisteredOnline over meetings in table `meetings` whose body name starts '3GPP' and whose start date falls between 2024-01-01 and 2025-12-31, read from /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite on 2026-08-04. One person registering for eight meetings is eight registrations count:load-registered

53,714 of those registrations ended with a presence recorded cited

53714 How it was counted: the sum of Participantsf2f and ParticipantsOnline over meetings in table `meetings` whose body name starts '3GPP' and whose start date falls between 2024-01-01 and 2025-12-31, read from /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite on 2026-08-04. The calendar records presence separately from registration, and some bodies barely record it at all count:load-present

213,886 documents were filed to them cited

213886 How it was counted: the sum of DocCount over meetings in table `meetings` whose body name starts '3GPP' and whose start date falls between 2024-01-01 and 2025-12-31, read from /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite on 2026-08-04 count:load-documents

21 3GPP bodies held at least 4 meetings in 2024 and 2025 cited

21 How it was counted: bodies with 4 or more meetings in meetings in table `meetings` whose body name starts '3GPP' and whose start date falls between 2024-01-01 and 2025-12-31; below that a middle meeting says nothing, so no such body is counted here, read from /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite on 2026-08-04 count:load-bodies

3GPP RAN 4 held 15 meetings in 2024 and 2025 cited

15 How it was counted: meetings in table `meetings` whose body name starts '3GPP' and whose start date falls between 2024-01-01 and 2025-12-31 where the body name is '3GPP RAN 4', read from /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite on 2026-08-04 count:load-3gpp-ran-4-meetings

541 delegates registered for the middle 3GPP RAN 4 meeting cited

541 How it was counted: the middle value of Registeredf2f plus RegisteredOnline over the 15 meetings of '3GPP RAN 4' in meetings in table `meetings` whose body name starts '3GPP' and whose start date falls between 2024-01-01 and 2025-12-31; where two sit in the middle the lower is taken, so the figure is one a real meeting had, read from /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite on 2026-08-04 count:load-3gpp-ran-4-delegates

3,079 documents were filed to the middle 3GPP RAN 4 meeting cited

3079 How it was counted: the middle value of DocCount over the 15 meetings of '3GPP RAN 4' in meetings in table `meetings` whose body name starts '3GPP' and whose start date falls between 2024-01-01 and 2025-12-31, taken the same way as the delegate figure, read from /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite on 2026-08-04 count:load-3gpp-ran-4-documents

38,154 documents were filed to 3GPP RAN 4 in 2024 and 2025 cited

38154 How it was counted: the sum of DocCount over the 15 meetings of '3GPP RAN 4' in meetings in table `meetings` whose body name starts '3GPP' and whose start date falls between 2024-01-01 and 2025-12-31, read from /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite on 2026-08-04 count:load-3gpp-ran-4-documents-total

3GPP SA 2 held 16 meetings in 2024 and 2025 cited

16 How it was counted: meetings in table `meetings` whose body name starts '3GPP' and whose start date falls between 2024-01-01 and 2025-12-31 where the body name is '3GPP SA 2', read from /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite on 2026-08-04 count:load-3gpp-sa-2-meetings

453 delegates registered for the middle 3GPP SA 2 meeting cited

453 How it was counted: the middle value of Registeredf2f plus RegisteredOnline over the 16 meetings of '3GPP SA 2' in meetings in table `meetings` whose body name starts '3GPP' and whose start date falls between 2024-01-01 and 2025-12-31; where two sit in the middle the lower is taken, so the figure is one a real meeting had, read from /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite on 2026-08-04 count:load-3gpp-sa-2-delegates

1,694 documents were filed to the middle 3GPP SA 2 meeting cited

1694 How it was counted: the middle value of DocCount over the 16 meetings of '3GPP SA 2' in meetings in table `meetings` whose body name starts '3GPP' and whose start date falls between 2024-01-01 and 2025-12-31, taken the same way as the delegate figure, read from /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite on 2026-08-04 count:load-3gpp-sa-2-documents

24,355 documents were filed to 3GPP SA 2 in 2024 and 2025 cited

24355 How it was counted: the sum of DocCount over the 16 meetings of '3GPP SA 2' in meetings in table `meetings` whose body name starts '3GPP' and whose start date falls between 2024-01-01 and 2025-12-31, read from /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite on 2026-08-04 count:load-3gpp-sa-2-documents-total

3GPP RAN 1 held 14 meetings in 2024 and 2025 cited

14 How it was counted: meetings in table `meetings` whose body name starts '3GPP' and whose start date falls between 2024-01-01 and 2025-12-31 where the body name is '3GPP RAN 1', read from /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite on 2026-08-04 count:load-3gpp-ran-1-meetings

1,092 delegates registered for the middle 3GPP RAN 1 meeting cited

1092 How it was counted: the middle value of Registeredf2f plus RegisteredOnline over the 14 meetings of '3GPP RAN 1' in meetings in table `meetings` whose body name starts '3GPP' and whose start date falls between 2024-01-01 and 2025-12-31; where two sit in the middle the lower is taken, so the figure is one a real meeting had, read from /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite on 2026-08-04 count:load-3gpp-ran-1-delegates

1,600 documents were filed to the middle 3GPP RAN 1 meeting cited

1600 How it was counted: the middle value of DocCount over the 14 meetings of '3GPP RAN 1' in meetings in table `meetings` whose body name starts '3GPP' and whose start date falls between 2024-01-01 and 2025-12-31, taken the same way as the delegate figure, read from /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite on 2026-08-04 count:load-3gpp-ran-1-documents

20,556 documents were filed to 3GPP RAN 1 in 2024 and 2025 cited

20556 How it was counted: the sum of DocCount over the 14 meetings of '3GPP RAN 1' in meetings in table `meetings` whose body name starts '3GPP' and whose start date falls between 2024-01-01 and 2025-12-31, read from /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite on 2026-08-04 count:load-3gpp-ran-1-documents-total

3GPP RAN 2 held 13 meetings in 2024 and 2025 cited

13 How it was counted: meetings in table `meetings` whose body name starts '3GPP' and whose start date falls between 2024-01-01 and 2025-12-31 where the body name is '3GPP RAN 2', read from /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite on 2026-08-04 count:load-3gpp-ran-2-meetings

702 delegates registered for the middle 3GPP RAN 2 meeting cited

702 How it was counted: the middle value of Registeredf2f plus RegisteredOnline over the 13 meetings of '3GPP RAN 2' in meetings in table `meetings` whose body name starts '3GPP' and whose start date falls between 2024-01-01 and 2025-12-31; where two sit in the middle the lower is taken, so the figure is one a real meeting had, read from /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite on 2026-08-04 count:load-3gpp-ran-2-delegates

1,617 documents were filed to the middle 3GPP RAN 2 meeting cited

1617 How it was counted: the middle value of DocCount over the 13 meetings of '3GPP RAN 2' in meetings in table `meetings` whose body name starts '3GPP' and whose start date falls between 2024-01-01 and 2025-12-31, taken the same way as the delegate figure, read from /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite on 2026-08-04 count:load-3gpp-ran-2-documents

19,478 documents were filed to 3GPP RAN 2 in 2024 and 2025 cited

19478 How it was counted: the sum of DocCount over the 13 meetings of '3GPP RAN 2' in meetings in table `meetings` whose body name starts '3GPP' and whose start date falls between 2024-01-01 and 2025-12-31, read from /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite on 2026-08-04 count:load-3gpp-ran-2-documents-total

3GPP RAN 5 held 19 meetings in 2024 and 2025 cited

19 How it was counted: meetings in table `meetings` whose body name starts '3GPP' and whose start date falls between 2024-01-01 and 2025-12-31 where the body name is '3GPP RAN 5', read from /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite on 2026-08-04 count:load-3gpp-ran-5-meetings

28 delegates registered for the middle 3GPP RAN 5 meeting cited

28 How it was counted: the middle value of Registeredf2f plus RegisteredOnline over the 19 meetings of '3GPP RAN 5' in meetings in table `meetings` whose body name starts '3GPP' and whose start date falls between 2024-01-01 and 2025-12-31; where two sit in the middle the lower is taken, so the figure is one a real meeting had, read from /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite on 2026-08-04 count:load-3gpp-ran-5-delegates

289 documents were filed to the middle 3GPP RAN 5 meeting cited

289 How it was counted: the middle value of DocCount over the 19 meetings of '3GPP RAN 5' in meetings in table `meetings` whose body name starts '3GPP' and whose start date falls between 2024-01-01 and 2025-12-31, taken the same way as the delegate figure, read from /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite on 2026-08-04 count:load-3gpp-ran-5-documents

15,199 documents were filed to 3GPP RAN 5 in 2024 and 2025 cited

15199 How it was counted: the sum of DocCount over the 19 meetings of '3GPP RAN 5' in meetings in table `meetings` whose body name starts '3GPP' and whose start date falls between 2024-01-01 and 2025-12-31, read from /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite on 2026-08-04 count:load-3gpp-ran-5-documents-total

3GPP SA 5 held 17 meetings in 2024 and 2025 cited

17 How it was counted: meetings in table `meetings` whose body name starts '3GPP' and whose start date falls between 2024-01-01 and 2025-12-31 where the body name is '3GPP SA 5', read from /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite on 2026-08-04 count:load-3gpp-sa-5-meetings

203 delegates registered for the middle 3GPP SA 5 meeting cited

203 How it was counted: the middle value of Registeredf2f plus RegisteredOnline over the 17 meetings of '3GPP SA 5' in meetings in table `meetings` whose body name starts '3GPP' and whose start date falls between 2024-01-01 and 2025-12-31; where two sit in the middle the lower is taken, so the figure is one a real meeting had, read from /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite on 2026-08-04 count:load-3gpp-sa-5-delegates

912 documents were filed to the middle 3GPP SA 5 meeting cited

912 How it was counted: the middle value of DocCount over the 17 meetings of '3GPP SA 5' in meetings in table `meetings` whose body name starts '3GPP' and whose start date falls between 2024-01-01 and 2025-12-31, taken the same way as the delegate figure, read from /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite on 2026-08-04 count:load-3gpp-sa-5-documents

12,437 documents were filed to 3GPP SA 5 in 2024 and 2025 cited

12437 How it was counted: the sum of DocCount over the 17 meetings of '3GPP SA 5' in meetings in table `meetings` whose body name starts '3GPP' and whose start date falls between 2024-01-01 and 2025-12-31, read from /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite on 2026-08-04 count:load-3gpp-sa-5-documents-total

3GPP CT 1 held 13 meetings in 2024 and 2025 cited

13 How it was counted: meetings in table `meetings` whose body name starts '3GPP' and whose start date falls between 2024-01-01 and 2025-12-31 where the body name is '3GPP CT 1', read from /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite on 2026-08-04 count:load-3gpp-ct-1-meetings

231 delegates registered for the middle 3GPP CT 1 meeting cited

231 How it was counted: the middle value of Registeredf2f plus RegisteredOnline over the 13 meetings of '3GPP CT 1' in meetings in table `meetings` whose body name starts '3GPP' and whose start date falls between 2024-01-01 and 2025-12-31; where two sit in the middle the lower is taken, so the figure is one a real meeting had, read from /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite on 2026-08-04 count:load-3gpp-ct-1-delegates

907 documents were filed to the middle 3GPP CT 1 meeting cited

907 How it was counted: the middle value of DocCount over the 13 meetings of '3GPP CT 1' in meetings in table `meetings` whose body name starts '3GPP' and whose start date falls between 2024-01-01 and 2025-12-31, taken the same way as the delegate figure, read from /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite on 2026-08-04 count:load-3gpp-ct-1-documents

12,100 documents were filed to 3GPP CT 1 in 2024 and 2025 cited

12100 How it was counted: the sum of DocCount over the 13 meetings of '3GPP CT 1' in meetings in table `meetings` whose body name starts '3GPP' and whose start date falls between 2024-01-01 and 2025-12-31, read from /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite on 2026-08-04 count:load-3gpp-ct-1-documents-total

3GPP RAN 3 held 13 meetings in 2024 and 2025 cited

13 How it was counted: meetings in table `meetings` whose body name starts '3GPP' and whose start date falls between 2024-01-01 and 2025-12-31 where the body name is '3GPP RAN 3', read from /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite on 2026-08-04 count:load-3gpp-ran-3-meetings

425 delegates registered for the middle 3GPP RAN 3 meeting cited

425 How it was counted: the middle value of Registeredf2f plus RegisteredOnline over the 13 meetings of '3GPP RAN 3' in meetings in table `meetings` whose body name starts '3GPP' and whose start date falls between 2024-01-01 and 2025-12-31; where two sit in the middle the lower is taken, so the figure is one a real meeting had, read from /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite on 2026-08-04 count:load-3gpp-ran-3-delegates

938 documents were filed to the middle 3GPP RAN 3 meeting cited

938 How it was counted: the middle value of DocCount over the 13 meetings of '3GPP RAN 3' in meetings in table `meetings` whose body name starts '3GPP' and whose start date falls between 2024-01-01 and 2025-12-31, taken the same way as the delegate figure, read from /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite on 2026-08-04 count:load-3gpp-ran-3-documents

11,384 documents were filed to 3GPP RAN 3 in 2024 and 2025 cited

11384 How it was counted: the sum of DocCount over the 13 meetings of '3GPP RAN 3' in meetings in table `meetings` whose body name starts '3GPP' and whose start date falls between 2024-01-01 and 2025-12-31, read from /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite on 2026-08-04 count:load-3gpp-ran-3-documents-total

3GPP SA 3 held 29 meetings in 2024 and 2025 cited

29 How it was counted: meetings in table `meetings` whose body name starts '3GPP' and whose start date falls between 2024-01-01 and 2025-12-31 where the body name is '3GPP SA 3', read from /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite on 2026-08-04 count:load-3gpp-sa-3-meetings

61 delegates registered for the middle 3GPP SA 3 meeting cited

61 How it was counted: the middle value of Registeredf2f plus RegisteredOnline over the 29 meetings of '3GPP SA 3' in meetings in table `meetings` whose body name starts '3GPP' and whose start date falls between 2024-01-01 and 2025-12-31; where two sit in the middle the lower is taken, so the figure is one a real meeting had, read from /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite on 2026-08-04 count:load-3gpp-sa-3-delegates

145 documents were filed to the middle 3GPP SA 3 meeting cited

145 How it was counted: the middle value of DocCount over the 29 meetings of '3GPP SA 3' in meetings in table `meetings` whose body name starts '3GPP' and whose start date falls between 2024-01-01 and 2025-12-31, taken the same way as the delegate figure, read from /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite on 2026-08-04 count:load-3gpp-sa-3-documents

10,375 documents were filed to 3GPP SA 3 in 2024 and 2025 cited

10375 How it was counted: the sum of DocCount over the 29 meetings of '3GPP SA 3' in meetings in table `meetings` whose body name starts '3GPP' and whose start date falls between 2024-01-01 and 2025-12-31, read from /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite on 2026-08-04 count:load-3gpp-sa-3-documents-total

3GPP SA 6 held 14 meetings in 2024 and 2025

14 How it was counted: meetings in table `meetings` whose body name starts '3GPP' and whose start date falls between 2024-01-01 and 2025-12-31 where the body name is '3GPP SA 6', read from /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite on 2026-08-04 count:load-3gpp-sa-6-meetings

199 delegates registered for the middle 3GPP SA 6 meeting

199 How it was counted: the middle value of Registeredf2f plus RegisteredOnline over the 14 meetings of '3GPP SA 6' in meetings in table `meetings` whose body name starts '3GPP' and whose start date falls between 2024-01-01 and 2025-12-31; where two sit in the middle the lower is taken, so the figure is one a real meeting had, read from /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite on 2026-08-04 count:load-3gpp-sa-6-delegates

691 documents were filed to the middle 3GPP SA 6 meeting

691 How it was counted: the middle value of DocCount over the 14 meetings of '3GPP SA 6' in meetings in table `meetings` whose body name starts '3GPP' and whose start date falls between 2024-01-01 and 2025-12-31, taken the same way as the delegate figure, read from /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite on 2026-08-04 count:load-3gpp-sa-6-documents

8,799 documents were filed to 3GPP SA 6 in 2024 and 2025

8799 How it was counted: the sum of DocCount over the 14 meetings of '3GPP SA 6' in meetings in table `meetings` whose body name starts '3GPP' and whose start date falls between 2024-01-01 and 2025-12-31, read from /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite on 2026-08-04 count:load-3gpp-sa-6-documents-total

3GPP CT 3 held 13 meetings in 2024 and 2025

13 How it was counted: meetings in table `meetings` whose body name starts '3GPP' and whose start date falls between 2024-01-01 and 2025-12-31 where the body name is '3GPP CT 3', read from /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite on 2026-08-04 count:load-3gpp-ct-3-meetings

185 delegates registered for the middle 3GPP CT 3 meeting

185 How it was counted: the middle value of Registeredf2f plus RegisteredOnline over the 13 meetings of '3GPP CT 3' in meetings in table `meetings` whose body name starts '3GPP' and whose start date falls between 2024-01-01 and 2025-12-31; where two sit in the middle the lower is taken, so the figure is one a real meeting had, read from /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite on 2026-08-04 count:load-3gpp-ct-3-delegates

670 documents were filed to the middle 3GPP CT 3 meeting

670 How it was counted: the middle value of DocCount over the 13 meetings of '3GPP CT 3' in meetings in table `meetings` whose body name starts '3GPP' and whose start date falls between 2024-01-01 and 2025-12-31, taken the same way as the delegate figure, read from /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite on 2026-08-04 count:load-3gpp-ct-3-documents

8,309 documents were filed to 3GPP CT 3 in 2024 and 2025

8309 How it was counted: the sum of DocCount over the 13 meetings of '3GPP CT 3' in meetings in table `meetings` whose body name starts '3GPP' and whose start date falls between 2024-01-01 and 2025-12-31, read from /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite on 2026-08-04 count:load-3gpp-ct-3-documents-total

3GPP RAN held 8 meetings in 2024 and 2025

8 How it was counted: meetings in table `meetings` whose body name starts '3GPP' and whose start date falls between 2024-01-01 and 2025-12-31 where the body name is '3GPP RAN', read from /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite on 2026-08-04 count:load-3gpp-ran-meetings

765 delegates registered for the middle 3GPP RAN meeting

765 How it was counted: the middle value of Registeredf2f plus RegisteredOnline over the 8 meetings of '3GPP RAN' in meetings in table `meetings` whose body name starts '3GPP' and whose start date falls between 2024-01-01 and 2025-12-31; where two sit in the middle the lower is taken, so the figure is one a real meeting had, read from /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite on 2026-08-04 count:load-3gpp-ran-delegates

860 documents were filed to the middle 3GPP RAN meeting

860 How it was counted: the middle value of DocCount over the 8 meetings of '3GPP RAN' in meetings in table `meetings` whose body name starts '3GPP' and whose start date falls between 2024-01-01 and 2025-12-31, taken the same way as the delegate figure, read from /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite on 2026-08-04 count:load-3gpp-ran-documents

7,197 documents were filed to 3GPP RAN in 2024 and 2025

7197 How it was counted: the sum of DocCount over the 8 meetings of '3GPP RAN' in meetings in table `meetings` whose body name starts '3GPP' and whose start date falls between 2024-01-01 and 2025-12-31, read from /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite on 2026-08-04 count:load-3gpp-ran-documents-total

3GPP CT 4 held 13 meetings in 2024 and 2025

13 How it was counted: meetings in table `meetings` whose body name starts '3GPP' and whose start date falls between 2024-01-01 and 2025-12-31 where the body name is '3GPP CT 4', read from /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite on 2026-08-04 count:load-3gpp-ct-4-meetings

189 delegates registered for the middle 3GPP CT 4 meeting

189 How it was counted: the middle value of Registeredf2f plus RegisteredOnline over the 13 meetings of '3GPP CT 4' in meetings in table `meetings` whose body name starts '3GPP' and whose start date falls between 2024-01-01 and 2025-12-31; where two sit in the middle the lower is taken, so the figure is one a real meeting had, read from /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite on 2026-08-04 count:load-3gpp-ct-4-delegates

550 documents were filed to the middle 3GPP CT 4 meeting

550 How it was counted: the middle value of DocCount over the 13 meetings of '3GPP CT 4' in meetings in table `meetings` whose body name starts '3GPP' and whose start date falls between 2024-01-01 and 2025-12-31, taken the same way as the delegate figure, read from /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite on 2026-08-04 count:load-3gpp-ct-4-documents

7,036 documents were filed to 3GPP CT 4 in 2024 and 2025

7036 How it was counted: the sum of DocCount over the 13 meetings of '3GPP CT 4' in meetings in table `meetings` whose body name starts '3GPP' and whose start date falls between 2024-01-01 and 2025-12-31, read from /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite on 2026-08-04 count:load-3gpp-ct-4-documents-total

3GPP SA 4 held 70 meetings in 2024 and 2025 cited

70 How it was counted: meetings in table `meetings` whose body name starts '3GPP' and whose start date falls between 2024-01-01 and 2025-12-31 where the body name is '3GPP SA 4', read from /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite on 2026-08-04 count:load-3gpp-sa-4-meetings

32 delegates registered for the middle 3GPP SA 4 meeting cited

32 How it was counted: the middle value of Registeredf2f plus RegisteredOnline over the 70 meetings of '3GPP SA 4' in meetings in table `meetings` whose body name starts '3GPP' and whose start date falls between 2024-01-01 and 2025-12-31; where two sit in the middle the lower is taken, so the figure is one a real meeting had, read from /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite on 2026-08-04 count:load-3gpp-sa-4-delegates

16 documents were filed to the middle 3GPP SA 4 meeting cited

16 How it was counted: the middle value of DocCount over the 70 meetings of '3GPP SA 4' in meetings in table `meetings` whose body name starts '3GPP' and whose start date falls between 2024-01-01 and 2025-12-31, taken the same way as the delegate figure, read from /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite on 2026-08-04 count:load-3gpp-sa-4-documents

5,588 documents were filed to 3GPP SA 4 in 2024 and 2025 cited

5588 How it was counted: the sum of DocCount over the 70 meetings of '3GPP SA 4' in meetings in table `meetings` whose body name starts '3GPP' and whose start date falls between 2024-01-01 and 2025-12-31, read from /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite on 2026-08-04 count:load-3gpp-sa-4-documents-total

3GPP SA 1 held 10 meetings in 2024 and 2025

10 How it was counted: meetings in table `meetings` whose body name starts '3GPP' and whose start date falls between 2024-01-01 and 2025-12-31 where the body name is '3GPP SA 1', read from /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite on 2026-08-04 count:load-3gpp-sa-1-meetings

425 delegates registered for the middle 3GPP SA 1 meeting

425 How it was counted: the middle value of Registeredf2f plus RegisteredOnline over the 10 meetings of '3GPP SA 1' in meetings in table `meetings` whose body name starts '3GPP' and whose start date falls between 2024-01-01 and 2025-12-31; where two sit in the middle the lower is taken, so the figure is one a real meeting had, read from /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite on 2026-08-04 count:load-3gpp-sa-1-delegates

521 documents were filed to the middle 3GPP SA 1 meeting

521 How it was counted: the middle value of DocCount over the 10 meetings of '3GPP SA 1' in meetings in table `meetings` whose body name starts '3GPP' and whose start date falls between 2024-01-01 and 2025-12-31, taken the same way as the delegate figure, read from /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite on 2026-08-04 count:load-3gpp-sa-1-documents

5,393 documents were filed to 3GPP SA 1 in 2024 and 2025

5393 How it was counted: the sum of DocCount over the 10 meetings of '3GPP SA 1' in meetings in table `meetings` whose body name starts '3GPP' and whose start date falls between 2024-01-01 and 2025-12-31, read from /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite on 2026-08-04 count:load-3gpp-sa-1-documents-total

3GPP SA held 12 meetings in 2024 and 2025

12 How it was counted: meetings in table `meetings` whose body name starts '3GPP' and whose start date falls between 2024-01-01 and 2025-12-31 where the body name is '3GPP SA', read from /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite on 2026-08-04 count:load-3gpp-sa-meetings

439 delegates registered for the middle 3GPP SA meeting

439 How it was counted: the middle value of Registeredf2f plus RegisteredOnline over the 12 meetings of '3GPP SA' in meetings in table `meetings` whose body name starts '3GPP' and whose start date falls between 2024-01-01 and 2025-12-31; where two sit in the middle the lower is taken, so the figure is one a real meeting had, read from /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite on 2026-08-04 count:load-3gpp-sa-delegates

404 documents were filed to the middle 3GPP SA meeting

404 How it was counted: the middle value of DocCount over the 12 meetings of '3GPP SA' in meetings in table `meetings` whose body name starts '3GPP' and whose start date falls between 2024-01-01 and 2025-12-31, taken the same way as the delegate figure, read from /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite on 2026-08-04 count:load-3gpp-sa-documents

3,855 documents were filed to 3GPP SA in 2024 and 2025

3855 How it was counted: the sum of DocCount over the 12 meetings of '3GPP SA' in meetings in table `meetings` whose body name starts '3GPP' and whose start date falls between 2024-01-01 and 2025-12-31, read from /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite on 2026-08-04 count:load-3gpp-sa-documents-total

3GPP CT held 9 meetings in 2024 and 2025

9 How it was counted: meetings in table `meetings` whose body name starts '3GPP' and whose start date falls between 2024-01-01 and 2025-12-31 where the body name is '3GPP CT', read from /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite on 2026-08-04 count:load-3gpp-ct-meetings

284 delegates registered for the middle 3GPP CT meeting

284 How it was counted: the middle value of Registeredf2f plus RegisteredOnline over the 9 meetings of '3GPP CT' in meetings in table `meetings` whose body name starts '3GPP' and whose start date falls between 2024-01-01 and 2025-12-31; where two sit in the middle the lower is taken, so the figure is one a real meeting had, read from /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite on 2026-08-04 count:load-3gpp-ct-delegates

263 documents were filed to the middle 3GPP CT meeting

263 How it was counted: the middle value of DocCount over the 9 meetings of '3GPP CT' in meetings in table `meetings` whose body name starts '3GPP' and whose start date falls between 2024-01-01 and 2025-12-31, taken the same way as the delegate figure, read from /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite on 2026-08-04 count:load-3gpp-ct-documents

2,248 documents were filed to 3GPP CT in 2024 and 2025

2248 How it was counted: the sum of DocCount over the 9 meetings of '3GPP CT' in meetings in table `meetings` whose body name starts '3GPP' and whose start date falls between 2024-01-01 and 2025-12-31, read from /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite on 2026-08-04 count:load-3gpp-ct-documents-total

3GPP CT 6 held 10 meetings in 2024 and 2025

10 How it was counted: meetings in table `meetings` whose body name starts '3GPP' and whose start date falls between 2024-01-01 and 2025-12-31 where the body name is '3GPP CT 6', read from /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite on 2026-08-04 count:load-3gpp-ct-6-meetings

71 delegates registered for the middle 3GPP CT 6 meeting

71 How it was counted: the middle value of Registeredf2f plus RegisteredOnline over the 10 meetings of '3GPP CT 6' in meetings in table `meetings` whose body name starts '3GPP' and whose start date falls between 2024-01-01 and 2025-12-31; where two sit in the middle the lower is taken, so the figure is one a real meeting had, read from /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite on 2026-08-04 count:load-3gpp-ct-6-delegates

118 documents were filed to the middle 3GPP CT 6 meeting

118 How it was counted: the middle value of DocCount over the 10 meetings of '3GPP CT 6' in meetings in table `meetings` whose body name starts '3GPP' and whose start date falls between 2024-01-01 and 2025-12-31, taken the same way as the delegate figure, read from /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite on 2026-08-04 count:load-3gpp-ct-6-documents

912 documents were filed to 3GPP CT 6 in 2024 and 2025

912 How it was counted: the sum of DocCount over the 10 meetings of '3GPP CT 6' in meetings in table `meetings` whose body name starts '3GPP' and whose start date falls between 2024-01-01 and 2025-12-31, read from /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite on 2026-08-04 count:load-3gpp-ct-6-documents-total

3GPP held 11 meetings in 2024 and 2025

11 How it was counted: meetings in table `meetings` whose body name starts '3GPP' and whose start date falls between 2024-01-01 and 2025-12-31 where the body name is '3GPP', read from /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite on 2026-08-04 count:load-3gpp-meetings

78 delegates registered for the middle 3GPP meeting

78 How it was counted: the middle value of Registeredf2f plus RegisteredOnline over the 11 meetings of '3GPP' in meetings in table `meetings` whose body name starts '3GPP' and whose start date falls between 2024-01-01 and 2025-12-31; where two sit in the middle the lower is taken, so the figure is one a real meeting had, read from /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite on 2026-08-04 count:load-3gpp-delegates

0 documents were filed to the middle 3GPP meeting

0 How it was counted: the middle value of DocCount over the 11 meetings of '3GPP' in meetings in table `meetings` whose body name starts '3GPP' and whose start date falls between 2024-01-01 and 2025-12-31, taken the same way as the delegate figure, read from /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite on 2026-08-04 count:load-3gpp-documents

304 documents were filed to 3GPP in 2024 and 2025

304 How it was counted: the sum of DocCount over the 11 meetings of '3GPP' in meetings in table `meetings` whose body name starts '3GPP' and whose start date falls between 2024-01-01 and 2025-12-31, read from /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite on 2026-08-04 count:load-3gpp-documents-total

3GPP PCG held 4 meetings in 2024 and 2025

4 How it was counted: meetings in table `meetings` whose body name starts '3GPP' and whose start date falls between 2024-01-01 and 2025-12-31 where the body name is '3GPP PCG', read from /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite on 2026-08-04 count:load-3gpp-pcg-meetings

60 delegates registered for the middle 3GPP PCG meeting

60 How it was counted: the middle value of Registeredf2f plus RegisteredOnline over the 4 meetings of '3GPP PCG' in meetings in table `meetings` whose body name starts '3GPP' and whose start date falls between 2024-01-01 and 2025-12-31; where two sit in the middle the lower is taken, so the figure is one a real meeting had, read from /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite on 2026-08-04 count:load-3gpp-pcg-delegates

32 documents were filed to the middle 3GPP PCG meeting

32 How it was counted: the middle value of DocCount over the 4 meetings of '3GPP PCG' in meetings in table `meetings` whose body name starts '3GPP' and whose start date falls between 2024-01-01 and 2025-12-31, taken the same way as the delegate figure, read from /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite on 2026-08-04 count:load-3gpp-pcg-documents

136 documents were filed to 3GPP PCG in 2024 and 2025

136 How it was counted: the sum of DocCount over the 4 meetings of '3GPP PCG' in meetings in table `meetings` whose body name starts '3GPP' and whose start date falls between 2024-01-01 and 2025-12-31, read from /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite on 2026-08-04 count:load-3gpp-pcg-documents-total

3GPP OP held 8 meetings in 2024 and 2025

8 How it was counted: meetings in table `meetings` whose body name starts '3GPP' and whose start date falls between 2024-01-01 and 2025-12-31 where the body name is '3GPP OP', read from /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite on 2026-08-04 count:load-3gpp-op-meetings

9 delegates registered for the middle 3GPP OP meeting

9 How it was counted: the middle value of Registeredf2f plus RegisteredOnline over the 8 meetings of '3GPP OP' in meetings in table `meetings` whose body name starts '3GPP' and whose start date falls between 2024-01-01 and 2025-12-31; where two sit in the middle the lower is taken, so the figure is one a real meeting had, read from /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite on 2026-08-04 count:load-3gpp-op-delegates

7 documents were filed to the middle 3GPP OP meeting

7 How it was counted: the middle value of DocCount over the 8 meetings of '3GPP OP' in meetings in table `meetings` whose body name starts '3GPP' and whose start date falls between 2024-01-01 and 2025-12-31, taken the same way as the delegate figure, read from /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite on 2026-08-04 count:load-3gpp-op-documents

71 documents were filed to 3GPP OP in 2024 and 2025

71 How it was counted: the sum of DocCount over the 8 meetings of '3GPP OP' in meetings in table `meetings` whose body name starts '3GPP' and whose start date falls between 2024-01-01 and 2025-12-31, read from /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite on 2026-08-04 count:load-3gpp-op-documents-total

9,735 RFCs in the local archive cited

9735 How it was counted: files named rfc<number>.txt or rfc<number>.xml, counted in /var/www/whatthespec.net/data/data/rfcs on 2026-08-04 count:rfcs-total

8,457 of them are plain text, numbered 1 to 8649 cited

8457 How it was counted: files named rfc<number>.txt, counted in /var/www/whatthespec.net/data/data/rfcs on 2026-08-04 count:rfcs-text

1,278 of them are XML, numbered 8650 to 9953 cited

1278 How it was counted: files named rfc<number>.xml, counted in /var/www/whatthespec.net/data/data/rfcs on 2026-08-04 count:rfcs-xml

579 terms defined in the 3GPP vocabulary cited

579 How it was counted: lines of clause 3 of 3GPP TR 21.905 v19.2.0 shaped 'term: definition', counted in /var/www/whatthespec.net/data/friendlyspec/json/21905/19.2.0/full.md on 2026-08-04 count:vocabulary-terms

97 clauses in TR 21.900, the working-methods document cited

97 How it was counted: parsed clause files of 3GPP TR 21.900 v20.0.0, counted in /var/www/whatthespec.net/data/friendlyspec/json/21900/20.0.0/sections on 2026-08-04 count:21900-clauses

Quoted wording 35

TR 21.900, clause 2

Definitions and abbreviations Change Request (CR): formal proposal presented on a standard form to modify a specification which is under change control. How it was counted: the words of clause 2 of 3GPP TR 21.900 v20.0.0 as parsed under /var/www/whatthespec.net/data/friendlyspec/json/21900/20.0.0 quote:change-request

TR 21.900, clause 2

Definitions and abbreviations change control: procedure whereby proposed modifications to a specification are presented for approval to the TSG as formal Change Requests. How it was counted: the words of clause 2 of 3GPP TR 21.900 v20.0.0 as parsed under /var/www/whatthespec.net/data/friendlyspec/json/21900/20.0.0 quote:change-control

TR 21.900, clause 2

Definitions and abbreviations frozen: release status or specification status in which only essential corrections are permitted. How it was counted: the words of clause 2 of 3GPP TR 21.900 v20.0.0 as parsed under /var/www/whatthespec.net/data/friendlyspec/json/21900/20.0.0 quote:frozen

TR 21.900, clause 2

Definitions and abbreviations closed: release status or specification status in which no changes of any kind to the release or the specification are permitted. How it was counted: the words of clause 2 of 3GPP TR 21.900 v20.0.0 as parsed under /var/www/whatthespec.net/data/friendlyspec/json/21900/20.0.0 quote:closed

TR 21.900, clause 2

Definitions and abbreviations pseudo Change Request (pCR): similar to a Change Request but has no CR number and is intended to propose new or revised text for inclusion in 3GPP TSs or TRs not yet under change control (i.e. still in the drafting phase). How it was counted: the words of clause 2 of 3GPP TR 21.900 v20.0.0 as parsed under /var/www/whatthespec.net/data/friendlyspec/json/21900/20.0.0 quote:pseudo-cr

TR 21.900, clause 2

Definitions and abbreviations Work Item (WI): description of an enhancement to a technical area, which may be categorized as Study Item, Feature, Building Block or Work Task. How it was counted: the words of clause 2 of 3GPP TR 21.900 v20.0.0 as parsed under /var/www/whatthespec.net/data/friendlyspec/json/21900/20.0.0 quote:work-item

TR 21.900, clause 4.0B

Releases Specifications are grouped into "Releases". A mobile system can be constructed based on the set of all specifications which comprise a given Release. How it was counted: the words of clause 4.0B of 3GPP TR 21.900 v20.0.0 as parsed under /var/www/whatthespec.net/data/friendlyspec/json/21900/20.0.0 quote:release

TR 21.900, clause 4.0A

Version nomenclature Each specification is associated with a "version number" in the form x.y.z which uniquely identifies the document. How it was counted: the words of clause 4.0A of 3GPP TR 21.900 v20.0.0 as parsed under /var/www/whatthespec.net/data/friendlyspec/json/21900/20.0.0 quote:version-number

TR 21.900, clause 4.6.1

Change Requests Once a specification has been approved by the TSG and version x.0.0 (where x >= 3, corresponding to the Release - see table 4) has been produced, it shall be considered to be under change control. Any technical change which may be identified for inclusion in the specification from this point on shall be accomplished by means of a Change Request (CR). How it was counted: the words of clause 4.6.1 of 3GPP TR 21.900 v20.0.0 as parsed under /var/www/whatthespec.net/data/friendlyspec/json/21900/20.0.0 quote:under-change-control

TR 21.900, clause 4.6.1

Change Requests A CR may be raised by any individual member and brought to the attention of the responsible Group. How it was counted: the words of clause 4.6.1 of 3GPP TR 21.900 v20.0.0 as parsed under /var/www/whatthespec.net/data/friendlyspec/json/21900/20.0.0 quote:cr-from-anyone

TR 21.900, clause 4.6.1

Change Requests CR numbers shall not be re-used, even if a CR is ultimately rejected by the TSG (see note). How it was counted: the words of clause 4.6.1 of 3GPP TR 21.900 v20.0.0 as parsed under /var/www/whatthespec.net/data/friendlyspec/json/21900/20.0.0 quote:cr-numbers

TR 21.900, clause 4.6.1

Change Requests The TSG should approve, reject or postpone a CR in its entirety (after revision, if necessary). That is, the modifications proposed by the CR should either be accepted without change, or unconditionally rejected. How it was counted: the words of clause 4.6.1 of 3GPP TR 21.900 v20.0.0 as parsed under /var/www/whatthespec.net/data/friendlyspec/json/21900/20.0.0 quote:cr-whole-or-nothing

TR 21.900, clause 4.10.2

Mirror Change Requests Where it is determined that several Releases are affected, an (independently numbered) Change Request shall be created for each such affected version of the specification. Such CRs are termed "mirror Change Requests". How it was counted: the words of clause 4.10.2 of 3GPP TR 21.900 v20.0.0 as parsed under /var/www/whatthespec.net/data/friendlyspec/json/21900/20.0.0 quote:mirror-cr

TR 21.900, clause 4.7

"Freezing" of specifications A TSG may decide that a specification is sufficiently stable that it may be considered "frozen". That is, only CRs for essential corrections of errors shall be considered except as discussed below (see clause 4.6.2 and in particular the derogation statement below table 4A). How it was counted: the words of clause 4.7 of 3GPP TR 21.900 v20.0.0 as parsed under /var/www/whatthespec.net/data/friendlyspec/json/21900/20.0.0 quote:freezing

TR 21.900, clause 9.1

Terminology Written contributions to 3GPP meetings are called "TDocs". How it was counted: the words of clause 9.1 of 3GPP TR 21.900 v20.0.0 as parsed under /var/www/whatthespec.net/data/friendlyspec/json/21900/20.0.0 quote:tdoc

TR 21.900, clause 8.6

General if there are no comments during the allowed period, agreement is granted automatically; How it was counted: the words of clause 8.6 of 3GPP TR 21.900 v20.0.0 as parsed under /var/www/whatthespec.net/data/friendlyspec/json/21900/20.0.0 quote:email-agreement

TR 21.900, clause 4.1.1

General At creation, a rapporteur shall be appointed. The rapporteur shall produce an initial draft, version 0.0.0, and subsequent revised versions (version 0.1.0, possibly 0.1.1, 0.1.2 and so on, then version 0.2.0 etc.). How it was counted: the words of clause 4.1.1 of 3GPP TR 21.900 v20.0.0 as parsed under /var/www/whatthespec.net/data/friendlyspec/json/21900/20.0.0 quote:rapporteur

TR 21.900, clause 4.1

Overview Stage 1 is an overall service description from the user's standpoint. How it was counted: the words of clause 4.1 of 3GPP TR 21.900 v20.0.0 as parsed under /var/www/whatthespec.net/data/friendlyspec/json/21900/20.0.0 quote:three-stages

TR 21.801, Annex E cited

Verbal forms for the expression of provisions The verbal forms shown in table E.1 shall be used to indicate requirements strictly to be followed in order to conform to the standard and from which no deviation is permitted. How it was counted: the words of clause Annex E of 3GPP TR 21.801 v19.1.0 as parsed under /var/www/whatthespec.net/data/friendlyspec/json/21801/19.1.0 quote:3gpp-shall

TR 21.801, Annex E cited

Verbal forms for the expression of provisions The verbal forms shown in table E.2 shall be used to indicate that among several possibilities one is recommended as particularly suitable, without mentioning or excluding others, or that a certain course of action is preferred but not necessarily required, or that (in the negative form) a certain possibility or course of action is deprecated but not prohibited. How it was counted: the words of clause Annex E of 3GPP TR 21.801 v19.1.0 as parsed under /var/www/whatthespec.net/data/friendlyspec/json/21801/19.1.0 quote:3gpp-should

RFC 3935, section 1 cited

A Mission Statement for the IETF The goal of the IETF is to make the Internet work better. How it was counted: the words of section 1 of RFC 3935 as stored at /var/www/whatthespec.net/data/data/rfcs/rfc3935.txt quote:ietf-mission

RFC 2026, section 1.1 cited

The Internet Standards Process -- Revision 3 In general, an Internet Standard is a specification that is stable and well-understood, is technically competent, has multiple, independent, and interoperable implementations with substantial operational experience, enjoys significant public support, and is recognizably useful in some or all parts of the Internet. How it was counted: the words of section 1.1 of RFC 2026 as stored at /var/www/whatthespec.net/data/data/rfcs/rfc2026.txt quote:internet-standard

RFC 2026, section 2.2 cited

The Internet Standards Process -- Revision 3 An Internet-Draft is NOT a means of "publishing" a specification; specifications are published through the RFC mechanism described in the previous section. Internet-Drafts have no formal status, and are subject to change or removal at any time. How it was counted: the words of section 2.2 of RFC 2026 as stored at /var/www/whatthespec.net/data/data/rfcs/rfc2026.txt quote:internet-draft

RFC 2026, section 4.1.1 cited

The Internet Standards Process -- Revision 3 The entry-level maturity for the standards track is "Proposed Standard". A specific action by the IESG is required to move a specification onto the standards track at the "Proposed Standard" level. How it was counted: the words of section 4.1.1 of RFC 2026 as stored at /var/www/whatthespec.net/data/data/rfcs/rfc2026.txt quote:proposed-standard

RFC 6410, section 2 cited

Reducing the Standards Track to Two Maturity Levels This document replaces the three-tier maturity ladder defined in RFC 2026 [1] with a two-tier maturity ladder. Specifications become Internet Standards through a set of two maturity levels known as the "Standards Track". How it was counted: the words of section 2 of RFC 6410 as stored at /var/www/whatthespec.net/data/data/rfcs/rfc6410.txt quote:two-maturity-levels

RFC 7282, section 1 cited

On Consensus and Humming in the IETF We reject: kings, presidents and voting. We believe in: rough consensus and running code. How it was counted: the words of section 1 of RFC 7282 as stored at /var/www/whatthespec.net/data/data/rfcs/rfc7282.txt quote:credo

RFC 7282, section 1 cited

On Consensus and Humming in the IETF We only require rough consensus: If the chair of a working group determines that a technical issue brought forward by an objector has been truly considered by the working group, and the working group has made an informed decision that the objection has been answered or is not enough of a technical problem to prevent moving forward, the chair can declare that there is rough consensus to go forward, the objection notwithstanding. How it was counted: the words of section 1 of RFC 7282 as stored at /var/www/whatthespec.net/data/data/rfcs/rfc7282.txt quote:rough-consensus

RFC 2418, section 3.3 cited

IETF Working Group Guidelines and Procedures Working groups make decisions through a "rough consensus" process. IETF consensus does not require that all participants agree although this is, of course, preferred. How it was counted: the words of section 3.3 of RFC 2418 as stored at /var/www/whatthespec.net/data/data/rfcs/rfc2418.txt quote:wg-decisions

RFC 2418, section 3.3 cited

IETF Working Group Guidelines and Procedures Note that 51% of the working group does not qualify as "rough consensus" and 99% is better than rough. It is up to the Chair to determine if rough consensus has been reached. How it was counted: the words of section 3.3 of RFC 2418 as stored at /var/www/whatthespec.net/data/data/rfcs/rfc2418.txt quote:not-a-vote

RFC 2418, section 1 cited

IETF Working Group Guidelines and Procedures There is no formal membership in the IETF. Participation is open to all. How it was counted: the words of section 1 of RFC 2418 as stored at /var/www/whatthespec.net/data/data/rfcs/rfc2418.txt quote:no-membership

RFC 2418, section 1 cited

IETF Working Group Guidelines and Procedures The area directors sitting as a body, along with the IETF Chair, comprise the Internet Engineering Steering Group (IESG). How it was counted: the words of section 1 of RFC 2418 as stored at /var/www/whatthespec.net/data/data/rfcs/rfc2418.txt quote:iesg

RFC 2119, section 1 cited

Key words for use in RFCs to Indicate Requirement Levels MUST This word, or the terms "REQUIRED" or "SHALL", mean that the definition is an absolute requirement of the specification. How it was counted: the words of section 1 of RFC 2119 as stored at /var/www/whatthespec.net/data/data/rfcs/rfc2119.txt quote:must

RFC 2119, section 3 cited

Key words for use in RFCs to Indicate Requirement Levels SHOULD This word, or the adjective "RECOMMENDED", mean that there may exist valid reasons in particular circumstances to ignore a particular item, but the full implications must be understood and carefully weighed before choosing a different course. How it was counted: the words of section 3 of RFC 2119 as stored at /var/www/whatthespec.net/data/data/rfcs/rfc2119.txt quote:should

RFC 2119, section 5 cited

Key words for use in RFCs to Indicate Requirement Levels MAY This word, or the adjective "OPTIONAL", mean that an item is truly optional. How it was counted: the words of section 5 of RFC 2119 as stored at /var/www/whatthespec.net/data/data/rfcs/rfc2119.txt quote:may

RFC 8174, section 1 cited

Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words This document updates RFC 2119 by clarifying that only UPPERCASE usage of the key words have the defined special meanings. How it was counted: the words of section 1 of RFC 8174 as stored at /var/www/whatthespec.net/data/data/rfcs/rfc8174.txt quote:uppercase-only

Working group 21

3GPP cited

A 3GPP body with its own meeting series: 94 meetings recorded, from 1998-12-07 to 2026-09-15 94 How it was counted: rows in table `meetings` where the body name is '3GPP', read from /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite on 2026-08-04. The last date may be a meeting already scheduled rather than one held group:3gpp

3GPP CT cited

A 3GPP body with its own meeting series: 110 meetings recorded, from 2005-03-11 to 2028-06-12 110 How it was counted: rows in table `meetings` where the body name is '3GPP CT', read from /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite on 2026-08-04. The last date may be a meeting already scheduled rather than one held group:3gpp-ct

3GPP CT 1 cited

A 3GPP body with its own meeting series: 184 meetings recorded, from 2005-04-25 to 2028-05-22 184 How it was counted: rows in table `meetings` where the body name is '3GPP CT 1', read from /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite on 2026-08-04. The last date may be a meeting already scheduled rather than one held group:3gpp-ct-1

3GPP CT 3 cited

A 3GPP body with its own meeting series: 171 meetings recorded, from 2005-04-25 to 2028-05-22 171 How it was counted: rows in table `meetings` where the body name is '3GPP CT 3', read from /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite on 2026-08-04. The last date may be a meeting already scheduled rather than one held group:3gpp-ct-3

3GPP CT 4 cited

A 3GPP body with its own meeting series: 179 meetings recorded, from 2005-04-25 to 2028-05-22 179 How it was counted: rows in table `meetings` where the body name is '3GPP CT 4', read from /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite on 2026-08-04. The last date may be a meeting already scheduled rather than one held group:3gpp-ct-4

3GPP CT 6 cited

A 3GPP body with its own meeting series: 123 meetings recorded, from 2005-04-12 to 2028-05-23 123 How it was counted: rows in table `meetings` where the body name is '3GPP CT 6', read from /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite on 2026-08-04. The last date may be a meeting already scheduled rather than one held group:3gpp-ct-6

3GPP OP cited

A 3GPP body with its own meeting series: 58 meetings recorded, from 2015-04-29 to 2026-10-22 58 How it was counted: rows in table `meetings` where the body name is '3GPP OP', read from /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite on 2026-08-04. The last date may be a meeting already scheduled rather than one held group:3gpp-op

3GPP PCG cited

A 3GPP body with its own meeting series: 64 meetings recorded, from 1999-07-06 to 2026-10-21 64 How it was counted: rows in table `meetings` where the body name is '3GPP PCG', read from /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite on 2026-08-04. The last date may be a meeting already scheduled rather than one held group:3gpp-pcg

3GPP RAN cited

A 3GPP body with its own meeting series: 160 meetings recorded, from 1998-12-07 to 2028-06-12 160 How it was counted: rows in table `meetings` where the body name is '3GPP RAN', read from /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite on 2026-08-04. The last date may be a meeting already scheduled rather than one held group:3gpp-ran

3GPP RAN 1 cited

A 3GPP body with its own meeting series: 232 meetings recorded, from 1999-01-21 to 2028-05-22 232 How it was counted: rows in table `meetings` where the body name is '3GPP RAN 1', read from /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite on 2026-08-04. The last date may be a meeting already scheduled rather than one held group:3gpp-ran-1

3GPP RAN 2 cited

A 3GPP body with its own meeting series: 243 meetings recorded, from 1999-01-18 to 2028-05-22 243 How it was counted: rows in table `meetings` where the body name is '3GPP RAN 2', read from /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite on 2026-08-04. The last date may be a meeting already scheduled rather than one held group:3gpp-ran-2

3GPP RAN 3 cited

A 3GPP body with its own meeting series: 233 meetings recorded, from 1999-02-02 to 2028-05-22 233 How it was counted: rows in table `meetings` where the body name is '3GPP RAN 3', read from /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite on 2026-08-04. The last date may be a meeting already scheduled rather than one held group:3gpp-ran-3

3GPP RAN 4 cited

A 3GPP body with its own meeting series: 239 meetings recorded, from 1999-01-21 to 2028-05-22 239 How it was counted: rows in table `meetings` where the body name is '3GPP RAN 4', read from /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite on 2026-08-04. The last date may be a meeting already scheduled rather than one held group:3gpp-ran-4

3GPP RAN 5 cited

A 3GPP body with its own meeting series: 208 meetings recorded, from 2005-03-01 to 2028-05-22 208 How it was counted: rows in table `meetings` where the body name is '3GPP RAN 5', read from /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite on 2026-08-04. The last date may be a meeting already scheduled rather than one held group:3gpp-ran-5

3GPP SA cited

A 3GPP body with its own meeting series: 173 meetings recorded, from 1998-12-07 to 2028-06-13 173 How it was counted: rows in table `meetings` where the body name is '3GPP SA', read from /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite on 2026-08-04. The last date may be a meeting already scheduled rather than one held group:3gpp-sa

3GPP SA 1 cited

A 3GPP body with its own meeting series: 230 meetings recorded, from 1999-02-01 to 2028-05-22 230 How it was counted: rows in table `meetings` where the body name is '3GPP SA 1', read from /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite on 2026-08-04. The last date may be a meeting already scheduled rather than one held group:3gpp-sa-1

3GPP SA 2 cited

A 3GPP body with its own meeting series: 301 meetings recorded, from 1999-01-20 to 2028-05-22 301 How it was counted: rows in table `meetings` where the body name is '3GPP SA 2', read from /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite on 2026-08-04. The last date may be a meeting already scheduled rather than one held group:3gpp-sa-2

3GPP SA 3 cited

A 3GPP body with its own meeting series: 363 meetings recorded, from 1999-02-02 to 2028-05-22 363 How it was counted: rows in table `meetings` where the body name is '3GPP SA 3', read from /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite on 2026-08-04. The last date may be a meeting already scheduled rather than one held group:3gpp-sa-3

3GPP SA 4 cited

A 3GPP body with its own meeting series: 404 meetings recorded, from 1999-01-21 to 2028-05-22 404 How it was counted: rows in table `meetings` where the body name is '3GPP SA 4', read from /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite on 2026-08-04. The last date may be a meeting already scheduled rather than one held group:3gpp-sa-4

3GPP SA 5 cited

A 3GPP body with its own meeting series: 443 meetings recorded, from 1999-01-18 to 2028-05-22 443 How it was counted: rows in table `meetings` where the body name is '3GPP SA 5', read from /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite on 2026-08-04. The last date may be a meeting already scheduled rather than one held group:3gpp-sa-5

3GPP SA 6 cited

A 3GPP body with its own meeting series: 112 meetings recorded, from 2015-01-13 to 2028-05-22 112 How it was counted: rows in table `meetings` where the body name is '3GPP SA 6', read from /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite on 2026-08-04. The last date may be a meeting already scheduled rather than one held group:3gpp-sa-6

RFC 15

RFC 2026 cited

The Internet Standards Process -- Revision 3 rfc:2026

RFC 6410 cited

Reducing the Standards Track to Two Maturity Levels rfc:6410

RFC 2418 cited

IETF Working Group Guidelines and Procedures rfc:2418

RFC 7282 cited

On Consensus and Humming in the IETF rfc:7282

RFC 3935 cited

A Mission Statement for the IETF rfc:3935

RFC 2028 cited

The Organizations Involved in the IETF Standards Process rfc:2028

RFC 2119 cited

Key words for use in RFCs to Indicate Requirement Levels rfc:2119

RFC 8174 cited

Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words rfc:8174

RFC 7322 cited

RFC Style Guide rfc:7322

RFC 7841 cited

RFC Streams, Headers, and Boilerplates rfc:7841

RFC 8179 cited

Intellectual Property Rights in IETF Technology rfc:8179

RFC 8126 cited

Guidelines for Writing an IANA Considerations Section in RFCs rfc:8126

RFC 3629 cited

UTF-8, a transformation format of ISO 10646 rfc:3629

RFC 8729 cited

The RFC Series and RFC Editor rfc:8729

RFC 9280 cited

RFC Editor Model (Version 3) rfc:9280

Specification 10

TR 21.900 v20.0.0

Technical Specification Group working methods spec:21.900

TR 21.801 v19.1.0 cited

Specification drafting rules spec:21.801

TR 21.905 v19.2.0 cited

Vocabulary for 3GPP Specifications spec:21.905

TR 21.802 v1.2.1 cited

Study on Modernization of Specification Format and Procedures for 6G spec:21.802

TS 21.101 v19.0.0 cited

Technical Specifications and Technical Reports for a UTRAN-based 3GPP system spec:21.101

TS 21.201 v19.0.0 cited

Technical Specifications and Technical Reports for an Evolved Packet System (EPS) based 3GPP system spec:21.201

TS 21.202 v19.1.0 cited

Technical Specifications and Technical Reports relating to the Common IP Multimedia Subsystem (IMS) spec:21.202

TS 21.205 v19.0.0 cited

Technical Specifications and Technical Reports for a 5G based 3GPP system spec:21.205

TR 21.919 v19.0.0 cited

Release 19 Description; Summary of Rel-19 Work Items spec:21.919

TS 21.111 v19.0.0 cited

USIM and IC card requirements spec:21.111

Page on the standards body's own site 7

The 3GPP website cited

Meeting calendars, minutes, documents and the latest specifications. How it was counted: the address as written in TR 21.900 clause 7.6 page:3gpp-web

The 3GPP portal cited

Where a change request reserves its number and where the decisions on it are recorded. How it was counted: the address as written in TR 21.900 clause 7.6 page:3gpp-portal

The change-request database cited

Every change request ever raised against a 3GPP specification. How it was counted: the address as written in TR 21.900 clause 4.6.2 page:cr-database

Change requests, step by step cited

3GPP's own guidance on filling in a change-request form. How it was counted: the address as written in TR 21.900 clause 4.6.2 page:cr-step-by-step

The 3GPP Working Procedures cited

The rules of the partnership itself, above the working methods. How it was counted: the address as written in the reference list of TR 21.900, reference [8] page:working-procedures

The IETF website cited

The current list of working groups and areas, which no document carries because it changes. How it was counted: the address as written in RFC 2418 section 1, where it is written http://www.ietf.org page:ietf-web

TR 21.900 as a readable web page cited

The parsed working-methods document this course is built on, clause by clause. How it was counted: the address as written in the FriendlySpec viewer on this machine page:whatthespec-21900

Nothing here matches that. Try a shorter word.