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

Glossary term · Security

De-personalisation

De-personalisation

Security →

De-personalisation is the process of deactivating personalisation in Mobile Equipment to stop verification checks, allowing it to be used with any SIM card and removing operator restrictions.

Introduced
Rel-4
Where
Services
Specifications
1 specs
De-personalisation Description Purpose What changed Neighbours Specifications

Description

De-personalisation is a security-related procedure in 3GPP specifications that allows a Mobile Equipment (ME) to be freed from personalisation restrictions. Personalisation refers to the configuration of an ME to only accept specific types of SIM cards or to operate only with a particular network operator. When an ME is personalised, it performs verification checks (e.g., comparing the SIM's IMSI or operator identifier with a stored list) before allowing normal operation. De-personalisation is the process of deactivating these checks, enabling the ME to accept any SIM card and operate on any compatible network.

The concept of personalisation and de-personalisation is defined in 3GPP TS 21.905 (Vocabulary for 3GPP Specifications). Personalisation is typically used by operators to subsidise handsets, ensuring that the device is used only on their network for a certain period. De-personalisation can be performed by the operator (e.g., after the contract period) or by the user using a special code (e.g., a SIM unlock code). The process involves modifying the ME's internal configuration to remove or disable the personalisation checks.

De-personalisation can be categorised into different types based on the level of personalisation: network personalisation, network subset personalisation, service provider personalisation, corporate personalisation, and SIM/USIM personalisation. Each type restricts the ME to a specific network, service provider, or SIM. De-personalisation removes these restrictions, either partially or completely, depending on the type. For example, network de-personalisation allows the ME to accept SIMs from any network, while service provider de-personalisation allows SIMs from any service provider.

The de-personalisation process is usually controlled by the operator and may require a de-personalisation code (e.g., a 16-digit code) that is entered into the ME. The ME verifies the code and, if correct, deactivates the personalisation. The process is defined in 3GPP specifications to ensure interoperability and security. It is important to note that de-personalisation does not affect the SIM card itself; it only modifies the ME's behaviour.

In summary, de-personalisation is a security mechanism that allows a personalised ME to be unlocked for use with any SIM card. It is a standardised procedure that ensures flexibility for users and operators while maintaining security during the personalisation period.

Purpose & Motivation

De-personalisation exists to provide flexibility and control over Mobile Equipment (ME) usage. When operators subsidise handsets, they often personalise them to ensure the device is used on their network for a minimum period, protecting their investment. However, after the contract period or under certain conditions, users may want to use the device with other SIM cards. De-personalisation allows this transition, enabling the ME to be reused or sold.

The concept addresses the need for a standardised method to remove personalisation restrictions without compromising security. It ensures that only authorised parties (e.g., the operator or the user with a valid code) can de-personalise the device. This prevents unauthorised unlocking and maintains the integrity of the subsidy model.

Historically, personalisation was introduced in early mobile networks to support operator subsidies. De-personalisation was defined in 3GPP specifications to provide a clear, interoperable procedure for unlocking devices. It has evolved over releases, but the fundamental purpose remains the same: to allow MEs to be freed from operator-specific restrictions in a controlled manner.

What changed in its specifications

The latest release-to-release comparison of specifications that define De-personalisation. Each summary describes the whole specification, not only this term.

TR 21.905Rel-17 → Rel-18

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.

Rel-4 Initial

Initial definition: 'Is the process of deactivating the personalisation so that the ME ceases to carry out the verification checks.' This release established the basic concept of de-personalisation as a security procedure.

The definition carried over unchanged from Rel-4. No technical changes were made to the de-personalisation concept.

The definition carried over unchanged from Rel-5. The de-personalisation procedure remained stable.

The definition carried over unchanged from Rel-6. No changes to the de-personalisation definition.

The definition carried over unchanged from Rel-7. The de-personalisation concept continued to be used as specified.

The definition carried over unchanged from Rel-8. No technical changes were made.

The definition carried over unchanged from Rel-9. The de-personalisation procedure remained the same.

The definition carried over unchanged from Rel-10. No changes to the de-personalisation definition.

The definition carried over unchanged from Rel-11. The de-personalisation concept continued to be used as specified.

The definition carried over unchanged from Rel-12. No technical changes were made.

The definition carried over unchanged from Rel-13. The de-personalisation procedure remained the same.

The definition carried over unchanged from Rel-14. No changes to the de-personalisation definition.

The definition carried over unchanged from Rel-15. The de-personalisation concept continued to be used as specified.

The definition carried over unchanged from Rel-16. No technical changes were made.

The definition carried over unchanged from Rel-17. The de-personalisation procedure remained the same.

The definition carried over unchanged from Rel-18. No changes to the de-personalisation definition.

Defining Specifications

3GPP specifications that define or reference De-personalisation, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TR 21.905 vj20 3GPP Terminology and Definitions Rel-19 read