This invention relates generally to land mobile radios, and more particularly, to a land mobile radio providing communication of land mobile radio content using a land mobile radio network or a cellular data network.
Land mobile radios (LMRs) may be used to provide communication between different mobile units. 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).
Cellular networks also provide communication between different mobile users, for example, cellular telephones. These cellular networks, as well as LMR networks, continue to be enhanced and allow for improved operation and communication. For example, cellular networks now provide Push-to-talk (PTT) services that allow direct connect capabilities. Thus, a cellular phone user may request a direct connect communication link with another cellular phone user in a two way radio or “walkie talkie” type communication. As another example, cellular networks provide high-speed data services, such as, for example, General Packet Radio Service (GPRS), Enhanced Data Rates for GSM Evolution (EDGE), Evolution Data Optimized (EV-DO) and Universal Mobile Telephone Service (UMTS).
Known systems providing enhanced services or features, such as enhanced calling or voice features, which may be used, for example, for mission critical wireless applications, such as public safety applications, use commercial cellular services, such as PTT services, to augment and or replace traditional LMR systems. These known systems are provided using specialized gateway equipment that enable certain interoperability capabilities between an LMR system and a cellular network with, for example, PTT capabilities. The interoperability is provided by translating and/or transforming the data or voice communications to be communicated between the networks, for example, from an LMR network to a cellular network.
In the LMR area, new technologies are also being provided, including the use of digital communication instead of analog communication.
Additionally, LMR systems are now using packet switching instead of circuit switching, for example, using Internet Protocol (IP) and Voice Over IP (VoIP) to enable construction of highly scalable and cost effective LMR networks.
However, these improvements also result in need to support migration to new technologies. Further, interoperability between systems deployed either by different LMR owners/operators or between different cellular carriers, particularly when different technologies are used in different systems, is increasingly important. It is known to utilize multimode terminal devices to facilitate both migration and interoperability. In LMR, these devices are often referred to as multimode radios, and in the cellular area these devices are often referred to as multimode phones.
Multimode terminal devices enable inter-system roaming, and specifically, roaming from one network and/or technology to another, without user intervention. These terminal devices change mode as a user roams between different systems provided using different technologies. Further, components for operation in multiple protocols and frequency bands may be integrated into a single terminal device. For example, in the cellular area, multimode phones can roam between TDMA and CDMA networks. In the LMR are, radios can roam between an analog trunked system and a digital trunked system.
Multimode operation is provided by the interconnection of corresponding network infrastructures. Thus, to provide transparency to a user, gateway equipment may be used to connect the various systems or networks. Known devices for communicating between different types of networks or systems use different communication components (e.g., hardware and software) each configured specifically to communicate with a particular network or system. For each system or network, the functions and operations for that system or network are implemented using the capabilities and protocols specific to that system or network. However, these systems are limited in the set of overall functions that are available because the functions and user interface available to a user depend on the system into which the terminal device has roamed.
Further, the functions of one system may differ significantly from the functions available on another system. Additionally, because of these protocol incompatibilities certain end-to-end services cannot be provided, for example, end-to-end encryption. For voice communications, the use of a gateway to interconnect systems can introduce degradation in voice quality as a result of the voice data being converted from one format to another.
Thus, these systems not only may operate at non-satisfactory quality levels, but may require additional controls and equipment to implement the interconnectivity, thereby adding complexity and cost to the overall systems.
In one exemplary embodiment, a land mobile radio (LMR) is provided that includes an LMR communication portion configured to provide communication with an LMR network and a cellular data network communication portion configured to provide communication with a cellular data network.
In another exemplary embodiment, a multimode terminal device is provided that includes a land mobile radio and a cellular radio modem.
In yet another exemplary embodiment, a method of communicating land mobile radio (LMR) content using an LMR device is provided. The method includes configuring a land mobile radio to communicate LMR content using one of an LMR network and a cellular data network. The LMR content is encapsulated using a packet switching protocol when communicating using the cellular data network.
Various embodiments of the present invention include a multimode terminal device having a land mobile radio (LMR) unit providing LMR content, for example, LMR services using both an LMR network and a cellular data network. The LMR content retains an LMR application layer, but instead of using the LMR frequency bands with LMR transport protocols, the LMR content is communicated using cellular frequency bands over cellular packet switched data networks.
The multimode device is configured to provide inter-system roaming between, for example, LMR systems and cellular systems. Operation using the cellular system is provided generally by including a cellular radio modem into an LMR device, and supporting LMR features through encapsulation and transport of LMR voice, data and control information, utilizing end-to-end packet switched protocols between the LMR device and a packet switched infrastructure.
In the various embodiments, the data services of a cellular system are used when communicating using the cellular system. The cellular radio modem provides data services between an application layer within the LMR device and a gateway that bridges the LMR system or network and the cellular system or network. The end-to-end protocols between the multimode LMR device and the gateway utilize encapsulation techniques to transport LMR voice and data services over the cellular data network. The processes and techniques for performing the encapsulation and packet switched transport also may be referred to as LMR-over-cellular protocols.
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.
A wireless communication system will first be described followed by a description of an LMR unit in accordance with various embodiments of the invention.
As shown in
Various embodiments of the present invention enable end-to-end LMR services to be overlaid on top of the cellular data network 26, thereby allowing, for example, implementation of mission critical LMR systems within the service area of these cellular data networks 26. In order to provide this functionality and communication of LMR content using the cellular data network 26, each of the LMR units 22, for example, LMR radios, is provided with a cellular radio modem to allow operating end-to-end LMR application layer protocols and services between the LMR units 22 and the packet switched LMR infrastructure.
More particularly, and as shown in
Specifically, and as shown in
In operation, and as described in more detail herein, the processor 45 is configured to control selection of either the LMR communication portion 40 or cellular data network communication portion 42 using the selector 43. The processor 43 may access the memory 47 to obtain, for example, user preferences or predefined operating parameters. The processor 47 also may receive inputs (e.g., commands) from a user via the user interface 250, for example, to activate or select a certain function or operation. The input/output 51 may include different transmission and/or receiving components for transmitting and receiving to and from the LMR network 24 or the cellular data network 26 (shown in
Additional or different components may be provided to the LMR unit 22. For example, a global positioning system (GPS) unit may be provided as part of the LMR unit 22 to determine the location of the LMR unit 22.
The LMR unit 22 may be configured having different external configurations, for example, based on the specific application for the LMR unit 22. Various embodiments of different external configurations for LMR units are illustrated in
A side portion 236 of the LMR unit 220 also includes control members for controlling operation of the LMR unit 220. In this embodiment, an option button 238, a clear/monitor button 240 and a push-to-talk (PTT) button 242 are all provided on the side portion 236. The option button 238 is used to select different options, for example, within a particular operating mode (e.g., high/low power settings, keypad lock, display contrast, keypad lighting, etc.) and the clear/monitor button is used, for example, to clear a setting or end a call. The PTT button 244 is used to activate and deactivate PTT operations.
A front portion 244 of the LMR unit 220 generally includes the display 246, a speaker 248, a microphone 259 and a user interface 250. The user interface 250 includes a plurality of user depressible buttons that may be used, for example, for entering numeric inputs and selecting various functions of the LMR unit 220. This portion of the user interface may be configured, for example, as a numeric keypad. Additional control buttons also may be provided, for example, a menu button 252 and an increase and a decrease button 254 and 256, respectively. The increase button 252 and decrease button 254 may be used to provide the same functions as other user inputs, for example, correspond to the same operations as the system or channel knob 226. The menu button 252 is used to access a stored menu and/or activate an item within a list displayed on the display 246.
With respect to the plurality of user depressible buttons corresponding to numeric inputs, each may also provide control or activation of a particular function of the LMR unit 220. For example, numeric button (1) 258 also may be used to select a specific system or network, for example, the LMR network 24 or cellular data network 26 (shown in
The display 246 may be configured having a plurality of lines, for example, for displaying a system designation on one line, a group designation on another line and icons or other information (e.g., mode of operation) on additional lines. Other information may be provided on the display 246, for example, a battery power level indicator.
The LMR unit 220 also may be referred to as a system unit. An LMR unit 280 configured as a scan unit is shown in
Various other embodiments provide configurations of LMR units for use in different applications or in different settings. For example, an LMR unit 300 as shown in
The LMR units may include additional components, for example, filters (not shown), such as a receive filter and a transmit filter for filtering signals that are received and transmitted, respectively, by the LMR units. The LMR units also may include, for example, a dedicated switch (not shown) or other controller for switching between the LMR communication portion 40 and the cellular data network communication portion 42 (shown in
It should be noted when reference is made below to LMR unit 22, any of the various embodiments may be used, including LMR units 220, 280, 300 and 310.
In operation, the LMR system 20 may provide communication via the LMR network 24 using different known protocols, for example, LMR airlink protocols. 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, for example, LMR unit 22 and the LMR network 24, and in particular, the LMR base station 46. It should be noted that when the base station(s) 46 are part of a larger system, the base station(s) 46 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 46 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 24, for example, for transport to switching equipment. For example, received discrete voice, data and control transmissions may be encapsulated in TCP/IP or UDP/IP packets as is known, with the resultant IP packets communicated between the LMR base station(s) 46 and the switching equipment over an IP network.
The LMR unit 22 also may provide communication via the cellular data network 26 using different known protocols, for example, General Packet Radio Service (GPRS), Enhanced Data Rates for GSM Evolution (EDGE), Evolution Data Optimized (EV-DO), Universal Mobile Telephone Service (UMTS), and 802.16 standards, among others. These cellular protocols specify the format and procedures for information exchange between the LMR unit 22 and in particular, the cellular radio modem 38, and the cellular data network 26.
For example, a cellular tower (not shown) having base station (not shown) may be provided for receiving and processing signals from the LMR unit 22, for example, manipulating the received voice, data and control information into an alternate format suitable for communication within the cellular data network 26, for example, for transport to a router and server (not shown) based on an IP address for the data packets received. For example, received encapsulated signals are decapsulated and appropriately routed within the cellular data network 26.
Thus, communication of data from either the LMR network 24 or the cellular data network 26 to a packet switched LMR infrastructure 41 is provided. It should be noted that the LMR content and LMR network may be configured based on different airlink protocols. In order to provide communication via either the LMR network 24 or the cellular data network 26 using the LMR unit 22 the communication protocol stacks for communication with each of these networks is partitioned as shown in
In this two-layer protocol stack model, the LMR base station 46 (shown in
Further, this two-layer protocol stack model enables delivering LMR application layer services over non-LMR wireless networks using, for example, the cellular data network communication portion 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.
Various embodiments of the present invention provide for controlling communication of LMR content in an LMR communication system using an LMR network and a non-LMR wireless network, in particular, a wireless cellular data network. In particular, a method 100 of controlling communication of LMR content is shown in
After a determination of the network to use to communicate the LMR content is made at 102, a method of communication is selected at 104 based on the determined network 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 network may be selected. For example, if the LMR network is to be used, an LMR network communication setup routine may be executed wherein a communication link is established between the LMR unit and the LMR network via an LMR transmitter/receiver within the LMR unit. If the cellular data network is to be used, a cellular data network communication setup routine may be executed wherein a communication link is established between the LMR unit and the cellular data network via a cellular radio modem of the LMR unit. The setup routine may include any suitable process as is known for establishing a wireless communication link.
Thereafter, at 106 the LMR content is configured for communication based on the determined network and selected method of communication. For example, if the LMR content is to be communicated using the LMR network, a selection of a particular LMR standard in which to configure or format the LMR content is selected. In particular, an LMR 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. Further, and for example, a proprietary format may be selected, for example, an OpenSky M/A-COM proprietary format, a NetworkFirst or EDACS system proprietary format.
Further and for example, if the LMR content is to be communicated using the cellular data network, a selection of a particular wireless cellular data network standard in which to configure or format the LMR content is selected. In particular, a wireless cellular 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 General Packet Radio Service (GPRS), Enhanced Data Rates for GSM Evolution (EDGE), Evolution Data Optimized (EV-DO), Universal Mobile Telephone Service (UMTS) or 802.11 system 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. For example, if the LMR content is communicated using the cellular data network, 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.
Referring now to
This LMR content 130 is essentially encapsulated, for example, encapsulated in an IP wrapper. The processor 122 decapsulates the LMR content 130, for example, by removing the packet switch 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. Essentially, once the LMR content 130 is decapsulated, the LMR content 130 is configured for communication within a packet switched LMR infrastructure or an LMR network. 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. It should be noted that the LMR content may be reencapsulated for transmission within the LMR network or within the cellular data network.
The operation and selection of the network to use by the LMR unit, and more particularly, the selection of either an LMR network or a non-LMR network, for example, a cellular data network, to communicate the LMR content will now be described. In general, an LMR unit may automatically select the network to use based on, for example, a user setting, a predetermined setting, a user defined setting, an operating condition of the LMR unit, etc. The system selection also may be made by a user using a selector or input on the LMR unit. A method 350 for selecting the operating mode of the LMR unit, and more particularly, for determining when to use a particular network for communication is shown in
Thereafter at 358 a determination is made as to the LMR settings of the LMR unit. This may include, for example, determining preprogrammed settings or preferences for the LMR unit, such as, for example, based on threshold levels of data traffic on a particular network or available bandwidth on that network, a transmission priority level, the type of communication or content (e.g., voice or emergency broadcast signal, emergency communication or PTT request), the current network being used for communication, etc. A determination is then made at 360 as to whether the LMR settings override the user input or preference, or vice versa. For example, the LMR unit may be configured such that an emergency broadcast message must be transmitted over the LMR network and this overrides any user inputs or preferences. If the LMR settings do not override the user inputs or preferences, then at 362 a network to use for communication is selected based on the user inputs or preferences and the corresponding communication portion of the LMR unit is accessed, for example, the LMR communication portion 40 of the LMR unit 22 or the cellular data network communication portion 42 of the LMR unit 22 (all shown in
If at 360 a determination is made that the LMR settings override the user inputs or preferences then at 364 the network to use for communication is selected based on the LMR settings. This also may include using the determined operating conditions of the LMR unit to make the selection. It should be noted that selection of the network to use at either 362 or 364 may result in a new network selected or no change in the network (i.e., continue using the current network for communication). Further, after the selection of the network at either 362 or 364, if the network is changed then an indication may be provided at 366, for example, and audible indication (e.g., sound) or visual indication (e.g., LED on LMR unit illuminated or network selection displayed on display).
The method 350 may be performed, for example, periodically or upon certain events such as a user input, change in operating condition of the LMR unit, which may include exceeding a predetermined threshold, etc.
Referring now to
At the destination of the LMR content, the LMR content is processed at 160, for example, decapsulated and then an action determined at 162 based on the processed data. For example, a determination may be made at 162 that an emergency signal is to be transmitted or that the LMR content is to be further routed to another base station. The corresponding action is then performed at 164, for example, within the packet switched LMR infrastructure.
If a determination is made at 152 that the LMR content is not going to be communicated using the LMR network, then the LMR content is encapsulated for communication at 166. For example, in an exemplary embodiment, the LMR encapsulation module 36 (shown in
The LMR content is then processed at a destination, which may include decapsulating the LMR content and determining an action at 162. For example, a determination may be made that an emergency signal is to be transmitted or that the LMR content is to be further routed to another base station. The corresponding action is then performed at 164, for example, within the packet switched LMR infrastructure.
Thus, various embodiments of the present invention provide for communicating LMR content using an LMR network or a non-LMR network, for example, a cellular data network. If the LMR content is to be communicated using the cellular data network, the LMR content is encapsulated into a packet switching protocol before transmission. For example, and as shown in
Further, as shown in
The various embodiments or components, for example, the LMR communication system 20 or controllers therein, or the LMR units 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 20 or LMR unit, respectively. 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 present 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 present invention may provide end-to-end digital voice coding, thereby eliminating the use of intervening transcoding equipment and hence the fidelity loss encountered when one digital voice format is converted to another format.
Additionally, the various embodiments of the present invention may provide mission critical functions such as, for example, PTT, scanning, priority calls with preemption, emergency alerting and notification, content scanning and tracking, navigation, dispatch and GPS location. The mission critical functions may be implemented in different mission critical applications, including, but not limited to, public safety, utility industry and public transit industry.
Thus, the various embodiments provide multimode operation that allows implementing the same features, functions and user interface, independent of the system (e.g., LMR network or cellular network) on which the LMR unit is operating. The various embodiments also allow end-to-end encryption between LMR devices across different systems. Additionally, coding and recoding of the voice content is eliminated, thereby preserving voice quality.
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.
This application is a continuation of and claims priority to copending non-provisional U.S. patent application Ser. No. 11/167,005, filed on Jun. 24, 2005, which is a continuation-in-part of and claims priority to copending non-provisional U.S. patent application Ser. No. 11/130,975, filed on May 17, 2005, which are hereby incorporated by reference in their entireties.
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 |
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 | Iyer 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 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 et al. | Jun 2006 | A1 |
20060141939 | Nakada | Jun 2006 | A1 |
20060145781 | Layne et al. | Jul 2006 | A1 |
20060147008 | Blossom 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 |
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 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 |
20090138563 | Zhu et al. | May 2009 | A1 |
20090215411 | Tucker et al. | Aug 2009 | A1 |
Number | Date | Country |
---|---|---|
0 848 565 | Jun 1998 | EP |
1612996 | Jan 2006 | EP |
2315193 | Jan 1998 | GB |
9523485 | Aug 1995 | WO |
98 57482 | Dec 1998 | WO |
01 52563 | Jul 2001 | WO |
2005039112 | Apr 2005 | WO |
Entry |
---|
M/A COM, Inc., VIDA Network Solutions—The IP Network Approach to Your Critical Communications, [online], May 18, 2004, pp. 1-8, XP-002619659, [retrieved on Feb. 1, 2011]. Retrieved from the Internet: < URL:http://www.racom.net/Downloads/VIDA—Brochure.pdf>. |
Extended European Search Report mailed Mar. 3, 2011, European Application No. 10015389.9-1249, in the name of Pine Valley Investments, Inc. |
M/A COM Inc.: “P25IP—Expanding Digital Communications”, May 18, 2004, pp. 1-4, XP002619660, Retrieved from the Internet: URL:http://www.racom.net/Downloads/P24—Brochure.pdf [retrieved on Feb. 1, 2011]. |
Information about Related Patents and Patent Applications, see section 6 of the accompanying Information Disclosure Statement Letter, which concerns Related Patents and Patent Applications. |
European Search Report mailed Feb. 24, 2011, Application Serial No. 10015388.1. |
Whitepaper, Mobitv, “ATSC-M/H: The Promise of Free to Air Mobile Simulcast” found at <<http://www.mobitv.com/technology/whitepapers/ATSC.PDF>> on Mar. 13, 2009. |
Software-Enabled Wireless Interoperability Assessment Report—Voice-over-IP Technology, Dec. 2001, www.safecomprogram.lgov/NR/rdonlyres/63893E23—C4EE-4779-BB91-600847499056/0/voip—technolgy—assessment.pdf. |
“The Authoritative Dictionary of IEEE Standard Terms”, Standards Information Network IEEE Press, Seventh Edition, p. 378. |
Ericsson: “Communication and Information Services for National Security and Public Safety”, White Paper, [online] Apr. 2005, pp. 1-25, XP002397357. |
Number | Date | Country | |
---|---|---|---|
20120178442 A1 | Jul 2012 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 11167005 | Jun 2005 | US |
Child | 13424956 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 11130975 | May 2005 | US |
Child | 11167005 | US |