throbber
US007123926B2
`
`(12)
`
`United States Patent
`Himmelstein
`
`(10) Patent No.:
`(45) Date of Patent:
`
`US 7,123,926 B2
`*Oct. 17, 2006
`
`(54) SYSTEM AND METHOD FOR PROVIDING
`INFORMATION TO USERS BASED ON THE
`USERS LOCATION
`
`(76) Inventor: Richard B. Himmelstein, 857 Fort
`Fisher Blvd. South, Kure Beach, NC
`(US) 28449
`
`(*) Notice:
`
`Subject to any disclaimer, the term of this
`patent is extended or adjusted under 35
`U.S.C. 154(b) by 162 days.
`
`This patent is Subject to a terminal dis-
`claimer.
`
`(21) Appl. No.: 10/705,674
`
`(22) Filed:
`
`Nov. 10, 2003
`
`(65)
`
`Prior Publication Data
`US 2004/O145459 A1
`Jul. 29, 2004
`
`5, 1995 James ........................ 701 117
`5,420,794. A
`6/1995 Sprague et al.
`5,422,816 A
`6, 1995 Mui
`5.425,058 A
`5,459,304 A * 10/1995 Eisenmann ................. 235,380
`5,473,602 A 12/1995 McKenna et al.
`5,539,398 A
`7, 1996 Hall et al.
`5,572.201 A 11/1996 Graham et al.
`5,663,734. A
`9/1997 Krasner
`5,740,532 A * 4/1998 Fernandez et al. ....... 455,404.1
`5,805,082 A
`9, 1998 Hassett
`5,875, 183 A
`2f1999 Nitadori
`5,900,825 A
`5/1999 Pressel et al.
`5,908.454 A
`6/1999 Zyburt et al.
`5,952,941 A
`9, 1999 Mardirossian
`5,974,368 A 10/1999 Schepps et al.
`5,982.281 A * 11/1999 Layson, Jr. ............ 340,539.13
`5,983, 161 A 11/1999 Lemelson et al.
`
`(Continued)
`OTHER PUBLICATIONS
`
`O
`O
`Related U.S. Application Data
`(63) Continuation of application No. 09/659,074, filed on
`Sep. 11, 2000, now Pat. No. 6,647,270.
`(60) Provisional application No. 60/153.424, filed on Sep.
`10, 1999.
`
`(51) Int. Cl.
`(2006.01)
`H04O 7/20
`(52) U.S. Cl. ............................... 455/456.1:455/456,3;
`455/416:455/518; 455/414.2:455/521: 342/357.1;
`342/.457; 701/207
`(58) Field of Classification Search ............. 455/404.1,
`455/404.2, 412.2, 414.2, 414.3, 456.1–457,
`455/521: 701/207,214, 216; 340/988:
`342/357.1, 457; 702/3
`See application file for complete search history.
`References Cited
`
`(56)
`
`U.S. PATENT DOCUMENTS
`4,591,823. A
`5, 1986 Horvat ....................... 340/936
`5,170,499 A * 12/1992 Grothause ................ 455,238.1
`
`Yahoo Finance “Private Inventor files Patent Application for
`Telematics-Based Public and Emergency First Re:S Safety
`Advisory System” Feb. 4, 2004 (4 pgs).
`(Continued)
`Primary Examiner Steve M. D’Agosta
`(74) Attorney, Agent, or Firm—Benesch Friedlander LLP:
`Jeffrey L. Brandt; Robert B Lech
`
`(7)
`
`ABSTRACT
`
`A system for providing an advisory communication to a user
`via a mobile unit includes locating means for locating the
`position of the mobile unit and sending means for sending a
`communication to the mobile unit. The mobile unit includes
`alerting means for alerting the user of the communication.
`The advisory communication can include information relat
`ing to an approaching emergency Vehicle, an accident Scene,
`road conditions, a traffic signal, traffic conditions, or weather
`conditions.
`
`36 Claims, 7 Drawing Sheets
`
`-N
`
`
`
`4.
`
`BASESAON
`CONTROLLER
`
`Exhibit 1015
`IPR2022-0427
`Page 1 of 19
`
`

`

`US 7,123,926 B2
`Page 2
`
`U.S. PATENT DOCUMENTS
`
`1/2000 Rosen et al. ................ 340,905
`6,014,090 A
`1/2000 Baron et al. ...
`... 702/3
`6,018,699 A *
`6,052,598 A * 4/2000 Rudrapatna et al. ..... 455,456.1
`6,060,995 A * 5/2000 Wicks et al. ............... 340,748
`6,097,974 A
`8/2000 Camp et al.
`
`
`
`6,177,873 B1* 1/2001 Cragun - - - - - - - - - - - - - - - - - - - - - - - 340,601
`
`6,199,045 B1* 3/2001 Giniger et al. ................. 70.5/1
`6,208,844 B1
`3/2001 Abdelgany
`6,208,862 B1
`3, 2001 Lee
`6,225,890 B1
`5/2001 Murphy
`6,252,539 B1
`6/2001 Phillips et al.
`6.255,953 B1
`7/2001 Barber
`85.60 R
`39. R et al.
`6.466,796 B1 * 10, 2002 J al
`tal
`6,480.699 B1
`11, 2002 s son et al. ........
`6.498.987 B1
`12, 2002 K. tal
`6.505.133 B1
`1, 2003 R :
`i
`6,526.268 B1* 2, 2003 R al 1
`- 4 W
`aal C al. ...........
`6,539,232 B1
`3/2003 Hendrey et al.
`6542,748 B1
`4/2003 Hendrew etal
`- 14
`endrey et al.
`6,542,749 B1
`4/2003 Tanaka et al.
`863 R 2. sdrey tal.
`6603-405 B1
`8, 2003 S. beg
`6. 6 is. 593 B1
`9, 2003 SM tal
`6,646.559 B1
`11, 2003 SNA a C a.
`6,647.270 Bf
`11/2003 R lstei
`w I
`See
`6,654,689 B1
`11/2003 Kelly et al.
`6.678,516 B1
`1/2004 Nordman et al.
`s
`sy
`6,700,482 B1
`3, 2004 Ververs et al.
`6,728.323 B1
`4/2004 Ch
`tal
`6.72s. 528 B1
`4, 2004 L s gal,
`6.74 5.02 1 B1
`6, 2004 s e
`I -
`WS
`6,754,585 B1
`6, 2004 Root et al.
`6,819,919 B1
`1 1/2004 Tanaka
`6,853,849 B1
`2/2005 Tognazzini
`2001/0147766
`10, 2002 Vanska et al.
`2002/0147766 A1 10, 2002 Vanska et al.
`2002/0174073 A1
`11/2002 Nordman et al.
`
`455,456.3
`
`455,186.1
`
`9/2003 Taylor
`2003. O169181 A1
`9/2003 Taylor
`2003. O169185 A1
`9/2003 Taylor
`2003/07691.81
`1/2004 Sinn et al.
`2004/0010591 A1
`1/2004 Stevens
`2004, OO14457 A1
`7/2004 Himmelstein
`2004/0145459 A1
`2004/0203931 A1 10/2004 Karaoguz
`
`2004/024.8569 A1 12/2004 Kondou et al.
`
`1/2005 Dinnage et al.
`2005, 0021666 A1
`2005/0233741 A1 10, 2005 Zamani
`
`OTHER PUBLICATIONS
`Selingo, Jeffrey “Protecting the Cellphone User's Rights to Hide'
`Feb. 5, 2004 (2 pgs.)
`Match.com Corporate "Match.com's Wireless Dating Service
`MatchMobile Launches Photo Profiles' (2 pgs).
`Match.com Corporate “Match.com Launches Match Mobile
`Launches with AT&T Wireless” (2 pgs).
`AT&T Wireless “Our Biggest Store: Organization” (2 pgs).
`AT&T Wireless “Features and Services User Guide” (2 pgs).
`http://wwwal accuweather.com/iwxpage/adc/mobile/messenger.htm
`(admitted, not prior art).
`"Match.com Launches Match Mobile with AT&T Wireless', Match.
`com Corporate, Dec. 2003
`“Match.com's Wireless Dating Service MatchMobile Launches
`Photo Profiles'. Match.com Corporate, Dec. 2003.
`“Our Biggest Store: Organization Find People Nearby, AT&T
`Wireless, http://www.attwireless.com/personal/features/organiza
`tion/findfriends.jhtml, Feb. 2004.
`AT&T Wireless, "Features and Services User Guide, How to Use
`Your AT&T Wireless Features and Services'.
`Selingo, “Protecting the Cellphone User's Right to Hide'. The New
`York Times, nytimes.com, Feb. 5, 2004.
`Yahoo Finance, "Private Inventor Files Patent Application for
`Telematics-Based Public and Emergency First Reponders Safety
`Advisory System'. Feb. 2004, http://biz.yahoo.com/prnews/
`040204/law 0211.html
`http://wwwa.accuweather.com/iwxpage/adc/mobile/messenger.htm
`(admitted, not prior art)
`US 6,731,928, 05/2004, Tanaka (withdrawn)
`* cited by examiner
`
`Exhibit 1015
`IPR2022-0427
`Page 2 of 19
`
`

`

`U.S. Patent
`
`Oct. 17, 2006
`
`Sheet 1 of 7
`
`US 7,123,926 B2
`
`
`
`22
`
`
`
`BASE STATION
`CONTROLLER
`
`14
`
`16
`
`16
`
`16
`
`-16
`
`FIG. 1
`
`Exhibit 1015
`IPR2022-0427
`Page 3 of 19
`
`

`

`U.S. Patent
`
`Oct. 17, 2006
`
`Sheet 2 of 7
`
`US 7,123,926 B2
`
`33
`
`- - - - - - - - - - - - - - - - - - - -
`
`-
`
`-
`
`-
`
`- - - - - - - - - -
`
`
`
`RF
`RECEIVER
`
`32
`
`
`
`4
`
`35
`
`MICRO
`PROCESSOR
`
`46
`
`41
`
`
`
`
`MEMORY
`
`ELECTRO
`MECHANICAL
`INTERFACE
`
`
`
`
`
`
`
`
`
`COMMUNICATION PACKET
`FIG. 3A
`
`51 N.
`
`
`
`55
`
`56
`
`57
`
`ADMINISTRATIVE
`
`SENDER
`
`RECEIVER
`
`INFORMATION FIELDS
`FIG. 3B
`
`Exhibit 1015
`IPR2022-0427
`Page 4 of 19
`
`

`

`U.S. Patent
`
`Oct. 17, 2006
`
`Sheet 3 of 7
`
`US 7,123,926 B2
`
`
`
`
`Sdials|ee|go,NOUWNILSSG|NOILVNISIYO}NOILOSYIC]
`
`
`
`JE‘OldSQTAlsVIVGSALLVYLSININGY
`
`AEYiSd7Al4VIVOY3SAIF93uY
`
`GEJdSq7aldVLva¥3qNas
`
`4IeOlaSG1aI4HSSWNNGiHS0NSS
`FIOINSA|SIOIHSA|STOIHSA|HaawAN|JTOIHAA opegeesbgzB18
`
`ssaloor|+++|ssateasafoav‘vata
`
` 4OSSAYqavssauaayv|sSay¥qavWaaninn
`
`U08208qog
`
`YAISILNACI|-LNIOdaAotid|ALIHNOaSYO|4OLNOYO}
`
`
`
`WOO_[1s¥OdvOUS|WALSASNI
`
`
`
`
`HOLVHSd0JHOLVH3dO|HOLWH3dO|JO}3009STOIHSA
`e#dlz#'d'l#d'1|SHOLVHSd0
`
`
`
`Exhibit 1015
`IPR2022-0427
`Page 5 of 19
`
`Exhibit 1015
`IPR2022-0427
`Page 5 of 19
`
`
`
`

`

`U.S. Patent
`
`Oct. 17, 2006
`
`Sheet 4 of 7
`
`US 7,123,926 B2
`
`ADVSSAN
`
`39nd3y
`
`NOLLONHISNI
`
`|
`
`426!26IZ6y6qz6&26
`TOHINODG33d8}9|||BezLvEesro00z/L0/60|80:21
`
`
`
`SLNALNOOIOANI210%|wunoas4OLNONI|/LSvoavOHALIWOldd|SASSAYAGY|pgniwogni|LVSWIL
`
`
`
`
`
`I44VYLASvG81Z96cEr000¢/10/60}¢S-80
`
`
`
`
`JOYULNOO]SOIOAWALSAS|LNIOd-OL-LNIOdSNIODLNO
`106206p06206qos26\_a
`2662612682PZ6926
`
`GP‘Dla
`
`VPOld
`
`
`
`KRa
`
`Exhibit 1015
`IPR2022-0427
`Page 6 of 19
`
`Exhibit 1015
`IPR2022-0427
`Page 6 of 19
`
`
`
`

`

`U.S. Patent
`U.S. Patent
`
`Oct. 17, 2006
`
`Sheet 5 of 7
`
`US 7
`
`2
`
`123,926 B2
`123,926 B2
`
`
`
`3009
`
`oganny{fANNOOOV
`
`ONDYVd
`
`YdaWnn
`
`KOMN0d
`
`po1aq00WSIVA
`yo109|ssauaay|ava
`
`
`
`SWIL
`
`80/1
`
`POLL90h}
`
`GOb}
`
`IbDid
`
`OP‘Did
`
`Exhibit 1015
`IPR2022-0427
`Page 7 of 19
`
`Exhibit 1015
`IPR2022-0427
`Page 7 of 19
`
`

`

`U.S. Patent
`
`Oct. 17, 2006
`
`Sheet 6 of 7
`
`US 7,123,926 B2
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`502
`Y
`
`ADDRESS MATCH
`
`CREATE CONTACT
`LOG ENTRY
`
`530
`
`506
`
`508
`
`
`
`STORE I
`PACKET
`
`
`
`ARE
`OTHER
`PACKETS
`PENDING
`
`ARE
`THEY LOWER THAN
`NEW PACKET
`
`
`
`524
`
`HALT PROCESSING
`OF PENDING PACKET
`
`STORE PENDING
`PACKET
`
`526
`
`STORE NEW
`PACKET IN
`OUEUE
`
`CONTINUE TO
`PROCESS
`PENDING
`PACKET
`
`
`
`520
`
`522
`
`
`
`PROCESS NEW
`PACKET
`
`
`
`RE-PRIORITIZE QUEUEN
`ACCORDANCE WITH PRIORITY
`OF PENDING PACKETS
`
`S512
`
`GO TONEXT
`PACKET
`
`FIG. 5
`
`Exhibit 1015
`IPR2022-0427
`Page 8 of 19
`
`

`

`U.S. Patent
`
`Oct. 17, 2006
`
`Sheet 7 Of 7
`
`US 7,123,926 B2
`
`START
`
`602
`
`PARSE PACKET INTO FIELDS
`
`604
`
`STORE FIELDS THAT DO NOT
`RECURE ADD'L PROCESSING
`
`606
`
`
`
`PACKETA
`DATA COMMUN.
`
`
`
`610
`
`Y
`
`
`
`
`
`PACKETA
`CONTROL
`COMMUN.
`
`608
`
`614
`
`PROCESS COMMUN.
`AS CONTROL
`INSTRUCTION
`
`PROCESS
`COMMUN.
`AS INFO
`
`PROCESS
`COMMUN.
`AS VOICE
`
`616
`
`
`
`
`
`COMPARE CONTROL
`INSTRUCTION TO
`SECURITY LEVEL
`REOUIRED
`
`Y
`
`618
`
`N
`
`622
`
`PERFORM
`CONTROL
`INSTRUCT
`
`620
`
`NOTIFY BOTH
`SENDER AND
`RECIPIENT OF DENIAL
`
`FIG. 6
`
`GO TONEXT
`PACKET
`
`624
`
`Exhibit 1015
`IPR2022-0427
`Page 9 of 19
`
`

`

`US 7,123,926 B2
`
`1.
`SYSTEMAND METHOD FOR PROVIDING
`INFORMATION TO USERS BASED ON THE
`USERS LOCATION
`
`CROSS REFERENCE TO RELATED
`APPLICATION
`
`5
`
`This application claims priority from U.S. application Ser.
`No. 09/659,074 filed Sep. 11, 2000, issued as U.S. Pat. No.
`6,647,270 on Nov. 11, 2003, which in turn claims priority 10
`from U.S. Provisional Application No. 60/153,424 filed Sep.
`10, 1999, which are incorporated by reference as if fully set
`forth herein.
`
`BACKGROUND
`
`15
`
`25
`
`30
`
`The present invention generally relates to communication
`systems. More particularly, the invention relates to a mobile
`communication system which allows mobile vehicles to
`communicate with neighboring vehicles and roadside com- 20
`munication networks.
`Various communication systems have been used by auto
`mobile drivers to communicate with other vehicles while the
`vehicle is in motion. While many advances have been made
`in vehicle to vehicle communication, numerous disadvan
`tages still remain in using conventional communication
`systems.
`Conventional mobile communication systems include cel
`lular telephones and CB or two-way radio. When using a cell
`phone as a means of mobile communication, there is no
`practical way of discovering whether a neighboring vehicle
`operator possesses a cell phone. Additionally, there is no
`process for determining the phone number of the targeted
`cell phone. Accordingly, the cell phone as a communication
`medium is severely limited.
`CB radio is a widely broadcast public medium where
`mobile users may talk to other mobile or stationary users in
`their vicinity. However, since there is no ability to prevent
`others from listening, there is no privacy between mobile
`40
`communicators.
`Automobile accidents are one of the greatest causes of
`serious injury and fatalities in Society. Accordingly, the
`development of improved control and warning systems to
`minimize personal and financial losses resulting from auto
`45
`mobile accidents is of utmost importance. The limitations of
`present forms of communication are even more severe when
`considering the extent to which a communication link can
`improve both the driving experience and the safety statistics
`of modern vehicles.
`
`35
`
`50
`
`SUMMARY
`
`The present invention provides a communication link
`among vehicles which eliminates these pitfalls. The system 55
`comprises a broadband RF transceiver with antenna, a
`position determining means (such as a GPS receiver) an
`audio-visual interface, an electromechanical interface, and a
`microprocessor with associated memory. These components
`are incorporated into a mobile unit located within each 60
`vehicle.
`The GPS receiver receives signals from GPS satellites and
`calculates the position of the vehicle. The microprocessor
`carries out overall control of the system. The memory
`includes identification information that is unique to each 65
`vehicle. In response to input from the GPS receiver, infor
`mation received by the transceiver and instructions input by
`
`2
`the vehicle operator via the audio-visual interface, the
`microprocessor determines the necessary Subsequent
`actions.
`The transmission from a vehicle may include information
`describing the status of the vehicle for use by the receiving
`vehicle. For example, the transmission may provide infor
`mation regarding the speed, direction, and position of the
`transmitting vehicle. This information is received and pro
`cessed by the receiving vehicle to provide a visual or audible
`display of the position, direction, and speed of the transmit
`ting vehicle.
`According to one aspect of the present invention, there is
`provided a communication system for transmitting informa
`tion between a mobile unit within a vehicle traveling on a
`road and a fixed communication network installed on a
`roadside. The fixed communication network includes a base
`station having a transceiver for communicating with the
`vehicle by transmitting and receiving a plurality of commu
`nication packets. This communication can include payment
`instructions, security instructions, and/or access codes
`which can be transmitted with or without intervention by the
`vehicle operator.
`
`BRIEF DESCRIPTION OF THE DRAWING(S)
`FIG. 1 shows a vehicle communication system embody
`ing the present invention.
`FIG. 2 is a block diagram showing a mobile unit in
`accordance with the preferred embodiment.
`FIG. 3A is a diagram illustrating the contents of a com
`munication packet transmitted by the mobile unit shown in
`FIG. 2.
`FIG. 3B illustrates the header of the communication
`packet.
`FIG. 3C illustrates the information fields of the header's
`transmission administration.
`FIG. 3D illustrates the information fields of the header's
`sender portion.
`FIG. 3E illustrates the information fields of the header's
`receiver portion.
`FIG. 3F illustrates the sub fields contained in the identi
`fication number field.
`FIG. 4A illustrates the memory of a typical mobile unit
`shown in FIG. 2.
`FIG. 4B is a diagram of a vehicle communication log.
`FIG. 4C is a diagram of a vehicle user log.
`FIG. 4D is a diagram of a vehicle contact log.
`FIG. 5 is a flow diagram of the procedure utilized by the
`microprocessor upon receipt of a communication packet.
`FIG. 6 is a flow diagram of the procedure for processing
`communication packets.
`
`DETAILED DESCRIPTION OF THE
`PREFERRED EMBODIMENT(S)
`
`The preferred embodiment will be described with refer
`ence to the drawing figures where identical numerals rep
`resent similar elements throughout.
`A vehicle communication system embodying the present
`invention is shown in FIG. 1. The vehicle communication
`system 10 generally includes one or more base stations 14,
`each of which is in wireless communication with a plurality
`of remote units 16. Although the remote units 16 may be
`fixed or mobile, they will be referred to hereinafter for
`simplicity as mobile units 16. Each mobile unit 16 can
`communicate with another mobile unit 16, the closest base
`station 14, or the base station 14 which provides the stron
`
`Exhibit 1015
`IPR2022-0427
`Page 10 of 19
`
`

`

`15
`
`3
`gest communication signal. The base stations 14 communi
`cate with a base station controller 20, which coordinates
`communications among base stations 14 and mobile units
`16. The communication system 10 may be connected to a
`public switched telephone network (PSTN) 22, wherein the
`base station controller 20 also coordinates communications
`between the base stations 14 and the PSTN 22. Preferably,
`each base station 14, communicates with the base station
`controller 20 over a wireless link, although a land line may
`also be provided. A land line is particularly applicable when
`a base station 14 is in close proximity to the base station
`controller 20. The fixed remote units 16 may also commu
`nicate with a base station 14 over a land line.
`The base station controller 20 performs several functions.
`Primarily, the base station controller 20 provides all of the
`operations, administrative, and maintenance (OA&M) sig
`naling associated with establishing and maintaining all of
`the wireless communications between the mobile units 16,
`the base stations 14, and the base station controller 20. The
`base station controller 20 can provide the routing of all
`communications between mobile units 16, and between the
`mobile units 16 and the PSTN 22. The base station controller
`20 also provides an interface between the mobile units 16
`and the PSTN 22. This interface includes multiplexing and
`demultiplexing of the communication signals that enter and
`leave the system 10 via the base station controller 20.
`Although the vehicle communication system 10 is shown
`employing antennas to transmit radio frequency (RF) sig
`nals, one skilled in the art should recognize that communi
`cations may be accomplished via microwave or satellite
`uplinks. Additionally, the functions of the base station
`controller 20 may be combined with a base station 14 to
`form a “master base station'.
`A preferred embodiment of the mobile unit 16 is shown in
`FIG. 2. Each mobile unit includes an RF transceiver 32 with
`an antenna 33 capable of transmitting and receiving a
`plurality of RF signals, a global positioning system (GPS)
`receiver 35, a microprocessor 40 with associated memory
`41, an interface to the vehicle's electromechanical systems
`44, and an audio-visual interface 46.
`The RF transceiver 32 transmits and receives RF signals
`at a plurality of RF frequencies to one or more vehicles
`which include a mobile unit 16. Received signals are down
`loaded to baseband and forwarded to the microprocessor 40
`for further processing. Transmitted signals are forwarded
`from the microprocessor 40 to the RF transceiver 32 for
`upconversion and transmission over one of the plurality of
`RF frequencies. The vehicle communication system 10 also
`provides for the option of transmitting a communication
`over currently licensed radio station channels, for example
`105.9 FM. This can permit mobile unit operator to broadcast
`to non-mobile unit operators. It also can provide a 'scanning
`channel’. Such that non-mobile unit operators can listen to
`broadcast communications.
`The GPS receiver 35 is configured to receive signals from
`GPS satellites and compute the position of the mobile unit
`16. There are many commercially available GPS receivers
`35 that can perform such a function. GPS readings which are
`provided to the microprocessor 40 permit the microproces
`Sor 40 to accurately calculate the speed, direction, and
`acceleration or deceleration rate of the vehicle.
`The microprocessor 40 provides central control of the
`mobile unit 16. As will be explained in greater detail
`hereinafter, the microprocessor 40 also performs packet
`handling, including packet assembling for outgoing com
`65
`munication packets 50 and packet disassembling for incom
`ing communication packets 50 received from the RF trans
`
`40
`
`45
`
`50
`
`55
`
`60
`
`US 7,123,926 B2
`
`10
`
`25
`
`30
`
`35
`
`4
`ceiver 32. Communication packets 50 received by the
`microprocessor 40 are stored in memory 41. The memory 41
`is also used to store identification information that is unique
`to each vehicle and/or vehicle operator. For example, license
`and registration for each vehicle can be read if positioned
`with a bar code or magnetic strip in a specific location of the
`vehicle. Optionally, the system may have a card reader
`where the operator must place their card prior to the vehicle
`starting. This card can be a license with a magnetic strip or
`a smartcard that identifies the driver and the vehicle. This
`unique information regarding the vehicle may also include
`the position of the vehicle, speed of the vehicle and rate of
`acceleration or deceleration as calculated by data obtained
`from the GPS receiver 35.
`The audio-visual interface (AVI) 46 preferably includes a
`microphone, speakers, and graphic display along with alpha
`numeric and directional keypads. However, those of skill in
`the art should realize that the AVI 46 may encompass other
`input devices which are known, Such as a voice activated
`input unit, an infrared remote control, a full keyboard or any
`other type of electronic or manual data input means. Addi
`tionally, the output portion of the AVI 46 may include any
`type of output means such as a stereo system or a heads-up
`display.
`The electromechanical interface 44 provides an electrical
`coupling to the electromechanical systems of the vehicle
`over which the mobile unit 16 has control. These systems
`may include the radio, lights, horn, windows, locks, steering,
`breaking, and any other electromechanical systems of the
`vehicle.
`Communications between mobile units 16 using the
`vehicle communication system 10 are accomplished through
`a stream of transmitted communication packets 50. As
`shown in FIG. 3A, each communication packet 50 includes
`a header 51 and a payload 53. The header 51 includes a
`plurality of predefined information fields which provide
`information regarding the particular communication, the
`sender which originated the communication, and the
`receiver to which the communication is destined. It should
`be recognized that a voice or data communication may be
`segmented or “packetized' and transmitted using a plurality
`of packets 50. The present invention is not restricted to
`transmitting a communication having a predefined length.
`Accordingly, the payload 53 may include only a portion of
`the communication that is sent between mobile units 16, and
`a single communication may be sent using a plurality of
`packets 50. Communications may include data transmis
`sions, such as uploads from the mobile unit 16, downloads
`to the mobile unit 16, or voice communications.
`Referring to FIG. 3B, the header 51 includes a plurality of
`information fields which can be generally categorized by
`three different functional groups: 1) transmission adminis
`trative information 55; 2) sender information 56; and 3)
`receiver information 57. These fields will be explained in
`greater detail hereinafter.
`Referring to FIG. 3C, the information fields associated
`with the transmission administration 55 are shown. These
`fields provide information that defines the particular com
`munication being transmitted. Although the number of fields
`vary, and the type of fields described may change depending
`on the particular communication and the requirements of the
`system 10, in one embodiment of the present invention, the
`fields associated with transmission administration 55
`include, the following fields: security 61; priority 62; in
`system/out of system 63; broadcast/point-to-point 64; com
`
`Exhibit 1015
`IPR2022-0427
`Page 11 of 19
`
`

`

`US 7,123,926 B2
`
`10
`
`15
`
`25
`
`30
`
`35
`
`5
`munication identifier (data/voice) 65; communication type
`(information/control) 66; and communication length (stan
`dalone or continuous) 67.
`Since the vehicle communication system 10 in accordance
`with the present invention permits control of a vehicle and
`overall control of the communication system 10 by law
`enforcement authorities via a “security instruction', the
`system 10 has a plurality of security levels to ensure that
`unauthorized individuals will not use the system 10 for
`subversive purposes. Optionally, driver may override law
`enforcement. The system 10 may ask for permission for law
`enforcement to control vehicle. The security field 61 is
`defined as follows:
`0 Access to all functions of the vehicle communication
`system 10, including the physical control of the vehicle and
`all of the information stored within the memory 41.
`1—Access only to the physical control of the vehicle.
`2—Access only to the information stored within the
`memory 41.
`3—Access for transmitting and receiving communica
`tions.
`4—Access only to receiving communications.
`The security field 61 may also include a security code,
`which permits authentication of the entity sending the Secu
`rity instruction. As aforementioned, it should be understood
`by those skilled in the art that additional fields may be added
`or defined as desired to increase the functionality of the
`system 10 or the security layers. Additionally, it should be
`recognized that although the system 10 is capable of a broad
`range of functionality, there are legal implications to imple
`menting all of the functionality. For example, a court order
`would most likely be necessary before permitting law
`enforcement officials access to information in, or control of
`the mobile unit 16.
`The priority field 62 is an indicator of the urgency of the
`transmitted communication. The priority field 62 can be a
`numeric priority from one to ten; with urgent communica
`tions having the highest priority of one (e.g., communica
`40
`tions from law enforcement officials) and non-urgent com
`munications having the lowest priority of ten (e.g.,
`advertisements).
`The in system/out of system field 63 indicates whether the
`communication is destined for, or originated from, another
`mobile unit 16 or an entity located outside of the vehicle
`communication system 10. Communications with entities
`outside the vehicle communication system 10 can be routed
`between the mobile unit 16 and the outside entity over the
`PSTN 22.
`The broadcast/point-to-point field 64 identifies whether
`the message is intended for broadcast to all mobile units 16
`or whether it is intended to be routed to a particular mobile
`unit 16. As will be explained in detail hereinafter, the
`receiver field 57 will specify the particular address, or
`multiple addresses, of the mobile units 16 to which the
`communication will be transmitted.
`The communication identifier field 65 identifies whether
`the communication is a voice or data transmission since each
`transmission may be encoded and processed differently by
`the receiving microprocessor 40.
`The communication type field 66 identifies whether the
`communication comprises information for output to the user
`via the AVI 46, or whether the information is a control
`instruction that will permit electromechanical control of the
`vehicle.
`
`50
`
`45
`
`55
`
`60
`
`65
`
`6
`The communication length field 67 indicates whether the
`entire communication is included within the current packet
`50, or whether the packet 50 is part of a multi-packet
`communication.
`Referring to FIG. 3D, the fields associated with the sender
`portion 56 of the header 51 include identification number 71,
`position 72, speed 73, acceleration or deceleration 74, direc
`tion 75, origination 76, and destination 77, and may include
`additional optional fields 78 as specified by the vehicle
`operator.
`The identification number 71 provides a unique identifi
`cation for the sending mobile unit 16. The identification
`number may be the vehicle license number with two addi
`tional letters representing the state where the license plate
`was issued. Such as PA for Pennsylvania. Depending upon
`system administration, the identification number 71 may
`further relate to one or more individual operators of the
`vehicle. As shown in FIG. 3F, the identification number field
`71 may include a plurality of subfields including vehicle
`code 81, number of authorized vehicle operators 82, and a
`vehicle operator identification number 83, ,
`, for each
`operator. This feature is particularly useful if the vehicle is
`part of a commercial fleet of vehicles with multiple drivers.
`Upon turning on the vehicle, the vehicle operator inputs their
`identification number 71. This number 71 is compared to the
`list of authorized operators previously stored in memory 41.
`If the input operator identification number 71 matches
`favorably with one of the authorized operators previously
`stored in memory 41, operation of the vehicle is permitted;
`if not, operation is denied. Optionally, license plate, regis
`tration, insurance information and driver's license informa
`tion can be additional fields stored with the identification
`number 71.
`Use of a vehicle operator identification number 71, such
`as a driver's license, also permits different operators to use
`the vehicle while retaining their distinct identity and storing
`information particular to that vehicle operator, similar to a
`screen name for Internet use Such as the America Online
`(AOL) system.
`Referring back to FIG. 3D, the next four fields associated
`with the sender portion 56 of the header 51 include position
`72, speed 73, acceleration or deceleration 74, and direction
`75, which are automatically created from the information
`obtained from the Sender’s GPS receiver 35.
`The origination field 76 includes the location of the
`vehicle when the vehicle was turned on. The destination
`field 77 includes the destination of the vehicle. This, of
`course, requires that the destination be input into the mobile
`unit 16, Such as when a destination is input into a navigation
`system. It should be understood that the mobile unit operator
`may override certain fields to ensure that this information is
`not obtained by other mobile unit operators. For example,
`the origination 76 and destination fields 77, which may
`include personal information that the mobile unit operator
`does not desire other mobile unit operators to have access to,
`may include null data such that the sender's destination and
`origination will be listed as “not available' to the receiver.
`The vehicle operator configures their mobile unit 16 as
`desired to specify which fields should be transmitted with
`null data.
`Referring to FIG. 3E, the fields associated with the
`receiver portion 56 of the header 51 are shown in greater
`detail. As discussed with reference to FIG. 3C, the broadcast
`or point-to-point field 64 indicates whether the communi
`cation is destined for one, multiple, or all operators. If the
`communication is to be broadcast to all mobile unit opera
`tors, the number of addressees field 79 is designated as Zero,
`
`Exhibit 1015
`IPR2022-0427
`Page 12 of 19
`
`

`

`US 7,123,926 B2
`
`10
`
`15
`
`7
`indicating that all operators will receive the communication.
`For point-to-point or point-to-multipoint communications,
`(whereby a plurality of operators may be included within a
`conversation or communication), the number of addressees
`field 79 includes the number of operators which will be
`receiving the communication. For example, if a point-to
`point communication is desired, the number of addressees
`field 79 will include the number one (1) and address field
`number one 80a will be the only field which includes an
`address. If a point-to-multipoint communication is desired
`between, for example four additional mobile unit operators,
`the number of addresses field 79 will include the number
`four (4) and address fields one through four 80a-d will
`include the addresses of the four receivers to be sent the
`communication.
`Once all of the aforementioned fields have been populated
`with the information, the microprocessor 40 builds each
`communication packet 50 and forwards the packet 50 to the
`transceiver 32 for transmission. The packets 50 are prefer
`ably transmitted to the base station 14, and then forwarded
`to the base station controller 20. The base station controller
`20 routes all of the communication packets 50 to the
`specified addresses, either to one or more mobile unit
`operators, one or more outside entities, or both. This routing
`function is the same as an Internet router, whereby the
`destination address or addresses are read by the router and
`the communication packet 50 is forwarded to those
`addresses. If the communication packet 50 is to be for
`warded to multiple addresses or broadcast to all addresses,
`the base station controller 20 provides such a routing func
`tion.
`The base station controller 20 may also confirm to sender
`whether or not a signal has been received by the recipient.
`In an alternative embodiment, each communication may
`require a confirmation packet be sen

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket