Group and List Management Server

Description

The Group and List Management Server (GLMS) is a functional entity within the IP Multimedia Subsystem (IMS) architecture, defined in 3GPP specifications. It is responsible for the storage and management of group-related information on behalf of users. This information primarily consists of groups (like "work colleagues" or "family") and lists (specifically, authorization lists that define rules for who can see a user's presence information or send them messages). The GLMS provides a standardized interface, typically based on the XML Configuration Access Protocol (XCAP), allowing IMS clients to manipulate this data. When a user wants to create a new contact group or modify who can see their online status, their client application sends an XCAP request (HTTP PUT, GET, DELETE) to the GLMS, which then stores the data in its internal database.

The GLMS's architecture is designed to be a centralized repository for user-managed data that is referenced by other IMS application servers. For instance, a Presence Server will query the GLMS to retrieve a user's "presence authorization list" to determine which watchers are permitted to receive presence updates. Similarly, an Instant Messaging (IM) server might use group definitions stored in the GLMS for managing chat rooms or distribution lists. The server authenticates requests using IMS subscription identities (like the Private User Identity) and ensures data integrity and privacy for each user. It does not execute service logic itself but provides the persistent data storage that enables service personalization and access control.

From a network integration perspective, the GLMS is often implemented as a standalone node or collocated with other IMS application servers. It interfaces with the Home Subscriber Server (HSS) for user profile-related data but is distinct in that it manages dynamic, user-created content rather than static subscription profiles. Its role is critical for user-centric services, as it empowers subscribers to control their communication environment. The management of this data via XCAP aligns with IMS's principle of using internet protocols, facilitating interoperability with non-3GPP clients and services.

Purpose & Motivation

The GLMS was introduced to address the need for user-managed service personalization and access control within the emerging IP Multimedia Subsystem. Prior to IMS, cellular services like SMS or MMS had limited capabilities for users to define complex contact groups or fine-grained sharing rules. As IMS aimed to deliver internet-style services (presence, instant messaging, conferencing) with carrier-grade reliability, a standardized mechanism for users to manage the data underpinning these services became essential.

The creation of the GLMS solved the problem of where and how to store user-defined service data in a scalable and interoperable way. Without it, each application server (e.g., for presence or messaging) would need to implement its own proprietary method for storing user lists, leading to data silos, inconsistency, and a poor user experience. The GLMS provides a unified, network-based repository, ensuring that a user's contact groups and privacy rules are consistently applied across all IMS services they use. This separation of data management from service execution is a key architectural principle that promotes service agility and simplifies the development of new group-based applications.

Key Features

• Stores and manages user-defined contact groups and authorization lists (e.g., presence allow/block lists).
• Provides standardized XCAP (XML Configuration Access Protocol) interfaces for client access and manipulation.
• Integrates with IMS application servers like Presence Servers and Instant Messaging Servers to enforce user preferences.
• Supports authentication based on IMS subscriber identities for secure data access.
• Enables consistent service personalization across multiple IMS applications from a single data source.
• Facilitates the creation of advanced communication services like group chat, resource lists for presence, and conferencing.

Evolution Across Releases

Defining Specifications