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

Glossary term · Security

Home Security Domain

Home Security Domain

Security →

Home Security Domain is the primary security domain of an MCX user, anchoring authentication, key management, and authorization in the user's home network as the trust root for secure access to MCX services.

Introduced
Rel-14
Where
Security
Specifications
2 specs
Home Security Domain Description Purpose What changed Specifications

Description

The Home Security Domain (HSD) is a foundational security concept in the 3GPP Mission Critical Services (MCX) architecture, covering MCPTT, MCVideo and MCData. It represents the security domain in which an MCX user is permanently provisioned and from which the user's security credentials, identities and authorization policies originate. In practice, the HSD is realized by the home MCX network infrastructure — the home MC service provider's security functions, including the key management server (KMS), the identity and authorization functions, and the MC service configuration data that binds a user to their home domain.

Architecturally, the HSD is the counterpart to the visited or serving security domain. When an MCX user roams or accesses services through a partner or visited network, the serving domain must establish a trust relationship with the HSD in order to authenticate the user and obtain the material needed to protect MCX signalling and media. The HSD therefore acts as the authoritative source for user authentication, for the generation and distribution of security keys, and for the authorization decisions that determine which MCX services and groups the user may access. The security architecture in TS 33.180 defines how these functions interact, including the key hierarchy used to protect MCX signalling, media and group communications.

The HSD is closely tied to the MCX identity model. Each MCX user has a home MCX identity and is associated with a home MC service provider. The HSD holds the subscription and security context for that identity. When the user registers with an MCX service, the serving functions consult the HSD (directly or through trust relationships) to validate the user, derive or retrieve the appropriate keys, and confirm the user's service authorizations. This separation of home and serving domains mirrors the home/visited model familiar from cellular roaming and enables MCX interoperability between different operators and agencies.

Key management in the HSD is central to protecting group communications. MCX group calls require that media be encrypted so that only authorized group members can decrypt it. The HSD, through its key management functions, is responsible for generating and distributing the group keys and for ensuring that only authorized participants receive them. This is especially important in mission critical contexts where group membership and authorization can change dynamically and where security must hold even when users are served by different networks.

The HSD concept was introduced in Release 14 as part of the first MCX security specifications and has remained stable through subsequent releases. Its definition has not changed across Rel-14 to Rel-20, reflecting the maturity and stability of the underlying security architecture. Understanding the HSD is essential for engineers designing or operating MCX systems, because it defines where trust originates and how secure, interoperable mission critical communication is achieved across organizational and network boundaries.

Purpose & Motivation

Mission critical communications demand strong, interoperable security across organizational and network boundaries. Before the HSD concept, MCX security lacked a clear architectural anchor for where a user's credentials, keys and authorizations live, making roaming and multi-operator interoperability difficult to secure consistently. The HSD was created to provide that anchor: a well-defined primary security domain that owns the user's security context and serves as the authoritative trust root.

The HSD solves the problem of securely extending MCX services beyond a single network. When a user is served by a visited or partner domain, the serving domain needs a trustworthy way to authenticate the user and obtain keys without holding the user's long-term secrets itself. By defining the HSD as the source of authentication, key management and authorization, 3GPP enabled a home/visited trust model analogous to cellular roaming, allowing agencies and operators to interoperate while keeping security control with the home provider.

It also addresses the security of group communications. MCX group calls require shared keys distributed only to authorized members. The HSD, through its key management functions, provides a single authoritative point for generating and distributing those keys, ensuring that group media remains protected even as membership and serving networks change. This motivation — secure, scalable, interoperable mission critical communication — is why the HSD definition has remained stable across releases.

What changed in its specifications

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

TS 33.180Rel-18 → Rel-19

Rel-19 adds recording admin and replay access-token claims to TS 33.180 and removes the MC user event audit and service media collection text. It also adds Annex B recommendations on client registration, authentication request handling, public key distribution, and Issuer claim verification of the access token.

Full comparison in TS 33.180 →

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-14 Initial

Introduced the Home Security Domain as the MCX user's primary security domain within the first MCX security architecture (TS 33.180), establishing the trust root for authentication, key management and authorization.

Definition carried over unchanged; the HSD concept remained stable as MCX security architecture matured.

Definition carried over unchanged; the HSD continued as the primary security domain for MCX users.

Definition carried over unchanged; no revision to the HSD definition text.

Definition carried over unchanged; the HSD remained the MCX user's primary security domain.

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

Definition carried over unchanged; the HSD concept remains stable in the latest release.

Defining Specifications

3GPP specifications that define or reference Home Security Domain, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TS 33.180 vk10 Security of the Mission Critical Service (MCX) Rel-20 read
TS 33.880 vf10 Security Study for Enhanced Mission Critical Services Rel-15 read