US 6,240,295 B1Grant

Data messaging in a communications network using a feature request

Issue Date:2001-05-29

•54 Claims

•8 Drawing Sheets

Abstract

A messaging unit (16) equipped with a cellular transceiver (38) is attached to a mobile item (12) located within a communications network (10). The messaging unit (16) issues a feature request having data digits that represent information on the mobile item (12). The cellular transceiver (38) transmits the feature request using the network (10). The feature request is received at an MTSO (20) and then routed to a platform (24), a clearinghouse (22), or the platform (24) through the clearinghouse (22). The data digits are translated into information on the mobile item (12) and stored at the platform (24) or the clearinghouse (22) for access by a host (26).

Metadata

Assignee

@Track Communications, Inc.

Inventors

William C. Kennedy, III
Kenneth R. Westerlage
Kenneth W. Hammer

Application Information

Application Number:US 09/092,620

Filing Date:1998-06-05

Priority Date:1993-07-20

Art Unit:7

Classifications

IPC:

H04Q 720H04M 342

Field of Search:

4554564554574554144554034554224554664555504555643409883409893409923404255340431340445340447342457342357342450

Patent Drawings (8 sheets)

Description

[0002] This application is a continuation application of U.S. patent application Ser. No. 08/573,135, filed Dec. 15, 1995, entitled “Data Messaging in a Communications Network Using a Feature Request,” by William C. Kennedy III and Kenneth R. Westerlage, now U.S. Pat. No. 5,771,455, which is a continuation application of U.S. patent application Ser. No. 08/175,256, filed Dec. 28, 1993, entitled “Data Messaging in a Communications Network,” by William C. Kennedy III and Kenneth R Westerlage, now U.S. Pat. No. 5,539,810; which is a continuation-in-part application of U.S. patent application Ser. No. 08/095,166, filed Jul. 20, 1993, and entitled “Method and Apparatus for a Nation-Wide Cellular Telephone Network,” by William C. Kennedy III and Kenneth R. Westerlage, now abandoned. This application is related to pending U.S. patent application Ser. No. 09/044,766, filed Mar. 19, 1998 and entitled “Data Messaging in a Communications Network Using a Feature Request.”

Technical Field of the Invention

[0003] This invention relates generally to the field of telecommunications, and more particularly to data messaging in a communications network.

Background of the Invention

[0004] The proliferation of sophisticated communications systems has resulted in developments in mobile communications and in particular mobile data messaging. Data messaging collectively refers to the transfer of information over voice or data channels of a communications network. One application of data messaging is the monitoring of a group of items by causing the items to send data messages to a remote location in response to a recognized reporting event. For example, a truck trailer monitoring system may use data messaging to collect information on the current position and status of a fleet of truck trailers.

[0005] A network of cellular telephone systems is a suitable conduit for such data messaging, especially if the monitored items are mobile, such as people, vehicles, or cargo containers. However, the cost of using traditional cellular communication is prohibitive, both in terms of chargeable air time and roamer fees.

[0006] Another problem with using traditional cellular networks for data messaging is that the fragmentation of cellular service providers results in disintegrated monitoring and control of cellular air traffic, which often contributes to fraudulent use of the cellular telephone network. Increasing incidents of roamer fraud adds significantly to the cost of cellular air time, especially for nation-wide users of the cellular telephone network. To combat these problems, cellular service providers are implementing authorization and verification procedures for validating roaming customers.

[0007] Therefore, a need has arisen for a communications network that handles a high volume of data messaging by exploiting the functionality of existing cellular telecommunications equipment, while reducing opportunities for fraud. In particular, a need has arisen for data messaging to monitor the position and status of a national fleet of truck trailers in the most cost effective and reliable manner.

Summary of the Invention

[0008] In accordance with the teachings of the invention, a method and apparatus for data messaging in a communications network is provided which substantially eliminate or reduce disadvantages and problems associated with prior art data messaging systems. Furthermore, data messaging in a cellular telephone network to monitor the location and status information of a fleet of truck trailers substantially eliminates or reduces disadvantages and problems associated with prior art truck trailer monitoring systems.

[0009] In accordance with one aspect of the invention, a method for data messaging over a cellular telephone network by issuing a feature request is disclosed. Information is obtained on a mobile item. A feature request is generated having data digits that represent information on the mobile item. The feature request is communicated using the cellular telephone network. The feature request is received at a platform operating as an end user of the cellular telephone network.

[0010] In accordance with another aspect of the present invention, a system for data messaging using a cellular telephone network by issuing a feature request includes a messaging unit. The messaging unit obtains information on a mobile item and generates a feature request having data digits that represent information on the mobile item. The messaging unit has a cellular transceiver that communicates the feature request using the cellular telephone network. A platform is coupled to the cellular telephone network and receives the feature request communicated by the messaging unit. The platform translates the data digits to determine the information on the mobile item. The platform has a memory that stores the information on the mobile item. A host is coupled to the platform and operates external to the cellular telephone network. The host accesses the information on the mobile item stored at the platform.

[0011] An important advantage of the invention is that messaging units can send data messages using a cellular telephone network by issuing a feature request having data digits. The data digits represent information obtained on a mobile item, and in one particular embodiment, information generated by a sensor. The feature request may be communicated to a platform for translation of the data digits into information obtained on the mobile item. The platform may then store the information on the mobile item for access by a host. In one embodiment, the communication of the feature request is performed through a switch, which may recognize a feature request identification code or a cellular transceiver identifier to determine that the feature request is associated with data messaging. In addition to data digits, the feature request may also include an altered identifier of a cellular transceiver that reflects information on the mobile item. Other technical advantages are readily apparent to one skilled in the art from the following figures, descriptions, and claims.

Brief Description of the Drawings

[0012] For a more complete understanding of the invention and the advantages thereof, reference is now made to the following description taken in conjunction with the accompanying drawings, wherein:

[0013] FIG. 1 is a block diagram of a communications network for communicating a variety of data messages in accordance with the teachings of the invention;

[0014] FIG. 2 is a block diagram of a messaging unit operating within the communications network for sending and receiving a variety of data messages in accordance with the teachings of the invention;

[0015] FIG. 3 is a flow diagram for sending a data message over a voice channel of the communications network using a modem handshake protocol in accordance with the teachings of the invention;

[0016] FIG. 4 is a flow diagram for sending a data message over a data channel of the communications network in accordance with the teachings of the invention;

[0017] FIG. 5 illustrates a block diagram of a nation-wide cellular system constructed according to the teachings of the present invention;

[0018] FIG. 6 illustrates another embodiment of a nation-wide cellular system constructed according to the teachings of the present invention;

[0019] FIG. 7 illustrates a mobile unit constructed according to the teachings of the present invention;

[0020] FIG. 8 illustrates a telecommunications platform constructed according to the teachings of the present invention;

[0021] FIG. 9 is a flow diagram for transmission and reception of a present message according to the teachings of the present invention;

[0022] FIG. 10 is a flow diagram of a call to a mobile unit according to the teachings of the present invention;

[0023] FIG. 11 is a flow diagram of a call from a mobile unit according to the teachings of the present invention; and

[0024] FIG. 12 is a block diagram of a central host constructed according to the teachings of the present invention.

Detailed Description of the Invention

[0025] FIG. 1 is a block diagram of a communications network 10. Located within cellular system 14 of network 10 is a truck trailer 12 carried by a cab, barge, train, or other suitable transportation system. It should be understood that the invention contemplates data messaging from any group of cargo containers, vehicles, persons, and other items whose location and status information are to be monitored.

[0026] Network 10 may be a cellular telephone network, but it may also be another type of communications system, such as a specialized mobile radio (SMR) system, a personal communication services (PCS) system, or any other suitable communications system. Furthermore, network 10 may be comprised of land-based transmission towers, space-based satellite transponders, or a combination of communications hardware in space or on land. Transmissions over network 10 may be analog or digital without departing from the scope of the invention.

[0027] Truck trailer 12 is equipped with a messaging unit 16, which contains a cellular transceiver for sending and receiving data messages. The design of messaging unit 16 is discussed in detail with reference to FIG. 2. Cellular system 14 includes a transmission tower 18 and a mobile telecommunications switching office (MTSO) 20 coupled to the transmission tower 18. It should be understood that each cellular system 14 may comprise a plurality of transmission towers and a plurality of MTSOs.

[0028] MTSO 20 switches calls to and from the cellular system 14 and a land-based telecommunications system (not shown). MTSO 20 is also coupled to clearinghouse 22, which provides call information to MTSO 20 through data link 23. For example, MTSO 20 can be configured to connect calls only if clearinghouse 22 provides, for example, validation information indicating that the cellular phone involved has good credit or is authorized to make calls. Clearinghouse 22 may also maintain other information, such as “roaming” phones' present locations and home systems. In existing cellular systems, companies such as GTE/TSI, EDS, and McCaw provide the clearinghouse function.

[0029] MTSO 20 is coupled to a telecommunications platform (“platform”) 24 through a voice/data link 21. Clearinghouse 22 is also coupled to platform 24 through data link 27 to provide platform 24 with information generated by clearinghouse 22. In turn, platform 24 is coupled to host 26 through voice/data link 29. Platform 24 may be coupled to any other host, such as host 28, through a similar voice/data link. Alternatively, hosts 26 and 28 may receive call information directly from clearinghouse 22 over data link 31.

[0030] Hosts 26 and 28 are shown for clarity, but it should be understood that many other hosts may be similarly coupled to platform 24, other platforms, other hosts, or clearinghouse 22. Link 33 between host 26 and host 28 allows hosts to exchange information. Host 35 may be connected to host 28 via link 33, such that host 35 receives information solely from host 28. In such a manner, designated hosts in network 10 act as central hosts to receive data messages and distribute these messages to other hosts.

[0031] FIG. 1 illustrates another cellular system 30, which includes a separate transmission tower 18 and MTSO 20. Within the operating region of cellular system 30 are truck trailers 12 equipped with messaging units 16. A platform 25 may be associated with cellular system 30, illustrating that the platform functions can be performed at distributed locations throughout network 10. However, platform 24 may perform all platform functions for all cellular systems. Moreover, as shown in FIG. 1, platform 24 may be coupled to one or more cellular systems. For example, platform 24 may be coupled to all of the east coast cellular systems. Likewise, platform 25 is a distributed platform, and is associated with and part of a particular cellular system. Platform 25, like platform 24, is coupled to a host, such as host 28.

[0032] Dashed line 32 indicates a link between MTSO 20 and platform 24. With a proposed standard (IS41, revision A), validation of a user can be performed prior to the placing of cellular calls. For example, at power up or upon first entry into a particular cellular system, a cellular transceiver can issue identifiers to MTSO 20 for pre-validation. Alternatively, MTSO 20 can poll a cellular transceiver to provide identifiers for validation and registration. The pre-validation information may be transmitted from MTSO 20 to clearinghouse 22 over data link 23. Likewise, platform 24 may perform the pre-validation without resort to an outside clearinghouse, over link 32. With pre-call validation performed by clearinghouse 22, later data messages can be sent directly to platform 24 over link 32. It should be understood that link 32 may be the same as voice/data link 21, a separate dedicated data link, or another communications link.

[0033] Data link 34 between platform 24 to platform 25 allows distributed platforms to exchange information regarding user validation, fraud management, systems operation, and billing functions. The distributed platform embodiment also provides fault tolerant and traffic management features in network 10, not unlike those features found in conventional long-distance telephone systems. Thus, as is shown in FIG. 1, telecommunications platforms may be centrally located or arranged in a distributed manner and connected by data link 34.

[0034] Throughout this description of the invention, host 26, platform 24, clearinghouse 22, MTSO 20, and cellular system 14 have been discussed as separate elements. It should be understood that each of these components are logical components, and they may be combined without physical separation. For example, the functions of platform 24 and host 26 may be accomplished at a single site. Furthermore, the functions of platform 24 and clearinghouse 22 may also be accomplished at a single site. References to cellular system 14, MTSO 20, clearinghouse 22, platform 24, and host 26 are to be understood as also referring to any cellular system, switch, clearinghouse, platform, and host, respectively, of network 10.

[0035] Also illustrated in FIG. 1 is data link 36, which allows for data transfer between MTSOs of the cellular systems in network 10. Such a link may be an SS7 backbone link for linking cellular systems. Link 36 allows cellular systems to share information relating to validation, roaming, billing, call routing, and other functions performed by network 10. For example, one cellular system that knows the location of a particular cellular transceiver, such as the cellular transceiver in messaging unit 16, may share that information with other cellular systems. Platform 24 may tie into link 36 across link 21 or link 32 to access information exchanged among MTSOs of the cellular systems in network 10.

[0036] The description of FIG. 1 references both data links and voice/data links. Data links, such as links 23, 27, 31, 34, and 36, allow transmission of data over a dedicated data channel. Voice/data links, such as links 21 and 29, support transmission of voice over a voice channel and transmission of data over a data channel. For example, a cellular telephone transmission over a voice/data link, such as a T1 transmission link, may employ digital transmission techniques to carry voice over a voice channel and data over a data channel, such as an overhead message stream. It should be understood that the invention contemplates any transmission technique over a voice/data link, whether digital or analog, that provides a voice channel and a data channel. Current systems used in the industry include the DS-1 standard used in the United States and the CCITT primary multiplex standard used in European telecommunication systems.

[0037] Another communications protocol contemplated by the invention, termed cellular digital packet data (CDPD), sends data in packets interspersed between voice transmissions. The data messages in this protocol may be carried in a reserved section of the digital bit stream or selectively placed to fill unoccupied sections of the digital bit stream. CDPD technology also supports delivery of data messages that is not real-time. This is accomplished by establishing delivery addresses, so a user may receive and store data messages at a designated address and retrieve the data messages at a later time for processing.

[0038] Voice/data links also support transmission of data over a voice channel using a modem, dual-tone multifrequency (“DTMF”) tones, or other suitable data encoder. The invention contemplates two ways to send a data message in network 10, data transmission over a data channel and data transmission over a voice channel using a data encoder. It should be understood that a dedicated data channel, such as link 34, could be replaced with a link that also allows voice transmission, without departing from the intended scope of the present invention.

[0039] In operation, network 10 allows data messages to be sent across cellular systems, such as cellular systems 14 and 30, in a variety of ways. Data messages sent to or received from messaging units 16 over a voice channel in network 10 must pass through platform 24 or 25, where they are subject to a handshake protocol to minimize cellular telephone fraud and maintain secured communications.

[0040] Data messages may also be sent to or received from messaging unit 16 over a data channel in network 10. As described below, these messages are packaged and sent over a data channel as part of the call data processing procedures. Like data messages sent over a voice channel of network 10, data messages sent over a data channel may also be subject to a security protocol. Each type of data messaging supported by network 10 will be discussed in detail with reference to FIGS. 3 and 4.

[0041] FIG. 2 is a block diagram of a messaging unit 16 operating within network 10 of FIG. 1. In one embodiment of the invention, messaging unit 16 may be attached to truck trailer 12. However, it should be understood that data messaging in network 10 is not limited to truck trailer monitoring systems. Messaging unit 16 may be attached to any mobile items to be monitored, such as people, vehicles, or cargo containers.

[0042] As shown in FIG. 2, cellular transceiver 38 is coupled to cellular transceiver bus 40. Cellular transceiver 38 receives and transmits signals across cellular antenna 42, including cellular transmission and reception of voice and data over the voice and data channels in network 10. Cellular transceiver 38 may be just a cellular transmitter equipped to transmit data messages or just a receiver equipped to receive data messages. It should be understood that further references to cellular transceiver 38 contemplate a transmitter, a receiver, or both.

[0043] Cellular transceiver bus 40 is coupled to one or more processors 44 through cellular interface drivers 46. Cellular interface drivers 46 provide the necessary protocol for communications between processor 44 and cellular transceiver 38.

[0044] A modem 48 allows processor 44 to receive and transmit digital communication over a voice channel in network 10, as received from and transmitted through cellular antenna 42 and cellular transceiver 38. Modem 48, or any suitable device, distinguishes between voice and data encoded on the voice channel, and handles the information accordingly.

[0045] Processor 44 is also coupled to a DTMF recognizer 50. DTMF recognizer 50 allows reception and transmission of DTMF data over a voice channel of network 10, as received from and transmitted through cellular antenna 42 and cellular transceiver 38. All data transmissions to or from messaging unit 16 can be made using DTMF data.

[0046] Processor 44 is also coupled to a read-only memory (“ROM”) 52 and a random access memory (“RAM”) 54. These memories are for storage of instructions and data for operation of processor 44. It should be understood that the invention contemplates use of any other suitable storage devices (not shown) including, but not limited to, hard disk and floppy disk drives, optical disk drives, CD-ROM storage devices, tape backups, and plug-in memory modules. A real-time clock 56 provides processor 44 with time-of-day, day-of-week, month, or year information.

[0047] Messaging unit 16 allows for input of location information from a LORAN-C system, global positioning satellite (GPS) system, dead reckoning system, inertial navigation system, or any suitable system providing location information. A positioning system interface 58 provides location information to processor 44, as received from positioning system transceiver 60 through positioning system antenna 62. The location information sent to processor 44 from the positioning system can be either raw location data (for example, data directly received from a LORAN-C system) or processed location data. Therefore, the processing of raw location data can occur within the positioning system itself, within the positioning system interface 58, within processor 44, or transmitted through cellular transceiver 38 and cellular antenna 42 for later processing at platform 24 or host 26 of FIG. 1.

[0048] Messaging unit 16 also allows for input of status information through sensor system 64. In one embodiment, sensor system 64 comprises sensors, controllers, and processors used to monitor various parameters of truck trailer 12, and operates to pass status information to processor 44. Sensor system 64 may monitor performance parameters of truck trailer 12, such as the temperature of a refrigerated compartment, battery voltage levels, or diagnostics of other truck trailer subsystems. Sensor system 64 may also monitor the status of truck trailer 12 and its contents, such as whether truck trailer 12 is connected to a cab and whether the contents have been tampered with. For purposes of this description, “sensor” refers to any device that furnishes processor 44 with location and status information, including a positioning system.

[0049] A power supply 66 powers the various components of messaging unit 16. For clarity, the power connections to the different components of messaging unit 16 are not shown. Power supply 66 is a power management system which may include a battery and charging circuitry. In addition, power supply 66 may include optional sources of power, such as an external power connection 68 from, for example, a truck electrical system interconnection cable or a solar cell 70 mounted on the roof of truck trailer 12.

[0050] As shown in the particular embodiment of FIG. 2, solar cell 70, cellular antenna 42, and positioning system antenna 62 may be mounted directly on the truck trailer roof, while the other components of messaging unit 16 reside inside the cargo compartment. However, it should be understood that the invention contemplates any arrangement and placement of the components of messaging unit 16 in one or more separate housings attached to the mobile item to be monitored.

[0051] In operation, messaging unit 16 generates a data message to be sent over voice or data channels of network 10 upon the occurrence of a reporting event. The occurrence of a reporting event is determined by processor 44 executing a reporting event determination module 72, shown as a part of processor 44 in FIG. 2. Upon the occurrence of a reporting event, processor 44 may immediately generate and transmit a data message or generate and store the data message for later transmission. By storing data messages, messaging unit 16 may then send a batch of data messages chronicling the status of truck trailer 12 over a period of time.

[0052] One reporting event that may trigger generation of a data message is a time-out signal received by processor 44 from real-time clock 56. Therefore, messaging unit 16 may generate data messages and report location and status information for truck trailer 12 at a particular time interval, such as twice a day, every day, or every week. In addition, a reporting event may be an external request from a variety of sources, such as MTSO 20, clearinghouse 22, platform 24 and host 26, among others.

[0053] A reporting event may also be initiated by the truck trailer transportation equipment or its operator. For example, messaging unit 16 may generate and transmit a data message upon a signal, received by processor 44 from sensor system 64, indicating connection or disconnection from the cab. An operator of the transportation equipment may also manually request messaging unit 16 to send a data message.

[0054] A reporting event may occur in response to a performance or alarm signal received by sensor system 64 that is beyond predetermined limits. For example, a reporting event may be when the cargo temperature in a refrigerated truck trailer exceeds a certain minimum or maximum level. The predetermined limits that trigger a reporting event may be remotely configured from the clearinghouse 22, platform 24, or host 26. Processor 44 may also determine a reporting event upon improper access to the cargo hold, malfunctioning of truck trailer subsystems, or malfunctioning of messaging unit 16 itself.

[0055] Furthermore, a reporting event may be based on geographical information. For example, messaging unit 16 may generate a data message when the truck trailer location determined by the positioning system deviates from an expected truck trailer location. The expected location may be stored in memory such as ROM 52, RAM 54, or other storage device, computed by processor 44, or received from host 26 or platform 24.

[0056] In a similar manner, a reporting event may occur when truck trailer 12 approaches or crosses a city, state, or national border, or enters the service area of a cellular system. Therefore, processor 44 executing reporting event determination module 72 causes messaging unit 16 to generate a data message upon the occurrence of a reporting event. The reporting event may be based on time, external requests, sensor inputs, manual requests by the driver, geographical information, or any other event or condition that warrants reporting of a data message to host 26.

[0057] Upon determination of a reporting event, messaging unit 16 operates to transmit and receive a variety of data messages over network 10. The data messages may contain information that initiated the reporting event, such as a signal indicating connection of the truck trailer to a cab, and also other monitored information, such as the location of the truck trailer at the time of the reporting event. Ultimately data messages transmitted from messaging unit 16 are routed through platform 24, clearinghouse 22, or both and accessed by host 26, as shown in FIG. 1. A data message may be communicated over network 10 using either a voice channel or a data channel.

[0058] Messaging unit 16, through control of processor 44 may transmit and receive data messages over a voice channel through platform 24. For clarity, the transmission or reception of data messages over a voice channel, including handshaking, will be discussed in connection with modem transfers, it being understood that such transmissions can be made using DTMF tones or other data encoded on the voice channel.

[0059] The ability to require that all data messages communicated over a voice channel pass through platform 24 is an important advantage of the invention, and allows for modem handshaking between platform 24 and messaging unit 16. As shown in FIG. 2, processor 44 runs instructions that execute a handshake protocol module 74 which establishes secure data modem communication with platform 24. The method to transmit data messages over a voice channel is described in more detail with reference to FIG. 3.

[0060] Processor 44 also executes a MIN statusing module 76 and a feature request generation module 78, which allow messaging unit 16 to generate and transmit data messages over a data channel of network 10. As described below with reference to FIG. 4, MIN statusing module 76 allows messaging unit 16 to encode status and location information by altering identifiers of cellular transceiver 38, such as the mobile identification number (MIN) or electronic serial number (ESN), transmitted over a data channel of network 10. Feature request generation module 78, also discussed with reference to FIG. 4, is another method to send data messages over a data channel by appending to a feature request data digits representing status and location information.

[0061] Link 80 between processor 44 and the transportation system allows messaging unit 16 to send and receive communications to and from, for example, a truck cab. The link may allow two-way communications using a short range radio system, an infra-red (IR) coupling, a direct connection through signal wires, or other appropriate technology. Alternatively, the link may be a one-way communications link that allows messaging unit 16 to send data messages for transmission by the transportation system. In one embodiment, a one-way link may allow a scanner attached to the transportation system to identify the attached truck trailer 12.

[0062] Functionally, link 80 allows components of messaging unit 16 to be divided between the mobile item and its transportation system. In one embodiment, processor 44 residing on the mobile item generates a data message and then sends this data message over link 80 for transmission by cellular transceiver 38 located on the transportation system. In such a manner, the cost of outfitting mobile items with data messaging capabilities may be reduced by placing components of messaging unit 16 on the transportation system. It should be understood that the invention contemplates any arrangement of components of messaging unit 16 on the mobile item and the transportation system.

[0063] FIG. 3 is a flow diagram for sending a data message generated by messaging unit 16 over a voice channel of network 10 using a modem handshake protocol. The method begins at block 100 which determines whether one of a variety of reporting events has occurred, as determined by processor 44 running reporting event determination module 72. If no reporting event has occurred, the method loops back in a continuous fashion to monitor the existence of a reporting event. When a reporting event occurs, block 102 generates a data message. The data message may contain location and status information of truck trailer 12 in a standard data package for transmission by modem 48. It should be understood that the invention contemplates any suitable modem transfer protocol and compression technique to prepare the data for transmission by modem 48.

[0064] The method of FIG. 3 then proceeds to block 104 where messaging unit 16 establishes a data modem connection with platform 24 over a voice channel of voice/data link 21 or 32. Data modem connection establishes the parameters for communication, such as baud rate, parity, and number of stop bits. After the connection is established, block 106 initiates a modem handshake between messaging unit 16 and platform 24. If messaging unit 16 does not pass the modem handshake and establish secure communications with platform 24, the method proceeds to block 108, where the communication is disconnected. At block 110, messaging unit 16 may try to reestablish a data modem connection and retry modem handshaking. Alternatively, the process may be reset for detection of another reporting event at block 100.

[0065] Upon successful modem handshake, the method proceeds to block 112 where modem 48 downloads the contents of the data message into a storage device in platform 24. The data may be time-stamped and stored as an entry in a log of data messages from messaging unit 16. Platform 24 can also index received data messages by an identification number of messaging unit 16 or cellular transceiver 38 received during modem handshaking at block 106. At block 114, an external device, such as a dispatcher's computer at host 26, can access the stored data messages and update a record of the location and status of mobile items equipped with messaging unit 16.

[0066] FIG. 4 is a flow diagram for sending a data message over a data channel of network 10 using either the MIN statusing 76 or feature request generation 78 modules of processor 44. Unlike data messaging using modem data or DTMF tones, the following discussion describes transmission of data messages through network 10 without opening a voice channel. Furthermore, the data messaging techniques described below can be routed through clearinghouse 22, platform 24, or both clearinghouse 22 and platform 24.

[0067] The method of FIG. 4 begins at block 116 which determines whether a reporting event has occurred by executing reporting event determination module 72 in processor 44. If no reporting event has occurred, the method continues to monitor sensor system 64, real-time clock 56, location data received from positioning system interface 58, and other inputs to determine if a reporting event has occurred.

[0068] Upon the occurrence of a reporting event, block 118 generates a data message. As described above, data messages may be created and sent immediately or created and stored for later transmission by messaging unit 16. A data message for transmission over a data channel of network 10 may be generated in two ways. First, location and status information can be encoded by altering identifiers of cellular transceiver 38, such as the mobile identification number (MIN) or electronic serial number (ESN). A second way to generate a data message is by dialing a feature request and appending location and status information in digits of data within the feature request. These two different ways of generating a data message are described in detail below.

[0069] The process to alter identifiers of a cellular transceiver 38 to transmit a data message, termed MIN statusing, begins with identification of the event to be reported and a translation of this event into a coded number. For example, assume processor 44 of messaging unit 16 receives a reporting event signal from sensor system 64 indicating that the temperature in the refrigerator compartment of truck trailer 12 is too high. Processor 44 translates the reporting event into, for example, a two-digit status code “39”. The MIN of cellular transceiver 38 may be altered to include status code “39” in a designated data field. For example, if the current MIN is “099 881 1234”, then the new altered MIN with the embedded status code may be “099 880 0039”. The prefix “880” indicates that the MIN has been altered to convey status or location information, and the last four digits contain the encoded location or status information in the form of a two-digit status code “39”.

[0070] The MIN of cellular transceiver 38 is altered to include a data message, but the ESN remains fixed to be used as an identifier of the messaging unit 16 that sends the data message. Therefore, upon receipt of the MIN/ESN, clearinghouse 22 or platform 24 can identify the messaging unit 16 by the ESN and can also receive status and location information encoded in the MIN. Alternatively, processor 44 can alter the ESN of cellular transceiver 38 and keep the MIN constant. It should be understood that the invention contemplates modification of the MIN, ESN, both the MIN and ESN, or other identifiers of cellular transceiver 38 to accomplish the dual task of encoding location or status information and identifying messaging unit 16.

[0071] Cellular transceiver 38 may transmit identifiers to MTSO 20 upon a call, feature request, pre-call validation, or other communication between cellular transceiver 38 and MTSO 20. Therefore, the MIN statusing techniques of the invention can be used alone or in connection with feature request data messaging, data messaging over a voice channel of network 10, or any other data messaging technique that also transmits identifiers of cellular transceiver 38.

[0072] A second way to generate a data message at block 118 is to use a feature request and append location and status information in designated data digits of the feature request. Feature requests come in several varieties. For example, some feature requests are intercepted and acted upon by MTSO 20, such as “*18” and “*19” used to establish and disconnect roaming services. Other feature requests, such as programmed speed dial numbers, are equivalent to dialing a telephone number.

[0073] A dedicated feature request intercepted by MTSO 20 may be specifically implemented to transmit data messages. Such dedicated feature requests allow messaging unit 16 to send detailed data messages containing, for example, accurate location information generated by the positioning system. As an example, a data messaging feature request termed “*71” is generated by automatically or manually dialing the star key “*”, a two-digit feature request identification code “71”, and 29 digits of data. Furthermore, cellular transceiver 38 automatically appends the MIN/ESN to a feature request transmission. Such a feature request generated by messaging unit 16 and sent over a data channel of the cellular system would allow appended data messages of up to 29 digits.

[0074] Upon generating a data message using either MIN statusing 76 or feature request generation 78, the method of FIG. 4 proceeds to block 120 where MTSO 20 receives the data message. MTSO 20 may directly recognize the MIN/ESN or feature request identification code as identifying a data message from messaging unit 16. For example, MTSO 20 may be directed to recognize and process in a special manner all communications from a particular predetermined MIN/ESN, such as all MINs beginning with “099 880”. Alternatively, MTSO 20 may be directed to recognize and process in a special manner all feature request transmissions with a particular feature request identification code, such as “71”.

[0075] In another embodiment, MTSO 20 may contain a separate processor that indirectly monitors the call transactions through MTSO 20. The separate processor may also recognize and process data messages from messaging unit 16 in the same manner described above. In either situation, MTSO 20 appends a mobile serving carrier I.D. (“MSCID”) to the MIN/ESN at block 122 and routes the data message to clearinghouse 22 over data link 23 or platform 24 over voice/data link 21 or 32.

[0076] In one embodiment, the data message is received directly at clearinghouse 22, as shown in block 124. In another embodiment shown in block 126, the data message is received at platform 24 directly through voice/data links 21 or 32, or indirectly through data link 27 from clearinghouse 22. An optional security protocol is performed at block 127 to ensure the authenticity of the data message. At block 128, the method identifies the particular messaging unit 16 that is reporting the data message using the MIN/ESN or other identifiers of cellular transceiver 38 or messaging unit 16. The data message is then translated or decoded to determine the status or location information reported by messaging unit 16.

[0077] The method of FIG. 4 continues at block 130 where each data message may be time-stamped, indexed by identification number, and stored for later retrieval. The method of FIG. 4 concludes at block 132, where an external device, such as a dispatcher's computer at host 26, can access the stored data messages and update a record of the location and status of items equipped with messaging unit 16, and thus allow appropriate responses to the data messages.

[0078] Throughout the discussion of FIGS. 3 and 4, the data messages are transmitted by messaging unit 16 to be collected at a central location, such as clearinghouse 22, platform 24, or host 26. It should be understood that messaging unit 16 equipped with cellular transceiver 38 may also receive data messages from a central location. The data messages may be sent from a central location to messaging unit 16 over a voice or data channel of network 10 and in a similar manner as described above with reference to FIGS. 3 and 4. For example, data messages received by messaging unit 16 may be sent over a data channel using MIN statusing or feature request generation, or over a voice channel using a data encoder, such as a modem or DTMF recognizer. Received data messages at messaging unit 16 may serve a variety of functions, such as remotely programming predetermined sensor reporting limits, updating messaging unit 16 software, requesting information, or alerting the operator of the transportation system, among others.

[0079] FIG. 5 is a block diagram of a nation-wide cellular network 210 constructed according to the teachings of the present invention. As shown in FIG. 5, a vehicle 212 is within cellular system 214. Vehicle 212 includes a mobile unit 216, which will be discussed in detail below. Cellular system 214 includes transmission towers 218 (only one tower is shown for clarity, it being understood that each cellular system includes a plurality of transmission towers). Cellular system 214 also includes a central mobile telecommunications switching office (MTSO) 220 coupled to the transmission tower 218.

[0080] MTSO 220 switches calls to and from the cellular system 214 and the land based telecommunications system. MTSO 220 is also coupled to clearinghouse 222. The link between MTSO 220 and clearinghouse 222 is a data link, and clearinghouse 222 provides call validation information to MTSO 220. For example, MTSO 220 can be configured to connect calls only if clearinghouse 222 provides validation information on the call, such as that the cellular phone involved has good credit, or is authorized to make calls. Clearinghouse 222 may also maintain other information, such as information on “roaming” phones' present locations, and home systems. In existing cellular systems, companies such as GTE/TSI, EDS, and McCaw provide the clearinghouse function.

[0081] MTSO 220 is also coupled to telecommunications platform (“platform”) 224 through a telecommunications link 221 allowing both voice and data transmissions.

[0082] Clearinghouse 222 is also coupled to platform 224. In turn, platform 224 is coupled to central hosts 226 and 228. Central hosts 226 and 228 are shown for clarity. It should be understood that many other central hosts may be similarly coupled to platform 224. Furthermore, other cellular systems will also be coupled to telecommunications platform 224. For clarity, FIG. 5 illustrates one other such cellular system, cellular system 230. As shown, cellular system 230 also includes transmission towers and an MTSO.

[0083] Dashed line 232 indicates a link between MTSO 220 and platform 224. With a proposed standard (IS41, revision A), validation of calls can be performed prior to the placing of cellular calls. For example, at power up, or upon first entry into a particular cellular system, a cellular phone can issue its identification numbers, and pre-validation can be performed. Alternatively, the MTSO 220 can poll mobile unit 216 to request identification for validation and registration. The pre-validation may be between MTSO 220 and a clearinghouse, such as clearinghouse 222. Likewise, platform 224 may perform the pre-validation without resort to an outside clearinghouse, over link 232. With pre-call validation performed by clearinghouse 222, later data transmissions, such as feature requests, can be sent directly to platform 224 over link 232. It should be understood that link 232 may be the same as link 221.

[0084] In operation, nation-wide cellular network 210 operates to control access to and information sent across cellular systems such as cellular systems 214 and 230. In particular, all calls to or from mobile unit 216 must pass through telecommunications platform 224. Therefore, calls to and from mobile unit 216 are controlled to limit access to and time on cellular system 214. The details of this control will be discussed below.

[0085] FIG. 6 illustrates an alternate embodiment of the present invention which includes distributed telecommunications platforms. FIG. 6 includes the elements described above in connection with FIG. 5, with the exception that the telecommunications platform is distributed. Illustrated in FIG. 6 are platforms 234 and 236. In contrast to platform 224 of FIG. 5, which is centrally located and to which all cellular systems are connected, platforms 234 and 236 may be distributed throughout the nation-wide cellular network. As shown in FIG. 6, platform 234 may be coupled to one or more cellular systems. For example, platform 234 may be coupled to all of the east coast cellular systems. Likewise, platform 236 is a distributed platform, and is associated with and part of a particular cellular system.

[0086] Also shown in FIG. 6 is a communications link 237 from platform 234 to platform 236 that allows the distributed platforms to exchange voice and data, which may include user activity, systems operation, and billing functions. In particular, the distributed platforms 234 and 236 can exchange information regarding user validation and fraud management. The distributed platform embodiment also provides fault tolerant and traffic management features to the nation-wide cellular telephone system, not unlike those features found in conventional long-distance telephone systems. Thus, as is shown in FIGS. 5 and 6, telecommunications platforms may be centrally located or distributed, as required by the needs of the particular system implementing the present invention.

[0087] Also illustrated in FIG. 6 is link 239. Link 239 allows for data transfer between MTSOs of various cellular systems. Such a link may be an SS7 backbone link for linking cellular systems. Link 239 allows cellular systems to share information such as validation, roaming information, billing, and call routing, among other types of information. For example, one cellular system that knows the location of a particular cellular phone, such as mobile unit 216, may share that information with other cellular systems. Platform 224, across link 232, may tie into link 239. This allows platform 224 to have access to all MTSO 220s of different cellular systems.

[0088] FIG. 7 illustrates a mobile unit 216 constructed according to the teachings of the present invention. As shown in FIG. 7, phone transceiver 238 and hand set 240 are coupled to cellular phone bus 242. Phone transceiver 238 receives and transmits signals across antenna 244, including cellular transmission and reception of voice, data, and DTMF data, among other signals. The cellular phone bus 242 is coupled to processor 246 through phone interface drivers 248. Phone interface drivers 248 provide the necessary protocol for communications between the processor 246 and the phone transceiver 238 and hand set 240.

[0089] A hands-free microphone 250 and speaker 252 are provided for hands-free communications by the operator of the mobile unit. The hands-free microphone 250 and speaker 252 are coupled to audio multiplexer 254. Audio multiplexer 254 is also coupled to the hand set 240, the cellular phone bus 242, and the processor 246. The audio multiplexer 254 is also coupled to a modem 256 and a voice recognition and synthesis system 258. The modem 256 allows for digital communication between the processor 246 and the cellular system, as received from and transmitted through antenna 244 and phone transceiver 238. Modem 256, or any suitable device, is used to distinguish between voice and data and handle the information accordingly. Voice recognition and synthesis system 258 allows for voice activation of various functions of the mobile unit. Voice recognition and synthesis system 258 is coupled to processor 246.

[0090] Processor 246 and audio multiplexer 254 are also coupled to a dual-tone multi-frequency (“DTMF”) recognizer 259, which allows for recognition of DTMF data. All data transmissions to or from mobile unit 216 can be made using DTMF.

[0091] Mobile unit 216 also allows for reception and storing of telephone numbers. These numbers may be received as modem or DTMF data, and may be recalled and automatically dialed. Furthermore, processor 246 of mobile unit 216 can execute software allowing for voice mail functions for calls to mobile unit 216.

[0092] Processor 246 is also coupled to a read-only memory 260 and a random access memory 262. These memories are for storage of instructions and data for operation of processor 246. Furthermore, a plug-in ROM module 264 may also be coupled to processor 246 for optional information, such as map and emergency assistance information for a particular locality.

[0093] A key pad 266 is provided for user input of various information into the mobile unit 216 through processor 246. It should be understood that key pad 266 could comprise many other input devices, such as a touch screen. Information is displayed at mobile unit 216 through graphic display 268, which is driven by processor 246 through display drive 270.

[0094] Mobile unit 216 allows for input of location information from a LORAN-C system, a global positioning satellite (GPS) system or any suitable system providing location information of the mobile unit. This input is shown by positioning system 272 in FIG. 7. The positioning system 272 may be located within the housing of the mobile unit 216, or part or all of positioning system 272 may be located outside the mobile unit 216. The data sent to the mobile unit 216 from positioning system 272 can be either raw location data (for example, data directly received from LORAN-C system) or processed location data. Therefore, the processing of raw location data can occur within the positioning system 272 itself, within processor 246, or transmitted through phone transceiver 238 and antenna 244 for later processing at the platform 224 or central host 226 of FIG. 5.

[0095] Mobile unit 216 also allows for input of status information through automatic status generator 274. The automatic status generator 274 comprises any sensors, controllers, and processors used to monitor performance parameters of the vehicle 212, and operates to pass information from such monitors to the mobile unit 216. As will be discussed, status information may be received by the mobile unit 216 from either the automatic status generator 274 or the key pad 266. Block 276 allows for the input or output of various other options, such as an alarm input which, for example, could indicate that a vehicle on which the mobile unit is located has been broken into. As other examples, block 276 allows for the input or output of fax data or digital data to or from a modem. Such inputs and outputs may be from personal computers, for example, from users of recreational vehicles or traveling salesmen. Throughout this discussion, data communications, including handshaking, will be discussed in connection with modem transfers for clarity, it being understood that such transmissions can be made as DTMF data. A power supply 278 powers the mobile unit 216.

[0096] In operation, mobile unit 216 operates to transmit and receive information, including voice and data, across a cellular system and through telecommunications platform 224 of FIG. 5. Ultimately, data transmitted from mobile unit 216 is sent through platform 224 to one of the central hosts, for example central hosts 226 or 228 shown in FIG. 5.

[0097] Mobile unit 216, through control of processor 246, receives all calls through telecommunications platform 224, and makes all outgoing calls through telecommunications platform 224. This restriction is accomplished through use of a handshake protocol. The details of this protocol will be discussed below in connection with calls to or from the mobile unit. The ability to require that all calls to and from the mobile unit pass through platform 224 is an important advantage of the present invention, and allows for control of the character and length of calls made to and from the mobile unit. This is important in reducing cellular telephone usage costs, for example for a nation-wide trucking company, in which the trucking company provides mobile units in each of the trucks of the fleet, and wishes to restrict the character and length of calls from and to the mobile units.

[0098] The mobile unit 216 allows for transmission and reception of both voice and data. The voice transmissions, once a call is connected, are performed conventionally. Hands-free microphone 250 and speaker 252 allow for hands-free voice communications.

[0099] Data received by remote unit 216 is input to the processor 246 through modem 256. Data transmitted from mobile unit 216 is transmitted under control of the processor 246 through modem 256. Data to be transmitted from mobile unit 216 may be input in several ways. Key pad 266 may be used by a user of the mobile unit 216 to input various data, such as location data or status data (for example, whether a vehicle is broken down, whether it is loading, unloaded, waiting to load, waiting to unload, etc.). Such data may also be input by voice command through voice recognition and synthesis system 258. Data may also be automatically generated for output by mobile unit 216. For example, positioning system 272, which may comprise a LORAN-C positioning system, a GPS system, or any other positioning system, may generate position location information for transmission by mobile unit 216.

[0100] As discussed above, positioning system 272 may generate longitude and latitude information, or simply raw data, for example from a GPS system, to be transmitted from mobile unit 216. If only raw data is generated by a positioning system 272, then processor 246, the platform 224, or the central host 226 can generate the longitude and latitude information for positioning information. Likewise, automatic status generator 274 may be used to automatically generate status information, such as engine performance, trailer temperature (for example, if a refrigerated trailer tractor is associated with the remote unit), or other status information.

[0101] Processor 246 drives graphic display 268 through display driver 270 to display data received by mobile unit 216 for viewing by a user of mobile unit 216. Such data, for example, may be messages from a central host on weather conditions, delivery or destination instructions, among other messages. Furthermore, plug-in ROM 264 provides various information, such as map information or emergency assistance information for use by a user of the remote unit 216. This information can be displayed on graphic display 268.

[0102] FIG. 8 illustrates a block diagram of telecommunications platform 224 constructed according to the teachings of the present invention. A processor 280 is coupled to memory 282, look-up tables 284, and switch 286. Processor 280 is also coupled to fraud management system 287, usage tracking system 288 and billing system 290. In the distributed platform embodiment of FIG. 6, processor 280 may also communicate with another platform through communications link 291. Switch 286 is coupled to telecommunications trunks 292 and 294. Trunk 292 allows for telecommunications connections to central hosts, such as central hosts 226 and 228 of FIG. 5, as well as other outside land based systems. As shown in FIG. 8, some of the individual telecommunications lines of trunk 292 are coupled to modems, such as modems 296 and 298, thus allowing for data communications. Likewise, trunk 294 allows for telecommunications connections with various cellular systems, such as cellular systems 214 and 230 of FIG. 5. Some of the individual telecommunications lines are coupled through modems, such as modems 300 and 302, so as to allow for data communications with the cellular systems. Modems 296 and 300 are illustrated as MODEM/DTMF, to indicate that DTMF data can be transmitted and received as well. Modems 296, 298, 300 and 302 are coupled to processor 280 and can also operate to allow both voice and data communications. Trunks 292 and 294 are separated for clarity to show one bank of telecommunications lines serving dispatchers and other outside systems while another bank serves cellular systems. However, switch 286 can contain a single trunk or several trunks to accomplish the operations of the platform.

[0103] Telecommunications platform 224 operates as a smart telecommunications switch. Calls to and from remote unit 216 are passed through switch 286. Processor 280 monitors switch 286 and records information on each call through switch 286. This information, such as the number and length of calls to each remote unit 216, is recorded in usage tracking system 288. In this manner, bills can be generated for usage of telecommunications platform 224. Typically there will be several remote units associated with a particular nation-wide system, such as a trucking system. Thus, all calls to and from remote units owned by that trucking system will be logged for billing to that particular trucking system.

[0104] As discussed previously, a fraud management system 287 performs a handshake protocol between the telecommunications platform 224 and the remote unit 216. This protocol ensures than only authorized calls are made to and from mobile unit 216. If the handshake protocol is not performed correctly, then processor 280 will disconnect the call through switch 286, thereby greatly reducing costs resulting from unauthorized usage of cellular networks. Processor 280 also links to credit card validation system 303, to validate credit cards for allowing for personal calls, as will be discussed.

[0105] FIG. 9 is a flow diagram for transmission and reception of a “present” message according to the teachings of the present invention. Mobile unit 216 of the present invention, upon entry into a new cellular system, issues a present message which will eventually be sent to its central host. The “present” message can also be generated in response to a poll from platform 224 or MTSO 220, periodically, upon power up of mobile unit 216 upon re-establishment of communication, through use of a feature request reserved for the “present” message, or during pre-call or post-call validation, among other events. This “present” message can also be sent automatically or manually, and provides information to the central host on the current cellular system in which the mobile unit is located. Furthermore, other information, such as status information, can be sent with this “present” message. An important technical advantage of the present invention is the fact that this “present” message may be sent automatically, and with a minimum of cellular air time, thus providing significant cost savings. The “present” message may be sent to platform 224 through clearinghouse 222, through link 221 (for example, as part of a call), or through link 232 of FIG. 5.

[0106] Turning to the flow diagram of FIG. 9, at decision block 304, mobile unit 216 monitors the system identification number of the particular cellular system in which it is located. This system identification number, as is generally known in the art, is periodically issued by the cellular system in the overhead message stream. Once the remote unit 216 identifies a new system identification number, indicating that the mobile unit has entered a new system, it issues a “present” message at block 306. For example, the “present” message can be initiated by transmitting a “*19” feature request. Presently, “*19” is used in mobile systems to clear the roaming status of a cellular phone. As discussed above, the “present” message can also be generated upon other events, such as power up of the mobile unit 216.

[0107] Every cellular phone has associated with it a mobile identification number (“MIN”) and an electronic serial number (“ESN”). These numbers are transmitted by the cellular phone whenever it makes a call or issues a feature request, such as “*19.” Certain digits of the ESN are used by local cellular carriers. The unused digits may be used by mobile unit 216 to send information, such as location or status data. For example, longitude and latitude data can be embedded in the unused portion of the ESN. Likewise, certain digits of the MIN may not be necessary to identify calls to be directed to platform 224, and thus data may be embedded in these unused digits. Thus, the “present” message may contain important data as well. At block 308, the “present” message is received at MTSO 220 of FIG. 5. The MTSO 220 typically appends the cellular system identification number plus a switch identification number to the MIN and ESN numbers. As discussed, the “present” message may also be sent as part of a call from the mobile unit 216, and thus is sent to platform 224 across link 221.

[0108] When the “*19” is received at the clearing house 222 at block 310, it will determine whether the “present” message is to be sent to the telecommunications platform 224 at block 312. If the “present” message is not to be sent to the platform, then no data is sent. The clearinghouse 222 determines whether the “present” message is to be sent to the platform 224 by matching the MIN/ESN of the mobile unit to numbers stored in a pre-established user data base. This data base is established by making arrangements with the clearinghouse 222 that all communications from particular cellular phones, i.e., the mobile units 216, will be recognized by their MIN/ESN and directed to the platform 224. This data base can also be established such that even with a mobile unit registered at some home cellular system, the “present” message will be directed to the platform 24.

[0109] As discussed above, a direct link 232 may exist between MTSO 220 and platform 224. This link 232 allows for direct transmission of data and feature requests, such as the “*19” feature request and “present” data message, to the platform 224. MTSO 220 can be configured to directly send such transmissions by pre-arranging with MTSO 220 to recognize particular mobile units 216, or by forwarding such instructions from clearinghouse 222 as part of a pre-call validation scheme.

[0110] One embodiment allows the clearinghouse 222 to identify the mobile units 216 by a specified area code and prefix of the MIN. Upon matching the registered mobile units 216 with the user data base in the clearinghouse 222, the “present” message is sent to the platform 224 at block 314. The platform then timestamps and stores all “present” messages received from mobile unit 216 through the local carrier. The platform stores the data under each MIN/ESN for later transmittal to the central host. For example, a single mobile unit 216 on a truck traveling across the country may send numerous “present” messages to the platform as the truck passes through different cellular systems. The platform 224 maintains a timestamped chronological list of the “present” messages, so the truck company dispatch can access the list and determine the location and status of the truck.

[0111] The platform 224 of FIG. 8 eventually sends this information to the particular central host associated with the mobile unit 216 as shown at block 316. This transfer of data can occur periodically, such as at a particular time interval, upon request by a central host, or whenever a call connection is made between a central host and the mobile unit 216. It should be understood that there will typically be a plurality of mobile units associated with a particular central host. For example, the central host may be a truck company dispatch that locates and coordinates the activities of a fleet of trucks equipped with mobile units 216. Thus, data can be down loaded from the platform 224 to the truck company dispatch anytime a call is made between the dispatch and any of the trucks. Alternatively, the truck company can periodically call the platform, preferably when call rates are low or on a dedicated or “800” number, and download a data package containing status and location information on the truck fleet. From the “present” message, the central host can determine at least which cellular system a particular mobile unit has entered. This information is available since the MTSO 220 appends information the MIN/ESN. Such information may be, for example, a mobile serving carrier I.D. (“MSCID”). Furthermore, any data, including specific location data generated by positioning system 272, embedded in the ESN/MIN can be extracted by the central host.

[0112] The ability to generate “present” messages provides a significant advantage of the present invention. In particular, one central location—the platform 224—maintains these “present” messages and thus has knowledge of the location (at least the cellular system location) of various mobile units. This information allows for efficient and inexpensive call delivery. By directing calls to the mobile units through the platform 224, roaming difficulties are eliminated, since the platform 224 maintains a record of the locations of the mobile units 216. This call delivery advantage is useful in a wide range of applications, such as the broadcasting of messages to distributed mobile units, like those used in trucking companies, barges, traveling sales forces, rail systems, commercial and private bus lines, airplanes, and rental vehicles, among others. The architecture of the present invention also allows for efficient broadcasting of messages to non-mobile units, such as those used in a distributed advertising system. For example, billboards for lotteries can be programmed to automatically display the jackpot amount. This amount can be sent across cellular networks, with the calls being made through platform 224.

[0113] FIG. 10 is a flow diagram of a call made to a mobile unit according to the teachings of the present invention. FIG. 10, along with FIG. 11 to be discussed below, describe the operation of the fraud management system 287 and the protocol handshake mentioned above. Without a successful handshake, a call cannot be connected either to or from a remote unit.

[0114] As shown in FIG. 10, a call to a mobile unit is first made by placing a call to the platform at block 318. This call is, for a example, a 1-800 call, thereby reducing costs to those calling the platform. At block 320 the platform requests a mobile unit I.D. for the mobile unit to be called. This mobile unit I.D., for example, could be a truck identification number for mobile units placed on trucks. If no mobile unit I.D. number is received or the mobile unit I.D. is not proper, then decision block 322 returns the flow to block 320. If the mobile unit I.D. is proper, then the platform acquires authorization information at block 324. Authorization information may be, for example, a credit card number or an authorized code. For example, personal calls made to the mobile unit would only be initiated if the caller to the platform gave a valid credit card number. Validation of the credit card number may be accomplished through credit card validation system 303 of FIG. 8. For business calls coming from an associated central host, authorization can occur by entering an authorized code, or by calling in on a special business line, for example. This authorization occurs at block 326.

[0115] If the call is authorized, then the platform calls a mobile unit at block 328. Platform 224 uses look-up tables 284 of FIG. 8 to associate the phone number of the remote unit to be called with the mobile unit I.D. Platform 224 then looks up the most recently recorded cellular system identification number and switch identification number associated with mobile unit 216, such as that provided by the most recent “present” message issued by mobile unit 216 and stored by platform 224. Platform 224 then calls the appropriate roamer access port, and dials the phone number. Once the call is connected and the platform and mobile unit modems establish data communication, the mobile unit 216 issues a challenge at block 330. This challenge may be, for example, a random number. If no challenge is received, then the platform 224 disconnects the call at block 331. If the platform receives a challenge, then at block 332 the platform returns a response based on the challenge received, a key particular to the mobile unit, and an encryption algorithm. As noted, the key used in the generation of the response is a function of the mobile unit and may be generated from a lookup table of numbers shared by both mobile unit 216 and platform 224 indexed by the MIN/ESN of mobile unit 216. The encryption algorithm, also known by both mobile unit 216 and platform 224 can be any appropriate mathematical algorithm, and may be modified periodically, as can the lookup table, to maximize security.

[0116] At block 334, the platform determines whether the response is correct by running the same encryption algorithm on the challenge and key. If the response is not correct, or if no response is received, then the call is disconnected at block 336. U.S. Pat. No. 5,155,689, issued on Oct. 13, 1992, and assigned to By-Word Technologies, Inc., of Dallas, Tex., discloses a system that connects or disconnects calls based upon interrogation between two modems in a cellular system. That patent is herein incorporated by reference.

[0117] If the response is correct, the call is completed at block 338. At block 338, either voice or data or both may be transmitted to or from the mobile unit.

[0118] For calls from the central host 226 that include voice communications, a voice request is sent to the platform 224 from the central host 226 to communicate with a particular mobile unit 216. Any data to be exchanged with that mobile unit is exchanged before connecting the voice communications. For example, data from the central host 226 is delivered through the platform 224 to the mobile unit 216, and any data at mobile unit 216 is delivered at least to platform 224. Next, the platform 224 requests that mobile unit 216 to switch to voice, and rings the user of mobile unit 216. If no answer is received, then no voice connection is made between mobile unit 216 and central host 226. If an answer is received, then platform 224 calls the central host 226 (or any other number provided to the platform 224 by the central host) and patches the appropriate connection.

[0119] There will be times when calls cannot be delivered to mobile unit 216, for example, when it is out of any cellular system, temporarily out of communication with a cellular system, or powered-down. In such cases, an alert will be set at the platform 224, indicating that a call has not been completed. Upon receipt of a “present” message, for example, when the mobile unit 216 to which the call was intended powers up, re-establishes communication or enters a new cellular system, the platform 224 can complete the call. If only data is to be transferred, then this data can be sent from the platform 224 to the mobile unit 216. If a voice call had not been completed, then the platform 224 calls the calling party, for example the dispatcher at a central host, and indicates that a call can be or will automatically be placed to the appropriate mobile unit 216. Furthermore, the user of a mobile unit 216 may be provided with a pager/remote ringer, to ensure that he is aware of any voice calls to his mobile unit 216.

[0120] FIG. 11 is a flow diagram of a call from a mobile unit 216 according to the teachings of the present invention. At block 340, the mobile unit will initiate an outgoing call. The outgoing call can be initiated in any of several ways. The mobile unit 216 can be programmed such that only certain pre-programmed numbers can be called. These authorized phone numbers are stored in remote unit 216 and can be programmed remotely by the central host 226 or platform 224. Thus, a user of a remote unit would only be able to call these pre-programmed numbers and no others. Alternatively, the remote unit could be configured so as to allow personal calls—if eventually authorized—as well as pre-programmed authorized calls. Regardless of what number is to be eventually called, the mobile unit 216 is pre-programmed to first call the platform at block 342. This call, for example, could be a 1-800 number call. Alternatively, arrangements can be made with each cellular system to direct all calls from mobile units with particular MIN/ESNs to platform 224. Each local carrier would recognize these particular MIN/ESNs and route their calls to platform 224. Recognition can occur through use of a pre-arranged database, as discussed above. The handshake protocol between the mobile unit and the platform is similar to that described in connection with FIG. 10, except that the challenge and response are issued by the platform and mobile unit, respectively.

[0121] As shown in FIG. 11, at block 344 the platform issues a challenge after modem connection with the mobile unit and receipt of a mobile unit I.D., such as an MIN. This I.D. provides the platform 224 with knowledge of which mobile unit is calling. If no challenge is received, then the mobile unit disconnects the call at block 346. If the challenge is received, then the mobile unit returns a response and the platform receives the response at block 348. The response is generated by executing the encryption algorithm on the challenge and the key particular to the mobile unit. If the response generated by the mobile unit does not match the desired response generated by the platform, as determined at block 350, then the call is disconnected by the platform at block 352. If the response is correct, then the platform receives the ultimate number to be called at block 354. If it is determined that this ultimate number to be called is one of the pre-programmed calls at block 356, then the call is connected at block 358. Typically, such a call would be to a user of the central host or a customer. In such a case, voice or data or both can be transmitted. If it is determined at block 356 that the ultimate number to be called is not a pre-programmed number, then an authorization decision is made at block 360. For example, block 360 may compromise a credit card authorization step. If there is no authorization for the call, then the call is disconnected at block 362. If the call is authorized at block 360, for example by entry of a valid credit card number, then the call will be connected at block 364. For data transmissions, the data can be stored at platform 224 and transmitted to central host 226 at various times, as discussed above in connection with “present” messages.

[0122] The system of the present invention provides for several layers of fraud prevention. For calls originating at mobile unit 216, a first layer of protection is the ability to restrict outgoing calls to only pre-programmed calls. Thus, a user of mobile unit 216 may be restricted from calling any unauthorized numbers.

[0123] A second layer of fraud prevention is provided by the requirement that all calls to or from a mobile unit 216 pass through the platform 224. This requirement allows for a myriad of “gatekeeping” functions to be performed at the platform 224. For example, the platform 224 may connect only certain authorized calls from the mobile unit 216, and require a valid credit card for all others calls. Likewise, the platform 224 can ensure that only authorized calls (such as business calls or credit card authorized calls) are directed to the mobile unit 216.

[0124] A third layer of protection is provided by the handshake protocol of the present invention. With this handshake protocol, fraudulent procurement of the MIN/ESN of the mobile unit 216 will be to no avail without knowledge of the handshake protocol. For example, if a call were placed directly to the mobile unit 216, through knowledge of its MIN, the call could not be completed without knowledge of the handshake protocol.

[0125] One of the most popular schemes for defrauding cellular users involves obtaining the MIN/ESN of a particular mobile unit 216, and then cloning a phone with the same MIN/ESN. Such a cloned phone can then be used in most any cellular system, with the cellular usage charges being billed to the original mobile unit 216 as roamer charges. The present invention foils this variety of fraud by requiring that any call using the particular MIN/ESN of mobile unit 216 be directed through the platform 224. As discussed above, this requirement can be accomplished by making arrangements with the local cellular carriers to trap calls having particular MIN/ESNs and route them to the platform 224, or alternatively forcing all mobile units to only call the platform. The platform 224 then requires successful protocol handshaking to connect the call.

[0126] Each mobile unit 216 may be equipped with a unique handshake protocol, and the platform 224 would maintain a data base that associated each mobile unit 216 with its unique handshake protocol. Alternatively, a library of handshake protocols can be maintained, with each mobile unit 216 assigned one of the handshake protocols from that library. The platform 224 would then keep a record of which protocol of the library is assigned to a particular mobile unit 216, and perform handshake protocols accordingly.

[0127] The handshake protocol described herein provides an excellent means of preventing cellular fraud. It should be understood, however, that mobile unit-cellular system-telecommunications platform architecture of the present invention provides technical advantages even without the fraud prevention technique. For example, the ability to gather information on the cellular system location of the mobile units 216 allows for efficient call delivery to these mobile units.

[0128] Throughout this description of the invention, the central host 226, the platform 224, the clearinghouse 222, and the cellular system 212 have been discussed as separate elements. It should be understood that each of these components are logical components, and they may be combined without physical separation. For example, the functions of the platform 224 and the central host 226 may be accomplished at a single site. Likewise, the functions of the platform 224 or clearinghouse 222 may be performed at the local cellular system, for example, at the MTSO.

[0129] The present invention has been discussed in connection with cellular systems. It should be understood that it may also be used in connection with satellite telecommunications systems. For example, the transmission towers 218 and MTSO 220 of FIG. 5 may be replaced with, or used in conjunction with, a satellite telecommunications system. Furthermore, transmissions to and from the mobile unit 216 may be across various channels, such as separate data and voice channels, for example for packet data communications.

[0130] FIG. 12 is a block diagram of the central host 226 constructed according to the teachings of the present invention. As shown in FIG. 12, a central host includes a processor 366 coupled to memory 368. Data transmitted to and received from mobile units is transmitted through modem 370 to and from processor 366. Such data may be stored in memory 368 and displayed on display 372. Furthermore, various data, such as data to be transmitted to remote units, is input through user input/output 374. Data which may be input through user input/output 374, for example, may include the text data to be transmitted to a particular remote unit. Such text data could include particular messages, such as changes in delivery schedules, weather conditions, or the like. Such data is displayed on display 268 of remote unit 216, a shown in FIG. 7. Voice communications between a central host and remote units may be made through voice phone 376. Throughout this description in drawings, separate communications have been shown for data and voice, with the data passing through a modem. It should be understood that a single telecommunications line may be used to provide both voice and data without departing from the intended scope of the present invention.

[0131] In operation of central host 226 of FIG. 12, data and messages received from remote units may be displayed on display 372 and output, for example in hard copy form, through user input/output 374. For example, a map with location identification of each remote unit associated with the central host is displayed on display 372. In this way, the central host 226 can keep track of the location and progress of remote units and for example, vehicles associated with the mobile units. The processor 366 runs software which allows automated sending of data to particular remote units. This data can be automatically generated by processor 366 or input through user input/output 374. Central host can also receive raw location information, that can then be processed in processor 366 to generate latitude and longitude coordinates.

[0132] Processor 366 may also, by tracking the locations of mobile units, based on longitude and latitude and road map information, determine how many miles each mobile unit travels within a particular state. From this information, fleet mileage reports can be generated, for example for trucking companies. These fleet mileage reports can be used to determine the distance traveled and amount of fuel used in various states, which allows for accurate reporting for both fuel and road usage taxes. Furthermore, knowledge of the location of vehicles at particular times, for example from “present” messages or geographic location data, allows for calculation of estimated times of arrivals by dispatchers at central hosts. For example, knowledge that a truck is in Dallas, Tex. on Thursday night allows for an estimate of arrival time in Mobile, Alabama.

[0133] There have been described certain embodiments of the invention that are capable of data messaging in a communications network. While these embodiments have been described and disclosed, other changes, substitutions, or alterations can be made without departing from the spirit and scope of the invention, as described in the appended claims.

Claims

What is claimed is:

1. A method for data messaging using a cellular telephone network by issuing a feature request, comprising:

providing information on an item to be monitored;

generating a feature request having data digits that represent information on the item;

communicating the feature request using the cellular telephone network without opening a voice channel; and

receiving the feature request at a remote location to determine information on the item.

2. The method of claim 1, wherein the step of providing information on an item occurs upon receiving a request to initiate data messaging from the remote location.

3. The method of claim 1, wherein the step of providing information on an item comprises generating information on the item using a sensor.

4. The method of claim 1, wherein the step of communicating the feature request comprises:

receiving the feature request at a switch;

recognizing the feature request at the switch as a feature request for data messaging; and

communicating the feature request from the switch to the remote location upon recognition.

5. The method of claim 1, wherein the feature request comprises a feature request identification code that indicates data messaging and the step of communicating the feature request comprises:

receiving the feature request at a switch;

recognizing the feature request identification code at the switch; and

communicating the feature request from the switch to the remote location upon recognition of the feature request identification code.

6. The method of claim 1, wherein the feature request comprises a cellular transceiver identifier and the step of communicating the feature request comprises:

receiving the feature request at a switch;

comparing the cellular transceiver identifier to a plurality of predetermined identifiers associated with data messaging; and

communicating the feature request from the switch to the remote location if the cellular transceiver identifier matches one of the predetermined identifiers associated with data messaging.

7. The method of claims 1, wherein the feature request comprises a feature request identification code and a cellular transceiver identifier and the step of communicating the feature request comprises:

receiving the feature request at a switch, and

communicating the feature request from the switch to the remote location in response to the feature request identification code and the cellular transceiver identifier.

8. The method of claim 1, wherein the step of receiving comprises:

identifying a cellular transceiver that transmitted the feature request;

translating the data digits to determine information on the item; and

storing information on the item indexed by the cellular transceiver for access by a host operating external to the cellular telephone network.

9. The method of claim 1, wherein the step of receiving comprises:

identifying a cellular transceiver that transmitted the feature request;

translating the data digits to determine information on the item; and

storing information on the item in a time-stamped list of information received from the cellular transceiver for access by a host operating external to the cellular telephone network.

10. The method of claim 1, wherein the feature request comprises an altered identifier of a cellular transceiver that reflects information obtained on the item.

11. The method of claim 1, wherein the feature request comprises a star key followed by the data digits.

12. A method for data messaging by issuing a feature request, comprising:

generating information on an item using a sensor;

generating a feature request having data digits that represent information generated by the sensor;

communicating the feature request using the cellular telephone network without opening a voice channel;

receiving the feature request at a remote location;

translating the data digits to determine information generated by the sensor; and

storing information generated by the sensor for access by a host operating external to the cellular telephone network.

13. The method of claim 12, wherein the sensor is a positioning system that generates location information on the item.

14. The method of claim 12, wherein the feature request comprises a feature request identification code that indicates data messaging, and further comprising:

receiving the feature request at a switch;

recognizing the feature request identification code at the switch; and

communicating the feature request from the switch to the remote location upon recognition of the feature request identification code.

15. The method of claim 12, wherein the feature request comprises a cellular transceiver identifier, and further comprising:

receiving the feature request at a switch;

comparing the cellular transceiver identifier to a plurality of predetermined identifiers associated with data messaging; and

communicating the feature request from the switch to the remote location if the cellular transceiver identifier matches one of the predetermined identifiers associated with data messaging.

16. The method of claim 12, wherein the feature request comprises a feature request identification code and a cellular transceiver identifier, and further comprising:

receiving the feature request at a switch; and

communicating the feature request from the switch to the remote location in response to the feature request identification code and the cellular transceiver identifier.

17. The method of claim 12, wherein the step of storing information generated by the sensor comprises storing information generated by the sensor in a time-stamped list of information received from the cellular transceiver.

18. The method of claim 12, wherein the feature request comprises an altered identifier of a cellular transceiver that reflects information generated by the sensor.

19. The method of claim 12, wherein the item is a vehicle and the sensor is coupled to the vehicle.

20. The method of claim 12, wherein the feature request comprises a star key followed by the data digits.

21. A system for data messaging using a cellular telephone network by issuing a feature request, comprising:

a messaging unit operable to obtain information on an item, the messaging unit further operable to generate a feature request having data digits that represent information on the item, the messaging unit comprising a cellular transceiver operable to communicate the feature request using the cellular telephone network without opening a voice channel;

a remote location coupled to the cellular telephone network, the remote location operable to receive the feature request communicated by the messaging unit, the remote location further operable to translate the data digits to determine the information on the item, the remote location comprising a memory operable to store the information on the item; and

a host coupled to the remote location and operating external to the cellular telephone network, the host operable to access the information on the item stored at the remote location.

22. The system of claim 21, further comprising a switch coupled to the cellular telephone network, the switch operable to receive the feature request communicated by the messaging unit and to communicate the feature request to the remote location upon recognition of a feature request identification code that indicates data messaging.

23. The system of claim 21, further comprising a switch coupled to the cellular telephone network, the switch operable to receive the feature request communicated by the messaging unit and to communicate the feature request to the remote location upon matching a cellular transceiver identifier with one of a plurality of predetermined identifiers associated with data messaging.

24. The system of claim 21, further comprising a switch coupled to the cellular telephone network, the switch operable to receive the feature request communicated by the messaging unit and to communicate the feature request to the remote location in response to a feature request identification code and a cellular transceiver identifier of the messaging unit.

25. The system of claim 21, wherein the messaging unit further comprises a sensor operable to generate information on the item.

26. The system of claim 21, wherein the messaging unit further comprises a positioning system operable to generate location information on the item.

27. The system of claim 21, wherein the item is a vehicle and the messaging unit is coupled to the vehicle.

28. The system of claim 21, wherein the feature request comprises an altered identifier of a cellular transceiver that reflects information obtained on the item.

29. The system of claim 21, wherein the feature request comprises a star key followed by data digits.

30. A system for data messaging using a cellular telephone network by issuing a feature request, comprising:

a messaging unit having a sensor operable to generate information on an item, the messaging unit further operable to generate a feature request having data digits that represent information generated by the sensor, the messaging unit comprising a cellular transceiver operable to communicate the feature request using the cellular telephone network without opening a voice channel;

a switch coupled to the cellular telephone network, the switch operable to receive the feature request communicated by the messaging unit and to communicate the feature request to a remote location if the feature request indicates data messaging;

the remote location coupled to the cellular telephone network, the remote location operable to receive the feature request communicated by the switch, the remote location further operable to translate the data digits to determine information generated by the sensor, the remote location comprising a memory operable to store information generated by the sensor; and

a host coupled to the remote location and operating external to the cellular telephone network, the host operable to access information stored at the remote location.

31. The system of claim 30, wherein:

the feature request comprises a feature request identification code that indicates data messaging; and

the switch is operable to communicate the feature request to the remote location upon recognition of the feature request identification code.

32. The system of claim 30, wherein:

the feature request comprises a cellular transceiver identifier associated with the cellular transceiver of the messaging unit; and

the switch has a memory operable to store a plurality of predetermined identifiers associated with data messaging, the switch further operable to communicate the feature request to the remote location upon matching the cellular transceiver identifier with one of the predetermined identifiers stored at the switch.

33. The system of claim 30, wherein:

the feature request comprises a feature request identification code and a cellular transceiver identifier associated with the cellular transceiver of the messaging unit; and

the switch is operable to communicate the feature request to the remote location in response to the feature request identification code and the cellular transceiver identifier.

34. The system of claim 30, wherein the sensor comprises a positioning system operable to generate location information on the item.

35. The system of claim 30, wherein the feature request comprises an altered identifier of the cellular transceiver that reflects information generated by the sensor.

36. The system of claim 30, wherein the item is a vehicle and the sensor is coupled to the vehicle.

37. The system of claim 30, wherein the feature request comprises a star key followed by the data digits.

38. A messaging unit for data messaging using a cellular telephone network by issuing a feature request, comprising:

a sensor operable to generate information;

a processor coupled to the sensor and operable to receive information generated by the sensor, the processor further operable to generate a feature request having data digits that represent information generated by the sensor; and

a cellular transceiver operable to communicate the feature request using the cellular telephone network without opening a voice channel.

39. The messaging unit of claim 38, further comprising a memory coupled to the processor, the memory operable to accumulate information generated by the sensor, wherein the processor generates a feature request having data digits that represent information accumulated in the memory.

40. The messaging unit of claim 38, wherein the sensor comprises an engine sensor operable to generate performance information on the engine of a vehicle.

41. The messaging unit of claim 38, wherein the sensor comprises a positioning system operable to generate location information.

42. The messaging unit of claim 38, wherein the feature request comprises a star key followed by the data digits.

43. A method for communicating information using a cellular telephone network by issuing a feature request, the method comprising:

generating information using a sensor;

generating a feature request having data digits that represent information generated by the sensor; and

communicating the feature request using a cellular transceiver coupled to the cellular telephone network without opening a voice channel.

44. The method of claim 43 further comprising the step of accumulating in a memory information generated by the sensor.

45. The method of claim 43, further comprising the step of altering an identifier of the cellular transceiver to reflect information generated by the sensor.

46. The method of claim 43, wherein the sensor comprises a positioning system operable to generate location information on the vehicle.

47. The method of claim 43, wherein the feature request comprises a star key followed by the data digits.

48. A system for data messaging using a cellular telephone network by issuing a feature request, comprising:

a messaging unit operable to automatically obtain information on an item, the messaging unit further operable to automatically generate a feature request having data digits that represent information on the item, the messaging unit comprising a cellular transceiver operable to communicate the feature request using the cellular telephone network without opening a voice channel;

a mobile telephone switching office coupled to the cellular telephone network, the switching office operable to receive the feature request communicated by the messaging unit, determine if the feature request is a feature request for data messaging, and communicate the feature request to a telecommunications platform if the feature request is a feature request for data messaging;

the telecommunications platform coupled to the cellular telephone network, the telecommunications platform operable to receive the feature request communicated by the switching office, communicate a validation request, receive a validation response, translate the data digits to determine the information on the item if the messaging unit is valid, and store the information in a memory; and

a host coupled to the telecommunications platform and operating external to the cellular telephone network, the host operable to access the translated information stored at the telecommunications platform.

49. The system of claim 48, wherein:

the telecommunications platform communicates the validation request to the messaging unit;

the messaging unit is further operable to receive the validation request, generate a validation response, and communicate the validation response to the telecommunications platform; and

the telecommunications platform is further operable to receive the validation response and to determine whether the messaging unit is valid based on the validation response.

50. The system of claim 48, further comprising a clearinghouse coupled to the cellular telephone network, the clearinghouse operable to receive the validation request from the telecommunications platform, determine whether the messaging unit is valid, and communicate the validation response to the telecommunications platform.

51. The system of claim 50, wherein:

the telecommunications platform is further operable to communicate a second validation request to the messaging unit;

the messaging unit is further operable to receive the second validation request, generate a second validation response, and communicate the second validation response to the telecommunications platform; and

the telecommunications platform is further operable to receive the second validation response and determine whether the messaging unit is valid based on the second validation response.

52. The system of claim 48, wherein the feature request consists of a star key followed by the data digits.

53. The system of claim 48, wherein the data digits do not alter the features provided by the cellular telephone network.

54. The system of claim 48, wherein the messaging unit's operations to automatically obtain information may be remotely configured from the host.

Patent Citations (219)

Patent	Date	Inventor	Cited By
USH610	1989-03-01	Focarile et al.	Applicant
USRe.34034	1992-08-01	O'Sullivan	Applicant
US3518674	1970-06-01	Moorehead et al.	Applicant
US3680121	1972-07-01	Anderson et al.	Applicant
US3714650	1973-01-01	Fuller et al.	Applicant
US3757290	1973-09-01	Ross et al.	Applicant
US3789409	1974-01-01	Easton	Applicant
US3842208	1974-10-01	Paraskevakos	Applicant
US3848254	1974-11-01	Drebinger et al.	Applicant
US3906166	1975-09-01	Cooper et al.	Applicant
US3937892	1976-02-01	Bloch et al.	Applicant
US3973200	1976-08-01	Akerberg	Applicant
US4053893	1977-10-01	Boyer	Applicant
US4083003	1978-04-01	Haemming	Applicant
US4107689	1978-08-01	Jellinek	Applicant
US4152693	1979-05-01	Ashworth, Jr.	Applicant
US4172969	1979-10-01	Levine et al.	Applicant
US4177466	1979-12-01	Reagan	Applicant
US4222052	1980-09-01	Dunn	Applicant
US4245340	1981-01-01	Landry	Applicant
US4263480	1981-04-01	Levine	Applicant
US4266098	1981-05-01	Novak	Applicant
US4428052	1984-01-01	Robinson et al.	Applicant
US4428057	1984-01-01	Setliff et al.	Applicant
US4435711	1984-03-01	Ho et al.	Applicant
US4445118	1984-04-01	Taylor et al.	Applicant
US4547778	1985-10-01	Hinkle et al.	Applicant
US4590569	1986-05-01	Rogoff et al.	Applicant
US4633464	1986-12-01	Anderson	Applicant
US4644351	1987-02-01	Zabarsky et al.	Applicant
US4646082	1987-02-01	Engel et al.	Applicant
US4651157	1987-03-01	Gray et al.	Applicant
US4654879	1987-03-01	Goldman et al.	Applicant
US4660037	1987-04-01	Nakamura	Applicant
US4670905	1987-06-01	Sandvos et al.	Applicant
US4688244	1987-08-01	Hannon et al.	Applicant
US4692945	1987-09-01	Zdunek	Applicant
US4700374	1987-10-01	Bini	Applicant
US4713808	1987-12-01	Gaskill et al.	Applicant
US4734928	1988-03-01	Weiner et al.	Applicant
US4737978	1988-04-01	Burke et al.	Applicant
US4740792	1988-04-01	Sagey et al.	Applicant
US4742357	1988-05-01	Rackley	Applicant
US4750197	1988-06-01	Denekamp et al.	Examiner
US4754465	1988-06-01	Trimble	Applicant
US4774670	1988-09-01	Palmieri	Applicant
US4775999	1988-10-01	Williams	Applicant
US4776003	1988-10-01	Harris	Applicant
US4788637	1988-11-01	Tamaru	Applicant
US4791571	1988-12-01	Takahashi et al.	Applicant
US4791572	1988-12-01	Green, III et al.	Applicant
US4796189	1989-01-01	Nakayama et al.	Applicant
US4797948	1989-01-01	Milliorn et al.	Applicant
US4799162	1989-01-01	Shinkawa et al.	Applicant
US4804937	1989-02-01	Barbiaux et al.	Applicant
US4809005	1989-02-01	Counselman, III	Applicant
US4814763	1989-03-01	Nelson et al.	Applicant
US4819174	1989-04-01	Furuno et al.	Applicant
US4823123	1989-04-01	Siwiak	Applicant
US4825193	1989-04-01	Siwiak et al.	Applicant
US4825457	1989-04-01	Lebowitz	Applicant
US4831373	1989-05-01	Hess	Applicant
US4833477	1989-05-01	Tendler	Applicant
US4833701	1989-05-01	Comroe et al.	Applicant
US4833702	1989-05-01	Shitara et al.	Applicant
US4837800	1989-06-01	Freeburg et al.	Applicant
US4843575	1989-06-01	Crane	Applicant
US4856047	1989-08-01	Saunders	Applicant
US4860341	1989-08-01	D'Avello et al.	Applicant
US4866762	1989-09-01	Pintar	Applicant
US4868560	1989-09-01	Oliwa et al.	Applicant
US4868859	1989-09-01	Sheffer	Applicant
US4875038	1989-10-01	Siwiak et al.	Applicant
US4876738	1989-10-01	Selby	Applicant
US4882579	1989-11-01	Siwiak	Applicant
US4884208	1989-11-01	Marinelli et al.	Applicant
US4891637	1990-01-01	Siwiak et al.	Applicant
US4891650	1990-01-01	Sheffer	Applicant
US4891761	1990-01-01	Gray et al.	Applicant
US4897642	1990-01-01	DiLullo et al.	Applicant
US4901340	1990-02-01	Parker et al.	Applicant
US4905270	1990-02-01	Ono	Applicant
US4907290	1990-03-01	Crompton	Applicant
US4908629	1990-03-01	Apsell et al.	Applicant
US4912756	1990-03-01	Hop	Applicant
US4914651	1990-04-01	Lusignan	Applicant
US4914686	1990-04-01	Hagar, III et al.	Applicant
US4928096	1990-05-01	Leonardo et al.	Applicant
US4940963	1990-07-01	Gutman et al.	Applicant
US4945570	1990-07-01	Gerson et al.	Applicant
US4953198	1990-08-01	Daly et al.	Applicant
US4963865	1990-10-01	Ichikawa et al.	Applicant
US4964163	1990-10-01	Berry	Applicant
US4993059	1991-02-01	Smith et al.	Applicant
US4993062	1991-02-01	Dula et al.	Applicant
US4998291	1991-03-01	Marui et al.	Applicant
US5003317	1991-03-01	Gray et al.	Applicant
US5005014	1991-04-01	Jasinski	Applicant
US5008814	1991-04-01	Mathur	Applicant
US5014206	1991-05-01	Scribner et al.	Applicant
US5019963	1991-05-01	Alderson et al.	Applicant
US5025253	1991-06-01	DiLullo et al.	Applicant
US5027383	1991-06-01	Sheffer	Applicant
US5032845	1991-07-01	Velasco	Applicant
US5043736	1991-08-01	Darnell et al.	Applicant
US5045861	1991-09-01	Duffett-Smith	Applicant
US5046082	1991-09-01	Zicker et al.	Applicant
US5047763	1991-09-01	Kuznicki et al.	Applicant
US5048015	1991-09-01	Zilberfarb	Applicant
US5055851	1991-10-01	Sheffer	Applicant
US5058201	1991-10-01	Ishii et al.	Applicant
US5068656	1991-11-01	Sutherland	Applicant
US5077830	1991-12-01	Mallia	Applicant
US5090050	1992-02-01	Heffernan	Applicant
US5101500	1992-03-01	Marui	Applicant
US5119102	1992-06-01	Barnard	Applicant
US5121126	1992-06-01	Clagett	Applicant
US5121325	1992-06-01	DeJonge	Applicant
US5124697	1992-06-01	Moore	Applicant
US5128979	1992-07-01	Reich et al.	Applicant
US5131019	1992-07-01	Sheffer et al.	Applicant
US5131020	1992-07-01	Liebesny et al.	Applicant
US5142279	1992-08-01	Jasinski et al.	Applicant
US5142281	1992-08-01	Park	Applicant
US5142654	1992-08-01	Sonberg et al.	Examiner
US5148473	1992-09-01	Freeland et al.	Applicant
US5153582	1992-10-01	Davis	Applicant
US5153902	1992-10-01	Buhl et al.	Applicant
US5153903	1992-10-01	Eastmond et al.	Applicant
US5153904	1992-10-01	Coombes et al.	Applicant
US5155490	1992-10-01	Spradley, Jr. et al.	Applicant
US5155689	1992-10-01	Wortham	Applicant
US5155847	1992-10-01	Kirouac et al.	Applicant
US5159625	1992-10-01	Zicker	Applicant
US5162790	1992-11-01	Jasinski	Applicant
US5166694	1992-11-01	Russell et al.	Applicant
US5172321	1992-12-01	Ghaem et al.	Applicant
US5175758	1992-12-01	Levanto et al.	Applicant
US5208756	1993-05-01	Song	Applicant
US5222123	1993-06-01	Brown et al.	Applicant
US5223844	1993-06-01	Mansell et al.	Applicant
US5225842	1993-07-01	Brown et al.	Applicant
US5235598	1993-08-01	Sasuta	Applicant
US5235633	1993-08-01	Dennison et al.	Applicant
US5237612	1993-08-01	Raith	Applicant
US5239294	1993-08-01	Flanders et al.	Applicant
US5239678	1993-08-01	Grube et al.	Applicant
US5241598	1993-08-01	Raith	Applicant
US5243529	1993-09-01	Kashiwazaki	Applicant
US5247564	1993-09-01	Zicker	Applicant
US5247700	1993-09-01	Wohl et al.	Applicant
US5248215	1993-09-01	Fladung	Applicant
US5252982	1993-10-01	Frei	Applicant
US5255306	1993-10-01	Melton et al.	Applicant
US5261118	1993-11-01	Vanderspool, II et al.	Applicant
US5270936	1993-12-01	Fukushima et al.	Applicant
US5276729	1994-01-01	Higuchi et al.	Applicant
US5278890	1994-01-01	Beeson, Jr. et al.	Applicant
US5293163	1994-03-01	Kakihara et al.	Applicant
US5293576	1994-03-01	Mihm, Jr. et al.	Applicant
US5295178	1994-03-01	Nickel et al.	Applicant
US5297191	1994-03-01	Gerszberg	Applicant
US5297192	1994-03-01	Gerszberg	Applicant
US5299132	1994-03-01	Wortham	Applicant
US5305466	1994-04-01	Taketsugu	Applicant
US5307509	1994-04-01	Michalon et al.	Applicant
US5311194	1994-05-01	Brown	Applicant
US5323322	1994-06-01	Mueller et al.	Applicant
US5327478	1994-07-01	Lebowitz	Applicant
US5335278	1994-08-01	Matchett et al.	Applicant
US5341410	1994-08-01	Aron et al.	Applicant
US5343493	1994-08-01	Karimullah	Applicant
US5365516	1994-11-01	Jandrell	Applicant
US5369681	1994-11-01	Boudreau et al.	Applicant
US5377193	1994-12-01	Grube et al.	Applicant
US5382970	1995-01-01	Kiefl	Applicant
US5392458	1995-02-01	Sasuta et al.	Applicant
US5396539	1995-03-01	Slekys et al.	Applicant
US5396540	1995-03-01	Gooch	Applicant
US5404392	1995-04-01	Miller et al.	Examiner
US5410737	1995-04-01	Jones	Applicant
US5420911	1995-05-01	Dahlin et al.	Applicant
US5423056	1995-06-01	Linquist et al.	Applicant
US5454027	1995-09-01	Kennedy et al.	Applicant
US5463672	1995-10-01	Kage	Applicant
US5506886	1996-04-01	Maine et al.	Applicant
US5513243	1996-04-01	Kage	Applicant
US5517690	1996-05-01	Linquist et al.	Applicant
US5519621	1996-05-01	Wortham	Examiner
US5526398	1996-06-01	Okada et al.	Applicant
US5533094	1996-07-01	Sanmugam	Applicant
US5539810	1996-07-01	Kennedy, III et al.	Applicant
US5544225	1996-08-01	Kennedy, III et al.	Applicant
US5546444	1996-08-01	Roach, Jr. et al.	Applicant
US5594740	1997-01-01	LaDue	Applicant
US5752976	1998-05-01	Duffin et al.	Applicant
US5771445	1998-06-01	Kennedy et al.	Examiner
US5771455	1998-06-01	Kennedy, et al.	Examiner
US5787149	1998-07-01	Yousefi et al.	Applicant
US5826195	1998-10-01	Westerlage et al.	Applicant
US5845203	1998-12-01	LaDue	Applicant
US5913170	1999-06-01	Wortham	Applicant
US5950122	1999-09-01	Foladare et al.	Applicant
US5974331	1999-10-01	Cook et al.	Applicant
US5983108	1999-11-01	Kennedy, III et al.	Applicant
AU3767589	1993-02-01		Applicant
DE3516357	1986-11-01		Applicant
EP242099	1987-10-01		Applicant
EP290725	1988-11-01		Applicant
EP367935	1990-05-01		Applicant
EP417944A2	1991-03-01		Applicant
GB2193861	1988-02-01		Applicant
GB2221113	1993-01-01		Applicant
JP161941	1984-09-01		Applicant
JP175537	1988-07-01		Applicant
JP219238	1988-09-01		Applicant
JP226226	1989-09-01		Applicant
WO8904035	1989-05-01		Applicant
WO8912835	1989-12-01		Applicant

Non-Patent Literature (38)

“Trimpack” Brochure, TrimbleNavigation, date unknown, 1 page.Applicant
Gary D. Ott, “Vehicle Location in Cellular Mobile Radio Systems,” IEEE, vol. VT-26, No. 1, Feb., 1977, pp. 43-46.Applicant
James C. Reynolds, et al., “GPS-Based Vessel Position Monitoring and Display System,” IEEE, 1990, pp. 601-607.Applicant
R. DeSadaba, “Personal Communications in the Intelligent Network,” British Telecommunications Engineering, vol. 9, Aug., 1990, pp. 80-83.Applicant
“GPS Navstar Global Positioning System User's Overview—YEE-82-009D,” Navstar Global Positioning System Joint Program Office, Mar., 1991, pp. 1-164.Applicant
“U.S. Coast Guard Differential GPS” Brochure, U.S. Department of Transportation, United States Coast Guard, May, 1993.Applicant
“GPS Facts & Figures” Brochure, U.S. Department of Transportation, United States Coast Guard, May, 1993.Applicant
D. H. Alsip, J. M. Butler, and J. T. Radice, “Implementation of the U.S. Coast Guard's Differential GPS Navigation Service,” U.S. Coast Guard Headquarters, Office of Navigation Safety and Waterway Services, Radionavigation Division, Jun. 28, 1993, pp. 1-10.Applicant
“Motorola GPS Technical Reference Manual,” Motorola, Oct., 1993, Manual Cover, Title Page, and p. 4-109.Applicant
Don Burtis, “CDPD—A Bandwidth Optimization Technique for Cellular Telephones,” Computer Design's OEM Integration, May, 1994, pp. 19-20.Applicant
“U.S. Coast Guard Bulletin System File ‘FRP-DGPS,’” U.S. Coast Guard, Date Unknown, pp. 1-6.Applicant
Gene L. Schlechte, LCDR, “U.S. Coast Guard Bulletin Board System Document ‘Design.TXT’—Design Process for the United States Coast Guard's Differential GPS Navigation Service,” U.S. Coast Guard, U.S. Coast Guard Omega Navigation System Center, Date Unknown, pp. 1-21.Applicant
“Appendix B, The 1991 Radionavigation User Conference,” Department of Transportation, Date Unknown, pp. 1-2.Applicant
Kirk Ladendorf, First in Flight—Using State-Of-The-Art Technology, Austin-Based Arrowsmith Technologies Establishes Itself As A Major Player in Nascent Technology-Supplier Market, Austin America-Statesman, Jan. 30, 1995, 3 pages.Applicant
International Patent Search dated Jun. 20, 1995, PCT/US94/08351.Applicant
Sarnecki, et al., “Microcell Design Principles”, IEEE Communications Magazine, Apr. 1993, pp. 76-82.Applicant
Bell South, CellemetrySM, “We have ways to make you talk!,” 5 pages, undated.Applicant
BellSouth Wireless, Inc., CellemetrySM by BellSouth, Application Developers Kit, “It's potential is limited only by your imagination,” Copyright 1996, 8 pages.Applicant
BellSouth Wireless, Inc., Cellemetry News, “Bell Mobility to Use BellSouth's Cellemetry,” 1996, 4 pages.Applicant
BellSouth Wireless, Inc., Thomas F. Evans, “Cellemetry Telemetry Via Cellular,” 1996, 6 pages.Applicant
BellSouth News Release, “BellSouth Teams Up with Commnet, Skywire to Provide First U.S. Deployment of CellemetrySM Wireless Service,” May 20, 1996, 3 pages.Applicant
Jason Meyers, “BellSouth puts a new slant on wireless data service,” Telephony™ (Copyright 1995 by INTERTEC® Publishing, Chicago, Ill., Jul. 31, 1995, 1 page.Applicant
Kelly Pate, “BellSouth tests new technology for wireless tracking capability,” Radio Communications Report, vol. 14, No. 15, Aug. 7, 1995, 1 page.Applicant
Mobile Phone News®, Phillips Business Information, Inc., vol. 13, No. 32, Aug. 7, 1995, 1 page.Applicant
Thomas F. Evans, CellemetrySM Network Access Strategy, BellSouth Wireless, Inc., Abstract and Summary, undated 3 pages.Applicant
Author Unknown, “National Applications,” undated, 3 pages.Applicant
Michel Mouly and Marie-Bernadette Pautet, The GSM System, 1992, pp. 56-59.Applicant
European Telecommunications Standard ETS 300 537, GSM Global System For Mobile Communications—Digital cellular telecommunications system (Phase 2); Technical realization of Short Message Service Cell Broadcast (SMSCB) (GSM 03.41), European Telecommunications Standards Institute, May, 1996, 32 pages.Applicant
European Telecommunications Standard ETS 300 536, GSM Global System For Mobile Communications—Digital cellular telecommunications system (phase 2); Technical realization of the Short Message Service (SMS) Point-to-Point (PP) (GSM 03.40), European Telecommunications Standards Institute, Oct. 1996, 106 pages.Applicant
“EIA/TIA Interim Standard—Cellular Radiotelecommunications Intersystem Operations: Functional Overview,” EIA/TIA/IS-41.1-B, Electronic Industries Association Engineering Department, Jan., 1992, 14 pages and table of contents.Applicant
“EIA/TIA Interim Standard—Cellular Radiotelecommunications Intersystem Operations: Intersystem Handoff,” EIA/TIA/IS-41.2-B, Electronic Industries Association Engineering Department, Jan., 1992, 25 pages and table of contents.Applicant
“EIA/TIA Interim Standard—Cellular Radiotelecommunications Intersystem Operations: Automatic Roaming,” EIA/TIA/IS-41.3-B, Electronic Industries Association Engineering Department, Jan., 1992, 58 pages and table of contents.Applicant
“EIA/TIA Interim Standard—Cellular Radiotelecommunications Intersystem Operations: Operations, Administration, and Maintenance,” EIA/TIA/IS-41.4-B, Electronic Industries Association Engineering Department, Jan., 1992, 29 pages and table of contents.Applicant
“EIA/TIA Interim Standard—Cellular Radiotelecommunications Intersystem Operations: Data Communications,” EIA/TIA/IS-41.5-B, Electronic Industries Association Engineering Department, Jan., 1992, 84 pages and table of contents.Applicant
“EIA/TIA Interim Standard—Cellular Radio-Telecommunications Intersystem Operations: Automatic Roaming,” EIA/TIA/IS-41.3-B, Electronic Industries Association Engineering Department, Dec., 1991, 64 pages and table of contents.Applicant
EPO Communication Supplemental Search Report in Application No. 94923566.7-1522-US9408346, dated Jul. 16, 1999, 3 pages.Applicant
Kevin Holley, “The GSM Short Message Service,” Services and Standards Department of Cellnet, 1990, 5 pages.Applicant
Bogut, et al., “Scanning Locator System,” Motorola Inc. Technical Developments, vol. 12, Apr., 1991, 3 pages.Applicant

Abstract