Simple Object Access Protocol

Description

Within 3GPP standards, the Simple Object Access Protocol (SOAP) is adopted as the underlying messaging protocol for implementing web services interfaces, most notably for the Open Service Architecture (OSA) and the Parlay/OSA Gateway. SOAP is an XML-based protocol that defines a framework for structuring messages and a convention for representing remote procedure calls (RPCs) and responses. In the 3GPP context, it is used to facilitate machine-to-machine communication between application servers (AS) residing in an external domain and the network's service capability servers (SCS) that expose core network functionalities.

The architecture involves a SOAP client, typically the external application, and a SOAP server, which is the network's Parlay/OSA Gateway or a specific Service Capability Server. Communication occurs over transport protocols like HTTP or HTTPS. A SOAP message is an XML document containing a mandatory Envelope element, an optional Header element for extensibility (e.g., for security or transaction information), and a mandatory Body element that carries the actual RPC request or response data. For OSA, the Body contains method invocations and parameters defined by the Parlay/OSA Application Programming Interfaces (APIs), such as methods for call control, messaging, or user status interrogation.

The role of SOAP in 3GPP is to provide a platform- and language-neutral wire format for API calls. This abstraction is crucial for the OSA principle, which aims to decouple service development from the underlying network technology. By using SOAP/XML, application developers can use various programming languages and tools to create services that interact with the telecom network through a standardized, web-friendly interface. The 3GPP specifications detail the precise XML schemas (XSDs) and Web Services Description Language (WSDL) files that define the OSA APIs, ensuring interoperability between different vendors' gateways and applications.

Purpose & Motivation

SOAP was incorporated into 3GPP specifications to address the need for a standardized, open, and technology-agnostic protocol for network capability exposure. The driving force was the Open Service Architecture (OSA) and the Parlay Group's initiative to create secure, scalable APIs that would allow third-party application providers to innovate without deep knowledge of telecom network protocols. Prior to this, accessing network capabilities required proprietary, vendor-specific interfaces, which stifled the development of a vibrant ecosystem of value-added services.

The adoption of SOAP, along with related web services standards like WSDL and XML, provided a widely recognized and industry-supported foundation. It solved the problem of interoperability between heterogeneous systems by offering a text-based, self-describing message format. This allowed 3GPP to specify the *what* (the API semantics) separately from the *how* (the underlying transport and encoding). The historical context includes the convergence of IT and telecom worlds in the early 2000s, where web services emerged as the dominant paradigm for system integration. SOAP provided the necessary rigor and extensibility (e.g., through WS-* standards for security) required for critical telecom operations, making it a suitable choice for the Parlay/OSA framework within 3GPP.

Key Features

• XML-based messaging protocol for structured information exchange.
• Core protocol for implementing 3GPP Parlay/OSA web services interfaces.
• Defines a standard Envelope, Header, and Body structure for messages.
• Transport-protocol independent, commonly used over HTTP/HTTPS.
• Enables Remote Procedure Call (RPC) and document-style interactions.
• Facilitates interoperability through standardized WSDL and XSD definitions.

Evolution Across Releases

Defining Specifications