Description
Customized Alerting Tone (CAT), also known as personalized ringback tone, is a service that lets a called subscriber replace the standard ringback tone heard by the calling party with a personalized audio or multimedia content. CAT Inter-working, formally defined as Multiple Domains Inter-working in 3GPP TS 22.182 and TS 22.982, addresses the challenge of delivering this service consistently when the calling and called parties are attached to different network domains or different Public Land Mobile Networks (PLMNs).
The service architecture distinguishes between the CS domain and the IMS subsystem. In the CS domain, CAT is typically realized through an Intelligent Network (IN) approach using CAMEL (Customized Applications for Mobile network Enhanced Logic) service logic, where the gsmSCF and specialized resources such as the IP Multimedia Subsystem Media Resource Function or an IN-based tone server play the alerting content toward the calling party. In IMS, CAT is implemented using SIP-based application servers (the CAT AS) that act as a terminating application, intercepting the session setup and playing the customized tone through the MRF before the final 200 OK is delivered to the caller.
Multiple Domains Inter-working defines the requirements and procedures that allow a CAT service to function when the originating and terminating sides reside in different domains. For example, a caller on a CS network may call a subscriber whose CAT service is hosted in IMS, or vice versa. The interworking function must ensure that the customized alerting content is played to the caller, that charging is correctly attributed, and that the service experience is preserved end-to-end. This involves coordination between the CS core (MSC/VLR, GMSC), the IMS core (CSCF, AS), and the underlying bearer and signalling paths.
Inter-PLMN interworking extends the concept further: when the called subscriber roams or is served by a different operator, the home operator's CAT service must still be invoked. This relies on CAMEL subscription information being transferred to the visited network and on the home network's service control points being reachable. For IMS, the home S-CSCF anchors the session and routes it to the home CAT AS, ensuring the service is applied regardless of the visited network.
Key components include the CAT application server or SCP, the media resource function that stores and plays the alerting content, the call session control functions in IMS, and the CAMEL service environment in CS. The service also interacts with charging systems to bill the called subscriber for the personalized tone. Because the definition has remained stable from Rel-8 through Rel-19, CAT Inter-working is a mature, well-understood capability that continues to be relevant as operators maintain hybrid CS/IMS networks and as VoLTE deployments grow.
Purpose & Motivation
CAT Inter-working exists to solve the problem of service continuity for personalized ringback tones in heterogeneous networks. Early CAT deployments were typically confined to a single domain — either a pure CS/IN implementation or an IMS-only implementation. As operators migrated toward IMS while retaining CS infrastructure, subscribers could find that their CAT service worked in one domain but not the other, or failed when calling across network boundaries. This inconsistency degraded user experience and created billing and service-assurance complications.
The specification in TS 22.182 and TS 22.982 was created to define a consistent set of requirements so that a CAT service can be offered irrespective of the domain (CS or IMS) and irrespective of whether the call crosses PLMN boundaries. It addresses the limitations of siloed service implementations by mandating interworking functions and service control mechanisms that preserve the personalized alerting experience end-to-end.
Historically, the service builds on the CAMEL framework for CS and on SIP/IMS application server architecture for IMS. The interworking requirements ensure that operators can evolve their networks incrementally — deploying IMS CAT while continuing to serve CS customers — without stranding subscribers on either side of the domain divide.
Release Timeline
Evolution Across Releases
An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.
Defining Specifications
3GPP specifications that define or reference CAT Inter-working, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 22.182 vj00 | Customized Alerting Tone (CAT) Service Requirements | Rel-19 read |
| TR 22.982 vj00 | Customized Alerting Tone Service Requirements | Rel-19 read |