Cheat sheet
IMS — the call as an internet session
3GPP's IMS work in one morning
- Depth
- Overview
- Chapters
- 7
- Reading
- 45 min
- Questions
- 33
- Sources cited
- 193
The shape of it
1 What IMS is, and where it came from
- 1 What IMS is, in the words of its own documents
- 2 The founding: Release 5 and the ring of work around it
- 3 Rebuilt for every new network: circuits, LTE, the browser, 5G
2 Who does the work, and what they write
- 4 Who does the work: fourteen groups, and a core-network shape
- 5 What they write: the IMS family of specifications
3 Where it stands, and how to follow it
Keep these in your head
-
1.2 What IMS is, in the words of its own documents
Four documents, one subject. TS 22.228 says what IMS must do, TS 23.228 how it is put together, TS 23.218 how one session runs from start to finish, and TS 24.229 what the messages look like. Nobody works from one of them alone.
-
2.2 The founding: Release 5 and the ring of work around it
The IMS work item opened as a stage 1 job — what the service must do, not how it is built. The architecture, the protocol, the security and the charging each opened as their own work plan rows beside it.
-
3.3 Rebuilt for every new network: circuits, LTE, the browser, 5G
Most IMS work is not a new feature. Reaching the old circuit network, meeting an emergency-call rule, keeping a session alive across networks, recovering after a failure — release after release, the same system is made to hold up in one more situation.
-
4.3 Who does the work: fourteen groups, and a core-network shape
IMS is core-network work. The three largest document counts in this record are CT working groups — CT1 with 2169, CT4 with 746 and CT3 with 719 — and the largest radio-side count is RAN5's 147, which is conformance testing rather than radio design.
-
5.7 What they write: the IMS family of specifications
TS 29.562, the 5G system's subscriber-server services, is the second-largest target in this register: 230 IMS documents change it, against 92 for TS 23.228, the stage 2 description of IMS itself. Not one of the 5G core documents this work edits has the letters IMS in its title.
-
6.1 Maintenance, and what is running now
Most IMS paperwork is upkeep, not invention: 3509 of the 4939 documents in the local record are change requests, and 1680 of those edit one document, the stage 3 protocol TS 24.229.
-
7.1 Following it yourself, and what the record cannot tell you
Search 3GPP by the work item acronym, never by the subject. Four IMS work items — IMS, IMS-CODEC, IMS_SSFDD and IMS_Corp2 — do not have the letters IMS anywhere in their titles, so a title search loses them silently.
Easy to get wrong
One from each chapter that has one. The course carries 9 in all.
-
1.5 What IMS is, in the words of its own documents
IMS is not SIP. TS 24.229 defines a call control protocol based on SIP and SDP for use in the IM CN subsystem — the protocol is one document out of four, and the other three define the subsystem without mentioning a message at all.
-
2.1 The founding: Release 5 and the ring of work around it
SP-000216, the paper the work plan names as the one that opened IMS, has no title in this store, and meeting SP-8 has no days and no place. Both may be named and neither may be described or dated. Thirty-two of the papers that opened a work item are like that — the store has the number, the meeting and the file address, and nothing else.
-
3.6 Rebuilt for every new network: circuits, LTE, the browser, 5G
Rows per release and documents per work item are two different measurements, and neither one is "how much work happened". Rel-16 carries only 13 IMS work plan rows [1], and it also holds eIMS5G_SBA, the acronym with 543 documents behind it — more than any other in this register [2]. Both numbers are true and they answer different questions.
-
4.3 Who does the work: fourteen groups, and a core-network shape
RAN2 has exactly one IMS document in this record, at meeting R2-92, tagged with the acronym IMS-CODEC. The register does not record what kind of document it is, so never call it a change request, a liaison or work of RAN2's own — that would be inventing a field nobody stored.
-
5.2 What they write: the IMS family of specifications
A change-request count is a count of edits, not a ranking of importance. TS 23.228 takes 92 and TS 24.229 takes 1680, and all that says is that the description of a system is edited less often than the protocol that carries it.
-
6.5 Maintenance, and what is running now
"Deleted" at the front of a 3GPP work plan title is text somebody typed into the name, not a status field. FS_IMSRE_SEC carries that word and an approved study paper and 16 documents at the same time, so quoting one half of that is misleading either way.
-
7.4 Following it yourself, and what the record cannot tell you
Every document count in this course is a floor, not a total. The record holds nothing earlier than 2015-01-23 and IMS work opened in Rel-5, so the years before that date are missing from every number on this site.
The numbers, and where each came from
Every one was counted out of a file on this machine. Hover a row to read the question that produced it.
- 14 14 IMS work plan rows are marked Rel-5
- 2015-01-23 the earliest IMS document on record went up on 2015-01-23
- 17 17 IMS work plan rows are marked Rel-6
- 207 207 documents carry the work item IMS-CCR-IWCS
- 64 64 IMS work plan rows are marked Rel-8
- 45 45 IMS work plan rows are marked Rel-9
- 60 60 IMS work plan rows are marked Rel-12
- 543 543 documents carry the work item eIMS5G_SBA
- 13 13 IMS work plan rows are marked Rel-16
- 309 309 meetings have had IMS documents on the table
- 206 C1-112 handled 206 IMS documents, more than any other single meeting
- 374 374 different names appear as the writer of an IMS document
- 602 Ericsson filed 602 IMS documents
- 258 Nokia, Nokia Shanghai Bell filed 258 IMS documents
- 173 Huawei filed 173 IMS documents
- 167 China Mobile filed 167 IMS documents
- 130 Ericsson / Nevenka filed 130 IMS documents
- 241 241 specifications this work touches
- 3599 3599 3GPP specifications are marked active altogether
- 1680 1680 IMS documents name 24.229 as the document they change
- 4939 4939 IMS meeting documents
- 3509 3509 IMS documents are of type CR
- 767 767 IMS documents are of type pCR
- 92 92 IMS documents name 23.228 as the document they change
- 1942 1942 IMS documents carry the outcome word revised
- 1736 1736 IMS documents carry the outcome word agreed
- 379 379 IMS documents carry the outcome word approved
- 297 297 IMS documents carry the outcome word postponed
- 189 189 IMS documents carry the outcome word withdrawn
- 364 364 documents carry the work item IMSProtoc7
- 10 10 IMS work plan rows are marked Rel-19
- 7 7 IMS work plan rows are marked Rel-20
- 345 345 rows of the 3GPP work plan are IMS work
- 177 177 different work item acronyms carry IMS
- 163 163 of those acronyms survive a boundary that also forbids a lower-case letter
- 1629723 the document store holds 1629723 meeting documents altogether
- 157 157 of the 177 IMS acronyms have a work item description on this machine
- 36 36 work items are quoted here in their proposers' own words
- 22 22 IMS work item acronyms carry the word Deleted at the front of their own name
- 1 1 IMS work item acronyms carry the word STOPPED at the front of their own name
- 339 339 of the 345 IMS work plan rows stand at 100%
- 237 237 IMS documents carry no upload time
Where to look it up
The 151 named sources it cites, by what they are.
Quoted wording 48
the scope of 22.228the scope of 23.228the scope of 23.218the scope of 24.229"IM CN subsystem" as 22.228 defines it"IP multimedia session" as 22.228 defines it"IP multimedia application" as 22.228 defines it"IP multimedia service" as 22.228 defines it"Access independence" as 22.228 defines it"Application data channel" as 23.228 defines it"Data channel application" as 23.228 defines itwhat IMS set out to dowhy IMS was proposedwhat IMS-CODEC set out to dowhy IMS-CCR-IWCS was proposedwhy IMS_EMER_GPRS_EPS was proposedwhy IMS_SCC was proposedwhy IMS_WebRTC was proposedwhy IMS_TELEP was proposedwhy 5GS_Ph1-IMSo5G was proposedwhy FS_eIMS5G was proposedwhat IMS-CCR-IWCS set out to dowhat IMS_EMER_GPRS_EPS set out to dowhat eIMS_RP set out to dowhy eIMS_RP was proposedwhat IMS_WebRTC set out to dowhat IMS_TELEP set out to dowhat 5GS_Ph1-IMSo5G set out to dowhat FS_eIMS5G set out to dowhat eIMS5G_SBA set out to dowhy FS_eIMS5G2 was proposedwhat IMS_IBCF set out to dothe scope of 23.380the scope of 23.334the scope of 22.173the scope of 23.237the scope of 23.292the scope of 23.167why IMSProtoc2 was proposedwhy IMSProtoc20-CT was proposedwhy FS_IMS_RES was proposedwhy FS_IMSResil was proposedwhat IMSProtoc2 set out to dowhat IMS_RES-CT set out to dowhat SR_IMS set out to dowhat FS_enIMS_ARC set out to dowhat AIML_IMS-MED set out to dowhy AIML_IMS-MED was proposed
Work item 48
IMSIMS-ASECIMS-LIIMS-CCRIMS-CCR-IWMMIMS-CAMELIMS-ONOSAIMS-OAMIMS-CODECIMS-TESTIMS-CCR_TestIMS_CONV_IP_COM-UEConTestIMS-FrWkIMS-SexIMS-CCR-IWCSIMS_EMER_GPRS_EPSIMS_SCCIMS_WebRTCIMS_WebRTC-CTIMS_TELEPIMS_TELEP_S45GS_Ph1-IMSo5GFS_eIMS5GFS_eIMS5G2IMS_IBCFIMSProtocIMSProtoc2IMSProtoc3IMSProtoc4IMSProtoc5IMSProtoc6IMSProtoc7IMSProtoc8IMSProtoc9IMSProtoc16IMSProtoc17IMSProtoc18IMSProtoc19IMSProtoc20-CTFS_IMS_RESIMS_RES-CTSR_IMSFS_IMSResilFS_enIMS_ARCAIML_IMS-MEDFS_IMSRE_SECIMS_SSFDDIMS_Corp2
Specification 32
TS 22.228TS 23.228TS 23.218TS 24.229TS 23.292TS 23.237TS 23.380TS 24.371TS 26.223TR 23.794TR 23.700-10TS 29.163TS 34.229-1TS 23.167TS 23.334TS 22.173TS 29.165TS 33.226TR 33.926TR 23.700-11TR 23.700-12TR 29.866TR 29.867TS 29.562TS 29.514TS 29.513TS 23.501TR 22.823TS 26.567TS 26.114TR 23.801-03TR 23.801-04
Working group 14
SA4CT1CT4CT3SA2RAN5SA3SA1SA5CT6RAN2CTSARAN
Meeting document 8
SP-000216RP-171635CP-060101CP-261069SP-260686SP-250878CP-260044SP-251237
Meeting 1
Where to go from here
- The same subject, quick start — Under an hour, four chapters, the shape of the thing.
- The same subject, in depth — The working reference: every mechanism, every parameter.
- Every question of this course — 33 of them, on one page.
- The final test — 12 questions, 70 per cent to pass.
- Every source behind the course — 858 of them, each with its method.
The raised numbers on this page
- 13 IMS work plan rows are marked Rel-16 — rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite taken in by the acronym rule whose release field is exactly 'Rel-16', read 2026-08-05
- 543 documents carry the work item eIMS5G_SBA — rows of `tdoc` whose work item column names eIMS5G_SBA as a whole word, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05; the first and last meeting are those of its earliest and latest upload stamp