Description
The Basic Communication Part (BCP) is a core protocol entity defined within the 3GPP Mission Critical Services (MCS) architecture, specifically for the Mission Critical Push to Talk (MCPTT) service. It operates at the application layer and is responsible for managing the fundamental signaling and media flows for MCPTT sessions. BCP is implemented within both the MCPTT client (in the User Equipment) and the MCPTT server (in the network). Its primary function is to handle the call control procedures for group calls, private calls, and emergency calls, which are the foundational communication modes for public safety personnel.
Architecturally, BCP interacts with other MCPTT functional components, such as the MCPTT Application Server and the Floor Control Part (FCP). While BCP manages the overall session establishment (e.g., inviting participants, negotiating codecs), the FCP manages the arbitration of who has the right to speak (the "floor") during a session. BCP uses SIP (Session Initiation Protocol) as its underlying signaling protocol, as defined in 3GPP TS 24.229, and RTP/RTCP for media transport. It defines specific SIP methods, headers, and message bodies to carry MCPTT-specific information, such as group identifiers, user priorities, and call types.
The protocol works by processing SIP INVITE requests for initiating calls, BYE requests for terminating calls, and various mid-session requests. For a group call, the BCP in the initiating client sends a SIP INVITE containing the target group ID to the network's MCPTT server. The server's BCP then processes this request, potentially performing authorization checks, and is responsible for forking the invitation to all members of the group or managing a pre-established group session. It handles responses, manages session timers, and coordinates with media plane functions to ensure the voice packets are routed correctly to all authorized participants.
Key components of the BCP specification include the detailed state machines for the client and server, the definition of MCPTT-specific SIP URI parameters and header fields, and the procedures for handling abnormal events like pre-emption (where a higher priority user takes over the floor) or network detachment. Its role is foundational; without BCP, the basic call connectivity for MCPTT would not exist. It provides the standardized "handshake" that allows disparate vendors' MCPTT clients and servers to interoperate, which is a critical requirement for public safety networks where equipment from multiple suppliers must work together seamlessly during emergencies.
Purpose & Motivation
BCP was created to solve the critical need for a standardized, interoperable protocol for push-to-talk voice communications within LTE and 5G networks for public safety and mission-critical users. Prior to 3GPP standardization, professional mobile radio (PMR) systems like TETRA and P25 provided similar functionality but were based on narrowband, circuit-switched technology with limited data capabilities and often proprietary implementations. The motivation was to leverage the high bandwidth, low latency, and economies of scale of commercial 3GPP networks (LTE/5G NR) to deliver advanced mission-critical services while ensuring guaranteed reliability, security, and functionality.
The specific problem BCP addresses is the lack of a unified call control protocol for MCPTT. Without a standard like BCP, each vendor would implement their own signaling methods for setting up group calls, leading to fragmentation and an inability for different agencies or organizations to communicate during joint operations. BCP, as part of the broader 3GPP MCPTT standard, provides this common language. It defines exactly how a call is initiated, how participants are added, and how the session is managed, ensuring that an MCPTT client from vendor A can successfully establish a group call through an MCPTT server from vendor B.
Furthermore, BCP enables the integration of advanced IP-based telephony features (inherited from SIP) into the mission-critical domain, such as presence, instant messaging, and location integration, while adding the necessary public safety extensions like user prioritization, pre-emption, and inherent security. It was a key enabler for the transition from legacy LMR (Land Mobile Radio) systems to broadband-based Mission Critical Communications over LTE/5G, often referred to as MCX (Mission Critical Services).
Key Features
- Standardized SIP-based call control for MCPTT group, private, and emergency calls
- Defines specific SIP methods, headers, and message bodies for MCPTT parameters (e.g., group ID, MCPTT service type)
- Manages session establishment, modification, and termination procedures between MCPTT client and server
- Interworks with the Floor Control Part (FCP) for coordinated call and floor management
- Supports essential mission-critical features like pre-emption, priority, and imminent peril calls
- Provides state machines and procedures for handling abnormal network and client conditions
Evolution Across Releases
Introduced as the foundational call control protocol for the first 3GPP standardized Mission Critical Push to Talk (MCPTT) service in TS 24.275. It defined the initial architecture where BCP in the client and server uses SIP to establish, manage, and release MCPTT call sessions. Key initial capabilities included support for group calls, private calls, emergency calls, and basic session management procedures integrated with the newly defined Floor Control Part.
Defining Specifications
| Specification | Title |
|---|---|
| TS 24.275 | 3GPP TS 24.275 |