Description
In 3GPP terminology, a Personalisation entity refers to the network, network subset, Service Provider (SP), Corporate, or (U)SIM to which a Mobile Equipment (ME) is personalised. This concept is defined in specification 21.905 and was introduced in Release 4. Personalisation is a mechanism that binds a mobile device to a specific entity, restricting its use to that entity unless unlocked. The Personalisation entity is the target of this binding.
The ME personalisation feature allows mobile operators, service providers, or corporations to subsidise or customise devices and ensure they are used only within their network or service environment. For example, a network operator may personalise a device to its network, meaning the device will only accept SIM cards from that operator. Similarly, a service provider may personalise a device to its services, or a corporation may personalise devices to its corporate network. The Personalisation entity is the entity to which the device is bound.
The personalisation entity can be one of several types: Network, Network Subset, Service Provider (SP), Corporate, or (U)SIM. Each type represents a different level or scope of personalisation. Network personalisation binds the device to a specific network operator. Network subset personalisation binds it to a subset of the network, such as a particular brand or region. SP personalisation binds it to a service provider. Corporate personalisation binds it to a corporate entity. (U)SIM personalisation binds it to a specific SIM or USIM card. These categories allow for flexible business models.
The personalisation mechanism is implemented in the ME and involves checks during startup or when a SIM is inserted. The ME compares the identity of the inserted SIM or the network with the personalisation entity stored in the ME. If they do not match, the ME may restrict services or refuse to operate. The personalisation can be unlocked by entering a code, often provided by the entity that personalised the device. This allows the device to be used with other entities after the contract or subsidy period.
The Personalisation entity concept is important for mobile network operators and service providers as it enables them to protect their investments in subsidised devices and ensure that users adhere to the terms of their contracts. It also provides a way for corporations to secure their mobile assets. From a user perspective, personalisation can be a limitation, but it often comes with benefits such as lower device costs. The concept has been maintained in 3GPP specifications with minimal changes, reflecting its stable role in device management.
In summary, the Personalisation entity is a key element in the ME personalisation framework, defining the entity to which a device is bound. It supports various business models and helps enforce contractual obligations. The term has been part of 3GPP since Release 4 and continues to be relevant in the era of multi-device and IoT, where device customisation and subsidy models remain prevalent.
Purpose & Motivation
The Personalisation entity concept was created to support the business needs of mobile network operators, service providers, and corporations that subsidise or customise mobile devices. Before personalisation, subsidised devices could be used with any SIM, leading to potential revenue loss for operators who invested in device subsidies. The Personalisation entity defines the target of the personalisation, allowing operators to lock devices to their networks or services.
The motivation for personalisation is to protect the investment of the entity that provides the device at a reduced cost. By binding the device to a specific network, network subset, service provider, corporate, or (U)SIM, the entity ensures that the device is used in accordance with the subsidy agreement. This is similar to SIM locking but at the device level, and it provides more flexibility in terms of the types of entities that can be targeted.
The Personalisation entity also addresses the need for corporations to manage their mobile assets. A corporation can personalise devices to its corporate network, ensuring that only authorised SIMs are used. This helps in maintaining security and policy compliance. The concept was introduced in Release 4 and has been maintained since, as it remains relevant for device subsidy and customisation models. It is a foundational element for mobile device management and operator business strategies.
What changed in its specifications
The latest release-to-release comparison of specifications that define Personalisation entity. Each summary describes the whole specification, not only this term.
Rel-18 brings only minor changes to TS 21.905: 0 clauses changed, with no change attributed to a release feature.
Full comparison in TR 21.905 →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 Personalisation entity, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TR 21.905 vj20 | 3GPP Terminology and Definitions | Rel-19 read |