WO2022100073A1

WO2022100073A1 - Information management systems and methods

Info

Publication number: WO2022100073A1
Application number: PCT/CN2021/097912
Authority: WO
Inventors: Yunlong Zhang
Original assignee: Zhejiang Dahua Technology Co., Ltd.
Priority date: 2020-11-10
Filing date: 2021-06-02
Publication date: 2022-05-19
Also published as: EP4232912A1; EP4232912A4; CN112749133A

Abstract

A method may include determining, based on an event record of an event, first event information associated with the event. The method may include determining, based on recording content regarding the event collected by at least one target recording device, second event information associated with the event. The method may further include determining, based on the first event information and the second event information, a corresponding relationship between the recording content and the event record, the corresponding relationship being used to retrieve, transmit, or store the recording content.

Description

INFORMATION MANAGEMENT SYSTEMS AND METHODS

CROSS-REFERENCE TO RELATED APPLICATION

This application claims priority of Chinese Patent Application No. 202011244308.2, filed on November 10, 2020, the contents of which are hereby incorporated by reference.

TECHNICAL FIELD

The present disclosure generally relates to information technology, and in particular, to information management systems and methods.

BACKGROUND

Recording devices, such as wearable cameras, can collect data (e.g., images, videos) about various events (e.g., traffic accidents, news events) . A docking station and/or a file management platform may store data received from the recording devices. A large amount of data in the docking station and/or the file management platform usually needs to be classified and managed manually, which is inefficient and leads to high manpower costs. Thus, it is desirable to develop systems and methods for information management.

SUMMARY

According to an aspect of the present disclosure, an information management system is provided. The information management system may include one or more recording devices, a docking station communicated with the one or more recording devices, and a file management platform communicated with the docking station and configured to store data. The docking station may be configured to obtain first event information associate with an event, wherein the first event information is determined based on an event record of the event. The docking station may be configured to determine, based on recording content regarding the event collected by at least one target recording device of the one or more recording devices, second event information associated with the event. The docking station may be further configured to determine, based on the first event information and the second event information, a corresponding relationship between the recording content and the event record, the corresponding relationship being used to retrieve, transmit, or store the recording content on the file management platform.

In some embodiments, the docking station may be further configured to obtain a storage address of the file management platform, the storage address corresponding to the event. The docking station may be further configured to cause the file management platform to store the recording content at the storage address based on the corresponding relationship.

In some embodiments, the first event information may include first event scenario information of the event. The second event information may include second event scenario information of the event. To determine, based on the first event information and the second event information, a corresponding relationship between the recording content and the event record, the docking station may be further configured to determine, based on the first event scenario information and the second event scenario information, the corresponding relationship between the recording content and the event record.

In some embodiments, the first event information may include a first label of the event or the at least one target recording device. The second event information may include a second label of the event or the at least one target recording device. To determine, based on the first event information and the second event information, a corresponding relationship between the recording content and the event record, the docking station may be further configured to determine, based on the first label and the second label, the corresponding relationship between the recording content and the event record.

In some embodiments, the second event information may be determined by performing speech recognition or text recognition on the recording content.

In some embodiments, one or more recording devices may include a plurality of recording devices. The docking station may be further configured to select, from the plurality of recording devices, the at least one target recording device based on the first event information.

In some embodiments, the first event information may include first position information of the event. To select, from the plurality of recording devices, the at least one target recording device based on the first event information, the docking station may be further configured to obtain second position information of the plurality of recording devices, and select, from the plurality of recording devices, the at least one target recording device based on the first position information and the second position information.

In some embodiments, the file management platform may be configured to create the event record of the event based on a reporting signal associated with the event.

In some embodiments, the docking station or the file management platform may be further configured to verify the recording content.

In some embodiments, to verify the recording content, the docking station or the file management platform may be further configured to receive a verification code from the at least one target recording device; and verify the recording content based on the verification code.

According to another aspect of the present disclosure, a method for information management is provided. The method may be implemented on a computing device having at least one processor and at least one storage device. The method may include determining, based on an event record of an event, first event information associated with the event. The method may include determining, based on recording content regarding the event collected by at least one target recording device, second event information associated with the event. The method may further include determining, based on the first event information and the second event information, a corresponding relationship between the recording content and the event record, the corresponding relationship being used to retrieve, transmit, or store the recording content.

In some embodiments, the method may further include obtaining a storage address of a file management platform, the storage address corresponding to the event. The method may further include storing the recording content at the storage address in the file management platform based on the corresponding relationship.

In some embodiments, the first event information may include first event scenario information of the event. The second event information may include second event scenario information of the event. The determining, based on the first event information and the second event information, a corresponding relationship between the recording content and the event record may include determining, based on the first event scenario information and the second event scenario information, the corresponding relationship between the recording content and the event record.

In some embodiments, the first event information may include a first label of the event or the at least one target recording device. The second event information may include a second label of the event or the at least one target recording device. The determining, based on the first event information and the second event information, a corresponding relationship between the recording content and the event record may include determining, based on the first label and the second label, the corresponding relationship between the recording content and the event record.

In some embodiments, the method may further include selecting, from a plurality of recording devices, the at least one target recording device based on the event record.

In some embodiments, the first event information may include first position information of the event. The selecting, from the plurality of recording devices, the at least one target recording device based on the first event information may include obtaining second position information of the plurality of recording devices; and selecting, from the plurality of recording devices, the at least one target recording device based on the first position information and the second position information.

In some embodiments, the method may further include creating the event record of the event based on a reporting signal associated with the event.

In some embodiments, the method may further include verifying the recording content.

According to another aspect of the present disclosure, a non-transitory computer-readable storage medium may include a set of instructions for file management. When executed by at least one processor, the set of instructions may direct the at least one processor to effectuate a method. The method may include determining, based on an event record of an event, first event information associated with the event. The method may include determining, based on recording content regarding the event collected by at least target one recording device, second event information associated with the event. The method may further include determining, based on the first event information and the second event information, a corresponding relationship between the recording content and the event record, the corresponding relationship being used to retrieve, transmit, or store the recording content.

Additional features will be set forth in part in the description which follows, and in part will become apparent to those skilled in the art upon examination of the following and the accompanying drawings or may be learned by production or operation of the examples. The features of the present disclosure may be realized and attained by practice or use of various aspects of the methodologies, instrumentalities and combinations set forth in the detailed examples discussed below.

BRIEF DESCRIPTION OF THE DRAWINGS

The present disclosure is further described in terms of exemplary embodiments. These exemplary embodiments are described in detail with reference to the drawings. These embodiments are non-limiting exemplary embodiments, in which like reference numerals present similar structures throughout the several views of the drawings, and wherein:

FIG. 1 is a schematic diagram illustrating an exemplary information management system according to some embodiments of the present disclosure;

FIG. 2 is a schematic diagram illustrating exemplary hardware and software components of a computing device according to some embodiments of the present disclosure;

FIG. 3 is a block diagram illustrating an exemplary file management platform according to some embodiments of the present disclosure;

FIG. 4 is a block diagram illustrating an exemplary docking station according to some embodiments of the present disclosure;

FIG. 5 is a flowchart illustrating an exemplary process for information management according to some embodiments of the present disclosure;

FIG. 6 is a flowchart illustrating an exemplary process for file management according to some embodiments of the present disclosure;

FIG. 7 is a flowchart illustrating an exemplary process for determining first event information according to some embodiments of the present disclosure;

FIG. 8 is a flowchart illustrating an exemplary process for uploading recording content to a file management directory according to some embodiments of the present disclosure; and

FIG. 9 illustrates an exemplary information management platform according to some embodiments of the present disclosure.

DETAILED DESCRIPTION

The following description is presented to enable any person skilled in the art to make and use the present disclosure, and is provided in the context of a particular application and its requirements. Various modifications to the disclosed embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other embodiments and applications without departing from the spirit and scope of the present disclosure. Thus, the present disclosure is not limited to the embodiments shown, but is to be accorded the widest scope consistent with the claims.

The terminology used herein is to describe particular example embodiments only and is not intended to be limiting. As used herein, the singular forms "a, " "an, " and "the" may be intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms "comprise, " "comprises, " and/or "comprising, " "include, " "includes, " and/or "including, " when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.

These and other features, and characteristics of the present disclosure, as well as the methods of operation and functions of the related elements of structure and the combination of parts and economies of manufacture, may become more apparent upon consideration of the following description with reference to the accompanying drawings, all of which form a part of this disclosure. It is to be expressly understood, however, that the drawings are for the purpose of illustration and description only and are not intended to limit the scope of the present disclosure. It is understood that the drawings are not to scale.

The flowcharts used in the present disclosure illustrate operations that systems implement according to some embodiments in the present disclosure. It is to be expressly understood, the operations of the flowchart may be implemented not in order. Conversely, the operations may be implemented in inverted order, or simultaneously. Moreover, one or more other operations may be added to the flowcharts. One or more operations may be removed from the flowcharts.

Recording devices are often used to collect recording content (e.g., images, videos, audios, texts) of one or more events and transmit the recording content to a docking station. The recording content in the docking station usually needs to be manually inspected and classified so that the recording content corresponding to the same event is stored in one category (e.g., a folder) . That is to say, whether different recording content belongs to one event needs to be determined manually, and then the recording content of the same event is then transmitted to a file management platform for storage. The conventional approach to manage the recording content collected by recording devices is inefficient.

An aspect of the present disclosure relates to an information management system. The information management system may include one or more recording devices, a docking station communicated with the one or more recording devices, and a file management platform. The docking station may obtain first event information associated with an event, wherein the first event information may be determined based on an event record of the event. The docking station may determine second event information associated with the event based on recording content regarding the event collected by at least one target recording device of the one or more recording devices. The docking station may further determine a corresponding relationship between the recording content and the event record based on the first event information and the second event information. The corresponding relationship between the recording content and the event record may indicate that the event record and the recording content relate to the same event. The corresponding relationship may be used to retrieve, transmit, or store the recording content.

For example, by determining the corresponding relationship between the recording content and the event record, the recording content and the event record corresponding to the same event may be associated. Further, the recording content may be stored in a storage address corresponding to the event record in the file management platform. In this way, the recording content of the event may be classified and stored in the corresponding storage address automatically, thereby improving the efficiency of information management and reducing human costs.

FIG. 1 is a schematic diagram illustrating an exemplary information management system according to some embodiments of the present disclosure. An information management system 100 may be configured to manage, store, retrieve various information (e.g., videos, audios, texts, images) associated with a plurality of events. In some embodiments, the information management system 100 may be applied in, such as a police station, a healthcare and medical center, a news agency, or the like.

As illustrated in FIG. 1, the information management system 100 may include a file management platform 110, a network 120, one or more recording devices 130 (e.g., 130-1, 130-2, 130-3, etc. ) , one or more docking stations 140 (e.g., 140-1, 140-2, 140-3, etc. ) , and an alarm center 150.

In some embodiments, two or more components of the information management system 100 may be connected to and/or communicate with each other via a wireless connection, a wired connection, or a combination thereof. The connection between the components of the information management system 100 may be variable. Merely by way of example, the alarm center 150 may be connected to the recording device (s) 130 and the file management platform 110 directly or via the network 120. The docking station (s) 140 may be connected to the recording device (s) 130 and the file management platform 110 directly or via the network 120.

In some embodiments, one docking station 140 may be connected to one or more of the recording device (s) 130, and one recording device 130 may be connected to one docking station 140. For example, as shown in FIG. 1, the recording devices 130-1 and 130-2 are both connected to the docking station 140-1, and the recording device 130-3 is connected to the docking station 140-3. As used herein, a recording device 130 and a docking station 140 connected to each other may be deemed as corresponding to each other. In some embodiments, the corresponding relationship between the docking station (s) 140 and the recording device (s) 130 may be determined manually by a user (e.g., an operator of the information management system 100) , or determined according to a default setting of the information management system 100, or determined by one or more components of the information management system 100. For example, the file management platform 110 may pre-allocate the recording device (s) 130 to the docking station (s) 140 to determine the corresponding relationship between the recording device (s) 130 and the docking station (s) 140.

The file management platform 110 may be used to manage and/or store information and/or data relating to the information management system 100. For example, as shown in FIG. 1, the file management platform 110 may be configured to store

files

11, 12, 13, etc., received from the docking station (s) 140. In some embodiments, the information management system 100 may be connected to a predetermined count of docking stations (e.g., 5, 10, 15 docking stations) . Other exemplary data stored in the file management platform 110 may include information relating to (e.g., event record (s) ) one or more events, the corresponding relationship between the docking station (s) 140 and the recording device (s) 130, a corresponding relationship between a recording device 130 and a user of the recording device 130, operation information of the recording device (s) 130 and the docking station (s) 140, or the like, or any combination thereof.

In some embodiments, the file management platform 110 may store recording content associated with an event, wherein the recording content may be collected by the recording device (s) 130 and processed by the docking station (s) 140. In some embodiments, the recording content of the event may be stored at a storage address corresponding to the event based on a corresponding relationship between the recording content and an event record of the event. More descriptions regarding the storage of the recording content may be found elsewhere in the present disclosure. See, e.g., FIGs. 5-8 and relevant descriptions thereof.

In some embodiments, the file management platform 110 may include one or more storage devices, such as a mass storage device, a removable storage device, a volatile read-and-write memory, a read-only memory (ROM) , or the like, or any combination thereof. Exemplary mass storage devices may include a magnetic disk, an optical disk, solid-state drives, etc. Exemplary removable storage devices may include a flash drive, a floppy disk, an optical disk, a memory card, a zip disk, a magnetic tape, etc. Exemplary volatile read-and-write memory may include a random-access memory (RAM) . Exemplary RAM may include a dynamic RAM (DRAM) , a double date rate synchronous dynamic RAM (DDR SDRAM) , a static RAM (SRAM) , a thyristor RAM (T-RAM) , and a zero-capacitor RAM (Z-RAM) , etc. Exemplary ROM may include a mask ROM (MROM) , a programmable ROM (PROM) , an erasable programmable ROM (EPROM) , an electrically-erasable programmable ROM (EEPROM) , a compact disk ROM (CD-ROM) , and a digital versatile disk ROM, etc. In some embodiments, the file management platform 110 may be implemented on a cloud platform. Merely by way of example, the cloud platform may include a private cloud, a public cloud, a hybrid cloud, a community cloud, a distributed cloud, an inter-cloud, a multi-cloud, or the like, or any combination thereof.

In some embodiments, the file management platform 110 may be implemented on a computing device 200 having one or more components illustrated in FIG. 2. In some embodiments, the file management platform 110 may be designed based on an open system architecture, which allows for integration with other systems (e.g., a video management system (VMS) , an evidence management system (EMS) ) .

The network 120 may facilitate the exchange of information and/or data. In some embodiments, one or more components of the information management system 100 (e.g., the file management platform 110, the recording device (s) 130, the docking station (s) 140) may transmit information and/or data to other component (s) of the information management system 100 via the network 120. For example, the alarm center 150 may transmit a reporting signal to the file management platform 110 via the network 120, and/or obtain position information from the recording device (s) 130 via the network 120. As another example, the recording device (s) 130 may transmit recording content to the docking station (s) 140 via the network 120. As yet another example, the docking station (s) 140 may transmit the recording content received from the recording device (s) 130 to the file management platform 110.

The network 120 may be or include any type network, such as a public network (e.g., the Internet) , a private network (e.g., a local region network (LAN) ) , a wired network, a wireless network (e.g., an 802.11 network, a Wi-Fi network) , a frame relay network, a virtual private network (VPN) , a satellite network, a telephone network, routers, hubs, switches, server computers, and/or any combination thereof. For example, the network 120 may include a cable network, a wireline network, a fiber-optic network, a telecommunications network, an intranet, a wireless local region network (WLAN) , a metropolitan region network (MAN) , a public telephone switched network (PSTN) , a Bluetooth ^TM network, a ZigBee ^TM network, a near field communication (NFC) network, or the like, or any combination thereof.

In some embodiments, the network 120 may be a wired or wireless private network of a particular entity (e.g., a police station, a hospital) . In some embodiments, the network 120 between different components of the information management system 100 may be of the same type or different types. For example, the network 120 between the recording device (s) 130 and the docking station (s) 140 may be a wireless local area network (WLAN) , and the network 120 between the file management platform 110 and the docking station (s) 140 may be a cable network.

Merely by way of example, a network 120-1 (not shown in FIG. 1) may be used between the file management platform 110 and the recording device (s) 130, a network 120-2 (not shown in FIG. 1) may be used between the recording device (s) 130 and the docking station (s) 140, and a network 120-3 (not shown in FIG. 1) may be used between the file management platform 110 and the docking station (s) 140. The networks 120-1, 120-2, and 120-3 may be of the same type or different types. For example, the speed of the network 120-1 may be relatively slow, and the speed of the network 120-3 may be relatively fast. In such cases, data transmission between the docking station (s) 140 and the file management platform 110 may be more efficient. In some embodiments, the network 120-1 may be, for example, a cellular network (e.g., 2G, 3G, 4G, or 5G) , etc. The network 120-2 may be, for example, a cable network, a Bluetooth network, a WLAN, etc. The network 120-3 may be, for example, a broadband network, an optical fiber network, etc.

In some embodiments, there may be no wireless network between the recording device (s) 130 and other components of the information management system 100 (e.g., the docking station (s) 140 and/or the file management platform 110) . For example, the recording device 130 may be in communication with the docking station (s) 140 and/or the file management platform 110 by, for example, a USB connection. Data collected by the recording device (s) 130 may be transmitted to the docking station (s) 140, and the docking station (s) 140 may transmit the data to the file management platform 110. In this way, data collected by the recording device (s) 130 may be transmitted to the file management platform 110 efficiently.

A recording device 130 may be used to collect data relating to one or more events that happened in various scenarios, e.g., a traffic accident, a fire disaster, a press conference, a competition. The data collected by the recording device 130 be in the form of text, an image, an audio, a video, or the like, or any combination thereof. In some embodiments, the recording device 130 may be a wearable or portable recording device. Exemplary wearable or portable recording devices may include a wearable camera, a wearable voice recorder, a smart watch, a smart bracelet, a smart footgear, smart glasses, a smart helmet, smart clothing, a smart backpack, a smart accessory, a smart phone, or the like, or any combination thereof. Merely by way of example, the recording device 130 may be a video recorder used by law enforcement officers (e.g., policemen) . The video recorder may have the functions of a digital camera and a microphone, which may be used to record the dynamic and static scene during the law enforcement process.

In some embodiments, a recording device 130 may be carried and/or operated by a user when it collects data relating to an event. For example, the recording device 130 may be worn on the torso of a user, or built into a helmet or glasses of the user. In some embodiments, the recording device 130 may be carried by a device (e.g., a vehicle) or mounted in a place for collecting data relating to an event. Optionally, the recording device 130 may be controlled remotely. The vehicle may include a horse, a carriage, a rickshaw (e.g., a wheelbarrow, a bike, a tricycle, etc. ) , a car (e.g., a taxi, a bus, a private car, etc. ) , a train, a subway, a vessel, an aircraft (e.g., an airplane, a helicopter, a space shuttle, a rocket, a hot-air balloon, etc. ) , or the like, or any combination thereof. For example, a camera may be carried by an unmanned aerial vehicle to move to the position where an event occurs to collect data of the event.

In some embodiments, a recording device 130 may include an image data acquisition module (e.g., a camera) , a microphone, a display, a connection module, a positioning module, one or more sensors (e.g., a gyrometer, an accelerometer, an altimeter, a pulse oximeter, a pedometer) , or the like, or any combination thereof. The connection module may be used to connect to another device. For example, the connection module may include a micro-USB port, a wireless connection module, and/or a charge port. The wireless connection module may include a

module, a

module, and/or a cellular module to implement wireless technologies (e.g.,

or cellular (e.g., 2G, 3G, 4G, or 5G) technologies) . In some embodiments, the recording device 130 may transmit recording content to another device (e.g., a docking station 140, the file management platform 110, or another storage device) via the connection module.

The positioning module may be configured to locate the recording device 130 and/or a user of the recording device 130. The positioning module may include a global positioning system (GPS) module, a global navigation satellite system (GLONASS) , a compass navigation system (COMPASS) , a BeiDou navigation satellite system, a Galileo positioning system, a quasi-zenith satellite system (QZSS) , etc. In some embodiments, the recording device 130 may communicate with another positioning device to determine the position of the recording device 130 and/or the user of the recording device. In some embodiments, the recording device 130 may transmit the positioning information to one or more other components of the information management system 100 (e.g., the file management platform 110, the alarm center 150) intermittently (e.g., periodically) or in real time.

A docking station 140 may be connected to one or more of the recording device (s) 130, and serve as an intermediate device between the connected recording device (s) 130 and the file management platform 110. For example, the docking station 140 may be configured to receive recording content from the connected recording device (s) 130, analyze the recording content, and cause the file management platform 110 to store the recording content based on the analysis result. In some embodiments, the docking station 140 may be configured to determine a corresponding relationship between recording content transmitted from a recording device 130 and an event record transmitted from the file management platform 110 if the recording content and the event record relate to the same event. The docking station 140 may further cause the file management platform 110 to store the recording content based on the corresponding relationship, for example, the recording content may be stored at a storage address corresponding to the event record based on the corresponding relationship.

In some embodiments, the docking station 140 may transmit recording content collected by the connected recording device (s) 130 to the file management platform 110 intermittently (e.g., periodically) or in real time. In some embodiments, the docking station 140 may include a display, through which a user may retrieve, review, and/or modify data (e.g., recording content) associated with events.

The alarm center 150 may be configured to receive a reporting signal associated with an event (e.g., a traffic accident, a fire disaster) . The reporting signal may be used to report the occurrence or a portability of occurrence of the event, which may be sent by a reporter or a monitoring device (e.g., a smoke transducer) . In some embodiments, the alarm center 150 may include, for example, a call center, an alarm center of a fire station, a police station, or the like, or any combination thereof. In some embodiments, the alarm center 150 may be configured to create an event record based on the reporting signal. In some embodiments, the alarm center 150 may obtain position information from the recording device (s) 130.

It should be noted that the above description of the information management system 100 is merely provided for the purposes of illustration, and not intended to limit the scope of the present disclosure. For persons having ordinary skills in the art, multiple variations and modifications may be made under the teachings of the present disclosure. However, those variations and modifications do not depart from the scope of the present disclosure. In some embodiments, the information management system 100 may include one or more additional components and/or one or more components of the information management system 100 described above may be omitted. For example, the alarm center 150 may be omitted. As another example, the information management system 100 may include multiple file management platforms 110, each of which is connected to one or more of the docking station (s) 140.

Additionally or alternatively, two or more components of the information management system 100 may be integrated into a single component. For example, the alarm center 150 may be integrated into the file management platform 110. A component of the information management system 100 may be implemented on two or more sub-components. In addition, the connections between the components of the information management system 100 as shown in FIG. 1 are illustrative, and can be modified according to an actual need. Merely by way of example, the recording device (s) 130 may be connected to the file management platform 110 directly or via the network 120. As another example, a recording device 130 may be connected to multiple docking stations 140.

FIG. 2 is a schematic diagram illustrating exemplary hardware and software components of a computing device 200 according to some embodiments of the present disclosure.

In some embodiments, the computing device 200 may be used to implement the information management system 100 for the present disclosure. For example, the computing device 200 may implement any component (e.g., the file management platform 110, a docking station 140, a recording device 130, the alarm center 150) of the information management system 100 as described herein. In FIG. 2, only one such computing device is shown purely for convenience purposes. One of ordinary skill in the art would understand at the time of filing of this application that the computer functions relating to the information management system 100 as described herein may be implemented in a distributed fashion on a number of similar platforms, to distribute the processing load.

The computing device 200, for example, may include COM ports 250 connected to and from a network connected thereto to facilitate data communications. The computing device 200 may also include a processor 220, in the form of one or more processors, for executing program instructions. For example, the processor 220 may include interface circuits and processing circuits therein. The interface circuits may be configured to receive electronic signals from a bus 210, wherein the electronic signals encode structured data and/or instructions for the processing circuits to process. The processing circuits may conduct logic calculations, and then determine a conclusion, a result, and/or an instruction encoded as electronic signals. Then the interface circuits may send out the electronic signals from the processing circuits via the bus 210.

The computing device 200 may include a program storage and a data storage of different forms, for example, a disk 270, and a read-only memory (ROM) 230, or a random access memory (RAM) 240, for various data files to be processed and/or transmitted by the computing device. The computing device 200 may also include program instructions stored in the ROM 230, the RAM 240, and/or another type of non-transitory storage medium to be executed by the processor 220. The methods and/or processes of the present disclosure may be implemented as the program instructions. The computing device 200 may also include an I/O component 260, supporting input/output between the computer and other components therein such as a user interface element (not shown in FIG. 2) . The computing device 200 may also receive programming and data via network communications.

Merely for illustration, only one processor 220 is described in the computing device 200. However, it should be noted that the computing device 200 in the present disclosure may also include multiple processors, thus operations and/or method steps that are performed by one processor 220 as described in the present disclosure may also be jointly or separately performed by the multiple CPUs/processors. For example, if in the present disclosure the processor 220 of the computing device 200 executes both step A and step B, it should be understood that step A and step B may also be performed by two different processors jointly or separately in the computing device 200 (e.g., the first processor executes step A and the second processor executes step B, or the first and second processors jointly execute steps A and B) .

FIG. 3 is a block diagram illustrating an exemplary file management platform according to some embodiments of the present disclosure. The file management platform 110 may include a generation module 310, a selection module 320, a determination module 330, and a storage module 340. The modules may be hardware circuits of all or part of the file management platform 110. The modules may also be implemented as an application or set of instructions read and executed by the file management platform 110. Further, the modules may be any combination of the hardware circuits and the application/instructions. For example, the modules may be part of the file management platform 110 when the file management platform 110 is executing the application/set of instructions.

The generation module 310 may be configured to create an event record of an event. The event may include various incidents or occurrences (e.g., a traffic accident, family violence, etc. ) . The event record refers to a record describing the event. For example, the event record may include a position where the event occurs (or referred to as an event position or first position information) , a time when the event occurs (or referred to as an event time or first time information) , an event type, one or more entities involved in the event, the cause of the event, a severity degree of the event, or the like, or any combination thereof. More descriptions regarding the generation of the event record may be found elsewhere in the present disclosure. See, e.g., operation 510 and the relevant descriptions thereof.

The selection module 320 may be configured to select one or more target recording devices from a plurality of recording devices based on the event record of the event. For example, the selection module 320 may select the target recording device (s) randomly from the recording devices. As another example, a corresponding relationship between the target recording device (s) and a docking station 140 may be pre-determined and stored in a storage device (e.g., the ROM 230, the RAM 240, the disk 270) . The selection module 320 may determine the target recording device (s) from the recording devices based on the corresponding relationship obtained from the storage device. As yet another example, the selection module 320 may determine the target recording device (s) based on the event position of the event (or referred to as first position information) . More descriptions regarding the selection of the target recording device (s) may be found elsewhere in the present disclosure. See, e.g., operation 520 and the relevant descriptions thereof.

The determination module 330 may be configured to determine the first event information associated with the event based on the event record of the event. For example, the determination module 330 may determine the first event information by parsing the event record of the event. The determination module 330 may be further configured to a corresponding relationship between the recording content and the event record based on the first event information and second event information of the event. More descriptions regarding the determination of the first event information and the corresponding relationship may be found elsewhere in the present disclosure. See, e.g.,

operations

530 and 550 and the relevant descriptions thereof.

The storage module 340 may be configured to store the recording content at the storage address corresponding to the event in the file management platform 110 based on the corresponding relationship. More descriptions regarding the storage of the recording content may be found elsewhere in the present disclosure. See, e.g., operation 560 and the relevant descriptions thereof.

FIG. 4 is a block diagram illustrating an exemplary docking station according to some embodiments of the present disclosure. The docking station 140 may include a selection module 410, a determination module 420, and a transmission module 430. The modules may be hardware circuits of all or part of the docking station 140. The modules may also be implemented as an application or set of instructions read and executed by the docking station 140. Further, the modules may be any combination of the hardware circuits and the application/instructions. For example, the modules may be the part of the docking station 140 when the docking station 140 is executing the application/set of instructions.

The selection module 410 may be configured to select one or more target recording devices from a plurality of recording devices based on the event record of the event. More descriptions regarding the selection of the target recording device (s) may be found elsewhere in the present disclosure. See, e.g., operation 520 and the relevant descriptions thereof.

The determination module 420 may be configured to determine the first event information associated with the event based on the event record of the event. Additionally or alternatively, the determination module 420 may be configured to determine the second event information associated with the event based on recording content regarding the event collected by the target recording device (s) . Additionally or alternatively, the determination module 420 may be further configured to determine a corresponding relationship between the recording content and the event record based on the first event information and the second event information. More descriptions regarding the determination of the first event information and the corresponding relationship may be found elsewhere in the present disclosure. See, e.g.,

operations

530 and 550 and the relevant descriptions thereof.

The transmission module 430 may be configured to transmit information and/or instructions to one or more other components of the information management system 100. For example, the transmission module 430 may transmit the recording content of the event to the file management platform 110 and direct the file management platform 110 to store the recording content at a storage address corresponding to the event. More descriptions regarding the transmission of information and/or instructions may be found elsewhere in the present disclosure. See, e.g., operation 560 and the relevant descriptions thereof.

It should be noted that the above description of the file management platform 110 and the docking station 140 is provided for the purposes of illustration, and is not intended to limit the scope of the present disclosure. For persons having ordinary skills in the art, multiple variations and modifications may be made under the teachings of the present disclosure. However, those variations and modifications do not depart from the scope of the present disclosure. In some embodiments, any module mentioned above may be divided into two or more units. In some embodiments, one or more of the modules mentioned above may be omitted. For example, one or more of the generation module 310, the selection module 320, and the selection module 410 may be omitted. In some embodiments, one or more additional modules may be added. For example, the docking station 140 may further include an encryption module configured to encrypt information and/or a decryption module configured to decrypt information. As another example, the file management platform 110 and/or the docking station 140 may further include a verification module configured to verify the recording content before or after the recording content is stored at the storage address.

FIG. 5 is a flowchart illustrating an exemplary process for information management according to some embodiments of the present disclosure. In some embodiments, process 500 may be executed by the information management system 100. For example, the process 500 may be implemented as a set of instructions (e.g., an application) stored in a storage device (e.g., the ROM 230, the RAM 240) . In some embodiments, one or more of the recording device (s) 130, the docking station (s) 140, and the file management platform 110 may be used to execute the set of instructions and may accordingly be directed to perform the process 500 in the information management system 100.

In 510, an event record of an event may be created. In some embodiments, operation 510 may be performed by the file management platform 110 (e.g., the generation module 310) or the alarm center 150.

The event may include various incidents or occurrences. For example, the event may be an event that needs to be handled by law enforcement personnel (e.g., a police officer) , such as a traffic accident, a fire disaster, a theft, or the like. As another example, the event may be an event that needs to be followed up by media personnel (e.g., a journalist) , such as family violence, a rescue, a robbery, a competition, or the like.

The event record refers to a record describing the event. For example, the event record may include a position where the event occurs (or referred to as an event position or first position information) , a time when the event occurs (or referred to as an event time or first time information) , an event type, one or more entities involved in the event, the cause of the event, a severity degree of the event, or the like, or any combination thereof. In some embodiments, the event record may include descriptions about the event, for example, paragraph (s) , sentence (s) , keyword (s) , etc. Exemplary keyword (s) may relate to the event position, the event time, the event type, the one or more entities involved in the event, the cause of the event, the severity degree of the event, or the like, or any combination thereof. In some embodiments, the event record may have a standard format. In some embodiments, the event record may include an event label (or referred to as a label of the event) . For example, the event label may include an identification number (e.g., including one or more values and/or symbols) that can be used to uniquely identify the event.

In some embodiments, the event may be reported to the alarm center 150 by a reporting signal regarding the event. The event record may be created based on the reporting signal of the event. The reporting signal may be used to report the occurrence or a portability of the occurrence of the event. The reporting signal may be in the form of a phone call, a letter (e.g., an email) , a massage, or the like. The reporting signal may include information describing the event, such as the event position, the event time, the event type, the severity degree of the event, or the like, or any combination thereof. In some embodiments, the reporting signal may at least include the event position and the event time.

In some embodiments, the reporting signal may be sent by a reporter associated with the event. For example, a driver may send a reporting signal regarding a traffic accident to an alarm center of a police station using a mobile telephone. Merely by way of example, the reporting signal may include “I had a traffic accident at an intersection of Road A and Road B at 9 a. m. ” As another example, the reporting signal may be sent by a monitoring device (e.g., a smoke transducer, a gas leakage sensor, a photoelectric alarm) when the monitoring device detects the occurrence of the event. For example, a smoke transducer may send a reporting signal regarding a fire disaster to an alarm center of a fire station when it detects the fire disaster.

In some embodiments, the alarm center 150 may transmit the reporting signal to the file management platform 110. The file management platform 110 may generate the event record of the event based on the reporting signal. For example, the file management platform 110 may generate the event record of the event by performing recognition (e.g., text recognition, voice recognition) on the reporting signal. Alternatively, the alarm center 150 may generate the event record of the event based on the reporting signal and then transmit the event record to the file management platform 110 for storage and/or further processing.

In some embodiments, the alarm center 150 or the file management platform 110 may create the event record based on information associated with the event provided by a user (e.g., a user of a recording device) . For example, a police officer may send information associated with the event to the alarm center 150 or the file management platform 110 via his/her recording device or another terminal device when he/she encounters the event. As another example, the police officer may input the information associated with the event to the alarm center 150 or the file management platform 110 via an input component of the alarm center 150 or the file management platform 110.

In some embodiments, data of the event (e.g., the event record, recording content collected by one or more recording devices) may be stored in a storage address in the file management platform 110. The storage address may be assigned to the event automatically by the file management platform 110 (e.g., in response to the reporting signal) or manually by a user. The storage address may include a storage path, a storage directory (e.g., a file management directory as described in connection with operation 601) , a file location, an URL, etc. Merely by way of example, the storage address may be a storage directory used to store one or more files of the event. Each file may store a specific type of data (e.g., image data, video data, text data) . In some embodiments, the storage address may be determined based on information relating to the event, such as the type of the event, a label of the event, the event time, or the like, or any combination thereof. For example, a name of the storage address may be determined based on a label of the event. As another example, different types of events may be stored in different storage regions of the file management platform 110, and the storage address may be determined based on the type of the event.

In 520, one or more target recording devices may be selected from a plurality of recording devices based on the event record of the event.

In some embodiments, operation 520 may be performed by a docking station 140 (e.g., the selection module 410) , or the file management platform 110 (e.g., the selection module 320) , or the alarm center 150. For illustration purposes, the implementation of operation 520 by the docking station 140 is described hereinafter as an example.

The target recording device (s) may be used to collect recording content regarding the event. For example, a police officer may use the target recording device (e.g., a wearable camera) to record the occurrence of the event as evidence. The plurality of recording devices may include all or part of recording devices of the information management system 100. For example, the recording devices may include recording devices that are currently usable in the information management system 100. As another example, the recording devices may include recording devices that are communicated with the docking station 140.

In some embodiments, the docking station 140 may select the target recording device (s) randomly from the recording devices. As another example, a corresponding relationship between the target recording device (s) and the docking station 140 may be pre-determined and stored in a storage device (e.g., the ROM 230, the RAM 240, the disk 270, a storage device of the file management platform 110) . The docking station 140 may determine the target recording device (s) from the recording devices based on the corresponding relationship between the target recording device (s) and the docking station 140obtained from the storage device. As yet another example, the docking station 140 may determine the target recording device (s) based on the event position of the event (or referred to as first position information) .

In some embodiments, the docking station 140 may obtain position information of each of the plurality of recording devices. For example, each of the recording devices may include a GPS component configured to determine the position of the recording device. The position of each recording device may be transmitted to the docking station 140 continuously or intermittently (e.g., periodically or irregularly) . The docking station 140 may also determine the event position of the event based on the event record (or the reporting signal of the event as aforementioned) . Then, the docking station 140 may select the target recording device (s) from the recording devices based on the event position and the position of each recording device.

For example, the distance between the event position and each of the target recording device (s) may below a threshold distance (e.g., 1 kilometer (km) , 3km, 5km, 10km) . As another example, the target recording device (s) may be located within a region including the event position, for example, within a district including the event position. As a further example, the estimated time for each of the target recording device (s) to arrive at the event position may below a threshold time (e.g., 10 minutes, 15 minutes, 30 minutes, 45 minutes) . As yet another example, the plurality of recording devices may be ranked according to their respective distances to the event position in ascending order. The target recording device (s) may include top N (e.g., top 1, top 2, top 5, top 10, top 1%, top 5%, top 10%) recording device (s) among the recording devices according to the ranking result.

In some embodiments, after the target recording device (s) is selected, the docking station 140 may transmit a message to the target recording device (s) , or a terminal of a user of target recording device (s) , or a device (e.g., (unmanned aerial vehicle) that carries the target recording device (s) . The massage may include information regarding the event to be recorded, such as the event position. The target recording device (s) may move to the event position based on the message. Alternatively, the user or the device may carry the target recording device (s) to the event position based on the message.

In some embodiments, operation 520 may be omitted. The target recording device (s) may be predetermined or selected manually by a user. In some embodiments, operation 520 may be performed by the alarm center 150. Merely by way of example, as described in connection with operation 510, the alarm center 150 may receive a reporting signal with respect to the event. The alarm center 150 may determine the target recording device (s) based on the reporting signal. As another example, the alarm center 150 may display the reporting signal to a user (e.g., a policeman who manages the alarm center) , and receive an input for selecting the target recording device (s) from the user.

In 530, first event information associated with the event may be determined based on the event record of the event.

In some embodiments, operation 530 may be performed by a docking station 140 (e.g., the determination module 420) , or the file management platform 110 (e.g., the determination module 330) , or the alarm center 150. For example, the docking station 140 may determine the first event information by parsing the event record of the event. As another example, the file management platform 110 may determine the first event information by parsing the event record of the event, and the docking station 140 may obtain the first event information from the file management platform 110. In some embodiments, the first event information may be determined based on the event record according to one or more text recognition algorithms.

The first event information refers to information of the event determined based on the event record. Exemplary first event information may include first event scenario information of the event, first label (s) of the event and/or the target recording device (s) , or any other information relating to the event, or any combination thereof. The first event scenario information may relate to a scenario under which the event occurs. For example, the first event scenario information may include the first position information and/or the first time information. A first label of a recording device or an event may be used to uniquely identify the recording device or the event. Exemplary other first information relating to the event may include a user identity of a user of the target recording device (s) , a time for establishing the event record, an event type, one or more entities involved in the event, the cause of the event, a severity degree of the event, etc.

In some embodiments, the first event information may include a storage address in the file management platform 110 corresponding to the event. In some embodiments, the first event information may not include the storage address.

In 540, second event information associated with the event may be determined based on recording content regarding the event collected by the target recording device (s) . In some embodiments, operation 540 may be performed by the docking station 140 (e.g., the determination module 420) .

In some embodiments, the target recording device (s) may collect various recording content associated with the event before, during, and/or after the event occurs. The recording content may include text, an image, an audio, a video, or the like, or any combination thereof. In some embodiments, the recording content collected by a target recording device may be transmitted to the docking station 140 continuously or intermittently (e.g., periodically) . For example, the target recording device may transmit the collected recording content associated with the event to the docking station 140 in real-time through a wireless connection between the docking station 140 and the target recording device. Alternatively, the recording device collected by the target recording device may be transmitted to the docking station 140 after, for example, a USB connection or another wired connection is established between the docking station 140 and the target recording device. In some embodiments, the target recording device may add an identification number (e.g., a serial number) of the target recording device or the event to its collected recording content, and transmit the recording content with the identification number to the docking station 140.

The second event information refers to information of the event determined based on the recording content collected by the target recording device (s) . Exemplary second event information may include second event scenario information of the event, second label (s) of the event and/or the target recording device (s) , or any other information relating to the event, or the like, or any combination thereof. The second event scenario information of the event may be similar to the first event scenario information. For example, the second event scenario information may include second position information and/or the second time information. A second label of a recording device or an event may be used to uniquely identify the recording device or the event. Exemplary other second information relating to the event may include a user identity of a user of the target recording device (s) , a starting time to record the recording content, an ending time to record the recording content, an event type, one or more entities involved in the event, the cause of the event, a severity degree of the event, position information of the target recording device (s) when the target recording device (s) collect the recording content, etc.

The second event information may be determined based on the recording content by various means. For example, the second event information or a portion thereof (e.g., the second event scenario information) may be determined by recognizing the recording content, e.g., via a text recognition technique, an image recognition technique, a speech recognition technique, a video recognition technique, etc., or any combination thereof. As another example, the second event information or a portion thereof may be determined based on source data (or referred to as file information) (e.g., attribute information) of the recording content. The source data may indicate, for example, the time when and/or the position where the recording content is collected. As yet another example, the second label of a target recording device may be determined by the docking station 140 based on the identification number of the target recording device included in the recording content or a connection between the docking station 140 and the target recording device.

In some embodiments, when a target recording device records recording content regarding the event, one or more tags may be added to the recording content by a user of the target recording device or by the target recording device automatically. Merely by way of example, a target recording device may add, to the recording content, one or more voice tags input by a user via a voice input component of the target recording device. As another example, a target recording device may add, to the recording content, one or more text tags input by a user via a text input component of the target recording device. A voice tag or a text tag may include a start tag, an end tag, an event scenario tag, a label tag regarding a second label of the event and/or a target recording device, or the like. Merely by way of example, when the target recording device starts to collect a video, a user of the target recording device may input a start tag of, for example, “event A starts. ” When the target recording device finishes the video collection, the user of the target recording device may input an end tag of, for example, “event A ends. ”

In some embodiments, the event scenario tag may include a location tag regarding the event position, a time tag regarding the event time, a content tag regarding the event content, etc. Merely by way of example, the event scenario tag may be “it is 9 a. m., and a traffic accident happens at an intersection of Road A and Road B. ” The label tag may include an identification number of the target recording device, an identification number of the event, a user identity of a user using the target recording device, or the like, or any combination thereof. For example, the label tag may be added to the recording content by the target recording device automatically or the user of the target recording device manually.

In some embodiments, the target recording device may automatically add a tag to its collected recording content based on, for example, a time point when it starts to collect a video or finishes the video collection, GPS information collected by a GPS component of the target recording device, an identification number of the target recording device or event, or the like.

In some embodiments, the second event information (or a portion thereof) may be determined by identifying the tag (s) included in the recording content through speech recognition or text recognition. For example, the second position information and/or the second time information may be determined based on the location tag and/or the time tag. As another example, the second label may be determined based on the label tag. As a further example, the one or more entities involved in the event, the cause of the event, and/or the severity degree of the event may be determined based on the content tag regarding the event content.

In some alternative embodiments, the target recording device (s) may determine the second event information based on the recording content, and then transmit the second event record to the docking station 140.

In 550, a corresponding relationship between the recording content and the event record may be determined based on the first event information and the second event information.

In some embodiments, operation 550 may be performed by the docking station 140 (e.g., the determination module 420) or the file management platform 110 (e.g., the determination module 330) . For illustration purposes, the implementation of operation 550 by the docking station 140 is described hereinafter as an example.

The corresponding relationship between the recording content and the event record may indicate that the event record and the recording content correspond to (or relate to) the same event. In some embodiments, the corresponding relationship may be used to retrieve, transmit, or store the recording content. For example, the docking station 140 may transmit the recording content to the file management platform 110 and store the recording content at a storage address of the file management platform 110 based on the corresponding relationship, which will be described in operation 560. As another example, the recording content may be retrieved by inputting information (e.g., the event position, the event time, descriptions about the event) included in the event record based on the corresponding relationship.

In some embodiments, the docking station 140 may determine the corresponding relationship between the recording content and the event record by matching (or comparing) the first event information with the second event information. If the first event information and the second event information match with each other, the docking station 140 may establish the corresponding relationship between the recording content and the event record. If the first event information and the second event information do not match with each other, the docking station 140 may further match the first event information of the event with second event information of another event until the first event information is matched with the second event information of a certain event. Additionally or alternatively, if the first event information and the second event information do not match with each other, the docking station 140 may further match the second event information of the event with first event information of another event until the second event information is matched with the first event information of a certain event.

In some embodiments, the docking station 140 may determine or obtain second event information of a plurality of candidate events (e.g., a plurality of events occur within the same period as the event) , and match the first event information of the event with the second event information of each of the plurality of candidate events. The docking station 140 may determine a certain candidate event whose second event information matches the first event information of the event best. Additionally or alternatively, the docking station 140 may determine or obtain first event information of the plurality of candidate events, and match the second event information of the event with the first event information of each of the plurality of candidate events. The docking station 140 may determine a certain candidate event whose first event information matches the second event information of the event best. Further, the docking station 140 may establish a corresponding relationship between the event record of the event and the recording content corresponding certain candidate event, i.e., determine that the event and the certain candidate event are the same event.

In some embodiments, the docking station 140 may determine a matching degree between the first event information and the second event information. The docking station 140 may further determine whether the first event information and the second event information match with each other based on the matching degree. Merely by way of example, if the matching degree exceeds a threshold degree, the first event information and the second event information may be deemed as matching with each other.

The matching degree between the first event information and the second event information may be determined based on, for example, one or more of a first difference between the first position information and the second position information, a second difference between the first time information and the second time information, a third difference between the first label and the second label of the event, a fourth difference between the first label and the second label of the target recording device, or the like. The matching degree may have a negative correlation with each of the first, second, third, and fourth differences. In some embodiments, each of the first, second, third, and fourth differences may be assigned with a weight that represents its importance to the matching degree. The docking station 140 may determine the matching degree based on the first, second, third, and fourth differences and their respective weights.

In some embodiments, the first event information may include the first event scenario information of the event (e.g., the first time information and/or the first position information) , and the second event information may include the second event scenario information of the event (e.g., the second time information and/or the second position information) . The docking station 140 may determine the corresponding relationship between the recording content and the event record based on the first event scenario information and the second event scenario information. For example, the first difference and the second difference as aforementioned may be determined based on the first event scenario information and the second event scenario information. The docking station 140 may further determine the matching degree between the first event information and the second event information based on the first difference and the second difference, and determine the corresponding relationship based on the matching degree.

In some embodiments, the first event information may include the first label (s) of the event and/or the target recording device, and the second event information may include the second label (s) of the event and/or the target recording device. The docking station 140 may determine the corresponding relationship between the recording content and the event record based on the first label and the second label. For example, the third difference and the fourth difference as aforementioned may be determined based on the first label (s) and the second label (s) . The docking station 140 may further determine the matching degree between the first event information and the second event information based on the third difference and the fourth difference, and determine the corresponding relationship based on the matching degree.

In 560, the recording content may be stored at the storage address corresponding to the event in the file management platform 110 based on the corresponding relationship. In some embodiments, operation 560 may be performed by the docking station 140 (e.g., the transmission module 430) or the file management platform 110 (e.g., the storage module 340) .

Merely by way of example, after the corresponding relationship is determined, the docking station 140 may obtain the storage address corresponding to the event, for example, based on the first event information and/or the event record. The docking station 140 may then cause the file management platform 110 to store the recording content at the storage address. The recording content may be transmitted to the file management platform 110 by the docking station 140 or the target recording device (s) . As another example, the docking station 140 may transmit a message regarding the establishment of the corresponding relationship to the file management platform 110. In response to the message, the file management platform 110 may obtain the storage address, and store the recording content at the storage address based on the corresponding relationship.

According to some embodiments of the present disclosure, the docking station may determine a corresponding relationship between an event record of an event and recording content of the event by matching (or comparing) first event information determined from the event record with second event information determined from the recording content. The corresponding relationship between the recording content and the event record may indicate that the event record and the recording content correspond to (or relate to) the same event. The docking station 140 may then cause the file management platform 110 to store the recording content at the storage address after the corresponding relationship is determined. Conventionally, recording content collected by recording devices may need to be manually classified and inspected to determine where it should be stored in the file management platform, which is inefficient and causes a waste of manpower and time. By using the docking station 140 to establish the corresponding relationship, recording content of an event can be classified and stored automatically at a corresponding storage address of the file management platform, thereby improving the efficiency of information management and reducing human costs.

It should be noted that the above description regarding the process 500 is merely provided for the purposes of illustration, and not intended to limit the scope of the present disclosure. For persons having ordinary skills in the art, multiple variations and modifications may be made under the teachings of the present disclosure. However, those variations and modifications do not depart from the scope of the present disclosure. In some embodiments, the order of the operations of the process 500 as illustrated in FIG. 5 and described above is not intended to be limiting. For example,

operations

520 and 530 may be performed simultaneously, or operation 530 may be performed before 520. Additionally or alternatively, the process 500 may be accomplished with one or more additional operations not described and/or without one or more of the operations herein discussed. For example, operation 510 may be omitted, and the event record may be previously generated or inputted by a user manually. As another example, operation 520 may be omitted, and the target recording device (s) may be predetermined or selected by a user manually.

In some embodiments, before or after the recording content is stored at the storage address, the file management platform 110 and/or the docking station 140 may verify the recording content. The verification of the recording content may include verification of the data integrity, the data authenticity, the data source, or the like, or any combination thereof. In some embodiments, the file management platform 110 may verify the recording content based on one or more verification codes received from the target recording device (s) . For example, each target recording device may generate a first verification code for its collected recording content, and transmit the collected recording content with the first verification code to the docking station 140. The docking station 140 may further transmit the recording content of each target recording device and the first verification code (s) to the file management platform 110. As another example, each target recording device may transmit the first verification code directly to the file management platform 110. In other words, the first verification code (s) may be transmitted to the file management platform 110 together with the recording content through a first channel including the target recording device (s) and the docking station 140, or through a second channel merely including the target recording device (s) . One or more second verification codes may be generated by the file management platform 110 based on the recording content using, for example, an encryption algorithm or a decryption algorithm.

The file management platform 110 may further verify the recording content based on the first verification code (s) and the second verification code (s) . For example, the file management platform 110 may compare the first verification code (s) and the second verification code (s) . The file management platform 110 may determine that the recording content is valid if the first verification code (s) are the same as the second verification code (s) . Otherwise, the file management platform 110 may determine that the recording content is invalid, and transmit an instruction to the docking station 140 and/or the target recording device (s) . The instruction may direct the docking station 140 and/or the target recording device (s) to, for example, re-send the recording content. In some embodiments, the first verification code (s) and/or the second verification code (s) may include a parity code, a Hamming code, a cyclic redundancy check (CRC) code, an MD5 code, etc.

In some embodiments, the docking station 140 may verify the recording content based on one or more verification codes received from the target recording device (s) . For example, each target recording device may transmit its recording content and the first verification code to the docking station 140. The docking station 140 may generate the second verification code (s) based on the recording content, and then verify the recording content based on the first verification code (s) and the second verification code (s) .

In some embodiments, the docking station 140 and/or the file management platform 110 may verify the target recording device (s) to verify the recording content. For example, the docking station 140 may be configured to process data collected by one or more specific recording devices, and a corresponding relationship between the docking station 140 and the specific recording device (s) may be predetermined. The docking station 140 may determine whether a target recording device is one of the specific recording device (s) based on the predetermined corresponding relationship between the docking station 140 and the specific recording device (s) . The docking station 140 may determine that the recording content is valid if each target recording device is one of the specific recording device (s) . The docking station 140 may determine that the recording device is invalid if each target recording device is not one of the specific recording device (s) . Optionally, the docking station 140 may disconnect from a target recording device if the target recording device is not one of the specific recording device (s) .

It should be noted that the above description regarding the verification of the recording content is merely provided for the purposes of illustration, and not intended to limit the scope of the present disclosure. In some embodiments, the verification of the recording content may be performed according to a digital signature technique, a data encryption and decryption technique, or the like, or any combination thereof. The verification of the recording content may improve the data safety and prevent data transmission errors and/or data fraud.

FIG. 6 is a flowchart illustrating an exemplary process for file management according to some embodiments of the present disclosure. In some embodiments, process 600 may be executed by the information management system 100. For example, the process 600 may be implemented as a set of instructions (e.g., an application) stored in a storage device (e.g., the ROM 230, the RAM 240) . In some embodiments, one or more of the recording device (s) 130, the docking station (s) 140, and the file management platform 110 may be used to execute the set of instructions and may accordingly be directed to perform the process 600 in the information management system 100.

In 601, a file management platform (e.g., the file management platform 110) may establish a file management directory associated with an event upon receiving a reporting signal of the event.

Upon receiving the reporting signal of the event, the file management platform may be triggered to establish the file management dictionary of the event. When the event occurs, the reporting signal may be triggered manually or by an alarm device. The reporting signal triggered manually may be a signal sent by a person to communicate with an alarm center (e.g., the alarm center 150) . For example, when a traffic accident occurs, the reporting signal may be an alarm message sent by a passerby to the alarm center. The reporting signal triggered by the alarm device may be a signal triggered by an alarm device mounted in a specific area. The alarm device may include a smoke sensor, a gas sensor, or the like. For example, a smoke sensor installed on a roof of a restaurant may send an alarm message to the alarm center when it detects smoke. The reporting signal may include time information and position information associated with the event, etc.

In 602, one or more target recording devices may collect recording content of the event, and upload the recording content to a docking station electrically connected to the target recording device (s) . The recording content may include multiple files.

In some embodiments, the target recording device (s) may collect the recording content of the event and upload the recording content to the docking station electrically connected to the target recording device (s) . Specifically, after the reporting signal of the event is received, a position where the event occurred (also referred to as an event position) may be determined by analyzing the reporting signal. Then, one or more police officers near the event position may be dispatched to process the event. The target recording device (s) carried by the police officer (s) may be used to collect recording content of the event. Usually, there is a one-to-one corresponding relationship between a police officer and a recording device. For example, the police officer number of each police officer may correspond to a serial number of one recording device. The police officer number is a unique identification of the police officer, and the serial number of the recording device is a unique identification of the recording device. After the police officer (s) to process the event are determined, the target recording device (s) corresponding to the police officer (s) may be determined.

In some embodiments, the recording content of the event collected by the target recording device (s) may include multiple files, such as an image, an audio, a video, etc. After the recording content of the event is collected, the target recording device (s) may be electrically connected to the docking station, and the recording content of the event collected by the target recording device (s) may be uploaded to the docking station.

In 603, the docking station may upload the recording content to the file management directory. The file management directory may indicate that the multiple files included in the recording content correspond to the same event.

In some embodiments, after the recording content of the event is obtained, the docking station may upload the recording content to the file management directory in the file management platform. The file management directory may indicate that multiple files included in the recording content correspond to the same event, thereby realizing automatic filing and classification of the recording content of the same event. Automatic determination of all files of the same event may be equivalent to automatically classifying all the files of the same event is into one classification. In this way, multiple files of the event are automatically classified. All recording content of the event may be uploaded to the file management directory corresponding to the event. In this way, different file management directories may correspond to different events, thereby improving the efficiency of event information management.

It should be noted that the above description regarding the process 600 is merely provided for the purposes of illustration, and not intended to limit the scope of the present disclosure. For persons having ordinary skills in the art, multiple variations and modifications may be made under the teachings of the present disclosure. However, those variations and modifications do not depart from the scope of the present disclosure.

In some embodiments, before operation 601, the process 600 may further include an additional operation, in which a first corresponding relationship between the target recording device (s) and the docking station, and a second corresponding relationship between the docking station and the file management platform are established in advance. Specifically, a docking station usually corresponds to multiple recording devices, and a file management platform usually corresponds to multiple docking stations. Conversely, multiple recording devices may correspond to the same docking station, and multiple docking stations may correspond to the same file management platform. After the serial number (s) of the target recording device (s) are determined, a docking station corresponding to the target recording device (s) may be determined, and a file management platform corresponding to the docking station may be determined. Those skilled in the art may set the first corresponding relationship between the target recording device (s) and the corresponding docking station, and the second corresponding relationship between the docking station and the corresponding file management platform according to actual needs, which is not limited herein.

FIG. 7 is a flowchart illustrating an exemplary process for determining first event information according to some embodiments of the present disclosure. In some embodiments, the process 700 may be performed when the reporting signal of the event is received.

In 701, the file management platform may determine first serial number (s) of the target recording device (s) , first position information of the event, and first time information of the event by analyzing the reporting signal. A serial number of a recording device is the unique identification of the recording device.

In 702, the file management platform may transmit first event information including the first serial number (s) of the target recording device (s) , the file management directory, the first position information, and the first time information of the event to the docking station corresponding to the target recording device (s) .

In some embodiments, operations 701 and 702 may be implemented by the following process.

First, the file management platform may analyze the reporting signal to determine the serial number (s) of the target recording device (s) used to collect data of the event, the first position information, and the first time information of the event. The serial number (s) are the unique identification of the target recording device (s) . For example, the reporting signal is "when I drove to the intersection A at nine o'clock in the morning on August 8th, I found that a vehicle A knocked a person to the ground. I hope the police come here quickly. " After analyzing the reporting signal, the file management platform may determine that the event is a traffic accident, the first position information is "the intersection A, " and the first time information is "nine o'clock in the morning on August 8 ^th. "

Specifically, the file management platform may obtain position information of each recording device. After the first position information of the traffic accident is determined, the file management platform may determine a target recording device closest to the traffic accident, and then determine the serial number corresponding to the target recording device closest to the traffic accident. In some embodiments, the file management platform may determine multiple recording devices whose distances to the event position are within a preset distance range. The recording device closest to the event position among the multiple recording devices may be determined as one of the target recording device (s) . In addition, a policeman within the preset distance range from the event position may determine one or more recording devices among the multiple recording devices as the target recording device (s) . The target recording device (s) used to collect the recording content of the event may also be determined in another manner according to actual needs, which is not limited herein.

Then, the file management platform may transmit the first event information including the determined serial number (s) of the target recording device (s) , the established file management directory of the event, and the first position information and first time information of the event to the docking station corresponding to the target recording device (s) . In this way, the first event information may be obtained by the docking station, which may be used to establish a one-to-one corresponding relationship between the docking station and the file management directory of the file management platform.

FIG. 8 is a flowchart illustrating an exemplary process for uploading recording content to a file management directory according to some embodiments of the present disclosure. In some embodiments, one or more operations of the process 800 may be performed to achieve at least part of operation 603 as described in connection with FIG. 6.

In 801, the docking station may determine second serial number (s) of the target recording device (s) , second time information of the event, and second position information of the event by parsing file information of the recording content.

In 802, the docking station may match second event information with the first event information. The second event information may include the second serial number (s) of the target recording device (s) , the second time information, the second position information of the event, and the recording content. When the second serial number (s) of the target recording device (s) , the second time information, and the second position information are the same as the first serial number (s) , the first time information, and the first position information, respectively, the docking station may determine that the recording content corresponds to the file management directory.

In 803, the docking station may upload the recording content to the file management directory.

In some embodiments, operations 801 to 803 may be implemented by the following process.

First, the docking station may determine the second serial number (s) of the target recording device (s) used to collect data of the event. The docking station may also determine the second time information and the second position information of the event by parsing the file information of the recording content. The file information of the recording content may include attribute information. When the target recording device (s) are electrically connected to the docking station, the docking station may determine the second serial number (s) of the target recording device (s) . For example, the docking station may determine the second serial number (s) of the target recording device (s) used to collect recording content of a traffic accident C, and parse second time information and second position information of the traffic accident C from the file information of the recording content (such as images, audios, and videos) of the traffic accident C.

Then, the docking station may match the second event information with the first event information. The second event information may include the second serial number (s) of the target recording device (s) , the second time information, the second position information, and the recording content. When the second serial number (s) of the target recording device (s) , the second time information, and the second position information of the event are the same as the first serial number (s) , the first time information, and the first position information, respectively, the docking station may determine that the recording content corresponds to the file management directory. Then, the docking station may upload the recording content to the file management directory. That is, the docking station may match the first event information transmitted from the file management platform with the second event information parsed from the recording content collected by the target recording device (s) . The docking station may determine the file management directory corresponding to the recording content when the first serial number (s) , the first time information, and the first position information in the first event information are the same as the second serial number (s) , the second time information, and the second position information in the second event information, respectively. The docking station may then upload the recording content to the file management directory.

Since the docking station may store multiple files of the recording content of a same event and multiple files of the recording content of different events, the recording content of the same event can be screened rapidly and automatically without manual classification in the whole process by matching the first event information and the second event information. The recording content of the same event may be uploaded to the file management directory corresponding to the same event, thereby realizing automatic classification of the recording content of the event into one category. In addition, a file management directory may be established for each event, and recording content of different events can be uploaded to different file management directories, thereby realizing automatic classification of recording content of each event, and further improving the efficiency of event information management.

FIG. 9 illustrates an exemplary information management platform 900 according to some embodiments of the present disclosure. The information management system 900 may be an exemplary embodiment of the information management system 100 as described in connection with FIG. 1.

The information management system 900 may include a recording device 130, a docking station 140 electrically connected to the recording device 130, and a file management platform 110 connected to the docking station 140. The file management platform 110 may be configured to establish a file management directory associated with an event upon receiving reporting signal of the event. The recording device 130 may be configured to collect recording content of the event, and upload the recording content to the docking station 140. The recording content may include multiple files. The docking station 140 may be configured to upload the recording content to the file management directory. The file management directory may indicate that the multiple files included in the recording content correspond to the same event.

In some embodiments, the file management platform 110 may be configured to determine the first serial number (s) of target recording device (s) , first position information of the event, and first time information of the event by analyzing the reporting signal. The file management platform 110 may be configured to transmit the first event information including the first serial number (s) , the file management directory, the first position information, and the first time information to the docking station 140 corresponding to the target recording device (s) .

In some embodiments, the docking station 140 may be configured to determine the second serial number (s) of the target recording device (s) 130, second time information of the event, and second position information of the event by parsing the file information of the recording content. The docking station 140 may be configured to match the second event information with the first event information. The second event information may include the second serial number (s) of the target recording device (s) , the second time information, the second position information of the event, and the recording content. When the second serial number (s) of the target recording device (s) 130, the second time information, and the second position information of the event are the same as the first serial number (s) , the first time information, and the first position information, respectively, the docking station 140 may determine that the recording content corresponds to the file management directory. The docking station 140 may be configured to upload the recording content to the file management directory.

In some embodiments, the file management platform 110 may be configured to establish a first corresponding relationship between the target recording device (s) 130 and the docking station 140, and a second corresponding relationship between the docking station 140 and the file management platform 110 in advance.

Having thus described the basic concepts, it may be rather apparent to those skilled in the art after reading this detailed disclosure that the foregoing detailed disclosure is intended to be presented by way of example only and is not limiting. Various alterations, improvements, and modifications may occur and are intended to those skilled in the art, though not expressly stated herein. These alterations, improvements, and modifications are intended to be suggested by this disclosure, and are within the spirit and scope of the exemplary embodiments of this disclosure.

Moreover, certain terminology has been used to describe embodiments of the present disclosure. For example, the terms “one embodiment, ” “an embodiment, ” and/or “some embodiments” mean that a particular feature, structure or characteristic described in connection with the embodiment is included in at least one embodiment of the present disclosure. Therefore, it is emphasized and should be appreciated that two or more references to “an embodiment, ” “one embodiment, ” or “an alternative embodiment” in various portions of this specification are not necessarily all referring to the same embodiment. Furthermore, the particular features, structures or characteristics may be combined as suitable in one or more embodiments of the present disclosure.

Further, it will be appreciated by one skilled in the art, aspects of the present disclosure may be illustrated and described herein in any of a number of patentable classes or context including any new and useful process, machine, manufacture, or composition of matter, or any new and useful improvement thereof. Accordingly, aspects of the present disclosure may be implemented entirely hardware, entirely software (including firmware, resident software, micro-code, etc. ) or combining software and hardware implementation that may all generally be referred to herein as a "block, " “module, ” “device, ” “unit, ” “component, ” or “system. ” Furthermore, aspects of the present disclosure may take the form of a computer program product embodied in one or more computer readable media having computer readable program code embodied thereon.

A computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated signal may take any of a variety of forms, including electro-magnetic, optical, or the like, or any suitable combination thereof. A computer readable signal medium may be any computer readable medium that is not a computer readable storage medium and that may communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable signal medium may be transmitted using any appropriate medium, including wireless, wireline, optical fiber cable, RF, or the like, or any suitable combination of the foregoing.

Computer program code for carrying out operations for aspects of the present disclosure may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Scala, Smalltalk, Eiffel, JADE, Emerald, C++, C#, VB. NET, Python or the like, conventional procedural programming languages, such as the “C” programming language, Visual Basic, Fortran 1703, Perl, COBOL 1702, PHP, ABAP, dynamic programming languages such as Python, Ruby and Groovy, or other programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN) , or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider) or in a cloud computing environment or offered as a service such as a software as a service (SaaS) .

Furthermore, the recited order of processing elements or sequences, or the use of numbers, letters, or other designations, therefore, is not intended to limit the claimed processes and methods to any order except as may be specified in the claims. Although the above disclosure discusses through various examples what is currently considered to be a variety of useful embodiments of the disclosure, it is to be understood that such detail is solely for that purpose, and that the appended claims are not limited to the disclosed embodiments, but, on the contrary, are intended to cover modifications and equivalent arrangements that are within the spirit and scope of the disclosed embodiments. For example, although the implementation of various components described above may be embodied in a hardware device, it may also be implemented as a software-only solution-e.g., an installation on an existing server or mobile device.

Similarly, it should be appreciated that in the foregoing description of embodiments of the present disclosure, various features are sometimes grouped together in a single embodiment, figure, or description thereof for the purpose of streamlining the disclosure aiding in the understanding of one or more of the various embodiments. This method of disclosure, however, is not to be interpreted as reflecting an intention that the claimed subject matter requires more features than are expressly recited in each claim. Rather, claimed subject matter may lie in less than all features of a single foregoing disclosed embodiment.

Claims

A system for information management, comprising:

one or more recording devices;

a docking station communicated with the one or more recording devices; and

a file management platform communicated with the docking station and configured to store data, wherein the docking station is configured to:

obtain first event information associate with an event, wherein the first event information is determined based on an event record of the event;

determine, based on recording content regarding the event collected by at least one target recording device of the one or more recording devices, second event information associated with the event; and

determine, based on the first event information and the second event information, a corresponding relationship between the recording content and the event record, the corresponding relationship being used to retrieve, transmit, or store the recording content on the file management platform.
The system of claim 1, wherein the docking station is further configured to:

obtain a storage address of the file management platform, the storage address corresponding to the event; and

cause the file management platform to store the recording content at the storage address based on the corresponding relationship.
The system of claim 1, wherein

the first event information includes first event scenario information of the event,

the second event information includes second event scenario information of the event, and

to determine, based on the first event information and the second event information, a corresponding relationship between the recording content and the event record, the docking station is further configured to:

determine, based on the first event scenario information and the second event scenario information, the corresponding relationship between the recording content and the event record.
The system of claim 1, wherein

the first event information includes a first label of the event or the at least one target recording device,

the second event information includes a second label of the event or the at least one target recording device, and

to determine, based on the first event information and the second event information, a corresponding relationship between the recording content and the event record, the docking station is further configured to:

determine, based on the first label and the second label, the corresponding relationship between the recording content and the event record.
The system of claim 1, wherein the second event information is determined by performing speech recognition or text recognition on the recording content.
The system of claim 1, wherein one or more recording devices include a plurality of recording devices, and the docking station is further configured to:

select, from the plurality of recording devices, the at least one target recording device based on the first event information.
The system of claim 6, wherein the first event information includes first position information of the event, and

to select, from the plurality of recording devices, the at least one target recording device based on the first event information, the docking station is further configured to:

obtain second position information of the plurality of recording devices; and

select, from the plurality of recording devices, the at least one target recording device based on the first position information and the second position information.
The system of claim 1, wherein the file management platform is configured to:

create the event record of the event based on a reporting signal associated with the event.
The system of claim 1, wherein the docking station or the file management platform is further configured to:

verify the recording content.
The system of claim 9, wherein to verify the recording content, the docking station or the file management platform is further configured to:

receive a verification code from the at least one target recording device; and

verify the recording content based on the verification code.
A method for information management, that is implemented on a computing device having at least one processor and at least one storage device, the method comprising:

determining, based on an event record of an event, first event information associated with the event;

determining, based on recording content regarding the event collected by at least one target recording device, second event information associated with the event; and

determining, based on the first event information and the second event information, a corresponding relationship between the recording content and the event record, the corresponding relationship being used to retrieve, transmit, or store the recording content.
The method of claim 11, further comprising:

obtaining a storage address of a file management platform, the storage address corresponding to the event; and

storing the recording content at the storage address in the file management platform based on the corresponding relationship.
The method of claim 11, wherein

the first event information includes first event scenario information of the event,

the second event information includes second event scenario information of the event, and

the determining, based on the first event information and the second event information, a corresponding relationship between the recording content and the event record comprises:

determining, based on the first event scenario information and the second event scenario information, the corresponding relationship between the recording content and the event record.
The method of claim 11, wherein

the first event information includes a first label of the event or the at least one target recording device,

the second event information includes a second label of the event or the at least one target recording device, and

the determining, based on the first event information and the second event information, a corresponding relationship between the recording content and the event record comprises:

determining, based on the first label and the second label, the corresponding relationship between the recording content and the event record.
The method of claim 11, wherein the second event information is determined by performing speech recognition or text recognition on the recording content.
The method of claim 11, further comprising:

selecting, from a plurality of recording devices, the at least one target recording device based on the event record.
The method of claim 16, wherein the first event information includes first position information of the event, and

the selecting, from the plurality of recording devices, the at least one target recording device based on the first event information comprises:

obtaining second position information of the plurality of recording devices; and

selecting, from the plurality of recording devices, the at least one target recording device based on the first position information and the second position information.
The method of claim 11, further comprising:

creating the event record of the event based on a reporting signal associated with the event.
The method of claim 11, further comprising:

verifying the recording content.
A non-transitory computer-readable storage medium, comprising a set of instructions for file management, wherein when executed by at least one processor, the set of instructions direct the at least one processor to effectuate a method, the method comprising:

determining, based on an event record of an event, first event information associated with the event;

determining, based on recording content regarding the event collected by at least target one recording device, second event information associated with the event; and

determining, based on the first event information and the second event information, a corresponding relationship between the recording content and the event record, the corresponding relationship being used to retrieve, transmit, or store the recording content.