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

Glossary term · Management

Data Element

Data Element

Management →

Data Element is the indivisible unit of Generic User Profile information, defined in 3GPP TS 23.240 and TS 29.240, representing the smallest addressable piece of user profile data managed by the GUP framework.

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

Description

A Data Element is the fundamental, indivisible building block of the Generic User Profile (GUP) information model defined in 3GPP TS 23.240 and its stage-3 counterpart TS 29.240. The GUP framework was created to provide a standardized, unified way to describe, store, and access user-related information across the 3GPP ecosystem — spanning the home network, the visited network, and the UE. Within that framework, a Data Element represents the smallest unit of profile information that cannot be further decomposed; it is the atomic piece of data around which the entire GUP data model is constructed.

Architecturally, the GUP information model is hierarchical. Individual Data Elements are the leaves of the model. They are aggregated into Data Element Groups, which are pre-defined sets of closely related Data Elements and/or other Data Element Groups. One or more Data Element Groups can in turn constitute a GUP Component, the top-level container of profile information. This layered structure allows the profile to be organized by domain (for example, service-related, user-related, or terminal-related information) while preserving a consistent, machine-readable representation at every level.

Each Data Element carries a defined data type and semantics, so that producers and consumers of GUP information — such as application servers, HSS/HLR functions, and UE-resident functions — interpret the data identically. Because the element is indivisible, operations such as reading, writing, or access-control decisions can be applied at element granularity, enabling fine-grained privacy and authorization policies. The GUP framework defines how these elements are described, discovered, and accessed through standardized interfaces, and TS 29.240 specifies the corresponding stage-3 protocol details.

The Data Element concept matters because interoperability of user profile data depends on a shared, unambiguous data model. Without a common definition of the smallest data unit, different implementations would represent the same information differently, making cross-domain and cross-vendor exchange error-prone. By anchoring the model on indivisible Data Elements, 3GPP ensures that profile information can be composed, versioned, and governed consistently.

In practice, a Data Element is referenced by its position within the GUP hierarchy and by its defined type. Access to it is mediated by GUP functions that enforce the applicable access rules. The definition of Data Element has remained stable across every release from Rel-8 through Rel-19, underscoring the maturity and stability of the GUP information model.

Purpose & Motivation

The Data Element exists to give the Generic User Profile a precise, interoperable foundation. Before GUP, user-related information in 3GPP networks was scattered across multiple entities and represented in heterogeneous, often proprietary formats. Different nodes held overlapping or conflicting views of subscriber data, and there was no standardized way to describe the smallest unit of that data. This made it difficult to share profile information reliably between the home network, visited networks, application servers, and the UE, and it complicated privacy management because access control could not be applied at a fine granularity.

By defining the Data Element as the indivisible unit of GUP information, 3GPP established a common vocabulary and data model. Every piece of profile information, no matter how simple, is expressed as a Data Element with defined semantics and type. This enables consistent interpretation across vendors and domains, supports composition into Data Element Groups and GUP Components, and allows access-control and privacy policies to be enforced at the finest possible level. It also provides a stable anchor for the stage-3 protocol definitions in TS 29.240.

The stability of the definition across twelve releases reflects that the concept solved its problem well: once the atomic unit of profile information is standardized, the surrounding framework can evolve — adding groups, components, and access mechanisms — without redefining the foundation. This longevity is itself evidence of the value of a well-scoped data-model primitive.

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 as 'the indivisible unit of Generic User Profile information', anchoring the GUP hierarchical data model with Data Element Groups and GUP Components.

Definition carried over unchanged; the Data Element remained the atomic unit of GUP information.

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, 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