The IMS in OMA Enabler Release version 1.0 contains general requirements and guidelines and does not specify detailed requirements that should be tested or that by themselves can be implemented in products.

The basic IETF SIP specification

Definition of the PRACK method, the RAck and RSeq headers. Used to send 1xx responses reliably. In IMS used to allow SDP Offer/Answer Exchange in early dialog state.

Definition of the SDP Offer / Answer mechanism, that is used in SIP to negotiate session parameters between the two endpoints.

Definition of the SIP SUBSCRIBE and NOTIFY messages and related headers. Allows a user to subscribe to continous notification of an event service (e.g. used for presence and reg-event)

Definition of the UPDATE request. Allows updating of session parameters (SDP) during a dialog. In IMS used to confirm successful resource reservation at the A-side during session establishment.

Definition of the P-Preferred-Identity and P-Asserted-Identity headers. User can indicate it's preferred identity to the network, which then asserts the identity. Used in IMS for authentication purposes.

Definition of Path header, which is used to enforce routing via certain Proxies towards the user. In IMS used for enforcing routing of initial request via the P-CSCF.

3GPP specfic headers: P-Associated-URI, P-Called-Party-ID, P-Visited-Network-ID, P-Access-Network-Info, P-Charging-Function-Address, P-Charging-Vector

Diameter is used on Cx, Dx and Sh interfaces within the IMS, i.e. between the HSS and the CSCFs and between the HSS and an Application Server (AS).

Definition of the Service-Route header, which is used to indicate the UE the address of the Home Service Proxy. Im IMS used for enforcing routing of initial requests via the S-CSCF.

Definition of the Reg-Event package. In IMS used for registering implicitly registered public user identities (AORs), network initiated re-authentication and de-registration.

The basic IMS requirements.

The basic IMS architecture specification.

The IMS protocol specification - how SIP and SDP are used in IMS.

IMS to PSTN / ISUP interworking

The basic IMS security specification.

The old version of the basic SIP specification. This document was obsolted by RFC 3261. Only listed for backward-compatibility issues.

Definest the SIP INFO messages. Used mainly for interworking with / tunneling of ISUP.

The basic IETF SIP specification

Definition of the PRACK method, the RAck and RSeq headers. Used to send 1xx responses reliably. In IMS used to allow SDP Offer/Answer Exchange in early dialog state.

How to find and resolve SIP Servers

Definition of the SDP Offer / Answer mechanism, that is used in SIP to negotiate session parameters between the two endpoints.

Definition of the SIP SUBSCRIBE and NOTIFY messages and related headers. Allows a user to subscribe to continous notification of an event service (e.g. used for presence and reg-event)

Definition of the UPDATE request. Allows updating of session parameters (SDP) during a dialog. In IMS used to confirm successful resource reservation at the A-side during session establishment.

Definition of Preconditions - they allow (besides other things) to guard the resource reservation time during session setup.

Definition of the P-Media-Authorization header, which is used to transport the Authorization token from the P-CSCF to the UE

DHCP extensions enabling a UE to automatically find an Outbound Proxy (in IMS: P-CSCF). Defines DHCPv6 options 21 (OPTION_SIP_SERVER_D - domain name) and 22 (OPTION_SIP_SERVER_A - IPv6 addresses)

Definition of the SIP Privacy header. Allows users to hide their identity from the remote party.

Definition of the P-Preferred-Identity and P-Asserted-Identity headers. User can indicate it's preferred identity to the network, which then asserts the identity. Used in IMS for authentication purposes.

Definition of the SIP Reason header, which is used for indicating reasons for session cancellations (e.g. transport of ISUP cause codes)

Definition of Path header, which is used to enforce routing via certain Proxies towards the user. In IMS used for enforcing routing of initial request via the P-CSCF.

Definition of the Security-Client, Security-Server and Security-Verify headers. UE and Outbound Proxy can agree on the Security Mechanism they want to use.

DHCP extension enabling a UE to automatically find an Outbound Proxy. Defines DHCPv4 option 120 for the SIP Servers discovery

Allows repetition of certain SIP headers in the body of the very same SIP message - for end-to-end security purposes. Also used with REFER.

Definition of the SIP MESSAGE method

3GPP specfic headers: P-Associated-URI, P-Called-Party-ID, P-Visited-Network-ID, P-Access-Network-Info, P-Charging-Function-Address, P-Charging-Vector

SigComp Dictionary for compression of SIP and SDP

Definition of the SIP "comp" URI parameter, to indicate the willingness (ability) of a UE or a Proxy to compress SIP messages.

Definition of the REFER method. Used e.g. for transferring calls to a user or to join a user into a conference.

Definition of the rport parameter

Definition of the Service-Route header, which is used to indicate the UE the address of the Home Service Proxy. Im IMS used for enforcing routing of initial requests via the S-CSCF.

This document gives examples of Session Initiation Protocol (SIP) call flows. Elements in these call flows include SIP User Agents and Clients, SIP Proxy and Redirect Servers. Scenarios include SIP Registration and SIP session establishment. Call flow dia

Definition of the Reg-Event package. In IMS used for registering implicitly registered public user identities (AORs), network initiated re-authentication and de-registration.

Definition of so-called "Feature Tags" - UE can indicate its basic capabilities during registration in the Contact Header. Used in IMS for PoC and CSI. See also RFC 3841.

Caller can indicate that call should be routed preferrably / only to a terminating UE that supports certain features ("Feature Tags" - see also RFC 3840)

The basic Presence specification for SIP. Defines a event package (see RFC 3265) that transports the PIDF format (see RFC 3863)

Defines a SIP event package (see RFC 3265) that allows a presentity (the entity which publishes its presence information) to find out who is watching (is subscribed to) its presence information.

The watcher related information, that is transported by the mechanisms defined in RFC 3857

Defines the "pres" and "im" address schemes (e.g. pres:heini@imsbook.com) for Presence and Instant Messaging

Definition of the Replaces header. Used to indicate that a new SIP dialog replaces an old SIP dialog.

Definition of the Referred-By header. Used for indicating to the final destination the identity of the referrer.

Defines the SIP PUBLISH metod, which is used to publish ones own presence information to a presence server.

Definition of the Join header. Used to join two existing SIP dialogs, so that only one SIP dialog results.

Defines the Session-Expires and the Min-SE headers. Used for enforcing periodic refreshes of SIP sessions through a re-INVITE or UPDATE request.

Additional clarifications to RFC 3312 (Preconditions)

The basic SIP conferencing specification.

Definition of the SDP Offer / Answer mechanism, that is used in SIP to negotiate session parameters between the two endpoints.

Definition of the UPDATE request. Allows updating of session parameters (SDP) during a dialog. In IMS used to confirm successful resource reservation at the A-side during session establishment.

Definition of Preconditions - they allow (besides other things) to guard the resource reservation time during session setup.

Defines a Framework for grouping of media streams for different purposes (e.g. lip synchronization between a video and an audio stream)

Uses the m-line grouping" framework (RFC 3388) to allow grouping of media streams e.g. into different PDP contexts

Definition of the SDP b=RS and b=RR attributes, to indicate bandwidth that will be used for RTCP during a session

Additional clarifications to RFC 3312 (Preconditions)

Comprehensive examples for how SDP is used in SIP

RFC 1889 - RTP: A Transport Protocol for Real-Time Applications

Definition of RTP (Real Time Protocol) and RTCP (Real Time Control Protocol). RTP is used to transport media streams (e.g. a voice or video stream). RTCP is used to control the flow of RTP messages.

RTP/AVP is a profile used to map the payload type (e.g. voice) to a specific codec (e.g. G.711).

This document describes a simple client/server model for supporting policy control over QoS signaling protocols. The model does not make any assumptions about the methods of the policy server, but is based on the server returning decisions to policy reque

Framework allowing users to request (and get granted) specific levels of qualtiy of service

How to transport DTMF signals (key-press signals) in a SIP and RTP based environment. In IMS the telephony-event type is used.

How COPS (RFC 2748) is used to provide policy provisioning. This is used in the IMS over the Go and Gq interfaces (GGSN/PEP - PDF - P-CSCF) for service based local policy (SBLP)

RFC 2748 defines the COPS protocol, and the provisioning of policy is introduced in RFC 3084. This RFC defines the adapted subset of SNMP's Structure of Management Information (SMI) used to write Policy Information Base (PIB) modules.

Definition of Preconditions - they allow (besides other things) to guard the resource reservation time during session setup.

Definition of the P-Media-Authorization header, which is used to transport the Authorization token from the P-CSCF to the UE

Defines the structure of the Media Authorization token.

Usage of codecs, RTP and SDP in IMS Multimedia Telephony (This TR will be replaced with TS 26.114)

Architecture for guaranteeing quality of service

Architecture for Policy Control (Media Authorization / SBLP) and Charging

Basic 3GPP Quality of Service architecture specification

Usage of codecs, RTP and SDP in IMS Multimedia Telephony

Default codecs and media as used for IMS presence and messaging

Gives guidance on how to use RTP and SDP in case of 3G Streaming Service

Specification of default multimedia codecs to be used within IMS

Specification of required protocol usage within 3GPP specified Conversational Packet Switched Multimedia Services, which is used in IMS.

COPS-based interface between the P-CSCF and the Policy Decision Function (PDF)

Examples of QoS signalling flows for resource reservation - between UE, GGSN, PDF and AF

COPS-based interface between the Policy Enforcement Point (PEP) in the GGSN and a Policy Decision Function (PDF)

Diameter is used on Cx, Dx and Sh interfaces within the IMS, i.e. between the HSS and the CSCFs and between the HSS and an Application Server (AS).

Example Signalling flows between the HSS and the CSCFs

Cx and Dx interfaces are between the CSCFs and the HSS. They are based on the Diameter Protocol.

How to configure the Mobile with IMS related settings. OMA Device Management Manged Object (DM MO) and Client Provisioning Application Characteristics (CP AC).

Defines a OMA DM Management Object (MO) that is used to configure VCC related parameters (VDI, VDN, Operator Policy for DomainTransfers) to the UE.

Automatically deactivate certain UE functionalities.

Architecture specification for Handovers between CS and IMS (VCC)

Architectural Study on Handovers between CS and IMS (VCC)

Handing over ongoing calls from IMS to CS and vice versa (VCC) - IMS Protocol impacts

Defines a OMA DM Management Object (MO) that is used to configure VCC related parameters (VDI, VDN, Operator Policy for DomainTransfers) to the UE.

Architecture for IMS Emergency Calls

The IMS protocol specification - how SIP and SDP are used in IMS.

3GPP specfic headers: P-Associated-URI, P-Called-Party-ID, P-Visited-Network-ID, P-Access-Network-Info, P-Charging-Function-Address, P-Charging-Vector

Charging per media flow - Architecture

Architecture for Policy Control (Media Authorization / SBLP) and Charging

The IMS protocol specification - how SIP and SDP are used in IMS.

General 3GPP Charging Architecture

3GPP IMS charging management basicims

Transport Layer Security - security mechanism that is used by SIP (besides others)

Definition of IPSec. IPSec based Security Associations are used between the IMS UE and the P-CSCF (see 3GPP TS 24.229 and 3GPP TS 33.203)

Algorithm used for the IPSec Security Associations between the IMS UE and the P-CSCF (see 3GPP TS 24.229 and 3GPP TS 33.203)

Algorithm used for the IPSec Security Associations between the IMS UE and the P-CSCF (see 3GPP TS 24.229 and 3GPP TS 33.203)

HTTP Digest Authentication is used also in SIP. In IMS HTTP Digest is used to transport 3GPP AKA (see also RFC 3310, 3GPP TS 33.210 and 3GPP TS 24.229)

How 3GPP AKA can be used on top of HTTP Digest

Definition of the Security-Client, Security-Server and Security-Verify headers. UE and Outbound Proxy can agree on the Security Mechanism they want to use.

Release 7 related feasibility study on IMS security (mainly for TISPAN)

General security architecture for 3rd generation mobile systems.

Security considerations for Presence within 3GPP.

The basic IMS security specification.

Security between 3G networks

Early IMS security / IP-Authentication.

General Framework for Compression of IETF Protocols

SigComp Dictionary for compression of SIP and SDP

Definition of the SIP "comp" URI parameter, to indicate the willingness (ability) of a UE or a Proxy to compress SIP messages.

Definition of the SIP SUBSCRIBE and NOTIFY messages and related headers. Allows a user to subscribe to continous notification of an event service (e.g. used for presence and reg-event)

Definition of the SIP Privacy header. Allows users to hide their identity from the remote party.

Definition of the P-Preferred-Identity and P-Asserted-Identity headers. User can indicate it's preferred identity to the network, which then asserts the identity. Used in IMS for authentication purposes.

3GPP specfic headers: P-Associated-URI, P-Called-Party-ID, P-Visited-Network-ID, P-Access-Network-Info, P-Charging-Function-Address, P-Charging-Vector

Definition of the Reg-Event package. In IMS used for registering implicitly registered public user identities (AORs), network initiated re-authentication and de-registration.

Definition of the tel-URI scheme, which is also used in IMS to address users (e.g. with their already existing MSIDN/phone number)

Defines, besides other things, how SIP identities look like in IMS and how temporary identities are derived.

Definition of so-called "Feature Tags" - UE can indicate its basic capabilities during registration in the Contact Header. Used in IMS for PoC and CSI. See also RFC 3841.

Caller can indicate that call should be routed preferrably / only to a terminating UE that supports certain features ("Feature Tags" - see also RFC 3840)

Architectural study on support of device related URIs (GRUU) in IMS

Architectural definition of Service Identifiers.

TR collecting ongoing work on IMS Centralized Services (ICS) in SA2 - Release 8.

Requirements on how to combine CS and IMS sessions.

Architecture for Service Provisioning in IMS

The basic IMS architecture specification.

The IMS protocol specification - how SIP and SDP are used in IMS.

** This TR is discontinued - relevant content can be found in TS 24.229, 24.008 and 24.279 and other core specifications **

Requirements on how to combine CS and IMS sessions.

Architecture for the comination of CS and IMS services.

Studies how to handle terminating real-time sessions and calls taking into account different domains (CS, IMS) and different UE capabilities (CSI, IMS VoIP, etc.) - "CSI Phase 2"

CSI: parallel ongoing IMS and CS sessions.

Usage of codecs, RTP and SDP in IMS Multimedia Telephony (This TR will be replaced with TS 26.114)

Voice over IP in IMS - including Supplementary Services

Usage of codecs, RTP and SDP in IMS Multimedia Telephony

Defines an abstract model for presence and instant messaging. This model is used as a base by the SIP and IMS presence/messaging specifications.

The basic Presence specification for SIP. Defines a event package (see RFC 3265) that transports the PIDF format (see RFC 3863)

Defines a SIP event package (see RFC 3265) that allows a presentity (the entity which publishes its presence information) to find out who is watching (is subscribed to) its presence information.

The watcher related information, that is transported by the mechanisms defined in RFC 3857

Defines the "pres" and "im" address schemes (e.g. pres:heini@imsbook.com) for Presence and Instant Messaging

PIDF is the XML encoded presence information, that is transported by SIP messages.

Defines the SIP PUBLISH metod, which is used to publish ones own presence information to a presence server.

** This TR is discontinued - relevant content can be found in TS 24.141 and other core specifications **

Requirements for IMS Presence

Architecture for Presence in IMS

SIP Presence as it is used in IMS. Introduced in rel6

Default codecs and media as used for IMS presence and messaging

Security considerations for Presence within 3GPP.

Defines an abstract model for presence and instant messaging. This model is used as a base by the SIP and IMS presence/messaging specifications.

Definition of the SIP MESSAGE method

Defines the "pres" and "im" address schemes (e.g. pres:heini@imsbook.com) for Presence and Instant Messaging

IMS Messaging requirements

The basic IMS architecture specification.

SIP Messaging in IMS - includes MESSAGE method as well as usage of MRSP.

Default codecs and media as used for IMS presence and messaging

Definition of the REFER method. Used e.g. for transferring calls to a user or to join a user into a conference.

The basic SIP conferencing specification.

** This TR is discontinued - relevant content can be found in TS 24.147 and other core specifications ** Introduced in Rel-6

The basic IMS requirements.

The basic IMS architecture specification.

SIP conferencing as it is used in IMS

How OMA PoC works within 3GPP IMS.

Technical report - SMS and MMS via IMS

Sending MMS and SMS via IMS. Introduced in Rel-7.

3GPP Stage 2 (SA2) specification that introduces concepts like short session setup and network initiated PDP context. Rel-7 architectural study. This specification will not be officially published.

Test Cases for IMS conformance testing

Impelementation Conformance Statements for IMS conformance testing

Abstract Test Suite (TTCN) for IMS conformance testing

This document gives examples of Session Initiation Protocol (SIP) call flows. Elements in these call flows include SIP User Agents and Clients, SIP Proxy and Redirect Servers. Scenarios include SIP Registration and SIP session establishment. Call flow dia

Comprehensive examples for how SDP is used in SIP

Example flows for different session setup scenarios in IMS (e.g. GPRS attched UE to WLAN attached UE, applications that need resource reservations and those which need not). Also informally known as "short session setup".

SIP Presence as it is used in IMS. Introduced in rel6

SIP conferencing as it is used in IMS

This specification is outdated - don't use it anymore

Examples of QoS signalling flows for resource reservation - between UE, GGSN, PDF and AF

Example Signalling flows between the HSS and the CSCFs

Basic DHCP specification. DHCP is used in IMS for discovering Outbound Proxies (see RFC 3319)

MIME Multipart allows to put several different content types into the body of a SIP message (e.g. SDP and a picture)

HTTP, the protocol that makes the world wide web work, was the model for SIP. Many SIP procedures and protocol elements are identical to those of HTTP.

Transport of signalling messages over IP networks. Used in 3GPP to transport e.g. also Diameter messages.

Update for the SCTP Checksum Mechanism

Basic DHCP specification. DHCP is used in IMS for discovering Outbound Proxies (see RFC 3319)

Vocabulary used in 3GPP specs.

General 3GPP Network Architecture. Introduced in Rel-99

Defines, besides other things, how SIP identities look like in IMS and how temporary identities are derived.

GPRS architecture and overview.

3GPP protocols for CS and GPRS.