JP4390571B2 - Position information processing method and apparatus - Google Patents

Description

  The present invention relates to position information processing technology.

  In recent years, with the advent of mobile phones with GPS (Global Positioning System) functions and personal portable GPS terminals, it has become relatively easy to know where you are. It is also possible to know the current position of a specific person or object using a technique such as GPS.

  For example, Japanese Patent Laid-Open No. 2001-175718 discloses the following technique. That is, a plurality of users register information necessary for introduction including the user's own attributes and conditions for the attributes of others in the server, carry the user terminal, and the user terminal is the user terminal The location information is transmitted to the server via the wireless communication network, and the server is based on the information registered by the user, the location information received from the user terminal, and the determination history of whether or not past introduction processing has been executed. Determines whether or not the introduction process of the pair between users is executed, and notifies the user terminal of the pair of users who are the target of the introduction process via the wireless communication network To do. As a result, it is possible to introduce the user who matches the profile and exists in the vicinity of the user, or the other who satisfies the condition obtained by adding the past condition search result history to the condition.

  Further, for example, Japanese Patent Application Laid-Open No. 2002-58054 discloses the following technique. That is, using the location information of the mobile communication terminal set in the network of the communication carrier Y, the mobile phone of the third party telephone number registered by the user in the same area as the cell C1 where the user actually exists. The presence / absence of the communication terminals P, Q, and R is determined and a response is made to the user. Thereby, it can be easily and immediately known that a specific person is in the vicinity of the user.

  Further, for example, Japanese Patent Laid-Open No. 9-264943 discloses the following technique. In other words, current location information from mobile objects such as pedestrians, running cars, trains, etc. is organized based on the individual identification serial number (telephone number) of the mobile object through the telephone station from the base station antenna to the management center. (Memorized), and a third party (for example, a telephone subscriber or a personal computer terminal) can freely access the current position of the mobile body and other information based on the serial number (telephone number) via the telephone line and the telephone office. . This makes it possible to freely access location information and the like from a mobile object from anywhere at any time.

Further, for example, Japanese Patent Laid-Open No. 11-64007 discloses the following technique. In other words, it is a GPS device consisting of a GPS antenna device that receives signals from satellites, a GPS reception analysis device, and a display device, and can be remotely operated from a communication line by a mobile phone, a pager, or a PHS (Personal Handy phone System) Display device for displaying a current position based on a signal analyzed by a reception analysis device for a signal received by a GPS antenna at a remote control center, equipped with a simple GPS antenna device and a transfer transmission device for received signals Is installed. As a result, a third party can search for the current position of the person carrying the device, or a person can contact the person, and the mobile phone is equipped with a GPS antenna device, and the display signal is analyzed by analyzing the received signal at the control center. Can be displayed.
JP 2001-175718 A JP 2002-58054 A Japanese Patent Laid-Open No. 9-264943 Japanese Patent Laid-Open No. 11-64007

  As described above, the related art is capable of knowing a specific person in the vicinity of the user or knowing position information of the specific person. However, a normal user cannot always monitor the position information of a specific person. Also, it does not always keep track of the action schedule of a specific person. Also, for example, if you are in a store or a store nearby, you want to buy that, or if you go to a store or store in the neighborhood tomorrow, you need a technology that meets your request. Nothing is disclosed.

  Accordingly, an object of the present invention is to provide a position information processing method for making it possible to make various requests to other specific users at an appropriate timing according to the user's desires.

  The position information processing method according to the present invention includes a step of extracting a second user associated with a moving first user with reference to a user information storage unit that stores correspondence between users; Referring to a notification condition storage unit that stores a notification condition related to a position unrelated to the current position, the first user's position information (for example, the first user's current position or the first user's planned position) A determination step for determining whether the notification condition related to the position related to the extracted second user is satisfied, and a case where it is determined that the position information of the first user satisfies the notification condition related to the position Includes a notification step of notifying the second user of the information including the first user information.

  In this way, the position information of the first user associated with the second user is, for example, a notification condition related to the position desired by the second user (for example, in the vicinity of a specific store, selling a specific product) In the vicinity of a certain store, in the vicinity of a store selling products belonging to a specific product genre), for example, when the notification condition is satisfied or when it is determined that the notification condition is scheduled in the near future A notification is made to the second user. That is, the second user can make some request to the first user at an appropriate timing if necessary.

  Moreover, in this invention, when the purchase request of the specific goods with respect to the 1st user is received from the 2nd user, you may make it further include the step which transmits the purchase request of a specific goods with respect to the 1st user. . In this way, the transfer of the request from the second user to the first user may be handled in this mechanism, or the request itself may be directly performed from the second user to the first user. good.

  Furthermore, the notification condition related to the position described above is at least one of the condition related to the position set by the second user and the condition related to the position automatically extracted based on the purchase history of the second user. May be included. That is, not only conditions based on the second user's wishes, but also features that are not automatically noticed by the second user may be automatically extracted from the purchase history and set.

  Further, the notification condition related to the position described above may include at least one of store identification information and product information.

  Further, the determination step described above refers to a store information storage unit that stores store information including store location information and sales merchandise information, and extracts corresponding store information based on the first user location information. Determining whether the step and the extracted store information match at least one of store identification information and product information included in the notification condition related to the position related to the second user stored in the notification condition storage unit A second determination step may be included.

  As described above, there are cases where conditions are directly set for a store, and conditions are set for a product and a store is specified from the product. Further, there are cases where conditions are set not only for specific products but also for product groups such as product genres.

  The above method may be implemented by a combination of a computer and a program, in which case the program is stored in a storage medium or storage device such as a flexible disk, a CD-ROM, a magneto-optical disk, a semiconductor memory, or a hard disk. Stored in Moreover, it may be distributed as a digital signal via a network or the like. The intermediate processing result is temporarily stored in a storage device such as a memory.

  According to the present invention, various requests can be made to other specific users at an appropriate timing according to the user's wishes and the like.

  FIG. 1 shows a system outline diagram according to an embodiment of the present invention. For example, a network 1 such as a public line network or the Internet includes a plurality of wireless base stations 5a and 5b, for example, one or a plurality of user terminals C that are personal computers, a person to be searched (the current position is searched, for example, a shopping request is made Mobile terminal A that transmits position information at predetermined time intervals while moving and held by a user), and mobile terminal B that is held by a user who has registered a search target person who holds mobile terminal A. A center server 3 that performs main processing and one or a plurality of administrator terminals 7 that are personal computers operated by an administrator of the center server 3 are connected.

The mobile terminal A and the mobile terminal B are, for example, mobile phones having a GPS function, a mailer function, and a web (Web) browser function. However, it may be a terminal device such as a PDA (Personal Digital A s sistant) . The radio base stations 5a and 5b are the same as in the prior art and will not be described further. The user terminal C and the administrator terminal 7 have a mailer function and a web browser function.

  The center server 3 has a Web server function and a mailer function, and further includes a data maintenance unit 31, a user interface unit 32, a purchase history analysis unit 33, a search target person search processing unit 34, and a matching processing unit 35. ing. Details of these functions will be described later. The center server 3 manages a product database (DB) 36, a list DB 37, a store DB 40, a map DB 39, and a user DB 38. The data stored in these databases will be described below.

First, the map DB 39 will be described, but before that, the handling of map data in the present embodiment will be outlined. In this embodiment, in principle, the map is divided into 200 m × 200 m square meshes. FIG. 2 shows an example of an area constituted by a predetermined number of meshes. In the example of FIG. 2, the area is composed of 5 × 7 = 35 meshes. In FIG. 2, latitude and longitude values are shown in the boundary line of the area and the boundary line of the mesh. For example, the upper limit value of the area is 36.05.15.19994 N, and the lower limit value is 36 N of latitude. 05.15.19494. The left limit value of the area is 136.57.51.64609 east longitude, and the right limit value of the area is 136.57.51.63909 east longitude. As shown in FIG. 2, the vertex of each mesh is specified by the latitude / longitude values of the intersection of the boundary lines.

  For the purpose of this embodiment, if you are traveling on a train or highway, you cannot shop immediately, so areas on train tracks and highways are included in the area. Do not. In the example of FIG. 2, the hatched portion is a train track and is not included in the area.

  When a predetermined number of areas are collected, an area is formed. In the present embodiment, it is assumed that an area is configured by putting together a certain range of areas such as municipalities. Each mesh in the hierarchical map is a combination of a number (or ID) given to the mesh, a number (or ID) given to the area, and a number (or ID) given to the area. It shall be specified in For example, it is expressed as horizontal 01-098-13.

  In addition, when a mesh having a size of about 200 mm × 200 mm is used, a large-scale commercial facility may span a number of meshes as shown in FIG. That is, the commercial facility F is arranged on the meshes B, C, and D among the normal meshes B, C, D, and E. In such a case, the commercial facility F is identified as one mesh. Accordingly, even if the points on the meshes B, C, and D overlap with the mesh F, the mesh F is specified with priority. In addition, since the angle of the mesh F and another mesh is not necessarily 90 degrees, it is judged by the following method, for example whether a specific point is contained in the mesh F, for example. That is, the target rectangle is divided into two triangles, and the determination is made based on whether or not the determination target point is within the triangular area. Whether it is included in the region within the triangle is determined by expressing the position of the target point by a linear combination of vectors of two sides of the triangle.

  Since the method for determining whether a specific point is included in the mesh F in the special case as shown in FIG. 3 has been described, a method for determining in which mesh a specific point is included in a normal case. This will be briefly described with reference to FIG. In the example of FIG. 4, the mesh A shown in FIG. 2 is shown. The vertices of the mesh A are a, b, c, and d. And let a specific point be x. In the center server 3 (searched person search processing unit 34), the range of the square is indicated by the east longitude and the north latitude as described above, and the distance between a and b is between 36.0.15.19594 and 36.36. 05.15.19494, and the distance between b and c is 136.57.51.64509 to 136.57.51.64409. Therefore, if the specific point x is (36.0.15.19582, 136.57.51.64475), the north latitude and the east longitude are within the square range described above, It is determined that the point x is included in the mesh A. When specifying a mesh, all meshes in the area are sequentially searched in this way, and a mesh having a range that includes both east longitude and north latitude is specified.

  Under such a premise, the map DB 39 stores the following data. Such data registration is performed, for example, by exchanging data between the administrator terminal 7 and the data maintenance unit 31 of the center server 3.

  FIG. 5 shows an example of the area information table stored in the map DB 39. In the example of FIG. 5, for each area, the area name, the upper limit value (latitude) of the area, the lower limit value (latitude) of the area, the left limit value (longitude) of the area, and the right limit value of the area ( (Longitude) is registered. Thus, the range of each area can be specified by specifying the side of the area. FIG. 6 shows an example of an area information table provided for each area. In the example of FIG. 6, for each area, the area name, the upper limit value (latitude) of the area, the lower limit value (latitude) of the area, the left limit value (longitude) of the area, and the right limit value ( (Longitude) is registered. Thus, the range of each area can be specified by specifying the sides of the area.

  FIG. 7 shows an example of the area data table stored in the map DB 39. The area data table in FIG. 7 links the data of each mesh with the area and area. In the example of FIG. 7, for each mesh, the area name, area name, mesh name, and upper limit value of the mesh (latitude ), The lower limit value (latitude) of the mesh, the left limit value (longitude) of the mesh, and the right limit value (longitude) of the mesh. As a result, the range of each mesh can be specified, and the hierarchical relationship with the areas and sections can be specified. For example, the area “lateral 01”, the area “0001”, and the mesh “04” are specified by the mesh ID “lateral 01-0001-04”. For the commercial facility mesh, the latitude and longitude data of the four vertices are registered.

  The map DB 39 also stores an address data table as shown in FIG. The address data table of FIG. 8 is used to identify the mesh ID from the address. In the example of FIG. 8, the column of the prefecture name, the column of the city name, the column of the town name, the column of the chome, A row of addresses and the like and a row of mesh IDs are provided. For example, the mesh ID can be easily specified from the store address or the user's home address in this table.

  Further, a station data table as shown in FIG. 9 is also stored in the map DB 39. The station data table of FIG. 9 is used to identify the mesh ID of the station from the station name and the like. In the example of FIG. 9, the nearest station ID column, the route name / company (railway company) column, and the station name And a mesh ID column are provided. Thereby, for example, when the user's nearest station is designated, the mesh ID of the nearest station can be easily specified.

  Next, an example of data stored in the product DB 36 will be described. FIG. 10 shows an example of the product data table. The product data table of FIG. 10 is used to acquire data of a specific product. In the example of FIG. 10, a genre ID (genre ID) column, a product ID column, There are provided a column, a manufacturer column, a retail price column, and an exclusive sales flag (Y / N) column. A product with an exclusive sales flag “Y” represents a product that is sold only in one store or one chain store, and a product “N” indicates a product that is not limited to a particular store. .

  FIG. 11 shows an example of a genre table stored in the product DB 36. The genre table in FIG. 11 associates genre names with genre IDs. In the example of FIG. 11, a genre ID column and a genre column are provided.

  In the present embodiment, since the person to be searched mainly purchases a product requested by the user while moving, (1) design items such as clothing, accessories, and watches are high, and the product selection is personal. Products that greatly depend on subjectivity, (2) Large and large items such as PCs, home appliances such as refrigerators, and furniture such as desks and chests, (3) Ordinary repetitive purchases and purchases from others No data is registered in the product DB 36 for products that cannot be used.

  Next, an example of data stored in the store DB 40 will be described. FIG. 12 shows an example of the store data table. The store data table of FIG. 12 is used to specify stores that exist in a specific mesh, to specify the products handled by the store and the genre of the products, etc. In the example of FIG. , A business hours flag column, a store name column, a store address column, a handling product ID column, a handling genre ID column, and a remarks column. The business hours flag is set in order to confirm whether the person being searched is open because there is no point in making a purchase request if the store is not open when the person being searched is nearby. Set according to the rules. For example, A09-18 indicates that business hours are from 9:00 to 18:00 without holidays. D10-17 indicates that the business hours are from 10:00 to 17:00 on a regular holiday on Wednesday. In the handled product ID and handled genre ID, the product ID and genre ID registered in the product data table are registered for the product handled in the store. Information such as temporary holidays and closing information are registered in the remarks.

  The product that is not registered in the product DB 36 has been described above, but the store that handles only the product as described above is not registered in the store DB 40.

  Next, an example of data stored in the user DB 38 will be described. When using the service provided by the center server 3, the user needs to register in advance using the user terminal C or the mobile terminal B, for example. For example, when the user operates the user terminal C or the mobile terminal B to access the user registration page of the center server 3, the user interface unit 32 of the center server 3 transmits the data on the user registration page to the user terminal. C or mobile terminal B (hereinafter, an example using user terminal C is shown). The user terminal C receives the user registration page data and displays a screen as shown in FIG. 13 on the display device, for example.

  In the example of FIG. 13, a name input field, a phonetic input field, a home address input field, a nearest station name input field, a railway company name input field, a telephone number input field, a forwarding mail address input field, An account number input field and a bank name input field for collecting the consideration for the service, a credit card number input field for collecting the consideration, and a contract terms display button for displaying the contract terms for the service In addition, a check box for confirming acceptance of the contract terms, a registration button for executing user registration, and a cancel button for canceling registration are provided. The user inputs necessary data according to this screen, and when the user agrees to the contract terms, the user selects a check box and clicks a registration button.

  Then, the user terminal C transmits input data and the like to the user interface unit 32 of the center server 3. The user interface unit 32 of the center server 3 receives data for user registration from the user terminal C, and registers the received data in the user DB 38 through a confirmation step for the user, for example. FIG. 14 shows an example of a user registration table stored in the user DB 38. In the example of the user registration table in FIG. 14, a user ID column, a password column, a name column, a phonetic column, an address column, a telephone number column, an email address column, and a payment account. A column of information or credit card information, a column of nearest station ID, a column of station mesh ID, and a column of address mesh ID are provided. The user ID and password are automatically issued by the user interface unit 32 at the time of registration. The user ID and password are notified to the user. Further, the user interface unit 32 acquires and registers the nearest station ID and the station mesh ID for the nearest station of the user using the data stored in the map DB 39 (FIG. 9). Further, the address mesh ID is specified and registered from the home address of the user with reference to the map DB 39 (FIG. 8).

  Next, in order to receive the provision of this service, the search target person must be registered. Accordingly, the user operates the user terminal C to access the search target person registration / update / delete page. In response to the access from the user terminal C, the user interface unit 32 of the center server 3 transmits the search target person registration / update / delete page data to the user terminal C. The user terminal C receives the search target person registration / update / delete page data from the center server 3 and displays a screen as shown in FIG. 15 on the display device, for example.

  In the example of FIG. 15, the search target person registration / update / deletion page includes a registration unit 150 and an update / deletion unit 151. The registration unit 150 includes a search target person name input field, a search target person mail address input field, and a registered mail transmission button. When registering a new search target person, enter his / her name and e-mail address and click the registration e-mail transmission button. It is not registered as a search target person simply by clicking the registration mail transmission button. This is because the searchee's consent is required because personal information called position information of the searchee is used. Therefore, when the registered mail transmission button is clicked, the name of the search target person and the information of the mail address are transmitted from the user terminal C to the user interface unit 32 of the center server 3. The user interface unit 32 temporarily registers the data in association with the user ID of the registration requesting user in the user DB 38 and transmits an email requesting consent to the search target person. If consent can be obtained from the search target person in response to the email, the temporary registration is changed to full registration. Information such as “phonetic” is additionally acquired from the search target person, and data such as a search target person ID and password is issued. The search target ID and password are notified to the search target, and are used when, for example, the search target changes or deletes his / her registration.

  Note that the update / delete unit 151 includes a table including data of registered search target persons corresponding to the user, an update button, and a delete button. The user clicks data (name / email address) to be changed, and clicks an update button. When the user clicks on the update button, the ID or the like of the selected button is transmitted from the user terminal C to the center server 3. The user interface unit 32 of the center server 3 generates page data including a change item input field from the selected button ID, and transmits the page data to the user terminal C. The user terminal C receives the page data and displays it on the display device. The user inputs the change content (name / mail address) in the input field of the change item, and clicks the update mail transmission button. The user terminal C transmits the change item content data to the center server 3. The center server 3 receives the content data of the change item and temporarily registers it in the user DB 38 corresponding to the search target person ID. In this embodiment, since update registration cannot be performed without obtaining the consent of the search target person, an update confirmation mail is transmitted to the search target person. If consent is obtained from the search target person, temporary registration is changed to full registration.

  When deleting, it is not necessary to obtain the consent of the search target person. Therefore, when the user clicks either the search target person or the e-mail address and the delete button on the screen of FIG. 15, the ID of the selected button is selected. Are transmitted from the user terminal C to the center server 3. The user interface unit 32 of the center server 3 receives the ID or the like of the selected button, specifies the search target person ID, and cancels the association between the registered user and the search target person ID in the user DB 38.

  An example of data related to the search target person stored in the user DB 38 used in the processing described above will be described with reference to FIGS. 16 and 17. FIG. 16 shows an example of a search target person data table. In the example of FIG. 16, a search target person ID column, a password column, a name column, a phonetic column, and a mail address column are provided. Thereby, necessary data can be obtained for each person to be searched. FIG. 17 shows an example of a correspondence table for associating a registered user with a search target person. In the example of FIG. 17, a column of user IDs and a column of IDs of search target persons registered as search target persons are provided. In this way, a plurality of search target persons can be registered per user. In this table, registered users can also be extracted from the search target person ID. It is possible for a plurality of users to register the same person as a search target person. Although not shown, the user DB 38 also stores a search target person position table for managing an area ID where the search target person is currently located.

  In addition, the user can manually register when it is desired to receive notification from the center server 3. The user operates the user terminal C to access the store of the center server 3 or the product registration page. Here, first, a process for registering a store by accessing the store registration page will be described. In response to the access from the user terminal C, the user interface unit 32 of the center server 3 transmits the data of the store registration page to the user terminal C. The user terminal C receives the store registration page data from the center server 3, and displays a screen as shown in FIG. 18 on the display device, for example.

  In the example of FIG. 18, the store registration page includes a store search unit 180 and a registered store correction deletion unit 181. The store search unit 180 is provided with a store name input column, a store address input column, a product genre selection column, and a store search button. When registering a new store, the user inputs data in the input field and selects a product genre. However, since it is a search, any data may be selected or input. In response to the click on the store search button, the user terminal C transmits selection input data to the center server 3. The user interface unit 32 of the center server 3 receives selection input data as a search condition from the user terminal C, and searches the store DB 40 (FIG. 12) according to the selection input data. The user interface unit 32 generates store list page data including the search result and transmits it to the user terminal C. The user terminal C receives the store list page data from the center server 3 and displays it on the display device. The store list page includes store data that matches the search conditions. In addition, not only a store but the product which the said store handles, and the data about the genre of the product are shown in the aspect which can be selected. The user can select only a store, only a genre, only a product, a combination of a store and a product and a genre, a combination of a store and a genre, and a combination of a product and a genre. When the registration button is clicked after selection, the user terminal C transmits selection data to the center server 3. The user interface unit 32 of the center server 3 receives the selection data from the user terminal C and registers it in the list DB 37. Note that a memo or the like can be registered in association with a store.

  The registered store correction / deletion unit 181 includes a registration item table including a store name, a registered genre, a store location, a memo, and the like, an information correction button, and an information deletion button. If there is data already registered in the list DB 37 (registration data for the store), this registration item table is generated. When a store and a genre are registered correspondingly, data on the registered genre is displayed. The items that can be corrected or deleted from the registered item table are buttons and can be selected. The store name can be selected to delete the store, the registered genre can be selected to delete or change the genre, and the memo etc. can also be deleted or changed It is selectable. When performing information correction, the information correction button is clicked after the item to be corrected is clicked. The user terminal C receives an input from the user, and transmits a selection button ID and the like and a code indicating information correction to the center server 3. The center server 3 receives the selection button ID and the code indicating the information correction, generates information correction page data including a correction input field corresponding to the selection button ID and the like, and transmits the information correction page data to the user terminal C. . The user terminal C receives the information correction page data from the center server 3 and displays it on the display device. The user inputs corrected data for the selected item and clicks the registration button. The user terminal C transmits the correction data input by the user to the center server 3. The center server 3 receives the correction data from the user terminal C, and updates the data in the list DB 37 according to the correction data.

  On the other hand, when deleting information, the user clicks an item to be deleted and then clicks an information deletion button. The user terminal C receives an input from the user, and transmits a selection button ID and the like and a code indicating information deletion to the center server 3. The center server 3 receives the ID etc. of the selection button and the code indicating information deletion, and deletes the data stored in the list DB 37 according to the received data.

  Next, a process for registering a product by accessing the product registration page will be described. In response to the access from the user terminal C, the user interface unit 32 of the center server 3 transmits the data of the product registration page to the user terminal C. The user terminal C receives the product registration page data from the center server 3, and displays a screen as shown in FIG. 19 on the display device, for example.

  In the example of FIG. 19, the product registration page includes a product search unit 190 and a registered product correction / deletion unit 191. The product search unit 190 is provided with a product name input field, a product genre selection field, a store name input field, and a product search button. When registering a new product, the user inputs data in the input field and selects a product genre. However, since it is a search, any data may be selected or input. In response to the click of the product search button, the user terminal C transmits selection input data to the center server 3. The user interface unit 32 of the center server 3 receives selection input data as a search condition from the user terminal C, and searches the product DB 36 (FIG. 10) according to the selection input data. The user interface unit 32 generates product list page data including the search result and transmits it to the user terminal C. The user terminal C receives the product list page data from the center server 3 and displays it on the display device. This product list page includes data on products that match the search conditions. Not only the product but also the store selling the product (for example, it may be limited to exclusive sales only) and the data about the genre of the product are presented in a selectable manner. The user can select only a store, only a genre, only a product, a combination of a store and a product and a genre, a combination of a store and a genre, and a combination of a product and a genre. When the registration button is clicked after selection, the user terminal C transmits selection data to the center server 3. The user interface unit 32 of the center server 3 receives the selection data from the user terminal C and registers it in the list DB 37. Note that a memo or the like can be associated with the product and registered.

  The registered product correction / deletion unit 191 includes a registration item table including a product name, a registered genre, a store name, a memo, and the like, an information correction button, and an information deletion button. If there is data already registered in the list DB 37 (registered data about the product), this registration item table is generated. When a store is associated with a registered product and registered, data is displayed in the sales store name column. The items that can be corrected or deleted from the registered item table are buttons and can be selected. The product name can be selected to delete the product, the registered genre can be selected to delete the genre along with the product, and the store name can also be selected by the store. It can be selected to change or delete the association, and a memo or the like can also be selected to delete or change. When performing information correction, the information correction button is clicked after the item to be corrected is clicked. The user terminal C receives an input from the user, and transmits a selection button ID and the like and a code indicating information correction to the center server 3. The center server 3 receives the selection button ID and the code indicating the information correction, generates information correction page data including a correction input field corresponding to the selection button ID and the like, and transmits the information correction page data to the user terminal C. . The user terminal C receives the information correction page data from the center server 3 and displays it on the display device. The user inputs corrected data for the selected item and clicks the registration button. The user terminal C transmits the correction data input by the user to the center server 3. The center server 3 receives the correction data from the user terminal C, and updates the data in the list DB 37 according to the correction data.

  On the other hand, when deleting information, the user clicks an item to be deleted and then clicks an information deletion button. The user terminal C receives an input from the user, and transmits a selection button ID and the like and a code indicating information deletion to the center server 3. The center server 3 receives the ID etc. of the selection button and the code indicating information deletion, and deletes the data stored in the list DB 37 according to the received data. As for the exclusive sales products mentioned above, the relationship between the store and the products cannot be deleted. Therefore, for the change / deletion, the exclusive sales are deleted / modified after confirmation processing.

  For example, data as shown in FIG. 20 is registered in the list DB 37 by the above processing. In the example of FIG. 20, a user ID column for registered users, a store ID column, a genre ID column, and a product ID column are provided. As shown in the example of FIG. 20, when the user designates only the store, only the store ID, when only the genre is designated, only the genre ID is designated, and when only the product is designated, the genre ID and the product are designated. An ID (a store may be registered in the case of exclusive sales) is registered. Although not shown, there may be cases where a combination of a store ID and a genre ID is registered. Data registered in the list DB 37 is a notification condition for a registered user.

  Next, the outline of the processing flow of the present embodiment will be described with reference to FIG. First, initial information registration is performed (step S1). As described above, the initial information registration is to register data in the product DB 36, the store DB 40, and the map DB 39. For example, the data is exchanged between the administrator terminal 7 and the data maintenance unit 31 of the center server 3. To be implemented. Next, user information registration is performed (step S3). The user information registration process registers data in the user DB 38 and the list DB 37 as described above. For example, the user information registration process is performed between the mobile terminal A, the mobile terminal B, the user terminal C, and the user interface unit 32 of the center server 3. Implemented in exchange. Next, the purchase history analysis unit 33 performs a purchase history analysis process (step S5). In the user information registration process (step S3), the store or product information is registered by itself, but here, the user himself / herself is automatically unaware of or forgetful information that has been forgotten. sign up. This will be described in detail later. Then, the search target person search processing unit 34 and the verification processing unit 35 perform search / verification / notification processing (step S7). The location of the search target person is specified, the notification condition is collated, and the registered user is notified. This process will also be described in detail later.

  First, the purchase history analysis process (FIG. 21: step S5) will be described. As described above, a store, a product, or a genre that should be noted by the user may be registered. However, there are items that the user has forgotten to register or items that the user is not aware of. For example, when payment is made by means such as a credit card or electronic money that records purchase history, if the purchase history data can be acquired, products to be registered are automatically extracted and registered in the list DB 37. be able to. Note that the user information registration process may be skipped and only this process may be executed.

  In the present embodiment, purchase history data (including at least purchase date, purchased store, and purchased product data) is acquired from an external system of the center server 3 and (1) sold at stores within the range of action. As for products, purchases are made only once every several months with a purchase interval of 1 month or more and within 6 months. (2) For products sold in stores outside the range of action, purchase 3 to 6 times a year The product which is doing is extracted. In addition, the numerical value in this condition is an example, You may make it use another numerical value. In this embodiment, the “range of action” means (1) a mesh on a straight line connecting the home and the nearest station and within 1 mesh above and below or on the left and right of the mesh, and (2) purchased 5 times or more per month. It is assumed that the store has a mesh. In addition, you may make it employ | adopt the definition different from this Embodiment also about the definition of action range.

  Next, purchase history analysis processing will be described with reference to FIGS. The purchase history analysis unit 33 performs provisional table creation processing for sorting purchase history data (step S11). This provisional table creation process is: (1) In purchase history data acquired from an external system, data for the past year from the last date is subject to analysis, and purchases are excluded from handling in the present embodiment described above. A record group excluding records that are commodities is extracted, and (2) a table including a result of sorting the records in the oldest order based on the “purchase date” included in the purchase history data is generated. The purchase history data acquired from the external system is used by being stored in a purchase history data storage unit (not shown).

  Next, the purchase history analysis unit 33 performs an action range analysis process (step S13). This process is a process of extracting a mesh based on the criteria as described above, and details will be described later. And the store contained in the mesh extracted as an action range is extracted from store DB40 (FIG. 12), for example, is stored in storage devices, such as a main memory (step S15). Then, one unprocessed record is extracted from the temporary table generated in step S11 (step S17), and the purchased product is sold in the store within the action range with reference to the store data read in step S15. It is judged (step S19). If it is determined that the product is sold, it is determined whether the purchase interval is 1 month or more and 6 months or less with reference to the temporary table generated in step S11 (step S21). If it is determined that this criterion is not satisfied, the process proceeds to step S29. On the other hand, if it is determined that this standard is satisfied, the purchase product ID is specified by searching the product DB 36 (FIG. 10) (step S25), and the purchase product ID and the like are registered in the list DB 37 ( Step S27). Not only the product ID but also the genre ID is registered. In some cases, the store ID may also be registered. Then, control goes to a step S29. On the other hand, if it is determined in step S19 that the purchased item is not sold at a store within the range of activity, whether the purchased item has been purchased three to six times within one year from the first purchase is generated in step S11. The judgment is made with reference to the provisional table (step S23). When this criterion is satisfied, the process proceeds to step S25, and when this criterion is not satisfied, the process proceeds to step S29.

  In step S29, it is determined whether all unprocessed records have been processed in the temporary table (step S29). If an unprocessed record exists, the process returns to step S17. On the other hand, if there is no unprocessed record, the process returns to the original process.

  In this way, products and the like that satisfy the criteria as described above can be automatically extracted and registered in the list DB 37.

  Next, the action range analysis process will be described with reference to FIGS. The purchase history analysis unit 33 acquires the mesh ID of the user's home and the nearest station from the user DB 38 and stores the mesh ID in a storage device such as a main memory (FIG. 23: step S31). Then, the map DB 39 (FIG. 7) is searched with the acquired mesh ID, the limit value of the mesh is acquired, and stored in a storage device such as a main memory (step S33). Then, the direction from the nearest station to the home is specified based on the limit value (step S35).

  For example, the upper limit value of the home mesh is compared with the upper limit value of the nearest station mesh, and if they are the same, the direction from the nearest station to the home is specified as horizontal. For example, the right limit value of the home mesh is compared with the right limit value of the nearest station mesh. If the right limit value of the home mesh is smaller, it is simply “right”; if the right limit value of the home mesh is larger, Simply identified as “left”.

  On the other hand, the upper limit value of the home mesh and the upper limit value of the nearest station mesh are compared. If the upper limit value of the home mesh is larger, the direction from the nearest station to the home is temporarily “up” If the upper limit value of the home mesh is smaller, the direction from the nearest station to the home is temporarily determined to be “down”. Furthermore, for example, the right upper limit value of the home mesh and the right upper limit value of the nearest station mesh are compared, and if they are the same, the direction from the nearest station to the home is simply “up” or “down”, and the upper limit value. It is decided by the judgment result at the time of comparison.

  If there is a difference between the upper limit value of the home mesh and the upper limit value of the nearest station mesh, the right limit value of the home mesh is compared with the right limit value of the nearest station mesh, and the right limit value is further compared. Compare the difference for and the upper limit. If (1) the right limit value of the home mesh is smaller and the difference with respect to the right limit value is larger, the vertical or horizontal direction “right” and the diagonal directions “right diagonal” and “up” or “ ”Bottom” (according to the comparison result for the upper limit value), and (2) if the right limit value of the home mesh is larger and the difference for the right limit value is greater, the vertical or horizontal direction “left ”And diagonal directions“ left diagonal ”and“ up ”or“ down ”(according to the comparison result for the upper limit value), and (3) the right limit value of the home mesh is smaller and the difference for the upper limit value If it is greater, the vertical or horizontal direction “up” or “down” (according to the comparison result for the upper limit value) and the diagonal direction “right diagonal” and “up” or “lower” (for the upper limit value) (4) right limit of home mesh If the value is greater and the difference for the upper limit value is greater, the vertical or horizontal direction “up” or “down” (according to the comparison result for the upper limit value) and the diagonal directions “left diagonal” and “ Specify "up" or "down" (according to the comparison result for the upper limit value).

Then, the purchase history analysis unit 33 determines whether the home and the nearest station can be connected by a vertical or horizontal straight line based on the processing result of step S35 (step S37). In step S35, it is confirmed whether the direction from the nearest station to the home is determined to be “right” only, “left” only, “up” only, or “down” only. The case where the oblique direction is specified will be described with reference to FIG. An example of the case where it is determined in step S37 that the home and the nearest station can be connected by a vertical or horizontal straight line will be described with reference to FIG. In the example of FIG. 24, the meshes of the home and the station (nearest station) are arranged horizontally.

  Next, the purchase history analysis unit 33 registers 1 mesh in the direction opposite to the direction specified in step S35 in the action range table (step S39). In the example of FIG. 24, since the direction is specified as “left” in step S35, the mesh a advanced by one mesh in the “right” direction is registered in the action range table. Further, the nearest station mesh is specified (step S41). In the example of FIG. 24, since the mesh b1 is the nearest station mesh, this is specified. The action range table includes the specified mesh, the upper and lower meshes in the horizontal direction (“right” or “left”), and the left and right meshes in the vertical direction (“up” or “down”). (Step S43). Further, it is determined whether the identified mesh is a home mesh (step S45). If it is determined that the home mesh has not yet been reached, the process proceeds by one mesh in the direction specified in step S35, and the mesh is specified (step S47). In the example of FIG. 24, the mesh b2 is specified. Then, the process returns to step S43. When steps S43 to S47 are repeated, meshes b2 and c2, meshes b3 and c3, and meshes b4 and c4 are registered in the action range table. When the meshes b4 and c4 are registered in the action range table, it is determined in step S45 that the home mesh has been reached.

  If it is determined that the home mesh has been reached, the process advances by one mesh in the direction specified in step S35, and the mesh is registered in the action range table (step S49). In the example of FIG. 24, the mesh e is registered in the action range table. Thus, the mesh group hatched in FIG. 24 is specified as the action range.

  Further, the purchase history analysis unit 33 refers to the temporary table generated in step S11, identifies a store that has been purchased five or more times a month, and registers the mesh of the store in the action range table (step S51). ). Then, the process returns to the original process.

  Next, the previous processing that has shifted from the terminal A will be described with reference to FIGS. 25 and 26. The case where the processing of FIG. 25 is performed is because the home mesh and the nearest station mesh are horizontal (“right” or “left”) or vertical (“down” or “up”), for example, as shown in FIG. This is a case where it cannot be connected by a straight line. The purchase history analysis unit 33 arranges the mesh line from the home mesh to the nearest station mesh according to the oblique direction specified in step S35 (step S53). In the example of FIG. 26, the direction specified in step S35 is “left” in the vertical or horizontal direction, and “left diagonal” and “up” in the diagonal direction. In other words, the home position is diagonally up to the left when viewed from the nearest station. On the other hand, if the standard is home, the nearest station is at the lower right. In this step, the directions of “right diagonal” and “down” are specified from “left diagonal” and “up”, and the mesh line is arranged in the 45 ° downward diagonal direction to the right. In the example of FIG. 26, a mesh with diagonal lines is a mesh on the mesh line.

  Then, the purchase history analysis unit 33 registers one mesh in the direction opposite to the vertical or horizontal direction specified in step S35 in the action range table (step S55). In the example of FIG. 26, since the vertical or horizontal direction “left” is specified in step S35, the mesh B advanced by 1 mesh in the “right” direction is registered in the action range table.

  Further, the nearest station mesh is specified (step S57). The specified mesh and its upper and lower (when the vertical or horizontal direction is “right” or “left”) or left and right (when the vertical or horizontal direction is “up” or “down”) are displayed in the action range table. Registration is performed (step S59). In the example of FIG. 26, meshes C1 and D1 are registered in the action range table. Then, it is determined whether the mesh on the mesh line has been reached (step S61). If it is determined that it has not reached, the mesh advances by one mesh in the vertical or horizontal direction specified in step S35, and the mesh is specified (step S63). Then, the process returns to step S59. On the other hand, when it reaches the mesh line, the process proceeds to step S65. By repeating steps S59 to S63, meshes C2 and D2 and meshes C3 and D3 are specified. Then, the mesh C3 becomes a mesh on the mesh line, and the process proceeds to step S65.

  Next, the purchase history analysis unit 33 specifies the next mesh in the direction of the home mesh on the mesh line (step S65). In the example of FIG. 26, the mesh F1 is specified. Then, the specified mesh and its upper and lower sides (when the vertical or horizontal direction is “right” or “left”) or left and right (when the vertical or horizontal direction is “up” or “down”) are registered in the action range table. (Step S67). In the example of FIG. 26, meshes F1 and G1 are registered. Then, it is determined whether the home mesh has been reached (step S69). If the home mesh has not been reached, the mesh advances on the mesh line by 1 mesh in the home mesh direction, and the mesh is specified (step S71). In the example of FIG. 26, the mesh F2 is specified. Then, the process returns to step S67. By repeating steps S67 to S71, the meshes F2 and G2 are specified in the example of FIG.

  When the home mesh is reached, the mesh advances by one mesh in the vertical or horizontal direction specified in step S35, and the mesh is registered in the action range table (step S73). In the example of FIG. 26, since the vertical or horizontal direction is “left”, the “left” mesh I is registered in the action range table. Then, the process proceeds to step S51 in FIG.

  In this way, the action range described above is specified, and stores that are included in the mesh within the action range can be extracted.

  Next, search / collation / notification processing executed by the search target person search processing unit 34 and the collation processing unit 35 will be described. When the preparation has been completed in the processing so far, and the person to be searched is set to transmit the location information to the mobile server A, the processing as shown in FIG. 27 is performed. That is, the mobile terminal A transmits the position information to the center server 3 periodically (for example, every few minutes), for example (step S81). The position information includes a search target person ID and latitude / longitude data of the current position. Upon receiving the location information from the mobile terminal A, the search target person search processing unit 34 of the center server 3 stores the location information in a storage device such as a main memory (step S83). The position information of the search target person is used only in the search target person search process for privacy protection. Then, a search target person search process is performed (step S85). This search target person search process will be described in detail with reference to FIGS.

  The search target person search processing unit 34 specifies the search target person from the position information received from the search target person terminal (FIG. 28: step S111). The search target person ID included in the position information is specified. Then, it is determined whether the previous area ID is registered (step S115). For example, a search target person position table is provided in the user DB 38, and a search target person ID and an area ID are registered. Note that, when the position information is not received from the mobile terminal A of the search target person for a predetermined period, the record of the search target person is deleted from the search target person position table. If it is determined that an area ID is registered for the search target person with reference to the search target person position table, the previous area ID and the received position are referred to the map DB 39 (FIG. 6). An area is specified from the information (step S117). In the case where the previous area ID is held, it is possible to speed up the identification of the mesh ID by determining whether or not the area has moved from the area. That is, the upper, lower, left, and right limit values are registered in each area, and if the latitude / longitude received from the searchee's mobile terminal A exceeds that value, it is determined that the area has moved outside the area. it can. When the upper limit value is exceeded, it is estimated that the area has moved to the upper area, and when the right limit value is exceeded, it is estimated that the area on the right side has moved, and the same applies to other directions. In some cases, if the limit value is exceeded in comparison with not only the area but also the limit value of the area, the area is specified for another area.

  An example is shown in FIG. For example, the previous area ID indicates A, the upper limit value of the area A is 36.05.15.19994, the lower limit value is 36.05.15.19494, and the left limit value is 136.57.51. 64609 and the right limit value is 136.57.51.63909. At this time, if the position of the search target person is (36.005.15.19594, 136.57.51.64409), since both values are within the limit value of area A, from area A Is determined not to move. On the other hand, in the case of (36.005.15.194, 136.57.51.64409), the upper limit value is exceeded, so it is estimated that the vehicle has moved to area B. Further, in the case of (36.0.5.15.19594, 136.57.51.63709), the right limit value is exceeded, so it is estimated that the vehicle has moved to area E. Furthermore, in the case of (36.005.15.1944, 136.57.51.63609), it is estimated that the vehicle has moved to the area F because both the upper limit value and the right limit value are exceeded.

On the other hand, if it is determined in step S115 that the previous area ID has not been registered, the area is identified based on the received position information and information on the limit value of the area stored in the map DB 39 (FIG. 5). (Step S119). Then, the area (area ID) is specified based on the received position information and information on the limit value of the area stored in the map DB 39 (FIG. 6) and specified in step S119 (step S121). And the area ID specified in step S121 or step S 117, for example, to register the search target person position table of the user DB 38 (step S123).

  An area is specified by performing such processing. Although a method of registering the mesh ID in the search target person position table is also possible, since the mesh is too narrow, it becomes a problem when the movement record of the mesh leaks for some reason. The area is used in consideration.

  When the area is specified, the limit value of the mesh in the area is read from the map DB 39 (FIG. 7), and the mesh in the area is specified from the limit value of each mesh and the received longitude / latitude information (step S125). . That is, the mesh ID is acquired and stored in a storage device such as a main memory. As mentioned above, commercial facilities may be defined separately from the square mesh. Therefore, it is determined whether the current position is not on the commercial facility (step S127). As for commercial facilities, latitude and longitude data at four vertices are registered in the map DB 39 for each area as a rectangular mesh. If the commercial facility exists in the area, refer to that data, Determine if the location is on a commercial facility. If it is determined that it is on a commercial facility, the mesh ID of the commercial facility is identified instead of the mesh ID identified in step S125 (step S129). Then, the process returns to the original process. On the other hand, if it is determined not to be on a commercial facility, the process returns to the original process without doing anything.

  By performing the processing as described above, the area ID of the search target person to be used for the next processing can be specified, and further, the originally necessary mesh ID can be specified. Here, the position information itself of the search target person is discarded.

  Returning to the description of FIG. 27, the collation processing unit 35 performs collation processing (step S87). This collation process will be described with reference to FIGS. First, the matching processing unit 35 acquires the search target person ID and the mesh ID specified in the search target person search process (FIG. 30: step S131). Then, the user ID of the user whose search target person is the search target person acquired is read from the user DB 38 (FIG. 17), a user ID table is generated, and stored in a storage device such as a main memory. Store (step S133). Then, it is determined whether all the users in the user ID table have been processed (step S135). If the process is completed for all users, the process returns to the original process.

  On the other hand, when an unprocessed user remains in the user ID table, one user is extracted from the user ID table (step S137), and provisional table generation processing is performed for the user (step S139). This temporary table generation process will be described with reference to FIG. The collation processing unit 35 reads the information of the corresponding user from the list DB 37 (FIG. 20) to a storage device such as a main memory (step S155). Then, it is determined whether all records have been processed (step S157). When all the records have been processed, the process returns to the original process. On the other hand, when there is an unprocessed record, one unprocessed record is specified (step S159). And it is judged whether the said record is comprised only with store ID (step S161). If the record is composed only of the store ID, the store ID of the record is registered in the temporary store table (step S163). Then, the process returns to step S157 via the terminal E. On the other hand, if the record is not composed of only the store ID, it is determined whether the record is composed of only the genre ID (step S165). If the record is composed only of the genre ID, the genre ID of the record is registered in the temporary genre table (step S167). Then, the process returns to step S157 via the terminal E. On the other hand, if the record is not composed only of the genre ID, the product ID is registered in the product temporary table (step S169), and the genre ID registered corresponding to the product ID is registered in the genre temporary table. (Step S171). Then, the process returns to step S157 via the terminal E.

  In this way, the store temporary table, the genre temporary table, and the product temporary table are generated. That is, a list of stores, a list of genres, and a list of products that are conditions for notifying the user are generated.

  Returning to the description of FIG. 30, the matching processing unit 35 stores store information of all stores during business hours in the mesh specified by the mesh ID from the store DB 40 (FIG. 12) to a storage device such as a main memory. Read (step S141). Since shopping is not possible unless it is during business hours, according to the present embodiment, it is previously removed from the processing object according to the business hours flag. And it is judged whether it processed about all the store information of the store information read in step S141 (step S143). If it is determined that all store information has been processed, the process returns to step S135. On the other hand, if unprocessed store information exists, information for one unprocessed store is specified (step S145), and the product ID of the product sold at the store is in the product provisional table generated in step S139. It is determined whether it matches any of the products (step S147). If the product ID of the product sold at the store matches any product in the temporary product table generated in step S139, a product email is generated (step S149), and the product email is transmitted (step S149). Step S151). Then, the process returns to step S143 via the terminal D. Here, the user name and e-mail address are extracted from the user DB 38 (FIG. 14) using the processing target user ID, and the search target person name and e-mail address are extracted from the user DB 38 (FIG. 16). Then, the product name is extracted from the product DB 36 (FIG. 10) using the product ID determined to match, and the store name is extracted from the store DB 40 (FIG. 12) using the processing target store ID. It is stored in a storage device such as Then, a product mail is generated using the read data. A specific example of the product mail will be described later.

  On the other hand, if the product ID of the product sold at the store does not match any product ID in the temporary product table generated in step S139, the process proceeds to the process of FIG. Next, the verification processing unit 35 determines whether the store ID of the processing target store matches any store in the temporary store table generated in step S139 (FIG. 32: step S175). If it is determined that the store ID of the store to be processed matches one of the store IDs in the store provisional table, store email is generated (step S177) and the store email is transmitted (step S179). ), And then returns to step S143 via the terminal D. Here, the user name and mail address are extracted from the user DB 38 (FIG. 14) using the user ID to be processed, and the search target person name and mail address are extracted from the user DB 38 (FIG. 16) using the search target person ID. Then, the store name is extracted from the store DB 40 (FIG. 12) using the store ID of the store to be processed, and stored in a storage device such as a main memory, for example. And store mail is produced | generated using the read data.

  On the other hand, if the store ID of the processing target store does not match any store ID in the temporary table generated in step S139, the genre ID registered corresponding to the processing target store is generated in step S139. It is determined whether the genre ID matches any genre ID in the temporary table (step S181). If it is determined that the genre ID registered corresponding to the processing target store matches any genre ID in the temporary genre table, a genre mail is generated (step S183), and the genre / The mail is transmitted (step S185), and the process returns to step S143 via the terminal D. Here, the user name and e-mail address are extracted from the user DB 38 (FIG. 14) using the processing target user ID, and the search target person name and e-mail address are extracted from the user DB 38 (FIG. 16). Then, the genre name is extracted from the product DB 36 (FIG. 11) using the genre ID, the store name is extracted from the store DB 40 (FIG. 12) using the store ID of the processing target store, and a storage device such as a main memory, for example. To store. Then, a genre mail is generated using the read data.

  By executing such processing, the store provisional table, which is a notification condition in which any one of the store, the product, and the genre is set corresponding to the user for the store included in the mesh of the position where the search target person currently exists. It is determined whether the item matches any item of the product temporary table or the genre temporary table. If there is a matching item, product mail, store mail, and genre mail are sent to the user. If there is no matching item, no mail is generated and sent. Then, the process proceeds to the processing of the position information of the next search target person. Here, it is assumed that any mail is generated and transmitted.

  Returning to the description of FIG. 27, a mail is generated and transmitted in step S87. Then, the mobile terminal B held by the user receives the mail from the center server 3 and displays it on the display device (step S89). For example, a product mail as shown in FIG. 33 is displayed on the display device. The example of FIG. 33 shows a case where a store “ΔΔΔΔ” is specified based on the position information of the search target person “XX”, and a product “■■■■■” is specified. That is, the product mail includes information on the search target, product information, and store information. In the example of the product mail in FIG. 33, a message input field, a “send” button, and a “do not send” button are provided. When the user requests the person to be searched for XX to purchase the product, for example, he / she inputs a message in the message input field and clicks the “Send” button. When not requesting the purchase of a product, there are a case where a “don't send” button is clicked and a case where nothing is done.

  Here, it is assumed that a message is input and the “Send” button is clicked. Then, the mobile terminal B transmits purchase request data to the center server 3 according to the instruction (step S91). The purchase request data includes a message, a search target person ID, a store ID, a product ID, or the like, or a product mail ID associated with these data. For example, when receiving the purchase request data from the mobile terminal B (step S93), the verification processing unit 35 of the center server 3 uses the data specified in step S87 and stored in the storage device such as the main memory. A purchase request mail addressed to the search target person is transmitted (step S95). Such data may be specified by the product mail ID.

  Then, the mobile terminal A receives the purchase request mail from the center server 3 and displays it on the display device (step S96). For example, a purchase request mail as shown in FIG. 34 is displayed. In the example of the purchase request e-mail in FIG. 34, information on the requester (◎◎), store (△△△△), product (■■■■■) is included, and a message display field from the requester and A “Purchase” button for expressing acceptance of the request and a “Do not purchase” button for expressing rejection of the request are provided. The search target person confirms the contents of the mail, and clicks the “Purchase” button when accepting the request, or clicks the “Do not purchase” button when rejecting the request.

  The mobile terminal A receives an acceptance / rejection response from the search target person and transmits it to the center server 3 (step S97). The collation processing unit 35 of the center server 3 receives an acceptance / rejection response by the search target person from the mobile terminal A, and temporarily stores it in a storage device such as a main memory (step S99). Then, the acceptance / rejection response mail is generated, and the acceptance / rejection response mail is transmitted to the requester (step S101). The mobile terminal B receives the acceptance / rejection response mail from the center server 3 and displays it on the display device (step S103).

  As described above, according to the current position of the search target person, it is determined whether or not the notification condition of the product, the store, and the product genre set for the corresponding user is satisfied. A notification is made to confirm whether the request is to be made. Further, when making a purchase request, the center server 3 mediates.

  A genre mail as shown in FIG. 35 may be sent instead of the product mail in FIG. In the example of FIG. 35, the genre in which “eye drops (for middle-aged and elderly people)” is specified is represented, and information on a search target person (XXX) and a store (ΔΔΔΔ) is included. Furthermore, in the example of FIG. 35, a purchase request item input field, a message input field, a “send” button, and a “not send” button are provided. The user inputs the purchase request product name and clicks the “Send” button, or clicks the “Do not send” button. When the “Send” button is clicked, for example, the searchee ID, genre ID, store ID, purchase request product name, and message data are sent to the center server 3 as purchase request data. Note that the genre / mail ID may be identified by the genre / mail ID in step S87 and stored in the main memory, and the genre / mail may be transmitted to the center server 3.

  When the user makes a purchase request corresponding to the genre mail as shown in FIG. 35, a purchase request mail as shown in FIG. 36 is sent to the search target person instead of the purchase request mail in FIG. Sent to. In the example of FIG. 36, data of a requester (◎◎), a store (△△△△), and a purchase request product (■■■■■) are included. In addition, a message display field, a “buy” button, and a “do not buy” button are provided. Since the genre matches and the genre mail as shown in FIG. 35 is transmitted, it is unclear whether the purchase request product specified by the requester is sold at the store, so a message to that effect is also included. ing. The search target person clicks the “Purchase” button when accepting the request, and clicks the “Do not purchase” button when rejecting the request.

  Although the store mail is not shown, basically, mail that does not include genre data in the genre mail is generated and transmitted. Although the purchase request mail transmitted to the search target person in response to the store mail is not shown, it has the same contents as FIG.

  The center server 3, user terminal C, and administrator terminal 7 described above are computers, and the computer has a configuration as shown in FIG. That is, the memory 2501, the CPU 2503, the hard disk drive (HDD) 2505, the display control unit 2507 connected to the display device 2509, the drive device 2513 for the removable disk 2511, the input device 2515, and the communication control unit for connecting to the network. 2517 is connected to the bus 2519. An operating system (OS) and an application program for performing the above-described processing are stored in the HDD 2505, and are read from the HDD 2505 to the memory 2501 when executed by the CPU 2503. If necessary, the CPU 2503 controls the display control unit 2507, the communication control unit 2517, and the drive device 2513 to perform necessary operations. Further, data in the middle of processing is stored in the memory 2501 and stored in the HDD 2505 if necessary. Such a computer realizes various functions as described above by organically cooperating hardware such as the CPU 2503 and the memory 2501 described above with the OS and necessary application programs.

  Also, the mobile terminals A and B may not hold the drive device 2513 and the HDD 2505, but instead hold a semiconductor storage device such as a flash memory.

  Although one embodiment of the present invention has been described above, the present invention is not limited to the above-described embodiment. For example, FIG. 38 shows another embodiment. FIG. 38 shows a processing flow executed in place of FIG. In FIG. 38, the search target person operates the mobile terminal A to transmit the future planned position information such as tomorrow or next week to the center server 3 instead of the current position (step S191). For example, according to a business trip schedule or a travel plan, for example, the business trip destination, the station name of the travel destination, the building name, and other location information are included. The time data may include only the date or may include time data. In addition, it is possible to use data for schedule registration in a service for managing a schedule, for example, instead of sending only the planned position information. In that case, the received data is stored in the schedule data storage unit.

  The search target person search processing unit 34 of the center server 3 receives the scheduled position information from the mobile terminal A and stores it in a storage device such as a main memory (step S193). Next, the mesh ID corresponding to the scheduled position information is specified with reference to, for example, the map DB 39 (step S195). And the collation process part 35 implements a collation process (step S197). In addition, although the collation process shown in FIG. 30 thru | or FIG. 32 is implemented, if the scheduled time can be identified, for example, confirmation of the business hours in step S141 will be implemented. Hereinafter, steps S199 to S215 are substantially the same as steps S89 to S103 in FIG.

  Other variations are possible. For example, the center server 3 may be realized by a single computer, and may be realized by a plurality of computers. Furthermore, the functional blocks shown in FIG. 1 do not necessarily correspond to program modules. Further, the database configuration is not limited to that shown in FIG. 1, and more or fewer databases may be used.

  Although an example using mail has been described, a voice message may be used instead of mail, or an instant message or the like may be used. Further, the user and the search target may directly exchange after the purchase request without going through the center server 3.

  Also, in the above processing flow, the same content mail may be generated and sent every few minutes, so save the previously sent notification mail and do not send it if it has the same content Sometimes it is applied.

(Appendix 1)
Extracting a second user associated with the moving first user by referring to the user information storage unit storing the correspondence between users;
With reference to a notification condition storage unit that stores a notification condition related to a position unrelated to the current position of the user, the position information of the first user relates to the position related to the extracted second user. A determination step for determining whether the notification condition is satisfied;
A notification step of notifying the second user of the information including the first user information when it is determined that the position information of the first user satisfies a notification condition related to the position; ,
A position information processing method executed by a computer.

(Appendix 2)
The method according to claim 1, further comprising a step of transmitting a purchase request for the specific product to the first user when receiving a purchase request for the specific product for the first user from the second user. Location information processing method.

(Appendix 3)
The location information according to appendix 1 or 2, wherein the location information of the first user is one of information on a current location of the first user and information on a planned location of the first user. Processing method.

(Appendix 4)
The notification condition related to the position includes at least one of a condition related to the position set by the second user and a condition related to the position automatically extracted based on the purchase history of the second user. The position information processing method according to any one of 1 to 3.

(Appendix 5)
The position information processing method according to any one of supplementary notes 1 to 4, wherein the notification condition related to the position includes at least one of store identification information and product information.

(Appendix 6)
The determination step includes
Referring to a store information storage unit that stores store information including store location information and sales product information, and extracting corresponding store information based on the location information of the first user;
The extracted store information matches at least one of the store identification information and the product information included in the notification condition related to the position related to the second user stored in the notification condition storage unit. A second determination step for determining whether or not
The position information processing method according to appendix 5, including:

(Appendix 7)
The product information includes product genre information,
The location information processing method according to claim 6, wherein, in the second determination step, the genre of the product sold at the store is compared with information on the product genre included in the product information.

(Appendix 8)
With reference to a purchase history data storage unit that stores purchase history data including purchase date and purchase store information, a first condition for purchase stores included in the geographical range identified as the user's action range; The supplementary note 4 further including the step of specifying information on a store that satisfies at least one of a second condition for a store that is not included in the geographical range specified as the user's action range as a condition related to the location. Position information processing method.

(Appendix 9)
The determination step includes
If it is determined to match in the second determination step, further includes a specifying step of specifying the store identification information determined to match, or the product information determined to match and the store identification information for selling the product,
The position information processing method according to appendix 6, wherein the information specified in the specifying step is further notified in the notification step.

(Appendix 10)
A program for causing a computer to execute the position information processing method according to any one of appendices 1 to 9.

(Appendix 11)
Means for extracting a second user associated with the moving first user with reference to the user information storage unit storing the correspondence between users;
With reference to a notification condition storage unit that stores a notification condition related to a position unrelated to the current position of the user, the position information of the first user relates to the position related to the extracted second user. A determination means for determining whether the notification condition is satisfied;
A notification means for notifying the second user of the information including the information of the first user when it is determined that the position information of the first user satisfies a notification condition related to the position; ,
A position information processing apparatus.

It is a system outline figure concerning one embodiment of the present invention. It is a figure which shows an example of an area. It is a schematic diagram for demonstrating the handling of the commercial facility in a mesh. It is a schematic diagram for demonstrating the process for determining whether it is contained in a mesh. It is a figure which shows an example of an area information table. It is a figure which shows an example of an area information table. It is a figure which shows an example of an area data table. It is a figure which shows an example of an address data table. It is a figure which shows an example of a station data table. It is a figure which shows an example of a goods data table. It is a figure which shows an example of a genre table. It is a figure which shows an example of a shop data table. It is a figure which shows an example of a user registration screen. It is a figure which shows an example of a user registration table. It is a figure which shows an example of a to-be-searched person registration / update / deletion screen. It is a figure which shows an example of a to-be-searched person data table. It is a figure which shows an example of a correspondence table. It is a figure which shows an example of a favorite store registration screen. It is a figure which shows an example of a favorite goods registration screen. It is a figure which shows an example of the data registered into list DB. It is a figure which shows the processing flow which concerns on one embodiment of this invention. It is a figure which shows the processing flow of a purchase history analysis process. It is a figure which shows a part of processing flow of action range analysis processing. It is a schematic diagram for demonstrating the processing flow of action range analysis processing. It is a figure which shows a part of processing flow of action range analysis processing. It is a schematic diagram for demonstrating the processing flow of action range analysis processing. It is a figure which shows the processing flow of search / collation / notification process. It is a figure which shows the processing flow of a search target person search process. It is a figure which shows the example of an area. It is a figure which shows a part of processing flow of collation processing. It is a figure which shows the processing flow of a temporary table production | generation process. It is a figure which shows a part of processing flow of collation processing. It is a figure which shows an example of goods mail. It is a figure which shows an example of a purchase request mail. It is a figure which shows an example of a genre mail. It is a figure which shows an example of a purchase request mail. It is a figure which shows an example of the functional block of a computer. It is a figure which shows the 2nd example of the processing flow of search / collation / notification process.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 Network 3 Center server 5a, 5b Wireless base station 7 Manager terminal A, B Mobile terminal C User terminal 31 Data maintenance part 32 User interface part 33 Purchase history analysis part 34 Search target person search processing part 35 Collation processing part 36 Goods DB 37 List DB 38 User DB
39 Map DB 40 Store DB

Claims (5)

A position information processing method executed by a computer,
Based on the location information including the ID of the first user, the computer stores store information near the terminal of the first user from a store information storage unit that stores store information including store location information and sales product information. Extracting, and
Corresponding to the ID of the first user from the correspondence table storage unit in which the computer stores the ID of the user and the ID of the second user who wants to receive notification regarding the movement of the user. Extracting the second user's ID,
The computer specifies product information associated with the extracted second user ID from the notification condition storage unit that stores the user ID and product information in association with each other, and the product information, A determination step of determining whether or not the sales product information included in the extracted store information matches;
If it is determined in the determination step that the information matches, the computer stores a notification associated with the second user ID from the user information storage unit that stores the user ID and the notification destination in association with each other. The first user information associated with the first user ID is identified from a second user information storage unit that identifies the destination and stores the user ID and the user information in association with each other. A notification step of specifying and notifying the specified notification destination, including the product information determined to match in the determination step and the information of the specified first user;
A position information processing method comprising: Based on the purchase history data stored in the purchase history data storage unit including information on the product purchased by the user, the computer associates the information on the product purchased by the user with the ID of the user. The position information processing method according to claim 1, further comprising a purchase history analysis step registered in the storage unit. A second specifying step in which the computer specifies a notification destination associated with the ID of the first user from the user information storage unit;
When receiving a purchase request for a specific product for the first user from the second user, the computer requests the purchase of the specific product to the notification destination specified in the second specification step. A step of sending
The position information processing method according to claim 1, further comprising: The purchase history analysis step comprises:
A first condition that is applied when the sales merchandise information stored in the store information storage unit in association with a store included in the user's action range matches information on a product purchased by the user; The position information processing method according to claim 2, further comprising: specifying information on a product that satisfies at least one of the second conditions applied when they do not match. Means for extracting store information in the vicinity of the terminal of the first user from a store information storage unit that stores store information including store location information and sales merchandise information based on location information including the first user ID; ,
From the correspondence table storage unit that associates and stores the ID of the user and the ID of the second user who wishes to receive notification regarding the movement of the user, the first ID associated with the first user ID Means for extracting the IDs of the two users;
From the notification condition storage unit that stores the user ID and product information in association with each other, the product information associated with the extracted second user ID is specified, and the product information and the extracted product information are identified. Determining means for determining whether or not the sales product information included in the store information matches;
If it is determined that matching by the determining means, from the user information storage unit that stores in association with the ID of the user notification destination, identifying a notification destination associated with the ID of the second user And identifying the first user information associated with the first user ID from the second user information storage unit that stores the user ID and the user information in association with each other. Notification means for making a notification including the product information determined to be matched by the determination means and the information of the identified first user to the notification destination,
A position information processing apparatus.

Images