Content for TS 24.183 Word version: 17.1.0
1 Scope p. 6
The present document provides the protocol details for the Customized Ringing Signal (CRS) service in the IP Multimedia (IM) Core Network (CN) subsystem based on the requirements from TS 22.183.
The CRS service is an operator specific service by which an operator enables the subscriber to customize the media which is played to the called party as an incoming communication indication during establishment of a communication.
The present document is applicable to User Equipment (UE) and Application Servers (AS) which are intended to support the CRS service.
2 References p. 6
The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
- References are either specific (identified by date of publication, edition number, version number, etc.) or non specific.
- For a specific reference, subsequent revisions do not apply.
- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1]
TR 21.905: "Vocabulary for 3GPP Specifications".
[2]
TS 22.183: "Customized Ringing Signal (CRS) Requirements; Stage 1".
[3]
TS 24.229: "IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3".
[4]
RFC 3959: "The Early Session Disposition Type for the Session Initiation Protocol (SIP)".
[5]
TS 24.623: "Extensible Markup Language (XML) Configuration Access Protocol (XCAP) over the Ut interface for Manipulating Supplementary Services".
[6]
TS 24.238: "Session Initiation Protocol (SIP) based user configuration; Stage 3".
[7]
RFC 6086 (January 2011): "Session Initiation Protocol (SIP) INFO Method and Package Framework".
[8]
RFC 7462 (March 2015): "URNs for the Alert-Info Header Field of the Session Initiation Protocol (SIP)".
[9]
RFC 4796: "The Session Description Protocol (SDP) Content Attribute".
[10]
RFC 3960: "Early Media and Ringing Tone Generation in the Session Initiation Protocol (SIP)".
[11]
TS 24.628: "Common Basic Communication procedures; Protocol specification".
[12]
RFC 3311: "The Session Initiation Protocol (SIP) UPDATE Method".
[13]
TS 24.174: "Support of Multi-Device and Multi-Identity in IMS; Stage 3".
[14]
RFC 3312: "Integration of Resource Management and Session Initiation Protocol (SIP)".
[15]
RFC 3840: "Indicating User Agent Capabilities in the Session Initiation Protocol (SIP)".
3 Definitions and abbreviations p. 7
3.1 Definitions p. 7
For the purposes of the present document, the terms and definitions given in TR 21.905 and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905.
Media component:
A media component, described by the SDP, is a separate data-flow related to a media type which is sent by using an IP-based transport protocol (e.g. RTP). Multiple media components may be used in the same session to send multiple media types.
3.2 Abbreviations p. 7
For the purposes of the present document, the abbreviations given in TR 21.905 and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905.
CRS
Customized Ringing Signal
MiD
Multi-iDentity
MuD
Multi-Device
