Standalone Transaction

Description

A Standalone Transaction is a Session Initiation Protocol (SIP) transaction that operates independently of any existing SIP dialog and does not create a new dialog. In SIP, a transaction consists of a request and all responses to that request, and it is a fundamental unit of SIP operation. Transactions can be of two types: those that are part of a dialog (in-dialog transactions) and those that are not (out-of-dialog transactions). A Standalone Transaction is a specific type of out-of-dialog transaction that does not initiate the creation of a new dialog. This means that the SIP request is sent outside the context of any dialog, and the response does not establish a dialog for future communication.

The concept of a Standalone Transaction is particularly relevant in the IP Multimedia Subsystem (IMS) and other 3GPP SIP-based architectures. In IMS, SIP is used for session control, and transactions are used for various purposes such as registration, subscription, notification, and instant messaging. A Standalone Transaction is typically used for requests that are self-contained and do not require an ongoing dialog. For example, a SIP MESSAGE request for instant messaging is often sent as a Standalone Transaction because it does not need to establish a dialog; the message is delivered and the transaction ends. Similarly, a SIP OPTIONS request for capability discovery is a Standalone Transaction.

The operation of a Standalone Transaction follows standard SIP transaction semantics. The client (User Agent Client, UAC) generates a request and sends it to a server (User Agent Server, UAS) via a proxy or directly. The transaction is identified by the branch parameter in the Via header, which uniquely identifies the transaction. The UAS processes the request and generates a response. If the response is a final response (2xx, 3xx, 4xx, 5xx, or 6xx), the transaction is completed. For a Standalone Transaction, the final response does not create a dialog, meaning that no dialog state is maintained by either the UAC or UAS after the transaction completes. This is in contrast to an INVITE transaction that results in a 2xx response, which establishes a dialog.

The distinction between Standalone Transactions and dialog-creating transactions is important for SIP implementations. Standalone Transactions are simpler to handle because they do not require dialog state management. However, they also have limitations: they cannot be used for services that require an ongoing session, such as voice or video calls. They are best suited for one-shot request-response interactions. In 3GPP specifications 23.218, 24.407, and 24.607, the term is used to describe SIP transactions in the IMS that are used for specific procedures, such as subscription to registration state (REGISTER), presence, and messaging.

In the context of IMS, Standalone Transactions are used in various interfaces, including the Gm interface (between UE and P-CSCF), the ISC interface (between S-CSCF and application servers), and the Ut interface (between UE and application servers). For example, when a UE sends a SIP SUBSCRIBE request to subscribe to its own registration state, this is a Standalone Transaction because it does not create a dialog; the notifications are sent as separate transactions. Similarly, the SIP PUBLISH request for presence information is a Standalone Transaction. The definition has remained stable across 3GPP releases, indicating that the fundamental concept of a Standalone Transaction is well-established and does not require revision.

Purpose & Motivation

The Standalone Transaction concept exists to provide a clear classification of SIP transactions that do not involve dialog establishment. In SIP, dialogs are essential for session-oriented communication, but many SIP operations are inherently one-shot and do not require a dialog. Without a clear term for these transactions, there would be ambiguity in specifications and implementations regarding how to handle such requests. The Standalone Transaction term solves this by explicitly defining a transaction that is not part of an existing dialog and does not initiate a new one.

The motivation for defining this term in 3GPP Release 5 was the growing use of SIP in IMS for services beyond basic session establishment. IMS introduced a wide range of SIP-based services, including instant messaging, presence, and event notification, which rely on out-of-dialog transactions. These services needed a standardised way to describe transactions that are independent of dialogs. The Standalone Transaction term provided this standardisation, enabling consistent implementation across different vendors and ensuring interoperability.

Prior to this definition, SIP specifications (such as RFC 3261) already described out-of-dialog transactions, but the term 'Standalone Transaction' was not standardised in 3GPP. By introducing this term, 3GPP aligned its specifications with IETF SIP standards and provided a common vocabulary for IMS developers. The term has been carried forward unchanged through subsequent releases, demonstrating its continued relevance and stability. It remains a fundamental concept for understanding SIP transaction handling in IMS and other 3GPP SIP-based systems.