Everything this course is built on

Specification 241

TS 22.011

Service accessibility How it was counted: the catalogue row and every stored release of 22.011, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 22.011; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:22.011

TS 22.101 cited

Service aspects; Service principles How it was counted: the catalogue row and every stored release of 22.101, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 22.101; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:22.101

TS 22.115

Service aspects; Charging and billing How it was counted: the catalogue row and every stored release of 22.115, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 22.115; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:22.115

TS 22.127

Service requirement for the Open Services Access (OSA); Stage 1 How it was counted: the catalogue row and every stored release of 22.127, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 22.127; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:22.127

TS 22.173 cited

IP Multimedia Core Network Subsystem (IMS) Multimedia Telephony Service and supplementary services; Stage 1 How it was counted: the catalogue row and every stored release of 22.173, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 22.173; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:22.173

TS 22.179

Mission Critical Push to Talk (MCPTT); Stage 1 How it was counted: the catalogue row and every stored release of 22.179, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 22.179; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:22.179

TS 22.228 cited

Service requirements for the Internet Protocol (IP) multimedia core network subsystem (IMS); Stage 1 How it was counted: the catalogue row and every stored release of 22.228, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 22.228; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:22.228

TS 22.261

Service requirements for the 5G system How it was counted: the catalogue row and every stored release of 22.261, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 22.261; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:22.261

TS 22.273

TISPAN; Multimedia Telephony with PSTN/ISDN simulation services How it was counted: the catalogue row and every stored release of 22.273, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 22.273; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:22.273

TS 22.280

Mission Critical Services Common Requirements (MCCoRe); Stage 1 How it was counted: the catalogue row and every stored release of 22.280, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 22.280; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:22.280

TS 22.281

Mission Critical (MC) video How it was counted: the catalogue row and every stored release of 22.281, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 22.281; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:22.281

TS 22.282

Mission Critical (MC) data How it was counted: the catalogue row and every stored release of 22.282, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 22.282; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:22.282

TS 22.340

IP Multimedia Subsystem (IMS) messaging; Stage 1 How it was counted: the catalogue row and every stored release of 22.340, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 22.340; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:22.340

TS 22.401

TISPAN; Videotelephony over NGN Service Description How it was counted: the catalogue row and every stored release of 22.401, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 22.401; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:22.401

TS 22.468

Group Communication System Enablers (GCSE) How it was counted: the catalogue row and every stored release of 22.468, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 22.468; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:22.468

TS 22.519

Business communication requirements How it was counted: the catalogue row and every stored release of 22.519, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 22.519; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:22.519

TR 22.823 cited

Study on enhancements to IMS for new real time communication services How it was counted: the catalogue row and every stored release of 22.823, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 22.823; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:22.823

TR 22.906

Study on IMS based peer-to-peer content distribution services How it was counted: the catalogue row and every stored release of 22.906, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 22.906; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:22.906

TR 22.940

IP Multimedia Subsystem (IMS) messaging How it was counted: the catalogue row and every stored release of 22.940, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 22.940; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:22.940

TR 22.941

IP based multimedia framework; Stage 0 How it was counted: the catalogue row and every stored release of 22.941, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 22.941; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:22.941

TR 22.948

Study of requirements of IP-Multimedia Subsystem (IMS) convergent multimedia conferencing How it was counted: the catalogue row and every stored release of 22.948, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 22.948; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:22.948

TR 22.979

Feasibility study on combined Circuit Switched (CS) calls and IP Multimedia Subsystem (IMS) sessions How it was counted: the catalogue row and every stored release of 22.979, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 22.979; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:22.979

TS 23.002

Network architecture How it was counted: the catalogue row and every stored release of 23.002, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 23.002; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:23.002

TS 23.003 cited

Numbering, addressing and identification How it was counted: the catalogue row and every stored release of 23.003, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 23.003; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:23.003

TS 23.008 cited

Organization of subscriber data How it was counted: the catalogue row and every stored release of 23.008, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 23.008; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:23.008

TS 23.060

General Packet Radio Service (GPRS); Service description; Stage 2 How it was counted: the catalogue row and every stored release of 23.060, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 23.060; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:23.060

TS 23.122

Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode How it was counted: the catalogue row and every stored release of 23.122, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 23.122; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:23.122

TS 23.167 cited

IP Multimedia Subsystem (IMS) emergency sessions How it was counted: the catalogue row and every stored release of 23.167, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 23.167; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:23.167

TS 23.198

Open Service Access (OSA); Stage 2 How it was counted: the catalogue row and every stored release of 23.198, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 23.198; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:23.198

TS 23.203

Policy and charging control architecture How it was counted: the catalogue row and every stored release of 23.203, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 23.203; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:23.203

TS 23.204 cited

Support of Short Message Service (SMS) over generic 3GPP Internet Protocol (IP) access; Stage 2 How it was counted: the catalogue row and every stored release of 23.204, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 23.204; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:23.204

TS 23.216

Single Radio Voice Call Continuity (SRVCC); Stage 2 How it was counted: the catalogue row and every stored release of 23.216, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 23.216; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:23.216

TS 23.218 cited

IP Multimedia (IM) session handling; IM call model; Stage 2 How it was counted: the catalogue row and every stored release of 23.218, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 23.218; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:23.218

TS 23.221

Architectural requirements How it was counted: the catalogue row and every stored release of 23.221, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 23.221; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:23.221

TS 23.228 cited

IP Multimedia Subsystem (IMS); Stage 2 How it was counted: the catalogue row and every stored release of 23.228, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 23.228; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:23.228

TS 23.237 cited

IP Multimedia Subsystem (IMS) Service Continuity; Stage 2 How it was counted: the catalogue row and every stored release of 23.237, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 23.237; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:23.237

TS 23.271

Functional stage 2 description of Location Services (LCS) How it was counted: the catalogue row and every stored release of 23.271, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 23.271; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:23.271

TS 23.292 cited

IP Multimedia Subsystem (IMS) centralized services; Stage 2 How it was counted: the catalogue row and every stored release of 23.292, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 23.292; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:23.292

TS 23.333

Multimedia Resource Function Controller (MRFC) - Multimedia Resource Function Processor (MRFP) Mp interface: Procedures descriptions How it was counted: the catalogue row and every stored release of 23.333, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 23.333; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:23.333

TS 23.334 cited

IP Multimedia Subsystem (IMS) Application Level Gateway (IMS-ALG) - IMS Access Gateway (IMS-AGW) interface: Procedures descriptions How it was counted: the catalogue row and every stored release of 23.334, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 23.334; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:23.334

TS 23.380 cited

IMS Restoration Procedures How it was counted: the catalogue row and every stored release of 23.380, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 23.380; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:23.380

TS 23.401 cited

General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access How it was counted: the catalogue row and every stored release of 23.401, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 23.401; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:23.401

TS 23.402 cited

Architecture enhancements for non-3GPP accesses How it was counted: the catalogue row and every stored release of 23.402, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 23.402; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:23.402

TS 23.406 cited

TISPAN; IP Multimedia Subsystem (IMS); Stage 2 description [3GPP TS 23.228 v7.2.0, modified] How it was counted: the catalogue row and every stored release of 23.406, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 23.406; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:23.406

TS 23.417 cited

TISPAN; IP Multimedia Subsystem (IMS); Functional architecture How it was counted: the catalogue row and every stored release of 23.417, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 23.417; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:23.417

TS 23.501 cited

System architecture for the 5G System (5GS) How it was counted: the catalogue row and every stored release of 23.501, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 23.501; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:23.501

TS 23.502 cited

Procedures for the 5G System (5GS) How it was counted: the catalogue row and every stored release of 23.502, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 23.502; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:23.502

TS 23.503 cited

Policy and charging control framework for the 5G System (5GS); Stage 2 How it was counted: the catalogue row and every stored release of 23.503, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 23.503; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:23.503

TS 23.506 cited

TISPAN; IP Multimedia Subsystem (IMS); Stage 2 description [3GPP TS 23.228 Release 7, modified] How it was counted: the catalogue row and every stored release of 23.506, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 23.506; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:23.506

TS 23.508

TISPAN; Presence Service; Architecture and functional description [Endorsement of 3GPP TS 23.141 and OMA-AD-Presence_SIMPLE-V1_0] How it was counted: the catalogue row and every stored release of 23.508, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 23.508; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:23.508

TS 23.509

TISPAN; NGN Architecture to support emergency communication from citizen to authority [Endorsed document 3GPP TS 23.167, Release 7] How it was counted: the catalogue row and every stored release of 23.509, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 23.509; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:23.509

TS 23.511

TISPAN; XML Document Management; Architecture and functional description [OMA-AD-XDM-V1_0-20051006-C modified] How it was counted: the catalogue row and every stored release of 23.511, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 23.511; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:23.511

TS 23.521 cited

Telecommunications and Internet converged Services and Protocols for Advanced Networks (TISPAN); Support of Short Message Service (SMS) over NGN IMS subsystem; Stage 2; [Endorsement of 3GPP TS 23.204 Release 7] How it was counted: the catalogue row and every stored release of 23.521, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 23.521; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:23.521

TR 23.700-10 cited

Study on enhanced IP Multimedia Subsystem (IMS) to 5GC integration Phase 2; CT WG1 aspects How it was counted: the catalogue row and every stored release of 23.700-10, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 23.700-10; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:23.700-10

TR 23.700-11 cited

Study on enhanced IP Multimedia Subsystem (IMS) to 5GC integration Phase 2; CT WG3 aspects How it was counted: the catalogue row and every stored release of 23.700-11, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 23.700-11; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:23.700-11

TR 23.700-12 cited

Study on enhanced IP Multimedia Subsystem (IMS) to 5GC integration Phase 2; CT WG4 aspects How it was counted: the catalogue row and every stored release of 23.700-12, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 23.700-12; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:23.700-12

TR 23.701

Study on Web Real Time Communication (WebRTC) access to IP Multimedia Subsystem (IMS); Stage 2 How it was counted: the catalogue row and every stored release of 23.701, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 23.701; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:23.701

TR 23.794 cited

Study on enhanced IP Multimedia Subsystem (IMS) to 5GC integration How it was counted: the catalogue row and every stored release of 23.794, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 23.794; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:23.794

TR 23.801-03 cited

Study on MC architecture evolution and 6G capabilities for MC services How it was counted: the catalogue row and every stored release of 23.801-03, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 23.801-03; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:23.801-03

TR 23.801-04 cited

Study on IMS Architecture Enhancement How it was counted: the catalogue row and every stored release of 23.801-04, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 23.801-04; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:23.801-04

TR 23.812

Feasibility study on IP Multimedia Subsystem (IMS) evolution How it was counted: the catalogue row and every stored release of 23.812, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 23.812; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:23.812

TR 23.818

Optimisations and Enhancements for Realtime IMS Communication How it was counted: the catalogue row and every stored release of 23.818, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 23.818; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:23.818

TR 23.820 cited

Study of IMS restoration procedures How it was counted: the catalogue row and every stored release of 23.820, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 23.820; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:23.820

TR 23.821 cited

Architecture Principles for Reelase 2000 How it was counted: the catalogue row and every stored release of 23.821, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 23.821; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:23.821

TR 23.822

Framework for Gq' / Rx harmonization How it was counted: the catalogue row and every stored release of 23.822, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 23.822; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:23.822

TR 23.831

IP Multimedia Subsystem (IMS) service continuity; Inter-UE transfer enhancements; Stage 2 How it was counted: the catalogue row and every stored release of 23.831, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 23.831; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:23.831

TR 23.832

IP Multimedia Subsystem (IMS) aspects of architecture for Home Node B (HNB); Stage 2 How it was counted: the catalogue row and every stored release of 23.832, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 23.832; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:23.832

TR 23.838

IP Multimedia Subsystem (IMS) service continuity enhancements; Service, policy and interaction; Stage 2 How it was counted: the catalogue row and every stored release of 23.838, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 23.838; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:23.838

TR 23.842

Study on network provided location information to the IP Multimedia Subsystem (IMS) How it was counted: the catalogue row and every stored release of 23.842, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 23.842; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:23.842

TR 23.844

Feasibility study on IP Multimedia Subsystem (IMS) based peer-to-peer content distribution services; Stage 2 How it was counted: the catalogue row and every stored release of 23.844, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 23.844; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:23.844

TR 23.847

Enhancements to IMS service functionalities facilitating multicast bearer services How it was counted: the catalogue row and every stored release of 23.847, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 23.847; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:23.847

TR 23.848

Study on enhancements to IP Multimedia Subsystem (IMS) border functions for interconnection of IMS based services How it was counted: the catalogue row and every stored release of 23.848, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 23.848; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:23.848

TR 23.864

Commonality and interoperability between IP Multimedia System (IMS) core networks How it was counted: the catalogue row and every stored release of 23.864, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 23.864; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:23.864

TR 23.867

Internet Protocol (IP) based IP Multimedia Subsystem (IMS) emergency sessions How it was counted: the catalogue row and every stored release of 23.867, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 23.867; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:23.867

TR 23.868

Feasibility study on extension of support for IP Multimedia Subsystem (IMS) emergency calls How it was counted: the catalogue row and every stored release of 23.868, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 23.868; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:23.868

TR 23.869 cited

Support for Internet Protocol (IP) based IP Multimedia Subsystem (IMS) Emergency calls over General Packet Radio Service (GPRS) and Evolved Packet Service (EPS) How it was counted: the catalogue row and every stored release of 23.869, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 23.869; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:23.869

TR 23.870

Single Radio Voice Call Continuity (SR-VCC) support for IMS Emergency Calls How it was counted: the catalogue row and every stored release of 23.870, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 23.870; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:23.870

TR 23.883

Study on enhancements to IMS Centralized Services (ICS) How it was counted: the catalogue row and every stored release of 23.883, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 23.883; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:23.883

TR 23.892

IP Multimedia Subsystem (IMS) centralized services How it was counted: the catalogue row and every stored release of 23.892, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 23.892; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:23.892

TR 23.894

System enhancements for the use of IP Multimedia Subsystem (IMS) services in local breakout and optimal routeing of media How it was counted: the catalogue row and every stored release of 23.894, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 23.894; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:23.894

TR 23.899

Combining Circuit Switched (CS) bearers with IP Multimeida Subsystem (IMS) How it was counted: the catalogue row and every stored release of 23.899, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 23.899; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:23.899

TR 23.981

Interworking aspects and migration scenarios for IPv4-based IP Multimedia Subsystem (IMS) implementations How it was counted: the catalogue row and every stored release of 23.981, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 23.981; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:23.981

TS 24.008

Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 How it was counted: the catalogue row and every stored release of 24.008, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 24.008; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:24.008

TS 24.103 cited

Telepresence using the IP Multimedia (IM) Core Network (CN) Subsystem (IMS); Stage 3 How it was counted: the catalogue row and every stored release of 24.103, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 24.103; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:24.103

TS 24.141

Presence service using the IP Multimedia (IM) Core Network (CN) subsystem; Stage 3 How it was counted: the catalogue row and every stored release of 24.141, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 24.141; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:24.141

TS 24.147 cited

Conferencing using the IP Multimedia (IM) Core Network (CN) subsystem; Stage 3 How it was counted: the catalogue row and every stored release of 24.147, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 24.147; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:24.147

TS 24.166

3GPP IP Multimedia Subsystem (IMS) conferencing Management Object (MO) How it was counted: the catalogue row and every stored release of 24.166, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 24.166; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:24.166

TS 24.167 cited

3GPP IMS Management Object (MO); Stage 3 How it was counted: the catalogue row and every stored release of 24.167, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 24.167; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:24.167

TS 24.173

IMS Multimedia telephony communication service and supplementary services; Stage 3 How it was counted: the catalogue row and every stored release of 24.173, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 24.173; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:24.173

TS 24.182

IP Multimedia Subsystem (IMS) Customized Alerting Tones (CAT); Protocol specification How it was counted: the catalogue row and every stored release of 24.182, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 24.182; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:24.182

TS 24.183

IP Multimedia Subsystem (IMS) Customized Ringing Signal (CRS); Protocol specification How it was counted: the catalogue row and every stored release of 24.183, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 24.183; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:24.183

TS 24.186 cited

IMS Data Channel applications; Protocol specification How it was counted: the catalogue row and every stored release of 24.186, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 24.186; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:24.186

TS 24.216

Communication Continuity Management Object (MO) How it was counted: the catalogue row and every stored release of 24.216, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 24.216; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:24.216

TS 24.228 cited

Signalling flows for the IP multimedia call control based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 How it was counted: the catalogue row and every stored release of 24.228, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 24.228; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:24.228

TS 24.229 cited

IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 How it was counted: the catalogue row and every stored release of 24.229, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 24.229; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:24.229

TS 24.237

IP Multimedia (IM) Core Network (CN) subsystem IP Multimedia Subsystem (IMS) service continuity; Stage 3 How it was counted: the catalogue row and every stored release of 24.237, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 24.237; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:24.237

TS 24.292

IP Multimedia (IM) Core Network (CN) subsystem Centralized Services (ICS); Stage 3 How it was counted: the catalogue row and every stored release of 24.292, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 24.292; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:24.292

TS 24.294

IP Multimedia Subsystem (IMS) Centralized Services (ICS) protocol via I1 interface How it was counted: the catalogue row and every stored release of 24.294, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 24.294; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:24.294

TS 24.301

Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 How it was counted: the catalogue row and every stored release of 24.301, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 24.301; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:24.301

TS 24.302

Access to the 3GPP Evolved Packet Core (EPC) via non-3GPP access networks; Stage 3 How it was counted: the catalogue row and every stored release of 24.302, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 24.302; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:24.302

TS 24.305

Selective Disabling of 3GPP User Equipment Capabilities (SDoUE) Management Object (MO) How it was counted: the catalogue row and every stored release of 24.305, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 24.305; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:24.305

TS 24.341

Support of SMS over IP networks; Stage 3 How it was counted: the catalogue row and every stored release of 24.341, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 24.341; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:24.341

TS 24.371 cited

Web Real-Time Communications (WebRTC) access to the IP Multimedia (IM) Core Network (CN) subsystem (IMS); Stage 3; Protocol specification How it was counted: the catalogue row and every stored release of 24.371, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 24.371; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:24.371

TS 24.390

Unstructured Supplementary Service Data (USSD) using IP Multimedia (IM) Core Network (CN) subsystem IMS; Stage 3 How it was counted: the catalogue row and every stored release of 24.390, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 24.390; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:24.390

TS 24.424

Management Object (MO) for Extensible Markup Language (XML) Configuration Access Protocol (XCAP) over the Ut interface for Manipulating Supplementary Services (SS) How it was counted: the catalogue row and every stored release of 24.424, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 24.424; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:24.424

TS 24.501

Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 How it was counted: the catalogue row and every stored release of 24.501, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 24.501; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:24.501

TS 24.503

TISPAN; IP Multimedia Call Control Protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP) Stage 3 [3GPP TS 24.229 (Release 7), modified] How it was counted: the catalogue row and every stored release of 24.503, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 24.503; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:24.503

TS 24.524

Hosted enterprise services; Architecture, functional description and signalling How it was counted: the catalogue row and every stored release of 24.524, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 24.524; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:24.524

TS 24.525

Business trunking; Architecture and functional description How it was counted: the catalogue row and every stored release of 24.525, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 24.525; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:24.525

TS 24.604

Communication Diversion (CDIV) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification How it was counted: the catalogue row and every stored release of 24.604, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 24.604; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:24.604

TS 24.607

Originating Identification Presentation (OIP) and Originating Identification Restriction (OIR) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification How it was counted: the catalogue row and every stored release of 24.607, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 24.607; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:24.607

TS 24.608

Terminating Identification Presentation (TIP) and Terminating Identification Restriction (TIR) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification How it was counted: the catalogue row and every stored release of 24.608, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 24.608; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:24.608

TS 24.611

Anonymous Communication Rejection (ACR) and Communication Barring (CB) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification How it was counted: the catalogue row and every stored release of 24.611, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 24.611; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:24.611

TS 24.615

Communication Waiting (CW) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol Specification How it was counted: the catalogue row and every stored release of 24.615, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 24.615; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:24.615

TS 24.623

Extensible Markup Language (XML) Configuration Access Protocol (XCAP) over the Ut interface for Manipulating Supplementary Services How it was counted: the catalogue row and every stored release of 24.623, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 24.623; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:24.623

TS 24.628

Common Basic Communication procedures using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification How it was counted: the catalogue row and every stored release of 24.628, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 24.628; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:24.628

TR 24.803

Study on telepresence using the IP Multimedia (IM) Core Network (CN) Subsystem (IMS); Stage 3 How it was counted: the catalogue row and every stored release of 24.803, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 24.803; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:24.803

TR 24.930 cited

Signalling flows for the session setup in the IP Multimedia core network Subsystem (IMS) based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 How it was counted: the catalogue row and every stored release of 24.930, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 24.930; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:24.930

TR 24.969

Business trunking; Next Generation Corporate Network (NGCN) - Next Generation Network (NGN) interfaces implementation guide How it was counted: the catalogue row and every stored release of 24.969, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 24.969; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:24.969

TS 26.114 cited

IP Multimedia Subsystem (IMS); Multimedia Telephony; Media handling and interaction How it was counted: the catalogue row and every stored release of 26.114, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 26.114; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:26.114

TS 26.223 cited

Telepresence using the IP Multimedia Subsystem (IMS); Media handling and interaction How it was counted: the catalogue row and every stored release of 26.223, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 26.223; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:26.223

TS 26.234

Transparent end-to-end Packet-switched Streaming Service (PSS); Protocols and codecs How it was counted: the catalogue row and every stored release of 26.234, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 26.234; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:26.234

TS 26.235

Packet switched conversational multimedia applications; Default codecs How it was counted: the catalogue row and every stored release of 26.235, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 26.235; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:26.235

TS 26.236

Packet switched conversational multimedia applications; Transport protocols How it was counted: the catalogue row and every stored release of 26.236, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 26.236; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:26.236

TS 26.237

IP Multimedia Subsystem (IMS) based Packet Switch Streaming (PSS) and Multimedia Broadcast/Multicast Service (MBMS) User Service; Protocols How it was counted: the catalogue row and every stored release of 26.237, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 26.237; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:26.237

TS 26.264 cited

IMS-based AR Real-Time Communication How it was counted: the catalogue row and every stored release of 26.264, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 26.264; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:26.264

TS 26.346

Multimedia Broadcast/Multicast Service (MBMS); Protocols and codecs How it was counted: the catalogue row and every stored release of 26.346, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 26.346; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:26.346

TS 26.567 cited

Split rendering over IMS How it was counted: the catalogue row and every stored release of 26.567, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 26.567; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:26.567

TR 26.827

IP Multimedia Subsystem (IMS) based streaming and download delivery enhancements How it was counted: the catalogue row and every stored release of 26.827, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 26.827; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:26.827

TR 26.923

Study on media handling aspects of IP Multimedia Subsystem (IMS) based telepresence How it was counted: the catalogue row and every stored release of 26.923, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 26.923; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:26.923

TR 26.935

Packet Switched (PS) conversational multimedia applications; Performance characterisation of default codecs How it was counted: the catalogue row and every stored release of 26.935, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 26.935; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:26.935

TR 26.998

Support of 5G glass-type Augmented Reality / Mixed Reality (AR/MR) devices How it was counted: the catalogue row and every stored release of 26.998, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 26.998; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:26.998

TS 27.007

AT command set for User Equipment (UE) How it was counted: the catalogue row and every stored release of 27.007, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 27.007; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:27.007

TS 29.002

Mobile Application Part (MAP) specification How it was counted: the catalogue row and every stored release of 29.002, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 29.002; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:29.002

TS 29.060

General Packet Radio Service (GPRS); GPRS Tunnelling Protocol (GTP) across the Gn and Gp interface How it was counted: the catalogue row and every stored release of 29.060, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 29.060; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:29.060

TS 29.061 cited

Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN) How it was counted: the catalogue row and every stored release of 29.061, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 29.061; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:29.061

TS 29.162 cited

Interworking between the IM CN subsystem and IP networks How it was counted: the catalogue row and every stored release of 29.162, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 29.162; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:29.162

TS 29.163 cited

Interworking between the IP Multimedia (IM) Core Network (CN) subsystem and Circuit Switched (CS) networks How it was counted: the catalogue row and every stored release of 29.163, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 29.163; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:29.163

TS 29.165 cited

Inter-IMS Network to Network Interface (NNI) How it was counted: the catalogue row and every stored release of 29.165, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 29.165; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:29.165

TS 29.198

Open Service Architecture (OSA) Application Programming Interface (API) - Part 1 How it was counted: the catalogue row and every stored release of 29.198, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 29.198; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:29.198

TS 29.198-03

Open Service Access (OSA) Application Programming Interface (API); Part 3: Framework How it was counted: the catalogue row and every stored release of 29.198-03, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 29.198-03; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:29.198-03

TS 29.198-06

Open Service Access (OSA) Application Programming Interface (API); Part 6: Mobility Service Capability Feature (SCF) How it was counted: the catalogue row and every stored release of 29.198-06, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 29.198-06; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:29.198-06

TS 29.198-10

Open Service Access (OSA) Application Programming Interface (API); Part 10: Connectivity manager Service Capability Feature (SCF) How it was counted: the catalogue row and every stored release of 29.198-10, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 29.198-10; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:29.198-10

TS 29.198-14

Open Service Access (OSA) Application Programming Interface (API); Part 14: Presence and Availability Management (PAM) Service Capability Feature (SCF) How it was counted: the catalogue row and every stored release of 29.198-14, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 29.198-14; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:29.198-14

TS 29.199

Open Service Access (OSA); Web Services Application Programming Interface (API) for OSA; Parlay X services How it was counted: the catalogue row and every stored release of 29.199, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 29.199; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:29.199

TS 29.199-08

Open Service Access (OSA); Parlay X web services; Part 8: Terminal status How it was counted: the catalogue row and every stored release of 29.199-08, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 29.199-08; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:29.199-08

TS 29.199-21

Open Service Access (OSA); Parlay X web services; Part 21: Content management How it was counted: the catalogue row and every stored release of 29.199-21, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 29.199-21; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:29.199-21

TS 29.199-22

Open Service Access (OSA); Parlay X web services; Part 22: Policy How it was counted: the catalogue row and every stored release of 29.199-22, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 29.199-22; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:29.199-22

TS 29.205

Application of Q.1900 series to bearer independent Circuit Switched (CS) core network architecture; Stage 3 How it was counted: the catalogue row and every stored release of 29.205, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 29.205; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:29.205

TS 29.212

Policy and Charging Control (PCC); Reference points How it was counted: the catalogue row and every stored release of 29.212, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 29.212; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:29.212

TS 29.213 cited

Policy and charging control signalling flows and Quality of Service (QoS) parameter mapping How it was counted: the catalogue row and every stored release of 29.213, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 29.213; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:29.213

TS 29.214 cited

Policy and charging control over Rx reference point How it was counted: the catalogue row and every stored release of 29.214, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 29.214; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:29.214

TS 29.215

Policy and Charging Control (PCC) over S9 reference point; Stage 3 How it was counted: the catalogue row and every stored release of 29.215, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 29.215; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:29.215

TS 29.228 cited

IP Multimedia (IM) Subsystem Cx and Dx Interfaces; Signalling flows and message contents How it was counted: the catalogue row and every stored release of 29.228, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 29.228; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:29.228

TS 29.229 cited

Cx and Dx interfaces based on the Diameter protocol; Protocol details How it was counted: the catalogue row and every stored release of 29.229, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 29.229; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:29.229

TS 29.230

Diameter applications; 3GPP specific codes and identifiers How it was counted: the catalogue row and every stored release of 29.230, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 29.230; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:29.230

TS 29.232

Media Gateway Controller (MGC) - Media Gateway (MGW) interface; Stage 3 How it was counted: the catalogue row and every stored release of 29.232, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 29.232; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:29.232

TS 29.235 cited

Interworking between SIP-I based circuit-switched core network and other networks How it was counted: the catalogue row and every stored release of 29.235, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 29.235; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:29.235

TS 29.238 cited

Interconnection Border Control Functions (IBCF) - Transition Gateway (TrGW) interface, Ix interface; Stage 3 How it was counted: the catalogue row and every stored release of 29.238, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 29.238; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:29.238

TS 29.244

Interface between the Control Plane and the User Plane nodes How it was counted: the catalogue row and every stored release of 29.244, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 29.244; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:29.244

TS 29.272

Evolved Packet System (EPS); Mobility Management Entity (MME) and Serving GPRS Support Node (SGSN) related interfaces based on Diameter protocol How it was counted: the catalogue row and every stored release of 29.272, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 29.272; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:29.272

TS 29.273

Evolved Packet System (EPS); 3GPP EPS AAA interfaces How it was counted: the catalogue row and every stored release of 29.273, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 29.273; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:29.273

TS 29.274

3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 How it was counted: the catalogue row and every stored release of 29.274, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 29.274; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:29.274

TS 29.275

Proxy Mobile IPv6 (PMIPv6) based Mobility and Tunnelling protocols; Stage 3 How it was counted: the catalogue row and every stored release of 29.275, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 29.275; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:29.275

TS 29.276

3GPP Evolved Packet System (EPS); Optimized handover procedures and protocols between E-UTRAN access and cdma2000 HRPD Access; Stage 3 How it was counted: the catalogue row and every stored release of 29.276, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 29.276; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:29.276

TS 29.280

Evolved Packet System (EPS); 3GPP Sv interface (MME to MSC, and SGSN to MSC) for SRVCC How it was counted: the catalogue row and every stored release of 29.280, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 29.280; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:29.280

TS 29.292 cited

Interworking between the IP Multimedia (IM) Core Network (CN) subsystem (IMS) and MSC Server for IMS Centralized Services (ICS) How it was counted: the catalogue row and every stored release of 29.292, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 29.292; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:29.292

TS 29.305

InterWorking Function (IWF) between MAP based and Diameter based interfaces How it was counted: the catalogue row and every stored release of 29.305, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 29.305; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:29.305

TS 29.328 cited

IP Multimedia (IM) Subsystem Sh interface; Signalling flows and message contents How it was counted: the catalogue row and every stored release of 29.328, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 29.328; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:29.328

TS 29.329 cited

Sh interface based on the Diameter protocol; Protocol details How it was counted: the catalogue row and every stored release of 29.329, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 29.329; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:29.329

TS 29.332

Media Gateway Control Function (MGCF) - IM Media Gateway; Mn interface How it was counted: the catalogue row and every stored release of 29.332, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 29.332; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:29.332

TS 29.333

Multimedia Resource Function Controller (MRFC) - Multimedia Resource Function Processor (MRFP) Mp interface; Stage 3 How it was counted: the catalogue row and every stored release of 29.333, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 29.333; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:29.333

TS 29.334

IMS Application Level Gateway (IMS-ALG) – IMS Access Gateway (IMS-AGW); Iq Interface; Stage 3 How it was counted: the catalogue row and every stored release of 29.334, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 29.334; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:29.334

TS 29.364

IP Multimedia Subsystem (IMS) Application Server (AS) service data descriptions for AS interoperability How it was counted: the catalogue row and every stored release of 29.364, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 29.364; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:29.364

TS 29.433

TISPAN; IP Multimedia; Diameter based protocol for the interfaces between the Call Session Control Function and the User Profile Server Function/Subscription Locator Function; Signalling flows and protocol details [3GPP TS 29.228 and 29.229 modified] How it was counted: the catalogue row and every stored release of 29.433, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 29.433; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:29.433

TS 29.500

5G System; Technical Realization of Service Based Architecture; Stage 3 How it was counted: the catalogue row and every stored release of 29.500, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 29.500; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:29.500

TS 29.503

5G System; Unified Data Management Services; Stage 3 How it was counted: the catalogue row and every stored release of 29.503, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 29.503; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:29.503

TS 29.504

5G System; Unified Data Repository Services; Stage 3 How it was counted: the catalogue row and every stored release of 29.504, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 29.504; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:29.504

TS 29.505

5G System; Usage of the Unified Data Repository services for Subscription Data; Stage 3 How it was counted: the catalogue row and every stored release of 29.505, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 29.505; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:29.505

TS 29.510 cited

5G System; Network function repository services; Stage 3 How it was counted: the catalogue row and every stored release of 29.510, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 29.510; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:29.510

TS 29.512

5G System; Session Management Policy Control Service; Stage 3 How it was counted: the catalogue row and every stored release of 29.512, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 29.512; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:29.512

TS 29.513 cited

5G System; Policy and Charging Control signalling flows and QoS parameter mapping; Stage 3 How it was counted: the catalogue row and every stored release of 29.513, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 29.513; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:29.513

TS 29.514 cited

5G System; Policy Authorization Service; Stage 3 How it was counted: the catalogue row and every stored release of 29.514, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 29.514; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:29.514

TS 29.562 cited

5G System; Home Subscriber Server (HSS) services; Stage 3 How it was counted: the catalogue row and every stored release of 29.562, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 29.562; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:29.562

TS 29.571 cited

5G System; Common Data Types for Service Based Interfaces; Stage 3 How it was counted: the catalogue row and every stored release of 29.571, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 29.571; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:29.571

TR 29.863

Feasibility Study for the multimedia inter-working between the IP Multimedia Core Network (CN) Subsystem (IMS) and Circuit Switched (CS) networks How it was counted: the catalogue row and every stored release of 29.863, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 29.863; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:29.863

TR 29.864

Study on IMS Application Server (AS) service data descriptions for AS interoperability How it was counted: the catalogue row and every stored release of 29.864, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 29.864; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:29.864

TR 29.866 cited

Study on IMS Disaster Prevention and Restoration Enhancement How it was counted: the catalogue row and every stored release of 29.866, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 29.866; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:29.866

TR 29.867 cited

Study on IMS resiliency How it was counted: the catalogue row and every stored release of 29.867, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 29.867; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:29.867

TR 29.949 cited

Study on technical aspects on roaming end-to-end scenarios with Voice over LTE (VoLTE) IP Multimedia Subsystem (IMS) and other networks How it was counted: the catalogue row and every stored release of 29.949, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 29.949; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:29.949

TR 29.998

Open Services Architecture (OSA) Application Programming Interface (API) part 2 How it was counted: the catalogue row and every stored release of 29.998, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 29.998; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:29.998

TS 31.102

Characteristics of the Universal Subscriber Identity Module (USIM) application How it was counted: the catalogue row and every stored release of 31.102, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 31.102; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:31.102

TS 31.103

Characteristics of the IP Multimedia Services Identity Module (ISIM) application How it was counted: the catalogue row and every stored release of 31.103, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 31.103; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:31.103

TS 31.111

Universal Subscriber Identity Module (USIM) Application Toolkit (USAT) How it was counted: the catalogue row and every stored release of 31.111, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 31.111; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:31.111

TS 31.121

UICC-terminal interface; Universal Subscriber Identity Module (USIM) application test specification How it was counted: the catalogue row and every stored release of 31.121, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 31.121; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:31.121

TS 31.124

Mobile Equipment (ME) conformance test specification; Universal Subscriber Identity Module Application Toolkit (USAT) conformance test specification How it was counted: the catalogue row and every stored release of 31.124, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 31.124; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:31.124

TS 31.130

(U)SIM Application Programming Interface (API); (U)SIM API for JavaTM Card How it was counted: the catalogue row and every stored release of 31.130, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 31.130; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:31.130

TR 31.828

UICC access to IMS How it was counted: the catalogue row and every stored release of 31.828, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 31.828; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:31.828

TS 32.240

Telecommunication management; Charging management; Charging architecture and principles How it was counted: the catalogue row and every stored release of 32.240, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 32.240; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:32.240

TS 32.260

Telecommunication management;Charging management;IP Multimedia Subsystem (IMS) charging How it was counted: the catalogue row and every stored release of 32.260, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 32.260; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:32.260

TS 32.280

Telecommunication management; Charging management; Advice of Charge (AoC) service How it was counted: the catalogue row and every stored release of 32.280, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 32.280; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:32.280

TS 32.296

Telecommunication management; Charging management; Online Charging System (OCS): Applications and interfaces How it was counted: the catalogue row and every stored release of 32.296, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 32.296; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:32.296

TS 32.298

Telecommunication management; Charging management; Charging Data Record (CDR) parameter description How it was counted: the catalogue row and every stored release of 32.298, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 32.298; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:32.298

TS 32.299

Telecommunication management; Charging management; Diameter charging applications How it was counted: the catalogue row and every stored release of 32.299, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 32.299; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:32.299

TS 32.409

Telecommunication management; Performance Management (PM); Performance measurements; IP Multimedia Subsystem (IMS) How it was counted: the catalogue row and every stored release of 32.409, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 32.409; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:32.409

TS 32.454

Telecommunication management; Key Performance Indicators (KPI) for the IP Multimedia Subsystem (IMS); Definitions How it was counted: the catalogue row and every stored release of 32.454, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 32.454; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:32.454

TR 32.849

Study on Charging aspects of Roaming End-to-end scenarios with VoLTE IMS and interconnecting networks How it was counted: the catalogue row and every stored release of 32.849, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 32.849; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:32.849

TS 33.106

3G security; Lawful interception requirements How it was counted: the catalogue row and every stored release of 33.106, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 33.106; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:33.106

TS 33.107

3G security; Lawful interception architecture and functions How it was counted: the catalogue row and every stored release of 33.107, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 33.107; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:33.107

TS 33.108

3G security; Handover interface for Lawful Interception (LI) How it was counted: the catalogue row and every stored release of 33.108, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 33.108; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:33.108

TS 33.141

Presence service; Security How it was counted: the catalogue row and every stored release of 33.141, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 33.141; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:33.141

TS 33.203

3G security; Access security for IP-based services How it was counted: the catalogue row and every stored release of 33.203, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 33.203; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:33.203

TS 33.226 cited

Security assurance for IP Multimedia Subsystem (IMS) How it was counted: the catalogue row and every stored release of 33.226, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 33.226; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:33.226

TS 33.246

3G Security; Security of Multimedia Broadcast/Multicast Service (MBMS) How it was counted: the catalogue row and every stored release of 33.246, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 33.246; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:33.246

TS 33.328

IP Multimedia Subsystem (IMS) media plane security How it was counted: the catalogue row and every stored release of 33.328, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 33.328; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:33.328

TS 33.401

3GPP System Architecture Evolution (SAE); Security architecture How it was counted: the catalogue row and every stored release of 33.401, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 33.401; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:33.401

TS 33.402

3GPP System Architecture Evolution (SAE); Security aspects of non-3GPP accesses How it was counted: the catalogue row and every stored release of 33.402, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 33.402; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:33.402

TR 33.768 cited

Study on security aspects of IMS resiliency How it was counted: the catalogue row and every stored release of 33.768, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 33.768; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:33.768

TR 33.803

Coexistence between TISPAN and 3GPP authentication schemes How it was counted: the catalogue row and every stored release of 33.803, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 33.803; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:33.803

TR 33.844

Security Study on IP Multimedia Subsystem (IMS) based peer-to-peer content distribution services; Stage 2 How it was counted: the catalogue row and every stored release of 33.844, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 33.844; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:33.844

TR 33.871

Study on security for Web Real Time Communications (WebRTC) IP Multimedia Subsystem (IMS) client access to IMS How it was counted: the catalogue row and every stored release of 33.871, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 33.871; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:33.871

TR 33.926 cited

Security Assurance Specification (SCAS) threats and critical assets in 3GPP network product classes How it was counted: the catalogue row and every stored release of 33.926, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 33.926; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:33.926

TR 33.978

Security aspects of early IP Multimedia Subsystem (IMS) How it was counted: the catalogue row and every stored release of 33.978, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 33.978; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:33.978

TS 34.108

Common test environments for User Equipment (UE); Conformance testing How it was counted: the catalogue row and every stored release of 34.108, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 34.108; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:34.108

TS 34.123-1

User Equipment (UE) conformance specification; Part 1: Protocol conformance specification How it was counted: the catalogue row and every stored release of 34.123-1, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 34.123-1; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:34.123-1

TS 34.123-2

User Equipment (UE) conformance specification; Part 2: Implementation conformance statement (ICS) proforma specification How it was counted: the catalogue row and every stored release of 34.123-2, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 34.123-2; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:34.123-2

TS 34.123-3

User Equipment (UE) conformance specification; Part 3: Abstract test suite (ATS) How it was counted: the catalogue row and every stored release of 34.123-3, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 34.123-3; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:34.123-3

TS 34.229-1 cited

Internet Protocol (IP) multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); User Equipment (UE) conformance specification; Part 1: Protocol conformance specification How it was counted: the catalogue row and every stored release of 34.229-1, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 34.229-1; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:34.229-1

TS 34.229-2

Internet Protocol (IP) multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); User Equipment (UE) conformance specification; Part 2: Implementation Conformance Statement (ICS) specification How it was counted: the catalogue row and every stored release of 34.229-2, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 34.229-2; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:34.229-2

TS 34.229-3

Internet Protocol (IP) multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); User Equipment (UE) conformance specification; Part 3: Abstract test suite (ATS) How it was counted: the catalogue row and every stored release of 34.229-3, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 34.229-3; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:34.229-3

TS 34.229-4

Internet Protocol (IP) multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); User Equipment (UE) conformance specification; Part 4: Enabler for IP multimedia applications testing How it was counted: the catalogue row and every stored release of 34.229-4, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 34.229-4; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:34.229-4

TS 34.229-5

Internet Protocol (IP) multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); User Equipment (UE) conformance specification; Part 5: Protocol conformance specification using 5G System (5GS) How it was counted: the catalogue row and every stored release of 34.229-5, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 34.229-5; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:34.229-5

TS 36.331

Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification How it was counted: the catalogue row and every stored release of 36.331, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 36.331; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:36.331

TS 36.413

Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) How it was counted: the catalogue row and every stored release of 36.413, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 36.413; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:36.413

TS 36.508

Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Packet Core (EPC); Common test environments for User Equipment (UE) conformance testing How it was counted: the catalogue row and every stored release of 36.508, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 36.508; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:36.508

TS 36.509

Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Packet Core (EPC); Special conformance testing functions for User Equipment (UE) How it was counted: the catalogue row and every stored release of 36.509, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 36.509; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:36.509

TS 36.523-1

Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Packet Core (EPC); User Equipment (UE) conformance specification; Part 1: Protocol conformance specification How it was counted: the catalogue row and every stored release of 36.523-1, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 36.523-1; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:36.523-1

TS 36.523-2

Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Packet Core (EPC); User Equipment (UE) conformance specification; Part 2: Implementation Conformance Statement (ICS) proforma specification How it was counted: the catalogue row and every stored release of 36.523-2, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 36.523-2; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:36.523-2

TS 36.523-3

Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Packet Core (EPC); User Equipment (UE) conformance specification; Part 3: Test suites How it was counted: the catalogue row and every stored release of 36.523-3, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 36.523-3; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:36.523-3

TS 38.508-1

5GS; User Equipment (UE) conformance specification; Part 1: Common test environment How it was counted: the catalogue row and every stored release of 38.508-1, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 38.508-1; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:38.508-1

TS 38.509

5GS; Special conformance testing functions for User Equipment (UE) How it was counted: the catalogue row and every stored release of 38.509, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05; the day each version file went up from /var/www/whatthespec.net/data/database/api/spec_version_dates.sqlite; the document counts are IMS rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose change-request column names 38.509; the rapporteur from /var/www/whatthespec.net/data/database/api/spec_rapporteurs.sqlite spec:38.509

Work item 177

5GS_Ph1-IMSo5G cited

IMS impact due to 5GS IP-CAN How it was counted: the 4 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly '5GS_Ph1-IMSo5G', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names 5GS_Ph1-IMSo5G as a whole word; the target documents come from section 5 of CP-180094.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:5GS_Ph1-IMSo5G

5GS_Ph1_IMSCH cited

Charging for IMS over 5G System Architecture Phase 1 How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly '5GS_Ph1_IMSCH', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names 5GS_Ph1_IMSCH as a whole word; the target documents come from section 5 of SP-180391 New WID on Charging for IMS over 5G System Architecture Phase 1.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:5GS_Ph1_IMSCH

AIML_IMS-MED cited

Media aspects for AI/ML in IMS services How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'AIML_IMS-MED', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names AIML_IMS-MED as a whole word; the target documents come from section 5 of SP-250878_SP-250634.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:AIML_IMS-MED

AT_IMS cited

AT Commands for IMS-configuration How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'AT_IMS', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names AT_IMS as a whole word; the target documents come from section 5 of CP-100376.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:AT_IMS

CC_IMS_USIM cited

Communication Control for IMS by USIM (Stage 3) How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'CC_IMS_USIM', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names CC_IMS_USIM as a whole word; the target documents come from section 5 of CP-100647.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:CC_IMS_USIM

CH7-IMS-ACP

Alternate Charged Party (ACP) for IMS How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'CH7-IMS-ACP', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names CH7-IMS-ACP as a whole word; the target documents come from section 5 of SP-060442 - revision marked.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:CH7-IMS-ACP

CH8_IMS cited

IMS Charging How it was counted: the 3 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'CH8_IMS', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names CH8_IMS as a whole word; the target documents come from section 5 of SP-070621.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:CH8_IMS

CW_IMS

Communication Wait on IMS How it was counted: the 4 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'CW_IMS', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names CW_IMS as a whole word; the target documents come from section 5 of CP-080214.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:CW_IMS

EHNB-IMS cited

IMS aspects of Architecture for Home NodeB How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'EHNB-IMS', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names EHNB-IMS as a whole word; the target documents come from section 5 of SP-080799_S2-088289.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:EHNB-IMS

FS_IMS-UICC

Study on UICC access to IMS How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'FS_IMS-UICC', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names FS_IMS-UICC as a whole word; the target documents come from section 5 of CP-100424.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:FS_IMS-UICC

FS_IMS-eCall

Study on Extended Support of IMS Emergency Calls How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'FS_IMS-eCall', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names FS_IMS-eCall as a whole word; the target documents come from section 5 of SP-070547_S2-073733 (Rel-8 WID for IMS Emergency Calls)-clean.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:FS_IMS-eCall

FS_IMSRE_SEC cited

Deleted - Study on Security Aspects for IMS resiliency How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'FS_IMSRE_SEC', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names FS_IMSRE_SEC as a whole word; the target documents come from section 5 of SP-251237_new_SID_Security Aspects for IMS resiliency.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:FS_IMSRE_SEC

FS_IMSResil cited

Study on IMS resiliency How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'FS_IMSResil', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names FS_IMSResil as a whole word; the target documents come from section 5 of CP-251280 was CP-251017.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:FS_IMSResil

FS_IMS_ASIO

Study on IMS Application Server Service Data Descriptions for AS interoperability How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'FS_IMS_ASIO', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names FS_IMS_ASIO as a whole word; the target documents come from section 5 of CP-070685.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:FS_IMS_ASIO

FS_IMS_CSC

Study on centralized IMS services control How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'FS_IMS_CSC', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names FS_IMS_CSC as a whole word; the target documents come from section 5 of SP-070494.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:FS_IMS_CSC

FS_IMS_LBO_ORM

Study on System enhancements for the use of IMS services in Local BreakOut and Optimal Routing of Media How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'FS_IMS_LBO_ORM', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names FS_IMS_LBO_ORM as a whole word; the target documents come from section 5 of SP-080556_S2-086385_Rev-FS-IMS_LBO.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:FS_IMS_LBO_ORM

FS_IMS_P2P cited

Study on IMS based Peer-to-Peer Content Distribution Services How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'FS_IMS_P2P', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names FS_IMS_P2P as a whole word; the target documents come from section 5 of SP-090491.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:FS_IMS_P2P

FS_IMS_P2P_CDS

Study on IMS based Peer-to-Peer Content Distribution Services (Stage 2) How it was counted: the 4 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'FS_IMS_P2P_CDS', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names FS_IMS_P2P_CDS as a whole word; the target documents come from section 5 of SP-120622 Update SID_Study on IMS Based Peer-to-Peer Content Distribution Services.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:FS_IMS_P2P_CDS

FS_IMS_RES cited

Study on IMS Disaster Prevention and Restoration Enhancement How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'FS_IMS_RES', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names FS_IMS_RES as a whole word; the target documents come from section 5 of CP-232281-CP-232026.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:FS_IMS_RES

FS_IMS_RP

Study on IMS Restoration Procedures How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'FS_IMS_RP', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names FS_IMS_RP as a whole word; the target documents come from section 5 of CP-070031.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:FS_IMS_RP

FS_IMSconf

Study on Requirements of IMS Multimedia Conferencing How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'FS_IMSconf', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names FS_IMSconf as a whole word; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:FS_IMSconf

FS_MLTICAST-IMS

Study on IMS utilizing multicast bearer services How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'FS_MLTICAST-IMS', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names FS_MLTICAST-IMS as a whole word; the target documents come from section 5 of SP-060148_S2-061214.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:FS_MLTICAST-IMS

FS_REVOLTE_IMS

Study on Technical aspects on Roaming End-to-end scenarios with VoLTE IMS and other networks How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'FS_REVOLTE_IMS', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names FS_REVOLTE_IMS as a whole word; the target documents come from section 5 of CP-130774.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:FS_REVOLTE_IMS

FS_REVOLTE_IMS_CH

Study on Charging aspects on Roaming End-to-end scenarios with VoLTE IMS and interconnecting networks How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'FS_REVOLTE_IMS_CH', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names FS_REVOLTE_IMS_CH as a whole word; the target documents come from section 5 of SP-130609 S5-132106 WID_FS_REVOLTE_CHG.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:FS_REVOLTE_IMS_CH

FS_eIMS cited

Study on IMS Evolution How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'FS_eIMS', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names FS_eIMS as a whole word; the target documents come from section 5 of SP-100360_S2-103084_eIMS_WID_update.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:FS_eIMS

FS_eIMS5G cited

Study on Enhanced IMS to 5GC Integration How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'FS_eIMS5G', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names FS_eIMS5G as a whole word; the target documents come from section 5 of SP-180736_S2-188366_revised SID 5GC IMS Enhancements.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:FS_eIMS5G

FS_eIMS5G2 cited

Study on enhanced IMS to 5GC Integration Phase 2 How it was counted: the 4 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'FS_eIMS5G2', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names FS_eIMS5G2 as a whole word; the target documents come from section 5 of CP-201358.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:FS_eIMS5G2

FS_eIMS_IBCF

Deleted - Study on enhancements to IMS border functions for IMS Interconnection of services How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'FS_eIMS_IBCF', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names FS_eIMS_IBCF as a whole word; the target documents come from section 5 of SP-090809_S2-097568_Updated_SID_Fs-eIMS-IBCF.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:FS_eIMS_IBCF

FS_enIMS cited

Study on enhancements to IMS for new real time communication services How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'FS_enIMS', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names FS_enIMS as a whole word; the target documents come from section 5 of SP-170703.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:FS_enIMS

FS_enIMS_ARC cited

Study on IMS Architecture Enhancement How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'FS_enIMS_ARC', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names FS_enIMS_ARC as a whole word; the target documents come from section 5 of SP-251692 was SP-251656 was of SP-251638 was SP-251411_S2-2511300_was_S2-2511257_New SID on IMS architecture enhancement r02.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:FS_enIMS_ARC

IMS cited

Provisioning of IP-based multimedia services How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'IMS', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names IMS as a whole word; the target documents come from section 5 of S1-000299.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:IMS

IMS-ASEC cited

Access Security for IMS How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'IMS-ASEC', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names IMS-ASEC as a whole word; the target documents come from section 5 of SP-010323_S3-010283_WI-aSIP.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:IMS-ASEC

IMS-CAMEL cited

CAMEL control of IMS services How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'IMS-CAMEL', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names IMS-CAMEL as a whole word; the target documents come from section 5 of NP-020305.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:IMS-CAMEL

IMS-CCR cited

Call control and roaming to support IMS in UMTS How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'IMS-CCR', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names IMS-CCR as a whole word; the target documents come from section 5 of SP-010339.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:IMS-CCR

IMS-CCR-IWCS cited

Interworking between IMS and CS networks How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'IMS-CCR-IWCS', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names IMS-CCR-IWCS as a whole word; the target documents come from section 5 of NP-030292.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:IMS-CCR-IWCS

IMS-CCR-IWIP cited

Interworking between IMS and IP networks How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'IMS-CCR-IWIP', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names IMS-CCR-IWIP as a whole word; the target documents come from section 5 of NP-020091.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:IMS-CCR-IWIP

IMS-CCR-IWMM cited

Impact on MM/CC/SM How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'IMS-CCR-IWMM', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names IMS-CCR-IWMM as a whole word; the target documents come from section 5 of NP-010434.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:IMS-CCR-IWMM

IMS-CCR-Mn

Mn interface (IM-MGW to MGCF) enhancements (CN4 Part) How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'IMS-CCR-Mn', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names IMS-CCR-Mn as a whole word; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:IMS-CCR-Mn

IMS-CCR_Test cited

Conformance Test Aspects – IMS Call Control How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'IMS-CCR_Test', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names IMS-CCR_Test as a whole word; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:IMS-CCR_Test

IMS-CCR_Test2

Split TTCN Test Models for IMS testing in TS 34.229-3 How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'IMS-CCR_Test2', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names IMS-CCR_Test2 as a whole word; the target documents come from section 5 of RP-140440.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:IMS-CCR_Test2

IMS-CODEC cited

Multimedia codecs and protocols for conversational PS services How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'IMS-CODEC', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names IMS-CODEC as a whole word; the target documents come from section 5 of SP-000398.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:IMS-CODEC

IMS-Cont cited

IMS Service Continuity How it was counted: the 4 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'IMS-Cont', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names IMS-Cont as a whole word; the target documents come from section 5 of SP-080092_S2-080987_IMS_SC_WID.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:IMS-Cont

IMS-EMER

Deleted - PS domain and IMS support for IMS Emergency sessions How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'IMS-EMER', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names IMS-EMER as a whole word; the target documents come from section 5 of SP-050604_S2-052409_over_SP-040746.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:IMS-EMER

IMS-FrWk cited

IMS Framework Report (work stopped) How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'IMS-FrWk', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names IMS-FrWk as a whole word; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:IMS-FrWk

IMS-LI cited

IMS Lawful Interception How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'IMS-LI', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names IMS-LI as a whole word; the target documents come from section 5 of SP-010621_S3-010611_S3LI01_145_WI_3G_interceptR3-01-10.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:IMS-LI

IMS-MMTel cited

IMS Multimedia Telephony Service How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'IMS-MMTel', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names IMS-MMTel as a whole word; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:IMS-MMTel

IMS-OAM cited

Charging and OAM&P for IMS How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'IMS-OAM', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names IMS-OAM as a whole word; the target documents come from section 5 of _S5-010527_WID_Feature_OAM&P.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:IMS-OAM

IMS-ONOSA cited

Support of VHE/OSA by entities and protocols of the IMS (e.g. CSCF) How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'IMS-ONOSA', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names IMS-ONOSA as a whole word; the target documents come from section 5 of NP-010692.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:IMS-ONOSA

IMS-RT

Deleted - Study on IMS enhancements and optimizations for real time communication. How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'IMS-RT', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names IMS-RT as a whole word; the target documents come from section 5 of SP-050492_S2-052410.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:IMS-RT

IMS-SE

Deleted - IMS security extensions (covered by UID33027) How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'IMS-SE', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names IMS-SE as a whole word; the target documents come from section 5 of SP-050395.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:IMS-SE

IMS-Sec cited

Security Enhancements for IMS How it was counted: the 4 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'IMS-Sec', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names IMS-Sec as a whole word; the target documents come from section 5 of SP-070496_revision of_343.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:IMS-Sec

IMS-Sex cited

Service Examples (Work stopped) How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'IMS-Sex', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names IMS-Sex as a whole word; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:IMS-Sex

IMS-TEST cited

Conformance Test Aspects - Provisioning of IMS How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'IMS-TEST', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names IMS-TEST as a whole word; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:IMS-TEST

IMS-UICC-S cited

UICC access to IMS Specification How it was counted: the 3 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'IMS-UICC-S', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names IMS-UICC-S as a whole word; the target documents come from section 5 of CP-110279-cl.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:IMS-UICC-S

IMS2 cited

IMS Phase 2 How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'IMS2', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names IMS2 as a whole word; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:IMS2

IMS2-CCR

Enhancements to the Cx and Sh interfaces How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'IMS2-CCR', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names IMS2-CCR as a whole word; the target documents come from section 5 of NP-030229.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:IMS2-CCR

IMS2-CH

IMS charging How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'IMS2-CH', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names IMS2-CH as a whole word; the target documents come from section 5 of SP-030049 S5-034164 BB IMS WID.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:IMS2-CH

IMS2_CCR_Test

Conformance Test Aspects – IMS Call Control Rel-6 enhancements How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'IMS2_CCR_Test', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names IMS2_CCR_Test as a whole word; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:IMS2_CCR_Test

IMS8

Deleted - IMS Enhancements Rel-8 How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'IMS8', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names IMS8 as a whole word; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:IMS8

IMSCOOP

Interoperability and Commonality between IMS using different IP-connectivity Networks How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'IMSCOOP', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names IMSCOOP as a whole word; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:IMSCOOP

IMSDCDataOff cited

PS Data Off for IMS Data Channel Service How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'IMSDCDataOff', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names IMSDCDataOff as a whole word; the target documents come from section 5 of SP-230227.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:IMSDCDataOff

IMSGM cited

IMS Group Management How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'IMSGM', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names IMSGM as a whole word; the target documents come from section 5 of S1-020576.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:IMSGM

IMSLocal

Deleted - IMS Local services How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'IMSLocal', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names IMSLocal as a whole word; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:IMSLocal

IMSM cited

IMS Messaging How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'IMSM', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names IMSM as a whole word; the target documents come from section 5 of S1-020575.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:IMSM

IMSM-CR

CRs to 22.140 & 22.228 How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'IMSM-CR', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names IMSM-CR as a whole word; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:IMSM-CR

IMSM-TR

TR on support of messaging in the IMS How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'IMSM-TR', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names IMSM-TR as a whole word; the target documents come from section 5 of S1-020575.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:IMSM-TR

IMSM-TS

Stage 1 22.340 How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'IMSM-TS', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names IMSM-TS as a whole word; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:IMSM-TS

IMSProtoc cited

IMS Stage 3 IETF Protocol Alignment How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'IMSProtoc', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names IMSProtoc as a whole word; the target documents come from section 5 of CP-060101_clean.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:IMSProtoc

IMSProtoc16 cited

IMS Stage-3 IETF Protocol Alignment How it was counted: the 3 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'IMSProtoc16', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names IMSProtoc16 as a whole word; the target documents come from section 5 of CP-183084.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:IMSProtoc16

IMSProtoc17 cited

IMS Stage-3 IETF Protocol Alignment How it was counted: the 3 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'IMSProtoc17', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names IMSProtoc17 as a whole word; the target documents come from section 5 of CP-201167.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:IMSProtoc17

IMSProtoc17_dataCH-UEContest cited

STOPPED - UE Conformance - IMS Data Channel How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'IMSProtoc17_dataCH-UEContest', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names IMSProtoc17_dataCH-UEContest as a whole word; the target documents come from section 5 of RP-240283 Revised WID on UE Conformance - Rel-17 IMS Data Channel_cl.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:IMSProtoc17_dataCH-UEContest

IMSProtoc18 cited

IMS Stage-3 IETF Protocol Alignment How it was counted: the 3 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'IMSProtoc18', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names IMSProtoc18 as a whole word; the target documents come from section 5 of CP-223102-cl.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:IMSProtoc18

IMSProtoc19 cited

IMS Stage-3 IETF Protocol Alignment How it was counted: the 3 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'IMSProtoc19', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names IMSProtoc19 as a whole word; the target documents come from section 5 of CP-251219_cl.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:IMSProtoc19

IMSProtoc2 cited

IMS Stage 3 IETF Protocol Alignment - phase 2 How it was counted: the 5 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'IMSProtoc2', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names IMSProtoc2 as a whole word; the target documents come from section 5 of CP-080794.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:IMSProtoc2

IMSProtoc20-CT cited

IMS Stage-3 IETF Protocol Alignment How it was counted: the 3 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'IMSProtoc20-CT', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names IMSProtoc20-CT as a whole word; the target documents come from section 5 of CP-260044.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:IMSProtoc20-CT

IMSProtoc3 cited

IMS Stage 3 IETF Protocol Alignment - phase 3 How it was counted: the 4 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'IMSProtoc3', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names IMSProtoc3 as a whole word; the target documents come from section 5 of CP-090491.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:IMSProtoc3

IMSProtoc4 cited

IMS Stage 3 IETF Protocol Alignment - phase 4 How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'IMSProtoc4', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names IMSProtoc4 as a whole word; the target documents come from section 5 of CP-100099-imsprotoc4-wid.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:IMSProtoc4

IMSProtoc5 cited

IMS Stage 3 IETF Protocol Alignment - phase 5 How it was counted: the 7 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'IMSProtoc5', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names IMSProtoc5 as a whole word; the target documents come from section 5 of CP-110437.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:IMSProtoc5

IMSProtoc6 cited

IMS Stage 3 IETF Protocol Alignment - phase 6 How it was counted: the 7 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'IMSProtoc6', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names IMSProtoc6 as a whole word; the target documents come from section 5 of CP-120905_cl.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:IMSProtoc6

IMSProtoc7 cited

IMS Stage-3 IETF Protocol Alignment How it was counted: the 4 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'IMSProtoc7', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names IMSProtoc7 as a whole word; the target documents come from section 5 of CP-140815.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:IMSProtoc7

IMSProtoc8 cited

IMS Stage-3 IETF Protocol Alignment How it was counted: the 6 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'IMSProtoc8', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names IMSProtoc8 as a whole word; the target documents come from section 5 of CP-160294.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:IMSProtoc8

IMSProtoc9 cited

IMS Stage-3 IETF Protocol Alignment How it was counted: the 6 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'IMSProtoc9', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names IMSProtoc9 as a whole word; the target documents come from section 5 of CP-171098.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:IMSProtoc9

IMSSS-Gal

General aspects of IMS Sup Services How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'IMSSS-Gal', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names IMSSS-Gal as a whole word; the target documents come from section 5 of SP-070691_WID_TISCAP_R8.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:IMSSS-Gal

IMSSat cited

IMS access via Digital Video Broadcast - Return Channel via Satellite (DVB-RCS2) How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'IMSSat', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names IMSSat as a whole word; the target documents come from section 5 of SP-120543.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:IMSSat

IMSSat-SA1

Stage 1 for IMS access via DVB-RCS2 How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'IMSSat-SA1', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names IMSSat-SA1 as a whole word; the target documents come from section 5 of SP-120543.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:IMSSat-SA1

IMSTSS

IMS Multimedia Telephony and Supplementary Services How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'IMSTSS', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names IMSTSS as a whole word; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:IMSTSS

IMSTSS-RTTI-CH

Support of Real-time Transfer of Tariff Information (RTTI) in IMS charging How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'IMSTSS-RTTI-CH', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names IMSTSS-RTTI-CH as a whole word; the target documents come from section 5 of SP-090306 S5-092655 rev SP-090055 S5-091560 WID RTTI charging.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:IMSTSS-RTTI-CH

IMS_AGCF

IMS Application Level Gateway Control Function (ALGCF) – IMS Access Media Gateway (IMA-MGW); Iq Interface; Stage 2 and Stage 3 How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'IMS_AGCF', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names IMS_AGCF as a whole word; the target documents come from section 5 of CP-090020.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:IMS_AGCF

IMS_ASIO

IMS Application Server Service Data Descriptions for AS interoperability How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'IMS_ASIO', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names IMS_ASIO as a whole word; the target documents come from section 5 of CP-080451.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:IMS_ASIO

IMS_CONV_IP_COM-UEConTest cited

UE Conformance Test Aspects – IMS for Converged IP Communications How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'IMS_CONV_IP_COM-UEConTest', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names IMS_CONV_IP_COM-UEConTest as a whole word; the target documents come from section 5 of RP-171635 (Revised WID on ConvIPComm WID).md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:IMS_CONV_IP_COM-UEConTest

IMS_Comm_Doc cited

Documentation of TISPAN NGN R1 and R2 in 3GPP SA2 How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'IMS_Comm_Doc', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names IMS_Comm_Doc as a whole word; the target documents come from section 5 of SP-070823_New_Documentation of TISPAN NGN R1 and R2_S2-075696.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:IMS_Comm_Doc

IMS_Comm_GqRx_Harm

Deleted - Harmonization of Gq'/Rx for Common IMS How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'IMS_Comm_GqRx_Harm', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names IMS_Comm_GqRx_Harm as a whole word; the target documents come from section 5 of SP-070822_New_Harmonization of Gq'_Rx for Common IMS_S2-075692.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:IMS_Comm_GqRx_Harm

IMS_Comm_Mtce7 cited

SA1,SA2 part of Maintenance of TISPAN release 1 common IMS How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'IMS_Comm_Mtce7', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names IMS_Comm_Mtce7 as a whole word; the target documents come from section 5 of SP-080501.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:IMS_Comm_Mtce7

IMS_Comm_Mtce8 cited

Maintenance of TISPAN release 2 common IMS How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'IMS_Comm_Mtce8', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names IMS_Comm_Mtce8 as a whole word; the target documents come from section 5 of SP-070916_TISPAN_Rel2_Maintenance.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:IMS_Comm_Mtce8

IMS_ConfMO

3GPP IMS Conferencing Management Object (MO) How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'IMS_ConfMO', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names IMS_ConfMO as a whole word; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:IMS_ConfMO

IMS_Corp cited

IMS System enhancements for corporate network access How it was counted: the 6 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'IMS_Corp', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names IMS_Corp as a whole word; the target documents come from section 5 of SP-080095_S2-081986_IMS_Corp_WID_Update.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:IMS_Corp

IMS_Corp2 cited

Transfer of ETSI business trunking specifications How it was counted: the 3 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'IMS_Corp2', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names IMS_Corp2 as a whole word; the target documents come from section 5 of SP-140170.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:IMS_Corp2

IMS_EMER_GPRS_EPS cited

Support for IMS Emergency Calls over GPRS and EPS How it was counted: the 4 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'IMS_EMER_GPRS_EPS', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names IMS_EMER_GPRS_EPS as a whole word; the target documents come from section 5 of SP-080844.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:IMS_EMER_GPRS_EPS

IMS_EMER_GPRS_EPS-SRVCC cited

Single Radio Voice Call Continuity (SRVCC) support for IMS Emergency Calls How it was counted: the 7 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'IMS_EMER_GPRS_EPS-SRVCC', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names IMS_EMER_GPRS_EPS-SRVCC as a whole word; the target documents come from section 5 of SP-090099_S2-091753_SRVCC-IMS_Emer_revised.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:IMS_EMER_GPRS_EPS-SRVCC

IMS_EMER_GPRS_EPS-Sec cited

Security aspects for IMS Emergency Calls over GPRS and EPS How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'IMS_EMER_GPRS_EPS-Sec', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names IMS_EMER_GPRS_EPS-Sec as a whole word; the target documents come from section 5 of SP-080844.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:IMS_EMER_GPRS_EPS-Sec

IMS_EMER_GPRS_EPSC1 cited

CT1 aspects - Stage 3 for IMS Emergency Calls over GPRS and EPS How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'IMS_EMER_GPRS_EPSC1', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names IMS_EMER_GPRS_EPSC1 as a whole word; the target documents come from section 5 of CP-090564.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:IMS_EMER_GPRS_EPSC1

IMS_EMER_GPRS_EPSC3

CT3 aspects - Stage 3 for IMS Emergency Calls over GPRS and EPS How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'IMS_EMER_GPRS_EPSC3', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names IMS_EMER_GPRS_EPSC3 as a whole word; the target documents come from section 5 of CP-090564.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:IMS_EMER_GPRS_EPSC3

IMS_EMER_GPRS_EPSC4

CT4 aspects - Stage 3 for IMS Emergency Calls over GPRS and EPS How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'IMS_EMER_GPRS_EPSC4', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names IMS_EMER_GPRS_EPSC4 as a whole word; the target documents come from section 5 of CP-090564.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:IMS_EMER_GPRS_EPSC4

IMS_EMER_GPRS_EPS_UEConTest

Conformance Test Aspects - CT1 aspects for IMS Emergency Calls over GPRS and EPS How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'IMS_EMER_GPRS_EPS_UEConTest', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names IMS_EMER_GPRS_EPS_UEConTest as a whole word; the target documents come from section 5 of RP-100567 WID_Conformance Test CT1 aspects IMS Emergency Calls.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:IMS_EMER_GPRS_EPS_UEConTest

IMS_EMER_LTE

Support for IMS Emergency Calls over LTE How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'IMS_EMER_LTE', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names IMS_EMER_LTE as a whole word; the target documents come from section 5 of RP-081140.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:IMS_EMER_LTE

IMS_EMER_LTE_UEConTest

Conformance Test Aspects – Support for IMS Emergency Calls over LTE How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'IMS_EMER_LTE_UEConTest', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names IMS_EMER_LTE_UEConTest as a whole word; the target documents come from section 5 of RP-100118 (New RAN5 WI proposal for IMS emergency call over LTE).md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:IMS_EMER_LTE_UEConTest

IMS_IBCF cited

IMS – Interconnection Border Control Function (IBCF) – Transition Gateway (TrGW); Ix Interface; Stage 3 How it was counted: the 3 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'IMS_IBCF', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names IMS_IBCF as a whole word; the target documents come from section 5 of CP-090019.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:IMS_IBCF

IMS_NNI

System enhancements for interconnection interfaces between two IMSs How it was counted: the 2 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'IMS_NNI', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names IMS_NNI as a whole word; the target documents come from section 5 of SP-080554_S2-086007_Rev-IMS-NNI.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:IMS_NNI

IMS_PSS_MBMS_US

IMS initiated and controlled PSS and MBMS User Service How it was counted: the 3 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'IMS_PSS_MBMS_US', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names IMS_PSS_MBMS_US as a whole word; the target documents come from section 5 of SP-080201.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:IMS_PSS_MBMS_US

IMS_PSS_MBMS_US_EXT

IMS based PSS and MBMS User Service extensions How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'IMS_PSS_MBMS_US_EXT', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names IMS_PSS_MBMS_US_EXT as a whole word; the target documents come from section 5 of SP-090225.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:IMS_PSS_MBMS_US_EXT

IMS_RES-CT cited

IMS Disaster Prevention and Restoration Enhancement How it was counted: the 4 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'IMS_RES-CT', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names IMS_RES-CT as a whole word; the target documents come from section 5 of CP-253168.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:IMS_RES-CT

IMS_RP

IMS Restoration Procedures How it was counted: the 3 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'IMS_RP', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names IMS_RP as a whole word; the target documents come from section 5 of CP-080447.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:IMS_RP

IMS_RegCon cited

Deleted - IMS Registration Control How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'IMS_RegCon', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names IMS_RegCon as a whole word; the target documents come from section 5 of SP-120735_S2-124080_Updated_WID for IMS registration control_SP-120544_(clean).md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:IMS_RegCon

IMS_RegCon-CT cited

Deleted - CT aspects of IMS registration control How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'IMS_RegCon-CT', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names IMS_RegCon-CT as a whole word; the target documents come from section 5 of CP-130217.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:IMS_RegCon-CT

IMS_RegCon-CT1

Deleted - CT1 aspects of CT aspects of IMS registration control (Stage 2/3) How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'IMS_RegCon-CT1', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names IMS_RegCon-CT1 as a whole word; the target documents come from section 5 of CP-130217.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:IMS_RegCon-CT1

IMS_RegCon-CT4

Deleted - CT4 aspects of CT aspects of IMS registration control (Stage 3) How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'IMS_RegCon-CT4', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names IMS_RegCon-CT4 as a whole word; the target documents come from section 5 of CP-130217.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:IMS_RegCon-CT4

IMS_RegCon-del1 cited

Deleted - Stage 1 for IMS Registration Control How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'IMS_RegCon-del1', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names IMS_RegCon-del1 as a whole word; the target documents come from section 5 of SP-120735_S2-124080_Updated_WID for IMS registration control_SP-120544_(clean).md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:IMS_RegCon-del1

IMS_RegCon-del2

Deleted - Stage 2 for IMS Registration Control How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'IMS_RegCon-del2', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names IMS_RegCon-del2 as a whole word; the target documents come from section 5 of SP-120735_S2-124080_Updated_WID for IMS registration control_SP-120544_(clean).md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:IMS_RegCon-del2

IMS_SCC cited

IMS Services Centralization and Continuity How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'IMS_SCC', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names IMS_SCC as a whole word; the target documents come from section 5 of SP-080633 SP-080557rev_New-IMSSSC-Nortel.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:IMS_SCC

IMS_SCC-ICS

Stage 2/3 for IMS Centralized Services How it was counted: the 3 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'IMS_SCC-ICS', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names IMS_SCC-ICS as a whole word; the target documents come from section 5 of SP-080634 SP-080563rev_New-IMSSCC-ICS-Nortel.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:IMS_SCC-ICS

IMS_SCC-ICS_I1

Stage 3 - IMS Centralized Services support via I1 interface How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'IMS_SCC-ICS_I1', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names IMS_SCC-ICS_I1 as a whole word; the target documents come from section 5 of CP-090640.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:IMS_SCC-ICS_I1

IMS_SCC-IDT

Stage 1 - Inter-Device Transfer – Requirements How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'IMS_SCC-IDT', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names IMS_SCC-IDT as a whole word; the target documents come from section 5 of SP-080507.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:IMS_SCC-IDT

IMS_SCC-SPI

Stage 2/3 for IMS Service Continuity Enhancements: Service, Policy and Interactions How it was counted: the 3 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'IMS_SCC-SPI', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names IMS_SCC-SPI as a whole word; the target documents come from section 5 of SP-080561_S2-086381_New-IMSSCC-SPI.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:IMS_SCC-SPI

IMS_SC_eIDT cited

IMS Service Continuity – Inter Device Transfer enhancements How it was counted: the 5 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'IMS_SC_eIDT', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names IMS_SC_eIDT as a whole word; the target documents come from section 5 of SP-090452.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:IMS_SC_eIDT

IMS_SDE cited

IMS-based Streaming and Download Delivery Enhancements How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'IMS_SDE', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names IMS_SDE as a whole word; the target documents come from section 5 of SP-120767_S4-121535.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:IMS_SDE

IMS_SDE-SA4

Specification on IMS-based Streaming and Download Delivery Enhancements How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'IMS_SDE-SA4', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names IMS_SDE-SA4 as a whole word; the target documents come from section 5 of SP-120767_S4-121535.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:IMS_SDE-SA4

IMS_SDE-SA4TR

TR on IMS-based Streaming and Download Delivery Enhancements How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'IMS_SDE-SA4TR', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names IMS_SDE-SA4TR as a whole word; the target documents come from section 5 of SP-120767_S4-121535.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:IMS_SDE-SA4TR

IMS_SSFDD cited

IM-SSF Application Server Service Data Descriptions (Stage 2/3) How it was counted: the 3 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'IMS_SSFDD', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names IMS_SSFDD as a whole word; the target documents come from section 5 of CP-120756.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:IMS_SSFDD

IMS_TELEP cited

IMS-based Telepresence How it was counted: the 12 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'IMS_TELEP', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names IMS_TELEP as a whole word; the target documents come from section 5 of SP-110588.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:IMS_TELEP

IMS_TELEP_EXT cited

Media Handling Extensions of IMS-based Telepresence How it was counted: the 12 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'IMS_TELEP_EXT', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names IMS_TELEP_EXT as a whole word; the target documents come from section 5 of SP-160081_S4-160201 WID IMS_TELEP_ext.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:IMS_TELEP_EXT

IMS_TELEP_S4 cited

Media Handling Aspects of IMS-based Telepresence How it was counted: the 7 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'IMS_TELEP_S4', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names IMS_TELEP_S4 as a whole word; the target documents come from section 5 of SP-140483_S4-140989 Rel-13_WID IMS_TELEP.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:IMS_TELEP_S4

IMS_UApAs cited

IMS impacts on UICC Application Aspects (Stage 3) How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'IMS_UApAs', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names IMS_UApAs as a whole word; the target documents come from section 5 of CP-130169-cl.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:IMS_UApAs

IMS_WebRTC cited

Web Real Time Communication access to IMS How it was counted: the 8 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'IMS_WebRTC', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names IMS_WebRTC as a whole word; the target documents come from section 5 of SP-130707_clean.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:IMS_WebRTC

IMS_WebRTC-CT cited

CT aspects of Web Real Time Communication (WebRTC) Access to IMS How it was counted: the 3 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'IMS_WebRTC-CT', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names IMS_WebRTC-CT as a whole word; the target documents come from section 5 of CP-140192.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:IMS_WebRTC-CT

IMS_WebRTC-CT1 cited

CT1 part of CT aspects of Web Real Time Communication (WebRTC) Access to IMS How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'IMS_WebRTC-CT1', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names IMS_WebRTC-CT1 as a whole word; the target documents come from section 5 of CP-140192.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:IMS_WebRTC-CT1

IMS_WebRTC-CT4 cited

CT4 part of CT aspects of Web Real Time Communication (WebRTC) Access to IMS How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'IMS_WebRTC-CT4', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names IMS_WebRTC-CT4 as a whole word; the target documents come from section 5 of CP-140192.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:IMS_WebRTC-CT4

IMS_WebRTC-data

(IETF) Web Real Time Communication access to IMS (draft-ietf-rtcweb-data-channel) How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'IMS_WebRTC-data', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names IMS_WebRTC-data as a whole word; the target documents come from section 5 of CP-140192.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:IMS_WebRTC-data

IMS_WebRTC-holmb

Deleted - (IETF) Web Real Time Communication access to IMS (draft-holmberg-sipcore-auth-id) How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'IMS_WebRTC-holmb', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names IMS_WebRTC-holmb as a whole word; the target documents come from section 5 of CP-140192.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:IMS_WebRTC-holmb

IMS_WebRTC-stun

(IETF) Web Real Time Communication access to IMS (draft-ietf-rtcweb-stun-consent-freshness) How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'IMS_WebRTC-stun', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names IMS_WebRTC-stun as a whole word; the target documents come from section 5 of CP-140192.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:IMS_WebRTC-stun

IMS_WebRTC-yusef

Deleted - (IETF) Web Real Time Communication access to IMS (draft-ietf-sipcore-sip-authn) How it was counted: the 2 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'IMS_WebRTC-yusef', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names IMS_WebRTC-yusef as a whole word; the target documents come from section 5 of CP-140192.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:IMS_WebRTC-yusef

IMSconf cited

IMS Support of Conferencing How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'IMSconf', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names IMSconf as a whole word; the target documents come from section 5 of CP-070120.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:IMSconf

IOI_IMS_CH

Transit Inter Operator Identifier for IMS Interconnection Charging in multi operator environment How it was counted: the 4 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'IOI_IMS_CH', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names IOI_IMS_CH as a whole word; the target documents come from section 5 of SP-110132 S5-110422_New_WID_IOI_IMS_CH.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:IOI_IMS_CH

IPv4IMS

Study on Interworking aspects and migration scenarios for IPv4 based IMS Implementations How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'IPv4IMS', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names IPv4IMS as a whole word; the target documents come from section 5 of SP-040327.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:IPv4IMS

IRTSD-CS_IMS

Study on Combining CS calls and IMS sessions How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'IRTSD-CS_IMS', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names IRTSD-CS_IMS as a whole word; the target documents come from section 5 of SP-040467.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:IRTSD-CS_IMS

IRTSD-IMSCS

Deleted - Study on Stage 2 (IMS services using CS bearers) How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'IRTSD-IMSCS', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names IRTSD-IMSCS as a whole word; the target documents come from section 5 of SP-040479.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:IRTSD-IMSCS

MIW-IMS cited

Multimedia interworking between IMS and CS networks How it was counted: the 2 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'MIW-IMS', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names MIW-IMS as a whole word; the target documents come from section 5 of CP-070729__C3-071150.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:MIW-IMS

MIW-IMS-St3C3

Stage 3 of MW-IMS How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'MIW-IMS-St3C3', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names MIW-IMS-St3C3 as a whole word; the target documents come from section 5 of CP-070096.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:MIW-IMS-St3C3

MIW-IMS-St3C3_MONA

Stage 3 for MW-IMS, MONA extension How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'MIW-IMS-St3C3_MONA', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names MIW-IMS-St3C3_MONA as a whole word; the target documents come from section 5 of CP-070729__C3-071150.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:MIW-IMS-St3C3_MONA

MIW-IMS-St3C4

Mn interface (MGCF – IM MGW) How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'MIW-IMS-St3C4', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names MIW-IMS-St3C4 as a whole word; the target documents come from section 5 of CP-070729__C3-071150.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:MIW-IMS-St3C4

NG_RTC_IMS_dataCH-UEConTest

UE Conformance - IMS Data Channel for NG RTC (Real Time Communication) How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'NG_RTC_IMS_dataCH-UEConTest', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names NG_RTC_IMS_dataCH-UEConTest as a whole word; the target documents come from section 5 of RP-253432-revised WID for UE Conformance - IMS Data Channel test-cl.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:NG_RTC_IMS_dataCH-UEConTest

NOVES-IMSESOM

Stage 2 for Non Voice Emergency Services (Support of IMS Emergency Sessions with Other Media on UTRAN and E-UTRAN) How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'NOVES-IMSESOM', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names NOVES-IMSESOM as a whole word; the target documents come from section 5 of SP-110644_Update NOVES-IMSESOM BB.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:NOVES-IMSESOM

NWK-PL2IMS cited

Network-provided Location information for IMS (NETLOC) How it was counted: the 4 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'NWK-PL2IMS', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names NWK-PL2IMS as a whole word; the target documents come from section 5 of SP-110631_S2-113723_NWK-PL2IMS-clean.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:NWK-PL2IMS

NWK-PL2IMS-CT cited

CT aspects of Network-provided Location information for IMS (Stage 3) How it was counted: the 4 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'NWK-PL2IMS-CT', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names NWK-PL2IMS-CT as a whole word; the target documents come from section 5 of CP-120845.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:NWK-PL2IMS-CT

NWK-PL2IMS_CH

Charging for Network-provided Location information for IMS How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'NWK-PL2IMS_CH', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names NWK-PL2IMS_CH as a whole word; the target documents come from section 5 of SP-110700 S5-113819 SP-110125 S5-110356_CH for NWK-PL2IMS_cl.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:NWK-PL2IMS_CH

OAM-PM-KPI_IMS

Key Performance Indicators (KPIs) for IMS How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'OAM-PM-KPI_IMS', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names OAM-PM-KPI_IMS as a whole word; the target documents come from section 5 of SP-100083 S5-100340 WID Key Performance Indicators for IMS.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:OAM-PM-KPI_IMS

OAM-ePM-IMS

IMS Performance Management enhancements How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'OAM-ePM-IMS', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names OAM-ePM-IMS as a whole word; the target documents come from section 5 of SP-110134 S5-110518.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:OAM-ePM-IMS

OPT_IMS_PSS_MBMS_US

Optimization of IMS based PSS and MBMS User Service How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'OPT_IMS_PSS_MBMS_US', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names OPT_IMS_PSS_MBMS_US as a whole word; the target documents come from section 5 of SP-100031.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:OPT_IMS_PSS_MBMS_US

OSA8-IMS

Rel-8 OSA Stage 2/3 enhancements How it was counted: the 9 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'OSA8-IMS', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names OSA8-IMS as a whole word; the target documents come from section 5 of CP-080429_rev_CP-080252_rev_CP-070349 OSA_WID_clean.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:OSA8-IMS

OSA8-IMSReq

OSA Stage 1 - NGN Service Requirement How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'OSA8-IMSReq', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names OSA8-IMSReq as a whole word; the target documents come from section 5 of SP-070692.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:OSA8-IMSReq

RANimp-IMSRealTime

Improved support of IMS Realtime Services using HSDPA/HSUPA How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'RANimp-IMSRealTime', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names RANimp-IMSRealTime as a whole word; the target documents come from section 5 of RP-050160.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:RANimp-IMSRealTime

RANimp-RABSE-IuEnhIMS

Deleted - Iu enhancements for IMS support in RAN How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'RANimp-RABSE-IuEnhIMS', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names RANimp-RABSE-IuEnhIMS as a whole word; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:RANimp-RABSE-IuEnhIMS

RInImp-IMSRealTime

Improved support of IMS Realtime Services using HSDPA/EDCH How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'RInImp-IMSRealTime', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names RInImp-IMSRealTime as a whole word; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:RInImp-IMSRealTime

SAES-IMS_LBO

System enhancements for the use of IMS services in local breakout How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'SAES-IMS_LBO', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names SAES-IMS_LBO as a whole word; the target documents come from section 5 of SP-080090_S2-080985_LBO_WID.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:SAES-IMS_LBO

SAES-ISIM_IMS_Test

Test interworking of IP Multimedia Services Identity Module (ISIM) terminals with IP Multimedia Subsystem (IMS) How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'SAES-ISIM_IMS_Test', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names SAES-ISIM_IMS_Test as a whole word; the target documents come from section 5 of CP-100602.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:SAES-ISIM_IMS_Test

SAES-SA_IMS

SAE impacts on IMS How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'SAES-SA_IMS', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names SAES-SA_IMS as a whole word; the target documents come from section 5 of SP-080132.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:SAES-SA_IMS

SCAS_IMS cited

Assurance Specification for IMS How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'SCAS_IMS', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names SCAS_IMS as a whole word; the target documents come from section 5 of SP-191128 WID_SCAS_IMS.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:SCAS_IMS

SDPCN_IMS cited

Controlling IMS Media Plane with SDP Capability How it was counted: the 3 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'SDPCN_IMS', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names SDPCN_IMS as a whole word; the target documents come from section 5 of CP-150238.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:SDPCN_IMS

SEC-IMS

Study on Security for early IMS How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'SEC-IMS', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names SEC-IMS as a whole word; the target documents come from section 5 of SP-040691.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:SEC-IMS

SMSoverIMS_UEConTest

Conformance Test Aspects – SMS over IMS in E-UTRAN How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'SMSoverIMS_UEConTest', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names SMSoverIMS_UEConTest as a whole word; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:SMSoverIMS_UEConTest

SR_IMS cited

Split rendering over IMS How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'SR_IMS', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names SR_IMS as a whole word; the target documents come from section 5 of SP-240492 - revision of SP-240061 New WID on Split Rendering over IMS (SR_IMS).md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:SR_IMS

TEI17_IMSGID

IMS Optimization for HSS Group ID in an SBA environment (St. 2) How it was counted: the 3 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'TEI17_IMSGID', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names TEI17_IMSGID as a whole word; the target documents come from section 5 of SP-200452_Postponed_SP-200084_S2-2001838_IMS_HSSGID_WID.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:TEI17_IMSGID

VoIMS cited

Deleted - VoIMS bearer related enhancements How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'VoIMS', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names VoIMS as a whole word; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:VoIMS

VoIMS-PCVoIMS

Performance Characterization of VoIMS over HSDPA\EUL channels How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'VoIMS-PCVoIMS', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names VoIMS-PCVoIMS as a whole word; the target documents come from section 5 of SP-050089.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:VoIMS-PCVoIMS

eIMS5G_SBA cited

SBA aspects of enhanced IMS to 5GC integration How it was counted: the 6 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'eIMS5G_SBA', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names eIMS5G_SBA as a whole word; the target documents come from section 5 of SP-190181_S2-1902837_eIMS5G_SBA WID.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:eIMS5G_SBA

eIMSVideo

Video enhancement of IMS CAT/CRS/announcement services How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'eIMSVideo', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names eIMSVideo as a whole word; the target documents come from section 5 of CP-193149.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:eIMSVideo

eIMS_RP cited

Completion of IMS Restoration Procedures How it was counted: the 4 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'eIMS_RP', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names eIMS_RP as a whole word; the target documents come from section 5 of CP-091050-WID-IMS-Restoration.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:eIMS_RP

enIMS cited

Enhancements to IMS for new real time communication services How it was counted: the 1 rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym is exactly 'enIMS', read 2026-08-05; the document count is rows of `tdoc` in /var/www/whatthespec.net/data/database/api/api.sqlite whose work item column names enIMS as a whole word; the target documents come from section 5 of SP-180137.md; the day it was created from table `wi_dates` in /var/www/whatthespec.net/data/database/api/suggest_sidecar.sqlite wi:enIMS

Meeting document 166

C1-216839

LS on access to multiple IMS networks via a 5GC network slice How it was counted: IMS documents of type LS out whose outcome word is approved or agreed, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:C1-216839

C1-220734

LS on progress of FS_eIMS5G2 How it was counted: IMS documents of type LS out whose outcome word is approved or agreed, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:C1-220734

C1-246921 cited

Reply LS on FS_IMS_RES outcome and future work plan How it was counted: IMS documents of type LS out whose outcome word is approved or agreed, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:C1-246921

C1-246950

Reply to Reply LS on CEN's requirements for eCall over IMS How it was counted: IMS documents of type LS out whose outcome word is approved or agreed, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:C1-246950

C1-262608 cited

Reply LS on IMS resiliency How it was counted: IMS documents of type LS out whose outcome word is approved or agreed, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:C1-262608

C3-250657 cited

LS reply on FS_IMS_RES outcome and future work plan How it was counted: IMS documents of type LS out whose outcome word is approved or agreed, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:C3-250657

C3-255462

LS to CT4 for new TS 29.214 AVP to be included in TS 29.230 How it was counted: IMS documents of type LS out whose outcome word is approved or agreed, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:C3-255462

C4-191313

LS on Status of FS_eIMS5G How it was counted: IMS documents of type LS out whose outcome word is approved or agreed, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:C4-191313

C4-204337

AUSF/UDM discovery based on SUCI information How it was counted: IMS documents of type LS out whose outcome word is approved or agreed, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:C4-204337

C4-220445

Progress of FS_eIMS5G2 How it was counted: IMS documents of type LS out whose outcome word is approved or agreed, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:C4-220445

C4-244485 cited

FS_IMS_RES outcome and future work plan How it was counted: IMS documents of type LS out whose outcome word is approved or agreed, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:C4-244485

C4-261402 cited

LS on IMS resiliency How it was counted: IMS documents of type LS out whose outcome word is approved or agreed, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:C4-261402

CP-060101 cited

WID on IMS Stage 3 IETF Protocol Alignment How it was counted: the row of `tdoc` whose name is CP-060101, which is the value of the `hyperlink` field on the work plan row of IMSProtoc, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:CP-060101

CP-070031

FS WID for IMS Restoration Procedures How it was counted: the row of `tdoc` whose name is CP-070031, which is the value of the `hyperlink` field on the work plan row of FS_IMS_RP, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:CP-070031

CP-070096

Updated WID on Multimedia interworking between IM CN subsystem and circuit switched networks How it was counted: the row of `tdoc` whose name is CP-070096, which is the value of the `hyperlink` field on the work plan row of MIW-IMS-St3C3, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:CP-070096

CP-070120

Revision of the WID on IMS Support of Conferencing How it was counted: the row of `tdoc` whose name is CP-070120, which is the value of the `hyperlink` field on the work plan row of IMSconf, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:CP-070120

CP-070685

WID for IMS Application Server Service Data Descriptions for AS interoperability. How it was counted: the row of `tdoc` whose name is CP-070685, which is the value of the `hyperlink` field on the work plan row of FS_IMS_ASIO, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:CP-070685

CP-070729

Updated WID: Multimedia interworking between IMS and CS networks (MIW-IMS / 713024) How it was counted: the row of `tdoc` whose name is CP-070729, which is the value of the `hyperlink` field on the work plan row of MIW-IMS, MIW-IMS-St3C3_MONA, MIW-IMS-St3C4, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:CP-070729

CP-080214

Revised WID for definition of Communication Wait Service How it was counted: the row of `tdoc` whose name is CP-080214, which is the value of the `hyperlink` field on the work plan row of CW_IMS, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:CP-080214

CP-080220

WID for IMS System enhancements for corporate network access How it was counted: the row of `tdoc` whose name is CP-080220, which is the value of the `hyperlink` field on the work plan row of IMS_Corp, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:CP-080220

CP-080429

Revised R8 WID OSA Stage 2/3 enhancements (OSA8) How it was counted: the row of `tdoc` whose name is CP-080429, which is the value of the `hyperlink` field on the work plan row of OSA8-IMS, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:CP-080429

CP-080447

Updated WID (CP-080281) on IMS Restoration Procedures How it was counted: the row of `tdoc` whose name is CP-080447, which is the value of the `hyperlink` field on the work plan row of IMS_RP, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:CP-080447

CP-080451

IMS Application Server Service Data Descriptions for AS interoperability How it was counted: the row of `tdoc` whose name is CP-080451, which is the value of the `hyperlink` field on the work plan row of IMS_ASIO, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:CP-080451

CP-080491

Updated WID for IMS Service Continuity Stage3 How it was counted: the row of `tdoc` whose name is CP-080491, which is the value of the `hyperlink` field on the work plan row of IMS-Cont, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:CP-080491

CP-080794 cited

Revised WID for IMSProtoc Phase 2 How it was counted: the row of `tdoc` whose name is CP-080794, which is the value of the `hyperlink` field on the work plan row of IMSProtoc2, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:CP-080794

CP-090019

IMS-IBCF – TrGW definitions in 3GPP How it was counted: the row of `tdoc` whose name is CP-090019, which is the value of the `hyperlink` field on the work plan row of IMS_IBCF, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:CP-090019

CP-090020

IMS-ALGCF – IMS-AGW definitions in 3GPP How it was counted: the row of `tdoc` whose name is CP-090020, which is the value of the `hyperlink` field on the work plan row of IMS_AGCF, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:CP-090020

CP-090440

new WID on IMS Service Continuity Enhancements How it was counted: the row of `tdoc` whose name is CP-090440, which is the value of the `hyperlink` field on the work plan row of IMS_SCC-SPI, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:CP-090440

CP-090491

new WID on IMS Stage-3 IETF Protocol Alignment How it was counted: the row of `tdoc` whose name is CP-090491, which is the value of the `hyperlink` field on the work plan row of IMSProtoc3, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:CP-090491

CP-090564

Support for IMS Emergency Calls over GPRS and EPS How it was counted: the row of `tdoc` whose name is CP-090564, which is the value of the `hyperlink` field on the work plan row of IMS_EMER_GPRS_EPS, IMS_EMER_GPRS_EPSC1, IMS_EMER_GPRS_EPSC3, IMS_EMER_GPRS_EPSC4, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:CP-090564

CP-090640

Revised WID of I1 interface How it was counted: the row of `tdoc` whose name is CP-090640, which is the value of the `hyperlink` field on the work plan row of IMS_SCC-ICS_I1, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:CP-090640

CP-090882

Revised WID - IMS_EMER_GPRS_EPS-SRVCC How it was counted: the row of `tdoc` whose name is CP-090882, which is the value of the `hyperlink` field on the work plan row of IMS_EMER_GPRS_EPS-SRVCC, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:CP-090882

CP-090883

Revised WID - IMS_SCC-ICS How it was counted: the row of `tdoc` whose name is CP-090883, which is the value of the `hyperlink` field on the work plan row of IMS_SCC-ICS, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:CP-090883

CP-091050 cited

Revised WID: Completion of IMS Restoration Procedures How it was counted: the row of `tdoc` whose name is CP-091050, which is the value of the `hyperlink` field on the work plan row of eIMS_RP, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:CP-091050

CP-100099

Proposed WID for IMS Stage-3 IETF Protocol Alignment How it was counted: the row of `tdoc` whose name is CP-100099, which is the value of the `hyperlink` field on the work plan row of IMSProtoc4, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:CP-100099

CP-100376

Update of WID for AT Commands for IMS-configuration How it was counted: the row of `tdoc` whose name is CP-100376, which is the value of the `hyperlink` field on the work plan row of AT_IMS, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:CP-100376

CP-100424

UICC access to IMS How it was counted: the row of `tdoc` whose name is CP-100424, which is the value of the `hyperlink` field on the work plan row of FS_IMS-UICC, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:CP-100424

CP-100602

Testing the interworking of ISIM Terminals with the IP Multimedia Subsystem How it was counted: the row of `tdoc` whose name is CP-100602, which is the value of the `hyperlink` field on the work plan row of SAES-ISIM_IMS_Test, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:CP-100602

CP-100647

IMS CALL CONTROL How it was counted: the row of `tdoc` whose name is CP-100647, which is the value of the `hyperlink` field on the work plan row of CC_IMS_USIM, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:CP-100647

CP-110279

How it was counted: the row of `tdoc` whose name is CP-110279, which is the value of the `hyperlink` field on the work plan row of IMS-UICC-S, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:CP-110279

CP-110285

How it was counted: the row of `tdoc` whose name is CP-110285, which is the value of the `hyperlink` field on the work plan row of IMS_SC_eIDT, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:CP-110285

CP-110437

How it was counted: the row of `tdoc` whose name is CP-110437, which is the value of the `hyperlink` field on the work plan row of IMSProtoc5, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:CP-110437

CP-110440

How it was counted: the row of `tdoc` whose name is CP-110440, which is the value of the `hyperlink` field on the work plan row of IOI_IMS_CH, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:CP-110440

CP-120756

IM-SSF Application Server Service Data Descriptions How it was counted: the row of `tdoc` whose name is CP-120756, which is the value of the `hyperlink` field on the work plan row of IMS_SSFDD, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:CP-120756

CP-120845

Revised WID on CT aspect on Network Provided Location Information for IMS How it was counted: the row of `tdoc` whose name is CP-120845, which is the value of the `hyperlink` field on the work plan row of NWK-PL2IMS-CT, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:CP-120845

CP-120905

IMS Stage-3 IETF Protocol Alignment How it was counted: the row of `tdoc` whose name is CP-120905, which is the value of the `hyperlink` field on the work plan row of IMSProtoc6, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:CP-120905

CP-130169

WID for IMS impacts on UICC Application Aspects How it was counted: the row of `tdoc` whose name is CP-130169, which is the value of the `hyperlink` field on the work plan row of IMS_UApAs, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:CP-130169

CP-130217

new WID - WID for CT aspects of location based IMS registration control How it was counted: the row of `tdoc` whose name is CP-130217, which is the value of the `hyperlink` field on the work plan row of IMS_RegCon-CT, IMS_RegCon-CT1, IMS_RegCon-CT4, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:CP-130217

CP-130774

Revised WID - Study on Technical Aspects on Roaming End to End scenarios with VoLTE IMS and other networks (FS_REVOLTE_IMS) How it was counted: the row of `tdoc` whose name is CP-130774, which is the value of the `hyperlink` field on the work plan row of FS_REVOLTE_IMS, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:CP-130774

CP-140192

How it was counted: the row of `tdoc` whose name is CP-140192, which is the value of the `hyperlink` field on the work plan row of IMS_WebRTC, IMS_WebRTC-CT, IMS_WebRTC-CT1, IMS_WebRTC-CT4, IMS_WebRTC-data, IMS_WebRTC-holmb, IMS_WebRTC-stun, IMS_WebRTC-yusef, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:CP-140192

CP-140624

Revised WID - IMS_TELEP How it was counted: the row of `tdoc` whose name is CP-140624, which is the value of the `hyperlink` field on the work plan row of IMS_TELEP, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:CP-140624

CP-140815

New WID on IMS Stage-3 IETF Protocol Alignment How it was counted: the row of `tdoc` whose name is CP-140815, which is the value of the `hyperlink` field on the work plan row of IMSProtoc7, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:CP-140815

CP-150238

New WID on Controlling IMS Media Plane with SDP Capability Negotiation How it was counted: the row of `tdoc` whose name is CP-150238, which is the value of the `hyperlink` field on the work plan row of SDPCN_IMS, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:CP-150238

CP-160294

New WID on IMS Stage-3 IETF Protocol Alignment How it was counted: the row of `tdoc` whose name is CP-160294, which is the value of the `hyperlink` field on the work plan row of IMSProtoc8, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:CP-160294

CP-171098

New WID on IMS Stage-3 IETF Protocol Alignment How it was counted: the row of `tdoc` whose name is CP-171098, which is the value of the `hyperlink` field on the work plan row of IMSProtoc9, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:CP-171098

CP-180094

Revised WID on IMS impact due to 5GS IP-CAN How it was counted: the row of `tdoc` whose name is CP-180094, which is the value of the `hyperlink` field on the work plan row of 5GS_Ph1-IMSo5G, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:CP-180094

CP-183084

New WID on IMS Stage-3 IETF Protocol Alignment How it was counted: the row of `tdoc` whose name is CP-183084, which is the value of the `hyperlink` field on the work plan row of IMSProtoc16, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:CP-183084

CP-192023

Revised Work Item on CT aspects of SBA interactions between IMS and 5GC How it was counted: the row of `tdoc` whose name is CP-192023, which is the value of the `hyperlink` field on the work plan row of eIMS5G_SBA, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:CP-192023

CP-193149

New WID on Video enhancement of IMS CAT/CRS/announcement services How it was counted: the row of `tdoc` whose name is CP-193149, which is the value of the `hyperlink` field on the work plan row of eIMSVideo, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:CP-193149

CP-201167

New WID on IMS Stage-3 IETF Protocol Alignment How it was counted: the row of `tdoc` whose name is CP-201167, which is the value of the `hyperlink` field on the work plan row of IMSProtoc17, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:CP-201167

CP-201358

New SID on Enhanced IMS to 5GC Integration Phase 2 How it was counted: the row of `tdoc` whose name is CP-201358, which is the value of the `hyperlink` field on the work plan row of FS_eIMS5G2, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:CP-201358

CP-213082

New WID on IMS Optimization for HSS Group ID in an SBA environment How it was counted: the row of `tdoc` whose name is CP-213082, which is the value of the `hyperlink` field on the work plan row of TEI17_IMSGID, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:CP-213082

CP-223102

Revised WID on IMS Stage-3 IETF Protocol Alignment How it was counted: the row of `tdoc` whose name is CP-223102, which is the value of the `hyperlink` field on the work plan row of IMSProtoc18, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:CP-223102

CP-232281 cited

Study on IMS Disaster Prevention and Restoration Enhancement How it was counted: the row of `tdoc` whose name is CP-232281, which is the value of the `hyperlink` field on the work plan row of FS_IMS_RES, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:CP-232281

CP-251219

Revised WID on IMS Stage-3 IETF Protocol Alignment How it was counted: the row of `tdoc` whose name is CP-251219, which is the value of the `hyperlink` field on the work plan row of IMSProtoc19, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:CP-251219

CP-253168 cited

Revised WID on IMS Disaster Prevention and Restoration Enhancement How it was counted: the row of `tdoc` whose name is CP-253168, which is the value of the `hyperlink` field on the work plan row of IMS_RES-CT, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:CP-253168

CP-260044 cited

IMS Stage-3 IETF Protocol Alignment How it was counted: the row of `tdoc` whose name is CP-260044, which is the value of the `hyperlink` field on the work plan row of IMSProtoc20-CT, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:CP-260044

CP-261069 cited

Study on IMS resiliency How it was counted: the row of `tdoc` whose name is CP-261069, which is the value of the `hyperlink` field on the work plan row of FS_IMSResil, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:CP-261069

NP-010434

How it was counted: the row of `tdoc` whose name is NP-010434, which is the value of the `hyperlink` field on the work plan row of IMS-CCR-IWMM, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:NP-010434

NP-010692

How it was counted: the row of `tdoc` whose name is NP-010692, which is the value of the `hyperlink` field on the work plan row of IMS-ONOSA, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:NP-010692

NP-020091

How it was counted: the row of `tdoc` whose name is NP-020091, which is the value of the `hyperlink` field on the work plan row of IMS-CCR-IWIP, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:NP-020091

NP-020305

How it was counted: the row of `tdoc` whose name is NP-020305, which is the value of the `hyperlink` field on the work plan row of IMS-CAMEL, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:NP-020305

NP-030229

How it was counted: the row of `tdoc` whose name is NP-030229, which is the value of the `hyperlink` field on the work plan row of IMS2-CCR, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:NP-030229

NP-030292

How it was counted: the row of `tdoc` whose name is NP-030292, which is the value of the `hyperlink` field on the work plan row of IMS-CCR-IWCS, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:NP-030292

RP-050160

Proposed WI: Improved support of IMS Realtime Services using HSDPA/EDCH How it was counted: the row of `tdoc` whose name is RP-050160, which is the value of the `hyperlink` field on the work plan row of RANimp-IMSRealTime, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:RP-050160

RP-081140

Support of IMS emergency calls How it was counted: the row of `tdoc` whose name is RP-081140, which is the value of the `hyperlink` field on the work plan row of IMS_EMER_LTE, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:RP-081140

RP-090959

SMS over IMS Conformance Testing How it was counted: the row of `tdoc` whose name is RP-090959, which is the value of the `hyperlink` field on the work plan row of SMSoverIMS_UEConTest, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:RP-090959

RP-100118

New work item proposal: Conformance Test Aspects - IMS Emergency Calls over LTE (Rel-9) How it was counted: the row of `tdoc` whose name is RP-100118, which is the value of the `hyperlink` field on the work plan row of IMS_EMER_LTE_UEConTest, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:RP-100118

RP-100567

New work item proposal: Conformance Test Aspects - CT1 aspects of IMS Emergency Calls over GPRS and EPS How it was counted: the row of `tdoc` whose name is RP-100567, which is the value of the `hyperlink` field on the work plan row of IMS_EMER_GPRS_EPS_UEConTest, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:RP-100567

RP-140440

Revised WID: UE Conformance Test Aspects - Split TTCN Test Models for IMS testing in TS 34.229-3 How it was counted: the row of `tdoc` whose name is RP-140440, which is the value of the `hyperlink` field on the work plan row of IMS-CCR_Test2, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:RP-140440

RP-171635 cited

Revised WID: UE Conformance Test Aspects - IMS for Converged IP Communications How it was counted: the row of `tdoc` whose name is RP-171635, which is the value of the `hyperlink` field on the work plan row of IMS_CONV_IP_COM-UEConTest, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:RP-171635

RP-240283

Revised WID: UE Conformance - IMS Data Channel test; rapporteur: Huawei How it was counted: the row of `tdoc` whose name is RP-240283, which is the value of the `hyperlink` field on the work plan row of IMSProtoc17_dataCH-UEContest, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:RP-240283

RP-253432

Revised WID: UE Conformance - IMS Data Channel for NG_RTC How it was counted: the row of `tdoc` whose name is RP-253432, which is the value of the `hyperlink` field on the work plan row of NG_RTC_IMS_dataCH-UEConTest, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:RP-253432

S2-2413007 cited

Reply LS on FS_IMS_RES outcome and future work plan How it was counted: IMS documents of type LS out whose outcome word is approved or agreed, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:S2-2413007

S2-2510954

LS on AI/ML for Media How it was counted: IMS documents of type LS out whose outcome word is approved or agreed, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:S2-2510954

S4-150401

LS on codec support in IMS-WebRTC for WLAN and fixed access (To: CT1, Cc: CT4, SA, CT, SA2) How it was counted: IMS documents of type LS out whose outcome word is approved or agreed, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:S4-150401

SP-000216 cited

How it was counted: the row of `tdoc` whose name is SP-000216, which is the value of the `hyperlink` field on the work plan row of IMS, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-000216

SP-000398 cited

How it was counted: the row of `tdoc` whose name is SP-000398, which is the value of the `hyperlink` field on the work plan row of IMS-CODEC, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-000398

SP-010323

How it was counted: the row of `tdoc` whose name is SP-010323, which is the value of the `hyperlink` field on the work plan row of IMS-ASEC, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-010323

SP-010339

How it was counted: the row of `tdoc` whose name is SP-010339, which is the value of the `hyperlink` field on the work plan row of IMS-CCR, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-010339

SP-010461

How it was counted: the row of `tdoc` whose name is SP-010461, which is the value of the `hyperlink` field on the work plan row of IMS-OAM, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-010461

SP-010621

How it was counted: the row of `tdoc` whose name is SP-010621, which is the value of the `hyperlink` field on the work plan row of IMS-LI, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-010621

SP-020065 cited

How it was counted: the row of `tdoc` whose name is SP-020065, which is the value of the `hyperlink` field on the work plan row of IMSGM, IMSM, IMSM-CR, IMSM-TR, IMSM-TS, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-020065

SP-030049

How it was counted: the row of `tdoc` whose name is SP-030049, which is the value of the `hyperlink` field on the work plan row of IMS2-CH, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-030049

SP-040327

How it was counted: the row of `tdoc` whose name is SP-040327, which is the value of the `hyperlink` field on the work plan row of IPv4IMS, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-040327

SP-040467

How it was counted: the row of `tdoc` whose name is SP-040467, which is the value of the `hyperlink` field on the work plan row of IRTSD-CS_IMS, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-040467

SP-040479

How it was counted: the row of `tdoc` whose name is SP-040479, which is the value of the `hyperlink` field on the work plan row of IRTSD-IMSCS, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-040479

SP-040691

How it was counted: the row of `tdoc` whose name is SP-040691, which is the value of the `hyperlink` field on the work plan row of SEC-IMS, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-040691

SP-050089

How it was counted: the row of `tdoc` whose name is SP-050089, which is the value of the `hyperlink` field on the work plan row of VoIMS-PCVoIMS, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-050089

SP-050395

How it was counted: the row of `tdoc` whose name is SP-050395, which is the value of the `hyperlink` field on the work plan row of IMS-SE, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-050395

SP-050492

How it was counted: the row of `tdoc` whose name is SP-050492, which is the value of the `hyperlink` field on the work plan row of IMS-RT, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-050492

SP-050604

How it was counted: the row of `tdoc` whose name is SP-050604, which is the value of the `hyperlink` field on the work plan row of IMS-EMER, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-050604

SP-060148

How it was counted: the row of `tdoc` whose name is SP-060148, which is the value of the `hyperlink` field on the work plan row of FS_MLTICAST-IMS, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-060148

SP-060442

How it was counted: the row of `tdoc` whose name is SP-060442, which is the value of the `hyperlink` field on the work plan row of CH7-IMS-ACP, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-060442

SP-060479

How it was counted: the row of `tdoc` whose name is SP-060479, which is the value of the `hyperlink` field on the work plan row of FS_IMSconf, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-060479

SP-070494

How it was counted: the row of `tdoc` whose name is SP-070494, which is the value of the `hyperlink` field on the work plan row of FS_IMS_CSC, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-070494

SP-070496

How it was counted: the row of `tdoc` whose name is SP-070496, which is the value of the `hyperlink` field on the work plan row of IMS-Sec, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-070496

SP-070547

New Study Item for Extended Support of IMS Emergency Calls How it was counted: the row of `tdoc` whose name is SP-070547, which is the value of the `hyperlink` field on the work plan row of FS_IMS-eCall, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-070547

SP-070621

WID to Add Interconnection Border Control Function (IBCF) to IMS Charging (CH8) - Charging Management small Enhancements How it was counted: the row of `tdoc` whose name is SP-070621, which is the value of the `hyperlink` field on the work plan row of CH8_IMS, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-070621

SP-070691

WID for TISPAN Service and Capability for Common IMS How it was counted: the row of `tdoc` whose name is SP-070691, which is the value of the `hyperlink` field on the work plan row of IMSSS-Gal, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-070691

SP-070692

WID for Service requirements for open service access How it was counted: the row of `tdoc` whose name is SP-070692, which is the value of the `hyperlink` field on the work plan row of OSA8-IMSReq, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-070692

SP-070739

New WID on Advice of Charge (AoC) support in IMS Charging How it was counted: the row of `tdoc` whose name is SP-070739, which is the value of the `hyperlink` field on the work plan row of CH8_IMS, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-070739

SP-070822

New WID: Harmonization of Gq' / Rx for Common IMS How it was counted: the row of `tdoc` whose name is SP-070822, which is the value of the `hyperlink` field on the work plan row of IMS_Comm_GqRx_Harm, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-070822

SP-070823

New WID: Documentation of TISPAN NGN R1 and R2 in 3GPP SA WG2 How it was counted: the row of `tdoc` whose name is SP-070823, which is the value of the `hyperlink` field on the work plan row of IMS_Comm_Doc, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-070823

SP-070916

New WID: Maintenance of TISPAN release 2 common IMS How it was counted: the row of `tdoc` whose name is SP-070916, which is the value of the `hyperlink` field on the work plan row of IMS_Comm_Mtce8, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-070916

SP-080090

New WID: System enhancements for the use of IMS services through local breakout How it was counted: the row of `tdoc` whose name is SP-080090, which is the value of the `hyperlink` field on the work plan row of SAES-IMS_LBO, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-080090

SP-080092

New WID: IMS Service Continuity How it was counted: the row of `tdoc` whose name is SP-080092, which is the value of the `hyperlink` field on the work plan row of IMS-Cont, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-080092

SP-080095

Updated WID: IMS System enhancements for corporate network access How it was counted: the row of `tdoc` whose name is SP-080095, which is the value of the `hyperlink` field on the work plan row of IMS_Corp, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-080095

SP-080132

Updated WID: 3GPP System Architecture Evolution Specification (SAES) to include Security Building blocks based on SP-070933 after accepting revision marks How it was counted: the row of `tdoc` whose name is SP-080132, which is the value of the `hyperlink` field on the work plan row of SAES-SA_IMS, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-080132

SP-080201

New WID: IMS initiated and controlled PSS and MBMS User Service How it was counted: the row of `tdoc` whose name is SP-080201, which is the value of the `hyperlink` field on the work plan row of IMS_PSS_MBMS_US, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-080201

SP-080501

Revised WID on Maintenance of TISPAN release 1 common IMS How it was counted: the row of `tdoc` whose name is SP-080501, which is the value of the `hyperlink` field on the work plan row of IMS_Comm_Mtce7, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-080501

SP-080507

WID on Inter-Device Transfer - Requirements How it was counted: the row of `tdoc` whose name is SP-080507, which is the value of the `hyperlink` field on the work plan row of IMS_SCC-IDT, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-080507

SP-080554

Revised WID "System enhancements for interconnection interfaces between two IM CN subsystem networks (IMS-NNI)" How it was counted: the row of `tdoc` whose name is SP-080554, which is the value of the `hyperlink` field on the work plan row of IMS_NNI, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-080554

SP-080556

Revised SID "System enhancements for the use of IMS services in local breakout and optimal routing of media" How it was counted: the row of `tdoc` whose name is SP-080556, which is the value of the `hyperlink` field on the work plan row of FS_IMS_LBO_ORM, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-080556

SP-080561

New WID: WID for IMS Service Continuity Enhancements: Service, Policy and Interactions How it was counted: the row of `tdoc` whose name is SP-080561, which is the value of the `hyperlink` field on the work plan row of IMS_SCC-SPI, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-080561

SP-080633 cited

New WID on IMS Services Centralization and Continuity (IMSSCC) How it was counted: the row of `tdoc` whose name is SP-080633, which is the value of the `hyperlink` field on the work plan row of IMS_SCC, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-080633

SP-080634

New WID: IMS Centralized Services (IMSSCC-ICS) How it was counted: the row of `tdoc` whose name is SP-080634, which is the value of the `hyperlink` field on the work plan row of IMS_SCC-ICS, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-080634

SP-080799

WID on IMS Aspects of Architecture for Home NodeB How it was counted: the row of `tdoc` whose name is SP-080799, which is the value of the `hyperlink` field on the work plan row of EHNB-IMS, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-080799

SP-080844 cited

Updated WID: Support for IMS Emergency Calls over GPRS and EPS How it was counted: the row of `tdoc` whose name is SP-080844, which is the value of the `hyperlink` field on the work plan row of IMS_EMER_GPRS_EPS, IMS_EMER_GPRS_EPS-Sec, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-080844

SP-090099

Updated WID: SR VCC Support for IMS Emergency Calls How it was counted: the row of `tdoc` whose name is SP-090099, which is the value of the `hyperlink` field on the work plan row of IMS_EMER_GPRS_EPS-SRVCC, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-090099

SP-090225

New WID on 'IMS based PSS and MBMS User Service extensions' How it was counted: the row of `tdoc` whose name is SP-090225, which is the value of the `hyperlink` field on the work plan row of IMS_PSS_MBMS_US_EXT, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-090225

SP-090306

Updated WID on RTTI support in IMS charging How it was counted: the row of `tdoc` whose name is SP-090306, which is the value of the `hyperlink` field on the work plan row of IMSTSS-RTTI-CH, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-090306

SP-090452

IMS Service Continuity IUT enhancements How it was counted: the row of `tdoc` whose name is SP-090452, which is the value of the `hyperlink` field on the work plan row of IMS_SC_eIDT, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-090452

SP-090491

New WID: Study on IMS based Peer-to-Peer Content Distribution Services How it was counted: the row of `tdoc` whose name is SP-090491, which is the value of the `hyperlink` field on the work plan row of FS_IMS_P2P, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-090491

SP-090809

Updated Study WID: Study on enhancements to IMS border control functions for advanced IMS interconnection of services How it was counted: the row of `tdoc` whose name is SP-090809, which is the value of the `hyperlink` field on the work plan row of FS_eIMS_IBCF, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-090809

SP-100031

Proposed New WID on 'Optimization of IMS based PSS and MBMS User Service' (OPT_IMS_PSS_MBMS_US) How it was counted: the row of `tdoc` whose name is SP-100031, which is the value of the `hyperlink` field on the work plan row of OPT_IMS_PSS_MBMS_US, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-100031

SP-100083

WI proposal on Key Performance Indicators for IMS How it was counted: the row of `tdoc` whose name is SP-100083, which is the value of the `hyperlink` field on the work plan row of OAM-PM-KPI_IMS, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-100083

SP-100167

Updated WID (BB): Revise IUT enhancement WID: IMS Inter-UE Transfer enhancements How it was counted: the row of `tdoc` whose name is SP-100167, which is the value of the `hyperlink` field on the work plan row of IMS_SC_eIDT, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-100167

SP-100360

Update to: Feasibility Study on IMS Evolution to add IMS Overload Control and update the timescale How it was counted: the row of `tdoc` whose name is SP-100360, which is the value of the `hyperlink` field on the work plan row of FS_eIMS, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-100360

SP-110132

New WI proposal on IMS Interconnection Charging Enhancements for transit scenarios in multi operator environments How it was counted: the row of `tdoc` whose name is SP-110132, which is the value of the `hyperlink` field on the work plan row of IOI_IMS_CH, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-110132

SP-110134

New WI proposal on IMS Performance Management enhancements How it was counted: the row of `tdoc` whose name is SP-110134, which is the value of the `hyperlink` field on the work plan row of OAM-ePM-IMS, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-110134

SP-110588

WID on IMS-Based Telepresence How it was counted: the row of `tdoc` whose name is SP-110588, which is the value of the `hyperlink` field on the work plan row of IMS_TELEP, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-110588

SP-110631

Updated WID: Network Provided Location Information for IMS (NWK-PL2IMS) How it was counted: the row of `tdoc` whose name is SP-110631, which is the value of the `hyperlink` field on the work plan row of NWK-PL2IMS, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-110631

SP-110644

Proposed New Building Block WID on 'Support of IMS Emergency Sessions with Other Media on UTRAN and E-UTRAN ' How it was counted: the row of `tdoc` whose name is SP-110644, which is the value of the `hyperlink` field on the work plan row of NOVES-IMSESOM, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-110644

SP-110700

Revised WID on Network Provided Location Information for IMS Charging How it was counted: the row of `tdoc` whose name is SP-110700, which is the value of the `hyperlink` field on the work plan row of NWK-PL2IMS_CH, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-110700

SP-120543

WID for IMS access via Digital Video Broadcast - Return Channel via Satellite (DVB-RCS2) (IMSSat) How it was counted: the row of `tdoc` whose name is SP-120543, which is the value of the `hyperlink` field on the work plan row of IMSSat, IMSSat-SA1, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-120543

SP-120622

Revised WID Study on IMS Based Peer-to-Peer Content Distribution Services (Stage 2) FS_IMS_P2P_CDS - adding SA WG3 part How it was counted: the row of `tdoc` whose name is SP-120622, which is the value of the `hyperlink` field on the work plan row of FS_IMS_P2P_CDS, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-120622

SP-120735

Updated WID: 'IMS registration control (IMS_RegCon)' How it was counted: the row of `tdoc` whose name is SP-120735, which is the value of the `hyperlink` field on the work plan row of IMS_RegCon, IMS_RegCon-del1, IMS_RegCon-del2, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-120735

SP-120767

New Work Item Description on 'IMS-based Streaming and Download Delivery Enhancements' (IMS_SDE) (Feature) How it was counted: the row of `tdoc` whose name is SP-120767, which is the value of the `hyperlink` field on the work plan row of IMS_SDE, IMS_SDE-SA4, IMS_SDE-SA4TR, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-120767

SP-130609

New Study Item on Charging aspects on Roaming End-to-end scenarios with VoLTE IMS and interconnecting networks How it was counted: the row of `tdoc` whose name is SP-130609, which is the value of the `hyperlink` field on the work plan row of FS_REVOLTE_IMS_CH, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-130609

SP-130707

Revised WID for Web Real Time Communication (WebRTC) Access to IMS How it was counted: the row of `tdoc` whose name is SP-130707, which is the value of the `hyperlink` field on the work plan row of IMS_WebRTC, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-130707

SP-140170

Updated TSG CT WID: Transfer of ETSI business trunking specifications How it was counted: the row of `tdoc` whose name is SP-140170, which is the value of the `hyperlink` field on the work plan row of IMS_Corp2, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-140170

SP-140483

New WID on 'Media Handling Aspects of IMS-based Telepresence' (IMS_TELEP_S4) How it was counted: the row of `tdoc` whose name is SP-140483, which is the value of the `hyperlink` field on the work plan row of IMS_TELEP_S4, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-140483

SP-160081

New Work Item on 'Media Handling Extensions of IMS-based Telepresence' (IMS_TELEP_EXT) How it was counted: the row of `tdoc` whose name is SP-160081, which is the value of the `hyperlink` field on the work plan row of IMS_TELEP_EXT, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-160081

SP-170703

New WID on Study on enhancements to IMS for new real time communication services (FS_enIMS) How it was counted: the row of `tdoc` whose name is SP-170703, which is the value of the `hyperlink` field on the work plan row of FS_enIMS, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-170703

SP-180137

New WID on enIMS (enhancements to IMS for new real time communication services) How it was counted: the row of `tdoc` whose name is SP-180137, which is the value of the `hyperlink` field on the work plan row of enIMS, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-180137

SP-180391

Charging for IMS over 5G System Architecture Phase 1 How it was counted: the row of `tdoc` whose name is SP-180391, which is the value of the `hyperlink` field on the work plan row of 5GS_Ph1_IMSCH, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-180391

SP-180736

Updated SID: Study on Enhanced IMS to 5GC Integration How it was counted: the row of `tdoc` whose name is SP-180736, which is the value of the `hyperlink` field on the work plan row of FS_eIMS5G, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-180736

SP-190181

New WID: Work Item on SBA aspects of enhanced IMS to 5GC integration How it was counted: the row of `tdoc` whose name is SP-190181, which is the value of the `hyperlink` field on the work plan row of eIMS5G_SBA, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-190181

SP-191128

New WID on Security Assurance Specification for IMS How it was counted: the row of `tdoc` whose name is SP-191128, which is the value of the `hyperlink` field on the work plan row of SCAS_IMS, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-191128

SP-200452

New WID: IMS Optimization for HSS Group ID in an SBA environment (TEI17) How it was counted: the row of `tdoc` whose name is SP-200452, which is the value of the `hyperlink` field on the work plan row of TEI17_IMSGID, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-200452

SP-230227

New WID on PS Data Off for IMS Data Channel Service (IMSDCDataOff) How it was counted: the row of `tdoc` whose name is SP-230227, which is the value of the `hyperlink` field on the work plan row of IMSDCDataOff, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-230227

SP-240492 cited

New WID on Split Rendering over IMS (SR_IMS) How it was counted: the row of `tdoc` whose name is SP-240492, which is the value of the `hyperlink` field on the work plan row of SR_IMS, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-240492

SP-250878 cited

New WID on AI/ML for IMS services How it was counted: the row of `tdoc` whose name is SP-250878, which is the value of the `hyperlink` field on the work plan row of AIML_IMS-MED, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-250878

SP-251237 cited

New Study on Security Aspects for IMS resiliency How it was counted: the row of `tdoc` whose name is SP-251237, which is the value of the `hyperlink` field on the work plan row of FS_IMSRE_SEC, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-251237

SP-260686 cited

Revised SID: Study on IMS Architecture Enhancement (FS_enIMS_ARC) How it was counted: the row of `tdoc` whose name is SP-260686, which is the value of the `hyperlink` field on the work plan row of FS_enIMS_ARC, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 tdoc:SP-260686

Counted from the data 141

177 different work item acronyms carry IMS cited

177 How it was counted: distinct values of the acronym field over those 345 rows, read 2026-08-05 count:acronyms

163 of those acronyms survive a boundary that also forbids a lower-case letter cited

163 How it was counted: the same rows counted with (?:^|[^A-Za-z])IMS instead, which throws out the lower-case 'enhanced' prefix 3GPP writes on eIMS5G_SBA, eIMS_RP, enIMS and FS_enIMS_ARC. Recorded so the rule this register uses can be checked, read 2026-08-05 count:acronyms-narrow-rule

C1-112 handled 206 IMS documents, more than any other single meeting cited

206 How it was counted: IMS documents grouped by meeting code, largest first, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:busiest-meeting

92 IMS documents name 23.228 as the document they change cited

92 How it was counted: IMS documents whose change-request column names 23.228, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05, of which 92 are of type CR, CR pack or draftCR count:crs-23-228

1680 IMS documents name 24.229 as the document they change cited

1680 How it was counted: IMS documents whose change-request column names 24.229, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05, of which 1675 are of type CR, CR pack or draftCR count:crs-24-229

157 of the 177 IMS acronyms have a work item description on this machine cited

157 How it was counted: folders under /var/www/whatthespec.net/data/data/wis holding a converted description that proves it belongs to that work item, read 2026-08-05 count:descriptions

476 documents carry the work item 5GS_Ph1-IMSo5G cited

476 How it was counted: rows of `tdoc` whose work item column names 5GS_Ph1-IMSo5G 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 count:docs-5gs-ph1-imso5g

32 documents carry the work item AIML_IMS-MED cited

32 How it was counted: rows of `tdoc` whose work item column names AIML_IMS-MED 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 count:docs-aiml-ims-med

29 documents carry the work item CW_IMS

29 How it was counted: rows of `tdoc` whose work item column names CW_IMS 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 count:docs-cw-ims

543 documents carry the work item eIMS5G_SBA cited

543 How it was counted: 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 count:docs-eims5g-sba

36 documents carry the work item eIMSVideo

36 How it was counted: rows of `tdoc` whose work item column names eIMSVideo 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 count:docs-eimsvideo

36 documents carry the work item enIMS

36 How it was counted: rows of `tdoc` whose work item column names enIMS 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 count:docs-enims

228 documents carry the work item FS_eIMS5G cited

228 How it was counted: rows of `tdoc` whose work item column names FS_eIMS5G 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 count:docs-fs-eims5g

184 documents carry the work item FS_eIMS5G2 cited

184 How it was counted: rows of `tdoc` whose work item column names FS_eIMS5G2 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 count:docs-fs-eims5g2

45 documents carry the work item FS_enIMS

45 How it was counted: rows of `tdoc` whose work item column names FS_enIMS 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 count:docs-fs-enims

51 documents carry the work item FS_enIMS_ARC cited

51 How it was counted: rows of `tdoc` whose work item column names FS_enIMS_ARC 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 count:docs-fs-enims-arc

147 documents carry the work item FS_IMS_RES cited

147 How it was counted: rows of `tdoc` whose work item column names FS_IMS_RES 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 count:docs-fs-ims-res

93 documents carry the work item FS_IMSResil cited

93 How it was counted: rows of `tdoc` whose work item column names FS_IMSResil 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 count:docs-fs-imsresil

35 documents carry the work item FS_REVOLTE_IMS_CH

35 How it was counted: rows of `tdoc` whose work item column names FS_REVOLTE_IMS_CH 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 count:docs-fs-revolte-ims-ch

207 documents carry the work item IMS-CCR-IWCS cited

207 How it was counted: rows of `tdoc` whose work item column names IMS-CCR-IWCS 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 count:docs-ims-ccr-iwcs

59 documents carry the work item IMS_CONV_IP_COM-UEConTest

59 How it was counted: rows of `tdoc` whose work item column names IMS_CONV_IP_COM-UEConTest 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 count:docs-ims-conv-ip-com-uecontest

19 documents carry the work item IMS_EMER_GPRS_EPS cited

19 How it was counted: rows of `tdoc` whose work item column names IMS_EMER_GPRS_EPS 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 count:docs-ims-emer-gprs-eps

101 documents carry the work item IMS_RES-CT cited

101 How it was counted: rows of `tdoc` whose work item column names IMS_RES-CT 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 count:docs-ims-res-ct

116 documents carry the work item IMS_TELEP cited

116 How it was counted: rows of `tdoc` whose work item column names IMS_TELEP 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 count:docs-ims-telep

71 documents carry the work item IMS_TELEP_S4 cited

71 How it was counted: rows of `tdoc` whose work item column names IMS_TELEP_S4 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 count:docs-ims-telep-s4

139 documents carry the work item IMS_WebRTC cited

139 How it was counted: rows of `tdoc` whose work item column names IMS_WebRTC 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 count:docs-ims-webrtc

101 documents carry the work item IMS_WebRTC-CT cited

101 How it was counted: rows of `tdoc` whose work item column names IMS_WebRTC-CT 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 count:docs-ims-webrtc-ct

72 documents carry the work item IMSProtoc16 cited

72 How it was counted: rows of `tdoc` whose work item column names IMSProtoc16 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 count:docs-imsprotoc16

26 documents carry the work item IMSProtoc17 cited

26 How it was counted: rows of `tdoc` whose work item column names IMSProtoc17 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 count:docs-imsprotoc17

20 documents carry the work item IMSProtoc17_dataCH-UEContest

20 How it was counted: rows of `tdoc` whose work item column names IMSProtoc17_dataCH-UEContest 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 count:docs-imsprotoc17-datach-uecontest

45 documents carry the work item IMSProtoc18 cited

45 How it was counted: rows of `tdoc` whose work item column names IMSProtoc18 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 count:docs-imsprotoc18

62 documents carry the work item IMSProtoc19 cited

62 How it was counted: rows of `tdoc` whose work item column names IMSProtoc19 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 count:docs-imsprotoc19

248 documents carry the work item IMSProtoc2 cited

248 How it was counted: rows of `tdoc` whose work item column names IMSProtoc2 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 count:docs-imsprotoc2

19 documents carry the work item IMSProtoc20-CT cited

19 How it was counted: rows of `tdoc` whose work item column names IMSProtoc20-CT 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 count:docs-imsprotoc20-ct

32 documents carry the work item IMSProtoc3 cited

32 How it was counted: rows of `tdoc` whose work item column names IMSProtoc3 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 count:docs-imsprotoc3

19 documents carry the work item IMSProtoc4 cited

19 How it was counted: rows of `tdoc` whose work item column names IMSProtoc4 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 count:docs-imsprotoc4

248 documents carry the work item IMSProtoc5 cited

248 How it was counted: rows of `tdoc` whose work item column names IMSProtoc5 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 count:docs-imsprotoc5

209 documents carry the work item IMSProtoc6 cited

209 How it was counted: rows of `tdoc` whose work item column names IMSProtoc6 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 count:docs-imsprotoc6

364 documents carry the work item IMSProtoc7 cited

364 How it was counted: rows of `tdoc` whose work item column names IMSProtoc7 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 count:docs-imsprotoc7

169 documents carry the work item IMSProtoc8 cited

169 How it was counted: rows of `tdoc` whose work item column names IMSProtoc8 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 count:docs-imsprotoc8

123 documents carry the work item IMSProtoc9 cited

123 How it was counted: rows of `tdoc` whose work item column names IMSProtoc9 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 count:docs-imsprotoc9

92 documents carry the work item NG_RTC_IMS_dataCH-UEConTest

92 How it was counted: rows of `tdoc` whose work item column names NG_RTC_IMS_dataCH-UEConTest 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 count:docs-ng-rtc-ims-datach-uecontest

36 documents carry the work item NWK-PL2IMS-CT cited

36 How it was counted: rows of `tdoc` whose work item column names NWK-PL2IMS-CT 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 count:docs-nwk-pl2ims-ct

83 documents carry the work item SCAS_IMS cited

83 How it was counted: rows of `tdoc` whose work item column names SCAS_IMS 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 count:docs-scas-ims

71 documents carry the work item SDPCN_IMS

71 How it was counted: rows of `tdoc` whose work item column names SDPCN_IMS 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 count:docs-sdpcn-ims

84 documents carry the work item SR_IMS cited

84 How it was counted: rows of `tdoc` whose work item column names SR_IMS 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 count:docs-sr-ims

4939 IMS meeting documents cited

4939 How it was counted: rows of table `tdoc` whose work item column holds, as a whole word, one of the 177 IMS acronyms — 159 different spellings of that column match, because it sometimes carries two work item names at once, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:documents

the document store holds 1629723 meeting documents altogether cited

1629723 How it was counted: rows of table `tdoc`, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05; 852617 of them carry any work item acronym at all count:documents-all

92 IMS documents are marked Rel-10 cited

92 How it was counted: IMS documents whose release column is 'Rel-10', asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05. That is the release the document was filed against and nothing more count:documents-rel-10

164 IMS documents are marked Rel-11 cited

164 How it was counted: IMS documents whose release column is 'Rel-11', asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05. That is the release the document was filed against and nothing more count:documents-rel-11

433 IMS documents are marked Rel-12 cited

433 How it was counted: IMS documents whose release column is 'Rel-12', asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05. That is the release the document was filed against and nothing more count:documents-rel-12

830 IMS documents are marked Rel-13 cited

830 How it was counted: IMS documents whose release column is 'Rel-13', asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05. That is the release the document was filed against and nothing more count:documents-rel-13

354 IMS documents are marked Rel-14 cited

354 How it was counted: IMS documents whose release column is 'Rel-14', asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05. That is the release the document was filed against and nothing more count:documents-rel-14

640 IMS documents are marked Rel-15 cited

640 How it was counted: IMS documents whose release column is 'Rel-15', asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05. That is the release the document was filed against and nothing more count:documents-rel-15

943 IMS documents are marked Rel-16 cited

943 How it was counted: IMS documents whose release column is 'Rel-16', asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05. That is the release the document was filed against and nothing more count:documents-rel-16

419 IMS documents are marked Rel-17 cited

419 How it was counted: IMS documents whose release column is 'Rel-17', asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05. That is the release the document was filed against and nothing more count:documents-rel-17

217 IMS documents are marked Rel-18 cited

217 How it was counted: IMS documents whose release column is 'Rel-18', asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05. That is the release the document was filed against and nothing more count:documents-rel-18

387 IMS documents are marked Rel-19 cited

387 How it was counted: IMS documents whose release column is 'Rel-19', asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05. That is the release the document was filed against and nothing more count:documents-rel-19

189 IMS documents are marked Rel-20 cited

189 How it was counted: IMS documents whose release column is 'Rel-20', asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05. That is the release the document was filed against and nothing more count:documents-rel-20

85 IMS documents are marked Rel-8

85 How it was counted: IMS documents whose release column is 'Rel-8', asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05. That is the release the document was filed against and nothing more count:documents-rel-8

87 IMS documents are marked Rel-9

87 How it was counted: IMS documents whose release column is 'Rel-9', asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05. That is the release the document was filed against and nothing more count:documents-rel-9

BlackBerry UK Ltd. filed 123 IMS documents cited

123 How it was counted: IMS documents grouped by the source column, largest first, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05. The column is the name the document spelled, so one company under two spellings counts twice and no name was resolved to a parent company count:filer-blackberry-uk-ltd

China Mobile filed 167 IMS documents cited

167 How it was counted: IMS documents grouped by the source column, largest first, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05. The column is the name the document spelled, so one company under two spellings counts twice and no name was resolved to a parent company count:filer-china-mobile

Ericsson filed 602 IMS documents cited

602 How it was counted: IMS documents grouped by the source column, largest first, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05. The column is the name the document spelled, so one company under two spellings counts twice and no name was resolved to a parent company count:filer-ericsson

Ericsson / Nevenka filed 130 IMS documents cited

130 How it was counted: IMS documents grouped by the source column, largest first, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05. The column is the name the document spelled, so one company under two spellings counts twice and no name was resolved to a parent company count:filer-ericsson-nevenka

Huawei filed 173 IMS documents cited

173 How it was counted: IMS documents grouped by the source column, largest first, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05. The column is the name the document spelled, so one company under two spellings counts twice and no name was resolved to a parent company count:filer-huawei

Huawei, HiSilicon filed 158 IMS documents cited

158 How it was counted: IMS documents grouped by the source column, largest first, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05. The column is the name the document spelled, so one company under two spellings counts twice and no name was resolved to a parent company count:filer-huawei-hisilicon

Nokia, Nokia Shanghai Bell filed 258 IMS documents cited

258 How it was counted: IMS documents grouped by the source column, largest first, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05. The column is the name the document spelled, so one company under two spellings counts twice and no name was resolved to a parent company count:filer-nokia-nokia-shanghai-bell

Orange / Marianne filed 160 IMS documents cited

160 How it was counted: IMS documents grouped by the source column, largest first, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05. The column is the name the document spelled, so one company under two spellings counts twice and no name was resolved to a parent company count:filer-orange-marianne

374 different names appear as the writer of an IMS document cited

374 How it was counted: distinct values of the source column over the IMS documents, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05. Same caution: the column is free text count:filers

the earliest IMS document on record went up on 2015-01-23 cited

2015-01-23 How it was counted: the smallest upload stamp over the IMS documents that is 1999-01-01 or later. This is where the store's work item labelling begins and not where IMS work began: the work plan's own Rel-5 rows carry planned days from 2000-01-03, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:first-document

the newest IMS document on record went up on 2026-08-04 cited

2026-08-04 How it was counted: the largest upload stamp over the IMS documents, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:last-document

309 meetings have had IMS documents on the table cited

309 How it was counted: distinct meeting codes over the IMS documents that are written as a meeting code; a handful of stored codes are a whole ad-hoc title that ran into the field and are counted as documents but not as meetings, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:meetings

36 work items are quoted here in their proposers' own words cited

36 How it was counted: work items chosen by name for what they did, plus the 12 with the most documents behind them; each is quoted only where a description in its own folder proves it belongs to it, read 2026-08-05 count:quoted-workitems

IMS work items are spread over 16 releases, Rel-5 to Rel-20 cited

16 How it was counted: distinct values of the release field over the 345 IMS work plan rows, read 2026-08-05. They are named in the order the field spells them and no date of any release is stored count:releases

3599 3GPP specifications are marked active altogether cited

3599 How it was counted: catalogue rows whose active column is yes, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05. The flag is about the catalogue row and says nothing about whether work is running count:specs-active

15 documents are named by fewer than 3 IMS change requests and by no work item cited

15 How it was counted: specifications named in the change-request column of one or two IMS documents and by no work item (23.288, 24.109, 24.259, 24.322, 24.379, 24.39, 24.481, 24.484 and more); left out of the register because one document is as likely a filing mistake as a real link, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:specs-thin

241 specifications this work touches cited

241 How it was counted: catalogue rows for every document a work item names as one it changes, plus every one named in the change-request column of at least 3 IMS documents, asked of /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-05 count:specs-touched

1736 IMS documents carry the outcome word agreed cited

1736 How it was counted: IMS documents whose status column is exactly 'agreed', asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05. The word is about that document and never about the work item count:status-agreed

379 IMS documents carry the outcome word approved cited

379 How it was counted: IMS documents whose status column is exactly 'approved', asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05. The word is about that document and never about the work item count:status-approved

19 IMS documents carry the outcome word available cited

19 How it was counted: IMS documents whose status column is exactly 'available', asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05. The word is about that document and never about the work item count:status-available

24 IMS documents carry the outcome word endorsed cited

24 How it was counted: IMS documents whose status column is exactly 'endorsed', asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05. The word is about that document and never about the work item count:status-endorsed

68 IMS documents carry the outcome word merged cited

68 How it was counted: IMS documents whose status column is exactly 'merged', asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05. The word is about that document and never about the work item count:status-merged

20 IMS documents carry the outcome word not pursued cited

20 How it was counted: IMS documents whose status column is exactly 'not pursued', asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05. The word is about that document and never about the work item count:status-not-pursued

51 IMS documents carry the outcome word not treated cited

51 How it was counted: IMS documents whose status column is exactly 'not treated', asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05. The word is about that document and never about the work item count:status-not-treated

173 IMS documents carry the outcome word noted cited

173 How it was counted: IMS documents whose status column is exactly 'noted', asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05. The word is about that document and never about the work item count:status-noted

6 IMS documents carry the outcome word partially approved cited

6 How it was counted: IMS documents whose status column is exactly 'partially approved', asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05. The word is about that document and never about the work item count:status-partially-approved

297 IMS documents carry the outcome word postponed cited

297 How it was counted: IMS documents whose status column is exactly 'postponed', asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05. The word is about that document and never about the work item count:status-postponed

35 IMS documents carry the outcome word rejected cited

35 How it was counted: IMS documents whose status column is exactly 'rejected', asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05. The word is about that document and never about the work item count:status-rejected

1942 IMS documents carry the outcome word revised cited

1942 How it was counted: IMS documents whose status column is exactly 'revised', asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05. The word is about that document and never about the work item count:status-revised

189 IMS documents carry the outcome word withdrawn cited

189 How it was counted: IMS documents whose status column is exactly 'withdrawn', asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05. The word is about that document and never about the work item count:status-withdrawn

3509 IMS documents are of type CR cited

3509 How it was counted: IMS documents whose type column is exactly 'CR', asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:type-cr

175 IMS documents are of type CR pack cited

175 How it was counted: IMS documents whose type column is exactly 'CR pack', asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:type-cr-pack

61 IMS documents are of type discussion cited

61 How it was counted: IMS documents whose type column is exactly 'discussion', asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:type-discussion

51 IMS documents are of type draft TR cited

51 How it was counted: IMS documents whose type column is exactly 'draft TR', asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:type-draft-tr

32 IMS documents are of type draft TS cited

32 How it was counted: IMS documents whose type column is exactly 'draft TS', asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:type-draft-ts

38 IMS documents are of type draftCR cited

38 How it was counted: IMS documents whose type column is exactly 'draftCR', asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:type-draftcr

32 IMS documents are of type LS in cited

32 How it was counted: IMS documents whose type column is exactly 'LS in', asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:type-ls-in

45 IMS documents are of type LS out cited

45 How it was counted: IMS documents whose type column is exactly 'LS out', asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:type-ls-out

90 IMS documents are of type other cited

90 How it was counted: IMS documents whose type column is exactly 'other', asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:type-other

767 IMS documents are of type pCR cited

767 How it was counted: IMS documents whose type column is exactly 'pCR', asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:type-pcr

14 IMS documents are of type SID revised

14 How it was counted: IMS documents whose type column is exactly 'SID revised', asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:type-sid-revised

9 IMS documents are of type TS or TR cover

9 How it was counted: IMS documents whose type column is exactly 'TS or TR cover', asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:type-ts-or-tr-cover

19 IMS documents are of type WI exception request cited

19 How it was counted: IMS documents whose type column is exactly 'WI exception request', asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:type-wi-exception-request

30 IMS documents are of type WI status report cited

30 How it was counted: IMS documents whose type column is exactly 'WI status report', asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:type-wi-status-report

9 IMS documents are of type WI summary

9 How it was counted: IMS documents whose type column is exactly 'WI summary', asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:type-wi-summary

40 IMS documents are of type WID revised cited

40 How it was counted: IMS documents whose type column is exactly 'WID revised', asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:type-wid-revised

16 IMS documents are of type Work Plan cited

16 How it was counted: IMS documents whose type column is exactly 'Work Plan', asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:type-work-plan

237 IMS documents carry no upload time cited

237 How it was counted: IMS documents whose upload column is empty, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05, which is why the per-year counts do not add up to the total and why a count over a year and a count over the whole record answer different questions count:undated-documents

339 of the 345 IMS work plan rows stand at 100% cited

339 How it was counted: rows taken in by the acronym rule whose completion field reads 1, read 2026-08-05. The field is a percentage the work plan keeps by hand and it is not a status word count:wp-complete

22 IMS work item acronyms carry the word Deleted at the front of their own name cited

22 How it was counted: rows taken in by the acronym rule whose name field begins 'Deleted', read 2026-08-05. The prefix is written by hand into the title and is the only mark of the kind the work plan carries; it is not a status field (FS_IMSRE_SEC, FS_eIMS_IBCF, IMS-EMER, IMS-RT, IMS-SE, IMS8, IMSLocal, IMSProtoc5, IMSProtoc6, IMS_Comm_GqRx_Harm, IMS_RegCon, IMS_RegCon-CT, IMS_RegCon-CT1, IMS_RegCon-CT4, IMS_RegCon-del1, IMS_RegCon-del2, IMS_TELEP_S4, IMS_WebRTC-holmb, IMS_WebRTC-yusef, IRTSD-IMSCS, RANimp-RABSE-IuEnhIMS, VoIMS) count:wp-deleted

17 IMS work plan rows are marked Rel-10 cited

17 How it was counted: 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-10', read 2026-08-05 count:wp-rel-10

25 IMS work plan rows are marked Rel-11 cited

25 How it was counted: 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-11', read 2026-08-05 count:wp-rel-11

60 IMS work plan rows are marked Rel-12 cited

60 How it was counted: 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-12', read 2026-08-05 count:wp-rel-12

15 IMS work plan rows are marked Rel-13 cited

15 How it was counted: 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-13', read 2026-08-05 count:wp-rel-13

17 IMS work plan rows are marked Rel-14 cited

17 How it was counted: 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-14', read 2026-08-05 count:wp-rel-14

12 IMS work plan rows are marked Rel-15 cited

12 How it was counted: 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-15', read 2026-08-05 count:wp-rel-15

13 IMS work plan rows are marked Rel-16 cited

13 How it was counted: 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 count:wp-rel-16

12 IMS work plan rows are marked Rel-17 cited

12 How it was counted: 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-17', read 2026-08-05 count:wp-rel-17

4 IMS work plan rows are marked Rel-18 cited

4 How it was counted: 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-18', read 2026-08-05 count:wp-rel-18

10 IMS work plan rows are marked Rel-19 cited

10 How it was counted: 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-19', read 2026-08-05 count:wp-rel-19

7 IMS work plan rows are marked Rel-20 cited

7 How it was counted: 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-20', read 2026-08-05 count:wp-rel-20

14 IMS work plan rows are marked Rel-5 cited

14 How it was counted: 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-5', read 2026-08-05 count:wp-rel-5

17 IMS work plan rows are marked Rel-6 cited

17 How it was counted: 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-6', read 2026-08-05 count:wp-rel-6

13 IMS work plan rows are marked Rel-7 cited

13 How it was counted: 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-7', read 2026-08-05 count:wp-rel-7

64 IMS work plan rows are marked Rel-8 cited

64 How it was counted: 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-8', read 2026-08-05 count:wp-rel-8

45 IMS work plan rows are marked Rel-9 cited

45 How it was counted: 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-9', read 2026-08-05 count:wp-rel-9

345 rows of the 3GPP work plan are IMS work cited

345 How it was counted: rows of table `item` in /var/www/whatthespec.net/data/database/api/wp.sqlite whose acronym matches the regular expression (?:^|[^A-Z])IMS — the three letters IMS with no capital letter in front of them — out of 9495 rows altogether, read 2026-08-05 count:wp-rows

1 IMS work item acronyms carry the word STOPPED at the front of their own name cited

1 How it was counted: rows taken in by the acronym rule whose name field begins 'STOPPED', read 2026-08-05. The prefix is written by hand into the title and is the only mark of the kind the work plan carries; it is not a status field (IMSProtoc17_dataCH-UEContest) count:wp-stopped

855 IMS documents were filed in 2015

855 How it was counted: IMS documents whose upload stamp starts 2015, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:year-2015

512 IMS documents were filed in 2016

512 How it was counted: IMS documents whose upload stamp starts 2016, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:year-2016

443 IMS documents were filed in 2017

443 How it was counted: IMS documents whose upload stamp starts 2017, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:year-2017

776 IMS documents were filed in 2018

776 How it was counted: IMS documents whose upload stamp starts 2018, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:year-2018

478 IMS documents were filed in 2019

478 How it was counted: IMS documents whose upload stamp starts 2019, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:year-2019

386 IMS documents were filed in 2020

386 How it was counted: IMS documents whose upload stamp starts 2020, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:year-2020

329 IMS documents were filed in 2021

329 How it was counted: IMS documents whose upload stamp starts 2021, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:year-2021

77 IMS documents were filed in 2022

77 How it was counted: IMS documents whose upload stamp starts 2022, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:year-2022

106 IMS documents were filed in 2023

106 How it was counted: IMS documents whose upload stamp starts 2023, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:year-2023

209 IMS documents were filed in 2024 cited

209 How it was counted: IMS documents whose upload stamp starts 2024, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:year-2024

365 IMS documents were filed in 2025 cited

365 How it was counted: IMS documents whose upload stamp starts 2025, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:year-2025

166 IMS documents were filed in 2026 cited

166 How it was counted: IMS documents whose upload stamp starts 2026, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05 count:year-2026

Quoted wording 80

the scope of 22.173 cited

The present document define the IMS Multimedia Telephony service and the minimum set of capabilities required to secure multi-vendor and multi-operator inter-operability for Multimedia Telephony and related Supplementary Services. How it was counted: the opening sentences of clause 1 of the parsed text at /var/www/whatthespec.net/data/friendlyspec/json/22173/20.0.0/, copied word for word, read 2026-08-05 quote:scope:22.173

the scope of 22.228 cited

This TS defines the service requirements from users’ and operators’ perspective for the support of IP multimedia applications through the IMS. How it was counted: the opening sentences of clause 1 of the parsed text at /var/www/whatthespec.net/data/friendlyspec/json/22228/19.0.0/, copied word for word, read 2026-08-05 quote:scope:22.228

the scope of 23.167 cited

This document defines the stage 2 service description for emergency services in the IP Multimedia Core Network Subsystem (IMS), including the elements necessary to support IP Multimedia (IM) emergency services and IM emergency services for eCall. ITUT Recommendation I.130 [4] describes a three-stage method for characterisation of telecommunication services and ITUT Recommendation Q.65 [3] defines stage 2 of the method. How it was counted: the opening sentences of clause 1 of the parsed text at /var/www/whatthespec.net/data/friendlyspec/json/23167/20.0.0/, copied word for word, read 2026-08-05 quote:scope:23.167

the scope of 23.218 cited

The present document specifies the IP Multimedia (IM) Call Model for handling of an IP multimedia session origination and termination for an IP Multimedia subscriber. How it was counted: the opening sentences of clause 1 of the parsed text at /var/www/whatthespec.net/data/friendlyspec/json/23218/19.0.0/, copied word for word, read 2026-08-05 quote:scope:23.218

the scope of 23.228 cited

This document defines the stage-2 service description for the IP Multimedia Core Network Subsystem (IMS), which includes the elements necessary to support IP Multimedia (IM) services. ITUT Recommendation I.130 [4] describes a three-stage method for characterisation of telecommunication services and ITUT Recommendation Q.65 [3] defines stage 2 of the method. How it was counted: the opening sentences of clause 1 of the parsed text at /var/www/whatthespec.net/data/friendlyspec/json/23228/20.0.0/, copied word for word, read 2026-08-05 quote:scope:23.228

the scope of 23.237 cited

The present document specifies the architectural requirements and procedures for delivery of IMS Service Continuity. How it was counted: the opening sentences of clause 1 of the parsed text at /var/www/whatthespec.net/data/friendlyspec/json/23237/19.0.0/, copied word for word, read 2026-08-05 quote:scope:23.237

the scope of 23.292 cited

This document specifies the architectural requirements for delivery of consistent services to the user regardless of the attached access type (e.g. CS domain access, or IP-CAN). How it was counted: the opening sentences of clause 1 of the parsed text at /var/www/whatthespec.net/data/friendlyspec/json/23292/19.0.0/, copied word for word, read 2026-08-05 quote:scope:23.292

the scope of 23.334 cited

Annex G of 3GPP TS 23.228 [2] gives out an IMS Application Level Gateway (IMS-ALG) and IMS Access Media Gateway (IMS-AGW) based reference model to support NAPT-PT, gate control and traffic policing between IP-CAN and IMS domain. How it was counted: the opening sentences of clause 1 of the parsed text at /var/www/whatthespec.net/data/friendlyspec/json/23334/19.0.0/, copied word for word, read 2026-08-05 quote:scope:23.334

the scope of 23.380 cited

The present document specifies the procedures required in 3GPP IMS to handle a S-CSCF or a P-CSCF service interruption scenario with minimum impact to the service to the end user. How it was counted: the opening sentences of clause 1 of the parsed text at /var/www/whatthespec.net/data/friendlyspec/json/23380/20.0.0/, copied word for word, read 2026-08-05 quote:scope:23.380

the scope of 23.801-04 cited

This study aims to: How it was counted: the opening sentences of clause 1 of the parsed text at /var/www/whatthespec.net/data/friendlyspec/json/23801-04/0.1.0/, copied word for word, read 2026-08-05 quote:scope:23.801-04

the scope of 24.229 cited

The present document defines a call control protocol for use in the IP Multimedia (IM) Core Network (CN) subsystem based on the Session Initiation Protocol (SIP), and the associated Session Description Protocol (SDP). How it was counted: the opening sentences of clause 1 of the parsed text at /var/www/whatthespec.net/data/friendlyspec/json/24229/20.0.0/, copied word for word, read 2026-08-05 quote:scope:24.229

"Access independence" as 22.228 defines it cited

Access independence: the ability for the subscribers to access their IP Multimedia services over any access network capable of providing IP-connectivity, e.g. via: How it was counted: the paragraph of clause 3.1 of the parsed text at /var/www/whatthespec.net/data/friendlyspec/json/22228/19.0.0/ that begins 'Access independence', copied word for word, read 2026-08-05 quote:term:access-independence

"Application data channel" as 23.228 defines it cited

Application data channel: A data channel within an IMS session used to transfer data of data channel applications between UEs or between the UE and the network. How it was counted: the paragraph of clause 3.1 of the parsed text at /var/www/whatthespec.net/data/friendlyspec/json/23228/20.0.0/ that begins 'Application data channel', copied word for word, read 2026-08-05 quote:term:application-data-channel

"Conference" as 22.228 defines it cited

Conference: An IP multimedia session with two or more participants. Each conference has a "conference focus". How it was counted: the paragraph of clause 3.1 of the parsed text at /var/www/whatthespec.net/data/friendlyspec/json/22228/19.0.0/ that begins 'Conference', copied word for word, read 2026-08-05 quote:term:conference

"Data channel application" as 23.228 defines it cited

Data channel application: A HTML page including JavaScript(s) and optionally image(s) and style sheet(s). It is downloaded from the network to the UE through the bootstrap data channel. How it was counted: the paragraph of clause 3.1 of the parsed text at /var/www/whatthespec.net/data/friendlyspec/json/23228/20.0.0/ that begins 'Data channel application', copied word for word, read 2026-08-05 quote:term:data-channel-application

"IM CN subsystem" as 22.228 defines it cited

IM CN subsystem: (IP Multimedia CN subsystem) comprises of all CN elements for the provision of IP multimedia applications over IP multimedia sessions How it was counted: the paragraph of clause 3.1 of the parsed text at /var/www/whatthespec.net/data/friendlyspec/json/22228/19.0.0/ that begins 'IM CN subsystem', copied word for word, read 2026-08-05 quote:term:im-cn-subsystem

"IMS application" as 23.228 defines it cited

IMS application: An IMS application is an application that uses an IMS communication service(s) in order to provide a specific service to the end-user. An IMS application utilises the IMS communication service(s) as they are specified without extending the definition of the IMS communication service(s). How it was counted: the paragraph of clause 3.1 of the parsed text at /var/www/whatthespec.net/data/friendlyspec/json/23228/20.0.0/ that begins 'IMS application', copied word for word, read 2026-08-05 quote:term:ims-application

"IP multimedia application" as 22.228 defines it cited

IP multimedia application: an application that handles one or more media types simultaneously such as speech, audio, video and data (e.g. chat text, shared whiteboard) in a synchronised way from the user’s point of view. A multimedia application may involve multiple media streams of the same or different types multiple parties, multiple connections, and the addition or deletion of resources within a single IP multimedia session. How it was counted: the paragraph of clause 3.1 of the parsed text at /var/www/whatthespec.net/data/friendlyspec/json/22228/19.0.0/ that begins 'IP multimedia application', copied word for word, read 2026-08-05 quote:term:ip-multimedia-application

"IP multimedia service" as 22.228 defines it cited

IP multimedia service: an IP multimedia service is the user experience provided by one or more IP multimedia applications. How it was counted: the paragraph of clause 3.1 of the parsed text at /var/www/whatthespec.net/data/friendlyspec/json/22228/19.0.0/ that begins 'IP multimedia service', copied word for word, read 2026-08-05 quote:term:ip-multimedia-service

"IP multimedia session" as 22.228 defines it cited

IP multimedia session: an IP multimedia session is a set of multimedia senders and receivers and the data streams flowing from senders to receivers. IP multimedia sessions are supported by the IP multimedia CN Subsystem and are enabled by IP connectivity bearers (e.g. How it was counted: the paragraph of clause 3.1 of the parsed text at /var/www/whatthespec.net/data/friendlyspec/json/22228/19.0.0/ that begins 'IP multimedia session', copied word for word, read 2026-08-05 quote:term:ip-multimedia-session

what 5GS_Ph1-IMSo5G set out to do cited

The objective is to study and then specify the core-network and terminal protocol aspects to support IMS services including IMS emergency services over 5G. This work item is to deal with the technical issues within IMS area, while those of the 5G core network are not covered in this work item. How it was counted: the opening sentences of the objective of the work item description /var/www/whatthespec.net/data/data/wis/760029/CP-180094/CP-180094.md, copied word for word, read 2026-08-05. That file was taken as this work item's own because it states the unique identifier of this work plan row quote:what:5GS_Ph1-IMSo5G

what AIML_IMS-MED set out to do

The AI_IMS-MED work item will focus solely on enabling AI/ML media processing as part of IMS-based services (including audio, video and AR calls) and has the following objectives in Rel-20: Extend TS 26.114 and TS 26.264 specifications to support AI/ML data delivery in IMS services, as identified in TR 26.927 clause 5.4. How it was counted: the opening sentences of the objective of the work item description /var/www/whatthespec.net/data/data/wis/1080049/SP-250878_SP-250634/SP-250878_SP-250634.md, copied word for word, read 2026-08-05. That file was taken as this work item's own because it states the unique identifier of this work plan row quote:what:AIML_IMS-MED

what FS_IMSRE_SEC set out to do

The study aims to investigate and identify enhancements on 5GS and/or IMS to support the network resiliency. The main objectives of this study include: WT1: Study the security aspects of the solutions provided in TR 29.867. How it was counted: the opening sentences of the objective of the work item description /var/www/whatthespec.net/data/data/wis/1090015/SP-251237_new_SID_Security Aspects for IMS resiliency/SP-251237_new_SID_Security Aspects for IMS resiliency.md, copied word for word, read 2026-08-05. That file was taken as this work item's own because it states the unique identifier of this work plan row quote:what:FS_IMSRE_SEC

what FS_IMSResil set out to do

The study aims to investigate and identify enhancements on 5GS and IMS to support the network resiliency. The main objectives of this study include: Study and identify IMS congestion scenarios and whether lack of coordination between UE and network exacerbates the congestion How it was counted: the opening sentences of the objective of the work item description /var/www/whatthespec.net/data/data/wis/1080002/CP-251280 was CP-251017/CP-251280 was CP-251017.md, copied word for word, read 2026-08-05. That file was taken as this work item's own because it states the unique identifier of this work plan row quote:what:FS_IMSResil

what FS_IMS_RES set out to do cited

The main objective of this work item proposal is to study the way for a more stable IMS network, by means of reducing the chance of IMS accident and enhancing the IMS restoration mechanism. This translates to the following: Create/enhance corresponding the restoration mechanism to support the normal use of voice, video and SMS services in the IMS network. How it was counted: the opening sentences of the objective of the work item description /var/www/whatthespec.net/data/data/wis/1010003/CP-232281-CP-232026/CP-232281-CP-232026.md, copied word for word, read 2026-08-05. That file was taken as this work item's own because it states the unique identifier of this work plan row quote:what:FS_IMS_RES

what FS_eIMS set out to do

This study item intends to study the feasibility of enhancing IMS network architecture as follows, How it was counted: the opening sentences of the objective of the work item description /var/www/whatthespec.net/data/data/wis/410041/SP-100360_S2-103084_eIMS_WID_update/SP-100360_S2-103084_eIMS_WID_update.md, copied word for word, read 2026-08-05. That file was taken as this work item's own because its name begins with SP-100360, the document the work plan points at quote:what:FS_eIMS

what FS_eIMS5G set out to do cited

The aim of this study is to investigate enhancements to the IMS architecture and capabilities to better address the new features and services of the 5GC system and to enhance how IMS FE’s integrate with the new network functions of 5GC. The existing IMS architecture and characteristics are the baseline from which this investigation will study, it is not expected to propose changes to the nature of the functional split and the signalling between IMS network functions – specifically SIP signalling between the UE and IMS network, and between IMS FE’s remains “as-is” with only necessary extensions (e.g. new headers) where required. How it was counted: the opening sentences of the objective of the work item description /var/www/whatthespec.net/data/data/wis/780029/SP-180736_S2-188366_revised SID 5GC IMS Enhancements/SP-180736_S2-188366_revised SID 5GC IMS Enhancements.md, copied word for word, read 2026-08-05. That file was taken as this work item's own because it states the unique identifier of this work plan row quote:what:FS_eIMS5G

what FS_eIMS5G2 set out to do cited

The aim of this study is to investigate enhancements to the IMS architecture and capabilities to better utilize the new features and services of the 5GC system and to enhance the IMS FE to integrate with the new network functions of 5GC. The existing IMS architecture and characteristics are the baseline from which this investigation will study, it is not expected to propose changes to the nature of the functional split and the signalling between IMS network functions – specifically SIP signalling between the UE and IMS network, and between IMS FE’s remains “as-is” with only necessary extensions (e.g. new headers) where required. How it was counted: the opening sentences of the objective of the work item description /var/www/whatthespec.net/data/data/wis/911032/CP-201358/CP-201358.md, copied word for word, read 2026-08-05. That file was taken as this work item's own because its name begins with CP-201358, the document the work plan points at quote:what:FS_eIMS5G2

what FS_enIMS set out to do cited

The objective of this study is to develop high-level use cases and identify the related potential requirements to enable IMS network to support new RTC services. The study will for example consider the following scenarios: large scale one to many asymmetric communication (e.g. live broadcast video service in a stadium, concert, or other events) with efficient media negotiation; How it was counted: the opening sentences of the objective of the work item description /var/www/whatthespec.net/data/data/wis/770003/SP-170703/SP-170703.md, copied word for word, read 2026-08-05. That file was taken as this work item's own because it states the unique identifier of this work plan row quote:what:FS_enIMS

what FS_enIMS_ARC set out to do cited

This study aims to introduce new capabilities in the IMS network for both existing services and potential new service requirements identified in 6G. All work tasks aim at supporting multi-vendor interoperable interfaces. How it was counted: the opening sentences of the objective of the work item description /var/www/whatthespec.net/data/data/wis/1100026/SP-251692 was SP-251656 was of SP-251638 was SP-251411_S2-2511300_was_S2-2511257_New SID on IMS architecture enhancement r02/SP-251692 was SP-251656 was of SP-251638 was SP-251411_S2-2511300_was_S2-2511257_New SID on IMS architecture enhancement r02.md, copied word for word, read 2026-08-05. That file was taken as this work item's own because it states the unique identifier of this work plan row quote:what:FS_enIMS_ARC

what IMS set out to do cited

The objective is to define concepts regarding general service requirements and service features for Release 2000, consisting of an evolved Release 99, and IM (IP Multimedia) services. IP multimedia services shall support multiple media components per call based on existing multimedia call control standards. How it was counted: the opening sentences of the objective of the work item description /var/www/whatthespec.net/data/data/wis/1273/S1-000299/S1-000299.md, copied word for word, read 2026-08-05. That file was taken as this work item's own because its own title, 'Support of IP multimedia services', shares 3 words with the work plan name; the document store has no row for S1-000299, so the address here is the plenary paper SP-000216 that carried it quote:what:IMS

what IMS-CCR-IWCS set out to do cited

The objective of this work item is to address the issue of interworking between the IM CN subsystem and CS networks, in order to support basic voice calls. How it was counted: the opening sentences of the objective of the work item description /var/www/whatthespec.net/data/data/wis/2047/NP-030292/NP-030292.md, copied word for word, read 2026-08-05. That file was taken as this work item's own because its name begins with NP-030292, the document the work plan points at quote:what:IMS-CCR-IWCS

what IMS-CODEC set out to do cited

Standardisation of default codecs for conversational packet-switched multimedia services for Release 2000 (likely to become Release 4). Identification of those additional components required for conversational packet-switched multimedia services that are the responsibility of S4, e.g. elements of protocols for transport, session and bearer control. How it was counted: the opening sentences of the objective of the work item description /var/www/whatthespec.net/data/data/wis/2036/SP-000398/SP-000398.md, copied word for word, read 2026-08-05. That file was taken as this work item's own because its name begins with SP-000398, the document the work plan points at quote:what:IMS-CODEC

what IMS-Sec set out to do cited

The objective with this WI is to study security requirements for common IMS and find solutions to meet these requirements. How it was counted: the opening sentences of the objective of the work item description /var/www/whatthespec.net/data/data/wis/370078/SP-070496_revision of_343/SP-070496_revision of_343.md, copied word for word, read 2026-08-05. That file was taken as this work item's own because its name begins with SP-070496, the document the work plan points at quote:what:IMS-Sec

what IMSDCDataOff set out to do

The objective of this work item is to define IMS Data Channel as part of the 3GPP PS Data Off Exempt Services. How it was counted: the opening sentences of the objective of the work item description /var/www/whatthespec.net/data/data/wis/990049/SP-230227/SP-230227.md, copied word for word, read 2026-08-05. That file was taken as this work item's own because it states the unique identifier of this work plan row quote:what:IMSDCDataOff

what IMSGM set out to do cited

The objectives of this work item are to define and develop support of the Group Management capability in IMS to facilitate group-enabled (multimedia) services in IMS. How it was counted: the opening sentences of the objective of the work item description /var/www/whatthespec.net/data/data/wis/31025/S1-020576/S1-020576.md, copied word for word, read 2026-08-05. That file was taken as this work item's own because its own title, 'IMS Group Management', shares 3 words with the work plan name quote:what:IMSGM

what IMSM set out to do cited

The objectives of this work item is to identify support of messaging services in the IMS by first generating a technical report, followed by the creation of a technical specification and/or change requests as appropriate. How it was counted: the opening sentences of the objective of the work item description /var/www/whatthespec.net/data/data/wis/31022/S1-020575/S1-020575.md, copied word for word, read 2026-08-05. That file was taken as this work item's own because its own title, 'IMS Messaging', shares 2 words with the work plan name quote:what:IMSM

what IMSProtoc2 set out to do cited

The areas to be considered are: 1. Ensure protocol alignment between 3GPP Stage 3 IMS work and IETF. How it was counted: the opening sentences of the objective of the work item description /var/www/whatthespec.net/data/data/wis/360029/CP-080794/CP-080794.md, copied word for word, read 2026-08-05. That file was taken as this work item's own because its name begins with CP-080794, the document the work plan points at quote:what:IMSProtoc2

what IMS_Corp set out to do cited

The objective of this work item is to provide possible IMS architectural enhancements necessary in the 3GPP system to support the access to IMS from e.g. corporate, private, residential networks. One of the scenarios required to be supported is the connection of a corporate network to the IMS, where the corporate network has an IMS subscription and the users of the corporate network are owned and managed by the corporate network. How it was counted: the opening sentences of the objective of the work item description /var/www/whatthespec.net/data/data/wis/360012/SP-080095_S2-081986_IMS_Corp_WID_Update/SP-080095_S2-081986_IMS_Corp_WID_Update.md, copied word for word, read 2026-08-05. That file was taken as this work item's own because its name begins with SP-080095, the document the work plan points at quote:what:IMS_Corp

what IMS_EMER_GPRS_EPS set out to do cited

The work item objectives are the following: Update of requirements on the support of IMS emergency calls over GERAN, UTRAN and E-UTRAN access. How it was counted: the opening sentences of the objective of the work item description /var/www/whatthespec.net/data/data/wis/380064/SP-080844/SP-080844.md, copied word for word, read 2026-08-05. That file was taken as this work item's own because its name begins with SP-080844, the document the work plan points at quote:what:IMS_EMER_GPRS_EPS

what IMS_IBCF set out to do cited

Define the necessary detailed stage 2 and stage 3 specification for Ix. More specifically, this includes: For CT3: specify the detailed stage 2 procedures (functional requirements and information flows) for Ix. How it was counted: the opening sentences of the objective of the work item description /var/www/whatthespec.net/data/data/wis/410008/CP-090019/CP-090019.md, copied word for word, read 2026-08-05. That file was taken as this work item's own because it states the unique identifier of this work plan row quote:what:IMS_IBCF

what IMS_RES-CT set out to do cited

The aim of this work item is to specify the solutions that concluded to be standardized in 3GPP TR 29.866 Clause 8 Conclusions. Specifically, the objectives include: Stage 2 objectives: CT4: Specify enhancements to IMS disaster prevention and restoration mechanism, based on the solutions that concluded to be standardized in 3GPP TR 29.866. e.g. on the following aspects: How it was counted: the opening sentences of the objective of the work item description /var/www/whatthespec.net/data/data/wis/1080001/CP-253168/CP-253168.md, copied word for word, read 2026-08-05. That file was taken as this work item's own because it states the unique identifier of this work plan row quote:what:IMS_RES-CT

what IMS_SCC set out to do cited

For SA1, the objectives include: Identification of additional IMS Centralized Services requirements How it was counted: the opening sentences of the objective of the work item description /var/www/whatthespec.net/data/data/wis/410032/SP-080633 SP-080557rev_New-IMSSSC-Nortel/SP-080633 SP-080557rev_New-IMSSSC-Nortel.md, copied word for word, read 2026-08-05. That file was taken as this work item's own because its name begins with SP-080633, the document the work plan points at quote:what:IMS_SCC

what IMS_TELEP set out to do cited

The objectives of this work item are: To specify the use cases and requirements for IMS-Based Telepresence Conference as extensions of existing IMS multi-media conference services and as applicable for different kinds of devices (mobile, fixed, etc) How it was counted: the opening sentences of the objective of the work item description /var/www/whatthespec.net/data/data/wis/530042/SP-110588/SP-110588.md, copied word for word, read 2026-08-05. That file was taken as this work item's own because its name begins with SP-110588, the document the work plan points at quote:what:IMS_TELEP

what IMS_WebRTC set out to do cited

The objective of this work item is to specify service requirements for: the ability for WebRTC clients to access IMS, including for example, reusing IMS client security credentials and/or public identities/credentials as appropriate; How it was counted: the opening sentences of the objective of the work item description /var/www/whatthespec.net/data/data/wis/580062/SP-130707_clean/SP-130707_clean.md, copied word for word, read 2026-08-05. That file was taken as this work item's own because its name begins with SP-130707, the document the work plan points at quote:what:IMS_WebRTC

what SCAS_IMS set out to do cited

The objective is to develop the Security Assurance Specification(s) (SCAS) for the IMS network product classes (Release 15): identify threats and critical assets of IMS network elements ( e.g. CSCF, ATCF, ATGW, HSS, I-BCF, MRFC and MRFP) that are not already identified in TR 33.926; How it was counted: the opening sentences of the objective of the work item description /var/www/whatthespec.net/data/data/wis/860016/SP-191128 WID_SCAS_IMS/SP-191128 WID_SCAS_IMS.md, copied word for word, read 2026-08-05. That file was taken as this work item's own because it states the unique identifier of this work plan row quote:what:SCAS_IMS

what SR_IMS set out to do cited

The Work has the following objectives: 1. Identify functional entities for IMS-based split rendering, and introduce a mapping to the IMS architecture (reuse of architectures in TS 26.264 and the IMS architecture in TS 23.228). How it was counted: the opening sentences of the objective of the work item description /var/www/whatthespec.net/data/data/wis/1030003/SP-240492 - revision of SP-240061 New WID on Split Rendering over IMS (SR_IMS)/SP-240492 - revision of SP-240061 New WID on Split Rendering over IMS (SR_IMS).md, copied word for word, read 2026-08-05. That file was taken as this work item's own because it states the unique identifier of this work plan row quote:what:SR_IMS

what eIMS5G_SBA set out to do cited

The objectives of this Rel-16 SA2 normative work are to implement the service-based architecture conclusions of the FS_eIMS5G study contained in clauses 8.1, 8.2, and 8.3 of TR 23.794; this work will: Define new services for the IMS service logic performed by the HSS portion of the UDM/HSS (identified as Nhss), including the handling of “transparent Sh data”. How it was counted: the opening sentences of the objective of the work item description /var/www/whatthespec.net/data/data/wis/840062/SP-190181_S2-1902837_eIMS5G_SBA WID/SP-190181_S2-1902837_eIMS5G_SBA WID.md, copied word for word, read 2026-08-05. That file was taken as this work item's own because its name begins with SP-190181, the document the work plan points at quote:what:eIMS5G_SBA

what eIMS_RP set out to do cited

The objective of this work item is to complete the IMS restoration procedures which were studied in TR 23.820. The work is will be based on the content from 3GPP TS 23.380 and TR 23.820. How it was counted: the opening sentences of the objective of the work item description /var/www/whatthespec.net/data/data/wis/440017/CP-091050-WID-IMS-Restoration/CP-091050-WID-IMS-Restoration.md, copied word for word, read 2026-08-05. That file was taken as this work item's own because its name begins with CP-091050, the document the work plan points at quote:what:eIMS_RP

what enIMS set out to do cited

The objective of this work item is to develop system level requirements for IMS, MC and GCSE services to support new RTC services. This work will consider the potential requirements identified in TR 22.823 and use that as the basis for developing the stage 1 normative requirements with focus on system enhancements. How it was counted: the opening sentences of the objective of the work item description /var/www/whatthespec.net/data/data/wis/790003/SP-180137/SP-180137.md, copied word for word, read 2026-08-05. That file was taken as this work item's own because it states the unique identifier of this work plan row quote:what:enIMS

why 5GS_Ph1-IMSo5G was proposed cited

Voice services including emergency call are basic services provided by operators, which should be supported in the initial deployment of next generation system (5G). During the SA2 discussion it was agreed that the voice services should still be provided by IMS network and the 5GC provides a new type of IP-CAN for the UE to access IMS. How it was counted: the opening sentences of the justification of the work item description /var/www/whatthespec.net/data/data/wis/760029/CP-180094/CP-180094.md, copied word for word, read 2026-08-05. That file was taken as this work item's own because it states the unique identifier of this work plan row quote:why:5GS_Ph1-IMSo5G

why AIML_IMS-MED was proposed cited

The use of AI/ML for media processing is now common in many different consumer applications, applicable not only to specific user devices (e.g. immersive headsets, mobile phones), but also to a variety of different media services. Whilst AI/ML processing is commonly supported for non-real time services such as consumer picture enhancement or video editing, there is a market need from operators to support AI/ML for media processing in real-time communication services such that new enhanced services can be provided; examples being real-time translation, speech-to-text and text-to-speech applications, object detection, tracking and/or segmentation based computer vision services. How it was counted: the opening sentences of the justification of the work item description /var/www/whatthespec.net/data/data/wis/1080049/SP-250878_SP-250634/SP-250878_SP-250634.md, copied word for word, read 2026-08-05. That file was taken as this work item's own because it states the unique identifier of this work plan row quote:why:AIML_IMS-MED

why FS_IMSRE_SEC was proposed cited

When a major network error occurs, e.g. a router fault in the transport network, SIP registration requests are dropped, triggering massive retransmissions that congested IMS and then nationwide IMS. As IMS couldn’t process, the congestion spread to the PCF as UEs’ retransmissions. How it was counted: the opening sentences of the justification of the work item description /var/www/whatthespec.net/data/data/wis/1090015/SP-251237_new_SID_Security Aspects for IMS resiliency/SP-251237_new_SID_Security Aspects for IMS resiliency.md, copied word for word, read 2026-08-05. That file was taken as this work item's own because it states the unique identifier of this work plan row quote:why:FS_IMSRE_SEC

why FS_IMSResil was proposed cited

If IMS encounters a failure and cannot send a response to UE, the UE will not receive the expected response and will subsequently initiate the SIP Registration procedure with the IMS. If the UE repeatedly sends SIP Registration requests, the IMS transactions increases, leading to congestion and making failure recovery difficult. How it was counted: the opening sentences of the justification of the work item description /var/www/whatthespec.net/data/data/wis/1080002/CP-251280 was CP-251017/CP-251280 was CP-251017.md, copied word for word, read 2026-08-05. That file was taken as this work item's own because it states the unique identifier of this work plan row quote:why:FS_IMSResil

why FS_IMS_RES was proposed cited

In the past few years, IMS-related / IMS-affected communication accidents happen on different operators’ mobile network occasionally. These accidents affected voice, video and SMS services for millions of people, and caused serious impacts on the finance, aviation, logistics, automobile, electric power and other industries. How it was counted: the opening sentences of the justification of the work item description /var/www/whatthespec.net/data/data/wis/1010003/CP-232281-CP-232026/CP-232281-CP-232026.md, copied word for word, read 2026-08-05. That file was taken as this work item's own because it states the unique identifier of this work plan row quote:why:FS_IMS_RES

why FS_eIMS was proposed cited

IMS architecture has laid a solid foundation for rolling out all kinds of multimedia services, however we found out there is still some room for improvement in IMS architecture, for example, how to make IMS network simpler, more robust, more intelligent and therefore easier to operate and maintain. How it was counted: the opening sentences of the justification of the work item description /var/www/whatthespec.net/data/data/wis/410041/SP-100360_S2-103084_eIMS_WID_update/SP-100360_S2-103084_eIMS_WID_update.md, copied word for word, read 2026-08-05. That file was taken as this work item's own because its name begins with SP-100360, the document the work plan points at quote:why:FS_eIMS

why FS_eIMS5G was proposed cited

During the normative work on defining the 5GC network some aspects of interworking existing IMS architectures with the 5GC were considered; however, the scope was intentionally limited to avoid major IMS re-specification that might delay initial 5GC specification. This limit on scope has enabled the basic services offered by IMS today (e.g. How it was counted: the opening sentences of the justification of the work item description /var/www/whatthespec.net/data/data/wis/780029/SP-180736_S2-188366_revised SID 5GC IMS Enhancements/SP-180736_S2-188366_revised SID 5GC IMS Enhancements.md, copied word for word, read 2026-08-05. That file was taken as this work item's own because it states the unique identifier of this work plan row quote:why:FS_eIMS5G

why FS_eIMS5G2 was proposed cited

The related Rel-16 SA2 study (FS_eIMS5G, ) has reached conclusions on the service-based architecture interactions between IMS and the 5GC. While other aspects of the study have not been concluded, the investigations related to key issues #1, #2, #3 and #8 were not finalized and no solutions were agreed for those key issues. How it was counted: the opening sentences of the justification of the work item description /var/www/whatthespec.net/data/data/wis/911032/CP-201358/CP-201358.md, copied word for word, read 2026-08-05. That file was taken as this work item's own because its name begins with CP-201358, the document the work plan points at quote:why:FS_eIMS5G2

why FS_enIMS was proposed

The 3GPP network operators are striving to accommodate continuously fast increasing data traffic demand resulting from the support of existing real time services such as internet access, voice, and multimedia communication. In addition, new services such as instantaneous interaction among Things & People are emerging. How it was counted: the opening sentences of the justification of the work item description /var/www/whatthespec.net/data/data/wis/770003/SP-170703/SP-170703.md, copied word for word, read 2026-08-05. That file was taken as this work item's own because it states the unique identifier of this work plan row quote:why:FS_enIMS

why FS_enIMS_ARC was proposed cited

Empowered by the rapid development of advanced technologies such as Generative Artificial Intelligence (Gen AI), Large Language Models (LLMs) and AI Agent, and with emerging new types of terminals such as AI glasses and embodied robots, operators will be able to provide various personalized and enriched communication services. 3GPP SA1 has started the FS_6G_REQ study item to identify use cases and service/operational requirements for new multi-media services. How it was counted: the opening sentences of the justification of the work item description /var/www/whatthespec.net/data/data/wis/1100026/SP-251692 was SP-251656 was of SP-251638 was SP-251411_S2-2511300_was_S2-2511257_New SID on IMS architecture enhancement r02/SP-251692 was SP-251656 was of SP-251638 was SP-251411_S2-2511300_was_S2-2511257_New SID on IMS architecture enhancement r02.md, copied word for word, read 2026-08-05. That file was taken as this work item's own because it states the unique identifier of this work plan row quote:why:FS_enIMS_ARC

why IMS was proposed cited

The work item describes the work to be done – from a services point of view – on R00 IP Multimedia service requirements. How it was counted: the opening sentences of the justification of the work item description /var/www/whatthespec.net/data/data/wis/1273/S1-000299/S1-000299.md, copied word for word, read 2026-08-05. That file was taken as this work item's own because its own title, 'Support of IP multimedia services', shares 3 words with the work plan name; the document store has no row for S1-000299, so the address here is the plenary paper SP-000216 that carried it quote:why:IMS

why IMS-CCR-IWCS was proposed cited

Within UMTS, the capability of IP-based multimedia (IM) services will enable the support of basic voice calls to and from circuit switched (CS) networks (i.e. PSTN, ISDN and GSM/UMTS CS networks). How it was counted: the opening sentences of the justification of the work item description /var/www/whatthespec.net/data/data/wis/2047/NP-030292/NP-030292.md, copied word for word, read 2026-08-05. That file was taken as this work item's own because its name begins with NP-030292, the document the work plan points at quote:why:IMS-CCR-IWCS

why IMS-CODEC was proposed cited

Conversational services will form an important component of the packet-switched multimedia services offered by 3G systems (e.g. UTRAN, GERAN). How it was counted: the opening sentences of the justification of the work item description /var/www/whatthespec.net/data/data/wis/2036/SP-000398/SP-000398.md, copied word for word, read 2026-08-05. That file was taken as this work item's own because its name begins with SP-000398, the document the work plan points at quote:why:IMS-CODEC

why IMS-Sec was proposed

As part of common IMS, new security requirements on IMS are identified. 3GPP SA3 needs to study how to extend the existing IMS security architecture to meet the new security requirements. How it was counted: the opening sentences of the justification of the work item description /var/www/whatthespec.net/data/data/wis/370078/SP-070496_revision of_343/SP-070496_revision of_343.md, copied word for word, read 2026-08-05. That file was taken as this work item's own because its name begins with SP-070496, the document the work plan points at quote:why:IMS-Sec

why IMSDCDataOff was proposed

The LS(S2-2301827) from SA2 proposes that SA1 could investigate whether IMS data channel should be considered as a feature to be exempted when PS Data Off is activated. By adding IMS data channel to the list of 3GPP PS Data Off Exempt Services, operators can configure whether the IMS data channel will still be enabled when the user set the UE to PS Data Off. How it was counted: the opening sentences of the justification of the work item description /var/www/whatthespec.net/data/data/wis/990049/SP-230227/SP-230227.md, copied word for word, read 2026-08-05. That file was taken as this work item's own because it states the unique identifier of this work plan row quote:why:IMSDCDataOff

why IMSGM was proposed cited

This WID covers the new Group Management capability based on the IMS architecture as part of the Release 6 timeframe. By combining this Group Management capability with other IMS Service capabilities, such as Presence and Messaging, new rich and enhanced services for the end users can be created. How it was counted: the opening sentences of the justification of the work item description /var/www/whatthespec.net/data/data/wis/31025/S1-020576/S1-020576.md, copied word for word, read 2026-08-05. That file was taken as this work item's own because its own title, 'IMS Group Management', shares 3 words with the work plan name quote:why:IMSGM

why IMSM was proposed cited

This WID covers the support of messaging in the IMS as part of the Release 6 timeframe. By combining the support of messaging with other IMS service capabilities, such as Presence, new rich and enhanced messaging services for the end users can be created. How it was counted: the opening sentences of the justification of the work item description /var/www/whatthespec.net/data/data/wis/31022/S1-020575/S1-020575.md, copied word for word, read 2026-08-05. That file was taken as this work item's own because its own title, 'IMS Messaging', shares 2 words with the work plan name quote:why:IMSM

why IMSProtoc2 was proposed cited

In Release 5, the IMS was defined to support IP Multimedia services. The feature set in Release 5 provides a basis for IP Multimedia support. How it was counted: the opening sentences of the justification of the work item description /var/www/whatthespec.net/data/data/wis/360029/CP-080794/CP-080794.md, copied word for word, read 2026-08-05. That file was taken as this work item's own because its name begins with CP-080794, the document the work plan points at quote:why:IMSProtoc2

why IMSProtoc20-CT was proposed cited

In Release 5, the IMS was defined to support IP Multimedia services. The feature set in Release 5 provided a basis for IP Multimedia support. How it was counted: the opening sentences of the justification of the work item description /var/www/whatthespec.net/data/data/wis/1110010/CP-260044/CP-260044.md, copied word for word, read 2026-08-05. That file was taken as this work item's own because it states the unique identifier of this work plan row quote:why:IMSProtoc20-CT

why IMS_Corp was proposed

The standardization of fixed broadband access to IMS is addressed by a number of SDOs, e.g. ETSI and ITU-T in the framework of next generation networking (NGN). How it was counted: the opening sentences of the justification of the work item description /var/www/whatthespec.net/data/data/wis/360012/SP-080095_S2-081986_IMS_Corp_WID_Update/SP-080095_S2-081986_IMS_Corp_WID_Update.md, copied word for word, read 2026-08-05. That file was taken as this work item's own because its name begins with SP-080095, the document the work plan points at quote:why:IMS_Corp

why IMS_EMER_GPRS_EPS was proposed cited

To prepare for meeting regional regulatory requirements for PS based emergency calls, and to remain competitive with other wireless PS technologies (e.g., WLAN and cdma2000), functionality is needed to establish an emergency session in PS mode via GPRS access and the IM CN subsystem.. How it was counted: the opening sentences of the justification of the work item description /var/www/whatthespec.net/data/data/wis/380064/SP-080844/SP-080844.md, copied word for word, read 2026-08-05. That file was taken as this work item's own because its name begins with SP-080844, the document the work plan points at quote:why:IMS_EMER_GPRS_EPS

why IMS_IBCF was proposed

TS 23.228 defines the Ix reference point and provides stage 2 information. Interface Ix is used for control of the IMS Transition Gateway (TrGW). How it was counted: the opening sentences of the justification of the work item description /var/www/whatthespec.net/data/data/wis/410008/CP-090019/CP-090019.md, copied word for word, read 2026-08-05. That file was taken as this work item's own because it states the unique identifier of this work plan row quote:why:IMS_IBCF

why IMS_RES-CT was proposed

In the past few years, IMS-related / IMS-affected communication accidents have happened occasionally on different operators’ mobile network. These accidents affected voice, video and SMS services of millions of people, and had serious impacts on areas such as the finance, aviation, logistics, automobile, electric power and so on. How it was counted: the opening sentences of the justification of the work item description /var/www/whatthespec.net/data/data/wis/1080001/CP-253168/CP-253168.md, copied word for word, read 2026-08-05. That file was taken as this work item's own because it states the unique identifier of this work plan row quote:why:IMS_RES-CT

why IMS_SCC was proposed cited

In Release 8 3GPP has worked on the specification of the IMS Centralized Services (ICS) and of the IMS Service Continuity (IMS_Cont). These two functionalities allow the IMS to control the service delivery as well as enable services to progress over heterogeneous networks. How it was counted: the opening sentences of the justification of the work item description /var/www/whatthespec.net/data/data/wis/410032/SP-080633 SP-080557rev_New-IMSSSC-Nortel/SP-080633 SP-080557rev_New-IMSSSC-Nortel.md, copied word for word, read 2026-08-05. That file was taken as this work item's own because its name begins with SP-080633, the document the work plan points at quote:why:IMS_SCC

why IMS_TELEP was proposed cited

The Telepresence Conference allows the participants to envoy a strong sense of realism and presence between all participants in remote conference rooms (called Telepresence rooms). How it was counted: the opening sentences of the justification of the work item description /var/www/whatthespec.net/data/data/wis/530042/SP-110588/SP-110588.md, copied word for word, read 2026-08-05. That file was taken as this work item's own because its name begins with SP-110588, the document the work plan points at quote:why:IMS_TELEP

why IMS_WebRTC was proposed cited

The RTCWEB group in the IETF and the WEBRTC group in W3C are specifying a browser based client to support communication services. The work may be summarised as in this extract from the IETF RTCWEB charter: There are a number of proprietary implementations that provide direct interactive rich communication using audio, video, collaboration, games, etc. between two peers' web-browsers. How it was counted: the opening sentences of the justification of the work item description /var/www/whatthespec.net/data/data/wis/580062/SP-130707_clean/SP-130707_clean.md, copied word for word, read 2026-08-05. That file was taken as this work item's own because its name begins with SP-130707, the document the work plan points at quote:why:IMS_WebRTC

why SCAS_IMS was proposed cited

Significant progress has been made to security assurance specification for LTE, such as MME, AMF, etc. However, the network elements of IP Multimedia Core Network Subsystem (IMS) that was designed for LTE for Multimedia service (e.g. voice) is not within the scope of these specified security assurance specification. How it was counted: the opening sentences of the justification of the work item description /var/www/whatthespec.net/data/data/wis/860016/SP-191128 WID_SCAS_IMS/SP-191128 WID_SCAS_IMS.md, copied word for word, read 2026-08-05. That file was taken as this work item's own because it states the unique identifier of this work plan row quote:why:SCAS_IMS

why SR_IMS was proposed cited

In Rel-18 SA4 will complete a work item on split rendering Media Service Enabler (SR_MSE) that provides split rendering functionalities for UEs over the Generic RTC architecture in TS 26.506 using WebRTC for delivery of rendered media. Simultaneously, workflows for split rendering over the IMS for conversational AR were specified as part of the IBACS work item during Rel-18. How it was counted: the opening sentences of the justification of the work item description /var/www/whatthespec.net/data/data/wis/1030003/SP-240492 - revision of SP-240061 New WID on Split Rendering over IMS (SR_IMS)/SP-240492 - revision of SP-240061 New WID on Split Rendering over IMS (SR_IMS).md, copied word for word, read 2026-08-05. That file was taken as this work item's own because it states the unique identifier of this work plan row quote:why:SR_IMS

why eIMS5G_SBA was proposed cited

The related SA2 study (FS_eIMS5G) has reached conclusions on the service-based architecture interactions between IMS and the 5GC. While other aspects of the study have not been concluded, the service-based aspects can be implemented without dependency on the outstanding study items. How it was counted: the opening sentences of the justification of the work item description /var/www/whatthespec.net/data/data/wis/840062/SP-190181_S2-1902837_eIMS5G_SBA WID/SP-190181_S2-1902837_eIMS5G_SBA WID.md, copied word for word, read 2026-08-05. That file was taken as this work item's own because its name begins with SP-190181, the document the work plan points at quote:why:eIMS5G_SBA

why eIMS_RP was proposed cited

During Rel-8 timeframe, IMS restoration procedures were developed specified in 3GPP TS 23.380 covering S-CSCF service interruption. However, there are features, in particular P-CSCF restoration procedures, included in the a study (3GPP TR 23.820) that were not finalized in the timeframe of Rel-8 and therefore not covered in 3GPP TS 23.380. How it was counted: the opening sentences of the justification of the work item description /var/www/whatthespec.net/data/data/wis/440017/CP-091050-WID-IMS-Restoration/CP-091050-WID-IMS-Restoration.md, copied word for word, read 2026-08-05. That file was taken as this work item's own because its name begins with CP-091050, the document the work plan points at quote:why:eIMS_RP

Meeting 39

C1-111 cited

3GPPCT1#111 How it was counted: row of table `meeting` in /var/www/whatthespec.net/data/database/api/meeting_resolve.sqlite where the code is 'C1-111', and the days and place from table `meetings` in /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite for event 19602, read 2026-08-05 meeting:C1-111

C1-112 cited

3GPPCT1#112 How it was counted: row of table `meeting` in /var/www/whatthespec.net/data/database/api/meeting_resolve.sqlite where the code is 'C1-112', and the days and place from table `meetings` in /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite for event 19604, read 2026-08-05 meeting:C1-112

C1-162 cited

3GPPCT1#162 How it was counted: row of table `meeting` in /var/www/whatthespec.net/data/database/api/meeting_resolve.sqlite where the code is 'C1-162', and the days and place from table `meetings` in /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite for event 60741, read 2026-08-05; the registration count from /var/www/whatthespec.net/data/database/api/participants.sqlite meeting:C1-162

C1-90 cited

3GPPCT1#90 How it was counted: row of table `meeting` in /var/www/whatthespec.net/data/database/api/meeting_resolve.sqlite where the code is 'C1-90', and the days and place from table `meetings` in /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite for event 31324, read 2026-08-05 meeting:C1-90

C1-91 cited

3GPPCT1#91 How it was counted: row of table `meeting` in /var/www/whatthespec.net/data/database/api/meeting_resolve.sqlite where the code is 'C1-91', and the days and place from table `meetings` in /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite for event 31325, read 2026-08-05 meeting:C1-91

C1-92 cited

3GPPCT1#92 How it was counted: row of table `meeting` in /var/www/whatthespec.net/data/database/api/meeting_resolve.sqlite where the code is 'C1-92', and the days and place from table `meetings` in /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite for event 31326, read 2026-08-05 meeting:C1-92

C1-95 cited

3GPPCT1#95 How it was counted: row of table `meeting` in /var/www/whatthespec.net/data/database/api/meeting_resolve.sqlite where the code is 'C1-95', and the days and place from table `meetings` in /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite for event 31329, read 2026-08-05 meeting:C1-95

C4-68 cited

3GPPCT4#68 How it was counted: row of table `meeting` in /var/www/whatthespec.net/data/database/api/meeting_resolve.sqlite where the code is 'C4-68', and the days and place from table `meetings` in /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite for event 31336, read 2026-08-05 meeting:C4-68

CP-101

3GPPCT#101 How it was counted: row of table `meeting` in /var/www/whatthespec.net/data/database/api/meeting_resolve.sqlite where the code is 'CP-101', and the days and place from table `meetings` in /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite for event 41043, read 2026-08-05 meeting:CP-101

CP-110 cited

3GPPCT#110 How it was counted: row of table `meeting` in /var/www/whatthespec.net/data/database/api/meeting_resolve.sqlite where the code is 'CP-110', and the days and place from table `meetings` in /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite for event 60581, read 2026-08-05; the registration count from /var/www/whatthespec.net/data/database/api/participants.sqlite meeting:CP-110

CP-111 cited

3GPPCT#111 How it was counted: row of table `meeting` in /var/www/whatthespec.net/data/database/api/meeting_resolve.sqlite where the code is 'CP-111', and the days and place from table `meetings` in /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite for event 60792, read 2026-08-05; the registration count from /var/www/whatthespec.net/data/database/api/participants.sqlite meeting:CP-111

CP-112 cited

3GPPCT#112 How it was counted: row of table `meeting` in /var/www/whatthespec.net/data/database/api/meeting_resolve.sqlite where the code is 'CP-112', and the days and place from table `meetings` in /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite for event 60795, read 2026-08-05; the registration count from /var/www/whatthespec.net/data/database/api/participants.sqlite meeting:CP-112

CP-42

3GPPCT#42 How it was counted: row of table `meeting` in /var/www/whatthespec.net/data/database/api/meeting_resolve.sqlite where the code is 'CP-42', and the days and place from table `meetings` in /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite for event 25896, read 2026-08-05 meeting:CP-42

CP-43

3GPPCT#43 How it was counted: row of table `meeting` in /var/www/whatthespec.net/data/database/api/meeting_resolve.sqlite where the code is 'CP-43', and the days and place from table `meetings` in /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite for event 26392, read 2026-08-05 meeting:CP-43

CP-46

3GPPCT#46 How it was counted: row of table `meeting` in /var/www/whatthespec.net/data/database/api/meeting_resolve.sqlite where the code is 'CP-46', and the days and place from table `meetings` in /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite for event 26395, read 2026-08-05 meeting:CP-46

CP-52

3GPPCT#52 How it was counted: row of table `meeting` in /var/www/whatthespec.net/data/database/api/meeting_resolve.sqlite where the code is 'CP-52', and the days and place from table `meetings` in /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite for event 28177, read 2026-08-05 meeting:CP-52

CP-58

3GPPCT#58 How it was counted: row of table `meeting` in /var/www/whatthespec.net/data/database/api/meeting_resolve.sqlite where the code is 'CP-58', and the days and place from table `meetings` in /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite for event 28539, read 2026-08-05 meeting:CP-58

CP-66

3GPPCT#66 How it was counted: row of table `meeting` in /var/www/whatthespec.net/data/database/api/meeting_resolve.sqlite where the code is 'CP-66', and the days and place from table `meetings` in /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite for event 30571, read 2026-08-05 meeting:CP-66

CP-72

3GPPCT#72 How it was counted: row of table `meeting` in /var/www/whatthespec.net/data/database/api/meeting_resolve.sqlite where the code is 'CP-72', and the days and place from table `meetings` in /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite for event 31642, read 2026-08-05 meeting:CP-72

CP-79

3GPPCT#79 How it was counted: row of table `meeting` in /var/www/whatthespec.net/data/database/api/meeting_resolve.sqlite where the code is 'CP-79', and the days and place from table `meetings` in /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite for event 18660, read 2026-08-05 meeting:CP-79

CP-88-e

3GPPCT#88-e How it was counted: row of table `meeting` in /var/www/whatthespec.net/data/database/api/meeting_resolve.sqlite where the code is 'CP-88-e', and the days and place from table `meetings` in /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite for event 38122, read 2026-08-05 meeting:CP-88-e

SP-103

3GPPSA#103 How it was counted: row of table `meeting` in /var/www/whatthespec.net/data/database/api/meeting_resolve.sqlite where the code is 'SP-103', and the days and place from table `meetings` in /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite for event 60295, read 2026-08-05; the registration count from /var/www/whatthespec.net/data/database/api/participants.sqlite meeting:SP-103

SP-108 cited

3GPPSA#108 How it was counted: row of table `meeting` in /var/www/whatthespec.net/data/database/api/meeting_resolve.sqlite where the code is 'SP-108', and the days and place from table `meetings` in /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite for event 60577, read 2026-08-05; the registration count from /var/www/whatthespec.net/data/database/api/participants.sqlite meeting:SP-108

SP-109

3GPPSA#109 How it was counted: row of table `meeting` in /var/www/whatthespec.net/data/database/api/meeting_resolve.sqlite where the code is 'SP-109', and the days and place from table `meetings` in /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite for event 60580, read 2026-08-05; the registration count from /var/www/whatthespec.net/data/database/api/participants.sqlite meeting:SP-109

SP-112 cited

3GPPSA#112 How it was counted: row of table `meeting` in /var/www/whatthespec.net/data/database/api/meeting_resolve.sqlite where the code is 'SP-112', and the days and place from table `meetings` in /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite for event 60797, read 2026-08-05; the registration count from /var/www/whatthespec.net/data/database/api/participants.sqlite meeting:SP-112

SP-36

3GPPSA#36 How it was counted: row of table `meeting` in /var/www/whatthespec.net/data/database/api/meeting_resolve.sqlite where the code is 'SP-36', and the days and place from table `meetings` in /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite for event 25057, read 2026-08-05 meeting:SP-36

SP-39

3GPPSA#39 How it was counted: row of table `meeting` in /var/www/whatthespec.net/data/database/api/meeting_resolve.sqlite where the code is 'SP-39', and the days and place from table `meetings` in /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite for event 25897, read 2026-08-05 meeting:SP-39

SP-41

3GPPSA#41 How it was counted: row of table `meeting` in /var/www/whatthespec.net/data/database/api/meeting_resolve.sqlite where the code is 'SP-41', and the days and place from table `meetings` in /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite for event 25899, read 2026-08-05 meeting:SP-41

SP-42

3GPPSA#42 How it was counted: row of table `meeting` in /var/www/whatthespec.net/data/database/api/meeting_resolve.sqlite where the code is 'SP-42', and the days and place from table `meetings` in /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite for event 25900, read 2026-08-05 meeting:SP-42

SP-48

3GPPSA#48 How it was counted: row of table `meeting` in /var/www/whatthespec.net/data/database/api/meeting_resolve.sqlite where the code is 'SP-48', and the days and place from table `meetings` in /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite for event 27023, read 2026-08-05 meeting:SP-48

SP-53

3GPPSA#53 How it was counted: row of table `meeting` in /var/www/whatthespec.net/data/database/api/meeting_resolve.sqlite where the code is 'SP-53', and the days and place from table `meetings` in /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite for event 28183, read 2026-08-05 meeting:SP-53

SP-58

3GPPSA#58 How it was counted: row of table `meeting` in /var/www/whatthespec.net/data/database/api/meeting_resolve.sqlite where the code is 'SP-58', and the days and place from table `meetings` in /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite for event 28527, read 2026-08-05 meeting:SP-58

SP-62

3GPPSA#62 How it was counted: row of table `meeting` in /var/www/whatthespec.net/data/database/api/meeting_resolve.sqlite where the code is 'SP-62', and the days and place from table `meetings` in /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite for event 29581, read 2026-08-05 meeting:SP-62

SP-77

3GPPSA#77 How it was counted: row of table `meeting` in /var/www/whatthespec.net/data/database/api/meeting_resolve.sqlite where the code is 'SP-77', and the days and place from table `meetings` in /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite for event 31947, read 2026-08-05 meeting:SP-77

SP-79

3GPPSA#79 How it was counted: row of table `meeting` in /var/www/whatthespec.net/data/database/api/meeting_resolve.sqlite where the code is 'SP-79', and the days and place from table `meetings` in /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite for event 18661, read 2026-08-05 meeting:SP-79

SP-81

3GPPSA#81 How it was counted: row of table `meeting` in /var/www/whatthespec.net/data/database/api/meeting_resolve.sqlite where the code is 'SP-81', and the days and place from table `meetings` in /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite for event 18667, read 2026-08-05 meeting:SP-81

SP-83

3GPPSA#83 How it was counted: row of table `meeting` in /var/www/whatthespec.net/data/database/api/meeting_resolve.sqlite where the code is 'SP-83', and the days and place from table `meetings` in /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite for event 19637, read 2026-08-05 meeting:SP-83

SP-86

3GPPSA#86 How it was counted: row of table `meeting` in /var/www/whatthespec.net/data/database/api/meeting_resolve.sqlite where the code is 'SP-86', and the days and place from table `meetings` in /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite for event 19646, read 2026-08-05 meeting:SP-86

SP-99

3GPPSA#99 How it was counted: row of table `meeting` in /var/www/whatthespec.net/data/database/api/meeting_resolve.sqlite where the code is 'SP-99', and the days and place from table `meetings` in /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite for event 60009, read 2026-08-05 meeting:SP-99

Working group 14

CT1 cited

CT1 — Mobility, call control, session management (WG1_mm-cc-sm_ex-CN1) How it was counted: documents whose work item acronym is one of the 177 IMS acronyms and whose meeting code begins C1-, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05; the printed name from /var/www/whatthespec.net/pygppe/site/shared/groups_catalog.php and /var/www/whatthespec.net/data/database/api/wts3.sqlite group:C1

CT3 cited

CT3 — Interworking with external networks (WG3_interworking_ex-CN3) How it was counted: documents whose work item acronym is one of the 177 IMS acronyms and whose meeting code begins C3-, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05; the printed name from /var/www/whatthespec.net/pygppe/site/shared/groups_catalog.php and /var/www/whatthespec.net/data/database/api/wts3.sqlite group:C3

CT4 cited

CT4 — Core network protocols (WG4_protocollars_ex-CN4) How it was counted: documents whose work item acronym is one of the 177 IMS acronyms and whose meeting code begins C4-, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05; the printed name from /var/www/whatthespec.net/pygppe/site/shared/groups_catalog.php and /var/www/whatthespec.net/data/database/api/wts3.sqlite group:C4

CT6 cited

CT6 — Smart card application aspects (WG6_Smartcard_Ex-T3) How it was counted: documents whose work item acronym is one of the 177 IMS acronyms and whose meeting code begins C6-, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05; the printed name from /var/www/whatthespec.net/pygppe/site/shared/groups_catalog.php and /var/www/whatthespec.net/data/database/api/wts3.sqlite group:C6

CT cited

TSG CT (plenary) How it was counted: documents whose work item acronym is one of the 177 IMS acronyms and whose meeting code begins CP-, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05; the printed name from /var/www/whatthespec.net/pygppe/site/shared/groups_catalog.php and /var/www/whatthespec.net/data/database/api/wts3.sqlite group:CP

RAN2 cited

RAN2 — Layer 2/3 (WG2_RL2) How it was counted: documents whose work item acronym is one of the 177 IMS acronyms and whose meeting code begins R2-, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05; the printed name from /var/www/whatthespec.net/pygppe/site/shared/groups_catalog.php and /var/www/whatthespec.net/data/database/api/wts3.sqlite group:R2

RAN5 cited

RAN5 — Mobile Terminal Conformance Testing (WG5_Test_ex-T1) How it was counted: documents whose work item acronym is one of the 177 IMS acronyms and whose meeting code begins R5-, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05; the printed name from /var/www/whatthespec.net/pygppe/site/shared/groups_catalog.php and /var/www/whatthespec.net/data/database/api/wts3.sqlite group:R5

RAN cited

TSG RAN (plenary) How it was counted: documents whose work item acronym is one of the 177 IMS acronyms and whose meeting code begins RP-, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05; the printed name from /var/www/whatthespec.net/pygppe/site/shared/groups_catalog.php and /var/www/whatthespec.net/data/database/api/wts3.sqlite group:RP

SA1 cited

SA1 — Services (WG1_Serv) How it was counted: documents whose work item acronym is one of the 177 IMS acronyms and whose meeting code begins S1-, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05; the printed name from /var/www/whatthespec.net/pygppe/site/shared/groups_catalog.php and /var/www/whatthespec.net/data/database/api/wts3.sqlite group:S1

SA2 cited

SA2 — Architecture (WG2_Arch) — preserved, do not change defaults How it was counted: documents whose work item acronym is one of the 177 IMS acronyms and whose meeting code begins S2-, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05; the printed name from /var/www/whatthespec.net/pygppe/site/shared/groups_catalog.php and /var/www/whatthespec.net/data/database/api/wts3.sqlite group:S2

SA3 cited

SA3 — Security (WG3_Security) How it was counted: documents whose work item acronym is one of the 177 IMS acronyms and whose meeting code begins S3-, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05; the printed name from /var/www/whatthespec.net/pygppe/site/shared/groups_catalog.php and /var/www/whatthespec.net/data/database/api/wts3.sqlite group:S3

SA4 cited

SA4 — Codec (WG4_CODEC) How it was counted: documents whose work item acronym is one of the 177 IMS acronyms and whose meeting code begins S4-, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05; the printed name from /var/www/whatthespec.net/pygppe/site/shared/groups_catalog.php and /var/www/whatthespec.net/data/database/api/wts3.sqlite group:S4

SA5 cited

SA5 — Telecom Management (WG5_TM) How it was counted: documents whose work item acronym is one of the 177 IMS acronyms and whose meeting code begins S5-, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05; the printed name from /var/www/whatthespec.net/pygppe/site/shared/groups_catalog.php and /var/www/whatthespec.net/data/database/api/wts3.sqlite group:S5

SA cited

TSG SA (plenary) How it was counted: documents whose work item acronym is one of the 177 IMS acronyms and whose meeting code begins SP-, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05; the printed name from /var/www/whatthespec.net/pygppe/site/shared/groups_catalog.php and /var/www/whatthespec.net/data/database/api/wts3.sqlite group:SP

Nothing here matches that. Try a shorter word.