Menu
Latest
12 meetings · Prague, Jeju · 12–16 Oct
Reports
RAN1#126-bis · SA2#177

Glossary term · Services

Operator specific service

Operator Specific Service

Services →

Operator specific service is a network-based, operator-administered function that provides additional, operator-defined MMS services for address translation and charging.

Introduced
R99
Where
Services
Specifications
2 specs
Operator specific service Description Purpose What changed Neighbours Specifications

Description

The Operator Specific Service is a concept within 3GPP that enables mobile network operators to offer services beyond those standardized by 3GPP specifications. Initially defined in R99 as any service not standardized by 3GPP, it evolved in Rel-6 to specifically refer to a network-based and operator-administered function that performs additional, operator-defined MMS services. These services leverage MMS capabilities for address translation and charging, allowing operators to differentiate their offerings and generate additional revenue.

Architecturally, the Operator Specific Service is implemented within the operator's network, typically as an application server or a functional entity that interacts with the MMS infrastructure. It can perform address translation, converting between different addressing formats (e.g., MSISDN to email), and apply charging mechanisms specific to the operator's business model. This function is not standardized in detail, giving operators flexibility to implement proprietary features.

The service operates by intercepting or processing MMS messages based on operator-defined rules. For example, an operator might offer a service that translates a short code into a full email address, or applies special charging for multimedia messages sent to certain destinations. The service can also add value by modifying message content, adding advertisements, or providing delivery reports with operator-specific information.

Key components include the MMS Proxy-Relay, which handles message routing and can invoke the Operator Specific Service, and the charging system, which applies the operator-defined charging rules. The service may also interact with the HLR/HSS for subscriber data and with the SMSC for SMS notifications. The exact implementation is left to the operator, but it must comply with the overall MMS architecture defined in 3GPP TS 22.140 and TS 22.976.

The Operator Specific Service is important because it allows operators to create unique services that differentiate them from competitors. It also enables operators to monetize MMS beyond standard messaging, for example through premium content or sponsored messages. However, it must be implemented carefully to avoid interoperability issues and to ensure a consistent user experience.

Purpose & Motivation

The Operator Specific Service exists to allow mobile network operators to offer value-added services that are not standardized by 3GPP. In the early days of mobile telephony, services were limited to voice and SMS, and operators had little flexibility to differentiate. With the introduction of MMS, operators saw an opportunity to create custom services that could generate additional revenue and improve customer loyalty. However, standardizing every possible service would be impractical and would stifle innovation. Therefore, 3GPP defined the concept of an Operator Specific Service as a catch-all for non-standardized services, and later refined it to focus on MMS-based services.

The primary problem it solves is the need for operators to provide unique features that are not covered by global standards. For example, an operator might want to offer a service that translates email addresses to mobile numbers for MMS, or applies special charging for messages sent during peak hours. Without a standardized framework, such services would be difficult to implement and could conflict with standard procedures. The Operator Specific Service provides a defined interface and functional description, ensuring that these custom services can be integrated into the MMS architecture without breaking interoperability.

Historically, the concept was introduced in R99 as a broad definition, but as MMS became more prevalent, it was refined in Rel-6 to specifically address MMS capabilities. This evolution reflects the growing importance of MMS as a revenue-generating service and the need for operators to have a clear framework for customizing it. The Operator Specific Service continues to be relevant in later releases, as operators seek new ways to monetize messaging and provide value-added features.

What changed in its specifications

The latest release-to-release comparison of specifications that define Operator specific service. Each summary describes the whole specification, not only this term.

TS 22.140Rel-5 → Rel-6

Added configurable error messages, prepaid error notification, UICC interaction, forwarding loop prevention, blacklists, and conditional delivery.

Full comparison in TS 22.140 →

Release Timeline

Evolution Across Releases

An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.

R99 Initial

Initial definition: 'any service offered to a mobile user that is not standardised by the 3GPP specifications'. This broad definition allowed operators to offer any non-standardized service, but did not provide specific technical details.

Definition unchanged from R99: 'any service offered to a mobile user that is not standardised by the 3GPP specifications'. The term continued to be used in the same context.

Definition changed to: 'network-based and operator administred function being able to perform additional, operator defined, MMS services based on MMS capabilities for address translation and charging.' This narrowed the scope to MMS-specific services and introduced the concept of a network-based function.

Definition unchanged from Rel-6. The term carried over without modification.

Definition unchanged from Rel-6. The term carried over without modification.

Definition unchanged from Rel-6. The term carried over without modification.

Definition unchanged from Rel-6. The term carried over without modification.

Definition unchanged from Rel-6. The term carried over without modification.

Definition unchanged from Rel-6. The term carried over without modification.

Definition unchanged from Rel-6. The term carried over without modification.

Definition unchanged from Rel-6. The term carried over without modification.

Definition unchanged from Rel-6. The term carried over without modification.

Definition unchanged from Rel-6. The term carried over without modification.

Definition unchanged from Rel-6. The term carried over without modification.

Definition unchanged from Rel-6. The term carried over without modification.

Definition unchanged from Rel-6. The term carried over without modification.

Defining Specifications

3GPP specifications that define or reference Operator specific service, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TS 22.140 vj00 MMS Stage 1 Requirements Rel-19 read
TS 22.976 3GPP TS 22.976 R99 read