CN114374813A - Multimedia resource management method, recorder and server - Google Patents

Abstract

The application relates to the technical field of information processing, and discloses a multimedia resource management method, a recorder and a server, which are used for solving the problems of rough management and low management efficiency of multimedia resources recorded by the recorder in the related technology. In the method, a plurality of scene identifiers are displayed by a recorder; then responding to the selection operation of a target scene identifier in the scene identifiers, and performing associated storage on the target scene identifier and the corresponding multimedia resource; and carrying the target scene identification, the multimedia resource, and the starting recording time and the ending recording time of the multimedia resource in a file uploading request and sending the file uploading request to a server. Therefore, when the user uses the recorder, the user can directly select the target scene identification to record the multimedia information, and the target scene identification and the corresponding multimedia resource are stored in an associated manner, so that the recorder can actively divide the multimedia information more accurately, and the subsequent accurate query of the multimedia information is facilitated.

Description

Multimedia resource management method, recorder and server

technical field

The present application relates to the technical field of information processing, and in particular, to a multimedia resource management method, a recorder and a server.

Background technique

A recorder is a portable device with synchronous audio and video recording capabilities that can automatically record various events.

The recorder will record a large number of data resources such as videos and photos during use. The data time and amount of information of these data resources are huge, which makes it very difficult to organize these data later. In the prior art, the data maintenance of the recorder can automatically mark and manage data resources according to time points, but there are problems of rough management of data resources and low management efficiency.

SUMMARY OF THE INVENTION

The purpose of this application is to provide a multimedia resource management method, a recorder and a server to solve the problems in the prior art that the recorder automatically marks and manages data resources according to time points, which may have rough management data resources and low management efficiency. .

In a first aspect, the present application provides a multimedia resource management method, which is applied to a recorder, and the method includes:

Display multiple scene identifiers;

In response to the selection operation of the target scene identifier in the plurality of scene identifiers, the target scene identifier and the corresponding multimedia resource are associated and stored;

The target scene identifier, the multimedia resource, the start recording time and the end recording time of the multimedia resource are carried in the file upload request and sent to the server.

In a possible implementation manner, before the displaying of the plurality of scene identifiers, the method further includes:

Send a login request to the server, where the login request includes the user's login information;

The plurality of scene identifiers sent by the server are acquired in response to the successful result of the verification of the login information by the server.

In a possible implementation manner, in response to the selection operation of the target scene identifier among the plurality of scene identifiers, the target scene identifier and the corresponding multimedia resource are stored in association, specifically including:

In response to the selection operation of the target scene identification among the plurality of scene identifications, recording the current start time of the selection operation for the target scene identification and the keyword corresponding to the target scene identification;

Using the login information of the user, the start time of the current selection operation on the target scene identifier, and the keyword corresponding to the target scene identifier as the description information of the recorded multimedia resource, a first file containing the description information is generated. ;

The first file is stored in association with the multimedia resource.

In a possible implementation, the method further includes:

In response to the selection operation of the target scene identifier, start a recording function to collect image data of the multimedia resource and save it;

In response to the operation of pausing the recording, the acquired image data is previewed and the saving of the acquired image data is stopped.

In a possible implementation manner, after previewing the collected image data and stopping saving the collected image data, the method further includes:

In response to the operation of starting the recording, record the start time of the current recording and the keyword corresponding to the target scene identifier;

Using the login information of the user, the start time of the recording and the keyword corresponding to the target scene identifier as the description information of the recorded multimedia resource, a second file containing the description information is generated;

The second file is stored in association with the multimedia resource.

In a possible implementation manner, saving the collected image data of the multimedia resource specifically includes:

The collected image data of the multimedia resource is stored in segments.

In a possible implementation, the method further includes:

In the process of recording the multimedia resource, based on the user operation of stopping recording and switching to the photographing function, the photographing function interface is displayed, and the photographing is performed in response to the photographing instruction to obtain the image; or,

In the process of recording the multimedia resource, performing a screenshot operation in response to the screenshot instruction to obtain an image;

storing the target scene identifier and the image in association;

The image and the target scene identification are sent to the server.

In a possible implementation, the method further includes:

Sending a query request to the server, where the query request includes query conditions, and the query conditions include at least one of the keywords corresponding to the scene identifier, the start time of recording, and the end time of recording;

Receive and display the multimedia resource returned by the server in response to the query condition.

In a second aspect, the present application provides a multimedia resource management method, which is applied to a server, and the method includes:

Receive a file upload request sent by the recorder, where the file upload request includes a keyword corresponding to the target scene identifier, the multimedia resource, the start time of the multimedia resource recording, and the end time of the recording;

The target scene identifier, the multimedia resource, the start time of recording of the multimedia resource, and the end time of recording are stored in association.

In a possible implementation, the method includes:

Receive a query request sent by the terminal device, where the query request includes query conditions, and the query conditions include at least one of the keywords corresponding to the scene identifier, the start time of recording, and the end time of recording;

Query the stored multimedia resource set based on the query condition, and send the query result to the terminal device.

In a third aspect, the present application provides a recorder, including:

cameras, displays, processors and memory;

The camera is used to collect multimedia resource data;

the display is used to display the screen display area;

the memory for storing the processor-executable instructions;

The processor is configured to execute the instructions to implement the multimedia resource management method according to any one of the above first aspects.

In a fourth aspect, the present application provides a server, including:

processor;

a memory for storing the processor-executable instructions;

Wherein, the processor is configured to execute the instructions to implement the multimedia resource management method according to any one of the second aspect above.

In a fifth aspect, the present application provides a computer-readable storage medium, when the instructions in the computer-readable storage medium are executed by a recorder or a server, the recorder or the server can perform the above-mentioned first aspect or the multimedia resource management method according to any one of the second aspects.

In a sixth aspect, the present application provides a computer program product, including a computer program, which implements the multimedia resource management method according to any one of the first aspect or the second aspect when the computer program is executed by a processor.

The method provided by the embodiment of the present application is applied to a recorder to display a plurality of scene identifiers; in response to a selection operation of a target scene identifier among the plurality of scene identifiers, the target scene identifier and the corresponding multimedia resource are stored in association; The target scene identifier, the multimedia resource, the start recording time and the end recording time of the multimedia resource are carried in the file upload request and sent to the server, so that the recorder can have the initiative to divide the multimedia information, and the user uses the record. The instrument can directly select the target scene identifier to record multimedia information, which can combine the recording scene to manage the multimedia resources and improve the management efficiency of the multimedia resources.

With the method provided in the embodiment of the present application, the recorder can also directly exit the recording of multimedia information under the current scene identifier when recording another multimedia information, and select the corresponding scene identifier to record the multimedia information, so as to realize the active recording of the multimedia information by the recorder. The division and the associated storage of the target scene identifier and the corresponding multimedia resource makes the division of the multimedia information more accurate, and facilitates subsequent accurate query of the multimedia information. Thus, a multimedia resource management method based on an application scenario is provided, which can improve management efficiency.

Other features and advantages of the present application will be set forth in the description which follows, and in part will be apparent from the description, or may be learned by practice of the present application. The objectives and other advantages of the application may be realized and attained by the structure particularly pointed out in the written description, claims, and drawings.

Description of drawings

In order to illustrate the technical solutions of the embodiments of the present application more clearly, the following briefly introduces the drawings that need to be used in the embodiments of the present application. Obviously, the drawings introduced below are only some embodiments of the present application. For those of ordinary skill in the art, other drawings can also be obtained from these drawings without any creative effort.

1 is a schematic structural diagram of a recorder according to an embodiment of the present application;

2 is a block diagram of a software structure of a recorder provided by an embodiment of the present application;

3 is a schematic diagram of an application scenario of the multimedia resource management method provided by the embodiment of the present application;

4 is a schematic flowchart of a multimedia resource management method provided by an embodiment of the present application;

5A is a schematic interface diagram of multiple scene identifiers provided by an embodiment of the present application;

5B is a schematic diagram of a generated file provided by an embodiment of the present application;

5C is a schematic diagram of field content changes provided by an embodiment of the present application;

5D is a schematic interface diagram of an exit target scene identification provided by an embodiment of the present application;

FIG. 5E is a schematic diagram of a complete data chain provided by an embodiment of the present application;

FIG. 5F is a schematic diagram of collecting multimedia resources by photographing according to an embodiment of the present application;

FIG. 5G is a schematic diagram of capturing multimedia resources with screenshots provided by an embodiment of the present application;

5H is a schematic diagram of segmented storage multimedia resources provided by an embodiment of the present application;

6 is a schematic flowchart of automatic file uploading according to an embodiment of the present application;

7 is a schematic flowchart of a recorder recording multimedia resources provided by an embodiment of the present application;

8A is a schematic diagram of displaying multiple files to a user according to an embodiment of the present application;

FIG. 8B is a schematic structural diagram of a server according to an embodiment of the present application.

Detailed ways

In order to make the purposes, technical solutions and advantages of the embodiments of the present application more clear, the technical solutions in the embodiments of the present application will be described clearly and completely below with reference to the accompanying drawings in the embodiments of the present application. The described embodiments are part of the embodiments of the present application, but not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative work fall within the protection scope of the present application.

In addition, in the description of the embodiments of the present application, unless otherwise specified, "/" means or means, for example, A/B can mean A or B; "and/or" in the text is only a description of the associated object The association relationship indicates that there can be three kinds of relationships, for example, A and/or B can indicate that A exists alone, A and B exist at the same time, and B exists alone. In addition, in the description of the embodiments of this application , "plurality" means two or more.

Hereinafter, the terms "first" and "second" are only used for descriptive purposes, and should not be construed as implying or implying relative importance or implying the number of indicated technical features. Therefore, the features defined as "first", "second", may expressly or implicitly include one or more features, and in the description of the embodiments of the present application, unless otherwise specified, "multiple" The meaning is two or more.

A recorder is a portable device with synchronous audio and video recording capabilities that can automatically record various events.

The recorder will record a large number of data resources such as videos and photos during use. The data time and amount of information of these data resources are huge, which makes it very difficult to organize these data later. In the prior art, the data maintenance of the recorder can automatically mark and manage data resources according to time points, but there are problems of rough management of data resources and low management efficiency.

In view of this, the embodiments of the present application provide a multimedia resource management method, a recorder, and a server to solve the problem that in the prior art, the recorder automatically marks and manages data resources according to time points, and there may be rough management of data resources and management of data resources. problem of inefficiency. The multimedia resource management method provided by the present application will be introduced below with reference to the embodiments.

The inventive concept of the present application can be summarized as follows: the recorder can display multiple scene identifiers; and in response to the selection operation of the target scene identifier among the multiple scene identifiers, the target scene identifier and the corresponding multimedia resources are stored in association with each other. ; Further, the target scene identifier, the multimedia resource, the start recording time and the end recording time of the multimedia resource can be carried in the file upload request and sent to the server. Thus, in the present application, the recorder can have the initiative to divide the multimedia information, so that the user can directly select the target scene identifier to record the multimedia information when using the recorder, and can also directly exit the multimedia information under the current scene identifier when recording another multimedia information. Select the corresponding scene identifier to record the multimedia information, so as to realize the active division of the multimedia information by the recorder and the associated storage of the target scene identifier and the corresponding multimedia resources, so that the multimedia information can be divided more accurately, and it is also convenient for subsequent Accurate query of multimedia information, thereby improving the management efficiency of multimedia resources.

After introducing the inventive concept of the present application, the recorder provided by the present application will be described below. FIG. 1 shows a schematic structural diagram of a recorder 100 . It should be understood that the recorder 100 shown in FIG. 1 is merely an example, and the recorder 100 may have more or fewer components than those shown in FIG. 1, two or more components may be combined, or Different component configurations are possible. The various components shown in the figures may be implemented in hardware, software, or a combination of hardware and software, including one or more signal processing and/or application specific integrated circuits.

FIG. 1 exemplarily shows a hardware configuration block diagram of the recorder 100 according to the exemplary embodiment. As shown in FIG. 1 , the recorder 100 includes: a radio frequency (RF) circuit 110 , a memory 120 , a display unit 130 , a camera 140 , a sensor 150 , an audio circuit 160 , and a Wireless Fidelity (Wi-Fi) module 170 , the processor 180 , the Bluetooth module 181 , and the power supply 190 and other components.

The RF circuit 110 can be used for signal reception and transmission in the process of sending and receiving multimedia information, can receive downlink data from the base station and then hand it over to the processor 180 for processing; and can send uplink data to the base station. Typically, RF circuits include, but are not limited to, antennas, at least one amplifier, transceivers, couplers, low noise amplifiers, duplexers, and the like.

Memory 120 may be used to store software programs and data. The processor 180 executes various functions of the recorder 100 and data processing by executing software programs or data stored in the memory 120 . Memory 120 may include high-speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other volatile solid state storage device. The memory 120 stores an operating system that enables the recorder 100 to operate. In this application, the memory 120 may store an operating system and various application programs, and may also store program codes for executing the multimedia resource management methods described in the embodiments of this application.

The display unit 130 can be used to receive input multimedia information such as numbers or characters, and generate signal input related to user settings and function control of the recorder 100 .

The display unit 130 may also be used to display information input by the user or information provided to the user and a graphical user interface (GUI) of various menus of the recorder 100 . Specifically, the display unit 130 may include a display screen 132 disposed on the front of the recorder 100 . The display screen 132 may be configured in the form of a liquid crystal display, a light emitting diode, or the like. The display unit 130 can be used to display multiple scene identifiers of the screen display interface of the recorder in the present application, and preview the collected multimedia data.

The touch screen 131 may cover the display screen 132, or the touch screen 131 and the display screen 132 may be integrated to realize the input and output functions of the recorder 100, which may be referred to as touch screen after integration. In this application, the display unit 130 can display application programs and corresponding operation steps.

Camera 140 may be used to capture still images or video. The object is projected through the lens to generate an optical image onto the photosensitive element. The photosensitive element may be a charge coupled device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor. The photosensitive element converts the optical signal into an electrical signal, and then transmits the electrical signal to the processor 180 for conversion into a digital image signal.

The recorder 100 may further include at least one sensor 150 , such as an acceleration sensor 151 , a distance sensor 152 , a fingerprint sensor 153 , and a temperature sensor 154 . The recorder 100 may also be configured with other sensors such as a gyroscope, a barometer, a hygrometer, a thermometer, an infrared sensor, a light sensor, a motion sensor, and the like.

Audio circuitry 160 , speaker 161 , and microphone 162 may provide an audio interface between the user and recorder 100 . The audio circuit 160 can transmit the electrical signal converted from the received audio data to the speaker 161, and the speaker 161 converts it into a sound signal and outputs it. The recorder 100 can also be configured with volume buttons for adjusting the volume of the sound signal, and can also be used in combination with other buttons to perform corresponding operations. On the other hand, the microphone 162 converts the collected sound signal into an electrical signal, which is received by the audio circuit 160 and converted into audio data, and then outputs the audio data to the RF circuit 110 for transmission to, for example, another recorder, or outputs the audio data to memory 120 for further processing.

Wi-Fi is a short-distance wireless transmission technology, and the recorder 100 can help users to send and receive emails, browse web pages, access streaming media, etc. through the Wi-Fi module 170, which provides users with wireless broadband Internet access.

The processor 180 is the control center of the recorder 100, uses various interfaces and lines to connect various parts of the entire recorder, and executes recording by running or executing the software programs stored in the memory 120 and calling the data stored in the memory 120. Various functions of the meter 100 and processing data. In some embodiments, the processor 180 may include one or more processing units; the processor 180 may also integrate an application processor and a baseband processor, wherein the application processor mainly processes the operating system, user interface and application programs, etc., and the baseband The processor mainly handles wireless communication. It can be understood that, the above-mentioned baseband processor may not be integrated into the processor 180 . In this application, the processor 180 may run an operating system, an application program, user interface display and touch response, and the multimedia resource management method described in the embodiments of this application. In addition, the processor 180 is coupled to the display unit 130 .

The bluetooth module 181 is used to exchange information with other bluetooth devices having bluetooth modules through the bluetooth protocol. For example, the recorder 100 can establish a Bluetooth connection with a wearable electronic device (such as a smart watch) that also has a Bluetooth module through the Bluetooth module 181, so as to perform data interaction.

The recorder 100 also includes a power source 190 (eg, a battery) for powering the various components. The power supply can be logically connected to the processor 180 through a power management system, so that functions such as managing charging, discharging, and power consumption are implemented through the power management system. The recorder 100 can also be configured with a power button, which is used to turn on and off the recorder, and lock the screen and other functions.

FIG. 2 is a block diagram of the software structure of the recorder 100 according to the embodiment of the present application.

The layered architecture divides the software into several layers, and each layer has a clear role and division of labor. Layers communicate with each other through software interfaces. In some embodiments, the Android system can be divided into four layers, which are, from top to bottom, an application layer, an application framework layer, an Android runtime (Android runtime) and system libraries, and a kernel layer.

The application layer can include a series of application packages.

As shown in Figure 2, the application package can include applications such as camera, gallery, calendar, call, map, navigation, WLAN, Bluetooth, video, recording, etc.

The application framework layer provides an application programming interface (application programming interface, API) and a programming framework for the applications of the application layer. The application framework layer includes some predefined functions.

As shown in Figure 2, the application framework layer may include window managers, content providers, view systems, telephony managers, resource managers, notification managers, and the like.

A window manager is used to manage window programs. The window manager can get the size of the display screen, determine whether there is a status bar, lock the screen, take screenshots, etc.

Content providers are used to store and retrieve data and make these data accessible to applications. The data may include video, images, audio, calls made and received, browsing history and bookmarks, phonebooks, short messages, and the like.

The view system includes visual controls, such as a user interface of a camera, which may include controls for displaying text, controls for displaying pictures, controls for selecting scene identifiers, and the like. View systems can be used to build applications. A display interface can consist of one or more views. For example, the display interface including the short message notification icon may include a view for displaying text, a view for displaying pictures, and a view for selecting scene identifiers.

The network manager is used to provide the communication function of the recorder 100, as well as the connection status and transmission interface of the network (including data and Wifi), such as judging whether the network is available and receiving and sending data packets through the transmission interface.

The resource manager provides various resources for the application, such as localization strings, icons, pictures, layout files, video files, etc.

The notification manager enables the application to display notification information in the status bar (such as the message summary of the short message, the message content, the notification with the update of the scene ID), which can be used to convey the notification type message, and can disappear automatically after a short stay, without the need for User interaction. For example, the notification manager is used to notify download completion, message reminders, etc. The notification manager can also display notifications in the status bar at the top of the system in the form of graphs or scroll bar text, such as notifications of applications running in the background, and notifications on the screen in the form of dialog windows. For example, text information is prompted in the status bar, a prompt sound is issued, the recorder vibrates, and the indicator light flashes.

Android Runtime includes core libraries and a virtual machine. The Android runtime is responsible for the scheduling and management of the Android system.

The core library consists of two parts: one is the function functions that the java language needs to call, and the other is the core library of Android.

The application layer and the application framework layer run in virtual machines. The virtual machine executes the java files of the application layer and the application framework layer as binary files. The virtual machine is used to perform functions such as object lifecycle management, stack management, thread management, safety and exception management, and garbage collection.

A system library can include multiple functional modules. For example: surface manager (surface manager), media library (Media Libraries), 3D graphics processing library (eg: OpenGL ES), 2D graphics engine (eg: SGL) and so on.

The Surface Manager is used to manage the display subsystem and provides a fusion of 2D and 3D layers for multiple applications.

The media library supports playback and recording of a variety of commonly used audio and video formats, as well as still image files. The media library can support a variety of audio and video encoding formats, such as: MPEG4, H.264, MP3, AAC, AMR, JPG, PNG, etc.

The 3D graphics processing library is used to implement 3D graphics drawing, image rendering, compositing, and layer processing.

A 2D (a way of animation) graphics engine is a drawing engine for 2D drawing.

The kernel layer is the layer between hardware and software. The kernel layer contains at least display drivers, camera drivers, audio drivers, and sensor drivers.

After introducing the recorder of the embodiments of the present application, the following briefly introduces some application scenarios to which the technical solutions of the embodiments of the present application can be applied. It should be noted that the application scenarios introduced below are only used to illustrate the embodiments of the present application and not limited. During specific implementation, the technical solutions provided by the embodiments of the present application may be flexibly applied according to actual needs.

Referring to FIG. 3 , it is a schematic diagram of an application scenario of the multimedia resource management method provided by the embodiment of the present application. The application scenario includes the recorder 100 and the server 101 .

The recorder 100 and the server 101 are connected through a wireless or wired network, and the server 101 provides a scene identifier for the recorder 100 to display.

The server 101 in this embodiment of the present application may be a server, a server cluster composed of several servers, or a cloud computing center. The server 101 may be an independent physical server, or a server cluster or distributed system composed of multiple physical servers, or may provide cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, Cloud servers for basic cloud computing services such as middleware services, domain name services, security services, CDN, and big data and artificial intelligence platforms.

Of course, the method provided by the embodiment of the present application is not limited to the application scenario shown in FIG. 3 , and can also be used in other possible application scenarios, which is not limited by the embodiment of the present application. The functions that can be implemented by each device in the application scenario shown in FIG. 3 will be described together in the subsequent method embodiments, which will not be repeated here.

In order to facilitate understanding of the multimedia resource management method provided by the embodiments of the present application, this is further described below with reference to the accompanying drawings.

FIG. 4 is a schematic flowchart of a multimedia resource management method provided by an embodiment of the present application. As shown in Figure 4, the method is applied to the recorder, and specifically includes the following steps:

In step 401, multiple scene identifiers are displayed.

In a possible implementation, the server has an account management function, so in order to ensure the information security of the recorder and determine the use authority of the logged-in user, in this application, when the user uses the recorder, he can communicate with the server through the network and use the login information Log in to the recorder. Therefore, before the multiple scene identifiers are displayed, the recorder in this application can send a login request to the server, and the login request includes the user's login information; the plurality of scene identifiers sent by the server.

In this way, the server can verify the correctness of the user information using the recorder and the use authority of the user who logs in the recorder according to the user login information in the login request, so that according to the verification result, the user who logs in the recorder can use more A scene identifier can be displayed on the interface of the recorder for the user to select, as shown in FIG. 5A . It can ensure the information security of the recorder and avoid the information security problems caused by illegal user login. For example, the default scene in FIG. 5A is an illegal scene, for example including: scene 1 is a car accident, scene 2 is running a red light, scene 3 is drunk driving, scene 4 is retrograde, scene 5 is fighting, scene 6 is driving without a license, and scene 7 is Visit, scene 8 is a checkpoint inspection. It is also possible to perform more detailed division according to the actual usage situation, or set other scenarios according to the actual situation, which is not limited in this embodiment of the present application.

In another embodiment, the recorder may also store multiple scene identifiers locally, and then periodically synchronize the scene identifiers with the server so that the scene identifiers are available when the scene identifiers are updated. The update timing can also be when the user selects a scene ID, compares it with the server's version of the scene ID, and uses the server's version of the scene ID to update if it needs to be updated.

In step 402, in response to the selection operation of the target scene identifier among the plurality of scene identifiers, the target scene identifier and the corresponding multimedia resource are associated and stored.

In a possible implementation, the user selects a scene in the interface shown in FIG. 5A according to actual needs, and the scene identifier of the selected scene is used as the target scene identifier, and the recorder can record the collected multimedia resource data and the target scene. Identity for associative storage. Thereby, classification, storage and management of multiple multimedia resources based on the scene can be realized.

In some embodiments, in order to further refine the management of multimedia data, the management efficiency is improved. The recorder can also record the start time of the current selection operation on the target scene identifier and the keyword corresponding to the target scene identifier in response to the selection operation of the target scene identifier among the multiple scene identifiers; and then record the user's login information. , the start time of the current selection operation of the target scene identification and the keyword corresponding to the target scene identification are used as the description information of the recorded multimedia resources, and the first file containing the description information is generated; The file is stored in association with the multimedia resource. Therefore, the management of multimedia resources combines scene categories, user login information and time information, so that multimedia resources can be stored and managed from multiple information dimensions.

Exemplarily, as shown in FIG. 5B , the user selects the scene 1 in FIG. 5A as the target scene, and the scene identifier of the scene 1 is the target scene identifier. After the recorder responds to the user's selection of the scene ID of the scene 1, it will generate the keyword of the scene 1, the time of selecting the scene 1 and the user's login information, and use this as the description information of the file to be generated. For example, it is implemented as the file name of the file, which is stored in the memory, and then the recorded multimedia resource is used as the content of the file, thereby obtaining a file with the multimedia resource. For example, if the scene 1 is a car accident, the keyword of the scene 1 may be CH. If user A selects the scene 1 at 17:20:30, the file name of the generated file 1 will be CH:A:17:20:30, and then Store the recorded car crash video in this file.

Wherein, the start time of the selection operation on the target scene identifier is the start time of the first recording by the user under the target scene identifier; the keyword corresponding to the target scene identifier can be set according to the actual situation, for example, it can be the pinyin of the target scene identifier The first letter can also be the first letter of the English translation of the target scene identifier, so that fuzzy search based on letters or simple search based on letters can be realized, and the convenience of querying multimedia resources in the later stage can be improved. The specific keywords may be set according to actual needs, and as long as the scene identifier can be identified, the embodiment of the present application is applicable, which is not limited in the present application.

In a possible implementation manner, multimedia resources can be collected and stored in the file while the file containing the description information is generated. Therefore, the timing of collecting multimedia resource data in this application may be in response to the identification of the target scene. Select Action to start the recording function. The image data of the multimedia resource is thus collected and saved.

When encountering special circumstances, the user can temporarily stop recording, and the user can pause the recording. Meanwhile, in order to facilitate the preview, in response to the operation of pausing the recording, preview the collected image data but stop saving the collected image data.

Thus, the image data collected and saved between the start of the recording function and the pause of the recording are multimedia resources under the corresponding file. When recording is not needed, recording can also be paused to preview without saving data, thus saving processing and storage resources.

For example, when the user may encounter resources that are not related to the multimedia resources required by the target scene identifier during the recording process, in order to save memory, it is necessary to pause the recording in the target scene identifier, but do not exit the scene corresponding to the target scene identifier. Restart recording in the target scene ID when re-encountering the multimedia resource under the target scene ID. Retaining the currently selected target scene identifier can avoid the user's operation of selecting the scene identifier again. In this application, after stopping the saving of the collected image data due to the suspension of the recording, the user can also be supported to restart the recording, and continue to use the current target scene identifier and the re-recorded data for associated storage. It can be implemented to record the start time of the current recording and the keyword corresponding to the target scene identifier in response to the operation of starting the recording; The word is used as the description information of the recorded multimedia resource, and a second file containing the description information is generated; the second file and the multimedia resource are associated and stored.

Exemplarily, in the scene 1 shown in FIG. 5B , assuming that the scene 1 is a car accident, the keyword of the scene 1 may be CH. If the user A selects the scene 1 at 17:20:30, the file 1 will be generated at this time. The file name is CH:A:17:20:30, and then the recorded car accident video is stored in this file 1, so that the name of this car accident video is the file name of this file 1. If the user is at 17:25:30 When encountering resources not related to car accidents, such as helping the elderly from 17:25:30 to 17:30:30, you can pause the recording of the car accident video at 17:25:30 and record it at 17:30:30 Start time, the file name of the generated file 2 is CH:A:17:30:30, and then continue to record the car accident video, and store the recorded car accident video in this file 2, so that the name of this car accident video is the name of this file 2 Filename CH:A:17:30:30.

During implementation, a field M may be provided, and the field value of the field M is the currently selected scene identifier. For example, in FIG. 5C , the user selects the scene identifier B at time T1, and the field value of the field M is the keyword CH1 of the scene identifier B. During the time period of time T1-T2, the user does not exit the current scene of the scene identifier B, even if the recording is paused, the field value of the field M is still CH1 of the current scene identifier B. The CH1 of the scene identification B in this field M can be read whenever recording is used for compositing into the recorded video. If the user exits the current scene B and reselects the scene identifier C at time T2, the field value of the field M is updated to the keyword CH2 of the currently selected scene identifier C, and subsequent recordings are performed based on the scene identifier C. Of course, when the field M is empty, it means that the user has not selected the target scene identifier, and the user can be reminded to select the target scene identifier.

Among them, if a video file is recorded under a target scene identifier, the recording will fail because the video file is too long and too large. In view of this, in this application, a video file recorded under a scene identifier can be segmented. It should be noted that, if the scene identifier A is not changed after selection, all files generated by recording are video files with one scene identifier. If scene identification B is re-selected, and then the same scene identification A selected before is selected, the video files recorded under the scene identification A twice still belong to video files with different scene identifications. A video file with the same scene identifier includes multiple files, and although the file name and content of each file are different, all the files are files related to the same target scene identifier A. If the user exits the target scene identification A through the back to scene button as shown in FIG. 5D after stopping the recording, it can be considered that the recording under the target scene identification A is over, from the selection operation of the target scene identification A to stopping the recording All files generated in the process of exiting the target scene identification A are stored uniformly, and all files are regarded as a complete data chain of the target scene identification A.

Exemplarily, in the scene 1 shown in FIG. 5B , assuming that the scene 1 is a car accident, the keyword of the scene 1 may be CH. If in FIG. 5E , user A selects the scene 1 at 17:20:30, then at this time The file name of the generated file 1 is CH:A:17:20:30, and then the recorded car accident resources are stored in this file. In this way, the name of this car accident resource is the file name CH:A:17:20:30 of this file 1. If the recording is paused at 17:30:30 in the middle, the recording is re-recorded at 17:45:30 until 17:50:30, and the recording of scene 1 is exited through the back to scene button as shown in Figure 5D, then file 2 will be generated at this time. The file name is CH:A:17:45:30, and then the car accident resources recorded from 17:45:30 to 17:50:30 are stored in this file 2, so that this car accident resource also includes this file 2 The file name is CH:A:17:45:30, after exiting the recording of scene 1 through the back to scene button as shown in Figure 5D at 17:50:30, the file name is CH:A:17:20:30 File 1 and file 2 with file name CH:A:17:45:30 together constitute a complete data chain.

In a possible implementation manner, during the recording process or when the recording is paused, it may be necessary to take pictures and screenshots. In this application, it is also possible to: in the process of recording the multimedia resources, based on stopping the recording and switching to The user operation of the photographing function, displaying the photographing function interface, and taking a photograph to obtain an image in response to the photographing instruction; or, in the process of recording the multimedia resource, performing a screenshot operation in response to the screenshot instruction to obtain an image, and identifying the target scene and the target scene. The image is associated with storage; and then the image and the target scene identification are sent to the server. The previewing of the multimedia resource may be previewing after pausing recording, or previewing while recording is in progress.

Among them, the functions in the recorder may include a photographing function and a recording function, the photographing function is used to obtain a static image, and the recording function is used to record a video. The image collected based on the photographing instruction may be an image obtained by taking a screenshot of the currently previewed multimedia resource, or may be an image obtained by using the photographing function after pausing the recording. Exemplarily, after selecting scene 1 as the target scene identification in Fig. 5F, start recording video, if encountering a picture that needs to be photographed during the recording process, you can pause the recording through the start or stop recording button on the left in Fig. 5F. video, and save the recorded video in file 1, then exit the recording function and enter the camera function interface in the right picture, click the camera button to take a picture, and save the collected photos in file 2, then you can exit the camera function again. Enter the video recording interface in the left picture, and continue to record video by clicking the start or stop recording button.

In another embodiment, a screen capture control is provided in the preview interface of the recording function. For example, after selecting scene 1 as the target scene identifier, the video recording starts. If a picture that needs to be photographed is encountered during the recording process, the video recording can be continued. , and through the screenshot button in the upper right corner of Figure 5G, the recorded video will be saved in file 2 through a screenshot. During the screenshot, you can continue to record the video until you exit scene 1 and save the video in file 1.

Among them, the method of obtaining screenshots is not limited to the screenshot button in FIG. 5G, but may also include gesture operations, voice control screenshots, etc., gesture operations such as sliding from top to bottom, sliding from left to right, sliding from bottom to top, and sliding from right to Sliding up and sliding from both sides to the middle are applicable to the embodiments of the present application as long as the screenshot function can be achieved.

The method of associating the scene description with the multimedia resource may be to write the relevant information of the scene identifier into the file with the file name as described above, and then store the image in the corresponding file, or it may be to combine the scene identifier and the The name of the corresponding image is written into the database table, and then the name of the image corresponding to the keyword of the corresponding scene identifier is searched according to the database table. The embodiment of the present application does not limit the manner of performing associative storage.

In a possible implementation, whether it is a multimedia resource obtained by recording a video or a multimedia resource obtained by taking a photo, the file name of the corresponding file can be set to be named after the keyword corresponding to the user information, the start time and the selected scene identifier. If the file is a multimedia resource obtained by recording a video, save the file in the video format; if it is a multimedia resource obtained by taking a photo, save the file in the image format, so that users can classify, save and query according to the file format, and get the corresponding video or photo. Wherein, all files (including videos and pictures) acquired during the period from selecting the target scene identification to exiting the same target scene identification belong to the same complete data chain.

In a possible implementation manner, in order to avoid damage to a large number of multimedia resources caused by network abnormalities or device abnormalities during the recording process, the application may store the collected image data of the multimedia resources in segments. Among them, when the multimedia resources are stored in segments, it can be implemented to manually end the recording and start the recording, so that the recorded video stream is divided into video segments and saved, or it can be implemented to automatically end the recording process by setting a fixed time interval Record and start recording, so that the recorded video stream can be automatically divided into video segments and saved. The multimedia resource data between the automatic start and end of recording each time can be saved as a separate file.

Exemplarily, a video can be set to be recorded every 10 minutes. Assuming that in the scene 1 shown in FIG. 5B, if the scene 1 is a car accident, the keyword of the scene 1 may be CH. In FIG. 5H, the user A is at 17: Select scene 1 at 20:30, then file 1 with the file name CH:A:17:20:30 will be generated. After 10 minutes, that is, stop recording file 1 at 17:30:30, and then record the car accident resource. Store in this file 1, and at the same time generate a file 2 with the file name CH:A:17:30:30 at 17:30:30, and start recording, 10 minutes later, that is, stop recording at 17:40:30 , and then store the recorded car accident resource in the file 2, so that the name of this car accident resource is the file name of this file CH:A:17:30:30. When the recording of scene 1 is exited by the back to scene button as shown in Fig. 5D, file 1 with file name CH:A:17:20:30 and file 2 with file name CH:A:17:30:30 Together they form a complete data chain.

Segmented storage can avoid damage to a large number of multimedia resources caused by network abnormalities or device abnormalities during the recording process, and can also support more accurate multimedia resource query based on the recording start time and recording end time.

In step 403, the target scene identifier, the multimedia resource, the start recording time and the end recording time of the multimedia resource are carried in the file upload request and sent to the server.

Wherein, all files in the target scene identifier can be classified according to the type of the file or the recording time of the file. When displaying, all files can be sorted according to the start time in the file name, and then the target scene identification number is carried out according to the sorting order, and finally the display is classified according to the number of the target scene identification. For example, the first file under scene identification 1 can be numbered as 1-1. The second file under scene ID 1 can be numbered 1-2, and the rest of the files can be numbered and displayed according to the same method. For example, scene 1 is a car accident, the keyword is CH, and now there are 5 files, the file names are CH:A:17:20:30, CH:A:17:30:30, CH:A:17:25: 30. CH:A:17:48:30, CH:A:17:35:30, you can identify these five files as the data in scene 1 according to the file name. Sort the time and number the five files: the file with the file name CH:A:17:20:30 is numbered 1-1, the file with CH:A:17:25:30 is numbered 1-2, CH:A:17:30:30 has file numbers 1-3, CH:A:17:35:30 has file numbers 1-4, CH:A:17:48:30 has file numbers 1-5 , the file with the earlier start time is numbered first.

The timing for sending the file upload request may be uploading all the files after the multimedia resources are all recorded for all files under the same target scene identifier, or after the multimedia resources are recorded for each file, that is, uploading each file one by one. When uploading, the keyword corresponding to the target scene identifier where the file is located needs to be uploaded together with the start time of the selection operation for the target scene identifier where the file is located.

In a possible implementation manner, the policy for file uploading may be configured as automatic uploading or manual uploading. When it is configured to upload automatically, the recorded files can be automatically uploaded to the server in the background when the network is normal. As shown in FIG. The upload can be implemented as the following steps:

In step 601, recording of multimedia resources is started based on the target scene identification.

In step 602, it is judged whether the recording of the multimedia resources in the file is completed, if not, proceed to step 601, if completed, in step 603, determine whether the network is available, if not, in step 604, wait for the network to change until The network is available. If the network is available, in step 605, a file upload request is sent and the file is uploaded.

As shown in FIG. 7 , it is a schematic flowchart of a recorder recording a multimedia resource provided by an embodiment of the present application. According to the foregoing description, the process of recording multimedia resources by the recorder can be specifically performed as the steps shown in FIG. 7 :

In step 701, scene identification data is acquired.

In step 702, a target scene identifier is selected.

In step 703, the collected multimedia data is previewed, a corresponding file is generated, and the multimedia resource is recorded.

In step 704, it is judged whether to stop recording, if not, proceed to step 703, if the recording is stopped, in step 705, preview the recorded multimedia resources.

In step 706, it is judged whether to continue recording, if it continues to record, go back to step 703, if not, in step 707, judge whether to quit the recording of the target scene, if not, go back to step 705, if quit, go to step 705 In 708, the file is uploaded.

Among them, if the back to scene button is clicked, it is considered to exit the target scene recording, and if the back to scene button is not clicked, it is considered that the target scene recording is not exited.

Thus, the recorder completes the entire process of logging in to generate a complete data chain. When there are multiple files in a complete data chain, they can be sorted and displayed to the user as shown in FIG. 8A .

In a possible implementation, the recorder can also query the required multimedia resources from a large number of multimedia resources in the database. Therefore, the method described in this application further includes: terminal equipment (including recorders, mobile phones, and computers) A query request can be sent to the server, and the query request includes query conditions, and then the multimedia resources returned by the server for the query conditions are received and displayed, and the query conditions include keywords corresponding to the scene identifiers, recorded At least one of the start time and the end time of the recording.

Among them, the user can query according to any condition of the user's login information, the start time of the recording, the end time of the recording, the keyword corresponding to the scene identifier, and the format of the file, or according to any combination of the above conditions. The more conditions you set, the more accurate the query results will be. For example, it is possible to obtain the multimedia resources that the user started recording at this time according to the combination of the user's login information and the recording start time, or to obtain the user's login information and the combination of keywords corresponding to the scene identifier. The user's multimedia resources under this scene ID.

Therefore, the active division of the multimedia information by the recorder and the associated storage of the target scene identifier and the corresponding multimedia resources are realized, so that the division of the multimedia information is more accurate, and the subsequent query of the multimedia resources according to the corresponding query conditions is more accurate.

Based on the same inventive concept, the present application provides a multimedia resource management method, which is applied to a server. The method includes: receiving a file upload request sent by a recorder, where the file upload request includes a target scene identifier, the multimedia resource , the start time of the multimedia resource recording and the end time of the recording; associate and store the keyword corresponding to the target scene identifier, the multimedia resource, the start time of the multimedia resource recording and the end time of the recording.

In a possible implementation manner, the method includes: receiving a query request sent by a terminal device, where the query request includes query conditions, and the query conditions include keywords corresponding to the scene identifier, recording start time and recording at least one kind of information in the end time of the stored multimedia resource set based on the query condition, and send the query result to the terminal device.

Wherein, the terminal device may be an electronic device including but not limited to a recorder, a mobile terminal, a desktop computer, a mobile computer, a tablet computer, a server, and the like.

It can be implemented that, when receiving the file uploaded by the recorder, the server associates and stores the keyword corresponding to the target scene identifier corresponding to the file, the multimedia resource, the start time of the multimedia resource recording, and the end time of the recording. , and save it in the database, when receiving the query request sent by the recorder, according to the query conditions in the query request, query from the database, and feed back the query results to the recorder, so that the user can view the corresponding file. multimedia resources.

Based on the foregoing description, the embodiment of the present application displays multiple scene identifiers; in response to the selection operation of the target scene identifier among the multiple scene identifiers, the target scene identifier and the corresponding multimedia resource are stored in association; The target scene identifier, the multimedia resource, the start recording time and the end recording time of the multimedia resource are carried in the file upload request and sent to the server, so that the recorder can have the initiative to divide the multimedia information. When the user uses the recorder You can directly select the target scene logo to record multimedia information, or you can directly exit the multimedia information recording under the current scene logo when recording another multimedia information, and select the corresponding scene logo to record the multimedia information, so as to realize the active division of the multimedia information by the recorder. And the target scene identifier and the corresponding multimedia resource are stored in association, so that the multimedia information can be divided more accurately, and the subsequent accurate query of the multimedia information is facilitated.

Similar parts between the embodiments provided in the present application may be referred to each other. The specific embodiments provided above are just a few examples under the general concept of the present application, and do not constitute a limitation on the protection scope of the present application. For those skilled in the art, any other implementations expanded according to the solution of the present application without creative work fall within the protection scope of the present application.

After the multimedia resource management method of the exemplary embodiment of the present application is introduced, next, the server provided according to the embodiment of the present application is introduced.

In some possible implementations, a server according to the present application may include at least one processor and at least one memory. The memory stores program codes, which, when executed by the processor, cause the processor to execute the multimedia resource management methods described above in this specification according to various exemplary embodiments of the present application. For example, the processor may perform steps as in the multimedia resource management method.

The server 101 according to this embodiment of the present application is described below with reference to FIG. 8B . The server 101 shown in FIG. 8B is only an example, and should not impose any limitations on the functions and scope of use of the embodiments of the present application.

As shown in FIG. 8B, the server 101 is represented in the form of a general server. Components of the server 101 may include, but are not limited to: the above-mentioned at least one processor 801 , the above-mentioned at least one memory 802 , and a bus 803 connecting different system components (including the memory 802 and the processor 801 ).

Bus 803 represents one or more of several types of bus structures, including a memory bus or memory controller, a peripheral bus, a processor, or a local bus using any of a variety of bus structures.

Memory 802 may include readable media in the form of volatile memory, such as random access memory (RAM) 8021 and/or cache memory 8022 , and may further include read only memory (ROM) 8023 .

The memory 802 may also include a program/utility 8025 having a set (at least one) of program modules 8024 including, but not limited to, an operating system, one or more application programs, other program modules, and program data, which An implementation of a network environment may be included in each or some combination of the examples.

The server 101 may also communicate with one or more external devices 804 (eg, keyboards, pointing devices, etc.), may also communicate with one or more devices that enable a user to interact with the server 101 and/or enable the server 101 to communicate with a or any device (eg, router, modem, etc.) that communicates with multiple other servers. Such communication may take place through input/output (I/O) interface 805 . Also, the server 101 may communicate with one or more networks (eg, a local area network (LAN), a wide area network (WAN), and/or a public network such as the Internet) through a network adapter 806 . As shown, network adapter 806 communicates with other modules for server 101 via bus 803 . It should be understood that, although not shown, other hardware and/or software modules may be used in conjunction with server 101, including but not limited to: microcode, device drivers, redundant processors, external disk drive arrays, RAID systems, tape drives, and Data backup storage system, etc.

The actual deployment of the server 101 may be directly deployed on the server hardware or in a virtual environment provided by a cloud service provider, but will eventually be correspondingly stored in the physical memory.

In an exemplary embodiment, a computer-readable storage medium including instructions, such as a memory 802 including instructions, is also provided, and the above-mentioned instructions can be executed by the processor 801 to complete the above-mentioned multimedia resource management method. Alternatively, the storage medium may be a non-transitory computer-readable storage medium, for example, the non-transitory computer-readable storage medium may be ROM, random access memory (RAM), CD-ROM, magnetic tape, floppy disk, and optical data storage equipment, etc.

In an exemplary embodiment, a computer program product is also provided, including a computer program, which, when executed by the processor 501, implements any one of the multimedia resource management methods provided in this application.

In an exemplary embodiment, various aspects of a multimedia resource management method provided by the present application can also be implemented in the form of a program product, which includes program code, and when the program product runs on a computer device, the program code is used for The computer device is caused to execute the steps in the multimedia resource management method according to various exemplary embodiments of the present application described above in this specification.

The program product may employ any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. The readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus or device, or a combination of any of the above. More specific examples (non-exhaustive list) of readable storage media include: electrical connections with one or more wires, portable disks, hard disks, random access memory (RAM), read only memory (ROM), erasable programmable read only memory (EPROM or flash memory), optical fiber, portable compact disk read only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

The program product for the multimedia resource management method of the embodiment of the present application may adopt a portable compact disk read only memory (CD-ROM) and include program codes, and may be executed on a server. However, the program product of the present application is not limited thereto, and in this document, a readable storage medium may be any tangible medium that contains or stores a program that can be used by or in conjunction with an instruction execution system, apparatus, or device.

A readable signal medium may include a propagated data signal in baseband or as part of a carrier wave, carrying readable program code therein. Such propagated data signals may take a variety of forms including, but not limited to, electromagnetic signals, optical signals, or any suitable combination of the foregoing. A readable signal medium can also be any readable medium, other than a readable storage medium, that can transmit, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device.

Program code embodied on a readable medium may be transmitted using any suitable medium including, but not limited to, wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

Program code for performing the operations of the present application may be written in any combination of one or more programming languages, including object-oriented programming languages such as Java, C++, etc., as well as conventional procedural programming Language - such as the "C" language or similar programming language. The program code may execute entirely on the user's server, partly on the user's device, as a stand-alone software package, partly on the user's server and partly on a remote server, or entirely on a remote server or server. In the case of a remote server, the remote server may be connected to the user server through any kind of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external server (eg, using an Internet service provider via Internet connection).

It should be noted that although several units or sub-units of the apparatus are mentioned in the above detailed description, this division is merely exemplary and not mandatory. Indeed, according to embodiments of the present application, the features and functions of two or more units described above may be embodied in one unit. Conversely, the features and functions of one unit described above may be further subdivided to be embodied by multiple units.

Furthermore, although the operations of the methods of the present application are depicted in the figures in a particular order, this does not require or imply that the operations must be performed in the particular order, or that all illustrated operations must be performed to achieve desirable results. Additionally or alternatively, certain steps may be omitted, multiple steps may be combined to be performed as one step, and/or one step may be decomposed into multiple steps to be performed.

As will be appreciated by those skilled in the art, embodiments of the present application may be provided as a method, a recorder or a computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein.

The present application is described with reference to flowchart illustrations and/or block diagrams of methods, recorders (systems), and computer program products according to the present application. It will be understood that each flow and/or block in the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to the processor of a general purpose computer, special purpose computer, embedded processor or other programmable data processing device to produce a machine such that the instructions executed by the processor of the computer or other programmable data processing device produce Means for implementing the functions specified in a flow or flow of a flowchart and/or a block or blocks of a block diagram.

These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory result in an article of manufacture comprising instruction means, the instructions The apparatus implements the functions specified in the flow or flow of the flowcharts and/or the block or blocks of the block diagrams.

These computer program instructions can also be loaded on a computer or other programmable data processing device to cause a series of operational steps to be performed on the computer or other programmable device to produce a computer-implemented process such that The instructions provide steps for implementing the functions specified in the flow or blocks of the flowcharts and/or the block or blocks of the block diagrams.

Obviously, those skilled in the art can make various changes and modifications to the present application without departing from the spirit and scope of the present application. Thus, if these modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is also intended to include these modifications and variations.

Claims (10)

1. A multimedia resource management method is applied to a recorder, and the method comprises the following steps:

displaying a plurality of scene identifications;

responding to the selection operation of a target scene identifier in the scene identifiers, and performing associated storage on the target scene identifier and the corresponding multimedia resource;

and carrying the target scene identification, the multimedia resource, and the starting recording time and the ending recording time of the multimedia resource in a file uploading request and sending the file uploading request to a server.

2. The method of claim 1, wherein prior to said presenting the plurality of scene identifiers, the method further comprises:

sending a login request to a server, wherein the login request comprises login information of a user;

and responding to the verification passing result of the server to the login information, and acquiring the plurality of scene identifications sent by the server.

3. The method according to claim 1, wherein the associating and storing the target scene identifier and the corresponding multimedia resource in response to the selection operation of the target scene identifier from the plurality of scene identifiers specifically comprises:

responding to the selection operation of a target scene identifier in a plurality of scene identifiers, and recording the starting time of the current selection operation of the target scene identifier and a keyword corresponding to the target scene identifier;

taking the login information of the user, the start time of the current selection operation on the target scene identification and the keyword corresponding to the target scene identification as description information of the recorded multimedia resource, and generating a first file containing the description information;

and storing the first file and the multimedia resource in an associated manner.

4. The method of claim 3, further comprising:

responding to the selection operation of the target scene identification, starting a recording function to acquire and store image data of the multimedia resource;

and in response to the operation of suspending the recording, previewing the acquired image data and stopping saving the acquired image data.

5. The method of claim 4, wherein after previewing the captured image data and ceasing to save the captured image data, the method further comprises:

responding to the operation of starting recording, and recording the starting time of the current recording and the keywords corresponding to the target scene identification;

taking the login information of the user, the recording start time and the keywords corresponding to the target scene identification as description information of the recorded multimedia resource, and generating a second file containing the description information;

and storing the second file and the multimedia resource in an associated manner.

6. The method according to any one of claims 4-5, further comprising:

in the process of recording the multimedia resources, displaying a photographing function interface based on user operation of stopping recording and switching to a photographing function, and responding to a photographing instruction to obtain a photographing image; or,

responding to the screenshot instruction to perform screenshot operation to obtain an image in the process of recording the multimedia resource;

storing the target scene identification and the image in an associated manner;

and sending the image and the target scene identification to the server.

7. A multimedia resource management method applied to a server, the method comprising:

receiving a file uploading request sent by a recorder, wherein the file uploading request comprises keywords corresponding to a target scene identifier, the multimedia resource, the recording start time of the multimedia resource and the recording end time;

and performing associated storage on the target scene identification, the multimedia resource, the recording start time of the multimedia resource and the recording end time.

8. The method of claim 7, wherein the method comprises:

receiving a query request sent by a terminal device, wherein the query request comprises a query condition, and the query condition comprises at least one of keywords corresponding to a scene identifier, a recording start time and a recording end time;

and inquiring the stored multimedia resource set based on the inquiry condition, and sending an inquiry result to the terminal equipment.

9. A recorder, comprising:

the device comprises a camera, a display, a processor and a memory;

the camera is used for acquiring multimedia resource data;

the display is used for displaying the multimedia resource data;

the memory to store the processor-executable instructions;

the processor is configured to execute the instructions to implement the multimedia asset management method of any of claims 1-6.

10. A server, comprising:

a processor;

a memory for storing the processor-executable instructions;

wherein the processor is configured to execute the instructions to implement the multimedia asset management method of any of claims 7-8.

Images