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

Glossary term · Management

Data Element Group

Data Element Group

Management →

Data Element Group is a pre-defined set of closely related Data Elements and/or other Data Element Groups in the Generic User Profile model, and one or more such groups can constitute a GUP Component.

Introduced
Rel-8
Where
Services › IMS
Specifications
2 specs
Data Element Group Description Purpose Neighbours Specifications

Description

A Data Element Group is a structural construct in the Generic User Profile (GUP) information model defined in 3GPP TS 23.240 and TS 29.240. It is defined as a pre-defined set of Data Elements and/or other Data Element Groups that are closely related to each other. This definition makes the Data Element Group a recursive aggregation mechanism: a group may contain atomic Data Elements, other Data Element Groups, or a mixture of both, allowing the profile model to express arbitrarily deep and richly structured relationships while remaining anchored on the indivisible Data Element.

The primary role of the Data Element Group is organization and semantic clustering. Profile information naturally falls into domains — for example, subscription attributes, service preferences, terminal capabilities, or user settings — and each domain comprises many individual Data Elements that are meaningful together. Grouping them makes the model comprehensible to humans and manageable for machines: operations, access policies, and versioning can be applied to a coherent set of related information rather than to isolated elements. Because groups can nest, coarse domains can be decomposed into finer sub-domains without losing the hierarchical structure.

At the top of the hierarchy, one or more Data Element Groups can constitute a GUP Component. The GUP Component is the container that represents a complete, self-contained portion of the user profile, and it is built from groups. This three-level pattern — Data Element, Data Element Group, GUP Component — gives the GUP framework a clean, composable architecture: atomic data at the bottom, semantically related clusters in the middle, and complete profile components at the top.

In operation, a Data Element Group is identified within the GUP hierarchy and is subject to the access-control and privacy rules defined by the GUP framework. Because the group is pre-defined, its membership and semantics are standardized, ensuring that all parties — home network, visited network, application servers, and UE functions — share the same understanding of what the group contains and means. This standardization is essential for interoperability when profile information crosses domain or vendor boundaries.

The Data Element Group concept has proven durable: its definition has remained unchanged from Release 8 through Release 19. This stability indicates that the recursive grouping abstraction adequately captures the structure of user profile information and continues to serve as a reliable foundation for GUP-based data management.

Purpose & Motivation

The Data Element Group exists to bring structure and manageability to the Generic User Profile. While the Data Element provides the atomic unit of profile information, real-world profiles contain hundreds or thousands of such elements, and treating them as a flat list would be impractical for discovery, access control, versioning, and human comprehension. The Data Element Group solves this by allowing closely related Data Elements — and nested groups — to be bundled into pre-defined, standardized clusters that can be managed as a unit.

The recursive nature of the definition is deliberate. User profile information is naturally hierarchical: a service domain contains sub-domains, which contain individual attributes. By permitting groups to contain other groups, the model can mirror this hierarchy faithfully without imposing a fixed depth. This flexibility lets 3GPP define profile structures that scale from simple subscriptions to complex, multi-service profiles while keeping the underlying representation consistent.

The group also serves as the bridge to the GUP Component. Since one or more Data Element Groups can constitute a GUP Component, the group is the modular building block from which complete profile components are assembled. This enables reuse: the same standardized group can appear in multiple components, and components can be composed from well-understood, interoperable parts. The result is a profile architecture that is both expressive and standardized, reducing integration effort and ambiguity across the 3GPP ecosystem. Its unchanged definition across twelve releases confirms the design has stood the test of time.

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.

Rel-8 Initial

Initial definition established the Data Element Group as a pre-defined set of Data Elements and/or other Data Element Groups closely related to each other, with one or more groups able to constitute a GUP Component.

Definition carried over unchanged.

Definition carried over unchanged.

Definition carried over unchanged.

Definition carried over unchanged.

Definition carried over unchanged.

Definition carried over unchanged.

Definition carried over unchanged.

Definition carried over unchanged.

Definition carried over unchanged.

Definition carried over unchanged.

Definition carried over unchanged; the term retained its original Rel-8 wording.

Defining Specifications

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

SpecificationTitleRelease
TS 23.240 vj00 3GPP Generic User Profile (GUP) Architecture Rel-19 read
TS 29.240 vj00 3GPP Generic User Profile (GUP) Stage 3 Protocol Rel-19 read