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

Glossary term · Services

Migration

Migration

Services →

Migration is the process for a mission-critical service user to obtain that service directly from a partner system when roaming or when their home system is unavailable.

Introduced
Rel-13
Where
Services › IMS
Specifications
3 specs
Migration Description Purpose What changed Neighbours Detected Changes Specifications

Description

In the context of 3GPP Mission Critical (MC) services, 'Migration' refers to the capability of an MC Service user to obtain MC service directly from a partner MC system. This allows a user to continue using mission-critical applications such as MCPTT (Mission Critical Push-to-Talk), MCVideo, or MCData even when they are outside the coverage of their home MC system or when their home system is temporarily unavailable. The partner MC system is a separate MC service provider that has a trust relationship and interoperability agreement with the user's home system.

Migration is a key feature for ensuring service continuity and resilience in mission-critical communications. It is defined in specifications such as TS 23.280 (Common functional architecture for MC services), TS 23.779 (Functional architecture and information flows for MC services), and TS 23.781 (Mission Critical Data). The mechanism involves the user's MC client discovering and registering with a partner MC system, which then provides the service. The home MC system may still be involved for authorization, policy, and charging, but the actual media and signalling may be handled by the partner system.

The concept evolved from the initial MCPTT-specific definition in Rel-13, where migration meant obtaining service from an MCPTT system where no MCPTT user profile exists for that user. This was later generalized to cover all MC services and to explicitly involve a partner MC system. The migration procedure typically includes steps such as service discovery, authentication and authorization with the partner system, and establishment of the necessary bearers and signalling connections. Security and privacy are paramount, so the partner system must verify the user's credentials and ensure that the user is authorized to receive the service.

Migration is distinct from roaming, although it may be used in roaming scenarios. While roaming typically involves the user's home network providing services through a visited network, migration allows the user to directly obtain services from a partner network, which may be necessary when the home network is not reachable or when the partner network offers better coverage or capabilities. This makes migration an essential tool for public safety and other mission-critical users who require reliable communications in all circumstances.

Purpose & Motivation

Migration exists to address the need for mission-critical service continuity when users are outside their home network's coverage or when their home network is unavailable. In public safety and other mission-critical scenarios, reliable communication is essential, and any interruption can have severe consequences. Traditional roaming may not be sufficient because it relies on the home network's involvement, which may be impossible if the home network is down or if there is no roaming agreement. Migration allows a user to directly obtain service from a partner MC system, ensuring that communication can continue.

The concept was introduced in Rel-13 as part of the initial MCPTT specifications. At that time, it was defined narrowly as obtaining service from an MCPTT system where no user profile exists. This addressed the scenario where a user from one MCPTT system needs to use another MCPTT system, perhaps during a large-scale incident where mutual aid is required. Over time, the definition was broadened to cover all MC services and to explicitly involve a partner MC system, reflecting the evolution of MC services from MCPTT to a suite of applications including MCVideo and MCData.

Migration solves the problem of interoperability between different MC service providers. It enables seamless service across organizational boundaries, which is crucial for multi-agency responses. It also provides a fallback mechanism when the home system is unavailable, enhancing the resilience of the overall MC service. By standardizing the procedures for migration, 3GPP ensures that different vendors' implementations can interoperate, which is vital for the success of mission-critical communications.

What changed in its specifications

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

TS 23.280Rel-18 → Rel-19

Rel-19 adds Enhanced Mission Critical Architecture changes, including location reporting trigger cancel and override indication. It also adds location reporting and location information request procedures for mission critical clients on non-3GPP devices behind a UE or 5G-RG.

Full comparison in TS 23.280 →

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

Specific changes extracted from the „Change history“ tables of 3GPP specifications (26 CRs across 5 releases). Complements the general historical overview above with the evidence-based evolution of this function.

Rel-15 8 changes
  • User profile retrieval for migration TS 23.280CR0075
  • Retrieval of migration credentials for access to SIP core / IMS of a partner MC system TS 23.280CR0066
  • Architecture requirements for migration TS 23.280CR0079
  • Network selection for EPC-level roaming to support migration TS 23.280CR0099
  • Defintions of interconnection, migration and MC gateway server TS 23.280CR0123
  • Signalling plane registration for MC UE migration TS 23.280CR0125

+ 2 more changes

Rel-16 2 changes
  • Migration connectivity information TS 23.280CR0179
  • Functional model update for interconnection and migration TS 23.280CR0220
Rel-18 7 changes
  • Migration during an ongoing group communication TS 23.280CR0315
  • Migration procedure during and ongoing private communication TS 23.280CR0330
  • Allow no roaming migration TS 23.280CR0331
  • Migration service de-authorization procedure initiated by MC service server TS 23.280CR0363
  • Updating migration overview TS 23.280CR0352
  • Terminology clean-up on the architectural requirements for migration TS 23.280CR0346

+ 1 more changes

Rel-19 6 changes
  • ACM user migration management TS 23.280CR0507
  • ACM updating MC service UE initial configuration for migration TS 23.280CR0508
  • Migration during Ad hoc group call procedure TS 23.280CR0580
  • Editor's note about migration vs recording TS 23.280CR0619
  • Including UE capabilities towards the partner MC system during migration TS 23.280CR0622
  • Potential IMS limitations based on deployment scenarios after migration TS 23.280CR0600
Rel-20 3 changes
  • Adding MCData to generic procedure for migration during an ongoing private communication TS 23.280CR0657
  • Adding MCData to generic procedure for migration during an ongoing group communication TS 23.280CR0658
  • MC gateway UE migration support TS 23.280CR0724

Defining Specifications

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

SpecificationTitleRelease
TS 23.280 vk51 Mission Critical Services Architecture Rel-20 read
TS 23.779 vd00 MCPTT over LTE Stage 2 Study Rel-13 read
TR 23.781 vf00 Study on MC services migration & interconnection Rel-15 read