throbber
111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111
`US 20030100326Al
`
`(19) United States
`(12) Patent Application Publication
`Grube et al.
`
`(10) Pub. No.: US 2003/0100326 Al
`May 29, 2003
`(43) Pub. Date:
`
`(54) GROUP LOCATION AND ROUTE SHARING
`SYSTEM FOR COMMUNICATION UNITS IN
`A TRUNKED COMMUNICATION SYSTEM
`
`(76)
`
`Inventors: Gary W. Grube, Barrington, IL (US);
`Leslie Gabor Seymour, Barrington, IL
`(US)
`
`Correspondence Address:
`MOTOROLA, INC.
`1303 EAST ALGONQUIN ROAD
`IL01/3RD
`SCHAUMBURG, IL 60196
`
`(21) Appl. No.:
`
`09/995,231
`
`(22) Filed:
`
`Nov. 27, 2001
`
`Publication Classification
`
`(51)
`
`Int. CI? ....................................................... H04B 7/00
`
`(52) U.S. Cl. ........................... 455/515; 455/445; 455/518
`
`(57)
`
`ABSTRACT
`
`Methods are disclosed for sharing location and route infor(cid:173)
`mation between communication units (e.g., talkgroup mem(cid:173)
`bers) that are subscribed to a group location sharing service.
`The group location sharing service is event-based, such that
`the communication units may form a subset of a talkgroup
`desiring to actively participate or monitor an event. Com(cid:173)
`munication units de-subscribe from the group location shar(cid:173)
`ing service or talkgroup when they no longer desire to
`participate or monitor the event. Service levels may be
`determined for various subscribers to the group location
`sharing service. The service levels may include, for
`example, an information transmission service level and
`information reception service level that determine an
`amount, type, and/or timing of information to be sent or
`received by particular subscribers.
`
`~ 107
`
`~ 108
`
`~ 113
`
`109
`
`~ 106
`
`Apple Inc. 1025
`U.S. Patent No. 9,445,251
`
`

`

`Patent Application Publication May 29, 2003 Sheet 1 of 10
`
`US 2003/0100326 A1
`
`100
`
`~ 107
`
`~ 108
`
`~ 113
`
`109
`
`~ 106
`
`WIRELESS
`INFRASTRUCTURE
`
`FIG. 1
`
`~ 110
`
`......
`
`"\
`
`l J
`._J
`..._J.
`1-J·
`
`~J-
`.._J·
`
`/'\17
`r-115
`
`TRANSCEIVER
`PROCESSOR
`MEMORY
`SELECTION
`ELEMENT
`OPERATOR
`INTERFACE
`I
`I LOCATION
`DETERMINATION
`
`(
`
`

`

`Patent Application Publication May 29, 2003 Sheet 2 of 10
`
`US 2003/0100326 A1
`
`MOBILE GROUP LOCATION MAP DISPLAY
`
`FIG. 2
`
`

`

`Patent Application Publication May 29, 2003 Sheet 3 of 10
`
`US 2003/0100326 A1
`
`USE CU SELECTION ELEMENT TO REQUEST LOCA liON SHARING
`
`301
`
`BUILD LOCATION SHARING SERVICE INITIATION REQUEST MESSAGE
`FOR THE EVENT IN THE CU UEMORY
`
`TRANSMIT LOCATION SHARING SERVICE INITIATION REQUEST
`MESSAGE FROM THE INITIATING CU
`
`RECEIVE LOCATION SHARING SERVICE INITIATION REQUEST
`MESSAGE IN POTENTIAL SUBSCRIBING CUs
`
`USE SELECTION ELEMENT OF THE RECEIVING CUs TO SUBSCRIBE
`TO THE LOCATION SHARING SERVICE FOR THE EVENT
`
`REGISTER THE SUBSCRIPTIONS FRON THE CUs SELECTING THE
`PARTICIPATION IN THE LOCATION SHARING SERVICE
`
`JOl
`
`.109
`
`v
`
`311
`
`NEW LOCATION INFORMATION FOR THE
`EVENT IS AVAILABLE
`SUBSCRIBER CUs FOR THE EVENT
`ARE REGISTERED
`TRANSMIT NEW LOCATION INFORMATION TO
`REGISTERED SUBSCRIBER CUs
`
`RECEIVE LOCATION INFORMATION BY
`REGISTERED SUBSCRIBER CUs
`
`FIG. 3
`
`

`

`Patent Application Publication May 29, 2003 Sheet 4 of 10
`
`US 2003/0100326 A1
`
`REQUEST LOCATION SHARING
`
`401
`
`REQUEST VOICE CHANNEL
`
`REQUEST LOCATION
`
`403
`
`405
`
`GLSS ALREADY INITIATED ?
`NO
`
`TRANSMIT NEW UNIT STATUS OF
`INITIATING OR SUBSCRIBING
`
`417
`
`SELECT FILTERING POLICY
`
`GET LOCATION
`
`419
`
`421
`
`CONSTRUCT INITIALIZATION AND
`SUBSCRIPTION PARAMETER BLOCK
`
`423
`
`TRANSMIT PARAMETER BLOCK
`
`425
`
`LOC SHARING REQ. RELEASED ?
`
`RELEASE VOICE CHANNEL
`
`NO
`427
`429
`
`FIG. 4
`
`

`

`c START )
`-.
`I RECEIVE TRANS~ISSION FROM SUBSCRTBER
`;
`APPLY filTERING POLICY ON SENDING SUBSCRIBER 503
`NO~E""XI=sT""'"IN=G--;O"'R -;;N=Ew". ~AU;;-;lTT.-o:HO'""'RI...-ZE""D--;S""UB=s=cR=Is=ER~? 505
`YES
`
`l-501
`
`FIG. 5
`
`I.
`
`525
`
`nrs
`INSERT THE NEW
`SUBSCRIBER WITH ITS
`NEW LOCATION
`INTO THE
`GROUP LOCATION AND
`SUBSCRIBER FILTERING
`CONSTRAINTS TABLE
`
`513
`
`BROADCAST NEW GLSS
`ANNOUNCEMENT AND
`LOCATION
`
`517
`IJ
`
`I
`
`I
`
`REJECT
`REQUEST OR
`NOTIFICATION
`
`527
`
`Ll
`
`I
`
`I
`
`REJECT
`SUBSCRIPTION
`.....,......
`REQUEST
`
`531
`=INE=w~Lo=c~AT,~IO~N=RE=Po~RTr ~===rl~~~J
`
`533
`
`UPDATE GROUP
`LOCATION TABLE
`WITH NEW
`SUBSCRIBER
`LOCATION
`
`543
`
`REMOVE THE SUBSCRIBER
`FROM THE GROUP
`LOCATION AND
`SUBSCRIBER-FILTERING
`TABLE
`L
`
`-+~--___j
`535
`· -PLY m=TE~RI=Nc,.....,p=oL=rc.,.,.....u
`ON GROUP LOCATION
`CHANGE
`
`539
`BROADCAST NEW LOCATION AND/
`~~ OR SUBSCRIPTION CHANGE TO All
`SUBSCRIBING CLIENT DEVICES IN
`THE GROUP LOCATION TABLE
`
`NO
`
`~
`
`-= ~
`~ = ~ >
`
`~
`~
`
`~
`~
`
`'t:)
`'a
`;:;·
`~· =
`-= c:
`0" -;:;·
`~· =
`~
`~
`'<
`
`N ::c
`~ a
`'J). =-~
`
`N
`
`~
`~
`til
`
`~ -..
`
`~
`~
`
`c
`
`'J).
`N
`
`~
`
`~ a -~
`~ a N
`="" > ~
`
`7
`
`

`

`(
`
`I
`
`~PJ
`NOTIFICATION FROU
`OTHER SUBSCRIBER?
`
`INITIATION?
`
`NOTIFICATION?
`
`NEW GLSS I I SUB~~:IBER
`•
`
`RECORD
`GLSS
`INITIATION
`IN GROUP
`LOCATION
`OUTPUT
`BUFFER
`
`PUT NEW
`SUBSCRIBER
`WITH NEW
`LOCATION IN
`GROUP
`LOCATION OUTPUT
`BUFFER
`I
`
`6.JJ
`
`605
`
`601
`
`609
`
`NEW
`LOCATION
`UPDATE?
`
`l..-651
`
`SUBSCRIBER
`LOCATION IN
`GROUP LOCATION
`
`653
`
`i-643
`
`SET
`REQUEST
`FAILURE
`INDICA liON IN
`GROUP
`LOCATION
`OUTPUT BUFFER
`
`SET
`REQUEST
`SUCCESS
`INDICATION
`IN GROUP
`LOCATION
`OUTPUT BUFFER
`
`CLEAR GROUP
`LOCATION
`OUTPUT BUFFE
`FROM NEW
`GROUP
`LOCATION
`UPDATES
`
`641
`~Jl
`DE -SUBSCRIPTION
`NOTIFICA liON?
`
`•
`•
`
`REUOVE
`SUBSCRIBER
`AND ITS
`LOCATION
`FROU GROUP
`LOCATION
`OUTPUT
`BUFFER
`
`FIG. 6A
`
`""C
`~ .....
`~ = .....
`~ 't:l -....
`.... 0 =
`0' -....
`.... 0 =
`
`I")
`
`~ .....
`
`~
`
`I")
`
`~ .....
`
`~
`~
`'-<
`N
`~~
`N c
`8
`'JJ. =(cid:173)~
`~ .....
`0'1
`0 ......,
`'"""' c
`
`Cj
`'JJ.
`N c
`@
`c
`'"""' c
`8 N
`>
`'"""'
`
`0'1
`
`

`

`625
`
`SET NEW
`UNIT
`STATUS:
`GLSS
`INITIATED
`
`m}T _____ i _____ r,
`1 1 APPLY FILTERING POLICY ON 1 1
`L.,l.. _____ I _____ .J....J
`GROUP LOCATION CHANGE
`I
`I
`I
`I
`r 645
`NO( R"~~~.Y~~}'}
`
`I
`
`665
`
`r 673
`
`/683
`
`RESET
`PENDING
`INITIATION/
`SUBSCRIPTION
`STATUS
`
`SET GLSS
`~NITIATED OR
`SUBSCRIBED
`TO STATUS
`
`CLEAR
`GLSS
`NIT IA TEO OR1
`SUBSCRIBED
`TO STATUS
`
`675
`
`ENABLE
`PERIODIC
`LOCATION
`TRANSMISSIONS
`
`CANCEL
`PERIODIC
`LOCATION
`TRANSMISSIONS
`
`OUTPUT NEW GROUP
`LOCATION BUFFER
`
`655
`
`FIG. 6B
`
`~
`ll:l
`
`"0
`
`~ = ....
`>
`"0 -;::;·
`ll:l ....
`~· =
`~
`0"' c:
`ll:l ....
`~· =
`~
`ll:l
`'-<
`N :p
`N
`Q
`Q
`~
`
`~
`
`\FJ ::r
`~
`~
`-...l
`
`~ -..
`
`~
`Q
`
`d
`\FJ
`N
`
`Q
`
`@
`~ 8 N
`~ > ~
`
`

`

`Patent Application Publication May 29, 2003 Sheet 8 of 10
`
`US 2003/0100326 A1
`
`START )
`
`GLSS STATUS
`INITIATED OR
`SUBSCRIBED TO?
`YES
`DETERMINE
`LOCATION
`
`•
`
`NO
`
`YES
`
`701
`
`707
`
`'-705
`
`7 09
`
`'-703
`DETERMINE CHANGES IN SPEED, ROUTE
`AND/OR ESTIMATED TIME OF ARRIVAL IF ANY
`~
`LOCATION CHANGE
`SI GNIFI GANT?
`.NO
`DETERMINE IF CHANGES IN SPEED, ROUTE
`AND/OR ESTIMATED TIME OF ARRIVAL ARE SIGNIFICIANT
`
`•
`NO
`ANY CHANGES
`SIGNIFIGANT? ~ 711
`-.
`YES
`TRANSMIT LOCATION AND/OR
`OTHER CHANGES TO GLSS
`CONTROLLER
`
`713
`
`~
`
`END
`
`)
`
`FIG. 7
`
`

`

`INIT
`cu
`SELECTING
`ELEMENT
`122
`
`INIT
`cu
`LOC
`DET
`126
`
`!NIT
`CLNT
`PROC
`
`. --
`
`!NIT
`CLNT
`LOC
`NOTIF
`FIG 7
`
`INIT
`CLNT
`SRVR
`NOTIF
`114
`
`GLSS
`CONTROLLER
`101
`
`GVC
`VOICE
`CHAN
`CTRL
`103
`
`GLSS
`CLNT
`CLOCK
`
`SBSCR
`CLNT
`SRVR
`NOTIF
`
`SBSCR
`CLNT
`LOC
`NOTIF
`FIG 7
`
`SBSCR
`CLNT
`PROC
`
`SBSCR
`cu
`LOC
`DET
`126
`
`114
`
`118
`
`I
`
`SBSCR
`cu
`UI
`124
`
`..J,..
`
`..J,..
`
`..J,..
`
`...)..
`
`..J,..
`
`FIG. BA
`
`850
`
`cD
`
`826
`
`~
`
`I
`I
`I
`
`cD
`
`'t:l
`
`""C
`~ ....
`~ = ....
`>
`'t:l -.... n
`~ .... .... 0 =
`""C = 0'
`-.... n
`~ .... .... 0 =
`
`~
`
`~
`~
`N
`~~
`N c
`8
`rJ'1 =-~
`~ ....
`~
`0 .....,
`1-" c
`
`Cj
`rJ'1
`N
`
`c c
`
`~ -c
`
`1-"
`c
`8 N
`> 1-"
`
`0'1
`
`

`

`0
`
`-r
`-r
`'r
`I
`I
`I
`I
`I
`I
`I
`I
`I
`I
`I
`I
`I
`I
`I
`I
`I
`I
`I
`I
`I
`828 .
`I
`I
`I
`~ I
`I lOJI-OJJ}
`'
`I
`· •
`I
`OUTPUT GROUP I LOC BUFFffR
`I
`• SHOWING I NEW SUBSICRIBER CUI ( 655)
`
`'r
`I
`I
`I
`I
`I
`I
`I
`I
`
`1
`
`•
`
`-r
`-r
`I
`I
`; GET LOC_I
`1,.REV LOCI
`
`~I
`
`I
`
`CD
`
`SUBSCRIPTION
`VOICE
`ANNOUNCEMENT
`
`856
`
`I
`I
`
`1 1\L.LLn-.JL 'v~vL v11n~111LL \ •
`
`::
`
`:VOICE TRANSMIT
`I (671~673) I
`
`829
`
`FIG. B.B
`
`I")
`
`~ .....
`
`""C
`~ .....
`~ = .....
`~ 't:l -....
`.... 0 =
`0' -....
`.... 0 =
`
`~
`
`I")
`
`~ .....
`
`~
`~
`'-<
`N
`~~
`N c
`8
`'JJ. =(cid:173)~
`~ .....
`'"""' c
`0 .....,
`'"""' c
`
`Cj
`'JJ.
`N c
`@
`c
`'"""' c
`8 N
`>
`'"""'
`
`0'1
`
`

`

`US 2003/0100326 Al
`
`May 29,2003
`
`1
`
`GROUP LOCATION AND ROUTE SHARING
`SYSTEM FOR COMMUNICATION UNITS IN A
`TRUNKED COMMUNICATION SYSTEM
`
`FIELD OF THE INVENTION
`
`[0001] The present invention relates generally to trunked
`communication systems and, in particular, to a group loca(cid:173)
`tion and route sharing service for communication units in a
`trunked communication system.
`
`BACKGROUND OF THE INVENTION
`
`[0002] Trunked communication systems are known to
`include a wireless infrastructure and a plurality of commu(cid:173)
`nication units, such as mobile or portable two-way radios or
`mobile data terminals. Some communication systems, such
`as those used for public safety, also include a dispatch
`console and a so-called "computer aided dispatch (CAD)
`system" that includes a display-based terminal to control
`communications between the communication units. The
`CAD terminal typically displays categorized tables of infor(cid:173)
`mation to the terminal user (typically referred to as a
`"dispatcher" or "dispatch operator"). For example, the CAD
`terminal may display queues of currently pending incidents
`and/or a list of communication units that are currently
`available. In addition, some CAD terminals include an
`integrated mapping program that enables the CAD terminal
`to display locations of communication units on a map that
`represents a geographic area supported by the dispatch
`system. The locations of the communication units are typi(cid:173)
`cally provided to the CAD system on a periodic basis by an
`automatic vehicle location (AVL) system that is coupled to
`the CAD system via a dedicated communication link.
`
`[0003]
`In addition to receiving communication unit loca(cid:173)
`tion information, the CAD system may also receive incident
`information from a 911 system that is coupled to the CAD
`system. For example, the map may display the origination
`point of a 911 telephone call to the dispatcher as an icon on
`the map. By viewing communication unit location, commu(cid:173)
`nication unit status, and incident location on the map, the
`dispatcher can determine which communication unit users
`(e.g., policemen, firemen, paramedics, and so forth) would
`be in the best situation to respond to the incident. As an
`incident is attended to by users of the communication units,
`the status of the communication units associated with such
`users is updated either manually by the dispatcher or auto(cid:173)
`matically by the CAD system responsive to messaging from
`the wireless infrastructure. In the latter case, the wireless
`infrastructure receives status updates over a wireless com(cid:173)
`munication channel from the communication units that are
`participating in the handling of the incident. Changes in
`communication unit status are typically indicated to the
`dispatcher by some type of visual change, such as a color
`change or icon update, to the participating unit's represen(cid:173)
`tation on the map.
`
`[0004] A map display, with icons representing the inci(cid:173)
`dents and the communication units with their current status,
`gives a dispatcher a useful tool for evaluating an emergency
`situation. By using standard graphical user interface (GUI)
`cursor interaction (e.g., point and click or drag and drop), the
`dispatcher can manipulate the screen icons to assign units to
`incidents. Thereafter, the dispatcher may communicate
`information to the assigned units such as, for example, the
`
`incident location and other details. As one may appreciate,
`such systems place a heavy burden upon the dispatch
`operator, particularly where events and details are rapidly
`changing. It is possible that a dispatcher might assign units
`to an incident that are not in the best position to respond or
`conversely, fail to assign units that otherwise would wish to
`respond or at least monitor the event. Perhaps even more
`problematic is the difficulty in determining the type, extent
`and timing of information to be provided to the assigned
`units. The problem is exacerbated when one considers that
`certain units may wish to change their level of participation
`as the incident progresses.
`
`[0005] For example, consider a police chase scenario
`involving multiple police cars pursuing a fleeing vehicle. It
`would be desirable for all of the pursuing police cars to
`receive real time location and/or route information to deter(cid:173)
`mine what they each will do to help stop the wanted vehicle.
`In most instances, the police chase scenario relies upon the
`lead car broadcasting cross-street references directly to the
`other assisting vehicles or to the dispatch center for re(cid:173)
`broadcast. The dispatch operator is burdened with determin(cid:173)
`ing which of the field units are involved in the event,
`relaying the cross-street references and team member loca(cid:173)
`tion information to the team. However, this verbal method is
`prone to errors and it distracts the lead unit from the primary
`task of the high-speed chase. In addition, the lead car or
`assisting cars may not really know what other units are
`assisting in the chase and where they are. Knowing the total
`"team" of assisting units and where they are, what routes
`they have followed and what routes they are planning to
`follow can help determine a chase strategy.
`
`[0006] Even if the team member location could be con(cid:173)
`veyed correctly from the dispatcher to all participating
`vehicles, the comprehension of the spatial relations of these
`vehicle locations to other important and relevant events,
`temporary and potentially moving objects may be severely
`impaired if not completely impossible. Such temporal
`objects could include injured persons, pockets of activities
`of accidents and violence, etc. On the other hand, the
`continuous transmission of location information to a remote
`site where it may be displayed also in non-emergency
`situations may pose an additional problem of the perceived
`intrusion of work-place privacy or even a security risk. As
`one can imagine, the current location methods are very
`error-prone, untimely, limited both in the completeness of
`location information to be conveyed and in the desired
`access control.
`
`[0007] Current methods are also are deficient in terms of
`route information, such as the visualization of the spatial
`context of traversed trajectories, planned routes of the work(cid:173)
`team members and the moving objects related to an event.
`Route information (e.g., knowing which routes are to be
`followed, or which routes have already been visited by other
`responding vehicles) and the timeliness of the route infor(cid:173)
`mation is also important, particularly in assignments where
`territorial coverage optimization is needed or desired.
`Examples of such missions are neighborhood-patrolling,
`search for persons and/or for objects, public works for snow
`removal, road inspections, utility readings, delivery drop(cid:173)
`off/pick-up routes, on-demand car-pooling, etc. Particularly
`for larger work groups, up-to-date route information would
`have been impossible to convey only verbally, especially
`when the routes are changing based on real-time events. In
`
`

`

`US 2003/0100326 Al
`
`May 29,2003
`
`2
`
`real life situations, a compounded problem is the need for a
`real-time, on-going optimization of the set of routes for all
`group members as a whole, which makes the use of a verbal
`only communication with no visualization support even less
`effective.
`
`[0008] Accordingly, there is a need for a group location
`and/or route sharing service whereby participating commu(cid:173)
`nication units share location and/or route information for a
`particular event. It would be desirable for field units them(cid:173)
`selves, or a third party on behalf of the field units, to
`subscribe for participation in an event based on the com(cid:173)
`munication units' ability or desire to respond. Advanta(cid:173)
`geously, the subscribing units may comprise a talkgroup or
`subset of a talkgroup assigned to an event. There is further
`a need for such a group location and/or route sharing service
`to provide for different levels of participation and/or service
`levels for the subscribing units. The service levels may
`include, for example, an information transmission service
`level and information reception service level that determine
`an amount, type, and/or timing of information to be sent or
`received by particular subscribers. The present invention is
`directed to addressing or at least partially addressing these
`needs.
`
`SUMMARY OF THE INVENTION
`
`[0009] According to one embodiment of the present inven(cid:173)
`tion, there is provided a method for a communication unit
`engaged in a group dispatch voice call to participate in a
`location sharing service. The communication unit receives a
`message initiating a location sharing service associated with
`an event. Responsive to receiving the message, the commu(cid:173)
`nication unit, or a third party (e.g., controller) on behalf of
`the communication unit, subscribes to the location sharing
`service so as to receive location information associated with
`the event. Optionally, the communication unit may send
`location information associated with the event. The location
`information may comprise, for example, the location of the
`communication unit and/or the location of an incident the
`resolution of which requires the location sharing service.
`
`[0010] According to another embodiment of the present
`invention, there is provided a method for groups of com(cid:173)
`munication units engaged in dispatch voice calls to partici(cid:173)
`pate in a location sharing service according to different
`service levels. A group of communication units, such as a
`talkgroup or subset of a talkgroup, subscribes to the location
`sharing service, yielding a plurality of subscriptions. The
`subscriptions are associated with respective service levels
`which are based, for example, on the amount or type of
`information to be transmitted or received by the various
`subscribers. Thereafter, location information is exchanged
`between the subscribers based on the service levels. The
`service levels may be based on the level of participation of
`the subscribers for a particular event, for example, active
`units or monitoring units. The location information may also
`be exchanged in response to triggering events such as, for
`example, change(s) in location or speed, expiration of a time
`period since the last location information exchange, de via(cid:173)
`tions in route or travel time of certain subscriber(s), or upon
`certain subscriber(s) entering or being within a particular
`geographic reference area.
`
`[0011] According to still another embodiment of the
`present invention, there is provided a method for commu-
`
`nication units engaged in a group dispatch call that are
`distributed among a plurality of locations to participate in a
`location sharing service, whereby the communication units
`are eligible for movement causing changes in the plurality of
`locations. The method comprises a first communication unit
`sending a message initiating a group location sharing service
`to one or more receiving communication units. The receiv(cid:173)
`ing units or a subset of the receiving units subscribe to the
`location sharing service, forming a group of participating
`units. Thereafter, a first plurality of the participating units
`receive periodic location update information associated with
`a second plurality of the participating units.
`[0012] According to yet another embodiment of the
`present invention, there is provided a wireless communica(cid:173)
`tion unit operable to participate in a location sharing service.
`The communication unit includes a radio frequency trans(cid:173)
`ceiver, operable to send and receive messages initiating an
`event-based location sharing service; a selection element
`enabling an operator to selectively subscribe to the event(cid:173)
`based location sharing service, thereby enabling the radio
`frequency transceiver to receive location information asso(cid:173)
`ciated with an event; and an operator interface for commu(cid:173)
`nicating at least a portion of the location information to the
`operator.
`
`BRIEF DESCRIPTION OF THE DRAWINGS
`
`[0013] FIG. 1 illustrates a block diagram of a communi(cid:173)
`cation system in accordance with one embodiment of the
`present invention;
`[0014] FIG. 2 illustrates an exemplary map displayed to a
`user of a communication unit;
`[0015] FIG. 3 is a flowchart illustrating a high-level
`location sharing service algorithm according to the present
`invention;
`[0016] FIG. 4 is a flowchart showing a GLSS client
`algorithm for processing user input from a group voice call
`talkgroup member;
`[0017] FIG. 5 is a flowchart illustrating steps performed
`by a GLSS controller to implement a group location sharing
`service;
`[0018] FIG. 6 is a flowchart showing a client algorithm for
`processing GLSS update notifications from a GLSS control(cid:173)
`ler;
`[0019] FIG. 7 is a flowchart showing an algorithm for
`processing periodic location updates from GLSS clients; and
`[0020] FIG. 8 is a message sequence chart showing
`example GLSS service initiation, subscription and location
`update notifications.
`
`DETAILED DESCRIPTION OF PREFERRED
`EMBODIMENTS
`
`[0021] Turning now to the drawings and referring initially
`to FIG. 1, there is shown a block diagram of a communi(cid:173)
`cation system 100 in accordance with the present invention.
`The communication system 100 includes a plurality of
`communication units 105-113 that communicate with a
`wireless infrastructure 103 and/or each other over one or
`more communication resources 114 (one shown). The com(cid:173)
`munication system 100 may be either a conventional system
`
`

`

`US 2003/0100326 Al
`
`May 29,2003
`
`3
`
`or a trunked system and each communication resource 114
`may comprise a frequency carrier, one or more time slots of
`a frequency carrier, or an orthogonal code implemented by
`a respective frequency hopping pattern or by a pseudo(cid:173)
`random noise sequence spread over a wide bandwidth (e.g.,
`3 MHz).
`
`[0022] The communication units 105-113 comprise two(cid:173)
`way mobile radios, two-way portable radios, or two-way
`wireless data terminals. The wireless infrastructure 103
`supports the particular communication system 100 and,
`therefore, comprises one or more base stations (e.g., in a
`conventional system) or one or more base stations and one
`or more system controllers (e.g., in a trunking system).
`Typically, the wireless infrastructure 103 also includes one
`or more dispatch consoles comprising fixed computer-aided
`dispatch (CAD) terminals, which may be coupled to an
`automated vehicle location (AVL) system and an emergency
`911 system (not shown). The AVL system and the 911
`system are well known; thus, no further discussion of them
`will be presented except to facilitate an understanding of the
`present invention.
`
`[0023] The wireless infrastructure 103 includes or is
`coupled to a group location sharing service (GLSS) server or
`controller 101. As will be described in greater detail here(cid:173)
`inafter, the GLSS controller 101 is adapted to coordinate and
`manage group location sharing service(s) between partici(cid:173)
`pating communication units and/or infrastructure devices.
`As will be appreciated, the GLSS controller 101 is a
`functional element that may reside in one or more physical
`devices. For example, the GLSS controller may reside
`within a personal computer or functional equivalent, a
`dispatch console or server, the AVL system or 911 system or,
`in a trunking system, may reside within one or more system
`controllers. Alternatively or additionally, the GLSS control(cid:173)
`ler may be distributed among the various communication
`units 105-113.
`
`[0024] As depicted in FIG. 1 in block view (only com(cid:173)
`munication unit 105 shown), the communication units 105-
`113 include an antenna 115, radio transceiver 116, processor
`118, memory 120, selection element 122, operator interface
`124 and location determination element 126. As will be
`appreciated, the various elements are functional elements
`that may reside in one or more physical devices and, in some
`implementations, may be operated remotely from
`the
`vehicle associated with the communication unit 105. For
`example, ergonomic efficiency may be realized by incorpo(cid:173)
`rating some or all of the elements into a mobile or portable
`dispatch radio or phone that may be operated inside or
`outside of a vehicle.
`
`[0025] The radio transceiver 116 is coupled to the proces(cid:173)
`sor 118 and antenna 115 to enable the communication unit
`105 to exchange information (e.g., voice, video, data, text,
`etc.) with the wireless infrastructure 103 and/or other com(cid:173)
`munication units via an RF channel (i.e., communication
`resource 114). In the preferred embodiment, the transceiver
`116 is used to exchange messages with the GLSS controller
`101 to initiate and/or subscribe to a location sharing service
`and, for those communications units having initiated or
`subscribed to the location sharing service (hereinafter, "sub(cid:173)
`scribers" or "subscriber units"), to send location information
`to or receive location information from the GLSS controller
`101. In the former case, the location information (or a
`
`portion thereof) may be forwarded from the GLSS controller
`to various subscribers whereas in the latter case, the location
`information may have been received by the GLSS controller
`from various subscribers. Alternatively or additionally, the
`transceiver 116 may be used to exchange messages and/or
`location information directly with other communication
`units.
`[0026] The processor 118 comprises a microprocessor and
`a digital signal processor for controlling the various ele(cid:173)
`ments of the communication unit 105 and for communicat(cid:173)
`ing with the wireless infrastructure 103. The memory 120
`comprises a random access memory (RAM), read only
`(ROM), programmable
`read only memory
`memory
`(PROM), and/or a floppy disk to store software algorithms
`and data, such as communication information, used by the
`processor 118 during operation of the communication unit
`105. The processor 118 and memory 120 enable computa(cid:173)
`tional processing necessary for executing wireless transmis(cid:173)
`sions, and communication services such as two-way radio
`voice communication services, including dispatch or talk(cid:173)
`group call services. The processor and memory also enable
`execution of location or route sharing services, separately or
`in combination with the talkgroup call services. The pro(cid:173)
`cessor and memory further enable certain location-based
`data applications such as, for example, map-based location
`tracking and routing applications that track the location and
`manage the route of the communication unit 105.
`[0027] The selection element 122 comprises a user input
`device such as, for example, a push-to-talk (PTT) activator
`or push button of a mobile or portable dispatch radio/phone,
`foot switch, panel microphone, computer mouse or equiva(cid:173)
`lent (e.g., trackball or touchpad), keyboard or touchscreen,
`voice activated device, voice recognition device, or some
`combination thereof to enable the operator of the commu(cid:173)
`nication unit 105 to initiate a location sharing service or
`subscribe to an already-initiated service. That is, the opera(cid:173)
`tor uses the selection element 122 to express a desire to
`initiate or subscribe to the location sharing service, which
`desire is communicated, via the transceiver 116 and wireless
`infrastructure, to the GLSS controller 101. The selection
`element may similarly be used by the operator to de(cid:173)
`subscribe to the location sharing service.
`[0028] The operator interface 124 comprises an input
`device, incorporating (or separate from) the selection ele(cid:173)
`ment 122, that permits a user to input information other than
`initiation of or subscription to a location sharing service for
`transmission to one or more of the communication units
`105-113 or the wireless infrastructure 103; and output device
`such as a display having speaker(s) for communicating
`voice, video and/or data to the operator of the communica(cid:173)
`tion unit 105. In the preferred embodiment, the operator
`interface 124 comprises a display window adapted for
`displaying location information, such as a map including
`street information, landmarks, locations and/or status of
`communication units 105-113 in a particular geographic
`area. An example of such a display is shown at FIG. 2.
`Alternatively or additionally, text messages, graphical icons
`or synthesized voice may be employed to communicate
`location information to the user. In either case, the location
`information
`is adapted for periodic updates
`through
`exchanges of information with the GLSS controller 101.
`[0029] The location determination element 126 comprises
`a location sensor and associated hardware and software for
`
`

`

`US 2003/0100326 Al
`
`May 29,2003
`
`4
`
`determining the location of the communication unit 105.
`Typically, the location determination is performed by an
`in-vehicle navigation unit, utilizing a Global Positioning
`System (GPS) receiver connected to a GPS antenna. The
`navigation unit and the rest of the communication unit 105
`(e.g., mobile dispatch phone) are connected through a serial
`connection. Alternatively, the two devices have wireless
`connection, such as Blue Tooth, that would enable the use of
`the phone outside of the vehicle for other purposes, as well.
`This connection is used for sharing location data between
`the navigation device and the mobile phone. Alternatively or
`additionally, assisted GPS, time-of-arrival, enhanced time(cid:173)
`of-arrival, dead-reckoning sensors or any other suitable
`technology that enables the location determination element
`126 to accurately determine the location of the communi(cid:173)
`cation unit 105 may be used. Examples of commercially
`available brands of in-vehicle navigation units include
`Garmin and Alpine. In any case, the resulting location is
`communicated via the transceiver 116 to the GLSS control(cid:173)
`ler 101 where it may be forwarded to other participating
`subscribers 106-110 and/or infrastructure devices. In addi(cid:173)
`tion, the location information may be used to filter and
`interpret the location information received from other sub(cid:173)
`scribers.
`[0030] FIG. 2 shows an example map display that may be
`provided to a user of a communication unit according to
`principles of the present invention. The map display shows
`three public safety vehicles approaching an incident loca(cid:173)
`tion, as well as the planned routes and estimated time of
`arrival (ETA) of the vehicles. As shown, the current location
`of the vehicles is represented by respective vehicle icons, the
`incident location is depicted by a "dot" in the lower middle
`of the display, the planned routes are depicted by arrows
`leading to the incident location and the ETAs (i.e., 4.1, 6.3
`and 3.2 minutes, respectively) are shown in small windows
`attached to the vehicle icons. Preferably, all of this infor(cid:173)
`mation is updated in real-time (e.g., every 10 seconds or
`less) as the vehicles change their location, ETA, planned or
`actual route, etc. The map display may also be augmented by
`an additional speech interface and/or light and sound effects.
`It is contemplated that such augmented human interface may
`assist in reducing driver distraction, which could be espe(cid:173)
`cially critical if the driver is the only person in the vehicle.
`The additional speech interface, if provided, could be used
`to produce a pre-recorded and/or synthesized voice
`announcement of major changes in the location of any of the
`vehicles and to specify/change the conditions when such
`announcement is required. For example, the announcement
`could be given if and when any of the vehicles pass a major
`intersection, if the distance between vehicle(s) or the dis(cid:173)
`tance between certain vehicle(s) and the incident location
`reaches a certain threshold, if any of the vehicles change
`routes, etc.
`[0031] Now turning to FIG. 3, there is shown a h

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


Or .

Accessing this document will incur an additional charge of $.

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

Accept $ Charge
throbber

Still Working On It

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

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

throbber

A few More Minutes ... Still Working

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

Thank you for your continued patience.

This document could not be displayed.

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

Your account does not support viewing this document.

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

Your account does not support viewing this document.

Set your membership status to view this document.

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

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

Become a Member

One Moment Please

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

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

Your document is on its way!

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

Sealed Document

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

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


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket