Hardened VoIP system
View Patent ↗A hardened VoIP system is presented that includes secure push-to-talk voice functionality. Through the addition of encryption, authentication, user filtering, and integration with the new and existing LMR systems, a secure voice platform ensures malicious software, unauthorized access and brute force security attacks will not compromise the voice communications of the system. The VoIP system is engineered to ensure graceful system degradation in the event of maintenance activities, natural disasters and failure modes. The hardened VoIP system offers the functions a LMR trunking system while utilizing broadband connections. Private calls, group calls, Emergency Alarms with covert monitoring capability, scanning and priority scanning may be incorporated into the system. The system includes a VoIP controller that serves as a trunking controller, manages available VoIP based conference bridges, and assigns them as needed to the parties involved in each voice call.
1. A system for providing hardened VoIP and land mobile radio communication services to mobile devices, the system comprising:
a controller configured
in a first standby state to
receive via a cellular communications system
a first heartbeat signal from a first mobile device and
a second heartbeat signal from a second mobile device,
transmit via the cellular communications system
a first status control signal to the first mobile device and
a second status control signal to the second mobile device, and
maintain a database with
a first identifier associating the first mobile device with the cellular communications system and
a second identifier associating the second mobile device with the cellular communications system;
in a second standby state to
receive via the cellular communications system
the second heartbeat signal from the second mobile device,
transmit via the cellular communications system
the second status control signal to the second mobile device,
monitor a channel of a land mobile radio system associated with the first mobile device, and
maintain the database with
the first identifier associating the first mobile device with the land mobile radio system and
the second identifier associating the second mobile device with the cellular communications system; and
to transition from the second standby state to the first standby state upon receiving the heartbeat signal from the first mobile device.
2. The system of claim 1 further comprising
the controller configured
in a first communication state to
coordinate receipt, at a first VoIP switch, of a first communication from the first mobile device, and
coordinate transmission, at the first VoIP switch, of the first communication to the second mobile device; and
transition from the first standby state to the first communication state upon receipt, in the first standby state, of a push-to-talk initiation signal from the first mobile device.
3. The system of claim 2 further comprising
the controller configured
in a second communication state to
coordinate receipt, at an RoIP gateway, of a second communication from the first mobile device via the channel of the land mobile radio system associated with the first mobile device, and
coordinate transmission, at the first VoIP switch, of the second communication to the second mobile device; and
transition from the second standby state to the second communication state upon receipt, in the second standby state, of a push-to-talk land mobile radio signal from the first mobile device.
4. The system of claim 3 further comprising
the controller configured to transition from the first communication state to the second communication state upon a degradation of the first communication from the first mobile device.
5. The system of claim 3 wherein
the RoIP gateway converts the second communication from a LMR protocol to a VoIP protocol, and the
RoIP gateway includes a first rack with a first module and a second module;
the first mobile device and the second mobile device are in a first talk group associated with the first module; and
a third mobile device and the fourth mobile device are in a second talk group associated with the second module.
6. The system of claim 5 wherein
the controller is configured
in the first communication state to
coordinate transmission, at the first VoIP switch, the first communication to a first plurality of mobile devices of the first talk group; and
coordinate transmission, at the RoIP gateway, the first communication to a second plurality of mobile devices of the first talk group.
7. The system of claim 6 wherein
the database, in the first communication state, associates
each of the first plurality of mobile devices with the cellular communications system and
each of the second plurality of mobile devices with the land mobile radio system.
8. The system of claim 5 further comprising:
a console client specifically configured for reassigning the first mobile device from the first talk group to the second talk group.
9. The system of claim 8 wherein
the first talk group is a police talk group, and the second talk group is a fire talk group.
10. The system of claim 2 wherein
the first status control signal includes an identifier of the channel of the land mobile radio system associated with the first mobile device.
11. The system of claim 2 wherein
the transition from the first standby state to the first communication state includes a Session Initiation Protocol initiating a Real-time Transport Protocol between the first mobile device and the second mobile device.
12. The system of claim 1 wherein
the first mobile device includes a land mobile radio connected to both an intelligent vehicle network and a cellular communication device via a Universal Mobile Access Radio Link Control module.
13. A method of providing hardened mobile VOIP and LMR services, the method comprising:
in a first state
transmitting a status signal via a cellular data channel to a first mobile device,
receiving a heartbeat signal via the cellular data channel from the first mobile device,
monitoring a first land mobile radio channel for a first communication from a second mobile device, and
associating, in a database, an identifier of the first mobile device with cellular data communications;
in a second state
monitoring the first land mobile radio channel for a first communication from the first mobile device and second mobile device, and
associating, in the database, the identifier of the first mobile device with land mobile radio communications;
transitioning from the second state to the first state upon receiving the heartbeat signal from the first mobile device;
transitioning from the first state to a third state upon receipt of a push-to-talk signal via the cellular data channel from the first mobile device;
in the third state
receiving, via the cellular data channel, a communication from the first mobile device,
converting the communication from a VoIP format to LMR format, and
transmitting the communication to a second mobile device via a land mobile radio format.
14. The method of claim 13 wherein
transitioning from the first state to the third state further includes establishing a hosted conference bridge between the first mobile device and the second mobile device.
15. The method of claim 13 further comprising
receiving a configuration signal from a dispatcher client; and
in response to receipt of the configuration signal
disassociating the first mobile device from a first talk group and
associating the first mobile device with a second talk group.
16. The method of claim 13 further comprising
transitioning from the first state to a fourth state upon detection of a push-to-talk signal on the first land mobile radio channel;
in the fourth state
receiving, via the first land mobile radio channel, a communication from the second mobile device,
converting the communication from an LMR format to a VoIP format, and
transmitting the communication to first mobile device via the cellular data channel.
17. The method of claim 13 further comprising
transitioning from the first state to a fifth state upon receipt of a shut-down notice from the first mobile device; and
in the fifth state
associating, in the database, the identifier of the first mobile device with inactive communications.
18. The method of claim 17 further comprising
in the fifth state
providing an active device list to a dispatcher client, the active device list indicating the first mobile device is inactive.
19. The method of claim 13 , wherein
in the first state
transmitting the status signal via the cellular data channel to the first mobile device includes transmitting the status signal from a first VoIP controller, and
receiving the heartbeat signal via the cellular data channel from the first mobile device includes receiving the heartbeat signal at a second VoIP controller located at least 10 miles away from the first VoIP controller.