Web Services Description Language

Description

The Web Services Description Language (WSDL) is a fundamental technology within 3GPP for defining the technical interface of network-exposed web services. It is an XML schema that provides a formal, machine-readable description of how a service can be called, what parameters it expects, and what data structures it returns. In 3GPP architectures, WSDL documents are used to specify the northbound and southbound Application Programming Interfaces (APIs) for numerous network functions, particularly in the domains of Operations, Administration, and Maintenance (OAM), Policy and Charging Control (PCC), and network element provisioning.

Architecturally, a WSDL 1.1 document (the version predominantly referenced in 3GPP) is composed of several key sections. The 'types' section defines the complex data structures (using XML Schema - XSD) that are exchanged in messages. The 'message' section defines the abstract content of a communication, grouping parts into input and output messages. The 'portType' (akin to an interface in programming) groups related operations, each specifying an input and/or output message. The 'binding' section concretely specifies the protocol (e.g., SOAP over HTTP) and data format (e.g., document/literal) for a portType. Finally, the 'service' section defines the network address (URL) where the bound interface can be accessed.

How it works in practice is that a network function acting as a Web Service Provider (e.g., a Home Subscriber Server - HSS for provisioning) publishes its WSDL document. A client system, or Web Service Consumer (e.g., a Network Management System - NMS), retrieves this WSDL. Using standard development tools, the consumer can automatically generate client-side code (stubs) that knows exactly how to construct a valid SOAP request, which endpoint to send it to, and how to parse the SOAP response. This automation drastically reduces integration effort and errors. Its role in the 3GPP network is as the cornerstone of a contract-first, service-oriented design for network interfaces, enabling multi-vendor interoperability, dynamic service discovery, and the alignment of telecom network management with mainstream IT integration practices.

Purpose & Motivation

WSDL was adopted by 3GPP to solve the critical problem of precisely and unambiguously defining the programmatic interfaces for network functions exposed as web services. Prior to its use, interface definitions were often conveyed through lengthy textual documents (human-readable specs), which led to interpretation errors, inconsistent implementations across vendors, and manual, error-prone integration work. This increased costs, delayed deployments, and created fragile multi-vendor networks.

The historical driver was the 3GPP's move towards all-IP networks and the desire to leverage widely adopted IT technologies for network management (starting in Release 8 with SAE). Web services offered a standardized communication framework, but a service is only as interoperable as its definition. WSDL, as a W3C standard, provided the missing piece: a formal, platform-neutral contract. Its creation was motivated by the need for a language that could be processed by machines to automate the generation of client and server code, ensuring that both sides of the communication adhered to the same data formats and procedural rules.

It addressed the limitations of previous approaches like proprietary APIs or protocols described only in prose. By using WSDL, 3GPP could specify interfaces in a way that was both human-readable (as XML) and directly consumable by software development kits (SDKs). This enabled a 'design by contract' methodology, where the interface is defined first and implementations are built to conform. This was essential for achieving the plug-and-play interoperability required for modern, automated, and virtualized networks, supporting key initiatives like Network Functions Virtualization (NFV) and Management and Orchestration (MANO) where dynamic service composition relies on standardized, discoverable interfaces.

Key Features

• XML-based format for describing web service interfaces in a platform-neutral manner
• Defines abstract operations (portType) and concrete protocol bindings (e.g., SOAP/HTTP)
• Uses XML Schema (XSD) within the 'types' section to define complex data structures
• Specifies the network endpoint location (URL) for accessing the service
• Enables automatic generation of client and server code stubs from the interface definition
• Supports a contract-first design approach for service-oriented architecture

Evolution Across Releases

Defining Specifications