JP7837151B2 - RF reader housing - Google Patents

Description

This disclosure relates to an RF reader housing device.

In the field of inventory management, technologies are being sought to accurately read information about managed products and to efficiently utilize that information.

For example, a technology is known in which RFID readers are mounted on vests worn by employees to acquire product information without interfering with the employees' work (see Patent Document 1 below). Furthermore, a technology is known in which an RF reader worn by a user is activated based on a predetermined trigger event (see Patent Document 2 below).

Patent No. 5992616 Patent No. 5702772

However, conventional technology makes it difficult to achieve both optimal RF reader performance and improved ease of use for the user. For example, fully utilizing the RF reader's capabilities requires the user to wear relatively large equipment, such as an RFID antenna array, which could compromise user comfort and work efficiency.

Therefore, this disclosure proposes an RF reader housing device that can achieve both the full performance of the RF reader and improved ease of use for the user.

To solve the above problems, one embodiment of an RF reader storage device according to this disclosure comprises: a storage section for storing an RF reader capable of communicating with an RF (Radio Frequency) tag; a first support section connected to one end of the storage section and capable of being slung over the shoulder from the front of the person wearing the storage section; and a second support section connected to the other end of the storage section and extending to the rear side through both sides of the person. When the storage section is worn by the person, the first and second support sections support the one end and the other end symmetrically with respect to the front of the person, thereby maintaining the orientation of the stored RF reader substantially constant with respect to the RF tag.

This is a schematic block diagram showing the flow of processing performed by the parking management system according to the embodiment. Figure (1) shows the structure of a portable unit according to an embodiment. Figure (2) shows the structure of the portable unit according to the embodiment. Figure (3) shows the structure of the portable unit according to the embodiment. Figure (4) shows the structure of the portable unit according to the embodiment. Figure (5) shows the structure of the portable unit according to the embodiment. Figure (6) shows the structure of the portable unit according to the embodiment. This is a side view showing the structure of a portable unit according to an embodiment. This is a plan view showing the structure of a portable unit according to an embodiment. This figure shows an example configuration of a parking management system according to the embodiment. This figure shows an example configuration of a communication terminal and management device according to the embodiment. This figure shows an example of a location information storage unit according to the embodiment. This figure shows an example of a vehicle information storage unit according to the embodiment. This figure shows an example of a parking area storage unit according to an embodiment. This figure shows an example of a parking position memory unit according to the embodiment. Figure (1) shows a user interface according to the embodiment. Figure (2) shows a user interface according to the embodiment. Figure (1) shows the screen display process according to the embodiment. Figure (2) shows the screen display process according to the embodiment. This is a flowchart (1) showing the information processing procedure according to the embodiment. This is a flowchart (2) showing the information processing procedure according to the embodiment. This block diagram schematically shows the processing flow performed by the modified parking management system. This flowchart shows the procedure for processing information related to modification. This is a hardware configuration diagram showing an example of a computer that implements the functions of an information processing device.

The embodiments of this disclosure will be described in detail below with reference to the drawings. In the following embodiments, the same parts are denoted by the same reference numerals, and redundant descriptions will be omitted.

(1. Embodiments)
[1-1. An example of a parking management system according to the embodiment]
Figure 1 is a schematic block diagram showing the flow of processing performed by the parking management system 1 according to the embodiment. As shown in Figure 1, the parking management system 1 includes an information processing device (hereinafter referred to as "portable unit 10") stored in an outfit worn by the driver 30 of the vehicle 60 (in this embodiment, a backpack-like outfit with a storage compartment in front of the body), an RF (Radio Frequency) tag 50 mounted on the vehicle 60, and a management device 100.

The portable unit 10 includes a beacon button 11, an RF reader 12, and a communication terminal 20. The beacon button 11 is a device that emits a predetermined beacon signal. The RF reader 12 is a device for reading information from the RF tag 50. The RF reader 12 and the RF tag 50 constitute a wireless communication system, commonly known as RFID (Radio Frequency Identification), which uses radio waves to read and write data non-contactually at short distances of a few centimeters to a few meters. The communication terminal 20 is a device that receives beacon signals emitted from the beacon button 11, acquires location information using GPS (Global Positioning System), and transmits the acquired location information to the management device 100. The communication terminal 20 is, for example, a smartphone or tablet.

The RF tag 50 is an electronic recording tag mounted on the vehicle 60. The RF tag 50 contains identification information for the RF tag 50 (hereinafter referred to as "tag ID"), as well as vehicle ID (identification information for uniquely identifying the vehicle), vehicle type and shipment information, and various information assigned during manufacturing (hereinafter referred to as "vehicle information"). Furthermore, the RF tag 50 can store and record new or updated information, for example, via a communication terminal 20.

The management device 100 is a server for managing the parking positions of the vehicles 60. The management device 100 manages various information (hereinafter referred to as "parking area information") such as the vehicle information of each vehicle 60, the size, location, and name of the parking area where the vehicles 60 are parked, and the number of vehicles that can be accommodated.

Generally, vehicles such as automobiles awaiting shipment are parked in a vast, multi-area parking system, and their movement across these areas is complex, depending on the timing and destination of shipment. Therefore, vehicle managers need to properly manage which vehicle is parked where. For example, drivers moving vehicles must accurately identify the vehicle they are moving, record its parking location before and after the move, and accurately communicate this information to the manager. Furthermore, managers must accurately record the information provided by drivers. This places a significant burden on both vehicle managers and drivers.

Therefore, the parking management system 1 according to this embodiment improves the convenience of parking management and reduces the burden on vehicle managers and drivers by executing the process shown in Figure 1. The following describes the flow of processing performed by the parking management system 1 when a driver 30 moves a vehicle 60 before shipment to a predetermined parking area, using Figure 1 as an example.

First, the driver 30, intending to move vehicle 60 to a designated parking area, puts on the portable unit 10 and heads towards the vehicle 60's current parking position. As described above, vehicle 60 is equipped with an RF tag 50. For example, the RF tag 50 records information such as pre-move information 44A, which links the tag ID (in other words, vehicle 60) to the parking position. In Figure 1, the pre-move information 44A shows an example where the current parking position is stored as the specific parking area name "Location," but the parking position may also be stored as location information such as latitude and longitude obtained by GPS. The driver 30 gets into vehicle 60 and moves vehicle 60 to the next parking position (step S1).

After completing the move, the driver 30 presses the beacon button 11 inside the vehicle 60. Upon receiving the beacon signal emitted by the beacon button 11, the communication terminal 20 issues a read command to the RF reader 12. The RF reader 12, receiving the instruction from the communication terminal 20, begins reading the information from the RF tag 50. The communication terminal 20 reads the information from the RF tag 50 and, triggered by the driver 30's action (in this example, pressing the beacon button 11), acquires location information corresponding to the vehicle 60's parking position after its movement (step S2). Note that the driver 30 may press the beacon button 11 not only inside the vehicle, but also at a close proximity outside the vehicle 60, as long as the RF reader 12 is within a distance where it can read the information from the RF tag 50.

The communication terminal 20 reads the information from the RF tag 50 when the driver 30 presses the beacon button 11, and estimates the location information acquired at this time as the parking location of the vehicle 60.

The communication terminal 20 then transmits location information (latitude, longitude, etc.) of the parked location to the management device 100 and obtains the name of the parking area corresponding to the location information (in the example in Figure 1, "Yard 1") from the management device 100. The communication terminal 20 displays the obtained parking area name (location) on its screen. Once the driver 30 confirms that the displayed location is indeed the location they moved to, they operate the communication terminal 20 to confirm the parking position on its screen. Upon receiving this operation, the communication terminal 20 confirms the parking position of the vehicle 60 after its movement and stores post-movement information 44B linked to vehicle information, tag ID, date and time of completion of the move, etc.

Once the parking position after the vehicle's relocation is determined, the communication terminal 20 transmits the vehicle's relocation information 44B to the management device 100 and requests registration of the information (step S3). The management device 100 registers and stores the received relocation information 44B (step S4).

Subsequently, when an opportunity arises to move vehicle 60 again, operator 40 can search for the current location of vehicle 60 by entering search criteria (step S5). For example, operator 40 searches for vehicle 60 using one of the following as a search query: vehicle ID, tag ID, or date and time of movement. The search results are displayed, for example, on a map displayed on display 150, with the location information of vehicle 60 plotted.

As described above, the parking management system 1 achieves a parking management process that is burdenless for both the administrator and the driver 30 through the cooperation of the portable unit 10, the RF tag 50, and the management device 100. Specifically, after the driver 30 moves the vehicle 60, the portable unit 10 detects the driver 30's first action (pressing the beacon button 11 in the example of Figure 1) and acquires the vehicle information and vehicle 60's location information held in the RF tag 50. Furthermore, upon acquiring the vehicle information, the portable unit 10 determines the acquired location information to be the parking location of the vehicle 60, links the vehicle information and the parking location, and transmits it to the management device 100. The management device 100 stores the transmitted vehicle information and parking location, linking them with the vehicle 60's parking area information (yard 1 in the example of Figure 1), and displays the vehicle's parking location within the parking area on a map based on the stored information.

Thus, with the parking management system 1, the driver 30 does not need to go through the trouble of recording detailed information about the vehicle 60 before and after moving it. Instead, a simple operation, such as pressing the beacon button 11, triggers the recording, transmission, and registration of the vehicle 60's parking location. Furthermore, the parking management system 1 can achieve the above processing simply by mounting the RF tag 50 on the vehicle 60, eliminating the need for large-scale equipment investments such as installing communication equipment in the parking lot, thus reducing the burden on administrators.

Furthermore, the portable unit 10 is designed like a backpack, with the storage compartment positioned in front of the body. This design does not interfere with the driver's (30) work, thus reducing the workload of the driver (30) operating the vehicle (60). The structure of the portable unit 10 will be described in detail below with reference to Figures 2A to 4.

Figure 2A is a diagram (1) showing the structure of the portable unit 10 according to the embodiment. As shown in Figure 2A, the portable unit 10 has a storage compartment 16 in front of the driver's body 30 and a support part that supports the storage compartment 16. The support part includes a first support part 17 that supports the storage compartment 16 from above and a second support part 18 that supports the storage compartment 16 from the side of the driver's body 30. The portable unit 10 also has connecting parts 19 that connect the storage compartment 16 to the first support part 17 and the second support part 18, respectively.

The support section has a belt-like configuration. Specifically, the first support section 17 consists of two belts, each connected via a connecting section 19 at two different points on one end (upper part) of the storage section 16. Similarly, the second support section 18 also consists of two belts, each connected via a connecting section 19 at two different points on the other end (lower part) of the storage section 16.

The support section is constructed from a non-stretchable material, preventing stretching and other damage, thus achieving higher durability and a comfortable, long-lasting fit. The first support section 17 and the second support section 18 may also have adjustment sections to adjust the belt length. This allows the driver 30 to wear the portable unit 10 regardless of their physical characteristics, and because the support section does not constrict the body, it can be worn comfortably.

Furthermore, the support portion may be in the form of a retractable belt. For example, the support portion may be a rubber belt. Even with such specifications, the driver 30 can wear the portable unit 10 regardless of their physical characteristics, and since the support portion does not constrict the body, it can be worn comfortably.

Furthermore, the support section can be configured to combine the advantages of both stretchable and non-stretchable materials by using stretchable material for only a portion of the material. For example, by using partially stretchable material in areas that come into contact with the body or near the connection point 19, the wearability for the driver 30 can be improved.

The storage compartment 16 houses the beacon button 11. For example, the beacon button 11 is stored in the lower front position (near the driver's abdomen) where it is easily accessible to the driver 30 while they are wearing the device. This allows the driver 30 to easily press the beacon button 11 without being interrupted while driving. In the example shown in Figure 2A, the beacon button 11 is stored inside, but the beacon button 11 may also be exposed on the outside of the storage compartment.

Furthermore, although not shown in Figure 2A, the storage unit 16 houses the RF reader 12 and the communication terminal 20. As described above, when the storage unit 16 is attached to the driver 30, one end and the other end are supported symmetrically with respect to the front of the driver 30 by the first support part 17 and the second support part 18, thereby maintaining a substantially constant orientation of the stored RF reader 12. In other words, according to the structure of the portable unit 10, the RF reader 12 maintains a vertical orientation while attached to the driver 30, so that it can reliably face the RF tag 50 mounted on the vehicle. Specifically, the portable unit 10 can maintain the orientation of the RF reader 12's antenna in the optimal orientation for receiving radio waves emitted from the RF tag 50. As a result, the RF reader 12 can improve the accuracy and speed of reading information from the RF tag 50. This is because, when the RF tag 50 emits radio waves vertically, positioning the RF reader 12 vertically to face it directly improves reading accuracy and speed. The orientation in which the RF reader 12 is housed can be flexibly changed according to the orientation of the RF tag 50 mounted on the vehicle 60. For example, if the RF tag 50 is mounted horizontally to the vehicle, the RF reader 12 may be housed horizontally in the storage unit 16. That is, since the storage unit 16 is supported by the first support unit 17 and the second support unit 18, the orientation of the RF reader 12 can be kept approximately constant when the storage unit 16 is attached to the driver 30. Therefore, the RF reader 12 may be housed in the storage unit 16 facing the orientation in which the RF tag 50 is mounted.

Next, the structure of the portable unit 10 as viewed from the side of the driver 30 will be described using Figure 2B. Figure 2B is a diagram (2) showing the structure of the portable unit 10 according to this embodiment.

As shown in Figure 2B, the storage section 16 of the portable unit 10 is connected at one end to a first support section 17 via a connecting section 19. The upper end of the storage section 16 is supported when the first support section 17 is slung over the driver's shoulder from the front. Furthermore, the other end (lower end) of the storage section 16, different from the end supported by the first support section 17, is connected to a second support section 18 via a connecting section 19. The lower end of the storage section 16 is supported when the second support section 18 is supported from the driver's side to the rear. This structure allows the portable unit 10 to maintain a stable position without hindering the driver's movement during operation.

Next, the structure of the portable unit 10 as viewed from the rear of the driver 30 will be described using Figures 2C to 2F. Any of the examples shown in Figures 2C to 2F may be used for the structure of the support portion on the rear of the driver 30.

Figure 2C is a diagram (3) showing the structure of the portable unit 10 according to the embodiment. Figure 2C shows an example of how the first support portion 17 and the second support portion 18 are connected on the back of the driver 30. As shown in Figure 2C, in this example of connection between the first support portion 17 and the second support portion 18, the first support portion 17 and the second support portion 18 are connected in a Y-shape on the back of the driver 30. Specifically, the first support portion 17 consists of two belts, each connected from the front of the driver 30 through the upper shoulders to the rear connecting portion 17A, and the connected belts are then connected to the second support portion 18 to the rear connecting portion 18A.

Next, another example will be described using Figure 2D. Figure 2D is a diagram (4) showing the structure of the portable unit 10 according to the embodiment. In the example shown in Figure 2D, the first support portion 17, which extends from the shoulders to the waist of the driver 30, is connected to the second support portion 18 via a connecting portion 17B. That is, the first support portion 17 consists of two belts, each extending from the front side of the driver 30 through the upper shoulders to the back side, and each belt is connected to the second support portion 18.

Next, another example will be described using Figure 2E. Figure 2E is a diagram (5) showing the structure of the portable unit 10 according to the embodiment. In the example shown in Figure 2E, two belts, which constitute the first support portion 17, extend from the upper shoulders, back, and sides of the driver 30 to the front of the driver 30, respectively. The two belts of the first support portion 17 are connected to other belts at the connecting portion 17C on the back of the driver 30. In the example of Figure 2E, the first support portion 17 may also serve as the second support portion 18 connected to the other end on the front of the driver 30. That is, in the example of Figure 2E, the first support portion 17 and the second support portion 18 may be composed of one common belt, or they may be composed of two belts connected at the connecting portion 17C. As shown in Figure 2E, the first support portion 17, the second support portion 18, and the connecting portion 17C are shown in an H shape on the back of the driver 30. Thus, in the example shown in Figure 2E, the first support section 17 has two belts that extend from the front side of the driver 30, through the upper shoulders, back side, and side side, and the two belts are connected at the rear side by another belt at the connecting section 17C. The second support section 18 can also be considered an extended version of the first support section 17.

Next, another example will be explained using Figure 2F. Figure 2F is a diagram (6) showing the structure of the portable unit 10 according to the embodiment. In the example shown in Figure 2F, the two belts of the first support portion 17 cross over the upper shoulders of the driver 30 on the rear side, and then connect to the second support portion 18 at the connecting portion 17D. As shown in Figure 2F, the two belts of the first support portion 17 are shown in an X shape on the rear side of the driver 30. Thus, in the example of Figure 2F, each of the two belts of the first support portion 17 extends from the front side of the driver 30 through the upper shoulders to the rear side, and the two belts cross over on the rear side before connecting to the second support portion 18 on the rear side.

Next, the cross-sectional structure of the portable unit 10 will be described. Figure 3 is a side view showing the structure of the portable unit 10 according to the embodiment. As shown in Figure 3, the portable unit 10 houses the beacon button 11 in the front lower part (on the driver's abdomen), which is in a position easily accessible to the driver 30 when the wearer is wearing the device. Furthermore, the portable unit 10 houses the RF reader 12 on the front side of the body (the side furthest from the driver's body as seen by the driver 30) and the communication terminal 20 on the back side (the side closer to the driver's body as seen by the driver 30) when the wearer is wearing the device.

A sponge-shaped spacer 13 is installed between the communication terminal 20 and the RF reader 12. The spacer 13 reduces radio wave interference between the communication terminal 20 and the RF reader 12, improving the reading accuracy and reading distance of the RF reader 12.

Furthermore, a transparent window 14 is installed on the body-facing side of the communication terminal 20. By storing the communication terminal 20 in this state, the proximity sensor of the communication terminal 20, which detects its proximity to the driver's body 30, is activated, allowing the driver 30 to turn off the screen of the communication terminal 20 without being aware of it. This reduces battery consumption for the communication terminal 20.

Furthermore, the portable unit 10 may be configured without a transparent window 14, instead providing a spacer in that location to prevent contact between the communication terminal 20 and the driver 30. This is because, if a device emitting radio waves, such as a communication terminal, is in continuous contact with the human body, there is a concern about the absorption of radio waves by the human body; therefore, this configuration aims to suppress the effects of radio waves on the human body. For example, the specifications of the spacer, such as its material and thickness, may be determined based on the regulations of the country in which the portable unit 10 according to this embodiment is used. As an example, the spacer is designed with a thickness that provides a 15 mm gap between the communication terminal 20 and the driver 30. Note that such specifications may vary depending on the radio wave intensity emitted by the communication terminal 20, the distance between the communication terminal 20 and the base station with which it communicates, etc.

Next, the planar structure of the portable unit 10 will be described. Figure 4 is a plan view showing the structure of the portable unit 10 according to the embodiment. As shown in Figure 4, the portable unit 10 houses the beacon button 11 and RF reader 12 on the outside (the side furthest from the driver's body) when the wearable device is attached to the front of the driver's body by the driver 30. The pocket in which the beacon button 11 and RF reader 12 are stored can be opened and closed, for example, with a zipper. By storing the beacon button 11 and RF reader 12 on the outside of the driver's body by the driver 30, the operability of the beacon button 11 and the reading accuracy of the RF reader 12 are improved.

Furthermore, the area where the beacon button 11 is housed may be made of a transparent material such as vinyl or a translucent material such as mesh fabric. This allows the driver 30 to visually locate and press the beacon button 11 even when it is housed, thus improving operability.

Furthermore, the portable unit 10 stores the communication terminal 20 on the driver's side when the driver 30 is wearing the device on the front of their body. The bottom of the pocket where the communication terminal 20 is stored has a transparent window 14, which improves the visibility of the communication terminal 20's screen and contributes to reducing the communication terminal 20's battery consumption. Note that, as described above, the portable unit 10 may also be configured with a spacer instead of the transparent window 14.

Furthermore, the portable unit 10 has two connection points 19 at each of its upper and lower ends. The connection points 19 are connected to either the first support point 17 or the second support point 18, and support the storage section 16 when the driver 30 wears the portable unit 10.

Thus, the structure of the portable unit 10 allows the driver 30 to operate the device hands-free while driving, without hindering their work. Furthermore, the structure of the portable unit 10, supported by the first support section 17 and the second support section 18 in front of the driver 30's body, improves the reading accuracy of the RF reader 12 even with the driver 30's movements, preventing malfunctions such as reading the RF tag of a vehicle parked next to the vehicle 60 being moved. Moreover, since the portable unit 10 integrates the beacon button 11, RF reader 12, and communication terminal 20, the driver 30 can quickly and easily attach or detach the entire device. Additionally, because the portable unit 10 has a smaller contact area with the body than vest-shaped clothing, it improves the driver 30's comfort, for example, when working outdoors in extreme heat.

The above describes the overview of the processes performed by the parking management system 1 and the structure of the portable unit 10. Below, the elements and functions constituting the parking management system 1 will be described in detail using Figures 5 and following.

[1-2. Configuration of the parking management system according to the embodiment]
The configuration of the parking management system 1 that performs information processing according to the embodiment will be described. Figure 5 is a diagram showing an example of the configuration of the parking management system 1 according to the embodiment. Figure 5 shows an example of the device configuration for realizing the processing concept of the parking management system 1 shown in Figure 1.

As shown in Figure 5, the parking management system 1 includes a portable unit 10, an RF tag 50, and a management device 100. These various devices are connected via a network N (e.g., the Internet or short-range wireless communication) via wired or wireless communication. Note that the number of devices included in the parking management system 1 shown in Figure 5 is not limited to those illustrated. For example, the parking management system 1 may include multiple portable units 10 and RF tags 50. Furthermore, since the devices shown in Figure 5 are conceptual, the management device 100, for example, may be configured by linking multiple devices.

The portable unit 10 is an information processing device carried by the driver 30. In this embodiment, the portable unit 10 includes a beacon button 11, an RF reader 12, and a communication terminal 20. The beacon button 11 is a device that emits a wireless signal (beacon signal) based on a predetermined standard (such as Bluetooth®). The RF reader 12 is a device that reads information from the RF tag 50 via wireless communication. The communication terminal 20 is, for example, a smartphone, a tablet, or a wearable device.

The RF tag 50 is an information medium that uses radio waves to read and write data to its built-in memory non-contactually, based on a predetermined short-range wireless communication standard. The RF tag 50 can take various forms, such as card type, button type, or wristband type.

The management device 100 is a server that manages the parking positions of the vehicles 60. Based on information transmitted from the portable unit 10, the management device 100 stores vehicle information and parking positions of the vehicles 60. The management device 100 also stores vehicle-related information, such as which RF tag 50 is installed on which vehicle 60. Furthermore, the management device 100 stores information related to the parking area. For example, the management device 100 stores information such as the size and location of the parking area, the number of vehicles that can be accommodated, the current number of parked vehicles, and the occupancy rate. The management device 100 also displays the current parking positions of the vehicles 60 and the occupancy rates of each parking area on the display 150, according to the operator 40's instructions.

[1-3. Configuration of the Information Processing Device According to the Embodiment]
Next, the configuration of the communication terminal 20 and management device 100 that perform information processing according to the embodiment will be described. Figure 6 is a diagram showing an example of the configuration of the communication terminal 20 and management device 100 according to the embodiment.

First, let's describe the communication terminal 20. As shown in Figure 6, the communication terminal 20 has a communication unit 21, a storage unit 22, and a control unit 24. The communication terminal 20 may also have an input unit (e.g., a touch panel) for receiving various operations from the driver 30, etc., and a display unit (e.g., a liquid crystal display) for displaying various information.

The communication unit 21 is implemented, for example, by a NIC (Network Interface Card). The communication unit 21 is connected to the network N via wired or wireless connection and transmits and receives information with the beacon button 11, RF reader 12, management device 100, etc., via the network N.

The memory unit 22 is implemented using, for example, semiconductor memory elements such as RAM (Random Access Memory) or flash memory, or storage devices such as hard disks or optical discs. The memory unit 22 includes a location information storage unit 23.

Figure 7 shows an example of the information stored in the location information storage unit 23. Figure 7 is a diagram illustrating an example of the location information storage unit 23 according to this embodiment. In the example shown in Figure 7, the location information storage unit 23 includes items such as "tag ID," "vehicle information," "pre-movement location," and "parking location." Note that in the examples shown in Figures 7 to 10, the information stored in the storage units 22 and 120 is conceptually represented as "A001," but in reality, each piece of information described later is stored in the storage units 22 and 120.

The "Tag ID" is identification information for identifying the RF tag 50 installed on the vehicle 60. In this embodiment, since the RF tag 50 is installed on each vehicle 60, the Tag ID can also serve as identification information for the vehicle 60. "Vehicle Information" is various information related to the vehicle 60. For example, vehicle information includes the vehicle ID, which is identification information for uniquely identifying the vehicle, the vehicle type, shipping location, shipping destination, and various information assigned during manufacturing.

The "Pre-Movement Location" indicates the parking position before the vehicle was moved by the driver 30. The pre-movement location is, for example, information written to the RF tag 50 when the driver 30 moved the vehicle in the past. The driver 30 may also press the beacon button 11 before moving the vehicle, and the location information acquired at that time may be written to the RF tag 50. The "Parking Location" indicates the parking position after the vehicle was moved by the driver 30. The pre-movement location and parking location may be specific numerical information such as longitude and latitude, or they may be names indicating a parking area determined based on numerical information, or parking location information artificially set by the administrator within the parking area (for example, parking space 10 in parking lot 1, or any other information indicating a parking location determined independently by the administrator).

In other words, Figure 7 shows an example in which information acquired by the communication terminal 20, with the tag ID, vehicle information, pre-movement location, and parking location linked to each other, is stored in the location information storage unit 23.

Returning to Figure 6, let's continue the explanation. The control unit 24 is implemented, for example, by a CPU (Central Processing Unit), MPU (Micro Processing Unit), GPU (Graphics Processing Unit), etc., which executes a program stored inside the communication terminal 20 using RAM (Random Access Memory) or the like as the working area. Furthermore, the control unit 24 is a controller and may be implemented by an integrated circuit such as an ASIC (Application Specific Integrated Circuit) or FPGA (Field Programmable Gate Array).

As shown in Figure 6, the control unit 24 comprises an acquisition unit 25, a detection unit 26, and a transmission unit 27, and realizes or executes the information processing functions and operations described below. Note that the internal configuration of the control unit 24 is not limited to the configuration shown in Figure 6; other configurations are also acceptable as long as they perform the information processing described later.

The acquisition unit 25 acquires vehicle information and vehicle 60 location information held in the RF tag 50 upon detecting the first action performed by the driver 30. The first action is the action performed by the driver 30 to indicate that the vehicle 60 will be parked after it has been moved to its destination.

For example, as a first action, the acquisition unit 25 acquires vehicle information and vehicle 60 location information held in the RF tag 50, triggered by the transmission of a beacon signal by the driver 30 (i.e., pressing the beacon button 11). Alternatively, as a first action, the acquisition unit 25 may acquire vehicle information and vehicle 60 location information held in the RF tag 50, triggered by the detection of at least one of the following: a predetermined voice signal emitted by the driver 30, the driver 30 and vehicle 60 moving away from each other, or the driver 30 stopping the vehicle.

For example, the acquisition unit 25 may acquire the vehicle's parking position information at the time of recognition when it recognizes that the driver 30 has made a pre-set activation sound, such as "Parking complete." This allows the driver 30 to complete the process hands-free without having to perform any actions, such as pressing the beacon button 11. Alternatively, the acquisition unit 25 may acquire the vehicle's position information when it detects that the driver 30 (i.e., the communication terminal 20 or RF reader 12) and the vehicle 60 (i.e., the RF tag 50) have moved beyond a predetermined distance, using a proximity detection function in short-range wireless communication. Or, the acquisition unit 25 may acquire the vehicle's position information when it detects that the driver 30 has stopped the vehicle 60 (for example, by stopping the engine, stopping for a certain period of time, or returning the gear to the stopped position). This allows the driver 30 to complete the process without any conscious effort.

The detection unit 26 detects the location information of the vehicle 60 when the acquisition unit 25 acquires vehicle information. The acquisition unit 25 acquires the location information detected by the detection unit 26 as the location information of the vehicle 60.

For example, the detection unit 26 detects the location information of the vehicle 60 using the GPS sensor provided by the communication terminal 20. However, the detection unit 26 may detect the location information of the vehicle 60 using any means other than the GPS sensor. For example, the detection unit 26 may detect the location information of the vehicle 60 based on access information between the access point installed in the parking area and the communication terminal 20.

The transmission unit 27 determines the location information acquired by the acquisition unit 25 as the parking location of the vehicle 60, links the vehicle information with the parking location, and transmits it to the management device 100.

The transmitting unit 27, after determining that the location information acquired by the acquisition unit 25 is the parking location of the vehicle 60, may then present information about the parking area corresponding to the parking location to the driver 30 via display unit (screen) or voice notification. If the driver 30 approves the presented information, the transmitting unit 27 links the vehicle information and the parking location and transmits it to the management device 100.

For example, when the transmission unit 27 determines the parking position, it obtains the name of the parking area corresponding to that parking position from the management device 100. The transmission unit 27 then displays the obtained parking area name (shown as "Location" in the example in Figure 1) on the screen. If the driver 30 confirms that the name of the parking area to which they moved the vehicle 60 matches the one displayed on the screen, they perform an operation to approve the parking position. After this operation is performed, the transmission unit 27 links the vehicle information and the parking position and transmits it to the management device 100.

If the driver 30 does not approve the presented information, the transmission unit 27 accepts correction information from the driver 30. The transmission unit 27 then links the information entered by the driver 30 with the vehicle information and transmits it to the management device 100. In this way, the transmission unit 27 transmits only the information approved by the driver 30 to the management device 100, preventing incorrect information from being transmitted to the management device 100.

Furthermore, the transmitting unit 27 may determine the acquired location information as the parking location of the vehicle 60 if, after the acquisition unit 25 has acquired the location information, the detection unit 26 detects that the location information has not changed for a predetermined period of time. For example, even if the transmitting unit 27 acquires location information, it does not immediately transmit it, but waits for several tens of seconds and continues to detect the location information. Then, when the transmitting unit 27 detects that the location information of the parking location has not changed, that is, that parking has definitely been performed, it links the vehicle information and the parking location and transmits them to the management device 100. This prevents the transmitting unit 27 from transmitting an incorrect parking location acquired due to the beacon button 11 being pressed by mistake, etc., to the management device 100. Also, even if the transmitting unit 27 does not detect the driver 30 pressing the beacon button 11, etc., it may determine the location information acquired by the acquisition unit 25 as the parking location of the vehicle 60 after a certain period of time has elapsed. This allows the transmitter 27 to continue processing even if the driver 30 forgets to press the beacon button 11 or if the driver 30's actions cannot be detected due to some malfunction. Furthermore, when the vehicle 60 stops, the transmitter 27 may read aloud the location name to be registered at that time, and if the driver 30 does not make any changes within a certain period of time, it may determine that the location is the parking location of the vehicle 60. In this case, if the driver 30 performs an action indicating that the read-out location name is different from the actual location (for example, by long-pressing the beacon button 11), the transmitter 27 may cancel the registration of the location name or accept input of the correct location name.

Next, the management device 100 will be described. As shown in Figure 6, the management device 100 includes a communication unit 110, a storage unit 120, and a control unit 130. The management device 100 may also include an input unit (e.g., a keyboard or mouse) for receiving various operations from an administrator or other person managing the management device 100, and a display unit (e.g., a liquid crystal display) for displaying various information.

The communication unit 110 is implemented, for example, by a NIC (Non-Complex Integralizer). The communication unit 110 is connected to the network N via a wired or wireless connection and transmits and receives information with the communication terminal 20, etc., via the network N.

The storage unit 120 is implemented using, for example, semiconductor memory elements such as RAM and flash memory, or storage devices such as hard disks and optical discs. The storage unit 120 includes a vehicle information storage unit 121, a parking area storage unit 122, and a parking position storage unit 123. Each storage unit will be described in turn below.

Figure 8 shows an example of the information stored by the vehicle information storage unit 121. Figure 8 is a diagram illustrating an example of the vehicle information storage unit 121 according to this embodiment. In the example shown in Figure 8, the vehicle information storage unit 121 includes items such as "Vehicle ID," "Tag ID," "Vehicle Type," and "Shipping Destination."

The "Vehicle ID" is identification information for identifying vehicle 60. The "Tag ID" is the same information as shown in Figure 7. In this embodiment, since an RF tag 50 is installed on each vehicle 60, the Vehicle ID and Tag ID correspond one-to-one. The "Vehicle Type" is information indicating the vehicle type of vehicle 60. Note that the vehicle type may include various information such as shape and color, in addition to the vehicle type. The "Shipping Destination" is information about the location or customer to whom vehicle 60 is shipped.

In other words, Figure 8 shows an example where multiple pieces of information related to the vehicle 60, such as vehicle ID, tag ID, vehicle type, and shipping destination, are linked and stored in the vehicle information storage unit 121.

Next, Figure 9 shows an example of the information stored by the parking area storage unit 122. Figure 9 is a diagram showing an example of the parking area storage unit 122 according to this embodiment. In the example shown in Figure 9, the parking area storage unit 122 has items such as "parking area ID," "location," "name," "GPS location code," "capacity," "number of available spaces," and "occupancy rate."

The "Parking Area ID" is identification information for identifying a parking area. The "Location" is information indicating the location of the parking area. For example, the location is location information such as latitude and longitude corresponding to the parking area's position. The "Name" is, for example, the name set for the parking area by the administrator. When the name is displayed on the communication terminal 20, for example, an item name such as "Location" is used. The "GPS Location Code" is information that associates the location information identified by GPS with the parking area. For example, when the operator 40 searches for parking location or parking area information, the operator 40 may search based on the parking area's name or use the GPS location code. The "Capacity" indicates the maximum number of vehicles that can be accommodated in the parking area. The "Number of Available Spaces" indicates the current number of available parking spaces in the parking area. The "Occupancy Rate" indicates the current occupancy rate of the parking area. Note that the parking area storage unit 122 may store not only the above information, but also the area of the parking area and the number of divisions (number of parking spaces) set for parking vehicles.

In other words, Figure 9 shows an example where multiple pieces of information related to a parking area, such as parking area ID, location, name, GPS location code, capacity, number of available spaces, and occupancy rate, are linked and stored in the parking area storage unit 122.

Next, Figure 10 shows an example of the information stored by the parking position storage unit 123. Figure 10 is a diagram showing an example of the parking position storage unit 123 according to this embodiment. In the example shown in Figure 10, the parking position storage unit 123 has items such as "tag ID," "vehicle information," "parking position," "parking area ID," and "registration date and time."

The "Tag ID," "Vehicle Information," and "Parking Location" correspond to the information shown in Figure 7. The "Parking Area ID" corresponds to the information shown in Figure 9. The "Registration Date and Time" indicates the date and time when the parking location was transmitted from the communication terminal 20 after parking was completed and registered in the management device 100.

In other words, Figure 10 shows an example in which multiple pieces of information related to the movement and parking of vehicle 60, such as tag ID, vehicle information, parking location, parking area ID, and registration date and time, are linked and stored in the parking location storage unit 123. Specifically, the parking location storage unit 123 stores the vehicle information and parking location transmitted by the transmission unit 27, linked to the vehicle's parking area information. The management device 100 can obtain information such as which parking area and location vehicle 60 is in, and when it moved to that location, by referring to the parking location storage unit 123.

Returning to Figure 6, let's continue the explanation. The control unit 130 is implemented, for example, by a CPU, MPU, GPU, etc., which executes a program stored inside the management device 100 using RAM or the like as a working area. Furthermore, the control unit 130 is a controller and may be implemented by an integrated circuit such as an ASIC or FPGA.

As shown in Figure 6, the control unit 130 comprises a registration unit 131 and a display control unit 132, and implements or executes the information processing functions and operations described below. Note that the internal configuration of the control unit 130 is not limited to the configuration shown in Figure 6; other configurations are also acceptable as long as they perform the information processing described later.

The registration unit 131 registers various types of information in the storage unit 120. For example, when the vehicle 60 is delivered or manufactured, the registration unit 131 registers information about the vehicle in the vehicle information storage unit 121. Also, when the registration unit 131 acquires information about a parking area, it registers that information in the parking area storage unit 122. Furthermore, the registration unit 131 links the vehicle information and parking location transmitted by the transmission unit 27 with the vehicle's parking area information and registers it in the parking location storage unit 123.

The display control unit 132 displays the parking position of the vehicle in the parking area on a map based on the information stored in the storage unit 120. For example, the display control unit 132 retrieves the parking position of the vehicle 60, which has been retrieved based on the vehicle ID or tag ID, from the storage unit 120, and plots and displays the parking position on the map. This allows the display control unit 132 to accurately show the location of the target vehicle 60 to the driver 30, etc.

Furthermore, if the display control unit 132 has information stored in the storage unit 120 regarding the number of vehicles that can park in a parking area, or the area of the parking area, it may refer to this information. Based on this information, the display control unit 132 displays the occupancy rate on the map, indicating how many vehicles are accommodating the parking area. This allows the display control unit 132 to accurately show administrators and others the current occupancy rate of each parking area.

In this case, the display control unit 132 may display multiple parking areas with different occupancy rates in different display modes based on the current occupancy rate. For example, the display control unit 132 may display parking areas with a relatively high occupancy rate in red, parking areas with a relatively low occupancy rate in green, and parking areas with an intermediate occupancy rate in yellow. This allows the display control unit 132 to display parking areas with excellent visibility.

Furthermore, when information indicating a vehicle 60 displayed on the map is selected, the display control unit 132 may display at least one of the following near the information indicating the vehicle 60: vehicle information corresponding to the information indicating the vehicle 60, the location information of the vehicle 60, or the movement history of the vehicle 60. For example, the operator 40 operates a pointer on the display 150 to select a point indicating the vehicle 60. Based on this operation, the display control unit 132 displays the vehicle type, location information, movement history, etc., corresponding to the selected point in a pop-up window or similar manner. This allows the display control unit 132 to quickly allow the operator 40, etc., to confirm not only the current location of the vehicle 60 but also its vehicle information.

Next, using Figures 11 to 14, examples of user interfaces and screen displays used by the driver 30 and operator 40 when operating the communication terminal 20 and management device 100 are shown.

Figure 11 is a diagram (1) showing a user interface according to an embodiment. Figure 11 shows an example of a user interface displayed on a communication terminal 20 operated by the driver 30.

In the example shown in Figure 11, after the vehicle 60 has moved, when the driver 30 presses the "Read Vehicle Identification Number" display 20A, the portable unit 10 starts processing according to the embodiment. For example, if the driver 30 then presses the beacon button 11, the communication terminal 20 reads the RF tag 50 and automatically displays the vehicle ID and tag ID information on the screen. Alternatively, the driver 30 may manually input the vehicle ID, etc., before pressing the display 20A to start the processing. The driver 30 may also obtain vehicle information, etc., by reading a two-dimensional code such as a barcode attached to the vehicle.

Next, the communication terminal 20 detects the location information and displays the latitude and longitude. The communication terminal 20 may also acquire the location corresponding to the location information from the management device 100 and display it on the screen display 20B. The driver 30 confirms the location displayed on the screen, and if the confirmed information is accurate, presses the display 20D which displays "Confirm Location Registration." Alternatively, even if the driver 30 does not press display 20D, the communication terminal 20 may confirm the location information when the remaining time displayed on display 20C reaches zero.

Next, using Figure 12, an example of the operation in which the driver 30 displays the location of the vehicle 60 on the communication terminal 20 is shown. Figure 12 is a diagram (2) showing the user interface according to the embodiment.

In the example shown in Figure 12, the driver 30 desires to display the location of vehicle 60 on a map before or after moving the vehicle. In this case, the driver 30 inputs vehicle information into the communication terminal 20 by entering the vehicle ID and pressing the display button 20F, reading the vehicle's barcode, or pressing the beacon button 11. In the example shown in Figure 12, the driver 30 searches for information on vehicle 60 identified by vehicle ID "F001". The communication terminal 20 refers to the information stored in the location information storage unit 23 or the parking location storage unit 123 and outputs the information on vehicle 60 identified by vehicle ID "F001".

For example, as shown in Figure 12, the communication terminal 20 displays a map 20G and plots a point 20H on the map 20G indicating the vehicle 60. At this time, the communication terminal 20 may also display information indicating the vehicle type of the vehicle 60 near point 20H. This allows the driver 30 to confirm whether the location of the vehicle 60 they are about to move and the information about the vehicle 60 after the move are accurately stored.

Next, an example of the screen display when the operator 40 operates the management device 100 will be described. Figure 13 is a diagram (1) showing the screen display process according to the embodiment. Figure 13 shows an example of the screen displayed on the display 150 when the operator 40 searches for a vehicle 60.

The operator 40, attempting to search for vehicle 60, enters search criteria into the search window 150A. For example, the operator 40 enters a search query into the search window 150A, including the vehicle ID, the date and time the vehicle 60 was moved, the parking area, and the vehicle type, etc., to identify vehicle 60. The management device 100 displays the search results 150B based on the entered search query. Figure 13 shows an example where the management device 100 outputs vehicle IDs "F001" and "F002" as search results based on the search query. The management device 100 also plots and displays the location of the vehicle 60 corresponding to the search result on the map 150C. This allows the operator 40 to quickly see where the searched vehicle 60 is parked on the map 150C.

Next, an example of the screen display when the operator 40 investigates the parking area will be described. Figure 14 is Figure (2) showing the screen display process according to the embodiment. Figure 14 shows an example of the screen displayed on the display 150 when the operator 40 investigates the parking area.

The operator 40, who wishes to investigate the status of the parking area, enters search conditions into the search window 150E. For example, the operator 40 enters the parking area ID or GPS location code into the search window 150E. The management device 100 displays the search results 150F based on the entered search query. Figure 14 shows an example where the management device 100 outputs names such as "Yard 1" and "Yard 2" as search results based on the search query. The management device 100 also displays the location and occupancy rate of the parking areas corresponding to the search results on the map 150G. As shown in Figure 14, the management device 100 displays the location and occupancy rate of the parking areas by type. This allows the operator 40 to see at a glance on the map 150G information such as which parking areas have the most vehicles 60 parked in them.

[1-4. Information Processing Procedure According to the Embodiment]
Next, the information processing procedure according to the embodiment will be described using Figures 15 and 16. First, the processing flow executed by the portable unit 10 according to the embodiment will be described using Figure 15. Figure 15 is a flowchart (1) showing the information processing procedure according to the embodiment.

As shown in Figure 15, the communication terminal 20 determines whether or not it has received a beacon signal from the beacon button 11 (step S101). If the signal has not been received (step S101; No), the communication terminal 20 waits until it receives a signal.

On the other hand, if a signal is received (step S101; Yes), the communication terminal 20 reads the RF tag 50 via the RF reader 12 and obtains the vehicle information and vehicle 60 location information stored in the RF tag 50 (step S102). Subsequently, the communication terminal 20 determines whether the location information is accurate, that is, whether the parking location has been confirmed by the driver 30 (step S103). If the parking location is not confirmed (step S103; No), the communication terminal 20 waits until the parking location is confirmed.

On the other hand, if the parking position is confirmed (step S103; Yes), the communication terminal 20 determines the parking position, which is the position of the vehicle 60 after it has moved (step S104). Then, the communication terminal 20 links the vehicle information and tag ID used to identify the vehicle 60 with the parking position and transmits it to the management device 100 (step S105).

Next, using Figure 16, the flow of the display control processing performed by the management device 100 according to this embodiment will be explained. Figure 16 is a flowchart (2) showing the information processing procedure according to this embodiment.

As shown in Figure 16, the management device 100 determines whether or not it has received a search request from the operator 40, etc. (step S201). If no request has been received (step S201; No), the management device 100 waits until a request is received.

On the other hand, if a request is received (step S201; Yes), the management device 100 searches for vehicles 60 according to the received search conditions (step S202). The management device 100 identifies the vehicles 60 that were the target of the search (step S203) and plots and displays the identified vehicles 60 on the map (step S204).

Subsequently, the management device 100 determines whether a point on the map has been selected by the operator 40 or the like (step S205). If a point on the map is selected (step S205; Yes), the management device 100 displays detailed information about the vehicle 60 corresponding to the selected point (step S206). If no point is selected on the map (step S205; No), the management device 100 skips the process in step S206.

Subsequently, the management device 100 determines whether the operator 40 or the like has requested the display of the occupancy rate (step S207). If the display of the occupancy rate is requested (step S207; Yes), the management device 100 displays the occupancy rate of the parking area corresponding to the request (step S208). If the display of the occupancy rate is not requested (step S207; No), the management device 100 skips the process in step S208.

Subsequently, the management device 100 determines whether or not it has received a notification from the operator 40, etc., that the search process has ended (step S209). If the notification of termination of the search process is not received (step S209; No), the management device 100 continues the search process and accepts a request for new search conditions (step S201). On the other hand, if the notification of termination of the search process is received (step S209; Yes), the management device 100 terminates the search process.

Note that the information processing flow shown in Figures 15 and 16 is just one example, and the communication terminal 20 and the management device 100 may perform processing in a different order than shown in Figures 15 and 16. For example, the management device 100 may perform the processing in step S207 before step S205, or it may perform either step S205 or step S207.

(2. Modifications of the Embodiments)
[2-1. Pressing the beacon button before moving]
In the above embodiment, an example was shown in which the driver 30 presses the beacon button 11 after the vehicle 60 has moved. However, the driver 30 may press the beacon button 11 a total of two times, once before moving and once after moving. This modified example will be explained using Figure 17. Figure 17 is a schematic block diagram showing the flow of processing performed by the parking management system 1 according to the modified example.

In the example shown in Figure 17, the driver 30 wears the portable unit 10 and proceeds to the current parking position of the vehicle 60. Before starting the vehicle 60, the driver 30 presses the beacon button 11 inside the vehicle 60. Upon receiving the beacon signal emitted by the beacon button 11, the communication terminal 20 issues a read command to the RF reader 12. The RF reader 12, receiving the instruction from the communication terminal 20, begins reading the information from the RF tag 50 (step S301).

Similar to the example in Figure 1, the RF tag 50 stores the vehicle ID of the vehicle 60 and the tag ID of the RF tag 50, etc. The communication terminal 20 reads the information from the RF tag 50 and, triggered by an action by the driver 30 (in this example, pressing the beacon button 11), begins detecting location information. As a result, the communication terminal 20 obtains pre-movement information 44A, which is information linking the tag ID for identifying the RF tag 50 (in other words, the vehicle 60) with the current parking location.

After confirming on the communication terminal 20 screen that information has been acquired from the RF tag 50, the driver 30 begins moving the vehicle 60. During movement, the communication terminal 20 continues to detect and acquire location information. The driver 30 moves the vehicle 60 to the designated parking area and parks the vehicle 60.

The driver 30 presses the beacon button 11 again once parking is complete. The communication terminal 20, triggered by the driver 30 pressing the beacon button 11, reads the information from the RF tag 50 again and estimates the acquired location information as the parking position of the vehicle 60 (step S302).

Subsequently, the communication terminal 20 transmits the post-movement information 44B to the management device 100. The processes from steps S303 to S305 shown in Figure 17 are the same as those from steps S3 to S5 shown in Figure 1, therefore their explanation is omitted.

As described above, in the modified parking management system 1, the portable unit 10 detects the driver's action before moving the vehicle 60 (referred to as the "second action" for distinction; in the example in Figure 17, this corresponds to pressing the beacon button 11), acquires vehicle information held in the RF tag 50, and, upon acquiring the vehicle information, begins acquiring the vehicle 60's location information. Furthermore, upon detecting the driver's first action (the second press of the beacon button 11), the portable unit 10 determines the detected location information to be the parking location of the vehicle 60, links the vehicle information and the parking location, and transmits it to the management device 100. The management device 100 stores the transmitted vehicle information and parking location, linked to the vehicle 60's parking area information, and displays the vehicle's parking location within the parking area on a map based on the stored information.

Thus, according to the modified parking management system 1, by reading the RF tag 50 information twice—once when starting and once when parking—it is possible to prevent errors such as mistakenly reading the tag information of another vehicle (such as a vehicle parked near vehicle 60).

The function of the acquisition unit 25 in a modified example will now be explained. For example, the acquisition unit 25 acquires vehicle information held in the RF tag 50 when it detects a second action by the driver 30. The second action is an action taken by the driver 30 to indicate that the vehicle 60 is about to be moved.

For example, as a second action, the acquisition unit 25 acquires vehicle information held in the RF tag 50 when the driver 30 transmits a beacon signal (i.e., presses the beacon button 11). Alternatively, as a second action, the acquisition unit 25 may acquire vehicle information held in the RF tag 50 when it detects at least one of the following: a predetermined voice signal emitted by the driver 30, the driver 30 approaching the vehicle 60, or the driver 30 starting the vehicle.

For example, the acquisition unit 25 may acquire vehicle information when it recognizes that the driver 30 has made a pre-set activation sound, such as "I will now begin moving." Alternatively, the acquisition unit 25 may automatically recognize any voice spoken by the driver 30, even if it is not a pre-set activation sound, and accept the driver's requested operation based on the recognized voice. This allows the driver 30 to start the location information detection process hands-free, without needing to press the beacon button 11 or perform any other action. Furthermore, the acquisition unit 25 may acquire vehicle information when it detects that the driver 30 (i.e., the communication terminal 20 or RF reader 12) and the vehicle 60 (i.e., the RF tag 50) have approached within a predetermined distance, using a function that detects proximity in short-range wireless communication. Alternatively, the acquisition unit 25 may acquire vehicle information when it detects that the driver 30 has started the vehicle 60 (e.g., starting the engine, beginning to drive, changing gears, etc.). This allows the driver 30 to start the location information detection process without being consciously aware of it during the movement process.

Furthermore, the detection unit 26 in the modified configuration begins acquiring the vehicle's location information upon receiving vehicle information from the acquisition unit 25. For example, the detection unit 26 uses the GPS sensor provided by the communication terminal 20 to acquire the vehicle's location information before it moved, and continues to detect and acquire location information while it is moving.

Next, we will explain the information processing procedure related to the modified example using Figure 18. Figure 18 is a flowchart showing the information processing procedure related to the modified example.

As shown in Figure 18, the communication terminal 20 determines whether or not it has received a beacon signal from the beacon button 11 (step S401). If the signal has not been received (step S401; No), the communication terminal 20 waits until it receives a signal.

On the other hand, if a signal is received (step S401; Yes), the communication terminal 20 reads the information stored in the RF tag 50 via the RF reader 12 (step S402). The communication terminal 20 then obtains the tag ID and vehicle information stored in the RF tag 50 (step S403). The communication terminal 20 also begins detecting location information (step S404).

Subsequently, the communication terminal 20 determines whether or not it has received the beacon signal again (step S405). If the signal has not been received (step S405; No), the communication terminal 20 waits while continuing to detect location information until it receives the signal.

On the other hand, if a signal is received (step S405; Yes), the communication terminal 20 acquires the location information at that time as the parking location information (step S406). The processing from step S407 onwards is the same as the processing from step S103 onwards shown in Figure 15, so the explanation is omitted.

[2-2. Configuration of the portable unit]
In the above embodiment, the portable unit 10 according to the present disclosure was shown as an example including a beacon button 11, an RF reader 12, and a communication terminal 20. However, the configuration of the portable unit 10 is not limited to this example, as long as it is capable of performing the processing shown in the embodiment.

In other words, the portable unit 10 only needs to include a reader unit capable of reading information from the RF tag 50, a trigger unit capable of transmitting a signal to initiate reading of the RF tag, and an information communication terminal capable of transmitting a signal to the reader unit to initiate reading of the RF tag 50 upon receiving a signal from the trigger unit.

Furthermore, the portable unit 10 may consist of one or more units that implement the functions of a reader unit, a trigger unit, and an information and communication terminal. For example, if the functions of the reader unit, trigger unit, and information and communication terminal are implemented by a smartphone or an application that functions on a smartphone, the portable unit 10 may consist of a single smartphone. Also, while Figure 1 shows an example where the driver 30 confirms on the screen of the communication terminal 20 that information has been acquired from the RF tag 50, the communication terminal 20 may notify the driver 30 of the information by different means. For example, the communication terminal 20 may notify the driver 30 of the information not only through screen display, but also through means such as voice, notification sounds, flashing displays, or vibrations.

Furthermore, the portable unit 10 is not limited to the configuration shown in Figures 2 to 4. For example, the portable unit 10 may not have a spacer 13 as shown in Figure 3, and the beacon button 11, RF reader 12, and communication terminal 20 may be stored together in a single pocket. Also, in this embodiment, the storage section 16 for the portable unit 10 is shown as being vertically elongated relative to the person (with the RF reader 12 oriented vertically), but the storage section 16 may also be horizontally elongated (with the RF reader 12 oriented horizontally) or shaped to be worn diagonally across the person.

Thus, the portable unit 10 can have a flexible configuration. In other words, the portable unit 10 according to this disclosure can be implemented in a manner that meets the detailed requirements of administrators and drivers 30, thereby enabling the provision of a highly user-friendly parking management service.

[2-3. Types of Control Devices]
In the above embodiment, the management device 100 according to the disclosure is shown as an example of a server operated by an operator 40, but the configuration of the management device 100 is not limited to this. For example, if the functions of the management device 100 shown in the embodiment are realized by a communication terminal 20 included in the portable unit 10, the communication terminal 20 may also perform the functions of the management device 100. In this case, the communication terminal 20 stores the parking position of the vehicle 60 in association with vehicle information, and searches for the location of the vehicle 60 or displays the vehicle 60 and the occupancy rate of the parking area on the screen in response to a request from the driver 30.

[2-4. Types of actions that trigger the event]
In the above embodiment, the portable unit 10 according to the disclosure is shown to read the RF tag 50 in response to a first action by the driver and to acquire the parking position in response to a second action. Here, the first action and the second action are not limited to those exemplified in the embodiment, but may be any action that triggers processing.

Furthermore, the actions exemplified as the first and second actions may be combined in any way. For example, the portable unit 10 may read the RF tag 50 when the beacon button 11 is pressed and acquire the parking position when it detects that the driver has stopped the vehicle. Alternatively, the driver 30 may press the beacon button 11 in step S1 shown in Figure 1 and omit pressing the beacon button 11 in step S2. In this case, the portable unit 10 may determine the detected position as the parking position based on, for example, the elapsed time. Also, the processes shown in Figure 1, etc., do not necessarily have to be executed in order. For example, instead of acquiring the vehicle information of the vehicle 60 after acquiring the vehicle information held in the RF tag 50, the portable unit 10 may acquire the vehicle information immediately after the vehicle 60 has moved.

[2-5. Types of Parking Management Systems]
In the above embodiment, the processing performed by the parking management system 1 may be performed by either the portable unit 10 or the management device 100.

For example, in this embodiment, the portable unit 10 is shown to obtain the location, which is the name of the parking area, from the management device 100. However, the portable unit 10 may also store information about the parking area in the storage unit 22 and obtain location information from the storage unit 22.

Furthermore, while the embodiment shows an example where the vehicle 60 is parked in multiple wide-area parking spaces, the processing performed by the parking management system 1 is not limited to this. For example, the parking management system 1 may manage the location information of the vehicle 60 parked in an indoor warehouse or a large transport tanker. In this case, if it is difficult to detect location information using GPS or other satellites, the parking management system 1 may use various known technologies to detect location information, such as using the aforementioned access points, using radio waves from a smartphone base station, or using the vehicle speed sensor or gyroscope of the vehicle 60.

(3. Other Embodiments)
The processing according to the above-described embodiment may be carried out in various other forms besides those described above.

For example, among the processes described in the above embodiments, all or part of the processes described as being performed automatically can be performed manually, or all or part of the processes described as being performed manually can be performed automatically by known methods. Furthermore, the processing procedures, specific names, and various data and parameters shown in the above document and drawings can be arbitrarily changed unless otherwise specified. For example, the various information shown in each figure is not limited to the information illustrated.

Furthermore, the components of each illustrated device are functionally conceptual and do not necessarily need to be physically configured as shown. In other words, the specific forms of distribution and integration of each device are not limited to those illustrated; all or part of them can be functionally or physically distributed and integrated in any unit according to various loads and usage conditions.

Furthermore, the embodiments and modifications described above can be combined as appropriate, provided that the processing content remains consistent.

Furthermore, the effects described herein are merely illustrative and not limiting; other effects may also occur.

(4. Effects of the RF reader housing device related to this disclosure)
As described above, the RF reader storage device according to this disclosure (portable unit 10 in the embodiment) includes a storage section (storage section 16 in the embodiment) for storing an RF reader (RF reader 12 in the embodiment) capable of communicating with an RF tag (RF tag 50 in the embodiment), a first support section (first support section 17 in the embodiment) connected to one end of the storage section and capable of being slung over the shoulder from the front side of the person wearing the storage section, and a second support section (second support section 18 in the embodiment) connected to the other end of the storage section and extending to the back side through both sides of the person. When the storage section is worn by a person, one end and the other end are supported symmetrically with respect to the front of the person by the first support section and the second support section, thereby maintaining the orientation of the stored RF reader substantially constant with respect to the RF tag.

Thus, the RF reader housing device according to this disclosure, with its housing supported from two directions by a first support and a second support, maintains the orientation of the RF reader substantially constant relative to the RF tag while worn by a person, ensuring that the RF reader is reliably aligned with the RF tag. This allows the RF reader to improve the accuracy and speed of reading information from the RF tag. Furthermore, this structure does not hinder the movement of the person wearing the RF reader housing device and stably maintains the position of the housing, thereby improving the efficiency of work using the RF reader housing device.

Furthermore, the first support section consists of two belts, each connected to one end of the storage section. These two belts extend from the front of the person, across the upper shoulders, to the back, and connect to the second support section on the back.

Furthermore, the first support section may have two belts connected from the front of the person, passing over the upper shoulders and connecting at the back, and these connected belts may also be connected to the second support section at the back.

Furthermore, the first support section may be connected to the second support section on the rear side at different connection points (connecting section 17D in this embodiment) for each of the two belts.

Furthermore, the first support section may be connected to the second support section on the rear side after the two belts cross on the rear side.

Furthermore, the first support section consists of two belts, each extending from the front of the person through the upper shoulders, back, and sides to the front, and these two belts may be connected by another belt on the back. In this case, the second support section may be an extended version of the first support section.

This structure ensures that the RF reader housing device securely holds the housing in a nearly constant position relative to the person. In other words, this structure ensures that the RF reader housed in the housing is held in a nearly constant orientation relative to the RF tag. Therefore, the RF reader housing device can improve the reading accuracy of the RF reader.

Furthermore, the first support section consists of two expandable belts, each connected at two different points on one end of the storage section. The second support section consists of two expandable belts, each connected at two different points on the other end of the storage section.

This structure ensures that the RF reader housing device offers high wearability regardless of the wearer's body type.

Furthermore, the storage unit houses a trigger unit (a beacon button 11 in this embodiment) capable of transmitting a signal to initiate RF tag reading, and an information and communication terminal (a communication terminal 20 in this embodiment) capable of transmitting a signal to the RF reader to initiate RF tag reading upon receiving the signal emitted from the trigger unit.

In this way, the RF reader housing device, by housing multiple devices together, can implement parking management processes that reduce the driver's workload, such as initiating location information detection using beacon signals and reading vehicle information using RF readers.

Furthermore, the RF reader, upon receiving a signal to begin reading the RF tag, acquires vehicle information from the RF tag installed on the vehicle.

Thus, the RF reader storage device described in this disclosure improves convenience in parking management by housing a collection of devices that can acquire vehicle information through simple operations such as pressing a beacon button.

(5. Hardware Configuration)
The information devices such as the communication terminal 20 and the management device 100 according to the embodiments described above are realized by a computer 1000 having a configuration such as that shown in Figure 17. The following explanation will use the management device 100 according to the embodiments as an example. Figure 17 is a hardware configuration diagram showing an example of a computer 1000 that realizes the functions of the management device 100. The computer 1000 has a CPU 1100, RAM 1200, ROM (Read Only Memory) 1300, HDD (Hard Disk Drive) 1400, a communication interface 1500, and an input/output interface 1600. The various parts of the computer 1000 are connected by a bus 1050.

The CPU 1100 operates based on programs stored in the ROM 1300 or HDD 1400, controlling each component. For example, the CPU 1100 loads the programs stored in the ROM 1300 or HDD 1400 into the RAM 1200 and executes processing corresponding to various programs.

ROM 1300 stores boot programs such as the BIOS (Basic Input Output System) executed by the CPU 1100 when the computer 1000 starts up, as well as programs that depend on the computer 1000's hardware.

The HDD 1400 is a computer-readable recording medium that non-temporarily stores programs executed by the CPU 1100 and data used by such programs. Specifically, the HDD 1400 is a recording medium that stores an information processing program related to this disclosure, which is an example of program data 1450.

The communication interface 1500 is an interface for the computer 1000 to connect to an external network 1550 (e.g., the Internet). For example, the CPU 1100 receives data from other devices and transmits data it generates to other devices via the communication interface 1500.

The input/output interface 1600 is an interface for connecting the input/output device 1650 and the computer 1000. For example, the CPU 1100 receives data from input devices such as a keyboard or mouse via the input/output interface 1600. The CPU 1100 also transmits data to output devices such as a display, speaker, or printer via the input/output interface 1600. Furthermore, the input/output interface 1600 may function as a media interface for reading programs recorded on a predetermined recording medium (media). Examples of media include optical recording media such as DVDs (Digital Versatile Discs) and PDs (Phase-change rewritable Disks), magneto-optical recording media such as MOs (Magneto-Optical disks), tape media, magnetic recording media, or semiconductor memory.

For example, when computer 1000 functions as a management device 100 according to this embodiment, the CPU 1100 of computer 1000 realizes functions such as the control unit 130 by executing an information processing program loaded onto RAM 1200. Furthermore, the HDD 1400 stores the information processing program according to this disclosure and data from the storage unit 120. While the CPU 1100 reads and executes program data 1450 from HDD 1400, as an alternative example, these programs may be obtained from other devices via an external network 1550.

The embodiments of this application have been described in detail above with reference to the drawings. However, these are illustrative examples, and the present invention can be implemented in various modified and improved forms based on the knowledge of those skilled in the art, starting with the embodiments described in the disclosure section of the invention.

Furthermore, the terms "section," "module," and "unit" mentioned above can be replaced with "means" or "circuits." For example, the acquisition unit can be replaced with acquisition means or acquisition circuit.

1 Parking Management System 10 Portable Unit 11 Beacon Button 12 RF Reader 20 Communication Terminal 25 Acquisition Unit 26 Detection Unit 27 Transmission Unit 50 RF Tag 100 Management Device 110 Communication Unit 120 Storage Unit 121 Vehicle Information Storage Unit 122 Parking Area Storage Unit 123 Parking Position Storage Unit 130 Control Unit 131 Registration Unit 132 Display Control Unit

Claims (8)

A housing for an RF (Radio Frequency) tag-capable RF reader and a trigger unit for operating the RF reader ,
A first support portion is connected to one end of the storage unit and can be carried over the shoulder from the front side of the person wearing the storage unit,
It comprises a second support portion connected to the other end of the storage portion and extending to the rear side through both sides of the person,
The aforementioned storage compartment is
When viewed from the front of the person, the storage portion is roughly rectangular in shape, and when attached to the person, one end is supported by the first support portion on the front side of the person, the other end is supported by the second support portion on the front side of the person and below the first end, and the longitudinal direction of the storage portion is oriented from the head to the feet of the person.
It is equipped with a storage pocket for housing the RF reader and the trigger unit ,
The storage pocket is substantially rectangular when viewed from the front of the person, the longitudinal orientation of the storage section and the longitudinal orientation of the storage pocket are the same, the location where the trigger unit is stored is positioned closer to the person's feet than the RF reader, and the material of the part of the location where the trigger unit is stored, when viewed from the front of the person, is made of a transparent or translucent material.
An RF reader housing device characterized by the following features. The first support portion is,
The two belts are connected to one end of the storage section, and each of the two belts extends from the front of the person through the upper shoulders to the back, and connects to the second support section on the back side.
The RF reader housing device according to feature 1. The first support portion is,
The two belts are connected on the back side of the person, passing from the front side through the upper shoulders, and the connected belts are connected to the second support part on the back side.
The RF reader housing device according to feature 2. The first support portion is,
Each of the two belts is connected to the second support at a different connection point on the back side.
The RF reader housing device according to feature 2. The first support portion is,
The two belts cross on the rear side and then connect with the second support on the rear side.
The RF reader housing device according to feature 2. The first support portion is,
It consists of two belts, each of which extends from the front of the person through the upper shoulders, back, and sides to the front, and the two belts are connected by another belt on the back.
The second support portion is,
The extended first support portion is
The RF reader housing device according to feature 1. The first support portion is,
These are two expandable belts, each connected at two different points on one end of the aforementioned storage section.
The second support portion is,
These are two expandable belts, each connected at two different points on the other end of the aforementioned storage section.
The RF reader housing device according to any one of claims 1 to 6. The aforementioned storage pocket is
The RF reader, the trigger unit capable of transmitting a signal to initiate reading of the RF tag, and the information communication terminal capable of transmitting a signal to the RF reader to initiate reading of the RF tag upon receiving a signal from the trigger unit are housed together, and a spacer is provided between the information communication terminal and the RF reader.
The RF reader housing device according to any one of claims 1 to 7.