throbber
(12) INTERNATIONAL APPLICATION PUBLISHED UNDER THE PATENT COOPERATION TREATY (PCT)
`
`(19) World Intellectual Property Organization
`International Bureau
`
`4 October 2001 (04.10.2001) II|||||l|||||l||IIIIIIIIIIIIIIIIIIIII|||||||I||II|I|IIIIIIIII||||I|II|I|||||I||I
`
`(43) International Publication Date
`
`(10) International Publication Number
`WO 01/74034 A2
`
`
`(51) International Patent Classification7:
`
`H04M
`
`(21) International Application Number:
`
`PCTIUSO 1/041 28
`
`(22) International Filing Date: 8 February 2001 (08.02.2001)
`
`(25) Filing Language:
`
`(26) Publication Language:
`
`English
`
`English
`
`(30) Priority Data:
`09/536,966
`
`28 March 2000 (28.03.2000)
`
`US
`
`(71) Applicant (for all designated States except US): ERICS—
`SON INC. [US/US]; 7001 Development Drive, Research
`Triangle Park, NC 27709 (US).
`
`(72) Inventors; and
`(75) Inventors/Applicants (for US only): DUNKO, Gregory
`[US/US]; 103 Mixedwood Court, Cary, NC 27511 (US).
`LOHR, Jon [US/US]; 5928 Swales Way, Raleigh, NC
`27603 (US). KOLEV, Javor [SE/US]; 111 Murdock
`Creek Court, Apex, NC 27502 (US). JOLLEY, Edward,
`
`V. [US/US]; 5109 Green Oak Drive, Durham, NC 27712
`(US).
`
`(74) Agents: OWEN, John, R. et 211.: Coats & Bennett, PLLC,
`Post Office Box 5, Raleigh, NC 27602 (US).
`
`(81) Designated States (national): AE, AG, AL, AM, AT, AU,
`AZ, BA, BB, BG, BR, BY, BZ, CA, CH, CN, CR, CU, CZ,
`DE, DK, DM, DZ, EE, ES, FI, GB, GD, GE, GH, GM, HR,
`HU, ID, IL, IN, IS, JP, KE, KG, KP, KR, KZ, LC, LK, LR,
`LS, LT, LU, LV, MA, MD, MG, MK, MN, MW, MX, M2,
`NO, NZ, PL, PT, RO, RU, SD, SE, 80, SI, SK, SL, TJ, TM,
`TR, TT, TZ, UA, UG, US, UZ, VN, YU, ZA, ZW.
`
`(84) Designated States (regional): ARIPO patent (GH, GM,
`KE, LS, MW, MZ, SD, SL, SZ, TZ, UG, ZW), Eurasian
`patent (AM, AZ, BY, KG, KZ, MD, RU, TJ, TM), European
`patent (AT, BE, CH, CY, DE, DK, ES, Fl, FR, GB, GR, IE,
`IT, LU, MC, NL, PT, SE, TR), OAPI patent (BF, BJ, CF,
`CG, CI, CM, GA, GN, GW, ML, MR, NE, SN, TD, TG).
`
`Published:
`
`7 without international search report and to be republished
`upon receipt ofthat report
`
`[Continued on next page]
`
`
`(54) Title: ON DEMAND LOCATION FUNCTION FOR MOBILE TERMINAL
`
`100
`
`
`
`CREATE 'NEW"
`LOCATION PLACE-
`
`NAME DESCRIPTION
`
`
` 104
`RUN FUNCTION
`TI-IAT ASSOCIATES
`RUN FUNCTION
`
`
`
`THAI-r Wtfifié‘ém‘
`
`
`DESCRIPTION
`
`(CREATE LOOK-UP
`ENTRY)
`
`
` CONTACT OTHER
`MEMBERS
`
`SHARE
`
`OF AFFINITY GROUP
`LOOKUP?
`
`AND TRANSFER
`INFORMATION
`
`
`
`STOFIE
`
`ASSOCIATION
`
`FILE CABINET:
`(LOOKUP ENTRY)
`IN OWN
`
`
`KEEP TRACK OF
`
`MOBILE
`WHICH MEMBERS
`
`
`TERMINAL
`OF AFFINITY
`
`GROUP HAVE
`
`BEEN UPDATED
`
`
`I|||I|IIIIIIIIll|I||||||l|||||II||||||||||II|||||||||||||||||IIIIIIIIIIIIIIIIIII
`
`01/74034A2
`
`(57) Abstract: A wireless communications system supports affinity groups of like minded individuals who wish to know locations
`of other members of the affinity group. The system supports members of the affinity group querying, through a mobile terminal for
`the location of a remote member of the affinity group as sensed by the remote member’s mobile terminal. Rather than report raw
`0 geocoordinates, location place-name descriptions are defined by the members of the affinity group and shared amongst one another.
`a Additionally, situational alarms may be generated in the event certain user defined criteria are met, such as two remote members of
`the affinity group being in close proximity to one another.
`
`LYFT 1036
`
`LYFT 1036
`
`1
`
`

`

`WO 01/74034 A2
`
`||||ll|||||||||l|||||||||||||||||||||||||||||||||||||||||Illllllllllillllillllll
`
`For two-letter codes and other abbreviations, refer to the "Guid-
`ance Notes on Codes andAbbreviations " appearing at the begin—
`ning ofeach regular issue ofthe PCT Gazette.
`
`2
`
`

`

`WO 01/74034
`
`PCT/USOI/04128
`
`ON DEMAND LOCATION FUNCTION FOR MOBILE TERMINAL
`
`BACKGROUND OF THE INVENTION
`
`The present invention is directed to a mobile terminal, such as a cellular
`
`phone, equipped with affinity group messaging, and more particularly to a mobile
`
`terminal equipped with the ability to locate members of the affinity group on
`
`demand.
`
`One reason for the popularity of portable, wireless communication devices,
`
`such as cellular phones, is that they free people from tethers to fixed
`
`communication networks. A user can roam freely in the network, yet remain in
`
`1O
`
`touch with others. Thus, mobile communication devices provide a means by
`
`which people can remain in contact with whomever they want, wherever they
`
`happen to be. This is especially true among groups of individuals who share a
`
`common interest or affiliation (e.g., families, co-workers, those who share a
`
`common avocation or interest, such as tennis or music, and members of a club).
`
`15
`
`Such groups shall be referred to herein as an affinity group.
`
`Several existing technologies facilitate interaction among the members of
`
`an affinity group: Internet “chat rooms,” electronic mail (e-mail), advanced
`
`personal information management (PIM) applications such as Microsoft®
`
`Outlook“, paging services, and advanced messaging services employing contact
`
`20
`
`servers. Some Internet chat software, for example, AOL® Instant MessengerT“,
`
`ICQ, or other similar programs, informs members of an affinity group which other
`
`members of the group are currently logged into the sewer.
`
`All these technologies support, to some degree, the desire of members of
`
`an affinity group to stay in close contact. The Internet chat room approach of
`
`1
`
`3
`
`

`

`WO 01/74034
`
`PCT/USOl/04128
`
`informing the user which affinity group members are on-line is particularly useful.
`
`However, this approach has limitations, the most serious of which is that the user
`
`must be logged onto the Internet and in contact with a particular server to receive
`
`information on the status of the other group members. For example, suppose a
`
`first group member would like to chat with a second group member. The first
`
`group member has no way of knowing whether the second group member is
`
`logged onto the chat server without first logging onto the server supporting the
`
`affinity group. This typically requires connection through a personal computer
`
`over a wire-based phone line. Even in situations where wireless modems are
`
`10
`
`used, the majority of the members of the affinity group are tied to terrestrial phone
`
`lines.
`
`The assignee of the present invention has heretofore developed a system
`
`and method associated with a wireless communication network, described in
`
`application serial number 09/514,657, entitled METHOD FOR FACILITATING
`
`15
`
`ELECTRONIC COMMUNICATION, filed 29 February 2000 by Anders Waesterlid,
`
`which is hereby incorporated by reference, that supports wirelessly networked
`
`affinity groups. While that invention provides wireless affinity groups, along with
`
`some location information about the relative whereabouts of members of the
`
`affinity group, that invention still leaves unsatisfied customer demands.
`
`It is also
`
`20
`
`desired that consumers of the affinity group service be able to query for the
`
`location of other members in the affinity group in the event that the member has
`
`not provided a timely update of his or her location. Further, there is a need for
`
`situational alarms that may be generated based on the proximity of other
`
`4
`
`

`

`WO 01/74034
`
`PCT/US0l/04128
`
`members of the affinity group, the sensed location of a specific member of the
`
`affinity group, or other user defined situations as needed or desired.
`
`SUMMARY OF THE INVENTION
`
`The shortcomings of the prior art are addressed by providing a mobile
`
`terminal having software stored in local memory to enable additional functionality
`
`within an affinity group.
`
`In one embodiment, the software is adapted to function
`
`with a location detector, such as a Global Positioning System (GPS) receiver, and
`
`to extract therefrom data relating to the present location of the mobile terminal.
`
`1O
`
`When a first member in the affinity group wishes to know the location of a remote
`
`member of the affinity group, the first member instructs his or her mobile terminal
`
`to inquire as to the present location of the remote member. Through a Short
`
`Message Service or other comparable messaging technology, an inquiry is sent to
`
`the remote member’s mobile terminal.
`
`15
`
`In a first aspect of the invention, members of the affinity group are able to
`
`create location place-name descriptions such that commonly visited places have a
`
`name or common appellation attached thereto. When the location detector
`
`senses that the mobile terminal is within a predefined distance of a location
`
`associated with a location place-name description, the mobile terminal assumes
`
`20
`
`that the member is within the confines of that location. Thus, when an inquiry is
`
`made as to the location of a remote member, the inquiring member may be
`
`informed with the location place-name description rather than a set of raw
`
`geocoordinates such as are returned by a GPS receiver. This facilitates
`
`comprehension by the inquiring member as to the actual location of the remote
`
`5
`
`

`

`WO 01/74034
`
`PCT/USOl/04128
`
`member, whereas longitude and latitude measurements corresponding to the raw
`
`geocoordinates would perhaps not be particularly insightful.
`
`Location place-name descriptions may be shared amongst members of the
`
`affinity group or maintained privately by the original member who created the
`
`location place-name description. Further, if a member of the affinity group is not
`
`within a predefined location having a location place—name description, a last
`
`known location, a vector referencing a known location having a location place-
`
`name description. or other indicia of present location may be provided to the
`
`inquiring member. While not as useful as the location place—name descriptions,
`
`10
`
`these alternative location indicia may help inform the requesting member of the
`
`present location or the destination of the remote member whose location is
`
`sought
`
`In a second aspect of the invention, members of the affinity group may
`
`program the mobile terminal to generate situational alarms. Such situational
`
`15
`
`alarms may enable members of the affinity group to know when other members of
`
`the affinity group have reached a certain location, such as the mall. or when
`
`members of the affinity group are approaching. Once the predefined condition is
`
`met, the inquiring or programming member is alerted through an audible signal, a
`
`mechanical signal such as a vibration, or other appropriate means. Having been
`
`20
`
`alerted to the existence of the predefined condition, the programming member
`
`may then take appropriate action as originally contemplated when the situational
`
`alarm was programmed.
`
`6
`
`

`

`WO 01/74034
`
`PCT/USOl/04128
`
`BRIEF DESCRIPTION OF THE DRAWINGS
`
`Fig. 1 is schematic diagram of a wireless communications system;
`
`Fig. 2 is a schematic diagram of a mobile terminal;
`
`Fig. 3 is a flow chart of the methodology for creating and sharing translation
`
`tags for use in the present invention;
`
`Fig. 4 is a flow chart of the methodology behind a first aspect of the
`
`invenfion;and
`
`Fig. 5 is a flow chart of the methodology behind a second aspect of the
`
`10
`
`invention.
`
`DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
`
`The present invention preferably implements additional functionality in a
`
`mobile terminal. Specifically, members of affinity groups may now have a device
`
`15
`
`and technique for determining the location of other members of the affinity group.
`
`Likewise, members of the affinity group may be alerted when certain user-defined
`
`events occur. While particularly well suited for cellular phones, other mobile
`
`terminals such as pagers, personal digital assistants, or the like may also be
`
`adapted for use with the present invention. Regardless of the particular device
`
`20
`
`used with the present invention, a review of the elements of a wireless
`
`communications system and a mobile terminal will be helpful. A typical wireless
`
`communication system could be a system that complies with TIA/EIA-136, the
`
`GSM standard, or other well-defined standards. This list is provided as an
`
`example and is not intended to be a limiting example.
`
`5
`
`7
`
`

`

`WO 01/74034
`
`PCT/USOl/04128
`
`Turning now to the drawings, and particularly to Fig. 1, a wireless
`
`communications system 10 is shown in simplified form. Wireless communications
`
`system 10 includes a Mobile Services Switching Center (MSC) 12, a Visitor
`
`Location Register (VLR) 14, a Home Location Register (HLR) 16, a base station
`
`18, and a plurality of mobile terminals 20 wielded by consumers who may or may
`
`not be members of an affinity group.
`
`It should be appreciated that the wireless
`
`communications system 10 may comprise a plurality of cells (only one shown).
`
`Each cell is served by a base station, such as the base station 18 that provides
`
`wireless coverage to the mobile terminals 20 within that particular cell. Base
`
`1O
`
`station 18 is communicatively connected to the M80 12. Typically, the wireless
`
`communications network 10 includes many MSCs 12. At least one MSC 12 is
`
`typically connected via a gateway to the Public Switched Telephone Network
`
`(PSTN, not shown). Some MSCs 12 also serve as gateways connecting the
`
`network 10 with other wireless networks. The function of the MSCs 12 is to route
`
`15
`
`calls and signals in the network 10 to the appropriate destination. For example,
`
`the M80 12 is responsible for connecting calls to the appropriate base station 18
`
`or to the PSTN or other connected network via a gateway.
`
`To perform its call routing function, the M80 12 must know the location of
`the mobile terminals 20 in the Public Land Mobile Network (PLMN) so that calls
`
`20
`
`can be fonNarded to the appropriate base station 18.
`
`Information concerning the
`
`general whereabouts of each mobile terminal 20 is stored in databases that are
`
`centrally located in the network 10. Each service provider will typically maintain its
`
`own database containing subscriber information which is shared with other
`
`networks in the PLMN. These databases include the HLR 16 and the VLR 14.
`
`8
`
`

`

`WO 01/74034
`
`PCT/USOI/04128
`
`HLR 16 is used to store information concerning subscribers to a cellular
`
`network. This information typically includes the user‘s name and address for
`
`billing purposes, the serial number of the user’s mobile terminal 20, and the
`
`services to which the user is entitled to receive.
`
`In addition, the current general
`
`location in the form of a current network ID of the subscriber is stored in the HLR
`
`16 for retrieval by an M80 12 to use in routing calls to the subscriber.
`
`It should be
`
`appreciated that the general location stored in the HLR 16 is limited to
`
`approximate geographic region or cell, and is not specific enough to identify street
`
`addresses or the like. Mobile terminal 20 registers with the servicing M80 12
`
`10
`
`when it is powered on and at periodic intervals so that the servicing M80 12 can
`
`keep track of the location of the mobile terminal 20. The mobile terminal 20 also
`
`registers when it travels between two different service areas (areas served by
`
`different MSCs 12). As part of this registration procedure, the mobile terminal 20
`
`transmits its Mobile Identification Number (MIN) to the MSC 12. M80 12 uses the
`
`15
`
`MIN to determine which HLR 16 to access. When the mobile terminal 20 registers
`
`with MSC 12, the servicing M80 12 updates the HLR 16 with the current location
`
`of the mobile terminal 20. When an M80 12 receives a call addressed to a
`
`subscriber that is not currently in that MSC's service area, the MSC 12 will query
`
`the HLR 16 for the subscriber’s location so that the call can be fonlvarded to the
`
`20
`
`MSC 12 currently servicing the subscriber.
`
`VLR 14 is used to store information about users that are not in their home
`
`service area. When subscribers roam outside of their home service area, the VLR
`
`14 in the area being visited must keep track of the subscriber's location and be
`
`able to verify the Mobile Identification Number (MIN) of the mobile terminal 20.
`
`7
`
`9
`
`

`

`WO 01/74034
`
`PCT/USOl/04128
`
`VLR 14 in the area being visited queries the HLR 16 in the subscriber’s home
`
`service area to authenticate the subscriber and determine the services to which
`
`the subscriber is entitled.
`
`Information concerning the user is stored in the VLR 14
`
`as long as the subscriber remains in the service area. VLR 14 also stores the
`
`current general location of the subscriber. The subscriber’s current location is
`
`also communicated back to the home HLR 16 so that the home network 10 will
`
`know how to forward calls addressed to the subscriber who is currently outside of
`
`the home network 10.
`
`Many wireless communications networks 10 implement a service called
`
`10
`
`short message service (SMS). This service allows mobile users to send and
`
`receive short text messages. Messages originating from, or terminating at, a
`
`mobile terminal 20 in the network 10 are stored in a message center 13 connected
`
`to an M80 12. Message center 13 is a store-and-fowvard device or system that is
`
`used to support teleservices like cellular messaging. The typical interfaces to the
`
`15
`
`message center 13 allow direct dial-in access, computer interface for e-mail
`
`delivery to phones, or human operator input for paging services. Mobile-
`
`originated SMS messages are initially forwarded to the M80 12 servicing the
`
`addressed mobile terminal 20 and routed by the M80 12 to the message service
`
`center 13 where the SMS message is stored. M50 12 searches for the targeted
`
`20
`
`mobile terminal 20 and alerts the mobile terminal 20 that a message is coming.
`
`Targeted mobile terminal 20 tunes to a designated messaging channel (typically
`
`an SDCCH channel) where it waits forthe SMS message. M80 12 then forwards
`
`the SMS message to the mobile terminal 20 on the designated channel and waits
`
`for an acknowledgement from the mobile terminal 20 confirming receipt of the
`
`10
`
`10
`
`

`

`WO 01/74034
`
`PCT/USOIIO4128
`
`message.
`
`If an acknowledgement is received from the mobile terminal 20, the
`
`message is removed from storage.
`
`If receipt of the message is not
`
`acknowledged, the M30 12 may attempt to deliver the message again.
`
`It is
`
`disclosed in the previously incorporated application entitled METHOD FOR
`
`5
`
`FACILITATING ELECTRONIC COMMUNICATION that the message center 13 or
`
`other server may act in a supporting role for the affinity groups of the present
`
`invention.
`
`Additionally, some networks 10, and especially networks that are adapted
`
`to support the present invention, may include a Mobile Positioning Center (MPG)
`
`10
`
`that serves as the point of interface of the wireless network 10 for the exchange of
`
`geographic position information. An MP0 may control multiple Position
`
`Determining Entities (PDEs). A PDE is the network entity that manages the
`
`position or geographic location determination of the mobile terminal 20. For
`
`further information about such entities, reference is made to Enhanced Wireless
`
`15
`
`9—1-1 Phase 2, TR-45.2, AHES (PM-3890, Rev. 11, 13 Jan 2000). This published
`
`standard is well understood by those in the industry and is incorporated by
`
`reference.
`
`Turning now to Fig. 2, the mobile terminal 20 typically includes a controller
`
`22, an operator interface 26, a transmitter 38, a receiver 50, and an antenna
`
`20
`
`assembly 58. The operator interface 26 typically includes a display 28, keypad
`
`30, interface control 32, microphone 34, and a speaker 36. The display 28 allows
`
`the operator to see dialed digits, call status, and other service information. The
`
`keypad 30 allows the operator to dial numbers, enter commands, and select
`
`options.
`
`Interface control 32 interfaces the display 28 and keypad 30 with the
`
`9
`
`11
`
`11
`
`

`

`WO 01/74034
`
`PCT/USOl/04128
`
`controller 22. The microphone 34 receives acoustic signals from the user and
`
`converts the acoustic signals to an analog electrical signal. The speaker 36
`
`converts analog electrical signals from the receiver 50 to acoustic signals which
`
`can be heard by the user.
`
`The analog electrical signal from the microphone 34 is supplied to the
`
`transmitter 38. The transmitter 38 includes an analog to digital converter 40, a
`
`digital signal processor 42, and a phase modulator and RF amplifier 48. The
`
`analog to digital converter 40 changes the analog electrical signal from the
`
`microphone 34 into a digital signal. The digital signal is passed to the digital
`
`1O
`
`signal processor (DSP) 42, which contains a speech coder 44 and channel coder
`
`46. The speech coder 44 compresses the digital signal and the channel coder 46
`
`inserts errordetection, error correction and signaling information. The DSP 42
`
`may include, or may work in conjunction with, a DTMF tone generator (not
`
`shown). The compressed and encoded signal from the digital signal processor 42
`
`15
`
`is passed to the phase modulator and RF amplifier 48, which are shown as a
`
`combined unit in Figure 2. The modulator converts the signal to a form which is
`
`suitable for transmission on an RF carrier. The RF amplifier 48 then boosts the
`
`output of the modulator for transmission via the antenna assembly 58.
`The receiver 50 includes a receiver/amplifier 52, digital signal processor 54,
`
`20
`
`and a digital to analog converter 56. Signals received by the antenna assembly
`
`58 are passed to the receiver/amplifier 52, which shifts the frequency spectrum,
`
`and boosts the low—level RF signal to a level appropriate for input to the digital
`
`signal processor 54.
`
`10
`
`12
`
`12
`
`

`

`WO 01/74034
`
`PCT/USOl/04128
`
`The digital signal processor 54 typically includes an equalizer to
`
`compensate for phase and amplitude distortions in the channel corrupted signal, a
`
`demodulator for extracting bit sequences from the received signal, and a detector
`
`for determining transmitted bits based on the extracted sequences. A channel
`
`decoder detects and corrects channel errors in the received signal. The channel
`
`decoder also includes logic for separating control and signaling data from speech
`
`data. Control and signaling data are passed to the controller 22. Speech data is
`
`processed by a speech decoder and passed to the digital to analog converter 56.
`
`The digital signal processor 54, may include, or may work in conjunction with, a
`
`1O
`
`DTMF tone detector (not shown).
`
`The digital to analog converter 56 converts the speech data into an analog signal
`
`which is applied to the speaker 36 to generate acoustic signals which can be
`
`heard by the user.
`
`The antenna assembly 58 is connected to the RF amplifier of the
`
`15
`
`transmitter 38 and to the receiver/amplifier 52 of the receiver 50. The antenna
`
`assembly 58 typically includes a duplexer 60 and an antenna 62. The duplexer 60
`
`permits full duplex communications over the antenna 62.
`
`The controller 22 coordinates the operation of the transmitter 38 and the
`
`receiver 50, and may for instance take the form of a typical microprocessor. This
`
`20
`
`microprocessor may be a dedicated or shared microprocessor and may be a
`
`single processor or multiple parallel processors as needed or desired. This
`
`coordination includes power control, channel selection, timing, as well as a host of
`
`other functions known in the art. The controller 22 inserts signaling messages into
`
`the transmitted signals and extracts signaling messages from the received
`
`11
`
`13
`
`13
`
`

`

`WO 01/74034
`
`PCT/US01/04128
`
`signals. The controller 22 responds to any base station commands contained in
`
`the signaling messages, and implements those commands. When the user enters
`
`commands via the keypad 30, the commands are transferred to the controller 22
`
`for action. Memory 24 stores and supplies information at the direction of the
`
`controller 22 and preferably includes both volatile and non-volatile portions.
`
`in addition to the above described elements, the mobile terminal 20
`
`preferably also includes a location detector 64 in communication with the
`
`controller 22. Location detector 64 may have its own antenna (not shown) or may
`
`share the antenna 62. Location detector 64 may be Global Positioning System
`
`1O
`
`(GPS), an Observed Time Difference system (OTD - where the mobile terminal 20
`
`computes position using observed timing of bursts from multiple base stations 18),
`
`a Time of Arrival system (TOA — where the network 10 computes position using
`
`mobile terminal bursts observed by multiple base stations 18), or other satellite or
`
`terrestrial systems as needed or desired, e.g. inertial systems. Typically, the
`
`15
`
`location detector 64 will output a geocoordinate expressed as a longitude and
`
`latitude coordinates corresponding to the present location of the mobile terminal
`
`20.
`
`In the event that the location detector 64 is not able to provide a sensed
`
`geocoordinate through its normal position determining network, it is possible that
`
`20
`
`the network 10 may provide to the mobile terminal 20 and particularly to the
`
`location detector 64, at least a cell location within the network. Further, with the
`
`use of a technique called “timing advance,” a radius from a particular base station
`
`18 may be determined. Thus, if the location detector 64 was not operational, the
`
`network 10 could at least provide some location information about the location of
`
`12
`
`14
`
`14
`
`

`

`WO 01/74034
`
`PCT/USOl/04128
`
`the mobile terminal 20, such as within two miles of the base station 18 at
`
`Broadway and Main Streets. While not as helpful as the location place-name
`
`descriptions of the present invention, this information may still be helpful to
`
`members of the affinity group.
`
`The present invention may be implemented through software stored in
`
`memory 24 or specific hardware components may be implemented within
`
`controller 22 to perform the functions discussed below.
`
`The application entitled METHOD FOR FACILITATING ELECTRONIC
`
`COMMUNICATION defines affinity groups and provides a number of different
`
`10
`
`embodiments of how an affinity group may function. Specifically, affinity groups
`
`may share information using a sewer based approach, or a peer-to-peer
`
`approach. Members receive updated information automatically when they turn on
`
`their mobile terminals 20, or periodically as part of a camping routine.
`
`In
`
`particular, when a user provides an update to their reported location, the server
`
`15
`
`may distribute the information, or the updating user’s mobile terminal 20 may
`
`contact each other active member of the affinity group. One key shortcoming of
`
`the prior invention was the fact that users may not provide timely updates about
`
`their location, or users may provide erroneous location information through
`
`carelessness or intention. This reliance on fallible human remembrance to update
`
`20
`
`location information prevents exploring some aspects of the utility of wireless
`
`based affinity groups. Further, in that invention, there is no provision for queries
`
`or independent verification of the current location of a remote affinity group
`
`member.
`
`13
`
`15
`
`15
`
`

`

`WO 01/74034
`
`PCT/USOl/04128
`
`While the application entitled METHOD FOR FACILITATING
`
`ELECTRONIC COMMUNICATION contemplates Short Message Service (SMS)
`
`as the preferred technique by which members of an affinity group could
`
`communicate, there are other techniques that may be equally applicable including
`
`data messages, GPRS (GSM Packet Radio Service), e-mails, USSD, and the like.
`
`In certain geographically proximate locations, Bluetooth (a short range terminal to
`
`terminal communication technique) or other comparable technologies may be
`
`used. Regardless of the technique used to communicate amongst members of
`
`the affinity group, there remain functions that are not addressed in the Waesterlid
`
`10
`
`application.
`
`Commonly owned patent application serial number 09/097,941, entitled
`
`IMPROVED METHOD AND APPARATUS FOR LOCATING A WIRELESS
`
`COMMUNICATION DEVICE, which is hereby incorporated by reference, provides
`
`a technique by which a mobile terminal 20 may be combined with a location
`
`15
`
`detector 64 and further programmed to recognize certain default locations.
`
`Specifically, that application contemplates a user defining a home or other default
`
`location by its geocoordinates and, when the location detector 64 returns sensed
`
`geocoordinates within a predetermined distance of these predefined
`geocoordinates, the mobile terminal 20 reports that the mobile terminal 20 is at
`
`20
`
`the default location. This simplifies location reporting to the extent that an address
`
`or common appellation is reported rather than merely a latitude and longitude.
`
`This technique may be used and expanded upon in the present invention.
`
`Alternative techniques to link a common descriptor or address to sensed
`
`geocoordinates may also be used if needed or desired. Words or phrases to
`
`14
`
`16
`
`16
`
`

`

`WO 01/74034
`
`PCT/U801/04128
`
`describe such predefined locations will be defined herein as “location place-name
`
`descriptions.” Additionally, some mobile terminals have the ability to transfer
`
`images or video clips. Thus, location place-name description is also defined
`
`herein to include such images, such videos, or even a short audio phrase that
`
`may describe the location.
`
`Additionally, there need not be a specific point that is associated with a
`
`location place-name description, but rather a polygon of a predetermined number
`
`of points could define a location having a location place-name description. For
`
`example, the four corners of the mall may define such a polygon. Then if the
`
`1O
`
`sensed geocoordinates of the mobile terminal 20 were within the defined polygon,
`
`or within a predetermined distance from an edge of the polygon, then the mobile
`
`terminal 20 would be reported as being located within the polygon and thus within
`
`the designated location. These polygons may be regular or nonuniform as
`
`needed or desired.
`
`15
`
`Still further, there members of the affinity group need not define all the
`
`location place-name descriptions used by the affinity group. Rather, it is possible
`
`that the service provider could provide a set of predefined locations having
`
`location place-name descriptions. Thus, the service provider could predefine the
`
`mall, the park, and the university library for example, and let the members of the
`
`20
`
`affinity group define other desired locations.
`
`The process of assessing location may be continuous or may be accessed
`
`at discrete instances based on user requests as detailed more fully below.
`
`It is
`
`imagined that there will be many places for which there are no location place-
`
`name descriptions.
`
`In these instances, the location detector 64 may generate raw
`
`‘15
`
`17
`
`17
`
`

`

`WO 01/74034
`
`PCT/USOl/04128
`
`sensed geocoordinates, or the mobile terminal 20 may store the last known
`
`location place—name description. Alternatively, vectors indicating travel direction
`
`and velocity may be generated that could be linked to the last known location
`
`place-name description. For example, “left home six minutes ago, heading SW at
`
`35 mph" could be a valid reported location. Alternatively, just a vector to a known
`
`location place-name description could be provided such as “3 km southeast of the
`
`mall." These vectors referencing known location place-name descriptions are
`
`helpful in providing some user friendly information about the whereabouts of
`
`members of the affinity group. Further, even when the location detector 64 was
`
`10
`
`not operational, the network 10 could provide cell location or some other rough
`
`positional estimate.
`
`To maximize the utility of the present invention, the location place—name
`
`descriptions should be shared amongst the affinity group such that other members
`of the affinity group may recognize when members are within one of the
`
`15'
`
`predefined locations. An exemplary technique to share such location place-name
`
`descriptions is shown in Figure 3, wherein an individual user triggers a command
`
`on the mobile terminal 20 that creates a new location place-name description
`
`(block 100). This may be done through manual entry through the keypad 30,
`
`voice activation through the microphone 34, uploading from a personal computer
`
`20
`
`(not shown) communicatively connected to the mobile terminal 20, or other
`
`technique as needed or desired. Mobile terminal 20 runs a function that
`
`determines the geocoordinates of the mobile terminal 20 corresponding to the
`
`location place-name description (block 102). This may be done through
`
`positioning the mobile terminal 20 at the desired location prior to running the
`
`16
`
`18
`
`18
`
`

`

`WO 01/74034
`
`PCT/USOl/04128
`
`routine, through manual entry of geocoordinates corresponding to the location to
`
`be defined, or the like. The geocoordinates are then associated with the location
`
`place-name description (block 104). This may be done with a look up table or the
`
`like as needed or desired. The user may then be prompted to share the location
`
`place-name description (block 106).
`
`If the user chooses to share t

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