This invention relates generally to land mobile radios, and more particularly, to a system for providing land mobile radio (LMR) services using multiple LMR communication protocols.
Land mobile radios may be used to provide communication between different mobile units, for example, land mobile radios in different vehicles. Land mobile radio band communication, for example, public safety radio communication (e.g., police, fire department, etc.) is generally available within the VHF, UHF, 700 MHz and 800 MHz frequency bands. Part of each of these frequency bands is allocated by the Federal Communications Commission (FCC) for public safety communication services and are also referred to as Public Safety Frequency Bands. These communications also may be provided using private land mobile radio services (PLMRS).
Traditionally, LMR networks have been used to provide mission critical applications such as public safety communications. In addition to providing a very high level of system availability, LMR networks are designed to support PTT services, such as a dispatch mode of operation. These LMR systems use specialized LMR airlink protocols to communicate wirelessly between LMR radios and the LMR infrastructure.
Known LMR systems use a single protocol for the various layers in the communication protocol stack. For example, the same protocol must be used for both a transport layer and an application layer of the protocol stack. Further, when trying to interconnect multiple systems, with each system using a different protocol, transcoding and trascryption of the communicated LMR content is needed. Thus, design of these systems may result in sub-optimal performance and the cost of these systems may be increased.
In one exemplary embodiment, a method for communicating land mobile radio (LMR) content is provided. The method includes communicating the LMR content using a plurality of LMR transport protocols within a single LMR network. The method further includes encapsulating the LMR content based on an LMR application layer protocol for a portion of the single LMR network through which the LMR content is to be communicated.
In another exemplary embodiment, a wireless communication system is provided that includes a land mobile radio (LMR) infrastructure configured to communicate with a plurality of LMR units within a plurality of coverage areas of an LMR system. At least some of the plurality of coverage areas have different transport protocols. The wireless communication system further includes an interface configured to process received LMR content that is communicated using a first LMR transport protocol and reencapsulate the LMR content for communication using a second LMR transport protocol.
In yet another exemplary embodiment, a land mobile radio (LMR) unit is provided that includes at least one voice encode/decoder and a plurality of modems connected to the at least one voice encoder/decoder. The plurality of modems are each configured to communicate using a different LMR transport protocol.
Various embodiments of the invention include a system for providing land mobile radio (LMR) content, for example, LMR services via an LMR network using multiple communication protocols. More particularly, multiple LMR transport layer protocols are used to communicate LMR that can retain a single LMR application layer protocol.
It should be noted that when reference is made herein to LMR content, this refers generally to any type or kind of LMR voice and/or data content, and may define particular LMR services, operations, controls, etc. For example, the LMR content may include, but is not limited to, voice data, emergency signal data, control data relating to selecting a particular talk group, LMR data for transfer between a radio unit and a server, reprogramming data (e.g., software upgrade data), etc.
Specifically, as shown in
In various embodiments, the communication protocol provided by different base stations and associated communication towers 24 may be different. More particularly, the transmission protocol, and specifically, a transport layer protocol is different for some of the base stations and associated communication towers 24. For example, one base station and associated communication tower 24 may use a Terrestrial Trunked Radio (TETRA) transport protocol (e.g., ETSI TETRA standard) for the RF coverage area of that base station and associated communication tower 24 and another base station may use a P25 transport protocol (e.g., Project 25 (TIA 102) standard) for the RF coverage area of that base station and associated communication tower 24. It should be noted that some of the base stations and associated communication towers 24 may use the same transport protocol. Additionally, it should be noted that other types of LMR communication protocols and standards may be used, including, for example, M/A-COM OpenSky and EDACS protocols.
In operation, each of the LMR units is configured to communicate LMR content via the LMR communication system 20 using different communication protocols. In particular, and as described in more detail herein, the LMR units select between one of a plurality of transport layer protocols for use in communicating the LMR content (that may be different than an application layer protocol). The LMR content is then configured for communication using the selected communication protocol, and more particularly, encapsulated based on the selected communication protocol. Additionally, different application layer protocols may be used.
The LMR communication system 20 may include one or more communication areas 30, a portion of one communication area is shown in
Various embodiments enable end-to-end LMR services to be provided over a plurality of protocols, for example, a plurality of radio and/or airlink protocols. In general, an LMR unit 40 (also referred to as an LMR terminal) as shown in
More particularly, the LMR unit 40 includes a plurality of modules or components configured to provide communication via the LMR network 42. Specifically, the LMR unit 40 includes an LMR application module 46 connected to an LMR transport module 48 together provided for configuring voice and/or data for communication via the LMR network 42 (having one or more LMR base stations 44) using an LMR transmitter/receiver 50, which may be separate units or provided as a single transceiver. The LMR unit 22 further includes an LMR encapsulation module 50 connected between the LMR transport module 48 and the LMR transmitter receiver 50 for encapsulating the voice and/or data for communication using one of a plurality of communication protocols. The LMR transport module 48, the LMR encapsulation module 52 and the LMR transmitter/receiver 50 generally define a multiple protocol communication portion 54.
The LMR unit 40 may include additional components, for example, an antenna (not shown) for use in transmitting and receiving signals as is known. Additionally, and for example, the LMR unit 40 may include filters (not shown), such as a receive filter and a transmit filter for filtering signals that are received and transmitted, respectively, by the LMR unit 40. The LMR unit 40 also may include components for processing LMR content and for interfacing with a user. For example, a processor 56 connected to a memory 58 may be configured to receive the different LMR content and based on a user input 60 or other information (e.g., configuration or protocol description information in the LMR content signal) determine the manner is which to encapsulate or decapsulate the LMR content as described in more detail below. For example, the processor 56 may be configured to communicate control commands to a selector 62 of the LMR transport module 48 to select a protocol for use in communicating the LMR content. A display 64 also may be provided and configured to display, for example, the current channel, frequency, mode of communication, type of communication, communication protocol, etc, for the LMR unit 40.
In operation, the LMR communication system 20 with the LMR unit 40 may provide communication via the LMR network 42 using different known protocols, for example, LMR airlink protocols within a single LMR network 42. For example, these LMR airlink protocols include the Project 25 (TIA 102) and ETSI TETRA standards, among others. These LMR airlink protocols specify the format and procedures for information exchange between the LMR unit 40 and the LMR network 42, and in particular, the LMR base stations 44. It should be noted that when the base station(s) 44 are part of a larger system, the base station(s) 44 are interconnected to switching equipment (not shown) that routes voice and data between different parts of the system, such as to other LMR base stations or dispatch consoles. As is known, the LMR base station 44 processes, for example, manipulates, the voice, data and control information received over the airlink into an alternate format suitable for communication within the LMR network 42, for example, for transport to switching equipment.
For example, based on the current RF coverage area 32 (shown in
In operation, the LMR unit 40 either receives LMR content at the multiple protocol communication portion 72 or a user input (e.g., voice message via a microphone (not shown) or button depression input) at the voice encoder/decoder 70. For LMR content received at the multiple protocol communication portion 72, the LMR content is decapsulated and processed, which may include decoding and decrypting the LMR content, and then output, for example, via the speaker 78. For inputs received at the voice encoder/decoder 70, the input, for example, is encoded (e.g., encapsulated based on an encapsulation layer) and then transmitted from the multiple protocol communication portion 72 using one of the plurality of modems 76 based on the communication protocol for that portion of the LMR network 42 (shown in
Thus, communication of LMR content is communicated over the LMR network 42 and which may include transmitting and receiving using a plurality of different transport protocols and configuring the LMR content accordingly, for example, configuring the LMR content using different airlink protocols. In order to provide communication via the LMR network 42 using the LMR unit 40, the communication protocol stacks for communication using different protocols is partitioned as shown in
In this two-layer protocol stack model, the LMR base station 44 (shown in
Further, this two-layer protocol stack model enables delivering LMR application layer services over portions of the network using different transport layers defined by different communication protocols or a protocol different from the application layer. Specifically, as shown on the left side of
In particular, the LMR content encapsulation 86 is used with the packet switched transport datagrams 88 such that the LMR network 42 (shown in
It should be noted that the various embodiments are not limited to a two-layer protocol stack and additional layers may be provided to the multi-layer protocol stack as desired or needed. For example, different session layers, such as a bulk encryption layer may be provided. Further, and for example, an RTP layer may be provided. Further, it should be noted that although the example in
Various embodiments of the invention provide for controlling communication of LMR content in an LMR communication system using an LMR network having a plurality of LMR base stations or other repeaters or routers that may use different communication protocols. In particular, a method 100 of controlling communication of LMR content is shown in
After a determination of the transport protocol to use to communicate the LMR content is made at 102, a method of communication is selected at 104 based on the determined protocol to use. For example, the speed or baud rate of the communication may be selected (manually or automatically) from a range of communication data rates. Additionally, the setup procedures for establishing and connecting to the determined portion of the network may be selected. For example, if a first communication protocol is to be used, an LMR-1 transport layer network communication setup routine may be executed wherein a communication link is established between the LMR unit and that portion of the LMR network via an LMR transmitter/receiver within the LMR unit. If a second communication protocol is to be used, an LMR-2 transport layer network communication setup routine may be executed wherein a communication link is established between the LMR unit and that different portion (different from the first portion) of the LMR network. The setup routine may include any suitable processes as are known for establishing a wireless communication link.
Thereafter, at 106 the LMR content is configured for communication based on application layer protocol and the selected method of communication. For example, if the LMR content is to be communicated using the LMR-1 transport layer, a selection of a particular LMR standard in which to configure or format the LMR content is selected. In particular, an LMR-1 standard in which to configure the voice and/or data payload defining the LMR content is selected. This may include, for example, selecting one of a Project 25 (TIA 102) or an ETSI TETRA standard for the method of communication and encapsulating the data accordingly, for example, using IP wrapper encapsulation with a particular application layer protocol, for example, an LMR-1 application layer protocol. Further, and for example, a proprietary format may be selected, for example, an OpenSky MIA-COM proprietary format, a NetworkFirst or EDACS system proprietary format. A different communication protocol or format may be used, for example, if the portion of the LMR network requires communication in an LMR-2 standard.
Additionally, and as described in more detail above in connection with
Referring again to
After the LMR content is communicated and received, for example, by a base station of the network, the LMR content is processed at 110 to determine an action. For example, this may include a determination to communicate voice data or to issue an emergency signal or PTT request to a talk group. Further and for example, if the LMR content is communicated using different transport layers, the IP destination address of an encapsulated datagram may first be determined and then communicated to that location for processing using a router in the network. The LMR content then may be reencapsulated.
In the various embodiments, as shown in
This LMR content 130 is essentially encapsulated, for example, encapsulated in one or more IP wrappers such that different communication protocols may be used to communication the LMR content 130. The processor 122 decapsulates the LMR content 130, for example, by removing the transport layer protocol header 132 and may store the decapsulated LMR content 130 in a memory 124. The LMR content 130 then may be further processed by the processor 122 to determine an action to be performed or an address within the packet switched LMR infrastructure to which the LMR content 130 is to be communicated, which may include reencapsulation using a different transport layer identified by a different transport layer protocol header 132. Essentially, once the LMR content 130 is decapsulated, the LMR content 130 is configured for communication within the LMR infrastructure or within another portion of the LMR network 42. The control of communication of the LMR content 130 is controlled by a controller 126 that may include a router 128 for routing the LMR content 130 to a destination within, for example, the LMR network 42.
Thus, various embodiments of the invention provide for communicating LMR content using one or more protocols within an LMR network. The content may be encapsulated for communication based on a plurality of different transport layers and communicated accordingly using one of a plurality of modems of an LMR unit. For example, and as shown in
Further, as shown in
The various embodiments or components, for example, the LMR communication systems, networks or controllers therein, may be implemented as part of one or more computer systems, which may be separate from or integrated with the LMR communication system. The computer system may include a computer, an input device, a display unit and an interface, for example, for accessing the Internet. The computer may include a microprocessor. The microprocessor may be connected to a communication bus. The computer may also include a memory. The memory may include Random Access Memory (RAM) and Read Only Memory (ROM). The computer system further may include a storage device, which may be a hard disk drive or a removable storage drive such as a floppy disk drive, optical disk drive, and the like. The storage device may also be other similar means for loading computer programs or other instructions into the computer system.
As used herein, the term “computer” may include any processor-based or microprocessor-based system including systems using microcontrollers, reduced instruction set circuits (RISC), application specific integrated circuits (ASICs), logic circuits, and any other circuit or processor capable of executing the functions described herein. The above examples are exemplary only, and are thus not intended to limit in any way the definition and/or meaning of the term “computer”.
The computer system executes a set of instructions that are stored in one or more storage elements, in order to process input data. The storage elements may also store data or other information as desired or needed. The storage element may be in the form of an information source or a physical memory element within the processing machine.
The set of instructions may include various commands that instruct the computer as a processing machine to perform specific operations such as the methods and processes of the various embodiments of the invention. The set of instructions may be in the form of a software program. The software may be in various forms such as system software or application software. Further, the software may be in the form of a collection of separate programs, a program module within a larger program or a portion of a program module. The software also may include modular programming in the form of object-oriented programming. The processing of input data by the processing machine may be in response to user commands, or in response to results of previous processing, or in response to a request made by another processing machine.
As used herein, the terms “software” and “firmware” are interchangeable, and include any computer program stored in memory for execution by a computer, including RAM memory, ROM memory, EPROM memory, EEPROM memory, and non-volatile RAM (NVRAM) memory. The above memory types are exemplary only, and are thus not limiting as to the types of memory usable for storage of a computer program.
It also should be noted that the various embodiments of the invention also may provide different and/or additional functionality. For example, end-to-end encryption may be performed, thereby eliminating the use of intervening encryption equipment and the security risk encountered by having such intervening equipment with access to encryption keys. Further, various embodiments of the invention may provide end-to-end digital voice coding, thereby eliminating the use of intervening transcoding and transcription equipment and hence the fidelity loss encountered when one format is converted to another format.
While the invention has been described in terms of various specific embodiments, those skilled in the art will recognize that the invention can be practiced with modification within the spirit and scope of the claims.
Number | Name | Date | Kind |
---|---|---|---|
4845504 | Roberts et al. | Jul 1989 | A |
4852086 | Eastmond et al. | Jul 1989 | A |
4955083 | Phillips et al. | Sep 1990 | A |
5265264 | Dzung et al. | Nov 1993 | A |
5479480 | Scott | Dec 1995 | A |
5790527 | Janky et al. | Aug 1998 | A |
5805645 | Przelomiec et al. | Sep 1998 | A |
5862486 | Przelomiec | Jan 1999 | A |
5870149 | Comroe et al. | Feb 1999 | A |
5915212 | Przelomiec et al. | Jun 1999 | A |
5930723 | Heiskari et al. | Jul 1999 | A |
5995515 | Suzuki | Nov 1999 | A |
6002941 | Ablay et al. | Dec 1999 | A |
6009553 | Martinez et al. | Dec 1999 | A |
6023626 | Kinnunen et al. | Feb 2000 | A |
6035196 | Hengeveld et al. | Mar 2000 | A |
6041048 | Erickson et al. | Mar 2000 | A |
6084919 | Kleider et al. | Jul 2000 | A |
6144647 | Lopez-Torres | Nov 2000 | A |
6163710 | Blaser et al. | Dec 2000 | A |
6215778 | Lomp et al. | Apr 2001 | B1 |
6253082 | Hengeveld | Jun 2001 | B1 |
6301263 | Maggenti | Oct 2001 | B1 |
6351653 | Alberth, Jr. et al. | Feb 2002 | B1 |
6373828 | Stewart et al. | Apr 2002 | B1 |
6373946 | Johnston | Apr 2002 | B1 |
6449491 | Dailey | Sep 2002 | B1 |
6477150 | Maggenti et al. | Nov 2002 | B1 |
6515997 | Feltner et al. | Feb 2003 | B1 |
6549587 | Li | Apr 2003 | B1 |
6591084 | Chuprun et al. | Jul 2003 | B1 |
6611536 | Ahmed | Aug 2003 | B1 |
6683881 | Mijares et al. | Jan 2004 | B1 |
6757266 | Hundscheidt | Jun 2004 | B1 |
6775337 | Janky et al. | Aug 2004 | B2 |
6788946 | Winchell et al. | Sep 2004 | B2 |
6826414 | Reynolds et al. | Nov 2004 | B1 |
6831903 | Kang | Dec 2004 | B2 |
6865372 | Mauney et al. | Mar 2005 | B2 |
6912387 | Haas et al. | Jun 2005 | B2 |
6928067 | Hameleers et al. | Aug 2005 | B1 |
6928294 | Maggenti et al. | Aug 2005 | B2 |
6937589 | Taketsugu | Aug 2005 | B2 |
7031286 | Hall et al. | Apr 2006 | B1 |
7050786 | Caci | May 2006 | B2 |
7050787 | Caci | May 2006 | B2 |
7061894 | Pang et al. | Jun 2006 | B2 |
7065058 | Korus | Jun 2006 | B1 |
7079857 | Maggenti et al. | Jul 2006 | B2 |
7130282 | Black | Oct 2006 | B2 |
7149552 | Lair | Dec 2006 | B2 |
7218630 | Rahman | May 2007 | B1 |
7221660 | Simonson et al. | May 2007 | B1 |
7239867 | Kotzin et al. | Jul 2007 | B2 |
7245927 | Hansen | Jul 2007 | B2 |
7250830 | Layne et al. | Jul 2007 | B2 |
7305240 | Chou et al. | Dec 2007 | B2 |
7307963 | Chow et al. | Dec 2007 | B2 |
7333829 | Malone et al. | Feb 2008 | B2 |
7443965 | Blossom et al. | Oct 2008 | B2 |
7460510 | Olivier et al. | Dec 2008 | B2 |
7483416 | Olivier et al. | Jan 2009 | B2 |
7489698 | Blossom et al. | Feb 2009 | B2 |
7492734 | Mathis et al. | Feb 2009 | B2 |
7492737 | Fong et al. | Feb 2009 | B1 |
7864725 | Li et al. | Jan 2011 | B2 |
20010046214 | Kang | Nov 2001 | A1 |
20020086665 | Maggenti et al. | Jul 2002 | A1 |
20020086701 | Salmi et al. | Jul 2002 | A1 |
20020093928 | LoGalbo et al. | Jul 2002 | A1 |
20020101859 | Maclean | Aug 2002 | A1 |
20020115475 | Abrol et al. | Aug 2002 | A1 |
20020151321 | Winchell et al. | Oct 2002 | A1 |
20020161841 | Kinnunen | Oct 2002 | A1 |
20020196781 | Salovuori | Dec 2002 | A1 |
20030012217 | Andersson et al. | Jan 2003 | A1 |
20030053434 | Chow et al. | Mar 2003 | A1 |
20030058827 | Chow et al. | Mar 2003 | A1 |
20030119498 | Haas et al. | Jun 2003 | A1 |
20030134638 | Sundar et al. | Jul 2003 | A1 |
20030148785 | Mangal et al. | Aug 2003 | A1 |
20030156578 | Bergenlid et al. | Aug 2003 | A1 |
20030169768 | Bienn et al. | Sep 2003 | A1 |
20030177245 | Hansen | Sep 2003 | A1 |
20030189950 | Spear et al. | Oct 2003 | A1 |
20030190932 | Pulkkinen et al. | Oct 2003 | A1 |
20030198198 | Echavarri et al. | Oct 2003 | A1 |
20040032843 | Schaefer et al. | Feb 2004 | A1 |
20040121729 | Herndon et al. | Jun 2004 | A1 |
20040121781 | Sammarco | Jun 2004 | A1 |
20040190468 | Saijonmaa | Sep 2004 | A1 |
20040196861 | Rinchiuso et al. | Oct 2004 | A1 |
20040202940 | Kramer et al. | Oct 2004 | A1 |
20040203938 | Kulkarni | Oct 2004 | A1 |
20050058136 | Lothberg et al. | Mar 2005 | A1 |
20050070280 | Jung et al. | Mar 2005 | A1 |
20050073964 | Schmidt et al. | Apr 2005 | A1 |
20050078627 | Yoon et al. | Apr 2005 | A1 |
20050135348 | Staack | Jun 2005 | A1 |
20050143056 | Lyer et al. | Jun 2005 | A1 |
20050157673 | Verma et al. | Jul 2005 | A1 |
20050159107 | Mauney et al. | Jul 2005 | A1 |
20050176473 | Melpignano | Aug 2005 | A1 |
20050180418 | Andersen et al. | Aug 2005 | A1 |
20050197101 | Gupta | Sep 2005 | A1 |
20050232241 | Wu et al. | Oct 2005 | A1 |
20050233776 | Allen et al. | Oct 2005 | A1 |
20050243785 | Sabat, Jr. et al. | Nov 2005 | A1 |
20050243857 | Hofstaedter et al. | Nov 2005 | A1 |
20060002372 | Smith | Jan 2006 | A1 |
20060013191 | Kavanagh | Jan 2006 | A1 |
20060035669 | Chuprun et al. | Feb 2006 | A1 |
20060077924 | Rune | Apr 2006 | A1 |
20060084457 | Laha et al. | Apr 2006 | A1 |
20060089180 | Salmi | Apr 2006 | A1 |
20060092865 | Williams | May 2006 | A1 |
20060104293 | Kopp et al. | May 2006 | A1 |
20060114890 | Martin Boys | Jun 2006 | A1 |
20060126635 | Alberth, Jr. et al. | Jun 2006 | A1 |
20060141939 | Nakada | Jun 2006 | A1 |
20060145781 | Layne et al. | Jul 2006 | A1 |
20060171307 | Gopalakrishnan et al. | Aug 2006 | A1 |
20060193295 | White et al. | Aug 2006 | A1 |
20060205398 | Seckendorf et al. | Sep 2006 | A1 |
20060209828 | Ng et al. | Sep 2006 | A1 |
20060221968 | Razdan et al. | Oct 2006 | A1 |
20060234762 | Ozluturk | Oct 2006 | A1 |
20060245425 | Mathis et al. | Nov 2006 | A1 |
20060262771 | Martinez et al. | Nov 2006 | A1 |
20060262800 | Martinez et al. | Nov 2006 | A1 |
20060280144 | Kangas | Dec 2006 | A1 |
20060281471 | Shaffer et al. | Dec 2006 | A1 |
20070037596 | Shaffer et al. | Feb 2007 | A1 |
20070049314 | Balachandran et al. | Mar 2007 | A1 |
20070072554 | Janky | Mar 2007 | A1 |
20070081637 | Beard et al. | Apr 2007 | A1 |
20070153789 | Barker, Jr. et al. | Jul 2007 | A1 |
20070173222 | Hansen | Jul 2007 | A1 |
20070201432 | Sood et al. | Aug 2007 | A1 |
20070207731 | Hansen | Sep 2007 | A1 |
20070242670 | Simonson et al. | Oct 2007 | A1 |
20070291744 | Lundberg et al. | Dec 2007 | A1 |
20080031207 | Martinez et al. | Feb 2008 | A1 |
20080031275 | Janky et al. | Feb 2008 | A1 |
20080075055 | Chow et al. | Mar 2008 | A1 |
20080146221 | Noldus | Jun 2008 | A1 |
20080159128 | Shaffer et al. | Jul 2008 | A1 |
20080175263 | Chen et al. | Jul 2008 | A1 |
20080205321 | Martinez | Aug 2008 | A1 |
20080214232 | Ozluturk | Sep 2008 | A1 |
20080218427 | Dobosz et al. | Sep 2008 | A1 |
20080298293 | Hiben et al. | Dec 2008 | A1 |
20080299942 | Goulder et al. | Dec 2008 | A1 |
20080317066 | Trine et al. | Dec 2008 | A1 |
20090005100 | Copeland | Jan 2009 | A1 |
20090024845 | Benshetler et al. | Jan 2009 | A1 |
20090215411 | Tucker et al. | Aug 2009 | A1 |
Number | Date | Country |
---|---|---|
0 848 565 | Jun 1998 | EP |
0 848 565 | Jun 1998 | EP |
0 940 924 | Sep 1999 | EP |
1612996 | Jan 2006 | EP |
2 315 193 | Jan 1998 | GB |
62078925 | Apr 1987 | JP |
1020020025170 | Apr 2002 | KR |
WO-9523485 | Aug 1995 | WO |
WO 9736445 | Oct 1997 | WO |
WO-98 57482 | Dec 1998 | WO |
WO 0145310 | Jun 2001 | WO |
WO 0152563 | Jul 2001 | WO |
WO 0228131 | Apr 2002 | WO |
WO 02084913 | Oct 2002 | WO |
WO 03015431 | Feb 2003 | WO |
WO-2005391112 | Apr 2005 | WO |
WO 2006125043 | Nov 2006 | WO |
WO 2006125044 | Nov 2006 | WO |
WO 2007021586 | Feb 2007 | WO |
Number | Date | Country | |
---|---|---|---|
20080031207 A1 | Feb 2008 | US |