Description
The Front End Identifier (FE ID) is an identifier defined in 3GPP TS 23.335 and TS 29.335 within the User Data Convergence (UDC) architecture. UDC separates the data layer, represented by the User Data Repository (UDR), from the application logic layer, represented by Front Ends (FEs). Each FE is an application server (for example an HSS, an HLR- FE, or an application FE) that accesses subscriber data stored in the shared UDR. The FE ID is the name that uniquely identifies a given FE within the set of all FEs that access a particular UDR, allowing the UDR to attribute data, subscriptions, and operations to the correct FE instance.
Architecturally, the UDC model introduces a Ud reference point between FEs and the UDR. Over this interface, FEs use the FE ID to identify themselves when they register, when they create or modify subscription data, and when they subscribe to notifications about data changes. Because a single UDR may serve multiple FEs of different types (and multiple instances of the same type), the FE ID provides the necessary namespace separation so that data owned or managed by one FE is not confused with data from another.
The FE ID is used in several procedures. When an FE connects to the UDR, it provides its FE ID so the UDR can associate the connection with a known FE. When an FE creates data records, the UDR can store the identity of the creating FE alongside the data, which supports auditing, ownership, and conflict resolution. Subscription and notification mechanisms also rely on the FE ID so that change notifications are delivered only to FEs that have registered interest in the affected data.
In terms of format, the FE ID is a name (a string-based identifier) rather than a numeric identifier. This makes it human-readable and administratively manageable, and it aligns with the naming conventions used elsewhere in the UDC specifications. The uniqueness scope is explicitly limited to the set of FEs accessing a given UDR, meaning the same FE ID value could in principle be reused across different UDRs without conflict.
The FE ID has remained stable across Releases 9 through 19. Its definition has not changed since it was introduced, reflecting the maturity and stability of the UDC architecture itself. For engineers implementing UDC-based deployments, the FE ID is a fundamental configuration parameter that must be planned and provisioned consistently between the FE and the UDR.
Purpose & Motivation
The FE ID exists to solve the identity and namespace problem inherent in the User Data Convergence architecture. UDC was created to consolidate subscriber data that had historically been duplicated across separate databases for HSS, HLR, application servers, and other functions. By centralizing data in a single UDR, operators reduce data inconsistency and simplify provisioning. However, centralization creates a new challenge: the UDR must serve many different Front Ends, each with its own view of and responsibility for portions of the data.
The FE ID addresses this by giving every FE a unique name within the UDR's scope. Without such an identifier, the UDR could not reliably determine which FE created or owns a data record, which FE should receive a notification, or which FE is responsible for a given data schema. This is especially important in multi-vendor and multi-application environments where several FEs from different suppliers share one repository.
The identifier also supports operational concerns such as troubleshooting and auditing. Because data records can be associated with the FE that created them, operators can trace the origin of configuration or subscription changes. The stability of the FE ID definition from Rel-9 onward demonstrates that the original design adequately addressed these requirements without needing revision.
What changed in its specifications
The latest release-to-release comparison of specifications that define Front End Identifier. Each summary describes the whole specification, not only this term.
TR 29.935 reference added to the data model. Integration projects noted for multivendor interoperability.
Full comparison in TS 29.335 →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.
Defining Specifications
3GPP specifications that define or reference Front End Identifier, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 23.335 vj00 | User Data Convergence (UDC) Procedures | Rel-19 read |
| TS 29.335 vj00 | Ud Interface Protocol for UDC (Stage 3) | Rel-19 read |