Presence of position base and privacy management

[Cross-reference to related applications] This application claims priority to US Patent Application No. 11 / 838,876 entitled "LOCATION BASED PRESENCE AND PRIVACEY MANAGEMENT" filed on August 14, 2007, with reference to this document. I will use it for you.

Location-based services (LBS) have been on the roadmap for wireless carrier products for several years, but their primary use is limited, and their infrastructure and systems are also emergency services (E). It is arranged to satisfy the instruction for -911).

With the advancement of Global Positioning System (GPS) technology for mobile devices, the accuracy of mobile positioning systems has also improved dramatically, and consumer LBS applications (eg, real-time navigation using mobile devices) are now now available. It is available on certain mobile devices offered by several carriers. However, both carriers and consumers are concerned about consumer privacy and liability issues in delivering and enabling such applications.

Most of the mobile phones sold today are made possible by chips, which allows the exact location of the user to be determined. Users can turn off the location tracking feature of their mobile devices for all location-based applications (except E-911 services), but this allows them to use any location services. I can't do it.

For location-based existence, messaging and mobile social networking applications, users must share their location coordinates, but due to privacy concerns, many users do not have access to such services. Some of these location-based applications provide the ability to share location coordinates between users or groups of users and / or limit the sharing of location information to the city or zip code level. However, in order to convey location information that is accurate and relevant to the presence of the subscriber at a particular location (eg, the subscriber's home or work or place of business or important point), the subscriber may have its own location coordinates or Address information must be shared with other users and / or applications.

In addition, the process of updating the status of other users in a mobile instant messaging environment presents additional challenges compared to a desktop instant messaging environment. In particular, current mobile instant messaging applications have limited battery, memory, processing, and screen sizes that drain the mobile device's battery during the process of sending real-time updates of presence information for the entire friends list. ..

Also, some mobile location-based and social networking applications require a mapping interface to display the location of mobile users. Delivering mapping information over a mobile network requires additional cost and complexity due to the bandwidth constraints of the mobile network and the memory, processing power, and battery limits of the mobile device, resulting in Adoption of such applications will be narrowed.

0008In most cases, what users really want is to share locational contextual information about their presence in a particular location (eg, home, office, school) where they spend most of their time, and what they need. It is the ability to selectively share the user's own position coordinates with other users when doing so or when the need arises. The present invention provides the user with the option of sharing location contextual information related to a user-specified location by using generic or user-specified location names, graphical indicators and / or location category information, as well as instant messaging. Provides other users of the application with a location-based existence state without sharing the user's location coordinates or address information.

0009In other cases, where the user is at a place of business or an important point (eg, a restaurant, library, golf course), the present invention allows the mobile user to use the location (eg, restaurant, library, golf course) without sharing the position coordinates with other users. For example, based on the category of restaurant, golf course, library) and, if necessary, the establishment or POI name can indicate its presence.

0010In other cases, when the user is driving, the present invention indicates that the mobile user is in a driving state and is not in his or her normal location (eg, home or work). And location contextual information based on geographic area or neighborhood of user-specified location without sharing its location coordinates and providing location tracking capabilities to other users. Can be provided.

0011Due to such locational contextual information and location-based presence, in most cases the calling party or message sending party is significantly concerned about privacy and liability related to tracking the user's location coordinates. While mitigating, it is possible to recognize the contact status of the user and share all contacts widely.

0012Another embodiment of the invention groups user and / or location privacy options into multiple numerically or descriptively labeled location privacy or location sharing levels, one of which is said. Based on the shared position context state at the exact location, the shared position context state is a general or user-specified position name, position state indicator, or position category information without the user's shared position coordinates or address information. Is used.

0013Another aspect of the invention allows for an efficient and optimal way to update location-based presence with a large number of contacts in mobile and instant messaging environments. Other features of the present invention will become clear from the above description and the scope of the drawings.

The above aspects of the invention will be understood more deeply with reference to the following description, along with the accompanying drawings.<figref num="1">FIG. 6 is a block diagram of an exemplary communication system that provides an appropriate operating environment for the present invention.</figref><figref num="2a">Positional contextual information is exemplarily classified into multiple numerically and descriptively labeled position sharing levels.</figref><figref num="2b">An exemplary table for associating a positional contextual name type with the corresponding sharing level.</figref><figref num="3">FIG. 3 is an exemplary flowchart for updating the user with the position-based existence state corresponding to the level at a plurality of position sharing levels each time the position of the user changes.</figref><figref num="4">FIG. 4 is an exemplary flow chart for updating the user position status table depending on whether the user is at or near a position designated by himself / herself, is in operation, or is at a business establishment or POI position.</figref><figref num="5a">FIG. 5a is an exemplary table for storing a user-designated position and a corresponding criterion for sharing position contextual information when the user is in that position.</figref><figref num="5b">FIG. 5b is an exemplary table for storing the user's favorite establishments and POI locations and the corresponding criteria for sharing location contextual information.</figref><figref num="6">FIG. 6 is an exemplary table for storing the user's position-based existence state corresponding to each position sharing level.</figref><figref num="7">FIG. 7 is an exemplary user interface for specifying location contextual information corresponding to multiple location sharing levels.</figref><figref num="8">FIG. 8 is an exemplary flowchart for determining a user's favorite messaging options corresponding to a user-specified position.</figref><figref num="9">FIG. 9 is an exemplary flow chart for determining a user's favorite messaging options corresponding to a particular location category.</figref><figref num="10">FIG. 10 is an exemplary flowchart for determining a location state when there are multiple establishments or POI options or establishments or POI options at the same location at or near the user's current location.</figref>

FIG. 1 and the following description provide a general description of a communication system 100 suitable for implementing the various features of the present invention. An exemplary communication system for carrying out the present invention with reference to FIG. 1 includes a mobile carrier network 110. The mobile carrier network 110 provides voice, messaging and / or data services to the mobile phones 120a and 120b and is an instant messaging (IM) network (eg, public IM network 130 and public IM client 132, or corporate IM network 140). And can communicate with corporate IM client 142). The mobile carrier network 110 is also capable of delivering voice and / or data services to a communication device (eg, telephone 152), another telephone or data network 150 (eg, public switched telephone network (PSTN)) or voice over internet. It is also possible to communicate via a protocol (VoIP) network). The communication system may include a fixed mobile or broadband mobile network 160 (eg, WiMax network) capable of delivering voice and data services through a communication device (eg, mobile data card 162).

Specifically, communication system 100 can detect or receive geolocation information of a user's mobile phone or other associated terminal or device. In one impression, the mobile carrier network 110 includes a mobile positioning system 112. The mobile positioning system 112 can determine the position coordinates of the mobile phones 120a and 120b. The mobile positioning system 112 may receive position coordinates from a Global Positioning System (GPS) receiver embedded in the mobile phone 120a or 120b, and in another impression, the mobile phone 120a or 120b may have a mobile positioning method (eg, for example). Assists in determining the position using one or more of the assisted type (A-GPS), arrival time difference (TDOA), or other approach) that provides the position coordinates within the specified accuracy constraint. To do. In one impression, the mobile positioning system 112 includes a location server. This location server can be a gateway mobile location center (GML) in the case of a GSM® network, or a mobile positioning center (MPC) in the case of a CDMA network, so that the user's location information is , Provided to third-party location application servers that implement location services and applications.

The mobile carrier network 110 also includes a mobile messaging system 114. Mobile messaging system 114 can transmit text or data messages (including, for example, audio or video messages) from and to mobile phones 120a or 120b, mobile data messaging services and protocols (which may include audio or video messages). For example, short messaging services (SMS), multimedia messaging services (MMS), wireless application protocols (WAP) or other Internet protocols used in 3rd generation (3G) mobile standards (eg, Session Initiation Protocol (SIP)). (IP) -based data and application layer protocols) can be used. The mobile carrier network 110 is a basic RF transport protocol (eg, General Packet Radio Service (GPRS), GSM® Evolved High Speed Data Rate (EDGE), Broadband Code Division Multiple Access (WCDMA®)). , CDMA20001x-RTT, CDMA1x-EV-DO, or 3G or 4G mobile standard).

Mobile phones 120a and 120b are exemplary mobile devices used by two different mobile subscribers. These mobile subscribers may be on the same mobile carrier network or may be part of a different mobile carrier network. The mobile phone 120a or 120b is an address book 122a or 122b, a location client application 124a or 124b, one or more mobile messaging applications 126a or 126b, which are text messaging applications, multimedia messaging applications, email applications, and / or. Includes (which may include instant messaging applications).

The public IM network 130 can include instant messaging (IM) services (eg, those provided by MSN, AOL, Yahoo or Google) and is based on proprietary impressions or industry standards (eg,). , Session Initiation Protocol (SIP) or Extended Messaging and Existence Protocol (XMPP)). The public IM client 132 can be a desktop or mobile IM client that subscribes to the public IM network 130.

The corporate IM network 140 includes an instant messaging service. Instant messaging services are provided by companies and large corporations to their corporate users to control and manage access to instant messaging services. The corporate IM client 142 can be a desktop or mobile IM client that subscribes to the corporate IM network 140.

FIG. 2a shows exemplary impressions in grouping various types of location contextual information into multiple numerically and descriptively labeled location sharing levels. Further, one of the sharing levels makes it possible to share the position contextual name of the user-designated position without the user's sharing position coordinates. In one impression, the present invention allows the mobile user to select location sharing options and select or specify descriptive names for location sharing levels 0-3 as shown in Table 210. As shown in Table 210, positional contextual information options at a particular sharing level are added to the options available at the preceding sharing level. As shown in field 212, there is no shared location information at level 0. As shown in field 214, at level 1, only city and state level information is shared by default with the option to select a zip code or region level name. As shown in field 216, at level 2, if the user is at or near a geographic location specified by him / her, the location contextual information corresponding to these exact locations is shared, in which case the user's streets. No address or location coordinates are provided. To give examples of location contextual information, the names, categories and representative graphical indicators of user-specified locations and user-specified establishments or POI locations, and optionally other undesignated establishments or POI locations ( For example, there are categories (home, office, workplace, school, restaurant, golf course, library). If the user is in an unspecified establishment or POI location, the user may also specify options to include the establishment or POI name. As shown in field 218, at level 3, all relevant location information between selected users at this level (eg, street name, nearest intersection, establishment and POI name and / or specified by said user. Such categories) can be shared. This

FIG. 2b is an exemplary table for associating positional contextual name types with corresponding sharing levels. As shown in Table 220, default settings for location name types and corresponding sharing levels are specified along with configuration options for sharing levels that may be specified by the user. As shown in field 221 the city and state based location names can be shared between users at sharing level 1 and above. As shown in field 222, if the user is at or near a location specified by him / her, the location contextual information based on the location name and category of these locations is the location coordinates of the current location of the mobile subscriber or It can be shared among users of sharing level 2 or higher without providing street address information. As shown in field 223, the user-designated POI name also includes the user-designated business establishment name and can be shared at level 2 and above. As shown in the configuration options, the user may change the minimum sharing level of this location name type to level 3. As shown in field 224, if it is determined that the mobile subscriber is in a business establishment or POI location, the establishment or POI category information can be shared between Level 2 or higher users. The mobile subscriber may change the minimum sharing level for this location name type to level 3. Further, as shown in fields 225 and 226, in the case of sharing with a level 3 user, the location contextual information may also include the street name of the user's current location and the nearest intersection. The mobile subscriber may change the sharing level of this location name type to sharing level 2 or higher. As shown in field 227, if it is determined that the user is in the location of the establishment or POI, the establishment or POI name corresponding to the user's current location can also be shared between users at sharing level 3. .. The mobile subscriber may change the sharing level of this location name type to sharing level 2 or higher.

FIG. 3 shows an exemplary flow diagram 300 for updating users at multiple location sharing levels with location-based presence or status information corresponding to the level each time the location of the mobile subscriber changes. .. Starting from block 302, the position application server that stores and shares the position contextual information of the mobile phone 124a or 124b requests the position coordinates and accuracy information from the mobile positioning system 112. The mobile positioning system 112 may provide the latest location information for the mobile device from its own database or cache, or may request current location information from the corresponding mobile phone 120a or 120b. In the determination block 304, a test is performed to determine whether the current position of the mobile device has changed from its preceding position beyond the minimum threshold for considering the accuracy constraint of the position information. If the position has not changed, in block 308 the position application 124a or 124b is instructed to wait for a specified time interval and then repeats the process of requesting updated position coordinates in block 302. In another impression, the functions of blocks 302, 304, and 308 may be performed in the mobile positioning system by a triggering or notification process, where it is specified if the position of the mobile device changes. The location application server is notified and the updated location coordinates of the mobile subscriber are provided. In yet another impression, the functions of blocks 302, 304, and 308 may be performed by another location application server within the mobile carrier network that works in conjunction with said mobile positioning system. At block 306, the location application 124a or 124b or the designated location application server determines and modifies the location-based existence state corresponding to each sharing level. New (details are shown in FIG. 4). After the position state table has been updated based on the current position, in decision blocks 310, 312 and 314, whether the position state corresponding to levels 1, 2 and 3 has changed due to the new position of the mobile subscriber. A test will be conducted on whether or not. In blocks 316, 318, 320, if the corresponding shared level position state has changed, the corresponding level 1, 2 or 3 users are updated. In one scenario, only Level 2 and / or Level 3 states can change and Level 1 states can remain the same (eg, if the mobile subscriber moves to a new location in the same city). , The level 1 state remains the same). In this case, the application server updates the location status only for Level 2 and Level 3 users, thereby minimizing the update frequency for Level 1 users and receiving more specific location status. Provide an efficient way to update only to some authorized users.

In addition, mobile subscribers may choose Level 1 or Level 2 as their default location sharing level as the level to share with all users requesting status or listed in the contact list. In one impression, any user can request the location status of mobile subscribers corresponding to the default location sharing level, and the location application server is limited to only some users corresponding to the higher sharing level. On the other hand, the position state is updated, thereby providing an efficient and optimal method for sharing the position-based existence state among a large number of users. In another impression, the location state corresponding to the default sharing level 1 or 2 is shared in the public IM network with the option to request a location state corresponding to a higher sharing level, after which the contact is said to be said. For authorized users at a higher sharing level, the request may be served automatically, or the request may be sent to the mobile subscriber for approval.

FIG. 4 is for updating the mobile subscriber's location status table based on whether the user is at or near his or her designated location, is driving, or is at a business or POI location. An exemplary flowchart is shown. As mentioned above, if it is determined in the test in the determination block 304 that the position of the mobile subscriber has changed, the subroutine 400 will start and, as shown in block 402, the position coordinates, accuracy and speed information of the mobile phone will be mobile. Provided by the positioning system 112. In block 404, the position coordinates of the mobile subscriber are compared with the position coordinates of the user-specified position stored in the table shown in FIGS. 5a and 5b, from the nearest neighbor position and the user's current position. Determine the corresponding distance. If the determination block 406 determines that the user's current position is at or near this user-specified position within a specified distance, the user is at or near this position (eg, home, home neighborhood, workplace, etc.). Whether or not you are in the vicinity of your workplace) is further specified. Therefore, in block 408, the position-state table is updated based on the user-designated position and user criteria for states at levels 1, 2 and 3. In decision block 406, if it is determined that the user is not present at or near any of the user designated positions, in decision block 410, the user moves at a speed greater than or equal to the specified designated speed in another test. (For example, moving at a speed exceeding 10 mph), thereby assuming that the user's state is driving and the user is moving at a speed equal to or higher than a specific specified speed. If not, it is considered that the user is stationary or moving at a slower speed but is not in or near any of the user-specified locations. If it is determined that the user is in operation, the position state table is updated accordingly, as shown in block 412. If the user is determined to be stationary within reasonable accuracy constraints, at block 414, Perform another determination test to determine if the user is in a place of business or POI position. If it is determined that the user is in a business or POI location, the business name, category, and address information will be requested from the geodatabase and / or the business or POI database, as shown in block 424, and accordingly. At block 426, the position state is updated with the corresponding information and user-specified criteria for each sharing level. If it is determined that the user is moving slower than the specified speed that is considered to be driving, or if there are multiple offices in the same location at the current location, the user will determine the current office location. You may be prompted to confirm or select, and in these scenarios the functionality of blocks 414, 424 and 426 is replaced by Subroutine 1000 (details shown in FIG. 10). If the user is considered to be driving, or if it is determined in block 414 that the user is stationary but not in a place of business or POI location, the location state is geographic area level information. Is determined as corresponding to or based on the shared level 1 state of the user. Therefore, in block 416, the address information of the user is requested using the inverse geocode function of the mobile positioning system or using another geodatabase. In decision block 418, if the city (or area level information as specified by the user) changes, the level 1 state is updated accordingly. If the city or region level information has not changed, only level 2 and / or level 3 status information is updated in the mobile subscriber's location status table, as shown in block 422. In addition, there may be no additional location name and / or state information available for level 2, in which case the level 2 text state can be the same as the level 1 state. If the is determined to be in a business or POI location, the business name, category, and address information will be requested from the geodatabase and / or business or POI database and blocked accordingly, as shown in block 424. At 426, the position state is updated with the corresponding information and user-specified criteria for each sharing level. If it is determined that the user is moving slower than the specified speed that is considered to be driving, or if there are multiple offices in the same location at the current location, the user will determine the current office location. You may be prompted to confirm or select, and in these scenarios the functionality of blocks 414, 424 and 426 is replaced by Subroutine 1000 (details shown in FIG. 10). If the user is considered to be driving, or if it is determined in block 414 that the user is stationary but not in a place of business or POI location, the location state is geographic area level information. Is determined as corresponding to or based on the shared level 1 state of the user. Therefore, in block 416, the address information of the user is requested using the inverse geocode function of the mobile positioning system or using another geodatabase. In decision block 418, if the city (or area level information as specified by the user) changes, the level 1 state is updated accordingly. If the city or region level information has not changed, only level 2 and / or level 3 status information is updated in the mobile subscriber's location status table, as shown in block 422. In addition, there may be no additional location name and / or state information available for level 2, in which case the level 2 text state can be the same as the level 1 state. If the is determined to be in a business or POI location, the business name, category, and address information will be requested from the geodatabase and / or business or POI database and blocked accordingly, as shown in block 424. At 426, the position state is updated with the corresponding information and user-specified criteria for each sharing level. If it is determined that the user is moving slower than the specified speed that is considered to be driving, or if there are multiple offices in the same location at the current location, the user will determine the current office location. You may be prompted to confirm or select, and in these scenarios the functionality of blocks 414, 424 and 426 is replaced by Subroutine 1000 (details shown in FIG. 10). If the user is considered to be driving, or if it is determined in block 414 that the user is stationary but not in a place of business or POI location, the location state is geographic area level information. Is determined as corresponding to or based on the shared level 1 state of the user. Therefore, in block 416, the address information of the user is requested using the inverse geocode function of the mobile positioning system or using another geodatabase. In decision block 418, if the city (or area level information as specified by the user) changes, the level 1 state is updated accordingly. If the city or region level information has not changed, only level 2 and / or level 3 status information is updated in the mobile subscriber's location status table, as shown in block 422. In addition, there may be no additional location name and / or state information available for level 2, in which case the level 2 text state can be the same as the level 1 state. Requested by the base, the location state is updated in block 426 with the corresponding information and user-specified criteria for each sharing level accordingly. If it is determined that the user is moving slower than the specified speed that is considered to be driving, or if there are multiple offices in the same location at the current location, the user will determine the current office location. You may be prompted to confirm or select, and in these scenarios the functionality of blocks 414, 424 and 426 is replaced by Subroutine 1000 (details shown in FIG. 10). If the user is considered to be driving, or if it is determined in block 414 that the user is stationary but not in a place of business or POI location, the location state is geographic area level information. Is determined as corresponding to or based on the shared level 1 state of the user. Therefore, in block 416, the address information of the user is requested using the inverse geocode function of the mobile positioning system or using another geodatabase. In decision block 418, if the city (or area level information as specified by the user) changes, the level 1 state is updated accordingly. If the city or region level information has not changed, only level 2 and / or level 3 status information is updated in the mobile subscriber's location status table, as shown in block 422. In addition, there may be no additional location name and / or state information available for level 2, in which case the level 2 text state can be the same as the level 1 state. Requested by the base, the location state is updated in block 426 with the corresponding information and user-specified criteria for each sharing level accordingly. If it is determined that the user is moving slower than the specified speed that is considered to be driving, or if there are multiple offices in the same location at the current location, the user will determine the current office location. You may be prompted to confirm or select, and in these scenarios the functionality of blocks 414, 424 and 426 is replaced by Subroutine 1000 (details shown in FIG. 10). If the user is considered to be driving, or if it is determined in block 414 that the user is stationary but not in a place of business or POI location, the location state is geographic area level information. Is determined as corresponding to or based on the shared level 1 state of the user. Therefore, in block 416, the address information of the user is requested using the inverse geocode function of the mobile positioning system or using another geodatabase. In decision block 418, if the city (or area level information as specified by the user) changes, the level 1 state is updated accordingly. If the city or region level information has not changed, only level 2 and / or level 3 status information is updated in the mobile subscriber's location status table, as shown in block 422. In addition, there may be no additional location name and / or state information available for level 2, in which case the level 2 text state can be the same as the level 1 state. Promptable, in these scenarios, the functionality of blocks 414, 424 and 426 is replaced by Subroutine 1000 (details shown in FIG. 10). If the user is considered to be driving, or if it is determined in block 414 that the user is stationary but not in a place of business or POI location, the location state is geographic area level information. Is determined as corresponding to or based on the shared level 1 state of the user. Therefore, in block 416, the address information of the user is requested using the inverse geocode function of the mobile positioning system or using another geodatabase. In decision block 418, if the city (or area level information as specified by the user) changes, the level 1 state is updated accordingly. If the city or region level information has not changed, only level 2 and / or level 3 status information is updated in the mobile subscriber's location status table, as shown in block 422. In addition, there may be no additional location name and / or state information available for level 2, in which case the level 2 text state can be the same as the level 1 state. Promptable, in these scenarios, the functionality of blocks 414, 424 and 426 is replaced by Subroutine 1000 (details shown in FIG. 10). If the user is considered to be driving, or if it is determined in block 414 that the user is stationary but not in a place of business or POI location, the location state is geographic area level information. Is determined as corresponding to or based on the shared level 1 state of the user. Therefore, in block 416, the address information of the user is requested using the inverse geocode function of the mobile positioning system or using another geodatabase. In decision block 418, if the city (or area level information as specified by the user) changes, the level 1 state is updated accordingly. If the city or region level information has not changed, only level 2 and / or level 3 status information is updated in the mobile subscriber's location status table, as shown in block 422. In addition, there may be no additional location name and / or state information available for level 2, in which case the level 2 text state can be the same as the level 1 state. If changes, the level 1 status will be updated accordingly. If the city or region level information has not changed, only level 2 and / or level 3 status information is updated in the mobile subscriber's location status table, as shown in block 422. In addition, there may be no additional location name and / or state information available for level 2, in which case the level 2 text state can be the same as the level 1 state. If changes, the level 1 status will be updated accordingly. If the city or region level information has not changed, only level 2 and / or level 3 status information is updated in the mobile subscriber's location status table, as shown in block 422. In addition, there may be no additional location name and / or state information available for level 2, in which case the level 2 text state can be the same as the level 1 state.

As shown in FIG. 5a, Table 500 is an exemplary list of user-specified positions and corresponding settings stored in the table of pre-specified user positions. These user-specified positions and corresponding settings can be used in determining the position states as shown in steps 404, 406 and 408. In this example, the two most common user locations, "home" and "workplace," are stored as places where users are likely to spend most of their time. In field 502, a general location name (eg, "workplace") may be specified by the user, or a more contextual location name (eg, HQ, main campus, factory, building 34) may be specified. .. In field 504, the address of the location is stored. This address may be provided by the user or may be determined by the system based on the position coordinates provided or stored by the user. In field 506, the position coordinates are specified by the user or determined based on the address information provided in 504, or the option to save the current position when the user is at the particular position is available. If selected, it will be saved. In field 508, the user selects an appropriate position category from the available list or specifies a new category that can be used to indicate the user's position state. In field 510, the user either selects the default setting as the lowest sharing level, or from a range of choices, the position state to be shared between users at the corresponding sharing level when the user is at that particular position. specify. In fields 512 and 514, the user may select default settings or, if the position state should be shared with other users, specify options for day, date and / or time settings. ..

As shown in FIG. 5b, Table 520 is an exemplary table for storing user-designated establishments and POI locations, where the user is based on the name, category and / or address information of these locations. Hope to share the positional contextual state. The user can save these locations and the corresponding information while visiting these locations and building this list over time, or specify the required information or the options provided in the location application. Locations may be added at any time by searching for a particular place of business or POI location by name or address using. In field 522, the name of the place of business or POI that can be used for the location state is stored by referring to the place of business or POI database or by having the user specify or customize the name. In field 524, the address of the location is stored. This address may be provided by the user, may be determined by the system based on information available from the establishment or POI database, or may refer to an address corresponding to the location coordinates. It may be provided by doing so. In field 526, the location coordinates of the establishment or POI are determined based on the address information specified by the user or obtained in 524, or the current position when the user is at the particular position. If you have selected the option to save, save the location coordinates of the establishment or POI. In field 528, the geometry information of the POI is stored to indicate whether the POI is a point or covers an area of the specified geometry, in the latter case additional information may be stored or Further information may be requested from the geodatabase to determine the position state at that location. In field 530, store the appropriate location category based on information received from the establishment or POI database or as specified by the user. Fu In field 532, the user either selects the default setting as the minimum sharing level for the location name of the establishment or POI, or, from a range of choices, is at the corresponding sharing level when the user is in that particular location. Specifies the location status to be shared between users. In field 534, the user either selects the default setting as the minimum sharing level for the location category of the establishment or POI, or, from a range of choices, is at the corresponding sharing level when the user is in that particular location. Specifies the location status to be shared between users

As shown in FIG. 6, Table 600 is an exemplary table showing the determination and storage of the user's location-based presence status corresponding to each sharing level. Field 602 indicates a shared level, which is in the range 0-3 in the current impression, as shown in Table 210. Users can add new sharing levels, but for the purposes of this exemplary impression, only levels 0-3 (at level 0 there is no position to share, so only levels 1-3). It is assumed that there is a position state). As mentioned above, at level 1, the location name is based on city and state information, and once the location status of the mobile subscriber is determined, the corresponding city and state information is recorded in block 408, 420 or 426. Updated in field 606 corresponding to 610. In addition, the latest known state at this level can be saved with a timestamp in a similar table, thereby determining in decision block 310 whether the current state has changed from its predecessor. In addition, once the mobile subscriber's location status is determined, the corresponding Level 2 and Level 3 records 612 and 614 are updated accordingly in blocks 408, 422, and 426. If the user is at or near a user-specified location corresponding to Table 500 or 520, the corresponding state in field 604 is indicated as "currently located" or "currently located nearby" or another description. The child indicates the neighborhood of the specified location. In addition, for Level 3 conditions, at 614, store the appropriate distance or time required to indicate that the user is "within miles" or "within minutes" from each location. Can be done. In another case, if the mobile subscriber status in block 410 is determined to be "driving", the corresponding status indicator choices in fields 608 of records 612 and 614 are saved.

FIG. 7 is an exemplary user interface of a mobile device 120a or 120b for showing shared level options for location application 124a or 124b. The shared level interface 700 includes an option to select a default shared level as indicated by setting 702. The user can also select one of the sharing levels and change the setting of the sharing level. The shared level interface screen 710 describes the shared level 1 settings, includes a default name for this level (ie, "city, state"), and provides a choice button. This choice button provides the choice to specify or change the name of the share level. Setting 712 indicates the options available for location name types at this level and provides the option to select one or more region level name types for this level that are based on region level name types. A "+" indicates that this option is currently selected, and a "-" indicates that this option is not selected but can be selected at this sharing level. The shared level interface screen 720 describes the settings for shared level 2, includes the default name for this level, "favorite location", and provides the option to change the name and other settings at this shared level. Setting 722 indicates selected and available options for the position name type at this level (eg, options for selecting a favorite position, POI category and POI name). Examples of favorite locations include user-designated locations in Table 500 and user-designated offices or POI locations in Table 520. The POI category setting includes all categories corresponding to other POI positions not included in Table 520. The POI naming setting includes names corresponding to other POI positions not included in Table 520, which is not selected as the default at sharing level 2, but the user is at this sharing level. You can specify this option. The shared level interface screen 730 describes the settings for shared level 3, includes "positional coordinates" which is the default name at this level, and provides an option to specify or change the name of the shared level. Setting 732 presents the available options for this level of location information, and in addition to the location information available at shared level 2, neighbor-based information (eg, nearest intersections, street names, and POI names). Also based on, and includes options to share street addresses and location coordinates at this level.

FIG. 8 is an exemplary flowchart for determining a user's favorite messaging options corresponding to a user-specified position. As described above in determination block 406, if the user is determined to be at any of the user-designated positions, block 408 also includes subroutine 800 in the process of determining the position state at this position. As shown in block 802, the user is determined to be in a user-designated position. In the determination test of block 804, it is determined whether the user specifies any favorite messaging option corresponding to the user-designated position. For example, the user can specify the home phone as his or her favorite calling option when the user's position state is "at home", or the user's position state is "at work". In some cases, the telephone at work can be designated as a favorite caller option. In other cases, the user may specify email, SMS or IM as his preferred messaging option. If such a favorite messaging or calling option is specified, in block 806 this option is added to the position state table 600.

FIG. 9 is an exemplary flow chart for determining a user's favorite messaging options corresponding to a particular location category. If the user is determined to be in a place of business or POI position, block 428 includes subroutine 900 in the process of determining and updating the position state at this position. As shown in block 902, the user is determined to be in a place of business or POI position. In the block 904 determination test, it is determined whether the user has specified any favorite messaging option corresponding to the establishment or POI location, or whether any default option exists for the location category. The default. For example, for the POI category of library, the user can specify email, SMS or IM as his favorite messaging options. If such a favorite messaging option is specified, in block 906 the messaging option is added to the positional state in Table 600 described above.

FIG. 10 is an exemplary flow chart for determining a location state when there are multiple or co-located establishments or POI options at or near the user's current location. As mentioned above, in test block 410, to determine if the user is in the office or POI position if the user is not in the user-designated position and is not moving at a speed that exceeds the specified speed that is considered to be driving. Test. However, in some cases, multiple co-located offices or POI locations may correspond to the user's current location within the accuracy constraints of the mobile positioning system 112. Also, the user may be moving at a lower speed and not in a stationary state. The functions of blocks 414, 424 and 426 can be replaced by Subroutine 1000 to address these scenarios and determine the corresponding establishment or POI location. In the determination block 1002, first, it is determined whether the user is in a stationary state within the accuracy constraint of the mobile positioning system 112. If the user is not considered to be stationary, in block 1006, the position application 124a or 124b is instructed to wait for a specified time interval, after which the position application 124a or 124b updates the position coordinates. Is requested and the process in block 1002 is repeated. If the user is considered to be stationary, block 1004 determines the nearest POI position and the corresponding distance. In the determination block 1008, a test is conducted as to whether the current position of the user corresponds to only one business establishment or POI position, and if the test result is "yes", the business of the position in the block 1016 is performed. Provide location or POI name, category and address information as current location. If the test result is not "yes", in block 1010 the user's current position is determined within the accuracy constraints and the specified distance criteria. Determine if it is possible to accommodate multiple POI positions such as. If there are multiple co-located or nearby POI locations in the vicinity of the user location, block 1012 provides the user's location application 124a or 124b with a list of nearest neighbors within the user's specified distance and blocks. At 1014, the user is prompted to select the current position from the presented list, and based on the user's input, information about the position is provided to block 1016. However, if there is no response from the user within the specified time, in block 1006, the position application 124a or 124b is instructed to wait for the specified time interval, requests the updated position coordinates, and then blocks. Repeat the process at 1002.

Although exemplary embodiments of the invention have been described above, those skilled in the art will make some modifications and modifications without departing from the spirit and scope of the invention as described in the claims below. Please note that it is possible.