Source: http://www.google.com/patents/US20060143452?dq=4200770
Timestamp: 2016-09-26 21:48:03
Document Index: 309447375

Matched Legal Cases: ['Application No. 2003', 'Application No. 2001', 'Application No. 2001', 'Application No. 2001', 'art 302', 'art 304', 'art 305', 'art 305', 'art 352', 'art 352']

Patent US20060143452 - Verifying the ownership of an owner's authority in terms of product and service - Google PatentsSearch Images Maps Play YouTube News Gmail Drive More »Sign inPatentsThe present invention provides an apparatus for verifying the authority of an owner, in terms of an identifier of a product, the first verification information for verifying the authority held at a terminal for an owner with the authority involving the product, and the second verification information...http://www.google.com/patents/US20060143452?utm_source=gb-gplus-sharePatent US20060143452 - Verifying the ownership of an owner's authority in terms of product and serviceAdvanced Patent SearchTry the new Google Patents, with machine-classified Google Scholar results, and Japanese and South Korean patents.Publication numberUS20060143452 A1Publication typeApplicationApplication numberUS 11/319,892Publication dateJun 29, 2006Filing dateDec 28, 2005Priority dateDec 28, 2004Also published asCN1797500A, CN1797500B, US7657740, US8618905, US20080272882Publication number11319892, 319892, US 2006/0143452 A1, US 2006/143452 A1, US 20060143452 A1, US 20060143452A1, US 2006143452 A1, US 2006143452A1, US-A1-20060143452, US-A1-2006143452, US2006/0143452A1, US2006/143452A1, US20060143452 A1, US20060143452A1, US2006143452 A1, US2006143452A1InventorsMasayuki Numao, Yoshinobu Ishigaki, Yuji WatanabeOriginal AssigneeInternational Business Machines CorporationExport CitationBiBTeX, EndNote, RefManPatent Citations (51), Referenced by (10), Classifications (5), Legal Events (4) External Links: USPTO, USPTO Assignment, EspacenetVerifying the ownership of an owner's authority in terms of product and service
US 20060143452 A1Abstract
The present invention provides an apparatus for verifying the authority of an owner, in terms of an identifier of a product, the first verification information for verifying the authority held at a terminal for an owner with the authority involving the product, and the second verification information for verifying the authority concerning the identifier of the product stored in a product database. The apparatus comprises means for receiving the identifier and the first verification information, means for acquiring the second verification information from the product DB, and means for determining whether or not there is the authority from the first verification information and the second verification information. A hash value acquired from a one-way hash function is employed as a verification key of the verification information. Images(8) Claims(37)
1) An apparatus for verifying authority of at least one owner comprising: means for receiving an identifier of a product and first verification information, said apparatus for verifying the authority in terms of the identifier of a product, first verification information for verifying the authority held at a terminal for the owner with the authority involving said product, and second verification information for verifying the authority concerning the identifier of said product stored in a product database, means for acquiring said second verification information from said product database; and means for determining whether or not there is the authority from said first verification information and said second verification information. 2) The apparatus for verifying the authority according to claim 1, wherein said means for determining comprises determination means by using a hash value acquired by applying a one-way hash function to a number acquired by a predetermined method by t (an integer of 1 or more) times as a verification key for verifying information, and by using a hash value acquired by applying said one-way hash function to said number by t−1 times as a verification key for verifying information for the next verification. 3) The apparatus for verifying the authority according to claim 2, further comprising means for encrypting by using said hash value acquired by applying the hash function to the number by t−1 times as an encryption key when verifying information for verifying said authority is received from said terminal. 4) The apparatus for verifying the authority according to claim 3, wherein said encryption is performed by acquiring an exclusive OR of said verification key and said hash value acquired by applying the hash function to the number by t−1 times. 5) The apparatus for verifying the authority according to claim 1, wherein said terminal of an owner with the authority saves said identifier of the product. 6) The apparatus for verifying the authority according to claim 1, wherein said terminal of an owner with the authority comprises means for reading said identifier of the product. 7) The apparatus for verifying the authority according to claim 1, further comprising means for saving a list showing that a product has a plurality of owners and a verification key for each of the owners of the authority. 8) An apparatus for verifying the authority in terms of an identifier of a product, a verification key for verifying the authority held at a terminal for an assignor of the authority involving said product, and the verification information of the assignor concerning the identifier of said product stored in a product database, comprising: means for receiving a verification key of an assignee with said authority and the verification key of the assignor with the authority held at said terminal; means for acquiring the verification key of said assignor from said product database; means for verifying the verification key of said assignor in terms of the verification information involving said product; and means for storing the verification key of said assignee as said verification information of said product database under the condition that said verification is successful. 9) The apparatus for verifying the authority according to claim 8, wherein said verification means further comprises means for using a hash value acquired by applying a one-way hash function to the number acquired by a predetermined method in a terminal of said assignee by t (an integer of 1 or more) times as a verification key for said verifying information, and using a hash value acquired by applying said one-way hash function by u (an integer of 1 or more) times to the number acquired by a predetermined method in the terminal of said assignee as a verification key for the next verification. 10) The apparatus for verifying the authority according to claim 9, further comprising means for encrypting by using the hash value acquired by applying the hash function to the number acquired by a predetermined method in a terminal of said assignee by t−1 times as an encryption key when said verifying information is received from a terminal of said owner with the authority. 11) The apparatus for verifying the authority according to claim 10, wherein said encryption is performed by acquiring an exclusive OR of said verification key and said hash value acquired by applying the hash function to the number by t−1 times. 12) The apparatus for verifying the authority according to claim 1, wherein said product is a service ticket for a user to receive a service. 13) A terminal for managing the information regarding the authority of at least one owner involving a product, comprising: means for storing the first verification information managed separately from an identifier of the product; and means for creating a one-time verification key from the first verification information that is used for verification in an apparatus for verifying the authority in terms of the second verification information involving said product stored in a product database. 14) The terminal for saving information for verifying the authority in terms of a product according to claim 13, wherein said one-time verification key uses a hash value acquired by applying a one-way hash function to the number acquired by a predetermined method by t (an integer of 1 or more) times as a verification key for verifying information, and uses a hash value acquired by applying said one-way hash function to said number by t−1 times as a verification key for the next verification. 15) The terminal for saving information for verifying the authority in terms of a product according to claim 14, further comprising means for encrypting said verification key by using said hash value acquired by applying the hash function to the number by t−1 times as an encryption key. 16) The terminal for saving information for verifying the authority in terms of a product according to claim 13, wherein a terminal that saves information for verifying the authority in terms of a product comprises means for reading an identifier for identifying said product. 17) The terminal for saving information for verifying the authority in terms of a product according to claim 13, wherein said product is a service ticket for a user to receive a service. 18) A method for verifying the authority of at least one owner in terms of an identifier of a product, the first verification information for verifying the authority held at a terminal for an owner with the authority involving said product, and the second verification information for verifying the authority concerning the identifier of said product stored in a product database, comprising: a step of receiving said identifier and said first verification information; a step of acquiring said second verification information from said product DB; and a step of determining whether or not there is the authority from said first verification information and said second verification information. 19) The method for verifying the authority according to claim 18, wherein said step of determining comprises a step of determining by using a hash value acquired by applying a one-way hash function to a number acquired by a predetermined method by t (an integer of 1 or more) times as a verification key for verifying information, and by using a hash value acquired by applying said one-way hash function to said number by t−1 times as a verification key for verifying information for the next verification. 20) The method for verifying the authority according to claim 19, further comprising a step of encrypting by using said hash value acquired by applying the hash function to the number by t−1 times as an encryption key when verifying information for verifying said authority is received from said terminal. 21) The method for verifying the authority according to claim 20, wherein said encryption is performed by acquiring an exclusive OR of said verification key and said hash value acquired by applying the hash function to the number by t−1 times. 22) The method for verifying the authority according to claim 18, wherein said terminal of an owner with the authority saves said identifier of the product. 23) The method for verifying the authority according to claim 18, wherein said terminal of an owner with the authority comprises a step of reading said identifier of the product. 24) The method for verifying the authority according to claim 18, further comprising a step of saving a list showing that a product has a plurality of owners and a verification key for each of the owners of the authority. 25) A method for verifying the authority of at least one owner in terms of an identifier of a product, a verification key for verifying the authority held at a terminal for an assignor with the authority involving said product, and the verification information of the assignor concerning the identifier of said product stored in a product database, comprising: a step of receiving a verification key of an assignee with said authority and said verification key of the assignor with the authority held at said terminal; a step of acquiring said verification key of the assignor from said product DB; a step of verifying the verification key of said assignor in terms of the verification information involving said product; and a step of storing the verification key of said assignee as said verification information of said product DB under the condition that said verification is successful. 26) The method for verifying the authority according to claim 25, wherein said verification step further comprises a step of using a hash value acquired by applying a one-way hash function to the number acquired by a predetermined method in a terminal of said assignee by t (an integer of 1 or more) times as a verification key for said verifying information, and using a hash value acquired by applying said one-way hash function by u (an integer of 1 or more) times to the number acquired by a predetermined method in the terminal of said assignee as a verification key for the next verification. 27) The method for verifying the authority according to claim 26, further comprising a step of encrypting by using the hash value acquired by applying the hash function to the number acquired by a predetermined method in a terminal of said assignee by t−1 times as an encryption key when said verifying information is received from a terminal of said owner with the authority. 28) The method for verifying the authority according to claim 27, wherein said encryption is performed by acquiring an exclusive OR of said verification key and said hash value acquired by applying the hash function to the number by t−1 times. 29) The method for verifying the authority according to claim 18, wherein said product is a service ticket for a user to receive a service. 30) A method for managing the information regarding the authority of at least one owner involving a product at a terminal, comprising: a step of storing the first verification information managed separately from an identifier of the product; and a step of creating a one-time verification key from the first verification information that is used for verification in an apparatus for verifying the authority in terms of the second verification information involving said product stored in a product database. 31) The method for managing information relating to the authority in terms of a product in a terminal according to claim 30, wherein said one-time verification key uses a hash value acquired by applying a one-way hash function to the number acquired by a predetermined method by t (an integer of 1 or more) times as a verification key for verifying information, and uses a hash value acquired by applying said one-way hash function to said number by t−1 times as a verification key for the next verification. 32) The method for managing information relating to the authority in terms of a product in a terminal according to claim 31, further comprising a step of encrypting said verification key by using said hash value acquired by applying the hash function to the number by t−1 times as an encryption key. 33) The method for managing information relating to the authority in terms of a product in a terminal according to claim 30, wherein a terminal device that saves information for verifying the authority in terms of a product comprises a step of reading an identifier for identifying said product. 34) The method for managing information relating to the authority in terms of a product in a terminal according to claim 30, wherein said product is a service ticket for a user to receive a service. 35) A program storage device readable by machine, tangibly embodying a program of instructions executable by the machine to perform method steps for verifying authority of at least one owner, said method steps comprising the steps of claim 18. 36) A program storage device readable by machine, tangibly embodying a program of instructions executable by the machine to perform method steps for verifying authority of at least one owner, said method steps comprising the steps of claim 25. 37) A computer program product comprising a computer usable medium having computer readable program code means embodied therein for causing a verification of authority of at least one owner, the computer readable program code means in said computer program product comprising computer readable program code means for causing a computer to effect the functions of claim 1. Description
FIELD OF THE INVENTION [0001] The present invention relates to an apparatus, a method and a program for verifying the authority of a person as to whether or not the person is entitled to gain access to the information regarding a manufacturing process or circulation of a product or a service in the case of managing the product or service with RFID (Radio Frequency Identification), an IC tag, a two-dimensional bar code or any other identifier. BACKGROUND ART [0002] In the distributing industry, means of managing products (goods) are shifting from barcodes or the like to RFID (Radio Frequency Identification) using wireless chips or the like. The RFID is drawing attention as the important technique not only in promoting efficiency of stock and distribution of products but also in promoting the information technology and the automation technology, as wireless chips are added to various products in using the RFID. The RFID may be used for enabling a purchaser to search information on a food product he bought such as its producing region, its producer or its processor based on RFID data, or for a user to automatically list up foods stored in his refrigerator and notice him of expiration date of the foods. In order to put the RFID into widespread use, the RFID must be inexpensively supplied and used. [0003] In order to inexpensively supply and use the RFID, the most feasible option of the RFID is that the RFID made to save only product identifying information such as ID information, with information on product such as the producer and tracking information of the distribution channel being recorded in a product database (DB) server or the like and referenced by the product ID information. Practically, product ID information is read through a tag reader, sent to the product DB server to enable information on the product information to be accessed. In such a case, an authorized owner of an authority must be assured to access the information and an abuser must be prevented from acquiring product information, from distributing fake products, or from interfering a traceability system with fake goods or the like. [0004] The following documents are considered: [Patent Document 1] National Publication of International Patent Application No. 2003-524242 [Patent Document 2] Published Unexamined Patent Application No. 2001-184312 [Patent Document 3] Published Unexamined Patent Application No. 2001-160177 [Patent Document 4] Published Unexamined Patent Application No. 2001-160177 [Non-patent Document 1] A. Juels and J. Brainard, “Soft Blocking: Flexible Blocker Tags on the Cheap,” URL: http://www.rsasecurity.com/rsalabs/staff/bios/ajuels/publications/softblocker/softblocker.pdf. [0010] Patent Document 1 describes a method for providing a tag chip with two storage areas of a tag address and a security block and verifying a tag address usually read as RFID by comparing the tag with the second security block. A tag reader first reads a tag address, encrypts the tag address with a secret key it holds, and verifies the tag address by comparing the encrypted result and a value in the security block. Patent Document 2 discloses a method for saving verifying information in the tag and making a reader verify the owner with the authority by using the verifying information. This method saves information on a face image, a signature or a password in a tag for locally verifying the owner. Patent Document 2 shows a system for providing RFID to both a user and a confidential document and allowing a user to copy or the like the document only if the security level of the RFID owned by the user is higher than that of the RFID tag added to the confidential document. Patent Document 4 shows that a wireless tag stores goods identifiers and goods secret keys, creates goods digital signature by using the goods secret key or the like, and sends the goods digital signature to a verifying computer for verification. Non Patent Document 1 shows a method for controlling the reading of RFID added to a product with another RFID tag called Blocker tag by using a multi-accessing function of a reader. PROBLEMS TO BE SOLVED BY THE INVENTION [0011] The abovementioned techniques, however, cannot sufficiently prevent an abuser from accessing a product DB by using an unauthorized copy of an RFID tag. Even if the techniques can prevent an RFID tag from being illegally copied, they cost high. The technique described in Patent Document 1 is ineffective against an attack that uses a duplicated tag made by copying both a tag address and a security block. As the technique always uses the same tag address and the same security block, it is vulnerable to replay attacks. The technique described in Patent Document 2 is appropriate for a bank card or the like, where an owner of a tag is permanent, but is not appropriate for a product tag used in the distribution industry, where an owner of a tag is not permanent, as the technique saves verifying information in a tag. As the technique needs quite large storage for tags and quite many reader functions, the RFID cannot be used inexpensively. This kind of problem indicated for Patent Document 1 and Patent Document 2 can also be indicated for Patent Document 4. Although the technique described in Patent Document 3 provides RFID to both a user and a confidential document, it lacks a system for transferring ownership of a product which moves as it distributed or security measures against replay attacks. For example, the technique has a problem in enabling an abuser to behave as an authorized user if only the abuser reads an RFID tag for a user by another tag reader and copies it. The technique described in Non-Patent Document 1 only controls reading of tag information by a tag reader by using Blocker tag and cannot be applied to the case that a product moves as it distributed. SUMMARY OF THE INVENTION [0012] In order to solve the above problems, the present invention provides apparatus for verifying the authority of a person/owner in terms of an identifier of a product, first verifying information for verifying the authority held at a terminal for an owner with the authority involving said product, and second verifying information for verifying the authority concerning the identifier of said product stored in a product DB (database). [0013] An apparatus comprises means for receiving said identifier and said first verifying information, means for acquiring said second verifying information from said product DB, and means for determining whether or not there is the authority from said first verifying information and said second verifying information. If fake products made by copying the RFID appear, the apparatus according to the present invention can inexpensively prevent an abuser from accessing the verifying information and a false product from interfering a traceability system with fake goods, as the technique verifies the RFID, which is an identifier of each of the separately managed products and information for verifying an owner with the authority at a product/service DB server.
BRIEF DESCRIPTION OF THE DRAWINGS [0014] For a more complete understanding of the present invention and the advantage thereof, reference is now made to the following description taken in conjunction with the accompanying drawings, in which: [0015] FIG. 1 shows an outline of a system for verifying an authority in terms of a product/service operates; [0016] FIG. 2 shows an example of a hardware configuration of the product/service DB server or a user terminal; [0017] FIG. 3 shows an example of a function block diagram of functions of a product/service DB server and a user terminal; [0018] FIG. 4 illustrates the basic concept of the authority verification in terms of a product/service; [0019] FIG. 5 shows an example of a flow of verifying the ownership of the authority in terms of a product/service performed at a product/service DB server and a user terminal; [0020] FIG. 6 shows an example of a processing flow of transferring the ownership of the authority in terms of a product/service; [0021] FIG. 7 shows an outline of a product/service DB used in an application; and [0022] FIG. 8 shows an example where a user terminal keeps both a product/service ID and a verification key.
DETAILED DESCRIPTION OF THE INVENTION [0023] The present invention provides methods, systems and apparatus for verifying the authority in terms of an identifier of a product, by first verifying information for verifying the authority held at a terminal for an owner with the authority involving said product, and second verifying information for verifying the authority concerning the identifier of said product stored in a product DB (database) [0024] An embodiment of an apparatus comprises means for receiving said identifier and said first verifying information, means for acquiring said second verifying information from said product DB, and means for determining whether or not there is the authority from said first verifying information and said second verifying information. If fake products made by copying the RFID appear, the apparatus according to the present invention can inexpensively prevent an abuser from accessing the verifying information and a false product from interfering a traceability system with fake goods, as the technique verifies the RFID, which is an identifier of each of the separately managed products and information for verifying an owner with the authority at a product/service DB server. [0025] The present invention can assure an advanced security against leakage of a verification key by using a so-called one-time verification key, as said means for determining performs determination by using a hash value acquired by applying a one-way hash function to a value acquired by a predetermined method by t (an integer of 1 or more) times as a verification key for verifying information, and performs determination by using a hash value acquired by applying said one-way hash function by t−1 times to said number as a verification key for verifying information for the next verification. The present invention further improves security by using said hash value acquired by applying the hash function to the number by t−1 times as an encryption key when verifying information for verifying said authority is received from the terminal of an owner with the authority. [0026] The outlined present invention above does not enumerate all the features necessary to implement the present invention, and sub-combinations of the features can be included in the present invention. Although the present invention will be described through its embodiments, the embodiments below do not limit the present invention included according to the Claims below. Features described in the embodiments are combined just for helping a reader in understanding the present invention and it is not necessary to implement all of them as solving means of the present invention. [0027] FIG. 1 shows an outline of an environment where a system for verifying an authority in terms of a product/service operates. A product/service database (DB) server 101 responds to a request for sending information on a product/service. The product/service DB server verifies an authority of who requests information on the product/service. The product/service DB server also transfers an authority in terms of a product/service. A product/service DB 102 saves information on a product or a service and also saves information for verifying authority. The DB 102 may register only information on a product, or information on a service, or information on both a product and a service. A plurality of the product/service DB servers 101 exist, as they are managed by a producer or a distributor. One who owns the authority in terms of a product/service may need to view a past distribution channel of a product or a history of a service. Therefore, as the product/service is distributed through a market, information on the same product/service may present in a plurality of product/service DBs 102. The product/service DB saves information on a product, or information on a service, or information on the both. A network 103 connects the product/service DB server 101, a tag reader 104 or a user terminal 107 through a communication line. The network 103 is not limited to any particular network and can be either a wired network or a wireless network if only it is used for communication. [0028] The tag reader 104 is an appliance for reading a product/service ID 106 or verifying information 108 and sending it to the product/service DB server 101. The tag reader 104 may directly send/receive data to/from the product/service DB server 101 with a communication function. Alternatively, the tag reader 104 may have only a function of simply reading data and be connected with a communication appliance such as a personal computer. In this example, the tag reader 104 is shown as having a communication function. The tag reader 104 is preferably a multi-tag reader, which can read both a tag added to a product/service and a tag added to a user terminal. The tag reader 104 can easily accommodate the multi-tag reader by distinguishing the read in ID among a product/service ID, an owner ID (verification key), or a new owner ID for an assignee (verification key) shown in FIG. 6 to be described later, by identifying them with a header part (for example, product/service ID: 00, owner ID: 01, new owner ID: 11) of a RFID code or the like. The reference numeral 105 denotes a product/service ticket. This ticket can be a ticket for a product to be distributed in a market a member's card or a coupon for receiving a service, for example. [0029] The product/service ticket 105 is added with a product/service ID 106 and functions as an identifier for identifying the product or the service. The product/service ID 106 is not limited to particular IDs and can be any ID if only it can identify a product/service, such as a wireless ID tag, RFID, a one-dimensional barcode or two dimensional barcode. The product/service ID 106 can be directly added to a product but not to a service. Therefore, the product/service ID 106 is attached to a service ticket including a coupon or a ticket for receiving a service. The service ticket is not limited to a ticket printed on a sheet of paper and may be a ticket made of electronic codes. The reference numeral 107 denotes a user terminal and includes verifying information for verifying the ownership of the authority. The verifying information is verifying information 108, which relates to a verification key for verifying the authority. The verifying information 108 is used in verifying the ownership of the authority in terms of a product or a service at a product/service DB. The user terminal 107 can be a PDA (Persona Digital Assistance) or a cellular phone, or a terminal device such as a notebook personal computer or a desktop personal computer. The user terminal 108 preferably comprises a communication function when it needs to acquire information from a product/service DB server. The user terminal 107 may be integrated with a function of the tag reader 104. [0030] FIG. 2 outlines a hardware configuration 200 of the product/service DB server 101 or a user terminal. A CPU 201, which is a central processing unit, performs various programs under the control of various OSs. The CPU 201 interconnected with memory 203, a disk 204, a user interface 205 and a network interface 206 via a bus 202. The CPU 201 is connected with a display device 207, a keyboard 208 and a mouse 209 via the user interface 205 and connected with a network via the network interface 206. A user can input information through a touch pen 210 other than the keyboard 208 and the mouse 209. Therefore, the CPU 201 needs not to comprise all but any one of those denoted by the reference numerals 208-210. The memory 203 comprises main memory or cache memory. The cache memory is used for storing data of a product/service or owner information searched from a product/service DB saved in the disk 204 or the like. [0031] The disk 204 stores a program for verifying the authority in terms of a product/service at a product/service DB server. The program is read by the CPU 201 into main memory and executed. The disk 204 saves a product/service DB. The product/service DB needs not be saved on the same disk as that saves the program for verifying the authority in terms of a product/service. Therefore, a plurality of disks 204 may be present here. When a hardware configuration 200 is a user terminal, the disk 204 records a program operating at a user terminal and also saves verifying information. When a user terminal is integrated with a tag reader, a tag reader 211 is connected with the bus 202. [0032] When a user terminal is a PDA, generally without the keyboard 208 and the mouse 209, a user inputs information by using the touch pen 210. When a user terminal is a cellular phone, push buttons on the cellular phone substitute for the keyboard 208. When a product/service DB server and a user terminal directly communicate data with each other, they use the network interface 206. The hardware configuration 200 disclosed here is merely an example of a computer system and a bus arrangement. The features of the present invention can be implemented in various system configurations with a plurality of the same components included in a system or distributed over a network. [0033] FIG. 3 schematically shows a function of a product/service DB server 300 and a user terminal 350. First, the product/service DB 300 will be described. The reference numeral 301 denotes an interface for sending/receiving data to/from a user terminal or a tag reader. Blocks are schematically shown. The reference numeral 302 denotes a hash value calculation part for calculating a hash value by using a hash function. A hash function used at the hash value calculation part 302 is preferably a one-way hash function. The reference numeral 303 denotes an exclusive OR encoder for calculating an exclusive OR. The exclusive OR encoder 303 also decodes data of a verification key or the like, which is encrypted by an exclusive OR and received from a tag reader or a user terminal, by using a secret key or the like. [0034] The reference numeral 304 denotes an authority verification part for verifying the authority possession in terms of a product/service. The ownership of the authority determination part 304 determines the presence or absence of the ownership of the authority by using a verification key saved at a user terminal (a first verifying information) and a verification key received from a product/service information searching part 305 (a second verifying information). The product/service information searching part 305 is a DBMS (DataBase management System) for accessing a product/service DB 306. The product/service DB 306 comprises a product/service ID 311, an authority verification key 312, an attribute of a product/service and product/service related information 313 such as a name. [0035] Now, functions of the user terminal 350 will be described. An interface 351 is an interface for communicating data with a product/service DB server. When a user terminal is attached with a tag reader, the interface 351 is used for sending an ID or the like read from the tag to a product/service DB and receiving information in terms of a product/service sent from the product/service DB server. The reference numeral 352 denotes a hash value calculation part for calculating a hash value by using a hash function. The hash function to be used at the hash value calculation part 352 is preferably a one-way hash function as that is used at the product/service DB. The reference numeral 353 denotes an exclusive OR encoder for calculating an exclusive OR. The exclusive OR encoder 353 also decodes data of product/service related information or the like encrypted by an exclusive OR that is received from the product/service DB. [0036] The reference numeral 354 denotes a tag reader. The tag reader 354 is not necessary for a user terminal and can be implemented by reading a product/service ID and an authority verification key from a tag reader placed near. The reference numeral 355 denotes a disk (storage device) at a user terminal. The disk 355 saves a product/service ID 361 for verifying the ownership of the authority, a number S (made by random numbers or the like) 362 to be applied with a one-way hash value and the number t to apply a hash function 363. In order to make a single user terminal adapted to accommodate a plurality of products/services, those denoted by the reference numerals 361 to 362 are recorded for each product/service. When there are a plurality of product/service IDs, the tag reader 371 can easily identify an verification key for each product/service if only MAC of a product/service ID (may be a short hash or a checksum) is used as a part of a verification key. As such, the user terminal 350 manages verifying information by creating a verification key for each product/service with information on the disk 355. Generally, the multi tag reader 371 reads a product/service ID 372 attached to a product/service ticket and verifying information to be managed at the user terminal 350. Although respective functions are represented and arranged in FIG. 3 by block, the functions are not limited to be arranged in this block configuration and can be implemented by other functional block embodiment if only the configuration has these functions, as the respective functions can be made in blocks with various ranges. [0037] FIG. 4 illustrates the basic concept of the authority verification in terms of a product/service. The authority verification uses so called S/Key verification method, which uses a one-time verification key with a one-way hash function. In this authority verification, the verification key is encrypted with an exclusive OR for security before the key is transmitted. A one-way hash function is a hash function, which cannot give a value (a certain value) before applied with the hash function from the hash value acquired by applying the hash function to a certain value. The verification method is outlined in FIG. 4. Where t is an integer of 1 or more, Told is what a one-way hash function h is applied to a random number S by t times, i.e., Told=ht (S). Here, the random number is S, though, the random number can be the number acquired by a predetermined method including a predetermined number. [0038] As h is a one-way hash function, it cannot give the number before being applied with the hash function from the hash value. Tnew=ht−1(S), which means that Tnew is what the hash function h is applied with t−1 times. And Told=h (Tnew), which means that Told is what the hash function h is applied to Tnew once. This means that Told can be acquired from Tnew but Tnew cannot be acquired from Told. A user and who verifies the user use Told as the verification key (block 401, 451). Actually, the user holds the random number S and the times t that a hash function was applied to S. At block 452, the user calculates the verification key, the encryption key and the exclusive OR of them and sends the results to who verifies the user. The verification key Told is acquired from the random number S by using a value ht(S), which is what the hash function h is applied to S by t times. In order to encrypt the verification key Told, the user calculates Tnew=ht−1 (S) and an exclusive OR of Told and Tnew, ET=(Tnew xor Told), and sends the result to who verifies the user. [0039] Who verifies the user performs verification at block 402. Who verifies the user calculates an exclusive OR, ET xor Told=Tnew xor Told xor Told=Tnew by using its holding verification key Told. Then who verifies the user calculates Told from h (Tnew), which is what the hash function is applied to Tnew once. If the result matches with Told, which is held by the server, who verifies the user certifies the user. Then the server and the user use Tnew as a verification key (block 403, 453). Actually, the user holds the times t that the hash function is applied to the random number S. When the next verification (block 430) ends, the new verification key is T (=ht−2 (S)) (block 404, 454). The verification key comes next is T (=ht−3 (S)). The authority is verified with new verification key for each time. As the new verification key cannot be calculated from the old verification key, the security is kept high even if an old verification key is leaked. [0040] FIG. 5 shows a flow 500 of verifying the ownership of the authority in terms of a product/service performed at a product/service DB server and a user terminal. Processes performed by a user terminal are shown in the left side and that by a product/service DB server is shown in the right side. At step 551, the processing starts. At step 552, TA new and TA old are acquired. A hash value calculation part 352 of the user terminal shown in FIG. 3 calculates TA new and TA old by using a hash function h, t (an integer of 1 or more) and a random number SA. TA old is a value that the hash function is applied to SA by t times. TA new is a value that the hash function is applied to SA by (t−1) times. At step 553, the user terminal calculates an exclusive OR ET of TA new and TA old and sends the result with the product/service ID to the product/service DB server. Usually, a multi-tag reader is responsible for sending them. The calculation of the exclusive OR ET is encryption of TA old. If a tag reader is separated from the user terminal, the sending process at step 553 is performed by the tag reader. [0041] Then the process is performed by the process/service DB server. At step 501, the process/service DB server searches a product/service DB for a corresponding verification key (TA old) by using the product/service ID as a searching key. At step 502, the process/service DB determines whether there is a corresponding product/service ID or not. If it is determined that there is no corresponding product/service ID (No), the product/service DB server sends a message that there is no corresponding product/service ID to the user terminal at step 503. At step 554, the user terminal receives the message that there is no corresponding product/service ID and proceeds to step 558 and ends the process. If it is determined that there is a corresponding product/service ID (Yes) at step 502, i.e., that the authority is certified, the product/service DB server responds to the determination and proceeds to step 504. At step 504, the product/service DB server calculates TA new from the exclusive OR of the searched verification key (TA old) and ET, and determines whether the value that the calculated result is applied with the hash function matches the searched verification key (TA old) or not. If it is determined that they do not match (No), the product/service DB server proceeds to step 505 and sends a message that the user has no authority to the user terminal. [0042] At step 555, the user terminal receives the message that the user has no authority, and proceeds to step 558 and ends the process. If it is determined that they match (Yes) at 504, the product/service DB proceeds to step 506 and sets TA new as a new verification key, performs necessary encryption on information in terms to the product/service and sends the result to the user terminal. The encryption here is preferably what is acquired by an exclusive OR using TA new or TA old. If an encryption done by being calculated an exclusive OR by using TA new is used here, the user terminal can confirm that the server calculated TA new correctly. The user terminal acquires information in terms of the product/service at step 556, and performs a necessary decryption process on the information. Then at step 557, the user terminal replaces a verification key with TA new, which is the same as the user terminal stores t−1 as times for applying the hash function to have TA new for the next verification key. At step 558, the user terminal ends the process. In this processing flow 500, the product/service DB server need not have SA, as it can acquire TA new from ET sent from the user terminal (tag reader) if only holding TA old. [0043] FIG. 6 shows a processing flow of transferring the ownership of the authority in terms of a product/service. It is assumed here that the ownership of the authority is transferred from a user A (assignor) to a user B (assignee). Therefore, before the transferring of the ownership of the authority begins, the user A has the ownership of the authority and the product/service DB contains verifying information (verification key: TA old) of the user A. A user terminal of the user B, which the user A admits to transfer the ownership of the authority in terms of the product/service, starts the processing at step 681. At step 682, the user B acquires SB by using a random number or the like. Te user B calculates TB new by applying a hash function h by u (integer of 1 or more) times to SB. At step 683, the user B sends TB new to a user terminal of the user A, which admits to transfer the ownership of the authority to the user B. [0044] At step 651, the user terminal of the user A receives TB new from the user terminal of the user B. At step 652, the user terminal of the user A calculates TA new and TA old by using the hash function h, t and SA. TA old is acquired by applying the hash function h by t times to SA and TA new is acquired by applying the hash function h by t−1 times to SA. At step 653, the user terminal of the user A acquires an exclusive OR ETA of TA new and TA old, then an exclusive OR ETB of TB new and TA old and sends the results with the product/service ID in terms of transferring the ownership of the authority to the product/service DB server. A multi tag reader may send them. At step 601, the product/service DB server searches the product/service DB for a corresponding verification key (TA old) by using the product/service ID as a searching key. At step 602, the product/service DB server determines whether there is a corresponding product/service ID or not. If it is determined that there is no corresponding product/service ID (No), the product/service DB server proceeds to step 603 and sends a message that there is no product/service ID. The user terminal of the user A and the user terminal of the user B receive the message and end the process at step 654 and step 684, respectively. If it is determined that there is a corresponding product/service ID (Yes) at step 602, the product/service DB server proceeds to step 604. [0045] At step 604, the product/service DB server acquires TA new from the exclusive OR of the searched verification key (TA old) and ETA, and determines whether the value that it is applied with the hash function once matches the searched verification key (TA old) or not. If it is determined that they do not match (No), the product/service DB server proceeds to step 605 and sends a message that the user A has no ownership of the authority, or a message of no correspondence to the user terminal of the user A and the user terminal of the user B. The user terminal of the user A and the user terminal of the user B receive the message and end the processes at step 654 and step 684, respectively. If it is determined that they match (Yes) at step 604, i.e., if it is determined that the user is certified, the product/service DB server proceeds to step 606, acquires TB new from an exclusive OR of TA old and ETB and sets TB new as a new verification key. At step 607, the product/service DB server sends that the certification completed to the user terminal of the user A and the user terminal of the user B. The user terminal of the user A and the user terminal of the user B receive the message and end the processes at step 654 and step 684, respectively. [0046] With the processing flow 600, the ownership of the authority can be transferred from the user A to the user B with the security being kept. Only the user A, who is an authorized owner with the authority, is allowed to transfer the ownership of the authority to another user. If the same owner with the authority in terms of a product/service is recorded as that is stored in the product/service DB server at the first step of recording a record of information on the product/service in the product/service DB, i.e., if a product or the like is actually transferred to a customer (user B) by making a user A as the product/service DB server, the product/service can easily transferred to a distribution process with this processing flow 600. Transferring of data between product/service DB servers of different companies can also be performed by using this processing flow 600. For example, the ownership of the authority can be transferred with the security being kept, by making a manufacturer as the user A and a distributor as the user B. [0047] One-time verifying information uses a verification key which is what a random number S is applied with a hash function by t times first, and uses a verification key which is what the random number S is applied with the hash function by t−1 times for the next time. It uses a verification key which is what the random number S is applied with the hash function by t−2 times for the further next time. As the verification is performed for many times, the times for applying the hash function will be 0. In such a case, the random number S and t can be reset by using the processing flow 600. For this purpose, it only needs to perform processes for the user A and the user B in the same user terminal. With this procedure, new verification is enabled by using a verification key, which is what anew random number is applied with the hash function by times of integer. [0048] An application which modifies the embodiment will be described. FIG. 7 is an outline 700 of a product/service DB used in an application. This is a partly modified product/service DB 306 shown in FIG. 3. If a plurality of users have to view a history of a product/service to access the product/service, an embodiment can be such that the product/service DB contains an entry for an owners list with a verification key is assigned for each owner. The reference numeral 701 denotes a product/service ID. The reference numeral 702 denotes an owners list, which can contain a plurality of owners. The reference numeral 703 denotes information on the product/service. The reference numeral 704 denotes a table for managing verification keys for respective owners. With the configuration of the product/service DB 700, each of the sharing owners can access information on the product/service by keeping security without letting the other sharing owner to know the owner's own verification key for one product/service. [0049] FIG. 8 shows an application where a user terminal keeps both a product/service ID and a verification key. Here, the user terminal has both of the product/service ID 106 and the verifying information 108 shown in FIG. 1. The user terminal 801 saves a product/service ID 802 and verifying information 803. This embodiment is particularly convenient in the case where a product/service is a digital ticket or the like. If the product/service ID is a digital ticket or the like, the user terminal can save the product/service ID. An embodiment of a cellular phone having a function of a digital ticket is increasingly used. With this application, a user can directly buy a digital ticket from a ticket counter or an Internet site and a ticket can be distributed among users with security being kept high. A user can easily buy this type of digital ticket by using the flow 600 shown in FIG. 6. The product/service DB server only needs to include information on the digital ticket in the message it sends to the user terminal of the user B at step 607. [0050] If the ownership of the authority is temporally transferred from a user A to a user B in such a case that the user A leaves management of products or the like to the user B while the user A is on a business trip, another application can be considered to transfer the ownership of the authority by using the processing flow 600 and TB old is used as a verification key with a time limit and the verification key returns to TA new after a predetermined period. The verification key returns to TA new and not to TA old here because TAold was used in transferring the ownership of the authority from the user A to the user B and cannot be used as the one-time verification key any more. [0051] A manufacturer without a product/service DB server has to register itself with a product/service DB managed by a third party. In such a case, a product/service ID, a verification key or an attribute of a product/service can be sent from a user terminal for registration. The embodiments of the present invention have been described, though, the present invention is not technically limited to the ranges described in the abovementioned embodiments. It is apparent to those skilled in the art that various modifications and improvements can be applied to the embodiments. It is apparent from the Claims that the embodiments with various modifications and improvements can be included in the technical range of the present invention. Variations described for the present invention can be realized in any combination desirable for each particular application. Thus particular limitations, and/or embodiment enhancements described herein, which may have particular advantages to a particular application need not be used for all applications. Also, not all limitations need be implemented in methods, systems and/or apparatus including one or more concepts of the present invention. Methods may be implemented as signal methods employing signals to implement one or more steps. Signals include those emanating from the Internet, etc. [0052] The present invention can be realized in hardware, software, or a combination of hardware and software. A visualization tool according to the present invention can be realized in a centralized fashion in one computer system, or in a distributed fashion where different elements are spread across several interconnected computer systems. Any kind of computer system—or other apparatus adapted for carrying out the methods and/or functions described herein—is suitable. A typical combination of hardware and software could be a general purpose computer system with a computer program that, when being loaded and executed, controls the computer system such that it carries out the methods described herein. The present invention can also be embedded in a computer program product, which comprises all the features enabling the implementation of the methods described herein, and which—when loaded in a computer system—is able to carry out these methods. [0053] Computer program means or computer program in the present context include any expression, in any language, code or notation, of a set of instructions intended to cause a system having an information processing capability to perform a particular function either directly or after conversion to another language, code or notation, and/or reproduction in a different material form. [0054] Thus the invention includes an article of manufacture which comprises a computer usable medium having computer readable program code means embodied therein for causing a function described above. The computer readable program code means in the article of manufacture comprises computer readable program code means for causing a computer to effect the steps of a method of this invention. Similarly, the present invention may be implemented as a computer program product comprising a computer usable medium having computer readable program code means embodied therein for causing a a function described above. The computer readable program code means in the computer program product comprising computer readable program code means for causing a computer to effect one or more functions of this invention. Furthermore, the present invention may be implemented as a program storage device readable by machine, tangibly embodying a program of instructions executable by the machine to perform method steps for causing one or more functions of this invention. [0055] It is noted that the foregoing has outlined some of the more pertinent objects and embodiments of the present invention. This invention may be used for many applications. Thus, although the description is made for particular arrangements and methods, the intent and concept of the invention is suitable and applicable to other arrangements and applications. It will be clear to those skilled in the art that modifications to the disclosed embodiments can be effected without departing from the spirit and scope of the invention. The described embodiments ought to be construed to be merely illustrative of some of the more prominent features and applications of the invention. Other beneficial results can be realized by applying the disclosed invention in a different manner or modifying the invention in ways known to those familiar with the art. Patent CitationsCited PatentFiling datePublication dateApplicantTitleUS5805911 *Feb 1, 1995Sep 8, 1998Microsoft CorporationWord prediction systemUS5942978 *Jul 15, 1998Aug 24, 1999Sensormatic Electronics CorporationWireless transmitter key for EAS tag detacher unitUS6748533 *Dec 23, 1998Jun 8, 2004Kent Ridge Digital LabsMethod and apparatus for protecting the legitimacy of an articleUS7051206 *Nov 7, 2000May 23, 2006Unisys CorporationSelf-authentication of value documents using digital signaturesUS7174153 *Dec 16, 2004Feb 6, 2007Gregory A EhlersSystem and method for providing information to an operator of an emergency response vehicleUS7176791 *Dec 10, 2004Feb 13, 2007Nec CorporationSecurity verification method and deviceUS7212637 *Mar 11, 2003May 1, 2007Rimage CorporationCartridge validation with radio frequency identificationUS7221258 *Dec 9, 2003May 22, 2007Kathleen LaneHierarchical electronic watermarks and method of useUS7228155 *Oct 15, 2004Jun 5, 2007American Express Travel Related Services Company, Inc.System and method for remotely initializing a RF transactionUS7284003 *Sep 17, 2004Oct 16, 2007Honda Motor Co., Ltd.Product lifecycle data management system and product lifecycle data management methodUS7333001 *Dec 9, 2003Feb 19, 2008Kathleen LaneSecure personal RFID documents and method of useUS7357318 *Sep 17, 2004Apr 15, 2008Honda Motor Co., Ltd.RFID tag access authentication system and RFID tag access authentication methodUS7376626 *Sep 11, 2003May 20, 2008Sony CorporationInformation recording medium, information processing apparatus, information processing method, and computer programUS7471199 *Jan 10, 2005Dec 30, 2008Intermec Ip Corp.Mobile key using read/write RFID tagUS7492258 *Mar 21, 2006Feb 17, 2009Radiofy LlcSystems and methods for RFID securityUS7497384 *Nov 10, 2005Mar 3, 2009Symbol Technologies, Inc.Methods and systems for the negotiation of a population of RFID tags with improved securityUS7503480 *Mar 12, 2004Mar 17, 2009American Express Travel Related Services Company, Inc.Method and system for tracking user performanceUS20020165912 *Jul 25, 2001Nov 7, 2002Storymail, Inc.Secure certificate and system and method for issuing and using sameUS20020169714 *Sep 6, 2001Nov 14, 2002Masayuki IkeOrdering-and-reserving management method using paper medium mounted with radio frequency identification IC chip and advertising effect analysis method, and system thereofUS20020178360 *Jul 25, 2001Nov 28, 2002Storymail, Inc.System and method for communicating a secure unidirectional response messageUS20020194483 *Jul 25, 2001Dec 19, 2002Storymail, Inc.System and method for authorization of access to a resourceUS20020194501 *Jul 25, 2001Dec 19, 2002Storymail, Inc.System and method for conducting a secure interactive communication sessionUS20020196935 *Jul 25, 2001Dec 26, 2002Storymail, Inc.Common security protocol structure and mechanism and system and method for usingUS20020199001 *Jul 25, 2001Dec 26, 2002Storymail, Inc.System and method for conducting a secure response communication sessionUS20020199096 *Jul 25, 2001Dec 26, 2002Storymail, Inc.System and method for secure unidirectional messagingUS20030009694 *Jul 25, 2001Jan 9, 2003Storymail, Inc.Hardware architecture, operating system and network transport neutral system, method and computer program product for secure communications and messagingUS20030041110 *Jul 25, 2001Feb 27, 2003Storymail, Inc.System, Method and Structure for generating and using a compressed digital certificateUS20040088176 *Nov 4, 2002May 6, 2004Balaji RajamaniSystem and method of automated licensing of an appliance or an applicationUS20040181681 *Mar 11, 2003Sep 16, 2004Rimage CorporationCartridge validation with radio frequency identificationUS20040233040 *Dec 9, 2003Nov 25, 2004Kathleen LaneSecure personal RFID documents and method of useUS20050007236 *Dec 9, 2003Jan 13, 2005Kathleen LaneHierarchical electronic watermarks and method of useUS20050033619 *Mar 12, 2004Feb 10, 2005American Express Travel Related Services Company, Inc.Method and system for tracking user performanceUS20050038718 *Jul 1, 2004Feb 17, 2005American Express Travel Related Services Company, Inc.Method and system for facilitating a shopping experienceUS20050049979 *Aug 26, 2003Mar 3, 2005Collins Timothy J.Method, apparatus, and system for determining a fraudulent itemUS20050061875 *Sep 9, 2004Mar 24, 2005Zai Li-Cheng RichardMethod and apparatus for a secure RFID systemUS20050061879 *Sep 17, 2004Mar 24, 2005Honda Motor Co., Ltd.RFID tag access authentication system and RFID tag access authentication methodUS20050105140 *Nov 9, 2004May 19, 2005Canon Kabushiki KaishaCommunication apparatus and method for controlling sameUS20050144475 *Dec 10, 2004Jun 30, 2005Nec CorporationSecurity verification method and deviceUS20050164673 *Dec 16, 2004Jul 28, 2005Gregory EhlersSystem and method for providing information to an operator of an emergency response vehicleUS20050198489 *Dec 24, 2003Sep 8, 2005Apple Computer, Inc.Server computer issued credential authenticationUS20050218209 *Mar 30, 2004Oct 6, 2005International Business Machines CorporationCounterfeit detection methodUS20050289083 *May 24, 2004Dec 29, 2005Ngai Francis TSystem and method for authenticating and validating productsUS20060033608 *Jul 29, 2005Feb 16, 2006Ari JuelsProxy device for enhanced privacy in an RFID systemUS20060034453 *Aug 13, 2004Feb 16, 2006Yen-Fu LiuSystem and method for secure encryptionUS20060071791 *Sep 29, 2004Apr 6, 2006Honeywell International Inc.Enhanced RFID vehicle presence detection systemUS20060074813 *Oct 15, 2004Apr 6, 2006American Express Travel Related Services Company, Inc.System and method for remotely initializing a rf transactionUS20060247984 *Jun 4, 2004Nov 2, 2006Shaw Grant L HSystem for and method of monitoring an itemUS20060251442 *May 9, 2005Nov 9, 2006Fuqua Charles LStoring informationUS20070081671 *Oct 11, 2005Apr 12, 2007Ross John W JrControlling deactivation of RFID tagsUS20070106892 *Oct 8, 2004May 10, 2007Engberg Stephan JMethod and system for establishing a communication using privacy enhancing techniquesUS20080106385 *Oct 11, 2006May 8, 2008International Business Machines CorporationMethod and system for protecting rfid tags on purchased goods* Cited by examinerReferenced byCiting PatentFiling datePublication dateApplicantTitleUS8374320 *Feb 12, 2013Fujitsu LimitedEnvironment information transmission method, service controlling system, and computer productUS8618905 *Jul 8, 2008Dec 31, 2013International Business Machines CorporationVerifying the ownership of an owner's authority in terms of product and serviceUS20070061891 *May 3, 2006Mar 15, 2007Fujitsu LimitedEnvironment information transmission method, service controlling system, and computer productUS20080106372 *Dec 12, 2006May 8, 2008Wei ChangAuthentication method during product transactionsUS20080272882 *Jul 8, 2008Nov 6, 2008Masayuki NumaoVerifying the ownership of an owner's authority in terms of product and serviceUS20080320105 *Jun 13, 2008Dec 25, 2008Naono NorihikoSystem, server and information terminal for detection of a black hatUS20090072946 *Sep 14, 2007Mar 19, 2009Sap AgCollaborative product authenticationUS20110231656 *Mar 16, 2010Sep 22, 2011Telcordia Technologies, Inc.System and methods for authenticating a receiver in an on-demand sender-receiver transactionUS20130074152 *Mar 21, 2013Samsung Electronics Co., Ltd.Method and devices for security association (sa) between devicesUS20140286491 *Aug 8, 2012Sep 25, 2014Mikoh CorporationRadio frequency identification technology incorporating cryptographics* Cited by examinerClassifications U.S. Classification713/168International ClassificationH04L9/00Cooperative ClassificationH04L9/3236, H04L2209/805European ClassificationH04L9/32Legal EventsDateCodeEventDescriptionJun 27, 2008ASAssignmentOwner name: INTERNATIONAL BUSINESS MACHINES CORPORATION, NEW YFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:NUMAO, MASAYUKI;ISHIGAKI, YOSHINOBU;WATANABE, YUJI;REEL/FRAME:021161/0729;SIGNING DATES FROM 20060124 TO 20060126Owner name: INTERNATIONAL BUSINESS MACHINES CORPORATION,NEW YOFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:NUMAO, MASAYUKI;ISHIGAKI, YOSHINOBU;WATANABE, YUJI;SIGNING DATES FROM 20060124 TO 20060126;REEL/FRAME:021161/0729Sep 13, 2013REMIMaintenance fee reminder mailedFeb 2, 2014LAPSLapse for failure to pay maintenance feesMar 25, 2014FPExpired due to failure to pay maintenance feeEffective date: 20140202RotateOriginal ImageGoogle Home - Sitemap - USPTO Bulk Downloads - Privacy Policy - Terms of Service - About Google Patents - Send FeedbackData provided by IFI CLAIMS Patent Services