JP4688578B2 - Search processing method and data registration method - Google Patents

Description

  The present invention relates to an information processing technology related to an IC (Integrated Circuit) tag such as an RFID (Radio Frequency ID) tag.

  The RFID tag is attached to various articles and the like, and the ID is expected to be read at various places. That is, when the article attached with the RFID tag moves to a predetermined position, the ID of the RFID tag is read by a reader arranged at the position, and the ID of the reader is associated with the ID of the reader. Accumulated.

On the other hand, for example, Japanese Unexamined Patent Application Publication No. 2003-165626 discloses the following technique. An electronic circuit chip is attached to the ingested item and the ID code is read from the electronic circuit chip by an ID reader. The user terminal notifies this ID code to the ID management server, and obtains the destination of the attribute information management server that manages the attributes of the intake. Then, the ID code is notified to the attribute information management server of the acquired destination. In response to this, the attribute information management server identifies the attribute information of the ingested substance and notifies the ingestion management support server. The ingestion management support server creates a message for the ingestion action of the ingestion using the user's ingestion action history and ingestion attribute information managed by the ingestion management support server, and notifies the user terminal of the message. In this publication, there is a description of retrieval of data read by an ID reader. However, a retrieval pattern that considers a data storage mode and a use situation is not deeply studied.
JP 2003-165626 A

  Simply storing the ID of the RFID tag read by the reader is not preferable from the viewpoint of scalability and efficiency when using data such as traceability verification of an article attached with the RFID tag. This point has not been considered in the past.

  Therefore, an object of the present invention is to provide a technique for making it possible to efficiently use a result of reading an IC tag such as an RFID tag by a reader.

  Another object of the present invention is to provide a novel interface and platform for using the reading result of an IC tag such as an RFID tag by a reader.

  The search processing method according to the first aspect of the present invention includes an object information management for storing and managing identification information of an IC tag, static information of the IC tag, and static information of a reader that has read the IC tag. A server, a reader information management server that accumulates and manages the reader identification information, the static information of the reader, and the static information of the IC tag read by the reader are used. By holding data in these two servers, an efficient search can be performed for at least one of the following four basic search patterns.

  That is, the search processing method according to the first aspect of the present invention includes a step of receiving specification of a search key and a requested data type, and (a) when the specified search key is identification information of an IC tag, A step of generating a search request including the identification information of the IC tag as a key and the request data type, and transmitting it to the object information management server; and (b) if the designated search key is the identification information of the reader, A step of generating a search request including the identification information of the reader, which is a search key, and the request data type, and transmitting it to the reader information management server; and (c) when the specified search key is static information of the IC tag. Generating a search request including static information of the IC tag that is the search key and the request data type, and transmitting it to the object information management server; and (d) the specified search key In the case of the static information of the reader, among the steps of generating a search request including the static information of the reader as the search key and the request data type and transmitting it to the reader information management server, (a) or ( c) and (b) or (d).

  Steps (a) to (d) correspond to the four basic search patterns, and each of the four basic search patterns can be searched by simply distributing the search request to one necessary type of server. The result can be obtained, and the search process is made efficient.

  A data registration method according to the second aspect of the present invention is a method of registering data in the object information management server and the reader information management server described above, and the reader reads the identification information of a specific IC tag. A reader static information acquisition step for acquiring the reader static information from the reader information management server based on the reader identification information, and a reader static information acquisition step corresponding to the read identification information of the specific IC tag. The reader static information registration step for registering in the object information management server the static information of the reader acquired by the above, and acquiring the static information of the specific IC tag from the object information management server based on the read identification information of the specific IC tag IC tag static information acquisition step to perform and IC tag static information acquisition step corresponding to the identification information of the reader Static information of a specific IC tag acquired Ri includes an IC tag static information registration step of registering the reader information management server.

  As described above, if data is stored in the object information management server and the reader information management server used in the search processing method according to the first aspect of the present invention, the search becomes efficient.

  The reader static information acquisition step, the reader static information registration step, the IC tag static information acquisition step, and the IC tag static information registration step described above are performed by the reader or a proxy processing execution computer of the reader. May be executed. The leader takes the initiative in registering data.

  On the other hand, the reader static information acquisition step described above includes a step in which the reader transmits a first registration request including the identification information of the reader and the identification information of the read specific IC tag to the reader information management server; When the information management server receives the first registration request, the information management server may include a step of searching with the reader identification information to read out the corresponding reader static information. Further, in the reader static information registration step described above, the reader information management server transmits a second registration request including identification information of a specific IC tag and static information of the reader to the object information management server. And when the object information management server receives the second registration request, it may include a step of registering the static information of the reader corresponding to the identification information of the specific IC tag. In addition, in the IC tag static information acquisition step described above, the object information management server searches the identification information of the specific IC tag included in the second registration request to obtain the static information of the corresponding specific IC tag. You may make it read. Furthermore, the IC tag static information registration step described above includes a step in which the object information management server transmits the read static information of the specific IC tag to the reader information management server, and the reader information management server Receiving static information of the IC tag and registering the received static information of the specific IC tag corresponding to the identification information of the reader.

  The search processing method according to the third aspect of the present invention is an object for storing and managing identification information of an IC tag, static information of the IC tag, and static information of a reader that has read the IC tag. An information management server and a reader information management server that manages identification information of the reader and static information of the reader are used.

  In this case, the search processing method according to the third aspect of the present invention includes a step of receiving specification of a search key and a requested data type, and (a) when the specified search key is identification information of an IC tag, A step of generating a search request including the identification information of the IC tag, which is a search key, and the request data type, and transmitting it to the object information management server; and (b) when the designated search key is the identification information of the reader Then, a search request including the reader identification information as a search key and the request data type is generated and transmitted to the reader information management server, and further, the reader static information specified from the reader identification information in the reader information management server And a second search request including the request data type and transmitting it to the object information management server, and (c) a designated search key If it is static information of the IC tag, a step of generating a search request including the static information of the IC tag that is the search key and the request data type and sending it to the object information management server; (d) designated If the search key is the static information of the reader, a search request including the reader static information as the search key and the request data type is generated and transmitted to the object information management server ( a) or (c) and (b) or (d). Also in the third aspect of the present invention, the steps (a) to (d) correspond to the four basic search patterns, and the data necessary for traceability can be acquired by the interface in the present embodiment. It becomes like this.

  Furthermore, a data registration method according to the fourth aspect of the present invention is a method for registering data in the object information management server described above, wherein a reader reads identification information of a specific IC tag; A reader static information acquisition step for acquiring the reader static information from the reader information management server based on the reader identification information, and a reader acquired by the reader static information acquisition step corresponding to the read identification information of the specific IC tag. A static information registration step for registering the static information in the object information management server. Thus, the process of registering data in the object information management server used in the search processing method according to the third aspect of the present invention is relatively simple.

  Also, the search processing method according to the fifth aspect of the present invention provides object information for accumulating and managing identification information of an IC tag, static information of the IC tag, and static information of a reader that has read the IC tag. A management server and a reader information management server that stores and manages the static information of the reader and the static information of the IC tag read by the reader instead of the identification information of the reader are used.

  In this case, the search processing method includes a step of accepting specification of a search key and a request data type, and (a) identification of an IC tag that is a search key when the specified search key is identification information of an IC tag. A step of generating a search request including information and a request data type and transmitting it to the object information management server; and (b) if the specified search key is static information of an IC tag, the search key IC A step of generating a search request including the static information of the tag and the request data type and transmitting it to the object information management server; and (c) if the specified search key is the static information of the reader, the search key (A) or (b) and (c) are included among the steps of generating a search request including the static information of the reader and the request data type, and transmitting it to the reader information management server. Since the reader identification information is not handled, one of the four basic search patterns does not exist, and steps (a) to (c) correspond to the three basic search patterns. Also in this case, it is possible to obtain a search result of any one of the three basic search patterns only by distributing and transmitting the search request to each required one type of server, and the search processing is made efficient.

  Furthermore, a data registration method according to the sixth aspect of the present invention is a method for registering data in the object information management server and the reader information management server described above, wherein a reader having its own static information is specified. A step of reading identification information of the IC tag, a step of registering static information of the reader in the object information management server corresponding to the identification information of the read specific IC tag, and object information based on the identification information of the specific IC tag An acquisition step of acquiring static information of a specific IC tag from the management server, and a registration for registering the static information of the specific IC tag acquired by the acquisition step in the reader information management server in correspondence with the static information of the reader Steps.

  As described above, if data is stored in the object information management server and the reader information management server used in the search processing method according to the fifth aspect of the present invention, the search becomes efficient.

  The search processing method according to the seventh aspect of the present invention is an object information management for storing and managing identification information of an IC tag, static information of the IC tag, and static information of a reader that has read the IC tag. Use a server. The search processing method includes a step of receiving specification of a search key and a requested data type, and (a) when the specified search key is identification information of an IC tag, identification information of the IC tag that is a search key; A first step of generating a search request including a request data type and transmitting it to the object information management server; and (b) a search key if the specified search key is static information of an IC tag. A second step of generating a search request including the static information of the IC tag and the request data type and transmitting it to the object information management server; and (c) when the specified search key is the static information of the reader. Generates a search request including the reader's static information as a search key and the requested data type, and transmits it to the object information management server, and (a) and (b), or (A) or (b) and including the (c). Since the reader identification information is not handled, one of the four basic search patterns does not exist, and steps (a) to (c) correspond to the three basic search patterns. The interface according to the present embodiment makes it possible to acquire data necessary for traceability.

  The search processing method according to the eighth aspect of the present invention stores and manages IC tag identification information, static information of the IC tag, identification information of the reader that has read the IC tag, and reader identification information. And a reader information management server for storing and managing static information of the reader and identification information of the IC tag read by the reader.

  In this case, the present search processing method includes a step of accepting specification of a search key and a request data type, and (a) the specified search key is identification information of the IC tag and the request data type is static information of the reader. In this case, the identification information of the IC tag that is the search key and the request data type called the identification information of the reader are included, the identification information of the reader is extracted from the identification information of the IC tag, and the Generating a search request for extracting the target information and sending it to the object and reader information management server; and (b) a specified search key is the reader identification information and the request data type is a static of the IC tag. In the case of information, it includes the identification information of the reader as a search key and the request data type of static information of the IC tag, and the IC tag Generating a search request for extracting other information, extracting static information of the IC tag from the identification information of the IC tag, and transmitting it to the object and reader information management server; and (c) a specified search When the key is the static information of the IC tag and the request data type is the static information of the reader, the IC includes the static information of the IC that is the search key and the request data type of the static information of the reader, and the IC Extracting the reader identification information from the static information, generating a search request for extracting the reader static information from the reader identification information, and transmitting the search request to the object and reader information management server; and (d) If the specified search key is the static information of the reader and the request data type is the static information of the IC tag, the static information of the reader that is the search key and the static information of the IC tag. Including a request data type called information, generating a search request for extracting identification information of the IC tag from the static information of the reader, and extracting static information of the IC tag from the identification information of the IC tag, And (a) or (c) and (b) or (d) of the step of transmitting to the reader information management server.

  Steps (a) to (d) correspond to four basic search patterns, and the data necessary for traceability can be acquired by the interface in the present embodiment.

  According to a ninth aspect of the present invention, there is provided a search processing method comprising: identification information of an IC tag; static information of the IC tag; identification information of a reader that has read the IC tag; and an object information management server for storing and managing A reader information management server that accumulates and manages reader identification information, static information of the reader, and identification information of an IC tag read by the reader is used.

  In this case, the present search processing method includes a step of accepting specification of a search key and a request data type, and (a) the specified search key is identification information of the IC tag and the request data type is static information of the reader. In this case, a search request including the identification information of the IC tag as the search key and the request data type of the static information of the reader is generated and transmitted to the object information management server. A first step of generating a second search request including a request data type called reader identification information and reader static information identified from the identification information, and transmitting the second search request to the reader information management server; and (b) a designated search. When the key is the reader identification information and the request data type is the static information of the IC tag, the reader identification information as the search key and the IC tag A search request including the request data type of the target information is generated, transmitted to the reader information management server, and further, the IC tag identification information and the IC tag static information specified from the reader identification information in the reader information management server A second step of generating a second search request including the requested data type and sending it to the object information management server, and (c) the specified search key is static information of the IC tag and the requested data type is the reader Is generated, a search request including static information of an IC tag as a search key and a request data type of reader identification information is generated and transmitted to the object information management server. In the management server, the second verification including the identification information of the reader specified from the static information of the IC tag and the requested data type of the static information of the reader. A third step of generating a request and transmitting it to the reader information management server; and (d) when the designated search key is the static information of the reader and the request data type is the static information of the IC tag, A search request including a reader static information as a search key and a request data type called IC tag static information is generated and transmitted to the reader information management server. Further, the reader information management server uses the reader static information from the reader static information. Among the fourth steps of generating a second search request including the identification information of the identified IC tag and the request data type of the static information of the IC tag and transmitting it to the object information management server, (a) or (c ) And (b) or (d).

  Steps (a) to (d) correspond to four basic search patterns, and the data necessary for traceability can be acquired by the interface in the present embodiment.

  A program for causing a computer to execute the method according to the present invention can be created, and the program is stored in a storage medium or storage device such as a flexible disk, a CD-ROM, a magneto-optical disk, a semiconductor memory, or a hard disk. Is done. In some cases, digital signals are distributed over a network. Note that data being processed is temporarily stored in a storage device such as a computer memory.

  According to the present invention, a reading result of an IC tag such as an RFID tag by a reader can be efficiently used.

  As another aspect of the present invention, a novel interface and platform for using a reading result of an IC tag such as an RFID tag by a reader can be provided.

  The terminology will be explained first for the following explanation. O-ID (Object-ID) is an ID for uniquely identifying an IC tag, and an object to which the IC tag is attached can also be uniquely identified. R-ID (Reader-ID) is an ID for uniquely identifying a reader. Furthermore, O-inf (Object-information) is information related to an object, and includes O-sem and O-his described below. O-sem (Object-semantic) is static information of an object, for example, an article name. Further, O-his (Object-history) is history information composed of a set of R-ID or R-sem of the reader that has read the ID of the IC tag. Also, R-inf (Reader-information) is reader-related information, and includes R-sem and R-his described below. R-sem (Reader-semantic) is information indicating the name of the reader and the meaning of reading. Further, R-his (Reader-history) is history information including a set of O-sems or O-IDs of IC tags read by the reader.

  In the embodiment of the present invention, the network service related to traceability is supported by four basic search patterns. The first search pattern P1 is a search in which O-ID is specified as a search key and O-inf is specified as a request data type. The first search pattern P1 includes a search pattern P1-1 that uses O-sem (for example, a manufacturer name of a product) in O-inf as a request data type, and an O-his (distribution route of the product, that is, the RFID And a search pattern P1-2 having the request data type as the R-sem column of the reader that has read the tag.

  The second search pattern P2 is a search in which R-ID is specified as a search key and R-inf is specified as a request data type. The second search pattern P2 includes a search pattern P2-1 that uses R-sem in R-inf as a request data type and R-his (O-sem string of RFID tags read so far) as a request data type. And a search pattern P2-2. This pattern is useful when searching for items in the vicinity of the leader in inventory management, or when searching for a product that has passed through the gate to which the reader is attached when collecting the product.

  Furthermore, the third search pattern P3 designates an O-sem (for example, a product name or a place name) as a search key, and reads the RFID tag related to the O-sem (for example, an owner, an enrollment). This is a search pattern in which the request data type is a person or a place.

  The fourth search pattern P4 designates an R-sem (for example, a person name, a place name) as a search key, and the RFID tag O-sem (for example, the name of an belonging, the reader's name) read by the reader related to the R-sem. This is a search pattern in which a request data type is the name of a certain item.

  The search pattern P3 is a search pattern that makes the search pattern P1-2 natural, and the search pattern P4 is a search pattern that makes the search pattern P2-2 natural. There are situations in which the user does not know the identification information of the object or reader indicated by the IC tag. Alternatively, there may be a situation where there is no reader even if the object with the IC tag attached is in front of the user and detailed information of the object cannot be acquired. Even in such a situation, by specifying static information such as a name that is close to a natural language, it is possible to specify these and search for detailed information, thereby improving convenience.

  In the present embodiment, various search services can be provided by the above search patterns or combinations thereof. As described above, the user can use the search key as identification information of the IC tag attached to the object, identification information of the reader, static information such as the name of the object indicated by the IC tag, Detailed information can be searched by specifying one of static information such as the name of the place where the reader is installed.

  Furthermore, it is possible to provide an advanced service by combining a plurality of search patterns. For example, assume an advertisement distribution service that sends an advertisement to a person who has not purchased a new product of the same series (for example, a new publication of the same comic magazine) among purchasers of a certain series of products (for example, a comic magazine). The advertisement distributor needs to search for the owner of the corresponding product as the first step. If the product identification number is known, search pattern 1 using the search key as a search key, or if the product identification number is unknown, start search pattern 3 using the product name as the search key, and read the IC tag of the product By specifying the reader, it is possible to specify the purchaser of the product. As a second step, the advertisement distributor needs to confirm whether the owner of the corresponding product already has the new product. In this case, if the purchaser's identification number is known, search pattern 2 using that as a search key is activated, and if the identification number is unknown, search pattern 4 using the purchaser's name as a search key is activated. By specifying the IC tag attached to the belongings, it is possible to confirm whether the new product is already owned. If the person doesn't own the new product yet, whether the terminal he / she owns to send the advertisement is a mobile phone, PC (Personal Computer), PDA (Personal Digital Assistant), TV, etc. Can be confirmed at the same time, so it is sufficient to select the most suitable terminal and send an advertisement for a new product.

  Next, FIG. 1 shows a system outline diagram according to the present embodiment. A network 1 such as the Internet is connected to one or a plurality of DB servers 3 having a configuration described below, a plurality of RFID readers 5 and a plurality of search terminals 7. The RFID tag 11 is attached to the product 9, for example, and the data (for example, RFID) held by the RFID tag 5 is read by the RFID reader 5 disposed at a predetermined position, for example. The RFID reader 5 transmits the data read from the RFID tag 11 to the DB server 3 for registration. How to register is described in detail below. Further, the search terminal 7 performs processing for extracting from the DB server 3 the reading results of the RFID reader 5 stored and managed in the DB server 3 in accordance with any of the four basic search patterns described above. The DB server 3 performs a search process in response to a search request from the search terminal 7, receives data such as a read result from the RFID reader 5, and performs a registration process.

  Next, the relationship between the DB server 3 and the search terminal 7 is schematically shown using FIG. A traceability platform middleware is installed in the DB server 3 and the search terminal 7, and an API (Application Program Interface) -1 with an application executed on the search terminal 7 by the traceability platform middleware, and a DB server API-2 with the DB search unit 31 in FIG. In this traceability platform / middleware, a search interface unit 71 that executes a distribution process of a search request (search key, request data type, range) input via API-1 and a search pattern P1 in the search interface unit 71 The pattern 1 search processing unit 101 that performs processing in the search terminal 7 and the DB server 3 when it is determined to be present, and the search terminal 7 and the DB server 3 when the search interface unit 71 determines that the search pattern P2 is present. A pattern 2 search processing unit 102 that performs processing within the search terminal 7, a pattern 3 search processing unit 103 that performs processing within the search terminal 7 and the DB server 3 when the search interface unit 71 determines that the search pattern P 3 is detected, and a search In the interface unit 71, the search pattern P4 Includes a pattern 4 search processing unit 104 when it is determined that performing the process in the search terminal 7 and inside the DB server 3. In the case described below, there are cases where a plurality of DB servers 3 cooperate to process a search pattern. In such a case, a module constituting a search processing unit of the traceability platform / middleware in the plurality of DB servers 3. Work together.

  The search interface unit 71 determines one of the search patterns P1 to P4 based on the search key in the search request. Further, the search pattern P1-1 or P1-2 and the search pattern P2-1 or P2-2 are determined based on the request data type.

  Moreover, the relationship between the DB server 3 and the RFID reader 5 is schematically shown using FIG. A traceability platform middleware is installed in the DB server 3 and the RFID reader 5, and the API-3 with the ID reading unit 51 executed by the RFID reader 5 and the DB server 3 are installed by the traceability platform middleware. API-2 with the DB registration unit 32 is provided. The traceability platform middleware includes a data registration processing unit 105 executed in the RFID reader 5 and the DB server 3. In the case described below, there are cases where a plurality of DB servers 3 cooperate to perform registration processing. In such a case, the plurality of DB servers 3 constitute the data registration processing unit 105 of the traceability platform / middleware. Modules that perform this process in cooperation.

  Next, the configuration of the DB server 3 will be described by dividing it into three models according to the storage form of data read from the RFID tag 11 by the RFID reader 5.

(1) 1st model As a premise of this model, O-ID is stored in the RFID tag 11, O-sem is registered in the DB server 3, and O-his is also registered in the DB server 3. R-ID is registered in the RFID reader 5, R-sem is registered in the DB server 3, and R-his is also registered in the DB server 3.

  In the model 1-1 among the first models, the DB server 3 includes an object information management server 301 and a reader information management server 302 as shown in FIG. Then, the object information management server 301 manages the relationship between the O-ID, its O-sem, and O-his (R-ID string). Note that R-ID # 1 and R-ID # 2 indicate that a plurality of R-IDs are registered. The reader information management server 302 manages the relationship among R-ID, R-sem, and R-his (O-ID column). Note that O-ID # 1 and O-ID # 2 indicate that a plurality of O-IDs are registered. Model 1-1 shows a mode in which a pair of R-ID and O-ID specified by the RFID reader 5 is directly registered in the object information management server 301 and the reader information management server 302.

  In the model 1-2 of the first models, the DB server 3 includes an object & reader information management server 303 as shown in FIG. Then, the object & reader information management server 303 determines the relationship between the O-ID, its O-sem and O-his (R-ID column), and the R-ID, R-sem and R-his (O-ID column). ). That is, the object information management server 301 and the reader information management server 302 are integrated. Model 1-2 shows a mode in which a pair of R-ID and O-ID specified by the RFID reader 5 is directly registered in the object & reader information management server 303.

  An example of data registered in the object information management server 301 is shown in FIG. In the example of FIG. 6, the O-ID column, the O-sem column, the R-ID of the reader that read the corresponding column, and the date and time when the RFID reader 5 of the R-ID has read the RFID tag 11. And a column for registering an IP address of a reader information management server in which detailed information of the RFID reader 5 is managed.

  As shown in FIG. 6, for example, an object with an O-ID of 9370703 is PC FM xyz, and the IDs of the three readers who read it are stored. For example, as the information about the first O-his, that is, the first R-ID, the reader with the reader ID 7053528 reads “05053013040”, that is, May 13, 2005 at 8:40. It has come to understand. Also, it is shown here that the reader with the reader ID 7053528 is written in the reader information management server with the IP address 10.25.192.4. The static information of the reader can be easily obtained. In addition, since the date and time when the reader reads the object is managed, it is possible to perform a search specifying a time range. For example, for a PC FM xyz that is an object with an O-ID of 9370703, in the case of a search in which the time range after May 14, 2005 is specified as a time range, only information whose time information is greater than “05014000” is the search target. Therefore, only the third reader ID 8588 whose time data is “0505147130” is answered.

  Similarly, in the reader information management server 302, information such as an R-ID column, an R-sem column, an O-ID of an object read by the reader, and a date and time of reading are registered correspondingly. A search with a specified time range is also possible.

(2) Second model As a premise of this model, O-ID is stored in the RFID tag 11, O-sem is registered in the DB server 3, and O-his is also registered in the DB server 3. R-ID is not handled, R-sem is registered in the RFID reader 5, and R-his is registered in the DB server 3.

  In the model 2-2 of the second models, the DB server 3 includes an object information management server 304 as shown in FIG. The object information management server 304 manages the relationship among the O-ID, O-sem, and O-his (R-sem column). Note that R-sem # 1 and R-sem # 2 indicate that a plurality of R-sems are registered. Since model 2-1 does not handle R-ID, a mode in which a pair of O-ID and R-sem specified by RFID reader 5 is registered is shown.

  In the model 2-1, among the second models, the DB server 3 includes an object information management server 305 and a reader information management server 306 as shown in FIG. The object information management server 305 manages the relationship between the O-ID, O-sem, and O-his (R-sem column), and the reader information management server 306 manages the R-sem and R-his (O-his). sem column). In the model 2-2, a pair of R-sem and O-ID specified by the RFID reader 5 is registered in the object information management server 305, and the O-sem corresponding to the R-sem and O-ID is derived as a reader. An aspect of registration in the information management server 306 is shown.

(3) Third model As a premise of this model, the O-ID is stored in the RFID tag 11, the O-sem is registered in the DB server 3, and the O-his is also registered in the DB server 3. The R-ID is registered in the RDID reader 5, the R-sem is registered in the DB server 3, and the R-his is also registered in the DB server 3.

  In the model 3-1, among the third models, the DB server 3 includes an object information management server 307 and a reader information management server 308 as shown in FIG. Then, the object information management server 307 manages the relationship between the O-ID, its O-sem, and O-his (R-sem column). The reader information management server 308 manages the relationship between the R-ID and R-sem. In the model 3-1, the object information management server uses the R-ID and O-ID pair specified by the RFID reader 5 and the R-ID and R-sem registered in the reader information management server 308. Reference numeral 307 denotes a mode in which R-sem is registered corresponding to the O-ID.

  In the model 3-2 of the third model, the DB server 3 includes an object information management server 309 and a reader information management server 310 as shown in FIG. Then, the object information management server 309 manages the relationship between the O-ID, its O-sem, and O-his (R-sem column). Further, the reader information management server 310 manages the relationship among the R-ID, R-sem, and R-his (R-sem column). In the model 3-2, a pair of R-ID and O-sem is read using a pair of R-ID and O-ID specified by the RFID reader 5 and the object information management server 309 and the reader information management server 310. A mode in which a pair of O-ID and R-sem is registered in the object information management server 300 is registered in the information management server 310 is shown.

  FIG. 11 shows an example of data registered in the object information management server 309 in the third model. In the example of FIG. 11, the O-ID column, the O-sem column, the R-sem of the reader that read the column correspondingly, and the RFID reader 5 of the R-sem read the RFID tag 11. A column for registering the date and time and the IP address of the reader information management server in which detailed information of the RFID reader 5 is managed is registered.

  As shown in FIG. 11, for example, an object with an O-ID of 9370703 is PC FM xyz, and static information of three readers that read the object is stored. For example, the reader who last read this object, that is, the reader with the largest value related to the date and time, is the reader in SS Kamata 5FB01 whose date and time information is “0505147130”, and the reading time is May 14, 2005 You can see that it is 17:30 on the day. When it is necessary to know the detailed information of this reader, the IP address 10.25.144.129 is also stored. By accessing the reader information management server at this address, other detailed information such as what has been read can be obtained. May be tracked. Similarly to the description of FIG. 6, since the date and time when the reader reads the object is managed, it is possible to perform a search specifying a time range. For example, if you want to investigate the movement in January 2005 of DVD JUP, which is an object with O-ID 41551, the date and time search range is from January 1, 2005, 00:00, that is, “0501010000” to January 2005. The data of the object information management server 309 may be searched using the search range of 23:59 on 31st, that is, “0501312359”. Then, this server searches for the specified date and time range, and it was read at 14:20 on January 4, 2005 with the reader of Aobadai XX4F, and the main gate of elementary school at 22:10 on January 9, 2005. It is answered that it was read by the reader.

  Similarly, in the reader information management server 310, information such as the R-ID column, the R-sem column, the O-ID of the object read by the reader and the date and time of reading are registered correspondingly. A search with a specified time range is also possible.

  Next, registration and search processing in each model will be described.

(1-1) Model 1-1
(1-1-A) Registration Processing Registration processing in the model 1-1 will be described with reference to FIG. When reading the O-ID from the RFID tag 11, the ID reading unit 51 of the RFID reader 5 outputs a registration request to the data registration processing unit 105 via the API-3. In response to the registration request, the data registration processing unit 105 on the RFID reader 5 side generates a registration message using the O-ID as a key, O-his as the key details, and R-ID as registration information. Is transmitted to the object information management server 301 (step (1)). FIG. 13A shows an example of the message format of the registration message. The registration message includes a registration message header, a registration location key and key details, and registration information. The data registration processing unit 105 on the object information management server 301 side receives the registration message, and outputs the data included in the registration message to the DB registration unit 32 via API-2 as a registration request. The DB registration unit 32 of the object information management server 301 registers R-ID, which is registration information, in the DB as O-his with key details corresponding to the O-ID.

  The data registration processing unit 105 on the RFID reader 5 side generates a registration message using the R-ID as a key, R-his as a key detail, and O-ID as registration information. It transmits to the information management server 302 (step (2)). The format of the registration message is as shown in FIG. The data registration processing unit 105 on the reader information management server 302 side receives the registration message, and outputs the data included in the registration message to the DB registration unit 32 as a registration request via API-2. The DB registration unit 32 of the reader information management server 302 registers O-ID, which is registration information, in the DB as R-his with key details corresponding to the R-ID.

  Thus, although it is a two-stage process, a simple registration process may be performed.

(1-1-B) Search Process On the other hand, the search process is performed as shown in FIG. 14 for each basic search pattern. First, a search request including a key, a request data type, and a search range is output from the application 1 of the search terminal 7 to the search interface unit 71 via API-1. The search interface unit 71 specifies a search pattern from the search request key and the request data type.

(1-1-B-1) Search pattern P1-1
When the search request key is O-ID and the request data type is O-sem, the search interface unit 71 searches the pattern 1 search processing unit 101 on the search terminal 7 side because the search pattern P1-1. Output request data. In response to the search request, the pattern 1 search processing unit 101 on the search terminal 7 side generates a search request message using the O-ID as a search key and O-sem as the request search information. It transmits to the information management server 301 (step (1)). FIG. 13B shows an example of the message format of the search request message. The search request message includes a search request message header, a search request source address or ID, a message number (MN), a search key, and request search information. The pattern 1 search processing unit 101 on the object information management server 301 side receives the search request message and outputs the data included in the search request message to the DB search unit 31 via API-2. The DB search unit 31 of the object information management server 301 searches the DB using the O-ID as a search key, and extracts data of the requested data type O-sem.

  Thereafter, the DB search unit 31 outputs the extracted O-sem to the pattern 1 search processing unit 101 on the object information management server 301 side via API-2. The pattern 1 search processing unit 101 on the object information management server 301 side generates a search response message using O-sem as search information, and transmits it to the pattern 1 search processing unit 101 on the search terminal 7 side via the network 1 ( Step (2)). FIG. 13C shows an example of the message format of the search response message. The search response message includes the header of the search response message, the address or ID of the search request source, the message number (MN), and the extracted search information. The pattern 1 search processing unit 101 on the search terminal 7 side receives the search response message and outputs search result data included in the search response message to the search interface unit 71. The search interface unit 71 outputs O-sem as a search result to the request source application 1 via API-1.

(1-1-B-2) Search pattern P1-2
In addition, when the search request key is O-ID and the request data type is O-his (R-sem), the search interface unit 71 displays the pattern on the search terminal 7 side because the search pattern P1-2. 1 Search request data is output to the search processing unit 101. The pattern 1 search processing unit 101 on the search terminal 7 side uses O-ID as a first search key, a code representing the type of R-ID as a second key, and requests search for O-his (R-sem). An extended search request message as information is generated and transmitted to the object information management server 301 via the network 1 (step (1)). FIG. 15A shows an example of the message format of the extended search request message. The extended search request message is specified in the header of the extended search request message, the address or ID of the request source of the search request, the message number (MN), the first search key specified by the request source, and the first destination DB server 3. Second search key (type is specified at the request source) and request search information. Specifically, in this step, an extended search request message as shown in FIG. 15B is generated and transmitted. That is, the first search key is an O-ID, the second search key is a code representing the type of R-ID, and the requested search information is O-his (R-sem).

  The pattern 1 search processing unit 101 on the object information management server 301 side receives the extended search request message, and includes data included in the extended search request message (here, the type of search key O-ID and R-ID which is the request data type). Is output to the DB search unit 31 via API-2. The DB search unit 31 of the object information management server 301 searches the DB using the O-ID as a search key, and extracts a correspondingly registered R-ID string.

  Thereafter, the DB search unit 31 outputs the extracted R-ID string to the pattern 1 search processing unit 101 on the object information management server 301 side via API-2. The pattern 1 search processing unit 101 on the object information management server 301 side embeds one R-ID in the received R-ID string instead of a code representing the type of R-ID in one extended search request message, As a result, an extended search request message for the number of R-IDs included in the R-ID column is generated and transmitted to the reader information management server 302 via the network 1 (step (2)). In FIG. 14, #n represents the number of R-IDs in the R-ID column. Further, when there are a plurality of reader information management servers 302, it is necessary to change the destination for each R-ID.

  The pattern 1 search processing unit 101 on the reader information management server 302 side receives the extended search request message via the network 1, and includes data included in the extended search request message (here, the second search key R-ID and the request data). The type O-his (R-sem)) is output to the DB search unit 31 via API-2. The DB search unit 31 of the reader information management server 302 searches the DB using the R-ID as a search key, and extracts the corresponding R-sem. Processing is performed for each received extended search request message.

  Then, the DB search unit 31 outputs the extracted O-his R-sem to the pattern 1 search processing unit 101 on the reader information management server 302 side via API-2. The pattern 1 search processing unit 101 on the reader information management server 302 side generates a search response message including O-his (R-sem) in accordance with the format of the search response message in FIG. The request is transmitted to the requesting search terminal 7 (step (3)). The search information of one search response message may include all R-sems extracted by the reader information management server 302. The pattern 1 search processing unit 101 on the search terminal 7 side receives the search response message and outputs O-his (R-sem) included in the search response message to the search interface unit 71. The search interface unit 71 collectively outputs O-his (R-sem) as a search result to the request source application 1 via API-1.

  In the above example, the object information management server 301 manages the search state. However, the search state may be managed on the search terminal 7 side. The latter case will be described later together with address resolution. The search pattern P2-1 is considered to be executed less frequently, and the description is omitted because the processing is performed on the reader information management server 302 instead of the object information management server 301 in the search pattern P1-1.

(1-1-B-3) Search pattern P2-2
Further, when the key of the search request is R-ID and the request data type is R-his (O-sem), the search interface unit 71 uses the search terminal 7 side pattern because the search pattern P2-2. 2 Search request data is output to the search processing unit 102. The pattern 2 search processing unit 102 on the search terminal 7 side uses the R-ID as the first search key according to the search request, the code representing the type of O-ID as the second search key, and R-his (O-sem ) Is generated and sent to the reader information management server 302 via the network 1 (step (1)). In this step, an extended search request message as shown in FIG. 15C is generated and transmitted. That is, the first search key is the R-ID of the search request, the second search key is a code indicating the type of O-ID, and the request search information is R-his (O-sem).

  The pattern 2 search processing unit 102 on the reader information management server 302 side receives the extended search request message, and includes the data included in the extended search request message (here, the type of search key R-ID and request data type O-ID). Is output to the DB search unit 31 via API-2 as a search request. The DB search unit 31 of the reader information management server 302 searches the DB using the R-ID as a search key, and extracts a correspondingly registered O-ID string.

  Thereafter, the DB search unit 31 outputs the extracted O-ID string to the pattern 2 search processing unit 102 on the reader information management server 302 side via API-2. The pattern 2 search processing unit 102 on the reader information management server 302 side embeds one O-ID in the received O-ID string instead of a code representing the type of O-ID in one extended search request message, As a result, an extended search request message for the number of O-IDs included in the O-ID column is generated and transmitted to the object information management server 301 via the network 1 (step (2)). When there are a plurality of object information management servers 301, the destination is changed for each O-ID.

  The pattern 2 search processing unit 102 on the object information management server 301 side receives the extended search request message via the network 1 and receives data included in the extended search request message (here, the search key O-ID and the requested data type R-). his (O-sem)) is output as a search request to the DB search unit 31 via API-2. The DB search unit 31 of the object information management server 301 searches the DB using the O-ID as a search key, and extracts the corresponding O-sem. Processing is performed for each received extended search request message.

  Then, the DB search unit 31 outputs the extracted R-his O-sem to the pattern 2 search processing unit 102 on the object information management server 301 side via API-2. The pattern 2 search processing unit 102 on the object information management server 301 side generates a search response message including R-his (O-sem) according to the format of the search response message in FIG. The request is transmitted to the requesting search terminal 7 (step (3)). The search information of one search response message may include all O-sems extracted by the object information management server 301. The pattern 2 search processing unit 102 on the search terminal 7 side receives the search response message and outputs R-his (O-sem) included in the search response message to the search interface unit 71. The search interface unit 71 collectively outputs R-his (O-sem) as a search result to the request source application 1 via API-1.

  In the above example, the reader information management server 302 manages the search status. However, the search status may be managed on the search terminal 7 side.

(1-1-B-4) Search pattern P3
Further, when the search request key is O-sem and the request data type is O-his (R-sem), the search interface unit 71 searches for the pattern 3 on the search terminal 7 side. The search request data is output to the processing unit 103. The pattern 3 search processing unit 103 on the search terminal 7 side requests O-his (R-sem) using O-sem as a first search key and a code representing the type of R-ID as a second search key. An extended search request message as search information is generated and transmitted to the object information management server 301 via the network 1 (step (1)). In this step, an extended search request message as shown in FIG. 15 (d) is generated and transmitted. That is, the first search key is a search request O-sem, the second search key is a code representing the type of R-ID, and the request search information is O-his (R-sem).

  The pattern 3 search processing unit 103 on the object information management server 301 side receives the extended search request message, and includes the data included in the extended search request message (here, the type of search key O-sem and R-ID which is the request data type). Is output to the DB search unit 31 via API-2. The DB search unit 31 of the object information management server 301 searches the DB using O-sem as a search key, and extracts a correspondingly registered R-ID string.

  Thereafter, the DB search unit 31 outputs the extracted R-ID string to the pattern 3 search processing unit 103 on the object information management server 301 side via API-2. The pattern 3 search processing unit 103 on the object information management server 301 side embeds one R-ID in the received R-ID string instead of a code indicating the type of R-ID in one extended search request message. As a result, an extended search request message for the number of R-IDs included in the R-ID column is generated and transmitted to the reader information management server 302 via the network 1 (step (2)). If there are a plurality of reader information management servers 302, the destination is changed for each R-ID.

  The pattern 3 search processing unit 103 on the reader information management server 302 side receives the extended search request message via the network 1 and receives data included in the extended search request message (here, the search key R-ID and the request data type O-). His (R-sem)) as a search key is output to the DB search unit 31 via API-2. The DB search unit 31 of the reader information management server 302 searches the DB using the R-ID as a search key, and extracts the corresponding R-sem. Processing is performed for each received extended search request message.

  Then, the DB search unit 31 outputs the extracted O-his R-sem to the pattern 3 search processing unit 103 on the reader information management server 302 side via API-2. The pattern 3 search processing unit 103 on the reader information management server 302 side generates a search response message including O-his (R-sem) in accordance with the format of the search response message in FIG. The request is transmitted to the requesting search terminal 7 (step (3)). The search information of one search response message may include all R-sems extracted by the reader information management server 302. The pattern 3 search processing unit 103 on the search terminal 7 side receives the search response message and outputs O-his (R-sem) included in the search response message to the search interface unit 71. The search interface unit 71 collectively outputs O-his (R-sem) as a search result to the request source application 1 via API-1.

  In the above example, the object information management server 301 manages the search state. However, the search state may be managed on the search terminal 7 side.

(1-1-B-5) Search pattern P4
Furthermore, when the key of the search request is R-sem and the request data type is R-his (O-sem), the search interface unit 71 searches for the pattern 4 on the search terminal 7 side. The search request data is output to the processing unit 104. The pattern 4 search processing unit 104 on the search terminal 7 side requests R-his (O-sem) using R-sem as a first search key and a code representing the type of O-ID as a second key. An extended search request message as information is generated and transmitted to the reader information management server 302 via the network 1 (step (1)). In this step, an extended search request message as shown in FIG. 15 (e) is generated and transmitted. That is, the first search key is a search request R-sem, the second search key is a code representing the type of O-ID, and the request search information is R-his (O-sem).

  The pattern 4 search processing unit 104 on the reader information management server 302 side receives the extended search request message, and includes data included in the extended search request message (here, the type of search key R-sem and O-ID which is the request data type). Is output to the DB search unit 31 as a search request via API-2. The DB search unit 31 of the reader information management server 302 searches the DB using R-sem as a search key, and extracts a correspondingly registered O-ID string.

  Thereafter, the DB search unit 31 outputs the extracted O-ID string to the pattern 4 search processing unit 104 on the reader information management server 302 side via API-2. The pattern 4 search processing unit 104 on the reader information management server 302 side embeds one O-ID in the received O-ID string instead of a code representing the type of O-ID in one extended search request message, As a result, an extended search request message for the number of O-IDs included in the O-ID column is generated and transmitted to the object information management server 301 via the network 1 (step (2)). When there are a plurality of object information management servers 301, the destination is changed for each O-ID.

  The pattern 4 search processing unit 104 on the object information management server 301 side receives the extended search request message via the network 1 and receives data included in the extended search request message (here, the search key O-ID and the request data type R- his (O-sem)) is output to the DB search unit 31 via API-2. The DB search unit 31 of the object information management server 301 searches the DB using the O-ID as a search key, and extracts the corresponding O-sem. Processing is performed for each received extended search request message.

  Then, the DB search unit 31 outputs the extracted R-his O-sem to the pattern 4 search processing unit 104 on the object information management server 301 side via API-2. The pattern 4 search processing unit 104 on the object information management server 301 side generates a search response message including R-his (O-sem) in accordance with the format of the search response message in FIG. The request is transmitted to the requesting search terminal 7 (step (3)). The search information of one search response message may include all O-sems extracted in the object information management server 301. The pattern 4 search processing unit 104 on the search terminal 7 side receives the search response message and outputs R-his (O-sem) included in the search response message to the search interface unit 71. The search interface unit 71 collectively outputs R-his (O-sem) as a search result to the request source application 1 via API-1.

  By performing the processing as described above, it is possible to perform a search for each basic search pattern even when a data holding mode such as model 1-1 is adopted. However, there are many search patterns in which search results cannot be obtained unless the server is accessed in two stages. The search request message from the first-stage server to the second-stage server may have different destinations when the servers are load-balanced.

(1-2) Model 1-2
(1-2A) Registration Processing Registration processing in the model 1-2 will be described with reference to FIG. When reading the O-ID from the RFID tag 11, the ID reading unit 51 of the RFID reader 5 outputs a registration request to the data registration processing unit 105 via the API-3. The data registration processing unit 105 on the RFID reader 5 side sends a registration message using the O-ID as a key, O-his as a key detail, and R-ID as registration information via the network 1 as object & reader information. It transmits to the management server 303 (step (1)). The message format of the registration message is, for example, as shown in FIG. The data registration processing unit 105 on the object and reader information management server 303 side receives the registration message, and outputs the data included in the registration message to the DB registration unit 32 via API-2. The DB registration unit 32 of the object & reader information management server 303 registers R-ID, which is registration information, in the DB as O-his with key details corresponding to the O-ID.

  Further, the data registration processing unit 105 on the RFID reader 5 side transmits a registration message using the R-ID as a key, R-his as a key detail, and O-ID as registration information via the network 1 as an object & The information is transmitted to the reader information management server 303 (step (2)). The format of the registration message is as shown in FIG. The data registration processing unit 105 on the object & reader information management server 303 side receives the registration message and outputs the data included in the registration message to the DB registration unit 32 via API-2. The DB registration unit 32 of the object & reader information management server 303 registers the O-ID, which is registration information, in the DB as R-his with key details corresponding to the R-ID.

  Thus, although it is a two-stage process, a simple registration process may be performed.

(1-2B) Search Process On the other hand, the search process is performed as shown in FIG. 17 for each basic search pattern. First, a search request including a key, a request data type, and a search range is output from the application 1 of the search terminal 7 to the search interface unit 71 via API-1. The search interface unit 71 specifies a search pattern from the search request key and the request data type.

(1-2-B-1) Search pattern P1-1
When the search request key is O-ID and the request data type is O-sem, the search interface unit 71 searches the pattern 1 search processing unit 101 on the search terminal 7 side because the search pattern P1-1. Output request data. The pattern 1 search processing unit 101 on the search terminal 7 side generates a search request message using the O-ID as a search key and O-sem as the requested search information, and sends it to the object & reader information management server 303 via the network 1. Transmit (step (1)). The search request message shown in FIG. 13B is transmitted. The pattern 1 search processing unit 101 on the object & reader information management server 303 side receives the search request message and outputs data included in the search request message to the DB search unit 31 via API-2. The DB search unit 31 of the object & reader information management server 303 searches the DB using the O-ID as a search key, and extracts data of the O-sem of the requested data type.

  Thereafter, the DB search unit 31 outputs the extracted O-sem to the pattern 1 search processing unit 101 on the object & reader information management server 303 side via API-2. The pattern 1 search processing unit 101 on the object & reader information management server 303 side generates a search response message using O-sem as search information via the network 1 and sends it to the pattern 1 search processing unit 101 on the search terminal 7 side. Transmit (step (2)). The search response message shown in FIG. 13C is generated and transmitted. The pattern 1 search processing unit 101 on the search terminal 7 side receives the search response message and outputs search result data included in the search response message to the search interface unit 71. The search interface unit 71 outputs O-sem as a search result to the request source application 1 via API-1.

(1-2-B-2) Search pattern P1-2
In addition, when the search request key is O-ID and the request data type is O-his (R-sem), the search interface unit 71 displays the pattern on the search terminal 7 side because the search pattern P1-2. 1 Search request data is output to the search processing unit 101. The pattern 1 search processing unit 101 on the search terminal 7 side generates a search request message using the O-ID as a search key and O-his (R-sem) as request search information, and sends an object & reader via the network 1. It transmits to the information management server 303 (step (1)). The search request message shown in FIG. 13B is generated and transmitted.

  The pattern 1 search processing unit 101 on the object & reader information management server 303 side receives the search request message, and receives data (here, search key O-ID) included in the search request message and R-ID as the request data type. A search request is output to the DB search unit 31 via API-2. The DB search unit 31 of the object & reader information management server 303 searches the DB using the O-ID as a search key, and extracts a correspondingly registered R-ID string.

  Further, the DB search unit 31 outputs the extracted R-ID string to the pattern 1 search processing unit 101 on the object & reader information management server 303 side via API-2. The pattern 1 search processing unit 101 on the object & reader information management server 303 side receives the R-ID string from the DB search unit 31, and uses each R-ID included in the received R-ID string as a key, and O-his ( A search request having R-sem) as the request data type is output to the DB search unit 31 again.

  The DB search unit 31 receives a search request from the pattern 1 search processing unit 101 using the R-ID as a key and O-his (R-sem) as a request data type, and searches the DB using the R-ID as a search key. Then, R-sem registered correspondingly is extracted (step (2)). In order to search for each R-ID, R-sem is also extracted correspondingly. The DB search unit 31 outputs each extracted R-sem to the pattern 1 search processing unit 101 on the object & reader information management server 303 side. The pattern 1 search processing unit 101 on the object & reader information management server 303 side receives each R-sem from the DB search unit 31 and follows O-his (R-sem) according to the format of the search response message in FIG. Is generated and transmitted to the requesting search terminal 7 via the network 1 (step (3)). The search information of one search response message may include all R-sems. The pattern 1 search processing unit 101 on the search terminal 7 side receives the search response message and outputs O-his (R-sem) included in the search response message to the search interface unit 71. The search interface unit 71 collectively outputs O-his (R-sem) as a search result to the request source application 1 via API-1.

  In the above example, the object & reader information management server 303 manages the search status. However, the search status may be managed on the search terminal 7 side. Further, it is considered that the frequency of execution for the search pattern P2-1 is not high, and the O-ID in the search pattern P1-1 may be replaced with the R-ID, and the O-sem may be R-sem. Description is omitted.

(1-2-B-3) Search pattern P2-2
Further, when the key of the search request is R-ID and the request data type is R-his (O-sem), the search interface unit 71 uses the search terminal 7 side pattern because the search pattern P2-2. 2 Search request data is output to the search processing unit 102. The pattern 2 search processing section 102 on the search terminal 7 side generates a search request message using R-ID as a search key and R-his (O-sem) as request search information. It transmits to the information management server 303 (step (1)). In this step, a search request message as shown in FIG. 13B is generated and transmitted.

  The pattern 2 search processing unit 102 on the object & reader information management server 303 side receives the search request message, and includes data (here, search key R-ID) included in the search request message and O-ID as the request data type. The search request is output to the DB search unit 31 via API-2. The DB search unit 31 of the object & reader information management server 303 receives a search request from the pattern 2 search processing unit 102, searches the DB using the R-ID included in the search request as a search key, and is registered correspondingly. The O-ID column that is present is extracted.

  Further, the DB search unit 31 outputs the extracted O-ID string to the pattern 2 search processing unit 102 on the object & reader information management server 303 side via API-2. The pattern 2 search processing unit 102 on the object & reader information management server 303 side receives the O-ID column from the DB search unit 31, and uses each O-ID included in the received O-ID column as a key and R-his ( A search request having O-sem) as the request data type is output to the DB search unit 31 again.

  The DB search unit 31 receives a search request using the O-ID as a key and R-his (O-sem) as a request data type from the pattern 2 search processing unit 102, and searches the DB using the O-ID as a search key. Then, the corresponding O-sem registered is extracted (step (2)). In order to search for each O-ID, O-sem is also extracted correspondingly. The DB search unit 31 outputs each extracted O-sem to the pattern 2 search processing unit 102 on the object & reader information management server 303 side.

  The pattern 2 search processing unit 102 on the object & reader information management server 303 side generates a search response message including R-his (O-sem) according to the search response message format of FIG. To the requesting search terminal 7 (step (3)). The search information of one search response message may include all O-sems. The pattern 2 search processing unit 102 on the search terminal 7 side receives the search response message and outputs R-his (O-sem) included in the search response message to the search interface unit 71. The search interface unit 71 collectively outputs R-his (O-sem) as a search result to the request source application 1 via API-1.

  In the above example, the object & reader information management server 303 manages the search status. However, the search status may be managed on the search terminal 7 side.

(1-2-B-4) Search pattern P3
Further, when the search request key is O-sem and the request data type is O-his (R-sem), the search interface unit 71 searches for the pattern 3 on the search terminal 7 side. The search request data is output to the processing unit 103. A pattern 3 search processing unit 103 on the search terminal 7 side generates a search request message using O-sem as a search key and O-his (R-sem) as request search information, and sends an object & reader via the network 1. It transmits to the information management server 303 (step (1)). In this step, a search request message as shown in FIG. 13B is generated and transmitted.

  The pattern 3 search processing unit 103 on the object & reader information management server 303 side receives the search request message, and receives data (here, search key O-sem) included in the search request message and R-ID as the request data type. The search request is output to the DB search unit 31 via API-2. The DB search unit 31 of the object & reader information management server 303 searches the DB using O-sem as a search key, and extracts a correspondingly registered R-ID string.

  Further, the DB search unit 31 outputs the extracted R-ID string to the pattern 3 search processing unit 103 on the object & reader information management server 303 side via API-2. The pattern 3 search processing unit 103 on the object & reader information management server 303 side receives the R-ID string from the DB search unit 31, and uses each R-ID included in the received R-ID string as a key, and O-his ( A search request having R-sem) as the request data type is output to the DB search unit 31 again.

  The DB search unit 31 receives a search request using the R-ID as a key and O-his (R-sem) as a request data type from the pattern 3 search processing unit 103, and searches the DB using the R-ID as a search key. Then, R-sem registered correspondingly is extracted (step (2)). In order to search for each R-ID, R-sem is also extracted correspondingly. The DB search unit 31 outputs each extracted R-sem to the pattern 3 search processing unit 103 on the object & reader information management server 303 side. The pattern 3 search processing unit 103 on the object & reader information management server 303 side receives each R-sem from the DB search unit 31, and O-his (R-sem) according to the format of the search response message in FIG. Is generated and transmitted to the requesting search terminal 7 via the network 1 (step (3)). The search information of one search response message may include all R-sems. The pattern 3 search processing unit 103 on the search terminal 7 side receives the search response message and outputs O-his (R-sem) included in the search response message to the search interface unit 71. The search interface unit 71 collectively outputs O-his (R-sem) as a search result to the request source application 1 via API-1.

  In the above example, the object & reader information management server 303 manages the search status. However, the search status may be managed on the search terminal 7 side.

(1-2-B-5) Search pattern P4
Furthermore, when the key of the search request is R-sem and the request data type is R-his (O-sem), the search interface unit 71 searches for the pattern 4 on the search terminal 7 side. The search request data is output to the processing unit 104. The pattern 4 search processing unit 104 on the search terminal 7 side generates a search request message using R-sem as a search key and R-his (O-sem) as request search information, and sends an object & reader via the network 1. It transmits to the information management server 303 (step (1)). In this step, a search request message as shown in FIG. 13B is generated and transmitted.

  The pattern 4 search processing unit 104 on the object & reader information management server 303 side receives the search request message, and receives the data included in the search request message (here, the search key R-sem) and the O-ID as the request data type. The search request including this is output to the DB search unit 31 via API-2. The DB search unit 31 of the object & reader information management server 303 searches the DB using R-sem as a search key, and extracts a correspondingly registered O-ID string.

  Further, the DB search unit 31 outputs the extracted O-ID string to the pattern 4 search processing unit 104 on the object & reader information management server 303 side via API-2. The pattern 4 search processing unit 104 on the object & reader information management server 303 side receives the O-ID column from the DB search unit 31, and uses each O-ID included in the received O-ID column as a key and R-his ( A search request having O-sem) as the request data type is output to the DB search unit 31 again.

  The DB search unit 31 receives a search request using the O-ID as a key and R-his (O-sem) as a request data type from the pattern 4 search processing unit 104, and searches the DB using the O-ID as a search key. Then, the corresponding O-sem registered is extracted (step (2)). In order to search for each O-ID, O-sem is also extracted correspondingly. The DB search unit 31 outputs each extracted O-sem to the pattern 4 search processing unit 104 on the object & reader information management server 303 side.

  The pattern 4 search processing unit 104 on the object & reader information management server 303 side generates a search response message including R-his (O-sem) according to the search response message format of FIG. To the requesting search terminal 7 (step (3)). The search information of one search response message may include all O-sems. The pattern 4 search processing unit 104 on the search terminal 7 side receives the search response message and outputs R-his (O-sem) included in the search response message to the search interface unit 71. The search interface unit 71 collectively outputs R-his (O-sem) as a search result to the request source application 1 via API-1.

  By performing the processing as described above, it is possible to perform a search for each basic search pattern even when a data holding mode such as model 1-2 is adopted. In the present embodiment, since the object information management server and the reader information management server are integrated, communication between servers is not necessary if the scale is small, but is distributed if the scale is large. Intercommunication is required.

(2-1) Model 2-1
(2-1-A) Registration Processing Registration processing in the model 2-1 will be described with reference to FIG. When reading the O-ID from the RFID tag 11, the ID reading unit 51 of the RFID reader 5 outputs a registration request to the data registration processing unit 105 via the API-3. The data registration processing unit 105 on the RFID reader 5 side generates a registration message using the O-ID as a key, O-his as a key detail, and R-sem as registration information, and manages object information via the network 1. It transmits to the server 304 (step (1)). The registration message shown in FIG. 13A is generated and transmitted. The data registration processing unit 105 on the object information management server 304 side receives the registration message and outputs data included in the registration message to the DB registration unit 32 via API-2. The DB registration unit 32 of the object information management server 304 registers R-sem, which is registration information, in the DB as O-his with key details corresponding to the O-ID.

  Since only the object information management server 304 is thus provided, the registration process is simple.

(2-1-B) Search Process On the other hand, the search process is performed as shown in FIG. 19 for each basic search pattern. First, a search request including a key, a request data type, and a search range is output from the application 1 of the search terminal 7 to the search interface unit 71 via API-1. The search interface unit 71 specifies a search pattern from the search request key and the request data type.

(2-1-B-1) Search pattern P1-1
When the search request key is O-ID and the request data type is O-sem, the search interface unit 71 searches the pattern 1 search processing unit 101 on the search terminal 7 side because the search pattern P1-1. Output request data. The pattern 1 search processing unit 101 on the search terminal 7 side generates a search request message using the O-ID as a search key and O-sem as the requested search information, and transmits it to the object information management server 304 via the network 1. (Step (1)). The search request message shown in FIG. 13B is generated and transmitted. The pattern 1 search processing unit 101 on the object information management server 304 side receives the search request message and outputs the data included in the search request message to the DB search unit 31 via API-2. The DB search unit 31 of the object information management server 304 searches the DB using the O-ID as a search key, and extracts data of the requested data type O-sem.

  Thereafter, the DB search unit 31 outputs the extracted O-sem to the pattern 1 search processing unit 101 on the object information management server 304 side via API-2. The pattern 1 search processing unit 101 on the object information management server 304 side generates a search response message using O-sem as search information via the network 1 and transmits the search response message to the pattern 1 search processing unit 101 on the search terminal 7 side. (Step (2)). The search response message shown in FIG. 13C is generated and transmitted. The pattern 1 search processing unit 101 on the search terminal 7 side receives the search response message and outputs search result data included in the search response message to the search interface unit 71. The search interface unit 71 outputs O-sem as a search result to the request source application 1 via API-1.

(2-1-B-2) Search pattern P1-2
In addition, when the search request key is O-ID and the request data type is O-his (R-sem), the search interface unit 71 displays the pattern on the search terminal 7 side because the search pattern P1-2. 1 Search request data is output to the search processing unit 101. The pattern 1 search processing unit 101 on the search terminal 7 side generates a search request message using the O-ID as a search key and O-his (R-sem) as request search information, and manages object information via the network 1. It transmits to the server 304 (step (1)). The search request message shown in FIG. 13B is generated and transmitted.

  The pattern 1 search processing unit 101 on the object information management server 304 side receives the search request message, and includes data included in the search request message (here, search key O-ID, request data type O-his (R-sem)). Is output to the DB search unit 31 via API-2. The DB search unit 31 of the object information management server 304 searches the DB using the O-ID as a search key, and extracts a correspondingly registered R-sem column. Thus, in the model 2-1, since the R-sem sequence can be directly extracted, the search is performed efficiently.

  The DB search unit 31 outputs the extracted R-sem sequence to the pattern 1 search processing unit 101 on the object information management server 304 side. The pattern 1 search processing unit 101 on the object information management server 304 side receives the R-sem string from the DB search unit 31 and includes O-his (R-sem) according to the format of the search response message in FIG. A search response message is generated and transmitted to the requesting search terminal 7 via the network 1 (step (2)). The pattern 1 search processing unit 101 on the search terminal 7 side receives the search response message and outputs O-his (R-sem) included in the search response message to the search interface unit 71. The search interface unit 71 collectively outputs O-his (R-sem) as a search result to the request source application 1 via API-1.

  Note that the search pattern P2 does not exist in the model 2-1 that does not use the R-ID.

(2-1-B-3) Search pattern P3
Further, when the search request key is O-sem and the request data type is O-his (R-sem), the search interface unit 71 searches for the pattern 3 on the search terminal 7 side. The search request data is output to the processing unit 103. The pattern 3 search processing unit 103 on the search terminal 7 side generates a search request message using O-sem as a search key and O-his (R-sem) as request search information, and manages object information via the network 1. It transmits to the server 304 (step (1)). In this step, a search request message as shown in FIG. 13B is generated and transmitted.

  The pattern 3 search processing unit 103 on the object information management server 304 side receives the search request message, and data included in the search request message (here, search key O-sem, request data type O-his (R-sem)). As a search request to the DB search unit 31 via API-2. The DB search unit 31 of the object information management server 304 searches the DB using O-sem as a search key, and extracts an R-sem column registered correspondingly. Thus, in the model 2-1, the R-sem sequence can be extracted directly.

  The DB search unit 31 outputs the extracted R-sem sequence to the pattern 3 search processing unit 103 on the object information management server 304 side. The pattern 3 search processing unit 103 on the object information management server 304 side receives the R-sem column from the DB search unit 31 and includes O-his (R-sem) according to the format of the search response message in FIG. A search response message is generated and transmitted to the requesting search terminal 7 via the network 1 (step (2)). The pattern 3 search processing unit 103 on the search terminal 7 side receives the search response message and outputs O-his (R-sem) included in the search response message to the search interface unit 71. The search interface unit 71 collectively outputs O-his (R-sem) as a search result to the request source application 1 via API-1.

(2-1-B-4) Search pattern P4
Furthermore, when the key of the search request is R-sem and the request data type is R-his (O-sem), the search interface unit 71 searches for the pattern 4 on the search terminal 7 side. The search request data is output to the processing unit 104. The pattern 4 search processing unit 104 on the search terminal 7 side generates a search request message using R-sem as a search key and R-his (O-sem) as request search information, and manages object information via the network 1. It transmits to the server 304 (step (1)). In this step, a search request message as shown in FIG. 13B is generated and transmitted.

  The pattern 4 search processing unit 104 on the object information management server 304 side receives the search request message and sends a search request including data (here, search key R-sem, request data type O-sem) included in the search request message. , Output to the DB search unit 31 via API-2. The DB search unit 31 of the object information management server 304 searches the DB using R-sem as a search key, and extracts a corresponding O-sem group registered. In the model 2-1, since R-sem is not a key, DB reverse lookup processing is required.

  The DB search unit 31 outputs each extracted O-sem to the pattern 4 search processing unit 104 on the object information management server 304 side. The pattern 4 search processing unit 104 on the object information management server 304 side generates a search response message including R-his (O-sem) according to the format of the search response message in FIG. The data is transmitted to the requesting search terminal 7 (step (2)). The pattern 4 search processing unit 104 on the search terminal 7 side receives the search response message and outputs R-his (O-sem) included in the search response message to the search interface unit 71. The search interface unit 71 collectively outputs R-his (O-sem) as a search result to the request source application 1 via API-1.

  If there is one object information management server 304, it is possible to cope with the search pattern P4. However, if the amount of data increases, the object information management server 304 may be distributed. In this case, since it is not known in which object information management server 304 the R-sem is registered, it is necessary to send search request messages to all the object information management servers 304 as shown in FIG.

  That is, the pattern 4 search processing unit 104 on the search terminal 7 side transmits a search request message using R-sem # X as a search key and R-his (O-sem) as request search information via the network 1. It transmits to all the object information management servers 304 (step (1)).

  The pattern 4 search processing unit 104 on the object information management server 304 side receives the search request message, and includes a search request including data included in the search request message (here, search key R-sem, request data type O-sem). Is output to the DB search unit 31 via API-2. The DB search unit 31 of the object information management server 304 searches the DB using R-sem as a search key, and extracts a corresponding O-sem group registered. In the model 2-1, since R-sem is not a key, DB reverse lookup processing is required. In addition, R-sem may not always be extracted.

  The DB search unit 31 outputs each extracted O-sem to the pattern 4 search processing unit 104 on the object information management server 304 side. The pattern 4 search processing unit 104 on the object information management server 304 side generates a search response message including R-his (O-sem) according to the format of the search response message in FIG. It transmits to the search terminal 7 of the request source (steps (2a) (2b) (2c) ...). The pattern 4 search processing unit 104 on the search terminal 7 side receives a search response message from each object information management server 304 and outputs R-his (O-sem) included in the search response message to the search interface unit 71. The search interface unit 71 collectively outputs R-his (O-sem) as a search result to the request source application 1 via API-1.

(2-2) Model 2-2
(2-2A) Registration Processing Registration processing in the model 2-2 will be described with reference to FIG. When reading the O-ID from the RFID tag 11, the ID reading unit 51 of the RFID reader 5 outputs a registration request to the data registration processing unit 105 via the API-3. The data registration processing unit 105 on the RFID reader 5 side uses the O-ID as a key of the first registration location, sets the code representing the type of O-his as the details of the key of the first registration location, and sets R-sem as the first No. 1 registration information, R-sem as a second registration location key, a code representing the type R-his as the details of the second registration location key, and a code representing the type O-sem 2 is generated and transmitted to the object information management server 305 via the network 1 (step (1)). FIG. 22A shows an example of the message format of the extended registration message. The extended registration message shown in FIG. 22A includes an extended registration message header, a first registration location key, a first registration location detail key, first registration information, a second registration location key, The detail key of the second registration location and the second registration information are included. In this step, a message as shown in FIG. 22B is transmitted. That is, the O-ID is used as a first registration location key, the O-his type code is used as the details of the first registration location key, R-sem is used as first registration information, and R-sem is used. The code representing the type is the second registration location key, the code representing the type R-his is the details of the second registration location key, and the code representing the type O-sem is the second registration information. This is an extended registration message.

  The data registration processing unit 105 on the object information management server 305 side receives the extended registration message, and includes the data (the O-ID that is the key, the O-his that is the key details, and the registration information) included in the extended registration message. R-sem) is output to the DB registration unit 32 via API-2 as a registration request. The DB registration unit 32 of the object information management server 305 registers R-sem, which is registration information, in the DB as O-his with key details corresponding to the O-ID.

  When the DB registration unit 32 outputs registration completion to the data registration processing unit 105 on the object information management server 305 side, the data registration processing unit 105 uses the O-ID as a search key and a search request with O-sem as the requested data type. Is output to the DB search unit 31 via API-2. The DB search unit 31 searches the DB according to the search request, extracts the O-sem registered corresponding to the O-ID, and outputs the O-sem to the data registration processing unit 105 as a search result.

  The data registration processing unit 105 completes the extended registration message by embedding O-sem as the second registration information in the received extended registration message, and transmits it to the reader information management server 306 (step (2)). The data registration processing unit 105 on the reader information management server 306 side receives the extended registration message, and includes data included in the extended registration message (R-sem which is a key of the second registration location, and a detailed key of the second registration location) The code representing the type R-his and O-sem as the second registration information are output to the DB registration unit 32 via API-2. The DB registration unit 32 of the reader information management server 306 corresponds to the R-sem that is the key of the second registration location, and converts the O-sem that is the second registration information into the key details of the second registration location. Register in the DB as R-his.

  Thus, it is necessary to register data in the object information management server 305 and the reader information management server 306 in two stages.

(2-2B) Search Process The search process of the model 2-2 is the same as that of the model 2-1, except for the search pattern P4.

  First, a search request including a key, a request data type, and a search range is output from the application 1 of the search terminal 7 to the search interface unit 71 via API-1. The search interface unit 71 specifies a search pattern from the search request key and the request data type.

  When the key of the search request is R-sem and the request data type is R-his (O-sem), it is determined as the search pattern P4, and the search interface unit 71 searches the pattern 4 search processing unit on the search terminal 7 side. The search request data is output to 104. As shown in FIG. 23, the pattern 4 search processing unit 104 on the search terminal 7 side generates a search request message using R-sem # X as a search key and R-his (O-sem) as request search information. Then, the data is transmitted to the reader information management server 306 via the network 1 (step (1)). In this step, a search request message as shown in FIG. 13B is generated and transmitted. If address resolution is performed, the search request message is sent to one destination.

  The pattern 4 search processing unit 104 on the reader information management server 306 side receives the search request message, and includes the data (here, search key R-sem # X, request data type R-his) included in the search request message. The request is output to the DB search unit 31 via API-2. The DB search unit 31 of the reader information management server 306 searches the DB using R-sem # X as a search key, and extracts a correspondingly registered O-sem sequence. Note that the model 2-2 does not require reverse DB processing.

  The DB search unit 31 outputs the extracted O-sem sequence to the pattern 4 search processing unit 104 on the reader information management server 306 side. The pattern 4 search processing unit 104 on the reader information management server 306 side generates a search response message including R-his (O-sem) in accordance with the format of the search response message in FIG. The data is transmitted to the requesting search terminal 7 (step (2)). The pattern 4 search processing unit 104 on the search terminal 7 side receives the search response message and outputs R-his (O-sem) included in the search response message to the search interface unit 71. The search interface unit 71 collectively outputs R-his (O-sem) as a search result to the request source application 1 via API-1.

  By preparing the reader information management server 306 in this way, the search process is made efficient.

(3-1) Model 3-1
(3-1-A) Registration Processing Registration processing in the model 3-1 will be described with reference to FIG. When reading the O-ID from the RFID tag 11, the ID reading unit 51 of the RFID reader 5 outputs a registration request to the data registration processing unit 105 via the API-3. The data registration processing unit 105 on the RFID reader 5 side generates a search request message using the R-ID as a key and a code indicating the type of R-sem as request search information, and the reader information management server 308 via the network 1. (Step (1)). The data registration processing unit 105 of the reader information management server 308 receives a search request message from the RFID reader 5, and creates a DB search request using the R-ID included in the search request message as a key and R-sem as the requested data type. Output to the search unit 31. The DB search unit 31 of the reader information management server 308 searches the DB using the R-ID as a key, and extracts the R-sem registered correspondingly.

  The DB search unit 31 outputs the extracted R-sem as a search result to the data registration processing unit 105 on the reader information management server 308 side. The data registration processing unit 105 on the reader information management server 308 side receives the search result R-sem, generates a search response message including the R-sem, and transmits it to the data registration processing unit 105 on the RFID reader 5 side ( Step (2)).

  When receiving a search response message including R-sem, the data registration processing unit 105 on the RFID reader 5 side uses O-ID as a key, O-his as key details, and R-sem as registration information. Is transmitted to the object information management server 307 (step (3)). The registration message shown in FIG. 13A is generated and transmitted. The data registration processing unit 105 on the object information management server 307 side receives the registration message, and outputs the data included in the registration message to the DB registration unit 32 via API-2. The DB registration unit 32 of the object information management server 307 registers R-sem, which is registration information, in the DB as O-his with key details corresponding to the O-ID.

  In this way, using the reader information management server 308, the object information management server 307 registers the R-sem corresponding to the O-ID.

(3-1-B) Search Process On the other hand, the search process is performed as shown in FIG. 25 for each basic search pattern. First, a search request including a key, a request data type, and a search range is output from the application 1 of the search terminal 7 to the search interface unit 71 via API-1. The search interface unit 71 specifies a search pattern from the search request key and the request data type.

(3-1-B-1) Search pattern P1-1
When the search request key is O-ID and the request data type is O-sem, the search interface unit 71 searches the pattern 1 search processing unit 101 on the search terminal 7 side because the search pattern P1-1. Output request data. The pattern 1 search processing unit 101 on the search terminal 7 side generates a search request message using the O-ID as a search key and O-sem as the requested search information, and transmits it to the object information management server 307 via the network 1. (Step (1)). The search request message shown in FIG. 13B is generated and transmitted. The pattern 1 search processing unit 101 on the object information management server 307 side receives the search request message and outputs data included in the search request message to the DB search unit 31 via API-2. The DB search unit 31 of the object information management server 307 searches the DB using the O-ID as a search key, and extracts data of the requested data type O-sem.

  Thereafter, the DB search unit 31 outputs the extracted O-sem to the pattern 1 search processing unit 101 on the object information management server 307 side via API-2. The pattern 1 search processing unit 101 on the object information management server 307 side transmits a search response message having O-sem as search information to the pattern 1 search processing unit 101 on the search terminal 7 side via the network 1 (step ( 2)). The search response message shown in FIG. 13C is transmitted. The pattern 1 search processing unit 101 on the search terminal 7 side receives the search response message and outputs search result data included in the search response message to the search interface unit 71. The search interface unit 71 outputs O-sem as a search result to the request source application 1 via API-1.

(3-1-B-2) Search pattern P1-2
In addition, when the search request key is O-ID and the request data type is O-his (R-sem), the search interface unit 71 displays the pattern on the search terminal 7 side because the search pattern P1-2. 1 Search request data is output to the search processing unit 101. The pattern 1 search processing unit 101 on the search terminal 7 side generates a search request message using the O-ID as a search key and O-his (R-sem) as request search information, and manages object information via the network 1. It transmits to the server 307 (step (1)). The search request message shown in FIG. 13B is generated and transmitted.

  The pattern 1 search processing unit 101 on the object information management server 307 side receives the search request message, and includes data included in the search request message (here, the search key O-ID and the request data type O-his (R-sem). ) Is output to the DB search unit 31 via API-2 as a search request. The DB search unit 31 of the object information management server 307 searches the DB using the O-ID as a search key, and extracts a correspondingly registered R-sem column.

  Then, the DB search unit 31 outputs the extracted O-his R-sem sequence to the pattern 1 search processing unit 101 on the object information management server 307 side via API-2. The pattern 1 search processing unit 101 on the object information management server 307 side generates a search response message including O-his (R-sem) in accordance with the format of the search response message in FIG. The data is transmitted to the requesting search terminal 7 (step (2)). The pattern 1 search processing unit 101 on the search terminal 7 side receives the search response message and outputs O-his (R-sem) included in the search response message to the search interface unit 71. The search interface unit 71 collectively outputs O-his (R-sem) as a search result to the request source application 1 via API-1.

  Note that the search pattern P2-1 is considered to be executed less frequently, and the description is omitted because only the R-ID is used instead of the O-ID in the search pattern P1-1.

(3-1-B-3) Search pattern P2-2
Further, when the key of the search request is R-ID and the request data type is R-his (O-sem), the search interface unit 71 uses the search terminal 7 side pattern because the search pattern P2-2. 2 Search request data is output to the search processing unit 102. The pattern 2 search processing unit 102 on the search terminal 7 side requests R-his (O-sem) using the R-ID as the first search key and the code representing the type R-sem as the second search key. An extended search request message as search information is generated and transmitted to the reader information management server 308 via the network 1 (step (1)).

  The pattern 2 search processing unit 102 on the reader information management server 308 side receives the extended search request message, and includes data included in the extended search request message (here, the type of search key R-ID and request data type R-sem). Is output to the DB search unit 31 via API-2. The DB search unit 31 of the reader information management server 308 searches the DB using the R-ID as a search key, and extracts the R-sem registered correspondingly.

  Thereafter, the DB search unit 31 outputs the extracted R-sem to the pattern 2 search processing unit 102 on the reader information management server 308 side via API-2. The pattern 2 search processing unit 102 on the reader information management server 308 side generates an extended search request message by embedding the received R-sem instead of a code representing the type of R-sem of one extended search request message. To the object information management server 307 via the network 1 (step (2)).

  The pattern 2 search processing unit 102 on the object information management server 307 side receives the extended search request message via the network 1, and includes data included in the extended search request message (here, R-sem as a key and request data type). A certain R-his (O-sem)) is output to the DB search unit 31 via API-2. The DB search unit 31 of the object information management server 307 searches the DB using the R-sem as a search key, and extracts the corresponding O-sem. Since R-sem is not a key in the DB of the object information management server 307, a reverse lookup process for the DB is required. A plurality of O-sems may be extracted or may not be extracted at all.

  Then, the DB search unit 31 outputs the extracted R-his O-sem to the pattern 2 search processing unit 102 on the object information management server 307 side via API-2. The pattern 2 search processing unit 102 on the object information management server 307 side generates a search response message including R-his (O-sem) in accordance with the format of the search response message in FIG. The request is transmitted to the requesting search terminal 7 (step (3)). The search information of one search response message may include all O-sems. The pattern 2 search processing unit 102 on the search terminal 7 side receives the search response message and outputs R-his (O-sem) included in the search response message to the search interface unit 71. The search interface unit 71 collectively outputs R-his (O-sem) as a search result to the request source application 1 via API-1.

  In the above example, the reader information management server 308 manages the search state. However, the search state may be managed on the search terminal 7 side. Although not explicitly shown in FIG. 25, when the object information management server 307 is distributed, it is necessary to transmit an extended registration message to the plurality of object information management servers 307. That is, it is necessary to grasp all the object information management servers 307 and collect search response messages from the plurality of object information management servers 307.

(3-1-B-4) Search pattern P3
Further, when the search request key is O-sem and the request data type is O-his (R-sem), the search interface unit 71 searches for the pattern 3 on the search terminal 7 side. The search request data is output to the processing unit 103. The pattern 3 search processing unit 103 on the search terminal 7 side generates a search request message using O-sem as a search key and O-his (R-sem) as request search information, and manages object information via the network 1. It transmits to the server 307 (step (1)). In this step, a search request message as shown in FIG. 13B is generated and transmitted.

  The pattern 3 search processing unit 103 on the object information management server 307 side receives the search request message, and includes data included in the search request message (here, the search key O-sem and the request data type O-his (R-sem)). Is output to the DB search unit 31 via API-2. The DB search unit 31 of the object information management server 307 searches the DB using O-sem as a search key, and extracts an R-sem column registered correspondingly.

  Thereafter, the DB search unit 31 outputs the extracted R-sem sequence to the pattern 3 search processing unit 103 on the object information management server 307 side via API-2. The pattern 3 search processing unit 103 on the object information management server 307 side generates a search response message including O-his (R-sem) in accordance with the format of the search response message in FIG. The data is transmitted to the requesting search terminal 7 (step (2)). The pattern 1 search processing unit 101 on the search terminal 7 side receives the search response message and outputs O-his (R-sem) included in the search response message to the search interface unit 71. The search interface unit 71 collectively outputs O-his (R-sem) as a search result to the request source application 1 via API-1.

  Since the object information management server 307 holds the R-sem column, it can be directly searched.

(3-1-B-5) Search pattern P4
Furthermore, when the key of the search request is R-sem and the request data type is R-his (O-sem), the search interface unit 71 searches for the pattern 4 on the search terminal 7 side. The search request data is output to the processing unit 104. The pattern 4 search processing unit 104 on the search terminal 7 side sends a search request message using the R-sem as a search key and R-his (O-sem) as request search information via the network 1 to the object information management server. It transmits to 307 (step (1)). In this step, a search request message as shown in FIG. 13B is generated and transmitted.

  The pattern 4 search processing unit 104 on the object information management server 307 side receives the search request message, and includes data included in the search request message (here, the search key R-sem and the request data type R-his (O-sem). ) Is output to the DB search unit 31 via API-2 as a search request. The DB search unit 31 of the object information management server 307 searches the DB using R-sem as a search key and extracts a corresponding O-sem group. Since R-sem is not a DB key of the object information management server 307, reverse DB processing is required.

  Then, the DB search unit 31 outputs the extracted R-his O-sem group to the pattern 4 search processing unit 104 on the object information management server 307 side via API-2. The pattern 4 search processing unit 104 on the object information management server 307 side generates a search response message including R-his (O-sem) according to the format of the search response message in FIG. The data is transmitted to the requesting search terminal 7 (step (2)). The pattern 4 search processing unit 104 on the search terminal 7 side receives the search response message and outputs R-his (O-sem) included in the search response message to the search interface unit 71. The search interface unit 71 collectively outputs R-his (O-sem) as a search result to the request source application 1 via API-1.

  Although not shown in FIG. 25, when the object information management server 307 is distributed, it is necessary to transmit a search request message to the plurality of object information management servers 307. That is, it is necessary to grasp all the object information management servers 307 and collect search response messages from the plurality of object information management servers 307.

(3-1) Model 3-2
(3-2-A) Registration Processing Registration processing in the model 3-2 will be described with reference to FIG. When reading the O-ID from the RFID tag 11, the ID reading unit 51 of the RFID reader 5 outputs a registration request to the data registration processing unit 105 via the API-3. The data registration processing unit 105 on the RFID reader 5 side generates a search request message using the R-ID as a key and a code representing the type of R-sem as request search information, and the reader information management server 310 via the network 1. (Step (1)). The data registration processing unit 105 on the reader information management server 310 side receives a search request message from the RFID reader 5 and sends a search request with R-sem as a request data type using the R-ID included in the search request message as a key. The data is output to the DB search unit 31. The DB search unit 31 of the reader information management server 310 searches the DB using the R-ID as a key, and extracts the R-sem registered correspondingly.

  The DB search unit 31 outputs the extracted R-sem as a search result to the data registration processing unit 105 on the reader information management server 310 side. The data registration processing unit 105 on the reader information management server 310 side receives the search result R-sem, generates a search response message including the R-sem, and transmits it to the data registration processing unit 105 on the RFID reader 5 side ( Step (2)).

  When receiving a search response message including R-sem, the data registration processing unit 105 on the RFID reader 5 side uses O-ID as a key, O-his as key details, and R-sem as registration information. Is transmitted to the object information management server 309 (step (3)). The registration message shown in FIG. 13A is generated and transmitted. The data registration processing unit 105 on the object information management server 309 side receives the registration message, and outputs data included in the registration message to the DB registration unit 32 via API-2. The DB registration unit 32 of the object information management server 309 registers R-sem, which is registration information, in the DB as O-his with key details corresponding to the O-ID.

  Further, the data registration processing unit 105 on the RFID reader 5 side generates a search request message using the O-ID as a key and a code indicating the type of O-sem as request search information via the network 1, and object information It transmits to the management server 309 (step (4)). The data registration processing unit 105 of the object information management server 309 receives a search request message from the RFID reader 5 and creates a DB search request with O-sem as a requested data type using the O-ID included in the search request message as a key. Output to the search unit 31. The DB search unit 31 of the object information management server 309 searches the DB using the O-ID as a key, and extracts an O-sem registered correspondingly.

  The DB search unit 31 outputs the extracted O-sem as a search result to the data registration processing unit 105 on the object information management server 309 side. The data registration processing unit 105 on the object information management server 309 side receives the search result O-sem, generates a search response message including the O-sem, and transmits it to the data registration processing unit 105 on the RFID reader 5 side ( Step (5)).

  When receiving the search response message including O-sem, the data registration processing unit 105 on the RFID reader 5 side uses R-ID as a key, R-his as key details, and O-sem as registration information. Is transmitted to the reader information management server 310 (step (6)). The registration message shown in FIG. 13A is generated and transmitted. The data registration processing unit 105 on the reader information management server 310 side receives the registration message, and outputs the data included in the registration message to the DB registration unit 32 via API-2. The DB registration unit 32 of the reader information management server 310 registers R-sem, which is registration information, in the DB as O-his with key details in correspondence with the O-ID.

  As described above, in the registration process, the registration process must be performed for each server, and a search is attached to each registration process.

  In the registration process shown in FIG. 26, the reader information management server 310 is first accessed to resolve the R-Sem from the R-ID, and then the object information management server 309 is accessed, but this access order is reversed. It does not matter. When the access order is reversed, steps (4), (5), (6), (1), (2), and (3) are performed in this order.

  26 shows an example in which the registration state is managed on the RFID reader 5 side, the registration state may be managed on the server side as shown in FIG.

  In FIG. 27, when the ID reading unit 51 of the RFID reader 5 reads the O-ID from the RFID tag 11, it outputs a registration request to the data registration processing unit 105 via API-3. The data registration processing unit 105 on the RFID reader 5 side uses the O-ID as a key of the first registration location, sets the code representing the type of O-his as the details of the key of the first registration location, and sets the type of R-sem. Is a first registration information, the R-ID is a key of the second registration location, the code representing the type R-his is the details of the key of the second registration location, and the type O-sem An extended registration message having the code representing the second registration information as a second registration information is generated and transmitted to the reader information management server 310 via the network 1 (step (1)). In this step, a message as shown in FIG. 22 (c) is transmitted. That is, the O-ID is used as the first registration location key, the code representing the type O-his is the details of the first registration location key, and the code representing the type R-sem is used as the first registration information. , R-ID is the key of the second registration location, the code representing the type R-his is the details of the key of the second registration location, and the code representing the type O-sem is the second registration information. This is an extended registration message.

  The data registration processing unit 105 on the reader information management server 310 side receives the extended registration message, checks the extended registration message, and determines whether a registration request can be output. In the extended registration message transmitted in step (1), registration information R-sem corresponding to the key O-ID of the first registration location, and second registration information corresponding to the key R-ID of the second registration location Since O-sem has not been acquired yet, first, a search request having R-ID as a search key and R-sem as a request data type is output to the DB search unit 31 via API-2. The DB search unit 31 of the reader information management server 310 searches the DB with the search key R-ID included in the search request, extracts the corresponding R-sem (step (2)), and reads the reader information. The data is output to the data registration processing unit 105 on the management server 310 side.

  Upon receiving the R-sem, the data registration processing unit 105 on the reader information management server 310 side embeds the R-sem as the first registration information of the received extended registration message, and embeds the extended registration message into the object information management. It transmits to the server 309 (step (3)). The data registration processing unit 105 on the object information management server 309 side receives the extended registration message and receives the data (first registration location key O-ID, first registration location detail key O) included in the extended registration message. -His, first registration information R-sem) is output to the DB registration unit 32 via API-2 as a registration request. The DB registration unit 32 of the object information management server 309 registers R-sem, which is registration information, in the DB as O-his with key details corresponding to the O-ID.

  Further, when the DB registration unit 32 outputs the registration completion to the data registration processing unit 105 on the object information management server 309 side, the data registration processing unit 105 uses the O-ID as a search key and O-sem as the requested data type. The search request is output to the DB search unit 31 via API-2. The DB search unit 31 searches the DB according to the search request, extracts the O-sem registered corresponding to the O-ID (step (4)), and uses the O-sem as a search result to register the data registration processing unit 105. Output to.

  The data registration processing unit 105 completes the extended registration message by embedding O-sem as the second registration information in the received extended registration message, and transmits it to the reader information management server 310 (step (5)). The data registration processing unit 105 on the reader information management server 310 side receives the extended registration message and receives data included in the extended registration message (the R-ID that is the key of the second registration location, the detailed key of the second registration location) The code representing the type R-his and O-sem as the second registration information are output to the DB registration unit 32 via API-2. The DB registration unit 32 of the reader information management server 310 corresponds to the R-ID that is the key of the second registration location, and converts the O-sem that is the second registration information into the key details of the second registration location. Register in the DB as R-his.

  In this way, data is registered in the object information management server 309 and the reader information management server 310 in two stages. However, the registration process proceeds mainly by the reader information management server 310.

(3-2-B) Search Process On the other hand, the search process is performed as shown in FIG. 28 for each basic search pattern. First, a search request including a key, a request data type, and a search range is output from the application 1 of the search terminal 7 to the search interface unit 71 via API-1. The search interface unit 71 specifies a search pattern from the search request key and the request data type.

(3-2-B-1) Search pattern P1-1
When the search request key is O-ID and the request data type is O-sem, the search interface unit 71 searches the pattern 1 search processing unit 101 on the search terminal 7 side because the search pattern P1-1. Output request data. The pattern 1 search processing unit 101 on the search terminal 7 side generates a search request message using the O-ID as a search key and O-sem as the requested search information, and transmits it to the object information management server 309 via the network 1. (Step (1)). The search request message shown in FIG. 13B is transmitted. The pattern 1 search processing unit 101 on the object information management server 309 side receives the search request message and outputs data included in the search request message to the DB search unit 31 via API-2. The DB search unit 31 of the object information management server 309 searches the DB using the O-ID as a search key, and extracts data of O-sem of the requested data type.

  Thereafter, the DB search unit 31 outputs the extracted O-sem to the pattern 1 search processing unit 101 on the object information management server 309 side via API-2. The pattern 1 search processing unit 101 on the object information management server 309 side generates a search response message using O-sem as search information via the network 1 and transmits it to the pattern 1 search processing unit 101 on the search terminal 7 side. (Step (2)). The search response message shown in FIG. 13C is generated and transmitted. The pattern 1 search processing unit 101 on the search terminal 7 side receives the search response message and outputs search result data included in the search response message to the search interface unit 71. The search interface unit 71 outputs O-sem as a search result to the request source application 1 via API-1.

(3-2-B-2) Search pattern P1-2
When the search request key is O-ID and the request data type is O-his (R-sem), the search interface unit 71 searches for the pattern 1 on the search terminal 7 side. The search request data is output to the processing unit 101. The pattern 1 search processing unit 101 on the search terminal 7 side generates a search request message using the O-ID as a search key and O-his (R-sem) as request search information, and manages object information via the network 1. It transmits to the server 309 (step (1)). The search request message shown in FIG. 13B is generated and transmitted.

  The pattern 1 search processing unit 101 on the object information management server 309 side receives the search request message, and converts the data included in the search request message (here, search key O-ID, request data type R-sem) to API-2. To the DB search unit 31 as a search request. The DB search unit 31 of the object information management server 309 searches the DB using the O-ID as a search key, and extracts a correspondingly registered R-sem column.

  The DB search unit 31 outputs the extracted R-sem sequence to the pattern 1 search processing unit 101 on the object information management server 309 side. The pattern 1 search processing unit 101 on the object information management server 309 side receives the R-sem column from the DB search unit 31 and includes O-his (R-sem) according to the format of the search response message in FIG. A search response message is generated and transmitted to the requesting search terminal 7 via the network 1 (step (2)). The pattern 1 search processing unit 101 on the search terminal 7 side receives the search response message and outputs O-his (R-sem) included in the search response message to the search interface unit 71. The search interface unit 71 collectively outputs O-his (R-sem) as a search result to the request source application 1 via API-1.

  Note that it is considered that the frequency of execution for the search pattern P2-1 is not high, and the O-ID in the search pattern P1-1 may be replaced with the R-ID, and the O-sem may be R-sem. Description is omitted.

(3-2-B-3) Search pattern P2-2
Further, when the key of the search request is R-ID and the request data type is R-his (O-sem), the search interface unit 71 uses the search terminal 7 side pattern because the search pattern P2-2. 2 Search request data is output to the search processing unit 102. The pattern 2 search processing unit 102 on the search terminal 7 side generates a search request message using R-ID as a search key and R-his (O-sem) as request search information, and manages reader information via the network 1. It transmits to the server 310 (step (1)). In this step, a search request message as shown in FIG. 13B is generated and transmitted.

  The pattern 2 search processing unit 102 on the reader information management server 310 side receives the search request message, and includes data included in the search request message (here, search key R-ID, request data type R-his (O-sem)). Is output to the DB search unit 31 via API-2. The DB search unit 31 of the reader information management server 310 receives a search request from the pattern 2 search processing unit 102, searches the DB using the R-ID included in the search request as a search key, and registers the corresponding O. -Extract sem columns.

  The DB search unit 31 outputs the extracted O-sem sequence to the pattern 2 search processing unit 102 on the reader information management server 310 side. The pattern 2 search processing unit 102 on the reader information management server 310 side generates a search response message including R-his (O-sem) according to the format of the search response message in FIG. The data is transmitted to the requesting search terminal 7 (step (2)). The pattern 2 search processing unit 102 on the search terminal 7 side receives the search response message and outputs R-his (O-sem) included in the search response message to the search interface unit 71. The search interface unit 71 collectively outputs R-his (O-sem) as a search result to the request source application 1 via API-1.

(3-2-B-4) Search pattern P3
Further, when the search request key is O-sem and the request data type is O-his (R-sem), the search interface unit 71 searches for the pattern 3 on the search terminal 7 side. The search request data is output to the processing unit 103. The pattern 3 search processing unit 103 on the search terminal 7 side generates a search request message using O-sem as a search key and O-his (R-sem) as request search information, and manages object information via the network 1. It transmits to the server 309 (step (1)). In this step, a search request message as shown in FIG. 13B is generated and transmitted.

  The pattern 3 search processing unit 103 on the object information management server 309 side receives the search request message, and uses data included in the search request message (here, search key O-sem, request data type R-sem) as a search request. The data is output to the DB search unit 31 via API-2. The DB search unit 31 of the object information management server 309 searches the DB using O-sem as a search key, and extracts an R-sem column registered correspondingly.

  The DB search unit 31 outputs the extracted R-sem sequence to the pattern 3 search processing unit 103 on the object information management server 309 side. The pattern 3 search processing unit 103 on the object information management server 309 side receives the R-sem column from the DB search unit 31 and includes O-his (R-sem) according to the format of the search response message in FIG. A search response message is generated and transmitted to the requesting search terminal 7 via the network 1 (step (2)). The search information of one search response message may include all R-sems. The pattern 3 search processing unit 103 on the search terminal 7 side receives the search response message and outputs O-his (R-sem) included in the search response message to the search interface unit 71. The search interface unit 71 collectively outputs O-his (R-sem) as a search result to the request source application 1 via API-1.

(3-2-B-5) Search pattern P4
Furthermore, when the key of the search request is R-sem and the request data type is R-his (O-sem), the search interface unit 71 searches for the pattern 4 on the search terminal 7 side. The search request data is output to the processing unit 104. The pattern 4 search processing unit 104 on the search terminal 7 side generates a search request message using R-sem as a search key and R-his (O-sem) as request search information, and manages reader information via the network 1. It transmits to the server 310 (step (1)). In this step, a search request message as shown in FIG. 13B is generated and transmitted.

  The pattern 4 search processing unit 104 on the reader information management server 310 side receives the search request message and sends a search request including data (here, search key R-sem, request data type O-sem) included in the search request message. , Output to the DB search unit 31 via API-2. The DB search unit 31 searches the DB with the search key R-sem included in the search request, and extracts an O-sem column registered correspondingly. Then, the DB search unit 31 outputs the O-sem sequence to the DB search unit 31 on the reader information management server 310 side.

  The pattern 4 search processing unit 104 on the reader information management server 310 side receives the O-sem sequence, and generates a search response message including R-his (O-sem) according to the format of the search response message in FIG. Then, the request is transmitted to the requesting search terminal 7 via the network 1 (step (2)). The search information of one search response message may include all O-sems. The pattern 4 search processing unit 104 on the search terminal 7 side receives the search response message and outputs R-his (O-sem) included in the search response message to the search interface unit 71. The search interface unit 71 collectively outputs R-his (O-sem) as a search result to the request source application 1 via API-1.

  If the processing as described above is performed, the reverse processing of the DB is not necessary in the search processing, and the necessary data can be acquired from one server except for the address resolution processing, and the search efficiency Has improved.

  The models 1-1 to 3-2 described above can be summarized in terms of the necessity of inter-server communication, reverse DB processing, and server distribution for large scale. It becomes like this. In model 1, registration is simplified, and DB reverse lookup processing is also unnecessary. A difference between the model 1-1 and the model 1-2 depends on whether the RFID tag 11 and the RFID reader 5 are managed by the same entity or another entity. However, since it is necessary to associate the DB at the time of search, there is a problem that when extracting O-sem or R-sem from the ID, it is necessary to access a plurality of servers.

  The model 2-1 has a simple registration process, and the search process for the search patterns P1 and 3 may be simple. However, as shown in FIG. 20, a search request message must be sent to a plurality of servers for the search pattern P4. In addition, reverse DB processing is required. On the other hand, the model 2-2 solves this problem, but makes the registration process complicated.

  The model 3-1 also has two stages of registration processing, and DB search processing is required for the search patterns P2-2 and P4. On the other hand, in the model 3-2, the registration process is complicated, but the search process is completed with one server access, so that the search efficiency is improved.

  Although the processing contents of the embodiment of the present invention have been described above, address resolution has been ignored in order to simplify the description. However, in actuality, when accessing the object information management server and when accessing the reader information management server, in order to access the appropriate object information management server and the appropriate reader information management server, processing for address resolution is performed. There is a need to do. For example, when model 1-1 is adopted and data registration is performed, it is necessary to perform processing as shown in FIG. That is, steps (1) and (2) are the same as those shown in FIG. 12, but before step (1), the registration destination object information management server (O server or O-ID from O-ID) And the step of acquiring the IP address from the URL of the registration destination object information management server. Similarly, before the step (2), from the R-ID, a step of acquiring the URL of the R-ID registration destination reader information management server (also abbreviated as R server or R information management server), and further registration destination reader information The step of acquiring the IP address from the URL of the management server is required.

  Similarly, when the model 1-1 is adopted and the search pattern P1-2 is executed, it is necessary to perform a process as shown in FIG. That is, step (1) is the same as that shown in FIG. 14, but before step (1), the registered object information management server (O server or O information management server) from O-ID to O-ID. And a step of acquiring the IP address from the URL of the registration destination object information management server. Further, when the extended search request message is transmitted from the object information management server to the reader information management server, for each R-ID included in the R-ID column acquired in the object information management server, the registration destination of the R-ID A step of acquiring the URL of the reader information management server and a step of acquiring the IP address from the URL of the registration destination reader information management server are required. Thus, although only one step (2) and (3) is shown in FIG. 14, steps (2) and (3) are performed by the number of R-IDs extracted by the object information management server. Will be.

  Although such a processing load is necessary, since it becomes a large load when viewed as a whole, it is preferable to reduce it as much as possible.

  Therefore, if the URL or IP address is registered in the RFID tag 11 or the RFID reader 5, the processing load for address resolution can be reduced. That is, if not only the O-ID but also the URL of the registration destination object information management server is registered in the RFID tag 11, when registering the R-ID or R-sem corresponding to the O-ID, the URL The step of acquiring can be omitted. If the IP address of the registration destination object information management server is registered, a step of acquiring a URL and a step of acquiring an IP address when registering an R-ID or R-sem corresponding to the O-ID Can be omitted.

  Further, if not only R-ID or R-sem but also the URL of the reader information management server is registered in the RFID reader 5, when registering O-ID or the like corresponding to the R-ID, or the RFID reader When performing the search from 5, the step of acquiring the URL can be omitted. Further, if the IP address of the reader information management server is registered, when registering an O-ID corresponding to the R-ID, or when executing a search from the RFID reader 5, a step of acquiring a URL and an IP The step of acquiring the address can be omitted.

  Further, when two-stage data registration processing or search processing is required, the URL acquisition step is performed by registering the URL of the associated reader information management server corresponding to the R-ID in the intermediary DB server 3. If the IP address is registered, the URL acquisition step and the IP address acquisition step can be omitted. Similarly, when two-step data registration or search processing is required, the URL of the object information management server associated with the O-ID is registered in the intermediary DB server 3 to obtain the URL. If the IP address is registered, the IP address acquisition step can be omitted. That is, the data registration process and the search process can be made efficient.

  In the above case, when performing the two-stage data registration process or search process, the RFID reader 5 or the search terminal 7 may manage the status and perform the process independently, or access first. The server side may perform state management and perform processing independently, or an agent that executes processing on behalf of the RFID reader 5 or the search terminal 7 performs state management and performs processing independently. Also good.

  A case where the search pattern P1-2 of the model 1-1 is executed will be described as an example. FIG. 31 shows an example in which the object information management server performs state management and performs processing independently. Here, the step group included in A is executed after generating the extended search request message to be transmitted in step (1). These steps may be omitted if a URL or IP address is input together with the O-ID. The step group included in B1 is executed after reconstructing the extended search request message transmitted in step (2a). These steps may be omitted if the reader information management server URL or IP address is registered corresponding to the R-ID. The same applies to B2 and below.

  FIG. 32 shows a processing flow when the search terminal 7 performs state management and performs processing independently. When the search request key is O-ID and the request data type is O-his (R-sem), the search interface unit 71 searches for the pattern 1 on the search terminal 7 side. The search request data is output to the processing unit 101. The pattern 1 search processing unit 101 on the search terminal 7 side constitutes a search request message using the O-ID as a search key and O-his (R-ID) as request search information via the network 1. Address resolution processing is performed according to the key O-ID in the search request message. That is, the step group A corresponding to the URL and IP address acquisition step of the object management server 301 is executed. More specifically, a step of acquiring the URL of the object information management server corresponding to the O-ID from the object server URL resolution server, and an IP address of the object information management server corresponding to the URL from DNS (Domain Name Server) To perform the steps. If the URL or IP address of the related object information management server is specified together with the O-ID, there is a step that can be skipped.

  Next, the pattern 1 search processing unit 101 on the search terminal 7 side transmits to the object information management server 301 according to the processing result of the address resolution processing (step (1)).

  The pattern 1 search processing unit 101 on the object information management server 301 side receives the search request message, and uses the data included in the search request message (here, the key O-ID and the request data type O-his (R-ID)). The search request is output to the DB search unit 31 via API-2. The DB search unit 31 of the object information management server 301 searches the DB using the O-ID as a search key, and extracts a correspondingly registered R-ID string.

  Then, the DB search unit 31 outputs the extracted R-ID string to the pattern 1 search processing unit 101 on the object information management server 301 side via API-2. The pattern 1 search processing unit 101 on the object information management server 301 side composes a search response message including the received R-ID string and transmits it to the search terminal 7 (step (2)).

  The pattern 1 search processing unit 101 on the search terminal 7 side receives the search response message and decomposes the R-ID string included in the search response message. Then, for each R-ID included in the R-ID column, a search request message is formed using the R-ID as a key and R-sem as request search information.

  Then, address analysis processing is performed according to the key R-ID in the search request message. That is, the step group C corresponding to the URL and IP address acquisition step of the reader information management server 302 is executed. More specifically, the step of acquiring the URL of the reader information management server corresponding to the R-ID from the reader server URL resolution server and the step of acquiring the IP address of the object information management server corresponding to the URL from the DNS are executed. To do. If the URL or IP address of the related reader information management server is registered in the object information management server 301 together with the R-ID, and there is a step that can be skipped if it is transmitted in the search response message.

  Further, the pattern 1 search processing unit 101 on the search terminal 7 side transmits a search request message to the reader information management server 302 according to the result of the address resolution processing (step (3)).

  The pattern 1 search processing unit 101 on the reader information management server 302 side receives the search request message via the network 1 and receives data included in the search request message (here, the key R-ID and the request data type O-his (R -Sem)) is output to the DB search unit 31 via API-2. The DB search unit 31 of the reader information management server 302 searches the DB using the R-ID as a search key, and extracts the corresponding R-sem.

  Then, the DB search unit 31 outputs the extracted O-his R-sem to the pattern 1 search processing unit 101 on the reader information management server 302 side via API-2. The pattern 1 search processing unit 101 on the reader information management server 302 side generates a search response message including O-his (R-sem) in accordance with the format of the search response message in FIG. The data is transmitted to the requesting search terminal 7 (step (4)). The pattern 1 search processing unit 101 on the search terminal 7 side receives the search response message and outputs O-his (R-sem) included in the search response message to the search interface unit 71.

  Step group C and steps (3) and (4) are repeated for each R-ID included in the R-ID column.

  The search interface unit 71 collectively outputs O-his (R-sem) as a search result to the request source application 1 via API-1.

  In this way, the search can be performed without using the extended search request message.

  Next, processing when an agent is used will be described with reference to FIG. When using an agent, the pattern 1 search processing unit 101 on the search terminal 7 side generates a search request message with the O-ID as a search key and O-his (R-sem) as the request data type, As a result, the search response message including O-his (R-sem # X) is received from the agent. On the other hand, in the agent, processing of the pattern 1 search processing unit 101 of the search terminal 7 in FIG. 32 other than the processing that constitutes the search request message is performed.

  As described above, according to the embodiment of the present invention, various and various search services can be provided on a common platform. For example, the user can read the identification information of the IC tag attached to the object, the identification information of the reader, the static information such as the name of the object indicated by the IC tag, and the reader such as the name of the owner or reader where the reader is located. Detailed information can be searched by specifying any of the static information associated with as a search key. Such various search services can be provided on a common platform. In addition, even if the identification information of the IC tag and the reader is not known, it is possible to search for detailed information by specifying static information such as a name, so that convenience for the user can be improved.

  Although the embodiment of the present invention has been described above, the present invention is not limited to this. For example, the functional block diagrams shown in FIGS. 2 and 3 are examples, and may not correspond to actual program modules.

  The object information management server, reader information management server, and search terminal are computer devices as shown in FIG. 34, and include a memory 2501 (storage device), a CPU 2503 (processing device), a hard disk drive (HDD) 2505, and a display device. A display control unit 2507 connected to 2509, a drive device 2513 for the removable disk 2511, an input device 2515, and a communication control unit 2517 for connecting to a network are connected by a bus 2519. An operating system (OS: Operating System) and an application program for performing processing in the present embodiment are stored in the HDD 2505, and are read from the HDD 2505 to the memory 2501 when executed by the CPU 2503. If necessary, the CPU 2503 controls the display control unit 2507, the communication control unit 2517, and the drive device 2513 to perform necessary operations. Further, data in the middle of processing is stored in the memory 2501 and stored in the HDD 2505 if necessary. In the embodiment of the present invention, an application program for performing the processing described above is stored in the removable disk 2511 and distributed, and is installed in the HDD 2505 from the drive device 2513. In some cases, the HDD 2505 may be installed via a network such as the Internet and the communication control unit 2517. Such a computer apparatus realizes various functions as described above by organically cooperating hardware such as the CPU 2503 and the memory 2501 described above, the OS, and necessary application programs.

(Appendix 1) [Model 3-2]
Object information management server for accumulating and managing identification information of the IC tag, static information of the IC tag, and static information of the reader that has read the IC tag, identification information of the reader, and static information of the reader And a reader information management server that stores and manages static information of IC tags read by the reader,
Receiving a search key and request data type designation;
If the specified search key is identification information of the IC tag, a search request including the identification information of the IC tag that is the search key and the request data type is generated and transmitted to the object information management server And the steps
If the specified search key is the reader identification information, a search request including the reader identification information and the request data type as the search key is generated and transmitted to the reader information management server. When,
If the specified search key is static information of the IC tag, a search request including the static information of the IC tag that is the search key and the request data type is generated and transmitted to the object information management server. A third step;
If the designated search key is the reader static information, a search request including the reader static information as the search key and the request data type is generated and transmitted to the reader information management server. Of the steps and
A search processing method including the first step or the third step and the second step or the fourth step and executed by a computer.

(Appendix 2)
Object information management server for accumulating and managing identification information of the IC tag, static information of the IC tag, and static information of the reader that has read the IC tag, identification information of the reader, and static information of the reader And a reader information management server that stores and manages static information of IC tags read by the reader, and a data registration method for registering data,
A reader reading identification information of a specific IC tag;
A reader static information acquisition step of acquiring static information of the reader from the reader information management server based on the identification information of the reader;
A reader static information registration step for causing the object information management server to register the reader static information acquired by the reader static information acquisition step corresponding to the read identification information of the specific IC tag;
IC tag static information acquisition step of acquiring static information of the specific IC tag from the object information management server based on the read identification information of the specific IC tag;
An IC tag static information registration step for causing the reader information management server to register the static information of the specific IC tag acquired by the IC tag static information acquisition step corresponding to the identification information of the reader;
A data registration method executed by a computer.

(Appendix 3)
The reader or the proxy processing execution computer of the reader performs the reader static information acquisition step, the reader static information registration step, the IC tag static information acquisition step, and the IC tag static information registration step. The data registration method according to attachment 2 to be executed.

(Appendix 4)
The reader static information acquisition step includes:
The reader transmits a first registration request including identification information of the reader and identification information of the read specific IC tag to the reader information management server;
When the reader information management server receives the first registration request, the reader information management server searches for the reader identification information and reads the corresponding static information of the reader;
Including
The reader static information registration step includes:
The reader information management server transmitting a second registration request including identification information of the specific IC tag and static information of the reader to the object information management server;
When the object information management server receives the second registration request, the static information of the reader is registered corresponding to the identification information of the specific IC tag;
Including
In the IC tag static information acquisition step,
The object information management server retrieves the static information of the specific IC tag corresponding to the specific IC tag by searching with the identification information of the specific IC tag included in the second registration request,
The IC tag static information registration step includes:
The object information management server transmitting the read static information of the specific IC tag to the reader information management server;
The reader information management server receiving the static information of the specific IC tag and registering the received static information of the specific IC tag corresponding to the identification information of the reader;
The data registration method according to appendix 2, including

(Appendix 5)
The reader holds a URL (Uniform Resource Locator) or address of the reader information management server related to the reader,
The data registration method according to any one of appendices 2 to 4, wherein the IC tag holds the identification information of the IC tag and the URL or address of an object information management server related to the IC tag. .

(Appendix 6) [Model 3-1]
Object information management server for accumulating and managing identification information of the IC tag, static information of the IC tag, and static information of the reader that has read the IC tag, identification information of the reader, and static information of the reader A search processing method using a reader information management server for managing
Receiving a search key and request data type designation;
If the specified search key is identification information of the IC tag, a search request including the identification information of the IC tag that is the search key and the request data type is generated and transmitted to the object information management server And the steps
When the specified search key is reader identification information, a search request including the reader identification information and the request data type as a search key is generated and transmitted to the reader information management server, and A second step of generating a second search request including static information of the reader specified from the identification information of the reader and the request data type in the reader information management server, and transmitting the second search request to the object information management server;
If the specified search key is static information of the IC tag, a search request including the static information of the IC tag that is the search key and the request data type is generated and transmitted to the object information management server. A third step;
When the designated search key is the reader static information, a search request including the reader static information as the search key and the request data type is generated and transmitted to the object information management server. Of the steps and
A search processing method including the first step or the third step and the second step or the fourth step and executed by a computer.

(Appendix 7)
The second step may be any one of a search instruction terminal or a proxy processing execution computer of the search instruction terminal, and a combination of the search instruction terminal or the proxy processing execution computer of the search instruction terminal and the reader information management server. The search processing method according to supplementary note 6 to be executed.

(Appendix 8)
In the object information management server that stores and manages the identification information of the IC tag, the static information of the IC tag, and the static information of the reader that has read the IC tag, the identification information of the reader and the static information of the reader A data registration method for registering data using a reader information management server for managing
A reader reading identification information of a specific IC tag;
A reader static information acquisition step of acquiring static information of the reader from the reader information management server based on the identification information of the reader;
A reader static information registration step for causing the object information management server to register the reader static information acquired by the reader static information acquisition step corresponding to the read identification information of the specific IC tag;
A data registration method executed by a computer.

(Appendix 9)
The data registration method according to claim 8, wherein the reader static information registration step is executed by either the reader or the reader information management server.

(Appendix 10)
The reader holds a URL (Uniform Resource Locator) or address of the reader information management server related to the reader,
The data registration method according to appendix 8 or 9, wherein the IC tag holds identification information of the IC tag and a URL or address of an object information management server related to the IC tag.

(Supplementary Note 11) [Model 2-2]
An object information management server for storing and managing the identification information of the IC tag, the static information of the IC tag, and the static information of the reader that has read the IC tag, and the static information of the reader instead of the identification information of the reader A search processing method using a reader information management server for storing and managing information and static information of an IC tag read by the reader,
Receiving a search key and request data type designation;
If the specified search key is identification information of the IC tag, a search request including the identification information of the IC tag that is the search key and the request data type is generated and transmitted to the object information management server And the steps
If the specified search key is static information of the IC tag, a search request including the static information of the IC tag that is the search key and the request data type is generated and transmitted to the object information management server. A second step;
If the specified search key is the static information of the reader, a search request including the static information of the reader that is the search key and the request data type is generated and transmitted to the reader information management server. Of the steps and
A search processing method including the first step or the second step and the third step and executed by a computer.

(Appendix 12)
An object information management server for storing and managing the identification information of the IC tag, the static information of the IC tag, and the static information of the reader that has read the IC tag, and the static information of the reader instead of the identification information of the reader A data registration method for registering data in a reader information management server for storing and managing information and static information of an IC tag read by the reader,
A reader having its own static information reads identification information of a specific IC tag;
Registering the reader's static information in the object information management server in correspondence with the read identification information of the specific IC tag;
An acquisition step of acquiring static information of the specific IC tag from the object information management server based on identification information of the specific IC tag;
A registration step for causing the reader information management server to register the static information of the specific IC tag acquired by the acquisition step in correspondence with the static information of the reader;
A data registration method executed by a computer.

(Appendix 13)
The registration step includes
The data registration method according to appendix 12, wherein the data registration method is executed by either the reader or the object information management server.

(Appendix 14)
The reader holds a URL (Uniform Resource Locator) or address of the reader information management server related to the reader,
14. The data registration method according to appendix 12 or 13, wherein the IC tag holds identification information of the IC tag and a URL or address of an object information management server related to the IC tag.

(Supplementary Note 15) [Model 2-1]
A search processing method using an object information management server that stores and manages identification information of an IC tag, static information of the IC tag, and static information of a reader that has read the IC tag,
Receiving a search key and request data type designation;
If the specified search key is identification information of the IC tag, a search request including the identification information of the IC tag that is the search key and the request data type is generated and transmitted to the object information management server And the steps
If the specified search key is static information of the IC tag, a search request including the static information of the IC tag that is the search key and the request data type is generated and transmitted to the object information management server. A second step;
If the designated search key is the static information of the reader, a search request including the reader static information as the search key and the request data type is generated and transmitted to the object information management server. Of the steps and
A search processing method executed by a computer, comprising the first step and the second step, or the first step or the second step and the third step.

(Appendix 16)
When there are a plurality of the object information management servers,
The search processing method according to claim 15, wherein a search request is transmitted to the plurality of object information management servers in at least one of the IC tag static information search step and the reader static information search step.

(Supplementary Note 17) [Model 1-2]
The identification information of the IC tag, the static information of the IC tag, the identification information of the reader that read the IC tag, and the storage and management, the reader identification information, the static information of the reader, and the reader read A search processing method using an object that accumulates and manages identification information of an IC tag and a reader information management server,
Receiving a search key and request data type designation;
When the specified search key is identification information of the IC tag and the request data type is static information of the reader, the request data of the identification information of the IC tag that is the search key and the identification information of the reader A search request for extracting the reader identification information from the identification information of the IC tag, and extracting the static information of the reader from the identification information of the reader, and the object and reader information management server A first step of transmitting to
If the specified search key is reader identification information and the request data type is IC tag static information, a request for the reader identification information and IC tag static information as a search key A search request for extracting IC tag identification information from the reader identification information, and extracting static information of the IC tag from the IC tag identification information, and generating the object and reader A second step of transmitting to the information management server;
When the specified search key is IC tag static information and the request data type is reader static information, the IC static information and reader static information as search keys A search request for extracting the reader identification information from the static information of the IC, extracting the reader static information from the reader identification information, and managing the object and reader information A third step of sending to the server;
When the designated search key is static information of the reader and the request data type is static information of the IC tag, the static information of the reader and the static information of the IC tag that are the search keys Generating a search request for extracting identification information of the IC tag from the static information of the reader, extracting static information of the IC tag from the identification information of the IC tag, Of the fourth step of transmitting to the object and reader information management server,
A search processing method including the first step or the third step and the second step or the fourth step and executed by a computer.

(Supplementary Note 18) [Model 1-1]
Identification information of the IC tag, static information of the IC tag, identification information of the reader that read the IC tag, object information management server that stores and manages, identification information of the reader, static information of the reader, A search processing method using a reader information management server for accumulating and managing identification information of an IC tag read by a reader,
Receiving a search key and request data type designation;
When the specified search key is identification information of an IC tag and the request data type is static information of a reader, a request for identification information of the IC tag that is a search key and static information of the reader A search request including a data type is generated, transmitted to the object information management server, and further, the reader identification information and the reader static information specified from the identification information of the IC tag in the object information management server Generating a second search request including the request data type and sending it to the reader information management server;
If the specified search key is reader identification information and the request data type is IC tag static information, a request for the reader identification information and IC tag static information as a search key A search request including a data type is generated, transmitted to the reader information management server, and further, the IC tag identification information specified from the reader identification information in the reader information management server and the IC tag static information A second step of generating a second search request including a request data type of information and transmitting it to the object information management server;
When the designated search key is IC tag static information and the request data type is reader static information, the IC tag static information and the reader identification information are search keys. A search request including a request data type is generated and transmitted to the object information management server. Further, the identification information of the reader specified from the static information of the IC tag in the object information management server and the static information of the reader A third step of generating a second search request including a request data type of target information and transmitting it to the reader information management server;
When the designated search key is static information of the reader and the request data type is static information of the IC tag, the static information of the reader and the static information of the IC tag that are the search keys A search request including the request data type, and transmits the search request to the reader information management server. Further, the IC tag identification information and the IC tag specified from the reader static information in the reader information management server Generating a second search request including the request data type of static information and transmitting to the object information management server,
A search processing method including the first step or the third step and the second step or the fourth step and executed by a computer.

(Appendix 19)
At least one of the first step and the third step includes a search instruction terminal or a proxy process execution computer of the search instruction terminal, a search instruction terminal or a proxy process execution computer of the search instruction terminal, and the object information management server One of the combinations and
At least one of the second step and the fourth step includes a search instruction terminal or a proxy process execution computer of the search instruction terminal, a search instruction terminal or a proxy process execution computer of the search instruction terminal, and the reader information management server The search processing method according to appendix 18, wherein any one of the combinations is executed.

(Appendix 20)
In the object information management server, the reader information management server URL (Uniform Resource Locator) or address associated with the reader is registered together with the reader identification information,
The search processing method according to claim 18 or 19, wherein the reader information management server registers the URL or address of the object information management server related to the IC tag together with the identification information of the IC tag.

(Appendix 21)
A program for causing a computer to execute the search processing method according to any one of Supplementary Notes 1, 6, 7, 11, 15 to 20.

(Appendix 22)
A program for causing a computer to execute the data registration method according to any one of appendices 2 to 5, 8 to 10, and 12 to 14.

(Appendix 23)
Object information management server for accumulating and managing identification information of the IC tag, static information of the IC tag, and static information of the reader that has read the IC tag, identification information of the reader, and static information of the reader And a reader information management server that accumulates and manages static information of IC tags read by the reader,
Means for accepting designation of a search key and request data type;
If the specified search key is identification information of the IC tag, a search request including the identification information of the IC tag that is the search key and the request data type is generated and transmitted to the object information management server Means of
Second means for generating a search request including the reader identification information as a search key and the request data type when the specified search key is reader identification information, and transmitting the search request to the reader information management server. When,
If the specified search key is static information of the IC tag, a search request including the static information of the IC tag that is the search key and the request data type is generated and transmitted to the object information management server. A third means;
If the designated search key is the reader static information, a search request including the reader static information as the search key and the request data type is generated and transmitted to the reader information management server. Of the means,
A search system comprising the first means or the third means and the second means or the fourth means.

(Appendix 24)
Object information management server for accumulating and managing identification information of the IC tag, static information of the IC tag, and static information of the reader that has read the IC tag, identification information of the reader, and static information of the reader And a reader information management server that stores and manages static information of IC tags read by the reader, and a data registration device that registers data
Means for a reader to read identification information of a specific IC tag;
Reader static information acquisition means for acquiring static information of the reader from the reader information management server based on the identification information of the reader;
Reader static information registration means for registering in the object information management server the static information of the reader acquired in the reader static information acquisition step corresponding to the read identification information of the specific IC tag;
IC tag static information acquisition means for acquiring static information of the specific IC tag from the object information management server based on the read identification information of the specific IC tag;
IC tag static information registration means for causing the reader information management server to register the static information of the specific IC tag acquired by the IC tag static information acquisition step corresponding to the identification information of the reader;
A data registration device.

It is the figure which showed the system outline | summary of embodiment of this invention. It is a conceptual diagram which shows the relationship between DB server and a search terminal. It is a conceptual diagram which shows the relationship between DB server and an RFID reader. It is a figure which shows the structure of DB server in the model 1-1. It is a figure which shows the structure of DB server in the model 1-2. It is a figure which shows an example of the data registered into the object information management server in the model 1. It is a figure which shows the structure of DB server in the model 2-1. It is a figure which shows the structure of DB server in the model 2-2. It is a figure which shows the structure of DB server in the model 3-1. It is a figure which shows the structure of DB server in the model 3-2. It is an example of the data registered in the object information management server in the model 3. It is a figure which shows the processing flow at the time of performing a data registration process by the model 1-1. (A) thru | or (c) is a figure for demonstrating a registration message, a search request message, and a search response message. It is a figure which shows the processing flow at the time of performing a search process with the model 1-1. (A) thru | or (e) is a figure for demonstrating an extended search message. It is a figure which shows the processing flow at the time of performing a data registration process by the model 1-2. It is a figure which shows the processing flow at the time of performing a search process with the model 1-2. It is a figure which shows the processing flow at the time of performing a data registration process by the model 2-1. It is a figure which shows the processing flow at the time of performing a search process with the model 2-1. It is a figure which shows the processing flow at the time of performing search pattern P4 by the model 2-1. It is a figure which shows the processing flow at the time of performing data registration by model 2-2. (A) thru | or (c) is a figure for demonstrating an extended registration message. It is a figure which shows the processing flow at the time of performing search pattern P4 by model 2-2. It is a figure which shows the processing flow at the time of performing data registration by the model 3-1. It is a figure which shows the processing flow at the time of performing a search process with the model 3-1. It is a figure which shows the processing flow (RFID reader initiative) at the time of performing data registration by the model 3-2. It is a figure which shows the processing flow (server initiative) at the time of performing data registration by the model 3-2. It is a figure which shows the processing flow at the time of performing a search process by the model 3-2. It is the figure which arranged the model in embodiment of this invention. It is a figure for demonstrating the address resolution process at the time of data registration. It is a figure for demonstrating the address resolution process at the time of a search process. When executing a search pattern P1-2 in the model 1-1, FIG. FIG. 11 is a flowchart when state management is performed mainly by an agent when executing a search pattern P1-2 in the model 1-1. It is a block diagram of a computer.

Explanation of symbols

1 Network 3 DB Server 5 RFID Reader 7 Search Terminal 9 Product 11 RFID Tag

Claims (5)

Object information management server for accumulating and managing identification information of the IC tag, static information of the IC tag, and static information of the reader that has read the IC tag, identification information of the reader, and static information of the reader And a reader information management server that stores and manages static information of IC tags read by the reader,
Receiving a search key and request data type designation;
If the specified search key is identification information of the IC tag, a search request including the identification information of the IC tag that is the search key and the request data type is generated and transmitted to the object information management server And the steps
If the specified search key is the reader identification information, a search request including the reader identification information and the request data type as the search key is generated and transmitted to the reader information management server. When,
If the specified search key is static information of the IC tag, a search request including the static information of the IC tag that is the search key and the request data type is generated and transmitted to the object information management server. A third step;
If the designated search key is the reader static information, a search request including the reader static information as the search key and the request data type is generated and transmitted to the reader information management server. Of the steps and
A search processing method including the first step or the third step and the second step or the fourth step and executed by a computer. Object information management server for accumulating and managing identification information of the IC tag, static information of the IC tag, and static information of the reader that has read the IC tag, identification information of the reader, and static information of the reader And a reader information management server that stores and manages static information of IC tags read by the reader, and a data registration method for registering data,
A reader reading identification information of a specific IC tag;
A reader static information acquisition step of acquiring static information of the reader from the reader information management server based on the identification information of the reader;
A reader static information registration step for causing the object information management server to register the reader static information acquired by the reader static information acquisition step corresponding to the read identification information of the specific IC tag;
IC tag static information acquisition step of acquiring static information of the specific IC tag from the object information management server based on the read identification information of the specific IC tag;
An IC tag static information registration step for causing the reader information management server to register the static information of the specific IC tag acquired by the IC tag static information acquisition step corresponding to the identification information of the reader;
A data registration method executed by a computer. The reader static information acquisition step includes:
The reader transmits a first registration request including identification information of the reader and identification information of the read specific IC tag to the reader information management server;
When the reader information management server receives the first registration request, the reader information management server searches for the reader identification information and reads the corresponding static information of the reader;
Including
The reader static information registration step includes:
The reader information management server transmitting a second registration request including identification information of the specific IC tag and static information of the reader to the object information management server;
When the object information management server receives the second registration request, the static information of the reader is registered corresponding to the identification information of the specific IC tag;
Including
In the IC tag static information acquisition step,
The object information management server retrieves the static information of the specific IC tag corresponding to the specific IC tag by searching with the identification information of the specific IC tag included in the second registration request,
The IC tag static information registration step includes:
The object information management server transmitting the read static information of the specific IC tag to the reader information management server;
The reader information management server receiving the static information of the specific IC tag and registering the received static information of the specific IC tag corresponding to the identification information of the reader;
The data registration method according to claim 2, comprising: An object information management server for storing and managing the identification information of the IC tag, the static information of the IC tag, and the static information of the reader that has read the IC tag, and the static information of the reader instead of the identification information of the reader A search processing method using a reader information management server for storing and managing information and static information of an IC tag read by the reader,
Receiving a search key and request data type designation;
If the specified search key is identification information of the IC tag, a search request including the identification information of the IC tag that is the search key and the request data type is generated and transmitted to the object information management server And the steps
If the specified search key is static information of the IC tag, a search request including the static information of the IC tag that is the search key and the request data type is generated and transmitted to the object information management server. A second step;
If the specified search key is the static information of the reader, a search request including the static information of the reader that is the search key and the request data type is generated and transmitted to the reader information management server. Of the steps and
A search processing method including the first step or the second step and the third step and executed by a computer. An object information management server for storing and managing the identification information of the IC tag, the static information of the IC tag, and the static information of the reader that has read the IC tag, and the static information of the reader instead of the identification information of the reader A data registration method for registering data in a reader information management server for storing and managing information and static information of an IC tag read by the reader,
A reader having its own static information reads identification information of a specific IC tag;
Registering the reader's static information in the object information management server in correspondence with the read identification information of the specific IC tag;
An acquisition step of acquiring static information of the specific IC tag from the object information management server based on identification information of the specific IC tag;
A registration step for causing the reader information management server to register the static information of the specific IC tag acquired by the acquisition step in correspondence with the static information of the reader;
A data registration method executed by a computer.

Images