Controller capable User Equipment

Description

The Controller capable UE is a concept introduced in 3GPP Release 10 to distinguish devices that have the technical capability to assume the role of a Controller UE in a Collaborative Session. While the Controller UE is the device actively controlling the session, a Controller capable UE is any device that could potentially take on that role, given the right conditions. This distinction is important for network operations, as it allows the network to know which devices can be considered for session control, especially in scenarios involving session transfer or device switching.

In the Collaborative Session architecture, the Controller UE is responsible for managing the session and determining the services on the remote leg based on its service profile. The Controller capable UE, therefore, must support the necessary protocols and procedures to perform these functions. This includes the ability to handle SIP signaling for session control, manage the IUT procedures, and interact with the SCC AS. The capability to become a Controller UE is not automatically granted to all devices; it depends on the device's implementation and the services it supports. For example, a simple media player might only be capable of being a Controllee UE, while a smartphone with advanced IMS capabilities could be Controller capable.

The introduction of the Controller capable UE concept in Release 10 was driven by the need to support more dynamic Collaborative Sessions. In earlier releases, the Controller UE was typically fixed for the duration of the session. However, as users demanded more flexibility—such as transferring session control from one device to another—the network needed a way to identify which devices could accept the Controller role. The Controller capable UE provides this identification, enabling procedures like Controller UE transfer, where the role of the Controller UE is moved from one device to another. This is particularly useful when a user wants to switch from using a smartphone to a tablet for controlling a video session.

Technically, the Controller capable UE is defined in 3GPP specifications 24.337 and 24.837, which cover IMS IUT and related procedures. These specifications outline the signaling flows and requirements for a UE to be considered Controller capable. The capability is typically indicated during registration or session establishment, allowing the SCC AS to make informed decisions about session control. The Controller capable UE may also need to support additional features such as service profile management and remote leg control, which are essential for the Controller UE role.

Since its introduction, the definition of Controller capable UE has remained stable across releases up to Rel-19. This stability reflects the maturity of the concept and its continued relevance in multi-device scenarios. As networks evolve towards 5G and beyond, the principles of Collaborative Sessions and device capability differentiation remain important for delivering seamless user experiences. The Controller capable UE is a key enabler for advanced session control features, ensuring that only devices with the necessary capabilities can take on the responsibilities of session control.

Purpose & Motivation

The Controller capable UE concept was introduced to address the limitations of static session control in early IMS Collaborative Sessions. In Release 9, the Controller UE was defined as the device controlling the session, but there was no formal way to identify other devices that could potentially take on that role. This lack of flexibility hindered the development of features like session transfer between devices, where the user might want to move control from one device to another. The Controller capable UE solves this problem by providing a clear capability indicator, allowing the network to know which devices are eligible to become Controller UEs.

The primary motivation for this concept was to enable dynamic reconfiguration of Collaborative Sessions. Without it, the network would have to assume that only the original Controller UE could control the session, limiting the user's ability to switch devices. By defining Controller capable UEs, 3GPP enabled procedures for Controller UE transfer, where the session control can be handed over to another device that is capable of assuming the role. This enhances user experience by allowing seamless transitions between devices, such as moving from a mobile phone to a tablet when a larger screen is preferred.

Historically, the introduction in Release 10 coincided with the evolution of IUT procedures and the need for more sophisticated session management. The specifications 24.337 and 24.837 were developed to detail the IMS aspects of IUT, including the identification of Controller capable UEs. The concept has since been maintained without change, indicating that the original design was robust and sufficient for subsequent releases. As multi-device usage continues to grow, the Controller capable UE remains a foundational element for flexible session control in IMS networks.