On-board server and data transfer method

Abstract

To more accurately transfer data captured by a camera mounted on a moving object.SOLUTION: An on-board server that acquires video data from a video recording device that records video data from a camera mounted on a moving object traveling on a track and transfers the video data to a center device installed outside the moving object receives, from the moving object, mobile object status information indicating the status of the moving object and an operation plan for the moving object when acquiring video request information from the center device, calculates a transfer deadline for each of the video data corresponding to the video request information using the mobile object status information and the operation plan for the video request information, and controls the transfer of the corresponding video data in order of the calculated transfer deadline closest thereto, the transfer including at least one of a transfer from the video recording device to the on-board server and a transfer from the on-board server to the center device.SELECTED DRAWING: Figure 11

Description

[Technical Field]

[0001] The present invention relates to an on-board server and a data transfer method, and more particularly to an on-board server and a data transfer method for transferring data captured by a camera mounted on a moving object. [Background technology]

[0002] There are many people who wish to use video data recorded by cameras mounted on moving objects such as trains from various perspectives, such as operation, passenger service, and maintenance. For example, in the case of trains, these include dispatchers, depot staff, station staff, and drivers of other trains. In recent years, the amount of information handled by cameras mounted on moving objects has been increasing, and the amount of data transferred from moving objects is also on the rise.

[0003] Patent document 1 discloses a recording transfer device in which, when transferring video data outside the mobile body, a second recording device suspends recording of video data from a first recording device, and a control device reads out video data from the second recording device in descending order of importance. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Patent No. 4603603 Summary of the Invention [Problem to be solved by the invention]

[0005] However, if the communication paths between the interior of a mobile vehicle or between the mobile vehicle and the ground are insufficient, there is a limit to the transfer of all the video footage captured by the multiple cameras on the mobile vehicle. In such cases, it is expected that the video footage will not be delivered to users in a timely manner. Furthermore, while it is possible to increase the communication volume limits on the communication paths between the interior of a mobile vehicle or between the mobile vehicle and the ground, this would incur considerable costs. Also, there are cases where this technology cannot be applied directly to existing mobile vehicles.

[0006] In the video recording transfer device of Patent Document 1, the ranking of importance is based solely on the convenience of the mobile unit, so the transfer of less important data that the user wants immediately is delayed.

[0007] In view of the above-mentioned problems, an object of the present invention is to provide an on-board server and a data transfer method that more accurately transfer data captured by a camera mounted on a moving object. [Means for solving the problem]

[0008] In order to achieve the above-mentioned object, one representative on-board server of the present invention is an on-board server that acquires video data from a video recording device that records video data from a camera mounted on a moving body running on a track, and transfers the video data to a center device installed outside the moving body, and when video request information is acquired from the center device, it receives from the moving body mobile body status information indicating the status of the moving body and an operation plan for the moving body, uses the mobile body status information and the operation plan for the video request information to calculate a transfer deadline for each of the video data corresponding to the video request information, and controls the transfer of the corresponding video data in order of the calculated transfer deadline closest, and the transfer includes at least one of transfer from the video recording device to the on-board server and transfer from the on-board server to the center device.

[0009] Furthermore, one of the data transfer methods of the present invention is a data transfer method using an on-board server that acquires video data from a video recording device that records video data from a camera mounted on a mobile body running on a track, and transfers the video data to a center device installed outside the mobile body, and includes the steps of: when video request information is acquired from the center device, receiving from the mobile body mobile body status information indicating the status of the mobile body and an operation plan for the mobile body; using the mobile body status information and the operation plan for the video request information to calculate a transfer deadline for each of the video data corresponding to the video request information; and controlling the transfer of the corresponding video data in order of the calculated transfer deadline nearest, wherein the transfer includes at least one of transfer from the video recording device to the on-board server and transfer from the on-board server to the center device. [Effects of the Invention]

[0010] According to the present invention, in the on-board server and data transfer method, data captured by a camera mounted on a moving object can be transferred more accurately. Problems, configurations, and effects other than those described above will become apparent from the following embodiments. [Brief explanation of the drawings]

[0011] [Figure 1] FIG. 1 is a block diagram of a computer system for implementing aspects according to an embodiment of the present disclosure. [Figure 2] FIG. 2 is a block diagram showing an example of a data transfer system to which the present invention is applied. [Figure 3] FIG. 3 is a diagram showing an example of the installation location of the camera in the present invention. [Figure 4] FIG. 4 is a diagram showing an example of device list information in the present invention. [Figure 5] FIG. 5 is a diagram showing an example of the composition state information in the present invention. [Figure 6] FIG. 6 is a diagram showing an example of the organization event information in the present invention. [Figure 7] FIG. 7 is a diagram showing an example of video request information in the present invention. [Figure 8] FIG. 8 is a diagram showing an example of operation plan information in the present invention. [Figure 9] FIG. 9 is a diagram showing an example of video list information in the present invention. [Figure 10] FIG. 10 is a diagram showing an example of transfer policy information in the present invention. [Figure 11] FIG. 11 shows an example of a flowchart according to the present invention. DETAILED DESCRIPTION OF THE INVENTION

[0012] An embodiment of the present invention will be described.

[0013] <Computer system for implementing aspects according to the embodiment> 1 is a block diagram of a computer system 1 for implementing aspects according to an embodiment of the present disclosure. The mechanisms and devices of various embodiments disclosed herein may be applied to any suitable computing system. Major components of computer system 1 include one or more processors 2, memory 4, terminal interface 12, storage interface 14, I / O (input / output) device interface 16, and network interface 18. These components may be interconnected via a memory bus 6, an I / O bus 8, a bus interface unit 9, and an I / O bus interface unit 10.

[0014] Computer system 1 may include one or more processing units 2A and 2B, collectively referred to as processors 2. Each processor 2 executes instructions stored in memory 4 and may include an on-board cache. In some embodiments, computer system 1 may include multiple processors, while in other embodiments, computer system 1 may be a single processing unit. Examples of processing units include a central processing unit (CPU), a field-programmable gate array (FPGA), a graphics processing unit (GPU), and a digital signal processor (DSP).

[0015] In some embodiments, memory 4 may include random-access semiconductor memory, storage devices, or storage media (either volatile or non-volatile) for storing data and programs. In some embodiments, memory 4 represents the entire virtual memory of computer system 1 and may include virtual memories of other computer systems connected to computer system 1 via a network. While memory 4 may be conceptually considered a single entity, in other embodiments, memory 4 may be a more complex organization, such as a hierarchy of caches and other memory devices. For example, memory may exist as multiple levels of caches, and these caches may be divided by function. As a result, one cache may hold instructions, while other caches hold non-instruction data used by the processor. Memory may also be distributed and associated with various different processing units, such as in a so-called NUMA (Non-Uniform Memory Access) computer architecture.

[0016] Memory 4 may store all or part of the programs, modules, and data structures that implement the functions described herein. For example, memory 4 may store latent factor identification application 50. In some embodiments, latent factor identification application 50 may include instructions or descriptions that execute the functions described below on processor 2, or may include instructions or descriptions that are interpreted by other instructions or descriptions. In some embodiments, latent factor identification application 50 may be implemented in hardware via semiconductor devices, chips, logic gates, circuits, circuit cards, and / or other physical hardware devices instead of or in addition to a processor-based system. In some embodiments, latent factor identification application 50 may include data other than instructions or descriptions. In some embodiments, cameras, sensors, or other data input devices (not shown) may be provided to communicate directly with bus interface unit 9, processor 2, or other hardware in computer system 1. Such a configuration may reduce the need for processor 2 to access memory 4 and the latent factor identification application.

[0017] Computer system 1 may include a bus interface unit 9 that facilitates communication between processor 2, memory 4, display system 24, and I / O bus interface unit 10. I / O bus interface unit 10 may couple to I / O bus 8 for transferring data to and from various I / O units. I / O bus interface unit 10 may communicate with multiple I / O interface units 12, 14, 16, and 18, also known as I / O processors (IOPs) or I / O adapters (IOAs), via I / O bus 8. Display system 24 may include a display controller, a display memory, or both. The display controller may provide video, audio, or both data to display device 26. Computer system 1 may also include one or more sensors or other devices configured to collect data and provide the data to processor 2. For example, computer system 1 may include environmental sensors that collect humidity data, temperature data, pressure data, etc., and motion sensors that collect acceleration data, movement data, etc. Other types of sensors may also be used. Display memory may be dedicated memory for buffering video data. The display system 24 may be connected to a display device 26, such as a standalone display screen, a television, a tablet, or a handheld device. In some embodiments, the display device 26 may include a speaker for rendering audio. Alternatively, the speaker for rendering audio may be connected to an I / O interface unit. In other embodiments, the functionality provided by the display system 24 may be implemented by an integrated circuit that includes the processor 2. Similarly, the functionality provided by the bus interface unit 9 may be implemented by an integrated circuit that includes the processor 2.

[0018] The I / O interface unit provides functionality for communicating with various storage or I / O devices. For example, the terminal interface unit 12 may be equipped with user I / O devices 20, such as user output devices such as a video display, a television with speakers, and user input devices such as a keyboard, a mouse, a keypad, a touchpad, a trackball, buttons, a light pen, or other pointing device. A user may use a user interface to enter input data or instructions into the user I / O devices 20 and the computer system 1 and receive output data from the computer system 1 by operating the user input devices. The user interface may be displayed on a display, played through speakers, or printed via a printer via the user I / O devices 20, for example.

[0019] Storage interface 14 may be attached to one or more disk drives or direct access storage devices 22 (typically magnetic disk drive storage devices, but may also be an array of disk drives or other storage devices configured to appear as a single disk drive). In some embodiments, storage device 22 may be implemented as any secondary storage device. The contents of memory 4 may be stored in storage device 22 and retrieved from storage device 22 as needed. Network interface 18 may provide a communications path that allows computer system 1 and other devices to communicate with each other. This communications path may be, for example, a network 30.

[0020] While computer system 1 shown in FIG. 1 includes a bus structure providing direct communication paths between processor 2, memory 4, bus interface 9, display system 24, and I / O bus interface unit 10, in other embodiments, computer system 1 may include point-to-point links, multiple hierarchical buses, parallel or redundant communication paths in a hierarchical, star, or web configuration. Furthermore, while I / O bus interface unit 10 and I / O bus 8 are shown as a single unit, computer system 1 may actually include multiple I / O bus interface units 10 or multiple I / O buses 8. Additionally, while multiple I / O interface units are shown isolating I / O bus 8 from various communication paths leading to various I / O devices, in other embodiments, some or all of the I / O devices may be directly connected to a single system I / O bus.

[0021] In some embodiments, computer system 1 may be a device that receives requests from other computer systems (clients) without a direct user interface, such as a multi-user mainframe computer system, a single-user system, or a server computer. In other embodiments, computer system 1 may be a desktop computer, a portable computer, a laptop, a tablet computer, a pocket computer, a telephone, a smartphone, or any other suitable electronic device.

[0022] <Block diagram> FIG. 2 is a block diagram showing an example of a data transfer system to which the present invention is applied.

[0023] The data transfer system shown in Fig. 2 includes a camera 101, a video recording device 110, a train information management device 115, an on-board server 120, and a center device 130. A moving object can be equipped with the camera 101, the video recording device 110, the train information management device 115, and the on-board server 120. Here, a train will be used as an example of a moving object. A train (train set) is an example of a moving object that can run on a fixed track.

[0024] The camera 101 is a camera that can be mounted at various locations on a train. For example, it is a camera that can capture images of the front, rear, interior, and sides of the train. That is, one train can be equipped with multiple cameras 101, and one car can be equipped with multiple cameras. Here, the camera 102 can be configured as a camera that obtains information by focusing incident light on an imaging element via a lens and an aperture. Examples of the imaging element include a CCD (Charge-Coupled Device) image sensor and a CMOS (Complementary Metal Oxide Semiconductor) image sensor. The images captured by the camera 101 may be either moving images or still images. For moving images, the frame rate can be set to, for example, 3 frames per second (3 fps) or more, or even 5 frames per second (3 fps) or more, depending on the purpose of capturing images with the camera 101.

[0025] The video recording device 110 is a device that records the video captured by the camera 101. It may be installed in each train car, or may be installed for each type of camera 101. Therefore, a single train can be equipped with multiple video recording devices 110. As the video recording device 110, for example, a recording medium such as an HDD (Hard Disk Drive) or an SSD (Solid State Drive) can be used as needed.

[0026] The train information management device 115 is a device that manages information about the train. Here, formation status information 116, formation event information 117, and operation plan information 118 are recorded.

[0027] The train set status information 116 is information indicating the status of the train, such as the train's position, speed, door open / close status, etc. The train's position can be expressed in kilometers, which indicates the distance from the starting point on the track.

[0028] The formation event information 117 is information indicating the details of an abnormal state that has occurred in the train, such as a door failing to open or close, or an emergency call button being pressed, etc.

[0029] The operation plan information 118 is information about the operation plan of the train. For example, it includes at least the stations that the train will pass through and their arrival and departure times. If a train is delayed, the operation plan information may be updated to reflect the delay. The operation plan information 118 may be obtained from the center device 130.

[0030] The on-board server 120 has a video transfer control function 125 and is a device that performs the processing shown in FIG. 11 , which will be described later. One on-board server 120 may be installed in each train, or two or more may be installed in each train depending on the situation. The on-board server 120 also records device list information 121, transfer policy information 122, video list information 123, video request information 124, train set status information 116, train set event information 117, and operation plan information 118. The train set status information 116, train set event information 117, and operation plan information 118 can be acquired from the train information management device 115.

[0031] The video transfer control function 125 particularly controls the transfer of video data from the video recording device 110 to the on-board server 120 and the transfer of video data from the on-board server 120 to the center device 130. The video transfer control function 125 includes a transfer deadline calculation unit that calculates the transfer deadline for video data, a transfer policy setting unit that creates a policy for transferring video data, etc. It may also include a transmitting unit that transmits data and a receiving unit that receives data.

[0032] The device list information 121 has information about each camera 101. Specifically, the device list information 121 is information for managing the installation location and type of each camera 101 on a train. The device list information 121 may also have information about the imaging range of the camera 101.

[0033] The transfer policy information 122 is information that defines a policy for transmitting data that is captured by each camera 101 and recorded in the video recording device 110. The transfer policy information 122 is determined by the processing of the on-board server 120 shown in FIG.

[0034] The video list information 123 is information showing a list of videos recorded in the video recording device 110. The video list information 123 includes, for each video, information related to the video, such as the video request name, purpose of use, shooting location, transfer deadline, and affiliation.

[0035] The video request information 124 is information on a video request related to the on-board server 120 provided on the train, among the video request information 131 of the center device 130. The video request information 124 includes information on the video, such as the video request name, user, purpose of use, location of use, and affiliation.

[0036] The center device 130 is a device installed in a location other than a train, which is a moving object. For example, it is installed in a specific location on the ground. The center device 130 can communicate with each on-board server 120 wirelessly or via a wire. Furthermore, the center device 130 can exchange information with each computer and communication device installed in the control room 141, each station (Station A 142, Station B 143, etc.), inspection yard 144, etc. Here, the center device 130 can acquire video requests from the control room 141, each station, and inspection yard 144 and construct video request information 131. Furthermore, the center device 130 can transmit video sent from the on-board server 120 in response to the video request to the usage location, such as the control room 141, each station, or inspection yard 144.

[0037] The video request information 131 of the center device 130 includes the video request information of all corresponding on-board servers 120. On the other hand, the video request information 124 to be sent to one on-board server 120 may be the video request information 124 related to that on-board server 120 among the video request information 131.

[0038] The train information management device 115, the on-board server 120, and the center device 130 can use the computer system 1 described with reference to FIG.

[0039] Next, the flow of video data will be explained using FIG.

[0040] The video captured by the camera 101 is recorded in the video recording device 110. The video data recorded in the video recording device 110 is then transferred to the on-board server 120 under the control of the video transfer control function 125 of the on-board server 120. The video data recorded in the on-board server 120 is further transferred to the center device 130 under the control of the video transfer control function 125 of the on-board server 120. Of the video data transferred to the center device 130, the necessary video data is sent to destinations such as the control room 141, each station (Station A 142, Station B 143, etc.), and inspection yard 144 in response to each request. In the control room 141, each station (Station A 142, Station B 143, etc.), and inspection yard 144, etc., the video data can be played back and used using applications installed on computers, etc.

[0041] Here, there is a limit to the amount of data that can be transferred when transferring video data from the video recording device 110 to the on-board server 120 and when transferring video data from the on-board server 120 to the center device 130. In other words, there are cases where it is not possible to secure the bandwidth required for the communication capacity for transfer. For this reason, the video transfer control function 125 of the on-board server 120 processes the transfer of video data appropriately.

[0042] <Example of camera installation location> Fig. 3 is a diagram showing an example of the installation locations of cameras in the present invention, which shows an example of the installation locations of cameras 101-1 to 101-8 that can be placed on a leading car 200 of a train.

[0043] Camera 101-1 is a camera that captures an image in front of driver's seat 201. In other words, it is possible to capture images of the surrounding railway conditions including the tracks, stations, etc. ahead in the direction of travel.

[0044] Cameras 101-2 to 101-5 are cameras that capture images of the vicinity of each door of lead car 200. For example, they capture images of the upper and lower sides of the doors on the outer side of lead car 200. In this case, it is possible to check the open / closed state of each door and the state of passengers getting on and off the doors.

[0045] Cameras 101-6 to 101-8 are cameras that capture images of the interior of lead car 200. For example, they capture images from the ceiling downwards. In the example of Fig. 3, three cameras are installed along the direction of travel so that the interior of the car can be comprehensively captured. In this case, it is possible to check the state of passengers inside the car and whether they have left any items behind.

[0046] <Example of device list information> Fig. 4 is a diagram showing an example of device list information in the present invention. Fig. 4 shows an example of the device list information 121 shown in Fig. 2, and stores information on the items "camera ID," "type," "vehicle," and "location."

[0047] "Camera ID" is the ID (identification code) of each camera 101. In FIG. 4, it is associated with each of the cameras 101-1 to 101-8 in FIG.

[0048] "Type" indicates the range that the corresponding camera 101 is capturing. "Front" indicates that the camera is capturing the front of the train, "car side" indicates that the camera is capturing the outside side of the train, and "inside" indicates that the camera is capturing the inside of the train.

[0049] "Vehicle" specifies the vehicle photographed by each camera 101. In the example of FIG. 4, the vehicle number is written and is shown to be "1." Here, vehicle number "1" indicates that it corresponds to the lead vehicle in FIG. 3.

[0050] "Location" indicates where the corresponding camera 101 is installed. In FIG. 4, it is possible to identify on which door the camera is installed, as shown by "Door 1"..."Door 4." It is also possible to identify in which part of the vehicle the camera is installed, as shown by "Center 1"..."Center 3."

[0051] In this way, the device list information 121 is information that identifies the position and shooting range of the camera 101. The device list information can be set in advance.

[0052] <Example of organization status information> 5 is a diagram showing an example of the train set status information in the present invention. Here, the status of train X is shown in the diagram. An example of the train set status information 116 shown in FIG. 2 in this status will be described.

[0053] Train X is currently running between Station A and Station B. The distance (position of Train X) at this time is 105 and is stored as the train set status information. The speed of Train X at this time is also stored as the train set status information. In addition, information on the status of each door of Train X is also stored as the train set status information. This information can be obtained from Train X.

[0054] In this way, the train set status information 116 indicates the status of the train, and this information can be generated by the train information management device 115.

[0055] <Example of organization event information> Fig. 6 is a diagram showing an example of the organization event information in the present invention. Fig. 6 shows an example of the organization event information 117 shown in Fig. 2, and stores information on the items of "event name," "occurrence time," "vehicle," and "equipment."

[0056] "Event name" is the name of the event that occurred. Figure 6 shows the events "Door close failure", "Door open failure", and "Emergency call". "Door close failure" indicates a state in which a door does not close despite an operation to close it. "Door open failure" indicates a state in which a door does not open despite an operation to open it. "Emergency call" indicates that a specific emergency call button was pressed as an operation to make an emergency call.

[0057] "Occurrence time" indicates the time when the event occurred.

[0058] "Vehicle" indicates information that identifies the vehicle in which the event occurred.

[0059] "Device" indicates information that identifies the device on which the event occurred, such as which door it is, which emergency call button it is, etc.

[0060] In this way, the train set event information 117 indicates the details of the occurrence of an abnormal state. This information can be detected in the train and can be generated by the train information management device 115.

[0061] <Example of video request information> Fig. 7 is a diagram showing an example of video request information in the present invention. Fig. 7 shows an example of the video request information 124 shown in Fig. 2, and stores information on the items of "video request name," "user," "purpose of use," "place of use," and "affiliation."

[0062] "Video request name" is the name of the video request. It is recommended to use a name that makes it easy to understand the content. In Figure 7, the following items are shown: "Passenger support," "Emergency call," "Lost item check," "Check lineside facilities," and "Check lineside abnormalities."

[0063] "User" indicates the user who will use the video. In Figure 7, the order is "Station staff," "Dispatcher," "Lost and Found Center," "Inspection Yard," and "Dispatcher."

[0064] "Purpose of use" indicates the purpose for using the video. It is divided into several types and is referenced when creating the transfer policy information 122. In Figure 7, three types are shown: "support," "operation," and "maintenance." "Support" refers to responding to customers and relating to passenger service. "Operation" refers to train operation. "Maintenance" refers to train maintenance. These can be classified by task, such as passenger service, train operation, and maintenance.

[0065] "Location of use" is the location where the video will be used. This information allows the setting of the video data transfer destination and the video data transfer deadline. Figure 7 shows examples of "next station," "terminal station," and "vehicle depot." In the case of "next station," the video data required until the train arrives at the next station can be transferred to the next station. In the case of "terminal station," the video data required until the train arrives at the terminal station can be transferred to the terminal station. In the case of "vehicle depot," the video data required until the train returns to the vehicle depot can be transferred to the vehicle depot.

[0066] "Belonging" is information indicating where the subject of the video belongs. In Figure 7, two belongings are shown: "vehicle" and "railway". "Vehicle" is information about the vehicle of that train. It indicates information about a subject that can only be photographed by the camera 101 installed on that train. "Railway" is information about the railroad line that the train passes through. It indicates information about a subject that can also be photographed by the camera 101 on another train.

[0067] In this way, the video request information 124 includes information such as the location and purpose of video use, and affiliation.

[0068] <Example of operation plan information> Fig. 8 is a diagram showing an example of operation plan information in the present invention. Fig. 8 shows an example of the operation plan information 118 shown in Fig. 2, and stores information on the items of "train number," "station," "arrival time," and "departure time."

[0069] "Train number" is the train number of the train. The same train may change during operation depending on the train's schedule.

[0070] "Station," "Arrival time," and "Departure time" indicate the time when the train arrives at the station or depot and the time when it departs.

[0071] In this way, the operation plan information 118 indicates the operation plan of the train. This information can be acquired from the train information management device 115. Note that the initial operation plan information 118 can be acquired from the center device 130.

[0072] <Example of video list information> Fig. 9 is a diagram showing an example of video list information in the present invention. Fig. 9 shows an example of the video list information 123 shown in Fig. 2, and stores information on the items of "video request name," "purpose of use," "location," "transfer deadline," and "affiliation."

[0073] The "video request name" is the same as the "video request name" in the video request information shown in FIG.

[0074] The "purpose of use" is the same as the "purpose of use" of the video request information shown in FIG.

[0075] "Location" is a location that indicates the relevant shooting range, and is information that identifies the corresponding camera 101. It corresponds to "Location" in the device list information shown in FIG. 4 or "Type" in the device list information shown in FIG. 4. The image of the corresponding camera 101 corresponds. In the example of FIG. 4, "Vehicle 1, Door 1," "Inside the vehicle," and "Front" are shown. Here, in the case of an emergency call, the camera 101 closest to where the emergency call button was pressed corresponds. FIG. 4 shows that the emergency call button corresponding to Door 1 of Vehicle 1 was pressed.

[0076] The "transfer deadline" is calculated by the on-board server 120 using information such as the "location of use" in the video request information shown in FIG. 7 and the operation plan information shown in FIG. 8. In FIG. 9, "Realtime," "10:13," and "23:59" are shown. "Realtime" indicates immediate real-time transfer. "Realtime" in FIG. 9 is an "emergency call." In FIG. 7, the "emergency call" does not specify a "location of use," so it indicates immediate transfer. "10:13" in FIG. 9 is a "check for lost items." For "check for lost items," the "location of use" is set to "terminal station" in FIG. 7. In this case, the operation plan in FIG. 8 indicates that train number P will arrive at station D, the terminal station, at "10:13," so this time is calculated. "23:59" in FIG. 9 is a "check for lineside facilities." For "check for lineside facilities," the "location of use" is set to "depot" in FIG. 7. In this case, the operation plan in FIG. 8 indicates arrival at base X as "23:59," so this time is calculated.

[0077] In addition, for the formation event information "door close failure" and "door open failure" shown in Fig. 6, the "purpose of use" can be "operation", the "location" can be the corresponding door, and the "transfer deadline" can be "realtime." In other words, for video related to the formation event information in Fig. 6, the video from camera 101 at the corresponding location can be transferred in real time for the purpose of operation.

[0078] Furthermore, the "transfer deadline" can take into account train delays. Specifically, one of the arrival time, departure time, and passing time at a specific station (for example, the next station) is obtained from the operation plan information 118. Then, the current position and speed information of the train from the formation status information 116 is used to calculate one of the arrival time, departure time, and passing time at the corresponding specific station. By comparing these, the current train delay amount can be calculated. The calculated delay amount is added to the arrival time at the usage location of the corresponding video data, making it possible to recalculate the "transfer deadline." This makes it possible to calculate the transfer deadline, including the current delay amount.

[0079] "Affiliation" is the same as "Affiliation" in the video request information shown in FIG.

[0080] In this way, the video list information 123 shows a list of videos to be transferred, and includes information such as "video request name," "purpose of use," "location," "transfer deadline," and "affiliation." The video list information 123 is calculated by the on-board server 120.

[0081] <Example of forwarding policy information> Fig. 10 is a diagram showing an example of transfer policy information in the present invention. Fig. 10 shows an example of the transfer policy information 122 shown in Fig. 2, and stores information on the items "purpose of use," "affiliation," and "policy." The upper part of Fig. 10 shows an example of a default transfer policy, and the lower part shows an example of a changed transfer policy.

[0082] The "purpose of use" is the same as the "purpose of use" of the video request information shown in FIG.

[0083] "Affiliation" is the same as "Affiliation" in the video request information shown in FIG.

[0084] "Policy" indicates guidelines for transferring video data. "Normal" indicates that all video data will be transferred as specified. "Degenerate" indicates that the amount of data will be reduced before being transferred. For example, the video quality may be reduced before being sent. It is also possible to send the data at a later time. "Postponed" indicates that the video data will not be transferred.

[0085] In this way, the forwarding policy information 122 makes it possible to determine a policy for each purpose of use and affiliation. Comparing the default forwarding policy at the top of Figure 10 with the changed forwarding policy at the bottom, the following changes have been made: The policy for "Support / Vehicle" has been changed from "Normal" to "Degenerate." The policy for "Support / Lineside" has been changed from "Normal" to "Suspended." The policy for "Maintenance / Vehicle" has been changed from "Normal" to "Degenerate." The policy for "Maintenance / Lineside" has been changed from "Normal" to "Suspended."

[0086] For example, the purpose of use "operation" is the status of a currently running train, so it is prioritized over "maintenance" and "support," which can be checked later. Also, the belonging "vehicle" is an item that can only be photographed by that train, so it is prioritized over "lineside," which can be photographed by other trains. Furthermore, for the purpose of use "maintenance" and "support," if the belonging is "vehicle," it is determined that "degeneration" is acceptable. In this way, by defining policies for purpose of use and affiliation, it is possible to change the transfer policy appropriately. It is possible to determine the method of changing these policies in advance for each purpose of use and affiliation. It is also possible to use AI (artificial intelligence) or other methods to determine the change method as it learns.

[0087] <Flowchart> 11 shows an example of a flowchart according to the present invention, which illustrates the processing of the video transfer control function 125 in the on-board server 120.

[0088] First, in step S101, a video request is acquired. The video request can be acquired from the video request information 124 shown in Fig. 2. A specific example of the video request information 124 is as explained in Fig. 7.

[0089] Next, in step S102, the state of the rolling stock is acquired. The state of the rolling stock can be acquired from the formation status information 116 and formation event information 117 shown in Fig. 2. Specific examples of the formation status information 116 and formation event information 117 are as described in Figs. 5 and 6.

[0090] Next, in step S103, the transfer video is listed. The transfer video list can be created based on the video request acquired in step S101 and the device list information 121 shown in Fig. 2. In other words, a list of video data for which a video request has been made is created from the video of the camera 101 corresponding to the on-board server 120 that performs this processing. The listed list information is constructed in video list information 123.

[0091] Next, in step S104, the transfer deadline is calculated. The transfer deadline can be calculated using the train formation status information 116, the operation plan information 118, etc. shown in FIG. 2. That is, the transfer deadline can be calculated taking into account the arrival time of the train at the location of use, etc. Furthermore, the transfer deadline can be set in real time for video data corresponding to the train formation event information 117. The calculated transfer deadline is added to the corresponding video data in the video list information 123. A specific example of the video list information 123 is as described in FIG. 9.

[0092] Next, in step S105, the videos to be transferred are sorted in order of purpose of use and deadline. This can be done by sorting the video list information with transfer deadlines created in step S104 in order of purpose of use and transfer deadline. Specifically, the list of video data can be rearranged in order of transfer deadline for each same purpose of use. Furthermore, sorting can also be done by classification in addition to purpose of use and transfer deadline. In this case, specifically, the list of video data can be rearranged in order of transfer deadline for each classification for each same purpose of use.

[0093] Next, in step S106, a default forwarding policy is set. The default forwarding policy is the initial forwarding policy, and in this case, it is sufficient to set it so that messages are sent in order of their deadlines as usual. A specific example is shown in the forwarding policy at the top of Figure 10.

[0094] Next, in step S107, the amount of data to be transferred is added. Here, the amount of data to be transferred is calculated when transferring data according to the list of video data created by sorting in step S105. For example, how much data needs to be transferred per hour to meet the transfer deadline is calculated.

[0095] Next, in step S108, it is determined whether or not the communication limit has been exceeded. The communication limit can be determined in advance taking into consideration the corresponding communication environment. For example, a set value for the communication limit for the amount of communication per hour can be determined in advance. Here, if the amount of data transferred calculated in step S107 exceeds the communication limit, the process proceeds to step S109. If the amount of data transferred does not exceed the communication limit, the process ends.

[0096] In step S109, the transfer policy is changed. The transfer policy can be changed depending on the purpose of use or affiliation, for example, when not transferring video data or when processing is performed to reduce the amount of video data to be transferred. Specific examples of the transfer policy change are as described in FIG. 10. The transfer policy may be changed taking into consideration the difference between the amount of data to be transferred calculated in step S107 and the communication limit used in step S108. After step S109, the process returns to step S107, and the amount of data to be transferred is added based on the changed transfer policy.

[0097] The transfer of video data will now be described. Video data is transferred in order of earliest transfer deadline according to the list of video data sorted in step S105. At this time, the transfer policy changed in step S109 is applied, and transfer processing is carried out based on that.

[0098] The process in Fig. 11 can be applied to the transfer of video data from the video recording device 110 to the on-board server 120 shown in Fig. 2, and the transfer of video data from the on-board server 120 to the center device 130. These can be performed based on a common transfer policy using a common communication upper limit, or they can be performed based on individual transfer policies by setting communication upper limits for each.

[0099] <Effects> According to the above-described embodiment, a transfer deadline is set and video is transferred in order of earliest transfer deadline, so even if multiple video usage requests become congested, the necessary video can be transferred at the timing when the video user uses it. Furthermore, by changing the transfer policy based on the purpose of use and affiliation so as not to exceed the communication limit, it is possible to transfer appropriate video data within the communication limit. Furthermore, the transfer deadline can be set appropriately taking into account the purpose of use and the operation plan. At this time, by taking into account the current train delay, it is possible to set the deadline more accurately.

[0100] The present invention is not limited to the above-described embodiments and includes various modifications. For example, the above-described embodiments have been described in detail to clearly explain the present invention, and the present invention is not necessarily limited to those including all of the described configurations. Furthermore, it is possible to replace part of the configuration of one embodiment with the configuration of another embodiment, or to add the configuration of another embodiment to the configuration of one embodiment. Furthermore, it is possible to add, delete, or replace part of the configuration of each embodiment with other configurations.

[0101] For example, although the description has been given using a train as an example of a moving body, the present invention can also be applied to moving bodies other than trains.

[0102] This specification also includes the disclosure of the following aspects. (Aspect 1) An on-board server that acquires video data from a video recording device that records video data from a camera mounted on a moving object traveling on a track, and transfers the video data to a center device installed outside the moving object, When video request information is acquired from the center device, mobile object status information indicating a status of the mobile object and an operation plan of the mobile object are received from the mobile object; calculating a transfer deadline for each of the video data corresponding to the video request information using the mobile object status information and the operation plan for the video request information; performing control to transfer the corresponding video data in order of the calculated transfer deadline; The on-board server is characterized in that the transfer includes at least one of transfer from the video recording device to the on-board server and transfer from the on-board server to the center device.

[0103] (Aspect 2) In the on-board server according to aspect 1, The on-board server is characterized in that the video request information is information including at least one of the location where the video is to be used, the purpose of use, and the affiliation.

[0104] (Aspect 3) In the on-board server according to aspect 1 or aspect 2, The on-board server is characterized in that the mobile object status information is information including at least one of the position, speed, and organization status of the mobile object.

[0105] (Aspect 4) In the on-board server according to any one of aspects 1 to 3, The on-board server is characterized in that the video request information includes information on the purpose of use of the video, and the method of calculating the transfer deadline is selectively changed depending on the purpose of use.

[0106] (Aspect 5) In the on-board server according to any one of aspects 1 to 4, The on-board server is characterized in that the video request information includes information on a location where the video is to be used, and the transfer deadline is calculated using an arrival time of the video at the location of use in the operation plan.

[0107] (Aspect 6) In the on-board server according to aspect 5, The on-board server is characterized in that the mobile object status information includes information on the position and speed of the mobile object, and calculates the current delay amount of the mobile object relative to the operation plan using one of the arrival time, departure time, and passing time for each specific location in the operation plan and the position and speed information of the mobile object from the mobile object status information, and the transfer deadline is calculated by adding the delay amount to the arrival time in the operation plan at the location where the video is to be used.

[0108] (Aspect 7) In the on-board server according to any one of aspects 1 to 6, The video request information includes the purpose of use of the video and information on the affiliation, An on-board server characterized in that a transfer policy is set that indicates guidelines for the transfer of video data for each purpose of use or affiliation of the video so as not to exceed a predetermined communication limit, and the transfer of video data is performed in accordance with the transfer policy in order of the data with the nearest transfer deadline.

[0109] (Aspect 8) A data transfer method using an on-board server, which acquires video data from a video recording device that records video data from a camera mounted on a moving object traveling on a track, and transfers the video data to a center device installed outside the moving object, comprising: receiving, from the mobile object, mobile object status information indicating a status of the mobile object and an operation plan of the mobile object when the image request information is acquired from the center device; calculating a transfer deadline for each of the video data corresponding to the video request information by using the mobile object status information and the operation plan for the video request information; and performing control to transfer the video data in order of the calculated transfer deadline, A data transfer method characterized in that the transfer includes at least one of a transfer from the video recording device to the on-board server and a transfer from the on-board server to the center device.

[0110] (Aspect 9) In the data transfer method according to aspect 8, The data transfer method is characterized in that the video request information is information including at least one of the location, purpose, and affiliation of the video.

[0111] (Aspect 10) In the data transfer method according to aspect 8 or aspect 9, A data transfer method, wherein the mobile object status information is information including at least one of the position, speed, and organization status of the mobile object.

[0112] (Aspect 11) In the data transfer method according to any one of aspects 8 to 10, The data transfer method is characterized in that the video request information includes information on the purpose of use of the video, and the method of calculating the transfer deadline is selectively changed depending on the purpose of use.

[0113] (Aspect 12) In the data transfer method according to any one of aspects 8 to 11, The data transfer method, wherein the video request information includes information on a location where the video is to be used, and the transfer deadline is calculated using an arrival time of the video at the location of use in the operation plan.

[0114] (Aspect 13) In the data transfer method according to aspect 12, The data transfer method is characterized in that the mobile object status information includes information on the position and speed of the mobile object, and the current delay amount of the mobile object relative to the operation plan is calculated using one of the arrival time, departure time, and passing time for each specific location in the operation plan and the position and speed information of the mobile object from the mobile object status information, and the transfer deadline is calculated by adding the delay amount to the arrival time in the operation plan at the location where the video is used.

[0115] (Aspect 14) In the data transfer method according to any one of aspects 8 to 13, The video request information includes the purpose of use of the video and information on the affiliation, A data transfer method characterized by setting a transfer policy that indicates guidelines for the transfer of video data for each purpose of use or affiliation of the video so as not to exceed a predetermined communication limit, and transferring the video data in accordance with the transfer policy in order of the data with the closest transfer deadline. [Explanation of symbols]

[0116] 1...computer system, 2...processor, 2A, 2B...processing device, 4...memory, 6...memory bus, 8...I / O bus, 9...bus interface unit, 10...I / O bus interface unit, 12...terminal interface unit, 14...storage interface, 16...I / O device interface, 18...network interface, 20...user I / O device, 22...storage device, 24...display system, 26...display device, 30...network, 50...latent factor feature Fixed application, 101, 101-1 to 101-8...camera, 110...video recording device, 115...train information management device, 116...train set status information, 117...train set event information, 118...operation plan information, 120...on-board server, 121...equipment list information, 122...transfer policy information, 123...video list information, 124...video request information, 125...video transfer control function, 130...center device, 131...video request information, 141...control room, 142...station A, 143...station B, 144...inspection yard, 200...leading car, 201...driver's seat

Claims

1. An on-board server that acquires video data from a video recording device that records video data from a camera mounted on a moving object traveling on a track, and transfers the video data to a center device installed outside the moving object, When video request information is acquired from the center device, mobile object status information indicating a status of the mobile object and an operation plan of the mobile object are received from the mobile object; calculating a transfer deadline for each of the video data corresponding to the video request information using the mobile object status information and the operation plan for the video request information; performing control to transfer the corresponding video data in order of the calculated transfer deadline; The on-board server is characterized in that the transfer includes at least one of transfer from the video recording device to the on-board server and transfer from the on-board server to the center device.

2. The on-board server according to claim 1, The on-board server is characterized in that the video request information includes at least one of the location where the video is to be used, the purpose of use, and the affiliation.

3. The on-board server according to claim 1, The on-board server is characterized in that the mobile object status information is information including at least one of the position, speed, and organization status of the mobile object.

4. The on-board server according to claim 1, The on-board server is characterized in that the video request information includes information on the purpose of use of the video, and the method of calculating the transfer deadline is selectively changed depending on the purpose of use.

5. The on-board server according to claim 1, The on-board server is characterized in that the video request information includes information on a location where the video is to be used, and the transfer deadline is calculated using an arrival time of the video at the location of use in the operation plan.

6. The on-board server according to claim 5, The on-board server is characterized in that the mobile object status information includes information on the position and speed of the mobile object, and calculates the current delay amount of the mobile object relative to the operation plan using one of the arrival time, departure time, and passing time for each specific location in the operation plan and the position and speed information of the mobile object from the mobile object status information, and the transfer deadline is calculated by adding the delay amount to the arrival time in the operation plan at the location where the video is to be used.

7. 2. The on-board server according to claim 1, The video request information includes the purpose of use of the video and information on the affiliation, An on-board server characterized in that a transfer policy is set that indicates guidelines for the transfer of video data for each purpose of use or affiliation of the video so as not to exceed a predetermined communication limit, and the transfer of video data is performed in accordance with the transfer policy in order of the data with the nearest transfer deadline.

8. A data transfer method using an on-board server, which acquires video data from a video recording device that records video data from a camera mounted on a moving object traveling on a track, and transfers the video data to a center device installed outside the moving object, comprising: receiving, when receiving video request information from the center device, mobile object status information indicating a status of the mobile object and an operation plan of the mobile object from the mobile object; calculating a transfer deadline for each of the video data corresponding to the video request information by using the mobile object status information and the operation plan for the video request information; and performing control to transfer the video data in order of the calculated transfer deadline, A data transfer method characterized in that the transfer includes at least one of a transfer from the video recording device to the on-board server and a transfer from the on-board server to the center device.

9. 9. The data transfer method according to claim 8, The data transfer method is characterized in that the video request information is information including at least one of the location, purpose, and affiliation of the video.

10. 9. The data transfer method according to claim 8, A data transfer method, wherein the mobile unit status information is information including at least one of the position, speed, and organization status of the mobile unit.

11. 9. The data transfer method according to claim 8, The data transfer method is characterized in that the video request information includes information on the purpose of use of the video, and the method of calculating the transfer deadline is selectively changed depending on the purpose of use.

12. 9. The data transfer method according to claim 8, The data transfer method, wherein the video request information includes information on a location where the video is to be used, and the transfer deadline is calculated using an arrival time of the video at the location of use in the operation plan.

13. 13. The data transfer method according to claim 12, The data transfer method is characterized in that the mobile object status information includes information on the position and speed of the mobile object, and the current delay amount of the mobile object relative to the operation plan is calculated using one of the arrival time, departure time, and passing time for each specific location in the operation plan and the position and speed information of the mobile object from the mobile object status information, and the transfer deadline is calculated by adding the delay amount to the arrival time in the operation plan at the location where the video is used.

14. 9. The data transfer method according to claim 8, The video request information includes the purpose of use of the video and information on the affiliation, A data transfer method characterized by setting a transfer policy that indicates guidelines for the transfer of video data for each purpose of use or affiliation of the video so as not to exceed a predetermined communication limit, and transferring the video data in accordance with the transfer policy in order of the data with the closest transfer deadline.

Images