Abstract:
A system for information delivery includes: an electronic tag for holding a tag identifier being updatable; a server for storing the tag identifier held in the electronic tag and information corresponding to the tag identifier; and a terminal for causing the information corresponding to the tag identifier to be delivered from the server. The terminal includes a memory, and a processor coupled to the memory and configured to execute a process. The process executed by the processor includes reading the tag identifier from the electronic tag, updating the tag identifier in the electronic tag with a new tag identifier that is different in content from the tag identifier read from the electronic tag, and establishing, after updating the tag identifier in the electronic tag, a time period in which a discrepancy between the tag identifier in the electronic tag and the tag identifier stored in the server occurs.

Description:
CROSS-REFERENCE TO RELATED APPLICATION 
       [0001]    This application is based upon and claims the benefit of priority of the prior Japanese Patent Application No. 2015-240667, filed on Dec. 9, 2015, the entire contents of which are incorporated herein by reference. 
       FIELD 
       [0002]    The embodiments discussed herein are related to a system, a method for information delivery, and a non-transitory computer-readable storage medium. 
       BACKGROUND 
       [0003]    There is known a system in which the number unique to an electronic tag is managed. In such a system, an electronic device communicates wirelessly with an electronic tag to read the unique number in the electronic tag, and, if the unique number is a valid number, query a management server coupled via a network to verify the authenticity of the unique number. The management server calculates the probability of a forgery by referencing a history database, a black list database, a process transition rule, and the like, and then, if the probability is within a reference range, determines that the unique number is authentic, and, if the probability is out of the reference range, determines that the unique number is not authentic. 
         [0004]    There is also known a system in which the identification number of an electronic tag is updated and the updated identification number is managed. In such a system, in response to an instruction for reading an identification number issued by an individual identification device, an individual identification tag reads and transmits an identification number held in the individual identification tag, and updates the identification number by a predetermined method. The individual identification device acquires the identification number read and transmitted in response to the instruction for reading the identification number held in the individual identification tag, and updates the identification number by the same method as with the individual identification tag. As an example of the related art, Japanese Laid-open Patent Publication No. 2004-29984, Japanese Laid-open Patent Publication No. 2009-53877, Japanese Laid-open Patent Publication No. 2010-160673, and International Publication Pamphlet No. WO 2005/106680 are known. 
       SUMMARY 
       [0005]    According to an aspect of the invention, a system for information delivery includes: an electronic tag configured to hold a tag identifier that is updatable; a server configured to store the tag identifier held in the electronic tag and information corresponding to the tag identifier, and deliver information based on the tag identifier; and a terminal that configured to cause information corresponding to the tag identifier held in the electronic tag to be delivered from the server. The terminal includes a memory, and a processor coupled to the memory and configured to read the tag identifier from the electronic tag. The processor included in the terminal is configured to update the tag identifier in the electronic tag with a new tag identifier that is different in content from the tag identifier read from the electronic tag, and establish, after updating the tag identifier in the electronic tag, a time period in which a discrepancy between the tag identifier in the electronic tag and the tag identifier stored in the server occurs, by delaying a transmission timing of an update request to update the tag identifier stored in the server with the new tag identifier, or by causing the server to delay enabling the tag identifier stored in the server and updated with the new tag identifier. 
         [0006]    The object and advantages of the invention will be realized and attained by means of the elements and combinations particularly pointed out in the claims. 
         [0007]    It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory and are not restrictive of the invention, as claimed. 
     
    
     
       BRIEF DESCRIPTION OF DRAWINGS 
         [0008]      FIG. 1  is a block diagram illustrating a functional configuration of a system for information delivery according to a first embodiment; 
           [0009]      FIG. 2  is a diagram depicting an example of a data structure of a tag information database (DB); 
           [0010]      FIG. 3  is a diagram depicting an example of a data structure of a work schedule DB; 
           [0011]      FIG. 4  is a diagram illustrating an example of a flowchart of a process for information delivery according to the first embodiment; 
           [0012]      FIG. 5  is a diagram illustrating an example of a flowchart of an update request timing determination process according to the first embodiment; 
           [0013]      FIG. 6  is a block diagram illustrating a functional configuration of a system for information delivery according to a second embodiment; 
           [0014]      FIG. 7  is a diagram depicting an example of a data structure of a tag information DB; 
           [0015]      FIG. 8  is a diagram illustrating an example of a flowchart of a process for information delivery according to the second embodiment; and 
           [0016]      FIG. 9  is a diagram illustrating an example of a computer that executes a program for information delivery. 
       
    
    
     DESCRIPTION OF EMBODIMENTS 
       [0017]    Related-art techniques, by which even an arbitrary electronic device is able to read the identification number of an electronic tag, have an issue in that, if the read identification number is used, it is not possible to inhibit a third party who is not intended to possesses the electronic device that has read the identification number from impersonating a legitimate person. 
         [0018]    For example, in the system in which the number unique to an electronic tag is managed, an electronic device possessed by a third party is able to communicate wirelessly with the electronic tag to read the unique number in the electronic tag. This allows the electronic device to query a management server about the authenticity of the unique number and further allows the management server to provide a determination that the unique number is authentic. Accordingly, the system is unable to inhibit the third party from impersonating a legitimate person. 
         [0019]    In the system in which the identification number of an electronic tag is updated and the updated identification number is managed, an individual identification tag updates the identification number. However, if a third party possesses an individual identification device, in response to an instruction for reading an identification number held in the individual identification tag, the individual identification device acquires the identification number, and updates the identification number in the same method as with the individual identification tag. Accordingly, the individual identification device reads the same identification number as the identification number updated by the individual identification tag at the timing at which a response to the reading instruction is issued. Thus, it is not possible to inhibit the third party from impersonating a legitimate person. 
         [0020]    As one aspect of the present embodiment, provided are solutions for being able to perform: in a system in which the identification number of an electronic tag is managed, inhibiting a third party who possesses an electronic device from impersonating a legitimate person by fraudulently using an identification number. 
         [0021]    Hereinafter, embodiments of a system, program, and, method for information delivery will be described in detail with reference to the accompanying drawings. Note that the present disclosure is not intended to be limited to the embodiments. 
       First Embodiment 
       [0022]      FIG. 1  is a functional block diagram illustrating a functional configuration of a system for information delivery according to a first embodiment. As illustrated in  FIG. 1 , a system  9  for information delivery includes a terminal  1 , an electronic tag  2 , and a server  3 . The system  9  delivers information desired for work in the workplace during working, in accordance with an operation (work) of a worker who possesses the terminal  1 , from the server  3  to the terminal  1  by using a tag ID held by the electronic tag  2 . For example, the system  9  is used for home-visit medical treatment of medical care in the home. That is, the system  9  delivers an electronic health record of a patient, which is used when a doctor visits the home of the patient, from the server  3  to the terminal  1  of the doctor by using a tag ID held by the electronic tag  2 . Note that, hereinafter, the system  9  when used for home-visit medical treatment of medical care in the home will be described. However, by way of example and not of limitation, the system  9  is used for home-visit medical treatment of medical care in the home. 
         [0023]    The terminal  1  has a global positioning system (GPS) functionality and is coupled to the electronic tag  2  and the server  3 . The terminal  1  is coupled via wireless communication to the electronic tag  2 . The wireless communication is, by way of example, wireless fidelity (Wi-Fi; registered trademark) or wireless communication of Bluetooth (registered trademark) standards, or may be any near-distance wireless communication. 
         [0024]    The electronic tag  2  holds a tag identifier (ID)  20  unique to the tag and provides the held tag ID  20  to the terminal  1 . The electronic tag  2  may be, for example, a near-field communication (NFC) tag or a Bluetooth low energy (BLE) beacon, but is not limited thereto. The electronic tag  2  is, by way of example, arranged in the home of a patient. Note that, when the electronic tag  2  is an NFC tag, the tag ID  20  represents an ID held in the user area of the electronic tag  2 . When the electronic tag  2  is a BLE beacon, the tag ID  20  represents an ID of a universally unique identifier (UUID), MAJOR, and MINOR, or the like. 
         [0025]    In addition, the terminal  1  is coupled via a network to the server  3 . The network is, by way of example and not of limitation, the Internet, and may be an intranet or may be a network using a dedicated line. 
         [0026]    In accordance with the work of a worker who possesses the terminal  1 , the server  3  delivers information desired for work to the terminal  1 . The server  3  includes a memory  31 , an authenticity determination unit  32 , a service delivery unit  33 , and a tag ID update unit  34 . 
         [0027]    The memory  31  corresponds to a storage device of a nonvolatile semiconductor memory element, such as, for example, flash memory or Ferroelectric Random Access Memory (FRAM) (registered trademark). The memory  31  includes a tag information database (DB)  311  and a work schedule DB  312 . The tag information DB  311  stores information about the respective electronic tags  2  arranged at a plurality of locations. The work schedule DB  312  stores the respective working schedules of a plurality of workers who use the system  9 . 
         [0028]    With reference to  FIG. 2  and  FIG. 3 , the data structures of the tag information DB  311  and the work schedule DB  312  will be described.  FIG. 2  is a diagram depicting an example of a data structure of a tag information DB. As depicted in  FIG. 2 , the tag information DB  311  stores a tag name  311   a , a tag type  311   b , and a tag ID  311   c  in association with one another. The tag name  311   a  is a name uniquely representing the electronic tag  2 . The tag type  311   b  refers to the tag type of the electronic tag  2 . For the tag type  311   b , “BLE beacon” and “NFC”, which represents an NFC tag, are listed by way of example. The tag ID  311   c  refers to the identifier of the tag ID  20  held in the electronic tag  2 . 
         [0029]    By way of example, when the tag name  311   a  is “Home of patient A”, “BLE beacon” as the tag type  311   b  and “UUID: FFFF . . . MAJOR: 0001 MINOR: 0267” as the tag ID  311 C are stored. 
         [0030]      FIG. 3  is a diagram depicting an example of a data structure of a work schedule DB. As depicted in  FIG. 3 , the work schedule DB  312  stores a work number  312   a , a work name  312   b , a worker  312   c , a work destination  312   d , a work date and time  312   e , and a work location  312   f  in association with one another. The work number  312   a  is a number associated with each work. By way of example, the work number  312   a  is associated with each worker  312   c  and each work destination  312   d . The work name  312   b  represents the name of a work task. The worker  312   c  represents a person who carries out work. The work destination  312   d  represents a location where work is carried out. The work date and time  312   e  represents the date and time when work is carried out. The work location  312   f  represents the location of the work destination  312   d . The work location  312   f  may be an address or may be the latitude and the longitude. 
         [0031]    By way of example, when the work number  312   a  is “555”, “Home-visit medical treatment” as the work name  312   b , “Doctor β” as the worker  312   c , and “Home of patient A” as the work destination  312   d  are stored. As the work date and time  312   e, “ 2015/9/29 11:00” is stored, and, as the work location  312   f, “ 1-1 Z-cho, Y-ku, X-shi”. By referencing the work schedule DB  312 , the terminal  1  is able to search for transitions in the work date and time of a worker who visits the same work destination. 
         [0032]    Returning to  FIG. 1 , the authenticity determination unit  32  determines the authenticity of the tag ID  20 . For example, upon receiving the physical location of the terminal  1  and the tag ID  20  from the terminal  1 , the authenticity determination unit  32  determines the authenticity of the tag ID  20  by referencing the tag information DB  311  and the work schedule DB  312 . By way of example, by referencing the work schedule DB  312 , the authenticity determination unit  32  reads the work destination  312   d  of the work location  312   f  that matches the physical location of the terminal  1 . At the time of referencing the work schedule DB  312 , the work destination  312   d  that corresponds to the work location  312   f , which matches the physical location of the terminal  1 , and to the work date and time  312   e , which matches the current time, may be a target to be read. Here, it is to be noted that the term “match” may be used as a concept that includes not only complete matching but also matching with a difference within a given range. By referencing the tag information DB  311 , the authenticity determination unit  32  reads the tag ID  311   c  of the tag name  311   a  that matches the work destination represented by the read work destination  312   d . That is, in the present embodiment, as depicted in examples of  FIG. 2  and  FIG. 3 , the tag name  311   a  of the tag information DB  311  and the work destination  312   d  of the work schedule DB  312  are associated with each other. The authenticity determination unit  32  compares the tag ID represented by the read tab ID  311   c  with the tag ID  20  received from the terminal  1  to determine whether or not the tag IDs match. Then, if so, the authenticity determination unit  32  determines that the tag ID  20  is authentic. If not, the authenticity determination unit  32  determines that the tag ID  20  is not authentic. When it is determined that the tag ID  20  is authentic, the authenticity determination unit  32  outputs a determination that the tag ID  20  is authentic to the service delivery unit  33 . Note that the method to determine the authenticity is not limited to this and may be a method that uses any related-art technique. 
         [0033]    When receiving the determination that the tag ID  20  is authentic, the service delivery unit  33  delivers a service corresponding to the tag ID  20  to the terminal  1  that has issued a request for determining the authenticity of the tag ID  20 . By way of example, the service delivery unit  33  delivers an electronic health record of a patient corresponding to the tag ID  20  to the terminal  1  that has issued a request for determining the authenticity of the tag ID  20 . 
         [0034]    The tag ID update unit  34  updates the tag information DB  311  by using a new tag ID  20  for which an update request has been issued by the terminal  1 . For example, upon accepting an update request for the new tag ID  20  from the terminal  1 , the tag ID update unit  34  updates, for example, the tag ID  311   c  corresponding to the tag name of the electronic tag  2  contained in the update request, among the tag IDs  311   c  in the tag information DB  311 , with the new tag ID  20 . In other words, the update request may contain, for example, the tag name of the electronic tag  2  and the tag ID. 
         [0035]    Next, the terminal  1  illustrated in  FIG. 1  will be described. The terminal  1  includes a tag ID reading unit  11 , a physical location acquiring unit  12 , a service carry-out unit  13 , a tag ID update unit  14 , and an update request timing determination unit  15 . 
         [0036]    The tag ID reading unit  11  reads the tag ID  20  from the electronic tag  2 . For example, once the terminal  1  enters a range where the terminal  1  is able to communicate wirelessly with the electronic tag  2 , the tag ID reading unit  11  transmits a reading request of the tag ID  20  to the electronic tag  2  and receives the tag ID  20  output from the electronic tag  2 . By way of example, once the terminal  1  carried by a doctor enters a range where the terminal  1  is able to communicate wirelessly with the electronic tag  2  arranged in the home of a patient, the tag ID reading unit  11  transmits a reading request of the tag ID  20  to the electronic tag  2  and reads the tag ID  20  output from the electronic tag  2 . The tag ID reading unit  11  outputs the read tag ID  20  to, for example, the physical location reading unit  12 . 
         [0037]    The physical location acquiring unit  12  acquires the physical location by using, for example, a GPS functionality. The physical location acquiring unit  12  transmits the acquired physical location and the tag ID  20  to the authenticity determination unit  32 . The authenticity of the tag ID  20  is determined by the authenticity determination unit  32 . 
         [0038]    The service carry-out unit  13  carries out a service delivered from the server  3 . By way of example, the service carry-out unit  13  displays an electronic health record of a patient delivered from the server  3  on a monitor of the terminal  1  carried by the doctor. Thereby, the service carry-out unit  13  is able to save the doctor time and energy for displaying the health record of a desired patient, allowing the doctor to smoothly and safely read information related to medical treatment. 
         [0039]    The tag ID update unit  14  updates the tag ID  20  held in the electronic tag  2 . For example, once the service is carried out by the service carry-out unit  13 , the tag ID update unit  14  requests the server  3  to create a new tag ID. By way of example, the tag ID update unit  14  transmits a creation request of a new tag ID, which contains the current tag ID  20  and the physical location acquired by the physical location acquiring unit  12 , to the server  3 . The tag ID update unit  14  overwrites the tag ID  20  of the electronic tag  2  with the new tag ID  20  assigned by the server  2 . Note that, at the time point at which the tag ID update unit  14  overwrites the tag ID  20  of the electronic tag  2  with the new tag ID, the tag ID update unit  34  of the server  3  has not yet overwritten the value of the tag information DB  311  with the new tag ID. Therefore, as a result of update of the electronic tag  2  performed by the tag ID update unit  14 , the tag ID  20  of the electronic tag  2  does not match the tag ID  311   c  of the tag information DB  311  at least until an update request timing described below arrives. The tag ID update unit  14  outputs the overwritten new tag ID  20  to the update request timing determination unit  15 . 
         [0040]    At a given timing, the update request timing determination unit  15  requests the server  3  to perform update with the new tag ID  20  that has been updated by the tag ID update unit  14 . For example, the update request timing determination unit  15  references the work schedule DB  312  and, at any timing before the next reading of the tag ID  20  from this electronic tag  2 , requests the server  3  to perform update with the new tag ID  20 . The given timing is, for example, immediately before the date and time (the data and time of work) at which a worker next visits this work destination to carry out work. Thereby, the update request timing determination unit  15  is able to learn the work destination (the tag name) from the work schedule DB  312 . In other words, in the present embodiment, since the tag name  311   a  of the tag information DB  311  is associated with the work destination  312   d  of the work schedule DB  312 , the update request timing determination unit  15  is able to learn the tag name  311   a  from the work destination  312   d  by referencing the work schedule DB  312 . 
         [0041]    The determination of whether or not the time is immediately before the date and time of the next visit is made, for example, as follows. By way of example, when work is not shared with another person, the update request timing determination unit  15  references the work schedule DB  312  and acquires the work date and time  312   e  and the work location  312   f  of the next work schedule from among records that correspond to the worker  312   c  who is currently working and the work destination  312   d  of the current work. That is, when work is not shared with another person, the update request timing determination unit  15  acquires a timing at which the same worker as the worker who is currently working will next visit the same work destination to carry out the same work. In addition, when work is shared with another person, the update request timing determination unit  15  references the work schedule DB  312  and acquires the work date and time  312   e  and the work location  312   f  of the record of the next work schedule, among records that correspond to the worker  312   c  who currently shares work and the work destination  312   d  of the currently shared work. That is, when work is shared with another person, the update request timing determination unit  15  acquires a timing at which a worker who currently shares work will next visit the same work destination to carry out the same work. Further, if the update request timing determination unit  15  acquires only the work date and time  312   e , the update request timing determination unit  15  issues a request for update with the new tag ID  20  a specified amount of time prior to the work date and time  312   e . By way of example and not of limitation, the specified amount of time is 30 minutes. If the update request timing determination unit  15  acquires only the work location  312   f , the update request timing determination unit  15  issues a request for update with the new tag ID  20  when the next worker  312   c  is close, within a specified distance, to the work location  312   f . By way of example and not of limitation, the specified distance is 1 km. If the update request timing determination unit  15  acquires the work date and time  312   e  and the work location  312   f , the update request timing determination unit  15  issues a request for update with the new tag ID  20  when the next worker  312   c  is close at the specified distance to the work location  312   f  the specified amount of time prior to the work date and time  312   e.    
         [0042]    With reference to  FIG. 4 , an example of a procedure of a process for information delivery according to the first embodiment will be described.  FIG. 4  is a diagram illustrating an example of a flowchart of a process for information processing according to the first embodiment. The terminal  1  is assumed to enter a range where the terminal  1  is able to communicate wirelessly with the electronic tag  2 . 
         [0043]    As illustrated in  FIG. 4 , in the terminal  1 , the tag ID reading unit  11  reads the tag ID  20  from the electronic tag  2  (S 11 ). The physical location acquisition unit  12  acquires the physical location of the terminal  1 , transmits the acquired physical location and the tag ID  20  to the server  3 , and requests the server  3  to determine the authenticity of the tag ID  20  (S 12 ). 
         [0044]    In the server  3 , the authenticity determination unit  32  references the tag information DB  311  and the work schedule DB  312  to determine the authenticity of the tag ID  20  (S 13 ). The authenticity determination unit  32  determines whether or not the tag ID  20  is authentic (S 14 ). If it is determined that the tag ID  20  is authentic (Yes in S 14 ), the service delivery unit  33  delivers a service corresponding to the tag ID  20  to the terminal  1  (S 15 ). On the other hand, if it is determined that the tag ID  20  is not authentic (No in S 14 ), the service delivery unit  33  terminates the process for information delivery. 
         [0045]    In the terminal  1 , the service carry-out unit  13  determines whether or not delivery of a service has been accepted (S 16 ). If it is determined that delivery of a service has not been accepted (No in S 16 ), the service carry-out unit  13  terminates the process for information delivery. On the other hand, if it is determined that delivery of a service has been accepted (Yes in S 16 ), the service carry-out unit  13  carries out the accepted service (S 17 ). 
         [0046]    The tag ID update unit  14  requests the server  3  to create a new tag ID (S 18 ). The tag ID update unit  14  acquires the new tag ID created by the server  3  from the server  3  (S 19 ). The tag ID update unit  14  overwrites the tag ID  20  of the electronic tag  2  with the new tag ID (S 20 ). The update request timing determination unit  15  determines an update request timing with the new tag ID  20  (S 21 ). Note that an update request timing determination process will be described below. 
         [0047]    Further, at the update request timing determined in the update request timing determination process, the update request timing determination unit  15  requests the server  3  to perform update with the new tag ID  20  (S 22 ). 
         [0048]    In the server  3 , the tag ID update unit  34  updates the tag information DB  311  with the new tag ID  20 , with which the server  3  has been requested to perform update by the terminal  1  (S 23 ). 
         [0049]    With reference to  FIG. 5 , an example of a procedure of an update request timing determination process according to the first embodiment will be described.  FIG. 5  is a diagram illustrating an example of a flowchart of an update request timing determination process according to the first embodiment. 
         [0050]    The update request timing determination unit  15  determines whether or not work is shared with another person (S 31 ). For example, the update request timing determination unit  15  makes the determination, by reference to the work schedule DB  312 , depending on whether or not, among records that match in terms of the work name and the work destination of the work that is currently being carried out, any one record differs from the other records in terms of the worker  312   c.    
         [0051]    If it is determined that the work is not shared with another person (No in S 31 ), the update request timing determination unit  15  references the work schedule DB  312  and acquires the work date and time and the work location of the next schedule corresponding to the same worker and to the same work destination (S 32 ). For example, the update request timing determination unit  15  references the work schedule DB  312  and acquires the work date and time  312   e  and the work location  312   f  of a record of the next work schedule, among records corresponding to the worker  312   c  who is currently working and to the work destination  312   d  of the current work. Then, the update request timing determination unit  15  proceeds to S 34 . 
         [0052]    On the other hand, if it is determined that the work is shared with another person (Yes in S 31 ), the update request timing determination unit  15  acquires the work date and time and the work location of the next schedule corresponding to a worker who shares the work and to the same work destination (S 33 ). For example, the update request timing determination unit  15  references the work schedule DB  312  and acquires, among records corresponding to the worker  312   c  who currently shares the work and to the work destination  312   d  of the current work, the work date and time  312   e  and the work location  312   f  of a record of the next work schedule. Then, the update request timing determination unit  15  proceeds to S 34 . 
         [0053]    The update request timing determination unit  15  determines whether or not both the work date and time and the work location have been acquired (S 34 ). If it is determined that both the work date and time and the work location have been acquired (Yes in S 34 ), the update request timing determination unit  15  assumes the update request timing to be a time that is the specified amount of time prior to the work date and time and at which the worker enters the range of the specified distance to the work location (S 35 ). Then, the update request timing determination unit  15  terminates the update request timing determination process. 
         [0054]    On the other hand, if it is determined that both the work date and time and the work location have not been acquired (No in S 34 ), the update request timing determination unit  15  determines whether or not only the work date and time has been acquired (S 36 ). If it is determined that only the work date and time has been acquired (Yes in S 36 ), the update request timing determination unit  15  assumes the update request timing to be a time that is the specified amount of time prior to the work date and time (S 37 ). Then, the update request timing determination unit  15  terminates the update request timing determination process. 
         [0055]    On the other hand, if it is determined that only the work date and time has not been acquired (No in S 36 ), the update request timing determination unit  15  determines whether or not only the work location has been acquired (S 38 ). If it is determined that only the work location has been acquired (Yes in S 38 ), the update request timing determination unit  15  assumes the update request timing to be a time at which the worker enters the range of the specified distance to the work location (S 39 ). Then, the update request timing determination unit  15  terminates the update request timing determination process. 
         [0056]    On the other hand, if it is determined that only the work location has not been acquired (No in S 38 ), the update request timing determination unit  15  assumes the update request timing to be the current time point (S 40 ). Then, the update request timing determination unit  15  terminates the update request timing determination process. 
         [0057]    In this way, in the first embodiment described above, the system  9  includes the terminal  1 , the electronic tag  2 , and the server  3 . The terminal  1  reads the tag ID  20  from the electronic tag  2  and updates the tag ID  20  in the electronic tag  2  with a new tag ID  20  that is different from the read tag ID  20 . The terminal  1  references the work schedule DB  312  and, at a timing before the next reading of the tag ID  20  from the electronic tag  2 , requests the server  3  to perform update with the updated tag ID  20 . Upon requested to perform update by the terminal  1 , the server  3  updates the tag information DB  311  with the updated tag ID  20 . According to such a configuration, each time the user uses information delivery, the system  9  updates the tag ID  20  of the electronic tag  2  and avoids reflecting the update in the server  3  until a timing before the tag ID  20  is next read from the electronic tag  2 . Accordingly, even if a third party copies the tag ID  20  read from another terminal  1  possessed by the third party or by the terminal  1  that has been stolen, it is possible to inhibit the third party from impersonating a legitimate person by using the copied tag ID  20 . That is, the system  9  determines the timing at which the tag ID  20  updated in the electronic tag  2  is to be reflected in the tag information DB  311  of the server  3 , and performs update. Therefore, the tag ID  20  is not able to be used until the update timing. This makes it possible to improve the safety. In addition, the system  9  implements such a configuration without adding hardware to the electronic tag  2 , making it possible to implement the configuration at low cost. 
       Second Embodiment 
       [0058]    Description has been given of the system  9  according to the first embodiment in which, at the given timing, the terminal  1  requests the server  3  to perform update with the new tag ID  20  that has been updated in the electronic tag  2  and, upon receipt of the update request, the server  3  reflects the new tag ID  20 . However, in the system  9 , which is not limited to this, although, upon receipt of an update request, the server  3  performs update with the new tag ID  20 , the server  3  may enable the updated tag ID  20  at a given timing. 
         [0059]    Accordingly, description will be given of the case where, in the system  9  according to the second embodiment, although, upon receipt of an update request, the server  3  performs update with the new tag ID  20 , the server  3  enables the updated tag ID  20  at a given timing. 
         [0060]      FIG. 6  is a block diagram illustrating a functional configuration of a system for information delivery according to the second embodiment. Note that the same configurations as in the system  9  illustrated in  FIG. 1  are denoted by the same reference numerals and thus the overlapping configurations and operations are not described. In the terminal  1 , the first embodiment differs from the second embodiment in that the update request timing determination unit  15  is removed. In the server  3 , the first embodiment differs from the second embodiment in that a tag ID enable timing determination unit  35  is added. The embodiments also differ in that a tag information DB  311 A is changed. 
         [0061]    Here, the data structure of the tag information DB  311 A will be described with reference to  FIG. 7 .  FIG. 7  is a diagram depicting an example of a data structure of a tag information DB. As depicted in  FIG. 7 , the tag information DB  311 A stores the tag name  311   a , the tag type  311   b , the tag ID  311   c , and an enable  311   d  in association with one another. The tag name  311   a  is a name uniquely representing the electronic tag  2 . The tag type  311   b  refers to the tag type of the electronic tag  2 . For the tag type  311   b , by way of example, “BLE beacon” and “NFC”, which represents an NFC tag, are listed. The tag ID  311   c  refers to an identifier of the tag ID  20  held in the electronic tag  2 . The enable  311   d  is a flag indicating whether or not the tag ID represented by the tag ID  311   c  is enabled or disabled. For the enable  311   d , by way of example, “TRUE” representing that the tag ID is enabled, and “FALSE” representing that the tag ID is disabled are listed. 
         [0062]    By way of example, when the tag name  311   a  is “Home of patient A”, “BLE beacon” as the tag type  311   b , “UUID: FFFF . . . MAJOR: 0001 MINOR: 0267” as the tag ID  311   c , and “TRUE” as the enable  311   d  are stored. 
         [0063]    The tag ID update unit  14  updates the tag ID  20  held in the electronic tag  2 . For example, once a service is carried out by the service carry-out unit  13 , the tag ID update unit  14  requests the server  3  to create a new tag ID. By way of example, the tag ID update unit  14  transmits a creation request of a new tag ID, which contains the current ID  20  and a physical location acquired by the physical acquiring unit  12 , to the server  3 . Further, the tag ID update unit  14  overwrites the tag ID  20  of the electronic tag  2  with a new tag ID assigned by the server  3 . 
         [0064]    In addition, the tag ID update unit  14  requests the server  3  to perform update with the overwritten new tag ID  20 . 
         [0065]    The tag ID update unit  34  updates the tag information DB  311 A with the new tag ID  20  with which a request for update has been issued by the terminal  1 . For example, upon accepting an update request of the new tag ID  20  from the terminal  1 , the tag ID update unit  34  updates the tag information DB  311 A such that the tag ID  311   c  corresponding to the tag name of the electronic tag  2  contained in the update request is updated with the new tag ID  20 . 
         [0066]    At a given timing, the tag ID enable timing determination unit  35  enables the new tag ID  20  with which the update has been performed by the tag ID update unit  34 . For example, regarding the new tag ID  20  updated by the tag ID update unit  34 , the tag ID enable timing determination unit  35  references the work schedule DB  312  and enables the tag ID  20  at a timing before the next reading of the tag ID  20  from the electronic tag  2 . The given timing is immediately before a worker next visits this work destination in order to carry out work. 
         [0067]    The determination of whether or not the time is immediately before the next visit is made, for example, as follows. By way of example, when work is not shared with another person, the tag ID enable timing determination unit  35  references the work schedule DB  312  and acquires, among records that correspond to the worker  312   c  who is currently working and to the work destination  312   d  of the current work, the work date and time  312   e  and the work location  312   f  of a record of the next work schedule. That is, when work is not shared with another person, the tag ID enable timing determination unit  35  acquires a timing at which the same worker as the worker who is currently working next visits the same work destination for the same work. In addition, when work is shared with another person, the tag ID enable timing determination unit  35  references the work schedule DB  312  and acquires, among records that correspond to the worker  312   c  who currently shares work and the work destination  312   d  of the current work, the work date and time  312   e  and the work location  312   f  of a record of the next work schedule. That is, when work is shared with another person, the tag ID enable timing determination unit  35  acquires a timing at which a worker who currently shares work next visits the same work destination for the same work. Further, when acquiring only the work date and time  312   e , the tag ID enable timing determination unit  35  enables the new tag ID  20  a specified amount of time prior to the work date and time  312   e . By way of example but not of limitation, the specified amount of time is 30 minutes. When acquiring only the work location  312   f , the tag ID enable timing determination unit  35  enables the new tag ID  20  when the next worker  312   c  is close, within a specified distance, to the work location  312   f . By way of example but not of limitation, the specified distance is 1 km. When acquiring the work date and time  312   e  and the work location  312   f , the tag ID enable timing determination unit  35  enables the new tag ID  20  when the next worker  312   c  is close at the specified distance to the work location  312   f  the specified amount of time prior to the work date and time  312   e.    
         [0068]    Next, an example of a processing procedure of a process for information delivery according to the second embodiment will be described with reference to  FIG. 8 .  FIG. 8  is a diagram illustrating an example of a flowchart of a process for information delivery according to the second embodiment. Note that the same steps as in the flowchart of the process for information delivery illustrated in  FIG. 4  are denoted by the same reference numerals and the overlapping steps are simply described or are not described. The terminal  1  is assumed to enter a range where the terminal  1  is able to communicate wirelessly with the electronic tag  2 . 
         [0069]    As illustrated in  FIG. 8 , in the terminal  1 , the tag ID reading unit  11  reads the tag ID  20  from the electronic tag  2  (S 11 ). The physical location acquiring unit  12  acquires the physical location of the terminal  1 , transmits the acquired physical location together with the tag ID  20  to the server  3 , and requests the server  3  to determine the authenticity of the tag ID  20  (S 12 ). 
         [0070]    In the server  3 , the authenticity determination unit  32  references the tag information DB  311 A and the work schedule DB  312  to determine the authenticity of the tag ID  20  (S 13 ). The authenticity determination unit  32  determines whether or not the tag ID  20  is authentic (S 14 ). If it is determined that the tag ID  20  is authentic (Yes in S 14 ), the service delivery unit  33  delivers a service corresponding to the tag ID  20  to the terminal  1  (S 15 ). On the other hand, if it is determined that the tag ID  20  is not authentic (No in S 14 ), the service delivery unit  33  terminates the process for information delivery. 
         [0071]    In the terminal  1 , the service carry-out unit  13  determines whether or not delivery of a service has been accepted (S 16 ). If it is determined that delivery of a service has not been accepted (No in S 16 ), the service carry-out unit  13  terminates the process for information delivery. On the other hand, if it is determined that delivery of a service has been accepted (Yes in S 16 ), the service carry-out unit  13  carries out the accepted service (S 17 ). 
         [0072]    The tag ID update unit  14  requests the server  3  to create a new tag ID (S 18 ). The tag ID update unit  14  acquires a new tag ID created by the server  3  from the server  3  (S 19 ). The tag ID update unit  14  overwrites the tag ID  20  of the electronic tag  2  with the new tag ID (S 20 ). 
         [0073]    Further, the tag ID update unit  14  requests the server  3  to perform update with the overwritten new tag ID  20  (S 22 ). 
         [0074]    In the server  3 , the tag ID update unit  34  updates the tag information DB  311 A with the new tag ID  20  with which a request for update has been issued by the terminal  1  (S 23 ). Further, the tag ID enable timing determination unit  35  determines an enable timing of the new tag ID  20  (S 24 ). Note that the enable timing determination process is the same as steps of the update request timing determination process illustrated in  FIG. 5  and the overlapping steps are not described. 
         [0075]    Further, the tag ID enable timing determination unit  35  enables the new tag ID  20  at the determined enable timing (S 25 ). For example, for the tab information DB  311 A, the tag ID enable timing determination unit  35  sets the enable  311   d  corresponding to the tag ID  311   c  that matches the new tag ID  20  to be “TRUE”, which indicates that the tag ID is enabled. 
         [0076]    In this way, in the second embodiment described above, the system  9  includes the terminal  1 , the electronic tag  2 , and the server  3 . The terminal  1  reads the tag ID  20  from the electronic tag  2  and, for the electronic tag  2 , updates the read tag ID  20  with a tag ID  20  that is different from the tag ID  20  in question. The terminal  1  requests the server  3  to perform update with the updated tag ID  20 . The server  3  updates the tag information DB  311 A with the updated tag ID  20 . Further, the server  3  references the work schedule DB  312  and enables the updated tag ID  20  at a timing before the next reading of the tag ID  20  from the electronic tag  2 . With such a configuration, each time the user uses information delivery, the system  9  updates the tag ID  20  of the electronic tag  2  and avoids reflecting the update in the server  3  until a timing before the next reading of the tag ID  20  from the electronic tag  2 . Accordingly, even if a third party copies the tag ID  20  read from another terminal  1  possessed by the third party or the terminal  1  that has been stolen, it is possible to inhibit the third party from impersonating a legitimate person by using the copied tag ID  20 . That is, after determining the timing at which the tag ID  20  updated in the electronic tag  2  is to be reflected in the tag information DB  311 A of the server  3 , the system  9  enables the tag ID  20 . Therefore, the tag ID  20  is not able to be used until the timing of enabling. This makes it possible to improve the safety. In addition, the system  9  implements such a configuration without adding hardware to the electronic tag  2 , making it possible to implement the configuration at low cost. 
         [0077]    Note that it has been described that the update request timing determination unit  15  of the terminal  1  according to the first embodiment references the work schedule DB  312  stored in the server  3  to, at a timing before the next reading of the tag ID  20  from this electronic tag  2 , request the server  3  to perform update with the new tag ID  20 . However, the update request timing determination unit  15  may reference a work schedule DB stored in the terminal  1  to, at a timing before the next reading of the tag ID  20  from this electronic tag  2 , request the server  3  to perform update with the new tag ID  20 . The work schedule DB stored in the terminal  1  may be, by way of example, transferred from the server  3  at a time point at which the work schedule DB  312  of the server  3  is changed. This allows the update request timing determination unit  15  to acquire the update timing of a new tag ID without having a communication load. 
         [0078]    In addition, all of the components of devices illustrated in the drawings do not necessarily have to be physically configured as illustrated in the drawings. That is, specific manners of distribution and integration of devices are not limited to those illustrated in the drawings, and all or some of the devices may be configured so as to be functionally or physically distributed and integrated at arbitrary units in accordance with various types of loads and usage states. For example, the update request timing determination unit  15  may be divided into the case where work is not shared with another person and the case where work is shared. In addition, the memory  31  may be coupled as an external device of the server  3  via a network. 
         [0079]    In addition, various types of processing described in the above embodiments may be implemented by programs prepared in advance executed by a computer, such as a personal computer or a work station. Accordingly, hereinafter, description will be given of an example of a computer that executes a program for information delivery that implements functionalities similar to those of the terminal  1  and the server  3  illustrated in  FIG. 1 .  FIG. 9  is a diagram illustrating an example of a computer that executes a program for information delivery. 
         [0080]    As illustrated in  FIG. 9 , a computer  200  includes a central processing unit (CPU)  203  that executes various types of arithmetic processing, an input device  215  that accepts input of data from the user, and a display control unit  207  that controls a display device  209 . The computer  200  also includes a drive device  213  that reads a program and the like from a recording medium, and a communication control unit  217  that transmits and receives data to and from another computer over a network. The computer  200  also includes a memory  201  that temporarily stores various types of information, and a hard disk drive (HDD)  205 . Further, the memory  201 , the CPU  203 , the HDD  205 , the display control unit  207 , the drive device  213 , the input device  215 , and the communication control unit  217  are coupled by a bus  219 . 
         [0081]    The drive device  213  is a device for, for example, a removable disk  211 . 
         [0082]    The CPU  203  reads a program  205   a  for information delivery, loads the program  205   a  onto the memory  201 , and executes the program  205   a  as a process. Such a process corresponds to each of function units of the terminal  1  and the server  3 . Information delivery-related information  205   b  corresponds to the tag information DB  311  and the work schedule DB  312  in the server  3 . Further, for example, the removable disk  211  stores various types of information, such as the program  205   a  for information delivery. 
         [0083]    Note that the program  205   a  does not necessarily have to be originally stored in the HDD  205 . For example, the program is stored in a “portable physical medium”, such as a floppy disk (FD), a compact disk read-only memory (CD-ROM), a digital video disk (DVD), an optical magnetic disk, or an integrated circuit (IC) card, which is inserted in the computer  200 . Further, the computer  200  may read and execute the program  205   a  from such a medium. 
         [0084]    All examples and conditional language recited herein are intended for pedagogical purposes to aid the reader in understanding the invention and the concepts contributed by the inventor to furthering the art, and are to be construed as being without limitation to such specifically recited examples and conditions, nor does the organization of such examples in the specification relate to a showing of the superiority and inferiority of the invention. Although the embodiments of the present invention have been described in detail, it should be understood that the various changes, substitutions, and alterations could be made hereto without departing from the spirit and scope of the invention. For example, the steps recited in any of the method or process descriptions may be executed in any order and are not limited to the order presented.