Description
Far End Camera Control (FECC) is a service feature standardized by 3GPP as part of the Multimedia Telephony Service for IMS (MTSI) and other conversational video services. It defines a mechanism for a user in a point-to-point or multipoint video session to send control commands to remotely manipulate the camera at the far end. These commands typically include Pan (left/right movement), Tilt (up/down movement), Zoom (in/out), and potentially other camera-specific functions. The protocol operates over the signaling plane, often using SIP (Session Initiation Protocol) messages or as part of the media control channel, to ensure reliable and secure transmission of control commands separate from the media stream.
Architecturally, FECC involves several functional entities within the IMS and UE. The controlling UE generates FECC requests based on user input. These requests are formatted according to 3GPP specifications (e.g., using the XML format defined in TS 26.114) and transported via SIP INFO messages or as part of a BFCP (Binary Floor Control Protocol) stream in a centralized conferencing scenario. The request traverses the IMS core, potentially involving application servers, to the remote UE. The remote UE's MTSI client receives the request, interprets the commands, and interfaces with its local camera hardware or software API to execute the movement. The camera then feeds the new video perspective back into the media stream sent to the controlling user.
How it works involves a negotiation phase during session establishment. Capability exchange for FECC is performed using SIP/SDP (Session Description Protocol), where endpoints indicate support for FECC and the specific command sets (e.g., basic move, relative move, absolute move) they can handle. This ensures interoperability. During the session, a command is triggered by the controlling user, encoded into a defined syntax, and sent. The far-end device parses the command, applies security and authorization checks (e.g., verifying the sender is an authorized participant), and then executes the action. The feature is crucial for professional video conferencing, telepresence, and remote assistance scenarios, allowing a presenter or instructor to direct the camera view of a remote participant for a better collaborative experience.
Purpose & Motivation
FECC was created to address a key limitation in early video telephony and conferencing systems: the static or locally-controlled nature of the camera view. In scenarios like remote technical support, telemedicine, or distance learning, the expert or instructor often needs to see a specific detail or area from the remote site. Without FECC, they would have to verbally instruct the local user to physically adjust the camera, which is inefficient, prone to error, and disruptive. The purpose of FECC is to provide direct, precise remote control, improving communication efficiency and the overall user experience for interactive video services.
The motivation stems from the evolution of IMS-based telephony services beyond simple voice to rich multimedia communication. As 3GPP defined MTSI to compete with and enhance over-the-top services, incorporating advanced features like video quality adaptation and camera control became necessary to offer a premium, carrier-grade experience. FECC standardizes what was previously a proprietary feature in high-end telepresence systems, enabling interoperability between devices from different manufacturers within 3GPP ecosystems. It solves the problem of passive viewing in a collaborative session, transforming video calls into interactive visual collaborations.
Historically, before standardization, similar functionality existed in isolated systems using non-interoperable protocols. 3GPP's work, starting in Release 13, integrated FECC into the IMS framework, leveraging existing SIP signaling for control transport. This addressed the limitations of ad-hoc solutions by providing a secure, negotiated, and network-aware control channel. It enables new use cases such as remote surveillance (with consent), immersive education, and enhanced business conferencing, making video communication a more powerful tool for interaction rather than just observation.
Classification
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (2 CRs across 2 releases). Complements the general historical overview above with the evidence-based evolution of this function.
Studied in Rel-13, normative work from Rel-16.
In Release 16, the specification for the Far End Camera Control (FECC) function was updated by removing support for the legacy H.263 and MPEG-4 Visual codecs from the Multimedia Telephony Service for IMS (MTSI). This change streamlined the supported codec set for camera control. The update was part of a broader maintenance effort for the feature within the release.
- Removing H.263 and MPEG-4 Visual from MTSI TS 26.114CR0501
In Release 18, the new work for Far End Camera Control (FECC) specifically defined the protocol stack for the Multimedia Telephony Service for IMS (MTSI) User Equipment. This built upon the existing foundation which references the ITU-T H.281 protocol as the basis for far-end camera control in videoconferences. The update provided the necessary implementation details for UEs to utilize this control function within the IMS-based telephony service.
- Protocol Stack for MTSI UE TS 26.114CR0529
Explore further
Broader topics and technologies where FECC plays a role.
Defining Specifications
3GPP specifications that define or reference FECC, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 23.333 vj00 | MRFC-MRFP Mp Interface Requirements | Rel-19 |
| TS 23.334 vj00 | IMS-ALG to IMS-AGW Interface (Iq) Stage 2 | Rel-19 |
| TS 26.114 vj10 | IMS Multimedia Telephony Media Handling | Rel-19 |
| TS 29.162 vj00 | IMS-IP Network Interworking | Rel-19 |
| TS 29.238 vj00 | H.248 Profile for IBCF-TrGW Interface | Rel-19 |
| TS 29.333 vj00 | MRFC-MRFP Mp Interface Protocol | Rel-19 |
| TS 29.334 vj00 | IMS-ALG to IMS-AGW Interface Protocol | Rel-19 |