Web terminal-based preplan data processing method and system

Abstract

The application relates to a WEB terminal-based preplan data processing method and system, which comprises the following steps: a WEB terminal establishes and opens a preplan, and generates preplan data and sends the preplan data to a guide control server; when the preplan is in an open state, the guide control server sends a first request for preplan recording to a recording server according to the preplan data, wherein the first request comprises a device list, a device IP address and a device port of all audio and video decoding devices required to be recorded in the preplan; the recording server sends a second request to the audio and video decoding devices according to the first request to acquire audio and video input streams for recording and storage, and sends recording information to the guide control server; and the guide control server sends the received recording information to all WEB terminals. The full-scene recording of the preplan is realized, the output content of all audio and video decoding devices in the preplan is automatically recorded in the preplan open state, recording files are generated, and the recording files are uniformly associated with the execution record of the preplan for management.

Description

Technical Field

[0001] This application relates to the field of audio and video data processing technology, specifically to a method and system for processing pre-planned data based on a web terminal, particularly applicable to the recording and playback of pre-planned data for audio and video. Background Technology

[0002] Audio push technology associates the account of an audio encoding device with the account of an audio decoding device. Once associated, the audio encoding device sends the audio input stream to the audio decoding device for playback. Similarly, video push technology associates the account of a video encoding device with the account of a video decoding device. Once associated, the video encoding device sends the video input stream to the video decoding device for playback.

[0003] Audio encoding devices and video encoding devices are collectively referred to as audio-video encoding devices, and audio decoding devices and video decoding devices are collectively referred to as audio-video decoding devices. Audio and video are collectively referred to as audio-video. When multiple audio-video encoding devices and multiple audio-video decoding devices exist in the system, the system can establish multiple audio-video pushes. However, each set of audio-video pushes requires the user to perform an association operation one by one from the terminal, so that one audio-video encoding device is associated with one audio-video decoding device. To reduce the establishment of such redundant audio-video push relationships, multiple sets of audio-video push relationships are pre-set to the server. When an audio-video push needs to be established, the user terminal sends a message to the server, and the server automatically establishes the pre-saved audio-video push relationship. This is the contingency planning technology.

[0004] The contingency plan is used to manage multiple audio and video push relationships. When an audio and video push contingency plan is executed, all audio and video pushes in the plan will be executed simultaneously. The user terminal can enable or disable all audio and video push relationships in the plan with one click.

[0005] With the development of audio and video technology, there is a growing demand for recording the execution process of contingency plans during implementation and control. This allows for the querying and playback of historical execution records after the plan is completed, with playback functions including pause, stop, speed adjustment, skipping, and marking. In complex scenarios, this application investigates how to quickly and effectively deliver push notifications (audio and video signals from microphones, cameras, etc.) to the relevant users, record these notifications, and rapidly play back the recorded information. Summary of the Invention

[0006] The purpose of this application is to provide a method for processing contingency plan data based on a web terminal, comprising the following steps:

[0007] The web terminal establishes and activates the contingency plan, and generates contingency plan data to send to the control server;

[0008] When the contingency plan is enabled, the control server sends the first request for recording the contingency plan to the recording server based on the contingency plan data. The first request includes a device list, device IP address, and device port of all audio and video decoding devices that need to be recorded in the contingency plan.

[0009] The recording server sends a second request to the audio and video decoding device based on the first request to obtain the audio and video input stream for recording and storage, and sends the recording information to the control server;

[0010] The control server will send the received recording information to all web terminals.

[0011] The technical effect of this application's technical solution is that it realizes full-scene recording of the contingency plan. When the contingency plan is enabled, it automatically records the output content of all audio and video decoding devices in the contingency plan, generates recording files, and uniformly associates them with the execution record of the contingency plan for management.

[0012] In one embodiment of this technical solution, the step of "establishing and activating the pre-plan on the WEB terminal, and generating pre-plan data to send to the control server" includes:

[0013] The web terminal registers the login user, the device account of the audio and video encoding device, and the device account of the audio and video decoding device to the softswitch server. The softswitch server sends the login status of the login user, the device IP address and device port corresponding to all device accounts based on the SIP protocol to the control server.

[0014] The web terminal establishes the association between audio and video encoding devices and audio and video decoding devices, and generates pre-plan data for the control server.

[0015] The control server executes the activation plan based on the activation plan request from the web terminal.

[0016] In one embodiment of this technical solution, the contingency plan data includes a contingency plan number with a unique identifier, device IP address and device port, the association between audio / video encoding devices and audio / video decoding devices, and push information.

[0017] In one embodiment of this technical solution, the step of "the recording server sending a second request to the audio / video decoding device to obtain the audio / video input stream for recording and storage according to the first request, and sending the recording information to the control server" includes:

[0018] After receiving the first request for recording the pre-planned audio / video, the recording server creates a directory for recording the pre-planned audio / video and within that directory, it creates a subdirectory named after the device account of each audio / video decoding device that needs to be recorded.

[0019] The recording server sends a second request to the audio and video decoding device to obtain the audio and video input stream, generates a recording file and stores it in a subdirectory, and generates recording information, including the recording directory path, the start time of the recording file, and the duration of the recording file;

[0020] Send recording information to the control server.

[0021] In one embodiment of this technical solution, the step of "the control server sending the received recording information to all WEB terminals" further includes the following step:

[0022] The control server receives the pre-recorded playback request from the web terminal, finds the device accounts of all audio and video decoding devices based on the pre-recorded data, and notifies the audio and video decoding devices to start playing the recorded file.

[0023] The audio and video decoding device generates a new path based on the recording path and device account in the pre-planned playback request, retrieves the list of recorded files under the new path from the on-demand server, and plays the recorded files.

[0024] The audio and video decoding device periodically acquires time segments of the recorded files and plays them back, sequentially playing all the recorded files in the recorded file list.

[0025] In one embodiment of this technical solution, a step of "replaying the pre-planned playback at double speed" is also included, specifically:

[0026] When in the pre-plan playback state, the web terminal sends a pre-plan playback speed adjustment request. The speed adjustment request includes the pre-plan number, the path to the recording file of the pre-plan playback, and the playback speed.

[0027] After receiving the speed-up playback request, the control server forwards the speed-up playback request to all audio and video decoding devices in the plan;

[0028] After receiving a request to play at a different speed, the audio / video decoding device plays the recorded file according to the playback speed.

[0029] In one embodiment of this technical solution, a step of "jumping to a specified time for playback" is also included, specifically:

[0030] When in the pre-plan playback state, the web terminal sends a jump request to jump to the specified time for playback. The jump request includes the pre-plan number, the path to the recording file of the pre-plan playback, and the specified time for jump.

[0031] After receiving the redirection request, the control server forwards the redirection request to all audio and video decoding devices in the plan;

[0032] After receiving a jump request to play back at a specified time, the audio and video decoding device retrieves the time segment recorded at the specified time from the video-on-demand server and plays it.

[0033] In one embodiment of this technical solution, a step of "pausing or ending the replay of the plan" is also included, specifically:

[0034] When in the pre-plan playback state, the web terminal sends a pause request or end request for the pre-plan playback. Both the pause request and the end request include the pre-plan number and the recording file path.

[0035] After receiving a pause or end request, the control server forwards it to all audio and video decoding devices in the plan;

[0036] Upon receiving a pause or end request, the audio / video decoding device pauses or ends playback of the recorded file according to the request type.

[0037] In one embodiment of this technical solution, a step of "marking when the plan is activated or when the plan is replayed" is also included, specifically:

[0038] The web terminal sends a marking operation request to mark or modify a mark. The marking operation request includes the pre-recorded identifier, the mark time, and the mark content.

[0039] After receiving the marking operation request, the guidance and control server stores the marking operation request in the database and returns a success response;

[0040] When the pre-setup is activated or during playback, the audio and video decoding device receives a tagging operation request, retrieves the time segment recorded at the tagging point from the on-demand server, and plays it.

[0041] Another technical solution of this application is to provide a pre-plan data processing system based on a web terminal, including a web terminal, a control server, and a recording server, wherein...

[0042] The WEB terminal is used to establish and activate the contingency plan, generate contingency plan data and send it to the control server, and receive recording information.

[0043] When the pre-plan is enabled, the control server sends a first request for pre-plan recording to the recording server based on the pre-plan data. The first request includes a device list, device IP address, and device port of all audio and video decoding devices that need to be recorded in the pre-plan. The control server receives the recording information from the recording server and sends it to all WEB terminals.

[0044] The recording server sends a second request to the audio and video decoding device based on the first request to obtain the audio and video input stream for recording and storage, and sends the recording information to the control server.

[0045] In one embodiment of this technical solution, a video-on-demand server is also included. The video-on-demand server is used to store the recording path generated by the audio and video decoding device according to the recording path in the pre-planned playback request and the new path generated by the device account, and to send the list of recorded files under the new path to the audio and video decoding device. Attached Figure Description

[0046] Figure 1 This is a technical architecture diagram of the plan recording and plan playback of the plan data processing system in the embodiments of this application.

[0047] Figure 2 This is a flowchart illustrating the registration process of the preliminary data processing method in this application embodiment.

[0048] Figure 3 This is a flowchart of the pre-plan recording process for the pre-plan data processing method in the embodiments of this application.

[0049] Figure 4 This is a flowchart illustrating the pre-plan playback and playback control process of the pre-plan data processing method in this application embodiment.

[0050] Figure 5 This is a flowchart illustrating the process of marking points in the data processing system for the contingency plan in this application.

[0051] Figure 6 This is a flowchart illustrating the steps of recording and playing back the contingency plan in the contingency plan data processing method described in this application. Detailed Implementation

[0052] The embodiments of this application are described in detail below. Examples of these embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals denote the same or similar elements or elements having the same or similar functions throughout. The embodiments described below with reference to the accompanying drawings are exemplary and intended to explain this application, and should not be construed as limiting this application.

[0053] In the description of this application, it should be understood that the terms "center", "longitudinal", "lateral", "length", "width", "thickness", "upper", "lower", "front", "rear", "left", "right", "vertical", "horizontal", "top", "bottom", "inner", "outer", "clockwise", "counterclockwise", etc., indicate the orientation or positional relationship based on the orientation or positional relationship shown in the accompanying drawings. They are used only for the convenience of describing this application and simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, or be constructed and operated in a specific orientation. Therefore, they should not be construed as limitations on this application.

[0054] Furthermore, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature. In the description of this application, "multiple" means two or more, unless otherwise explicitly specified.

[0055] In this application, unless otherwise expressly specified and limited, the terms "installation," "connection," "linking," and "fixing," etc., should be interpreted broadly. For example, they can refer to a fixed connection, a detachable connection, or an integral connection; they can refer to a mechanical connection or an electrical connection; they can refer to a direct connection or an indirect connection through an intermediate medium; and they can refer to the internal connection between two components. Those skilled in the art can understand the specific meaning of the above terms in this application according to the specific circumstances.

[0056] In this application, unless otherwise expressly specified and limited, "above" or "below" the second feature can include direct contact between the first and second features, or contact between the first and second features through another feature between them. Furthermore, "above," "over," and "on top" of the second feature includes the first feature being directly above or diagonally above the second feature, or simply indicates that the first feature is at a higher horizontal level than the second feature. "Below," "below," and "under" the second feature includes the first feature being directly below or diagonally below the second feature, or simply indicates that the first feature is at a lower horizontal level than the second feature.

[0057] The present application will now be described in further detail with reference to specific embodiments and accompanying drawings.

[0058] like Figure 1 As shown in the figure, the first embodiment is a contingency plan data processing system, including a WEB terminal, a control server, a softswitch server, a recording server, a video-on-demand server, and several audio and video encoding devices and several audio and video decoding devices. The control server communicates with the audio and video encoding devices and the audio and video decoding devices respectively. The control server automatically establishes the audio and video push relationship between the pre-saved audio and video encoding devices and the audio and video decoding devices, that is, establishes the contingency plan.

[0059] like Figures 1 to 3 As shown in the figure, based on the above-mentioned contingency plan data processing system, this second embodiment is a contingency plan data processing method based on a web browser as a client, including the following steps:

[0060] S1: Using a browser, the login user of the web terminal, the device accounts of the audio and video encoding devices and the audio and video decoding devices are all registered to the softswitch server. The softswitch server will notify the control server of the login status of the login user, the device IP address and the device port.

[0061] Device IP addresses and device ports are based on the SIP protocol (Session Initialization Protocol, a multimedia communication protocol developed by the IETF (Internet Engineering Task Force)). Audio and video encoding devices can be devices that encode audio for microphones or devices that encode video for cameras. Audio and video decoding devices are devices that encode audio (e.g., decode and play it on speakers) or devices that decode video (e.g., decode and display it on a screen).

[0062] S2: Use a web terminal to pre-establish a connection between audio and video encoding devices and audio and video decoding devices. For example, the device account in the audio and video encoding device can push video resources captured by multiple cameras to the device account in the audio and video decoding device for display on the screen. Similarly, audio resources from multiple microphones can be pushed to the speakers for playback.

[0063] S3: On the web terminal page, click the "Save Plan" button, enter the plan name, and click "Save" to save the plan data containing all current push information to the control server.

[0064] S4: The web terminal page begins executing the pre-plan. The web terminal sends an HTTP message to start executing the pre-plan. The HTTP message carries the pre-plan number, which is the unique identifier ID of the pre-plan. After receiving the pre-plan execution message, the control server retrieves the pre-plan number carried in the HTTP message, searches for the pre-plan data, finds the push information between all audio and video encoding devices and audio and video decoding devices, and uses the SIP protocol to notify all audio and video decoding devices to enable the push service. After the pre-plan is enabled, all audio and video encoding and decoding devices will be consistent with the state when the pre-plan was saved.

[0065] S5: When the contingency plan is enabled, automatically start the contingency plan recording process. The automatic start of the contingency plan recording process is explained below:

[0066] S51: After the control server sends the audio and video push message, it automatically sends the list of all decoding devices that need to be recorded in the plan to the recording server in the MESSAGE format of the SIP protocol (MESSAGE is a computer file format). The MESSAGE format request message carries the list of audio and video decoding devices in the plan, as well as the device IP address and device port of each device.

[0067] S52: The request message in MESSAGE format carries the device IP address and device port of each audio and video encoding device. The recording server can directly communicate with the audio and video decoding device for media negotiation. The negotiation communication process no longer goes through the control server, reducing the audio and video desynchronization problem caused by the delay caused by the negotiation message going through the control server.

[0068] S53: After receiving the pre-recorded recording request, the recording server creates a directory for the pre-recorded content and creates a subdirectory named after the device account for each device account that needs to be recorded. It sends an INVITE request message to the audio / video codec device to retrieve the input video or audio stream and stores it in the recording file.

[0069] If the audio / video decoding device has no input, it sends a mute packet or a default image to the recording server. When the preset is activated, if the audio / video decoding device has a new input data stream, it sends the new input data stream to the recording server to achieve audio-visual synchronization when all devices play audio and video during preset playback.

[0070] S54: After starting the pre-recorded recording, the recording server sends a request message in SIP protocol MESSAGE format to the control server, which contains recording information such as the pre-recorded recording directory path, recording file start time, and recording file duration.

[0071] S55: After receiving the recording message from the recording server to start recording, the control server pushes it to all web terminals via an HTTP SSE format communication message.

[0072] S6: When the contingency plan needs to end, click the "End Contingency Plan" button on the web terminal page to send an HTTP message to end the contingency plan. The HTTP message carries the contingency plan number. After receiving the HTTP message to end the contingency plan, the control server uses the SIP protocol to notify all audio and video decoding devices to end the push service. At the same time, the control server sends a request message in SIP protocol MESSAGE format to end the contingency plan recording request to the recording server.

[0073] like Figures 4 to 6As shown in the figure, the pre-planned data processing method based on a web browser as a client in this embodiment may further include the following steps:

[0074] S7: The web terminal can enable one-click playback of pre-planned scenarios. The specific process is as follows:

[0075] S71: Select the recorded plan that needs to be replayed in the WEB terminal interface to perform full-scene plan replay. The WEB terminal sends an HTTP message to the control server to start the plan replay. The HTTP message carries information such as the plan number and the recording directory path of the plan replay.

[0076] S72: After receiving the HTTP message to start playback of the pre-recorded plan, the control server looks up the pre-recorded plan data based on the pre-recorded plan number carried in the HTTP message, finds the device accounts of all audio and video decoding devices, and uses a message in SIP protocol MESSAGE format to notify all audio and video decoding devices to start playing the pre-recorded plan file.

[0077] S73: After receiving a playback request, the audio and video decoding device (including audio decoding device and video decoding device) generates a new path by adding its own device account to the pre-planned recording path in the MESSAGE message, sends an HTTP message to the on-demand server to obtain the file list under the new path, and plays the recorded files in ascending order of time. The audio and video decoding device periodically obtains the time segment of the recorded file via HTTP and plays it. After playing a file, it will continue to play the next recorded file in the file list.

[0078] S8: When in the pre-plan playback state, play the pre-plan playback at an accelerated speed. The specific instructions for the accelerated playback process are as follows:

[0079] S81: The web terminal sends an HTTP message to start playback of the pre-set playback speed. The HTTP message carries the pre-set number and the path of the recording file to be started, the playback speed, and other information.

[0080] Step 2: After receiving the HTTP message for speed-up playback, the control server converts the HTTP message for speed-up playback into a SIP protocol MESSAGE message and forwards it to all audio and video decoding devices in the current plan.

[0081] S83: After receiving the MESSAGE message requesting playback speed adjustment, the audio / video decoding device plays the recorded file according to the playback speed adjustment.

[0082] S9: When in the contingency plan playback state, the playback will jump to a specified time. The specific process for jumping to a specified time playback is as follows:

[0083] S91: The web terminal sends an HTTP message to jump to the specified time for playback. The HTTP message carries information such as the pre-plan number, the path of the recording file to start playback, and the jump time.

[0084] S92: After receiving the HTTP message requesting a jump to a specified playback time, the control server converts the HTTP message into a SIP protocol MESSAGE message and forwards it to all audio and video decoding devices in the plan.

[0085] S93: After receiving the MESSAGE message requesting playback at a specified time, the audio / video decoding device obtains the time segment recorded at the specified time from the on-demand server via HTTP message and plays it.

[0086] S10: When in the pre-plan playback state, the process of pausing, playing, and ending playback is as follows:

[0087] S101: The web terminal sends HTTP messages for playback pause, play, end, etc. The HTTP messages carry information such as the pre-plan number and the recording file path;

[0088] S102: After receiving playback pause, play, or end messages, the control server converts the messages into SIP protocol MESSAGE messages and forwards them to all audio and video decoding devices in the plan.

[0089] S103: After receiving the MESSAGE message requesting playback, the audio / video decoding device performs operations such as playing, pausing, or ending playback on the recorded file according to the command type.

[0090] S11: During the activation or playback of the contingency plan, the marker function can be used through the web terminal interface to add, modify, and delete markers. The specific process for adding markers is as follows:

[0091] S111: The web terminal sends an HTTP message to mark or modify a marker. The HTTP message carries information such as the pre-recorded record identifier ID, marker time information, and marker content.

[0092] S112: After receiving the marking point message, the guidance and control server stores the marking point information in the database and returns a success response.

[0093] S113: During the playback of the pre-set plan, the web terminal page can click on the marker points added during the pre-set plan startup or playback to quickly jump to the location of the marker point, and the corresponding audio and video decoding device will output the image or sound content at that time point.

[0094] Thus, the method in this embodiment can realize full-scene playback, and all audio and video output devices will synchronously play the output content when the task is executed, as well as support functions such as speed playback, jumping to a specified time playback, and using the marker point function during the pre-planned playback process.

[0095] The various embodiments of this application have been described above. These descriptions are exemplary and not exhaustive, nor are they limited to the disclosed embodiments. Many modifications and variations will be apparent to those skilled in the art without departing from the scope and spirit of the described embodiments. The terminology used herein is chosen to best explain the principles, practical application, or improvement of the technology in the market, or to enable others skilled in the art to understand the embodiments disclosed herein.

Claims

1. A method for processing contingency plan data based on a web terminal, characterized in that, The steps include the following: The web terminal establishes and activates the contingency plan, and generates contingency plan data to send to the control server; When the contingency plan is enabled, the control server sends the first request for recording the contingency plan to the recording server based on the contingency plan data. The first request includes a device list, device IP address, and device port of all audio and video decoding devices that need to be recorded in the contingency plan. The recording server sends a second request to the audio / video decoding device based on the first request to obtain the audio / video input stream for recording and storage, and sends recording information to the control server. This includes: after receiving the first request for pre-planned recording, the recording server creates a directory for pre-planned recording, and within this directory, creates a subdirectory named after the device account of each audio / video decoding device that needs to be recorded; the recording server sends a second request to the audio / video decoding device to obtain the audio / video input stream, generates a recording file stored in the subdirectory, and generates recording information, including the recording directory path, recording start time, and recording duration; and sends the recording information to the control server. The control server will send the received recording information to all web terminals.

2. The method for processing contingency plan data based on a web terminal according to claim 1, characterized in that, The step of "establishing and activating the pre-plan on the WEB terminal, and generating pre-plan data and sending it to the control server" includes: The web terminal registers the login user, the device account of the audio and video encoding device, and the device account of the audio and video decoding device to the softswitch server. The softswitch server sends the login status of the login user, the device IP address and device port corresponding to all device accounts based on the SIP protocol to the control server. The web terminal establishes the association between audio and video encoding devices and audio and video decoding devices, and generates pre-plan data for the control server. The control server executes the activation plan based on the activation plan request from the web terminal.

3. The method for processing contingency plan data based on a web terminal according to claim 2, characterized in that, The contingency plan data includes a uniquely identified contingency plan number, device IP address and device port, the association between audio / video encoding devices and audio / video decoding devices, and push information.

4. The method for processing contingency plan data based on a web terminal according to claim 1, characterized in that, The step of "the control server sends the received recording information to all web terminals" also includes the following steps: The control server receives the pre-recorded playback request from the web terminal, finds the device accounts of all audio and video decoding devices based on the pre-recorded data, and notifies the audio and video decoding devices to start playing the recorded file. The audio and video decoding device generates a new path based on the recording path and device account in the pre-planned playback request, retrieves the list of recorded files under the new path from the on-demand server, and plays the recorded files. The audio and video decoding device periodically acquires time segments of the recorded files and plays them back, sequentially playing all the recorded files in the recorded file list.

5. The method for processing contingency plan data based on a web terminal according to claim 4, characterized in that, It also includes a step of "playing the pre-planned replay at an accelerated speed," specifically: When in the pre-plan playback state, the web terminal sends a pre-plan playback speed adjustment request. The speed adjustment request includes the pre-plan number, the path to the recording file of the pre-plan playback, and the playback speed. After receiving the speed-up playback request, the control server forwards the speed-up playback request to all audio and video decoding devices in the plan; After receiving a request to play at a different speed, the audio / video decoding device plays the recorded file according to the playback speed.

6. The method for processing contingency plan data based on a web terminal according to claim 4, characterized in that, It also includes a step to "jump to a specified time for playback", specifically: When in the pre-plan playback state, the web terminal sends a jump request to jump to the specified time for playback. The jump request includes the pre-plan number, the path to the recording file of the pre-plan playback, and the specified time for jump. After receiving the redirection request, the control server forwards the redirection request to all audio and video decoding devices in the plan; After receiving a jump request to play back at a specified time, the audio and video decoding device retrieves the time segment recorded at the specified time from the video-on-demand server and plays it.

7. The method for processing contingency plan data based on a web terminal according to claim 4, characterized in that, It also includes a step to "pause or end the replay of the contingency plan," specifically: When in the pre-plan playback state, the web terminal sends a pause request or end request for the pre-plan playback. Both the pause request and the end request include the pre-plan number and the recording file path. After receiving a pause or end request, the control server forwards it to all audio and video decoding devices in the plan; Upon receiving a pause or end request, the audio / video decoding device pauses or ends playback of the recorded file according to the request type.

8. The method for processing contingency plan data based on a web terminal according to claim 4, characterized in that, It also includes a step for "marking operations when the contingency plan is activated or replayed," specifically: The web terminal sends a marking operation request to mark or modify a mark. The marking operation request includes the pre-recorded identifier, the mark time, and the mark content. After receiving the marking operation request, the guidance and control server stores the marking operation request in the database and returns a success response; When the pre-setup is activated or during playback, the audio and video decoding device receives a tagging operation request, retrieves the time segment recorded at the tagging point from the on-demand server, and plays it.

9. A web-based contingency plan data processing system, characterized in that, It includes a web terminal, a control server, and a recording server, among which, The WEB terminal is used to establish and activate the contingency plan, generate contingency plan data and send it to the control server, and receive recording information. When the pre-plan is enabled, the control server sends a first request for pre-plan recording to the recording server based on the pre-plan data. The first request includes a device list, device IP address, and device port of all audio and video decoding devices that need to be recorded in the pre-plan. The control server receives the recording information from the recording server and sends it to all WEB terminals. The recording server sends a second request to the audio / video decoding device to obtain the audio / video input stream for recording and storage based on the first request, and sends recording information to the control server. This includes: after receiving the first request for pre-planned recording, the recording server creates a directory for pre-planned recording, and within this directory, creates a subdirectory named after the device account of each audio / video decoding device that needs to be recorded; the recording server sends a second request to the audio / video decoding device to obtain the audio / video input stream, generates a recording file stored in the subdirectory, and generates recording information, including the recording directory path, the start time of the recording file, and the duration of the recording file; and sends the recording information to the control server.

Images