1 Matt Olavi, Esq. (Bar No.

265945)
2
molavi@olavidunne.com
Brian J. Dunne, Esq. (Bar No. 275689)
bdunne@olavidunne.com
3
4
OLA VI DUNNE LLP
800 Wilshire Blvd., Suite 320
5 Los Angeles, California 90017
6
Telephone: (213) 516-7900
Facsimile: (213) 516-7910
7
8
Attorneys for Plaintiff Eclipse IP LLC
-· '
FILED
CLERK, U.S. 01$1RICT COURf
SEP I I 20\3
_....,.., DISTRICT OF CALIFORNIA
Cc.t" DEPUTY
Wf , ....
9
UNITED STATES DISTRICT COURT
10 CENTRAL DISTRICT OF CALIFORNIA
11 ECLIPSEIPLLC,aFloridaLimited .. ) CaseNo.
6
5 .. l\IYI\1\I ./
12 Liability Company, r"' )f'\ \11 - h Jr.) IJ\Iv 1"\\IA"
'
13 Plaintiff, ) INFRINGEMENT
)
) TRIAL BY JURY DEMANDED
14
v.
15
)
16
US AIRWAYS, INC., a Delaware
Corporation,
)
)
17
18
19
20
21
22
23
24
25
26
27
28
)
Defendant.
)
______________________)
COMPLAINT FOR PATENT INFRINGEMENT
1 Plaintiff Eclipse IP LLC ("Eclipse"), by and through counsel, complains
2
3
4
5
6
7
8
9
10
11
12
against US Airways, Inc. ("US Airways") as follows:
NATURE OF LAWSUIT
1.
This is a suit for patent infringement arising under the patent laws of
the United States, Title 35 of the United States Code§ 1 et seq. This Court has
exclusive jurisdiction over the subject matter of the Complaint under 28 U.S.C.
§§ 1331 and 1338(a).
PARTIES AND PATENTS
2.
Eclipse is a company organized under the laws of Florida and having
13 a principal place of business at 115 NW 1 ih St, Delray Beach, Florida 33444.
14
15
16
17
18
19
20
21
22
23
"
.),
Eclipse owns all right, title, and interest in and has standing to sue for
infringement of United States Patent No. 7, 119,716 ("the '716 patent"), entitled
"Response systems and methods for notification systems for modifying future
notifications" (Exhibit A); United States Patent No. 7,479,899 ("the '899 patent"),
entitled "Notification systems and methods enabling a response to cause
connection between a notified PCD and a delivery or pickup representative"
(Exhibit B); and United States Patent No. 7,504,966 ("the '966 patent"), entitled
24
"Response systems and methods for notification systems for modifying future
25 notifications" (Exhibit C) (collectively, "the Eclipse Patents").
26
27
4.
On information and belief, US Airways is a corporation existing under
28 the laws of Delaware.
1
COMPLAINT FOR PATENT INFRINGEMENT
1
2
3
4
5
6
7
8
9
10
11
5.
On information and belief, US Airways does regular business in this
Judicial District and conduct leading to US Airways' acts of infringement has
occurred in this Judicial District.
JURISDICTION AND VENUE
6.
This Court has personal jurisdiction over US Airways because it has
engaged in continuous and systematic business in California; upon information and
belief, derives substantial revenues from commercial activities in California; and,
upon information and belief, is operating and/or supporting products or services
12
that fall within one or more claims of Eclipse's patents in this District.
13
14
15
16
17
18
19
20
21
22
23
7.
Venue is proper in this District under 28 U.S.C. §§ 139l(b) and (c)
and 28 U.S.C. § 1400(a) at least because the claim arises in this Judicial District,
US Airways may be found and transacts business in this Judicial District, and
injuries suffered by Plaintiff took place in this Judicial District. US Airways is
subject to the general and specific personal jurisdiction of this Court at least
because of its contacts with the State of California.
FACTUAL BACKGROUND
8. On information and belief, US Airways is an airline that offers
24
domestic and international flights from cities across the United States, including
25 many from Los Angeles.
26
27
!II
28 Ill
2
COMPLAINT FOR PATENT INFRINGEMENT
1
2
3
4
9.
On information and belief, US Airways creates and maintains a
timetable for every scheduled US Airways flight, which includes a scheduled
departure time and a scheduled arrival time for every US Airways flight.
5 10. On information and belief, US Airways, either on its own or through
6
7
8
9
10
11
its agents, monitors the location of its various airplanes, and based at least in part
on the location of a given airplane, determines whether a particular flight will
depart from its scheduled departure city and/or whether a particular flight will
arrive at its scheduled arrival city earlier than the scheduled time, at the scheduled
12
time, or later than the scheduled time.
13 11. On information and belief, US Airways also uses the location of its
14
15
16
17
18
19
20
21
22
23
various airplanes to determine whether or not to cancel flights.
12. On information and belief, US Airways uses, makes, deploys,
advertises, and/or operates at least one system and/or service (the "US Airways
System") that can automatically notify one or more individuals about the status of
a flight. The at least one US Airways system may sometimes be referred to as the
US Airways "BeNotified" system.
13. On information and belief, as one non-limiting example, the US
24
Airways System can automatically notify one or more individuals of flight
25 schedule changes, gate changes, departure reminders, arrival alerts, flight delays,
26
27
and/or cancellations.
2
8
I I I
3
COMPLAINT FOR PATENT INFRINGEMENT
1 14. On information and belief, these notifications can occur through at
2
3
4
least one communications method, including but not limited to through email and
SMS messages, and that the one or more individuals can select or modify which of
5 the at least one communications method should be used.
6
7
8
US AIRWAYS' ACTS OF PATENT INFRINGEMENT
15. Eclipse reiterates and reincorporates the allegations set forth in
9 paragraphs 1 through 14 above as if fully set forth herein.
10
11
12
13
14
15
16. US Airways owns, uses, deploys, and/or operates at least one
computerized service and/or system, the US Airways System, for notifying one or
more individuals regarding flight departure and/or arrival times.
17. Based at least in part on the location a US Airways airplane, the US
16
Airways System provides electronic notifications to one or more individuals
17 regarding flight departure and/or arrival times.
18
19
20
21
22
23
CLAIMS FOR RELIEF
COUNT1
(Patent Infringement of U.S. Patent No. 7,119,716
Under 35 U.S.C. § 271 et seq.)
18. Eclipse reiterates and reincorporates the allegations set forth in
24
paragraphs 1 through 17 above as if fully set forth herein.
25 19. On October 10, 2006, the United States Patent and Trademark Office
26
duly and legally issued United States Patent No. 7,119,716, entitled "Response
27
2
8
systems and methods for notification systems for modifying future notifications."
4
COMPLAINT FOR PATENT INFRINGEMENT
1 Eclipse is the owner of the entire right, title and interest in and to the '716 patent.
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
A true and correct copy of the '716 patent is attached as Exhibit A to this
Complaint.
20. The '716 patent is valid and enforceable.
21. Eclipse is informed and believes, and thereupon alleges, that:
(1) US Airways has infringed and continues to infringe one or more claims of the
'716 patent, literally and/or under the doctrine of equivalents and additionally
and/or in the alternative, (2) US Airways has actively induced and continues to
actively induce and/or has contributed to and continues to contribute to the
infringement of one or more claims of the '716 patent in this District and elsewhere
in the United States.
22. On information and belief, US Airways has directly infringed and
17 continues to directly infringe one or more claims of the '716 patent, in violation of
18
19
20
21
35 U.S.C. § 27l(a), by, among other things, making, using, offering for sale,
and/or selling a method for communications in connection with a computer-based
notification system to, for example: store contact data in computer memory;
22
provide electronic notification communications to a personal communications
23
24
device based on the contact data; receive changes to the contact data; and modify if
25 and/or how future notification communications will be sent.
26
23. Additionally and/or in the alternative, on information and belief, US
27
28 Airways has actively induced and continues to actively induce and/or has
5
COMPLAINT FOR PATENT INFRINGEMENT
1 contributed to and continues to contribute to the infringement of one or more
2
3
4
5
6
7
claims of the '716 patent, in violation of35 U.S.C. § 271(b) and/or (c), by, among
other things, actively, knowingly, and intentionally encouraging, aiding, and/or
abetting others to make, use, offer for sale, and/or sell portions of a computer-
based notification system that infringes one or more claims of the '716 patent, with
8
the specific intent to encourage infringement and with the knowledge that the
9 making, using, offering to sell, and/or selling of such a system would constitute
10
11
12
infringement.
24. On information and belief, US Airways has had knowledge of the '716
13 patent at least as early as the filing of this Complaint. Additionally, at least as
14
early as the filing of this Complaint, US Airways knew or should have known that
15
16
its continued offering, use, deployment, and/or operation of the at least one flight
17 notification service and/or system and its continued support of others, if those
18
parties perform any limitations of one or more of the claims of the '716 patent,
19
20
would induce direct infringement ofthe '716 patent.
21 25. On information and belief, US Airways' aforesaid infringing activity
22
has been done with knowledge and willful disregard of Eclipse's patent rights,
23
24
making this an exceptional case within the meaning of 35 U.S.C. § 285.
25 26. US Airways' aforesaid infringing activity has directly and
26
proximately caused damage to Plaintiff Eclipse, including loss of profits from sales
27
28 and/or licensing revenues it would have made but for the infringements. Unless
6
COMPLAINT FOR PATENT INFRINGEMENT
1
2
3
4
5
6
7
enjoined, the aforesaid infringing activity will continue and cause irreparable
injury to Eclipse for which there is no adequate remedy at law.
COUNT2
(Patent Infringement of U.S. Patent No. 7,479,899
Under 35 U.S.C. § 271 et seq.)
27. Eclipse reiterates and reincorporates the allegations set forth in
8
paragraphs 1 through 26 above as if fully set forth herein.
9 28. On January 20, 2009, the United States Patent and Trademark Office
10
11
12
duly and legally issued United States Patent No. 7,479,899, entitled "Notification
systems and methods enabling a response to cause connection between a notified
13 PCD and a delivery or pickup representative." Eclipse is the owner of the entire
14
right, title and interest in and to the '899 patent. A true and correct copy of the '899
15
16
patent is attached as Exhibit B to this Complaint.
17
18
19
29. The '899 patent is valid and enforceable.
30. Eclipse is informed and believes, and thereupon alleges, that: (1) US
20
Airways has infringed and continues to infringe one or more claims of the '899
21 patent, literally and/or under the doctrine of equivalents and additionally and/or in
22
the alternative, (2) US Airways has actively induced and continues to actively
23
24
induce and/or has contributed to and continues to contribute to the infringement of
25 one or more claims ofthe '899 patent in this District and elsewhere in the United
26
States.
27
28 I II
7
COMPLAINT FOR PATENT INFRINGEMENT
1 31. On information and belief, US Airways has directly infringed and
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
continues to directly infringe one or more claims of the '899 patent, in violation of
35 U.S.C. § 271(a), by, among other things, making, using, offering for sale,
and/or selling a method for an automated notification system to, for example:
monitor the location of a plane; initiate a notification to one or more individuals
based on the location; and enable the one or more individuals to select whether or
not to communicate with US Airways.
32. Additionally and/or in the alternative, on information and belief, US
Airways has actively induced and continues to induce and/or has contributed to
and continues to contribute to the infringement of one or more claims of the '899
patent, in violation of35 U.S.C. § 271(b) and/or (c), by, among other things
actively, knowingly, and intentionally encouraging, aiding, and/or abetting others
17 to make, use, offer for sale, and/or sell portions of an automated notification
18
19
20
21
22
23
system that infringes one or more claims of the '899 patent, with the specific intent
to encourage infringement and with the knowledge that the making, using, offering
to sell, and/or selling of such a system would constitute infringement.
33. On information and belief, US Airways has had knowledge of the '899
24
patent at least as early as the filing of this Complaint. Additionally, at least as
25 early as the filing of this Complaint, US Airways knew or should have known that
26
27
its continued offering, use, deployment, and/or operation of the at least one flight
28
notification service and/or system and its continued support of others, if those
8
COMPLAINT FOR PATENT INFRINGEMENT
1 parties perform any limitations of one or more of the claims of the '899 patent,
2
3
4
would induce direct infringement of the '899 patent.
34. On information and belief, US Airways' the aforesaid infringing
5 activity has been done with knowledge and willful disregard of Eclipse's patent
6
rights, making this an exceptional case within the meaning of35 U.S.C. § 285.
7
8
35. US Airways' aforesaid infringing activity has directly and
9 proximately caused damage to Plaintiff Eclipse, including loss of profits from sales
10
and/or licensing revenues it would have made but for the infringements. Unless
11
12
13
14
15
16
enjoined, the aforesaid infringing activity will continue and cause irreparable
injury to Eclipse for which there is no adequate remedy at law.
COUNT3
(Patent Infringement of U.S. Patent No. 7,504,966
Under 35 U.S.C. § 271 et seq.)
17 36. Eclipse reiterates and reincorporates the allegations set forth in
paragraphs 1 through 35 above as if fully set forth herein.
21 duly and legally issued United States Patent No. 7,504,966, entitled "Response
22
systems and methods for notification systems for modifying future notifications."
23
24
Eclipse is the owner of the entire right, title and interest in and to the '966 patent.
25 A true and correct copy ofthe '966 patent is attached as Exhibit C to this
26
27
Complaint.
28 38. The '966 patent is valid and enforceable.
9
COMPLAINT FOR PATENT INFRINGEMENT
1 39. Eclipse is informed and believes, and thereupon alleges, that: (1) US
2
3
Airways has infringed and continues to infringe one or more claims of the '966
4
patent, literally and/or under the doctrine of equivalents and additionally and/or in
5 the alternative, (2) US Airways has actively induced and continues to actively
6
7
8
9
10
11
12
13
14
15
induce and/or has contributed to and continues to contribute to the infringement of
one or more claims of the '966 patent in this District and elsewhere in the United
States.
40. On information and belief, US Airways has directly infringed and
continues to directly infringe one or more claims of the '966 patent, in violation of
35 U.S.C. § 271(a), by, among other things, making, using, offering for sale,
and/or selling a method for communications in connection with a computer-based
16
notification system to, for example: monitor the location of a plane; send a
17 notification communication to a personal communications device when
18
19
appropriate; receive a response from the personal communications device; and
20
based upon the response, initiate one or more future notifications to one or more
21 different individuals and/or initiate one or more future notifications using one or
22
more different communications methods.
23
24
41. Additionally and/or in the alternative, on information and belief, US
25 Airways has actively induced and continues to actively induce and/or has
26
27
contributed to and continues to contribute to the infringement of one or more
28
claims of the '966 patent, in violation of35 U.S.C. § 271 (b) and/or (c), by, among
10
COMPLAINT FOR PATENT INFRINGEMENT
1
2
3
4
other things, actively, knowingly, and intentionally encouraging, aiding, and/or
abetting others to make, use, offer for sale, and/or sell portions of a computer-
based notification system that infringes one or more claims of the '966 patent, with
5 the specific intent to encourage infringement and with the knowledge that the
6
making, using, offering to sell, and/or selling of such a system would constitute
7
8
infringement.
9 42. On information and belief, US Airways has had knowledge of the '966
10
11
12
13
14
15
patent at least as early as the filing of this Complaint. Additionally, at least as
early as the filing of this Complaint, US Airways knew or should have known that
its continued offering, use, deployment, and/or operation of the at least one flight
notification service and/or system and its continued support of others, if those
16
parties perform any limitations of one or more of the claims of the '966 patent,
17 would induce direct infringement of the '966 patent.
18
43. On information and belief, US Airways' aforesaid infringing activity
19
20
has been done with knowledge and willful disregard of Eclipse's patent rights,
21 making this an exceptional case within the meaning of35 U.S.C. § 285.
22
44. US Airways' aforesaid infringing activity has directly and
23
24
proximately caused damage to Plaintiff Eclipse, including loss of profits from sales
25 and/or licensing revenues it would have made but for the infringements. Unless
26
27
28
enjoined, the aforesaid infringing activity will continue and cause irreparable
injury to Eclipse for which there is no adequate remedy at law.
11
COMPLAINT FOR PATENT INFRINGEMENT
1
2
3
PRAYER FOR RELIEF
WHEREFORE, Plaintiff Eclipse asks this Court to enter judgment against
4
US Airways and against each of US Airways' respective subsidiaries, affiliates,
5
6
7
8
agents, servants, employees and all persons in active concert or participation with
it, granting the following relief:
I.
A judgment that US Airways has infringed each and every one of the
9 Eclipse Patents;
10
11
12
13
14
15
16
17
18
19
2.
A permanent injunction against US Airways, its respective officers,
agents, servants, employees, attorneys, parent and subsidiary corporations, assigns
and successors in interest, and those persons in active concert or participation with
them, enjoining them from direct and indirect infringement of each and every one
of the Eclipse Patents;
3.
An award of damages adequate to compensate Eclipse for the
infringement that has occurred, together with prejudgment interest from the date
20
infringement of the Eclipse Patents began;
21
22
23
24
4.
A reasonable royalty for US Airways' use of Eclipse's patented
technology, as alleged herein;
5.
An award to Eclipse of all remedies available under 35 U.S.C. §§ 284
25 and 285, including enhanced damages up to and including trebling of Eclipse's
26
27
28
damages for Defendants' willful infringement, and reasonable attorneys' fees and
costs; and,
12
COMPLAINT FOR PATENT INFRINGEMENT
1 6. Such other and further relief as this Court or a jury may deem proper
2
3
4
and just.
5 DATED: September 11,2013
6
7
8
9
10
11
12
13
14
OLA VI DUNNE LLP


Matt Olavi
Brian J. Dunne
Attorneys for Plaintiff
Eclipse IP LLC
JURY DEMAND
15
Eclipse demands a trial by jury on all issues so triable pursuant to Federal
16
Rule of Civil Procedure 38.
17
18
19
20
21
22
23
24
25
26
27
28
DATED: September 11, 2013
OLA VI DUNNE LLP

'_:Z-<-_1'-"'.:.__ ____ _
13
Matt Olavi
Brian J. Dunne
Attorneys for Plaintiff
Eclipse IP LLC
COMPLAINT FOR PATENT INFRINGEMENT
Exhibit A
111111111111111111111111111111111111111111111111111111111111111111111111111
(12) United States Patent
Horstemeyer
(54) RESPONSE SYSTEMS AND METHODS FOR
NOTIFICATION SYSTEMS FOR MODIFYING
FUTURE NOTIFICATIONS
(75) Inventor: Scott A. Horstemeyer, Atlanta, GA
(US)
(73) Assignee: LegalView Assets, Limited, Tortola
(VG)
( * ) Notice; Subject to any disclaimer, the tenn of this
patent is extended or adjusted under 35
U.S.C. 154(b) by 328 days.
(21) Appl. No.: 101706,591
(22) Filed: Nov. 12, 2003
(65)
(60)
(51)
(52)
(58)
(56)
Prior Publication Data
US 200410254985 Al Dec. 16, 2004
Related U.S. Application Data
Provisional application No. 60/473,738, filed on May
28, 2003, provisional application No, 60/473,742,
filed on May 28, 2003, provisional application No.
60/473,949, filed on May 28, 2003, provisional
cation No. 60/486,768, filed on Jul. 11, 2003, provi·
sional application No. 60/498,819, filed on Aug. 29,
2003.
Int. Cl.
G08G 11123
U.S. Cl ....
(2006.01)
3401994; 340/928; 340/539.11;
3401502; 340/504; 340/506
Field of Classification Search ................ 340/994,
340/928,539.11,502,504,506
See application file for complete search history.
References Cited
U.S. PAl'ENT DOCUMENTS
3,568,161 A
3,644,883 A
3,845,289 A
3/1971 Knickel .. 340/994
2/1972 Borman eta!. .... 340/23
10/1974 French ......... 235/151.2
EP
US007119716B2
(10) Patent No.:
(45) Date of Patent:
US 7,119,716 B2
Oct. 10, 2006
3,886.515 A 5/1975 Cottin et a!. 340/994
3,934.125 A 1/1976 Macano ........ .... 235/150.2
4,220,946 A 9/1980 Henriot 340123
4,297,672 A 10/1981 Fruchey et a!. ............... 340/23
4,325,057 A 4/1982 Bishop ..... ....... 340/539
4,350,969 A 9/1982 Greer ......... ................ 340/23
4,525,601 A 6/1985 Bamich et al . ......... 37917 MM
4,585,904 A 4/1986 Mincone et al. ..... .. 179/7.1 TP
4,7l3,661 A 12/1987 Boone et al.
(Continued)
FOREIGN PATENT DOCUMENTS
0219859 A2 4/1987
(Continued)
OTHER PUBLICATIONS
340/994
Moriok, eta\., "Advanced Vehicle Monitoring and communication
Systems for Bus and Economic Feasibility", Final
Report-U.S. Department of Transportation, Scp. 1991, Revised
Mar. 1993, Dot-T-94-03.
(Continued)
Primary Examiner-Tai Nguyen
(74) Attorney, Agent, or Firm-Thomas, Kayden,
I-Iorstemeyer & Risley LLP
(57) ABSTRACT
Response systems and methods are disclosed for commu-
nications in connection with a computer-based notification
system and a personal communications device (e.g., tele-
phone, pager, computer, PDA, etc.) associated with a party.
One such representative response method, among others,
can be summarized by the following steps: initiating a
notification communication to a personal communications
device associated with a party; receiving a response com-
munication from the party's personal communications
device; and modifying a manner in which future notification
communications are implemented, based upon the response.
A representative response system, among others, has mecha-
nisms for implementing the fOregoing steps.
92 Claims, SO Drawing Sheets
NOIIflco<!cnS)'>10m I a .. oSioionC<l"""'
., Unii(BSCU)
"" •• ,.
Corn!MooQ I.<TIL
RoOjl<ln•• S)'>lom Stt>p l-=11""
"' Dallmnlnollol> OTLNo<iOoolloo
I f - ....
.,_
I
lll&!
"'
g GPS SololDIO$
r.<Jar oto ) 117""'"' Nolf=lton Mol!io Thl"!l
2
l .. .,glli_ oor:;:;:"'
17\ 2(
"'
I
,,.
Mo!>He Tnlog (MT)
TXIRX TXIRX
72
r•.a·'""'"'"'"""·"""·"''
""'"Th'""'ir 1J ' lli Ser;or
"
" "
"
" I
.,
'-
.
No!l!<l<I;(•J
·-··I
Thl"9 TXJRX
• ... ""'') (• .•. ,PS"II<J

'"
..
"
System

f-.-"'
""

Exhibit A
Page 14
Psr>Onal
Oevtce(PCO)
US 7,119,716 B2
Page 2
U.S. PATENT DOCUMENTS
5,602,739 A
5,623,260 A
5,648.770 A
5,652,707 A
5,657,010 A
5,668,543 A
5,673,305 A
5,680,119 A
5,694,322 A
5,694,459 A
5,699,275 A
5,712,908 A
5,715,307 A
5,719,771 A
5,724.243 A
5,724,584 A
5,729,597 A
5,732,074 A
5,734,981 A
5,736,940 A
5,739,774 A
5,742,672 A
5,751,245 A
5,760,742 A
5,771,282 A
5,771,455 A
5,774,825 A
5,78Ll56 A
5,784,443 A
5,793,853 A
5,796,365 A
5,799,073 A
5,799,263 A
5,805,680 A
5,808,565 A
RE35,920 E
5,835,580 A
5,841,847 A
5,852,659 A
5,864,610 A
5,875,238 A
5,881,138 A
5,910,979 A
5,912,954 A
5,915,006 A
5,920,613 A
5,922,040 A
5,937,044 A
5,943.320 A
5,943,406 A
5,943,657 A
5,945,919 A
5,946,379 A
5,950,174 A
5,955,974 A
5,956,391 A
5,982,864 A
5,987,103 A
5,9R7,377 A
5,991,377 A
5,991,380 A
5,991,381 A
5,995,602 A
6,006,159 A
6,094,149 A
6,097,317 A
6,111,538 A
6,124,810 A
6,134,501 A
6,137,425 A
6,144,301 A
6,178,378 Bl
6,184,802 B1
4,791,571 A
4,799,162 A
4.804,837 A
4,804,937 A
4,812,843 A
4,813,065 A
4,857,925 A
4,894,649 A
4,956,777 A
5,003,584 A
5,006,847 A
5,014,206 A
5,021,780 A
5,02!,789 A
5,048,079 A
5,068,656 A
5,097,429 A
5,103,475 A
5,113,185 A
5,121,326 A
5,122,959 A
5,131,020 A
5,144,301 A
5,146,491 A
5,155,689 A
5,168,451 A
5.179,584 A
5,218,629 A
5,218,632 A
5,223,844 A
5,243,529 A
5,271,4R4 A
5,299,132 A
5,323,456 A
5,351,194 A
5,361,296 A
5,381,338 A
5,381,467 A
5,394,332 A
5,398,190 A
5,400,020 A
5.420,794 A
5,424,727 A "'
5,428,546 A
5,432,841 A
5,440,489 A
5,444,444 A
5,446,678 A
5,448,479 A
5,461,374 A
5,483,234 A
5,483,454 A
5,485,520 A *
5,493,295 A
5,493,694 A
5,506,893 A
5,513,lll A
5,515,421 A
5,519,621 A
5,526,401 A
5,539,810 A
5,544,225 A
5,546,444 A
5,552,795 A
5,559,871 A
5,570,100 A
5,577,!01 A
5,579,376 A
5,587,715 A
5,594,650 A
5,594,787 A
12/1988 Takahashi ct al. . .. 364/436
1/1989 Shinkawa et a\. ....... 364/436
211989 Farley ................. 250/251
2/1989 Barbiau.x et a!. 340/52 F
311989 Champion, III ct a\. .... 340/905
3/1989 Segala ........ 379/112
8/1989 Brubaker .................... 340/994
111990 Davis .................... 340/825.44
911990 Cearley et al ......... 364/424.02
311991 Benyacar et al. 379/119
4/1991 Rush et al .................. 340/994
5/1991 Scribner eta!. ... 364/449
611991 Fabiano et al. ............ 340/994
6/1991 Fabiano eta!. . 264/436
9/1991 Harrington et al. .. 379/112
11/1991 Sutherland ...... 340/989
3/1992 Wood et al. 364/569
4/1992 Shucn ..... 379/115
511992 Ichikawa 340/995
611992 Moroto et al. . 364/449
6/1992 Nathanson et al. .. 364/436
711992 Liebesny eta!. .... 379/59
9/1992 Jackson et al. ............ 340/994
911992 Silver et al ............... , 379i1 14
I0/1992 Wortham .................... 364/460
12/1992 Bolger ....................... 364/436
1/1993 Tsumura ........ .. 379/114
6/1993 Dumond, Jr. et al .......... 379/59
611993 Cool ......................... 379/126
6/1993 Mansell et al .............. 342/357
911993 Kashiwazaki 364/449
1211993 Bahjat et al. 187/29.1
3/1994 Wortham .... . ... 364i460
611994 Oprea .... 379/375
9/1994 Ross eta!. ....... 364/449
11/1994 Reyes el a\. ........ 379/96
l/1995 Wysocki et al. . ......... 364/449
111995 Rosinski ct al. .. . .. 379/121
211995 Kuwahara eta!. .......... 364/449
3/1995 Wortham ........... .,, ..... 364/460
311995 Jones .......... .,., .......... 340/994
511995 James ... 364/436
61 I 99 5 Shieh 340/928
6/1995 Shah ot al. . .. 364/449
7/1995 Rimer 379/59
811995 l\'"ewman 364/426.05
8/1995 Ross . ., . ., .. ., ....... 340/994
8/1995 Sa\tzstein et al. . 364/514
9/1995 Kemner eta\. 365/424.02
10/1995 Lewiner eta\. ... 340/994
1/1996 Correel eta!. . ... 3401994
111996 Lewiner et al. . .... 364/443
1/1996 Chamn et al. ............... 705/74
2/1996 Lowinor ct a\. ....... ., .... 340/994
2/1996 Vlcek et al ................ 455/53.1
4/1996 Buscher ct al. .. .. ., 379/114
4/1996 Wortham .... . .... 364/460
511996 Sikand et al. . ............. 379/67
5/1996 Wortham .... . ..... 3641460
611996 Roach, Jr. eta!. 379/59
711996 Kennedy, III et a\. ........ 379/59
8/1996 Kennedy, III et al ......... 379/59
811996 Roach, Jr, et al. .......... 379/59
9/1996 Tayloe el al. 342/357
911996 Smith ........ 379/115
10/1996 Grube eta!. ............... 364/446
1111996 Bohm ........................ 379/58
1111996 Kennedy, III et al. ........ 379/60
I 2/1996 Lewis ............... 342/357
1/1997 Shah et al. ............. 364/449.1
1/1997 Ohshima eta!. ........... 379/114
Exhibit A
Page 15
2/1997 Haagensta.d eta\. 3641436
4/1997 Jones ......... .. 340/994
7!l997 Ross .......... . ...... 340/994
7/1997 Wortham ..... . ...... 364/460
8/1997 Jones ... ,......... .. ... 340/994
9/1997 JOnt;!S """""'"" ........... 340/994
911997 Ross .... ....... . ........ ... ... 379/58
10/1997 Magliari et al. .. 340/904
12/1997 Westerlage eta\ .......... 364/464
12/1997 Backaus et a!. ........... 379/427
12/1997 Beasley eta!. ........ 364/514 R
!11998 llrinkman et. a.J. .......... 379/119
2/1998 Zazzera ...................... 379/265
211998 Bucket a!. ........ 364/443
3/1998 Westerlage et al. . 364/446
3/1998 Peters eta!. 395/671
3/1998 Bhusri . . ... 379/115
3/1998 Spaur et al ................. 370/313
3/1998 Kennedy, III et al ...... 455/445
411998 Burgener . ... . . . ..... 340/994
4/1998 Olandesi ..... . ........ 340/994
4/1998 Burk .............. 3791198
5/1998 Jank.y et al ................. 342/357
6/1998 Branch eta!. .............. 342/457
611998 Friedes ................. ,. .... 379/121
6/1998 Kennedy, Ill et al ...... 455/456
6/1998 Reynolds ................. 364/449.7
7/1998 Krasner ........ 342/357
7/1998 Chapman et al ............ 379/119
8/1998 Sbisa ...... 379/120
8/1998 Lewis ............... 342/3 57
8/1998 Fleischer, III eta!. ...... 379/113
8/1998 Culbertson .,. ............ , .. 701/ll7
9/1998 Penzias ..................... 379/118
9/1998 Matta et al. . ........ 340/994
10/1998 Sorden eta!. .......... 3421457
11/1998 Fraser .. . ..... 379/115
11/1998 Graham eta!. ............ 379/114
\2/!998 Welter, Jr. .. . ...... 379/116
1/1999 Ronen ....................... 379/127
2/1999 Glitho et al ................ 379/116
3/1999 Keams eta!. .......... 379/114
6/1999 Gocl ct al ................... 379/120
6/1999 Whiled ct aL ..... 379/115
6!1999 Jagadish ot al. , ......... ,. 379/127
7/1999 Alcott eta!. ..... 379/114
7/1999 Prabhakaran ............... 701/117
8/1999 Kim .......................... 379/121
8/1999 Weik et a\. ........ .. 370/259
8!1999 Leta eta!. ......... 379/120
8/1999 Freestone et al. 705/400
8/1999 Trask ................. 340/825.491
8/1999 Bhusri ..................... 379/115
9/1999 Brendzel .................... 705/34
9!1999 Toga.wa ....... , ., .......... 340/994
9/1999 Melen et a! ................ 379/114
11/1999 Jagadish et al. 379/115
11/1999 Jagadish eta! ............. 379/114
11/1999 Wester\age eta\. ......... 701/204
11/1999 Malik.... 379/114
11/1999 Bruno eta!. 379/.115
11/1999 Bouanaka. et al. .. 379/115
1111999 Johnson eta!. ........ 379/116
12/1999 Schmier eta!. .......... 701/200
7/2000 Wilson ...................... 340!904
8/2000 Lewiner et al. . .. 340/994
8/2000 Schuchman et al. 342/357
9/2000 Segal et a!. .......... 340/994
10/2000 Oumi ........................ 701/209
1012000 Oster et a!. ................ 340/994
1112000 Frieden ................... 340/572.8
112001 Leibold ...................... 701/202
2/2001 Lamb .... ...... . ........... 340/994
US 7,119,716 B2
Page 3
6,191,708 Bl 2/2001 Davidson ...... .. 340/994
6,222,462 BJ 4/2001 Hahn ......... 3401904
6.240,362 Bl 5/2001 Gaspard, II .. 701/209
6,253,146 Bl 6/2001 Hanson eta!. .... 701/202
6,253,148 Bl 61200 I Decaux et aL 70l/204
6,278,936 Bl 8/2001 Jones ..................... ... 70ll201
6,313,760 Bl I J/200 I Jones . 340/994
6,317,060 Bl J 11200 I Jones . 340/994
6,360,101 Bl 3/2002 Irvin .... 445/456
6,363,254 B1 3/2002 Jones et a! ...... 4551456
6,363,323 Bl 3/2002 Jones 701/213
6,374,176 Bl 4/2002 Schmier et al. 701/200
6,400,956 Bl 6/2002 Richton ..... 455/456
6,411,891 Bl 6/2002 Jones ................ 70l/201
6,415,207 Bl 7/2002 JontJS 70111
6,486,801 BJ 11/2002 Jones ................. 340/994
6,492,912 81 12/2002 Jones
6,510,383 Bl l/2003 Jones
6,618,668 Bl 9/2003 Laird ..... 701/204
6,683,542 Bl 1/2004 Jones 340/994
6,700,507 Bl 3/2004 Jones ..... 340/994
6,882,334 Bl * 4/2005 Meyer .. .... 345/156
6,943,679 B1 * 9/2005 Sebanc et al. ... 340/505
2002/00I6171 AI 2/2002 Doganata et al. 455/456
2002/00690I7 AI 6/2002 Schrnicr ct a!. 7011213
2002/0082770 AI 6/2002 Jones
2002/0099500 AI 7/2002 Schmier et a!. .... 70I/200
2003/0091158 5/2003 Puchck et al. .............. 379/38
2003/00932I8 AI 5/2003 Jones 70I/20I
2003/0098802 AI 5/2003 Jones ......... 340/994
2003/0146854 AI 8/2003 Jones ............ 340/988
2003/0193412 AI 10/2003 Jones .. 340/994
2003/0193413 AI 10/2003 Jones . 340/994
2003/0193414 Al I0/2003 Jones ............. ...... .... 340/994
2003/0195696 Al I0/2003 Jones .. 701/20I
2003/0195697 Al !012003 Jones .. 701/201
2003/0195698 Al 10/2003 Jones ......................... 701/201
2003/0195699 AI 10/2003 Jones .... 70I/20I
2001/0233188 A I 1212003 Jones .... 701/200
2003/0233190 AI I2/2003 Jones .. 70l/207
FOREIGN PATENT DOCUMENTS
EP 0805427 AI 11/1997
EP 0889455 AI 111999
FR 2 559 930 8/1985
FR 2674355 9/1992
GB W093/13510 Al 7/1993
GB WO 9313510 AI 7/1993
JP 52066175 6/1977
JP 63288400 11/1988
JP 11034872 A 2/I999
wo wo 90/0I236 2/1990
wo wo 93/13503 7/1993
wo wo 94/02922 2/1994
wo wo 94/27264 1Jll994
wo wo 96/04634 2/1996
wo wo 96/16386 5/1996
wo wo 98/07128 2/1998
wo wo 98/08206 2/1998
wo wo 98/14926 4/1998
wo wo 98/40837 911998
011-IER PUBLICATIONS
Brynielsson, Thore. Step by Step Development Towards Attractive
Public Transport, Chalmers University of Technology, Gotebord,
Sweden, Department of Transportation, I976.
"Public Transporation Information and Management Ssytems'', lEE
Colloquium, Computing and Control Division, May 25, I993, pp.
9/1-9/4, 12/1-12/2, 7/1-7/3.
"Vehicle Location and Fleet Management Systems", !HE Col-
loquium, Computing and Control Division, Jun. 8, 1993.
'The Jrd International Conference on Vehicle Navigation & Infor-
mation Systems (VNIS) Norway, Sep. 2-4, 1992, pp. 312-315.
Preiss, George; Jenson, Lillian; "The Satref and GPS Information
Projects", 1992 IEEE-3rd International Conference on Vehcile
Navigation Infonnation Systems, pp. 648-655.
"Vehicle Navigation & Information Systems Conference Proceed-
ings" (P-253), Society of Automotive Engineers, Inc., Oct. 1991, pp.
789-796.
"1992 Compendimn of Technical Papers", Institute of Transporta-
tion Engineers-INRAD: A Deminostration ofTwo-Way Roadway
to Vehicle Communication for use in Traffic Operations, Annual
Meeting, Washington, D.C. pp. 214-218.
"Paving the Way for GPS in Vehicle Tracking", Showcase World,
Dec. 1992.
"Advanced Vehicle Monitoring and Communication Systems for
Bus Transit", Federal Transit Administration, Sep. 1991, Revised
Mar. 1993.
Koncz, et a!., "GIS-Based Transit Information Bolsters Travel
Options", GIS World, Jul. 1995, pp. 62-64.
Helleker, Jan, Real-Time Traveller Information--··-in everyone's
pocket?!--a pilot test using hand-p01table GSM terminals,
IEEE-lEE Vehicle Navigation & Infonnation systems Conference,
Ottawa, VNIS I993, pp. 49-52 .
Burgener. E. C., et al., "A Personal Transit Arrival Time Receiver",
IEEE-lEE Vehicle Navigation & Information Systems Confer-
ence, Ottawa, VNIS 1993, pp. 54-55.
Peng, Zhong-Rcn, "A Mdhudology for Design for a GIS-Based
Automatic Transit Traveler Information System'', Computer, Envi-
ronment and Urban Systems, vol. 21, No.5, pp. 359-372, 1997 .
Lessard, Robert, "The Use of Computer for Urban Transit Opera-
tions", IEEE-lEE Vehicle Navigation & Information systems
Conference, Ottawa, VNIS 1993, pp. 586-590.
Sommerville, Fraser, et al., "Reliable InfoiJDalion in Everyone's
Pocket-a Pilot Test", IEEE, vo!. 1927, Mar. 1994, pp. 425-428 .
"PROMISE-Personal Mobile Traveller and Traffic Information
Service-Specification of Promise Services, Ver. 7", Telematics
Application Progr111Illlle A2, Transport, Jul. 1, I996 .
"PROMISE---Personal Mobile Traveller and Traflic Inli.Hmation
Service--Generic Promise System Architecture, Ver. 2", Telematics
Application Progr111Illlle A2, Transport, Sep. 10, 1996.
"PROMISE-Personal Mobile Traveller and Traffic Information
Service----Summary of Promise Public Relation Activities, Ver. 1",
Telematics Application Progr111Illlle A2, Transport, Feb. 12, 1999.
"PROMISE-A Personal Mobile Traveller and Traffic InfOrmation
Service-Abstract", The Institution of Electrical Engineers, 1997.
Sommerville, Fraser, et al., "The Promise of Increased Patronage",
The Institution of Electrical Engineers, 1993, pp. 3/1-3/4.
"Automatic Transit Location System", Washington State Depart-
ment of Transportation, Final Report, Feb. 1996.
"Advanced Traveler Aid Systems for Public Tran&-portation", Fed-
eral Transit Administration, Sep. I994.
"Advanced Vehicle Monitoring and Communications Systems for
Bus Transit: Benefits and Economic Feasibility", U.S. Department
ofTransp01tation, Urban Mass Transportation Administration, Sep.
1991.
Leong, Robert, et al., ''An Unconventional Approach to Automatic
Vehicle Location and Control for Urban Transit", IEEE 1989, pp.
219-223.
"1994 Vehicle Navigation & Information Systems Conference Pro-
ceedings", Yokahama, Japan, Aug. 31-Sep. 2, I994, pp. 807-810.
"Vehicle Navigation & Information Conference
Proceedings-P-253, Part 2", Society of Automotive Engineers,
Inc., Oct. 1991.
Vehicle Navigation & Information Systems-Conference Record of
Papers presented at the Jro Vehicle Navigation & Information
Systems Conference 1992., Reso Hotel, Osio Plaza., pp. 49-52.
Nelson, l Richard, "Experiences Gained in Implementing an Eco-
nomical Universal Motorist System", , IEEE-lEE Vehicle Navi-
gation & Information Systems Conference, Ottawa, VNIS 1993, pp.
67-71.
"The Cassiope/Eurobus Approach", lEEE-lEE Vehicle Navigation
& Information Systems Conference, Ottawa, VNIS 1993, pp. 79-81.
Exhibit A
Page 16
US 7,119,716 B2
Page 4
Kihl, Mazy, "Advanced Vehicle Location System for Paratransit in
Iowa", IEEE-lEE Vehicle Navigation & Information Systems
Conference, Ottawa, VNIS 1993, pp. 381-384.
Gault, Helen, et al., "Automatic Vehicle Location and Control atOC
Transpo", Vehicle Navigation & Information Systems
Conference, Ottawa, VNIS 1993, pp. 596-600.
Vehicle navigation & Information System--Conference Record of
Papers presented at the First Vehicle Navigation and Information
Systems Conference (VNIS '89), Sep. 11-13, 1999, pp. 602-605.
Heti, Gabriel, "Travelguide: Ontario's Route Guidance System
Demonstration", IEEE---lEE Vehicle Navigation & Information
Systems Conference, Ottawa, VNIS 1993, pp. A13-A18.
Jeffery, D.J., et al., "Advanced Traveller Information Systems in the
UK: Experience from the Pleiades and Romanse Projects",
IEEE-IEE Vehicle Navigation & Information Systems Confer-
ence, Ottawa, VNIS 1993, pp. 309-313.
Sweeney, Lawrence, E., eta!., "Travinfo: A Progress Report", 1994
Vehicle Navigation & Information Systems Conference Proceed-
ings, Yokahama, Japan. Aug. J 1-Sep. 2, 1994, pp. J 1 S-120.
Shimamura, Yta, et al., "Combined Position Detection System for
Pedestrian/Train Mode", 1994 Vehicle Navigation & Information
Systems Conference Proceedings, Yokahama, Japan, Aug. 31-Scp.
2, 1994. pp. 603-606.
Zavoli, Walt, "Customer Location Services", 1994 Vehicle Navi-
gation & Infonnation Systems Conference Proceedings, Yokahama,
Japan, Aug. 31-Sep. 2, 1994, pp. 613-617.
Tanaka, Yoshimi, et al., "Automatic Traffic A1Anfonna.tion Provi-
sion System Utilizing facsimile and Telephone (Now Operating in
Osaka), 1994 Vehicle Navigation & Information Systems Confer-
ence Proceedings", Yokaha.ma, Japan, Aug. 31-Sep. 2, 1994, pp.
627-632.
McDonald, Mike, et al., "Romanse (Road Management System for
EuropcProject", 1994 Vehicle Navigation & Information Systems
Conference l)roceedings, Yokaharna, Japan, Aug. 31-Sep. 2, 1994,
pp. A-11-A-14.
Scott III, Robert H., "Computer-Aided Dispatch,", 1998. pp. 46-50.
Moore, Rodney J., ·'Hold the Phone!", Americilll Demographics,
Ithaca, Jan./Feb. 1996, p. 68.
Delong, Jr., Edgar S., "Making 911 even better", Telephony, Dec.
14, 1987, pp. 60-63.
Bmzek, Frank J., "Class Calling Service-A Consumer Service
Perspective", Globecom '85 IEEE Global Teleconununications
Conference, Dec. 2-5, 1985, voL 1 of3, pp. 11.4.1-11.4.4.
Powell, R., et aL, "Real Time Passenger Information System for the
Romanse Project", Colloouin Digest···"· lEE, Boston, Sep. 1993, pp.
9/1-913.
Huber, Paul, "Public Transport Information Systems in Munich",
Intelligent Transport Systems World Congress '95--Second Wold
Congress on Intelligent Transport Systems, Yokohama, Japru1, Nov.
9-11, 1995, pp. 2362-2366.
Roncz, Nicholas, et a!, Transit Information Bolsters
Travel Options", GJS World, vol. 6, part 7, Jun. 1995, pp. 62-64.
Catliog, Ian, eta!., "TABASCO-lmproving 'lransport Systems in
Europe", Pacific Rim TnmsTech Conferem;e, Jul. 30-Aug. 2, 1995,
995 Vehicle Navigation & Information Systems Conference Pro-
ceedings, Washington State Convention and Trade Center, Seattle,
Washington, USA, pp. 503-507.
Dailey, D.J., "Demonstration of an Advance Public Transportation
System in the Context of an IVHS Regional Architecture", Pro-
ceedings of the First World Congress on Applications of Transport
Telematics and Intelligent Vehicle-Highway Systems. Nov. 30-Dec.
3, 1994, Paris, Frilllce, pp. 3024-3031.
Hubner, Paul, "Advance Public Trru1sportation Information in
Munich", International Conference on Public Transport Electronic
Systems, Conference Publication No. 42, .Tun. 1996.
Thompson, S.M., eta!., "Exploiting Teleconununications to Deliv-
ery Real Time Transport Information", Road Transport Information
and Control, Apr. 21-23, 1998, pp. 59-63, Conference Publication
No. 454 TEE 1998.
Kaminitzer, David, et al., Driver fnfonnation Systems: Influencing
your Route, IEE Seminar, Mar. 3, 1999, pp. 5!1-5/5.
"Board Cites ATC in Spokane Near Miss", Article in Aviation Week
& Space Technology, Mar. 28, 1977, URL: http://www.aviationnow.
com.
Shifrin, Carole A, "Gate Assignment Expert System Reduces
Delays at United's Hubs", Article in Aviation Week & Space
Technology, Jan. 25, 1988,
"United Airlines applies TI's advru1ce technologies to improve gate
management at major airports", A ..rticle in Business Wire, Inc., Nov.
19, 1987.
Musich, Paula, "Airline Designs Software to move planes, people;
Unite Airline's use of Covia Corp.'s Open Systems Manager,
Connectivity Section", Article in PC Week, .Tun. 7, 1988. vol. 5, No.
23, p. Cll.
Stoll, Marilyn, "Systems help Airlines Manage Gate Schedules;
Connectivity Supplement", PC Week, Jul. 25, 1988, vol. 5, No. 30,
p. C4.
Reddy, Shyamala, "Traveling LAN: United Airlines Networks Its
Terminals'', Article in The Local Area Network Magazine, .Tan.
1990, vol. 5, No. I, p. 108.
Fisher, Sharon, "Networked Airport Systems help Travelers .find
their way; United Airlines subsidiary Covia Corp. devices inte-
grated network.", Article in Software Magazine, Mar. 15, 1990, vol.
10, No. 4, p. 31.
Henderson, Danna K., "Automation Takes aim at airports: the
power of the networked PC is being unleashed on passenger
handling and ramp activities worldwide.", Article in Air Transport
Wold, Aug. 1990., Vol. 27, No. 8, p. 52.
"United Airlines introduces United Cargo Plug I, a new cargo
computer system to serve freight fotwarders". Business Wire, Oct.
22, 1990.
Miller, Barry, "Special Report: Airline Equipment, Service Center",
Aviation Week & Space Technology, Aug. 25, 1975, p. 51.
Lyon, Mark W., "Cargo Net Debate Splits Industry", Journal of
Conunerce, Specials, p. 4, Jul. 27, 1992.
Davies, l.L., ct al., "Electronics and the Aeroplane", Proceedings of
the Institution of Electrical Engineers, Paper No. 7604, delivered
before the lEE Electronics Division, Oct. 29, 1975.
"Global Niche", Flight International, Sep. 26, 1990.
"Real-Time Briefings", Aviation Week and Space Technology, Oct.
13, 1986.
Flanagan, Mike, et a!., "Amelia Earhart-Mystery Still Clouds
Soaring Achievements", Chicago Tribune, Jul. 5, 1987, Final Ed.i-
tion, p. 5, Tempo Woman,
"Official A...irline Guides", Airports®, Nov. 20, 1990, Around. Air-
ports, vol. 7, Ko. 47. p. 485.
"Automation System Gains Acceptance", Aviation Week & Space
Technology, Nov. 23. 1992, vol. 137, No. 21, p. 97.
Klass, Philip, "French Testing Ground-Derived MLS ",Aviation &
Space Technology, Avionics, p. 56, Dec. IS, 1975.
"Forecast Realized for ATC System", Aviation & Space Technology,
Mar. 17, 1975, Avionics, p. 168.
Henderson, Danna, eta!., "Ionworks: America West Automates New
Phoenix Terminal Fully Integrated System to Hamdlc
SeJYice Demands (America West Airlines Inc) (Includes Related
Article Automation of passenger Service at Airports)", Airport
Trru1sport World, May 1, 1991. vol. 62.
3 Pages tfom a web site search under http://mit.edu/afs/net.mit/edu/
projectiattic/usa-today/tech/37, Jun. 12, 2003,
''What's New in passenger Handling Equipment", Air Transport
World, vol. 24, p. 62, Sep. 1987.
"Senator Urges Acceleration ofNavstar", Aviation & Space
nology, Avionics, p. 153, Oct. 3, 1983.
"AFSC Broadens Joint Program Efforts", Aviation & Space Tech-
nology, System Acquisition, p. 83, Ju. 19, 1976.
Herskovitz, Don, "GPS Insurance Antijarruning the System; Brief
Article", Journal of Electronic Defense, Dec. 1, 2000, No. 12, vol.
23, p. 41.
Hambly, Richard M., et a!., "Aircraft Traffic Mru1agement on the
Airport Surface Using VHF Data Link for CNS", IEEE AES
Systems Magazine, Mar. 1995, pp. 9-13.
Berzins. G., et al., "INMARSAT: Worldwide Mobile Satellite
Services on Seas, in Air and on I ,and", Space Technology, vol. l 0,
No.4, pp. 231-237, 1990.
Exhibit A
Page 17
US 7,119,716 B2
Page 5
Jenney, LL., eta!., "Man as Manager of Automated Resources in an
Advanced Air Traffic System", l Aircraft, vo\. 12, No. 12, Dec.
1975.
"Routing & Scheduling System improvements from RTSI; Routing
Technology Software, Inc.; Product Annotmcement", Modern
Brewery Age, vol. 43, No. 3, p. llS, Jan. 20, 1992.
Yanacek, Frank, "Hitching to the stars; satellites for shipment
tracking", Research Information Transportation Journals, Com-
bined, 6, vol. 29, p. 16.
Stoll, Marilyn, "For on-the-road firms, hand-held terminals are
pivotal. Connectivity", Research Information Transportation Jour-
nals, Combined, No. 34, vol. 5, p. Cll.
"IBM and Hunt to Market New Truck Tracker; International Busi-
ness Machines", lB. Hunt Transport Services; Brief Article, No.
210. vol. 101, p. 4.
Klass, Philip J., "Two Carriers Plan Automatic Data Link", Aviation
Week and Space Technology, Air Transport Section, May 23, 2977,
p. 36.
"Data Link Evolved Over Three Decades", Aviation Week and
Space Technology, Air Transport Section, May 23, 1977, p. 36.
Klass, Philip J., "American to Install Printers in Cockpits", Aviation
Week and Space Technology, Avionics, Jul. 21, 1980, p. 56.
Lefer, Henry, "Computers on a boon to E&M, but at a price", Air
Transport World, vol. 23, p. 53, Feb. 1986.
Donaghue, J.A., "Choice of Data Link Expands as New
Generation Hits the Market", Air Transport World, vol. 20, p. 58,
Apr. 1983.
Klass, Philip J., "Digital Network Could Improve Aircraft Links to
Operations, ATC", Aviation Week and Space Technology,
tiona! Air Transport Section, vol. 13 t, No. 21, p. 121, Nov. 20, 1989.
Board Cites ATC in Spokane Near Miss, Article in Aviation Week
& Space Technology, Safety Section, Mar. 28, 1977, p. 59.
"Vicorp Interactive Systems", Aviation Daily, Aviation Suppliers
Section, vol. 309, No. 17, p. 147.
Neumann, Dr. Horst, "ATC Concepts with ExtensivtJ Utili;r..ation of
Automatic Data Processing", pp. 4-1 to 4-9; no Publication Infor-
mation or Date Information Provided.
Balke, Kevin, et al., Collection and Dissemination of Real-Time
Travel Time and Incident Infonnation with In-Vehicle Communi-
cation Technologies, pp. 77-82, no Publication Information or Date
Information Available.
* cited by examiner
Exhibit A
Page 18

<a"
mO'
__,.;:::;:
<0)>
Notification System
Positioning System
(e.g., GPS Satellites,
radar, etc.)
17\
::
Mobile Thing (MT)
(e.g., a Motor Vehicle. PCD, etc.)
Mobile Thing Control
Unit (MTCU) S
JJi.
29\
ensor
.1§.
Mobile
Thing TXIRX
Manager
43
31a__..
44
Base Station Control
41'
Unit (BSCU)
Base Station (BS) Manager
Combined MTTL
Response System
Stop Location And
4l_
Feedback Analyzer
Determination DTL Notification
100a
System System
190 290
Mobile Thing
li3
Secure Notification
Messaging System
Determination
210
System
250
31b--
6
q 1--=70
52
J TX/RX II TX/RX
72
[48
"Ss 14
55
45)
(61 -(_
Network(s) Network(s)
(e.g., cellular) (e.g., PSTN)
t

r73
I :]...- Response
FIG. 1
TX/RX System

Feedback
1-----'75
\
Mechanism

Sensor
100b
Personal Communications
Device (PCD)
Lj

[Jl

'"C

-
(t>
=
-
0
il-
....
• -=
N
Q
-=
<:7-.
"'
::r
"' a
....
0
_,
<JI
Q
d
rJ)
,;--l
,....
,....
\0
':..!
,....
0'1
1:;1::1
N
-um
ID X
"'"'
CD 5'
!\.);::::;:
0)>
MTCU
3Da
~ I a \
Memory
(29 L39a
Mobile Mobile
(32a (18 f38a Thing Thing
Manager Schedule
Processing
Sensor
Mobile Thing
Element Clock
L
,.
L
,.
L
,.
L
,.
<
7
"7 <>
(33a
"
7
1\
\ L
Local Interface (e.g., one or more buses, interfaces, and/or connections)
,.
L
""
.L
""
L
,.
L
"" v
{34a {35a
<? "Z ""
7(44
~
(37a
7 "'
?('
Input
Display TX/RX Disk Printer
Device
FIG. 2
6a
~

\FJ
.
"ti
~
.....
~
=
.....
0
14-
.....
::>
"'
0
0
""'
<.1'1
=-
&
"'
0
....,
<Jo
0
d
fJJ
;--1
.....
.....
\0
~
.....
0\
1:1:1
......
-um
m x

ro cr
r-0;:::;:

1:)0VU
40
(32b
Processing
Element
L
;>-.
A "'--,Z

30b

Memory
Base /39b
Station
Combined MITL And
(52, 72
Manager Base Secure Notification DTL Notification
(38b
11
Station
Messaging System System
Schedule 210 290
TX/RX
Base Station
Response
Clock
System Stop Location
Mobile Thing
Feed bad Determination
Determination
I
GUI
L
?>-
L
;>-. Analyzer System
System
46
100a 190
250
""---Z -<7
(33b

Local Interface
L
;>-. ..--; ;>-.
L
;>-. L ;>-.
L
;>-.
'
.(34b
7 '
.( 35b
7 '
.(37b
7 '
7f36b
'
;,.(45
Input
Tone
Device
Display Disk Printer Reader/
Decoder
FIG. 3
I

v
Lj

rJJ
.
"'C
a
(!)
=
...
0
,.,
:""
.....
?
"'
=
=
o-,
[L)
Q"
"'

"'
0
....,
'11
=
d
1fl
,;--1
.......
.......
\0
':...!
.......
0'1
l;l:j
N
-um
ID X
"'"" ([) 5'
1\);:o:
")>
C ~ r - - - -
End
FIG. 4A
Yes
Route
finished?
No
Sample
period
expired?
Yes
76
77
No
78
Determine current
location values from
sensor and determine
current time values from
mobile thing clock
79
Store current location
values and current time
values in next entry of the
mobile thing schedule
29a
)
~
r:n

'"d
~
-
!'!>
=
-
0
'"'
,....
.....
!?
N
0
0
0\
[f)
::r
a
....
0
....,
Ul
0
(j
rJJ
;--l
1-'
1-'
"'
':...!
1-'
0'1
t:d
N
-um
m x
" ' ~
([I 0'
1'0;:=;
W)>
82
Transmit start signal and
store current value of f-----J
mobile thing clock
FIG. 48
Transmit
alarm signal
95
Yes
Determine current location
values from sensor I 85
87
Find corresponding
entry in mobile thing
schedule
91
Calculate deviation
indicator
93
Is
deviation indicator >
threshold?
No
.96
obile thing early or late·
based upon a predefined
threhold?
No
29b
~
99
Transmi.t status
message
~
rJJ

""C
~
-

=
-
0
~
....
-?
N
<::>
<::>
0\
r:n
=-
"'

fJo
0
_,
fJo
<::>
d
r:n
.;-1
-
-
"'
:._..
......
0\
t:l:l
N
-um
m x
"'"" roC'
/ \ ) ~
.,.,
)
T'
Us ;er
BSCU
40
{72
I
TX/RX r-
rfs,-72
.I TX/RX I
-1 I
(72
I
TX/RX
r-
52"
,),.
I
TX/RX
I
(41
Base Station
Manager
Database
94
Mobile User Comm Stop
Thing Data Data Method Location
68a 68b Data Data
68c 68d
I Authentication Data J
PCD Travel Traffic Flow
68h Data Pred. Data
68i §.ill
t
(67
Data Manager
I
Algorithms
I
98
~ Lsz
I
TX/RX
I I
TX/RX I
52_) j4
To Mobile Thing
FIG. 5A
MT Travel Ad PCD
Data Data Data
68e 68f 68g
Package Failure
Tasks Data
Data States Data
68m
68k 681
e

rn
l"d
a
('!)
=
...
0
l4-
l-'
?
....
c
c
0\
rJl
::r
"'

0\
0
...,
"'
c
d
fJJ
;-l
......
......
\0
~
......
0\
o:;
N
-um
~ ~
r-0;:;;:
<n)>
ToPCD
TX/RX
Database
94
User
Data
68b
Data Manager
(82
~ 0
Message
Manager
(86
Mapping
System
FIG. 58
(67
To Travel Data
(69
Monitoring
Mechanism
'
I
~ 6
To MobileT
TX/RX
hing
L:

lJ)
.
"'d
a

=
.....
0
(")
l"'
.....
• o
N
0
0
"'
"'
::r
"'

__,
0
...,
Ul
0
(j
[JJ
--1
-;.....
......
\0
~
......
0'\
l;d
N
-um
! ~
<»)>
Monitoring
mechansim
69--
FIG. 5C
881
T ransmil retrieved
travel data to
message manager
or mapping system
user
preferences
in database
88k
Retrieve desired
travel data
Yes
Data
received?
Yes
Data
H8a
No
88b
from mobile >-Yes
thing?
No
User
Preferences
?
No
88g
88i
Message is a
request for travel
data
88j
Interpret request to
determine which travel
data is desired
88c
Compare travel data
from mobile thing to
preference data in
travel data table
88d
88f
Send
notification?
No
Store travel data
in database
Yes
88e
Send notification
command to message
manager and/or
mapping system
e

<JJ

"C
~
('!)
=
-
0
~
.....
9
N
0
0
"'
"'
:r
"'

00
c
-,
Ul
0
d
r:n
;--1
......
......
"' ':...!
......
0'1
l:i:l
N
-um
m x

<ll CY
1'0;:::;:
"l>
FIG. 50
Data
90a J
No
received?
Yes
90b
Data from
user?
Yes
90f
Activation
request?
Yes 90g
Prompt user for
contact information
and notification
preferences
90h
Store contact
information in user
database
90i
Transmit notification
preferences to
monitoring
mechanism
No
90e
Send data to
user
90c
/90d
Message from H Retrieve contact
monJtonng information from
mechanism or user database
mapping system
90n
90j
Update
request?
Message is a
for travel
data.
Ok I r90o
Prompt user for
new information
901
Update contact
information
90m
Transmit new
notificaiton
preferences to
monitoring
mechanism
Send a request to
n:oonitoring
mechanism
·90p
Receive travel
data from
monitoring
mechanism

82
e

rJJ

"'C

-

=
-
0

,_.
,?
N
"'
"'
0\
r:IJ
=-
a
'<>
0
...,
Uo
"'
d
rJJ
,;-I
......
......
\0

......
0\
ttl
N
;;?;r
"'"'
CDO'
!'0;::::;:
CO)>
Notification System
1Q
Response System
Feedback Analyzer
100a
Instruction Lookup
84
'
Notification-Receiving Party
Contact Records
86
Response System
100
FIG. 6
Personal Communications
Device
75
Response System
Feedback Mechanism
100b
e

rJJ
.
"d
~
.....
~
= .....
0
"'
,..
- $'>
N
0
0
a--
"' =-
"'
a
-
0
<:0
....,
til
0
d
00
~ - - . . )
.....
.....
\0
~
.....
0'1
l;l:l
""
;;?!Jl
< 0 ~
CD 0'
tv;::;:
<D)>
Start
+
Causing initiation of a
notification communication to a
personal communications
device associated with a party
+
During the notification
communication, receiving a
response from the party's
personal communications
device, indicating that the party
associated with the personal
communications device has
received notice.
··---
FIG. 7A
100a
)
01
02
(
Start
'
Monitoring .travel data in
connection with a mobile thing
that is destined to pickup or
deliver an item at a stop
location
t
Causing initiation of a notification
communication to a personal
communications device based
upon the travel data
+
During the notification
communication, enabling a party
associated with the personal
communications device to select
whether or not to communicate
with a party having access to
particulars of the pickup or deliver
FIG. 78
100a
)
(
Start
'
'
Monitoring travel data in
connection with a mobile thing
that is destined to pickup or
deliver an item at a stop
location
6
t
Causing initiation of a notification
communication to a personal
communications device based
upon the travel data
+
07
During the notification
communication, enabling a party
associated with the personal
communications device to change
one or more tasks associated with
the pickup or delivery.
FIG. 7C
100a
)
9
0
~
rJ'1
.
.,
~
(!>
=
,...;..
0
"
,..
....
~
N
0
0
""
[fJ
"'
"'
('I>
-....
....
"'
....,
U1
0
c:j
fJ}
~ - . . . )
......
......
\0
~
......
0\
C:i
N


([l 0'
w;;:o:
OJ>
Start
)
Monitoring travel data in

connection witt things.
Causing initiation of a notification
communication to a personal
communications device based
upon the travel data.
During the notification
communication, providing a
plurality of arrival or departure
times in relation to a location and
enabling selection of one of the
times.
Causing a mobile thing to arrive
at or depart from the location at
substantially the selected time.
FIG. 70
100a
).
5
6
117
e

\Jl

'"C
a
!'0
=
......
0
"
,..
.....
?
.....
0
0
a,
[f)
=-
"'
"'
...
.....
.....
0
...,
lJl
0
(j
[fJ

......
......
'-0
':...!
......
0\
eo
N
\._
Start
+
Causing initiation of a
notification communication to a
personal communications
device associated with a party
J
Receiving a response




communication from the party's
personal communications
device

Modifying the manner in which
future notification 1--
communications are to be sent,
based upon the response
FIG. 8
100a
)
2
13
e

rJl


a

=
-
0
"'
,..
,.....
.?
N
...
...
0\
"' =-
"'
"'
-
,.....
,_.
0
-,
<Jl
...
(j
rJJ
;--I
.....
.....
\0

.....
0\
=
""
-um
~ X
"'"
g
N)>
(
Start
' _)

Modifying contact data based
upon the response
J
Causing one or more other
notification communications to
the party and/or one or more
other parties, based upon the
modified contact data
FIG. 9A
3
121
2
(
Start
)
+
Modifying contact data based 1--
upon the response
~
Causing the notification system
to refrain from sending
notification communications to
the party's personal
communications device after
receiving the response
+
Causing one or more other
notification communications to
the party and/or one or more
other parties, using one or more v
different communication
methods, based upon the
modified contact data
FIG. 98
113
31
32
3
( r J3
141
Modifying contact data based [__/
upon the response
1
Causing the notification syste.m l/
to refrain from sending 142
notification communications to
the party's personal
communications device after
receiving the response, until the
detection of one or more events
r 143
one or more events v
T
Causing one or more other
notification communications to
the party and/or one or more
other parties, using one or more
communication methods
FIG. 9C
144
/
~
1Jl

'"C
~
-

=
-
0
~
.....
?
N
<:>
0
"'
'JJ.
=-
!i
.....
...
0
....,
>Jo
0
d
rJJ
;-l
......
......
\0
':...!
......
0\
~
~ ! J l
" ' ~
(tl 6'
w:::o:
W)>
(
Start
)
~
Receiving a notification
communication with a personal
communications device
associated with the party from
the notification system
+
Receiving an input response
from the party associated with
the personal communications
device.
t
Communicating the party's response from the
personal communications device to the notification
system. The response may merely confirm receipt
of the notification, may indicate a desire to carry on
a discussion with a representative, andior may
indicate the manner in which future notification
communications should be communicated to the
party.
------- -
FIG. 10
53
~
\J1

'"C
~
-
!'!>
=
-
0
14-
....
~
N
0
0
"'
rJl
=-
!l
....
OJl
0
-,
OJl
0
cj
rJ)
;-l
.....
.....
\0
:.:.
.....
0\
=
N


Cll 0'
w;:::;:
.. ,.
(
Start
)
\
• Monitoring travel
data associated
with a mobile thing
Contacting a party
based upon the
travel data
Providing an
advertisement to the
party substantially
during the contact
Charging a fee or
monitarily benefrting
from providing the
advertisement
FIG. 11
1-
2
1-
64
(
Start "'
'
Enabling a party to indicate a
willingness to receive one or
more advertisements during a
notification regarding a mobile
thing
+
Providing a notification
communication involving travel
status of the mobile thing
+
Providing an
advertisement as part
of or accompanying the
notification
communication
+
Charging a fee or
monitarily benefiting
from providing the
advertisement
L__ ___
FIG. 12
71
172
e

rJ)
.
1-C

......
l'!>
= ......
0
"
,..
.....
?
N
""
""
0\
fJl
=-

.....
0\
0
....,
Ul
""
d
rJl

-
-
\C

-
0\

~ I r
~ ~
ct>O:
(;:);:::;:
"'""
(
Start
• Enabling a party to indicate a
willingness to receive one or
more advertisements during a
notification regarding a mobile
thing
~ Hl2
Providing a notification
~
communication involving travel
status of the mobile thing
184
Providing an
r-
advertisement as part
of or accompanying· the
notification
communication
'
185
Charging a fee or
__/
monitarily benefiting
from providing the
advertisement
Charging a fee or
monetarily benefiting from
providing the notification
communication
Providing a discount based 86
upon the party's willingness
to receive the one or more
advertisements
(j

1JJ

""'
a

= .....
0
"
:"
.....
?
"'
<::>
<::>
""
'Jj
:r
"'
.....
__,
0
....,
"'
<::>
d
[J)
~ - - ~
......
......
"'

......
0\
=
1:->
-um
m x
"'"'
rocr
w;::;.:
"'>
( Start
)
;
Monitoring travel data
associated with a mobile thing
~
Causing communication of a
notification involving a delivery or
pickup task associated with the
mobile thing to a personal
communications device
associated with a party
• Receiving location data from the
personal communications
device

Determining one or more stop
locations, based upon the
device location data and the
travel data associated with the
mobile thing
+
Causing communication of an
identification of the stop
location(s) to the personal
communications device so
that the delivery or pickup task
can be accomplished at one
of the stop locations.
FIG. 14A
Joa
92
193
94
95
(
Start
;
Monitoring travel data
associated with a mobile thing
+
Causing communication of a
notification involving a delivery or
pickup task associated with the
mobile thing to a personal
communications device
associated with a party

Receiving location data from the
personal communications
device

Determining one or more mobile things
with one or more corresponding stop
locations, based upon the device location
data and the travel data associated with
the mobile thing
+
Causing communication of an
identification of the mobile things
and stop locations to the personal
communications device so that the
delivery or pickup task can be
accomplished.
---------
FIG. 148
)90b
04
C'j

~
~
a
(!>
=
-
0
" r-
.....
?
....,
""
""
0\
00
:r
a
.....
QO
0
....,
Ul
""
d
rJl
;-l
.....
.....
\0
:...
.....
"' c:;
N
;;?1r
< 0 ~
(p 0'
w;::::;:
~ ) >
( Start
)
Receiving timing criteria
'
Monitoring travel data
associated with a mobile thing
~
Determining one or more stop
locations, based upon the
timing criteria and the travel
data associated with the
mobile thing
+
Causing communication of an
identification of the stop
location(s) to the personal
communications device so
that the delivery or pickup task
can be accomplished
FIG. 15A
190c
211 j
212
13
4
(
Start
J
_y
Receiving timing criteria
'
Monitoring travel data associated with
a plurality of mobile things, e.g., first
and second mobile things
t
Determining one or more first and
second stop locations, based upon the
timing criteria and the travel data
associated with the first and second
mobile things, respectively
+
Causing communication of an
identification of the first and second
mobile things and the first and second
stop locations to the personal
communications device so that the
delivery or pickup task can be
accomplished at least one of the stop
locations
FIG. 158
190d
1)
3
24
d

Vl
i"'d
a
('!)
=
......
0
~
.....
p
N
0
0
a,
en
:'
"'
a
.....
'0
0
....,
u.
0
('j
[JJ
~ - ~
......
......
'-0
~
......
Q\
c::;
N
;;?[Jl
~ ~
(D 0'
w;=,:
'")>
Memory
30b
Authentication
Information
234
...,
( S t a r t ~
I
231
Monitoring travel data 1----/
associated with a mobile thing
Causing communicating of a l-)
2
32
notification involving a delivery or
pickup task associated with the
mobile thing to a personal
communications device
associated with a party
Causing authentication l)33
information to be provided to
the personal communications
device that indicates to the
party that the notification is
from an authorized source
FIG. 16
210
)
Lj

rJl

"'tj
~
~
=
-
0
~
.....
~
N
<:>
<:>
"'
""
,.
g
-
N
<:>
0
-.
v.
<:>
d
"'
;-l
.....
.....
"' ':....!
.....
0'\
l:r:l
N
-um
W X

([) 5'
w;::;:
W)>
I
I
INTERNET SERVICE PROVIDER

--------
File Edit Go To Views Events Window Help

----
...
YOU HAVE RECEIVED NEW MAIL

FROM I
SUBJECT I RECEIVED
I
XYl-Charity@secur . Arriving € By seCU79Afriva-l ------- 1:47:58 PM
EST

Subj: YXZ CHARITY ARRIVJNG IN 2 MINUTES
VERIFICATION WAS PASSWORD
Date: 1/28/1995 1:47:56 PM Eastern Standard Time
"PATI2345G"
From: PatSmith@SecureArrival.com
I
To: NancyS@Domain.com
The person to the right will be approaching your
home at 1:49pm.
235
I
I
Please reply to this message for additional
verification, ·to cancel the arrival, or to reschedule. I
I
I
I
j
Save I Delete I Reply
I ...
------------------------------------------------
I fSP BROWSER
Start __ rcoNNECTt:D)
------
r------8,45-
FIG 16A
(""j

iJl

"'C

-

=
-
0
'"' :-
.....

N
.,
.,
""
"'
,.
"'

N
.....
0
.....
"'
.,
d
r:n

.....
.....
"'
':...!
.....
"'
l:d
N
-um
W X
~ ~
{[l 5'
_f>,.;::;:
0)>
Start

Permitting a party to identify a pickup
location, a dropoff location, and one or 1<
more notification preferences
Identifying a mobile thing based upon the -
identity of the pickup location. the dropofff-
location, or both
Causing communication of an identity of
the mobile thing when appropriate,
pursuant to the one or more notification
preferences
FIG. 17A
250a
)
2
3
(
Start
"
Causing establishment of a first
communication session between the
system and a PCD
'
During the first communication session,
permitting a party to identify (a) a
communications method for providing a
nolif!cation, (b) a pickup location and (c)
a dropoff location

Identifying a mobile thing that will arrive
at the pickup location for pickup and that
will travel to the dropoff location for
dropoff, based upon the identity of the
pickup location, the dropoff location, or
both

Causing establishment of a second
communication session in accordance
with the communications method for
providing a notification
~
During the second communications
session, identifying the mobile
thing,
FIG. 178
250b
)
2
3
-
4
65
("j

rJJ

'"0
~
(!>
=
"""
0
"'
:"'
.....
-?
N
0
0
0,
CIJ
:r
a
N
N
s..
Uo
0
d
r:n
;--l
......
......
1,0
~
......
0\
co
N
; ; ? ~
" ' ~
mO'
""'";:::;:
~ ) >
L.
(
Start '
~
During a communication session with a
personal communications device,
determining a location of the personal
communications device
~
Identifying a mobile thing to travel to the
location or a different location for a
pickup or delivery based upon the
determined location
FIG. 17C
1
250c
)
72
(
Start l
' Establishing a first communication
session between the system and a
personal communications device
During the first communication session,
determining a location of the personal
communications device
Selecting a mobile thing from among a
plurality to travel to the location or a
different location for a pickup or delivery
at the location
Establishing a second communication
session between the system and the
personal communications device when
one or more user preferences criteria
relating to travel status of the selected
mobile thing have been satisfied.
FIG. 170
250d
)
3
r-
84
Lj

7:JJ

~
~
-
(!>
=
-
0
;;.
.....
:?
...
¢
¢

[1).
=-
a
...
w
"'
....,
Uo
¢
d
rJ)
;--1
.....
.....
\0
':...1
.....
0'\
=
N
-um
m x

(J) 5'

"'""
(
Start
t
Monitoring travel data associated with a
mobile thing in relation to a location or
region
Monitoring travel data associated with a
personal communications device in
relation to the location or region
Causing a notification communication to
be initiated to the personal
communications device when the device
is at or within a predetermined proximity
of the location or region
Before, during, or after the forgoing
causing step, causing a different
notification communication to be initiated
to the personal communications device
when the mobile thing is at or within a
predefined proximity of the location or
region
FIG. 18
290
)
3
-
94
("j

rn
'"C

-
(1)
=
-
0
<">
,..
.....
9
N
0
0
a,
(J]
='
"' !!:.
N
...
0
....,
u.
0
d
r:n
;-"
......
......
"' ':...!
.....
0'1
O:l
N
; ; ? ~
~ " "
CPO'
.f».;:::;.:
W)>
(
Start

Monitoring travel data associated with a
~
mobile thing
Scheduling a notification communication r--
Analyzing traffic flow predicament data
associated with a travel path to be
t-
traveled by the mobile thing
Rescheduling the notification
communication, based upon the traffic flow
predicament data
FIG. 19A
310a
)
3
14
( Start
\
'
Monitoring travel data associated with a
mobile thing
+
Storing a notification time period
associated with a notification
communication, the time period
indicative of a proximity of the mobile
thing to a location
Analyzing traffic flow predicament data
associated with a travel path to be
traveled by the mobile thing
Determining when a notification
communication should be initiated, based
upon the notification time period and the
traffic flow predicament data
FIG. 198
310b
)
-
3
I--
24
Cj

1JJ
.
"0
~
!'!>
=
......
0
~
.....
9
N
0
0
0\
"' =-
"
N
Ul
0
....
Ul
0
d
"'
;--1
......
......
'0
':...!
......
0'1
b:l
N
; ; ? ~
"'"" (I) 5'
~ ; : : ; :
.. ,.
'
Start
'
Analyzing traffic flow predicament data
associated with a travel path to be
traveled by a party or mobile thing

Causing initiation of a notification
communication session with a personal
communications device, based upon the
traffic flow predicament data
During the notification communication
session, causing a message to be
provided that indicates a state of traffic
flow along the travel path
,_
-------- -------------
FIG. 19C
310c
)
2
33
~
r.FJ

"d
~
(!)
=
-
0
"" r-
,.....
~
N
0
0
0\
en
=-
a
N
0\
0
....,
<1o
0
d
[J)
;--1
.....
.....
"'
.....
0\
=
N
; ; ? ~
"'"'
CD8'
.f>.;:::::
~ >
'
Start
/

Monitoring travel data associated with a
I-'
first communication device

Causing a notification communication session
to be initiated to a second personal
communications device. the notification
communication including a message requesting
a response and a travel status report indicating
a proximity of the first personal communications
device to a location
...
Receiving the response from the second
-
personal communications device
Communicating the response to the first
personal communications device
I'
- ~ ~ ~ - - - - - · -
FIG. 20A
340a
)
42
4
( Start )
t
Monitoring travel data associated with a
first personal communications device
Receiving a message from the first
personal communications device, the
message including a request for a
response
Causing a notification communication
having the message and a travel status
report of the first personal
communications device to be intiated to
a second personal communications
device

Communicating the response to the first
personal communications device
---------
FIG. 208
340b
)
3
54
d

lJl

'"d
~
-

=
-
0
"'
,..
.....
. o
N
0
0
"'
00
"'
"'

N
_,
0
-.
(Jo
0
tj
CJ)
;--1
,.....
,.....
\0
':..t
,.....
0'\
b:l
N
-um
ID X
"'" CDO'
.t>.;:::;:
<»)>
\
Start
+
Monitoring travel data associated with a
first personal communications device
Causing a notification communication
session to be initiated to a plurality of
personal communications devices, the
notification communication including a
message requesting a response
Receiving responses from one or more
of the plurality of personal
communications devices
Producing a list of stops for the first
personal communications device, based
upon the responses, the lack of
responses, or a combination thereof
FIG. 20C
340c
1---
J
2
1-
3
1-
64
e

lJJ

'"C
~
-
!'!>
=
-
0
..,
,..
.....
.o
N
0
0
a--
"' =- .,
~
N
QO
0
....,
Ul
0
Cj
CJ}
.-I
1-'
1-'
\0
~
1-'
0\
O:i
N
,m
W X

Cll o=
..f>.;::::;:
"'"'
RECIPIENTS OF NOTIFICATION
MESSAGES
75g
'peRSON'S
MOBILE PHONE
75!
'-....
75h
'-....
PERSON'S
TELEVISION



PERSONAL OR VEHICLE
NAVIGATION SYSTEM

75e

WIRELESS VIEWER
75d
"'"' PERSON'S
NE"M'ORKED COMPUTER
"THE JONES f'AMILY,
PARTY OF 4 IS ARRIVING
I IN 20 MINUTES. PLEASE
CONFIRM A RESERVATION
IF AVAILABLE BETWEEN
20-45 MINUTES FROM
THIS TIME?
-·-·
1--1
75
10
BASE STATION CONTROL
UNIT IS
40a
D
40b
FIG. 21
40
VEHICLE NAVIGATION DEVICE WITH
NOTIFICATION MESSAGING
75a

MOBILE COMMUNICATION DEVICE
EQUIPPED WITH LOCATION DEVICE

VEHICLE WITH ROUTE
OR STOP LIST
DEVICE
@

'( .
75
75b
l'j

rJJ
.
""d

-
(0
=
-
0
"
'"'
"'"'
:0
N
0
0
"'
00
0'
,

N
>0
0
....,
Ul
0
Cj
1JJ

.....
.....
\0
':...:!
.....
0\

-um
W X
"'""
cn5'
.f>.;::;:
00)>
40

COMMUNICATION OPTIONS
COMMUNICATION THROUGH BSCU

L I ··· ....
I
I --------- -------- - - - _j
COMMUNICATION DIRECT (NO BSCU)
' ·n'
I I
I
RESPDNSE MUST BE RECEIVED WITHIN
4 MINlfTES & 57 SECONDS
I
75j
I , 75i
J l ____ _
FIG. 22
cj

1JJ
.
"d
a
('!)
=
.....
0
"
,...
....
$">
N
=
= a--
CJJ
=-
a
"'
0
0
-.
VI
0
d
fJ1
;--1
......
......
I.C
':...!
......
"'
c:l
N
-um
ID X
"'"'
(I) 5'

<0)>
RECIPIENTS OF
NOTIFICATION MESSAGES


MOBILE PHONE
75h
"
PERSON'S
TELEVISION


- .



NAVIGAnON SYSTEM

75e

WIRELESS VIEWER
75d
PERSON'S
NETWORKED COMPUTER
"THE WHITE F'AMIL Y,
PARTYOF41SARRIVING 114 )'{
IN 20 MINUTES. PLEASE
CONFIRM A RESERVATION
IF AVAILABLE BETWEEN
20-45 MINUTES FROM
THIS T!ME?
-·· _-w·-
, __ ,
75
MTCU

(IN-VEHICLE NAVIGATION SYSTEM)
ETA DETERMINING
E.G.,
MAPPING
HISTORIC OAT A,
TRAFFIC, ETC.
{External and/or
Internal)
---------------
POSITIONING
S-YSTEM E.G.,
GPS, LORAN,
GLONASS
AUDIO (VOICE)
. 431
1
• 432
;f
425
427
SEND
NOTIFICATION
REQUEST
RESPONSE
'.. -----f -; -----' Vehicle Navigation System
433 I : E """ . ;y
438
439
I I,

I
Italian Rcsbul";)nls" l
REsPONSE ___ _
l.J -------·· ··- .... · · ----···-·· • ··-··------------
FIG. 23
15
SELECT COMPANY
FROM LIST TO
NOTIFY
MENU
426
lr 4281
e

1JJ
.
'"d
a.

=
.....
0
"
,....
.....
.?
N
=
=
o-
[/]
0'
"'
"'
.....
"'
.....
0
....,
'Jl
=
d
rJ)
;-l
......
......

-:....
......
0'\
1:0
N
-um
0 X
"'"" (I) 8'
U'l;:::;:
OJ>
454
455
456
457
HAS RESPONSE OCCURRED?
NO
RESPONSE FAILURE
STATE BEEN
REACHED?
453
AN ARRIVAL NOTIFICATION
WAS SELECTED FOR THE
XYZ ITALIAN RESTAURANT
SHOULD THE MESSAGE
INCLUDE A REQUEST FOR
RESERVATION?
YES NO
SHOULD THE MESSAGE
RECIPIENT RESPOND?
NO
WHAT IS THE RESPONSE
FAILURE STATE?
PERSON'S
NETWORKED COMPUTER
75d
NOllFJCAT!ON WAS
RECEIVED AND YOU HAVE
A CONFIRMED
RESERVATION AT 6:40PM
I
UNDER WHITE
I PLEASE CHECK-IN UPON
ARRIVAL. THANK YOU.
.... --··-----
I --,_j
PERSON'S
75k IN-VEHICLE NAVIGATION SYSTEM
8
§\
""
8
4481
XYZ !lalian Restaurant "Notification Was Received
And You Have A CONFIRMED RCSERYATION AT 6;40PM
I_· --Under White. Please Check-In Upon Arrival. Thank You.
FIG. 24
I
'
d

rJJ

"'0

-
!'!>
=
-
0
"
,..
.....
?
"'
0
0
0\
CI:i
=-
g
-(H
"'
0
-.
Ul
0
Cj
r:n

......
......
\0
':...1
......
"'
l:d
N
-um
m x

('p 0'
01;;::.:

,----
NAVIGATION SYST£:1'! UTILIZING TIME BEFORE/AfTER MESSAGE

I \ \
I I \
I I I
I \ I
L
, I
ETA;;2!Jmmutes-12Mlles 8' I
1
- Reclplenll' 01 NottflcaHcn Message• MU$1 ResiXlnO "'ENU '
Wnt>rn 15 Or SysttrnW<n Not Extept?
FIG. 25A
463
IN-VEHICLE NAVIGATION SYSTEM IJTlL!ZlNG LOCATION AFfER MESSAGE
WAS SENT AS THJ! DEFAULT FOfl RECIPIEI>ITS TO RESPON[} TO NOTIFICATION MESSAGE$
! j_u ">;, 7 7r--
75k
-
ReclpH:nt. of NotlflcaUon MO:S$OIJ<l5 Mu$1
e,!ore ThO. Antvel; AI Tha !'toni L<ICIIUcn,

8\\
'\J8:i.
_eJJJ
·--·--
FIG. 25C
462

IN-VEHICLE NAVIGATION SYSTEM UTILIZING OIST ANCE AFTER
WAS SENT AS THE DEFAULT FOR RECIPIENTS TO RESPOND TO NOTIFICATION
of NotWJcatlon Messages; Must Respond
Within !6 OrSy5temWBI Prompt Ft>r
Acceptance?
FIG. 258
464

I
IN·VEHIClE NAVIGATION SYSTEM UTIUZING FIRST RESPONSE AFTI':R MESSAGE
W/l$, SENT AS THE DEFAULT FOR RECIPIENT$ TO RESPOND TO NOTIACATION MESSAGES
§ ""-

i
75k

8\\
8\\'
.@ill
The Flr.ll To Tho N<>llflc:atlcn
Will8e &cepted?
;
L
FIG. 250

rn
""d
a
(!)
=
""'"
0
...,
,..
.....
$'>
N
Q
Q

"' =-
"'

""
"" 0
..,
<Jo
Q
Cj
[JJ

......
......
"'
':..!
......
0\
=
N
-om
m X

(J) o=
01;:::;:
"'""
4
'.
f
"
VEHICLE
LOCATION
OElERMINED
.!.
\ WHAT ARE NEXT
STOPS?
h
i
l
'r- OOIHAVEANY
ADDITIONAl STOPS
47
TO ADD OR
DELElEJ?
I
474
OR STOP liST
Start )
I--
,->
1


WHAT IS TI-lE NEXT
STOP?

!-;476
j:;:::::
TYPE OF STOP IS

(OS) OUTSIDE SERVICE

IS RESPONSE NEEDED
!-;477
FOR(OS)TYPESTOPS?
B$
DETERMINE IF RESPONSE
HAS OCCURRED
FIG. 26
VEHICLE TYPE OF
STOPS STOP
__ -------- {IS)
___ West 6th Ave --(OSj·------:
2 l ••••••••••••••••••••• .
- 975 1st Avenue ------{isr·------·

I
I
I ;ETRY II lli [ MENU
1

rFJ

'"d
a

=
-
0
fl.
.....
$"
N
<::>
<::>
0\
00.
::r
...

"'
...
0
....,
tJo
<::>
d
'fJ
;--l
.....
.....
"' ':...!
.....
0'1
1:0
tv
-um
ID X

<DO'
01;:::;:
W)>
··--- --- ....... --l
505 500
i ........ ························ S........................... . .. S ...... ,I
I :
I •1
I
I
TIME FROM :: 501
. - CURRENT ;:
,-- LOCATION :; r-
i
l PLANNED • ... .!.._,., .. _ ·• __."o"_"o'·";i ERY ADDRESS #03
¢; . . 1: @;QQ. • .. DELIV AL
................. , • \.............. F 30 MINUTE ARRIV
..... ,.,,,,,,,,,:·T·•;r;r;;<; !i---..o. 0
I nru
F STOP t · #0
1
. . . . . · · · · · · · · · · .. i! . QO;O . Q 502 •
... 1= 0 . 7:50 r=__j_
!
•: O:Og:OO PERSON AT DELIVERY
: 00:10:50 .
-··· ··· .. · . . . . . . . .. 4" • • OO
12
ADDRESS #03 MAY
J• • · · · · • · ·oo
OF DELIVERY it. j, •) ; 00:15:00 ; " MINUTES OF
?
PERSON RECEIVES
NOTIFICATION
75d II I
"-YZ SERVlCEVEI-IICI.E
WilL ARRIIIE IN 30
MINUTES, IF YOU
RESPOND TO THIS

DRIVER RECEIVES
! .,;,,;., ;;;
# 02 . . . . . . d ; 00:16:50 :: NOTIFICATION .
- ""-· ..... : · oo·1a·oo -: i: I
.... '"j
503
I • '· "u"""""u" u•
. ··l·········· 00:21:00 :: 'I \ FAILURESTATEOR
••• ·f· • • • • • • • • • • • • • • • 00:22:50 • WHEN NO RESPONSE IS : . . . c ___o_.·.N.·FIR __ .. M., A __.-._·r __ 1_0_N_
'5c
00:24:00 . MADE FROM THE :' •
00:25:50 :' INTENDED RECIPIENT :I .lf"i:,;;,;:· .
DESTINATION . . . . • . ((" • • 00:27:00 :: WITHIN 20 MINUTES ::
OF DELIVERY f.t;), · · · · · Q0:
2
P:-
5
Q .. ;: AFTER NOTIFICATION, :'
# 03 t " 00·30·00 :: FAILURE STATE • .'
--- • • • 00:31:50 :
.... ····· ...... .... · ..................... :c-::::=-:c.. . . i ' ··········· . ..
FIG. 27
e

'/1
'"d
a
(!>
=
0
"
,..
.....
• o
N
0
0
"'
"'
=-
a
.....
Vo
0
-.
'Jo
0
d
00

......
......
"'
......
0\
t:tl
N
;;?!:r
< 0 ~
CD 0'
01;::::;:
"'"'
506
. : ~ : .......... .
DELIVERY ADDRESSES WITH
CONFIRMATIONS
DISTANCE
FROM
LOCATION
0000:20
. . . . . . . • . . . . . . '· 0000;40 .
I
0000:60
I, oooo:8o
DESTINATION . I· 000'1 :'00 ·
OF DELIVERY NO RESPONSE , 0001:20
1104 .. ,-, .-.-. .1 . . . • . . . . . . . . . . . i. PQ0.1 ;40 . J : rl
= I . I 0001:60 I
.............. t ............... 11. ~ ~ ~ ~ ~ ~ ..
I _ ooo2:2o
DESTINATION -/
OF DELIVERY ----\
#05
0002:40
·ooo2=6o ·
0002:80
0003:20
. . . . . . . . . . . . . .
. . • . • . . . . . .... '· 000'3:'40 .
DESTINATIONcl
L
. OF DELIVERY __.\
#06
----- I
0003:60
0003:80
0004:00
FIG. 28
Lj

rJl

"'d
~
-

=
-
0
14-
.....
$"
N
0
0
0\
TJJ.
::r
"' a
w
0\
0
...,
<Jl
0
d
IJ1
~ .....
>-'
>-'
"'
':...!
>-'
a._
o:l
N
-om
m x
"""" (I) 0'
()1:::;:
<n)>
BSCU
~
40
( Start
t
51t_
1-'- BASED ON RESPONSES
WHAT IS STOP ANO I OR
PCD
DELIVERY LIST NOW? 75c
...
5 1 ~
~
WHAT IS NEXT STOP
(
ON DELIVERY LIST?
I ~ } i ~ ~ ~ ~ 3
...
5 1 ~
r
IS THIS A CONFIRMED
DELIVERY ADDRESS?
Vr -I?[
(RESPONSE FROM USER) MOVe
li
l/l
1
+-- ~
...
RETRY .. II .!.i II
MENU
I
51t
r-
DISPLAY THE
,__..
INSTRUCTIONS ON
LCD
t
51t
r-
WAIT FOR NEW
ROUTE LIST OR MORE
INSTRUCTIONS
FIG. 29
(j

rJ)
.
"'d
a
('!)
= .....
0
"'
:""
.....
?
N
0
0
a,
"' =-
"'

w
-l
0
...,
Ol
0
d
[JJ
~ ......
.....
.....
"' ':...!
.....
0\
o:J
N
.,m
ID X
"'"'
CDQ'
U1;:o:
"""'"
BSCU 40 OR MTCU 1.9_
ROUTE STOP DESTINATIONS
. . . . . . . . . . . . . . . . . . . . .
:---- .....
: 11 DESTINATION !
•.... ·I OF I· ... .
·r ............. .A.c'fuAL:Ioc/\rioN ........... 1
•L .. .... !
·. '1" ............ .. ..
DESTINATION :
· .
1
.. · OF .. " ·
. . . . . . . . . . . . . . . . . . . .
.. i· .I DESTINATION , •.•...
I OF DELIVERY
#18
. 'l' .. -........ ..... .
. . . .
I
. .I OF DELIVERY
.. l-'. #19
I .................................... ..
540
- --- --------- - .- - :C. - 3 ____ ---
531
1-- NOTIFY NEXT
I DESTINATION
'
·l DETERMINE RESPONSE
FAILURESTATE

HAS RESPONSE
OCCURRED?
534 '-= * I -
HAS RESPONSE FAILURE
STATE BEEN REACHED?
. . FAILURESTATE I
L HAS OCCURRECJ__j
FIG. 30
WHAT IS
THE RESPONSE
FAILURE STATE?

I )P\ TYPE
TIME BEFORE
I ARRI'i¢L i
c 544
LOCATIONATOR
PRIOR TO DESTINATION [
"\:: 545
ROUTE LIST
STOP NUMBER
--"\::547

DISTANCE AWAY FROM .
DESTINATION
-. 548
I
d

r:FJ

"tt
a

= ....
0
"'
,..
.....
.Q
N
Q
Q
a,
"' =-
"'
a
"'
QO
0
....,
Ut
Q
d
(I)
,;--1
1-'
......
\0
':...1
1-'
0\

-om
ID X
<a"'
coO:
01;::::;:
--<)>
BSCU 40 OR MTCU
DELIVERY
LIST
,
i::l
DELIVERY TO BE MADE#4 1 ••
l :
.. [EELIVERY TO BE MADE #5 I' . :.1
. .. t
[ DELIVERY TO #6 __j ::1
........... [_ ........... :
. . . . . . . . . . . . .......... .
[REQUEST FOR PICKUP #7 ]
..................................... . ................................................. !
I CHANGES BY DRIVER AND L I
LOOK IN ACTIVE DATA
BASE FOR NEXT STOPS
I
I
AC11VE
I
DATABASE OF
CUSTOMERS
I
I
AND
DELIVERIES
65
i
I
........... l...... .. I] . .
! • • • l .. :: SHOW RESPONSE I
I --""'""'00"'"""'00 ', = I
...............•..... _ _ _ . THIS CUSIDMER I
I I !
000000000000000000000 woo 00 ,0000 000

......... wooo oo
0000000
00 00 ,,
00
'
0000
''" oowoooo•
00
1
• I
FIG. 31
('j

rJJ


a

=
...
0
"
" ....

N
0
0
""
rJJ.
::r
"' a
w
\0
0
....,
<Jl
<:>
c:j
r:n

......
......
"'
-:...-.
......
0'1

um
ID X
10;!.
roO"
01;::::;:
CO)>
I
571
L
ROUTE DATA
I ____......
II 573 57 4 575 576 !
l-.,
1 ..... . .1 .........

.... .1 ... ... l ... .. .
; STOP 001 10T,05CISC:&l.1212121 ; 07:22 1·: 07:37:22PM
... ....... : ... 1 ...... ..... :: ............ :;:;·::; .. ..
...... .'!l!. .. ...... ..... , ...... '!l!'! ....... I .... .<K!e:-. ... .
:; ... .................................. ! ..... .... H ..... ..•....
STOP
""
I
1BT, 0101010,5515515
STOP
"'
lBT, !l!l09:JS(l, Tl27?2.7
STOP rm 1BT,0006COO. 4994994
STOP
""
1BT, 07i.l7070, 2002002
STOP IX)) 18T, C€«1000, 9338338
STOP rno 181, 1515151,9449449
STOP
"'
1ST, 1414141,
STOP
"'
18T. 1313131, 6464645
STOP
'"
18T, 1212121. 191919!
STOP
'"
tST,1111111,3333383
STOP
"'
tBT. C09XJ9l ffi2662l5
STOP
'"
18T,008COBO, 81113118
STOP
"'
18T, 0070070, !:C05IXJ5
STOP
"'
tar. ooooo:;o, 9119119
STOP
"'
taT, OOSQJ50, 0030030
STOP
""
18T, S55855S
STOP
'"
1BT, 0030Cl:lJ, 1333133
STOP 022 18T, 00200ZJ, 5'144644
06:44
06;12
05:51
12:30
03:58
OtJ3
0720
00:55
07:36
04:50
0520
00:48
"'"'
07:15
05:31
"'""
'
I
II
1:
I ::: II
OB:t3:34!lM
08:19:41:./l.M
08:25:37AM
08:3e:07AM·
·De:42:0SA.M
OB:46:3MM
08:54:061\M
09:01:01AM
09:0B:37AM
09:13:l7Ml
09:18:47AM
092S:3511.M
09:32:081'M
09:39:2J.OM
09:44:54M1
09:52:55"M
09:58:39M!
10:04:2611M
i
I
I
I
STOP
""
18T,0010010,1999199
STOP 02< 1BT, 0009XO, OXI 0090

'
i
10:11:5.'JI'OM
j
10:17:00AM
lr
--
577 578
l-., \....._
I CONFIRMi STOP I
CODE NUMBER I NAME ADDRESS
C 001 ABCOMPANY 18John0oe0rive
. ... .......•.. ?E •......... .............. .......... .•...•....•... ;
C O:.:C : : XYZ COMPANY 999 Snith Street ;
... " ..................... ,1 [" .............. I<E'coNo .......... ".""''',;,;; ............... ..
U "" II STEVE JONES 855 Long Drive
I
U 00,) ' GlOBAL INC. 1000ChaseStreet
.... .... ,,,,,,;, ......... l .......... .......... •
' U 009 :; CLAY INDUSTRY ;
I.T ......... ::; ........ l
1
f .......... ......... ............ ll
U Ol:l C.LBLACK 777LooloclJtDrlve
DRIVER DISPLAY DATA
W 014 I JIM SMITH 1100 Abe Dnva
C 015 l L. WILLIAMS 9922 hightoM;rStreel
! .... .......... ........ J f ....... .......... ................ ,
...........
l w va; jl IDEAL SPORTS 644 Third Streel I
I
' w "" I THE BROWN COMPANY 555 Third Street
W OZ2
1
OUT SIDE SPORTS 1530 Thinj S!reel
I
W 023 j I K. FIELD 200 Pine Drill!! ·r
w ""' I L LANCE PATTERSON "" I
L_ ___________________________________________________________________________ l
FIG.32
("j

rJ.J

'"0
a
(D
=
.....
0

....
$'>
N
0
0
0\
00
::r

....
0
0
....,
"'
0
d
rJ)
;-l
-
-
"' ':....!
-
0\

-um

(j) 0:
01;:::;:
<0)>
!t§ll_xj -i
File Edit Go To Mail Members Window Help
.. r:9 .. . 0 I!J .. ·-···· - -·
Setting Up Responses To Notification Messages
Responses May Help To Verify That Each Recipient
Has Received An Notification Message
581).
I ..-
WOULD YOU LIKE TO SET UP
NOTIFICATION RESPONSES
OR CONFIRMATIONS TO
NOTIFICATION MESSAGES?
r
"'
!llll Start I [""'"""on . ji]
1
II __ II /
FIG. 33
e


"'d
a
""
=
-
0
,.,
,..
.....
.?
N
0
0
a,
00
='
It
...
.....
0
-.
VI
0
d
rJJ
;-l
......
......
"' ':....!
......
0\
1:0
N
-um
m x

(!) 5"
m;:::;:
0}>
I
Notification
Eile Edit .Go To l,'iews _Events Window !:ielp
ReS[)Qn_S§
Please Enter A Response Time For
....
Notification Messages!

·---·--
• Please Enter The Maximum Amount Of Time For

J( Message Recipients to Reply To Notification Messages
60S .,JU A message recipient must reply within this
min. & >e.t.

amount of time after the message was sent.
'
[Pi --

f1
I
ease Enter The Time Before Arrival For A Message

i
Recipient to Reply To A Notification Messa e

'
,f/1 A message rec1pient must reply within this amount
min. & g('"c.
'
606 before the arrival or departure
of a vehicle. Entering zero (0) means a message recipient must

Message -
1 ' Recipient to Reply To A Notification Message
A message recipient must reply within this amount of time
607 before the arrival or departure
of a vehicle. Entering zero (0) means a message recipient
must reply before the vehicle arrives.
I
-
608
Would You Like To View The Available Options When NO
!X
Response/s Within Your Select Time (above) Occur?
,.-/
I
!i.!
['0'1
II !illl Start II
Notification

.

II

FIG. 34
c

r:/1
.


.-;.
l't>
=
.-;.
0
;:..
"'""
$='
N
0
0

CfJ
=-
'"

....
N
0
....,
"'
0
d
CFl
.;--1
1-'
1-'
\C
':..!
1-'
0'1



mcr
0);::::;:

Notification
I File Edit Go To Views Events Window Help
I
Response Set-up __ cl
Please Enter A Prior Stop Number Before The
Arrival, That A User Must Respond To
A Notification Message!

X Please Enter The Number Of Stops Before The Destination

,0
608
A message recipient must reply before the number of stops before arrival is reached.

PI
il
r
I ARRIVALORDEPARTURE?
I ""'"' i Dep'""" I HELP I
i3C
6r09
Would You Like To View The Available Options When NO
•. Response/s Within Your Select Stops (above) Occur?
! •
FIG. 35
1_1 -·
I
I
i
I
i
I

e

rn
"'d

-
('!)
=
-
0
"
,..
.....
.?
N
<:>
<:>
""
00
=- ..,
a

0
-.
U1
<:>
Cj
[JJ
.-.t
.....
.....
"' ':...!
.....
0\
O:i
N
.,m
ID X

CDfr
<n;::<:
"l>
__
I File Edit Go To Views Events Window Help I
·---·· I
Please Enter A Vehicle's Minimum Distance
Away From A Destination, That You Would Like
A Response Back From The Message Recipient!
Please Enter A Distance Away From A Destination That
,.-/ A Response Back From A Notification Message
621 Must Be Received
Would You Like To· See A Vehicle's Location
Distance, Away From A Selected Destination On A Map?
622 II WOULD YOU LIKE THIS II
"-_ !
DISTANCE AS A DEFAULT
FOR ALL RESPONSES?

I .fiE.. II YES II HELP II
"NO" ALLOWS YOU TO SET DIFFERENT PREFFERENCES
FOR EACH CONTACT OR ACTION ON LIST
Notff/cption
FIG. 36


IX
II

...
··-
T
Lj

"(fl
.
"'d
a

=
......
0
"
,..
.....
?
N
Q
Q
""
rJl
=-
a
....
....
0
...,
"'
Q
c::
[JJ
,;-1
1-'
1-'
\0
':...1
1-'
0'1
Cl:i
N
-um
ID X
"'" ro a'
0);:::;.:
"'""
( Notification ____
---------
c;,To Views Events Window
·-
Define A Location/s That You Must Receive
A Response From As Vehicle Arrives or Passes!
rr=======iJ
Street Markers
Offers direct locations that
Notification Message Responses
must be received before arriving or
Departing from these areas, You
may use more than one!

WOULD YOU THIS TO --l
BE THE ARRIVAL OR DEPARTURE FROM
THIS LOCATION?
I I ' I
Arrival j Departure j HELP ! I
//
..
I I
Ir-------------------
e !ill! Stanl _ """"""'"
Save I Cancel I Default I I'"'(
FIG. 37
I 2T5
___ PM
d

\Jl
.
'"C
a

= .-+-
0

....
.?
N
0
0
'"'
""
::r
"'
....
Ul
0
...,
Ul
0
0
fJJ

1-'
1-'
'-C>
':...!
1-'
0\
l;l:j
""
-um
0 X

$ 0'
0);::::;:
.. ,
Notification _ _dc§l\ XI
File Edit Go To Views Events Window Help _,jc;jJI_XI
Define A Circle Perimeter For Receiving
A Response When The Vehicle Arrives or Passes!
/ ' /.
/
j.,g, Circle Perimeter
Perimeter
1
•l
l!ifdil yrid Perimeter/s
0 ,Street Markers
@"] Way Points
? Yehicle Defines
0 _!' rior Stop
Circle Perimeters
Offer you a circular area
around your home or office.
Additionally, you may view
time & distance by placing your
cursur on a street al \h(! edge
of the circle!
...
3n:l Street
....
I Save ] I Cancel I I Default I
1
..,.
1
I r.m St<)rt fP ·- [ :I
FIG. 38

\JJ
.
"d

.....
(!)
=
.....
0
il
.....
?
N
0
0
0\
[J)_
=-
&
....
0\
0
-.
'-"
0
d
en
_;-'1
,.....
,.....
\C

,.....
0'\
t:d
N
-urn
ro x
<a""
!g

Notification
. - - - _::l§lJ _X] _j
File Edit Go To Views Events Window Help
XI i
I
Please Select An Option, When A Response
"
Is Not Received Back From
A Notification Message?
641[
Would You Like To Be Notified?
I
!x
I
r····
64ir
Would You Like The System To Automatically
I
IX
II
Notify Another Person (On Contact List)?
6461!
Would You Like The System To Automatically
lx
't
Contact The Next Person On A Route List?
'

'
IX
Jt Would You Like The System To Notify The Driver?

Would You Like The System To Provide You With
f' Available Options And Allow You To Decide?
iX
ill! :;tarrl
I
I

Notlfkatlon
I
PM l
.. --
FIG. 39

.
!fl
.
'"d

('tl
=
......
0
'"' !"'
.....
p
N
0
0
a,
r/l
::r
a
....
--1
0
-.
"'
0
c
r:n
_;--'1
,_..
....
'-0
':..J
,_..
0\
l:d
N
-um
0 X

CllCf
0);::.:

/
I
I
I
INTERNET SERVICE PROVIDER

-·· ··-·------·
File Edit Go To Views Events Window Help

YOU HAVE RECEIVED NEW MAIL

FROM
I SUBJECT I RECEIVED I
ANS PROVIDER You Have A Delivery- Please Provide The Time You Will Be Available? 8:45am 01131197
L--------
'
lllll Start
ISPSROWSER
(CONNECTED)
Save \
FIG. 40
Delete I
Reply j
r----g:ij:5--
l AM
!
,-
,.
e

IJ1
.
"d
a
!'!>
=
.-+-
0
"
:""
.....

N
0
0
"'
[f)
""
..,

....
QO
0
...,
Ul
0
d
[J)

.....
.....
\0

.....
0\
l:d
N
-om
m x
~ "
ro 6'
m;::;:
--.J)>
A
~
Notification Failure Detection System
701
MEMORY
714
PROCESSOR
NOTIFICATION FAILURE
712
DETECTION SOFTWARE
710
OPERATING SYSTEM
(0/S)
722
LOCAL INTERFACE 718
INPUT/OUTPUT
DEVICE(S) PCD
(1/0) 75
716
1\
v
FIG. 41
Cj

\f)
.
""0
a
(!)
= .....
0
"
,..
,...
?
N
0
0
0\
r:n
.,.
<!>
a
....
""
0
....
"'
0
d
r:n
;-'1
.....
.....
'-0
':..:!
.....
0\
t:d
N
-urn
ID X
~ o r
([I cr
0"1;:::;:
W)>
f
Start
)
\.
lr
Storing information pertaining to timing
associated with a scheduled notification ,
communication.
Determining that the scheduled
notification communication failure has
occurred, based upon the timing
information.
Causing one or more tasks to be
performed based upon the scheduled
notification communication failure.
L-............__ •..
FIG. 42
710
)
2
33
c:j

rJJ

"d
a
(!)
= .....
0
~
'""'

N
0
0
"'
rfl
;:r
1t
Ul
0
0
....,
Ul
0
d
rJ1
;-l
......
......
'-0
':...!
......
0\
l:d
N
US 7,119,716 B2
1
RESPONSE SYSTEMS AND METHODS FOR
NOTIFICATION SYSTEMS FOR MODIFYING
FUTURE NOTIFICATIONS
CLAJM OF PRIORITY
2
Another example involves school children that ride school
buses. The arrival times of school buses at scheduled stops
can be significantly affected by many factors, such as
maintenance problems, rush hour traffic, congested urban!
This application claims the benefit of and priority to the
following provisional applications, all of which are incor-
porated herein in their entirety: Ser. No. 60/473,738, filed
May 28, 2003; Ser. No. 60/473,742, filed May 28, 2003; Ser.
No. 60/473,949, filed May 28, 2003; Ser. No. 60/486,768,
filed Jul. II, 2003; and Ser. No. 60/498,819, filed Aug. 29,
2003.
5 suburban conditions, and adverse weather. As a result,
school children typically wait at bus stops for long periods
of time, oftentimes in adverse weather conditions, on unlit
street comers, or in hazardous conditions near busy or
secluded streets. An advance notification system that would
10 inform the students of the school bus's proximity would be
desirable so that students can avoid having to wait for the
school bus at the bus stop for extended time periods.
Yet another example involves the commercial-overnight
RELATED APPLICATIONS
Tills application is related to the following copending
U.S. utility patent applications that were filed by the same
i11ventor of this application:
(1) "RESPONSE SYSTEMS AND METHODS FOR NOTI-
FICATION SYSTEMS" filed on Jun. 2, 2004 and
assigned Ser. No. 1 0/858,684;
(2) "SECURE NOTIFICATION MESSAGING SYSTEMS
AND METHODS USING AUTHENTICATION INDI-
CIA" filed on Jun. 2, 2005 and assigned Ser. No. 10/858,
732;
(3) "STOP LOCATION DETERMINATION SYSTEMS
AND METHODS BASED UPON USER-DEFINED
TIMING CRITERJA" PILED ON Jun. 2, 2005 and
assigned Ser. No. 10/858,774;
(4) "STOP LIST GENERATION SYSTEMS AND METH-
ODS BASED UPON TRACKED PCD'S AND
RESPONSES FROM NOTIFIED PCD'S"filedon Jun. 2,
2005 and assigned Ser. No. 10/859,343; and
(5) "NOTIFICATION SYSTEMS AND METHODS
ENABLING A RESPONSE TO CAUSE CONNECTION
BETWEEN A NOTIFIED PCD AND A DELIVERY OR
PICKUP REPRESENTATIVE" filed on Jun. 2, 2005 and
assigned Ser. No. 10/858,964.
BACKGROUND OF THE INVENTION
1. Field of the Invention
The present invention genemlly relates to data commuM
nications, information, and messaging systems and, more
particularly, to systems and methods that notify a party of
travel status associated with one or more mobile things
(MTs).
2. Related Art
For at least the purposes of allowing better preparation
and scheduling, for example, with respect to pickllps or
deliveries, it would be desirable to know, with substantial
accuracy, the expected arrival or departure time of a mobile
vehicle or thing (for example but not limited to, a bus,
automobile, truck, train, ship, plane, aircraft, etc.) with
respect to a location.
package industry, wherein packages are delivered or picked
15 up many times on a tight schedule. Customers oftentimes
wait on delivery or pickup of important timeMcritical pack-
ages, not knowing precisely when the delivery or pickup will
occur. A notification system that can inform a customer of
the precise arrival or departure time of a delivery vehicle
20 with respect to a location would be desirable in order to
improve customer service and to allow the customer to
better schedule a delivery or pickup of an item.
Still another example involves the airline indusuy. It is
desirable to notify airline workers, such as those who unload
25 baggage from airplanes, when an airplane is about to land or
has landed. A notification system can be employed to track
the airplane travel status and to send notifications to these
workers, when appropriate.
To date, notification systems have been develOped to
30 address the foregoing needs and some are known in the art.
Mr. M. Kelly Jones, a prolific inventor in this field, obtained
numerous patents that describe examples of such notification
systems, some of which are as follows: U.S. Pat. No.
5,400,020; U.S. Pat. No. 5,444,444; U.S. Pat. No. 5,623,260;
35 U.S. Pat. No. 5,647,010; U.S. Pat. No. 5,648,770; U.S. Pat.
No. 5,657,010; U.S. Pat. No. 5,668,543; and U.S. Pat. No.
5,400,020; U.S. Pat. No. 6,278,936; U.S. Pat. No. 6,317,060;
U.S. Pat. No. 6,363,323; U.S. Pat. No. 6,363,254; U.S. Pat.
No. 6,411,891; U.S. Pat. No. 6,415,207; U.S. Pat. No.
40 6,492,912; U.S. Pat No. 6,510,383; and U.S. Pat. No.
6,618,668.
A nonexhaustive list of other examples of notification
systems is as follows: U.S. Pat. No. 6,006,159 (for a public
bus transit system); U.S. Pat. No. 6,374,176 (for a public bus
45 transit system); application Ser. No. 09/163,535, filed on
Sep. 30, 1998; U.S. Pat. No. 5,602,739 (for a public transit
system); U.S. Pat. No. 5,736,940 (tracking system for buses;
notice of impending arrival is described); U.S. Pat. No.
5,808,565 (GPS triggered automatic enunciator for public
50 transportation vel::ricles that notifies of a stop based upon the
location of the vehicle); U.S. Pat. No. 5,955,974 (apparatus
carried by a user to notify of arrival so user does not miss
stop); U.S. Pat. No. 5,987,377 (dispatch system that deter-
mines expected time of arrival and indicates to dispatcher
55 when a vehicle will be late); U.S. Pat. No. 6,124,810
(vehicle apparatus determines when vehicle has arrived or
departed from a planned or unplanned stop and communiM
cates such information to a central facility); U.S. Pat. No.
6,137,425 (waiting time prediction system for a public
60 transit system); U.S. Pat. No. 6,178,378 (a vehicle naviga·
tion system where a start call, such as by telephone, is
made); and U.S. Pat. No. 6,184,802 (system for informing
users when a next vehicle will arrive at their boarding site).
For example, consider a commercial bus service. A person
intending to catch a bus or intending to pick up a friend or
relative at the commercial bus station usually calls the bus
station to find out the approximate arrival time (infonnation
which is oftentimes unavailable or unreliable) and/or arrives
at the bus station prior to the scheduled arrival or departure
time of the bus, hoping that the bus is not significantly
delayed. With knowledge of accurate arrival or departure
information, adjustments can be made to one's schedule to
avoid having to wait extended periods for a vehicle.
Furthermore, a nonexhaustive list of examples of tracking
65 systems is as follows: U.S. Pat. No. 5,014,206; U.S. Pat. No.
5,113,185; U.S. Pat. No. 5,155,689; U.S. Pat. No. 5,168,45I
(transit system for dispatching vehicles); U.S. Pat. No.
Exhibit A
Page 69
US 7,119,716 B2
3
5,223,844; U.S. Pat. No. 5,243,529 (in-vehicle navigation
apparatus with map display); U.S. Pat. No. 5,299,132; U.S.
Pat. No. 5,394,332 (on-board navigation system); U.S. Pat.
No. 5,398,190; U.S. Pat No. 5,432,841 (system for locating
and conununicating with mobile vehicles); U.S. Pat. No.
5,448,479; U.S. Pat. No. 5,483,454; U.S. Pat. No. 5,519,621;
U.S. Pat. No. 5,587,715 (describes a satellite based tracking
system); U.S. Pat. No. 5,594,650 (describes a tracking
system with map display capabilities); U.S. Pat. No. 5,652,
707; U.S. Pat. No. 5,724,243 (on board vehicle system
tracks location and expected time of arrival); U.S. Pat. No.
5,739,774 (mass transit monitoring system); U.S. Pat. No.
5,760,742 (integrated mobile GIS/GPS/AVL with wireless
messaging); U.S. Pat. No. 5,796,365 (uses satellites, vehicle
tracking units, and a central computer); U.S. Pat. No.
5,922,040 (vehicle positioning data is exchanged between
vehicles and a central processor having a map display); U.S.
Pat. No. 5,945,919 (dispatch system tracks vehicles); U.S.
Pat. No. 6,191,708 (vehicle location tracking without satel-
lites); U.S. Pat. No. 6,253,148 (tracks buses and communi-
cates waiting times to radio receivers); and U.S. Pat. No.
6,360,101 (cellular phone that displays or sends messages
upon its arrival at a predetem1ined location).
Another tracking system that has been known in the art is
the FlightView airline tracking system developed by RLM
Software, Inc., which monitors the progress of an airplane
and displays its location on a map on a user's computer
screen. RLM receives real-time flight data (for example,
position and speed) for each flight over North America. This
data comes from transponders located on aircraft. The FAA
co11ects the transponder data, adds radar and other informa-
tion, and supplies it to RLM. This data feed is known in the
aviation industry as "ASDI," which stands for Aircraft
Situation Display for Industry and has been made available
by the FAA since 1996. RLM processes this data and stores
it in the FlightView data base. A user can then request the
status of any commercial flight from the FlightView system
(by providing the airline and flight number), which sends to
the user's computer screen a map showing the current
position, route, and expected arrival time of the flight.
Sabre, Inc., provides similar map functionality at its
Yrrtually There web site using a system that is apparently
based upon the Flight View system.
4
steps. One such representative response system of the invenw
tion, among others, would comprise a comp11ter system
programmed to perform the foregoing steps.
A.nother such representative response method of the
s invention, among others, can be summarized by the followw
ing steps: receiving a notification communication with a
personal communications device associated with the party
from the notification system; communicating a response
communication from the party's personal communications
10 device, indicating that the party has received the notification
communication and is now occupied with a task associated
with the notification communication; and causing the noti-
fication system to refrain from sending any further notifi-
cation communications to the party's personal communica·
15 tions device, until detection of one or more events,
indicating that the party is no longer occupied with the task
and can perfonn another task as..<;ociated with another noti-
fication communication. Another such representative
response system of the invention, among others, would have
20 a computer system programmed to perform the foregoing
steps.
Yet another such representative response method of the
invention, among others, can be summarized by the follow-
ing steps; scheduling an arrival or departure time for a
25 mobile thing in relation to a stop location; scheduling a
notification communication to a personal communications
device; monitoring travel data pertaining to the mobile
thing; determining that the mobile thing will be delayed in
arriving or departing from the stop location; initiating a
30 communication session with a communications device; and
during the communication session, reporting a travel status
of the mobile thing indicating that the mobile thing will be
delayed and enabling cancellation of the scheduled notifi-
cation communication. Yet another such representative
35 response system of the invention, among others, would have
a computer system prognunmed to perfonn the foregoing
steps.
Other systems, methods, features, and advantages of the
present invention will become apparent from the accompa·
40 nying Drawings and following Detailed Description section.
BRJEF DESCRJPTION OF THE DRAWINGS
As can be seen from the aforementioned prior art, the
systems that give notice concerning the status of moving 45
things are still evolving and, in some sense, the art is still in
The invention can be better understood with reference to
the following drawings. The elements of the drawings are
not necessarily to scale relative to each other, emphasis
instead being placed upon clearly illustrating the principles
of the invention. Furthermore, like reference numerals des·
ignate corresponding parts throughout the several views.
a state of infancy. Accordingly, l write and submit this
application and invention for the public good to educate and
further advance the technology associated with such sysw
terns.
SUMMARY OF THE INVENTION
50
FIG. 1 is a block diagram il1ustrating an exemplary
implementation of an automated notification system, which
in this case, is a computer-based system.
Briefly described, the present invention provides response
systems and methods for communications in connection
with a computer·based notification system and a personal
communications device (e.g., telephone, pager, PDA, etc.)
associated with a party.
FlG. 2 is a block diagram illustrating an exemplary
implementation of a computer system implementing the
55 functionality of the mobile thing manager of FIG. 1.
One such representative response method of the invenw
rion, among others, can be summarized by the following 60
steps: initiating a notification communication to a personal
communications device associated with a party; receiving a
response commWlication from the party's personal commn·
nications device; and modifying a manner in which future
notification communications are implemented, based upon 65
the response. A representative response system, among
others, has mechanisms for implementing the foregoing
FIG. 3 is a block diagram illustrating an exemplary
implementation of a computer system implementing the
functionality of the base station manager (BS manager) of
FJG.l.
FIG. 4A is a flow chart illustrating an exemplary imple-
mentation of at least part of the architecture, functionality,
and operation of the mobile thing manager of FIG. 1 that
creates the mobile thing schedule.
FIG. 4B is a flow chart illustrating an exemplary imple-
mentation of at least part of the architecture, functionality,
and operation of the mobile thing manager of FIG. 1 that
tracks the mobile thing.
Exhibit A
Page 70
US 7,119,716 B2
5
FIG. SA is a functional block diagram illustrating an
exemplary implementation of at -]east part of the architec·
ture, functionality, and operation of the BS manager of FIG.
1.
6
FIG. 5B is a functional block diagram illustrating an 5
exemplary implementation of at least part of the architec·
ture, functionality, and operation of the data manager asso-
ciated with the BS manager of FIG. SA.
FIG. 10 is a flow chart illustrating an exemplary imple·
mentation of the response system feedback mechanism,
which is optionally implemented as at least a part of the
architecture, functionality, and operation of the personal
communications device (PCD) of FIG. 1, and which inter-
acts with the response system feedback analyzer of any of
FIGS. 7 through 9C.
FIG. 11 is a flow chart illustrating an exemplary imple·
mentation of an advertisement method of doing business that
can be optionally implemented in com1ection with any
notification system.
FIG. SC is a flow chart illustrating an exemplary imple-
mentation of at least part of the architecture, functionality, 10
and operation oftbe monitoring mechanism associated with
the BS manager of FIGS. SA and SB.
FIG. 12 is a flow chart illustrating an exemplary imple·
mentation of another advertisement method of doing busi·
ness that can be optionally implemented in connection with
any notification system.
FIG. SD is a flow chart illustrating an exemplary imple-
mentation of at least part of the architecrure, functionality,
and operation of the message manager associated with the 15
BS manager of FIGS. SA and 58.
FIG. 13 is a flow chart illustrating an exemplary i m p l e ~
mentation of yet another advertisement method of doing
business that can be optionally implemented in connection
FIG. 6 is a block diagram illustrating an exemplary
implementation of the response system of FIG. 1, which has
the response system feedback mechanism and the response
system feedback analyzer.
with any notification system.
20
FIG. 7A is a flow chart illustrating an exemplary imple·
mentation of a response system feedback analyzer, which is
optionally implemented as at least part of the architecture,
functionality, and operation of the BS manager of FIGS. 1
and 3.
FIG. 7B is a flow chart illustrating another exemplary
implementation of a response system feedback analyzer,
which is optionally implemented as at least part of the
architecture, functionality, and operation of the BS manager
FIG. 14A is a flow chart illustrating an exemplary imple·
mentation of a first stop location determination system (and
method; system and method are based upon feedback
regarding the location of the PCD and/or user) that can be
optionally implemented in connection with any notification
25
system, for example, as at least part of the architecture,
functionality, and operation of the BS manager of FIGS. 1
and 3.
of FIGS. 1 and 3. A response from a notified party causes a 30
telecommunications connection to be made between the
notified party and a party associated with a tracked MT that
will make a pickup or delivery at a stop location.
FIG. 7C is a flow chart illustrating yet another exemplary
implementation of a response system feedback analyzer, 35
which is optionally implemented as at least part of the
architecture, functionality, and operation of the BS manager
of FIGS. 1 and 3. A response from a notified party is used
to change one or more tasks associated with a pickup or
delivery of an item or service associated with a stop location. 4D
FTG. 7D is a flow chart illustrating still another exemplary
implementation of a response system feedback analyzer,
which is optionally implemented as at least part of the
architecture, functionality, and operation of the BS manager
of FIGS. 1 and 3. A response from a notified party is used 45
to select one of a plurality of times for a pickup or delivery
of an item or service associated with a stop location.
FIG. 8 is a flow chart illustrating another exemplary
implementation of a response system feedback analyzer of
the present invention, which is optionally implemented as at so
least part of the architecture, functionality, and operation of
the BS manager of FIGS. 1 and 3.
FIG. 9A is a flow chart illustrating an exemplary imple·
mentation of the modify step in the response system feed·
back analyzer of FIG. 8, which is optionally implemented as 55
at least part of the architecture, functionality, and operation
of the BS manager of FIGS. 1 and 3.
FIG. 9B is a flow chart illustrating another exemplary
implementation of the modify step in the response system
feedback analyzer of FIG. 8, which is optionally impJe. 60
men ted as at least part of the architecture, functionality, and
operation of the BS manager of FIGS. 1 and 3.
FIG. 9C is a flow chart illustrating yet another exemplary
implementation of the modify step in the response system
feedback analyzer of FIG. 8, which is optionally imple· 65
mented as at least part of the architecture, fWlCtionality, and
operation of the BS manager of FIGS. 1 and 3.
FTG.14B is a flow chart illustrating an exemplary impleD
mentation of a second stop location determination system
(and method; system and method are based upon feedback
regarding the location of the PCD and/or user) that can be
optionally implemented in connection with any notification
system, for example, as at least part of the architecture,
functionality, and operation of the BS manager of FIGS. 1
and 3.
FTG. 15A is a flow chart illustrating an exemplary imple·
mentation of a third stop location determination system (and
method; system and method are based upon timing criteria)
that can be optionally implemented in connection with any
notification system, for example, as at least part of the
architecture, functionality, and operation of the BS manager
ofFJGS. 1 and 3.
FIG. 15B is a flow chart illustrating an exemplary imple·
mentation of a fourth stop location determination system
(and method; system and method are based upon timing
criteria) that can be optionalJy implemented in connection
with any notification system, for example, as at least part of
the architecture, ii.mc:tionality, and operation of the BS
manager of FIGS. 1 and 3.
FTG. 16 is a flow chart illustrating an exempla"ry impleD
mentation of a secure notification messaging system (and
method) that can be optionally implemented in connection
with any notification system, for example, as at least part of
the architecture, functionality, and operation of the BS
manager of FIGS. 1 and 3.
FIG. 16A shows a possible screen message that can be
shown on a notified PCD during a notification communica·
tion for authentication purposes.
FIG. 17 A is a flow chart illustrating an exemplary imple·
mentation of a first mobile thlng determination system (and
method; system and method are based upon pickup and
dropoff locations that are communicated to the notification
system) that can be optionally implemented in connection
with any notification system, for example, as at least part of
the architecture, functionality, and operation of the BS
manager of FIGS. 1 and 3.
Exhibit A
Page 71
US 7,119,716 B2
7
FIG. 178 is a flow chart illustrating an exemplary imple-
mentation of a second mobile thing determination system
(and method system and method are based upon pickup and
dropo:II locations that are communicated to the notification
system) that can be optionally implemented in connection 5
'vith any notification system, for example .• as at least part of
the architecture, functionality, and operation of the BS
manager of FIGS. 1 and 3.
8
FIG. 20C is a flow chart illustrating an exemplary imple-
mentation of a third system (and method) for monitoring
travel of MTs that are PCDs and communicating notifica-
tions and responses among the PCDs. Tills system can be
optionally implemented in connection with any notification
system, for example, as at least part of the architecture,
functionality, and operation of the BS manager of FIGS. 1
and 3.
FIG. 21 is an illustration of an exemplary system with
various PCDs being tracked, communicating notifications to
other PCDs, and receiving responses from the other PCDs,
all by way of a base station control unit.
f'IG. 22 is an illustration of an exemplary system with a
PCD in the form of a first IlllVigation system (a) tracking its
FIG. 17C is a flow chart illustrating an exemplary imple-
mentation of a third mobile thing determination system (and 10
method; sys-tem and method are based upon the detected
location of the PCD and/or user) that can be optionally
implemented in connection with any notification system, for
example, as at least part of the architecture, functionality,
and operation of the BS manager of FIGS. 1 and 3.
FIG.17D is a flow chart illustrating an exemplary imple·
mentation of a fourth mobile thing determination system
(and method; system and method are based upon the
detected location of the PCD and/or user) that can be
optionally implemented in connection with any notification 20
system, for example, as at least part of the architecture,
functionality, and operation of the BS manager of FIGS. 1
and 3.
15 location, (b) communicating a notification to another PCD in
the form of a second navigation system, and (c) receiving a
response from the second navigation system, either indi-
rectly by way of a base station control unit or directly from
FIG. 18 is a flow chart illustrating an exemplary imple-
mentation of a combined mobile-thing-to-location (MTTL) 25
and device-to-location (DTL) notification system (and
method) that can be optionally implemented in connection
with any notification system, for example, as at least part of
the architecture: functionality, and operation of the BS
manager of FIGS. 1 and 3. 30
FIG. 19A is a flow chart illustrating an exemplary imple-
mentation of a first system (and method) for making more
accurate notifications by considering traffic flow predica-
ment data. 1bis system can be optionally implemented in
connection with any notification system, for example, as at 35
least part of the architecture, functionality, and operation of
the BS manager of FIGS. 1 and 3.
FIG.19B is a flow chart illustrating an exemplary imple-
mentation of a second system (and method) for making more
accurate notifications by considering traffic flow predica- 4D
ment data. Thi!> system can be optionally implemented in
connection with any notification system, for example, as at
least part of the architecture, functionality, and operation of
the BS manager of FIGS. 1 and 3.
FIG.19C is a flow cbart illustrating an exemplary imple· 45
mentation of a third system (and method) for making more
accurate notifications by considering traffic flow predica-
ment data. Tills system can be optionally implemented in
connection with any notification system, for example, as at
least part of the architecture, functionality, and operation of 50
the BS manager of FIGS. 1 and 3.
FIG. 20A is a flow chart illustrating an exemplary imp lea
mentation of a first system (and method) for monitoring
travel of MTs that are PCDs and communicating notifica-
tions and responses among the. PCDs. This system can be 55
optionally implemented in connection with any notification
system, for example, as at least part of the architecture,
functionality, and operation of the BS manager of FIGS. 1
and 3.
navigation system to navigation system.
FIG. 23 is an illustration of a possible architecture for
implementing the direct commlllications configuration
between a tracked PCD in the form of an in-vehicle navic
gation system and one or more other PCDs.
FIG. 24 is a continuation of the example in FIG. 23 and
shows implementation of response requests and failure
states.
FIGS. 25A through 25D illustrate examples of possible
failure states the can be shown on the screen of the tracked
PCD.
FIG. 26 is an illustration of an embodiment of a stop list
generation system that may be used in connection with a
delivery vehicle. A stop list is compiled based upon whether
or not a stop requires a response and whether or not a
response has been received from such stops that require one.
FIG. 27 is an illustration of an embodiment of a stop list
generation system that may be used in connection with a
delivery vehicle. A notified party is given a predetermined
time period to respond until a failure state is reached. The
existence of failure states (No Responses) and confirmations
are communicated to the PCD associated with the delivery
vehicle.
FIG. 28 is an illustration of an embodiment of a ~ i n p list
generation system that may be used in connection with a
delivery vehicle. A delivery vehicle driver can select or
otherwise indicate which of the confirmed notified parties
will be visited by the delivery vehicle.
FIG. 29 is an illustration of an embodiment of a stop list
generation system that may be used in connection with a
delivery vehicle. TI1e PCD associated with the delivery
vehicle and driver communicates with the BSCU in order to
determine whether or not a response pertaining to a stop has
been received.
FIG. 30 is an 111ustration of an embodiment that can be
implemented at the BSCU or MTCU showing implementa-
tion of failure states in connection with responses and
nonresponses to notification communications in the context
of a delivery vehicle.
FIG. 31 is an illustration of another embodiment that can
60 be implemented at the BSCU or MTCU showing implemen-
tation of failure states in connection with responses and
nonresponses to notification communications in the context
of a deUvery vehicle.
FIG. 20B is a flow chart illustrating an exemplary imple·
mentation of a second system (and method) for monitoring
travel of MTs that are PCDs and communicating notifica-
tions and responses among the PCDs. This system can be
optionally implemented in connection with any notification
system, for example, as at least part of the architecture, 65
functionality, and operation of the BS manager of FIGS. 1
and 3.
FIG. 32 is an illustration of an embodiment of route data
and corresponding driver display data that can be maintained
and implemented in connection with a delivery or pickup
service.
Exhibit A
Page 72
US 7,119,716 B2
9
10
FIG. 33 shows an example of a possible user interl'ace
screen that can be generated by the GUI of FIG. 3 and used
in connection with the response systems (and methods).
bus transit system); U.S. Pat. No. 6,374,176 (for a public bus
transit system); application Ser. No. 09/163,535, filed on
Sep. 30, 1998; U.S. Pat. No. 5,602,739 (for a public transit
FIG. 34 shows an example of a possible user interface
screen that can be generated by the GUI of FJG. 3 and used s
in connection with the response systems (and methods).
system); U.S. Pat. No. 5,736,940 (tracking system for buses;
notice of impending arrival is described); U.S. Pat. No.
5,808,565 (GPS triggered automatic enunciator for public
FIG. 35 shows an example of a possible user interface
screen that can be generated by the GUI of FIG. 3 and used
in connection with the response systems (and methods).
transportation vehicles that notifies of a stop based upon the
location of the vehicle); U.S. Pat. No. 5,955,974 (apparatus
carried by a user to notify of arrival so user does not miss
FIG. 36 shows an example of a possible user interface
screen that can be generaled by the GUI of FIG. 3 and used
in connection with the response systems (and methods).
10 stop); U.S. Pat. No. 5,987,377 (dispatch system that deter-
mines expected tlme of arrival and indicates to dispatcher
when a vehicle will be late); U.S. Pat. No. 6,124,810
(vehicle apparatus determines when vehicle has arrived or
departed from a planned or unplanned stop and communi-
FIG. 37 shows an example of a possible user interlace
screen that can be generated by the GUI of FIG. 3 and used
in connection with the response systems (and methods).
FIG. 38 shows an example of a possible user interface
screen that can be generated by the GUI of FIG. 3 and used
in connection with the response systems (and methods).
FIG. 39 shows an example of a possible user interface
screen that can be generated by the GUI of FIG. 3 and used
in connection with the response systems (and methods).
15 cates such information to a central facility); U.S. Pat. No.
6,137,425 (waiting time prediction system for a public
transit system); U.S. Pat. No. 6,178,378 (a vehicle naviga-
tion system where a start call, such as by telephone, is
made); and U.S. Pat. No. 6,184,802 (system for informing
20 users when a next vehicle will arrive at their boarding site).
FIG. 40 shows an example of an email that can be·
generated and sent by the BSCU 40 of FIG. 3 and used in
connection with the response systems (and methods).
All of the aforementioned patents or applications are incor-
porated herein by reference in their entirety. The inventions
that are claimed in this document can be implemented and
practiced in the systems described in the foregoing patents.
Furthermore, a nonexhaustive list of examples of, what
FIG. 41 is a block diagram illustrating an exemplary
25
implementation of a notification failure
detection system implemented in cmmection with a notified
PCD.
appear to be tracking systems, are as follows: U.S. Pat. No.
5,014,206; U.S. Pat. No. 5,113,185; U.S. Pat. No. 5,155,689;
U.S. Pat. No. 5,168,451 (transit system for dispatching
vehicles); U.S. Pat. No. 5,223,844; U.S. Pat. No. 5,243,529
FIG. 42 is a flow chart illustrating an exemplary imple-
mentation of notification failure detection software of FIG.
41.
DETAILED DESCRJPTJON
A. Notification System
The systems and methods of this patent application can be
implemented in connection with any type of notification
service or system, messaging system, information system,
data communications system, or tracking system, that noti-
fies a party of travel status associated with one or more
moving things {all referred to herein as "notification sys-
tem"). The notification system may or may not have a
tracking subsystem that actually directly or indirectly tracks
the mobile things (MIS), but has access to information or
data, perhaps from a tracking system(s) or data source, that
can be used by it to monitor travel of the :MTs. There are a
number of such notification, messaging, and tracking sys-
tems that are known in the art.
As mentioned in the Background, Mr. Martin Kelly Jones
has been an active pioneering inventor in this area and has
filed applications for patent 011 various notification systems,
a few of which, are as follows: U.S. Pat. No. 5,400,020; U.S.
Pat. No. 5,444,444; U.S. Pat. No. 5,623,260; U.S. Pat. No.
5,647,010; U.S. Pat. No. 5,648,770; U.S. Pat. No. 5,657,010;
U.S. Pat. No. 5,668,543; and U.S. Pat. No. 5,400,020; U.S.
Pat. No. 6,278,936; U.S. Pat. No. 6,31 7,060; U.S. Pat. No.
6,363,323; U.S. Pat. No. 6,363,254; U.S. Pat. No. 6,411,891;
U.S. Pat. No. 6,415,207; U.S. Pat. No. 6,492,912; U.S. Pat.
No. 6,510,383; and U.S. Pat. No. 6,618,668. All of the
foregoing patents are incorporated herein by reference in
their entirety. 'Ibe inventions that are claimed near the end
of this document can be implemented and practiced in the
systems described in the foregoing patents, as will be clear
from the discussion that follows.
A nonexhaustive list of other examples of notification
systems is as follows: U.S. Pat. No. 6,006,159 (for a public
30 (in-vehicle navigation apparatus with map display); U.S.
Pat. No. 5,299,132; U.S. Pat. No. 5,394,332 (on-board
navigation system); U.S. Pat. No. 5,398,190; U.S. Pat. No.
5,432,841 (system for locating and communicating with
mobile vehicles); U.S. Pat. No. 5,448,479; U.S. Pat. No.
35 5,483,454; U.S. Pat. No. 5,519,621; U.S. Pat. No. 5,587,715
(describes a satellite based tracking system); U.S. Pat No.
5,594,650 (describes a tracking system with map display
capabilities); U.S. Pat. No. 5,652,707; U.S. Pat. No. 5,724,
243 (on board vehicle system tracks location and expected
40 time of arrival); U.S. Pat. No. 5,739,774 (mass transit
monitoring system); U.S. Pat. No. 5,760,742 (integrated
mobile GIS/GPS/AVL with wireless messaging); U.S. Pat.
No. 5,796,365 (uses satellites, vehicle tracking units, and a
central computer); U.S. Pat. No. 5,922,040 (vehicle posi-
45 tioning data is exchanged between vehicles and a central
processor having a map display); U.S. Pat. No. 5,945,919
(dispatch system tracks vehicles); U.S. Pat. No. 6,191,708
(vehicle location tracking without satellites); U.S. Pat. No.
6,253,148 (tracks buses and communicates waiting times to
so radio receivers); and U.S. Pat. No. 6,360,101 (cellular phone
that displays or sends messages upon its arrival at a prede-
termined location). All of these mentioned patents or appli-
cations are incorporated herein by reference in their entirety.
The inventions that are claimed in this document can be
55 implemented and practiced in the systems described in these
mentioned patents.
The claimed systems (and methods) of the invention can
be implemented in many other known notification systems,
messaging systems, or tracking systems, that notifY a party
60 of travel status associated with one or more moving things
and that are not specifically referenced, shown, or described
in this document for reasons of simplicity.
As a nonlimiting example, FIG. 1 depicts a notification
system 10 illustrating a possible context, among others, in
65 which the invention may be implemented. As shown by FIG.
1, the notification system 10 has a tracking aspect and a
notification aspect.
Exhibit A
Page 73
US 7,119,716 B2
11
As depicted in FIG. 1, an MT control unit (MTCU) 15 is
disposed on an MT 17, which is capable of transporting the
MTCU 15 over various distances. For example, MT 17 can
be any movable object or thing, including but not limited to,
a motor vehicle, such as an automobile, motorcycle, truck,
bus, limousine, or taxicab, a bicycle, an aircraft such as an
airplane, helicopter, balloon, or rocket, a train, a water
vehicle such as a cruise ship, cargo ship, or other boat/ship,
a package, a human being, an animal, an electronic email or
transmission, an amusement park vehicle, or any other thing
capable of being moved across or through the Earth's
surface and/or atmosphere.
The notification service can be implemented in connec-
tion with any vehicle 17 for delivering items to a destination
or for picking up items at a destination. Items can include
any of many various types of packages or goods to be
delivered or picked up, for example but not limited to, mail,
pizza, beverages, shipping vessels, containers, produce, etc.
Furthermore, items can also include persons to be picked up
12
signals 21 received from GPS satellites 23 in order to
determine the sensor's location values. Since the sensor 18
is located within MTCU 15, the location values determined
by the sensor 18 are assumed to match the location values of
the MT 17 and the MTCU 15.
A location value can be any value or set of values that may
be used to detennine a location of a point on the Earth or
within the Earth's atmosphere. This value may be a coor-
dinate value (i.e., grid value), polar value, vector value,
10 time-distance value, or any other type of value or values
known in the art for indicating locations of points.
In alternative embodiments, the positioning system 23
may determine MT location infonnation and merely trans-
mit the position information to the MT 17. For example,
15 radar could be used to remotely track the Mf 17 and then the
radar system could be designed to convey MT position
information to the MT 17 (and/or the base station control
unit (BSCU) 40, which will be described in detail herein-
after).
In alternative embodiments, the positioning system 23
may be the Federal Aviation Administration (FAA), which
collects transponder data from airplanes, adds radar and
other infonnation, and makes the resultant data available for
tracking purposes. This data feed is known in the aviation
or delivered, such as when a bus picks up and/or delivers 20
passengers at different bus stops or such as when an airplane
picks up and/or delivers passengers at airports. Although not
necessary for implementation, the MT 17 can travel along a
predetermined route or modifiable route in making its deliv-
eries, and the MT 17 may make one or more stops along its
route in order to deliver or pick up different items at different
locations.
25 industry as "ASDI," which stands for Aircraft Situation
Display for Industry. Th.is data feed can be accessed by the
BSCU 40 (and/or the MTCU 15).
The notification service can also be implemented in
cormection with any services to be delivered, or perfonned
at or near, a destination. The notification service can be
implemented in connection with the following nonlimiting
list of examples: maid service, pest control, telephone repair
or installation, television repair, cable repair or installation,
garbage pickup, yard maintenance, pool maintenance, power
meter maintenance/reading, etc.
In alternative embodiments, the positioning system 23
may be asE>ociated with a computer system server commu-
30 nicatively coupled to the Internet that makes location infor-
mation pertaining to the Mf 17 available to the BSCU 40
and/or to the MTCU 15 over the Internet. In such embodi-
ments, it is also possible for the BSCU 40 to communicate
the server's uniform resource locator (URL) to the notified
35 PCD 75, which can be equipped with a web browser, so that
location information pertaining to the tracked Mf 17 (as
B. Mobile Thlng Control Unit (MTCU) well as the PCD 75) can be accessed by the notified PCD 75
In the preferred embodiment, a sensor 18 within MTCU from the server.
15 is configured to sense signals to help determine and/or In alternative embodiments, the positioning system 23
determine the location of the sensor 18 relative to a prede- 40 may be a tracking system that tracks a vehicle's progress
termined reference point. Tn the preferred embodiment, along a predetennined route based upon its arrival at and/or
sensor 18 is a global positioning system (GPS) sensor(s), departure from stops along the route.
although other types of positioning systems (having corn- Referring back to FIG.1, sensor 18 is designed to transmit
ponents that are local to and/or remote from the MTCU 15) a signal 27 to MT manager 29 indicating the MT's current
and/or sensors are also possible. For example, other types of 45 location values. MT manager 29 is configured to receive
positioning systems that may be used include, but are not signal27 and to monitor the location of the MT 17 overtime
limited to, GLONASS, LORAN, Shoran, Decca, TACAN, by processing multiple signals 27. The MI manager 29 can
radar, traffic system monitoring, a system for monitoring be implemented in software, hardware, or a combination
vehicle stops along a route, or any other of numerous thereof. In the preferred embodiment, as illustrated by way
possible tracking systems or combinations thereof It is also so of example in FIG. 2, the MT manager 29 along with its
possible to indirectly monitor the location of the MT 17 by associated methodology is implemented in software and
monitoring or tracking pickup or delivery of people, prod- stored in computer memory 30a of a computer system 31a.
ucts, packages, or things that are transported by the Mf 17. Note that the MT manager 29 can be stored and trans-
The GPS sensor 18 of the preferred embodiment is config- ported on any computer-readable medium for use by or in
ured to receive signals 21 from a plurality of GPS satellites 55 e,;onnection with an instruction execution system, apparatus,
23, and as known in the art, sensor 18 is designed to analyze or device, such as a computer-based system, processor-
signals 21 in order to determine the sensor's location or containing system, or other system that can fetch the
coordinate values relative to a predetermined reference tions from the instruction execution system, apparatus, or
point. For example, in the preferred embodiment where device and execute the instructions. In the context of this
sensor 18 is a GPS sensor, the sensor 18 determines the 60 document, a "computer-readable medium" can be any
sensor's location values relative to the Earth's zero degree means that can contain, store, communicate, propagate, or
latitude and zero degree longitude reference point, which is transport the program for use by or in connection with the
located at the intersection of the Equator and the Prime instruction execution system, apparatus, or device. The
Meridian. U.S. Pat. No. 5,7R1,156 entitled, "GPS Receiver computer readable medium can be, for example but not
and Method for Processing GPS Signals" and filed on Apr. 65 limited to, an electronic, magnetic, optical, electromagnetic,
23, 1997 by Krasner, which is incorporated herein by infrared, or semiconductor system, apparatus, device, or
reference, discusses a sensor for the processing of GPS propagation medium. More specific examples (a nonexhaus-
Exhibit A
Page 74
US 7,119,716 B2
13 14
tive list) of the computer-readable medium wm1ld include time value ofthe clock 38a versus the stored time value for
the following: an electrical connection (electronic) having the start of the route. Alternatively, the clock 38a can be
one or more wires, a portable computer diskette (magne1ic), designed as a counter that begins timing or counting in
a random access memory (RAM) (magnetic), a read-only response to a start signal transmitted by the MT manager 29.
memory (ROM) (magnetic), an erasable programmable Therefore, the MT manager 29 transmits the start signal
read-only memory (EPROM or Flash memory) (magnetic), when the Mf 17 starts the route, and thereafter, the MT
an optical fiber (optical), and a portable compact disc manager 29 can determine the amount of time that has
memory (CDROM) (optical). Note that the lapsed since the start of the route by analyzing the value of
puter-readable medium could even be paper or another the clock 38a. Other devices and/or methodologies may be
suitable medium upon which the program is printed, as the 10 employed to determine the amount of time that has lapsed
program can be electronically captured, via for instance since the start of the route.
optical scanning of the paper or other medium, then com- As the MT 17 travels along the predetcnnincd route of
piled, interpreted or otherwise processed in a suitable man- travel, the MT manager 29 is configured to determine the
ncr if necessary, and then stored in a computer memory. As MT' s current position by analyzing the location values from
an example, the MT manager 29 may be magnetically stored 15 the sensor 18. Furthermore, as the MT 17 travels, the MT 17
and transported on a conventional portable computer dis- passes the points or locations along the route that are defined
kette. in the MT schedule 39a. The MT manager 29 is designed to
An exemplary embodiment of the computer system 31a of compare the current location values of the MT 17 (i.e., of the
FIG. 2 comprises one or more conventional processing sensor 18) with the location values defined by the MT
elements 32a, such as microprocessors, digital signal 20 schedule 39a in order to determine which entry in the MT
cessors (DSPs), or other suitable processing means, that schedule 39a corresponds with the current location of the
communicate to and drive the other elements within the MT 17. In the preferred embodiment, the entry that
system 31a via a local interface 33a, which can include one sponds with the e1ment location of the MT 17 is the entry
or more buses. Furthennore, an input device(s) 34a, for having location vah1es most closely matching the location
example, a keyboard, mouse, or trackbal1, can be used to 25 values currently supplied by the sensor 18. In other words,
input data from a user of the system 31a, and screen the corresponding entry includes location values represent-
display(s) 35a or a printer(s) 36a can be used to output data ing the location that is closest to the location of the MT 17.
to the user. A nonvolatile disk storage mechanism 37a can be This entry will be referred to hereinafter as the "correspond-
connected to the local interface 33a to transfer data to and ing entry."
from a nonvolatile disk (e.g., magnetic, optical, etc.). It 30 After detennining which entry corresponds with the cur-
should be noted that input device 34a, display 35a, printer rent location of the MT 17, the MT manager 29 is designed
36a, and disk storage mechanism 37a are optional and are to determine whether the MT 17 is off schedule or on
not a part of the preferred embodiment, although other schedule. The MT 17 is off schedule if the amount of time
embodiments may include these features. that bas lapsed since the start of the route differs from an
TI1c MT manager 29 is preferably configured to maintain 35 estimated lapsed time by a predetennined amount oftime. In
a predefined MT schedule 39a within memory 30a. The the preferred embodiment, the estimated lapsed time is
predefined MT schedule 39a corresponds with a route of represented by the time value in the corresponding entry of
travel for the MT 17. In this regard, the predefined MT the MT schedule 39a. As an example, assume for illustrative
schedule 39a stored in memory 30a includes data defining purposes only that the predetermined amonnt of time is five
locations along the MT's intended route of travel. Further- 40 minutes. If the MT manager 29 determines that the differ-
more, each location is associated with a particular time value ence between the actual lapsed time since the start of the trip
indicating when the MT 17 is expected to reach the and the estimated lapsed time (i.e., the time value in the
ated location. Each time value along with its associated corresponding entry) is greater than five minutes, then the
location defmes an entry in the MT schedule 39a. MT 17 is off schedule. Otherwise the MT 17 is on schedule.
In the preferred embodiment, the time value corresponds 45 Furthennore, if the MT 17 is off schedule, then the MT
to the estimated amount of time that should lapse between manager 29 is also designed to determine whether the MT 17
the time that the MT 17 starts its intended route and the time is early or late. If the actual time lapsed since the start of the
that the Mf 17 reaches the associated location along the trip is greater than the estimated lapsed time, then the MT 17
route. However, other time values may be used. For is late. If the actual time lapsed since the start of the trip is
example, the time of day that the MT 17 is expected to reach so less than the estimated lapsed time, then the MT 17 is early.
the associated location may be used. Any time value that Alternatively, the MT manager 29 can be configured to
indicates when the MT 17 is expected to reach the associated select the corresponding entry in the predefined schedule
location is sufficient However, for illustrative purposes, the 39a via comparison of time values instead of location
system will be discussed hereinafter assuming that the time values. In this regard, the MT manager 29 can be configured
values in the entries of the MT schedule 39a conform to the 55 to compare the current time value indicated by the clock 38a
preferred embodiment (i.e., that the time values represent the (e.g., the lapsed time since the start of the route) with the
amount of time that should lapse between the time that the time values in the entries of the MT schedule 39a. The
MT 17 starts its intended route and the time that the MT 17 corresponding entry is then the entry in MT schedule 39a
reaches the associated location along the route). having the estimated time value that differs the least with the
The MT manager 29 is configured to monitor the amount 60 actual time value indicated by clock 38a.
of time that lapses as the MT 17 travels along the MT' s In this situation, the :MT manager 29 compares the current
route. For example, the computer system 31a can include a location values from sensor 18 with the location values
clock 38a that indicates the time of day. In this situation, the associated with the corresponding entry of the MT schedule
MT manager 29 is configured to store the time va1ue of the 39a in order to determine whether or not the MT 17 is on
clock 38a when the MT 17 begins the route. Therefore, the 65 schedule. If the location values differ by more than a
MT manager 29 can detennine the amount of time that has predefined threshold value, then the MT 17 is off schedule.
lapsed since the start of the route by comparing the current Otherwise, the MT 17 is on schedule. Furthennore, if the
Exhibit A
Page 75
US 7,119,716 B2
15
acrual location of the Mf 17 (as defined by the current
location values from sensor 18) is further along the route of
travel than the location associated with the corresponding
entry (as defined by the location values in the corresponding
entry), then the MT 17 is early. If the location associated
with the corresponding entry (as defined by the location
values in the corresponding en1Iy) is further along the route
of travel than the actual location of the MT 17 (as defined by
the current location values from sensor 18), then the MT 17
is late.
In response to a determination by the MT manager 29 that
the MT 17 is off schedule, the Mf manager 29 is designed
to transmit a status message to base station control unit 40
(BSCU; FIG. 1; essentially, the host computer), which is
remotely located from the MT 17. The status message
preferably indicates that MI 17 is off schedule and indicates
the amount that MI 17 is off schedule. U.S. Pat. No.
6,363.254 entitled, "System and Method for Enciphering
and Communicating Vehicle Tracking Information,"
describes a system and method for transmitting messages to
BSCU 40. The foregoing docwnent is incorporated herein
by reference.
C. Base Station Control Unit (BSCU)
BSCU 40 preiE:rably, although not necessarily, includes a
base station (BS) manager 41 designed to monitor the travel
of each MT 17 associated with the notification system 10. In
the prefe1Ted embodiment, although not limited to this
implementation, unlike the MTCU 15, the BSCU 40 is
non-mobile (although it could be in some embodiments). As
an example, the BSCU 40 can be located in a central office
of a telephone company.
TI1e BS manager 41 can be implemented in software,
hardware, or a combination thereof. In the preferredembodi·
ment, as illustrated by way of example in FIG. 3, the BS
manager 41 along with its associated methodology is imple-
mented in software and stored in computer memory 30b of
16
the communications device 44, such as the mobile identifi-
cation number (MIN) or electronic serial number (ESN),
transmitted over a data channel of the cellular network 48.
Alternatively, the status message can be appended to a
feature request transmitted over the data channel. As
examples, U.S. Pat. No. 5,771,445 entitled, "Data Messag-
ing in a Communications Network using a Feature Request,"
filed on Dec. 15, 1995, by Kennedy, lll, et al., and U.S. Pat.
No. 5,546,444 entitled, "Methods and Apparatus for Com-
10 municating Data Via a Cellular Network Control Channel"
filed on :Mar. 11, 1994; by Roach, Jr., et al., which are both
incorporated herein by reference, discuss the transmission of
travel data over a data or control channel associated with the
cellular network 48 in further detail. Also, see U.S. Pat. No.
15 5,526,401, which is incorporated herein by reference and
which describes a system for communications over a wire·
less network as well as text messaging to personal pagers.
Also, see U.S. Pat. No. 5,544,225, which is incorporated
herein by reference and which describes a system for com·
20 munications over a wireless network as well as communi·
cation of the location or status information of a mobile item.
In order to transmit the status message through a data
channel by manipulating identifiers of the communications
device 44, the MIN of the communications device 44 is
25 altered to include the status message, but the ESN remains
fixed to be used as an identifier of the communications
device 44. Therefore, after transmitting the identifiers
through the data channel, the communications device 44 can
be identified by the E..';N, and the status message can be
30 determined from the MJN. Alternatively, the ESN of com·
munications device 44 can be altered while the MJN is kept
constant. It should be understood that the invention contem·
plates modification of the MIN, ESN, both the MIN and
ESN, or other identifiers of the communications device 44 to
35 accomplish the dual task of transmitting staru.s messages and
identifying the communications device 44.
a computer system 31b. The computer system 31b can be
similar to computer system 31a, as can be seen by compar.
ing FIG. 2 to FIG. 3. In this regard, the computer system 31b
40
may include memory 30h for storing the BS manager 41,
and the computer system 3lb may also include processing
element 32b for executing software, local interface 33b for
connecting the various components, input device(s) 34b
(e.g., mouse, keyboard, etc.), display(s) 35b, printer(s) 36b,
45
and nonvolatile storage device(s) 37b. In the preferred
embodiment, transceiver (TX/RX) device(s) 52, 72 include
one or more suitable network interfaces that allow the
system 31b to communicate data in connection with network
Alternatively or in combination with the manipulation of
the identifiers of the communications device 44, the status
message can be communicated through the data channel by
appending the status message to feature requests that are
transmitted through the data channel. In this regard, most
feature requests are generated by automatically or manually
dialing the star key ("*'') followed by a two·digit feature
request identification code, and 29 digits of data. Therefore,
for each feature request generated, 29 digits of data pertain·
ing to the status message can be appended to the 1\vo·digit
feature request identification code and sent over the data
channel of the wireless cellular network 48. Other embodi •
ments may transmit different amounts of data following the
55 (FIG. 1).
so feature request By utilizing the manipulation of identifiers
D. Transmission of a Status Message or the appendage of travel data to feature requests, less data
In order to transmit the status message to the BSCU 40, is transmitted through the voice channels of the cellular
the I'vfi manager 29 is configured to transmit the status network 48, thereby reducing the cost of transmitting data
message, via signa143 (FIG. 1), to a communications device through the cellular network 48.
44, which is capable of transmitting and receiving data to 55 In order for successfUl communication to exist between
and from devices outside of MT 17. In this regard, commu· MT manager 29 and BS manager 41, both managers 29 and
nications device 44 is preferably, although not necessary, a 41 should be aware of the communications protocol utilized.
cellular modem configured to transmit and receive wireless Therefore, it is desirable for the BS manager 41 or the MT
signals to and from a cellular network 48 (FIG. 1). manager 29 to initially transmit an instruction via the data
The commWlications device 44 can transmit the status 60 channel of the cellular network 48 to the other manager 29
message over the voice channels associated with the cellular or 41 indicating the protocol to be utilized. Thereafter, the
network 48, as is done by most cellular modems of the prior Mf manager 29 transmits messages to the BS manager 41
art. However, in order to reduce the cost associated with via the selected protocol.
transmitting the travel data through the cellular network 48, Cellular network 48 is designed to transmit the status
the status message may be communicated through the celw 65 message to a communications device 52 (FIG. 1) at tbe
lular network 48 via a data or control channel. In this regard, BSCU 40. Although not necessary for implementation,
the status message can be encoded by altering identifiers of cellular network 48 is preferably designed to transmit to the
Exhibit A
Page 76
US 7,119,716 B2
17
communications device 52 via a public switched telephone
network (PSTN) 55. In this regard, PSTN 55 establishes a
link between communications device 52 and cellular net-
work 48, whereby cellular network 48 and communications
device 52 can corrummicate ~ a signnls 61 and 65, which are
transmitted over land-line connections in the preferred
embodiment. Therefore, communications device 52 is pref-
erably designed as or to include a PSTN modem capable of
communicating signals 65 between BS manager 41 and
PSTN network 55.
Although the preferred embodiment utilizes a cellular
network 48 and a PSTN network 55 to communicate travel
data to BS manager 41, one ordinarily skilled in the art
should realize that other configurations are possible. For
example, communications device 52 can be configured as a
cellular modem capable of communicating signals directly
with cellular network 48. Altematively, utilization of com-
munications networks 48 and 55 can be completely circum-
vented by configuring the communications device 44 to
communicate directly with communications device 52, for
example. Any embodiment capable of communicating data
between MT manager 29 and BS manager 41 should be
suitable.
18
the Mf manager 29, begins monitoring the amount of time
lapsed since the start of the route.
In the preferred embodiment, the base station schedule
39b stored in memory 30b matches the MI schedule 39a
stored in memory 30a, although variations in the two
predefined schedules 39a and 39b are possible. Furthermore,
the BS manager 41 is configured to retrieve an entry, the
"corresponding entry," in the base station schedule 39b
corresponding with the amount of time lapsed since the MT
10 17 began travelling its route. In this regard, the BS manager
41 compares the amount of time that has lapsed since the MT
17 began its route (as determined from the clock 3Bb at the
BSCU 40) with the time values in the base station schedule
39b. The corresponding entry in the base station schedule
15 39b is the entry having the time value differing the least with
the value indicated by the clock 38b (i.e., the time value
indicating the amount of time that has lapsed since the 111'
17 began its route).
The BS manager 41 assumes that the MT 17 is on
20 schedule, unless-the BS manager 41 has received a recent
status message from the MT manager 29. As used herein, a
"recent status message" is the most recent status message
that has been received by the BS manager 41 within a
predetermined time. For example, a recent status message
could be the latest status message received within the last
five minutes, or at the start of a route, or some other suitable
time frame. Therefore, if the BS manager 41 has not
received a recent status message from the MT manager 29,
then the BS manager 41 assumes that the location values in
the corresponding entry of the predefined base station sched-
ule 39b indicate the current location of the MT 17.
lt should be noted that by transmitting a status message 25
only when the MT 17 is off schedule reduces the cost of
operating the notification system 10. In this regard, com-
munication through a cellular network 48 is relatively
expensive, and the cost is based on the amount of data
transmitted By refraining from transmitting any data from 30
the MT manager 29 to the BS manager 41 when the MI 17
is on schedule, the amount of data transmitted through the
cellular network 48 is reduced, thereby reducing the com-
munications cost associated with the notification system 10.
Therefore, the methodology of assuming the MT 17 is on 35
schedule and of only transmitting data to the BS manager 41
when the Mr 17 is off schedule enables the notification
system 10 to minimize costs. It should be noted that the
foregoing feature is optional.
E. Base Station Manager
Recalling that BS manager 41 (when employed within the
context of notification system 1 0) is to transmit a notification
message when the MT 17 is a predetermined proximity from
a particular location (e.g., a predefined MT stop, etc.), the
BS manager 41 then compares the location values in the
corresponding entry (which represent the current location of
the MT 17) with location values defining the predetermined
proximity. lf the location values from the corresponding
40 entry differ from the location values of the predetermined
proximity by less than a predetermined amount, then the BS
BS manager 41 is designed to monitor the travel of the manager 41 transmits a notification message to the user.
MT 17 and (when employed in the context of advance Otherwise no notification message is transmitted to the user.
notification system 10) is also designed to transmit a noti- Alternatively, the BS manager 41 can be configured to
fication message to a user when the MT 17 is a predeter- 45 compare time values instead of location values in order to
mined proximity ±!om a particular MT destination or other determine whether a notification message should be trans-
location. The predetermined proximity can be a particular mitted to the user. In this regard, the BS manager 41 is
time or distance that the MT 17 is from the destination. If the designed to compare the time value in the corresponding
MT 17 is off schedule, then the BS manager 41 is further entry with a predetermined threshold value indicating the
configured to transmit a message to the user indicating that so amount oftime that should lapse between the MT 17 starting
the MT 17 is off schedule. its route and arriving at a location associated with the
The BS manager 41 of tracking notification system 10 is predetermined proximity (e.g., a threshold value indicating
designed to detennine the current location of the MT 17 and how long the MT 17 should travel along its route before
to compare the current location of the MT 17 to a predefined notification should be sent to the user). If the threshold value
location along the route of travel of the MT 17 in order to 55 in the corresponding entry exceeds the predetermined time
determine whether notification should be sent to the user. In value, then the BS manager 41 causes a notification message
this regard, like the MT manager 29, the BS manager 41 to be communicated to the user:
includes a predefined schedule 39b, referred herein as the If the BS manager 41 of notification system 10 has
"base station schedule 39b," in memory 30b. Furthermore, received a recent status message from the MT manager 29,
similar to the computer system 31a (FIG. 2), the computer 60 then the BS manager 41 determines the actual location
system 31b (FIG. 3) includes a clock 39b or other type of values of the MT 17 based on the location values in the
counter that can be used to determine the amount oftime that corresponding entry and the recent status message. In this
has lapsed since the MT 17 started traveling along the MT's regard, the location values in the corresponding entry rep-
route. When the MT 17 begins the route, the MT manager 29 resent the estimated location of the "MT 17. The status
preferably transmits a message to the BS manager 41 via 65 message indicates how much the MT 17 is oft schedule (i.e.,
communications devices 44 and 52 indicating that travel on bow far the MT 17 is from the estimated location). For
the route is beginning. In response, the BS manager 41, like example, the status message can indicate that the MT 17 is
Exhibit A
Page 77
US 7,119,716 B2
19
five miles off schedule. Therefore, the BS manager 41 is
designed to calculate new location values based on the
estimated location and the status message. These new loca-
tion values represent the actual location of the Mf 17.
Therefore, by using the new location values instead of the
values in the corresponding entry, the BS manager 41 can
determine whether a notification message should be sent to
the user according to the methodology described herein-
above.
Furthermore, instead of indicating how far the MT 17 is
from the estimated location via location values, the status
message can indicate how far the MT 17 is from the
estimated location via a time value (e.g., the status message
can indicate that the MT 17 is ten minutes late). In this case,
the BS manager 41 is designed to adjust the time value in the
corresponding entry to account for the MT 17 being off
schedule. For example, if the MT 17 is early, then the time
value in the corresponding entry is increased a correspond·
ing amount, and if the MT 17 is late, then the time value in
the corresponding entry is decreased a corresponding
amount. This adjusted time value is then compared with the
predetermined threshold value described hereinabove in
order to detem1ine whether notification should be sent. lf the
adjusted time exceed<; the predetennined time value, then
the BS manager 41 causes a notification message to be
transmitted to the user.
In an alternative embodiment, the location values trans·
mitred in the status message can represent the actual location
of the MT 17 instead of representing how far the Mr 17 is
off schedule. In this embodiment,. the BS manager 41 can be
designed to directly compare these location values with the
location values defining the predetennined proximity in
order to determine whether notification should be sent to the
user. Accordingly, if these location values differ from the
location values defining the predetermined proximity by less
than a predetermined amount, then the BS manager 41
transmits a notification message to the user. Otherwlse, no
notification message is sent to the user.
Furthermore, when the BS manager 41 determines that
the MT 17 is off schedule, the BS manager 41 preferably
transmits an off schedule message to the user, as described
hereinbelow, to notify the user that the MT 17 is off
schedule. This message can include a variety of information
including, but not limited, how much (in time or distance)
the "MT 17 is off schedule. However, it should be noted that
communication of the off schedule message is not a neces.
sary feature.
20
aud1ble, text, and/or other message that can be communi·
cated. A PCD 75 is a communications device that can be
personally associated with a party and enable poinHo·point
communications between the notification system 10 and the
party. Nonlimiting examples of PCDs 75 are as follows: a
personal computer (PC) capable of displaying the notifica-
tion through e·mail or some other communications softwarl\
a television, a wireless (e.g., cellular, satellite, etc.) or
non·wireless telephone, a pager, a personal data assistant, a
10 navigation system in a motor vehicle, a radio receiver or
transceiver, or any other device capable of notifying the user
with some type of user perceptible emission. Many, although
not all, PeDs 75 are transportable. Furthermore, a plurality
of communications devices 72 may exist in some applica·
15 tions, so that the BS manager 41 can simultaneously or
substantially concurrently notify a plurality of parties having
respective devices 72 of the impending arrival of the MT 17
at a particular MT stop.
Note that examples of useful PCDs 75 that can be utilized
20
to implement many of the features described in this docu·
ment are portable wireless telephones having image capa·
bilities (e.g., a Sanyo Model 8100 wireless PCS vision
picture phone distributed by Sprint, a Sony Ericsson T300
wireless picture phone distributed by T Mobile, etc.). The
25
Wireless Access Protocol (WAP; developed by the WAP
Fomm; see WAP Version 2.0 specification at www.wapfo·
rum.org, which is incorporated herein by reference in its
entirety) can be implemented in connection with wireless
telephones in order to enable these telephones to cornmu·
30
nicate with (send data packets to and! or receive data packets
from) computers or devices, such as serv·
ers, that are communicatively coupled to the World Wide
Web (WWW) of the Internet (by way of their respective
cellular or PCS networks).
35
Note fllliher that the PCDs 75 can be non·standard
input/output (I/0) devices that can be communicated with
over an open network, such as the Internet, using an
extended open network protocol, such as extended HTML,
40
as is described in U.S. Pat. Nos. 5,742,845 and 5,905,908,
both of which are incorporated herein in their entirety by
reference.
Although the preferred embodiment utilizes a PSTN
network 55 to communicate a notification or an off schedule
45
message to PCD 75, one ordinarily skilled in the art s_hould
realize that other configurations are possible. For example,
other communications networks can be utilized or utilization
of communications nerntorks can be completely circum·
F. Transmission of Off Schedule and Notification Messages vented by configuring communications device 72 to com·
Once the BS manager 41 of systems 10 and 12 determines 50 municate directly with communications device 73. Any
that a notification.or an off schedule message should be sent communications system capable of communicating data
to a user, the BS manager 41 is designed to communicate the between BS manager 41 and PCD 75 should be suitable.
message to the user via PSTN network 55 and communi ca. As an example, the BS manager 41 may notify the user of
tions devices 72 and 73 (FIG. 1). In this regard, communi· the impending arrival of the MT 17 by transmitting a
cations devices 72 and 73 are or include PSTN transceiver 55 distinctive ring to the user's message device. In this embodi·
modems capable of interfacing with and communicating ment, the PCD 75 is a telephone. A distinctive ring is a
with PSTN network 55. BS manager 41 is designed to ringing cadence that is different than the standard ringing
transmit the message as signal 70 to user communications cadence used to notifY the user of a telephone call. Since the
device 72, which communicates the message with PTSN user can different the different ringing cadence, the user is
network 55 via signal 74. PTSN network 55 then commu. 60 aware that the telephone call corresponds to a notification
nicates the message to personal communications device message from the BS manager 41 indicating that arrival of
(PCD) 75, which has a receiver and a transmitter, or a the MT 17 is imminent. A system for transmitting a distinc·
transceiver, denoted by block 73, in the preferred embodi· tive telephone ring as the notification message is fully
ment. described in U.S. Patent Application entitled, "Advance
PCD 75 is configured to notifY the user and communicate 65 Notification System and Method Utilizing a Distinctive
a notification message, which may merely be a ring in the Telephone Ring," assigned Ser. No, 081762,052 and filed on
case of a telephone or pager, optionally accompanied by an Dec. 9, 1996, which is incorporated herein by reference.
Exhibit A
Page 78
US 7,119,716 B2
21
G. Creation of the rviT and Base Station Schedules
It should be noted that the predefined MI schedule 39a
and the predefined base station schedule 39b can be deter-
mined or defined by a variety of methodologies. For
example, the predetermined schedules 39a and 39b can be 5
estimated based on various factors, such as the types of
speeds likely to be traveled by the MT 17 and the types of
traffic conditions expected to be encountered during travel.
However, in the preferred embodiment, the predefined
schedules 39a and 39b are defined via a previous delivery of 10
the MT 17 along the same route of travel.
In this regard, delivery vehicles 17 frequently travel the
same routes. Thjs is especially tme for buses, for example,
where a bus routinely travels the same route and makes the
same stops. As the MT 17 is traveling the route, the MT 15
manager 29 is configured to periodically read the sensor 18
and to store an entry in memory 30a. The entry preferably
includes the current location values of the MT 17 indicated
by sensor 18 and the time value indicated by clock 38a (i.e.,
the time value indicating the amount of time that has lapsed 20
since the start of the travel on the route). Therefore, when the
MT 17 reaches the end of the route, the MT manager 29 has
stored numerous entries which define the predefined MT
schedule 39a. This predefined schedule 39a may also be
used as the base station schedule 39h. Other methodologies 25
may be employed to define the Mf schedule 39a and/or the
base station schedule 39b.
22
T11e MT manager 29 is then designed to compare the
deviation indictor to an alarm threshold value to determine
whether an alarm signal should be transmitted to the BS
manager 41. The alarm threshold value corresponds with the
distance that the Mf 17 can deviate from the predefined MT
schedule 39a before an alann is generated. Therefore, if the
deviation indicator exceeds the alarm threshold value, the
MI manager 29 transmits an alarm message to the BS
manager 41 via communications devices 44 and 52. Pref-
erably the alarm message includes the current location
values produced by the sensor 18 so that the travel of the MT
17 can be tracked by the BS manager 41.
Providing an alarm message, as described hereinabove,
helps to discover when an MT 17 has been stolen or hijacked
and helps law enforcement agencies to recover the MT 17 by
tracking the travel of the MT 17 once the MT 17 has been
stolen. Tn this regard, the MT manager 29 automatically
generates an alarm message and monitors travel of the MT
17 once the MT 17 deviates from the Mf schedule 39a by
a predetermined amount. The alarm message can be used by
law enforcement agencies to discover when the MT 17 has
been stolen and where the MT 17 is located, thereby helping
law enforcement agencies to recover the MT 17 once it bas
been stolen.
Because the deviation indicator is defmed relative to
points along the MT' s route of travel, an alarm can be
generated when the MT 17 deviates from the route by a
relatively small amount. For example, the MT manager 29
can be configured to transmit an alarm signal when the MT
FIG. 4A is a flow chart depicting the operation and
functionality of the rviT manager 29 in embodiments where
the MT manager 29 determine.<; the Mf schedule 39a while
traveling along, the route of travel. As shown by blocks 76
and 77, the MI manager 29 determines whether a sample
period has expired while the MT 17 is traveling on the route
(i.e., before the MT 17 has finished the route). The sample
period is a predetermined amount of time that lapses
between samples, which will be discussed in more detail
hereinbelow. Preferably, the MT clock 38a indicates
whether the sample period has expired. For example, when
the clock 38a is a counter, the sample period can be defined
30 17 deviates from its predefined route by approximately 20
feet. Other distances, both less than and greater than 20 feet,
may be used to trigger an alarm signal. However, it is
generally desirable that a certain amount of deviation (de-
pending on the expected driving conditions and the precision
35 of sensor 18) be allowed so that the MT 17 can reasonably
maneuver through traffic without generating false alanns.
In addition, the alarm threshold value is selectable in the
as a predetermined number of counts by the clock 38a. 40
Therefore, the MT manger 29 can determine whether the
sample period has expired by counting the munber of
increments or cycles of the clock 38a.
preferred embodiment. This value can be entered into the
computer system 31a by a h1unan operator at the MT 17 via
input device 34a, for example. Alternatively, this value can
be communkated from the BS manager 41 to the Mf
manager 29 via communications devices 44 and 52 at or
around the start of the route. The alarm threshold value can
a l ~ o be hardwired into the computer system 31a with
When the MT manager 29 determines that the sample
period has expired, the MT manager 29 samples the current
location values of the MT 17 and the time value of the clock
38a. In other words, the rvrr manager 29 determines the
current location values of the MT 17 and the current time
value from the clock 38a and stores these values in the next
entry of the MT schedule 39a, as depicted by blocks 78 and
79. This process repeats until the MI manager 29 determines
that the MT 17 has completed the route. Thereafter, the MT
manager 29 can use the Mf schedule 39a to track the MI's
progress on future deliveries that utilize the route defined by
the MT schedule 39a.
H. Alarm System
The MT manager 29 can be configured to compare the
corresponding cnlly and the location values supplied from
the sensor 18 in order to determine whether an alarm signal
should be generated. Jn this regard, the MT manager 29
preferably subtracts the location values in the corresponding
entry from the current location values of the MT 17 (as
determined by the sensor 18) to produce a deviation indi-
cator. Therefore, the deviation indicator _indicates how far
the MT 17 has deviated from the route defined by the Mf
schedule 39a.
45 switches that can be manipulated by a human operator in
order to selectively change the value. Many other method-
ologies known in the art may be used for selecting the value
of the alarm threshold value.
It should be noted that in other embodiments, it may be
so desirable for the MI manager 29 to generate an. alarm signal
based on comparisons of the location of MT 17 to a
predefined geographical region instead of the route defined
in MT schedule .39a. For example, it may desirable to define
a region that is 30 miles (or some other distance) from the
55 start of the route (or some other particular location). Then,
the MT manager 29 can be configured to generate an alarm
signal if the MT manager 29 determines that the MT 17 is
outside of this predefined region based on the signals 27
received from sensor 18. Such a methodology for generating
60 an alarm signal is particularly suitable for applications
where only local deliveries are expected, for example.
There are various methodologies for determining whether
the MT 17 is outside of the predefined region. For example,
in one embodiment, the MT manger 29 subtracts the current
65 location values determined from signals 27 with the location
values of a particular point (e.g., the location values of the
start of the route, when the region is defined as any point
Exhibit A
Page 79
US 7,119,716 B2
23 24
within a certain distance of the start of the route) to derive BS manager 41. In the preferred embodiment, the MT
the deviation indicator, As in the preferred embodiment, if schedule 39a was created and stored in the MT manager 29
the deviation indicator has a magnitude greater than the as the MT 17 previously traveled along the same route. A
alarm threshold value, the MT manager 29 generates an copy of the MT schedule 39a is preferably transferred to the
alarm signal. Othenvise, no alarm signal is generated. BS manager 41 via any suitable methodology and stored as
Further note that U.S. Pat. No. 5,751,245, which is the base station schedule 39a. For example, the MT schedule
entirely incorporated herein by reference describes an alarm 39a can be copied to a magnetic disk and later downloaded
system that can be employed when a vehicle substantially in memory JOb or a copy of the MI schedule 39a can be
departs from a predetermined route, for the security of transmitted to the BS manager 41 via communications
transported cargo. 10 devices 44 and 52.
1. Alternative Embodiment of the MTCU
In an alternative embodiment of the MTCU, the "corre·
spending entry" of the MT schedule 39a can be defined as
the entry having location values defining a location along the
15
route that was roost recently passed by the MT 17. There-
fore, the MT manager 29 monitors the signals 27 from the
sensor 18 until the MT manager 29 determines that the MI
17 passed a location corresponding with one of the entries in
the MT schedule 39a. The MT manager 29 determines
20
whether the 'MT 17 is early or late via the t.echniques
described hereinabove using the aforementioned entry as the
corresponding entry.
After determining whether to generate an alarm signal
and/or status message for the corresponding entry (and after
generating the alarm signal and/or the status message, if
25
necessary), the MT manager 29 monitors the signals 27
again for the next corresponding entry. Therefore, when a
corresponding entry is detected (i.e., when the 'MT manager
29 determines that the MI 17 passed a location correspond·
30
ing with the location values in one of the entries of the MI
schedule 39a for the first time), the MT manager 29 analyzes
the values of the sensor 18, the clock 38a, and the corre·
spending entry to determine whether an alarm signal and/or
status message should be generated. Thereafter, the MT
35
manager 29 waits until the next corresponding entry is
detected before determining whether to generate another
status message. Therefore, the MT manager 29 detennines
whether a status message should be communicated to the BS
manager 41 each time the MI 17 passes a location corre-
40
spending with the location values in one of the entries of the
NIT schedule 39a, and the MT manager 29 refrains from
communicating status messages as the MT 17 travels
between locations defined by the data in the MT schedule
39a. In other words, the only time the :MT manager 28
45
transmits a status message is when the MT 17 is passing a
location corresponding with one of the entries in the iviT
schedule 39a or a short time thereafter.
However, since it is possible for the MT 17 not to pass any
of the locations defined in the predefined schedule when the
MT 17 deviates from the route (e.g., when the MT 17 is
50
stolen), the MT manager 29 preferably determines whether
to communicate an alarm signal periodically rather than
waiting for one of the locations defined by the Mf manager
In embodiments where the MI schedule 39a is not
previously created and stored by the MI manager 29, the
:MT schedule 39a is preferably downloaded into both the BS
manager 41 and the MT manager 29. It is possible to
download the base station schedule 39a in the BS manager
41 and to transmit a copy of the base station schedule 39a
to the MT manager 29 via communications devices 44 and
52 prior to the start of the route. Any methodology for
respectively storing the MT schedule 39a and the base
station schedule 39b into the MT manager 29 and the BS
manager 41 is suitable.
When the MT 17 begins travel, the MT manager 29 stores
the current value of the MT clock 38a and begins to monitor
the amount of time that lapses from that point until comple·
tion of the route. Furthermore, as can be seen by block 82 of
FIG. 4B, the MT manager 29 also transmits a start signal to
the base station manger 41 via communications devices 44
and 52 indicating that travel of the MI 17 is beginning. In
the BS manager 41 begins to monitor the lapsed
time as well.
In many situations, it may be desirable to begin monitor-
ing travel of the MT 17 after the MT 17 starts its route. This
is particularly true when unpredictable delays usually occur
close to the staring point of the route. For example, when the
MT 17 is a school bus taking children home from school,
unpredictable delays may occur close to the starting point
(i.e., at the" school) where traffic is often congested. There-
fore, instead of transmitting a start signal to the BS manager
41 when the MT 17 begins traveling, the MT manager 29
waits for a predetermined time period or until the Mf 17 has
traveled a predetennined dlstance from the !ltarting point
before transmitting the start signal. For example, the MI
manager 29 can monitor the travel of the MT 17 from the
starting point via the sensor 18 and trdnsmit the start signal
once the MT manager 29 determines that the MT has
traveled one-eighth of a mile from the starting point In this
regard, location values representing a predetermined point
along the route of travel and one-eighth of a mile from the
starting point can be stored in the MT manager 29. When the
MT manager 29 determines that the MT 17 passes this point,
the MT manager 29 determines that the MT 29 has traveled
more than one-eighth of a mile and transmits the start signal.
Preferably, the predetermined schedules 39a and 39b both
use the point where the MT manager 29 transmits the start
29 to be passed.
J. Overall Notification System Operation
A possible implementation of use and operation of the
notification system 10 and associated methodology are
described hereafter. For illustrative purposes only, assume
that the MT 17 is to travel a predetermined route to a
destination where the MT 17 is to pick up or deliver an item.
For example, assume that the MT 17 is a bus that is to travel
to a bus stop to pick llp a passenger and that this passenger
is to receive a notification signal when the MT 17 is ten
minutes from the bus stop.
55 signal as the starting point for the route. Therefore, the
distances and times stored in the predetermined schedules
39a and 39b are relative to the predetermined location where
MT manager 29 transmits the start signal instead of the
actual starting point of the route, However, this is not a
Initially, the MT schedule 39a is stored in the :MT
manager 29 and the base station schedule 39a is stored in the
60 necessary feature, and the location values and time values
stored in the predetermined schedules 39a and 39b may be
relative to other points both along the route of travel and
outside of the route of travel.
As the MT 17 travels, GPS satellites 23 transmit wire]e.'ls
65 signals 21 to sensor 18 that can be analyzed through tech-
niques well known in the art to determine a position (i.e.,
current location values) of the sensor 18 (and, therefore, of
Exhibit A
Page 80
US 7,119,716 B2
25
the MT 17) relative to a particular reference point, as
depicted by block 85 of FIG. 48. For example, in GPS
systems, the intersection of the Equator and the Prime
Meridian is typically used as the reference point. Sensor 18
receives the signals 21 and determines location values
representing the position of the MT 17 relative to the
reference point and trdnsmits these values to Mf manager
29.
TI1e MT manager 29 compares the current location values
of the MT 17 with the location values in the MT schedule
39a in order to determine which entry in the MT schedule
39a corresponds with the current location of the MT 17, as
shown by block 87 of FIG. 4B. The corresponding entry is
preferably the entry having location values that most closely
match the current location values received from the sensor
18.
26
In order to reduce the number of transmissions between
the MT 17 and the base station control unit 40, the MI
manager 29 preferably (although not necessary) transmits
the status message to the BS manager 41 only if another
status message has not been transmitted within a p r e d e t e r ~
mined delay period. For example, if a status message has
been sent within a predetermined time period, for example,
within the last five minutes, then the MT manager 29 refrains
from sending another status message. It should be apparent
10 to one skilled in the art that other delay periods can be
selected to update the location of the MT 17 at a desirable
rate.
Furthennore, it is possible to selectively control the delay
period. For example, when the MT 17 stops to make a
15 delivery or is slowly traveling through congested areas, it
may be desirable to increase the delay period to decrease the
After selecting the corresponding entry, the MT manager number of status messages sent to the BS manager 41.
29 retrieves the location values associated with the corre- Alternatively, when the MT 17 is traveling quickly and the
sponding entry and subtracts these values from the current location of the MT 17 is changing rapidly, it may be
location values received from the sensor 18 and used by the 20 desirable to decrease the delay period. Furthermore, when
MT manager 29 to select the corresponding entry. Referring the MT 17 enters an area where no immediate deliveries or
to block 91 of FIG. 4B, the resulting value or values pick ups are to made, there is no immediate need to morritor
(referred to as the deviation indicator) indicates the MT's the MT 17 and the delay period can be increased. The delay
deviation from the MT schedule 39a. As shown by block 93 periods can be predefined in memory 30a, can be controlled
of FIG. 4B, the MT manager 29 then compares the deviation 25 by the operator of the MT 17, or can be controlled via signals
indicator to the alarm threshold value. If the deviation transmitted from remote locations to the MT manager 29
indicator exceeds the alarm threshold value, then the MT (e.g., from -the BS manager 41 to the MT manager 29 via
manager 29 transrriits an alarm message to the BS manager communications device 44). Other methodologies for con-
41, as depicted by block 95 of FIG. 4B. The alann message trolling the delay periods are possible.
includes the current location of the MT 18, and the BS 30 Another way to reduce the number of transmissions of
manager 41 tracks the location of the Mf 17 based on the status messages at desired times is to selectively increase the
alann messages transmitted from the Mf manager 29. The predefined amount that the MT 17 should be off schedule
information provided by the alarm message can be used by before a status message is transmitted to the base station
law enforcement agencies to track the MT 17. control manager 41. Similar to the changes in the delay
After dctem1ining whether an alarm message should be 35 periods described above, the changes to the aforementioned
generated, the Mf manager 29 retrieves the time value predefined amount can be predefined in memory 30a, can be
associated with the corresponding entry and compares it controlled by the operator of the MT 17, or can be controlled
with the time value indicated by clock 38a (i.e., the time via signals transmitted from remote locations to the Mf
value indicating the amount of time elapsed since the start of manager 29 (e.g., from BS manager 41 to MT manager 29
the route). The Mf manager 29 also retrieves a predeter- 40 via communications device 44).
mined threshold value indicating bow much the MT 17 can The input device 34a (FTG. 2) can he used to input
deviate from the MT predefined schedule 39a before the MT changes in the delay period and/or in the predefined amount
17 is considered to be off schedule. Referring to block 97 of that the MT should be off schedule before a status message
FIG. 4B, if the difference of the foregoing time values is transmitted. In this regard, the input devk-e 34a may
exceeds the predetermined threshold value, then the MT 45 include switches, buttons, a key pad, or any other device that
manager 29 determines that the MT 17 is off schedule. canbemanipulatedbytheoperatoroftheMT17toinputthe
However, if the difference of the foregoing time values is changes.
less than the predetermined threshold value, then the MI When the BS manager 41 receives a status message, the
manager 29 determines that the MT 17 is on schedule. BS manager 41 stores the status message in memory JOb. If
When the MT manager 29 determines that the MT 17 is 5o desired, the BS manager 41 transmits a message to the user
on schedule, the MT manager takes no further action regard- via communications devices 72 and 73 indicating that the
ing the current location values received from the sensor 18. Mf 17 is off schedule and indicating how much the MT 17
The MT manager 29 merely receives a new set of location is off schedule in response to the status message.
values from the sensor 18 and analyzes the new set of values The BS manager 41 periodically detennines whether a
according to the methodology described herein. However, 55 notification message should be sent to the user indicating
when the MT manager 29 determines that the Mf 17 is off that arrival of the MT 17 at the bus stop is imminent (e. g.,
schedule, the MT manager 29 generates a status message indicating that the MT 17 is ten minutes from the bus stop).
and transmits the status message to the BS manager 41, as In this regard, the notification message should he sent to the
depicted by block 99 of FIG. 4B. user when the MT 17 is within a predetermined proximity
In this regard, the MT manager 29 determines whether the 60 (i.e., a predetennined time or distance) from the bus stop. To
MT 17 is early or late and how far the MT 17 is off schedule determine whether the notification message should be sent,
(e.g., how many minutes or miles the MT 17 is from the the BS manager 41 compares the location values of the
location specified by the lOcation values in the correspond- current location of the MT 17 to the location values of the
ing entry). The MT manager 29 then generates a status predetermined location (e.g., the bus stop). If the difference
message including tills information and transmits the status 65 between the location values of the current location of the MT
message to the BS manager 41 via communications devices 17 and the bus stop is greater than a threshold value, then the
44 and 52. Mf 17 is too far from the bus stop for notification to be sent
Exhibit A
Page 81
us 7,119,716 82
27
to the user. Therefore, a notification message is not
ated. However, if the difference between the location values
of the current location of the MT 17 and the bus stop is less
than the threshold value, then a notification message is
transmitted to the user via communications devices 72 and s
73, unless a similar notification message (i.e., a message
indicating that the MT 17 is off schedule by the same
amount) associated with the bus sto-p has previously been
sent to the user.
In determining the current location of the MT 17, the BS 10
manager 41 assumes that the MT 17 is on schedule unless a
recent status message has been received. Therefore, the MT
manager 41 determines which entry in the base station
schedule 39b corresponds to the assumed location of the MI
17. In this regard, the MT manager 41 compares the time l5
values in the base station schedlile 396 with a lapsed time
value indicating how much time has lapsed since the !viT 17
started the route. The entry having a time value closest to
this lapsed time value is the corresponding entry. The
location values associated with the corresponding entry 20
represent the assumed location of the MT 17. Unless a recent
status message has been received, the BS manager 41 uses
these location values as the current location values to be
compared against the location values of the predetermined
location (e.g., the bus stop) in order to detennine whether a 25
notification message should be sent to the user. However, if
28
ule. Otherwise, the MT 17 is on schedule. Furthermore,
regardless of which embodiment is used to determine how
far the MT 17 is off schedule, the Mf manager 29 can
indicate how far the MT 17 is off schedule via the status
message using either distance values, time values, or any
other type of values known in the art for indicating the
position of the MI 17.
It should be noted that the preferred embodiment has been
described hereinabove assuming that the sensor 18 is
capable of detennining the MT's location based on signals
received from satellites 23. However, this is not a necessary
feature, and any type of sensor 18 that may be used for
determining the MT's position along the route of travel is
sufficient. For example, the sensor 18 may be designed as an
odometer that indicates how far the MT 17 travels.
fore, the predetermined points along the route of travel used
to determine whether the MI 17 is on or ofr schedule can be
defined in the schedules 39a and 39b relative to their
distance from the starting point of the route. In other words,
the location values stored in the schedules 39a and 39b
correspond to distance values indicating how far the
termined points are from the starting point of the route.
Therefore, the MT manager 29 can determine-how far the
MT 29 is from any of the predetennined points by
mining how far the MT 17 has traveled from the starting
point of the route.
a recent status message has been received, then the BS
manager 41 determines the current location values oftheMI K. User Notification Preferences and Reports
17 based on the recent status message and/or the location BS manager 41 is designed to receive the travel data
values associated with the corresponding entry. 30 transmitted fr6in MT manager 29 and to monitor the travel
For example, if the recent status message includes of the MT attached to the MTCU 15 by monitoring the travel
tion vah1es indicating the actual location of the MT 17, then of the MTCU 15. In this regard, BS manager 41 is designed
the BS manager 41 uses these values to compare with the to include a data manager 67 configured to receive the travel
coordinate values of the predetermined location (e.g., the data via signal 66 from communications device 52, as
bus stop). However, if the status message only. indicates how 35 depicted by FIG. SA. Data manager 67 is designed to store
much the MT 17 is off schedulE; then the BS manager 41 the travel data for each MTCU 15 being monitored in a
calculates the cl.urent location values of the MT 17 based on database 94, which is preferably a relational database having
the status message and the location values associated with a number of tables 68, but other databases are possible, for
the corresponding entry in the base station schedule 39b. example, database, database, one made
Once the current location values of the "MT 17 have been 40 up of lookup tables, etc.
determined, the BS manager 41 compares the current As is well known in the art, a relational database is a
tion values of the Mf 17 with the location values of the database or database management system that stores
predetermined location (e.g., the bus stop) as previously mation in tables-rows and columns of data-and conducts
described hereinabove to determine whether a notification searches by using data in specified columns of one table to
signal should be transmitted to the user. 45 find additional data in another table. In a relational database,
The operation of the preferred embodiment has been the rows of a table represent records (collections of
described hereinabove in the context where the Mf manager mation about separate items) and the columns represent
29 compares location values to determine the corresponding fields (particular attributes of a record). In conducting
entry in the MT predefined schedule 39a. Therefore, the MT searches, a relational database matches information from a
manager 29 compares the time value associated with the 50 field in one table with infonnation in a corresponding field
corresponding entry in the MT schedule 39a to determine of another table to produce a third table that combines
whether or not the Mf 17 is on schedule. However, it should requested data from both tables. For example, if one table
be apparent to one skilled in the art upon reading this contains the fields
disclosure that time values may be compared by the MT and DATE, and another contains the fields
manager 29 to determine the corresponding entry in the MT 55 TIME, and a
predefined schedule 39a. relational database can match the
In this regard, the entry in the MT schedule 39a having a fields in the two tables to find such infonnation as the
time value most closely matching the lapsed time value possible pickup stop locations for packages transported by
indicated by the clock 38a (i.e., the value indicating the the MT or the delivery times (stop times) for all packages
amount of time lapsed since the start of the route) can be 60 loaded on the MT withln the last day. In other words, a
selected as the corresponding entry. As a result, the MI relational database uses matching values in two tables to
manager 29 determines how far the MT 17 is off schedule relate information in one to information in the other,
based on distance rather than time. For example, if the Although not limited to tills configuration, in one ernbodi-
difference between the current location values of the MT 17 ment, among others, the database 94 includes, among other
(as determined by the sensor 18) and the location values 65 things and in general, an MT data table 68a having
associated with the corresponding entry is greater than a mation pertaining to the MT, such as an ID, type (package,
predetermined threshold value, then the MT 17 is o:tfsched- mobile vehicle type, etc.), model, whether the thing has air
Exhibit A
Page 82
US 7,119,716 B2
29
conditioning, etc.; a user data table 68b having infonnation
regarding user preferences; a communication method data
table 68c having information pertaining to various commu-
nications methods that can be utilized for contacting a user
(which can be linked to the user preferences); a stop location
data table 68d having information pertaining to stop loca-
tions of MTs; an MT (MT) travel data table 68e having
information concerning travel status of MTs, an advertise-
ment data table 68f having advertisements that can be
communicated to a PCD 75; a PCD data table 68g having 10
information pertaining to the devices 75; an authentication
data table 68h having authentication infonnation or indicia
to be described later in this document, a PCD travel data
table 68i having information pertaining to travel of a tracked
PCD 75, a traffic flow predicament data table 68j, a package 15
data table 68k, a failure st<Jtes data table 68!, a tasks data
table 68m, subwtables of the foregoing, etc. The tables 68
inclucte·related fields for linking and relating various ele-
ments in the various tables 68.
30
make assumptions about the time necessary to travel to the
specified location. For example, if the route of the MTCU 15
is through congested areas, the monitoring mechanism 69
can assume a certain delay time for traveling certain dis-
tances, and if the route of the MfCU 15 is through less
congested areas, the monitoring mechanism 69 can assume
another delay time that is less than the delay time assumed
for the congested areas. Alternatively, the monitoring
mechanism 69 can use an average of the times it has
previously taken for MTs 17 to travel over the same route
during other deliveries. Therefore, by comparing the travel
data transmitted from MICU 15 with preference data, the
monitoring mechanism 69 can determine when to send a
notification message to a user.
As depicted by blocks 8Ba, 88b, 88g, and 88h ofF! G. 5C,
the preference data can be stored in user data table 68b of the
database 94 (FIG. SB). As stated hereinbefore, the MT travel
data table 68e of the database 94 is preferably configured to
store the travel data associated with each MTCU 15 in a
Furthermore, in this embodiment, MTCUs are related to
identification values in MT data table 68a, and these values
are correlated with travel data in MT travel data table 68e.
Travel data can include information such as, but not limited
to, the MICU's coordinate values (i.e., the MTCU's 15
location relative to a predetermined reference point), infor-
mation regarding delivery status of items to be delivered,
and/or the times that the MTCU 15 reached particular
locations or stops. The database 94 is configured to contain
20 respec.:tive entry uniquely identified with the associated
MTCU 15. Accordingly, each data entry can also include the
preference data associated with each MTCU 15 that corre-
sponds with the entry, or the preference data can be stored
in separate entries which are correlated with corresponding
all of the desirable information to monitor the status of each
MTCU 15 associated with the notification system 10.
Referring to FIG. SB, data manager 67 is configured to
include a monitoring mechanism 69. The functionality of
monitoring mechanism 69 is depicted in FIG. 5C. As shown
by blocks 88a-88jofFJG. SC, monitoring mechanism 69 is
configured to receive travel data from MICU 15 and to
compare the travel data with predefined preference data
stored in the database 94, particularly the user data table 68b.
Preference data, as used herein, is data that defines the
preferred parameters indicating when to notifY a user of the
impending arrival of the MTCU 15 at a particular location.
25 MTCU entries.
Once the monitoring mechanism 69 determines that a
notification message should be sent to a user, the data
manager 67 is designed to communicate a message to a user
at a remote location via PSTN network 55 and communi-
30 cations devkes 72 and 73 (FIG. 1).
In this regard, communications devices 72 and 73 are
preferably PSTN modems capable of communicating with
PSTN network 55. Data manager 67 is designed to transmit
the message as signal 70 to user communications device 72,
35 which communicates the message with PTSN network 55
via signal 74. PTSN network 55 then communicates the
message to communications device 73, which is preferably
configured to communicate the message to a PCD 75. PCD
75 is configured to notify the user of the impending arrival
40 of the MTCU 15. As mentioned, PCD 75 can be a computer
capable of displaying the notification through e-mail or
some other commullications software. Alternatively, PCD
75 can be a telephone, a pager or any other device capable
lt can be system defined or user defined. For example,
preference data can be coordinates of a desired location
whereby a notification message is sent to a user when the
coordinates of the MTCU 15 pass the coordinates of the
desired location. In this context, the desired location defined 45
of notifying a user.
1. User Activation
by the preference data can, for example, represent a location In order for data manager 67 to transmit a notification
that is a predetermined distance from the user house, place PCD 75, data manager 67 should be aware of certain contact
of delivery or pickup, or other particular location. Therefore, information enabling data manager 67 to contact the PCD
when the user receives the notification message, the user is 75. In this regard, data manager 67 is configured to include
aware of the approximate location of the MICU 15 or of the 50 a user data table 68b (FIG. 5) containing contact information
distance of the MTCU 15 from a predetermined point (i.e., pertaining to each user that is to receive a notification
of the proximity of the MTCU 15 from a predetermined message from the data manager 67. In the preferred embodi-
point or location). Consequently, the user can prepare for the ment, the user table 68b is capable of uniquely identifying
arrival of the MTCU 15, since the user knows that arrival of each user of the notification system 10, and has entries that
the MTCU 15 is imminent. 55 specify contact information as:sociated with each user. Each
As an alternative embodiment, the preference data can entry preferably includes a user identification number
define a certain time before the MTCU 15 reaches a desti- unique to each user that identifies the information in the
nation or other particular location (i.e., a proximity of the entry as relating to a particular user.
MTCU 15 from the predetennined point). In this regard, the Each entry preferably includes a value specifYing the
monitoring mechanism 69 is designed to determine the 60 medium through which the user has specified to be con-
location of the MTCU 15 from the travel data stored in Mf tacted. For example, the value can indicate that the user is to
travel data table 68e of database 94. The monitoring mecha- be contacted through e-mail, in which case the entry should
nism 69 is then designed to calculate the time it will take for also include the user e-mail address. Alternatively, the value
the MTCU 15 to reach the location specified by the prefer- can indicate that the user is to be contacted through a
ence data based on the location of the MTCU 15 and the 65 telephone call or a page. In these situations, the entry should
location of the desired destination. In calculating the travel also include the user telephone number or pager number.
time, the monitoring mechanism 69 can be configured to The value can also indicate multiple methods of notification.
Exhibit A
Page 83
US 7,119,716 B2
31
For example, the value can indicate that the user is to be first
contacted via telephone. If there is no answer when the data
manager 67 attempts to deliver a notification message, then
the data manager 67 can be configured to attempt
tion via paging. If paging fails, then the data manager 67 can
be configured to attempt notification through e·mail or other
computer oriented messaging system. Accordingly, the order
of notification media should be indicated by the data in the
user data table 68b, and the contact information
for each method selected (e.g., the telephone number, pager
number, and e-mail address of the user) should also be
included in the entry. lt should be noted that various other
communications media and combinations of communica-
tions media can be employed.
The contact information (and preference data, which will
be discussed in further detail hereinafter) can be manually
entered or downloaded into the user data table 68b in order
to activate a user for the notification system 10. In this
regard, a system operator can receive the contact informa-
tion (and preference data) via a telephone call or e-mail, for
example) and manually enter the information into the noti-
fication system 10.
However, in the preferred embodiment, the contact infor-
mation is automatically entered into the user data table 68b
via a message manager 82, which is depicted by FIG. 5B.
The functionality of the message manager 82 is shown in
FIG. 5D. The message manager 82 is configured to receive,
via communications device 72 (FIG. 1), an activation
request from a user at PCD 75, as shown hy blocks 90a, 90h,
90fof FIG. 5D. In this regard, the request can be transmitted
to PCD 75, via any suitable technique known in the art, and
the BSCU 38 can be configured to include a plurality of
communications devices 72, as depicted by FIG. SA.
Each of these communications devices 72 can be config-
ured to simultaneously communicate with a respective user
of the notification system 10. The information received by
the communications devices 72 can be transmitted to mes-
sage manager 82 (FIG. 5B) via any suitable technique, such
as time division multiplexing, for example. Each user com-
munications device 72 can also be designed to communicate
with different communications media. For example, one user
communications device 72 can be designed as a modem to
communicate with a modem associated with a user. This
user communications device 72 c.:an be designed to send data
configured to prompt the user to return data pertaining to
contact information. An example of such a prompt, could be
a template or web page where the PCD 75 (i.e., a computer
32
communicating via a modem, the message manager 82 is
configured to transmit signals compatible with the user
modem in order to prompt the user to enter the appropriate
contact information. This data could be in the form of a web
page transmitted through the Internet, or the prompt could
simply be messages transmitted through e-mail or some
other data communications system.
When the user is communicating via a PCD 75 in the form
of a telephone, the message manager 82 can be designed to
10 transmit recorded messages to the user. 111e user can then
select or enter data by transmitting signals in
response to the prompting messages, as is commonly known
in the art. The message manager 82 may be configured to
communicate with the user in other formats and media
15 known in the art.
Once the message manager 82 receives the contact infor-
mation from the user, the message manager 82 is designed
to store the contact information as an entry in the user data
table 68b, as depicted by block 90h of FIG. SD. When the
20 monitoring mechanism 69 determines that a user should be
notified of an impending arrival of an MTCU 15, the
monitoring mechanism 69 is designed to send a notification
command to message manager 82. The notification com-
mand may include travel data to be sent to the user, such as
25 data indicating that a particular Mf is a certain proximity
from the destination defined by the preference data. In
response, the message manager 82 is designed to retrieve the
contact information associated with the user from the user
data table 68b and to determine how to contact the user
30 based on the retrieved contact information, as depicted by
blocks 90c and 90d of FIG. SD.
The message manager 82 is then designed to transmit a
message compatible with the medium previously selected by
the user for notification, as depicted by block 90e of FIG.
35 5D. The message can include any travel data sent to the
message manager 82 from the monitoring mechanism 69.
For example, when the contact infonnation indicates that a
telephone call is the preferred medium for notification, the
message manager 82 can send a recorded telephone message
40 to the telephone number that is indicated by the contact
information retrieved from the user data table 68b. If the
monitoring mechanism 69 included travel data indicating the
time of arrival in the command to message manager 82, then
message manager 82 can be configured to include a message
45 indicating the expected time of arrival at a particular loca-
tion. Alternatively, the same information can be sent via
e-mail, facsimile, page or other type of commtmications
medium to the user, depending on the preferences selected in this case) displays the template, and the user can fill in
fields of the template with the appropriate contact informa-
tion. Alternatively, another one of the user communications 50
devices 72 can be designed to receive a telephone call from
by the user during activation.
During activation, the message manager 82 can be further
configured to prompt for and receive preference data (i.e.,
data pertaining to when the user is to be notified) from the
user, as shown by block 90g of FIG. 5D. In this regard, the
message manager 82 can be designed to prompt the user to
a user and to prompt the user to enter data through touch-
tone signaling. Other user communications devices 72 can
be designed to communicate with other types of communi-
cations media known in the art.
Once the message manager 82 (FIG. 5B) receives the
request from the user, the message manager 82 is designed
55 return information indicating which MICU 15 is to be
monitored on behalf of the user and when the notification is
to determine that the request is a request for activation (i,e.,
a request for the user to be entered into the notification
system 10). In response, the message manager 82 transmits 60
data to the user, via user communications device 72, in order
to prompt the user to transmit the necessary contact infor-
mation, as shown by block 90g of FIG. SD. In tbis regard,
the message manager 82 is configured to determine the type
of medium used by the user to communicate the request for 65
activation and to transmit a prompt to the user that is
compatible with this medium. For example, when the user is
to be sent to the user. For example, the user can be prompted
to select an MTCU 15, a destination (or other particular
location), and a notification preference to indicate a time or
distance that the MTCU 15 should be from the selected
destination or other particular location when a notification is
to be sent to the user. In response, the user specifies, through
any known suitable communications technique, which
MTCU 15 the user wishes the notification system 10 to
monitor and how the user wishes to be notified of an
impending arrival of the selected MfCU 15 at the selected
destination. ]f the user knows the coordinate values of the
Exhibit A
Page 84
US 7,119,716 B2
33
destination, the user can simply transmit the coordinate
values to the data manager 67. If the user selects the
destin.:'1tion without supplying the coordinates of the desti-
nation (e.g., the user selects a destination from a list of
locations) then the data manager 67 is preferably designed to s
determine the coordinate values transparently.
In some instances, the user may be aware of the vehicle
number and stop number used by the notification system 10
34
database 94 is desired by the user, as depicted by blocks 88i
and 88j of FIG. 5C. TI1e monitoring mechanism 69 is then
designed to retrieve from the database 94 the desired travel
data and to transmit the retrieved travel data to message
manager 82, as shown by blocks 88k and 881 of FIG. 5C.
In the case where the user desires to know the time and/or
distance the selected MTCU 15 is from the selected location.
the monitoring mechanism 69 is designed to retrieve from
to identify a particular MTCU 15 and destination. For
example, many buses are associated with a commonly
known bus number, and the stops along the bus' route are
associated with commonly known bus stop numbers. The
data manager 67 can be configured to recognize the MTCU
10
MT travel data table 68e of database 94 the coordinates of
the destination specified by the user (if not provided in the
request for travel data) and the current coordinates of the
MTCU 15 of interest to the user. Prior to retrieving this data,
15 and destination associated with the bus number and stop
number entered by the user in order to register the user with 15
the notification system 10.
the monitoring mechanism 69 can be configured to update
the travel data for the MTCU 15 by transmitting an upilllte
request to the MTCU 15 via MT communications device 52.
As depicted by block 90i of FIG. 5D, the message
manager 82 is preferably designed to automatically transmit
to monitoring mechanism 69 the preferences selected by the
user that pertain to when the user is to be notified The 20
monitoring mechanism 69 is designed to store this preferM
ence information in the database 94 and designed to relate it
to the selected MTCU 15.
Once a user becomes activated with the notification
system 10, the user may make changes to the preferences 25
specified by the user, as shown by blocks 9Qj-90m of FIG.
5D. The message manager 82 is configured to receive the
request for changes from the user. The message manager 82
can be configured to request the user to resubmit all contact
information and preference data, as updated, or can be 30
configured to request the user to only submit desired
changes to the contact information or preference data. After
receiving the new data, the message manager 82 is con:figM
ured to update the contact information in user data table 68b
and to send a request to monitoring mechanism 69 to update 35
the preference data relating to the monitoring of travel data.
In response, monitoring mechanism 69 is designed to update
the preference data in database 94, as shown by blocks 88g
and 88h of FIG. 5C.
It should be further noted that as described hereinabove, 40
the preference data and travel data can be automatically
received and stored in the database 94 and selected Mrs 17
can be automatically monitored by the notification system
10.
Similar to the user communications devices 72, a plurality of
MT communications devices 52 may be located at the BSCU
38 in order for multiple MTs 17 to simultaneously commu-
nicate with the monitoring mechanism 69, as depicted by
FIG. 5B. The MT communications devices 52 are configured
to communicate with the monitoring mechanism 69 through
any suitable technique, such as time division multiplexing,
for example.
After receiving the update request via communications
devices 52 and 44, the MT manager 29 is designed to
transmit the current values of the MT travel data to the
monitoring manager 69. By updating the MT travel data
before responding to the user request for travel data, the
monitoring mechanism 69 can ensure the accuracy of the
response transmitted to the user.
After retrieving the coordinate values from the database
94, the monitoring mechanism 69 is designed to calculate
the distance that the MTCU 15 is from the selected destiM
nation based on the coordinate values of the MTCU 15 and
the coordinate values of the destination. If the preference
data and/or request for travel data indicates that the user is
to be notified when the MTCU 15 is a certain time from the
selected destination, the monitoring mechanism 69 is then
designed to determine the estimated time of arrival of the
MTCU 15 at the destination based on this distance. As
described previously, the monitoring mechanism 69 is
designed to either assume that certain distances will take a
2. Requests for Travel Data
In addition to providing the user with automatic advance
notification of an impending arrival of an MTCU 15, the
notification system 10 can also be used to provide the user
with travel data on demand, as depicted by blocks 90n-90p,
90d and 90e of FIG. 5D. In this regard, the user communi-
cations device 72 is designed to receive a request for travel
data from a user: For example, the user may call the
communications device 72 on a telephone and through
touch-tone signaling select, among other options, an option
45
certain amount of time to travel based on the type of traffic
conditions usually encountered on the rottte or to calculate
an average time previously required for MTs 17 of the
system to travel the mute. To increase the accuracy of the
calculations, the route should be divided into sections where
50
the time required to travel each section is independently
calculated. Furthermore, time delays associated with schedM
uled stops or deliveries can be factored into the calculations
by assuming a delay time for each stop or delivery depend-
ing on the type of stop or delivery expected.
to discover the distance and/or time a particular MTCU 15 55
is from the destination specified by the user preference data
After calculating the distance and, if requested, the time
the MTCU 15 is from the destination, the monitoring
mechanism 69 is configured to transmit the calculated values
to the message manager 82. In response, the message
manager 82 is designed to transmit the calculated infonnaM
or specified by the user during the request for travel data.
The user communications device 72 is designed to transmit
the user selections to message manager 82. Based on the
selections, the message manager 82 is designed to determine
that the user message is a request for travel data. In response,
the message manager 82 sends a request to moilltoring
mechanism 69 to retrieve the requested database 94.
The monitoring mechanism 69 is designed to receive-the
request for travel data from message manager 82 and to
interpret the request in order to determine which travel
information from the MT travel data table 68e of the
60 tion to the user via user communications device 72. Since
the user already has an established communications connec-
tion with user communications device 72 when requesting
travel data, there is no need for the message manager 82 to
consult the contact information in the U'!er data table 68h.
65 The message manager 82 can simply transmit the data over
the same connection. However, if desired, the message
manager 82 may consult the contact information in the user
Exhibit A
Page 85
US 7,119,716 B2
35 36
data table 68b to determine the user preferences in
cation and notify the user of the distance and/or time
accordingly.
The message manager 82 then prompts the user to select
certain preferences. For example, the message manager 82
can request the user to identify a particular MICU 15 that
the user wishes the notification system 10 to track and a
particular destination for the selected MTCU 15. If the user
knows the identification number of the MTCU 15 or MT
stop number used by the notification system 10 to identify
the particular MTCU 15 and/or destination. the user can
simply transmit a message including this information. As an
10 example, the bus numbers and/or bus stops of commercial
and state operated buses are usually available to the public.
Therefore, the user may be aware of the bus number and/or
stop number of a particular bus that the user wishes to ride,
and the user can simply transmit the bus number and/or stop
The monitoring mechanism 69 can also be configured to
transmit a command to a mapping system 86 (FIG. SB) to
transmit mapping data to the message manager 82, if the
user request for travel data or user preference data in
database 94 includes a request for a mapping. The mapping
system 86 may be any system known in the art for producing
and supplying a user with mapping data for rendering a
display of a map. The command to the mapping system 86
preferably includes the coordinate values of the MTCU 15
and the destination. In response, the mapping system 86
transmits to message manager 82 mapping data sufficient for
forming a display map with the locations of the MfCU 15
and the destination graphically displayed by the display
map. The message manager 82 is designed to retrieve the
contact information for the user requesting the travel data
and is further configured to determine an address (e.g., an IP
address or other type of address indicating how the mapping 20
data is to be routed to user) associated with the user for
sending the mapping data. The message manager 82 is then
designed to transmit the mapping data to the retrieved
address, which preferably identifies a computer associated
with lhe user. When the: PCD 75 (i.e., a computer in this 25
case) receives the mapping data, the user computer is
configured to render a graphical display depicting a map that
shows the Mf' s location relative to the destination on the
map.
15 number to the message manager 82. Also, the user should be
able to specify other identifying information such as the day
or days of de..o;ired travel and the time of day of desired
travel.
In the embodiment where the user is expecting to receive
a package from a particular delivery vehicle, the user may be
aware of the package number or delivery number used by the
notification system 10. Therefore, by specifying the package
mm1ber and the address that the vehicle is to deliver the
package, the particular MTCU 15 of the vehicle that is to
deliver the package can be located by the notification system
10. In this regard. a database should be defined by the
operators of the notification system 10 that relates package
numbers to MTCU 15 numbers.
Alternatively, if the user is unable to ideritif)' a particular
30 MT or MTCU 15, the message manager 82 can send
information to the user that can be used to help the user
identify a particular MTCU 15. For example, the message
manager 82 can transmit to the user a list of buses or a list
of MT stops to the user. The user can use this information to
If desired, the monitoring mechanism 69 can be· configd
ured to transmit the coordinate values of the MTCU 15 to the
mapping system 86 each time the coordinate values are
updated. The user request for travel data can request this
feature or the user can indicate tllls desire in the preference
data submined during activation. Accordingly, for each
update, the mapping system 86 is designed to transmit
updated mapping data to the user computer 75 via message
manager 82, as previously described. As a result, the posi-
tion of the MTCU 15 "is updated, and the user can monitor
the progress of the MTCU 15 on the display map rendered
by the computer 75.
Although the preferred embodiment illustrates the
requests for travel data by determining the distance the
MTCU 15 is from a particular lOcation or by detennlning the
time tl1e MICU 15 is from the particular location, other
infonnation can be used to indicate the proximity of the
MTCU 15 from the particular location. For example, the
message transmitted to the user in response to a request for
travel data can indicate that the MTCU 15 is currently at
another particular location or landmark, preferably known to
the user. Any other information indicating the proximity of
the MTCU 15 from a particular location can be used
3. Establishing User Preferences
Initially, a user at remote location establishes communi-
cation with the message manager 82 via communications
devices 72 and 73. As used herein, the term "remote loca-
tion" shall refer to any location off the site of the BSCU 38.
The user can establish communication via a telephone, an
e-mail message, the Internet, or any other suitable commu-
nication medium. The message manager 82 preferably trans-
mits a list of options to the user, such as whether the user
would like to activate a monitoring of a particular MT, to
retrieve travel data Jar a particular MT or to modify pref-
erences previously selected by the user in an earlier com-
munication session with the message manager 82. In
response, the user selects the activation option.
35 select a particular MTCU 15 that is suitable to the user.
Also, the message manager 82 can send map data from
mapping system 86 to the user. The user can then view the
map and select points on the map where the user would like
to know when the MTCU 15 reaches the selected point. The
40 points available for selection can be predetermined, such as
scheduled bus stops or other types of vehicle stops, or the
user can be allowed to freely select any point on the map. In
either case, the mapping logic preferably transmits the
coordinates of the selected points to the message manager
45 82, which can use this information to not only identify the
selected destination. but to also choose an appropriate
MfCU 15.
The message manager 82 also prompts the user to enter
contact information such as how the user would like to be
50 notified of an impending arrival of the selected MTCU 15 at
the selected destination. In response, the user selects a
notification medium or combinations of media to be used to
notify the user and supplies the necessary infonnation to
enable communication of the notification. For example, if
55 the user selects a telephone as a notification medium, then
the user provides a telephone number. In addition, if the user
selects a computer as the notification medium, then the user
provides a suitable address for the computer, such as an
e-mail address or IPaddress. If the user selects a pager as the
60 notification medium, then the user provides a pager number.
It should be apparent to one skilled in the art when reading
this that other types of notification media are
possible. After receiving the desired contact information
from the user, the message manager 82 stores the contact
65 information in the user data table 68b.
The message manager 82 also prompts the user to trans-
mit travel data preferences, which is information pertaining
Exhibit A
Page 86
US 7,119,716 B2
37 38
to when the user would like to be notified. For example, the cation should be sent to the user. Alternatively, the moni-
user can select to be notified a certain time before the taring mechanism 69 can be con:figmed to periodically poll
selected MTCU 15 is to arrive at the selected destination. each ently in the MT data table 68a and to compare the
Also, the user can choose to be notified when the selected travel data corresponding to each entry with the
MTCU 15 is within a certain distance of the destination, and ing preference data in user data table 68h to determine which
the user can choose to be notified when the selected MrCU users should receive a notification.
15 is a certain number of deliveries or stops away from the In analyzing each entry, the monitoring mechanism 69
destination. preferably subtracts the current coordinate values in the
Since the monitoring mechanism 69 should have access to accessed entry of the MTCU 15 with the coordinate values
the travel data preferences in order to determine when a 10 previously stored in travel data 68e that indicate the
notification is appropriate, the message manager 82 nation location selected by the user. If the resulting value is
ably transmits the travel data preferences to the monitoring less than a predetermined value, then the monitoring
mechanism 69 along with a unique identification number nism 69 sends a notification command to message manager
that identifies the user and a unique identification number 82 instructing the message manager 82 to notify the user of
identifying the selected MTCU 15. The unique identification 15 the impending arrival of the MTCU 15. This predetermined
number identifying the selected MTCU 15 can be the MT value corresponds to the distance that the MTCU 15 should
number entered by the user provided that the number entered he from the destination before a notification is sent to the
by the user identifies the MTCU 15 to be monitored. In tum, user. Preferably, this predetermined value is calculated from
the monitoring mechanism 69 stores this in database 94. or is included in the preference data supplied by the user
Entries associated with a particular MTCU 15 can be related 20 during activation or during an update to the activation.
together in the database 94. For example, each entry The monitoring mechanism 69 can also send the
ciated with a particular MTCU 15 can be stored, and each of cation command to the message manager 82 based on the
the entries can have a pointer pointing to another one of the estimated time the MTCU 15 is from the destination. After
entries associated with the particular MTCU 15. Therefore, calculating the value indicating the distance of the MTCU
entries associated with a particular MTCU 15 can be easily 25 15 from the destination, the monitoring mechanism 69 can
located. Other methods known in the art for categorizing the estimate how long it will take for the MTCU 15 to reach the
entries and correlating the entries with a particular MI or destination by assuming that the MTCU 15 can travel certain
with the travel data of a particular MT are also possible. distances in a certain amount of time. In order to increase the
Once the message manager 82 has received the desired accuracy of the notification system 10, the monitoring
contact information and travel data preferences from the 30 mechanism 69 can vary the time for the distances according
user, the communication between the message manager 82 to the type of traffic that is typically encountered at the MT's
and the user can be terminated. The BS manager 41 should location and route of travel. If traffic conditions are usually
now have sufficient information to monitor the selected congested along the MTCU's route, then the monitoring
MTCU 15. If the user wishes to change the contact mechanism 69 can assume higher rates of time.
mation and/or the travel dftta preferences, the user can 35 more, if the travel data indicates that the MTCU 15 has a
reestablish cmmnunication with the message manager 82. number of MT stops prior to reaching the destination, the
The message manager 82 preferably recognizes the user monitoring mechanism 69 can factor in a delay time for each
requests as an update rather than an activation and prompts stop depending on the type of the stop.
the user to transmit the new information. In this regard, the Once the monitoring mechanism 69 determines the
message manager 82 can prompt the user for all of the 40 MTCU's expected time of arrivaJ at the destination, the
desired contact information and/or preference data, similar monitoring mechanism 69 can determlne whether the user
to the activation session, and simply replace the previously should be notified based on this estimated time. If the
stored contact information and/or preference data, or the estimated time is less than a predetermined value indicating
message manager 82 can prompt the user for only the the desired estimated time of arrival chosen by the user, then
information to be updated and then merely update the 45 the monitoring mechanism 69 sends the notification
previously stored information. mand to the message manager 82.
It should be noted that the information transferred The message manager 82, in response to the notification
between the user and the message manager 82 can be command from the monitoring mechanism 69, retrieves the
interfaced with the message manager 82 through a human contact information from user data table 68b indicating how
operator during the activation session or update session so the user desires to be notified. Utilizing the contact
descnbed here ina hove and during other sessions, which will mation, the message manager 82 then sends a message to the
be described further hereinbelow. The human operator can user at remote location. The monitoring mechanism 69
prompt the user for certain infonnation through a telephone preferably includes certain travel data in the notification
call or other suitable medium of communication and can command, such as the MTCU's location. Consequently, the
enter the response of the user into the message manager 82. 55 message manager 82 is able to include this travel data with
4. Monitoring the MT the message sent to the user. For example, the message may
The monitoring mechanism 69 of FIGS. 5B and 5C, upon indicate that the MTCU 15 (and, therefore, that the MT
receiving travel data from MTCU 15, stores the travel data attached to the MTCU 15) is a certain amount of time or
(in the preferred embodiment, coordinate values) relating to distance from the destination or the message may indicate
the MICU 15, in MT travel data table 68e of database 94 60 the MTCU's specific location, perhaps with reference to
that is configured to contain travel data and is associated street names and/or street blocks.
with the MTCU 15. After accessing an entry for storing If the contact information indicates that the user wishes to
travel data, the monitoring mechanism 69 compares the have map data sent to a computer at the remote location, the
current travel data (either received from the MTCU 15 or message manager 82 sends a request for map data to
selected from a predetermined or assumed set of travel data, 65 monitoring mechanism 69. In response, the monitoring
as described hereina hove) ..... the user preferences stored in mechanism 69 sends to the mapping system 86 the necessary
user data table 68b in order to determine whether a data (e.g., the coordinates of the MTCU 15 and the
Exhibit A
Page 87
US 7,119,716 B2
39
nation) for the mapping system 86 to transmit the appropri-
ate mapping data. The mapping system 86 transmits the
mapping data to message manager 82 which again utilizes
the contact infonnation retrieved from user data base 78 to
communicate the mapping data to the appropriate PCD 75 at
remote location. The PCD 75 then displays the mapping data
in graphical fom1 so that the user can see the Mf's location
relative to the destination within the map graphically dis-
played by the PCD 75.
40
TI1e message manager 82 then transmits a request for data
to· the monitoring mechanism 69. The request for data
includes the unique identification number used to identify
the Mrcu 15, as well as any other information needed by
the monitoring mechanism 69 to provide the desired infor-
mation. For example, the message manager 82 may also
transmit infonnation indicating that the user wishes to
discover information pertaining to the type of :MT that is en
route. 111e monitoring mechanism 69, ln tum, retrieves the
desired travel data from the database 94.
After retrieving the desired travel data, the monitoring
mechanism 69 transmits the retrieved data to the message
manager 82, which communicates the data information to
'llle notification message sent to the user indicates the 10
impencting arrival of the MTCU 15 at the destination pre-
viously selected by the user. Accordingly, the user can
prepare for the arrival of the MTCU 15 knowing approx1-
mately how long it should take for the MrCU 15 to arrive
15
the user in a message transmitted to the user. The message
can include the travel data retrieved by the monitoring
mechanism 69 or can be fanned to indicate the information
contained by the travel data. For example, when communi-
cation is over a telephone connection, a recorded message
at the destination.
Note that U.S. Pat. No. 6,317,060, which is incorporated
herein by reference, describes a communication handler that
can be implemented in or in connection with the manager 41
for enabling communication of a large number of concurrent
or substantially concurrent notification commmrications 20
(perhaps due to a large number of vehicles and/or users).
can be fanned by the message manager 82 indicating the
distance the MICU 15 is from the destination based on the
travel data sent to the message manager 82. When commu-
nication is via modem signals, travel data can be transmitted
to the user by the message device 82. In either case, the
5. Requesting Travel Data
contents of the message is based on the travel data retrieved
by the monitoring mechanism 69. Since a communications
line between the user and message manager 82 is already
established in order for the user to make the request for
travel data, the message manager 82 preferably transmits the
data to the user over the established communication con-
nection. When the user desires to receive map data (indi-
cated by the selection of an option during the request for
travel data or by the user preferences stored in the database
94), the monitoring mechanism 69 transmits a map genera-
During the monitoring process described hereinabove, the
user can discover the status of the MTCU 15 or of the MT
attached to the MTCU 15, on demand, by contacting the BS 25
manager 41 and requesting information pertaining to the
travel data-stored in the database 94. In this regard, the user
establishes communication with the message manager 82
(FJG. 5B) via communications devices 72 and 73. The
medium used for communication can be any suitable 30
medium known in the art (e.g., telephone, ewmai1, Internet,
cellular phone, etc.). The preferred will be discussed herew
inafter with the user establishing communication via tele-
phone, although other media of communication are also
suitable.
35 tion command and travel data of the selected MfCU 15 to
mapping system 86. Mapping system 86 then transmits
graphical data to message manager 82.
After the telephone connection is established, the message
manager 82 prompts the user with a series of recorded
questions or options in order to determine the user request.
The user responds to these prompts through touchwtone
signaling which is well known in current telephony com-
munications systems. Initially, the message manager 82
prompts the user to indicate whether the call is an activation,
Message manager 82 communicates the graphical data to
PCD 75 which is capable of generating a map display based
an update of an activation, or a request for travel data. The
user selects the appropriate touch-tone number to indicate
that the user is requesting travel data.
40
on the graphical data. In order to communicate this data, the
message manager 82 retrieves the user contact information
from the user data table 68b. The contact information
indicates the address (and/or other pertinent information) of
the PCD 75 so that the message manager 82 knows where to
'The message manager 82 receives and interprets the
touch-tone signal to determine that the user is requesting
travel data. In response, the message manager 82 prompts
the user to transmit an identification number of the MTCU
45
transmit the graphical data. By viewing the map display
generated by the PCD 75, the user can determine the
location and estimated time of arrival of the MTCU 15. The
map display preferably shows the intended route of travel by
15 of concern for the user. 1bis prompt can include infer- so
mation to aide the user in selecting an MTCU 15. The user
responds by transmitting a series of touch-tone signals that
indicate the identification number or other unique data of the
particular MTCU 15 of concern for the user. TI1e message
manager 82 receives and interprets the touch-tone signals 55
and determines which MTCU 15 is selected by the user
based on the received touch-tone signals.
1be message manager 82 can then, if desired, prompt the
user to indicate which travel data the user desires to know.
For example, it is likely that the user may want to know how 60
far the MTCU 15 is from the destination or how long it
should take the MTCU 15 to arrive at the destination.
However, the user may want to know other infonnation,
such as, but not limited to, how many MT stops the MTCU
15 encounters en route or the type ofMTthat is en route, etc. 65
The user responds with touch-tone signals. as appropriate, to
indicate what information the user is requesting.
the MTCU 15 and any scheduled MT stops along the route.
Since the notification system 10 stores certain travel
information in order to monitor the travel of an MTCU 15
for providing an advance notification of an impending
arrival of an MTCU 15, the notification system 10 can also
provide an easy and low cost way for a user to access
information pertaining to the MTCU 15, on demand.
Accordingly, the user does not have to wait for preselected
preferences to be satisfied before learning of the MfCU's
(and, therefore, the MT's) location and/or estimated time of
ani val. The 11SCr can monitor the travel of the MTCU 15 at
any time by submitting a request for travel data and can,
therefore, know the location and status of the MTCU 15
before receiving an advance notification signal that is based
on comparisons between the MTCU's travel data and the
user preselected preferences. As a result, the user can better
prepare for an arrival of any particular MTCU 15 or MT
attached to the MTCU 15 associa1ed with the notification
system 10.
Exhibit A
Page 88
US 7,119,716 B2
41
It should be apparent to one skilled in the art that at least
a portion of the functionality of the data manager 67 can be
implemented by the MT manager 29, if desired. In this
regard, preference data and/or travel data for the MTCU 15
can be stored in the computer system 31a coupled to the
'MTCU 15. Accordingly, it is possible for the MT manager
29 to determine when to transmit a notification to the user
and to transmit a notification to the user via conununication
device 52 and 72. However, such an implementation can
increase the complexity- and cost of the notification system
10 and is therefore generally not desirable.
L. Alternative Embodlment for Communications
U.S. Pat. No. 5,732,074, which is incorporated herein by
reference, describes systems for enabling communications
between mobile vehicles and a remote computer, via stan-
dardized network communications links. In one embodi-
ment, the Jinks include the Internet and a controller area
network used in vehicles. A TCP/IP stack is implemented in
the controller. In another embodiment, each of the vehicles
has an Internet address or designation associated with it.
The systems and methods described in this patent can be
employed in connection with a notification system 10 and
can be implemented to accomplish the many features
described in this document.
M. Response Systems/Methods
Response systems (and methods) are provided for notifi-
cation systems. Several nonlimiting exemplary embodi-
ments of possible response systems will be described in
detail hereafter.
The architecture of one such embodiment, among others,
is sho\Vll in FIG. 6 and is generally denoted by reference
numeral 100. Although not limited to this particular imple-
mentation, this response system 100 is implemented in the
notification system 10 of FJG. 1.
1. Response System Feedback Analyzer
42
is possible to have special purpose digital or analog hard-
ware designed to implement the same or similar methodol-
ogy, and such hardware could be associated with the BSCU
40.
In this embodiment, the initiating step 101 is performed
by the transmitter 72 associated with the BSCU 40 (FIG. 1),
under the control of the response system feedback analyzer
lOOa associated with the BS manager 41. The notification
communication passes through the network 55 (FIG. 1) to
10 the receiver 73 (FIG. 1) associated with the PCD 75.
The response from the notification-receiving party is first
produced by a party associated with the PCD 75. The
response is electronically recognized by a response system
feedback mechanism lOOb of the PCD 75. The response
15 system feedback mechanism lOOb causes the transmitter 73
(FIG. 1), also associated with the PCD 75, to communicate
suitable feedback data, which ultimately is communicated in
some form to the response system feedback analyzer 100a.
In one embodiment, among other possible embodiments,
20 the PCD 75 is a conventional and commercially available
touch-tone telephone, and the response can be accomplished
by having the notification-receiving party depress one or
more appropriate keys on the keypad associated with the
telephone. In this embodiment, the response system feed-
25 back mechanism 100b is already built into the telephone, in
the sense that there are already on-board the phone, system
components for recognizing keypad keys that are depressed
and for generating dual frequency tones that can be carried
across the communications medium. Also, the telephone is
30 equipped with a transmitter 73 for communicating the dual
frequem.-y tones. In this embodiment, the BSCU 40 is
equipped with a receiver 45 (communicatively coupled to
local interface 33b of FIG. 3) for receiving and decoding the
dual frequency tone that results from depression of a tele-
35 phone button. Such receivers/decoders 45 are well known in
the art of telephony and are readily commercially available.
For instance, the star (*) button could be assigned for
a. First Embodiment indicating that the receiving party has in fact received the
The response system 100, particularly the response sys- notification conununication. Once the receiving party
tern feedback analyzer lOOa, can be configured to imple- 40 depresses this key and once the BS manager 41 recognizes
ment the following methodology, as is summarized by flow that it has been depressed by detecting this event, then the
chart in FIG. 7A: causing initiation of or monitoring a BS manager 41 can definitively conclude receipt of the
notification communication to a PCD 75 associated with a notification communication by the party associated with the
party, as shown in block 101 of FIG. 7A; and during the PCD 75.
notification communication, receiving a response from the 45 More than one key can be used to convey multiple
party via the party's PCD 75, indicating that the party instructions or indications from the notification-receiving
associated with the PCD 75 has received notice, as indicated party to the BS manager 41. The BS manager 41 can be
by block 102 in FIG. 7A. The response can be produced by equipped with an instruction lookup mechanism 84, for
any system or method that verifies that any party or one or example, a lookup table, database, or other mechanism for
more specific parties received the notification communica- 50 identifying what each received key stroke means.
tion. Some such systems and/or methods can accomplish In some embodiments, more than one party may have
this by verifying or detecting the physical presence of such access to the PCD 75,. and it may be desirable to give each
party(ies) at the PCD 75. Some such systems and/or methods party their own personal code of one or more keys, so that
can accomplish this by having the notification-receiving when a response is given by a party, the party can enter
party exercise a physical action that can be converted to an 55 his/her own personal code, and the BS manager 41 will
electronic signal and communicated back to the notification therefore be advised as to which party actually received the
system 10. notification.
Although not necessary for implementation, the foregoing In another embodiment, the PCD is a conventional tele-
methodology can be implemented, and in the preferred phone and the BSCU 40 is equipped with voice recognition
embodiment is implemented, by software associated with 60 software. The receiving party confirms receipt of the noti-
the message manager 82 (FIG. 5B), the monitoring mecha- fication communication with any suitable voice command,
nism 69 (FIG. 5B) and/or the data manager 67 (FIG. SA) for instance, "notification received" Voice recognition sys-
associated with the BS manager 41 (FIGS. 1 and 3). See terns (e.g., lVR) are well known in the art.
response system feedback analyzer in FlGS. 1 and 3. The Jn another embodiment, when the PCD 75 is a computer,
blocks of FIG. 7A essentially represent the high level 65 one or more keys on the keyboard, a mouse click on a button
architecture of such software, i.e., the response system provided in a screen image, etc., can be assigned for
feedback analyzer in FIGS. 1 and 3. Note, however, that it indicating that the receiving party has in fact received the
Exhibit A
Page 89
US 7,119,716 B2
43 44
notification communication. In this embodiment, software at the stop location) is communicated to the PCD 75 during
associated with the computer recognizes the key depression the notification communication. Furthermore, the notifica-
or mouse click and communicates occurrence of same back tion message can indicate to the notified party an option that
to the notification system 10. The software can be a con- can be selected by the notified party to com1ect with and
ventional web browser and the notification communication 5 communicate with the driver of a vehicle or a party at the
could involve sencling an HTML page (or other markup BSCU 40 or another location, in order to enable the notified
language) to the computer that can be operated upon by the party to discuss the content of the work order.
web browser. An applet(s) associated with the HTML page b. Second Embodiment
can cause a window to appear on the computer screen with FIG. 78 is a flow chart illustrating another exemplary
a selectable button, for example, "Notification Received" 10 implementation of a response system feedback analyzer of
and when selected by the mouse, the applet can cause the the present invention, which is optionally implemented as at
browser to return an HTML page from the computer back to least part of the architecture, functionality, and operation of
the notification system 10, which in this case would have a the BS manager of FIGS. 1 and 3. In this embodiment, a
web server that can accept the HTML page response and notified party can cause a connection to be made with a
analyze the content. As an alternative, the response system 15 representative that knows the particulars of or that can
100 could be designed so that any input from an input/output access the particulars of a pickup or delivery of an item or
(I/0) peripheral device connected to the notification-receiv- service in connection with a stop location.
ing party's computer could be recognized as a confirmation In this embodiment, the response system 100, particularly
of receipt by the party of the notification. Also, note that the the response system feedback analyzer 100a, can be con-
response can occur during the same communication session 20 figured to implement the following methodology, as is
as the notification or in a separate communication within a summarized by flow chart in FIG. 7B: monitoring travel data
reasonable time period. in connection with an MT 17 that is destined to pickup or
Any response data, including confirmation of receipt of a deliver (an item or service) at a stop location, as indicated at
notification, that is received by the response system feed- block 105; causing initiation of a notification communica-
back analyzer 100a can be stored, if desired, with party 25 tion to a PCD 75 based upon the travel data (e.g., when the
contact records 86, as shown in FIG. 6, which can take the MT 17 is in close proximity, has just departed a prior stop
form of a table, database, etc. etc.), as indicated at block 106; and dttring the
It is also possible that the response system 100 and the notification communication, enabling a party associated
response system feedback analyzerlOOa can be designed so with the PCD 75 to select whether or not to communicate,
that the party's response indicates that the party associated 30 for example, via voice by way of a telephone or via text by
with the PCD 75 is willing to accept or refuses a task, or job, way of a computer network link, with a party having access
associated with the notification. The task can be virtUally to particulars of the pickup or delivery, as indicated at block
anything that is to be perfOrmed by the party. For example, 107, so that a discussion can be had regarding the particulars
in the context of a taxi service, a BSCU 40 could send a of the pickup or delivery.
notification via a telephone to a taxicab, and a message could 35 In some embodiments, where there is a BSCU 40 asso-
be played over the telephone asking the party if another ciated with the notification system 10, the BS manager 41
party can be picked up at a particular location within a causes communicative coupling between the PCD 75 of the
prescribed time period. The party associated with the taxicab party and a communications device associated with the party
could send a response back to the BSCU 40, indicating having access to particulars of the pickup or delivery. The
either acceptance or refusal of the task, by actuating a key 40 Jatter could be located at a call center, at a place that is local
that is coded to each of these responses. Note that U.S. Pat. to the BSCU 40, etc.
No. 5,945,919, which is entirely incorporated by reference, In some embodiments, where there is a BSCU 40 asso-
describes an automated dispatch system, in which the ciated with the notification system 10, the BS manager 41
response system 100 can be employed. causes communicative coupling between the PCD 75 of the
As another example, consider a public bus transit system 45 party and a PCD 75 associated with the Mf 17 or person in
that communicates bus arrival/departure information to a the MT 17.
PCD 75 and wherein a party can send a response indicating A message can be provided during the notification
receipt of notice and indicating that the party will be a munication that includes a work order or description of the
passenger on the bus. This information would be helpful reason why the stop is being made. This can be very useful
with respect to bus scheduling. 50 in connection with, for example, services to be performed at
It is also possible, in the context of a notification system the stop location. The party being called can communicate
10 employed in connection with a service (e.g., cable with somebody associated with the pickup/delivery service
installation, telephone line installation, etc.) to be performed to correct information that is in error on the work order, add
at a destination, that the response system 100 and the additional tasks to the work order, delete tasks on the work
response system feedback analyzer 100a can be designed so ss order, etc.
that the party's response indicates that the party associated As a further option, the BS manager 41 can be designed
with the PCD 75 needs to have an additional service to enable the party to select an option that indicates to the
performed at the destination or that additional equipment notification system 10 that the work order is proper. For
will be needed at the destination. As an example in the instance, a voice recording over a telephone link may say
context of a telephone line installation, the notified party 60 "Hit the pound key if the work order is accurate or hit the
could indicate that it wishes two lines to be installed instead star key to talk with a representative."' Selection of the pound
of the one which was ordered, so that the telephone service key would confirm to the BS manager 41 the order and the
vehicle operator is notified in advance of the requisite MT 17 would travel to the stop location, as scheduled, and
additional service/equipment. perfonn the requisite pickup/delivery task Selection of the
It is also possible, in the context of a notification system 65 star key would cause the BS manager 41 to connect the
10 employed in'connection with a service to be performed notified PCD 75 with a communications device of a party
at a destination, that a work order (of work to be performed having access to particulars of the pickup or delivery.
Exhibit A
Page 90
US 7,119,716 B2
45
46
c. n
1
ird Embodiment picked up; changing the number of rooms to be carpet
FIG. 7C is a flow chart illustrating yet another exemplary cleaned, changing the level of service (each having a difu
implementation of a response system feedback analyzer of ferent price), etc.
the present invention, which is optionally implemented as at d. Fourth Embodiment
least part ofthe architecture, functionality, and operation of 5 FIG. 7C is a flow chart illustrating still another exemplary
the BS manager of FIGS. 1 and 3. A response from a notified implementation of a response system feedback analyzer
party is used to change one or more tasks associated with a lOOa, which is optionally implemented as at least part of the
pickup or delivery of an item or service associated with a archltecture, functionality, and operation of the BS manager
stop location. ofFIGS.1 and3. In essence, a response from a notified party
In this embodiment, the response system 100, particularly 10 is used to select one of a plurality oftimes for a pickup or
delivery of an item or service to occur at a stop location.
the response system feedback analyzer lOOa, can be con· In this embodiment, the response system 100, particularly
figured to implement the following methodology, as is
the response system feedback analyzer 100a, can be con·
summarized by flow chart in FIG. 7C: monitoring travel data
in comlection with a MT 17 that is destined to pickup or figured to implement the following methodology, as is
15 summarized by flow chart in FIG. 7D: directly or indirectly
deliver an item or service at a stop location, as indicated at
monitoring travel or travel data in connection with one or
block 108; causing initiation of a riotification comrounica· more MTs 17 in order to track them, as indicated at block
tion (which may include a message indicating one or more
114; initiating or engaging in a notification communication
tasks to be accomplished at the stop location) to a personal session with a PCD 75, when appropriate, based upon
communications device based upon the travel data, as indi·
cated at block 109; and during the notification cornmunica* 20 impending arrival or departure of one or more Mrs 17 in
relation to a location as indicated at block 115; during the
tion, enabling a party associated with the personal commu-
nications device to change one or more tasks associated with notification communication session, providing a plurality of
arrival and/or departure times in relation to the location and
the pickup or delivery, as indlcated at block 110. enabling selection of at least one of the times (directly or
The tasks can be stored in and changed within database 94
25
indirectly; the selection can be of an item that is associated
(FIG. SA), particularly in tasks table 68m. The BS manager in some way with the time so that the selection is essentially
41 can be designed to change any of the tasks, based upon indirect), as indicated at block 116; and causing an MT 17
one or more inputs from the notified party. A set of options to arrive at or depart from the location at substantially the
can be provided by the BS manager 41 to the notified party, selected time, as indicated at block 117.
for example, via IVR, text, screen prompts, or otherwise,
30
As for step 114, the arrival or departure times associated
and the party can select one or more of the options. Possible with MTs
17
can be stored and updated in database 94 (FIG.
options are as follows: an option that indicates that the one SA), particularly in MT travel data table 68e. One or a
or more tasks are proper or confirmed (so go ahead and plurality ofMTs 17 can be monitored by the BS manager 41
follow through with the scheduled pichtp or delivery; an for purposes of carrying out this embodiment.
option that enables the party to change the one or more tasks 35 With respect to step 115, the notification communication
or scope thereof; an option to enable adding a task; or an session can be initiated by the BS manager 41 based upon
option to enable deletion of a task. user or system defined preferences stored in database 94
This embodiment has numerous applications. One non- (FIG. SA). User and system defined preferences have been
limiting example (e.g., pizza delivery, package delivery, described elsewhere in this document. The predefined pref-
etc.) involves indicating in a message associated with the
40
erences may include, for instance, (a) a proximity to the
notification communication the amount of a blll and location or (b) a designated location or region that is near the
enabling the notified party to confinn the amount and/or the location at issue and that when encountered by one or more
intention to pay the ammmt when the Mf 17 reaches the stop MTs 17, will result in the communication session.
location for the pickup or delivery. In some embodiments, The arrival or departure t i m e ~ of the one or more Mfs 17
the system can be configured so that the notified party can
45
in relation to the location may be determined, at least in part
make payment during the notification conununication ses- based upon actual travel status information of the MTs 17 or
sian. The BSCU 40 can be designed to prompt the notified at least in part based upon existing scheduling of the MTs 17
party to enter a credit card number to be used to pay the bill. (which may or may not be updated).
The card IUJmber can also be stored in user preferences and As an example of a mechanism for triggering a notifica·
retrieved by the manager 41 pursuant to an appropriate
50
tion in accordance with step 115, the user may indicate that
prompt from the notified party during the notification com- the user would like to receive a notification when a pickup
munication session. vehicle is one hour from arriving at a particular stop loca·
As another nonlimiting example of such an application, tion. The BS manager 41 may determine, based upon the
consider a configuration where a service, such as a telephone monitoring of travel data, that a particular vehicle 17 can
installation, is being provided at the stop location. Further· 55 arrive in one hour or, if a stop is skipped by such vehicle 17,
more, assume that there is a work order for installation of a then the vehicle 17 can arrive in 35 minutes instead of one
single telephone line. An advertisement (from table 68[ of hour. The BS manager 41 can be designed to initiate the
database 94 of FIG. SA) could be provided to the notified notification communication tmder these circumstances and
party during the notification communication that indicates provide the different options during the notification com-
that a second line can be installed for half the price of the 60 munication, one of which can be selected by the notified
first line and for half of the monthly subscription fee. An party.
option to select or deselect the second line installation can be Thus, as can be seen from the aforementioned example,
provided to the notified party. Accordingly, the notified party during the commtmication session, :first and second times
has the ability to add or change the tasks to be performed at may be offered that corresponds substantially with a sched·
the stop location. 65 uled time and a sooner time. Moreover, different fees may be
This idea can be applied to other contexts: changing the charged for selection of the different times. Or, a fee may be
number of goods (e.g., groceries, etc.) to be delivered or charged for selection of the sooner time.
Exhibit A
Page 91
US 7,119,716 B2
47 48
As another example of a mechanism for triggering a tation, the foregoing methodology can be implemented, and
notification in accordance with step 115, the user may in the preferred embodiment is implemented, by software
indicate via user preferences that the user would like to associated with the BS manager 41. The blocks of FIG. 7
receive a notification when a vehicle is one hour from would represent the high level architecture of such software.
departing from a location. The BS manager 41 may deter- Note, however, that it is possible to have special purpose
mine, based upon the monitoring of travel data, that two digital or analog hardware designed to implement the meth-
different vehicles are available, one departing in 15 minutes odology. Such hardware can be easily associated with the
and the other departing in one hour. The BS manager 41 can BSCU 40.
be designed to initiate the notification communication under In this embodiment, the initiating step 111 is performed by
these circumstances to provide the two different options, one 10 the transmitter 72 associated with the BSCU 40 (FIG. 1),
of which can be selected by the notified party. under the control of the response system feedback analyzer
With respect to step 116, the BS manager 41 can be easily 100a of the BS manager 41, The notification communication
designed to provide options to the notified party and to passes through the network 55 (FIG. 1) to the receiver 73
receive selections during the notification communication (FIG. 1) associated with the PCD 75.
session. The set of options can be provided by the BS 15 The response from the receiving party is communicated
manager 41 to the notified party, for example, via voice by the transmitter 73 (FIG. 1), under the control of the
recording, NR, text, screen prompts, or othetv.rise, commu- response system feedback mechanism lOOb associated with
nicated to the notified PCD 75. The notified party can select the PCD 75 that is associated with the receiving party. In one
one or more of the options on the notified PCD 75 via, for embodiment, the PCD 75 is a conventional touch-tone
example, IVR, entering text, pressing touch pad keys to send 20 telephone, and the response can be accomplished by having
a DTMF signal that means something to the BS manager 41, the receiving party depress one or more appropriate keys on
selecting a screen prompt via a mouse or touch screen, the keypad of the telephone 75 to communicate one or more
selecting a link on an HTML screen communicated by the instructions. In this embodiment, the BSCU 40 is equipped
BS manager 41 or a source controlled by or affiliated with with a receiver (communicatively coupled to local interface
the BS manager 41, etc. 25 33b of FIG. 3) forreceiving and decoding the dual frequency
In the case of a plurality of monitored MTs 17, a number tone that results. from depression of a telt"phone button. For
of times can be provided to correspond respectively with the instance, the star(*) button could be assigned for indicating
MTs 17. Furthermore, the notified party can se1ect one of the an instruction from the receiving party. Once the receiving
plurality of times for an MT 17 to arrive at or depart from party depress . . ~ this key and once the response system
the location, which will identifY to the BS manager 41 which 30 feedback analyzer 100a of the BS manager 41 recognizes
one of the MTs 17 should be caused to arrive at or depart that it has been depressed by detecting this event (with
from the location. receiver 72 under the control of the BS manager 41), then the
With respect to step 117, the BS manager 41 can cause, response system feedback analyzer 1 OOa of the BS manager
directly or indirectly, an MT 17 to arrive at or depart from 41 can act upon the instruction.
the location at the selected time by any of a variety of 35 As mentioned previously, more than one key can be used
possible systems and/or methods. One method involves in order to convey one or more instructions from the
having the selected time communicated to a PCD 75 asso- notification-receiving party to the notification system 10.
cia ted with the appropriate MT 17 so that the operator of the Furthermore, the PCD 75 could also be a computer or any
appropriate MT 17 knows of the scheduled arrival or deliv- of the other devices that have been mentioned, or equiva-
ery at the location and can make it happen. In alternative 40 1ents thereof.
embodiments, the steps 114-117 are performed in a PCD 75 As indicated at block 113 in FIG. 8, the response system
associated with a tracked MI 17, in which case the operator feedback analyzer 100a of the BS manager 41 modifies the
will be advised of the scheduled arrival or delivery at the manner in which future notification commtmications are to
location and can make it llilppen. be Sent, based upon the response or content in the response,
i\.nother method in which the BS manager 41 can cause 45 by manipulating data stored in connection with the notifi-
the MI 17 to arrive at or depart from the location at the cation-receiving party contact records 86 (FIG. 6). The
selected time, in a case where the MI 17 can be remotely response system feedback analyzer 100a of the BS manager
controlled, would be to communicate appropriate data or 41 can be configured to modify the manner in whkh future
control signals to the MT 17. notification communications are to be sent in a number of
Tills embodiment has numerous applications, but are not 5o possible ways.
all listed here for simplicity. In one embodiment, among many possible embodiments,
e. Fifth Embodiment when the response system feedback analyzer 1 OOa is imple-
Another embodiment of a response system feedback mented in software, it is designed to maintain one or more
analyzer 100a, among others, is shown in FIG. 8. This records pertaining to one or more parties and one or more
embodiment envisions more than one notification commu- 55 communication methods associated with each party. Any
nication, perhaps regular notifications, occurring between suitable table or database can be maintained to store this
the notification system and a party, and enabling a party to information, if desired. In this embodiment, this data is
influence how future notification communications are to stored in party contacts records 86 (FIG. 6). At this step in
occur, after the first one, This response system feedback the process, after receiving the response from the notifica·
analyzer lOOa can be summarized by the following steps: 60 tion-receivlng party, the response system feedback analyzer
initiating a first notification communication to a PCD as so- 100a associated with the BS manager 41 modifies these
ciated with a party) as indicated by block 111 in FIG. 8; records, based upon the notification-receiving party's
receiving a response communication from the party's PCD, instructions in the response, to store/create modified contact
as indicated by block 112 in FIG. 8_: and modifying the data, in order to affect changes in the manner in which future
manner in which future notification communications are to 65 notification communications are communicated.
be sent to the party, based upon the response, as indicated by By its instructions, the notification-receiving party can,
block 113 in FIG. 8. Although not necessary for implemen· among other things, change the party(ies) to which notifi·
Exhibit A
Page 92
US 7,119,716 B2
49 50
cation communications are sent in the future, change the
MT(s) that is monitored by the notification system 10,
change the proximity parameter that provokes a notification
communication, change the MT stop location that is used by
the notification system 10 to provoke a notification commu- 5
nication, change the notification communication method
and/or PCD, change a notification communication to a later
time based upon a time of day or time period, cancel
initiation of one or more scheduled future notification com-
As another example, the response system 100 and the
response system feedback analyzer lOOa may be designed so
that an instruction may be used to advise the notification
system 10 that the notificatimNeceiving party would like to
receive a status message in future notification communica-
tions, indicating the status of travel of the MT 17. For
example, in fumre notifications, the status message may
indicate the location of the MT 17 or the proximity (distance
and/or time) of the MT 17 with respect to a location.
municatioru;, etc.
FIGS. 9A through 9C illustrate, pictorially, notable
limiting examples of ways in which the response system
feedback analyzer 100a of the BS manager 41 can cause the
notification system 10 to modify the manner in which futtrre
notification communications are communicated bv the noli·
fication system 10. •
As illustrated in FIG. 9A, the response system feedback
analyzer 100a associated with the BS manager 41 may he
designed to cause the notification system 10 to modify
contact data after receiving the response, as indicated in
block 121, and to cause the notification system 10 to initiate
one or more other future notification communications in
10 As another example, the response system 100 and the
response system feedback analyzer lOOa may be designed so
that an instruction may be used to advise the notification
system 10 that the notification-receiving party would like to
receive directions to a site associated with the notification or
15 an advertisement played during the notification. In this
embodiment, the BSCU 40 can be communicatively coupled
to suitable map software. To further illustrate this concept,
a couple of specific examples are described hereafter.
As a first example consider a scenario where a telephone
20 message advises a taxicab driver to: "Pick up at 325 East
Broad Street. Confirm by pressing pound. If you need
directions, press the star key." The system could be configa
ured so that the response system feedback analyzer lOOa
recognizes the # key as a confirmation that the driver has in
25 fact received the notification and recognizes the * key as a
desire to receive directions. In this case, the response system
For example, the response system feedback analyzer lOOa
associated with the BS manager
41
can be configured to feedback analyzer lOOa would access direction information
accordance with, or based upon, the modified contact data
resulting from the notification-receiving party's response, as
indicated in block 122.
from the map software and forward the direction infonna-
cause the notification system 10 to wait a time period before
tion, or a part thereof, to the driver, during the original
sending another communication to the recejving party. The
30 notification communication or in a subsequent communica-
time period may be predefined or maybe be dynamically
tion.
programmable. The receiving party may define the time
period in his/her response, for example, by selecting an As a second example consider a scenario where a message
sent to a computer advises a person that: ''Your UPS package
appropriate keypad or keyboard button in the case of a
telephone or computer, respectively. The instruction may has arrived and is ready to be picked up at 325 East Broad
indicate to the respon....;;e system feedback analyzer
100
a 35 Street. Confirm by pressing the one key. Pizza Hut is next
door, and if you press the two key now, you w111 receive a
associated with the BS manager 41 that the notification-
receiving party cannot handle any further notifications for a free beverage." The system could be configured so that the
predetermined time period, such as So minutes, because the response system feedback analyzer 100a recognizes depres-
party now attends to a task (e.g., Wlloading or loading an sian of the 1 key as a confirmation that the person has in fact
item from an Mn resulting from the first notification. The 40 received the notification and recognizes depression of the 2
task may even be identified in the key as a desire to receive the discount. 1n this case, the
response system feedback analyzer 100a could be designed
party's response. Accordingly, the
party can influence how the BS manager
41
handles future to subsequently send a coupon electronically to the person
notifications to the particular party. via the computer, which could then be printed and Laken by
45 the person to the Pizza Hut to receive the discount.
As another example, the response system feedback ana- As illustrated in FIG. 98, the response system feedback
lyzer 100a associated with the BS manager 41 can be analyzer 100a associated with the BS manager 41 may be
configured to cause the notification system 10 to wait for the designed to cause the notification system 10 to modify
Mf 17 to move a prescribed distance or come within a contact data, as indicated in block 131, to refrain from
predetermined proximity of a location before sending so sending notification communications to the party's PCD 75
another communication to the notification-receiving party. after receiving a response, as denoted in block 132, and to
As another example, the response system 100 and the initiate one or more other future notification communica-
response system feedback analyzer 1 OOa may be designed to tions to the party and/or one or more other parties, using one
enable the notification·receiving party to advise the response or more different communication methods, based upon the
system feedback analyzer lOOa to communicate one or more 55 modified contact data, as denoted in block 133. The com-
future notifications to one or more different parties that have munication methods, may include for example,. but not
assigned devices 75, in addition to the notification receiving limited to, contacting the same or a different cellular or
party or instead of same. land-line telephone, sending an internet email, sending a
As another example, the response system 100 and the wireless text message to a PDA, sending a navigation screen
response system feedback analyzer 1 OOa may be designed so 60 to a computer, sending a notification signal and/or message
that the response may indicate to the response system to a television (TV) or computer via a cable modem or
feedback analyzer 100a associated with the BS manager 41 satellite modem, sending a notification signal and/or rues-
that the notification-receiving party will be changing loca- sage via telex, communicating a message via radio
tions. Therefore, the BS manager 41 should contact a ceiver, etc.
different PCD 75 in connection with future notifications that 65 As a specific example of the overall process, the receiving
is situated where the party will be in the future, for example party may indicate in the response that any future commu-
but not limited to, a different telephone in a different facility. nications should be forwarded to a different communications
Exhibit A
Page 93
US 7,119,716 B2
51 52
instance, a fingerprint scanner, a retina scanner, and/or key
insertion authentication could potentially be employed to
verify the appropriateness of the party to produce a response.
Finally, as denoted at block 153 of FIG. 10, the PCD 75
communicates the party's response to the notification sysw
rem, or in this example, the BSCU 40. The response may
confirm receipt of the notification, may indicate to the BSCU
40 that tl1e notified party would like to have a discussion
PCD 75. For example, in the case of a touch-tone telephone,
the "#"button may be assigned to indicate that the party bas
in fact received the notification, and the "5" button could be
assigned to the fWlction of indicating that the communica-
tion method is to be changed. Furthermore, having the party
depress the "2" key after depression of# and 5, could be
used to advise the BS manager 41 that communication
method 2, corresponding to a computer, should be used in
the future.
As a further option, the response system 100 and the
response system feedback analyzer 1 OOa can be designed to
enable a party to define times (times of day, days of the
week, etc.) for use of each future communications method or
PCD 75.
10
(oral, text, or otherwise) with somebody who has access to
the particulars of the pick"Up/delivery, may enable the notiw
fied party to change one or more tasks (or scope thereof)
associated with the pickup or delivery, and/or may indicate
the mallil.er in which future notification communications
As illustrated in FIG. 9C, the response system feedback 15
analyzer lOOa associated with the BS manager 41 may be
designed to cause the notification system 10 to modify
contact data, as indicated at block 141, to refrain from
sending notification communications to the party's PCD 75
after receiving a response, until the detection of one or more 20
events, as indicated in block 142, and then to monitor for
occurrence of the one or more events, as indicated in block
143, and then to cause the notification system 10 to initiate
one or more other future notification communications to the
party and/or one or more other parties, using one or more 25
communication methods, as denoted at block 144. The one
or more events can include, for example but not limited to,
detection that the MT 17 is about to arrive at, is at, and has
left a particular location or has moved a prescribed dlstance,
manual or automatic actuation of a switch on the MT 17 or 30
at a location where the :MT 17 visits, a certain time of the day
has been achieved, a time period has lapsed since the last
notification conununication, cancellation of a package delivw
ery or pickup, cancellation of an expected stop of an MT 17
at a stop location, delay of an expected stop of an MT 17 at 35
a stop location, anOther communication from the party
indicating that future notifications are welcome, etc. Detecn
tion may occur by actually monitoring travel of the Mf 17
should be communicated to the party, as will be further
described below.
N. Response Failure ·States
The notification system 10, such as the manager 41 of the
BSCU 40, can be designed to implement failure states in
connection with a request for a response. A failure state
occurs when a state of a variable has been reached without
receiving a response back from a notified party or PCD 75.
Internally, a failure state causes the system 10 to terminate
notification communication attempts and/or to take one or
more actions to accommodate the failure to receive a
response. A failure state can also be shown on a screen or
othenvise indicated to the operator of a PCD 75 (see FIGS.
25A through 25D; the one being tracked and/or the one
being notified). A fi:nlure state can be systenHiefined or
userwdeiined, and can be stored in user data table 68b (FIG.
SA) and/or failure state data table 68/ (FIG. SA).
A set ofnonlimiting examples of failure state variables are
as follows: (a) a time period variable (FIG. 25A) pertaining
to the amount 9f time that has elapsed since invocation of the
notification; when the time period variable has expired, it
triggers a failure state in the PCD 75k; (b) a distance variable
pertaining to the distance traveled by the tracked PCD 75k
(FIG. 25B) since invocation of the notification; when the
or by reviewing data corresponding with travel.
2. Response System Feedback Mechanism
FIG. 10 shows the high level steps taken by the PCD 75
in connection with the foregoing embodiments of the
response system feedback analyzer lOOa. Some devices 75
may already be configured with the appropriate flmctionalw
40
PCD 75k has traversed a prescribed distance that is moni·
tared with the distance variable, then a failure state can be
invoked in the moving/tracked PCD 75/c, (c) a predeterw
mined location variable (FIG, 25C) pertaining to a location
ity, while others may need to be configured to exhibit the 45
functionality and operate as shown in FIG. 10. For example,
in the case where a conventional touchwtone telephone is to
be used as the PCD 75 and where dualwfrequency key stroke
tones are to be used to convey instmctions to the BSCU 40,
the telephone already has the requisite functionality to so
perform the steps illustrated in FIG. 10.
First, the PCD 75 receives the notification communication
from the BSCU 40, as denoted by block 151 in FIG. 10.
Accordingly, the party associated with the PCD 75 is given
a notification with respect to the MT, e.g., the mobile MT 17. 55
Next, the PCD 75 receives an input response, e.g., d e p r e s ~
sian of one or more keys, a voice command, swiping of a
magnetic strip of a card through a card reader, etc., from the
party associated witl1 the PCD 75, as indicated at block 152
of FIG. 10. The input from the parry to the PCD 75 can be 60
manually or automatically accomplished, hut it is desirable
to implement a mechanism that shows that the party that is
supposed to be associated with the PCD 75 has received the
notification communication by way of the PCD 75.
For security, it may be desirable to have the notification- 65
receiving party identified (perhaps even ulliquely identified)
as one who is authorized or permitted to send a response. For
to be traversed by the moving/tracked PCD 75k, in other
words, once the PCD 75k determines that it has reached this
predetermined location, then a failure state will result; and
(d) an acceptance variable (FIG. 25D) which tracks the
number of responses and/or acceptances associated with
notification communications; this is useful in a configuration
where a number of parties have been invited to visit a
particular location (e.g., a restaurant), and there are only a
limited number of openings; as an example, the system can
be set to accept the first party to respond to the notification
and invoke a failure state in connection with all other
notifications (which can be communicated, if desired, to the
other PCDs 75 that responded late).
Once a failure state has been determined by the manager
41, the manager 41 may be designed to implement one or
more of the following actions: look for additional instrucw
tions to notify the next person on a contact or route list, try
different contact information for the same individual, or
utilize this information to rewroute drivers to another destiw
nation; automatically notify another user of this failure state
event; and/or automatically notify third party companies
providing additional services, such as but not limited to,
transportation services, that there has been a notification
failure.
Exhibit A
Page 94
US 7,119,716 B2
53
0. Advertisement Methods of Doing Business In Connec·
tion With Notification Services
Various advertisement methods of doing business can be
implemented in cmmection with the notification services, for
example, those described hereinbefore.
One such advertisement method of doing business, among
others, is illustrated in FIG. 11 and can be broadly summa·
rized by the following steps (not necessarily in this order):
54
practiced in connection with this method. For example, the
fee may be charged for each advertisement in each n o t i f i ~
cation, for a block of advertisements, or for the advertise-
ment service in general. As yet another example, a discount
on the advertisement service may be offered or extended
based upon a purchase of a predetermined number.
In alternative embodiments, the stop location of the Mf
(a) monitoring travel data associated with an Mf 17, as
indicated by reference numeral161; (b) contacting a party 10
based upon the travel data, as indicated by reference numeral
162; (c) providing an advertisement to the party substan-
tially during the contact, as indicated by reference numeral
163; and (d) charging a fee or monetarily benefiting from
providing the advertisement, as indicated by reference 15
numeral 164. There are various alternatives and optional
steps that may be practiced in connection with this method.
For example, the fee may be charged for each advertisement
17 and/or the location of the user and/or PCD 75 can be
determined and taken into account with respect to adver-
tisements. See next section for a discussion of the location
determination of the user, PCD 75, and/or stop location.
With this location information, the advertisements can be
selected based upon the geographical location of the user,
PCD 75, and/or stop location. As an example, advertise-
ments can be sorted in a database based upon the geographi-
cal areas to which they pertain. Then, if it is determined that
the PCD 75 or that the stop location is near the intersection
of First Street and 1 ryn Street, then the advertisement data-
base can be accessed for those advertisements that pertain to
the vicinity around First Street and 10
1
n Street. For instance,
the database might include an advertisement about Pizza
Hut, and there might be a Pizza Hut that is located one block
from this intersection. In this case, the manager 14 may be
designed to select the Pizza Hut advertisement and commu-
nicate this to the PCD 75 because the PCD 75 is in close
proximity to the Pizza Hut that is at issue. Also, the system
may be designed to forward directions to the Pizza Hut to the
PCD 75 before, during, or after the advertisement is effec-
tuated at the PCD 75.
in each notification, for a block of advertisements, or for the
advertisement service in generaL As yet another example, a 20
discount on the advertisement service may be offered or
extended based upon a purchase of a predetermined number.
An advertisement database 68f(FIG. 5A) can be disposed
within'the BS manager 41 or communicatively coupled to
same to enable the manager 41 to initiate an advertisement 25
at an appropriate time during a communication with a PCD
75. The advertisement can be conveyed by voice commu-
nication, by text commllllication, by visual presentation on
a screen (e.g., an email with an accompaOying advertise-
ment, etc.), or by other means.
Another advertisement method of doing b11siness, among
others, is illustrated in FIG. 12 and can be broadly summa-
rized by the following steps (not necessarily in this order):
(a) enabling a party to indicate a willingness to receive one
30
or more advertisements during a notification regarding an 35
MT 17, as indicated by reference numeral171; (b) providing
a notification communication involving travel status of the
MT 17, as indicated by reference numeral172; (c) providing
an advertisement as part of or accompanying the notification
communication, as indicated by reference numeral173; and 40
(d) charging a fee for or monetarily benefiting from provid-
ing the advertisement, as indicated by reference numeral
174. There are various alternatives and optional steps that
may be pracficed in connection with this method For
example, the tee may be charged for each advertisement in 45
each notification, for a block of advertisements, or for the
advertisement service in general. As yet another example, a
discount on the advertisement service may be offered or
extended based upon a purchase of a predetermined number.
Yet another advertisement method of doing business, 50
among others, is illustrated in FIG. 13 and can be broadly
summarized by the following steps (not necessarily in this
order): (a) enabling a party to indicate a willingness to
receive one or more advertisements during a notification
regarding an MT 17, as indicated by reference numeral18l; 55
(b) providing a notification communication involving travel
status of the MT 17, as indicated by reference numeral182;
(c) charging a fee or monetarily benefiting from providing
the notification communication, as indicated by reference
numeral183; (d) providing an advertisement as part of or 60
accompanying the notification communication, as indicated
by reference numeral 184; (e) charging a fee for or mon-
etarily benefiting from providing the advertisement, as indi-
cated by reference numeral185; and (f) providing a discount
based upon the party's willingness to receive the one or 65
more advertisements, as indicated by referencenumera1186.
There are various alternatives and optional steps that may be
In alternative embodiments, the timing of the notification
communication may be taken into account When advertise-
ments are selected from a database for communication to the
PCD 75. For example, the hours when a store is open may
be tracked in the advertisement database. Further, when a
notification commllllication is initiated, it may be desirable
to refrain from communicating those advertisements that
pertain to stores that are closed at the time of the notification
communication. In this case, the manager 41 could be
designed to prevent such advertisements to occur during
prescribed time periods. Moreover, the converse could be
designed into the system, i.e., the system could be de.o;igned
so that advertisements pertaining to those stores that are
known to be open at the time of the notification communi-
cation are communicated to the PCD 75.
In alternative embodiments, information regarding a noti-
fication-receiving party, for example, a personal profile in
user data table 68b indicating interests, activities, historic
information regarding prior purchases, traveling, etc., may
be stored in memory and used to make decisions regarding
which advertisements to communicate to the PCD 75.
In alternative embodiments, diSCOllllt awards can be coma
municated to the notification.-receiving party. For example,
an image of a discount coupon could be forwarded to the
PCD 75 that has a screen, which can be printed or shown by
the user to the business establishment to which it pertains, in
order to obtain the discount. As another example, a discount
code can be fonvarded to the PCD 75 via voice or text,
which can be communicated by the user to the business
establishment to which it pertains, in order to obtain the
discount. TI1e discount code can be predefined by the
business establishment and communicated to the notification.
system 10, which can store it in the memory 30b
1
such as in
association with advertisement data table 68f
In alternative embodiments, the waiting times associated
with retail establishments, for example but not limited to,
restaurants, are monitored with periodic communications
between a PCD 75 associated with such retail establishments
Exhibit A
Page 95
US 7,119,716 B2
55
and the BS manager 41. Furthermore, these waiting times
can be communicated with advertisements involving such
retail establishments to the notified PCD 75.
P. Stop Location Detem1ination Systems and Methods Based
Upon User and/or Device Location Feedback
Stop location determination systems (and methods) 190
that utilize user and/or device location feedback can be
implemented in connection with the notification systems, for
example, those described hereinbefore. Several nonlimiting
10
exemplary embodiments of possible stop location
nation systems (and methods) 190 will be described in detail
hereafter. Although not limited to this application, such stop
location determination systems 190 are particularly useful in
connection with transportable PCDs that are carried with a
15
mobile person, as will be clear from the discussion hereafter.
1. First Embodiment
The architecture of one such embodiment, among others,
is sl1own in FIG. 14A and is generally denoted by reference
numera1190a. Although not limited to this particular con-
20
figuration, in this embodiment, the stop location determina-
tion system J90a is implemented in the notification system
56
munication when the MT 17 is an acceptable proximity,
perhaps a predetermined proximity or system-defined or
proximity, with respect to one or more stop
locations, or has just passed one or more stop locations.
As another alternative, the BS manager 41 can be
designed to cause initiation of the notification communica-
tion when the MT 17 has already traveled a predefined time
period or distance along a predefined route.
As another alternative, the BS manager 41 can be
designed to initiate a first notification in order to sense the
current location of the PCD 75, make a selection of the stop
Jocation(s) (and perhaps notify the user of the identity of the
stop location(s) during this first notification), and then
provide a second notification communication at a later time,
when the MT 17 is an acceptable proximity to the stop
location (and perhaps notify the user, again or for the first
time, of the identity of the stop location(s) during the second
notification communication).
The location data identifYing the location of the PCD 75
is stored in the database 94, which as mentioned can contain
a PCD data table 68g for storing this information.
10 of FIGS. 1 and 3, particularly the BS manager 41. The
stop location determination system 190a, can be configured The location data identifYing the location of the PCD 75
to implement the following methodology, as is summarized can be generated by a physical action taken by the party
by flow chart in FIG. 14: monitoring travel data associated
25
associated with the PCD 75 or can be generated automati-
with an MT 17, as indicated at block 191; causing the callybythePCD75itselforbyotherremotesensingmeans.
notification system 10 to conununicate a notification involv- As an example of a physical action, the party could be
ing a delivery or pickup task associated with the MT 17 to prompted (e.g., by voice recording) by the BS manager 41
a PCD 75 associated with a party, as indicated at block 192; to enter a digit on a telephone to indicate a geographical
receiving location data from the PCD 75 (ultimately from
30
area. For instance, the voice recording could say, "Press one
the device user, device itself, and/or another source), as if you are located in northwest Atlanta, press two for
indicated at -block 193; determining one or more stop northeast Atlanta, press three for southwest Atlanta, and
locations, based upon the device location data and the travel press four for southeast Atlanta." Obviously, many other
data associated with the MT 17, as indicated at b)ock 194;
35
encoding schemes are possible. In this example, once the
and causing the notification system 10 to communicate an party presses one of these telephone buttons, the BS
identification of the one or more stop locations to the PCD ager 41 via a dual frequency tone decoder is able to
75 so that the delivery or pickup task can be accomplished determine the location of the party and PCD 75.
at the determined stop location, as indicated at block 195. For automatic generation of location data, a location
Note that these steps can occur as part ofthe same
40
sensor 80 can be associated with the PCD 75 to determine
nication session or link or in more than one communication or communicate location data to the BS manager 41 via
transacti011. transmitter 73, network 55, and receiver 72. Although not
.AJthough not necessary for implementation, the foregoing limited to this configuration, in the preferred embodiment,
methodology can be implemented, and in the preferred the location sensor 80 includes a GPS receiver that receives
embodiment is implemented, by software associated with
45
GPS signals from GPS satellites. In at least one configura-
the data manager 67, such as the monitoring mechanism 69, tion, the PCD 75 is a cellular or personal communication
of the BS manager 41. See stop location determination system (PCS) device and the network 55 is a cellular
system 190 in FIGS. 1 and 3. The blocks of FIG. 14 network and has computer-based support functionality and
essentially represent the high level architecture of such processing for receiving location signals from the GPS
software. Note, however, that it is possible to have special
50
receiver and communicating location information to the BS
purpose digital or analog hardware designed to implement manager 41. Examples of such systems are described in the
the same or similar methodology, and such hardware could following patents: U.S. Pat. Nos. 6,360,101; 6,519,466;
be associated with the BSCU 40. 6,453,237; and 5,479,482, all of which are incorporated
In this embodiment 190a, t1
1
e BS manager 41 monltors herein by reference in their entirety.
travel of the MT 17, as previously described, and stores such
55
In alternative embodiments, for automatic generation of
infonnation in the database 94. As mentioned, the database location data, other types of positioning systems may be
94 can employ an MT travel data table 68e for storing such utilized to determine location information for the PCD 75.
information, along with other fields that relate such infor- For example, radar could be used to remotely track the PCD
mation to other data in the same table 68 and in other tables 75 and then the radar system could be designed to convey
68. The tracking can be based ltpon timing, distance, and/or
60
position information to the PCD 75 or the base station
location information. control 1mit (BSCU) 40, for ultimate consumption and
The transmitter 72 associated with the BSCU 40 (FIG.1), analysis by the BS manager 41.
under the control of the BS manager 41, communicates the The BS manager 41 is designed to determine a stop
notification communication. The notification Iocation(s), based upon the location data provided by the
tion passes through the network 55 (FIG. 1) to the receiver 65 PCD 75 and based upon the travel status of the MT 17. The
73 (FIG.1) associated with the PCD 75. The BS manager 41 stop location(s) can be determined based upon any suitable
can be designed to cause initiation of the notification com- set of criteria. The database 94 can be provided with a stop
Exhibit A
Page 96
US 7,119,716 B2
57
location data table 68d for storing stop locations and relating
them to MTs 17 that are further identified in the MT data
table 68a.
As an example, the BS manager 41 may be designed to
determine an exact or approximate midpoint location
between the location of the MT 17 and the location of the
PCD 75 to serve as the stop location. The BS manager 41
can be interfaced with or be designed to include mapping
software (many versions of which are commercially avail-
able at the present time), geographic information system 10
(GIS) software, or an address lookup table to enable the BS
manager 41 to perform the foregoing determination. Map-
ping sofuvare and interfaces thereto are well known in the
art and are commercially available. Also, see U.S. Pat. No.
5,594,650, which is incorporated herein by reference and rs
which describes an example of mapping sofu.vare.
As another example, the stop location(s) may be selected
from a group of predetermined stops (a collection or along
a predetermined route), known intersections, known
addresses, detected locations, locations on a map, etc., that 20
are in an acceptable proximity to the PCD 75 and the MT 17,
at the time that the determination is made.
In some embodiments, a selection among of group of
possible stops can be made by correlating a maximum
device distance requirement (distance benveen the device 25
and a possible s1op location) and a maximum MT distance
requirement (distance between the MT 17 and a possible
stop location) to the group of possible stop locations. One or
more algorithms 98 (FIG. SA) can be provided and stored in
memory for this purpose. For instance, assume that the 30
maximum device distance requirement is set at a mile and
assume that the maximum MT distance requirement is set at
5 miles. Also, assume that the BS manager 41 has deter-
mined, based upon its database, address Jookl.1p table, map-
ping programs, or otherwise, that three locations A, B, and 35
Care possible candidates for the device user to pickup from
or deliver to the MT 17. In this scenario, the· BS manager 41
can be designed to analyze the locations A, B, and C to
determine which meet the requirements. 1t can be designed
to select one or more locations that meets the requirements. 40
The BS manager 41. communicates an identification of
each of the one or more stop locations to the PCD 75 so that
the delivery or pickup task can be accomplished at a stop
location. The identification can be any suitable information
that will enable the device user to travel to the stop 45
location(s), for example but not limited to, street address
information, bus stop location or number, street intersection
location, longitude and latitude coordinates, audio or visual
description of a place, an image of the stop location, a map
image, etc. All of the foregoing can be stored, if desired, in 50
and accessed from the stop location data table 68d (FIG.
SA). Directions to the stop location(s) can also be provided
by the BS manager 41 over the communications link to the
PCD 75. The directions can be stored in memory and
accessed by an appropriate index that is stored in the table 55
68d. Note that computer-based functionality for a notifica-
tion system for communicating a map image to the PCD is
described in U.S. Pat. No. 6,278,936, which is incorporated
herein by reference in its entirety.
58
In alternative embodiments, the BS manager 41 may be
designed to communicate, along with an identification of the
stop location(s), a code to the PCD 75 that will be used by
the contacted party to indicate to a party associated with the
MT 17, for example, a driver of the MT 17, for authentica-
tion purposes so that the party associated with the Mf 17
knows that the party arriving at the stop location is properly
authorized to perform the pickup or delivery. The code can
be stored in and accessed from, for example, the authenti-
cation data table 68h.
In alternative embodiments, the BS manager 41 may be
designed to receive an indication from the PCD 75 that the
party is unwiiiing to perlbrm the delivery or pickup task
associated with the notification; and as a consequence, to
initiate another notification communication to another d i f ~
ferent PCD 75 associated with another party in order to
request assistance in the delivery or pickup task from the
another party. As an example, the BS manager 41 may
prompt the party to press a particular telephone button to
indicate a willingness or unwillingness to accept the respon-
sibility of the delivery or pickup. As another example, the
BS manager 41 may forward an HTML page (or other
markup language) of code to a computer-based PCD 75 that
visually prompts the party to make a selection.
2. Second Embodiment
In further alternative embodiments, as is shown in FIG.
14B, the BS manager 41 may be designed to perform the
following steps: monitoring travel data associated with a
plurality (Mo or more) of MTs 17, for instance, first and
second MTs 17, as shown in block 201; communicating a
notification involving a delivery or pickup task to a PCD
associated with a party, as shown in block 202; receiving
location data from the PCD, as shown in block 203; deter-
mining one or more first stop locations and one or more
second stop locations, based upon the device location data
and the travel data associated with the first and second MTs
17, as shown in block 204; and communicating one or more
identifications for each of the first and second MTs 17 as
well as their respective first and second stop locations to the
PCD so that the delivery or pickup task can be accomplished
at a stop location, as shown in block 205.
In alternative embodiments, the BS manager 41 may be
designed to communicate, an indication of the type ofMT 17
that will stop at each location, for example but not limited
to, whether the MT 17, is a bus, railroad train, tax, etc. This
would enable the notification-receiving party to select which
mode of transportation to utilize.
In alternative embodiments, the manager 41 is designed to
enable the user of the PCD 75 to select which of the stop
locations and/or which of the MTs 17 that the user wishes to
utilize. This can be accomplished using one of the variations
of the response system, which have been described in detail
previously. Furthermore, this selection or information
indicative thereof can be forwarded by the manager 41 to a
communications device, for example, device 44 (FIG. 1),
associated with the selected MT 17, so that the MT 17 is
aware of the pickup or delivery by the user at the selected
stop location. Also, if desired, the manager 41 can be
designed to advise one or more other MTs 17 that they have
not been selected.
Q. Stop Location Determination Systems and Methods
Based Upon Timing Criteria
In alternative embodiments, the BS manager 41 may be 60
designed to communicate, along with an identification(s) of
the stop location(s), an identification of the MT 17 to the
PCD 75. For example, the identification could be a bus
number, visual or audio description, description of the driver
or vehicle type (bus, railroad train, tax, etc.), etc. The 65
foregoing information can be stored in and accessed from
the MT data table 68a (FIG. SA).
Stop location detennination systems (and methods) 190
that utilize timing criteria (system defined or user defined via
user preferences) can be implemented in connection with the
notification systems, for example, those described herein-
Exhibit A
Page 97
US 7,119,716 B2
59
before. Several non1imiting exemplary embodiments of pos-
sible stop location determination systems (and methods) 190
of this type will be described in detail hereafter. Although
not limited to this application, such stop location determi-
nation systems 190 are particularly useful in cormection with
transportable PCDs that are carried with a mobile person, as
will be clear from the discussion hereafter.
1. First Embodiment
The architecture of one such embodiment, among others,
60
Internet, in response to screen prompts associated with a
graphical user interface displayed on the user's computer
screen and generated from HTML (with applets, if desired,
in the implementation) communicated from the BSCU 40 to
the user computer.
The data manager 67 and/or the monitoring mechanism
69 of the BS manager 41 is designed to monitor travel of the
MT 17, as previously described. The tracking can be based
upon timing, dlstance, and/or location information.
is shown in FIG. 15A and is denoted by reference numeral 10
190c. AJthough not limited to this particular configuration,
11le data manager 67 and/or the monitoring mechanism
69 of the BS manager 41 is further designed to determine a
piclmp/delivery Iocation(s) for the MT 17 based upon the
travel status and the timing criteria (and in alternative
embodiments, additionally based upon location data
in this embodiment, the stop location detemtination system
190c is implemented in the monitoring mechanism 69 (FIG.
SB) associated with the notification system 10, particularly
in the software associated with the BS manager 41 (FIG. 3).
This stop location detennination system 190c, can be con-
figured to implement the following methodology, as is
summarized by flow chart in FIG. 15A, via suitable prou
gramming: receiving one or more timing criteria corre-
spondlng to a pick-up or delivery, as denoted at block 211;
monitoring travel data pertaining to an MT 17, as denoted at
block 212; determining one or more pick-up/delivery loca-
tions for the MT 17 based upon the travel status and the
timing criteria, as denoted at block 213; and communicating
with a PCD 75 associated with a party and providing the
pickup/delivery locations to the communications device, as
denoted at block 214, so that pickup or delivery can be
accomplished in accordance with the timing criteria at a stop
location.
15 ated with the PCD 75 itself, an originally scheduled pickup/
delivery location, or some other location or geographical
reference). Any suitable algorithms may be employed by the
BS manager 41 to accomplish this determination task.
The stop location(s) may be determined from a group of
20 predetermined eligible stops (a collection or along a prede-
termined route), from known intersections, from a set of
detected locations, from locations on a map, from addresses,
etc. The BS manager 41 can be interfaced with or be
designed to include conventional mapping software to
25 enable the BS manager 41 to perform the "foregoing deter·
The timing criteria can be, for example but not limited to, 30
a time of the day, a period of time during the day (e.g., 2:00
pm to 4:00pm, daytime, nighttime, etc.), days of the week,
weeks of the month, a period of time to elapse from the time
that the timing criteria are made known to the notification
system (e.g., in3 hours), an indication of ASAP (as soon as 35
possible), etc. In the preferred embodlment, the timing
criteria are communicated to the BS manager 41 by the user
and are stored in user data table 68b of the database 94 (FIG.
SA).
The entity that owns and/or operates the notification 40
system 10 or notification service could even practice a
business method involving charging a user for delivering to
or enabling pick"Up at a location that was not originally
scheduled or charging different fees to a user for different
degrees of notification immediacy or charging for 45
ing a delivery or pickup. For example, the entity could
charge more for ASAP service than for a service having a
timing requirement of within 24 hours. A stratified billing
schedule could be implemented, for example, similar to the
manner in which the U.S. Postal Service charges for mail so
services: overnight is one charge, two-day service is another,
etc.
mination.
As a simple example of a determination process, the BS
manager 41 could select the next stop or next tvm stops
along a predetermined route associated with a delivery
vehicle when it will arrive at such stop or stops within a
specified timing criterion, e.g., 30 minutes.
In some embodiments, a selection among a group of
possible stops can be made by correlating· a maximum
device time requirement (time that it will take a person
carrying the device to travel the distance between the device
and a possible stop location) and a maximum MT time
requirement (time that it will take the MT 17 to tfavel the
distance between the MT 17 and a possible stop location) to
the group of possible stop locations. For instance, assume
that the timing criterion is set at 15 minutes, that the BS
manager 4:1 has determined, based upon its database, map-
ping programs, or otherwise, that three locations A, B, and
Care possible candidates for the device user to pickup from
or deliver to 1he MT 17, that the maximum device time
requirement for locations A, B, and C are 10, 16, and 20
minutes, respectively, and that the maximum MT time
requirement for locations A, B, and C are 5, 11, and 9
minutes, respectively. In this scenario, the BS manager 41
can be designed to select location A, because the timing
criterion will be met.
In alternative embodiments, the stop location(s) may be
selected from locations that are in an acceptable proximity
to the PCD 75 and the MT 17, at the time that the determi-
nation is made, but which would satisfy the one or more
Note that, with the stop location determination system
190c, a user can meet a driver of a vehicle at any one of a
number of vehicle stops along a route traveled by the
vehicle. As an example, a party may wish to meet a driver
and obtain a package as soon as possible. 11lls system 190c
allows the party to interact with the driver/vehicle at an
appropriate veillcle stop (address or map based location) that
meets the timing criterion, perhaps one that was not origi-
naiiy intended by the party or driver.
55 tinring criteria. In these alternative embodiments, the
tion of the PCD 75 can be assumed, in general, based upon
the home address, work address, telephone number
exchange associated with the PCD 75, etc., associated with
the user, could be determined using a location sensor
60 ated on the PCD 75 (as previously described), could be
based upon other configuration data provided by the user,
etc. In this embodiment 190c, the massage manager 82 of the
BS manager 41 receives the one or more timing criteria
corresponding to a pickup or delivery and stores this infor-
mation in the user data table 68b. The timing criteria can be 65
communicated to the BS manager 41 via any suitable means,
for example but not limited to, via a computer over the
When a notification communication is to occur, the trans-
mitter 72 associated with the BSCU 40 (FIG. 1 ), under the
control of the BS manager 41, communicates the notification
conununication. The notification communication passes
through the network 55 (FIG. 1) to the receiver 73 (FIG. 1)
Exhibit A
Page 98
US 7,119,716 B2
61 62
associated with the PCD 75. The BS manager 41 can be tions device, so that pich.·up or delivery can be accomplished
designed to cause initiation of the notification communka- in accordance with the timing criteria, as denoted at block
tion when a suitable MT 17 is an acceptable proximity, 224.
perhaps a predetermined proximity or system-defined or In alternative embodiments, the BS manager 41 may be
user-defined proximity, with respect to one or more stop designedtocommtmicate,anindicationoftbetypeofMTl7
locations. that will stop at each location, for example but not limited
As another alternative, the BS manager 41 can be to, whether the Mr 17, is a bus, railroad train, tax, etc. This
designed to cause initiation of the notification communica- would enable the notification-receiving party to select which
tion when a suitable MT 17 has already traveled a predefined mode of transportation to utilize.
time period along a predefined route. 10 In alternative embodiments, the BS manager 41 is
The BS manager 41 communicates an identification of the designed to enable the user of the PCD 75 to select which of
stop location(s) to the PCD 75 so that the delivery or pickup the stop locations and/or which of the MTs 17 that the user
task can be accomplished at a stop location. The identifica- wishes to utilize. This can be accomplished using one of the
tion can be any suitable information that will enable the variations of the response system, which have been
device user to travel to the stop Iocation(s), for example but 15 described in detail previously. Furthermore, this selection or
not limited to, street address information, bus stop location information indicative thereof can be fo.nvarded by the BS
or number, street intersection location, longitude and lati- manager 41 to a communications device, for example,
tude coordinates, audio or visual description of a place, an device 44 (FIG. 1), associated with the selected MT 17, so
image of the stop location, a map image, etc. Directions to that the MT 17 is aware of the pickup or delivery by the user
the stop location(s) can also be provided by the BS manager 20 at the selected stop location. Also, if desired, the BS mana
41 over the commllllications Iinlc ager 41 can be designed to advise one or more other MTs 17
In altemative embodiments, the BS manager 41 may be that they have not been selected.
designed to communicate, along with an identification of the R. Secure Notification Messaging Systems and Methods
stop location(s), an identification of the MT 17 to the PCD Secure notification messaging systems and methods can
75. For example, the identification could be a bus number,
25
be implemented in cormection with the notification systems,
visual or audio descdption, description of the driver or for example, those described hereinbefore, to give the con-
vehicle type, etc, tacted party confidence that the notification message is
In alternative embodiments, the BS manager 41 may be genuine and legitimate.
designed to communicate, along with an identification of a More specifically, the BS manager 41 may be designed to
plurality of stop locations, an inclication of the type of MI
30
send authentication information to the PCD 75 when a
17 that will stop at each location .. for example but not lirnlted notification is in progress to indicate to the user that the
to, whether the MT 17, is a bus, railroad train, tax, etc. notification is originating from the proper source. The
In alternative embodiments, the BS manager 41 may be authentication information can be, for example but not
designed to communicate, along with an identification of the
35
limited to, any of the following: a logo, trademark, coat of
stop location, a code to the PCD 75 that will be used by the anns, symbol, predefined symbol or text or numeric code
contacted party to indicate to a party associated with the MI that has been made known to or selected by the party being
17, for example, a driver of the MT 17, for authentication contacted, specific sound or sounds or music, a distinctive
purposes so that the party associated with the MT 17 knows ring as described in U.S. Pat. No. 6,313,760 that is selected
that the party arriving at the stop location is properly
40
by the user, image of a vehicle or driver, Jive image of
authorized to perform the pickup or delivery. vehicle or driver, a telephone number that can be called to
In alternative embodiments, the BS m3nager 41 may be verify the notification, such as the telephone number asso-
designed to receive an indication from the PCD 75 that the ciated with a telephone situated on the MT 17 or associated
party is unwilling to perform the delivery or pickup task with a verification entity, part of a credit card number, such
associated with the notification; and as a consequence, to
45
as the last four digits, an image of a signature, such as the
initiate another notification communication to another dif- signature of the notified party, a public official, or another
ferent PCD 75 associated with another party in order to party, etc.
request assistance in the delivery or pickup task from the The authentication information can be preset or dynami-
another party, As an example, the BS manager 41 may cally programmable. It can be user defined or system
prompt the party to press a particular device button to
50
defined.
indicate a willingness or unwillingness to accept the respon- When the PCD 75 is equipped with a screen (e.g., a Sanyo
sibility of the delivery or pickup. As another example, the Model 8100 wireless PCS vision picture phone distributed
BS manager 41 may forward an HTML page of code to a by Sprint, a Sony Ericsson T300 wireless picture phone
computer-based PCD 75 that visually prompts the party to distributed by T-Mobile, etc.), an image can be sent. When
make a selection.
55
the PCD 75 is equipped with audio capabilities, a signal that
2. Second Embodiment causes an audible signal at the user end can be sent. When
As illustrated in FIG. 158, the BS manager 41 may be the PCD 75 is equipped with motion or vibration capabili-
configured to perform the following steps: receiving one or ties, a signal can be sent that causes a particular motion or
more timing criteria corresponding to a pickup or delivery, vibration signal to occur at the user end.
as denoted at block 221; monitoring travel data pertaining to 60 The authentication data can be stored in authentication
a plurality a HATs 17, for instance, first and second MTs 17, data table 68h of the database 94 or the data can be accessed
as denoted at block 222; determining a pickup/delivery remotely, even dynamically during a communication with
locations for the first and second MTs 17 based upon the PCD 75,
travel status and the timing criteria, as denoted at block 223; FIG. 16 shows graphically the secure notification mes-
and contacting a commun:ications device associated with a 65 saging system and is generally denoted by reference numeral
party and providing the pickup/delivery locations for the 210. As an exemplary implementation, the system 210 is
first and second MTs 17, respectively, to the communica- implemented in software in the monitoring mechanism 69
Exhibit A
Page 99
US 7,119,716 B2
63
associated with the BS manager 41. The software is con·
figured to perform or cause performance of the following
steps: monitoring travel data associated with an MT 17, as
indicated at block 231; communicating a notification involv-
ing a delivery or pickup task associated with the MT 17 to
a PCD associated with a party, as indicated at block 232; and
providing authentication infonnation 234 to the PCD that
indicates to the party that the notification is from an autho-
rized source, as indicated at block 233. The providing step
can be performed before, during (as part of the same step),
or after the communicating step. As is shown in FIG. 16, the
authentication information 234 can be stored in the memory
30b, can be accessed by the BS manager 41, and commu-
nicated by the BS manager 41 to the PCD 75.
In alternative embodiments, among others, a party can
predefine one or more authentication indicia to be sent to the
PCD 75 during a notification. The BS manager 41 is
designed with functionality to permit a party to communl-
cate with the BS manager 41 and provide configuration
information, such as an identification of the authentication
indicia. Such configuration information can be stored and
accessed by the BS manager 41 in the user data table 68b
and/or the authentication data table 68h.
As an example, the contact can occur by having the party
use a computer or computer-based device to communicate
with the BS manager 41 over the Internet, particularly the
WWW. Any suitable graphical user interface can be
employed to enable communications. U.S. Pat. No. 6,411,
891 describes systems and methods for enabling interactions
between a party using a computer and a base station com-
puter associated with a notification system, the description
of which is incorporate herein by reference. These systems
and methods can be employed in the context of this example.
64
separate entity. The server compares the image with an
image of the driver that is stored in a local accessible
database. When it matches or does not match, the server is
designed to communicate such message back to the PCD 75
5 indicating the match or nonmatch, respectively.
As another example, a certifiable code may be utilized. In
this example, the certification/verification server has a list of
authorized codes in its database that are authorized to be
used by the notification system/service. The server compares
10 the incoming code with a code that is stored in an accessible
database. When it matches or does not match, the server is
designed to communicate such message back to the PCD 75
indicating the match or nonmatch, respectively.
As another alternative embodiment, the MT 17 may be
15 equipped with one or more digital cameras (or the cameras
may be disposed remote from the MT 17) for capturing an
image, series of images, and/or video (real time live or
delayed) of the rvrr 17, of a person (e.g., a driver) or thing
situated within the MT 17, or of something outside the MT
20 17 and for communicating the image or video to a website
server on the World Wide Web (WWW) of the Internet.
Moreover, the authenticatiOn information may include a
hyperlink to the website server on the WWW of the Internet
so that the notification-receiving party can view the image or
25 video taken from the MT 17.
FIG. 16A shows a possible screen message that can be
driven to (such as ovet the internet) and shown on a notified
PCD 75 during a notification communication. The screen
has an image 235 of the party associated with the MT 17
30 who will be arriving at the stop location. Also, with this
example, a response system, as described previously in this
document, is implemented. More specifically, the notified
party is prompted: ''Please reply to this message for addi-
tional verification, to cancel the arrival, or to reschedule."
As another example, the contact can occur by having the
party use a conventional telephone to communicate with the
BS manager 41 over the PSTN. In cmmection with such a
telephone link, any suitable interac1ive voice response (IVR)
system or dual-tone encoding scheme may be utilized to
communicate information. U.S, Pat. No, 5,657,010
describes systems and methods for enabling interactions 40
between a party using a telephone and a base station
computer associated with a notification system, the descrip-
tion of which is incorporate herein by reference, These
systems and methods can be employed in the context ofthis
example.
35 Hyperlinks can be associated with each of the foregoing
sentence elements, so that when the recipient selects one, the
BSCU 40 receives the selection and can act accordingly.
S. Mobile Thing Determination Systems and Methods
1. First Embodiment
Mobile thing detennination systems (and methods) 250
can be implemented in connection with the notification
systems, for example, those described hereinbefore. Several
nonlimiting exemplary embodiments of possible MT deter-
45 mination systems (and methods) 250 will be described in
detail hereafter. Although not limited to these applications,
such determination systems 250 are particularly useful in
connection with transportable PCDs that are carried with a
In further alternative embodiments, a link may be pro-
vided by the BS manager 41 with the authentication infor-
mation to enable the party to certify that the authentication
information is from an authorized source. For example, the
link may be a hyperlink to a server on the Internet. The party so
can select the link to communicate with the server to certify
that the authentication information is from the authorized
source.
mobile person and in connection with transportation ser-
vices, like taxicab services, that have a number of vehicles
and stop locations that can be anywhere, as will be clear
from the discussion hereafter.
The architecture of one such embodiment, among others,
is shown in FIG. 17Aand is generally denoted by reference As an example, a certifiable image may be utilized. More
specifically, an image is communicated to the PCD 75 and
the user of the PCD 75 can have the content of the image
certified or verified as originating from an authorized source.
In one such embodiment, the image (captured live via digital
camera or prerecorded) is a picture of a mobile vehicle
driver that is communicated to a computer-based PCD 75
during the notification communication. The image is embed-
ded in HTML, XML, or some other markup language with
java applets. A hyperlin.k is provided so that the device user
can click on, or select, the image or select the hyperlink,
which causes the image to be sent to a remote certification/
verification server on the Internet. The certification/verifi-
cation server can be part of the notjfication system or a
55 numeral 250a. Although not limited to this particular con-
figuration, in this embodiment, the MT determination sys-
tem 250a is implemented in the notification system 10,
particularly the BS manager 41. The MT determination
system 250a, is configured to implement t11e following
60 methodology, as is summarized by flow chart in FIG.17A:
permitting a party to identifY a pickup location, a dropo:ff
location, and one or more user notification preferences, as
indicated at block 251; identifying an MT 17 based upon the
identity of the pickup location, the dropo:fflocation, or both,
65 as indicated at block 252; and communicating an identity of
the MT when appropriate, pursuant to the one or more
notification preferences, as indicated in block 253. Note that
Exhibit A
Page 100
US 7,119,716 B2
65
these steps can occur as part of the same communication
session or link or in more than one communication
action.
66
lite transceiver, personal data assistant (PDA), pager, any
addressable communications device on the internet, etc.
Both a signal and a message may be sent to the target
communications device, for example, a ring signal and a text
message could be communicated to a PDA, pager, or
puter.
With respect to step 252, any of a number of possible
criteria may be used by the BS manager 41 to identify and/or
select an MT 17 to accomplish the pickup and dropo:lf task,
Additionally and optionally, the MT determination system
250a (or system 250b) can be further designed to receive an 5
identification or characteristic of a thing during a commu·
nication session between the BSCU 40 and the PCD 75, for
example but not limited to, an identity or characteristic of a
package or person, to be picked up at the pickup location.
This information can be used for planning and/or verifica·
tion purposes. Further, if desired, the system 250a (or system
250b) can be configured to cause the BSCU 40 to commu-
nicate this identification or characteristic of the thing to be
picked up to a communications device associated with the
MT 17, so that a party associated with the MT 17 can verify
the thing at the pickup location. The identity or characteristic
can be any of a number of possibilities, such as a number
(e.g., bar code number, Federal Express number, etc.) asso-
ciated with a package, the weight or size of a package, or the
name of a person.
10 while complying with the user preferences. As an example
of the MT identification process in the context of taxicabs,
consider a scenario where the user has indicated that one of
his/her preferences is to get picked up whhin fifteen minutes
and that another one of his, her preferences is that the taxicab
15 must have air conditioning. Further assume that the BS
manager 41 knows that a taxicab having air conditioning is
currently available in the geographical area of the pickup
location ru1d can travel to the pickup location within the
specified fifteen minutes. In this example, the BS manager
20 41 can be designed to assign the taxicab to the task of
picking the user up at the pickup location and dropping the
user off at the dropo:lflocation. A communication can be sent
by the BSCU 40 to a communications device associated with
Although not necessary for implementation, the foregoing
methodology can be implemented, and in the preferred
embodiment is implemented, by software associated with
the data manager 67 m1d/or the monitoring mechanism 69
(F1G. 5B) of the BS manager 41. See stop location deter- 25
mination system 250 in FIGS. 1 and 3. The combination of
blocks of FIG. 17A essentially represents the high level
architecture of such software. Note, however, that it is
possible to have special purpose digttal or analog hardware
designed to implement the same or similar methodology, and 30
such hardware could be associated with the BSCU 40.
Pickup and dropoff locations can be stored and accessed
in the stop location data table 68d. Identification of MTs can
be stored and accessed in the Mf data table 68a. Further,
user notification preferences can be stored and accessed in 35
the user data table 68b.
More specifically, with respect to step 251, the BS man·
ager 41 is designed to permit a party to identify a pickup
location, a dropoff location, and one or more notification
preferences. The communication can occur via any suitable 40
communications device and with any suitable user interface,
but in the preferred embodiment, the communication is
accomplished through a portable computer-based PCD 75,
such as a wireless telephone or PDA. The notification
preferences may include, for example but not limited to, a 45
proximity of the MTto the pickup location (e.g., a distance
between the MT and the pickup location that is to be met
before a notification will occur, a telephone number to be
used when making the notification communication, a time
period that it will take the MT to reach the pickup location, so
the arrival or departure of the MT from a location, the entry
of the MT into a geographic region, etc.), a particular time
that the passenger must arrive at the drop off location, a time
period that the user is willing to expend on the trip (several
selections could be provided pertaining to the same or 55
different vehicles), the type or location of seat that the
passenger would like to reserve, whether a pid.'up vehicle
has air conditioning, the type of security or care that is to be
taken with respect to a package that is being picked up, an
identification and/or when to use one or more 60
tions methods , a specification to attempt another commu-
nications device if a first one fails, any of those preferences
mentioned previously in this document, etc. The
cations methods may involve, for example but not limited to,
communicating a signal and/or a message to a 65
telephone, cellular, satellite, or wireless telephone, facsimile
machine, computer, television, cable TV transceiver,
the taxicab, indicating the pickup particulars.
With respect to step 253, the BS manager 41 is designed
to initiate a notification communication and communicate an
identity of the MT 17, when appropriate, pursuant to the one
or more notification preferences. In the preferred
ment, the notification communication session is initiated by
the BS manager 41 when the MT 17 is at a particular
location, is within a particular geographical region, or is
within a particular proximity of the dropoff location, using
the monitoring systems and algorithms described previously
in this document.
During the notification communication session, the MT
17 can be identified with a vehicle number, with a
tion of a vehicle type, color, etc., with reference to a logo on
the MT, with a digitized picture or video of the MT, or in
some other way.
The BS manager 41 can be designed to enable the party
to accept or deny the pickup and dropoffusing the identified
MT 17 during the notification communication session or
during a subsequent communication session. This can be
accomplished with a suitable grdphical user interface,
assmning the PCD 75 has display capabilities, with an IVR,
by touch tone commands pressed by the device user, by
other means of communication described elsewhere in this
document, etc.
The BS manager 41 can be designed to provide
tion concerning the capacity of the MT 17 during the
notification communication session, for example but not
limited to, the number of passengers, packages, or other
items currently residing on the MT 17, the number of vacant
spaces, seats, slots, etc.
The BS manager 41 may be designed to receive
tion regarding an item, for example but not limited to, a
package, that is placed on the MT 17, based upon it being
placed on the MT 17 at the pickup location, based upon it
being dropped off at the dropo:ff location, or both. This
information is useful for tracking the item as well as the
capacity of the MT to handle new items. Furthennore, a
machine readable code, for example, a bar code or electronic
tag (see U.S. Pat. No. 6,144,301), could reside on or in or be
placed on or in the item and read by a suitable reader, such
as a bar code scanner or electronic tag reader, at some time
when the item is matched up with the MT 17. Moreover, this
code or a derivative thereof(e.g., an indicator of less bit size,
Exhibit A
Page 101
US 7,119,716 B2
67
a coded representation, an index in a lookup table, etc.)
could be communicated from the MT, using a suitable
communications device on the MT 17, to the BSCU 40 for
fUrther processing and analysis, if desired.
2. Second Embodiment
68
The BS manager 41 can be designed to provide informa-
tion conceming the capacity of the MT 17 during the first
communication session, second communication session, or
both, for example, the number of passengers, packages, or
other items, the number of vacant spaces, seats, slots, etc.
The BS manager 41 can be designed to receive informa·
tion regarding an item, for example, a package, that is placed
on the Mf 17, based upon it being placed on the MT 17 at
the pickup location, based upon it being dropped off at the
10 dropoff location, or both. This information is useful for
tracking the item as well as the capacity of the MT to handle
new items. Furthermore, a machine readable code, for
example, a bar code, could reside on or in or be placed on
or in the item and read by a suitable reader, such as a bar
The architecture of another embodiment of the MT deter-
mination system 250, among others, is shown in FIG. 17B
and is generally denoted by reference numeral 2506.
Although not limited to this particular configuration, in this
embodiment, the MT determination system 250b is imple-
mented in the notification system 10, particularly the BS
manager 41. The MT determination system 2506, is config-
ured to implement the following methodology, as is sum-
marized by flow chart in FIG. 17B: establishing a first
communication session between the system 10 and a PCD
75, as indicated at block 261; during the first communication
session, pennitting a party associated with the PCD 75 to
identify (a) a communications method for providing a notia
fication, (b) a pickup location and (c) a dropofflocation, as
indicated at block 262; identifying an MT that will arrive at 20
the pickup location for pickup and that will travel to the
dropoff location for dropoff, based upon the identity of the
pickup location, the dropofflocation, or both, as indicated at
block 263; establishing a second communication session in
accordance with the communications method for providing 25
a notification, as indicated at block 264; and during the
second communications session, identifYing the MT, as
indicated at block 265. In the preferred embodiment, the
second communication session is initiated by the BS man-
ager 41 when the MT 17 is at a particular location, is within 30
a particular geographical region, or is within a particular
proximity of the dropoff location, using the monitoring
systems and algorithms described previously in this docu-
ment.
15 code scanner, at some time when the item is matched up with
the MT 17. Moreover, this code or a derivative thereof could
be communicated from the MT, using a suitable communi-
cations device, to the BSCU 40 for further processing and
analysis, if desired.
3. Third Embodiment
The architecture of yet another embodiment of the MT
determination system 250, among others, is shown in FIG.
17C and is generally denoted by reference numeral 250c.
Although not limited to this particular configuration, in this
embodiment, the MT determination system 250c is imple·
mented in the notification system 10, particularly the BS
manager 41. The MT determination system 250c, is config-
ured to implement the following methodology, as is sum-
marized by flow chart in FIG.17C: during a communication
session with a PCD 75, determining a location (can be a
geographic area or an approximate location, depending upon
the precision needed to effect pickup or delivery) ofthe PCD
75; and identifYing an MT 17 to travel to the location or
another location that is near the determined location for a
35
pickup or delivery based upon the determined location ofthe
PCD 75.
Although not necessary for implementation, the foregoing
methodology can be implemented, and in the preferred
embodiment is implemented, by software associated with
the BS manager 41. See stop location determination system
250 in FIGS. 1 and 3. The combination of blocks of FIG.
17B essentially represents the high level architecture of such 40
software. Note, however, that it is possible to have special
purpose digital or analog hardware designed to implement
the same or similar methodology, and such hardware could
be associated wilh the BSCU 40.
During the first and/or second communication sessions, 45
the :MT 17 can be identified with a vehicle number, with a
description of a vehicle type, color, etc., with reference to a
logo on the MT, with a digitized picture or video of the MT,
or in some other way.
The BS manager 41 can be designed to enable the party so
to accept or deny the pickup and dropoff using the identified
MT 17 during the first communication session, during the
second communication session, or during a subsequent
communication session. This can be accomplished with a
suitable graphical user interface, assuming the PCD 75 has 55
display capabilities, with an NR, by touch tone commands
pressed by the device user, by other means of communica-
tion described elsewhere in this document, etc.
Note that the second communication session can occur
between the BSCU 40 and a clifferent PCD 75, that is, 60
different from the one involved in the first communication
session, based upon user notification preferences. The user
can specifY in the first communication session or in some
other communications session with the BS manager 41,
which communication method(s) should by used for the 65
second communication session (which is the notification
session).
Note that, in this embodiment 250c, the communication
session that is used to enable detection of the location of the
PCD 75 can be a notification communication initiated from
the system 10 to the PCD 75, based upon one or more
criteria defined by a user in user notification preferences, or
can be a communication initiated by the PCD 75 to the
system 10. When the latter is implemented, the system 250c
may be designed to cause a subsequent notification com-
munication session to the PCD 75 and/or a different PCD 75
(defined by user preferences) from the system 10 based upon
travel status of the MT 17, e.g., when the detennined MT is
at a particular location, is within a particular geographical
region, or is within a particular proximity of the location.
The location of the PCD 75 can be determined automati·
cally, using any of the techniques described previously, or
can be detennined by prompting the device user to manually
enter an identification (e.g., an address, region, stop number,
etc.) or description of the device location. As an example,
the device user could be prompted to enter a text message
that includes the post office address that is nearest the PCD
75 or to enter the zip code in which the PCD 75 resides.
Further, when the MT 17 is identified, it may be selected,
if necessary, from a plurality of possible MTs 17, based upon
user notification preferences in adclition to the determined
location of the PCD 75.
As with the other embodiments of the system 250, and as
previously described, although not in this context, this
embodiment 250c can be further designed to communicate
an identification of the location of the PCD 75 to a com-
munications device associated with the MT 17.
Exhibit A
Page 102
US 7,119,716 B2
69
As with the other embodiments of the system 250, and as
previously described, this embodiment 250c can be further
designed to communicating an identification of the MT 17,
such as a number or description, to the PCD 75,
70
As with the other embodiments of the system 250, and as
previously described, this embodiment 250c can be further
designed to enable the party associated with the PCD 75 to
accept or deny the responsibility of the pickup or the
delivery using the identified MT during the conununication
session or during a subsequent commu:rllcation session with
an appropriate response from the user of the PCD 75. See
response systems and methods described earlier in this
document. Furthermore, the BS manager 41 can be designed
to forward the detected location of the PCD 75 back to the
PCD 75, so that the user of the PCD 75 is aware of the
system detected location and can confim1 it
ured to implement the following methodology, as is sum-
marized by flow chart in FIG. 17D: causing or establishing
a first communication session between the system 10 and a
PCD 75; during the first communication session, determin-
ing a location (can be a geographic area or an approximate
location, depending upon the precision needed to effect
pickup or delivery) of the PCD 75; selecting an MT 17 from
among a plurality to travel to the determined location or
another location for a pickup or delivery at one of the
10
locations; and causing or monitoring establishment of a
second communication session between the system 10 and
the PCD 75 when one or more user preferences criteria
relating to travel status of the selected MI' 17 have been
satisfied to notify the user of the PCD 75 of the impending
15
arrival of the MT 17 at one of the locations.
As with the other embodiments of the system 250, and as
previously described, this embodiment 250c can be further
designed to provide information concerning a capacity of
items situated on the MT 17 that is to travel to the pickup or 20
delivery location.
As with the other embodiments of the system 250, and as
previously described, this embodiment 250c can be further
designed to receive information from the PCD 75 regarding
an item that is to be placed on the MT 17 at the location or 25
dropped off at the location, or both. With respect to the
former, the item may be equipped with a human readable
code or machine readable code that can be read or scanned
and sent to the system 10.
As with the other embodiments of the system 250, and as 30
previously described, this embodiment 250c can be further
designed to receive an identification or characteristic of a
thing to be picked up by the MT 17 at the location, and to
communicate the thing identification or characteristic to a
communications device, personal or otheiWise, associated 35
with the MT 17.
Note that, in this embodiment 250d, the communication
session that is used to enable detection of the location of the
PCD 75 can be a notification communication initiated from
the system 10 to the PCD 75, based upon one or more
criteria defined by a user in user notification preferences, or
can be a non-notification communication initiated by the
PCD 75 to the system 10.
The system 250d can be designed to cause the second
communication session to the PCD 75 (and perhaps to a
different PCD 75 pursuant to user preferences) from the
system 10 based upon travel status of the MT 17 and
predefined user preferences, e.g., when the determined MT
is at a particular location, is within a particular geographical
region, or is within a particular proximity of the location
with respect to timing or distance.
Further, when the MT 17 is identified, it may be selected,
if necessary, from a plurality of possible Mfs 17, based upon
user notification preferences in addition to the determined
location of the PCD 75.
As with the other embodiments of the system 250, and as
previously described, although not in this context, this
embodiment 250d can be further designed to communicate
an identification of the location of the PCD 75 to a com-
In other alternative embodiments, the BS manager 41 can
also be designed to communicate a location to the PCD 75
that is different than the detected location or approximate
detected location of the PCD 75 or that is in an area that the
PCD 75 is detected to be within or near. For example, if the
PCD 75 is detected to be near an already existing scheduled
stop location for an MT 17, then the PCD 75 may be advised
40 munications device associated with the MT 17.
of the stop location. An identity of, description of, and/or
directions thereto can be communicated to the PCD 75. The 45
As with the other embodiments of the system 250, and as
previously described, this embodiment 250d can be further
designed to communicate an identification of the MI 17,
such as a number or description, to the PCD 75.
As with the other embodiments of the system 250, and as
previously described, this embodiment 250d can be further
designed to enable the party associated with the PCD 75 to
accept or deny the responsibility of the pickup or the
device user can be given the opportunity to accept or deny
a pickup or delivery at the different location. As another
example, the zip code associated with the area in which the
PCD 75 presently resides may have been manually commu-
nicated to the system 10 by the user of PCD 75. In this
example, the BS manager 41 may be configured to select any
suitable stop location that is within the geographic region
corresponding to the zip code.
50
delivery using the identified MT during the communlcation
session or during a subsequent communication session with
an appropriate response from the user of the PCD 75. See
response systems and methods described earlier in this
document. Furthermore, the BS manager 41 can be designed
55
to forv.•ard the detected location of the PCD 75 back to the
PCD 75, so that the user of the PCD 75 is aware of the
system detected location and can confirm it.
The user can even be given the opportunity to select
between the determined or the different location. The user
could even be charged a fee or a higher rate for causing the
MT 17 to travel to the device location as opposed to the
different location (the one that may correspond to an already As with the other embodiments of the system 250, and as
scheduled stop). previously described, this embodiment 250d can be further
4. Fourth Embodiment 60 designed to provide information concerning a capacity of
The architecture of still another embodiment of the MT items situated on the MT 17 that is to travel to the pickup or
determination system 250, among others, is shown in FIG. delivery location.
17D and is generally denoted by reference numeral 250d. As with the other embodiments of the system 250, and as
Although not limited to this particular configuration, in this previously described, this embodiment 250d can be further
embodiment, the MT determination system 250d is i m p l e ~ 65 designed to receive information from the PCD 75 regarding
mented in the notification system 10, particularly the BS an item that is to be placed on the :MT 17 at the location or
manager 41. The MT determination system 250d, is config- dropped off at the location, or both. With respect to the
Exhibit A
Page 103
US 7,119,716 B2
71
former, the item may be equipped with a human readable
code or machine readable code that can be read or scanned
and sent to the system 10.
72
PCD 75 when the MT 17 is at or within a predefined
proximity of the location or region, as indicated at block
294.
The stop location or region can be predetermined or
dynamically determined while the MT 17 and/or the PCD 75
are in motion. The user can selectively predetermine the stop
location or region via user preferences. The system 290 can
be designed to give the user a stop location or region or to
give a number of stop locations or regions to choose from.
As with the other embodiments of the system 250, and as
previously described, tills embodiment 250d can be further 5
designed to receive an identification or characteristic of a
tiling to be picked up by the MT 17 at the location, and to
communicate the thing identification or characteristic to a
communications device, personal or otherwise, associated
with the MT 17. 10 The system 290 can also be designed to permit the user to
enter longitude and latitude values to specify a particular
stop location.
In other altemative embodiments, the BS manager 41 can
also be designed to communicate a location to the PCD 75
that is different than the detected location or approximate
detected location of the PCD 75 or that is in an area that the
PCD 75 is detected to be within or near. For example, if the
PCD 75 is detected to be near an already existing scheduled
stop location for an MT 17, then the PCD 75 may be advised
of the stop location. An identity o f ~ description ot: and/or
directions thereto can be communicated to the PCD 75. The
device user can be given the opportunity to accept or deny
a pickup or delivery at the different location.
The user can even be given the opportunity to select
between the determined or the different location. The user
could even be charged a fee or a higher rate for causing the
MT 17 to travel lo the device location as opposed to the
different location (the one that may correspond to an already
scheduled stop).
T. Combined Mobile-Thing-To-Location (MTTL) And
Device-To-Location (DTL) Notification Systems and Meth-
ods
The system 290 can be designed to determine a stop
location based upon the location of the PCD 75. Techniques
15 for determining the location of the PCD 75 have been
described herein.
Note that the aforementioned steps 293 and 294 can occur
as part of the same communkation session or link or in more
than one communication transaction. As an example of the
20 former scenario, a text .communication can be generated by
the system 290 and communicated to a pager or PDA that
indicates (a) that the device is within 10 yards of the stop
location and (b) that the MT 17 is within 10 minutes of
arriving at the stop location. As another example of the
25 former scenario, two telephone numbers associated with a
telephone could be called, substantially concurrently, by the
notification system 10. Further, each could have their own
distinctive ring.
The notification system 10 can track the location of the
30 PCD 75 and the MT 17 by using any of the location tracking
techniques that have been previously described. Travel data
associated with the MI 17 can be stored in a table 68e, while
travel data associated with the PCD 75 can be stored in a
Systems (and methods) can be implemented in coilllection
with the notification systems, for example, those described
hereinbefore, including system 10, wherein a notification is
communicated to the PCD 75, based upon the proximity of 35
the MT 17 to a location or region, and another notification
PCD travel data table 68i of database 94 (FIG. SA). Fur-
themlOre, the notifications can be triggered using any of the
previously described techniques and user preferences.
is communicated to the PCD 75, based upon the proximity
of the PCD 75 itself to the same location or region (or a
location or region that is in close proximity to or based upon
the same location or region). Several nonJimiting exemplary 40
embodiments of such systems (and methods), which will
generally be denoted by reference numeral 290, will be
described in detail hereafter. Although not limited to these
applications, such systems 290 are particularly useful in
connection with transportable PCDs 75 that are carried with 45
a mobile person and in coilllection with transportation
services, like taxicab services, that have a number of
vehicles and stop locations that can be anywhere, as will be
clear from the discussion hereafter.
In alternative embodiments, the system 290 can be
designed to communicate an identification of the MT 17 to
the PCD 75 during one or both of the notification comnm-
:nications (blocks 293, 294). Furthermore, the system 290
can he configured to enable the party associated with the
PCD 75 to accept or deny a pickup or a delivery using the
identified MT 17 during the communication session using
any of the response techniques described previously in this
document.
In alternative embodiments, the system 290 can be
designed to enable a party associated with the PCD 75 to
define user preferences in connection with the notification
communications and to operate in accordance with the user
The architecture of one such embodiment, among others,
is shown in FIG. 18 and is generally denoted by reference
numeral 290. Although not limited to this particular con-
figuration, in this embodiment, the system 290 is imple-
mented in the notification system 10, particularly the BS
manager 41. The system 290 is configured to implement the
following methodology, as is summarized by flow chart in
FIG. 18: (a) monitoring travel data associated with an MT 17
so preferences. For example, among other things, the party can
define the predetermined proximity between the MT 17 and
the stop location or region for triggering a notification to the
PCD 75 and/or the predetermined proximity between the
PCD 75 and the stop location or region for triggering a
in relation to a location or region, as indicated at block 291;
(b) monitoring travel data associated with a PCD 75 in
relation to the location or geographic region (or a location or
reglon that is in close proximity to or based upon the same
location or region), as indicated at block 292; (c) causing a
notification communication to be initiated to the PCD 75
when the PCD 75 is at or is within a predetennined prox-
imity of the location or region, as indicated at block 293; and
before, during, or after the forgoing causing step, causing a
different notification communication to be initiated to the
55 notification communication to the PCD 75. The predeter-
mined proximities can be defined as a point when the MT 17
is at a particular location, is within a particular geographical
region, or is within a particular proximity of the stop
location in terms of timing, distance, or a combination
60 thereof.
In alternative embodiments, the system 290 can be
designed to provide information concerning a capacity of
items situated on the MT 17. This type of information would
he communicated from the MT 17 to the system 10, directly
65 or indirectly.
In alternative embodiments, the system 290 can be
designed to receive information regarding an item that is
Exhibit A
Page 104
US 7,119,716 B2
73 74
placed on the MT 17 at the stop location or dropped off of
the MT 17 at the stop location, or both. A machine readable
code can be disposed on the item and can be read when the
item is introduced onto or dropped o:tf of the MT 17. The
information communicated to the system 10 can be the code s
or a derivative thereof.
As with this embodiment and the others described in this
section, the traffic flow predicament data can be stored in a
traffic flow predicament data table(s) 68} in the database 94
(FIG. SA) and accessed by the message manager 82 (FIG.
SB). The traffic flow predicament data can take a variety of
forms, and it can be or a
In alternative embodiments, the system 290 can be
designed to select the MT 17 from a plurality of MTs 17,
based upon user-defined or system-defined notification pref-
erences.
In alternative embodiments, the system 290 can be
designed to receive from the PCD 75 an identification or
characteristic of a thing to be picked up at the stop location.
Moreover, the system 290 can optionally be designed to
communkate the thing identification or characteristic to a
communications device associated with the MT 17.
combination thereof.
As a nonlimiting example, the traffic flow predicament
data can take the fonn of time periods during the day
10
correlated to a road segment, indicating how long it should
take a motor vehicle under normal circumstances to traverse
that road segment during the different time periods. As one
way to accomplish this, in a traffic flow predicament data
table(s) 68) (FIG. SA), the following could be a record of
15
fields (or this information could be related and retrieved
from several tables or
TIME-OF-DAY-6-7, TRAVERSAL-TIME-PERIOD. The
first of the foregoing fields identifies the road segment as
number 044, which is Main Street in this example. The
20
second field identifies the time period of the day, i.e., 6:00
am to 7:00 am, and this infonnation is correlated with the
road segment 044. The third field identifies the time period
to traverse the segment 044 when this type of traffic flow is
in existence,
In alternative embodiments, the notification system 10
can employ the functionality described in U.S. Pat. No.
6,360,101 for tracking the proximity of the PCD 75 to the
location or region and issuing a notification to the PCD 75.
U.S. Pat. No. 6,360,101, which is incorporated herein by
reference, describes a mobile comM
munications device, such as a cellular telephone, tlmt
mines its current location and compares the ClllTent location
25
of one or more target locations. When the device is at or near
one of the target locations, then the device annunciates its
arrival by generating an audible alarm, or displays or transM
mits a predetermined arrival message. The target location(s)
can be entered manually at the device with the keypad, can
As a specific example of traffic flow predicament data and
how it can be used to effect the timing of a notification,
consider the following. 1t may take 10 minutes to traverse
Main Street at between 6:00am and 7:00am, but it may take
30
30 minutes to traverse Main Street between 7:00 am and
9:00 am. So, continuing this example, assume that the stop
location for the vehicle is at the end of Main Street, assume
that the user preferences indicate that the user would like to
be notified 10 minutes prior to arrival of the vehicle at the
be obtained via a positioning receiver, or can be loaded via
a server connected to a communications network.
U. Notifications Based Upon Traffic Flow Predicament Data
The notification system 10 may be designed to take into
acco1mt traffic flow and anything that can influence traffic
flow when determining when and if notification
cations should be initiated.
.1\lthough not limited to this application, this feature is
particularly useful when the system 10 is to initiate a
notification when an MT 17 is a predefined proximity in
terms of time f!'Om a stop location. This predefined
imity can be system-defined via any suitable progra.mming
mechanism or via predefined user preferences.
Tbis feature is also useful to trigger a notification to a user
to enable the user to plan for a best transmit route (see third
embodiment, hereafter).
35
stop location, assume that the vehicle has just arrived at the
beginning of Main Street, and assume that it is 8:30 am.
With these assumptions, the BS manager41, particularly, the
message manager 82 (FIG. SB) can be designed to wait to
make the notification until it is detected that the vehicle is ¥.3
40
of the way through :Main Street. However, if the time of day
were 6:30 am, then the BS manager 41 can be designed to
make the notification, at once, when it is detected that the
vehicle started on Main Street.
Carrying this example further, the BS manager 41 could
1, First Embodiment
45
be designed to, recognize that Main Street is wet and slick,
and therefOre, initiate five minutes later any notification
communication corresponding to any MT 17 that must
traverse Main Street (because it will take five minutes longer
for the Mf 17 to traverse Main Street.
In one possible embodiment, among others, the BS man-
ager 41 can be configured to implement the following so
algorithm, as denoted by reference numeral 210a in FIG.
19A: monitoring travel data associated witl1 an MT 17, as
denoted at block 311; scheduling a notification
cation, such as in a calJ queue in message manager 82 (FlG.
SB), as denoted at block 312; analyzing tra:ffic flow 55
ment data associated with a travel path (e.g., a road) to be
traveled by the MT 17, as denoted at block 313; and
rescheduling the notification communication, such as in the
call queue of message manager 82 (FIG. 58), based at least
in part upon the traffic flow predicament data, as denoted at 60
block 314. As can be appreciated by this methodology, the
internal scheduling of the notification communication can be
initiated later, or delayed, or in the alternative, initiated
earlier, based upon the influence of heavy or light traffic,
adverse or favorable environmental conditions, etc., so that 65
the system-defined or user-defined advance notification is
more accmately timed and implemented.
As a further example of traffic flow predicament data, the
traffic flow predicament data could include the real time
detection of an accident, the knowledge of construction
work, the knowledge of a reduced speed limit due to road
work or some other reason on a road segment and its effect
on traffic flow (e.g., one of three lanes may be blocked, so
it will take 33% longer for a motor vehicle to traverse the
road segment, the speed limit is now 25 mph instead of 45
mph, etc.). As one way to accomplish this, in a traffic flow
predicament data tablc(s) 68} (FIG. SA), the following could
be a set of fields that can be related and retrieved:
SEGMENT-044, TRAFFIC-FLOW-02, TRAVERSAL-
TIME·PERIOD. TI1e first of the aforementioned fields idenM
tifies the road segment as number 044. The second field
identifies the number of lanes that are open, i.e., two of three
lanes are open for traffic flow (there are other entries that
include TRAFFIC-FLOW-OJ and TRAFFIC-FLOW-03),
and this information is correlated with the road segment 044.
Exhibit A
Page 105
US 7,119,716 B2
75
The third field identifies the time period to traverse the
segment 044 when this type of traffic flow is in existence.
76
munication session, providing a message indicating a state
of traffic flow along the travel path (e.g., there will be a delay
and perhaps to what extent, traffic is flowing at an acceptable
level and perhaps to what extent, etc.), as indicated at block
As yet another example of traffic flow predicament data,
the traffic flow predicament data could include infOrmation
concerning the environmental or physical conditions asso-
ciated with a road segment and the effect of such conditions
5 333.
on traffic flow, For instance, the environmental conditions
could be whether the road segment is exhibited by fog, rain,
snow, darkness, sun, dryness, slickness, numerous pot boles,
etc. This information can be obtained via a variety of 10
sources, including weather report data from a weather
reporting source, inspection via camera or physical human
presence, etc., and this information can be entered into the
notification system 10, either automatically or manually. As
one way to accomplish this, in a traffic flow predicament 15
data table 68j (FJG. SA), the following could be a retrievable
set of fields: ROAD-SEGMFNT-044, ENVJRONMFNT-05,
TRAVERSAL-TIME-PERIOD, The first of the foregoing
fields identifies the road segment as number 044. The second
field identifies the type of environmental condition of the 20
road segment, which in this case is number 05, which
corresponds to foggy. The third field identifies the time
period to traverse the segment 044 when there is fog.
As with this embodiment and others to be described in this
section, the travel path to be monitored by the notification 25
system 10 can be determined by the notification system 10
or entered/selected by a user. Furthermore, the parameters or
metrics that can be used to trigger a notification communi-
cation can be system-defined, user-defined (in user prefer-
ences data, such as in table 68b), or a combination thereof. 30
2. Second Effibodiment
The BS manager 41 can be configured to store the travel
path at issue, which can be, for example, one or more road
segments (but could also be waterways, airspace, etc., in the
case of other vehicles) and can be configured to receive and
store traffic flow predicament data associated with the travel
path.
In some embodiments, the BS manager 41 can be
designed to receive (via entry or selection from available
options; data can be stored in user preferences data) user
preferences from a user, for example but not limited to, an
identification of the travel path, a delay acceptance thresh-
old, which is a metric that can be used to determine whether
the travel path is acceptable or unacceptable and which is
used by the BS manager 41 to trigger a notification com-
munication, an identification of a time of day or time period
during the day, etc. The BS manager 41 initiates the noti-
fication communication based upon, not only the travel flow
predicament data, but also upon one or more other user-
defined preferences.
More specifically, in regard to the delay acceptance
threshold, the delay acceptance threshold can be expressed
in any suitable terms to enable the determination of whether
or not a delay is acceptable. For example, the delay accep-
tance threshold could be expressed in tenns of percentages:
if traffic traveling along the path will take 50% longer than
usual, then initiate the notification communication. As
another example, the threshold could be expressed in terms
of delay time: if traffic traveling along the path will be
35
delayed by an additional 10 minutes, then initiate the noti-
fication communication. As still another example, the
threshold could be expressed in terms of speed: if traffic
traveling along the path is 45 mph or greater, then initiate the
notification communication.
In another possible embodiment, among others, the BS
manager 41 can be configured to implement the following
algorithm, as denoted by reference numeral 310b and illus-
trated in FJG. 198: monitoring travel data associated \V'ith an
MT 17, as indicated at block 321; determining a notification
time period, as indicated at block 322,-by reading a system-
defined or user-defined time period (in user preferences
data); analyzing traffic flow predicament data associated
with a travel path (e.g., a road) to be traveled by the MT 17 40
(for example, based upon the current location of the MT 17,
the ultimate stop location, and the known travel path or
travel path data, such as map data from a mapping system
showing how the MT 17 is expected to travel), as indicated
In alternative embodiments, the notification communica-
tion session can be initiated or triggered based upon, not
only traffic flow predicament data, but also upon one or more
other parameters, for example but not limited to, at a
predetermined time (e.g., at 5:00pm) or during a time period
of the day (e.g., between 5:00pm and 6:00pm, after 7:00
pm, in the evening, etc.). As an example, tl1e BS manager 41
can be designed to initiate the notification communication at
5:00pm, or in the alternative, between 5:00pm and 6:00pm,
only if and when traffic traveling along the path will take
at block 323; and determining when a notification commu- 45
nication should be initiated (earlier or later), based upon the
notification time period, the influence of traffic that is
derived from the traffic flow predicament data, and other
user preferences, if any, as indicated at block 324.
50
50% longer than usual. As another example, , the BS
manager 41 can be designed to initiate the notification
communication at 5:00 pm, or in the alternative, between
5:00pm and 6:00pm, only if traffic traveling along the path
will be delayed by at least 10 minutes. As yet another
3. Third Embodiment
Although not limited to this application, the following
emhodlment is particularly useful in a case where a party
would like to know if and when travel flow is being
hindered, is acceptable, or is being expedited on a road
segment, so that the party in a vehicle can better plan hisJher
route, for example, enable the party to take an alternative
route or, enable the party to take the travel path at issue, if
and when travel flow is acceptable or is sufficiently expe-
dited.
In this possible embodiment, the BS manager 41 is
configured to implement the following algorithm, as denoted
by reference number 310c and as illustrated in FIG. 19C:
analyzing traffic flow predicament data associated with a
travel path to be traveled by a party or MT 17, as indicated
55
example, the BS manager 41 can be designed to initiate the
notification communication at 5:00 pro, or in the alternative,
between 5:00pm and 6:00pm, only if and when traffic flow
is at an acceptable rate along the path as determined by the
delay acceptance threshold, which can be system-defined or
60 user-defined.
at block 331; iilltiating a notification communkation session 65
with a PCD 75, based upon the traffic flow predicament data,
In alternative embodiments, the BS manager 41 can be
designed to determine a location or region of the PCD 75 in
accordance with techniques described previously in this
document (see Response Systems). From this information,
the BS manager 41 can be equipped with suitable algorithms
for determining the travel path to be traveled by the party or
the PCD 75. as indicated at block 332; and during the notification com-
Exhibit A
Page 106
US 7,119,716 B2
77
The BS manager 41 can determine direction of travel by
receiving two or more location values from the PCD 75 that
are spaced in time. The BS manager 41 can also detennine
direction of travel based upon a known destination of the
PCD 75. From this location and direction information, the
BS manager 41 can anticipate travel paths, such as road
segments, that will be traversed by the party or MT 17.
As a specific nonlimiting example, assume that a party has
given instructions to the notification system 10 to advise the
party of any unacceptable road segments when the party
starts to return home after work at 5:00pm. Further assume
that the party can take two different routes (which can be
communicated to the notification system 10 by the user or
determined by the notification system 10 based upon a
knowledge of the user destination): (a) from the workplace
to First Street to Elm Street to 416 Barker Street, or (b) from
the work-place to McCle11andAvenue to West Morton Street
to 416 Barker Street, or (c) from the workplace to McClel-
land A venue to Domino Avenue to 416 Barker Street. In this
scenario, further assume that the party and PCD 75 com-
mence onto McClelland. When the notification system 10
determines the location of the PCD 75 to be McClelland,
then the BS manager 41 can be designed to select the next
one or more road segments that correspond to the one or
more possible routes that have been taken and to analyze
those one or more road segments in terms of traffic flow
predicament data. 1n the present scenario, further assume
that the notification system 10 has determined that West
Morton Street is unacceptable based upon the delay accep-
tance threshold and the present traffic flow predicament data
associated with West Morton Street. In this situation, the BS
manager 41 will advise the party via the PCD 41 of this fact,
in which case the party can decide to travel route (c) instead
of route (b) to get home.
78
device), the concepts can be employed in connection with
one or more first devices 75 and one or more second devices,
in virtually any combination thereof.
In alternative embodiments, the notification system 10
can be designed to enable a first party associated with the
first PCD 75 (the one being tracked) to select whether or not
a response is requested at ali during the notification com-
munication session initiated by the system 10 to the second
PCD 75. Tills can be useful in many circumstances, such as
10 when a delivery vehicle needs a signature in order to drop off
a package, and therefore, the delivery vehicle driver, who is
associated with the first PCD 75 needs to know whether a
party associated with the second PCD 75 will be available at
the stop location to sign for the package. A response by the
15 party that gets communicated eventually to the driver wiU
enable the driver to schedule deliveries accordingly.
In alternative embodiments, the notification system 10
can be equipped with functionality to detennine whether or
not a response is necessary from the second PCD 75. For
20 example, the notification system 10 could track whether or
not deliveries need a signature in database 94 (FIGS. 5Aand
5B), such as in a package data table(s) 68k. For those
requiring a signature, the system 10 would invoke a require-
ment for a response. For those not requiring a signature, the
25 system 10 would not invoke a requirement for a response.
The notification system 10 can be designed to communi-
cate the status of one or more responses to the first PCD 75.
For example, the status could be "Confirmed" for the
situation where a response has been received and the notified
30 party is willing to commit to the pickup/delivery, "Uncon-
fnmed" for the situation where a response has been received
and the notified party does not want to commit to the
pickup/delivery or it is unclear whether the notified party
wishes to commit, and "Waiting" for the situation where a
35 response that has not been received at all from the notified
V. Systems and Methods for Monitoring Travel ofPCDs and party.
Communicating Messages Between PCDs In a design where the first PCD 75 is shown the status of
111enotificationsystem10maybedesignedtoimplement multiple notifications, the system 10 can be designed to
systems and methods for monitoring travel of MTs 17 that enable the party associated with the first PCD 75 to make a
are PCDs 75 and communicating notifications and responses
40
selection of one of the entries, such as by touch tone,
among the PCDs 75, as more particularly described hereaf- touching a screen, voice recognition (IVR), etc. TI
1
e system
ter. 10 can be designed to communicate an indlcation of the
1. First Embodiment selection to the selected ones of the PCDs 75. This feature
One embodiment, among others, can be practiced by the would be useful in the context of a delivery vehicle 17 so
notification system 10, particularly in the manager 41, and 45 that the driver can notifY the prospective package recipients
involves the following methodology, which is shown in FIG. of the driver's intention to deliver a package to them.
20A and denoted by reference numeral 340a: monitoring In alternative embodiments, the notification system 10
travel data associated with a first PCD 75, as indicated at can be designed to receive a message from the first PCD 75
block 341; causing a notification communication session to and communicate the message to the second PCD 75 during
be initiated to a second PCD 75, the notification communi- 50 the notification communication session. The message can be
cation session including a message requesting a response virtually anything, for example, "Can you meet me at Pizza
and a travel status report indicating a proximity of the first Hut in 20 minutes."
PCD 75 to a location, as indlcated at block 342; receiving the In alternative embodiments, the notification system 10
response from the second PCD 75, as indkated at block 343; can be equipped with functionality to enable the party
and comm1micating the response to the first PCD 75 (the one 55 associated with the second PCD 17 (notified party) to select
being tracked by the notification system 10), as indicated at or enter a time for a pickup or delivery at the stop location.
block 344. The time can then be communicated to the first PCD 17
Note that the travel data in this embodiment, as well as the (tracked party).
others described herein, can be directly related to the device 2. Second Embodlment
75, e.g., data that directly relates to the location of the device 60 Another embodiment, among others, can be practiced by
75 itself or can be indirectly related to the device 75, e.g., the notification system 10, particularly in the manager 41,
data that directly relates to the location of an MT that and involves the foil owing methodology, which is shown in
transports or is closely associated with the device 75. Further FIG. 20B and denoted by reference numeral 340b: moni-
note that in this embodiment, as well as the others described taring travel data of a first PCD 75, as denoted at block 351;
herein, although the concepts are described for simplicity in 65 receiving a message from the first PCD 75, the message
connection with a first device 75 (the tracked device that including a request for a response, as denoted at block 352;
receives a response) and a second device 75 (the notified initiating a notification communication having the message
Exhibit A
Page 107
US 7,119,716 B2
79
and a travel status report of the first PCD 75 to a second PCD
75, as denoted at block 353; receiving the response from the
second PCD 75; and communicating the response to the first
PCD 75, as denoted at block 354,
The travel status report can indicate a proximity (in terms
of time, distance from, etc.) of the first PCD 75 to a stop
location, that the first PCD 75 has left a location, that the first
PCD 75 has arrived at a location, that the first PCD 75 is in
a particular geographic region, etc.
80
(which would push the reply back to the relevant notified
PCD(s)). As an example, this would be a useful feature in a
case where a first PCD 75 associated with a delivery vehicle
wishes to confirm or advise a notified PCD 7S or party that
the party has been officially placed on a delivery list.
Furthermore, a party can indicate in user preferences in table
68b of database 94 (FIG. SA) that the party would like to
have a confirmation reply.
The travel status report can indicate any of a number of
Ibe response from the second PCD 75 can indicate a
number of possibilities, including but not limited to, whether
or not a second party associated with the second PCD 75 is
willing to meet a first party associated with the first PCD 75
10 things, for example but not limited to, a proximity (in terms
oftime, distance, or number of stops) of the first PCD 75 to
a location or region, can indicate that the first PCD 75 has
left a location, region, or scheduled stop location, etc,
The notification communication session can be initiated at the stop location, whether or not a second party associated
wit11 the second PCD 7S is willing to accept responsibility
for a pickup or delivery at the stop location.
The stop location can be remote from the locations of the
first and second PCD 75s. The second PCD 75 could also be
located at or in close proximity to the stop location.
rs when the first PCD 75 is within a predetennined proximity
of a stop location, region, or a location of the one or more
plurality ofPCD 75s, can be initiated when the first PCD 7S
has left a location, region, or stop location, can be initiated
when the plurality ofPCDs are within a prescribed number
In alternative embodiments, first PCD 75 or the notificaa
tion system 10 can communicate another message during the
notification communication session that indicates to the
second party associated with the second PCD 75 one or more
criteria for a response to be effective. For example, the one
or more criteria may include one or more of the following:
a time limit to respond, a travel distance limit associated
with travel of the first PCD 7S, a limit based upon the first
PCD 75 traveling to a particular location or region, or a limit
based upon one or more acceptance responses from other
PCD 75s.
20 of stops or distance of the first PCD 75, etc.
In alternative embodiments, the BSCU 40, particularly the
BS manager 41, can be configured to determine whether or
not a response to a notification communication is necessary
based upon the nature of the delivery/pickup (e.g., a package
25 requiring a signature would like to be delivered, and there-
fore, a person needs to be at the stop location to sign for the
package, a package does not require a signature and there-
fore a party need not be present to deliver the package,
business or residential delivery, inside service or outside
In alternative embodiments, the one or more criteria can
30 service, etc.). When a stop does not require a response, it can
be scheduled with the other stops that do require a response.
As an example, see FIG, 26. be communicated to the notification system 10 from a
suitable communications device, such as but not limited to,
the first PCD 75, and stored in user preference data in user
data table 68b (FIG. SA). Or, the criteria can be system- 35
defined via suitable programming.
3. Third Embodiment
Yet another embodiment, among others, can be practiced
The responses from the notified PDC(s) 75 can indicate
(via suitable text messaging, voice commands, depression of
keys on a keypad to emit tones, etc.) whether or not a party
associated with a notified PCD 7S is willing to accept
responsibility for a plckup or delivery at a stop location or
meet a first party associated with the first PCD 7S at the stop
location, The stop location can be remote from the locations by the notification system 10, particularly in the manager41,
and involves the following methodology, whlch is shown in
FIG. 20C and denoted by reference numeral340c: monitor-
ing travel data associated with a first PCD 7S, as indicated
40 of the first and second PCD 7Ss.
at block 361; initiating a notification communication session
to a plurality of PCD 7Ss, the notification communication
including a message requesting a response, as indicated at 45
block 362; receiving responses from one or more of the
plurality of PCDs 7S, as indicated at block 363; and pro-
ducing a list of stops for the first PCD 75, based upon the
responses, the lack of responses, or a combination thereof,
as indicated at block 364. Although not limited to this so
application, the foregoing methodology is particularly useful
in connection with package delivery services.
Another message can be communicated by the BSCU 40
to the notified PCD(s) 7S during the notification communi-
cation that indicates one or more criteria for a response to be
effective. The one or more criteria could include, for
example but not limited to, one or more of the following: a
time limit (FIG. 25A), a travel distance Emit associated with
travel of the first PCD 7S (FIG. 25B), a limit based upon the
first PCD 7S traveling to a particular location or region (FIG.
25C), or a limit based upon one or more acceptance
responses from other PCD 75s (FIG. 2SD).
In alternative embodiments, the BS manager 41 can be
designed to receive the one or more criteria from a com-
munications device, for example, the first PCD 75. Such
criteria can be stored in user preference data,
In alternative embodiments, the BS manager 41 can be
configured to enable a party associated with the first PCD 75
to select whether or not a response is requested of a notified
party during a notification communication session.
In the preferred embodiment, the software architecture
The stop list can be produced at the notification system
10, such as in the BSCU 40, at the first PCD 75 that is being
tracked (see FIG. 26 and accompanying discussion), or at a 55
computer that is communicatively coupled to either. If
produced remote from the first PCD 75, then the list can be
communicated to the first PCD 75, stored therein, and
displayed, if desired, to enable a party associated with the
first PCD 7S to take appropriate delivery/pickup action, 60 associated with the BS manager 41 implements failure states
in connection with the request for a response. A failure state
occurs when a state of a variable has been reached without
receiving a response back from the notified party. Intemally,
The stop list can be a list of predetennined stop locations
or stop numbers, can be street address, longitude/latitude
designations, etc.
In altemative embodiments, functionality for accepting a
reply from the first PCD 75 and communicating the reply to 65
the one or more plurality of PCDs 75 that have responded
can be implemented in the BSCU 40 or in the first PCD 75
a failure state causes the system to terminate notification
communication attempts and to ensure that a stop associated
with the failed communication attempts is not scheduled on
the stop list. A failure state can also be shown on a screen or
Exhibit A
Page 108
US 7,119,716 B2
81 82
otherwise indicated to the operator of the first PCD 75, as is FIG. 23 is a graphical illustration of a possible architec·
shown in FIGS. 25A through 25D. A failure state can be ture for implementing the direct conununications configu-
system-defined or user-defined, and can be stored in table ration between a tracked PCD 75 in the form of an in-vehicle
68b (FIG. SA) and/or failure state data table 68/ (FIG. SA). navigation system and one or more other PCDs 75d-1Sh.
A<> illustrated in FIGS. 25A through 25D, a set of non- 5 The in-vehicle navigation system 75 has functional blocks
limiting examples of failure state variables are as follows: 425-428 and optional functional blocks 431-433, which can
(a) a time period variable (FIG. 25A) pertaining to the be implemented as part of the MT manager 29 or as separate
amount of time that has elapsed since invocation of the software routines, as is shown in FIG. 23. The MT manager
notification; when the time period variable has expired, it 29 (also see FIGS. 1 and 2) is designed to cause the
triggers a failure state; (b) a distance variable pertaining to 10 navigation system 75k to provide a list of locations of
the distance traveled by the tracked first PCD 75 (FIG. 25B) interest, such as local restaurants in this example. At present,
since invocation of the notification; when the first PCD 75 such technology is known in the art. The user is permitted to
has traversed a prescribed distance that is monitored with the select a listed item, in this case, the XYZ Itallan Restaurant
distance variable, then a failure state can be invoked; (c) a has been selected via the user interface buttons that are
predetermined location variable (FIG. 25C) pertaining to a 15 shown. As shown, the display indicates that a response is
location to be traversed by the moving/tracked first PCD 75; being waited upon. Also, the expected time of arrival (ETA)
in other words, once the PCD 75 has reached this predeter- is shown on the screen in terms of both time (20 minutes)
mined location, then a failure state will result; and (d) an and distance (12 tniles). Either or both of the foregoing
acceptance variable (FJG. 2SD) which tracks the number of ETAs can be communicated to the PCD 75d, depending
responses and/or acceptances associated with notification 20 upon the desired design.
communications; this is useful in a configuration where a A PCD 75 in the form of a person's networked computer
number of parties have been invited to visit a particular 75d at the XYZ Italian Restaurant is shown receiving a the
location {e.g., a restaurant), and there are only a limited notification commtmication from the in·vehicle navigation
number of openings; as an example, the system can be set to system 75k, which asks for a response, i.e., in this example,
accept the first party to respond to the notification and 25 the party associated with the tracked PCD 75k at issue is
invoke a failure state in connection with all other notifica· attempting to make a reservation at a restaurant having the
tions (which can be communicated, if desired, to the other networked computer 75d.
PCDs 75 that responded late). The text content of the message that is sent by PCD 75k
In altemative embodiments, the BS manager 41 can he toPCD75dcanbeenteredbytheuserofthePCD75dusing
designed to communicate an additional message to the 30 any suitable graphical user interface (GUI) and screen
plurality of one or more PCDs 75. As an example, this could prompts and any suitable hardware input devices, such as
be a description of the MT 17 or of the driver. buttons 441-443. The content is communicated in pack·
In alternative embodiments, a status of the responses can etized manner with the other content associated with the
be communicated by the BSCU 40 to the first PCD 75. As notification communication.
an example of a possible scheme for indicating status, the 35 Tite text content could also be prc·stored in the memory
following text coding cold be employed and could be associated with the PCD 75k and selected by the user using
displayed on a display associated with the first PCD 75: "w" any suitable GUJ and screen prompts and user interface
for waiting for a response, "c" for confirmed indicating that buttons 441-443.
a response was received and delivery/pickup is to occur, and FIG. 24 is a continuation of the example in FIG. 23 and
"u" for unconfirmed indicating that a response was received 40 shows implementation of response requests and failure
and a delivery/pickup is not to occur) states, both of which have been discussed previously.
In alternative embodiments, the BSCU 40 can be As illustrated in FIG. 24, the PCD 75d at the XYZ Italian
designed to enable a party associated with one or more of the Restaurant is used to send a response message back to the
plurality ofPCD 75s to selecl or enter a time for a pickup or in· vehicle navigation system 75k. In this case, the person
delivery at a stop location, and then this information can be 45 operating the PCD 75d creates a message indicating receipt
communicated to the first PCD 75. of the notification and confirming the reservation at a
4. Example Implementations of Tracked PCD to Notified particular time, i.e., 6:40pm., ru1d communicates this mes-
PCD Communications sage back to the PCD 75k, so that the party associated with
FIG. 21 is a graphical illustration of an example of a the PCD 75k knows that the reservation is properly sched-
notification system 10 having a base station control unit 40 50 uled.
monitoring travel of PCDs 75 and capable of communicat· Another part of the software architecture associated with
ing notifications and responses among the various PCDs 75. the PCD 75k is shown at blocks 451-457. Although not
A PCD 75 in the form of a person's networked computer 75d limited to this configuration, this functionality in this
is shown receiving a notification communication from one example is implemented in the MT manager 29 (FJGS.l and
of the tracked PCDs 75a-75c, which asks for a response, 55 2). As is clear, the user of the PCD 75k can indicate that a
i.e., in this example, the party associated with the tracked response should be requested (in user preferences stored in
PCD 75 at issue is attempting to make a reservation at a PCD 75k or othenvise during interaction with PCD 75k).
restaurant having the networked computer 75d. The PCD 75k can also be configured to determine that a
FIG. 22 is a graphical illustration of possible ways in response is necessary based upon the type of notification
which communications can occur between a tracked PCD 75 60 communication (e.g., a package requiring a signature would
and a notified PCD 75. As shown, one embodiment involves like to be delivered, and therefore, a person needs to be at the
indirect communications using the BSCU 40, while the stop location to sign for the package).
other involves direct communications betv,reen the PCDs 75. The software architecture further implements failure
In the latter case, the functionality that would have been states in connection with the request for a response. A failure
associated with the BSCU 40 is incorporated in one of the 65 state occurs when a state of a variable has been reached
devices 75 or the functionality is distributed across the without receiving a response back from the notified party.
devices 75. Internally, a failure state causes the system to terminate
Exhibit A
Page 109
US 7,119,716 B2
83 84
notification communication attempts. A failure state can also in blocks 475 478, there is looping process for determinlng
be shown on a screen or otherwise indicated to the operator whether a response is needed for the stop, based upon
of the PCD 75k, as is shown in FIGS. 25A through 25D. A whether the stop is associated with IS or OS, and for
failure state can be system-defined or user-defined, and can determining whether a response has in fact been received
be stored in table 68b (FIG. SA) and/or failure state data from those stops that require a response. In this example, the
table 681 (FIG. 5A). two foregoing processes execute concurrently.
As illustrated in FIGS. 25A through 25D, a set of non- In this example, the PCD 75c can be designed to retrieve
limiting examples of failure state variables are as follows: all stops within a particular distance of the PCD 75c (e.g., a
(a) a time period variable (FIG. 25A) pertaining to the 3 mile radlus), the location of which is known, as indicated
amount of time that has elapsed since invocation of the 10 at blocks 471-472. Then, a list is created and iteratively
notification; when the time period variable has expired, it updated, at blocks 473 and 474. Once a stop is tentatively
triggers a failure state in the PCD 75k; (b) a distance variable added to the route or listing of stops, via blocks 47-474, then
pertaining to the distance traveled by the tracked PCD 75k the looping process associated with blocks 475--478 ana-
(FlG. 25B) since invocation of the notification; when the lyzes the stop type to detennine if the stop requires a
PCD 75k has traversed a prescribed eli stance that is mon.i- 15 response and if the required response bas been received In
tared with the distance variable, then a failure state can be this example, if a stop is OS or if a stop is IS (requires a
invoked in the moving/tracked PCD 75k; (c) a predeter- response) and the response was received, then blocks
mined location variable (FIG. 25C) pertaining to a location 473-474 cause the stop to be officially added to the stop list.
to be traversed by the moving/tracked PCD 75k; in other Otherwise, when the stop is IS and no response was
words, once the PCD 15k determines that it has reached this 20 received, then the stop is removed per block 474. Further-
predetermined location, then a failure state will result; and more, system or user preferences can be set so that a stop is
(d) an acceptance variable (FIG. 250) which tracks the classified as 1S or OS.
number of responses and/or acceptances associated with FIG. 27 is an illustration showing an embodiment involv-
notification communications; this is useful in a configuration ing a delivery vehicle with tracked PCD 75c that has a
where a nwnber of parties have been invited to visit a 25 predetermined route 505, or stop list, with a number of
particular location (e.g., a restaurant), and there are only a prescheduled delivery stops, for example, destinations #01
limited number of openings; as an example, the system can through #03. In this embodiment, the BS manager 41 or
be set to accept the first party to respond to the notification PCD 75c has functionality 500 that is designed to cause a
and invoke a failure state in connection with ali other notification communication to be initiated to a PCD 75d at
notifications (which can be communicated, if desired, to the 30 a point when the tracked PCD 75c is a predefined proximity,
other PCDs 75 that responded late). for example_, at or about 30 minutes, from a delivery
FIG. 26 illustrates an embodiment that can be irnple- destination . .AJso, the BS manager 41 is designed so that a
mented, if desired, in connection with a vehicle having a failure state will occur if a response is not received from the
route-or-stop-list device 75c (FIG. 21) that determines PCD 75d within predefined time period, for example, 20
whether a response to a notification is needed, based upon 35 minutes, of the notification. Furthermore, the driver associ-
user preferences, system preferences, and/or the nature/type ated with the tracked PCD 75d is notified of the occurrence
(e.g., business or residential, inside service or outside ser- of the failure state or confinnation, for example, via suitable
vice, etc.) of the stop. text (e.g., "Confirmed" or "No Response" in the event of a
In this nonlimiti.ng example, a determination is made as to ±ailure state) on a screen associated with the PCD 75d, so
whether the stop is associated with (a) inside service (IS; for 40 that the driver associated with the PCD 75c knows whether
example, a signature must be obtained to drop off a package, or not to make the stop at destination #03.
a person must inspect an item before dropo:ff, a person must FIG. 28 is an illustration showing an embodiment involv-
personally provide an item for pickup, a user has requested ing a delivery vehicle with tracked PCD 75c that has a
that a response from the user must be received before the predetermined route 506, or stop list, with a number of
user is scheduled for a delivery/pickup, etc.) or (b) outside 45 prescheduled delivery stops, for example, destinations #04
service (OS; for example, an item can be dropped off through #06. In this embodiment, the BS manager 41 or
without signature, an item is waiting outside a building to be PCD 15c has functionality that is designed to cause a
picked up and nobody needs to be present to give the item notification communication to be initiated to a PCD 75 at a
to the pickup vehicle, etc.). point when the tracked PCD 75c is a predefined proximity
The functionality associated with this embodiment, as 50 in tenns of distance from a delivery destination. Also, the BS
defined at blocks 471-478, can be implemented in the BSCU manager 41 is designed so that a failure state will occur if a
40 and.Jor the tracked PCD 75c. In this embodiment, it is response is not received from the notified PCD 75 based
implemented solely in the PCD 75c, and the route or stop list upon one or more failure state criteria. Furthermore, the
that is generated and periodically changed by the PCD 75c driver associated with the tracked PCD 75d is notified ofthe
is periodically communicated to the BSCU 40. Furthermore, 55 occurrence of the failure state or confinnation, for example,
in terms of external controls and user interlacing, the PCD via suitable text (e.g., "Confirmed" or "No Response" in the
75c has, as shown in FIG. 26, a screen for listing stops and event of a failure state) on a screen associated with the PCD
the type of stop, a notify button to initiate a notification 75d, which in this case, is in the form of an in-vehicle
communication, a retry button to retry a notification com- navigation system, so that the driver associated with the
munication, a move button to move a cursor on the screen 60 PCD 75c knows whether or not to make particular stops.
and/or to move through the stop list, a menu button to move As shown on the screen, two deliveries have been con-
through various menus and submenus, and a cursor move- firmed, and the system still awaits a response involving the
ment control with arrows in the center, which can be also be delivery for destination #04. The PCD 75c can be equipped
used to scroll through the listing of stops. with suitable programming to enable the driver to scroll
In terms of internal programming, as shown in blocks 65 through and select (e.g., via arrows on menu button and
471--474, there is a looping process for creating, determin- select buttons, as shown) or otherwise enter the deliveries
ing, and/or changing the route or stop list, and as illustrated that the driver intends to make, based upon the confirmation/
Exhibit A
Page110
US 7,119,716 B2
85
no-response information pertaining to each destination as
well as the distance information provided to the driver on the
screen. This selection or entry, or infonnation indicative
thereof, can be communicated from the PCD 7Sc to the
appropriate confirmed PCD, directly or indirectly via the
BSCU 40, depending upon the notification system imple-
mentation. In some implementations, the selection or entl)'
information is communicated only to the BSCU 40 for
tracking purposes and is not fonvarded to the confirmed
PCD.
FIG. 29 is an illustration of another embodiment involvM
ing a delivery vehicle having a PCD 7Sc, which shows
functionality at blocks Sll-,-515 that can be programmed into
the PCD 75c for updating a stop list based upon whether or
not responses were received. The software can be designed
to show confirmed and unconfinned (no response) stops or
to show only confinned stops, as desired, on the screen of
the PCD 75c.
FIG. 30 is an illustration of an embodiment that can be
implemented at the BSCU 40, such as the BS manager 41
(FIGS.1 and3) or at theMTCU 15, such as the MTmanager
29 (FJGS.l and 3), showing implementation of failure states
in connection with responses and nonresponses to notificaM
tion commtmications in the context of a delivery vehicle. As
shown at respective blocks 542 and 543 and as described
previously, failure states can be user defined and/or system
defined. Furthermore, failure states can be defined in a
number of ways, a few examples of which are indicated at
blocks 544-548.
86
of user interface screens to be described in paragraphs to
follow can also be generated and communicated to a party
in this manner,
As shown in FIG. 33) the screen prompts the party to
make a decision as to whether or not the party wishes a
response to a notification communication. This screen can be
used in connection with the response systems and methods
that have been described previously in this document. This
selection can be stored in the database 94 (FIG. 5A), such as
10
in users preferences in user data table(s) 68b.
FIG. 34 shows another example of a possible user inter-
face screen that can be generated by the GUI of FIG. 3 and
used in connection with the response systems (and methM
15
ads). This screen can be used separately or in addition to the
one of FIG. 33.
As shown, this screen can be used to solicit selections
from a party that will be used by the BS manager 41 in
connection with nonresponses (failure states). These
20
tions can be stored in the database 94 (FIG. SA), such as in
users preferences in user data table(s) 68b. Reference
numerals 605----607 illustrate questions relating to when
failure states should occur after a notification and response
request have been communicated to a notified party, while
25
reference numeral 60S illustrates a selection for enabling the
party to define what will occur when no response is received
by the BSCU 40. An example of a screen for enabling a party
to select such options is shown in FIG. 39.
FIG. 31 is an illustration of another embodiment that can 30
be implemented at the BSCU 40, such as the BS manager 41
(FIGS.1 and3) or at the MTCU 15, such as theMTmanager
Referring now to FIG. 35, FIG. 35 shows another example
of a possible user interface screen that can be generated by
the GUI of FIG. 3 and used in connection wifu the response
systems (and methods). Tbis screen can be used separately
or in addition to those screens of FIGS. 33 and 34. 29 (FIGS. 1 and 3), showing implementation of failure states
As shown, this screen can be used to solicit selections
from a party that will be used by the BS manager 41 in
connection with nonresponses (and occurrence of failure
states). These selections can be stored in the database 94
(FIG. SA), such as in users preferences in user datci table{s)
68b. Reference numeral608 illustrates a question relating to
in connection with responses and nonresponses to
tion communications in the context of a delivery vehicle. 35
Blocks 561-568 represent the high level architecture of the
software. As illustrated, the stop list can be determined and
changed dynamically, based upon responses and
spouses . .Also, a request for a pickup can be introduced into
the stop Jist of scheduled deliveries at any point.
40 when a failure state should occur after a notification and
response request have been communicated to a notified
party) while reference numeral 609 illustrates a selection for
enabling the party to define what will occur when no
FIG. 32 is an illustration of an embodiment of route data
471 and corresponding driver display data that can be
maintained and implemented in connection with a delivery
or pickup service. The route data 471 can be maintained at
the BSCU 40, at theMTCU 1S, or at both. The driver display 45
data 472 is displayed to the driver of the delivery/pickup
vehicle 17.
response is received by the BSCU 40. An example of a
screen for enabling a party to select such options is shown
in FIG. 39.
Note that, in this example, the party can set the system so
that a failure state will occur in the event that a notified party
does not respond before the vehicle 17 travels to within a
preset number of stops from a scheduled stop location, or
destination.
With reference to FIG. 36, FJG. 36 shows another
example of a possible user interface screen that can be
generated by the GUT of FIG. 3 and used in connection with
the response systems (and methods). This screen can be used
separately or in addition to those of FIGS. 33-35.
As indicated at reference nwneral 477 in the driver
display data 472, the status of response and nonresponses to
notifications is monitored and shown to the driver. In this so
example embodiment, the status is "C" for confirmed fOr the
situation where a response has been received and the notified
party is willing to commit to the pickup/delivery, is "U" for
unconfrrmed for the situation where a response has been
received and the notified party does not want to commit to ss
the pickup/delivery or it is unclear whether the notified party
wishes to commit, and is "W" for waiting for the situation
where a response that has not been received at all from the As shown, this screen can be used to solicit selections
notified party. from a party that will be used by the BS manager 41 in
Preferably, although not necessarily, the BSCU 40, par- 60 connection with failure states. These selections can be stored
ticularly the BS manager 41, is equipped with a suitable in the database 94 (FIG. SA), such as in users preferences in
graphical user interface (Gill), denoted by reference user data table(s) 68b. Reference numerals 621 and 622
numeral46 in FIG. 3, to enable a party to cmmnunicate with illustrate questions relating to when failure states should
the BSCU 40 via the Internet. FIG. 33 shows an example of occur after a notification and response request have been
a possible user interface screen that can be generated by the 65 communicated to a notified party.
GUI 46 and pushed to the remote communications device FIG. 37 shows another example of a possible user inter-
via, for example, HTML over the Internet. Other examples face screen that can be generated by the Gill of FIG. 3 and
Exhibit A
Page111
US 7,119,716 B2
87
used in connection with the response systems (;:md meth-
ods). This screen can be used separately or in addition to
those of FIGS. 33-36.
As shown, this screen can be used to solicit selections
from a party that will be used by the BS manager 41 in
connection with failure states. These selections can be stored
in the database 94 (FIG. SA), such as in users preferences in
user data table(s) 68b.
Reference numeral 631 illustrates a marker that can be
moved across a map of streets, for example, via a mouse, and
used to select one or more locations on the map pertaining
to when a failure state should occur for nonresponsiveness
on the part of the notified party. The marked location(s)
pertains to the moving vehi de 17 that is headed for the stop
location, or destination, which, in this example, is 1010 Oak
Lane.
U.S. Pat. No. 6,618,668, which is incorporated herein by
reference, describes a mapping system for a notification
system that can be used to implement the input-via-map
functionality illustrated in FIG. 37 (as well as FIG. 38).
FIG. 38 shows another example of a possible user inter-
face screen that can be generated by the GU1 of FIG. 3 and
used in connection with the response systems (and meth-
ods). This screen can be used separately or in addition to
those of FlGS. 33-37.
As shown, this screen can be used to solicit selections
fium a party that will be used by the BS manager 41 in
connection with failure states. These selections can be stored
in the database 94 (FIG. 5A), such as in users preferences in
user data table(s) 68b. Reference numeral 632 illustrates a
circle perimeter that can be moved, expanded in size, and/or
reduced in size in relation to the map of streets, for example,
via a mouse, and used to select a geographic region on the
map pertainlng to when a failure state should occur for
nonresponsivcncss on the part of the notified party. The
marked area(s) pertains to the moving vehicle 17 that is
headed for the stop location, or destination, which, in this
example, is 1010 Oak Lane.
FIG. 39 shows another example of a possible user
face screen that can be generated by the GU1 of FIG. 3 and
used in connection with the response systems (and meth-
ods). This screen can be used separately or in addition to
those of FIGS. 33-38.
As shown, this screen can be used to solicit selections
from a party that will be used by the BS manager 41 in
connection with failure states. This screen enables a party to
define what will occur in the event of occurrence of a failure
state in connection with nome::.1Jonsiveness by a notified
party. These selections can be stored in the database 94 (FIG.
SA), such as in users preferences in user data table(s) 68b.
Reference numerals 644--648 illustrate possible options that
can be selected by the party.
FIG. 40 shows an example of another type of computer
network message. As shown in FIG. 40, an electronic mail
(email) message can be generated and sent by the BSCU 40
(FIG. 3) over the Internet and used in connection with the
response systems (and methods).
88
There are many possible variations of this concept. For
example, the email could provide a plurality of options, one
of which can be selected by the party. Furthermore, there
could be different charges associated with different delivery
time options (e.g., more expensive options for faster service,
etc.).
Further note that this information from the notified party
can be communicated to a PCD 75c associated with the
delivery vel1icle 17 and correlated with other scheduling
10 information at the PCD 75c.
W. Notification Failure Detection Systems (and Methods)
that Cause Implementation of one or more Tasks When a
Scheduled Notification Communication is not Received
15
A notification failure detection system can be imple-
mented in connection with a PCD 75 (FIG. 1) that is
scheduled to be notified that will cause one or more tasks to
be performed in the event that such PCD 75 does not in fact
receive a scheduled notification communication.
20
As an example of an application of the notification failure
detection system, among numerous possible scenarios, con-
sider an -implementation where a service provider (e.g.,
maid, pool maintenance worker, lawn care worker, etc.) is
scheduled to provide service at a residential home, and the
25
service provider is to initiate a notification communication
to a PCD 75 at the house. A notification failure detection
system situated in or communicatively coupled to the PCD
75 can be designed to monltor for the incoming notification
communication. If one does not occur as scheduled, then the
30
notification failufe detection system can be designed to
perform one or more tasks, for instance, communlcating
with another service provider to request service from the
another instead, communicating with the home owner to
advise the home owner of the fiiilure state
1
communicating
35
with the service provider office, communicating with a
security company that can check on the service provider, or
communicating with another party or system, etc.
As another example of an application, among numerous
possible scenarios, consider an implementation where a
40 home owner, after completing work each day, is scheduled
to provide a notification comniunication to a PCD 75 at
his/her borne within a prescribed time period, indicating
impending arrival. When the notification communication is
received during the prescribed time period, then the notifi-
45 cation failure detection system can be designed to do noth-
ing or perform one or more steps, such as adjust the air
conditioning or heater down or up. However, when the
notification communication is not received during the pre-
scribed time period, then the notification failure detection
so system can be designed to perform one or more tasks, such
as turn on light switches (because it will be dark when the
home owner approaches since the home owner will be late).
When the notification communication is received during the
prescribed time period, then the notification failure detection
55 system can be designed to do nothing or perform one or
more steps. Moreover, when the notification communication
is not received during the prescribed time period, then the
noti:ficatim1 failure detection system can be designed to
perform one or more tasks, such as communicate with
60 another fire or police station.
As yet another example of an application, among numer-
ous possible scenarios, consider an implementation where
the notification failure detection system is designed to
monitor a fire or security alarm system associated with a
As illustrated, a party can be sent an email by the BSCU
40 during a notification communication to indicate
ing arrival of a delivery vehicle at a stop location, such as the
party's street address. In this example, the .notification
communication, in the form of an email sent over the
Internet to the party by the BSCU 40 asks the party to
identify when the party is available for the delivery. The
information input by the party can be utilized to fine tune the
scheduling of the delivery vehicle 17.
65 facility and to determine whether a notification communi-
cation is received from a fire or police station within a
prescribed time period after the alann is triggered. When the
Exhibit A
Page 112
us 7,119,716 82
89 90
alann gets triggered and no notification communication is CDR OM, etc.). Moreover, the memory 714 may incorporate
received indicating that the fire or police department is on electronic, magnetic, optical, andlor other types of storage
their way, then the notification failure detection system can media. Note that the memory 714 can have a distributed
be designed to contact another party, such as the owner, architecture, where various components are situated remote
another fire department, another police department, etc. from one another, but can be accessed by the processor 712 .
• A.s still another example of an application, among I l U m e r ~ The software in memory 714 may include one or more
ous possible scenarios, the notification failure detection separate programs, each of which comprises an ordered
system can be implemented in connection with cargo ships, listing of executable instructions for implementing logical
tankers, or other ships. An incoming vessel to a harbor can functions. In the example of FIG. 41, the software in the
be scheduled to send a notification communication (which 10 memory 714 includes notification failure detection sofuvare
can include the ship identity and/or other particulars per- 710 and a suitable operating system (0/S) 722. A nonex-
taining to the ship and/or hs cargo) to the harbor master haustive list of examples of suitable commercially available
(which typically determines when the vessel will dock and operating systems 722 is as follows: (a) a Windows oper-
sends out tug boats) when the incoming vessel is near and ating system available from Microsoft Corporation; (b) a
ready to dock. TI1e notification failure detection system can 15 Netware operating system available from Novell, Inc.; (c) a
be designed to contact the coast guard or other security Macintosh operating system available from Apple Com-
group if a ship is approaching and no notification commu- puter, Tnc.; (e) a lJl'..llX operating system, which is available
nication is received after the ship has come within a pre- for purchase from many vendors, such as the Hewlett-
defined proximity of the harbor or dock location. In an Packard Company, Sun Microsystems, Inc., and AT&T
alternative embodiment, the notification failure detection 20 Corporation; (d) a LINUX operating system, which is free-
system can be designed to contact providers of services ware that is readily available on the Internet; (e) a run time
(unloaders, customs personnel, crane operators, truck driv· Vxworks operating system from WindRiver Systems, Inc.;
ers, etc.) that were intending to meet the ship at the dock at or (f) an appliance-based operating system, such as that
a prescribed time or time period, so t11at the service provid- implemented in handheld computers or personal data assis-
ers can cancel their trips to the dock and/or take other 25 tants (PDAs) (e.g., PalmOS available from Palm Comput-
remedial actions. ing, Inc., and Windows CE available from Microsoft Cor-
The notification failure detection system can be imple- poration). The operating system 722 essentially controls the
mented in software (e.g., firmware), hardware, or a combi· execution of other computer programs, such as the notifi-
nation thereof. In the currently contemplated best mode, the cation failure detection software 710, and provides sched-
notification failure detection system is implemented with a 30 uling, input-output control, file and data management,
computer-based system that is a combination of hardware memory management, and communication control and
and software. An example of a general purpose computer related services.
that can implement the notification failure detection system The notification failure detection software 710 is a source
is shown in FIG. 41. In FIG. 41, the notification failure program, executable program (object code), script, or any
detection system is denoted by reference numeral 701. J5 other entity comprising a set of instructions to be pcrfonned.
Generally, in tem1s of hardware architecture, as shown in When a source program, then the program needs tO be
FIG. 41, the computer-based system 701 includes a proces- translated via a compiler, assembler, interpreter, or the like,
sor 712, memory 714, and one or more input and/or output which may or may not be included within the memory 714,
(IIO) devices 716 (or peripherals) that are communicatively so as to operate properly in connection with the 0/S 722.
coupled via a local interface 718. The local interface 718 can 40 Furtbennore, the notification failure detection software 710
-be, for example hut not limited to, one or more buses or other can be written as (a) an object oriented programming
wired or wireless connections, as is known in the art. The language, which has classes of data and methods, or (b) a
local interface 18 may have additional elements, which are procedure programming language, which has routines, sub-
omitted for simplicity, such as controllers, buffers (caches), routines, and/or functions, for example but not limited to, C,
drivers, repeaters, and receivers, to enable communications. 45 C++, Pascal, Basic, Fortran, Cobol, Perl, Java, and Ada.
Further, the local interface may include address, control, The optional I/0 devices 716 may include input devices,
and/or data cormcctions to enable appropriate commun.ica- for example but not limited to, a keyboard, mouse, scanner,
tions among the aforementioned components. microphone, etc. Furthermore, the 1/0 devices 716 may also
The processor 712 is a hardware device for executing include output devices, for example but not limited to, a
software, particularly that stored in memory 714. The pro- so printer, display, etc. Finally, the ]/0 devices 716 may further
cessor 712 can be any custom made or commercially avail- include devices that communicate both inputs and outputs,
able processor, a central processing unit (CPU), an auxiliary for instance but not limited to, a modulator/demodulator
processor among several processors associated with the (modem; for accessing another device, system, or network),
system 701, a semiconductor based microprocessor (in the a radio frequency (RF) or other transceiver, a telephonic
form of a microchip or chip set), a macroprocessor, or 55 interface, a bridge, a router, etc.
generally any device for executing software instructions. If the computer-based notification failure detection sys-
Examples of suitable commercially available microproces- tern 711 is a PC, workstation, or the like, the software in the
sors are as follows: a PA-RISC series microprocessor from memory 714 may further include a basic input output system
Hewlett-Packard Company, an 80x86 or Pentium series (BIOS) (omitted for simplicity). The BIOS is a set of
microprocessor from Intel Corporation, a PowerPC micro- 60 essential software routines that initialize and test hardware at
processor from IBM, a Spare microprocessor from Sun startup, start the 0/S 722, and support the transfer of data
Micro systems, Inc, or a 68xxx series microprocessor from among the hardware devices. The BIOS is stored in ROM so
the Motorola Corporation. that the BIOS can be executed when the system 701 is
The memory 714 can include any one or combination of activated.
volatile memory elements (e.g., random access memory 65 - When the system 701 is in operation, the processor 712 is
(R.t\M, such as DRAM, S:R..t\M, SDRAM, etc.)) and non- configured to execute software stored within the memory
volatile memory elements (e.g., ROM, hard drive, tape, 714, to communicate data to and from the memory 714, and
Exhibit A
Page 113
us 7,119,716 82
91
to generally control operations of the computer 711 pursuant
to the software. The notification failure detection software
710 and the 0/S 722, in whole or in part, but typically the
latter, are read by the processor 712, perhaps buffered within
the processor 712, and then executed.
92
X. Other Variations and Modifications
In concluding the detailed description, it should be noted
that the terminology "preferred embodiment" herein means
~ h e one example embodiment currently believed by the
inventor(s) to be the best embodiment of a plurality of
possible embodiments. Moreover, it will be obvious to those
skilled in the art that many variations and modifications may
be made to the preferred embodiment(s) without substan-
tially departing from the principles of the present invention.
The notification failure detection software 710 (as well as
any other software that is described in this document), as is
shown in FIG. 41, can be stored on any computer readable
medium for transportatjon or use by or in connection with
computer related systems. In the context of this document,
a computer readable medium is an electronic, magnetic,
optical, or other physical device or means that can contain
10 All such variations and modifications are intended to be
or store a computer program for use by or in connection with
a computer related system or method. In the context ofthis 15
document, a "computer-readable medium" can be any
means that can store, communicate, propagate, or transport
the program for use by or in cormection with the instruction
execution system, apparatus, or device. The computer read-
able medium can be, for example but not limited to, an 20
electronic, magnetic, optical, electromagnetic, infrared, or
semiconductor system, apparatus, device, or propagation
medium.
included herein within the teachings of the present invention
in this document and to be protected by the scope of the
following claims. A few examples of possible variatioru;
and/or modifications are set forth hereafter.
With respect to variations, note that although not specifi-
cally described for simplicity, any combination of the vari-
ous systems/methods that have been described under head-
ings above may be employed in connection with a
notification system. For example, use of authentication data
for secure notification messaging can be employed in con-
nection with one of the versions of the response system,
As another example of a variation, it is possible to
implement the systems and methods of this patent applica-
tion in connection with notification systems where notifica-
In an alternative embodiment, where the notification
failure detection system 701 implemented in hardware, the
notification failure detection system can be implemented
with any or a combination of the following technologies,
which are each well known in the art: a discrete logic
circuit(s) having loglc gates for implementing logic func-
tions upon data signals, an application specific integrated
circuit (ASIC) having appropriate combinational logic gates,
a prograrnm.able gdte array(s) (PGA), a field programmable
gate array (FPGA), etc.
25 tions are made from the moving thing itself (those systems
that do not utilize a BSCU 40 to implement the notifica-
tions). Essentially, the functions associated with the BSCU
40 are implemented in the tracked MT 17. One such system
is described in U.S. Pat. No. 5,444,444, which is incorpom
30 rated herein by reference in its entirety.
iw example of a possible architecture, among others, of
35
the notification failure detection software 710, is shown in
FIG. 42. As iiiustrated by way of flow chart in FIG. 42, the
notification failure detection software 710 is designed to
perform the following steps; storing information in memory
714 pertaining to timing (e.g., a time of day, time period,
40
etc.) associated with the scheduled notification communica-
tion, as indicated at block 731; determining that the sched-
uled notification communication failure has occurred, based
upon the timing information, as indicated at block 732; and
causing one or more tasks to be performed using I/0
45
device(s) 716 and/or using PCD 75 based upon the sched-
uled notification communication failure, as indicated at
block 733. TI1e tasks can include, for example but not
limited to, initiation of voice and/or data communications to
other parties or systems, actuation or adjustment of switches
50
or transducers, etc.
Note that failure in the context of the notification failure
As another example of a variation, MTCU 15 and/or the
BSCU 40 can be implemented within a single computer
system, across a plurality of computers that are communi-
catively coupled, or within a computer system having a
distributed architecture.
As another example of a variation, the notification system
can be one that notifies a party or PCD 75 after an MT 17
leaves or while an MT 17 is located at a location, as opposed
to a notification system that notifies a party or PCD 75 in
advance of arrival of the MT 17 at the location, as with the
notification system 10 described herein.
As another example of a variation, the BS manager 41 can
be designed to cause the notification system 10 to notifY the
user based upon a arrival time and/or departure time data in
a schedule or route of one or more stops associated with the
MT 17, as opposed to basing the notifications on real time
monitoring of the location of the MT 17.
As another example of a variation, the BS manager 41 can
be designed to cause the notification system 10 to notify the
user when the Mr' s schedule has been changed or the MT' s
stop at a location has been cancelled, as opposed to waiting
on tracking information to determine delay in arrivaJ or
departure of the MT 17. This information could be input
manually by a person or it could come from another com-
detection system 701 can be defined as failing to receive a
notification communication at a scheduled time or time
period, failing to receive a notification communication when
the system 701 knows or is advised that the system 701
should have based upon the MT 17 reaching a location or
region or distance 11-om the stop location, or as failing to
receive proper authentication indicia (which can be stored,
accessed, and analyzed in memory 714) during the notifi-
cation communication session. The authentication indicia,
or information, can be any of a number of things, for
example, a caller's telephone number, which can be com-
pared with an incoming telephone caller ID to determine if
there is a match. For other examples, see the section in this
document relating to secure notification messaging systems
and methods.
55 puter system. The software associated with the BS manager
41 could aJso be configured to enable a user to configure the
system so that the user is notified upon a change and/or
cancellation.
As another example of a variation, the notification system
60 (as well as the inventions claimed herein) can be employed
in connection with an amusement park ride, for instance, a
roller coaster, water vehicle, etc. PCDs 75 can be handed out
to prospective passengers of t11e ride, and when appropriate,
one or more of the devices 75 can be notified to alert one or
65 more prospective passengers their departure time (or arrival
time of their pickup mobile vehicle) is near. Any suitable
form of tracking can be utilized. For example, a passenger
Exhibit A
Page 114
US 7,119,716 B2
93
wait list or queue can be maintained and tracked (which
leads to an indirect way of monitoring the mobile vehicles).
As another example of a variation, the notification system
(as weil as the inventions claimed herein) can be employed
in cormection with electronic tags on assets (e.g., packages,
luggage, containers, etc.) that are being warehoused or
shipped to notify a party concerning the travel status of such
assets. Typically, an electronic tag has a controller, a trans-
ceiver controlled by the controller, and a memory that is
controlled by the controller and that stores an identification to
that can be commWlicated by the transceiver. U.S. Pat. No.
6,144,301, which is incorporated by reference, describes an
example of a tag and U.S. Pat. No. 5,774,876, which is
incorporated herein by reference in its entirety, describes a
system for monitoring assets with electronic tags. The BS 15
manager 41 can be designed to communicate with the
operations center 13 and/or the computer 14, both described
in the '876 patent, to track the assets and make notifications
pertaining to the assets. However, note that any design of
electronic tag can be utilized. 20
U.S. Pat. Nos. 6,408,108 and 6,211,781, which are both
also incorporated by reference, disclose systems that utilize
tags to track articles. A notification system (and the systems/
methods claimed herein) can be implemented in the context
of these tag systems. As an example, notification commu- 25
nications can be initiated from computer 118 in these
patents.
The invention claimed is:
94
initiating a first notification communication to a personal
communications device associated with a party based
upon the contact data;
receiving a response communication from the party's
personal commlmications device;
changing the contact data based upon the response com-
munlcation;
refraining from sending notification communications to
the party's personal communications device based
upon the change in the contact data; and
inltiating a second notification communication to the
party's personal communications device, one or more
other personal communications devices, or both, after
detection of occurrence of one or more events.
9. The method of claim 8, wherein the one or more events
comprises at least receipt of a second communication from
the party's personal communications device.
10. The method of claim 8, wherein the one or more
events comprises at least expiration of a predefined time
period.
11. The method of claim 8, wherein the one or more
events comprises arrival presence, or departure of a mobile
thing with respect to a location.
12. The method of claim 8, wherein the one or more
events comprises scanning a machine readable code on -an
object.
1. A method for communications in connection with a
computer-based notification system, comprising the steps of:
initiating a notification communication to a personal
communications device associated with a party;
receiving a response communication from the party's
personal communications device,
13. The method of claim 8, wherein the one or more
events comprises actuation of a manually or automatically
actuated switch that is associated with a mobile thing.
30
14. The method of claim 8, further comprising the step of
refraining from sending notification communications to one
or more additional personal communications devices.
15. The method of claim 8, wherein the step of initiating
a first notification communication is performed when a
35
mobile thing is a predetermined proximity with respect to a
location.
indicating that the party has received the notification
communication and is now occupied with a task asso-
ciated with the notification communication; and
refraining from sending any further notification commu-
nications to the party's personal communications
device, until detection of one or more events that
indicate that the party is no longer occupied with the
task and can perform another task associated with
another notification communication.
16. The method of claim 8, wherein the steps are per-
formed with a single computer system, a plurality of com-
40 puters that are communicatively coupled, or a computer
system having a distributed architecture.
2. The method of claim 1, wherein the one or more events
45
comprises at least receipt of a second communication from
the party's personal communications device.
3. The method of claim 1, wherein the one or more events
comprises at least expiration of a predefined time period.
50
4. The method of claim 1, wherein the one or more events
17. The method of claim 8, thither comprising the steps
of:
monitoring travel data associated with a mobile· thing;
perl'orming the step of initiating the first notification
communication based upon the relationship of a mobile
thing to a location; and
performing the step of initiating the second notification
communication based upon the relationship of the
mobile thing or another mobile thing to the location or
another location.
comprises at least arr:ival or departure of a mobile thing at or
from a location, respectively.
5. The method of claim 1, further comprising the step of
refraining from sending notification communications to one
or more additional personal communications devices.
18. A method for communications in connection with a
computer-based notification system and a personal commu-
nications device associated with a party, comprising the
55 steps of:
6. The method of claim 1, wherein the step of initiating
the notification communication is performed when a mobile
thing is a predetermined proximity with respect to a location.
7. The method of claim 1, wherein the steps are performed
60
with a single computer system, a plurality of computers that
are comrmmicatively coupled, or a computer system having
a distributed architecture.
8. A method for communications in connection with a
computer-based notification system, comprising the steps of: 65
storing contact data in memory pertaining to one or more
party personal communications device;
receiving a notification communication with the personal
communications device associated with the party from
the notification system;
communicating a response communication from the par-
ty's personal communications device, indicating that
the party has received the notification communication
and is now occupied with a task associated with the
notification communication; and
causing the notification system to refrain from sending
any further notification communications to the party's
personal communications device, until detection of one
or more events, indictating that the party is no longer
Exhibit A
Page 115
US 7,119,716 B2
95
occupied with the task and can perform another task
associated with another notification communication.
19. The method of claim 18, wherein the response com-
munication is generated by a physical action taken by the
party associated with the personal communications device.
20. TI1e method of claim 18, wherein the response com-
munication is generated by physically detecting the presence
of the party associated with the personal conununications
device.
21. A method fOr communications in connection with a
10
computer-based notification system, comprising the steps of:
storing contact data in memory pertaining to one or more
party personal communications devices,
initiating a notification communication to a personal
15
communications device associated with a party based
upon the contact data;
receiving a response communication from the party's
personal comnnmications device;
changing the contact data based upon the response com-
20
munication; and
modifying a manner in which future notification commu-
nications are implemented, based upon the change in
the contact data.
22. The method of claim 21, wherein the step of mocli- 25
fying comprises refraining from sending notification com-
munications to the party's personal communications device
after receiving the response communication, until detection
of one or more events.
96
30. The method of claim 29, further comprising the step
of refraining from sending notification communications to
one or more additional personal communications device.
31. The method of claim 29, wherein the step of initiating
the first notification communication is perfonned when a
mobile thing is a predetermined proximity with respect to a
location.
32. The method of claim 29, wherein the steps are
performed with a single computer system, a plurality of
computers that are communicatively coupled, or a computer
system having a distributed architecture.
33. The method of claim 29, wherein the response com-
munication is generated by a physkal action taken by the
party associated with the personal communications device.
34. The method of claim 29, wherein the response com-
munication is generated by physically detecting the presence
of the party associated with the personal communications
device.
35. A method for communications in connection with a
computer-based notification system, comprising the steps of:
initiating a first notification communication to a personal
communications device associated with a party;
receiving a response communication from the party's
personal communications device;
refraining from sending notification communications to
the party's personal communications device after
receiving the response communication; and
initiating a second notification communication to the
party's personal communications device, one or more
other personal communications devices, or both, after
detection of the scanning of a machine readable code
on an object.
23. The method of claim 22, wherein the one or more 30
events comprises at least one or more of the following;
receipt of a second communication from the party's personal
communications device; expiration of a predefined time
period; or arrival or departure of a mobile thing at or from
36. The method of claim 35, further comprising the step
of refraining from sending notification communications to
35
one or more additional personal communications devices.
37. The method of claim 35, wherein the step of initiating
the first notification communication is performed when a
mobile thing is a predetermined proximity with respect to a
40
location.
a location, respectively.
24. The method of claim 22, further comprising the step
of refraining :from sending notification communications to
one or more additional personal communications devices.
25. The method of claim 21, wherein the step of initiating
the notification commun.lcation.is performed when a mobile
thing is a predetermined proximity with respect to a location.
38. The method of claim 35, wherein the steps are
perfOrmed with a single computer system, a plurality of
computers that are communicatively coupled, or a computer
system having a distributed architecture.
26. The method of claim 21, wherein the steps are
performed with a single computer system, a plurality of
computers that are communicatively coupled, or a computer
system having a disttibuled architecture.
45
39. The method of claim 35, wherein the response com-
munication is generated by a physical action taken by the
party associated with the personal communications device.
40. The method of claim 35, wherein the response com-
munication is generated by physically detecting the presence
50
of the party associated with the personal communications
device.
27. TI1e method of claim 21, wherein the response com-
munication is generated by a physical action taken by the
party associated with the personal communications device.
28. The method of claim 21, wherein the response com-
munication is generated by physically detecting the presence
of the party associated with the personal communications
device.
29. A method for communications in connection with a
computer-basednotification system, comprising the steps of:
55
initiating a first notification communication to a personal
communications device associated with a party;
receiving a response communication from the party's
personaJ comnnmications device;
refraining from sending notification communications to 60
the party's personal communications device after
receiving the response communication;
initiating a second notification communication to the
party's personal communications device, one or more
otber personal communications devices, or both, after 65
detection of a receipt of a second communication iTem
the party's personal communications device.
41. A method for communications in connection with a
computer-based notification system, comprising the steps of:
monitoring travel data associated with a mobile thing;
initiating a first notification communication to a personal
commuillcations device associate with a party based
upon the relationship of the mobile thing to a location;
receiving a response communication from the party's
personal cornm1mications device;
refraining from sending notification communications to
the party's personal communications device after
receiving the response communication; and
initiating a second notification communication to the
party's personal communications device, one or more
other personal communications devices, or both, based
upon the upon the relationship of the mobile thing or
another mobile thing to the location or another location.
Exhibit A
Page 116
US 7,119,716 B2
97
42, The method of claim 41, further comprising the step
of refraining from sending notification communications to
one or more additional personal communications devices.
43. The method of claim 41, wherein the step of initiating
the first notification communication is performed when a
mobile thing is a predetermined proximity with respect to
the location.
44. The method of claim 41, wherein the steps are
performed with a single computer system, a plurality of
computers that are communicatively coupled, or a computer
system having a distributed architecture.
45. The me1hod of claim 41, wherein the response com-
munication is generated by a physical action taken by the
party associated with the personal communications device.
46. The method of claim 41, wherein the response comw
munication is generated by physically detecting the presence
of the party associated with the personal communications
device.
98
means for initiating a second notification communication
to the party's personal communications device, one or
more other personal communications devices, or both,
after detection of occurrence of one or more events.
55. The system of claim 54, wherein the one or more
events comprises at least receipt of a second communication
from the party's personal communications device.
56. The system of claim 54, wherein the one or more
events comprises at least expiration of a predefined time
10 period.
57. The system of claim 54, wherein the one or more
events comprises arrival, presence, or departure of a mobile
thing with respect to a location.
58. The system of claim 54, wherein the one or more
15 events comprises scannlng a machine readable code on an
object.
47. A computer-based notification system, comprising:
means for initiating a notification communication to a
20
personal communications device associated with a
party;
59. The system of claim 54, wherein the one or more
events comprises actuation of a manually or automaticaliy
actuated switch that is associated with a mobile thing.
60. The system of claim 54, further comprising a means
for refraining from sending notification communications to
one or more additional personal communications devices.
61. The system of claim 54, wherein the initiating means
initiates the first notification communication when a mobile
thing is a predetermined proximity wiTh respect to a location.
means for receiving a response communication from the
party's personal communications device, indicating
that the party has received the notification communi-
25
cation and is now occupied with a task associated with
the notification communication; and
means for refraining from sending any further notification
communications to the party's personal
tions device, until detection of one or more events that
30
indicate that the party is no longer occupied with the
task and can perform another task associated Mth
another notification communication.
48. The system of claim 47, wherein the one or more
events comprises at least receipt of second commtmication
35
from the party's personal communications device.
49. The system of claim 47, wherein the one or more
events comprises at least expiration of a predefined time
period.
40
50. rThe system of claim 47, wherein the one or more
events comprises at least arrival or departure of a mobile
thing at or from a location, respectively.
51. The system of claim 47, further comprising means for
refraining from sending notification communications to one
45
or more additional personal communications devices.
52. The system of claim 47, wherein the-initiating means
initiates the notification communication when a mobile
thing is a predetermined proximity with respect to a location.
53. The system of claim 47, wherein the initiating means,
50
the receiving means, the refraining means are implemented
with a single computer system, a plurality of computers that
are communicatively coupled, or a computer system having
a distributed architecture.
55
62. The system of claim 54, wherein the storing means,
the first initiating means, the receiving means, the refraining
means and the second initiating means are implemented with
a single computer system, a plurality of computers that are
communicatively coupled, or a computer system having a
distributed architecture.
63. The system of claim 54, further comprising:
means for monitoring travel data associated with a mobile
thing;
wherein the first initiating means initiates the first notifi·
cation communication based upon the relationship of a
mobile thing to a location; and
wherein the second initiating means initiates the second
notification communication based upon the relationship
of the mobile thing or another mobile thing to the
location or another location.
64. A computer·based notification system, comprising:
means for receiving a notification communication with
the personal communications device associated with
the party from the notification system;
means for communicating a response communication
from the party's personal communications device, indi •
eating that the party has received the notification com·
munication and is now occupied with a task associated
with the notification communication; and
means for causing the notification system to refrain from
sending any further notification communications to the
party's personal communications device, until
tion of one or more events, indicating that the party is
no longer occupied with the task and can perform
another task associated with another notification com·
munication.
54. A computer-based notification system, comprising:
means for storing contact data in memory pertaining to
one or more party personal communications devices;
means for initiating a first notification communication to
a personal communicatiOns device associated with a
party based upon the contact data;
65. The system of claim 64, wherein the response com·
munication is generated by a physical action taken by the
60 party associated with the personal communications device.
means for receiving a response communication from the
party's personal communications device;
means for changing the contact data based upon the
response communication;
means for refraining from sending notification commu· 65
nications to the party's personal communications
device based upon the change in contact data; and
66. The system of claim 64, wherein the response comw
munication is generated by physicaliy detecting the presence
of the party associated with the personal communications
device.
67. A computer·based notification system, comprising:
means for storing contact data in memory pertaining to
one or more party personal communications devices;
Exhibit A
Page 117
US 7,119,716 B2
99
mean for tmttatmg a notification commllllication to a
personal communications device associated with a
party based upon the contact data;
means for receiving a response communication from the
party's personal communlcations device;
means for changing the contact data based upon the
response; and
means for modifying a manner in which future notifica-
tion communications are implemented, based upon the
change in the contact data.
68. The system of claim 67, wherein the modifying means
comprises a means for refraining from sending notification
communications to the party's personal communications
device after receiving the response communication, until
detection of one or more events.
10
15
69. Tbe system of claim 68, wherein the one or more
events comprises at least one or more of the following:
receipt of a second cmrummication from the party's personal
communications device; expiration of a predefined time
period; or arrival or departure of a mobile thing at or from 20
a location, respectively.
70. The system of claim 68, further comprising a means
for refraining from sending notification commWiications to
one or more additional personal communications devices.
71. The system of claim 67, wherein the initiating means
25
initiates the notification communication when a mobile
thing is a predetermined proximity with respect to a location.
72. The system of claim 67, wherein the storing means,
the initiating means, the receiving means, and the modifying
means are implemented with a single computer system, a
30
plurality of computers that are communicatively coupled, or
a computer system having a dlstributed architecture.
73. The system of claim 67, wherein the response
munication is generated by a physical action taken by the
party associated with the personal communicatioru device.
35
100
79. The system of claim 75, wherein the response
munication is generated by a physical action taken by the
party associated with the personal communications device.
80. The system of claim 75, wherein the response
munication is generated by physically detecting the presence
of the party associated with the personal communications
device.
81. A notification system, comprising:
means for initiating a first notification communication to
a personal communications device associated with a
party;
means for receiving a response communication from the
party's personal cmmnunications device;
means for refraining from sendlng notification
nications to the party's personal communications
device after receiving the response communication;
and
mearu for initiating a second notification communication
to the party's personal communications device, one or
more other personal communications devices, or both,
after detection of the scanning of a machine readable
code on an object.
82. The system of claim 81, further·comprising a means
for refraining from sending notification communications to
one or more additional personal communications devices.
83. The system of claim 81, wherein the first initiating
means initiates the first notification communication when a
mobile thing is a predetermined proximity with respect to a
location.
84. The system of claim 81, wherein the first initiating
means, the receiving means, the refraining means, and the
second initiating means are implemented with a single
computer system, a plurality of computers that are
nicatively coupled, or a computer system having a
uted architecture.
74. The system of claim 67, wherein the response
munication is generated by physically detecting the presence
of the party associated with the personal communications
device.
75. A notification system, comprising:
means fOr initiating a first notification communication to
85. The system of claim 81, wherein the response com·
munication is generated by a physical action taken by the
40
party associated with the personal communications device.
a personal communications device associated with a
party;
means for receiving a response communication from the
45
party's personal communications device;
means for refraining from sendlng notification
nicatioru to the patty's personal communications
device after receiving the response communication;
means for initiating a second notification communication
50
to the party's personal communications device, one or
more other personal communications devices, or both,
after detection of a receipt of a second communication
from the party's personal communications device.
76, The system of claim 75, further comprising a means
55
for refraining from sending notification communications to
one or more additional personal communications devices.
77, The system of claim 75, wherein the first initiating
means initiates the first notification communication when a
mobile thing is a predetermined proximity with respect to a 60
location.
78. The system of claim 75, wherein the first initiating
means, the receiving means, the refraining means, and the
secOnd initiating means are implemented with a single
computer system, a plurality of computers that are 65
nicatively coupled, or a computer system having a
uted architecture.
86. The system of claim 82, wherein the response
munication is generated by physically detecting the presence
of the party associated with the personal communications
device.
87. A notification system, comprising:
means for monitoring travel data associated with a mobile
thing;
means for initiating a first notification communication to
a personal communications device associated with a
party based upon the relationship of the mobile thing to
a location;
mearu for receiving a response communication from the
party's personal communications device;
means for refraining from sending notification
nications to the party's personal communications
device after receiving the response communication;
and
means for initiating a second notification communication
to the party's personal communications device, one or
more other personal communications devices, or both,
based upon the upon the relationship of the mobile
thing or another mobile thing to the location or another
location.
88. The system of claim 87, further comprising means for
refraining from sending notification communicatioru to one
or more additional personal communications devices.
Exhibit A
Page 118
US 7,119,716 B2
101
89. The system of claim 87, wherein the first initiating
means initiates the first notification communication when a
mobile thing is a predetermined proximity with respect to
the location.
90. The system of claim 87, wherein the monitoring
means, the first initiating means, the receiving means, the
refraining means, and the second initiating means are imple-
mented with a single computer system, a plurality of com-
puters that are communicatively coupled or a computer
system having a distributed architecture.
102
91. The system of claim 87, wherein the response com-
munication is generated by a physical action taken by the
party associated with the personal communications device.
92. The system of claim 87, wherein the response com-
munication is generated by physically detecting the presence
of the party associated with the personal communications
device.
'f' * * * *
Exhibit A
Page 119
Exhibit B
(12) United States Patent
(54)
Horstemeyer
NOTIFICATION SYSTEMS AND METHODS
ENABLING A RESPONSE TO CAUSE
CONNECTION BETWEEN A NOTIFIED PCD
AND A DELIVERY OR PICKUP
REPRESENTATIVE
(75) Inventor: Scott A. Horstemeyer, Atlanta, GA (US)
(73) Assignee: LegalView Assets, Limited, Tortola
(VG)
( * ) Notice: Subject to any disclaimer, the term of this
patent is extended or adjusted under 35
U.S.C. !54(b) by 867 days.
(21) Appl. No.: 10/858,964
(22) Filed: Jun.2,2004
(65) Prior Publication Data
US 2004/0243430 AI Dec. 2, 2004
Related U.S. Application Data
(63) Continuation of application No. 1 0/706,591,-filed on
Nov.l2, 2003, now Pat. No. 7,119,716.
(60) Provisional application No. 60/498,819, filed on Aug.
29, 2003, provisional application No. 60/486,768,
filed on Jul. 11, 2003, provisional application No.
60/473,949, filed on May 28,2003, provisional appliG
cation No. 60/473,742, filed on May 28, 2003, proviG
sional application No. 60/473,738, filed on May 28,
2003.
(51) Int.Ct.
GOSG 11123 (2006.01)
(52) u.s. Cl ....................... 340/994; 340/992; 3401928;
340/502; 340/504; 340/506; 340/539.11;
7011201; 701/204; 705/8; 705/9; 705/10
(58) Field of Classification Search ................. 340/994,
340/992,928,502,504,506, 539.11; 701/201,
701/204; 705/8, 9, 10
See application file for complete search history.
11111111111111 111111111111111111 IIIII illllillllllllllllllllllllllllllllllll
US007479899B2
(10) Patent No.:
(45) Date of Patent:
US 7,479,899 B2
Jan.20,2009
(56) References Cited
U.S. PATENT DOCUMENTS
3,568,161 A 3/1971 Knickel ..................... 340/994
EP
(Continued)
FOREIGN PATENT DOCUMENTS
0219859 A2 4/1987
(Continued)
OTHER PUBLICATIONS
Moriok, et a!., "Advanced Vehicle Monitoring and communication
Systems for Bus Transit-Benefits and Economic Feasibility'', Final
Report-U.S. Department of Transportation, Sep. 1991, Revised
Mar. 1993, Dot-T-94-03.
(Continued)
Primary Examiner-Tai T Nguyen
(74) Attorney, Agent, or Firm-Thomas,
Horstemeyer & Risley LLP
(57) ABSTRACT
Kay den,
Systems and methods are disclosed for automated notifica-
tion systems. A representative method, among others, can be
summarized by the following steps: monitoring travel data in
connection with a mobile thing that is destined to pickup or
deliver an item at a stop location; causing initiation of a
notification communication to a personal communications
device based upon the travel data; and during the notification
communication, enabling a party associated with the personal
communications device to select whether or not to commu-
nicate with a party having access to particulars of the pickup
or delivery of items or services. A representative system,
among others, comprises a computer or other automated sys-
tem that is programmed or designed to perform the foregoing
steps.
22 Claims, 50 Drawing Sheets
a .. o3la!k>nComiol
41 Urltja.BC\!)
so .. _{BS)Monagor
Exhibit B
Page 120
stopl.ccauoo
[)o.lumlir>allon
S)..,om
"'
Po""""' CommJoica!Qno
Pt>1oo(PCIJJ -"
US 7,479,899 B2
Page 2
U.S. PATENT DOCUMENTS
5,552,795 A 9/1996 Tayloe eta!. ................ 342/357
5,559,871 A 9/1996
Smith ......................... 379/115
3,644,883 A 2/1972 Bannan et al. ................ 340/23 5,570.100 A
10/1996 Grube et al. ................ 364/446
3,845,289 A 10/1974 French .................... 235/151.2 5,577,101 A 11/1996 Bohm ......................... 379158
3,886,515 A 5/1975 Cottin et al.
················ 340/994
5,579,376 A 1111996 Kennedy, III et al.
········· 379160
3,934,125 A l/1976 l\1acano ................... 235/150.2
5,587,715 A 12/1996
Lewis ......................... 342/357
4,220,946 A 911980 Henriot ....................... 340/23 5,594,650 A
1/1997 Shah eta!. . .............. 364/449.1
4,297,672 A 10/1981 Fruchey et al. ................ 340/23 5,594,787 A
111997 Ohshima et al.
············ 379/114
4,325,057 A 4/1982 Bishop ....................... 340/539 5,602,739 A 2/1997 Haagenstad et al .......... 364/436
4,350,969 A 9/1982 Greer .......................... 340/23 5,623,260 A
4/1997 Jones ......................... 3401994
4,525,601 A 6/1985 Bamich et al. .......... 37917 MM
5,648,770 A
7/1997 Ross .......................... 340/994
4,585,904 A 4/1986 Min cone et a!. ......... 17917.1 TP 5,652,707 A
7(1997 Wortham . ................... 364/460
4,713,661 A 12/1987 Boone et al. ................ 340/994 5,657,010 A 8/1997 Jones . ........................ 340/994
4,791,571 A 12/1988 Takahashi et al. ........... 364/436
5,668,543 A 9/1997 Jones .. ....................... 340/994
4,799,162 A 111989 Shinkawa et a!. ........... 364/436 5,673,305 A 911997 Ross . .......................... 379158
4,804,837 A 2/1989 Farley ........................ 250/251 5,680,119 A 10/1997 Magliari et al. ............. 340/904
4,804,937 A 2/1989 Barbiaux et al. ........... 340/52 F 5,694.322 A 12/1997 Westerlage et al. .. ....... 364/464
4,812,843 A 3/1989 Champion, III ct al. ..... 340/905
5,694,459 A 12/1997 Backaus et al.
379/427
4,813,065 A 3/1989 Segala ........................ 379/112 5,699,275 A
12/1997 Beasley et al. .......... 3641514 R
4,857,925 A 8/1989 Brubaker .................... 340/994 5,712,908 A 111998 Brinkman et al. ........... 379/119
4,894,649 A l/1990 Davis .................... 340/825.44 5,715,307 A
2/1998 Zazzera ...................... 379/265
4,956,777 A 911990 Cearley et al.
364/424.02 5,719,771 A
2/1998 Bucket al. .................. 364/443
5,003,584 A 3/1991 Benyacar et al.
············ 3791119
5,724,243 A
3/1998 Westerlage et al. ......... 364/446
5,006,847 A 411991 Rush eta!. .................. 340/994 5,724,584 A 3/1998 Peters eta!.
················ 3951671
5,014,206 A 511991 Scribner et al. ............. 364/449 5,729.597 A 311998 Bhusri
················•······• 3791115
5,021,780 A 6/1991 Fabiano et al. .............. 340/994 5,731,074 A
3/1998 Spaur eta!. ................. 370/313
5,048,079 A 9/1991
Harrington et al ........... 379/112 5,734,981 A 3/1998 Kennedy, III et aJ, ....... 455/445
5,068,656 A 11/1991 Sutherland .................. 340/989 5,736,940 A 4/1998
Burgener .................... 340/994
5,097,429 A 3/1992 Wood eta!. ................. 364/569 5,739,774 A 411998
Olandesi ..................... 340/994
5,103,475 A 4/1992 Shu en
························ 379/115
5,742,672 A 4/1998 Burk .......................... 379/198
5,113,185 A 5/1992 Ichikawa .................... 340/995 5,751,245 A
5/1998 Janky et al. ................. 342/357
5,121,326 A 611992 Moroto et al. .............. 364/449 5,760,742 A
6/1998 Branch et al. ............... 342/457
5,122,959 A 6/1992 Nathanson eta!. .......... 364/436 5,771,282 A
6/1998
Friedes ....................... 379/121
5,131,020 A 7/1992 Liebesney et at. ............. 379/59 5,771,455 A 6/1998 Kennedy, III et al. ....... 455/456
5,144,301 A 911992 Jackson et al. .............. 340/994 5,774,825 A 6/1998 Reynolds
................. 364/449.7
5,146,491 A 9/1992 Silver et al. ................. 379/114 5,781,156 A 7/1998
Krasner ...................... 342/357
5,155,689 A 10/1992 Wortham .................... 364/460 5,784,443 A 711998
Chapman et al ............. 379/119
5,168,451 A 12/1992 Bolger ....................... 3641436 5,793,853 A
8/1998 Sbisa
·············•··········· 379/120
5,179,584 A 111993
Tsumura ..................... 379/114 5,796,365 A 8/1998
Lewis ......................... 342/357
5,218,629 A 6/1993 Dumond, Jr. et al. .......... 379/59 5,799,073 A
8/1998 Fleischer, III et al. ....... 379/113
5,218,632 A 6/1993 Cool
·························· 379/126
5,799,263 A 8/1998 Culbertson .................. 7011117
5,223,844 A 6/1993 Mansell et al. .............. 342/357 5,805,680 A 9/1998 Penzias .. .................... 379/118
5,243,529 A 911993 Kashiwazaki
··············· 3641449
5,808,565 A 9/1998 Matta et al. ................. 340/994
5,271,484 A 12/1993 Bahjat et al. ............... 187129.1
RE35,920 E 1011998 Sorden et al.
··············· 3421457
5,299,132 A 3/1994 Wortham .................... 364/460 5,835,580 A 11/1998 Frazer ........................ 379/115
5,323,456 A 611994 Oprea ........................ 379/375 5,841,847 A 11/1998 Graham et al. ............. 379/114
5,351,194 A 9/1994 Ross et al. .................. 364/449
5,852,659 A
12/1998 Welter, Jr. .•.....•........... 3791116
5,361,296 A 1111994 Reyes et al .................... 379/96 5,864,610 A 111999 Ronen ........................ 379/127
5,381,338 A 111995 Wysocki et al. ............. 364/449 5,875,238 A
211999 Glitho et al. .. .............. 379/116
5,381,467 A 111995 Rosinski et al . ............. 379/121 5,881,138 A 3/1999 Keams et al. ............... 379/114
5,394,332 A 211995 Kuwahara et al. ........... 364/449 5,9l0,979 A 6/1999 Goel eta!. . ................. 3791120
5,398,190 A 3/1995 Wortham .................... 364/460 5,912,954 A 611999 Whited et al . ............... 379/115
5,400,020 A 311995 Jones
························· 3401994
5,915,006 A 6/1999 Jagadish et al. ............. 379/127
5,420,794 A 5/1995 James
························ 364/436
5,920,613 A 7/1999 Alcott et al. ................ 379/114
5,428,546 A 6/1995 Shah et al.
·················· 3641449
5,922,040 A 7/1999 Prabhakara.n . .............. 7011117
5,432,841 A 7/1995 Rimer ......................... 379159
5,937,044 A 8/1999 Kim ........................... 379/121
5,440,489 A 8/1995 Newman .............. , 3641426.05 5,943,320 A
8/1999 Weiket al. .................. 370/259
5,444,444 A 8/1995 Ross .......................... 340/994 5,943,406 A 8/1999 Leta et al. ................... 379/120
5,446,678 A 8/1995 Saltzstein et al. ........... 364/514 5.943,657 A
8/1999 Freestone et al. ........... 705/400
5,448,479 A 911995 Kerrmer et al. .........
36)1424,02
5,945,919 A 8/1999 Trask . ................. 340/825.491
5,461,374 A 10/1995 Lewiner et al. ............. 340/994
5,946,379 A 8/1999 Bhusri ........................ 379/115
5,483,234 A J/1996 Correel efal. .............. 340/994 5,950,174 A 9/1999 Brendzel ..................... 705/34
5,483,454 A 111996 Lewiner et al . ............. 364/443 5,955,974 A 9/1999 Togawa
······················ 340/994
5,493,295 A 211996 Lewiner et al . ............. 340/994 5,956,391 A 9/1999 Melen et al. ................ 3791114
5,493,694 A 2/1996 Vlcek eta!.
················ 455/53.1
5,982,864 A 1111999
Jagadish et al. ............. 379/115
5,506,893 A 4/1996 Buscher et a!. ............. 379/114 5,9&7,108 A 11/1999 Jagadish et al. ............. 3791114
5,513,1l1 A 4/1996 Wortham .................... 364/460 5,987,377 A 11/1999 Westerlage et al. ......... 7011204
5,515,421 A 511996 Sikand et al . ................. 379/67
5,991,377 A 11/1999 Malik ......................... 379/114
5,519,621 A 5/1996 Wortham .................... 364/460 5,991,380 A 11/1999 Bnmo et al. ................ 379/115
5,526,401 A 6/1996 Roach, Jr. et al. ............. 379/59 5,991,381 A 1111999 Bouanaka. et al . ........... 379/115
5,539,810 A 711996 Kennedy, III et al. ......... 379/59 5,995,602 A 1ll1999 Johnson et al. ............. 379/116
5,544,225 A 8/1996 Kennedy, Ill et al. ......... 379/59
6,006,159 A 12/1999 Schmier et al. ............. 7011200
5,546,444 A 811996 Roach, Jr. et al.
379/59 6,094,149 A 7/2000 Wilson ....................... 340/904
Exhibit B
Page 121
US 7,479,899 B2
Page 3
6,097,317 A
6,111,538 A
6,124,810 A
6,134,501 A
6,137,425 A
6,144,301 A
6,178,378 Bl
6,184,802 Bl
6,191,708 Bl
6,222,462 Bl
6,240,362 Bl
6,253,146 Bl
6,253,148 BI
6,278,936 Bl
6,313,760 Bl
6,317,060 Bl
6,360,101 Bl
6,363,254 Bl
6,363,323 Bl
6,374,176 BI
6,400,956 Bl
6,411,891 Bl
6,415,207 Bl
6,486,801 B1
6,492,912 Bl
6,510,385 B2
6,618,668 Bl
6,683,542 Bl
6,700,507 82
8/2000 Lewiner et al. ............. 340/994
812000 Schuchman et al .......... 342/357
912000 Segal et al. ................. 340/994
l0/2000 Oumi ......................... 701/209
10/2000 Oster et al. ................. 340/994
1112000 Frieden ................... 340/572.8
112001 Leibold ...................... 7011202
212001 Lamb ......................... 340/994
2/2001 Davidson .................... 340/994
412001 Hahn ......................... 340/904
5/2001 Gaspard, II ................. 701/209
6/2001 Hanson et al. ... 701/202
6/2001 Decaux et al. .............. 7011204
8/2001 Jones ......................... 7011201
1112001 Jones ........ 340/994
1112001 Jones ......................... 340/994
3/2002 Irvin .......................... 445/456
3/2002 Jones et al .................. 455/456
3/2002 Jones ......................... 701/213
4/2002 Schmier et al ............. 701/200
6/2002 Richton ...................... 455/456
6/2002 Jones ......................... 701/201
7/2002 Jones ............................ 701/1
11/2002 Jones ......................... 340/994
12/2002 Jones
112003 Jones
9/2003 Laird ......................... 7011204
1/2004 Jones ......................... 340/994
3/2004 Jones ......................... 340/994
2002/00I6I71 AI
2002/0069017 Al
2002/0082770 AI
200210099500 Al
2003/0093218 A1
2003/0098802 AI
2003/0146854 AI
2003/0193412 AI
2003/0193413 Al
2003/0193414 Al
2003/0195696 AI
2003/0195697 Al
2003/0195698 Al
2003/0195699 Al
2003/0233188 Al
2003/0233190 Al
2004/0044467 AI •
2006/0206257 Al •
2/2002 Doganata et al. ............ 455/456
6/2002 Schmier et al. ............. 7011213
6/2002 Jones
7/2002 Scluniei et al .............. 7011200
5/2003 Jones ......................... 70l/201
5/2003 Jones ......................... 340/994
8/2003 Jones ......................... 340/988
10/2003 .Tones ......................... .140/994
10/2003 Jones ......................... 340/994
10/2003 Jones ......................... 340/994
10/2003 Jones ......................... 701/201
10/2003 Jones ......................... 701/201
10/2003 Jones '"'""'"""' 701/201
10/2003 Jones ......................... 701/201
12/2003 Jones ......................... 7011200
12/2003 Jones ........................ 70 l/207
3/2004 Laird ......................... 701/207
9/2006 Jones ......................... 701/201
FOREIGN PATENT DOCUMENTS
EP 0805427 Al 11/1997
EP 0889455 AI 1/1999
FR 2 559 930 8/1985
FR 2674355 9/1992
JP 52066175 6/1977
JP 63288400 ll/1988
JP 11034872 A 2/1999
wo wo 90/01236 2/1990
wo wo 93!13503 7/1993
wo WO 93113510 AI 7/1993
wo W09313510 AI 7/1993
wo wo 94/02922 2/1994
wo wo 94/27264 11/1994
wo wo 96/04634 2/1996
wo wo 96116386 5/1996
wo wo 98!07128 2/1998
wo wo 98/08206 2/1998
wo wo 98114926 4/1998
wo wo 98/40837 9/1998
OTHER PUBLICATIONS
Brynielsson, Thore, Step by Step Development Towards Attractive
Public Transport, Chalmers University of Technology, Gotebord,
Sweden, Department of Transportation, 1976.
"Public Transporation Information and Management Ssytems", IEE
Colloquium, Computing and Control Division, May 25, 1993, pp,
9/1-9/4, 12/l-I2/2, 7/1-7/3.
"Vehicle Location and Fleet Management Systems", lEE Col-
loquium, Computing and Control Division, Jun. 8, 1993.
The 3rd International Conference on Vehicle Navigation & Informa-
tion Systems (VNIS) Norway, Sep. 2-4, 1992, pp. 312-315.
Preiss, George; Jenson, Lillian; "The Satref and GPS Information
Projects", 1992 IEEE-3rd International Confeience on Vehci1e
Navigation Information Systems, pp. 648-655.
"Vehicle Navigation & Information Systems Conference
Proceedings"(P-253), Society of Automotive Engineeis, Inc., Oct.
1991, pp. 789-796,
" 1992 Compendium ofTechni cal Papers", Institute ofT ransportation
Engineers-INRAD: A Deminostration of Two-Way Roadway to
Vehicle Conununication for use in Traffic Operations, Annual Meet-
ing, Washington, D.C. pp. 214-218,
"Paving the Way for GPS in Vehicle Tracking", Showcase World,
Dec. 1992.
"Advanced Vehicle Monitoring and Corrununication Systems for Bus
Transit", Federal Transit Administration, Sep. 1991, Revised Mar.
1993.
Koncz, et al., "GIS-Based Transit Information Bolsters Travel
Options", GIS World, Jul. 1995, pp. 62-64.
Helleker, Jan, Real-Time Traveller Information-in everyone's
pocket1.1-a pilot test using hand-portable GSM terminals, IEEE-
lEE Vehicle Navigation & Information systems Conference, Ottawa,
VNIS 1993, pp. 49-52.
Burgener, E.C., et al., ''A Personal Transit Arrival Time Receiver",
IEEE-lEE Vehicle Navigation & Information Systems Conference,
Ottawa, VNIS 1993, pp. 54-55.
Peng, Zhong-Ren, ''A Methodology fur Design for a GIS-Based
Automatic Transit Traveler Information System", Computer, Envi-
ronment and Urban Systems, vol. 21, No. 5, pp. 359-372, 1997.
Lessard, Robert, "The Use of Computer for Urban Transit Opera-
tions", IEEE-lEE Vehicle Navigation & Information systems Con-
ference, Ottawa, Vl\TIS 1993, pp. 586-590.
Sommerville, Fraser, eta!., "Reliable Information in Everyone's
Pocket-a Pilot Test", IEEE, vol. 1927, Mar. 1994, pp. 425-428.
"Promise-Personal Mobile Traveller and Traffic Infonnation
Service-Specification of Promise Services, Ver. 7", Telematics
Application ProgrammeA2, Transport, Jul. 1, 1996,
"Promise-Personal Mobile Traveller and Traffic Information
Service--Generic Promise System Architecture, Ver. 2", Telematics
Application Programme A2, Transport, Sep. 10, 1996.
Promise-Personal Mobile Traveller and Traffic Information
Service--Sll1n1ll.3.l')' of Promise Public Relation Activities, Vei. 1,
Telema!ics Application PrograrnmeA2, Transport, Feb. 12, 1999.
"Prornise"-A Personal Mobile Traveller and Traffic Information
Service--Abstract, The Institution of Electrical Engineers, 1997.
Sommerville, Fraser, et aL, "The Promise of Increased Patronage",
The Institution ofElectrical Engineers, 1993, pp. 3/1-3/4.
"Automatic Transit Location System", Washington State Department
of Transportation, Final Report, Feb. 1996.
"Advanced Traveler Aid Systems for Public Transportation", Federal
Transit Administration, Sep. 1994.
"Advanced Vehicle Monitoring and Communication Systems fur Bus
Transit: Benefits and Economic Feasibility", U.S. Department of
Transportation, Urban Mass Transportation Administration, Sep.
1991.
Leong, Robert, et al., "An Unconventional Approach to Automatic
Vehicle Location and Control for Urban Transit", IEEE I989, pp.
219-223.
"\994 Vehicle Navigation & Information Systems Conference Proo
ceedlngs", Yokohama, Japan, Aug. 31-Sep. 2, 1994, pp. 807-810.
Exhibit B
Page 122
US 7,479,899 B2
Page4
"Vehicle Navigation & Information Systems Conference
Proceedings-P-253, Part 2", Society of Automotive Engineers, Inc.,
Oct. 1991.
Vehicle Navigation & Information Systems--Conference Record of
Papers presented at the 3'u Vehicle Navigation & Information Sys-
tems Conference 1992., Reso HoteL Osio Plaza., pp. 49-52.
Nelson, J. Richard, "Experiences Gained in Implementing an Eco-
nomical Universal Motorist System", IEEE-lEE Vehicle Naviga-
tion & Information Systems Conference, Ottawa, VNIS 1993, pp.
67-71.
"The Cassiope/EurobusApproach", IEEE-lEE Vehicle Navigation
& Information Systems Conference, Ottawa, VNIS 1993, pp. 79-81.
Kihl, Mary, "Advanced Vehicle Location System for Paratransit in
Iowa", IEEE-lEE Vehicle Navigation & Infonnation Systems Con-
ference, Ottawa, VNIS 1993, pp. 381-384.
Gault, Helen, eta!., "Automatic Vehicle Location and Control at OC
Transpo", Vehicle Navigation & Infonnation Systems
Conference, Ottawa, VNlS 1993, pp. 596-600.
Vehicle navigation & Information System-Conference Record of
Papers presented at the First Vehicle Navigation and Infonnation
Systems Conference (VNIS '89), Sep. 11-13, 1999, pp. 602-605.
Heti, Gabriel, "Travelguide: Ontario's Route Guidance System Dem-
onstration", IEEE-lEE Vehicle Navigation & Information Systems
Conference, Ottawa, VNIS 1993, pp. A13-A18.
Jeffery, D.J., et al., "Mvanced Traveller Infonnation Systems in the
UK: Experience from the Pleiades and Romanse Projects",
IEEE-lEE Vehicle Navigation & Infonnation Systems Conference,
Ottawa, VNIS 1993, pp. 309-313.
Sweeney, Lawrence, E., et al., "Travinfo: A Progress Report", 1994
Vehicle Navigation & Infonnation Systems Conference Proceed-
ings'', Yokahama, Japan, Aug. 31-Sep. 2, 1994, pp. 315-320.
Shimamura, Yta, et al., "Combined Position Detection System for
PedestrianrTrain Mode", 1994 Vehicle Navigation & Infonnation
Systems Conference Proceedings", Yokaharna, Japan, Aug. 31-Sep.
2, 1994, pp. 603-606.
Zavoli, Walt, "Customer Location Services", 1994 Vehicle Naviga-
tion & Information Systems Conference Proceedings", Yokaharna,
Japan, Aug. 31-Sep. 2, 1994, pp. 613-617.
Tanaka, Yoshimi, et al., "Automatic Traffic Information Provision
System Utilizing Facsimile and Telephone (Now Operating in
Osaka), 1994 Vehicle Navigation & lnfonnation Systems Conference
Proceedings", Yokahama, Japan, Aug. 31-Sep. 2, 1994, pp. 627-632.
McDonald, Mike, et a!., "Romanse (Road Management System for
Europe) Project", 1994 Vehicle Navigation & Information Systems
Conference Proceedings", Yokahama, Japan, Aug. 31-Sep. 2, 1994,
pp. A-11-A-14.
Scott III, Robert H., "Computer-Aided Dispatch,", 1998, pp. 46-50.
Moore, Rodney J., "Hold the Phone!", American Demographics,
Ithaca, Jan./Feb. 1996, p. 68.
Delong, Jr., Ed.garS., "Making 911 even better'', Telephony, Dec. 14,
1987, pp. 60·63.
Bruzek, Fmnk J., "Class Calling Service-A Consumer Service Per·
spective", Globecom '85 IEEE Global Telecommunications Confer-
ence, Dec. 2-5, 1985, vol. 1 of3, pp. 11.4.1-11.4.4.
Powell, R, et a!., "Real Time Passenger Infonnation System for the
Romanse Project", Colloouin Digest-lEE, Boston, Sep. 1993, pp.
9/1-9/3.
Huber, Paul, "Public Transport Infonnation Systems in Munich",
Intelligent Transport System World Congress '95-Second Wold
Congress on Intelligent Transport Systems, Yokohama, Japan., Nov.
9-11, 1995, pp. 2362-2366.
Ronez, Nicholas, et al, "GIS-Based Transit Information Bolsters
Travel Options", GIS World, vaL 6, part 7, Jun. 1995, pp. 62-64.
Catling, Ian, et al., "Tabasco-lmproving Transport Systems in
Europe", Pacific Rim TransTech Conference, Jul. 30·Aug. 2, 1995,
995 Vehicle Navigation & Information Systems Conference Proceed-
ings, Washington State Convention and Trade Center, Seattle, Wash-
ington, USA, PP· 503-507.
Dailey, D.J., "Demonstration of an Advance Public Transportation
System in the Context of an IVHS Regional Architecture", Proceed-
ings of the First World Congress on Applications of Transport
and Intelligent Vehicle-Highway Systems, Nov. 30-Dec.
3, 1994, Paris, France, pp. 3024-3031.
Hubner, Paul, "Advance Public Transportation Information in
Munich", International Conference on Public Transport Electronic
Systems, Conference Publication No. 42, Jun. 1996.
Thompson, S.M., etal., "Exploiting Telecommunications to Delivery
Real Time Transport Information", Road Transport Information and
Control, Apr. 21·23, 1998, pp. 59-63, Conference Publication No.
454 IEE 1998.
Kaminitzer, David, et at., Driver Information Systems: Influencing
your Route, lEE Seminar, Mar. 3, 1999, pp. 5/1-5/5.
''Board Cites ATC in Spokane Near Miss", Article in Aviation Week
& Space Technology, Mar. 28, 1977, URL: http://www.aviatiomlow.
com.
Shifrin, Carole A., "Gate Assignment Expert System Reduces Delays
at United's Hubs", Article in Aviation Week & Space Technology,
Jan. 25, 1988.
"United Airlines applies TI'advance technologies to improve gate
management at major airports", Article in Business Wire, Inc., Nov,
19, 1987.
Musich, Paula, "Airline Designs Software to move planes, people;
Unite Airline's use of Cavia Corp.'s Open Systems Manager, Con·
nectivitySection",Articlein PC Week, Jun. 7, 1988, vol. 5, No. 23, p.
Cll.
Stoll, Marilyn, "Systems help Airlines Manage Gate Schedules; Con·
nectivitySupplement", PC Week, Jul. 25, 1988, vol. 5, No. 30, p. C4.
Reddy, Shyamala., "Travelling LAN: United Airlines Networks Its
Terminals",Article in The Local Area Network Magazine, Jan. 1990,
vol. 5, No. I, p. 108.
Fisher, Sharon, "NetworkedAirport Systems help Travelers find their
way; United Airlines subsidiary Cavia Corp. devices integrated net-
work.", Article in Software Magazine, Mar. 15, 1990, voJ. 10, No.4,
p. 31.
Henderson, Danna K., ''Automation Takes aim at airports: the power
of the networked PC is being unleashed on passenger handling and
ramp activities worldwide.", Article in Air Transport Wold, Aug.
1990., vol. 27, No.8, p. 52.
"United Airlines introduces United Cargo Plug 1, a new cargo com-
puter system to serve freight foJWarders", Business Wire, Oct. 22,
1990.
Miller, Bany, "Special Report: Airline Equipment, Service Center",
Aviation Week & Space Technology, Aug. 25, 1975, p. 51.
Lyon, Mark W., "Cargo Net Debate Splits Industry", Journal of
Commerce, Specials, p. 4, Jul. 27, 1992.
Davies, I.L., et al., "Electronics and the Aeroplane", Proceedings of
the Institution of Electrical Engineers, Paper No. 7604, delivered
before the lEE Electronics Division, 29m Oct. 1975.
"Global Niche", Flight International, Sep. 26, 1990.
"Real-Time Briefing!>'', Aviation Week and Space Technology, Oct.
13, 1986.
Flanagan, Mike, eta!., ''Amelia Earhart-Mystery Still Clouds Soar·
ingAchievements", Chicago Tribune, Jul. 5, 1987, Final Edition, p. 5,
Tempo Woman.
"Official Airline Guides", Airports®, Nov. 20, 1990, Around Air-
ports, val. 7, No.4?, p. 485.
"Automation System Galus Acceptance", Aviation Week & Space
Technology; Nov. 23, 1992, vol. 137, No. 21, p. 97.
Klass, Philip, French Testing "Ground-Derived' MLS", Aviation &
Space Technology, Avionics, p. 56, Dec. 15, 1975.
"Forecast Realized for ATC System", Aviation & Space Technology,
Mar. 17, 1975, Avionics, p. 168.
Henderson, Danna, eta!., "lonworks: America We!>1Aulomates New
Phoenix Terminal Fully Integrated System to Handle Customer-Ser-
vice Demands (America West Airlines Inc) (Includes Related Article
Automation of passenger Service at Airports)", Airport Transport
World, May 1, 1991, vol. 62.
3 Pages from a web site search under http://mlt.edu/afs/net.mitfedul
proje;;;tfattic/usa-today/tech/37, Jun. 12, 2003.
"What's New in passenger Handling Equipment", Air Transport
World, val. 24, p. 62, Sep. 1987.
"Senator Urges Acceleration ofNavstar", Aviation & Space Technol-
ogy, Avionics, p. 153, Oct. 3, 1983.
"AFSC Broadens Joint Program Efforts", Aviation & Space Technol-
ogy, System Acquistions, p. 83, Jul. 19, 1976.
Exhibit B
Page 123
US 7,479,899 B2
Page 5
Herskovitz, Don, ''GPS Insurance Antijanuning the System; Brief
Article", Journal ofElectronic Defense, Dec.!, 2000, No. 12, val. 23,
p.4l.
Hambly, Richard M., et a!., "Aircraft Traffic Management on the
Airport Surface Using VHF Data Link for CNS", IEEE AES Systems
Magazine, Mar. 1995, pp. 9-13,
Berzins, G., et al., "INMARSAT: Worldwide Mobile Satellite Ser-
vices on Seas, in Air and on Land", SpaceToxhnology, val. 10, No.4,
pp. 231-237, 1990.
Jenney, L.L. et al., "Man as Manager of Automated Resources in an
Advanced Air Traffic System", l Aircraft. vol. 12. No. 12, Dec. 1975.
"Routing & Scheduling System improvements from RTSI; Routing
Technology Software, Inc.; Product A.nnouncement", Modem Brew-
ery Age, vol. 43, No.3, p. llS, Jan. 20, 1992.
Yanacek, Frank, "Hitching to the stars; satellites for shipment !rack-
ing", Research Infonnation Transportation Journals, Combined, No.
6, vol. 29, p. 16.
Stoll, Marilyn, "For on-the-road firms, hand-held terminals are piv-
otaL Connectivity", Research Infonnation Transportation Journals,
Combined, No. 34, vol. 5, p. Cll.
"IBM and Hunt to Market. NewT ruck Tracker; International Business
Machines", J.B. Hunt Transport Services; Brief Article, No. 210, vol.
101, p. 4.
Klass, Philip J., ''Two Carriers Plan Automatic Data Link", Aviation
Week and Space Technology, Air Transport Section, May 23, 2977, p.
36.
"Data Link Evolved Over Three Decades", Aviation Week and Space
Technology, Air Transport Section, May 23, 1977, p. 36.
Klass, Philip J.; ''American to Insta11 Printers in Cockpits", Aviation
Week and Space Technology, Avionics, Jul. 21, 1980, p. 56.
Lefer, Henry, "Computers on a boon to E&M, but at a price", Air
Transport World, vol. 23, p. 53, Feb. 1986.
Donaghue, J.A., "Choice of Data Link Systems Expands as New
Generation Hits the Market", AirTransportWorld, vol. 20, p. 58, Apr.
1983.
Klass, Philip J., "Digital Network Could hnprove Aircraft Links to
Operations, ATC", Aviation Week and Space Technology, Interna-
tional Air Transport Section, vol. 131, No. 21, p. 121, Nov. 1989.
Board Cites ATC in Spokane Near Miss, Article in Aviation Week &
Space lechnology, Safety Section, Mar. 28, 1977. p . .'i9.
"Vicorp Interactive Systems", Aviation Daily, Aviation Suppliers
Section, vol. 309, No. 17, p.147.
Neumann, Dr. Horst, "ATC Concepts with Extensive Utilization of
Automatic Data Processing", pp. 4-1 to 4-9; No Publication
Informaton or Date Information Provided.
Maxwell, Robert L., "Automation Possibilities in Air Traffic Con-
trol", pp. 561-563, No Publication Information or Date Infonnation
Available.
"History of GPS", 3 pages, No Publication Information or Date
Information Available.
"Road Transport Research-Intelligent Vehicle High
Systems-Review of Field Trials", prepared by An OECD Scientific
Expert Group, pp. 1-101, Organisation for Economic Co-Operation
and Development-No Date InfonnationAvailable.
Ratcliff, Robert, et a1., Transportation Resources Information Pro-
cessing System(TRJPS), pp. 109-113, No Publication Infonnation or
Date Information Available.
Ba1ke, Kevin, et al., Collection and Dissemination of Real-Time
Travel Time and Incident Infonnation with In-Vehicle Communica-
tion Technologies, pp. 77-82, No Publication Information or Date
Information Available.
* cited by examiner
Exhibit B
Page 124
-om
m x
~ "
m cr
...... ;:::;:
~ " '
Notification System
Positioning System
(e.g., GPS Satellites,
radar, etc.)
r
17\
21
Mobile Thing (MT)
(e.g., a Motor Vehicle, PCD, etc.)
Mobile Thing Control
Unit (MTCU) S
~ ensor
15• 29\ 2 .1Jl.
Mobile
Thing ~ TX/RX
Manaoer
43
31a
7
44
4l._
'i3
45)
10_)
Base Station Control
41'
Unit(BSCU)
Base Station (BS) Manager
Combined MTTL
Response System
Stop Location And
Feedback Analyzer
Determination DTL Notification
100a
System System
190 290
Mobile Thing
Secure Notification
Messaging System
Determination
210
System
250
31b_.
6
t__J ~ 7 0
52 TX/RX II TX/RX 72
t
_t
(48
fes r 74
55
(61 v(_
Nelwork(s) Network(s)
{e.g., cellular) (e.g., PSTN)
t
t r
73
Response
\ TX/RX 1- System
FIG. 1 t
Feedback
i----'75
~ Location \
Mechanism
e o ~
Sensor
100b
Personal Communications
Device (PCD)
I
I
~
rJJ
.
"'d
~
(!>
a
;<
?
N
9
N
0
0
\0
[JJ.
=-
~
>-'
0
-.
Ul
0
d
fJ)
--.l
....
--.l
\C)
Oo
\C)
\C)
l:d
to->
-um
m x


MTCU
30a
j1a\
-'-
Memory

c39a
Mobile Mobile
['_32a
(18 L38a Thing Thing
Manager Schedule
Processing
Mobile
Sensor Thing
Element
Clock
.G
"'"
"'
r-

['>-
-"1
,.
A "'

"'
7
.,
7
(33a
""
7
.J\
Local Interface (e.g., one or more buses, interfaces, and/or connections)
, I
"'
...,..
""
,..
""
r-
L
r
"'
r v
.(34a .(35a

.(37a ._{_
.. 7 .,
.7 ....
.,
7 -< z
36a
Input
Display TXIRX Disk Printer
Device
FIG. 2

rJ:J
.
"'d

a
;:;<
?
N
.o
N
0
0
'-0
00
::::r
"'
a
N
0
...
<JI
0
d
rn
-.l
."'"
-.l

00


l:d
N
-um
ru x

....... ;:i!'
':lm

40
(32b
Processing
Element
L
,..
A '
7

30b

Memory
Base /39b
Station
Combined MTIL
(52, 72
Manager Base Secure Notification
And
(38b

Station Messaging System
DTL Notification
Schedule
ill!
System
290
Base Station
Response
TX/RX
Clock
System Stop Location
Mobile Thing
Determination
Determination
I
-<
,..
.<'
,..
Analyzer System
System
GUI
100a 190
250
46
7 (33b
.., ,..
"'
s.
'
""'
7
Locallntertace
L
,..
""'
,..
<
,.. ..,
?--
L
r-

.(34b
7 "
.(35b
7. "
.(37b
7 '
:--(36b .(45
"""-.7
Input
Tone
Device
Display Disk Printer Reader/
Decoder
·-
- -
-
'-·-
FIG. 3
I

v

U'1

"C

(!>
a
'-<
..
?
"'
9
....
0
0
""
V1
,.
"'

w
0
.....
Ul
0
d
rJ1
-l
-:..
-l
\0
Oo
\0
\0
Cd
N
"m
ID X
! ~
~ " '
Start
End
FIG. 4A
Yes
Route
finished?
No
Sample
period
expired?
Yes
76
77
No
78
Determine current
location values from
sensor and determine
current time values from
mobile thing clock
79
Store current location
values and current time
values in next entry of the
mobile thing schedule
29a
)
~
r;Fl
'"0
~
......
!'!>
a
~
N
9
N
0
0
'C
[/]
"'"
"'
a
....
0
....,
Ul
0
d
r:n
-l
-:.:...
-l
\0
Qc,
\0
\0
l:d
N
"m
£ i ~
CD 5'
~ ~
82
Transmit start signal and
store current value of
mobile thing clock
FIG. 48
95
Determine current location
values from sensor I 85
87
Find corresponding
entry in mobile thing
schedule
91
Calculate deviation
indicator
93
Is
T
't ~ e s · · 'd' t >
ransm1 dev1at1on 1n 1ca or
alarm signal threshold?
No
96
·obile thing early or late
based upon a predefined
threhold?
es
No
29b
~
99
Transmit status
message
~
VJ
.
I"'Q
~
(t
a
'-<
~
....
9
....
0
0
\0
rn
=-
a
Ul
0
,...,
Ul
0
d
r:n
-'l
':..,.
-'l
\a
Oo
\a
\a
t:i:l
t.j
-urn
ID X
~ ~
....... ;:+
~ " '
T< )
u er
BSCU
40
[_72
!
TX/RX
r--
~ r r '
7 2
j TX/RX L
I I
_e__72
l
TX/RX _r-
52\
,j.
I
TX/RX _j
(41
Base Station
Manager
Database
94
Mobile User Comm Stop
Thing Data Data Method Location
68a 68b Data Data
68c 68d
I Authentication Data PCDTravel Traffic Flow
6Bh Data Pred. Data
6Bi
illll
t
(67
Data Manager
I
Algorithms
I
illl.
~ (52
l
TX/RX
_I
I
TX/RX J
sz.J
04
To Mobile Thing
FIG. 5A
MTTravel Ad PCD
Data Data Data
68e 681 68g
Package Failure
Tasks Data
Data States Data
68m
68k 681
~
00
.
""0
~
.....
~
a
'-<
.,
?
N
~
N
0
0
"'
00
=-
"

Q\
0
-.
Ul
0
d
r:Fl
-l
-:.:..
-l
\0
Qo
\0
\0
o:l
N
-urn
ID X
~ ~
-->. ;::::;.:
~ O J
ToPCD
TXIRX
Database
94
User
Data
68b
Data Manager
(82
lr7o
Message
Manager
(86
Mapping
System
FIG. 58
(67
To Travel Data
(69
Monitoring
Mechanism
~ 6
To Mobile T hing
TX/RX
~
\J)

"'d
~
.....
(t)
a
~
?
""
9
N
Q
Q
'0
[fJ
=-
!t
_,
0
,...,
U1
Q
d
en
-.l
-:.:..
-.l
\0
Oo
\0
\0
Cd
N
;.\'\]!
~ a ;
....>. :=.:
[dro
Monitoring J I A I I I
mechans1m j
B8a J
69 ---------.,...
FIG. 5C
881
Transmit retrieved
travel data to
message manager
or mapping system
user
preferences
in database
88k
Retrieve desired
travel data
Yes
Data
received? >No
Yes
88b
Yes
No
No 88i
Message is a
request for travel
data
88j
Interpret request to
determine which travel
data is desired
88c
Compare travel data
from mobile thing to
preference data in
travel data table
88d
851
No
Store travel data
in database
Yes
88e
Send notiftcation
command to message
manager and/or
mapping system
~
[J)

~
!:o:l
'*
(!)
~
'*
~
N
_o
N
0
0

"'
::r
"'

00
0
.....
tJl
0
(j
CJj
-..l
-:.:...
-..l
\C)
Oo
\C)
\&>
1::0
N
"rn
ID X
<O,-

tlco
Message
Manager
FIG. 50
·90a
I

received? No r
y
Yes
Ye•
90!)
Prompt user for
contact information
and notification
preferences
90h
Store contact
information in user
database
901
Transmit notifrcation
preferences to
monitoring
mechanism
No ->I
90c
Message is from
monitoring
mechanism or
mapping system
(90e
f Send data to
user
90d
Retrieve contact
information from
user database
On
Message is a
request for travel
data.
Yes
90k I
Prompt user for
new lnfonnatlon
901
Update contact
information
90nl
Transmit new
notificaiton
preferences to
monitoring
mechanism
Send a reqUest to
monitoring
mechanism
90p
Receive travel
data from
monitoring
mechanism
\
82

rJ1
.
"d


= .....

N
_o
N
0
0
"'
rn
=-
!!
"' 0
.....
!Jo
0
d
[J)
_---l
...
--.l
_'D
00
'>a
'>a
l:d
1->
-um
~ ~
ro 0'
....... ;:::;:
'gro
Notification System
10
Response System
Feedback Analyzer
100a
Instruction Lookup
84

Notification-Receiving Party
Contact Records
86
Response System
100

FIG. 6
Personal Communications
Device
75
Response System
Feedback Mechanism
100b
~
rJ1
.
"tj
~
tt
a
""'
?
N
p
N
0
0
""
r.n
:r
a
.....
0
0
...,
t/0.
0
e
r:n
--'1
~
--'1
'-0
Qo
'-0
'-0
~

"'"" (i) 5'
_,.;:::;:

(
Start
)

Causing initiation of a
notification communication to a
personal communications
device associated with a party
+
During the notification
communication, receiving a
response from the party's
personal communications
device, indicating that the party
associated with the personal
communications device has
received notice.
FIG. 7A
100a
)
01
02
(
Start
Monitoring travel data in
connection a mobile thing
that is destined to pickup or
1--
deliver an item at a stop
location

Causing initiation of a notification
communication to a personal
communications device based
upon the travel data
t
During the notification
communication, enabling a party
associated with the personal
communications device to select
whether or not to communicate
with a party having access to
particulars of the pickup or deliver
L._______._________ --------·-····- ---
FIG. 78
100a
)
(
Start
Monitoring travel data in
connection with a mobile thing
that is destined to pickup or
deliver an item at a stop
location
••
6
Causing initiation of a notification
communication to a personal
communications device based
upon the travel data
t
07
During the notification
communication, enabling a party
associated with the personal
communications device to
change one or more tasks
associated with the pickup or
delivery.
c___ __
FIG. 7C
100a
)
9
1-"
0

lJl


;.:l
(t
a

N
9
N
0
0
""
00
.,.
i
,....
.....
0
-.
U\
0
cj
rJJ
-l

-l
\C
Oo
\C
\C
o:l
N
(
"' Start
Monitoring travel data in
!J
connection w i t ~ mobile things.
Causing initiation of a notification
communication to a personal
communications device based
upon the travel data.
-um
~ ~
(1)5'
~ ~
During the notification
communication, providing a
plurality of arrival or departure
times in relation to a location and
enabling selection of one of the
times.
Causing a mobile thing to arrive
at or depart from the location at
substantially the selected time.
FIG. 70
100a
)
5
6
117
~
U'J.

"'0
~
,...,..
~
l:i
,...,..
'-<
..
?
...
9
...
0
0
\0
w
""
"'

....
N
0
....,
<Jo
0
c
00.
-l
~
-l
'-0
Oo
'-0
'-0
i:d
,...
100a
~
).
r:J'1
.
~
;:..
-
(!>
=
111
-
Causing initiation of a
l
notification communication to a
personal communications r
""'
..
device associated with a party
?
....,
.o
....,
0
0
112
\0
Receiving a response
I
-um
I
communication from the m x
~ = - -
r
'fl
ro 5'
party's personal
:T ...... ;::;:
~ O J
"'
communications device
$.
......
"' 0
....,
til
0
Modifying the manner in which
1 113
future notification
communications are to be
sent, based upon the response I
d
r:n
-'I
."""
-'I
1,0
Qo
FIG. 8
1,0
1,0
l:d
0:-.)
-um
m x
~ , . ,
<D 5'
w ~
m
(
Start
)
3

21
Modifying contact data based
upon the response
+
Causing one or more other
22
notification communications to
the party and/or one or more
other parties, based upon the
modified contact data
FIG. 9A
(
Start
' \.
)
~
Modifying contact data based
upon the response
~
Causing the notification system
to refrain from sending
notification communications to
the party's personal
communications device after
receiving the response
+
Causing one or more other
notification communications to
the party and/or one or more
other parties, using one or
more different communication
methods, based upon the
modified contact data
FIG. 9B
113
)
31
32
33
Modifying contact data based
upon the response
Causing the notification system
to refrain from sending
notification communications to
the party's personal
communications device after
receiving the response, until
the detection of one or more
events
Monitoring for occurrence of
the one or more events
Causing one or more other
notification communications to
the party and/or one or more
other parties, using one or
more communication methods
FIG. 9C
113
)
141
142
143
144
~
f/1
~
~
~
a
'-<
"' ?
N
p
N
0
0
"'
rLl
::>'
~
,....
....
0
-
tA
0
Cj
en
-l
~ " " "
-l
l.a
(x,
l.a
l.a
t:C
N
-um
ID X
"'"" (I) 6'
....>. ;::¥
~ " '
(
Start
" \,
~
Receiving a notification
communication with a personal
communications device
associated with the party from
the notification system

Receiving an input response
from the party associated with
the personal communications
device.

Communicating the party's response from the
personal communications device to the
notification system. The response may merely
confirm receipt of the notification, may indicate a f..
desire to carry on a discussion with a
representative, and/or may indicate the manner in
which future notification communications should
be communicated to the party.
FIG. 10
53
~
\J)

'"C
~
......
~
a
~
?
N
p
N
0
0
'0
r.n
:r
a
,....
U\
0
..,
U\
0
d
r:n
;-l
ol'o-
-l
'-0
Qo
'-0
'-0
ed
t-.>

r;F1
Enabling a party to indicate a
"'d
M "t. I


willingness to receive one or
.....
ant onng trave (!)
data associated more advertisements during
::;
.....
with a mobile thing a notification regarding a
mobile
'-<
.,
?
Contacting a party 62
Providing a notification

N
.0
based upon the
communication involving
N
0
travel data
travel status of the mobile
0
\0
thing
-um
ID X
w

(I) a= ::r
...... ;=,:
Providing an
Providing an
173
"'
1 3
"'
...
advertisement to the
advertisement as part
.....
Q\
party substantially
of or accompanying 0
....,
during the contact
the notification
VI
0
communication
t
;
Ch•<g;og ''"o'
Charging a fee or
174
monitarily benefiting monitarily benefiting
d
from providing the from providing the
rn
-l
advertisement advertisement
.""
-l

Co
FIG. 11 FIG. 12


eo
!;-.)
~ \ : r
~ ~
~ ~
\.
Start
'
Enabling a party to indicate a
181
willingness to receive one or
v more advertisements during
a notification regarding a
mobile thing
182
Providing a notification
L/
communication involving
travel status of the mobile
thing
184
Providing an
advertisement as part
of or accompanying
the notification
communication
t 185
Charging a fee or
_/
monitarily benefiting
from providing the
advertisement
'------------ -- - ··-
FIG. 13
Charging a fee or
monetarily benefiting from
providing the notification
,...
communication
Providing a discount based
86
upon the party's willingness
to receive the one or more
advertisements
-- ~ - - ~
~
\J)
.
1-C
~
-
('t)
a
'-<
.,
?
"'
?
"'
0
0
'C
"'
...
!t
......
....,
0
....,
vo
0
d
r:n
-l
-:.:...
-l
\J:)
Qo
\J:)
\J:)
o:l
t->
"Um
ID X
~ ~
mcr
~ ~
"'
\
Start
i
Monitoring travel data J
associated With a mobfie thing
+
Causing communication of a
notification involving a delivery
or pickup task associated with
the mobile thing to a personal
communications device
associated with a party

Receiving location data from
the persona\ communications
device
t
Determining one or more
stop locations, based upon
the device location data and
the travel data associated
with the mobile thing
• Causing communication of
an identification of the stop
location(s) to the personal
communications device so
that the delivery or pickup
task can be accomplished at
one of the stop locations.
FIG. 14A
1
Joa
92
93
94
95
(
Start
' Monitoring travel data
!
associated with a mobile thing
-'
+
Causing communication of a
notification involving a delivery
or pickup task associated with
the mobile thing to a personal
communications dovice
associated with a party
t
Receiving location data from
the personal communications
device

Determining one or more mobile things
with one or more corresponding stop
locations. based upon the device location
data and the travel data associated with
the mobile thing
'
Causing communication of an
identification of the mobije things
and stop locations to the personal
- communications device so that the
delivery or pickup task can be
accomplished.
-
FIG. 148
JOb
04
~
\F1
.
"'C
~
.....
(t>
a
'-<
..
?
"'
.o
"'
0
0
'<:>
w.
:r
"'
a
,_.
00
0
....,
Ul
0
d
r:n
-.1
."""
-.1
\C
Co
\C
\C
o::l
N
"m
ID X
<ga;
....>.;:::;:
i;OJ
(
Start
.. .
Receiving timing criteria
j_
Monitoring travel data
associated with a mobile thing
+
Determining one or more
stop locations, based upon
the timing criteria and the
travel data associated with
the mobile thing

Causing communication of
an identification of the stop
location(s) to the personal
communications device so
that the delivery or pickup
task can be accomplished
FIG. 15A
190c
211 )
212
13
4
(
Start
'f
Receiving timing criteria
'
Monitoring travel data associated with
a plurality of mobile things, e.g., first
and second mobile things
+
Determining one or more first and
second stop locations, based upon
the timing criteria and the travel data f.-
associated with the first and second
mobile things, respectively
+
Causing communication of an
identification of the first and second
mobile things and the first and
second stop locations to the personal
communications device so that the
delivery or pickup task can be
accomplished at least one of the stop
locations
FIG. 158
190d
~
1)
3
24
~
1Jl
.
"d
a
(t>
a
"--<
..
?
N
.?
N
g
""
00
g
~
,....
"" 0
....,
V>
0
d
r:n
...:t
-:....
...:t
~ > a
00
>a
>a
i;d
N
-um
m x
~ ~
...... ;:::;:
too
Memory
30b
Authentication
Information
234
'
Start
_)
Monitoring travel data
associated with a mobile thing
Causing communicating of a
notification involving a delivery
or pickup task associated with
the mobile thing to a personal
communications device
associated with a party
Causing authentication
information to be provided to
the personal communications
device that indicates to the
party that the notification is
from an authorized source
FIG. 16
231
210
1-
)
232
33
1---
~
\Zl
loti
~
(t
= ......
""'
"' ?
N
.o
N
0
0
~
"' ::r
"' a
N
0
0
...,
Ul
0
e
rJ)
-Cl
."""
-Cl
\0
Qo
\0
\0
o::J
.,..
"Um
ID X


<.n
-
INTERNET SERVICE PROVIDER
-l@l_xj
File Edit Go To Views Events Window Help

YOU HAVE RECEIVED NEW MAIL
FROM I
SUBJECT
I RECEIVED I
XYZ-Charity@secur Arriving in 2 Minules {,:49 Security By Secure Arrival 1:47:58 PM EST
Subj: YXZ CHARITY ARRIVING IN 2 MINUTES
VERIFICAUON WAS
Date: 1/28/1995 1:47:56 PM Eastern Standard Time
From: PatSmith@SecureArrival.com
To: NancyS@Domain.com
The person to the right will be approaching your
home at 1:49 pm,
Please reply to this message for additional
235
verification, to cancel the arrival, or to reschedule.
Save ) Delete I Reply
I
I ISP BROWSER
Mil Start (coNNEcTEo;
__ 1_. __
FIG 16A
....
""

r:Fl

""0
;:.:l
;"
a
;<
?
N
.o
N
0
0
\C>
""
::r

N
...
0
...
Ul
0
(j
1JJ
-'1
.""'
-'1
\0
Oo
\0
\0
eli
I:->
-om
m x
" ' ~
roo:
& ~
(
Start
"
Permitting a party to identify a pickup
location, a dropoff location, and one or f.--'
more notification preferences
Identifying a mobile thing based upon
the identity of the pickup location, the 1---
dropoff location, or both
Causing communication of an identity
of the mobile thing when appropriate,
pursuant to the one or more notification
preferences
FIG. 17A
250a
)
3
(St;rt)
"
Causing establishment of a first
communication session between the
system and a PCD
During the first communication session,
permitting a party to identify (a) a
communications method for providing a
notification, (b) a pickup location and
(c) a dropoff location

Identifying a mobile thing that will arrive
at the pickup location for pickup and
that will travel to the dropo.ff lo.cation for
dropo.ff, based upon the identity of the
pickup location, the dropoff location, or
both
j
Causing establishment of a seco.nd
communication session in accordance
with the communications method for
providing a notification
~
During the second
communications session,
identifying the mobile thing.
FIG. 178
250b
/
)
2
-
3
4
65
~
\rJ
"C
~
(t
~
.....
~
?
"'
.o
N
0
0
\0
"'
"'
"'

N
N
0
...,
VI
0
Cj
en
-l
~
-l
\Q
Qo
\Q
\Q
l:d
"""
-um
ru x
tgg;
~ ~
(
Start
~
During a communication session with a
personal communications device,
determining a location of the personal
communications device
~
Identifying a mobile thing to travel to
the location or a different location for a
pickup or delivery based upon the
determined location
FIG. 17C
1
250c
)
72
( Start
' Establishing a first communication
session between the system and a
,.
personal communications device
During the first communication session,
determining a location of the personal 1-'
communications device
Selecting a mobile thing from among a
plurality to travel to the location or a
1-
different location for a pickup or
delivery at the location
Establishing a second communication
session between the system and the
personal communications device when
one or more user preferences criteria
relating to travel status of the selected
mobile thing have been satisfied.
FIG. 170
250d
)
3
64
~
'JJ
.
"t;j
~
~
a
~
?
N
9
N
Q
Q
\0
Vl
""
"'

N
w
0
'"" Ul
0
cj
00
--l
~
--l
\C)
'QQ
\C)
\C)
l:d
N
-om
ru x
" ' ~
{[) 0'
g ; ~
(
Start
'
\
t
Monitoring travel data associated with a
mobile thing in relation to a location or 1---
region
Monitoring travel data associated with a
personal communications device in
relation to the location or region
Causing a notification communication
to be initiated to the personal
communications device when the
1-
device is at or within a predetermined
proximity of the location or region
Before, during, or after the forgoing
causing step, causing a different
notification communication to be initiated
to the personal communications device
when the mobile thing is at or within a
predefined proximity of the location or
region
·- ··------
FIG. 18
290
)
3
4
~
rJJ
.
"'0
a
rD
a
~
N
.?
N
0
0
'0
[fl
=-
a
N
....
0
....
<Jo
0
e
r:n
-l
-:....
-l
\0
Oo
\0
\0
l:d
N
"Om
ID X
tgff
...... ;:;;:
!l;m
( '
\
Start

Monitoring travel data associated with a
mobile thing
Scheduling a notification
communication
Analyzing traffic flow predicament data
associated with a travel path to be
traveled by the mobile thing
Rescheduling the notification
communication, based upon the traffic
flow predicament data
FIG. 19A
310a
1-'
)
1---
3
1-
14
( Start
t
Monitoring travel data associated with a
mobile thing

Storing a notification time period
associated with a notification
communication, the time period
indicative of a proximity of the mobile
thing to a location
Analyzing traffic fiow predicament data
associated with a travel path to be
traveled by the mobile thing
Determining when a notification
communication should be initiated,
based upon the notification time period
and the traffic flow predicament data
L-------- --------------
FIG. 198
310b
)
3
1-
24
r:
rJl

1-d
~
-

a
i:;'
?
...
p
...
0
0
\C>
rLl
=-
"'

...
Ul
0
...,
Ul
0
(j
en.
-l
~
-l
\0
Oo
\0
\0
l:d
N
-um
m x
'gff
a ; ~
0
Start
'---
..
Analyzing traffic flow predicament data
associated with a travel path to be
traveled by a party or mobile thing
'
Causing initiation of a notification
communication session with a personal
communications device, based upon
the traffic flow predicament data
r
During the notification communication
session, causing a message to be
provided that indicates a state of traffic
flow along the travel path
- - - - - - - - - - - - - - - ~ -
FIG. 19C
310c
)
33 2
3 33
~
VJ
1-0
~
-
I'D
=
-
;.;<
?
N
9
N
0
0
'<>
"' =-
"
N
"' 0
..,
VI
0
Cj
rn
-.1
':i;..
-.1
\.0
Oo
\.0
\.0
t=
N
-urn
ru x
~ , .
roc;:
- " ~
~ O J
( Start
"\
'
Monitoring travel data associated with a
first communication device

Causing a notification communication session
to be initiated to a second personal
communications device, the notification
communication including a message
requesting a response and a travel status
report indicating a proximity of the first
personal communications device to a location
t
Receiving the response from the
second personal communications
-
device
Communicating the response to the first
personal communications device
- ---- ----- -
FIG. 20A
340a
)
42
4
(
'
\
Start
J
l
Monitoring travel data associated with a
first personal communications device
Receiving a message from the first
personal communications device, the
message including a request for a
response
Causing a notification communication
having the message and a travel status
report of the first personal
communications device to be intiated to
a second personal communications
device

Communicating the response to the first
personal communications device
--- -----
FIG. 208
340b
)
3
54
~
[J1
.
'"e
~
.....
(t)
a
;-
?
N
9
N
0
0
""
r:Ll
::r
"'
l4
N
.._,
0
_,
"' 0
c::
ifJ
---l
-:..
---l
'0
Qo
'0
'0
t:d
N
-um
m x
< g ~
-->.;:::;:
Rlro
Start
./
'
-
Monitoring travel data associated with a
v
first personal communications device
Causing a notification communication
session to be initiated to a plurality of
personal communications devices, the 1--
notification communication including a
message requesting a response
Receiving responses from one or more
of the plurality of personal f--
communications devices
Producing a list of stops for the first
personal communications device, based
upon the responses, the lack of
responses, or· a combination thereof
FIG. 20C
340c
)
2
3
64
~
~
'"d
a
rD
a
i:;<
?
"'
9
"'
0
0
\0
rn
=-
a
N
QO
0
...,
Vl
0
(j
'fl
-I
-:....
-I
'0
Oo
'0
'0
Cd
N


2]oo
RECIPIENTS OF NOTIFICATION
MESSAGES
75h
75g


TELEVISION
MOBILE PHONE
751
........
.... ........... _
J'
PERSONAL OR


75e

WIRELESS VIEWER
75d
'-..
PERSON'

COMPUTER
"THE JONE:$ FAMtl V,
PARn' OF"' IS ARRIVING Ill '4 , t
IN 20 MINUTES, PLEASE I
CONFIRM A RESERVATION
IF AVAILABLE BETWEEN
20 • 45 MINUTES FROM
THIS TIME?
-==-:-=:··
75
.C11
10
BASE STATION CONTROL
UNIT/S
40a
D
40b
D
FIG. 21 40
VEHICLE NAVIGATION DEVICE WITH
NOTIFICATION MESSAGING
@··
MOBILE COMMUNICATION DEVICE
EQUIPPED WITH LOCATION DEVICE
VEHICLE WITH ROUTE
OR STOP LIST
DEVICE
@
''"" o(
n.
75
75b

f'J
'"d

""'"
(!>
a
'-<
.,
?
N
9
N
0
0
\C
"' ::r
"'

N
\C
0
....,
Ul
0
e
'71

--!

Qo


C:i
""
-um
ID X

-->.;::;,:

COMMUNICATION OPTIONS
COMMUNICATION THROUGH BSCU
40
D


. .
405
COMMUNICATION DIRECT (NO BSCU)
.Q,
JOIN BOB JONES AT XVZ ITALIAN
BOB JONES IS ARRIVING IN 20 MINUTES
RESPONSE MUST BE RECEIVED WITHIN
AT THE XYZ Uallan Restaurant .••
4 MINUTES & 57 SECONDS
WILL YOU JOIN THEM? Plt::AS RESPOND
75j
I
75i
FIG. 22
--


'"d

-
(!>
=
-
'-<
..
?
N
?
N
0
0
""
00.
::r
a
w
0
0
....,
Ul
0
d
fJj
-l
':!:.
-l
'0
Oo
'0
'0
i:d
I;.>


Cll 0'
....... ;::;:

RECIPIENTS OF
NOTIFICATION MESSAGES
75h
'"""
PERSON'S
75g'"' TELEVISION ,
m

75f'"'
PERSON'S
NAVIGATION SYSTEM

'
.
75d
"""" PERSON'S
NETWORKED COMPUTER
"THE WHITE FAM!L Y,
PARTY OF 4 IS ARRIVlNG II t ' \
IN 20 MINUTES, PLEASE
CONFIRM A RESERVATION
IF 6ElWfEN
20 • 45 MINUTES FROM
THIS TIME.?

r=--- I
75
MTCU
: e;. A ·oETERMiN,NG M •
(IN-VEHICLE NAVIGATION SYSTEM)
E.G., MAPPING, : 431 425
HISTORIC DATA, ;f
TRAFFIC, ETC. •
(External and/or
'!. __ .. ____ :
-------------- ..
POSITIONING
SYSTEM E.G ..
GPS,lORAN,
.
I GLONASS •
----------------·
427
SEND
NOTIFICATION
REQUEST
RESPONSE
; .................... ,,,,_. !! ; I
• AUDIO (VOICE)
SELECT COMPANY
FROM LIST TO
NOTIFY
MENU
--- -r---- .. -·
433 \ Vehicle $ystem
I ./ 7 ?r--
438
439
__ .
1.l XV% llalla11 Rnltountnl WAITING FOR A RESPONSE
J:j"iii!ii;;ch'Gin-. ----------------
FIG. 23
15
426
428

1J)
.
"'0

-
!'!>
=
-

N
.o
N
0
0
""
"'
:r
&
"'
,...
0
....
Ul
0
c::
rJ)
-l
':!:..
-l
\0
Qo
\0
\0
t;d
N
"m
ID X

8;0l
454
455
456
457
HAS RESPONSE OCCURRED?
NO
RESPONSE FAILURE
STATE BEEN
REACHED?
453
AN ARRIVAL NOTIFICATION
WAS SELECTED FOR THE
XVZ ITALIAN RESTAURANT
NO
SHOULD THE MESSAGE
RECIPIENT RESPOND?
YES NO
RESPONSE
FAILURE
STATE?
PERSON'S
NETWORKED COMPUTER
75d
NOTIFICATION WAS
.0.
RECEIVED AND YOU HAVE
A CONFIRMED
RESERVATION AT 6:40PM
UNDER WHITE
YES
PlEASE CHECK-IN UPON
ARRIVAL. THANK YOU.
--
--=-'"
YES
1-1
PERSON'S
75k IN-VEHICLE NAVIGATION SYSTEM
448
XYZ Italian "NotlHcilltltln Wall Raooelved
And You Have A CONFIRMED RESERVATION AT G:40PM
Under Whlta. Please Check-In Upon Arrival. Thank You.
--··-- -------
FIG. 24

r:J'J

'"d

......
('!)
a
;.;<
?
N
9
N
0
0
""
"' =-
"'
...
N
0
....,
Ul
0
d
r:n
-l
-:.:...
-l
\Q
Oo
\Q
\Q

-um
W X

CDO'
........ ;:::;;

461
IN•V!:HICLE NAVIGAllOH SYSTEM UTILIZING TIME BEFOREfAFTER MESSAGE
WAS SENT AS THE DEFAULT FOR RECIPIENTS TO RESPOND TO NOTIFICATION MESSAGES
I 1 .r "- 7 :;o>r--._
• at Nattncatlan Mosugu Must
Wllllln (S M!nutoll Or Sys\Om Will Nllt Except'/
FIG. 25A
IN•\IEHICLE HA\IJGATlOr-1 SYSTEM UTILIZING LOCATlOtl AFTER MESSAGE
463
WAS SENT AS THE DEFAULT FOR RECIPIENTS T0R£SP0NOTO NOllRCATION MESSAGES
I I I "" .... .. " l 7 ::;;:::::
ETA= 20 minutes -12 Miles
Raclplonts of NoUflcollon MnugM Muot RMp"nd
Antvea AI ThsPnosel Laca\lon,
DISpl:!yed On-Semen?
FIG. 25C
462

IN-VEHICLE NA\!IGAT!Ot.i SYSTEM UnLIZING DISTANCE AFTER MESSAGE
WAS SENT AS THE DEFAULT FOR RECIPIENTS TO RESPOND TO NOTIFICATION MESSAGES
1, "' --... 7
Reclplontsof Menag .. Must Respond
Wltbln (& Mnes) orsystsm wm Promt>l For
Accuptance?
FIG. 258
464
IN-VEHICLE NAVIGATlON SYSTEM UTILIZING FIRST RESPONSE AFTER MESSAGE
WAS SENT AS THE OEFAUL T FOR RECIPIENT$ TO RESPOND TO NOTIFICATION MESSAGES
I I ./ "' 7 .;;::::::::-
Tho Flmt RaetplontTo TheNalmcallon Mossag""
Will Ba &.eapllld?
FIG. 250

rJJ

"'C

-
(D
=
-
it
?
N
9
N
0
0
'CI
00
=-

w
w
0
....,
Ul
0
d
"'

-.l
\0
Qo
\0
\0
1:0
N