JP7751960B2 - Management device, management method, management program, and provision system - Google Patents

Description

The present invention relates to the management of recorded data in a system that collects recorded data and provides it to users who wish to use it, and in particular to technology for efficiently managing collected recorded data.

Conventionally, there have been systems that collect recording data, such as recording files recorded by imaging devices such as drive recorders, via a network.

For example, the data collection device disclosed in Patent Document 1 generates collection condition data that specifies the conditions (presence or absence of metadata) assigned to the recorded data to be used in advance, and sets this data in the image capture device. The image capture device then transmits recorded data that meets the collection conditions to the data collection device. This allows the data collection device to collect only recorded data that meets the conditions.

Japanese Patent Application Laid-Open No. 2020-38408

Now, suppose that recorded data is collected from a wide range of imaging devices, such as drive recorders, surveillance cameras, and personally owned smartphones, and that the data is provided to third parties upon request. In this case, more unused recorded data than expected may occur, resulting in unnecessary consumption of storage space on the management device that collects the recorded data.

In this case, for example, when a request for recorded data is received from a third party, one possible method would be to search for a camera that has recorded the requested data and send it directly to the user's terminal. In other words, the management device acts as an intermediary without collecting the recorded data.

However, the storage capacity of the imaging device is also limited. For example, dashcams and surveillance cameras record recorded data by overwriting it on the built-in storage medium, so when a request for use arises, it is possible that the recorded data that meets the requested conditions will be overwritten and lost.

In one aspect, the present invention aims to provide a management device, management method, management program, and provision system that efficiently manage collected recording data.

(1) A management device according to one aspect of the present disclosure includes: a storage unit that, upon receiving a provision request including specified conditions from a requesting device, acquires recorded data that meets the specified conditions from a providing device that provides the recorded data and stores the data in a storage device; an evaluation unit that provides the recorded data that meets the specified conditions from the storage device to the requesting device and evaluates the usage of the recorded data based on the number of times the recorded data is provided; and a deletion unit that deletes the recorded data from the storage device if the usage of the recorded data is low and meets predetermined conditions.

(2) In the management device described in (1) above, the recorded data may be associated with information indicating the detection target detected by image analysis of the recorded data, and the specified conditions may include the date and time the recorded data was taken, the location where the recorded data was taken, and information specifying the detection target detected from the recorded data.

(3) In the management device described in (1) above, if a predetermined detection target is detected as a result of image analysis of certain recorded data, the providing device may transmit the certain recorded data to the management device in association with the predetermined detection target, and the saving unit may save the recorded data in which the predetermined detection target was detected in a storage device upon receiving the recorded data from the providing device, and the deleting unit may not delete the recorded data in which the predetermined detection target was detected even if its usage rate is low and satisfies a predetermined condition.

(4) In the management device described in (2) above, the predetermined conditions for usage may be set according to the type of detection target.

(5) A management method according to one aspect of the present disclosure includes a computer receiving a provision request including specified conditions from a requesting device, acquiring recorded data that meets the specified conditions from a providing device that provides the recorded data and saving the data in a storage device, providing the recorded data that meets the specified conditions from the storage device to the requesting device, evaluating the usage of the recorded data based on the number of times the recorded data is provided, and deleting the recorded data from the storage device if the usage of the recorded data is low and meets the specified conditions.

(6) A management program according to one aspect of the present disclosure causes a computer to execute the following process when it receives a provision request including specified conditions from a requesting device: acquire recorded data that meets the specified conditions from a providing device that provides the recorded data, store the acquired data in a storage device; provide the recorded data that meets the specified conditions from the storage device to the requesting device; evaluate the usage of the recorded data based on the number of times the recorded data is provided; and, if the usage of the recorded data is low and meets the specified conditions, delete the recorded data from the storage device.

(7) One aspect of the provision system of the present disclosure is a provision system including a provision device that provides recorded data and a management device, wherein the management device, upon receiving a provision request including specified conditions from a requesting device, acquires recorded data that meets the specified conditions from the provision device and stores it in a storage device, provides the recorded data that meets the specified conditions from the storage device to the requesting device, evaluates the usage of the recorded data based on the number of times the recorded data is provided, and if the usage of the recorded data is low and meets the specified conditions, deletes the recorded data from the storage device.

You can efficiently manage the recorded data you collect.

FIG. 1 is a diagram illustrating a provision system according to an embodiment. FIG. 2 is a diagram illustrating an example of a functional block configuration of a management device according to an embodiment. FIG. 2 is a diagram illustrating a functional block configuration of a providing device according to an embodiment. 10 is a diagram illustrating an example of an operational flow of a recording data generation process executed by a control unit of a providing device according to an embodiment. FIG. 10A and 10B are diagrams illustrating examples of recorded data information according to an embodiment. FIG. 10 is a diagram illustrating a provision request according to the embodiment. 10 is a diagram illustrating an example of an operational flow of a recording data providing process executed by a control unit of a management device according to an embodiment; FIG. 10A and 10B are diagrams illustrating examples of recording data management information according to an embodiment. FIG. 10 is a diagram illustrating threshold information according to the embodiment. FIG. 10 is a diagram illustrating a detection target list according to the embodiment. FIG. 2 is a diagram illustrating an example of a hardware configuration of a computer for realizing a management device and a providing device according to an embodiment.

Several embodiments of the present invention will be described in detail below with reference to the drawings. Note that corresponding elements in multiple drawings will be designated by the same reference numerals.

Figure 1 is a diagram illustrating a provision system 100 according to an embodiment. In the provision system 100 of Figure 1, for example, a management device 101 and a provision device 102 that provides recorded data are connected via a network 105.

The management device 101 may be, for example, a computer such as a server that collects recording data from the provision device 102 and provides it to the terminal 103.

The providing device 102 is, for example, a device that provides recording data captured by a camera to the management device 101. The providing device 102 may include, for example, an in-vehicle device installed in a vehicle that provides recording data captured by a camera such as a drive recorder, a camera such as a surveillance camera, or a recording providing server that provides recording data captured by a camera.

Furthermore, the terminal 103 may be a device used by a user who receives the recording data provision service from the management device 101, and includes, for example, a smartphone, a tablet terminal, a mobile terminal such as a mobile computer, and a computer such as a personal computer. Note that the terminal 103 may also operate as the provision device 102.

In the provision system 100, when the management device 101 receives a request to provide recorded data from, for example, a terminal 103, it widely collects recorded data that meets the conditions specified in the provision request from various provision devices 102 (for example, in-vehicle devices, surveillance cameras, recording provision servers, personally owned smartphones, etc.) and stores it in a storage device. The management device 101 also provides the collected recorded data to the requesting terminal 103. Once collected, the recorded data may be stored in the storage device as is, as it may be used by other users, for example.

However, when storing recorded data in a storage device in this way, there may be recorded data that is used less than expected. In this case, the storage space of the storage device is wasted on recorded data that is used less frequently. Therefore, there is a need to provide technology that allows for efficient use of the storage capacity of storage devices.

One method for reducing the amount of recorded data stored in a storage device is, for example, for the management device 101 to, when it receives a provision request from a third party, search for a providing device 102 that has recorded data that meets the specified conditions included in the provision request, and then send the recorded data directly from that providing device 102 to the user's terminal. In other words, this method involves the management device 101 acting only as an intermediary without collecting the recorded data.

However, in providing devices 102 such as drive recorders and surveillance cameras, for example, recorded data is often overwritten and recorded on the built-in storage medium. In such cases, recorded data that meets the conditions specified in the provision request may have been overwritten and erased when the provision request is made. For this reason, it may be preferable to temporarily store recorded data for which a provision request has been made in the storage device of the management device 101.

In the embodiment described below, the management device 101 evaluates the usage of recorded data based on the number of times the recorded data is provided. If the usage of the recorded data is low and satisfies a predetermined condition, the management device 101 deletes the recorded data from the storage device. This prevents the storage area of the management device 101 from being overwhelmed by recorded data that is not often provided to users and has little utility value. The embodiment will be described in more detail below.

Figure 2 is a diagram illustrating an example of the functional block configuration of the management device 101 according to an embodiment. The management device 101 includes, for example, a control unit 201, a memory unit 202, and a communication unit 203. The control unit 201 includes, for example, a saving unit 211, an evaluation unit 212, and a deletion unit 213, and may also include other functional units. The memory unit 202 stores information such as a provision request 600, video recording data management information 800, and threshold information 900, which will be described later. The communication unit 203 communicates with other devices, such as the provision device 102 and terminal 103, according to instructions from the control unit 201. Details of each of these units and the information stored in the memory unit 202 will be described later.

Figure 3 is a diagram illustrating an example of the functional block configuration of the providing device 102 according to an embodiment. The providing device 102 includes, for example, a control unit 301, a storage unit 302, and a communication unit 303. The control unit 301 controls, for example, each unit of the providing device 102. The storage unit 302 stores, for example, information such as recorded data information 500, a provision request 600, and a detection target list 1000, which will be described later. The communication unit 303 communicates with other devices, such as the management device 101, in accordance with instructions from the control unit 301. Details of these functional units and the information stored in the storage unit 302 will be described later.

Next, we will explain the recording data generation process performed by the control unit 301 of the providing device 102.

Figure 4 is a diagram illustrating an example of the operational flow of the recording data generation process executed by the control unit 301 of the providing device 102 according to the embodiment. The control unit 301 may start the operational flow of Figure 4 when, for example, an instruction to execute the recording data generation process is input.

In S401, the control unit 301 of the providing device 102, for example, acquires recorded data. For example, if the providing device 102 is a photographing device such as a camera, it may acquire recorded data captured by its own device. Also, if the providing device 102 is a recorded data providing server that stores recorded data captured by a photographing device, the providing device 102 may acquire recorded data captured by a connected photographing device such as a surveillance camera and store it in the memory unit 302. In this case, the control unit 301 may acquire the recorded data to be processed from the recorded data stored in the memory unit 302.

In S402, the control unit 301 performs image analysis on the acquired recording data. For example, the control unit 301 divides the recording data into recording data of a predetermined length. The control unit 301 then executes a detection process to detect predetermined detection targets, such as objects and events, in each divided recording data, and determines whether the detection targets are captured in the recording data. The detection targets may be any targets that can be detected from the recording data, for example. In one example, detection targets include people, vehicles, animals, wheelchairs, signs, weather, etc.

The detection process can be performed using, for example, object detection technology, and various methods can be used, such as machine learning methods, methods using features such as local features, and matching methods such as template matching.

In S403, the control unit 301 associates additional information with the recording data. The additional information includes information about the recording data, such as information about the shooting date and time when the recording data was captured. The additional information also includes information about the shooting location where the recording data was captured. For example, if the recording device is a surveillance camera that captures images at a fixed location, information about the installation location may be recorded in the surveillance camera's storage device, and the control unit 301 of the providing device 102 can obtain the shooting location information by reading out the installation location information. Also, for example, if the recording device is a driving recorder that captures images while moving, a position sensor such as a GPS (Global Positioning System) can obtain location information corresponding to the time. The control unit 301 may then obtain the location information measured by the position sensor at the shooting date and time as the shooting location.

The control unit 301 also performs image analysis on the recorded data and acquires information about the detected target as additional information. Note that the additional information may be saved together with the recorded data as meta-information such as metadata of the recorded data, or may be saved as separate data associated with the recorded data.

At S404, the control unit 301 registers the record of the recording data associated with the additional information in the recording data information 500.

Figure 5 is a diagram illustrating recording data information 500 according to an embodiment. The recording data information 500 is stored, for example, in the providing device 102.

In the example of FIG. 5, the recording data information 500 contains records that associate a camera device identifier (ID), a recording data ID, recording data, and additional information. The camera device ID contains, for example, identification information for identifying the camera that captured the recording data corresponding to the record. The recording data ID contains, for example, an identifier for identifying the recording data corresponding to the record. The recording data contains, for example, information indicating the recording data corresponding to the record. The recording data may, for example, be information indicating the file name or storage location of the recording data. The additional information contains, for example, additional information associated with the recording data corresponding to the record. The additional information includes, for example, the date and time when the recording data corresponding to the record was captured, and information about the shooting location. The additional information also includes, for example, information about the detection target detected from the recording data.

Then, in the processing of S404, the control unit 301 registers, for example, a record in the recording data information 500 that associates the recording data to be processed with the additional information identified for the recording data.

In S405, the control unit 301 determines whether or not a request to provide recorded data has been received. For example, if the control unit 301 receives a request to provide recorded data from the management device 101, the control unit 301 may determine YES in S405, and the flow proceeds to S406. On the other hand, if a request to provide recorded data has not been received, the control unit 301 may determine NO in S405, and the flow returns to S401. Note that the request to provide includes, for example, a specification condition that specifies the recorded data for which provision is requested. The specification condition includes, for example, the shooting date and time when the recorded data was captured, the shooting location where the recorded data was captured, and information specifying the detection target detected from the recorded data.

Figure 6 is a diagram illustrating an example of a provision request 600 according to an embodiment. The provision request 600 includes, for example, the shooting date and time, the shooting location, and additional information as specification information. The shooting date and time of the provision request 600 is, for example, information specifying the shooting date and time when the video data requested to be provided was taken. The shooting location of the provision request 600 is, for example, information specifying the shooting location when the video data requested to be provided was taken. The additional information of the provision request 600 is information specifying the detection target that appears in the video data requested to be provided. For example, Figure 6 illustrates an example of provision request 600 requesting the provision of video data that was taken between 3:00 PM and 4:00 PM on April 10, 2020, the longitude and latitude of the shooting location is within a predetermined distance from (x, y), and includes the character "shika" as additional information.

In S406, the control unit 301 determines whether or not recorded data that meets the specified conditions specified in the provision request 600 is registered in the recorded data information 500. If, in S406, recorded data that meets the specified conditions specified in the provision request 600 is not registered in the recorded data information 500 (NO in S406), there is no recorded data to provide, so the flow returns to S401 and the control unit 301 repeats the process. On the other hand, if, in S406, recorded data that meets the specified conditions specified in the provision request 600 is registered in the recorded data information 500 (YES in S406), the flow proceeds to S407.

In S407, the control unit 301 provides, for example, the recording data that meets the specified conditions to the management device 101, and the flow returns to S401.

As described above, the providing device 102 according to the embodiment can associate additional information with recorded data and register it in the recorded data information 500. Furthermore, the providing device 102 can provide the recorded data specified in the provision request 600 to the management device 101.

Next, we will explain the process by which the management device 101 provides recorded data to the terminal 103.

Figure 7 is a diagram illustrating an example of the operational flow of the recording data provision process executed by the control unit 201 of the management device 101 according to an embodiment. For example, the control unit 201 of the management device 101 may start the operational flow of Figure 7 when an instruction to execute the recording data provision process is input.

In S701, the control unit 201 determines whether or not a provision request 600 has been received. For example, if a provision request 600 has not been received from the terminal 103 or the like in S701 (S701: NO), the flow proceeds to S707. On the other hand, if a provision request 600 has been received in S701 (S701: YES), the flow proceeds to S702.

In S702, the control unit 201 notifies the providing device 102 of the provision request 600. For example, upon receiving the provision request 600, the providing device 102 checks whether recorded data that meets the specified conditions included in the provision request 600 is registered in the recorded data information 500, and if so, provides the recorded data to the management device 101.

In S703, the control unit 201 collects, for example, from the providing device 102, recorded data that meets the specified conditions indicated in the provision request 600. For example, the control unit 201 receives the recorded data in response from the providing device 102 to the notification of the provision request 600.

At S704, the control unit 201 registers the record of the provided recording data in the recording data management information 800 and stores it in the storage unit 202.

Figure 8 is a diagram illustrating recording data management information 800 according to an embodiment. Recording data management information 800 contains, for example, records of recording data collected from the providing device 102, and the records include information indicating the degree of usage of the registered recording data.

In the example of FIG. 8, the recording data management information 800 contains records that associate the following information: a camera device ID, a recording data ID, recording data, additional information, the number of times provided, the collection date and time, and the frequency threshold. The camera device ID is, for example, an identifier that identifies the camera that captured the recording data corresponding to the record. The recording data ID is, for example, an identifier that identifies the recording data corresponding to the record. The recording data is, for example, information that indicates the recording data corresponding to the record, and may, for example, be information that indicates the file name or storage location of the recording data. The additional information is, for example, additional information associated with the recording data corresponding to the record. The additional information includes, for example, information about the shooting date and time and shooting location of the recording data corresponding to the record. The additional information also includes, for example, information about the detection target detected from the recording data corresponding to the record. The information registered in the recording data information 500 for the recording data of the record may be registered from the camera device ID to the additional information in the recording data management information 800.

The number of times the recorded data corresponding to the record has been provided is registered in the number of times of provision in the recorded data management information 800, for example. The collection date and time is registered, for example, as information on the date and time when the recorded data corresponding to the record was collected from the providing device 102. The frequency threshold is registered, for example, as a threshold for determining whether or not to delete the recorded data corresponding to the record. In one example, the frequency threshold may be a fixed value, and in another example, a threshold may be set for each type of recorded data. For example, the frequency threshold may be set in association with the type of additional information.

Figure 9 is a diagram illustrating threshold information 900 according to an embodiment. As shown in Figure 9, a frequency threshold may be set for additional information, for example. In one example, the frequency threshold can be set according to the value of the video. For example, the frequency threshold may be set so that the more valuable a video is, the longer it will be stored even if it is provided less frequently. For example, in Figure 9, a low frequency threshold is set for additional information representing a valuable detection target, such as once every 100 days if the additional information "wheelchair" is added, or once every 300 days if the additional information "only" is added.

Note that if the recorded data is associated with multiple pieces of additional information, a frequency threshold that represents the multiple pieces of additional information may be set. For example, the control unit 201 may use a frequency threshold that represents the multiple pieces of additional information detected from one piece of recorded data (e.g., the lowest frequency threshold) as the frequency threshold for that recorded data.

In S705, the control unit 201 provides the recording data to the requesting terminal 103. For example, the control unit 201 transmits to the requesting terminal 103, from among the recording data registered in the recording data management information 800, recording data that satisfies the specified conditions indicated in the provision request 600. Note that the recording data transmitted to the terminal 103 may include, for example, not only the recording data provided by the providing device 102 in response to the current provision request 600, but also recording data that has already been registered in the recording data management information 800.

In S706, the control unit 201 counts (e.g., counts) the number of times that recorded data has been provided to the terminal 103, and updates the number of times that data has been provided in the recorded data management information 800.

In S707, the control unit 201 evaluates the usage of the recorded data based on the number of times the recorded data has been provided, and determines whether there is any recorded data with a low usage rate. For example, the control unit 201 determines whether any recorded data whose provision frequency since the collection date and time is below the frequency threshold is registered in the recorded data management information 800. If any recorded data whose provision frequency since the collection date and time is below the frequency threshold is not registered in the recorded data management information 800 (NO in S707), the flow returns to S701. On the other hand, if any recorded data whose provision frequency since the collection date and time is below the frequency threshold is registered in the recorded data management information 800 (YES in S707), the flow proceeds to S708.

In S708, the control unit 201 deletes from the recording data management information 800 any recording data whose provision frequency since the collection date and time is equal to or less than the frequency threshold, and the flow returns to S701.

As described above, according to the embodiment, the management device 101 can delete recorded data according to the degree of use of the recorded data. This allows recorded data with high utility value to be carefully selected and retained. On the other hand, recorded data with low utility value can be deleted. Therefore, according to the embodiment, it is possible to prevent storage space from being consumed by recorded data with low utility value, and it is possible to use storage space efficiently.

In the above-described embodiment, for example, the storage unit 302 of the providing device 102 may store a list of detection targets for which detection is to be performed from the recorded data.

Figure 10 is a diagram illustrating a detection target list 1000 according to an embodiment. In the processes of S402 and S403 described above, the control unit 301 detects various detection targets as shown in the detection target list 1000, and associates additional information about the detected detection targets with the recorded data. This makes it possible to obtain information about what is shown in the recorded data from the additional information, thereby increasing the usefulness of the recorded data. Note that if a detection target object is not detected in the recorded data, the control unit 301 may associate additional information indicating that the detection target was not detected with the recorded data.

Furthermore, when the providing device 102 receives a request 600 for recording data containing certain additional information, it can determine whether the additional information is a detection target by referring to the detection target list 1000. This allows for rapid searches.

Furthermore, in the above-described embodiment, an example is described in which, when a provision request is received from the management device 101, the providing device 102 provides recorded data that meets the conditions indicated in the provision request, but the embodiment is not limited to this. For example, in another embodiment, the providing device 102 may transmit recorded data that meets specified transmission conditions to the management device 101.

For example, after registering the recording data in the recording data information 500 in S404, the management device 101 may transmit the recording data to the management device 101 if the registered recording data meets a predetermined transmission condition. The predetermined transmission condition may be, for example, the detection of a predetermined detection target, such as the presence of a rare detection target. For example, recording data that shows a deer jumping out into the road may be rarer than recording data that shows traffic lights and signs. Such rare footage may be difficult to obtain, so it may be desirable to collect and store it even if it is not used often. Furthermore, many providing devices 102, such as drive recorders, overwrite and delete previous recording data when their storage space becomes full, which results in the loss of rare footage that has been carefully captured. Therefore, the providing device 102 may be configured to immediately upload recording data that meets a predetermined transmission condition to the server.

For example, if the control unit 301 of the providing device 102 newly registers recorded data in which predetermined additional information (e.g., additional information indicating a rare detection target) was detected in the recorded data information 500 in S404, the control unit 301 of the providing device 102 may transmit the recorded data to the management device 101. This allows valuable recorded data to be efficiently collected by the management device 101.

Furthermore, in the above-described embodiment, the providing device 102 may associate information indicating the usefulness of the recorded data as additional information with the recorded data. For example, if the recording device for the recorded data is a drive recorder, the information indicating the usefulness may be information indicating that the proportion of the road captured is equal to or greater than a predetermined proportion.

For example, when recording data is collected, a large vehicle or similar object may be blocking the direction in which the recording data is being shot, obstructing the view and making it difficult to obtain information about the surrounding area. For this reason, if, for example, the area in the recording data in which the vehicle is visible is 20% or less of the shooting range, the control unit 301 of the providing device 102 may associate additional information (e.g., "good visibility") with the recording data, indicating that the view is likely to be good.

As another example, recorded data captured by a drive recorder attached to a large vehicle is likely to be captured from a higher position than a standard vehicle, and therefore has good visibility. Therefore, for example, if the recording device for the recorded data is a drive recorder, the information indicating usefulness may be that the model of the vehicle to which the drive recorder is attached is included in a predetermined model representing a large vehicle. In this case, the control unit 301 of the providing device 102 may associate the recorded data with additional information indicating a high likelihood of good visibility (e.g., "good visibility"), or may associate the recorded data with information indicating a large vehicle (e.g., "large vehicle"). The drive recorder may be connected to the providing device 102, such as an in-vehicle device, and information indicating the vehicle model may be stored in the memory unit 302 of the providing device 102.

Furthermore, for example, if the recording device for the recorded data is a drive recorder, the control unit 301 of the providing device 102 may associate information about the vehicle's driving lane (e.g., sidewalk side, center side, etc.) with the recorded data as additional information. This enables efficient operations such as, for example, when an accident occurs on the sidewalk side, collecting recording data captured by the drive recorder of a vehicle traveling on the sidewalk side.

In addition, while the above-described embodiment describes an example in which the control unit 201 of the management device 101 deletes recorded data collected in the recorded data management information 800 based on usage, the embodiment is not limited to this. For example, some recorded data is used according to the time of year, such as the season. For example, recorded data collected for use in spring tourist guides may not be used after the season changes to summer. One example would be footage of cherry blossoms in bloom. Such recorded data may not only be deleted based on usage in S407, but may also be deleted when the expiration date has passed, for example, in S404. In this way, in the embodiment, an expiration date may also be set for the recorded data, and recorded data may be deleted based on the expiration date in addition to deletion based on usage.

As another example, it may be desirable to use video that shows the latest situation. In this case, the control unit 301 may delete previously registered video data with the same additional information from the video data management information 800 when new video data with the same additional information is registered in the video data management information 800 in S404. This makes it possible to continue providing fresh video.

As described above, additional information indicating highly useful data that meets conditions set according to the intended use may be associated with recorded data. This allows the management device 101 to efficiently collect highly useful recorded data tailored to the intended purpose by specifying it using the additional information.

The above describes exemplary embodiments, but the embodiments are not limited to these. For example, the above operational flow is an example, and the embodiments are not limited to these. If possible, the operational flow may be executed with the order of processes changed, additional processes may be included, or some processes may be omitted.

Furthermore, while the above embodiment describes an example in which the providing device 102 associates additional information with recorded data, the embodiment is not limited to this. For example, in another embodiment, the association of additional information with at least some of the recorded data may be performed by the management device 101.

In the above embodiment, in the processing of S704, the control unit 201 operates, for example, as the storage unit 211. In addition, in the processing of S705 to S707, the control unit 201 operates, for example, as the evaluation unit 212. In the processing of S708, the control unit 201 operates, for example, as the deletion unit 213.

Figure 11 is a diagram illustrating the hardware configuration of a computer 1100 for realizing the management device 101 and the provision device 102 according to an embodiment. The hardware configuration of the computer 1100 in Figure 11 includes, for example, a processor 1101, memory 1102, storage device 1103, reading device 1104, communication interface 1106, and input/output interface 1107. The processor 1101, memory 1102, storage device 1103, reading device 1104, communication interface 1106, and input/output interface 1107 are connected to each other, for example, via a bus 1108.

The processor 1101 may be, for example, a single processor, or a multi-processor or multi-core. The processor 1101 provides some or all of the functions of the control unit 201 of the management device 101 or the control unit 301 of the provision device 102 described above by using the memory 1102 to execute a program that describes, for example, the procedures of the operational flow described above. For example, the processor 1101 of the management device 101 operates as the storage unit 211, evaluation unit 212, and deletion unit 213 by reading and executing programs stored in the storage device 1103.

Memory 1102 is, for example, semiconductor memory and may include a RAM area and a ROM area. Storage device 1103 is, for example, semiconductor memory such as a hard disk or flash memory, or an external storage device. Note that RAM is an abbreviation for Random Access Memory. ROM is an abbreviation for Read Only Memory.

Reader 1104 accesses removable storage medium 1105 in accordance with instructions from processor 1101. Removable storage medium 1105 is realized, for example, by a semiconductor device, a medium that inputs and outputs information magnetically, or a medium that inputs and outputs information optically. An example of a semiconductor device is a USB (Universal Serial Bus) memory. An example of a medium that inputs and outputs information magnetically is a magnetic disk. An example of a medium that inputs and outputs information optically is a CD-ROM, DVD, Blu-ray Disc, etc. (Blu-ray is a registered trademark). CD is an abbreviation for Compact Disc. DVD is an abbreviation for Digital Versatile Disk.

The memory unit 202 of the management device 101 and the memory unit 302 of the providing device 102 include, for example, memory 1102, storage device 1103, and removable storage medium 1105. The memory unit 202 of the management device 101 stores, for example, a provision request 600, video recording data management information 800, and threshold information 900. The memory unit 302 of the providing device 102 stores, for example, video recording data information 500, a provision request 600, and a detection target list 1000.

The communication interface 1106 communicates with other devices according to instructions from the processor 1101. For example, the communication interface 1106 of the management device 101 communicates with the providing device 102 and the terminal 103 according to instructions from the processor 1101. The communication interface 1106 of the providing device 102 communicates with the management device 101 according to instructions from the processor 1101, for example.

The input/output interface 1107 is, for example, an interface between an input device and an output device. Input devices are, for example, devices such as a keyboard, mouse, or touch panel that accept instructions from a user. Output devices are, for example, display devices such as a screen, and audio devices such as speakers.

In addition, in one example, the processor 1101 may be connected to a photographing device 1121 and a GPS device 1122. For example, the processor 1101 of the providing device 102 may be connected to a device such as a photographing device 1121 such as a drive recorder and a GPS device 1122.

Furthermore, each program according to the embodiment is provided to the management device 101 and the providing device 102 in the following form, for example.
(1) It is pre-installed in the storage device 1103.
(2) Provided by a removable storage medium 1105.
(3) Provided from a server such as a program server.

Note that the hardware configuration of the computer 1100 for realizing the management device 101 and the providing device 102 described with reference to FIG. 11 is an example, and embodiments are not limited to this. For example, part of the above-described configuration may be deleted, or new configuration may be added. Furthermore, in another embodiment, for example, some or all of the functions of the above-described control unit 201 and control unit 301 may be implemented as hardware using FPGA, SoC, ASIC, PLD, or the like. Note that FPGA is an abbreviation for Field Programmable Gate Array. SoC is an abbreviation for System-on-a-chip. ASIC is an abbreviation for Application Specific Integrated Circuit. PLD is an abbreviation for Programmable Logic Device.

A number of embodiments have been described above. However, the present invention is not limited to the above-described embodiments, and should be understood as including various modifications and alternative forms of the above-described embodiments. For example, various embodiments can be realized by modifying the components without departing from the spirit and scope of the present invention. The present invention also includes embodiments in which multiple components disclosed in the above embodiments are appropriately combined, embodiments in which some components are deleted from all of the components shown in the embodiments, or embodiments in which some components are added to the components shown in the embodiments.

100: Provision system 101: Management device 102: Provision device 103: Terminal 105: Network 201: Control unit 202: Memory unit 203: Communication unit 211: Saving unit 212: Evaluation unit 213: Deletion unit 301: Control unit 302: Memory unit 303: Communication unit 500: Recorded data information 600: Provision request 800: Recorded data management information 900: Threshold information 1000: Detection target list 1100: Computer 1101: Processor 1102: Memory 1103: Storage device 1104: Reading device 1105: Removable storage medium 1106: Communication interface 1107: Input/output interface 1108: Bus 1121: Imaging device 1122: GPS device

Claims (3)

a storage unit that, upon receiving a provision request including a specified condition from a requesting device, acquires video recording data that satisfies the specified condition from a providing device that provides video recording data, and stores the video recording data in a storage device;
an evaluation unit that provides the recording data that satisfies the specified condition from the storage device to the requesting device and evaluates the usage of the recording data based on the number of times the recording data has been provided;
a deletion unit that deletes the recorded data from the storage device when the usage rate of the recorded data is equal to or less than a predetermined threshold ;
the recorded data is associated with information indicating a detection target detected by image analysis of the recorded data,
the specified conditions include information specifying the shooting date and time of the recorded data, the shooting location of the recorded data, and the detection target detected from the recorded data;
The predetermined threshold is set according to the type of the detection target .
Management device. When a predetermined detection target is detected as a result of image analysis of certain recorded data, the providing device associates the certain recorded data with the predetermined detection target and transmits the certain recorded data to the management device regardless of the specified condition;
The management device according to claim 1, wherein the storage unit stores the recorded data in the storage device upon receiving the recorded data in which the predetermined detection target is detected from the providing device . A computer-implemented management method, the computer comprising:
When receiving a provision request including the specified conditions from the requesting device, the recording data providing device obtains the recording data that satisfies the specified conditions and stores the data in a storage device;
providing the recording data that satisfies the specified condition from the storage device to the requesting device, and evaluating the usage of the recording data based on the number of times the recording data has been provided;
If the usage of the recorded data is equal to or less than a predetermined threshold, the recorded data is deleted from the storage device;
the recorded data is associated with information indicating a detection target detected by image analysis of the recorded data,
the specified conditions include information specifying the shooting date and time of the recorded data, the shooting location of the recorded data, and the detection target detected from the recorded data;
The predetermined threshold is set according to the type of the detection target.
Management methods, including: