Video management device and video management program for industrial vehicles
The video management system for industrial vehicles addresses complexity and cost issues by using a web application and real-time communication, facilitating easy adaptation and user-friendly data management.
Patent Information
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- NICHIYU LOGISYS CO LTD
- Filing Date
- 2025-08-01
- Publication Date
- 2026-06-26
AI Technical Summary
Conventional video management systems for industrial vehicles are complex and costly, requiring specialized programming languages and advanced network configurations, making them difficult to adapt to specification changes and challenging for users to set up.
A video management system utilizing a web application and a real-time communication control unit that relays camera images and sensor data through a management server, enabling centralized management and peer-to-peer communication without complex network configurations.
The system allows easy adaptation to specification changes and eliminates the need for complex network setups, providing cost-effective and user-friendly management of industrial vehicle data.
Smart Images

Figure 2026105808000001_ABST
Abstract
Description
Technical Field
[0001] The present disclosure relates to a video management device and a video management program for industrial vehicles.
Background Art
[0002] In industrial vehicles such as forklifts, supplies such as a drive recorder and various sensors are often attached for managing the driving situation and the like. The videos recorded by these drive recorders and the information collected by the sensors can be used to avoid accidents in advance and to investigate the causes in case an accident occurs. In recent years, a management system has been proposed that collectively manages the videos of drive recorders collected by a plurality of industrial vehicles such as forklifts in a database and enables searching of the videos collectively managed in the database.
Prior Art Documents
Patent Documents
[0003]
Patent Document 1
Summary of the Invention
Problems to be Solved by the Invention
[0004] Conventional video management systems for industrial vehicles are often developed using complex programming languages such as C language. While complex systems can be developed with programming languages, development costs tend to be high. Also, in the case of a video management system created with a programming language, it is often necessary to install a dedicated application during introduction. Therefore, it is difficult to respond to various specification changes such as changes in the specifications of industrial vehicles.
[0005] Furthermore, transmitting sensor data and camera footage collected by industrial vehicles to a management server via the internet requires advanced network configurations, such as opening router ports and configuring NAT (Network Address Translation) traversal. These network configurations are often complex and require specialized knowledge.
[0006] The embodiment provides a video management device and video management program for industrial vehicles that can easily accommodate various specification changes and does not require the user to perform complex network configurations. [Means for solving the problem]
[0007] One embodiment of the video management device comprises a control unit and a real-time communication control unit. The control unit runs a web application for the centralized management of multiple industrial vehicles to start the video management system. The real-time communication control unit receives camera images transmitted from the industrial vehicles via a communication processing unit, relays the received camera images to a user terminal via the communication processing unit, and displays the camera images as moving images on the video management system screen displayed on the user terminal's web browser. [Effects of the Invention]
[0008] In this embodiment, a video management system and video management program for industrial vehicles are provided that can easily accommodate various specification changes and do not require the user to perform complex network configurations. [Brief explanation of the drawing]
[0009] [Figure 1] Figure 1 shows an example configuration of a video management system for an industrial vehicle according to an embodiment. [Figure 2] Figure 2 is an external view showing the configuration of a forklift as an example of an industrial vehicle. [Figure 3] Figure 3 is a block diagram showing the hardware configuration of an example management server. [Figure 4]Figure 4 is a block diagram showing the hardware configuration of an example user terminal. [Figure 5] Figure 5 is a functional block diagram of an industrial vehicle, specifically focusing on information processing, as an example of an industrial vehicle. [Figure 6] Figure 6 is a functional block diagram of the management server. [Figure 7] Figure 7 is a functional block diagram of the user terminal. [Figure 8] Figure 8 is a flowchart showing the operation of a forklift as an industrial vehicle. [Figure 9] Figure 9 is a flowchart showing the operation of the management server. [Figure 10] Figure 10 is a flowchart showing the operation of the user terminal. [Modes for carrying out the invention]
[0010] The embodiments will be described below with reference to the drawings. Figure 1 is a diagram showing the configuration of an example of a video management system for industrial vehicles according to the embodiment. The video management system 1 is a video management system that supports the centralized management of multiple industrial vehicles. The video management system 1 includes an industrial vehicle 2 and a management server 3. The industrial vehicle 2 can communicate with the management server 3 via a network 5. The management server 3 can also communicate with a user terminal 4 via the network 5. The network 5 is, for example, the internet. Of course, the network 5 is not limited to the internet and may be a local network.
[0011] Industrial vehicle 2 is a vehicle used for industrial purposes. Industrial vehicle 2 is not limited to this, but could be a forklift, for example. As will be explained later, industrial vehicle 2 is equipped with a camera and sensors, and can transmit camera images obtained by the camera and sensor data collected by the sensors to external devices. Industrial vehicle 2 can transmit camera images and sensor data to the management server 3 via wireless communication, for example, via access point 5a. In this embodiment, camera images and sensor data from multiple industrial vehicles 2 can be managed collectively by the management server 3. In Figure 1, there are three industrial vehicles 2. The number of industrial vehicles 2 is not limited to three; there can be one or more industrial vehicles 2.
[0012] The management server 3, acting as a video management device for industrial vehicles, centrally manages camera images and sensor data transmitted from the industrial vehicle 2. Furthermore, the management server 3 also functions as a signaling server and STUN (Session Traversal Utilities for NAT) / TURN (Traversal Using Relays around NAT) server for P2P (peer-to-peer) communication between the industrial vehicle 2 and the user terminal 4. Under the control of the management server 3, real-time communication between the industrial vehicle 2 and the user terminal 4 is achieved.
[0013] User terminal 4 is a terminal device with browser functionality, such as a personal computer (PC), smartphone, or tablet, but is not limited to these. User terminal 4 can display the vehicle status of the industrial vehicle 2 based on sensor data from the industrial vehicle 2, and, for example, a moving image of the front of the industrial vehicle 2 based on camera images.
[0014] Figure 2 is an external view showing the configuration of a forklift as an example of an industrial vehicle 2. The industrial vehicle 2 shown in Figure 2 is a counterbalanced forklift. On the other hand, the forklift in this embodiment is not limited to a counterbalanced type. That is, the forklift in this embodiment may be a reach forklift or the like.
[0015] As shown in FIG. 2, the forklift as the industrial vehicle 2 has a vehicle body 210. A mast 211 is attached to the front part of the vehicle body 210. Forks 212 are attached to the mast 211. The forks 212 move up and down along the mast 211 by the operation of an operator who is the driver of the industrial vehicle 2. Further, a counterweight 213 is provided at the rear part of the vehicle body 210. The counterweight 213 is provided to balance with the load when the load is placed on the forks 212.
[0016] Also, a seat 214 is attached to the vehicle body 210. Further, a steering wheel 215 is provided in front of the seat 214. An operator sitting on the seat 214 can operate the steering wheel 215. Four columns 216 are provided on the vehicle body 210 so as to surround the seat 214. Among the four columns 216, for example, a display 217 is attached to one column 216 in front of the seat 214. Various kinds of information related to the industrial vehicle 2 can be displayed on the display 217.
[0017] In addition, a head guard 218 is provided at the upper part of the four support columns 216. The head guard 218 is a guard member for protecting the head of an operator sitting on the seat 214. Forklift supplies such as a camera 219, an acceleration sensor 220, a gyro sensor 221, a GPS (Global Positioning System) receiver 222, and a wireless transceiver 223 may be attached to the head guard 218. The camera 219 is provided for photographing, for example, the front of the vehicle body 210. The camera image obtained by photographing with the camera 219 is recorded in a drive recorder (not shown) as a moving image. Also, the camera image obtained by photographing with the camera 219 can be transmitted to the management server 3 via the wireless transceiver 223. The acceleration sensor 220 is, for example, a three-axis acceleration sensor of XYZ, and detects the acceleration along each axis generated in the vehicle body 210. The gyro sensor 221 detects, for example, the angular velocity around the XYZ axes. The GPS receiver 222 collects the position information of the industrial vehicle 2 by receiving radio waves from a base station (not shown). The sensor data collected by the acceleration sensor 220, the gyro sensor 221, and the GPS receiver 222 can be recorded in a drive recorder (not shown) in association with the camera image obtained by the camera 219. Or, the sensor data collected by the acceleration sensor 220, the gyro sensor 221, and the GPS receiver 222 can be transmitted to the management server 3 via the wireless transceiver 223. The wireless transceiver 223 is a device for the industrial vehicle 2 to perform wireless communication with the management server 3.
[0018] Figure 3 is a block diagram showing an example of the hardware configuration of the management server 3. The management server 3 can be a computer having a processor 301, a memory 302, a storage 303, an input interface 304, a display 305, and a communication device 306 as hardware. The management server 3 may be configured as a cloud.
[0019] Processor 301 is a processor that controls the overall operation of the management server 3. Processor 301 controls various processes in the management server 3 by executing, for example, a video management program 3031 stored in storage 303. Processor 301 is, for example, a CPU. Processor 301 may also be an MPU, GPU, ASIC, FPGA, etc. Processor 301 may be a single CPU, or multiple CPUs, etc.
[0020] Memory 302 includes ROM and RAM. ROM is non-volatile memory. ROM stores the startup programs and other data for the computers that make up the management server 3. RAM is volatile memory. RAM is used, for example, as working memory during processing by the processor 301.
[0021] Storage 303 is, for example, a hard disk drive or a solid-state drive. Storage 303 stores various programs executed by the processor 301, such as the operating system (OS) and the video management program 3031. The video management program 3031 is a program for video management and is configured as a web application. The video management program 3031 is executed by the processor 301 of the management server 3, which acts as a web server. When the video management program 3031 is executed, the video management system screen is displayed on a web browser connected to the management server 3. The processor 301 is made to execute the following functions: a function to store camera images and sensor data transmitted from the industrial vehicle 2 in storage 303 in association with the ID of the industrial vehicle 2; a function to detect abnormal events of each industrial vehicle 2 from the camera images and sensor data managed in storage 303; and a real-time video display function that displays camera images transmitted from the industrial vehicle 2 in real time on the video management system screen displayed on the web browser of the user terminal 4. These functions may each be implemented by different web applications. Furthermore, the real-time video display function can be implemented by a program that operates the management server 3 as a signaling server and STUN / TURN server. Therefore, users of user terminal 4 do not need to perform complex network configurations when using the video management system.
[0022] Furthermore, the storage 303 can function as online storage for managing camera images 3032 and sensor data 3033 transmitted from the industrial vehicle 2 online. The camera images 3032 and sensor data 3033 stored in the storage 303 can be viewed on the video management system screen displayed on the web browser of the display 305 or on the web browser of the user terminal 4. Alternatively, the camera images 3032 and sensor data 3033 stored in the storage 303 can be viewed by downloading them from the user terminal 4.
[0023] The input interface 304 is an input device such as a touch panel, keyboard, or mouse. The input interface 304 receives operations from the operator of the management server 3. The content of the operations received via the input interface 304 is interpreted by the processor 301. The processor 301 can perform various data processing operations in response to the operator's operations, such as displaying images of the industrial vehicle 2 based on camera images 3032, for example, an image of the front of the industrial vehicle 2, and the vehicle status of the industrial vehicle 2 based on sensor data 3033, on the screen of the video management system.
[0024] Display 305 is a display device such as a liquid crystal display or an organic EL display. Display 305 performs various types of displays. These types of displays may include things like web browser displays.
[0025] The communication device 306 is a communication device that allows the management server 3 to communicate with external devices via the network 5. The communication device 306 may be a communication device for wired communication or a communication device for wireless communication.
[0026] Figure 4 is a block diagram showing the hardware configuration of an example of a user terminal 4. The user terminal 4 may be a computer having a processor 401, memory 402, storage 403, input interface 404, display 405, and communication device 406 as hardware.
[0027] Processor 401 is a processor that controls the overall operation of the user terminal 4. Processor 301 is, for example, a CPU. Processor 401 may be an MPU, GPU, ASIC, FPGA, etc. Processor 401 may be a single CPU, etc., or multiple CPUs, etc.
[0028] Memory 402 includes ROM and RAM. ROM is non-volatile memory. ROM stores the startup program and other data for the computer that constitutes the user terminal 4. RAM is volatile memory. RAM is used, for example, as working memory during processing by the processor 401.
[0029] Storage 403 is, for example, a storage device such as semiconductor memory, a hard disk drive, or a solid-state drive. Storage 303 stores various programs executed by the processor 401, such as the operating system (OS) and various application programs. The application programs stored in storage 403 include browser application programs. In addition, storage 403 can store camera images and sensor data downloaded from the management server 3.
[0030] The input interface 404 is an input device such as a touch panel, keyboard, or mouse. The input interface 304 receives user operations from the user terminal 4. The content of the operations received via the input interface 404 is interpreted by the processor 401. The processor 401 can perform various data processing operations in response to user operations, such as displaying images of the front of the industrial vehicle 2 based on camera images and the vehicle status of the industrial vehicle 2 based on sensor data on the screen of the video management system displayed on the web browser.
[0031] Display 405 is a display device such as a liquid crystal display or an organic EL display. Display 405 performs various types of displays. These types of displays may include things like web browser displays.
[0032] The communication device 406 is a communication device that allows the user terminal 4 to communicate with external devices via the network 5. The communication device 406 may be a communication device for wired communication or a communication device for wireless communication.
[0033] Figure 5 is a functional block diagram of the industrial vehicle 2, particularly concerning information processing. The industrial vehicle 2 has the following functions related to information processing: a sensor unit 2001, a camera unit 2002, an anomaly detection unit 2003, an image acquisition unit 2004, a recording unit 2005, a real-time communication processing unit 2006, a non-real-time communication processing unit 2007, and a control unit 2008. Here, the functions of the anomaly detection unit 2003, the image acquisition unit 2004, and the control unit 2008 can be realized by a program executed by a processor provided in the internal circuit of the industrial vehicle 2. In addition, the solid lines in Figure 5 show the flow of data, and the dashed lines in Figure 5 show the flow of control instructions.
[0034] The sensor unit 2001 includes a group of sensors, such as the acceleration sensor 220, gyro sensor 221, and GPS receiver 222 shown in Figure 2, and detects information related to various vehicle conditions of the industrial vehicle 2. The sensor unit 2001, for example, detects the condition of the industrial vehicle 2 at regular intervals and outputs sensor data including the detection results to the anomaly detection unit 2003. The group of sensors included in the sensor unit 2001 is not limited to the acceleration sensor 220, gyro sensor 221, and GPS receiver 222. The group of sensors may also include, for example, a magnetic sensor, a temperature sensor, and a humidity sensor.
[0035] The camera unit 2002 includes the camera 219 shown in Figure 2 and photographs, for example, the front of the industrial vehicle 2. The camera unit 2002 performs photography at, for example, a constant frame rate and outputs the camera image obtained from the photography to the image acquisition unit 2004. The cameras included in the camera unit 2002 are not limited to the camera 219 that photographs the front of the industrial vehicle 2. The cameras included in the camera unit 2002 may also include cameras that photograph the rear, sides, etc., of the industrial vehicle 2.
[0036] The anomaly detection unit 2003 determines whether or not there is an abnormal event in the industrial vehicle 2 from the sensor data acquired by the sensor unit 2001. An abnormal event in the industrial vehicle 2 is, for example, an abnormal event related to the safe operation of the industrial vehicle 2. An abnormal event in the industrial vehicle 2 includes abnormalities of the vehicle itself, such as abnormal vibration, voltage abnormalities, and temperature abnormalities of the industrial vehicle 2, as well as abnormalities caused by operational errors of the industrial vehicle 2 or the worker, such as the industrial vehicle 2's path deviating from the expected path or the distance between multiple industrial vehicles 2 being too close. When the anomaly detection unit 2003 detects an abnormal event in the industrial vehicle 2, it notifies the image acquisition unit 2004 of this fact. The anomaly detection unit 2003 also records the sensor data acquired by the sensor unit 2001 in the recording unit 2005. The anomaly detection unit 2003 may record the sensor data in the recording unit 2005 only when it detects an abnormality in the industrial vehicle 2.
[0037] The image acquisition unit 2004 acquires camera images from the camera unit 2002. The image acquisition unit 2004 then records the acquired camera images in the recording unit 2005. In addition, the image acquisition unit 2004 transfers the camera images acquired from the camera unit 2002 to the real-time communication processing unit 2006 in response to control instructions from the control unit 2008.
[0038] The recording unit 2005 is, for example, a drive recorder and can record sensor data acquired by the anomaly detection unit 2003 and camera images acquired by the image acquisition unit 2004. The control unit 2008 can refer to the sensor data and camera images recorded in the recording unit 2005.
[0039] The real-time communication processing unit 2006 includes the wireless transceiver 223 shown in Figure 2 and performs processing for P2P real-time communication between the industrial vehicle 2 and the user terminal 4 via the network 5. For example, when a camera image is transferred from the image acquisition unit 2004, the real-time communication processing unit 2006 transmits the camera image to the user terminal 4 according to the control of the management server 3. The non-real-time communication processing unit 2007 includes the wireless transceiver 223 shown in Figure 2 and performs processing for non-real-time communication between the industrial vehicle 2 and the management server 3 via the network 5. For example, when the non-real-time communication processing unit 2007 receives a control instruction or setting instruction from the management server 3, it transfers the received control instruction or setting instruction to the control unit 2008. Also, when sensor data and camera images are transferred from the control unit 2008, the non-real-time communication processing unit 2007 transmits the sensor data and camera images to the management server 3.
[0040] The control unit 2008 controls the industrial vehicle 2. For example, the control unit 2008 issues control instructions to the anomaly detection unit 2003 to acquire sensor data, to the image acquisition unit 2004 to record camera images to the recording unit 2005 or to transfer them to the real-time communication processing unit 2006, and to the non-real-time communication processing unit 2007 to transmit the sensor data and camera images recorded in the recording unit 2005 to the management server 3 in association with the ID of the industrial vehicle 2.
[0041] Figure 6 is a functional block diagram of the management server 3. The management server 3 includes a communication processing unit 3001, an information acquisition unit 3002, a recording unit 3003, a display unit 3004, a real-time communication control unit 3005, and a control unit 3006. Here, the functions of the information acquisition unit 3002, the real-time communication control unit 3005, and the control unit 3006 can be realized by the video management program 3031. In addition, the solid lines in Figure 6 show the flow of data, and the dashed lines in Figure 6 show the flow of control instructions.
[0042] The communication processing unit 3001 includes the communication device 306 shown in Figure 3 and performs processing for communication between the management server 3 and the industrial vehicle 2 via the network 5. For example, the communication processing unit 3001 transmits control instructions or setting instructions to the industrial vehicle 2. Also, when sensor data and camera images are received, the communication processing unit 3001 transfers the received sensor data and camera images to the information acquisition unit 3002. Furthermore, during real-time communication between the industrial vehicle 2 and the user terminal 4 via the network 5, the communication processing unit 3001 performs the necessary communication between the industrial vehicle 2 and the user terminal 4 to operate as a signaling server and STUN / TURN server.
[0043] The information acquisition unit 3002 acquires sensor data and camera images received by the communication processing unit 3001, and records the acquired sensor data and camera images in the recording unit 3003.
[0044] The recording unit 3003 includes the storage 303 shown in Figure 3 and records sensor data and camera images acquired by the information acquisition unit 3002 in association with the ID of the industrial vehicle 2. The sensor data and camera images recorded in the recording unit 3003 can be downloaded to the user terminal 4. The sensor data and camera images may be associated with the ID of the worker in addition to or instead of the ID of the industrial vehicle 2.
[0045] The display unit 3004 includes the display 305 shown in Figure 3 and displays various images. The display unit 3004 may be omitted.
[0046] The control unit 3006 controls the management server 3. For example, the control unit 3006 executes the video management program 3031 as a web application to start the video management system and displays the video management system screen on a web browser. The control unit 3006 also receives operation instructions from the operator on the video management system screen and displays the vehicle status of the industrial vehicle 2 based on sensor data recorded in the recording unit 3003, as well as video footage of the industrial vehicle 2, for example, the front view, based on camera images. Furthermore, the control unit 3006 monitors and evaluates the operating status of the industrial vehicle 2 from the sensor data and camera images recorded in the recording unit 3003. For example, if an abnormal event occurs in the industrial vehicle 2, the control unit 3006 sends a control instruction corresponding to the abnormal event to the industrial vehicle 2 using the communication processing unit 3001. In addition, the control unit 3006 may evaluate the driving skills of each worker of the industrial vehicle 2 based on the low number of abnormal events, etc.
[0047] The real-time communication control unit 3005 controls real-time communication between the industrial vehicle 2 and the user terminal 4 via the network 5. For example, the real-time communication control unit 3005 controls the system as a signaling server, performing session management during communication between the industrial vehicle 2 and the user terminal 4. The real-time communication control unit 3005 also controls the system as a STUN server, receiving IP address queries from the industrial vehicle 2 or the user terminal 4 and notifying the corresponding device of the IP address. Furthermore, the real-time communication control unit 3005 controls the system as a TURN server, relaying data transferred from the industrial vehicle 2 or the user terminal 4 to the recipient.
[0048] Figure 7 is a functional block diagram of the user terminal 4. The user terminal 4 includes a real-time communication processing unit 4001, a non-real-time communication processing unit 4002, a display unit 4003, a recording unit 4004, and a control unit 4005. Here, the functions of the control unit 4005 can be realized by a program stored in the storage 403. In Figure 7, the solid lines indicate the flow of data, and the dashed lines indicate the flow of control instructions.
[0049] The real-time communication processing unit 4001 includes the communication device 406 shown in Figure 4 and performs processing for P2P real-time communication between the user terminal 4 and the industrial vehicle 2 via the network 5. For example, when the real-time communication processing unit 4001 receives a camera image from the industrial vehicle 2, it transfers the camera image to the control unit 4005. The non-real-time communication processing unit 4002 includes the communication device 406 shown in Figure 4 and performs processing for non-real-time communication between the industrial vehicle 2 and the management server 3 via the network 5. For example, when sensor data and camera images are downloaded from the management server 3, the non-real-time communication processing unit 4002 transfers the sensor data and camera images to the control unit 4005.
[0050] The display unit 4003 includes the display 405 shown in Figure 4 and displays various images. The recording unit 4004 includes the storage 403 shown in Figure 4 and records sensor data and camera images downloaded from the management server 3.
[0051] The control unit 4005 controls the user terminal 4. For example, the control unit 4005 displays the camera image transferred from the real-time communication processing unit 4001 on the screen of the video management system displayed on the web browser on the display unit 4003. Furthermore, the control unit 4005 records the sensor data and camera image downloaded from the non-real-time communication processing unit 4002 in the recording unit 4004.
[0052] Next, the operation of the video management system 1 will be explained. Figure 8 is a flowchart showing the operation of a forklift as an industrial vehicle 2. Here, Figure 8 shows the processing of sensor data and camera images in the forklift. In reality, the operation of the forklift may include driving control of the vehicle body 210, such as when the accelerator pedal (not shown) is pressed, but this is omitted in Figure 8.
[0053] In step S1, the control unit 2008 instructs the anomaly detection unit 2003 to acquire sensor data. The control unit 2008 also instructs the image acquisition unit 2004 to acquire camera images. The interval for acquiring sensor data and the interval for acquiring camera images may be fixed intervals, or they may be intervals set by setting instructions from the management server 3.
[0054] In step S2, the anomaly detection unit 2003 determines whether or not an abnormal event has been detected from the sensor data. If it is determined in step S2 that an abnormal event has been detected, the process proceeds to step S3. If it is not determined in step S2 that an abnormal event has been detected, the process proceeds to step S5.
[0055] In step S3, the anomaly detection unit 2003 records the sensor data acquired when an abnormal event is detected in the recording unit 2005. The anomaly detection unit 2003 also notifies the image acquisition unit 2004 that an abnormal event has been detected. In response, the image acquisition unit 2004 records the camera image acquired when the abnormal event was detected in the recording unit 2005.
[0056] In step S4, the control unit 2008 associates the sensor data and camera images recorded in the recording unit 2005 when an abnormal event is detected with the ID of the industrial vehicle 2, and transmits them to the management server 3 via the non-real-time communication processing unit 2007.
[0057] In step S5, the image acquisition unit 2004 determines whether or not the camera image is set to be transmitted in real time. The setting for real-time transmission may be made, for example, based on a setting instruction from the control unit 2008 based on a setting instruction from the management server 3. If it is determined in step S5 that the camera image is set to be transmitted in real time, the process proceeds to step S6. If it is not determined in step S5 that the camera image is set to be transmitted in real time, the process returns to step S1.
[0058] In step S6, the image acquisition unit 2004 transmits the acquired camera image to the user terminal 4 via the real-time communication processing unit 2006. After that, the process returns to step S1. As mentioned above, the real-time communication processing unit 2006 may communicate with the user terminal 4 via P2P through the management server 3. In addition to the camera image, the real-time communication processing unit 2006 may also transmit sensor data to the user terminal 4.
[0059] In the example shown in Figure 8, sensor data and camera images are recorded in the recording unit 2005 only when an abnormal event is detected. However, sensor data and camera images may be recorded in the recording unit 2005 regardless of whether an abnormal event is detected. Furthermore, the transmission of sensor data and camera images to the management server 3 may also be performed regardless of whether an abnormal event is detected.
[0060] Figure 9 is a flowchart showing the operation of the management server 3. In step S101, the information acquisition unit 3002 determines whether or not it has acquired sensor data and camera images from the communication processing unit 3001. If it is determined in step S101 that sensor data and camera images have been acquired, the process proceeds to step S102. If it is not determined in step S101 that sensor data and camera images have been acquired, the process proceeds to step S103.
[0061] In step S102, the information acquisition unit 3002 records the sensor data and camera image in the recording unit 3003, associating them with the ID of the industrial vehicle 2. The process then proceeds to step S103.
[0062] In step S103, the control unit 3006 determines whether or not to display the sensor data and / or camera image on the display unit 3004. For example, if the control unit 3006 receives a request from the operator of the management server 3 to display any of the sensor data and / or camera image recorded in the recording unit 3003 through an operation on the video management system screen displayed on the display unit 3004, it determines to display the sensor data and / or camera image on the display unit 3004. If it is determined in step S103 to display the sensor data and / or camera image on the display unit 3004, the process proceeds to step S104. If it is not determined in step S103 to display the sensor data and / or camera image on the display unit 3004, the process proceeds to step S105.
[0063] In step S104, the control unit 3006 reads the specified sensor data and / or camera image from the recording unit 3003 and displays the read sensor data and / or camera image on the screen of the video management system displayed in the web browser. The process then proceeds to step S105.
[0064] In step S105, the control unit 3006 determines whether or not to send a control instruction or a setting instruction to the industrial vehicle 2. For example, if the control unit 3006 receives a request for any control instruction or setting instruction for the industrial vehicle 2 from an operator of the management server 3 through an operation on the video management system screen displayed on the display unit 3004, or if an abnormal event is detected from sensor data, it is determined to send a control instruction or a setting instruction to the industrial vehicle 2. Control instructions include instructions for transmitting sensor data and camera images from the industrial vehicle 2, and instructions for forcibly stopping the industrial vehicle 2. Setting instructions include instructions for the acquisition interval of sensor data and camera images. If it is determined in step S105 to send a control instruction or a setting instruction to the industrial vehicle 2, the process proceeds to step S106. If it is not determined in step S105 to send a control instruction or a setting instruction to the industrial vehicle 2, the process proceeds to step S107.
[0065] In step S106, the control unit 3006 transmits a control instruction or setting instruction to the industrial vehicle 2 via the communication processing unit 3001. The process then proceeds to step S107.
[0066] In step S107, the control unit 3006 determines whether a request to download sensor data or camera images has been made. For example, if a request to download any sensor data or camera images is made by the user through an operation on the web browser displayed on the display unit 4003 of the user terminal 4, it is determined that a request to download sensor data or camera images has been made. If it is determined in step S107 that a request to download sensor data or camera images has been made, the process proceeds to step S108. If it is not determined in step S107 that a request to download sensor data or camera images has been made, the process proceeds to step S109.
[0067] In step S108, the control unit 3006 transmits the specified sensor data or camera image to the user terminal 4 via the communication processing unit 3001. The process then proceeds to step S109.
[0068] In step S109, the real-time communication control unit 3005 determines whether or not to perform real-time data transmission between the industrial vehicle 2 and the user terminal 4. In step S109, if data is transmitted from either the real-time communication processing unit of the industrial vehicle 2 or the user terminal 4 using the real-time communication protocol, it is determined that real-time data transmission between the industrial vehicle 2 and the user terminal 4 will be performed. If it is determined in step S109 that real-time data transmission between the industrial vehicle 2 and the user terminal 4 will be performed, the process proceeds to step S110. If it is not determined in step S109 that real-time data transmission between the industrial vehicle 2 and the user terminal 4 will be performed, the process returns to step S101.
[0069] In step S110, the real-time communication control unit 3005 relays the data transmitted from either the industrial vehicle 2 or the user terminal 4 to the other. After that, the process returns to step S101.
[0070] Figure 10 is a flowchart showing the operation of the user terminal 4. In step S201, the control unit 4005 determines whether or not sensor data and camera images have been received from the real-time communication processing unit 4001. If it is determined in step S201 that sensor data and camera images have been received, the process proceeds to step S202. If it is not determined in step S201 that sensor data and camera images have been received, the process proceeds to step S203.
[0071] In step S202, the control unit 4005 displays the vehicle status of the industrial vehicle 2 based on sensor data received via the real-time communication processing unit 4001, and, for example, a video of the front of the industrial vehicle 2 based on camera images, on the screen of the video management system displayed in the web browser. The process then proceeds to step S203.
[0072] In step S203, the control unit 4005 determines whether or not to send a setting instruction. For example, if the user makes a setting instruction regarding the camera image acquisition interval, etc., through operation on the video management system screen displayed on the display unit 4003, it is determined to send the setting instruction. If it is determined in step S203 to send the setting instruction, the process proceeds to step S204. If it is not determined in step S203 to send the setting instruction, the process proceeds to step S205.
[0073] In step S204, the control unit 4005 sends a setting instruction to the management server 3 via the non-real-time communication processing unit 4002. The process then proceeds to step S205.
[0074] In step S205, the control unit 4005 determines whether or not to display the sensor data and / or camera image on the display unit 4003. For example, if the control unit 4005 receives a request to display any of the sensor data and / or camera image recorded in the recording unit 3003 of the management server 3 through an operation on the video management system screen displayed on the display unit 4003, it determines to display the sensor data and / or camera image on the display unit 4003. If it is determined in step S205 to display the sensor data and / or camera image on the display unit 4003, the process proceeds to step S206. If it is not determined in step S205 to display the sensor data and / or camera image on the display unit 4003, the process returns to step S201.
[0075] In step S206, the control unit 4005 sends a download request for the specified sensor data and / or camera image to the management server 3. The control unit 4005 then displays the vehicle status of the industrial vehicle 2 based on the sensor data received from the management server 3 and / or a moving image of the industrial vehicle 2, for example, the front view, based on the camera image, on the display unit 4003 and records it in the recording unit 4004. After that, the process returns to step S201.
[0076] As described above, in this embodiment, the video management program on the management server 3 is configured as a web application that runs on a web browser. Therefore, the video management system in this embodiment can operate without being affected by the specifications of the industrial vehicle 2 and the user terminal 4. Accordingly, the video management system in this embodiment can easily respond to various specification changes, such as changes in the specifications of the industrial vehicle. The development cost of a web application-based video management system for industrial vehicles is expected to be lower than that of a video management system developed using a complex programming language such as C.
[0077] Furthermore, the video management program includes a web application to operate the management server 3 as a signaling server and STUN / TURN server. This allows the industrial vehicle 2 and the user terminal 4 to communicate in real time via P2P over a network 5 such as the internet. Moreover, users of the user terminal 4 only need to install a web browser on their terminal 4 and do not need to perform complex network configurations.
[0078] Furthermore, because the video management system operates as a web application, there is no need to install any special applications on user terminal 4. In other words, the user on user terminal 4 can view the camera images acquired by the industrial vehicle 2 as moving images on a web browser.
[0079] The present invention is not limited to the embodiments described above, and can be modified in various ways during implementation without departing from its essence. Furthermore, each embodiment may be combined as appropriate, and in that case, the combined effects can be obtained. Moreover, the above embodiments include various inventions, and various inventions can be extracted by selecting combinations from the multiple constituent elements disclosed. For example, if the problem can be solved and effects obtained even if some constituent elements are deleted from all the constituent elements shown in the embodiment, then the configuration with these deleted constituent elements can be extracted as an invention. [Explanation of Symbols]
[0080] 1 Video management system, 2 Industrial vehicle, 3 Management server, 4 User terminal, 5 Network, 5a Access point, 2001 Sensor unit, 2002 Camera unit, 2003 Anomaly detection unit, 2004 Image acquisition unit, 2005 Recording unit, 2006 Real-time communication processing unit, 2007 Real-time communication processing unit, 2008 Control unit, 3001 Communication processing unit, 3002 Information acquisition unit, 3003 Recording unit, 3004 Display unit, 3005 Real-time communication control unit, 3006 Control unit, 4001 Real-time communication processing unit, 4002 Non-real-time communication processing unit, 4003 Display unit, 4004 Recording unit, 4005 Control unit.
Claims
1. A control unit that runs a web application for centralized management of multiple industrial vehicles and starts a video management system, A real-time communication control unit receives camera images transmitted from the industrial vehicle by a communication processing unit, relays the received camera images to a user terminal by the communication processing unit, and displays the camera images as moving images on the screen of the video management system displayed on the user terminal's web browser. A video management device for industrial vehicles.
2. The real-time communication control unit further receives sensor data, which is the detection result of the vehicle status of the industrial vehicle transmitted from the industrial vehicle, via the communication processing unit, relays the received sensor data to the user terminal via the communication processing unit, and displays the vehicle status of the industrial vehicle based on the sensor data on the screen of the video management system displayed on the web browser of the user terminal. A video management device for an industrial vehicle according to claim 1.
3. The system further comprises a recording unit that records the camera image received by the communication processing unit, A video management device for an industrial vehicle according to claim 1.
4. The aforementioned industrial vehicle is a forklift. A video management device for an industrial vehicle according to claim 1.
5. This involves running a web application for centralized management of multiple industrial vehicles to launch a video management system, and The system receives camera images transmitted from the industrial vehicle, relays the received camera images to a user terminal, and displays the camera images as moving images on the screen of the video management system displayed on the web browser of the user terminal. A video management program for industrial vehicles that causes the processor of a video management device to execute it.