MCX (MCPTT, MCVideo, MCData) in 4G and 5G Networks

Course outline : The realization of a critical telecommunications system requires the acquisition of three fundamental elements which form the technical heart of the critical communication infrastructure :
• capacity to access 4G radio coverage (then 5G) and telephony and internet services from some mobile network operators;
• the acquisition of the technical capacities of a virtual mobile network operator (MVNO), namely a "core network part" of the telecom network, an information system for managing the private network and its subscribers, a network and service operation center, and an offer of mobile terminals;
• the acquisition of a capacity to deliver mission critical communications (MCx), making it possible to organize group multimedia communications for the benefit of subscribers of the critical communications infrastructure while benefiting from a quality of service (QoS) with priority and preemption currtly in 4G networks and tomorrow in 5G networks.
This course presents MCX services including MCPTT for audio, MCVideo and MCData.

1.Mission Critical Communications (MCX)
1.1. Existing Tetra technology for supporting critical communications in a private network context
1.2. Place of MCX in PMR (Private Mobile Communication)
1.3. 4G/5G private network for MCX versus traditional 4G/5G public network
1.4. MCX 4G QoS versus traditional 4G QoS
1.5. 4G Network Setup for MCX
1.6. Example of MCX usage in the context of FRMCS (Future Railway Mobile Communication System)
1.6.1. FRMCS Requirements
1.6.2. FRMCS Features
1.6.3. Frequency issues for migration from GSM-R to FRMCS
1.6.4. Onboard System Architecture
1.6.5. FRMCS and 5G
1.6.6. Adoption of MCX for FRMCS

2. The MCX architecture
2.1. MCX Server (MCPTT server, MCVideo server, MCData server)
2.1.1. Participating Function
2.1.2. Controlling Function
2.1.3. Non-Controlling Function
2.2. Identity Management Server
2.3. Configuration Management Server
2.4. Key Management Server
2.5. Group Management Server
2.6. MC Gateway Server for interconnection between MCX systems
2.7. MCX Database

3. MCPTT registration procedure
3.1. Identity MC
3.2. Identity MCPTT
3.3. SIP identity (i.e., IMPU) versus MCPTT identity
3.4. MCPPT Customer ID
3.5. SIP/IMS registration versus MCPTT registration

4. MCPTT
4.1. Interfaces Between MCPTT Client and MCPTT Server
4.2. Private MCPTT call
4.3. Group MCPTT call
4.4. Broadcast group MCPTT call
4.5. MCPTT emergency or emergency group call
4.6. Imminent peril group call
4.7. Pre-established call versus on-demand call
4.8. Automatic call versus manual call
4.9. Floor Control
4.10. SIP, RTP and RTCP for the support of MCPTT communications
4.11. QoS for MCPTT sessions
4.12. Rx interface for dynamically requesting establishment of dedicated bearer for voice

5.MCData
5.1. Interfaces between MCData client and MCData server
5.2. Signaling protocol to support MCData services
5.3. Media protocol to support MCData services
5.4. SDS : Short Data Service
5.4.1. Standalone one-to-one and group Short Data Service (SDS) via SIP signaling
5.4.2. Standalone one-to-one and group SDS via user plane
5.4.2.1. MSRP protocol for the exchange of SDS on the user plane
5.4.3. One-to-one SDS session and group SDS session
5.4.4. Delivery and read notifications
5.5. FD : File Distribution
5.5.1. One-to-one and group File Distribution (FD) via HTTP
5.5.2. One-to-one and group FD via user plane
5.6. Data Streaming
5.7. IP Connectivity
5.8. QoS associated with MCData services
5.9. Rx interface for dynamically requesting establishment of dedicated bearer for data

6.MCVideo
6.1. Interfaces between MCVideo Client and MCVideo Server
6.2. Private MCVideo call
6.3. Group MCVideo call
6.4. MCVideo broadcast group call
6.5. Emergency private and group MCVideo call
6.6. Imminent peril Group MCVideo call
6.7. Video pull
6.8. video push
6.9. Transmission Control protocol for floor control in the context of MCVideo
6.10. SIP, RTP and RTCP for supporting MCVideo communications
6.11. QoS associated with MCVideo services
6.12. Rx interface dynamically requesting establishment of dedicated bearer for video