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

Glossary term · Services

EMS

Enhanced Messaging Service

Services →

EMS is an enhanced, standardized 3GPP messaging service that extends basic SMS to enable the exchange of rich multimedia content like pictures, audio, video, and formatted text.

Introduced
R99
Where
Management
Specifications
10 specs
Also in
Services
EMS Description Purpose What changed Family Neighbours Detected Changes Specifications

Description

Enhanced Messaging Service (EMS) is a 3GPP standardized service that defines the capabilities for sending and receiving messages containing multimedia content over cellular networks. It operates as an enhancement to the Short Message Service (SMS), utilizing the same fundamental transport mechanisms but extending the User Data Header (UDH) and payload to support richer media types. The architecture involves the Mobile Station (MS) for message creation and rendering, the core network elements (like MSC, SMSC) for routing, and potentially external servers (MMS Relay/Server) for more advanced MMS handling. EMS messages are structured as concatenated SMS messages with specific headers indicating the presence of formatted text, pictures, melodies, or animations.

Technically, EMS works by encoding media objects into a defined binary format and packaging them within the SMS transport protocol. The standard defines a set of predefined media objects (e.g., black & white pictures, ringtones in iMelody format) and their coding. When a user sends an EMS message, the handset's software assembles the content, applies the correct EMS coding, and submits it as one or more SMS submissions to the network. The receiving handset, upon detecting the EMS-specific indicators in the UDH, reassembles the message and interprets the media elements for display or playback.

Its role in the network is as a foundational messaging service layer. While largely superseded by the full Multimedia Messaging Service (MMS) in consumer perception, EMS specifications provided the crucial evolutionary step and technical framework. Key components defined in EMS specs include the message structure, media object definitions, and the application layer protocols for submission, delivery, and notification. It ensured interoperability between different vendors' handsets and networks for basic multimedia messaging before full IP-based MMS became ubiquitous.

Purpose & Motivation

EMS was created to address the significant limitation of SMS, which was restricted to plain text of a very limited length (160 characters). The driving motivation was to enable more expressive and engaging communication directly from mobile phones by supporting basic multimedia. This addressed growing user demand for sharing more than just text, such as simple graphics (e.g., emoticons, pictures) and ringtones, which was becoming popular in the late 1990s and early 2000s.

Historically, proprietary vendor-specific solutions for sending pictures or sounds existed, but they lacked interoperability. EMS provided a standardized, interoperable framework within the 3GPP ecosystem. It solved the problem of fragmentation by defining a common coding and transport method that all compliant networks and handsets could support, ensuring a user could send a picture message to any other user on any compatible network.

The creation of EMS was a strategic step towards full multimedia messaging (MMS). It allowed network operators and handset manufacturers to introduce richer messaging features incrementally, leveraging the existing, ubiquitous, and reliable SMS infrastructure. This lowered the barrier to entry for multimedia messaging and paved the way for the market adoption and technical evolution that culminated in the IP-based MMS standards.

What changed in its specifications

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

TS 32.101Rel-17 → Rel-18

Rel-18 brings only minor changes to TS 32.101: 1 clause changed, with no change attributed to a release feature.

Full comparison in TS 32.101 →

Technology family

Messaging services · Services

  1. Phase 1 CBC, MO-SMS, MT-SMS, SMS, SMS-CB
  2. Phase 2 CBE, SMS-GMSC, SMS-IWMSC
  3. R99 EMS, MMS, MMS User Agent, MMSE
  4. Rel-4 MMS Relay/Server
  5. Rel-6 IP-SM-GW, MSCF
  6. Rel-7 SMS over IP, SMS Router
  7. Rel-8 SMS over SGs
  8. Rel-15 CBCF, PWS-IWF, SMS over NAS, SMSF
  9. Rel-17 Legacy 3GPP Message Gateway, MSGin5G, MSGin5G Client, MSGin5G Server, Non-3GPP Message Gateway
  10. Rel-18 Broadcast Message Gateway
  • EMS builds on SMS
    “Enhanced Messaging is based on standard mechanism in GSM SMS messaging.” TS 23.040

Members and relations were proposed independently by several models and kept only where at least two agree; quotes are verified verbatim against the specifications. Release = first approved version of the defining specification.

Detected Changes Across Releases

verified against 3GPP sources

Documented changes in 1 releases, each verified against the text of 3GPP specifications or approved change requests and shown with the exact wording. The release timeline above shows the same releases. A release without an entry has no documented change for this term.

R99 introduced

Introduced in R99 (release dating of the term; no individual change cited).

Defining Specifications

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

SpecificationTitleRelease
TS 22.242 vj00 DRM Service Requirements Rel-19 read
TR 22.804 vg30 5G Automation in Vertical Domains Study Rel-16 read
TS 29.199 3GPP TS 29.199 R99 read
TS 32.101 vj00 PLMN Management Principles and Requirements Rel-19 read
TS 32.822 v900 EMS Maintenance Functions Study over Itf-N Rel-9 read
TS 32.826 va00 LTE Energy Savings Management Study Rel-10 read
TS 32.854 vb10 FMC Network Model Alignment Rel-11 read
TS 32.861 vd00 IRP Requirements Subsets for Network Management Rel-13 read
TS 32.880 vf00 Simplified Itf-N IRP Solution Sets Study Rel-15 read
TR 38.882 vi00 Technical Report on UE Location Service Rel-18 read