Article management system, article management method, reading device, and information processing device

Abstract

An article management system for managing article data indicating an entity to which an article belongs among a plurality of entities includes a first wireless device installed at a first location, a second wireless device that moves with the article, at least one reading device that reads identification information stored in a wireless device, and a management unit configured to manage the article data, wherein, in a state in which the article data indicates that the article belongs to a second entity related to a second location different from the first location, the management unit is configured to update the article data so that the article data indicates that the article belongs to a first entity related to the first location, provided that a first reading device has read identification information of the first wireless device and identification information of the second wireless device.

Description

Technical Field

[0001] This disclosure relates to an item management system, an item management method, a reading device, and an information processing device. Background Technology

[0002] Radio Frequency Identification (RFID) is a technology that allows information embedded in small devices, also known as tags, to be read by external readers via short-range wireless communication. For example, RFID tags with unique identification information are attached to items, making it possible to efficiently locate items for inventory and distribution management, and making it easier to visualize information about managed items. Passive RFID tags, which transmit information using energy from electromagnetic waves emitted by the reader, do not require batteries, resulting in low manufacturing costs and semi-permanent operation. Therefore, it has become widely used not only in inventory and distribution management but also in a variety of other applications.

[0003] Patent Document 1 discloses an example of a system utilizing RFID tags for item management purposes. The system in Patent Document 1 includes RFID tags attached to items sold in a store and a rewriting device installed at the store's exit. When a purchaser of an item passes through the exit, the rewriting device reads identification and price information from the item's RFID tag and credit information from the purchaser's credit card to process payment and rewrite the item's owner.

[0004] Citation List

[0005] Patent documents

[0006] Patent Document 1: Japanese Patent Application Publication No. 2018-156277 Summary of the Invention

[0007] Technical issues

[0008] In the scenario hypothesized in Patent Document 1, where the commercial product is sold, the explicit process of payment triggers the transfer of ownership of the commercial product. However, in the general case where goods are transferred between multiple entities, an explicit process triggering the transfer does not always exist, and even when a process such as inspection exists, it is desirable to make the process more efficient.

[0009] In view of the foregoing, the present invention aims to realize a mechanism that enables the efficient transfer of items between entities.

[0010] Solution to the problem

[0011] According to one aspect, an item management system for managing item data is provided, the item data indicating the entity to which an item belongs among a plurality of entities, the item management system comprising: a first wireless device installed at a first location; a second wireless device moving with the item; at least one reading device reading identification information stored in the wireless device; and a management unit configured to manage the item data; wherein, when the item data indicates that the item belongs to a second entity associated with a second location different from the first location, the management unit is configured to update the item data such that the item data indicates that the item belongs to a first entity associated with the first location if the first reading device has read the identification information of the first wireless device and the identification information of the second device.

[0012] A method for managing item data is also provided, wherein the item data indicates the entity to which an item belongs among a plurality of entities. The method includes, in a state where the item data indicates that the item belongs to a second entity associated with a second location: a first reading device reads identification information from a first wireless device installed at a first location; the first reading device reads identification information from a second wireless device that has been moved to the first location along with the item; the first reading device transmits reading result data to a management unit configured to manage the item data, wherein the reading result data indicates that the first reading device has read the identification information of the first wireless device and the identification information of the second wireless device; and the management unit updates the item data based on the reading result data received from the first reading device such that the item data indicates that the item belongs to a first entity associated with the first location.

[0013] A reading device is also provided, comprising: a reading unit capable of reading identification information stored in each of a first wireless device and a second wireless device, the first wireless device being installed at a first location among a plurality of locations, the second wireless device moving with an item; and a communication unit configured to communicate with an information processing device that manages item data indicating the entity to which the item belongs among a plurality of entities; wherein, when the reading unit has read the identification information of the first wireless device and the identification information of the second wireless device, the communication unit is configured to transmit the result of the reading performed by the reading unit to the information processing device, so that the information processing device changes the entity to which the item belongs in the item data from a second entity associated with a second location different from the first location to a first entity associated with the first location.

[0014] An information processing apparatus for managing item data is also provided, the item data indicating the entity to which an item belongs among a plurality of entities. The information processing apparatus includes: a communication unit configured to communicate with at least one reading device, the at least one reading device being capable of reading identification information stored in each wireless device from a first wireless device and from a second wireless device, the first wireless device being installed at a first location among a plurality of locations, the second wireless device moving with the item; and a management unit configured to, if the communication unit has received reading result data, update the item data such that the item data indicates the item belongs to a first entity associated with the first location when the item data indicates the item belongs to a second entity associated with a second location different from the first location, and the reading result data indicating the first reading device has read the identification information of the first wireless device and the identification information of the second wireless device.

[0015] According to another aspect, an item management system for managing item data is provided, the item data indicating the entity to which an item belongs among a plurality of entities, the item management system comprising: a first wireless device installed at a first location; a second wireless device moving with the item; at least one reading device reading identification information stored in the wireless device; and a management unit configured to manage the item data; wherein, in a state where the item data indicates that the item belongs to a first entity associated with the first location, the management unit is configured to update the item data such that the item data indicates the item belongs to the second entity if a second reading device associated with a second entity has read the identification information of the first wireless device and the identification information of the second device, wherein the association of the second reading device with the second entity includes at least one of the following: the existence of data associating the second reading device with the second entity, or the second reading device having read the identification information of a user device associated with the second entity.

[0016] A method for managing item data is also provided, wherein the item data indicates the entity to which an item belongs among a plurality of entities. The method includes, in a state where the item data indicates that the item belongs to a first entity associated with a first location: a second reading device reads identification information from a first wireless device, the second reading device being associated with a second entity, the first wireless device being installed at the first location; the second reading device reads identification information from a second wireless device, the second wireless device moving with the item; the first reading device transmits reading result data to a management unit configured to manage the item data, the reading result data indicating that the second reading device has read the identification information of the first wireless device and the identification information of the second wireless device; and the management unit updates the item data based on the reading result data received from the second reading device such that the item data indicates that the item belongs to the second entity, wherein the association of the second reading device with the second entity includes at least one of the following: the existence of data associating the second reading device with the second entity, or the second reading device having read the identification information of a user device associated with the second entity.

[0017] A reading device is also provided, comprising: a reading unit capable of reading identification information stored in each of a first wireless device and a second wireless device, the first wireless device being installed at a first location among a plurality of locations, the second wireless device moving with an item; and a communication unit configured to communicate with an information processing device that manages item data indicating the entity to which the item belongs among a plurality of entities; wherein the reading device is associated with a second entity by at least one of the following: the existence of data associating the reading device with the second entity, or the reading device reading identification information of a user device associated with the second entity, and wherein, when the reading unit has read the identification information of the first wireless device and the identification information of the second wireless device, the communication unit is configured to transmit the result of the reading performed by the reading unit to the information processing device, so that the information processing device changes the entity to which the item belongs in the item data from the first entity associated with the first location to the second entity.

[0018] An information processing apparatus for managing item data is also provided, the item data indicating the entity to which an item belongs among a plurality of entities. The information processing apparatus includes: a communication unit configured to communicate with at least one reading device capable of reading identification information stored in each wireless device from a first wireless device and from a second wireless device, the first wireless device being installed at a first location among a plurality of locations, the second wireless device moving with the item; and a management unit configured to, in a state where the item data indicates that the item belongs to a first entity associated with the first location, update the item data such that the item data indicates the item belongs to a second entity, provided the communication unit has received reading result data, if the reading result data indicates that a second reading device associated with the second entity has read the identification information of the first wireless device and the identification information of the second wireless device, wherein the association of the second reading device with the second entity includes at least one of the following: the existence of data associating the second reading device with the second entity, or the second reading device having read the identification information of a user device associated with the second entity.

[0019] Advantages of the invention

[0020] According to the present invention, it becomes possible to efficiently perform the transfer of items between entities.

[0021] Other features and advantages of this disclosure will become clear from the following description taken in conjunction with the accompanying drawings. It should be noted that throughout the drawings, the same reference numerals denote the same or similar components. Attached Figure Description

[0022] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments of the present disclosure and, together with the description, serve to explain the principles of the present disclosure.

[0023] Figure 1 This is a schematic diagram illustrating an example configuration of the item management system according to the first embodiment;

[0024] Figure 2 This is a block diagram illustrating an example configuration of a tag reader according to the first embodiment;

[0025] Figure 3 This is a block diagram illustrating an example configuration of a management server according to the first embodiment;

[0026] Figure 4A This is an explanatory diagram illustrating an example of the configuration of the item list;

[0027] Figure 4B This is an explanatory diagram illustrating an example of the layout of the location table;

[0028] Figure 4C This is an explanatory diagram illustrating an example of the configuration of a reader table;

[0029] Figure 4D This is an explanatory diagram illustrating an example of the configuration of the user table;

[0030] Figure 5 This is an explanatory diagram illustrating an example of the configuration for reading result tables related to inventory operations;

[0031] Figure 6 This is an explanatory diagram illustrating the configuration of the delivery reservation screen and delivery reservation form;

[0032] Figure 7 This is an explanatory diagram used to explain the tag reading during the delivery operation in a first practical example of the first embodiment;

[0033] Figure 8 This is an explanatory diagram used to explain the update of the delivery status in the first practical example of the first embodiment;

[0034] Figure 9 This is an explanatory diagram used to explain the tag reading during the delivery operation in a second practical example of the first embodiment;

[0035] Figure 10 This is an explanatory diagram used to explain the update of the delivery status in the second practical example of the first embodiment;

[0036] Figure 11 This is an explanatory diagram illustrating the configuration of the pickup reservation screen and pickup reservation form;

[0037] Figure 12 This is an explanatory diagram used to explain the tag reading during the retrieval operation in the first embodiment;

[0038] Figure 13 This is an explanatory diagram used to explain the update of the claim status in the first embodiment;

[0039] Figure 14 This is an explanatory diagram illustrating an example of a screen that provides users with information related to an item;

[0040] Figure 15 This is a first sequence diagram illustrating an example of a schematic flow of processing within a system;

[0041] Figure 16 This is a second sequence diagram illustrating an example of a schematic flow of processing within the system;

[0042] Figure 17 This is a third sequence diagram illustrating an example of a schematic flow of processing within the system;

[0043] Figure 18 This is a flowchart illustrating an example of the delivery status update process according to a first practical example of the first embodiment;

[0044] Figure 19 This is a flowchart illustrating an example of the delivery status update process according to a second practical example of the first embodiment;

[0045] Figure 20 This is a flowchart illustrating an example of the process for updating the claim status according to the first embodiment;

[0046] Figure 21 This is a schematic diagram illustrating an example configuration of an item management system according to the second embodiment;

[0047] Figure 22 This is a block diagram illustrating an example configuration of a management server according to the second embodiment;

[0048] Figure 23 This is an explanatory diagram illustrating an example of the configuration of a user tag table;

[0049] Figure 24 It is an explanatory diagram used to interpret entity determination based on user tag readings;

[0050] Figure 25 This is an explanatory diagram used to explain tag reading during the delivery operation in the second embodiment;

[0051] Figure 26 This is an explanatory diagram used to explain the update of the delivery status in the second embodiment;

[0052] Figure 27 This is an explanatory diagram used to explain the tag reading during the retrieval operation in the second embodiment;

[0053] Figure 28 This is an explanatory diagram used to explain the update of the claim status in the second embodiment;

[0054] Figure 29 This is a flowchart illustrating an example of the delivery status update process according to the second embodiment;

[0055] Figure 30 This is a flowchart illustrating an example of the process for updating the claim status according to the second embodiment;

[0056] Figure 31 This is a block diagram illustrating an example of a label reader configuration that has been modified according to the example.

[0057] Figure 32 This is a block diagram illustrating an example of configuring the management server according to a modified example; and

[0058] Figure 33 This is an explanatory diagram used to explain changes to the entity to which an item in the example belongs. Detailed Implementation

[0059] In the following, embodiments will be described in detail with reference to the accompanying drawings. Note that the following embodiments are not intended to limit the scope of the claimed invention. Several features are described in the embodiments, but the invention is not limited to requiring all such features, and multiple such features can be suitably combined. Furthermore, in the drawings, the same reference numerals are given to the same or similar configurations, and redundant descriptions thereof are omitted.

[0060] <1. First Embodiment>

[0061] <1-1. System Overview>

[0062] Figure 1This is a schematic diagram illustrating an example configuration of the item management system 1 according to the first embodiment. The item management system 1 is a system that manages item data in a database, indicating the entity to which an item belongs, in situations where items can be transferred between multiple entities. The transfer of an item can be any action involving, for example, the transfer of ownership, right of use, information access rights, or management responsibility for the item. Examples of transfers can include sale, assignment, lease, and return, whether for consideration or not. An entity can be any entity to which an item can belong, such as an individual, organization, company, department within a company, geographical region, etc. Examples of the entity to which an item belongs can include the owner of the item, the user of the item, the manager of the item, the place where the item is stored, and the location of the item.

[0063] Items can be inanimate objects (e.g., machines, equipment, tools, materials, consumer goods, vehicles, or robots) or living objects (e.g., animals or plants). To name just a few examples, the items management system1 can be applied to a variety of scenarios, such as the transfer of construction machinery between building developers and machinery rental operators, the transfer of commercial equipment between companies and rental operators, the delivery of goods from transport operators to users, and the transfer of farm animals between farmers.

[0064] The item management system 1 includes location tags 40a, 40b, and 40c installed in different locations, item tags 50a, 50b, and 50c attached to items, at least two tag readers 100a and 100b, a management server 200, and user terminals 300a and 300b. It should be noted that in the following description, when tag readers 100a and 100b do not need to be distinguished from each other, they are collectively referred to as tag reader 100 by omitting the last letter from the reference symbol. This also applies to location tags 40a, 40b, and 40c (location tags 40), item tags 50a, 50b, and 50c (item tags 50), and user terminals 300a and 300b (user terminals 300), and any other constituent elements.

[0065] Tag reader 100, management server 200, and user terminal 300 are connected to network 5. Network 5 can be a wired network, a wireless network, or any combination thereof. Examples of network 5 can include the Internet, an intranet, and a cloud network.

[0066] Location tag 40 is a wireless device installed in the item management system 1 in various possible locations where users can store items. Figure 1The illustration depicts three locations 10a, 10b, and 10c where a user might store items. For example, location 10a is a warehouse controlled by entity E1 (e.g., Company A), location 10b is a work site controlled by entity E2 (e.g., Company B), and location 10c is a parking space controlled by entity E1. Location tag 40a is installed at a predetermined location in warehouse 10a and has specific tag identification information 41a embedded in the tag. Location tag 40b is installed at a predetermined location in work site 10b and has specific tag identification information 41b embedded in the tag. Location tag 40c is installed at a predetermined location in parking space 10c and has specific tag identification information 41c embedded in the tag. The installation location of each location tag 40 can be fixed or can be changed within each location. When the location itself moves (e.g., the work site can move), the corresponding location tag can be repositioned as the location moves.

[0067] Item tag 50 is a wireless device attached to each item managed in the item management system 1. Figure 1 The illustration shows three items 30a, 30b, and 30c. Item 30a is located in warehouse 10a of entity E1 and has an item tag 50a attached to it. Item tag 50a has specific tag identification information 51a embedded in the tag. Item 30b is also located in warehouse 10a of entity E1 and has an item tag 50b attached to it. Item tag 50b has specific tag identification information 51b embedded in the tag. Item 30c is located in work site 10b of entity E2 and has an item tag 50c attached to it. Item tag 50c has specific tag identification information 51c embedded in the tag. Each item 30 is moved by being handled by a user, or moved autonomously according to user operation (e.g., it drives, walks, flies, or sails). When each item 30 moves, the item tag 50 attached to the item 30 moves with the item 30.

[0068] In this embodiment, it is assumed that each of the tags, such as location tag 40 and item tag 50, is a passive RFID tag (passive tag). A passive tag consists of a small integrated circuit (IC) chip with embedded memory; an antenna; and identification information for identifying the tag, as well as some other information stored in the memory. In this specification, the identification information is simply referred to as ID, and the identification information used to identify the tag is called the tag ID. It should be noted that the tag ID can be considered as information used to identify the object to which the tag is attached. The IC chip of the passive tag operates by utilizing the energy of electromagnetic waves emitted from the tag reader and modulates the information stored in the memory into an information signal to transmit (send back) the information signal from the antenna.

[0069] It should be noted that, in another embodiment, each tag may be an active RFID tag. If each tag actively (e.g., periodically) transmits information to its vicinity using power from an internal battery, then such a tag may be referred to as a beacon tag. In another embodiment, each tag may be a wireless device that, for example, transmits information in response to a signal from a reader according to a Near Field Communication (NFC) protocol or Bluetooth (registered trademark) protocol. Each tag may have any name, such as an IC tag, IC card, or transponder.

[0070] Tag reader 100 is a reading device that reads information from RFID tags. Tag reader 100 performs readings periodically or in response to a trigger such as a user operation, and transmits the tag reading results to management server 200. Tag reader 100 may be able to communicate with management server 200 directly or indirectly via a relay device. Figure 1 The illustration shows tag reader 100a used by user 20a and tag reader 100b used by user 20b. An example of a specific configuration of tag reader 100 will be described further later.

[0071] Management server 200 is an information processing device that manages item data indicating which of two or more entities each item 30 belongs to. Management server 200 can be implemented as an application server, database server, or cloud server, for example, using a high-end general-purpose computer. Management server 200 receives tag reading results from each tag reader 100 and updates the item data based on the received tag reading results, making it reflect the latest management status of each item 30. Management server 200 also has an information provisioning function that provides item-related information to the user. Item-related information is typically provided to the user on the screen of user terminal 300. An example of a specific configuration of management server 200 will be described further later.

[0072] exist Figure 1 In the example, management server 200 is a cloud server deployed in a cloud environment. Although in Figure 1 The illustration shows a single management server 200, but the item management functions of the management server 200, which will be described in detail later, can be provided by a single device or by multiple physically separate devices operating in combination with each other. Furthermore, while this embodiment will describe an example of the management server 200 maintaining a database including item data, devices other than the management server 200 can maintain a portion or all of the database. For example, a portion of the data may be maintained by a wireless device (e.g., location tags or item tags) or by a tag reader.

[0073] User terminal 300 is a terminal device used by users of the item management system 1. User terminal 300 can be a general-purpose terminal such as a personal computer (PC) or smartphone, or a dedicated terminal specifically for item management purposes. User terminal 300 typically includes an input device for receiving user input, a communication interface for communicating with other devices (e.g., management server 200), and a display device for displaying information. As an example, user terminal 300 is used by a user to query item-related information from management server 200. As another example, user terminal 300 is used by a user to enter an appointment for an operation to transfer items between entities. Examples of the user interface provided by user terminal 300 to the user in these scenarios will be further described later.

[0074] It should be noted that, although Figure 1 The tag reader 100 and user terminal 300 are illustrated as separate devices, but an integrated device with the functions of both the tag reader 100 and the user terminal 300 can be provided. Furthermore, the user terminal 300 can have a relay function to relay communication between the tag reader 100 and the management server 200.

[0075] <1-2. Tag Reader Configuration Example>

[0076] Figure 2 This is a block diagram illustrating an example configuration of the tag reader 100 according to the first embodiment. (See reference) Figure 2 The tag reader 100 includes a control unit 101, a storage unit 102, a communication unit 103, a positioning unit 104, a power supply 105, and a reading unit 106.

[0077] The control unit 101 consists of a memory storing a computer program and one or more processors (e.g., a central processing unit (CPU)) executing the computer program. The control unit 101 controls the overall functionality of the tag reader 100 described in this specification. For example, the control unit 101 causes the reading unit 106 to read RFID tags within the tag reading range, and causes the storage unit 102 to temporarily store the read information and the reading time as read result data. The control unit 101 can also cause the positioning unit 104 to perform current location positioning and add coordinates indicating the current location to the read result data. Then, the control unit 101 transmits the read result data stored in the storage unit 102, along with the reader identification information of the tag reader 100, to the management server 200 via the communication unit 103.

[0078] Storage unit 102 may include any type of storage medium, such as semiconductor memory (e.g., read-only memory (ROM), random access memory (RAM), etc.), optical disk, or magnetic disk. In this embodiment, storage unit 102 stores the read result data, the positioning result of positioning unit 104, and the reader identification information of tag reader 100.

[0079] Communication unit 103 is a communication interface for the tag reader 100 to communicate with management server 200. For example, communication unit 103 may be a wireless local area network (WLAN) interface for communicating with a WLAN access point, or a cellular communication interface for communicating with a cellular base station. Alternatively, communication unit 103 may be a connection interface (e.g., a Bluetooth (trademarked) interface or a Universal Serial Bus (USB) interface) for connecting to a relay device (e.g., a mobile terminal carried by user 20).

[0080] The positioning unit 104 is a positioning module that measures or estimates the current position of the tag reader 100. The positioning unit 104 can measure the relative movement from a reference position using, for example, a three-axis accelerometer, a gyroscope sensor, and a geomagnetic sensor, and calculate the position coordinates of the current position by adding the relative movement to the known coordinates of the reference position. In this document, the reference position may, for example, be the position of the location tag 40. Alternatively, the positioning unit 104 may be a GPS module that measures the current geographic location of the tag reader 100 using a Global Positioning System (GPS). Alternatively, the positioning unit 104 may be a positioning module that performs base station positioning or wireless LAN positioning to estimate the current position using the known location coordinates of a base station or wireless LAN access point to which the device is connected. The positioning unit 104 outputs two-dimensional or three-dimensional position coordinates indicating the current position of the tag reader 100 obtained as a result of positioning to the control unit 101.

[0081] The power supply 105 includes a battery and a DC-DC converter, and supplies power to the electronic circuitry for operating the control unit 101, storage unit 102, communication unit 103, positioning unit 104, and reading unit 106 of the tag reader 100. The battery may be a primary battery or a rechargeable secondary battery. Although not shown in the figures, the tag reader 100 may have connection terminals for connecting the tag reader 100 to an external power source for charging the power supply 105.

[0082] Reading unit 106 is a reading module capable of reading identification information stored in various RFID tags from location tags 40 installed at various locations in the item management system 1 and item tags 50 that move with the item 30. (Reference) Figure 2The reading unit 106 includes an RF controller 110, a power amplifier 111, a filter 112, a first coupler 113, a second coupler 114, an antenna 115, a power detector 116, and a canceller 117. The RF controller 110, under the control of the control unit 101, outputs a transmitted signal (e.g., a signal modulated in the UHF band) from the TX terminal to the power amplifier 111. The power amplifier 111 amplifies the transmitted signal input from the RF controller 110 and outputs it to the filter 112. The filter 112 may be, for example, a low-pass filter, and filters out unwanted frequency components from the transmitted signal amplified by the power amplifier 111. The first coupler 113 distributes the transmitted signal, which has been filtered by the filter 112, to the coupler 114 and the power detector 116. The second coupler 114 outputs the transmitted signal input from the first coupler 113 to the antenna 115, and outputs the received signal input from the antenna 115 to the RF controller 110. The antenna 115 transmits the transmitted signal input from the coupler 114 as an electromagnetic wave into the air. Additionally, antenna 115 receives signals transmitted from RFID tags present within the reading range of tag reader 100 in response to transmitted signals, and outputs the received signals to coupler 114. Power detector 116 detects the power level of the signal input from first coupler 113 and outputs a signal 'RF_DETECT' indicating the detected power level to control unit 101. Canceller 117 receives a signal 'CARRIER_CANCEL' indicating the power level of the carrier from control unit 101. Then, canceller 117 extracts the expected signal components of the received signal to be output to the RX terminal of RF controller 110 by cancelling the carrier component of the transmitted signal based on CARRIER_CANCEL. RF controller 110 demodulates the signal input from the RX terminal to obtain the tag ID and other information transmitted from the RFID tag, and outputs the obtained information to control unit 101.

[0083] In this embodiment, the reading unit 106 may attempt tag reading periodically (e.g., once per second) without any explicit command from the user. The transmission of read result data from the communication unit 103 to the management server 200 may also be performed periodically (e.g., every few seconds) or whenever a tag reading is completed, without any explicit command from the user. The control unit 101 may exclude records identical to the most recent records already transmitted within a predetermined time period from the read result data to be transmitted, thus eliminating redundant data transmission and reducing communication load. It should be noted that in another embodiment, one or both of the tag reading attempt by the reading unit 106 and the transmission of read result data to the management server 200 may be performed in response to user input via a user interface arranged in the tag reader 100. In the case where the communication unit 103 communicates indirectly with the management server 200 via a relay device, the transmission of read result data to the management server 200 may be performed only when a valid connection exists between the communication unit 103 and the relay device.

[0084] <1-3. Configuration Example of Management Server>

[0085] <1-3-1. Basic Configuration>

[0086] Figure 3 This is a block diagram illustrating an example configuration of the management server 200 according to the first embodiment. (See reference) Figure 3 The management server 200 includes a communication unit 210, an item database (DB) 220, and an item management unit 230.

[0087] Communication unit 210 is a communication interface used for communication between management server 200 and other devices. Communication unit 210 can be a wired communication interface or a wireless communication interface. In this embodiment, communication unit 210 communicates with tag reader 100 and user terminal 300 within the item management system 1. Item DB 220 consists of tables used to manage data indicating which entity each item under the system belongs to. In this embodiment, item DB 220 includes item table 310, location table 320, reader table 330, user table 340, reading result table 350, delivery reservation table 360, and collection reservation table 370. Item management unit 230 is a set of software modules that provide item management functions for managing data within item DB 220. Each software module can be run by executing a computer program stored in memory (not shown) through one or more processors (not shown) of management server 200. In this embodiment, item management unit 230 includes tag processing unit 231, location management unit 232, transfer processing unit 233, and information providing unit 234.

[0088] <1-3-2. Example of Master Data>

[0089] The item table 310, location table 320, reader table 330, and user table 340 in item DB 220 are tables used as so-called master data pre-registered in item DB 220. Figures 4A to 4D The diagrams illustrate various configuration examples for these tables.

[0090] The item table 310 has six data elements, including tag ID 311, item ID 312, name 313, organization 314, storage location 315, and coordinates 316. Tag ID 311 uniquely identifies the item tag 50 attached to each item managed by the system. The value of tag ID 311 is the same as the value of the tag ID stored in the corresponding item tag 50. Item ID 312 uniquely identifies each item. Name 313 represents the name of each item. Figure 4A In the example, the item identified by item ID 'IT01' has the name 'Item A', the item identified by item ID 'IT02' has the name 'Item B', and the item identified by item ID 'IT03' has the name 'Item C'. Here, 'Item A', 'Item B', and 'Item C' are respectively associated with... Figure 1 Items 30a, 30b, and 30c are shown in the diagram. Organization 314 represents the entity to which each item belongs. In this document, it is assumed that each item belongs to an entity responsible for managing that item. Figure 4A In the example, 'Company A' has management responsibility for 'Item A' and 'Item B', while 'Company B' has management responsibility for 'Item C'. Here, 'Company A' and 'Company B' are respectively associated with... Figure 1 The described entities E1 and E2 correspond. As will be described later, the value of organization 314 can be changed by transfer processing unit 233 in response to the transfer of items. Storage location 315 uses a location ID that identifies the location to represent the location where each item is stored. Figure 4A In the example, 'Item A' and 'Item B' are stored in the location identified by location ID 'PL01'. 'Item C' is stored in the location identified by location ID 'PL02'. Coordinate 316 represents the latest location coordinates of each item. As will be described later, when the tag reader 100 detects movement of an item, the values ​​of storage location 315 and coordinate 316 can be updated by the location management unit 232.

[0091] Location table 320 has five data elements: tag ID 321, location ID 322, name 323, organization 324, and coordinates 325. Tag ID 321 uniquely identifies the location tag 40 installed in each location under system management. The value of tag ID 321 is the same as the tag ID value stored in the corresponding location tag 40. Location ID 322 uniquely identifies each location. Name 323 represents the name of each location. Figure 4B In the example, the location identified by location ID 'PL01' is named 'Warehouse', the location identified by location ID 'PL02' is named 'Work Site', and the location identified by location ID 'PL03' is named 'Parking Space'. Here, 'Warehouse', 'Work Site', and 'Parking Space' are respectively... Figure 1 Locations 10a, 10b, and 10c are shown in the diagram. Organization 324 represents an entity responsible for managing each location. Figure 4B In the example, 'Company A' has management responsibility for 'warehouse' and 'parking space', while 'Company B' has management responsibility for 'work site'. Coordinate 325 represents the location coordinate of the location label 40 installed in each location.

[0092] The reader table 330 has three data elements: reader ID 331, name 332, and organization 333. Reader ID 331 uniquely identifies each of the tag readers 100 used in the system. Name 332 represents the name of each reader. Figure 4C In the example, the tag reader 100 identified by reader ID 'RD01' is named 'Reader A', and the tag reader 100 identified by reader ID 'RD02' is named 'Reader B'. Here, 'Reader A' and 'Reader B' are respectively associated with... Figure 1 The tag readers 100a and 100b shown correspond to each other. Organization 333 represents the entity responsible for managing each tag reader. Figure 4C In the example, 'Company A' has management responsibility for 'Reader A', while 'Company B' has management responsibility for 'Reader B'.

[0093] User table 340 has three data elements: User ID 341, Name 342, and Organization 343. User ID 341 uniquely identifies each of the users 20 using the item management system 1. Name 342 represents each user's name. Figure 4D In the example, the user identified by user ID 'A001' is named 'User A', and the user identified by user ID 'B001' is named 'User B'. Here, 'User A' and 'User B' are respectively... Figure 1 Users 20a and 20b are shown in the diagram. Organization 343 represents the organization to which each user belongs. Figure 4D In the example, 'User A' belongs to 'Company A', while 'User B' belongs to 'Company B'.

[0094] <1-3-3. Knowing the Storage Status of Items>

[0095] The tag processing unit 231 of the item management unit 230 adds the read result data received from each of the tag readers 100 via the communication unit 210 to the read result table 350. In this document, an inventory operation (which is one such operation that creates read result data during the process) is used as an example. Figure 5 This section describes a configuration example for storing the read result data in the read result table 350.

[0096] exist Figure 5 On the left, the illustration shows a user carrying a tag reader 100a accessing location 10a under entity E1 for inventory operations. When location tag 40a enters the reading range of tag reader 100a, tag reader 100a reads the tag ID 'TG11' of location tag 40a. When item tag 50a of item 30a enters the reading range, tag reader 100a reads the tag ID 'TG01' of item tag 50a. When item tag 50b of item 30b enters the reading range, tag reader 100a reads the tag ID 'TG02' of item tag 50b. When the scheduled transmission time for the reading result data arrives, tag reader 100a transmits the reading result data (including three records) indicating the tag reading results to management server 200. Tag processing unit 231 adds the three records of the reading result data received via communication unit 210 to reading result table 350.

[0097] refer to Figure 5The read result table 350 has five data elements, including record number 351, read time 352, tag ID 353, reader ID 354, and coordinates 355. In the following description, the record indicating record number 'N' is referred to as record #N (N is an integer). Record #1 of the read result table 350 indicates that the tag reader 100a, identified by reader ID 'RD01', has read the location tag 40a, identified by tag ID 'TG11', and the current location coordinates are (Xa,Ya). Record #2 indicates that the tag reader 100a has read the item tag 50a, identified by tag ID 'TG01', and the current location coordinates are (X1,Y1). Record #3 indicates that the tag reader 100a has read the item tag 50b, identified by tag ID 'TG02', and the current location coordinates are (X2,Y2). In this embodiment, the tag ID and other information read by each tag reader 100 are collected and stored by the management server 200 in this manner without any explicit user commands. In this way, the management server 200 can easily know which item is stored in which managed location without requiring cumbersome operations from the user.

[0098] After adding the record of the read result data received from the tag reader 100 to the read result table 350, the tag processing unit 231 calls the location management unit 232. The location management unit 232 updates the value of the coordinate 316 of the corresponding item in the item table 310 using the latest location coordinates of the item tag 50 indicated by the record added to the read result table 350. Additionally, the location management unit 232 determines the correspondence between the tag ID of the location tag 40 and the tag ID of the item tag 50 based on the temporal correlation between corresponding records of multiple read results received from the same reading device. For example, the location management unit 232... Figure 5 Records #1 and #2 shown indicate that tag reader 100a has read the tag ID 'TG11' of location tag 40a and the tag ID 'TG01' of item tag 50a within a predetermined interval (e.g., seconds to minutes). Therefore, location management unit 232 knows that item 30a is stored in location 10a where location tag 40a is installed, and updates the value of storage location 315 of item 30a (associated with tag ID 'TG01') in item table 310 to location ID 'PL01'. Similarly, location management unit 232... Figure 5 Records #1 and #3 shown indicate that item 30b is also stored in location 10a, and update the value of storage location 315 for item 30b in item table 310 to location ID 'PL01'. It should be noted that if each item 30b has not yet been moved, the value of storage location 315 will not change, and in this case, the update of that value can be skipped.

[0099] In this way, the item management unit 230 maintains the data in the item DB 220 so that it reflects the latest status about where each item 30 under the system management is currently stored and at what coordinates each item 30 is located.

[0100] <1-3-4. Transfer of Items (Change of the Entity to which the Item Belongs)>

[0101] The previous section described the process of simply tracking the movement of items within the same entity. This section will now describe how to handle the transfer of ownership, usage rights, information access rights, or management responsibilities of items—that is, the transfer of items between entities. This paper will primarily describe two types of operational models for transferring items: item delivery and item collection. Item delivery refers to the operation where the person in charge of the source entity moves (e.g., transports) the item to a location associated with the destination entity. Item collection refers to the operation where the person in charge of the destination entity visits a location associated with the source entity to collect the item. It should be noted that these names for operational models are merely examples, and any name other than "delivery" and "collection" may be used.

[0102] In this embodiment, the transfer processing unit 233 receives advance reservation information indicating that the operation of transferring item 30 will be performed for both delivery and collection. Then, the transfer processing unit 233 changes the entity to which item 30 belongs in item DB 220 based on the reading result of at least one tag reader 100 and the received reservation information.

[0103] (1) Receipt of delivery appointment

[0104] The transfer processing unit 233 causes the display device of the user terminal 300 to display a delivery reservation screen that provides a user interface (UI) for receiving delivery operation reservations. The transfer processing unit 233 stores the delivery reservation information received via the delivery reservation screen in the delivery reservation table 360 ​​of the item DB 220.

[0105] Figure 6 This is an explanatory diagram illustrating an example of the configuration for the delivery appointment screen and delivery appointment form. In this document, it is assumed that user 20a logs into the system using user terminal 300a and performs a delivery appointment operation. Figure 6On the left side, as an example illustration, a delivery appointment screen 400 is shown, where the logged-in username 'User A' is displayed at the top of the screen. The delivery appointment screen 400 includes a storage location selection bar 401, a transfer destination selection bar 402, a delivery location selection bar 403, a date specification bar 404, an item display area 411, and a destination display area 412. The storage location selection bar 401 is a UI that allows the logged-in user to select a storage location for the item 30 to be delivered from locations associated with the entity to which the user belongs. The transfer destination selection bar 402 is a UI that allows the logged-in user to select an entity to which the item is to be transferred from entities other than the entity to which the user belongs. The delivery location selection bar 403 is a UI that allows the user to select a location to which the item 30 is to be delivered from locations associated with the entity selected in the transfer destination selection bar 402. The date specification bar 404 is a UI that allows the user to specify the date on which the delivery operation will be performed (i.e., the expected delivery date). The item display area 411 displays icons representing items currently stored in the location selected in the storage location selection bar 401, based on the item table 310. Figure 6 In the example, as a result of selecting 'Warehouse' in the storage location selection bar 401, two icons representing items 30a and 30b currently stored in the warehouse are displayed in the item display area 411. The display position of each icon in the item display area 411 can be determined based on the coordinates of the corresponding item, thus virtually representing the current position of the item in the storage location. The destination display area 412 is a display area that virtually represents the destination of the delivery operation selected in the transfer destination selection bar 402 and the delivery location selection bar 403. Figure 6 In the example, the 'work site' of entity E2 (i.e., 'Company B') is selected as the destination for the delivery operation. For example, a user can designate item 30a as the target item to be delivered to the 'work site' by dragging and dropping the icon of item 30a displayed in item display area 411 into destination display area 412.

[0106] The transfer processing unit 233 receives such delivery reservation information via the delivery reservation screen 400. (Reference) Figure 5 On the right side, the delivery reservation form 360 has five data elements, including record number 361, expected delivery date 362, item ID 363, destination 364, and status 365. For example, record #2 of the delivery reservation form 360 indicates that item 30a, identified by item ID 'IT01', is expected to be delivered to the location identified by location ID 'PL02' on date 'YMD2', which is the expected delivery date. At the time the delivery reservation is received, the delivery operation has not been completed, so the transfer processing unit 233 sets the value of status 365 of that record to 'reserved'.

[0107] It should be noted that, Figure 6 The delivery appointment screen 400 shown is merely an example of a UI for receiving delivery appointments. The transfer processing unit 233 can receive delivery appointments via another screen with any other configuration. The transfer processing unit 233 can receive delivery appointments via a voice UI, or even by receiving a reservation data file describing the reservation information.

[0108] (2) Transfer of goods by delivery

[0109] For ease of explanation, it is assumed here that a target item (e.g., item 30a) belonging to a second entity (e.g., company A) associated with a second location is transferred to a first entity (e.g., company B) associated with a first location. It should be noted that in this specification, modifiers such as "first" and "second" are used only to distinguish multiple objects from one another, and these modifiers do not imply any ordering relationship. Before the delivery operation is performed, item table 310 indicates that the target item belongs to the second entity. From this state, if at least the first reading device has read the tag ID of the location tag of the first location and the tag ID of the item tag of the target item, the transfer processing unit 233 updates item table 310 so that it indicates that the target item belongs to the first entity. In the example where item 30a is delivered to location 10b, the location tag of the first location corresponds to location tag 40b, and the item tag of the target item corresponds to item tag 50a. These conditions mean that the tag reading results indicate that the target item has been properly delivered to the location associated with the first entity (e.g., a location managed by the first entity).

[0110] As a first practical example, delivery to the appropriate location can be confirmed by a first reading device (e.g., tag reader 100b) associated with a first entity and a second reading device (e.g., tag reader 100a) associated with a second entity. As a second practical example, delivery to the appropriate location can be confirmed solely by the first reading device (e.g., tag reader 100b) associated with the first entity receiving the target item.

[0111] Figure 7 This is an explanatory diagram used to explain tag reading during the delivery operation in the first practical example. Figure 7In the example, the target item for delivery is item 30a, which belongs to entity E1 and has been stored in location 10a. User 20a, carrying tag reader 100a, transports item 30a to location 10b on the expected delivery date. User 20b, carrying tag reader 100b, receives item 30a at location 10b. While user 20a remains at location 10b, tag reader 100a reads the tag ID of location tag 40b installed at location 10b and the tag ID of item tag 50a of item 30a, and transmits the reading result data to management server 200. Simultaneously, tag reader 100b reads the tag ID of location tag 40b and the tag ID of item tag 50a, and also transmits the reading result data to management server 200. The tag processing unit 231 of management server 200 stores these multiple reading result data received via communication unit 210 in reading result table 350.

[0112] Figure 8 It is used to explain based on usage Figure 7 An explanatory graph showing the updated delivery status of the results of the tag reading description. Figure 8 The read result table 350 has Figure 7The example shows two records #4 and #5 indicating the tag reading results of tag reader 100a, and two records #6 and #7 indicating the tag reading results of tag reader 100b. For example, transfer processing unit 233 refers to delivery reservation form 360 and knows that item 30a, identified by item ID 'IT01', is expected to be delivered to location 10b, identified by destination 'PL02', on the expected delivery date 'YMD2'. This delivery arrangement indicates that item 30a is to be transferred from entity E1 (company A) to entity E2 (company B) to which item 30a currently belongs. Transfer processing unit 233 knows from records #4 and #5 of the read result table 350 that tag reader 100a associated with entity E1 has read the tag ID 'TG21' of location tag 40b and the tag ID 'TG01' of item tag 50a at location 10b. Furthermore, the transfer processing unit 233 learns from records #6 and #7 of the read result table 350 that the tag reader 100b associated with entity E2 has read the tag ID 'TG21' of location tag 40b and the tag ID 'TG01' of item tag 50a. Based on the read results, the transfer processing unit 233 determines that the expected delivery operation has been performed and updates the value of the status 365 of the corresponding reservation information record #2 in the delivery reservation table 360 ​​to 'complete'. Moreover, the transfer processing unit 233 updates the value of the organization 314 of the item 30a record in the item table 310 to 'Company B', which is the name of entity E2. Similar to the processing in the inventory operation, the location management unit 232 updates the value of the storage location 315 of the item 30a record in the item table 310 to the location ID 'PL02', and updates the value of the coordinates 316 to the latest location coordinates (X4, Y4) of item 30a.

[0113] Based on this first practical example, the proper execution of the delivery operation is confirmed by the results of tag readings from both the tag reader under the management of the source entity and the tag reader under the management of the destination entity. Therefore, the entity to which the item belongs can be appropriately changed while reliably preventing the parties involved in the transfer from missing each other.

[0114] Figure 9 This is an explanatory diagram used to explain tag reading during the delivery operation in the second practical example. Figure 9In the example, the target item to be delivered is also item 30a belonging to entity E1 and already stored in location 10a. User 20a transports item 30a to location 10b on the expected delivery date. User 20b, carrying tag reader 100b, receives item 30a at location 10b. Tag reader 100b reads the tag ID of the location tag 40b installed at location 10b and the tag ID of the item tag 50a of item 30a received by user 20b, and transmits the reading result data to management server 200. The tag processing unit 231 of management server 200 stores the reading result data received via communication unit 210 in reading result table 350.

[0115] Figure 10 It is used to explain based on usage Figure 9 An explanatory graph showing the updated delivery status of the results of the tag reading description. Figure 10 The read results table 350 has an indication Figure 9 In the example, the tag reader 100b reads two records, #6 and #7, as a result of the tag reading. For example, the transfer processing unit 233 refers to the delivery reservation form 360 and is aware of the expected delivery schedule. Figure 8 This is a similar delivery operation to the example. The transfer processing unit 233 learns from records #6 and #7 of the read result table 350 that the tag reader 100b associated with entity E2 has read the tag ID 'TG21' of location tag 40b and the tag ID 'TG01' of item tag 50a. Based on the read results, the transfer processing unit 233 determines that the expected delivery operation has been performed and updates the value of the status 365 of the corresponding reservation information record #2 in the delivery reservation table 360 ​​to 'complete'. Furthermore, the transfer processing unit 233 updates the value of the organization 314 of the item 30a record in the item table 310 to 'company B'. The location management unit 232 updates the value of the storage location 315 of the item 30a record in the item table 310 to the location ID 'PL02', and updates the value of the coordinates 316 to the latest location coordinates (X4, Y4) of item 30a.

[0116] According to this second practical example, the execution of the delivery operation is confirmed based on the tag reading result of the tag reader under the management of the destination entity, and the entity to which the item belongs is changed accordingly in item DB 220. Therefore, the person in charge on the source entity side does not necessarily need to activate its own tag reader at the time of delivery, which allows the avoidance of the inconvenience of item data update failure due to the tag reader not being carried or malfunctioning (e.g., battery depletion).

[0117] In both practical examples, the transfer processing unit 233 changes the entity to which the target item belongs based on the tag reading results from at least the first reading device and on delivery reservation information indicating that the operation to move the target item to its destination will be performed. This means that when there is no valid delivery reservation information, the entity to which the target item belongs will not be changed solely based on the tag reading results. Therefore, if the tag ID of an item to be transported to a destination is unintentionally read by a tag reader at another location visited en route, or if the item is taken to an inappropriate location by a third party, the situation where the entity to which the item belongs can be prevented from being incorrectly changed. If the reading result data indicates that, for a given item, the tag reader has read the location tag of a location that is neither under the management of the entity to which the item currently belongs nor designated as the destination in the reservation information, as well as the item tag of the item, the transfer processing unit 233 can issue a warning to the user. This allows the user to immediately notice that the item has been incorrectly transported or improperly removed. It should be noted that such cross-checking with reservation information is not always necessary. For example, in environments where there are no problems caused by tag readers unintentionally reading tag IDs, simple transfer management without cross-checking with reservation information is also advantageous. This also applies to the pick-up appointment described later.

[0118] (3) Receiving the appointment receipt

[0119] The transfer processing unit 233 causes the display device of the user terminal 300 to display a pickup reservation screen, which provides a UI for receiving pickup reservations. The transfer processing unit 233 stores the pickup reservation information received via the pickup reservation screen in the pickup reservation table 370 of the item DB 220.

[0120] Figure 11 This is an explanatory diagram illustrating the configuration of the appointment booking screen and appointment booking form. In this document, it is assumed that user 20b logs into the system using user terminal 300b and performs the appointment booking operation. Figure 11On the left side, as an example illustration, a pickup reservation screen 500 is shown, where the logged-in username 'User B' is displayed at the top of the screen. The pickup reservation screen 500 includes a storage location selection bar 501, a pickup party selection bar 502, a date specification bar 504, an item display area 511, and a pickup party display area 512. The storage location selection bar 501 is a UI that allows the logged-in user to select a storage location for the item 30 to be picked up from locations associated with the entity to which the user belongs. The pickup party selection bar 502 is a UI that allows the logged-in user to select an entity other than the entity to which the user belongs as the pickup party (i.e., the transfer destination). The date specification bar 504 is a UI that allows the user to specify the date (i.e., the expected pickup date) for the pickup operation. The item display area 511 displays icons representing items currently stored in the location selected in the storage location selection bar 501, based on the item table 310. Figure 11 In the example, as a result of selecting 'Work Site' in the storage location selection bar 501, two icons representing items currently stored in the work site are displayed in the item display area 511. The display position of each icon in the item display area 511 can be determined based on the coordinates of the corresponding item, thus virtually representing the item's current position in the storage location. The recipient display area 512 is a virtual representation of the recipient selected in the recipient selection bar 502. Figure 11 In the example, entity E1 (i.e., 'Company A') is selected as the recipient. For example, a user can designate item 30a as the target item to be received by the person in charge of entity E1 by dragging and dropping the icon of item 30a displayed in item display area 511 into recipient display area 512.

[0121] The transfer processing unit 233 receives this collection reservation information via the collection reservation screen 500. (Reference) Figure 11 On the right side, the collection reservation form 370 has five data elements, including record number 371, expected collection date 372, item ID 373, recipient 374, and status 375. For example, record #2 of the collection reservation form 370 indicates that item 30a, identified by item ID 'IT01', is expected to be collected by recipient 'Company A' on date 'YMD4', which is the expected collection date. At the time the collection reservation is received, the collection operation has not been completed, so the transfer processing unit 233 sets the value of status 375 of that record to 'reservation'.

[0122] It should be noted that, Figure 11The reservation pick-up screen 500 shown is merely an example of a UI for receiving reservations. The transfer processing unit 233 can receive reservations via another screen with any other configuration. The transfer processing unit 233 can receive reservations via a voice UI, or even by receiving a reservation data file describing the reservation information.

[0123] (4) By receiving the transferred items

[0124] For ease of explanation, it is assumed here that a target item (e.g., item 30a) belonging to a first entity (e.g., company B) associated with a first location is transferred to a second entity (e.g., company A) associated with a second location via a retrieval operation. Before the retrieval operation is performed, item table 310 indicates that the target item belongs to the first entity. From this state, when a second reading device associated with the second entity reads the tag ID of the location tag of the first location and the tag ID of the item tag of the target item, the transfer processing unit 233 updates item table 310 so that it indicates that the target item belongs to the second entity. In this embodiment, the state of the second reading device being associated with the second entity means that there is data that associates the second reading device with the second entity. For example, as used... Figure 4C As explained, the reader table 330 of item DB 220 has a record that associates the tag reader 100a, identified by reader ID 'RD01', with the manager 'Company A'. Therefore, tag reader 100a is associated with entity E1 named 'Company A'. In the example where user 20a, as the person in charge of Company A, retrieves item 30a stored in location 10b, the second reading device corresponds to tag reader 100a, the location tag of the first location corresponds to location tag 40b, and the item tag of the target item corresponds to item tag 50a. These conditions imply that the tag reading result indicates that the person in charge of the legitimate recipient has visited the appropriate location to retrieve the target item.

[0125] Figure 12 This is an explanatory diagram used to explain the tag reading during the retrieval operation in this embodiment. Figure 12 In the example, the target item to be retrieved is item 30a, which belongs to entity E2 and is stored in location 10b. User 20a, carrying tag reader 100a, visits location 10b on the expected retrieval date and retrieves item 30a. While user 20a remains in location 10b, tag reader 100a reads the tag ID of the location tag 40b installed in location 10b and the tag ID of the item tag 50a of item 30a, and transmits the read result data to management server 200. The tag processing unit 231 of management server 200 stores this read result data received via communication unit 210 in read result table 350.

[0126] After retrieving item 30a from location 10b, user 20a takes item 30a back to location 10a under the management of entity E1. Tag reader 100a reads the tag ID of location tag 40a installed at location 10a and the tag ID of item tag 50a of item 30a, and transmits the reading result data to management server 200. Tag processing unit 231 of management server 200 stores this reading result data received via communication unit 210 in reading result table 350.

[0127] Figure 13 It is used to explain based on usage Figure 12 The diagram illustrates the update of the claim status of the results read from the described tag. Figure 13 The read results table 350 has an indication Figure 12 In the example, records #8 and #9 show the results of tag reading by tag reader 100a at location 10b. For instance, transfer processing unit 233 refers to collection reservation form 370 and knows that item 30a, identified by item ID 'IT01', is expected to be collected by the person in charge of entity E1 (which is company A) on the expected collection date 'YMD4'. This collection arrangement indicates that item 30a will be transferred from entity E2 (company B) to entity E1 (company A), where item 30a currently belongs. Transfer processing unit 233 knows from records #8 and #9 of the reading result form 350 that tag reader 100a associated with entity E1 has read the tag ID 'TG21' of location tag 40b at location 10b and the tag ID 'TG01' of item tag 50a. Based on this reading result, transfer processing unit 233 determines that the expected collection operation has been performed and updates the value of status 375 of record #2 of the corresponding reservation information in collection reservation form 370 to 'complete'. Furthermore, the transfer processing unit 233 updates the value of the organization 314 of the record of item 30a in the item table 310 to 'Company A', which is the name of entity E1.

[0128] Figure 13 The read result table 350 also has an indicator Figure 12 In the example, after user 20a brings item 30a back to location 10a, the tag reader 100a reads two records #10 and #11. Based on records #10 and #11 in the reading result table 350, the location management unit 232 updates the value of the storage location 315 of the item 30a record in the item table 310 to the location ID 'PL01', and updates the value of coordinates 316 to the latest location coordinates (X6, Y6) of item 30a.

[0129] According to such an embodiment, the entity to which an item belongs can be changed after the appropriate execution of the retrieval operation is confirmed by the tag reader's tag reading result under the management of the destination entity.

[0130] The transfer processing unit 233 changes the entity to which the target item belongs based on the tag reading result of the second reading device under the management of the recipient and based on the pick-up reservation information instructing the person in charge of the recipient to perform the operation of picking up the target item from the current storage location. This means that when there is no valid pick-up reservation information, the entity to which the target item belongs will not be changed solely based on the tag reading result. Therefore, if the item is incorrectly transferred to a third party who has the tag reader 100 but is not a legitimate recipient, the situation where the entity to which the item belongs can be changed accordingly can be prevented. In this case, as in the case of incorrect delivery, the transfer processing unit 233 can also issue a warning to the user associated with the entity to which the target item currently belongs.

[0131] (5) Determining correspondences based on time correlation

[0132] In this embodiment, similar to the location management unit 232, the transfer processing unit 233 can determine the correspondence between tag IDs read from two or more tags based on the temporal correlation between reading results received from the same tag reader 100. For example, the transfer processing unit 233 from... Figure 10 Records #6 and #7 in the read result table 350 shown indicate that tag reader 100b has read the tag ID 'TG21' of location tag 40b and the tag ID 'TG01' of item tag 50a within a predetermined interval. This allows transfer processing unit 233 to determine that tag reader 100b, under the management of transfer destination entity E2, has confirmed that item 30a has been properly delivered to location 10b where location tag 40b is installed. In this way, the correspondence between records is determined on the management server 200 side based on time correlation, so tag reader 100 only needs to simply transmit the results of tag readings from multiple tags along with their respective timestamps to management server 200. With this configuration, the implementation of tag reader 100 can be kept simple, making it easier to deploy multiple tag readers 100 to the system at low cost and expanding the use of item management system 1. The time correlation between read result records can be determined by any determining condition, such as the difference between their respective read times being less than a threshold, the read times belonging to the same time period, or the reads being performed more than a predetermined number of times within a predetermined interval.

[0133] <1-3-5. Provision of Item-Related Information>

[0134] Information providing unit 234 provides user terminals 300 of users associated with each entity with information related to items belonging to that entity, based on data maintained by item DB 220. For example, the item-related information provided to user terminals 300 includes at least one of each item's item ID, name, storage location, location information, and status such as delivery or pickup. When a user who is a member of an entity is logged into the system, only information related to items belonging to that entity can be provided to the logged-in user. Alternatively, information related to items expected to belong to that entity or items previously belonging to that entity can be provided to the logged-in user in a way that distinguishes these statuses. Access to information can be controlled per device rather than per user (or as an adjunct). That is, information providing unit 234 can provide accessing user terminals 300 with only information related to items belonging to the entity associated with the accessing user terminal 300.

[0135] Figure 14 The illustration shows an example of an information provision screen 800 that can be displayed on a user terminal's screen to provide the user with item-related information. In this document, it is assumed that user 20a, using user terminal 300a, logs into the system and queries item-related information. The logged-in username 'User A' is displayed at the top of the screen. The information provision screen 800 includes a map display area 811 and an item list display area 812. The map display area 811 is an area that visually displays the location information of one or more items stored in a location selected by the user in map form. Figure 14 In the example, icons for 'Item A' and 'Item B' stored in the 'Warehouse' are displayed in map display area 811 at coordinates 316 based on item table 310. Item list display area 812 is an area that displays item-related information for one or more items that the user can access in a table format. Figure 14 In the example, the item list display area 812 shows the item IDs, names, storage locations, and statuses of 'Item A', 'Item B', and 'Item D' belonging to entity E1. Meanwhile, information related to items such as 'Item C' belonging to entity E2 is not displayed on the screen. In this way, the item management system 1, which efficiently manages item transfers on the database, can provide access-controlled item-related information to each entity, balancing user convenience in item management with information security.

[0136] It should be noted that, Figure 14The information providing screen 800 shown is merely an example of a screen displaying item-related information. The information providing unit 234 can provide item-related information via another screen with any other configuration. The information providing unit 234 can output item-related information via a voice UI, or even provide item-related information to the user terminal 300 by transmitting a data file describing item-related information to the user terminal 300.

[0137] <1-4 Processing Flow>

[0138] In this section, we will use Figures 15 to 17 sequence diagrams and Figures 18 to 20 The flowchart described below is an example of the processing flow in the item management system 1 according to this embodiment. It should be noted that in the following description, processing steps are abbreviated as S (steps).

[0139] <1-4-1. Inventory>

[0140] Figure 15 The upper part of the diagram illustrates the process flow related to the inventory operation S110 performed by user 20a of company A and user 20b of company B at locations 10a and 10b, respectively.

[0141] First, in S111, when user 20a carrying tag reader 100a visits location 10a, tag reader 100a reads tag IDs from item tags 50 of at least one item 30 stored in location 10a. Next, in S112, tag reader 100a reads tag IDs from location tags 40a installed in location 10a. When the timed communication with management server 200 arrives, in S113, tag reader 100a transmits read result data indicating the results of tag reads performed up to that point to management server 200.

[0142] The tag processing unit 231 of the management server 200 adds the reading result data received from the tag reader 100a in S113 to the reading result table 350 and calls the location management unit 232. In S114, the location management unit 232 updates the location coordinates (values ​​of coordinates 316 in the item table 310) of at least one item 30 stored in location 10a based on the reading result data added to the reading result table 350. If the detected item 30 has been moved from another location (e.g., location 10c) to location 10a, the location management unit 232 also updates the storage location of that item 30 (values ​​of storage location 315 in the item table 310).

[0143] Simultaneously, in S115, when user 20b carrying tag reader 100b visits location 10b, tag reader 100b reads tag IDs from item tags 50 of at least one item 30 stored in location 10b. Next, in S116, tag reader 100b reads tag IDs from location tags 40b installed in location 10b. When the timed communication with management server 200 arrives, in S117, tag reader 100b transmits read result data indicating the results of tag reads performed up to that point to management server 200.

[0144] In S118, as in S114, the tag processing unit 231 and the location management unit 232 of the management server 200 update the detected location coordinates of the item 30 (and, if necessary, the storage location) based on the reading result data received from the tag reader 100b.

[0145] <1-4-2. Delivery Reservation>

[0146] Figure 15 The lower part of the diagram illustrates the process flow related to the delivery reservation operation S120 performed by user 20a of Company A using user terminal 300a.

[0147] First, in S121, user 20a, who is logged into the goods management system 1 on user terminal 300a, opens the delivery reservation screen 400 and enters delivery reservation information such as the target item to be delivered, the transfer destination entity, the destination location, and the expected delivery date. In S122, user terminal 300a transmits the entered delivery reservation information to management server 200.

[0148] In S123, the transfer processing unit 233 of the management server 200 registers the received delivery appointment by adding the delivery appointment information received from the user terminal 300a in S122 to the delivery appointment table 360. The transfer processing unit 233 sets the status of the newly registered delivery appointment (the value of status 365 in the delivery appointment table 360) to 'appointment'.

[0149] <1-4-3. Delivery>

[0150] Figure 16 The upper part of the diagram illustrates the process flow related to delivery operation S130, in which user 20a of company A transports item 30a (item A) as the delivery target item to location 10b (the work site of company B) to transfer item 30a to company B.

[0151] First, in S131, when user 20a carrying tag reader 100a arrives at location 10b, tag reader 100a reads the tag ID from the item tag 50a of item 30a that has been moved to location 10b. Next, in S132, tag reader 100a reads the tag ID from the location tag 40b installed at location 10b. When the scheduled communication with management server 200 arrives, in S133, tag reader 100a transmits read result data indicating the results of tag readings performed up to that point to management server 200. Tag processing unit 231 of management server 200 adds the read result data received from tag reader 100a in S133 to read result table 350.

[0152] In S135, the tag reader 100b, carried by user 20b in location 10b, reads the tag ID from the item tag 50a of item 30a. Next, in S136, the tag reader 100b reads the tag ID from the location tag 40b installed in location 10b. When the scheduled communication with management server 200 arrives, in S137, the tag reader 100b transmits read result data indicating the results of the tag reads performed up to that point to management server 200. The tag processing unit 231 of management server 200 adds the read result data received from tag reader 100b in S137 to read result table 350.

[0153] The transfer processing unit 233 of the management server 200 periodically reads delivery appointment information from the delivery appointment table 360 ​​and checks whether it has delivery appointments whose status needs to be updated. When the check timer arrives, in S180, the transfer processing unit 233 performs delivery status update processing and updates the entity to which item 30a belongs (the value of organization 314 in item table 310) based on the read result data received in S133 and S137. Here, the entity to which item 30a belongs is updated from entity E1 (company A) to entity E2 (company B). A detailed example of the delivery status update process in S180 will be described later.

[0154] <1-4-4. Information Inquiry>

[0155] Figure 16 The lower part of the diagram illustrates the processing flow related to the information query operation S140 performed by user 20a of company A using user terminal 300a.

[0156] First, in S141, user 20a, who has logged into the item management system 1 on user terminal 300a, invokes information provision screen 800. In S142, user terminal 300a requests management server 200 to provide item-related information that allows user 20a access. In S143, since user 20a is associated with entity E1 in user table 340, information provision unit 234 of management server 200 obtains item-related information for one or more items 30 belonging to entity E1 from item DB 220. Then, in S144, information provision unit 234 transmits the obtained item-related information to user terminal 300a. In S145, user terminal 300a causes information provision screen 800 to display the item-related information received from management server 200.

[0157] <1-4-5. Obtaining the Appointment>

[0158] Figure 17 The upper part of the diagram illustrates the processing flow related to the pick-up reservation operation S150 performed by user 20b of Company B using user terminal 300b.

[0159] First, in S151, user 20b, who has logged into the item management system 1 on user terminal 300b, calls the collection reservation screen 500 and enters collection reservation information such as the target item to be collected, the destination entity (collector), and the expected collection date. In S152, user terminal 300b transmits the entered collection reservation information to management server 200.

[0160] In S153, the transfer processing unit 233 of the management server 200 registers the received collection reservation by adding the collection reservation information received from the user terminal 300b in S152 to the collection reservation table 370. The transfer processing unit 233 sets the status of the newly registered collection reservation (the value of status 375 in the collection reservation table 370) to 'reservation'.

[0161] <1-4-6. Claim>

[0162] Figure 17 The middle part of the diagram illustrates the process flow related to the collection operation S160, in which a user 20a of company A visits location 10b (the workplace of company B) to collect item 30a (item A) as the target item and thereby transfers item 30a from company B to company A.

[0163] First, in S161, when user 20a carrying tag reader 100a arrives at location 10b, tag reader 100a reads the tag ID from the item tag 50a of item 30a stored in location 10b. Next, in S162, tag reader 100a reads the tag ID from the location tag 40b installed in location 10b. When the scheduled communication with management server 200 arrives, in S163, tag reader 100a transmits read result data indicating the results of tag readings performed up to that point to management server 200. Tag processing unit 231 of management server 200 adds the read result data received from tag reader 100a in S163 to read result table 350.

[0164] The transfer processing unit 233 periodically reads collection reservation information from the collection reservation table 370 and checks whether there are collection reservations whose status needs to be updated. When the check timer arrives, in S190, the transfer processing unit 233 performs collection status update processing and updates the entity to which item 30a belongs (the value of organization 314 in item table 310) based on the read result data received in S163. Here, the entity to which item 30a belongs is updated from entity E2 (company B) to entity E1 (company A). A detailed example of the collection status update process in S190 will be described later.

[0165] Figure 17 The lower part of the diagram illustrates the process flow related to the inventory management operation S170 performed when user 20a of Company A brings the received item 30a (item A) back to the warehouse.

[0166] First, in S171, the tag reader 100a, carried by user 20a, reads the tag ID from the item tag 50a of the item 30a that has been returned to location 10a. Next, in S172, the tag reader 100a reads the tag ID from the location tag 40a installed in location 10a. When the timed communication with management server 200 arrives, in S173, the tag reader 100a transmits the read result data indicating the results of the tag reads performed up to that point to management server 200.

[0167] The tag processing unit 231 of the management server 200 adds the reading result data received from the tag reader 100a in S173 to the reading result table 350 and calls the location management unit 232. In S174, the location management unit 232 updates the storage location and location coordinates of item 30a (the values ​​of storage location 315 and coordinates 316 of item table 310) based on the reading result data added to the reading result table 350.

[0168] <1-4-7. Delivery Status Update Process (First Practical Example)>

[0169] Figure 18 This is a flowchart illustrating an example of the delivery status update process according to a first practical example of the first embodiment. As described above, in the first practical example, the appropriate execution of the delivery operation is confirmed based on the tag reading results of the tag readers of both the source entity and the destination entity.

[0170] First, in S181, the transfer processing unit 233 reads incomplete delivery reservation records from the delivery reservation table 360. It should be noted that only records indicating dates prior to the current day as expected delivery dates are eligible for reading by the transfer processing unit 233. Next, in S182, the transfer processing unit 233 identifies the target delivery item, the source entity, the destination, and the destination entity from the read records and the master data of the item DB 220.

[0171] Then, in S183, the transfer processing unit 233 refers to the read result table 350 to determine whether the tag reader 100 of the transfer source entity has read the tag ID of the item tag of the target item and the tag ID of the location tag installed at the destination location. Furthermore, in S184, the transfer processing unit 233 refers to the read result table 350 to determine whether the tag reader 100 of the transfer destination entity has read the tag ID of the item tag of the target item and the tag ID of the location tag installed at the destination location.

[0172] If at least one of the determination conditions in S183 and S184 is not met (the determination result is "No"), the subsequent processing steps from S185 to S187 are skipped. If both determination conditions are met (the determination result is "Yes"), in S185, the transfer processing unit 233 changes the status of the delivery reservation record read in S181 to 'Completed'. Then, in S186, the transfer processing unit 233 changes the value of the organization 314 of the target item record in the item table 310 to a value indicating the transfer destination entity.

[0173] Then, in S187, the location management unit 232 updates the storage location 315 and coordinates 316 of the target item record in the item table 310 to the corresponding latest values.

[0174] Then, in S188, the transfer processing unit 233 determines whether the delivery reservation table 360 ​​still has another unfinished delivery reservation record to be processed next. If there is still a next delivery reservation record, then the processing returns to S181, and the next delivery reservation record is also processed in S181 to S187 as described above. When there is no next delivery reservation record remaining, Figure 18The delivery status update process is completed, and the transfer processing unit 233 is put into standby until the next processing timer.

[0175] <1-4-8. Delivery Status Update Processing (Second Practical Example)>

[0176] Figure 19 This is a flowchart illustrating an example of the delivery status update process according to a second practical example of the first embodiment. As described above, in the second practical example, the appropriate execution of the delivery operation is confirmed based on the result of tag reading by the tag reader under the management of the destination entity.

[0177] and Figure 18 The difference in the flowcharts is that Figure 19 The flowchart does not include the condition determination in S183. The transfer processing unit 233 reads the delivery reservation record from the delivery reservation table 360 ​​and identifies the target item and other necessary information. Then, in S184, the transfer processing unit 233 obtains the tag reading result of the tag reader 100 of the destination entity from the reading result table 350. When it is determined that the tag reader 100 of the destination entity has read the tag ID of the item tag of the target item and the tag ID of the location tag installed at the destination location, in S185, the transfer processing unit 233 changes the status of the delivery reservation record to 'complete'. Figure 19 China's utilization and Figure 18 The reference symbols in the same reference symbol represent the details of the processing steps that can be combined with the reference symbols. Figure 18 The descriptions are the same, so they will not be described in this article.

[0178] <1-4-9. Handling of Claim Status Updates>

[0179] Figure 20 This is a flowchart illustrating an example of the process for updating the collection status according to the first embodiment. As described above, in this embodiment, upon collection, the appropriate execution of the collection operation is confirmed based on the tag reading result of the tag reader under the management of the transfer destination entity.

[0180] First, in S191, the transfer processing unit 233 reads incomplete collection reservation records from the collection reservation table 370. It should be noted that only records indicating dates prior to the current day as expected collection dates are eligible for reading by the transfer processing unit 233. Next, in S192, the transfer processing unit 233 identifies the target item for collection, the target item's current storage location (collection location), and the transfer destination entity (collector) from the read records and the master data of the item DB 220.

[0181] Next, in S193, the transfer processing unit 233 refers to the read result table 350 to determine whether the tag reader 100 of the transfer destination entity has read the tag ID of the item tag of the target item and the tag ID of the location tag installed in the current storage location.

[0182] If the determination condition in S193 is not met (the determination result is "No"), the subsequent processing steps from S195 to S196 are skipped. If the determination condition is met (the determination result is "Yes"), in S195, the transfer processing unit 233 changes the status of the pick-up reservation record read in S191 to "Completed". Then, in S196, the transfer processing unit 233 changes the value of the organization 314 of the target item record in the item table 310 to a value indicating the transfer destination entity.

[0183] Then, in S198, the transfer processing unit 233 determines whether the collection reservation form 370 still has another incomplete collection reservation record to be processed next. If there is still a next collection reservation record, then the processing returns to S191, and the next collection reservation record is also processed in S191 to S196 as described above. When there is no next collection reservation record remaining, Figure 20 The status update process is completed, and the transfer processing unit 233 is in standby mode until the next processing timer.

[0184] <1-5. Overview>

[0185] According to the first embodiment, the item management system for managing changes (i.e., transfers) in the entity to which an item belongs integrates a first wireless device installed at a first location, a second wireless device that moves with the item, and a reading device that reads identification information from the wireless device. The first location is located in a place associated with a first entity, and the second location is located in a place associated with a second entity. When an item belonging to the second entity is delivered to the first location, the reading device associated with the first entity has read the following information:

[0186] • Identification information of the first wireless device (e.g., tag ID of the location tag); and

[0187] • The identification information of the second wireless device (e.g., the tag ID of the item tag) is used by the management unit of the item management system to update the entity to which the item belongs in the item data from the second entity to the first entity.

[0188] When an item belonging to the first entity is retrieved at the first location and thereby transferred to the second entity, the following information is read by the reading device associated with the second entity:

[0189] • Identification information of the first wireless device (e.g., tag ID of the location tag); and

[0190] • The identification information of the second wireless device (e.g., the tag ID of the item tag). The management unit of the item management system updates the entity to which the item belongs in the item data from the first entity to the second entity. Here, the reading device associated with the second entity is a reading device associated with the second entity through data in the database.

[0191] With this configuration, users involved in transferring items only need to carry the corresponding reading device, which allows for appropriate and efficient updating of the entity to which the item belongs in the item data based on the results of reading information from the wireless device.

[0192] <2. Second Embodiment>

[0193] In the first embodiment described above, a separate tag reader 100 is prepared for at least each entity, and a reader ID is assigned to the tag reading result. This allows determination of which entity a user participating in the operation belongs to based on the tag reading result. In the second embodiment described in this section, it is assumed that the determination of which entity a user participating in the operation belongs to is based on the tag reading result from the user's carried tag, rather than the reader ID used to identify the tag reader 100. This facilitates the sharing of the tag reader 100 among users and among entities.

[0194] <2-1. System Overview>

[0195] Figure 21 This is a schematic diagram illustrating an example configuration of the item management system 2 according to the second embodiment. Unlike the item management system 1, in the item management system 2, each user 20 carries a user tag 60 with embedded specific identification information (tag ID) 61, and the tag reader 100 also reads the tag ID 61 from the user tag 60. For example, user 20a carries a user tag 60a storing tag ID 61a. User 20b carries a user tag 60b storing tag ID 61b. Furthermore, the item management system 2 includes a management server 1200 instead of the management server 200 according to the first embodiment.

[0196] User tag 60 is a wireless device carried by user 20 in the item management system 2. When user 20 is a member of a company entity, user tag 60 can be embedded in an employee ID card.

[0197] In this embodiment, it is assumed that user tag 60 is a passive RFID tag, such as location tag 40 and item tag 50. It should be noted that in another embodiment, user tag 60 may be a wireless device (IC card) compliant with the Near Field Communication (NFC) protocol, while location tag 40 and item tag 50 are RFID tags. In this case, it is assumed that tag reader 100 supports both RFID and NFC protocols. Generally, each of location tag 40, item tag 50, and user tag 60 can be any kind of wireless device capable of transmitting its internal identification information in response to signals from the reader.

[0198] Like the management server 200 according to the first embodiment, the management server 1200 is a server device that manages item data that indicates which of two or more entities each item 30 belongs to.

[0199] <2-2. Configuration Example of Management Server>

[0200] <2-2-1. Basic Configuration>

[0201] Figure 22 This is a block diagram illustrating an example configuration of the management server 1200 according to the second embodiment. (See reference) Figure 22 The management server 1200 includes a communication unit 210, an item database 1220, and an item management unit 1230.

[0202] Similar to the item DB 220 according to the first embodiment, the item DB 1220 consists of tables used to manage data on which entity each item under the management of the instruction system belongs to. In this embodiment, the item DB 1220 includes an item table 310, a location table 320, a user table 340, a user tag table 1345, a read result table 1350, a delivery reservation table 360, and a pickup reservation table 370. The item DB 1220 does not need to include a reader table 330.

[0203] Figure 23 An example configuration of the user tag table 1345 according to this embodiment is illustrated. The user tag table 1345 has three data elements, including a tag ID 1346, a name 1347, and an organization 1348. The tag ID 1346 uniquely identifies each user tag 60. The value of the tag ID 1346 is the same as the value of the tag ID stored within the corresponding user tag 60. The name 1347 represents the name of each user tag 60. The organization 1348 represents the entity responsible for managing each user tag 60 (e.g., the company to which the user 20 carrying the user tag 60 belongs). Figure 23In the example, 'Company A' has administrative responsibility for user tag 60 (e.g., user tag 60a) identified by tag ID 'TG91', while 'Company B' has administrative responsibility for user tag 60 (e.g., user tag 60b) identified by tag ID 'TG92'.

[0204] Like the item management unit 230 according to the first embodiment, the item management unit 1230 is a set of software modules that provide item management functions for managing data within the item DB 1220. In this embodiment, the item management unit 1230 includes a tag processing unit 1231, a location management unit 232, a transfer processing unit 1233, and an information providing unit 234.

[0205] exist Figure 24 On the left side, it is illustrated that in this embodiment, a user 20a carrying a tag reader 100a accesses a location 10a managed by entity E1 to perform an inventory operation. When user tag 60a enters the reading range of tag reader 100a, tag reader 100a reads the tag ID 'TG91' of user tag 60a. Furthermore, when location tag 40a enters the reading range, tag reader 100a reads the tag ID 'TG11' of location tag 40a. Additionally, when item tag 50a of item 30a enters the reading range, tag reader 100a reads the tag ID 'TG01' of item tag 50a. When the transmission timer for the reading result data arrives, tag reader 100a transmits the reading result data (including three records) indicating the tag reading results to management server 1200. Tag processing unit 1231 adds the three records of the reading result data received via communication unit 210 to reading result table 1350.

[0206] like Figure 24 As shown on the right, in this embodiment, the read result table 1350 has six data elements, including record number 351, read time 352, tag ID 353, reader ID 354, coordinates 355, and organization 1356. In this embodiment, reader ID 354 can be omitted from the read result table 1350. When read result data is added to the read result table 1350, the value of organization 1356 can be empty. For example, the tag processing unit 1231 determines that the read time of record #1 of user tag 60a in the read result data is almost different from the read times of records #2 and #3 of location tag 40a and item tag 50a. Therefore, the tag processing unit 1231 updates the value of organization 1356 of the read result records of location tag 40a and item tag 50a to indicate the value of the entity associated with user tag 60a in user tag table 1345. Figure 24In the example, based on the temporal correlation between the read result records, the organization name 'Company A' associated with tag ID 'TG91' in user tag table 1345 is added to the organization 1356 column of read result records #2 and #3.

[0207] It should be noted that when multiple users 20 are working in the same location 10, multiple read result records for user tags 60 of different users 20 can be created for one read result record of item tag 50 (or location tag 40) (referred to herein as the target record). In this case, for example, tag processing unit 1231 can determine the entity to be added to the column of organization 1356 of the target record based on the read result record of the user tag 60 most frequently detected during a certain interval (e.g., a few seconds to tens of seconds) of the read time including the target record.

[0208] In this way, by employing a configuration for determining the relationship between tag reading results and entities based on the results of readings from user tag 60 (using its temporal correlation), the need to pre-associate reader IDs with entities is eliminated. Therefore, in, for example... Figure 24 In the scenario shown on the left, user 20a is not required to use tag reader 100a, and any tag reader 100 can be used to perform inventory operations. This reduces the burden on the item management system 2 in managing tag readers 100.

[0209] <2-2-2. Transfer of Items (Change of Entity to Which an Item Belongs)>

[0210] Similarly, in this embodiment, the transfer processing unit 1233 receives advance reservation information indicating that the operation of transferring item 30 will be performed for both delivery and pickup. Then, the transfer processing unit 1233 changes the entity to which item 30 belongs in item DB 1220 based on the reading results of at least one tag reader 100 and the received reservation information. This can be used in conjunction with the method used in the first embodiment. Figure 6 and 11 The same method is used to receive delivery and pickup appointments.

[0211] (1) Transfer of goods by delivery

[0212] For ease of explanation, it is also assumed here that a target item (e.g., item 30a) belonging to a second entity (e.g., company A) associated with the second location is transferred to a first entity (e.g., company B) associated with the first location. Before the delivery operation is performed, item table 310 indicates that the target item belongs to the second entity. From this state, if the first reading device has read at least the following three tag IDs, the transfer processing unit 1233 updates item table 310 so that it indicates that the target item belongs to the first entity:

[0213] a) The tag ID of the user tag associated with the first entity;

[0214] b) The tag ID of the position label of the first location; and

[0215] c) The tag ID of the target item's item tag.

[0216] In the example where user 20a delivers item 30a to location 10b to transfer it to user 20b: a) the user tag associated with the first entity corresponds to user tag 60b of user 20b; b) the location tag of the first location corresponds to location tag 40b; and c) the item tag of the target item corresponds to item tag 50a of item 30a. These conditions imply that the tag reading result indicates the target item has been properly transferred to the user on the first entity's side at the location associated with the first entity.

[0217] The above conditions for changing the entity to which the target item belongs may additionally include that the first reading device has read the following tag ID.

[0218] d) The tag ID of the user tag associated with the second entity.

[0219] In the example above where user 20a delivers item 30a to location 10b to transfer it to user 20b, d) the user tag associated with the second entity corresponds to user tag 60a of user 20a. This extended condition means that the tag reading result indicates that, with both users of the first and second entities present, it is confirmed that the target item has been transferred to the user on the first entity's side at the location associated with the first entity.

[0220] Figure 25 This is an explanatory diagram used to explain tag reading during the delivery operation in this embodiment. Figure 25 In the example, the target item for delivery is item 30a, which belongs to entity E1 and has been stored in location 10a. User 20a transports item 30a to location 10b on the expected delivery date. User 20b receives item 30a at location 10b. For example, tag reader 100b reads the tag ID of user tag 60b, the tag ID of location tag 40b, and the tag ID of item tag 50a, and transmits the read result data to management server 1200. The tag processing unit 1231 of management server 1200 stores the read result data in read result table 1350 and adds the value indicating entity E2 associated with user tag 60b to the column of the stored record organization 1356.

[0221] Figure 26 It is used to explain based on usage Figure 25 An explanatory graph showing the updated delivery status of the results of the tag reading description. Figure 26 The read results table 1350 has an indication Figure 25 The example shows three records #4, #5, and #6 of the tag reading results from tag reader 100b. For instance, transfer processing unit 1233 refers to delivery reservation table 360 ​​and knows that item 30a, identified by item ID 'IT01', is expected to be delivered on the expected delivery date 'YMD2' to location 10b identified by destination 'PL02'. This delivery arrangement indicates that item 30a will be transferred from entity E1 (company A) to which item 30a currently belongs, to entity E2 (company B). Transfer processing unit 1233 knows from records #5 and #6 of the reading results table 1350 that tag reader 100b, which has read the tag ID of user tag 60b, has read the tag ID of location tag 40b of location 10b and the tag ID of item tag 50a of item 30a. Based on the reading results, transfer processing unit 1233 determines that the expected delivery operation has been performed and updates the value of status 365 of the corresponding reservation information record #2 in delivery reservation table 360 ​​to 'complete'. Furthermore, the transfer processing unit 1233 updates the organization 314 value of the record for item 30a in the item table 310 to 'Company B'. The location management unit 232 updates the storage location 315 and coordinate 316 values ​​of the record for item 30a in the item table 310 to the latest values.

[0222] It should be noted that, although Figure 25 and 26 The illustration shows an example of tag reader 100b reading tag IDs from RFID tags 60b, 40b, and 50a, but tag reader 100a can read tag IDs from all three RFID tags. Furthermore, if the tag ID of user tag 60a of user 20a is also read (as described in the extended condition above), the transfer processing unit 1233 can change the entity to which item 30a belongs. In this case, the tag reading result confirms that the delivery operation was performed with the users of both the source and destination entities present. Therefore, the entity to which the target item belongs can be changed while reliably preventing the parties involved in the transfer from missing each other.

[0223] Similar to the first embodiment, the transfer processing unit 1233 changes the entity to which the target item belongs not only based on the tag reading result but also based on the delivery reservation information indicating that the operation of moving the target item to the destination will be performed. Therefore, also in this embodiment, if the tag ID of the item during transportation is unintentionally read at a location other than the destination or if the item is taken to an inappropriate location by a third party, the situation where the entity to which the item belongs can be prevented from being incorrectly changed.

[0224] (2) By receiving the transferred items

[0225] For ease of explanation, it is also assumed here that a target item (e.g., item 30a) belonging to a first entity (e.g., company B) associated with a first location is transferred to a second entity (e.g., company A) associated with a second location via a retrieval operation. Before the retrieval operation is performed, item list 310 indicates that the target item belongs to the first entity. From this state, if the second reading device associated with the second entity has read the tag ID of the location tag of the first location and the tag ID of the item tag of the target item, the transfer processing unit 1233 changes the entity to which the target item belongs to the second entity. In this embodiment, the state of the second reading device being associated with the second entity means that the second reading device has read the tag ID of the user tag associated with the second entity. In the example where user 20a, as the person in charge of company A, retrieves item 30a stored in location 10b, the tag reader 100a or 100b that has read the tag ID of user tag 60a of user 20a corresponds to the second reading device. The location tag of the first location corresponds to location tag 40b, and the item tag of the target item corresponds to item tag 50a. The above conditions mean that the tag reading result indicates that the person in charge of the legitimate recipient has visited the appropriate location to collect the target item.

[0226] Figure 27 This is an explanatory diagram used to explain the tag reading during the retrieval operation in this embodiment. Figure 27 In the example, the target item to be retrieved is item 30a, which belongs to entity E2 and is stored in location 10b. User 20a visits location 10b on the expected retrieval date and retrieves item 30a. For example, when user 20a remains in location 10b, tag reader 100b reads the tag ID of user tag 60a, the tag ID of location tag 40b, and the tag ID of item tag 50a, and transmits the read result data to management server 1200. The tag processing unit 1231 of management server 1200 stores the read result data in read result table 1350 and adds the value indicating the entity E1 associated with user tag 60a to the column of the stored record organization 1356.

[0227] Figure 28 It is used to explain based on usage Figure 27 The diagram illustrates the update of the claim status of the results read from the described tag. Figure 28 The read results table 1350 has an indication Figure 27In the example, records #7, #8, and #9 show the tag reading results from tag reader 100b at location 10b. For instance, transfer processing unit 1233 refers to collection reservation form 370 and knows that item 30a, identified by item ID 'IT01', is expected to be collected by the person in charge of entity E1 (which is company A) on the expected collection date 'YMD4'. This collection arrangement indicates that item 30a will be transferred from entity E2 (company B) to entity E1 (company A), where item 30a currently belongs. Transfer processing unit 1233 knows from records #8 and #9 of the reading result table 1350 that tag reader 100b, which has read the tag ID of user tag 60a, has read the tag ID of location tag 40b and the tag ID of item tag 50a. Based on this reading result, transfer processing unit 1233 determines that the expected collection operation has been performed and updates the value of status 375 of record #2 of the corresponding reservation information in collection reservation form 370 to 'complete'. Furthermore, the transfer processing unit 1233 updates the value of the organization 314 of the record of item 30a in the item table 310 to 'Company A', which is the name of entity E1.

[0228] According to such an embodiment, the entity to which the target item belongs can be changed after the appropriate execution of the user's retrieval operation associated with the transfer destination entity is confirmed from the tag reading results.

[0229] Similar to the first embodiment, the transfer processing unit 1233 changes the entity to which the target item belongs not only based on the tag reading result but also based on the pick-up reservation information instructing the person in charge of the pick-up to perform the operation of picking up the target item from the current storage location. Therefore, if the item is improperly transferred to an illegitimate third party carrying the user tag 60, the situation where the entity to which the item belongs can be changed accordingly can be prevented.

[0230] It should be noted that, in both delivery and collection cases, the transfer processing unit 1233 according to this embodiment can also determine the correspondence between tag IDs read from two or more tags based on the time correlation between the reading results received from the same tag reader 100.

[0231] <2-3. Processing Flow>

[0232] In this section, we will use Figure 29 and 30 The flowchart in this embodiment describes an example of the processing flow in the item management system 2.

[0233] <2-3-1. Delivery Status Update Processing>

[0234] Figure 29 This is a flowchart illustrating an example of the delivery status update process according to the second embodiment.

[0235] First, in S281, the transfer processing unit 1233 reads incomplete delivery reservation records from the delivery reservation table 360. It should be noted that only records indicating dates prior to the current day as expected delivery dates are eligible for reading by the transfer processing unit 1233. Next, in S282, the transfer processing unit 1233 identifies the target delivery item, the source entity, the destination, and the destination entity from the read records and the master data of the item DB 1220.

[0236] Then, in S283, the transfer processing unit 1233 refers to the read result table 1350 to determine whether any tag reader 100 has read the tag ID of a user tag associated with the transfer destination entity. For example, when the read result table 1350 has a record with the value of organization 1356 indicating a transfer destination entity, it is determined that the tag ID of the user tag associated with the transfer destination entity has been read, and the process proceeds to S284. If no such record exists, the process proceeds to S288.

[0237] In S284, the transfer processing unit 1233 further determines whether the same tag reader 100 (the tag reader 100 that has read the tag ID of the user tag associated with the transfer destination entity) has read the tag ID of the item tag of the target item and the tag ID of the location tag of the destination. When it is determined that the tag reader 100 has read the tag ID of the item tag of the target item and the tag ID of the location tag of the destination, the process proceeds to S285. If these tag IDs have not yet been read, the process proceeds to S288.

[0238] In S285, the transfer processing unit 1233 changes the status of the delivery reservation record read in S281 to 'complete'. Then, in S286, the transfer processing unit 1233 changes the value of the organization 314 of the target item record in the item table 310 to a value indicating the transfer destination entity.

[0239] Then, in S287, the location management unit 232 updates the storage location 315 and coordinates 316 of the target item record in the item table 310 to the corresponding latest values.

[0240] Then, in S288, the transfer processing unit 1233 determines whether the delivery reservation table 360 ​​still has another unfinished delivery reservation record to be processed next. If there is still a next delivery reservation record, then the processing returns to S281, and the next delivery reservation record is also processed in S281 to S287 as described above. When there is no next delivery reservation record remaining, Figure 29 The delivery status update process is complete, and the processing unit 1233 is put into standby mode until the next processing timer.

[0241] <2-3-2. Handling of Claim Status Updates>

[0242] Figure 30 This is a flowchart illustrating an example of the process for updating the claim status according to the second embodiment.

[0243] First, in S291, the transfer processing unit 1233 reads incomplete collection reservation records from the collection reservation table 370. It should be noted that only records indicating dates prior to the current day as expected collection dates are eligible for reading by the transfer processing unit 1233. Next, in S292, the transfer processing unit 1233 identifies the target item for collection, the target item's current storage location (collection location), and the transfer destination entity (collector) from the read records and the master data of the item DB 1220.

[0244] Then, in S293, the transfer processing unit 1233 refers to the read result table 1350 to determine whether any tag reader 100 has read the tag ID of a user tag associated with the transfer destination entity. For example, when the read result table 1350 has a record with the value of organization 1356 indicating a transfer destination entity, it is determined that the tag ID of the user tag associated with the transfer destination entity has been read, and the process proceeds to S294. When no such record exists, the process proceeds to S298.

[0245] In S294, the transfer processing unit 1233 further determines whether the same tag reader 100 (the tag reader 100 that has read the tag ID of the user tag associated with the transfer destination entity) has read the tag ID of the item tag of the target item and the tag ID of the location tag of the storage location. When it is determined that the tag reader 100 has read the tag ID of the item tag of the target item and the tag ID of the location tag of the storage location, the process proceeds to S295. If these tag IDs have not yet been read, the process proceeds to S298.

[0246] In S295, the transfer processing unit 1233 changes the status of the pick-up reservation record read in S291 to 'complete'. Then, in S296, the transfer processing unit 1233 changes the value of the organization 314 of the target item record in the item table 310 to a value indicating the transfer destination entity.

[0247] Then, in S298, the transfer processing unit 1233 determines whether the collection reservation form 370 still has another incomplete collection reservation record to be processed next. If there is still a next collection reservation record, then the processing returns to S291, and the next collection reservation record is also processed in S291 to S296 as described above. When there is no next collection reservation record remaining, Figure 30 The status update process is complete, and the transfer processing unit 1233 is put into standby until the next processing timer.

[0248] <2-4. Overview>

[0249] According to the second embodiment, the item management system for managing changes (i.e., transfers) in the entity to which an item belongs integrates a first wireless device installed at a first location, a second wireless device that moves with the item, and a reading device that reads identification information from the wireless device. The first location is located in a place associated with a first entity, and the second location is located in a place associated with a second entity. When an item belonging to the second entity is delivered to the first location, the reading device reads the following information:

[0250] • Identification information of the user equipment associated with the first entity (e.g., the tag ID of the user tag);

[0251] • Identification information of the first wireless device (e.g., tag ID of the location tag); and

[0252] • The identification information of the second wireless device (e.g., the tag ID of the item tag) is used by the management unit of the item management system to update the entity to which the item belongs in the item data from the second entity to the first entity.

[0253] When an item belonging to the first entity is retrieved at the first location and thereby transferred to the second entity, the following information is read by the reading device:

[0254] • Identification information of the user equipment associated with the second entity (e.g., the tag ID of the user tag);

[0255] • Identification information of the first wireless device (e.g., tag ID of the location tag); and

[0256] • Identification information of the second wireless device (e.g., tag ID of the item tag). The management unit of the item management system updates the entity to which the item belongs in the item data from the first entity to the second entity.

[0257] Using this configuration, the entity to which the user belongs is determined based on the tag reading results from the user's device. Therefore, any reading device (e.g., a device not designed for a specific entity) can be used for tag reading. This reduces the burden of managing reading devices and makes item management more efficient.

[0258] <3. Modified Example>

[0259] The features of the first and second embodiments described above can be combined with each other in any way. Moreover, the modification examples described below can be combined with the features above.

[0260] <3-1. Control of Tag Reading Range>

[0261] In the modified example, each tag reader 100 can be configured to shorten its reading range in response to a user action. As an example, the normal (unshortened) reading range is within a radius of several meters (e.g., 5m) around the antenna 115 of the tag reader 100, and the shortened reading range can be within a radius of one meter or less (e.g., 1m) around the antenna 115. The management server 200 can change the entity to which the item in the item DB 220 belongs based on reading result data indicating the reading results obtained by the tag reader 100 in a state where its reading range is shortened in response to a user action.

[0262] Figure 31 This is a block diagram illustrating an example configuration of a label reader 100 based on this modified example. (Reference) Figure 31 The tag reader 100 includes a control unit 151, a storage unit 102, a communication unit 103, a positioning unit 104, a power supply 105, a reading unit 156, an operation detection unit 171, and a notification unit 172.

[0263] The control unit 151 comprises a memory storing a computer program and one or more processors executing the computer program. Similar to the control unit 101 according to the above embodiment, the control unit 151 controls the overall function of the tag reader 100.

[0264] Reading unit 156 is a reading module capable of reading the identification information stored in each RFID tag present in the system. (And...) Figure 2 The difference between the reading unit 106 shown is that the reading unit 156 includes an RF controller 160. The RF controller 160 causes the power amplifier 111 to output a transmission signal with a power that can be variably set according to the control unit 151 to the filter 112. The RF controller 160 demodulates the signal input from the RX terminal to obtain the tag ID and other information sent back from the RFID tag, and outputs the obtained information to the control unit 151.

[0265] The operation detection unit 171 detects, for example, the operation status (pressed / not pressed) of a button (not shown) provided on the main body of the tag reader 100, and outputs a detection signal indicating the detected operation status to the control unit 151.

[0266] When the detection signal indicator button from the operation detection unit 171 is not pressed, the control unit 151 sets the power of the transmission signal transmitted from the reading unit 156 to a normal value, thereby adjusting the reading range of the tag reader 100 to a normal range. Conversely, when the detection signal indicator button from the operation detection unit 171 is pressed, the control unit 151 sets the power of the transmission signal transmitted from the reading unit 156 to a lower value, thereby adjusting the reading range of the tag reader 100 to a shorter range.

[0267] When the result read by the tag of the reading unit 156 is stored in the storage unit 102 or transmitted to the management server 200, the control unit 151 adds a flag indicating the operation state of the button during reading to the reading result data. This flag serves to identify whether each reading result record represents a reading result under the normal reading range or a reading result under a shortened reading range.

[0268] The notification unit 172 is a device for notifying the user that the tag reader 100 is performing a tag reading operation. The notification unit 172 may include, for example, a light-emitting diode (LED) that emits light under the control of the control unit 151. In this case, the control unit 151 may cause the notification unit 172 to emit light in different light emission modes (e.g., emission color, flashing frequency, flashing period, etc.) during periods when tag reading is attempted with a normal reading range and during periods when tag reading is attempted with a shortened reading range. Furthermore, upon detecting a received signal from an RFID tag, the control unit 151 may cause the notification unit 172 to emit light in a specific light emission mode. It should be noted that the notification unit 172 may include another notification device, such as a speaker or vibrator, instead of the LED (or as an addition thereto).

[0269] Figure 32 This is a block diagram illustrating an example configuration of management server 200 based on this modified example. (Reference) Figure 32 The management server 200 includes a communication unit 210, an item database 270, and an item management unit 280. The item database 270 has a read result table 390 to replace... Figure 3 The read result table 350 of item DB 220 shown is shown. Item management unit 280 has a transfer processing unit 283 to replace... Figure 3 The item management unit 230 shown is a transfer processing unit 233.

[0270] In this modification example, the transfer processing unit 283 changes the entity to which the item in the item DB 270 belongs based on the read result data obtained when the read range is shortened in response to a user operation. Other functions of the transfer processing unit 283 may be similar to those of the transfer processing unit 233 according to the first embodiment or the transfer processing unit 1233 according to the second embodiment.

[0271] Figure 33 This is an explanatory diagram used to explain the change in the entity to which the item belongs in this example. In this article, as an example, it is assumed that the following is executed: Figure 7 The delivery operation is described. The target item for delivery is item 30a belonging to entity E1. User 20a delivers item 30a to location 10b, and user 20b receives item 30a at location 10b. Tag reader 100a, carried by user 20a, reads the tag ID of location tag 40b. When user 20a presses the button on tag reader 100a, tag reader 100a reads the tag ID of item tag 50a of item 30a. Note that tag reader 100a reads the tag ID of item tag 50a of item 30a even when the button is not pressed.

[0272] Figure 33 The upper part of the diagram shows the read results table 390 of the management server 200, which stores records #1, #2, and #3, indicating the results of reading such tags. Besides... Figure 5 In addition to the five data elements in the read result table 350 shown, the read result table 390 also has a range shortening 391 as an additional data element. The value of range shortening 391 in record #1 is 'No', meaning that the read range of tag reader 100a was not shortened when reading the tag ID 'TG01' of item tag 50a indicated by this record. The value of range shortening 391 in record #2 is 'No', meaning that the read range of tag reader 100a was not shortened when reading the tag ID 'TG21' of location tag 40a indicated by this record. The value of range shortening 391 in record #3 is 'Yes', meaning that the read range of tag reader 100a was shortened when reading the tag ID 'TG01' of item tag 50a indicated by this record.

[0273] Similarly, the tag reader 100b carried by user 20b also reads the tag ID of location tag 40b. When user 20b presses the button on tag reader 100b, tag reader 100b reads the tag ID of item tag 50a of item 30a. Note that tag reader 100b reads the tag ID of item tag 50a of item 30a even when the button is not pressed. Figure 33The read results table 390 also stores records #4, #5 and #6 indicating the results of reading such tags.

[0274] For example, transfer processing unit 283 refers to delivery reservation form 360 and knows that item 30a is expected to be delivered to location 10b on the expected delivery date 'YMD2', thus transferring from entity E1 to entity E2. Transfer processing unit 283 ignores records #1 and #6 of read result table 390, which indicate the results of reading from item tag 50a under normal reading range, and determines that the expected delivery operation has been performed based on the contents of records #2 to #5. Then, transfer processing unit 283 updates the value of status 365 of record #2 corresponding to the reservation information in delivery reservation form 360 to 'complete'. Moreover, transfer processing unit 283 updates the value of organization 314 of the record for item 30a in item table 310 to 'company B', which is the name of entity E2.

[0275] Based on this example change, in situations where a large number of items are stored in a single location, the number of candidates for transferring a target item can be reduced based on explicit user actions, and the entity to which the target item belongs can then be updated efficiently. It should be noted that in the example above, shortening the reading range when reading from location tag 40 (range shortening 391 indicates 'yes') is not required to determine a transfer. This is because typically only one location tag 40 is installed in each location, so location tag 40 is not always present in a very close range to the user during a delivery or pickup operation. However, in another example, shortening the reading range when reading from location tag 40 (pressing a button) can also be required to determine a transfer.

[0276] For updates to data other than changes to the entity to which an item belongs (e.g., updates to location information by location management unit 232), item management unit 280 can utilize all read result records, regardless of whether the read range is shortened. This balances the need for simple management where item-related information under management is kept up-to-date solely through user-carried tag reader 100, and where item transfers between entities are triggered by explicit operations for data maintenance measures.

[0277] <3-2. Other Change Examples>

[0278] When it is determined that an operation for transferring items has been performed based on the above conditions, the management server 200 or 1200 may request user approval for the transfer and may change the entity to which the items belong after receiving approval. Transfer approval can be requested and granted via the user interface of any user-operated device (such as tag reader 100 or user terminal 300). Transfer approval can be requested from one or both the user of the source entity and the user of the destination entity.

[0279] In the above embodiments, the item-related information maintained by the database can be used not only to provide information to users, but also for various other purposes. For example, management server 200 or 1200 can provide item-related information to another system such as an accounting system, a business form system, or an item procurement planning system.

[0280] <4. Other embodiments>

[0281] The above embodiments can be implemented by supplying a program for implementing one or more functions to a system or device via a network or storage medium, and causing one or more processors in the computer of the system or device to read and execute the program. They can also be implemented by circuitry (e.g., an ASIC) for implementing one or more functions.

[0282] This invention is not limited to the above embodiments, and various changes and modifications can be made within the spirit and scope of this invention. Therefore, the appended claims are attached to inform the public of the scope of this invention.

[0283] This application claims priority to Japanese Patent Application No. 2021-061655, filed on March 31, 2021, which is hereby incorporated herein by reference in its entirety.

Claims

1. An item management system for managing item data, wherein the item data indicates the entity to which an item belongs among multiple entities, the item management system comprising: A first wireless device, wherein the first wireless device is installed at a first location; A second wireless device, which moves together with the item; At least one reading device, the at least one reading device reading identification information stored in a wireless device; as well as Management unit, configured to manage the item data; Wherein, when the item data indicates that the item belongs to a second entity associated with a second location different from the first location, the management unit is configured to update the item data such that the item data indicates that the item belongs to the first entity associated with the first location if the first reading device associated with the first entity has read the identification information of the first wireless device and the identification information of the second wireless device, wherein the entity is one of the owner of the item, the user of the item, and the manager of the item.

2. The item management system according to claim 1, wherein, When the item data indicates that the item belongs to the second entity, the management unit is configured to, If the second reading device associated with the second entity has read the identification information of the first wireless device and the identification information of the second wireless device, and the first reading device associated with the first entity has read the identification information of the first wireless device and the identification information of the second wireless device, Then update the item data so that the item data indicates that the item belongs to the first entity.

3. The item management system according to claim 1, wherein the first reading device is a reading device that has read the identification information of the first user equipment associated with the first entity.

4. The item management system of claim 1, wherein each reading device is configured to shorten the reading range in response to a user operation, and The management unit is configured to change the entity to which the item belongs in the item data based on the reading result obtained when the reading range is shortened in response to the user operation.

5. The item management system according to claim 1, wherein the management unit is configured as follows: Receive reservation information indicating that an operation to transfer the item between entities will be performed, and The entity to which the item belongs in the item data is changed based on the results of reading performed by at least the first reading device and the received reservation information.

6. The item management system of claim 5, wherein the management unit is configured to update the item data based on the result of a reading performed by at least the first reading device and based on reservation information indicating that an operation to move the item to the first location will be performed, such that the item data indicates that the item belongs to the first entity.

7. The item management system of claim 1, wherein each reading device is configured to transmit a reading result to the management unit, the reading result including identification information read from a wireless device and the reading time, and The management unit is configured to determine the correspondence between multiple pieces of identification information read from two or more wireless devices based on the temporal correlation between the reading results received from the same reading device.

8. The item management system of claim 1, wherein the management unit is configured to provide information related to items belonging to that entity to the user terminal of the user associated with each entity based on the item data.

9. The item management system according to claim 8, wherein the information provided to the user terminal includes the location information of each item.

10. The item management system of claim 1, wherein the wireless device is a radio frequency identification (RFID) tag, and The reading device is configured to emit electromagnetic waves into the reading range and read identification information sent back from the radio frequency identification (RFID) tag using the energy of the electromagnetic waves.

11. The item management system according to claim 1, comprising: A server device, deployed in a cloud environment, includes the management unit. Each reading device includes a communication unit configured to transmit the reading result directly or indirectly via another device to the server device.

12. An item management method for managing item data, wherein the item data indicates the entity to which an item belongs among a plurality of entities, the method comprising, in a state where the item data indicates that the item belongs to a second entity associated with a second location: The first reading device reads identification information from the first wireless device, which is installed at the first location. The first reading device reads identification information from the second wireless device, which has been moved to the first location along with the item. The first reading device transmits reading result data to the management unit, which is configured to manage the item data. The reading result data indicates that the first reading device associated with the first entity has read the identification information of the first wireless device and the identification information of the second wireless device. as well as The management unit updates the item data based on the reading result data received from the first reading device, such that the item data indicates that the item belongs to the first entity associated with the first location, wherein the entity is one of the item's owner, the item's user, and the item's manager.

13. An information processing apparatus for managing item data, wherein the item data indicates the entity to which an item belongs among a plurality of entities, the information processing apparatus comprising: A communication unit configured to communicate with at least one reading device capable of reading identification information stored in each wireless device from a first wireless device and from a second wireless device, wherein the first wireless device is installed at a first location among a plurality of locations, and the second wireless device moves with the item. as well as A management unit is configured to, if the communication unit has received read result data, update the item data such that the item data indicates the item belongs to a first entity associated with the first location when the item data indicates that the item belongs to a second entity associated with a second location different from the first location. The read result data indicates that a first reading device associated with the first entity has read the identification information of the first wireless device and the identification information of the second wireless device, wherein the entity is one of the item owner, the item user, and the item manager.

14. An item management system for managing item data, wherein the item data indicates the entity to which an item belongs among a plurality of entities, the item management system comprising: A first wireless device, wherein the first wireless device is installed at a first location; A second wireless device, which moves together with the item; At least one reading device, the at least one reading device reading identification information stored in a wireless device; as well as Management unit, configured to manage the item data; Wherein, when the item data indicates that the item belongs to a first entity associated with the first location, the management unit is configured to update the item data such that, if a second reading device associated with a second entity has read the identification information of the first wireless device and the identification information of the second wireless device, the item data indicates that the item belongs to the second entity. The second reading device associated with the second entity includes at least one of the following: There is data that associates the second reading device with the second entity, or The second reading device has read the identification information of the user device associated with the second entity, wherein the entity is one of the owner of the item, the user of the item, and the manager of the item.

15. The item management system of claim 14, wherein each reading device is configured to shorten the reading range in response to a user operation, and The management unit is configured to change the entity to which the item belongs in the item data based on the reading result obtained when the reading range is shortened in response to the user operation.

16. The item management system according to claim 14, wherein the management unit is configured to: Receive reservation information indicating that an operation to transfer the item between entities will be performed, and The entity to which the item belongs in the item data is changed based on the results of reading performed by at least the second reading device and the received reservation information.

17. The item management system of claim 16, wherein the management unit is configured to update the item data based on the result of a reading performed by at least the second reading device and based on the operation of retrieving the item from the first location, such that the item data indicates that the item belongs to the second entity.

18. The item management system of claim 14, wherein each reading device is configured to transmit a reading result to the management unit, the reading result including identification information read from a wireless device and the reading time, and The management unit is configured to determine the correspondence between multiple pieces of identification information read from two or more wireless devices based on the temporal correlation between the reading results received from the same reading device.

19. The item management system of claim 14, wherein the management unit is configured to provide information related to items belonging to that entity to the user terminal of the user associated with each entity based on the item data.

20. The item management system of claim 19, wherein the information provided to the user terminal includes the location information of each item.

21. The item management system of claim 14, wherein the wireless device is a radio frequency identification (RFID) tag, and The reading device is configured to emit electromagnetic waves into the reading range and read identification information sent back from the radio frequency identification (RFID) tag using the energy of the electromagnetic waves.

22. The item management system according to claim 14, comprising: A server device, deployed in a cloud environment, includes the management unit. Each reading device includes a communication unit configured to transmit the reading result directly or indirectly via another device to the server device.

23. An item management method for managing item data, wherein the item data indicates the entity to which an item belongs among a plurality of entities, the method comprising, in a state where the item data indicates that the item belongs to a first entity associated with a first location: The identification information is read from the first wireless device by a second reading device, which is associated with a second entity, and the first wireless device is installed at the first location. The second reading device reads identification information from the second wireless device, which moves with the item. The second reading device transmits reading result data to the management unit, which is configured to manage the item data. The reading result data indicates that the second reading device has read the identification information of the first wireless device and the identification information of the second wireless device. as well as The management unit updates the item data based on the reading result data received from the second reading device, so that the item data indicates that the item belongs to the second entity. The second reading device associated with the second entity includes at least one of the following: There is data that associates the second reading device with the second entity, or The second reading device has read the identification information of the user device associated with the second entity, wherein the entity is one of the owner of the item, the user of the item, and the manager of the item.

24. An information processing apparatus for managing item data, wherein the item data indicates the entity to which an item belongs among a plurality of entities, the information processing apparatus comprising: A communication unit configured to communicate with at least one reading device capable of reading identification information stored in each wireless device from a first wireless device and from a second wireless device, wherein the first wireless device is installed at a first location among a plurality of locations, and the second wireless device moves with the item. as well as A management unit is configured to, when the item data indicates that the item belongs to a first entity associated with the first location, update the item data such that, if the communication unit has received read result data, the item data indicates that the item belongs to a second entity, and the read result data indicates that a second reading device associated with the second entity has read the identification information of the first wireless device and the identification information of the second wireless device. The second reading device associated with the second entity includes at least one of the following: There is data that associates the second reading device with the second entity, or The second reading device has read the identification information of the user device associated with the second entity, wherein the entity is one of the owner of the item, the user of the item, and the manager of the item.

Images