An ssd recorder, a remote log export method, and a remote log export system

Abstract

The embodiment of the application provides a kind of SSD video recorder, remote log export method and remote log export system, it is applied to information technology field, SOC chip, for receiving the communication request sent by client;Through data channel, connection request is sent to SSD chip;SSD chip, for after receiving connection request, first response information is fed back to SOC chip by data channel;SOC chip is also used to send second response information to client after receiving first response information;Receive the data connection establishment request and log acquisition request sent by client;Establish data connection with client;Through data channel, log acquisition request is sent to SSD chip;SOC chip is also used to receive the target log fed back by SSD chip;Through data connection, target log is fed back to client.It can be seen, by the scheme of the embodiment of the application, the remote export of log can be realized, not only the convenience of log export can be realized, but also the labor cost can be reduced.

Description

Technical Field

[0001] This application relates to the field of information technology, and in particular to an SSD video recorder, a remote log export method, and a remote log export system. Background Technology

[0002] Currently, SSD recorders often generate log data during daily operation. For example, the SSD hard drive within the recorder generates log data during operation, which may include SSD operation logs, SSD error logs, etc. If an SSD hard drive malfunctions during the recorder's operation, the log data can be read, and by analyzing the log data, the cause of the malfunction can be found and addressed.

[0003] However, current SSD recorders often require removing the SSD from the recorder and connecting it to a computer to export logs, or exporting logs directly from the recorder via a data interface such as UART. Both of these methods necessitate on-site maintenance personnel. For manufacturers' maintenance personnel, SSD recorder locations are often scattered, some even overseas, making log export inconvenient and costly. Summary of the Invention

[0004] The purpose of this application is to provide an SSD recorder, a remote log export method, and a remote log export system to achieve remote log export. The specific technical solution is as follows:

[0005] A first aspect of the present application provides an SSD video recorder, the SSD video recorder including a SOC chip and an SSD chip, the SOC chip and the SSD chip being connected through a data channel;

[0006] The SOC chip is used to receive communication requests sent by a client, wherein the client is located at a remote end of the SSD recorder, and the communication request indicates that the client requests to communicate with the SOC chip; and to send connection requests to the SSD chip through the data channel, wherein the connection request indicates that the SOC chip requests to communicate with the SSD chip.

[0007] The SSD chip is configured to send a first response message to the SOC chip via the data channel after receiving the connection request, wherein the first response message indicates that the SSD chip currently allows communication;

[0008] The SOC chip is further configured to, after receiving the first response information, send a second response information to the client, wherein the second response information indicates that both the SOC chip and the SSD chip are currently allowed to communicate; receive a data connection establishment request and a log retrieval request sent by the client after receiving the second response information, wherein the data connection establishment request indicates that the client requests to establish a data connection with the SOC chip, and the log retrieval request includes the identification information of the target log; establish a data connection with the client based on the data connection establishment request; and send the log retrieval request to the SSD chip through the data channel.

[0009] The SSD chip is also used to send the target log to the SOC chip through the data channel after receiving the log acquisition request;

[0010] The SOC chip is also used to receive the target log fed back by the SSD chip; and to feed back the target log to the client through the data connection.

[0011] In one possible implementation, the client sends a communication request to the SOC chip via a first protocol;

[0012] The SOC chip sends the second response information to the client via the first protocol;

[0013] The client sends data connection establishment requests and log acquisition requests to the SOC chip through the first protocol.

[0014] The SOC chip establishes a data connection with the client based on the data connection establishment request, which is a data connection of the second protocol; the SOC chip feeds back the target log to the client through the established data connection between the SSD chip and the client, which is a data connection of the second protocol.

[0015] In one possible implementation, the first protocol is at least one of the ISAPI protocol, the HIK SDK protocol, and a preset private protocol;

[0016] And / or,

[0017] The second protocol is at least one of the following: HTTP protocol, HIK SDK protocol, and preset private protocol;

[0018] And / or,

[0019] The data channel is at least one of SATA and PCIe.

[0020] In one possible implementation, the SOC chip is specifically used to send a request to the SSD chip to obtain the length information of the target log.

[0021] The SSD chip is specifically used to identify and feed back the length information of the target log to the SOC chip after receiving the length information acquisition request;

[0022] The SOC chip is specifically used to send a log acquisition request to the SSD chip after receiving the length information, requesting the SSD chip to export the target log in one go, and to receive the target log fed back by the SSD chip.

[0023] In one possible implementation, the SOC chip is specifically used to send a request to the SSD chip to obtain the attribute information of the target log, wherein the attribute information of the target log includes the total length of the target log and the length of each export.

[0024] Specifically, after receiving the attribute information acquisition request, the SSD chip feeds back the attribute information of the target log to the SOC chip.

[0025] The SOC chip is specifically used to, after receiving the attribute information of the target log, calculate the number of loops based on the total length of the target log and the length of each export; based on the calculated number of loops, cyclically obtain log entries from the SSD chip; and assemble the cyclically obtained log entries into packets to obtain the target log.

[0026] In one possible implementation, the SOC chip is specifically used to send a request to the SSD chip to obtain the attribute information of the target log via at least one of SATA and PCIe, wherein the attribute information of the target log includes the total length of the target log and the length of each export.

[0027] The SSD chip is specifically used to feed back the attribute information of the target log to the SOC chip through at least one of SATA and PCIe.

[0028] The SOC chip is specifically used to obtain log entries cyclically through at least one of SATA and PCIe based on the calculated number of cycles; and to assemble the cyclically obtained log entries into packets using at least one of HTTP protocol, HIK SDK protocol, and preset private protocol to obtain the target log.

[0029] In one possible implementation, the SOC chip is further configured to receive a query request for a specified log sent by a client, wherein the query request is used to request the SOC chip to query whether the specified log is stored in the SSD chip, and the query request includes identification information of the specified log; generate a control instruction corresponding to the query request containing the identification information of the specified log, and send the control instruction to the SSD chip, wherein the control instruction is used to control the SSD chip to check whether it stores the specified log;

[0030] The SSD chip is further configured to, upon receiving the control command, parse the control command to obtain the identification information of the specified log; check whether it stores the specified log based on the identification information of the specified log, and obtain result information; and feed the result information back to the SOC chip.

[0031] The SOC chip is also used to receive the result information and forward the result information to the client.

[0032] In one possible implementation, a management channel is also included between the SOC chip and the SSD chip;

[0033] The SOC chip is specifically used to send control instructions for the specified log to the SSD chip through the data channel or the management channel.

[0034] The SSD chip is specifically used to forward the result information to the SOC chip through the data channel or the management channel.

[0035] In one possible implementation, when the SSD chip itself stores the specified log, the result information includes the target log; when the SSD chip itself does not store the specified log, the result information is a no-storage prompt.

[0036] Specifically, the SSD chip is used to feed back the target log information to the SOC chip through the data channel or the management channel when it stores the target log; and to feed back the non-stored prompt information to the SOC chip through the data channel or the management channel when it does not store the target log.

[0037] In one possible implementation, a management channel is further included between the SOC chip and the SSD chip, and the management channel is at least one of GPIO, UART, RS232, SMBus, and I2C;

[0038] The SOC chip is also used to obtain the status information of the SSD chip through at least one of the GPIO, UART, RS232, SMBus, and I2C.

[0039] In one possible implementation, the SOC chip is further configured to generate and send alarm information based on the acquired status information of the SSD chip when it is determined that the status information of the SSD chip meets preset alarm conditions.

[0040] In one possible implementation, the control terminals of the power modules of the SOC chip and the SSD chip are connected.

[0041] The SOC chip is further configured to send a level signal to the power module via at least one of GPIO, UART, RS232, SPI, and SMBus to control the SSD chip to restart when it receives a target restart command or when it is determined that the SSD chip is in an abnormal state based on the obtained status information of the SSD chip. The target restart command is used to instruct the SSD chip to restart.

[0042] In one possible implementation, the SSD chip being in an abnormal state includes the SSD chip being undetectable through the data channel and / or the management channel.

[0043] In one possible implementation, the control terminals of the power modules of the SOC chip and the SSD chip are connected.

[0044] The SOC chip is specifically used to input a first-level signal to the power control pin of the power module through at least one of GPIO, UART, RS232, SMBus, and I2C to power off the SSD chip; after a preset time, it inputs a second-level signal to the power control pin of the power module through at least one of GPIO, UART, RS232, SMBus, and I2C to power on the SSD chip.

[0045] A second aspect of this application provides a remote log export method applied to an SSD recorder, wherein the SSD recorder includes a SOC chip and an SSD chip, the SOC chip and the SSD chip are connected through a data channel, and the client is located at the remote end of the SSD recorder;

[0046] The method includes:

[0047] The SOC chip receives communication requests sent by clients, wherein the clients are located at the remote end of the SSD recorder, and the communication requests indicate that the clients request to communicate with the SOC chip; the SOC chip also sends connection requests to the SSD chip via the data channel, wherein the connection requests indicate that the SOC chip requests to communicate with the SSD chip.

[0048] After receiving the connection request, the SSD chip uses the data channel to send back a first response message to the SOC chip, wherein the first response message indicates that the SSD chip currently allows communication.

[0049] After receiving the first response information, the SOC chip sends a second response information to the client, wherein the second response information indicates that both the SOC chip and the SSD chip are currently allowed to communicate. The SOC chip then receives a data connection establishment request and a log retrieval request sent by the client after receiving the second response information. The data connection establishment request indicates that the client requests to establish a data connection with the SOC chip, and the log retrieval request includes the identification information of the target log. Based on the data connection establishment request, the SOC chip establishes a data connection with the client. Finally, the SOC chip uses the data channel to send the log retrieval request to the SSD chip.

[0050] After receiving the log acquisition request, the SSD chip sends the target log to the SOC chip via the data channel.

[0051] The SOC chip receives the target log fed back by the SSD chip; the SOC chip uses the data connection to send the target log back to the client.

[0052] In one possible implementation, the client sends a communication request to the SOC chip via a first protocol; the SOC chip sends a second response message to the client via the first protocol; the client sends a data connection establishment request and a log retrieval request to the SOC chip via the first protocol; the SOC chip establishes a data connection with the client based on the data connection establishment request, which is a data connection established via the second protocol; the SOC chip feeds back the target log to the client through the established data connection between the SSD chip and the client, which is a data connection fed back to the client via the second protocol.

[0053] In one possible implementation, the first protocol is at least one of ISAPI protocol, HIK SDK protocol, and preset private protocol; and / or, the second protocol is at least one of HTTP protocol, HIK SDK protocol, and preset private protocol; and / or, the data channel is at least one of SATA and PCIe.

[0054] In one possible implementation, the SOC chip sends a request to the SSD chip to obtain the length information of the target log; after receiving the request, the SSD chip identifies and sends the length information of the target log back to the SOC chip; after receiving the length information, the SOC chip sends a log acquisition request to the SSD chip requesting the SSD chip to export the target log all at once, and receives the target log back from the SSD chip.

[0055] In one possible implementation, the SOC chip sends a request to the SSD chip to obtain the attribute information of the target log, wherein the attribute information of the target log includes the total length of the target log and the length of each export; after receiving the attribute information request, the SSD chip feeds back the attribute information of the target log to the SOC chip; after receiving the attribute information of the target log, the SOC chip calculates the number of loops based on the total length of the target log and the length of each export; based on the calculated number of loops, log entries are repeatedly obtained from the SSD chip; the repeatedly obtained log entries are packaged to obtain the target log;

[0056] In one possible implementation, the SOC chip sends a request to the SSD chip to obtain the attribute information of the target log using at least one of SATA and PCIe, wherein the attribute information of the target log includes the total length of the target log and the length of each export; the SSD chip feeds back the attribute information of the target log to the SOC chip using at least one of SATA and PCIe; the SOC chip obtains log entries cyclically using at least one of SATA and PCIe according to a calculated number of iterations; and the cyclically obtained log entries are packaged using at least one of HTTP protocol, HIK SDK protocol, and preset private protocol to obtain the target log.

[0057] In one possible implementation, the SOC chip receives a query request for a specified log sent by a client. The query request requests the SOC chip to check whether the specified log is stored in the SSD chip. The query request includes identification information of the specified log. A control command containing the identification information of the specified log, corresponding to the query request, is generated and sent to the SSD chip. The control command controls the SSD chip to check whether it stores the specified log. Upon receiving the control command, the SSD chip parses the control command to obtain the identification information of the specified log. It then checks whether it stores the specified log based on the identification information to obtain result information. The result information is fed back to the SOC chip. Finally, the SOC chip receives the result information and forwards it to the client.

[0058] In one possible implementation, a management channel is further included between the SOC chip and the SSD chip; the SOC chip sends control commands for the specified log to the SSD chip via the data channel or the management channel; and the SSD chip forwards the result information to the SOC chip via the data channel or the management channel.

[0059] In one possible implementation, when the SSD chip itself stores the specified log, the result information includes the target log; when the SSD chip itself does not store the specified log, the result information is a "not stored" message. Specifically, the SSD chip is used to feed back the target log information to the SOC chip through the data channel or the management channel when it stores the target log; and to feed back the "not stored" message to the SOC chip through the data channel or the management channel when it does not store the target log.

[0060] In one possible implementation, a management channel is further included between the SOC chip and the SSD chip, the management channel being at least one of GPIO, UART, RS232, SMBus, and I2C; the SOC chip is also used to obtain the status information of the SSD chip through at least one of GPIO, UART, RS232, SMBus, and I2C.

[0061] In one possible implementation, the SOC chip generates and sends alarm information based on the acquired status information of the SSD chip when it is determined that the status information of the SSD chip meets a preset alarm condition.

[0062] In one possible implementation, the SOC chip and the power module of the SSD chip are connected to the control terminal; when the SOC chip receives a target restart command, or when it is determined that the SSD chip is in an abnormal state based on the obtained status information of the SSD chip, it sends a level signal to the power module through at least one of GPIO, UART, RS232, SPI, and SMBus to control the SSD chip to restart, wherein the target restart command is used to instruct the SSD chip to restart;

[0063] In one possible implementation, the SSD chip being in an abnormal state includes the SSD chip being undetectable through the data channel and / or the management channel;

[0064] In one possible implementation, the control terminals of the power modules of the SOC chip and the SSD chip are connected; the SOC chip inputs a first-level signal to the power control pin of the power module using at least one of GPIO, UART, RS232, SMBus, and I2C to power off the SSD chip; after a preset time, a second-level signal is input to the power control pin of the power module using at least one of GPIO, UART, RS232, SMBus, and I2C to power on the SSD chip.

[0065] A third aspect of this application provides a remote log export system, the system including a client and an SSD recorder, the SSD recorder including a SOC chip and an SSD chip, the SOC chip and the SSD chip being connected via a data channel, and the client being located at the remote end of the SSD recorder;

[0066] The client is used to send communication requests to the SOC chip;

[0067] The SOC chip is used to receive communication requests sent by a client, wherein the client is located at a remote end of the SSD recorder, and the communication request indicates that the client requests to communicate with the SOC chip; and to send connection requests to the SSD chip through the data channel, wherein the connection request indicates that the SOC chip requests to communicate with the SSD chip.

[0068] The SSD chip is configured to send a first response message to the SOC chip via the data channel after receiving the connection request, wherein the first response message indicates that the SSD chip currently allows communication;

[0069] The SOC chip is further configured to send a second response message to the client after receiving the first response message, wherein the second response message indicates that both the SOC chip and the SSD chip are currently allowed to communicate;

[0070] The client is further configured to, after receiving the second response information, generate and send a data connection establishment request and a log acquisition request to the SOC chip, wherein the data connection establishment request indicates that the client requests to establish a data connection with the SOC chip, and the log acquisition request includes the identification information of the target log;

[0071] The SOC chip is also used to receive the data connection establishment request and the log acquisition request; establish a data connection with the client based on the data connection establishment request; and send the log acquisition request to the SSD chip through the data channel.

[0072] The SSD chip is also used to send the target log to the SOC chip through the data channel after receiving the log acquisition request;

[0073] The SOC chip is also used to receive the target log fed back by the SSD chip; and to feed back the target log to the client through the data connection.

[0074] In one possible implementation, the client sends a communication request to the SOC chip via a first protocol; the SOC chip sends a second response message to the client via the first protocol; the client sends a data connection establishment request and a log retrieval request to the SOC chip via the first protocol; the SOC chip establishes a data connection with the client based on the data connection establishment request, which is a data connection established via the second protocol; the SOC chip feeds back the target log to the client through the established data connection between the SSD chip and the client, which is a data connection fed back to the client via the second protocol.

[0075] In one possible implementation, the first protocol is at least one of ISAPI protocol, HIK SDK protocol, and preset private protocol; and / or, the second protocol is at least one of HTTP protocol, HIK SDK protocol, and preset private protocol; and / or, the data channel is at least one of SATA and PCIe.

[0076] In one possible implementation, the SOC chip is specifically configured to send a target log length information acquisition request to the SSD chip; the SSD chip is specifically configured to, after receiving the length information acquisition request, identify and feed back the target log length information to the SOC chip; the SOC chip is specifically configured to, after receiving the length information, send a log acquisition request to the SSD chip requesting the SSD chip to export the target log in one go, and receive the target log fed back by the SSD chip;

[0077] In one possible implementation, the SOC chip is specifically configured to send a request to the SSD chip to obtain attribute information of the target log, wherein the attribute information of the target log includes the total length of the target log and the length of each export; the SSD chip, after receiving the attribute information acquisition request, specifically feeds back the attribute information of the target log to the SOC chip; the SOC chip, specifically configured to, after receiving the attribute information of the target log, calculate the number of loops based on the total length of the target log and the length of each export; cyclically obtain log entries from the SSD chip based on the calculated number of loops; and assemble the cyclically obtained log entries into packets to obtain the target log;

[0078] In one possible implementation, the SOC chip is specifically configured to send a request to the SSD chip for obtaining the attribute information of the target log via at least one of SATA and PCIe, wherein the attribute information of the target log includes the total length of the target log and the length of each export; the SSD chip is specifically configured to feed back the attribute information of the target log to the SOC chip via at least one of SATA and PCIe; the SOC chip is specifically configured to cyclically obtain log entries via at least one of SATA and PCIe according to a calculated number of loops; and to assemble the cyclically obtained log entries into packets using at least one of HTTP protocol, HIK SDK protocol, and preset private protocol to obtain the target log;

[0079] In one possible implementation, the SOC chip is further configured to receive a query request for a specified log sent by a client, wherein the query request requests the SOC chip to check whether the specified log is stored in the SSD chip, and the query request includes identification information of the specified log; generate a control instruction corresponding to the query request, which includes the identification information of the specified log, and send the control instruction to the SSD chip, wherein the control instruction controls the SSD chip to check whether it stores the specified log; the SSD chip is further configured to, upon receiving the control instruction, parse the control instruction to obtain the identification information of the specified log; check whether it stores the specified log based on the identification information of the specified log to obtain result information; and feed back the result information to the SOC chip; the SOC chip is further configured to receive the result information and forward the result information to the client;

[0080] In one possible implementation, a management channel is further included between the SOC chip and the SSD chip; the SOC chip is specifically used to send control instructions for the specified log to the SSD chip through the data channel or the management channel; the SSD chip is specifically used to forward the result information to the SOC chip through the data channel or the management channel.

[0081] In one possible implementation, when the SSD chip itself stores the specified log, the result information includes the target log; when the SSD chip itself does not store the specified log, the result information is a "not stored" message. Specifically, the SSD chip is used to, when it stores the target log, feed back the target log information to the SOC chip via the data channel or the management channel; and when it does not store the target log, feed back the "not stored" message to the SOC chip via the data channel or the management channel.

[0082] In one possible implementation, a management channel is further included between the SOC chip and the SSD chip, the management channel being at least one of GPIO, UART, RS232, SMBus, and I2C; the SOC chip is also used to obtain the status information of the SSD chip through at least one of GPIO, UART, RS232, SMBus, and I2C.

[0083] In one possible implementation, the SOC chip is further configured to generate and send alarm information based on the acquired status information of the SSD chip when it is determined that the status information of the SSD chip meets a preset alarm condition.

[0084] In one possible implementation, the SOC chip is connected to the control terminal of the power module of the SSD chip; the SOC chip is further configured to send a level signal to the power module via at least one of GPIO, UART, RS232, SPI, and SMBus to control the SSD chip to restart when it receives a target restart command or determines that the SSD chip is in an abnormal state based on the obtained status information of the SSD chip, wherein the target restart command is used to instruct the SSD chip to restart;

[0085] In one possible implementation, the SSD chip being in an abnormal state includes the SSD chip being undetectable through the data channel and / or the management channel;

[0086] In one possible implementation, the control terminals of the power modules of the SOC chip and the SSD chip are connected; specifically, the SOC chip is used to input a first-level signal to the power control pin of the power module through at least one of GPIO, UART, RS232, SMBus, and I2C to power off the SSD chip; after a preset time, it inputs a second-level signal to the power control pin of the power module through at least one of GPIO, UART, RS232, SMBus, and I2C to power on the SSD chip.

[0087] Beneficial effects of the embodiments in this application:

[0088] This application provides an SSD video recorder, a remote log export method, and a remote log export system. The SSD video recorder includes a SOC chip and an SSD chip, which are connected via a data channel. The SOC chip is used to receive communication requests sent by a client, wherein the client is located at a remote end of the SSD video recorder, and the communication request indicates that the client requests to communicate with the SOC chip. The SOC chip also sends connection requests to the SSD chip via the data channel, wherein the connection request indicates that the SOC chip requests to communicate with the SSD chip. Upon receiving the connection request, the SSD chip is used to send a first response message back to the SOC chip via the data channel, wherein the first response message indicates that the SSD chip currently allows communication. The SOC chip is further used to... After receiving the message, the system sends a second response message to the client, indicating that both the SOC chip and the SSD chip are currently allowed to communicate; it receives a data connection establishment request and a log retrieval request sent by the client after receiving the second response message, wherein the data connection establishment request indicates that the client requests to establish a data connection with the SOC chip, and the log retrieval request includes the identification information of the target log; based on the data connection establishment request, it establishes a data connection with the client; it sends the log retrieval request to the SSD chip through the data channel; the SSD chip is further configured to send the target log to the SOC chip through the data channel after receiving the log retrieval request; the SOC chip is further configured to receive the target log fed back by the SSD chip; and it feeds back the target log to the client through the data connection. As can be seen, the solution of this application embodiment allows the client to send a communication request to the SSD recorder. After the SOC chip in the SSD recorder receives the communication request, it forwards it to the SSD chip, then receives the response information from the SSD chip and sends the response information back to the client. Finally, the client establishes a data connection with the SSD recorder, and the SOC chip obtains the log data stored in the SSD chip and sends it back to the client, thereby realizing remote log export. This not only makes log export more convenient but also reduces labor costs.

[0089] Of course, implementing any product or method of this application does not necessarily require achieving all of the advantages described above at the same time. Attached Figure Description

[0090] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other embodiments can be obtained based on these drawings.

[0091] Figure 1 This is a schematic diagram of the structure of an SSD recorder provided in an embodiment of this application;

[0092] Figure 2 A schematic diagram illustrating the acquisition of log data provided in an embodiment of this application;

[0093] Figure 3 An interactive diagram for obtaining log data provided in an embodiment of this application;

[0094] Figure 4 Another schematic diagram illustrating the acquisition of log data provided in this application embodiment;

[0095] Figure 5 Another structural schematic diagram of the SSD recorder provided in the embodiments of this application;

[0096] Figure 6 This is a schematic diagram illustrating the power-off restart process of an SSD chip provided in an embodiment of this application.

[0097] Figure 7 A flowchart illustrating the remote log export method provided in this application embodiment;

[0098] Figure 8 This is a schematic diagram of the structure of the remote log export system provided in an embodiment of this application. Detailed Implementation

[0099] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art based on this application are within the scope of protection of this application.

[0100] First, the technical terms that may be used in the embodiments of this application will be explained:

[0101] SATA (Serial Advanced Technology Attachment) is an industry-standard serial hardware driver interface.

[0102] SSD: Solid State Disk;

[0103] GPIO: (General-purpose input / output, general-purpose input / output management channel);

[0104] UART: (Universal Asynchronous Receiver / Transmitter);

[0105] PCIE: PCI-Express (Peripheral Component Interconnect Express, a high-speed serial computer expansion bus standard);

[0106] Nand flash interface: conforms to the ONFI standard (Open NAND Flash Interface) specification.

[0107] A first aspect of this application provides an SSD video recorder, see [link to previous document]. Figure 1 The SSD recorder includes an SOC chip 101 and an SSD chip 102, which are connected via a data channel.

[0108] SOC chip 101 is used to receive communication requests sent by clients, where the client is located at the remote end of the SSD recorder, and the communication request indicates that the client requests to communicate with the SOC chip; and to send connection requests to the SSD chip through the data channel, where the connection request indicates that the SOC chip requests to communicate with the SSD chip.

[0109] SSD chip 102 is used to send a first response message to SOC chip through the data channel after receiving a connection request, wherein the first response message indicates that SSD chip currently allows communication;

[0110] The SOC chip 101 is also configured to, after receiving the first response information, send a second response information to the client, wherein the second response information indicates that both the SOC chip and the SSD chip are currently allowed to communicate; receive a data connection establishment request and a log retrieval request sent by the client after receiving the second response information, wherein the data connection establishment request indicates that the client requests to establish a data connection with the SOC chip, and the log retrieval request includes the identification information of the target log; establish a data connection with the client based on the data connection establishment request; and send the log retrieval request to the SSD chip through the data channel.

[0111] SSD chip 102 is also used to send the target log to the SOC chip through the data channel after receiving a log acquisition request;

[0112] SOC chip 101 is also used to receive target logs fed back by the SSD chip; and to feed back the target logs to the client via a data connection.

[0113] The SSD recorder in this application can be applied to various scenarios, such as surveillance. For example, it can collect audio and video data via a camera, send the data to the SSD recorder, and store the data in the SSD recorder, facilitating video playback and analysis based on the stored data. Specifically, the SSD recorder in this embodiment can be a DVR (Disk Video Recorder) or an NVR (Network Video Recorder).

[0114] In this application embodiment, the SOC (System on Chip) chip can be the main control chip. This chip can receive and forward the audio and video data to be stored, so that the SSD chip can receive and store the audio and video data to be stored.

[0115] The SSD chip in this application can be a chip packaged using various packaging methods in the prior art. For example, the SSD chip in this application can be a BGA SSD chip packaged using, but not limited to, BGA (Ball Grid Array) technology. This packaging technology can integrate a traditional SSD board-level system (including PCB, controller, flash memory, SDRAM, etc.) into a single IC (Integrated Circuit Chip). This allows the SSD chip to be integrated into the circuit board, simplifying the overall system by eliminating cables connecting to traditional hard drives and simplifying the assembly process. Furthermore, because the packaged BGA SSD chip is smaller, replacing mechanical hard drives or solid-state SSDs with this chip can result in a smaller, thinner, and lighter hard drive, reducing chassis costs. Finally, compared to traditional hard disk drives (HDDs) or solid-state drives (SSDs), BGA SSD chips consume significantly less power. The inventors have reported a 30% reduction in power consumption, resulting in energy-efficient and environmentally friendly products. Furthermore, the reduced power supply requirements significantly lower costs. Finally, compared to traditional SSDs, BGA SSD chips offer better shock resistance, improving the security of stored data.

[0116] In this embodiment, the client is located remotely to the SSD recorder. Specifically, it can be an IE (web browser) client or a smart terminal, etc. For example, when the client in this embodiment is an IE client, the user can access the SSD recorder and request it to export logs by visiting a website, entering their username and account. The client being located remotely to the SSD recorder means that the SSD recorder and the client are in different physical locations, but the client can establish a data connection with the SSD recorder. For example, the client can remotely access the SSD recorder via a network. In this embodiment, the client can be a customized dedicated client, such as a customized terminal device specifically for logging, or a general-purpose terminal, such as a computer. When the client communicates with the SSD recorder, it can do so through a webpage or an application running on the client. For example, when the client communicates with the SSD via a webpage, the user can log in to their corresponding account through the client to communicate with the SSD.

[0117] The log data in this embodiment can be of various types. Specifically, it can be log data generated by the SSD hard drive in the SSD recorder during operation, such as SSD hard drive operation logs and SSD hard drive error logs. If an SSD hard drive malfunctions during SSD recorder operation, the log data can be read, and the cause of the malfunction can be found and addressed through analysis of the log data. Specifically, the SSD hard drive in the SSD recorder can generate log data during operation, including parameters, faults or anomalies that occur, received instructions, and executed operations, and cache this data in a designated location. Therefore, when an anomaly or fault occurs, the cause of the anomaly or fault can be analyzed by exporting and identifying this log data. For example, the fault code can be obtained from the error log to analyze the type of fault, or the cause of the fault can be analyzed by analyzing the voltage or current at the initial moment of the anomaly or fault.

[0118] In this embodiment, the SOC chip and the SSD chip are connected via a data channel. Specifically, this data channel can be SATA, PCIe, etc. For example, when a SATA channel is established via the SATA protocol, the SOC chip and the SSD chip in the SSD recorder can interact with each other via this SATA channel. For example, see... Figure 2In the diagram, the technical support refers to maintenance personnel, which can also be understood as the user in this application. The client (the Web interface on the PC in the diagram) sends a communication request to the DVR / NVR. This request may simply be to confirm the other end's request; specifically, it confirms that the DVR / NVR is ready and that a communication connection can be established. After receiving this communication request, the DVR / NVR can send a connection request to the SSD chip within the DVR / NVR. This request can also confirm that the SSD chip is ready and that a communication connection can be established. When the SSD chip determines that it is ready and can communicate, it sends a first response message to the SOC chip. This first response message indicates that the SSD chip is ready and can communicate. When the SOC chip receives the first response message and determines that it is ready to communicate, it can send a second response message. This second response message indicates that the SOC chip is ready to communicate, meaning that log data can be exported. After the SOC chip receives the data connection establishment request and log acquisition request sent by the client, it can create a connection based on the data connection establishment request, and then send log data back to the client based on the established connection.

[0119] As can be seen, the SSD recorder in this embodiment can send a communication request to the SSD recorder through the client. After the SOC chip in the SSD recorder receives the communication request, it forwards it to the SSD chip, then receives the response information from the SSD chip and sends the response information back to the client. Finally, the client establishes a data connection with the SSD recorder, and the SOC chip obtains the log data stored in the SSD chip and sends it back to the client, thereby realizing remote log export. This not only makes log export more convenient but also reduces labor costs.

[0120] In one possible implementation, the client sends a communication request to the SOC chip via a first protocol;

[0121] The SOC chip sends the second response information to the client via the first protocol;

[0122] The client sends data connection establishment requests and log retrieval requests to the SOC chip via the first protocol.

[0123] The SOC chip establishes a data connection with the client based on a data connection establishment request, which is a data connection using the second protocol. The SOC chip then feeds back the target log to the client through the established data connection between the SSD chip and the client, which is also done through the second protocol data connection.

[0124] In one possible implementation, the first protocol is at least one of the ISAPI protocol, the HIK SDK protocol, and a preset private protocol;

[0125] And / or,

[0126] The second protocol is at least one of the following: HTTP protocol, HIK SDK protocol, and preset private protocol;

[0127] And / or,

[0128] The data channel is at least one of SATA and PCIe.

[0129] Specifically, the client sends communication requests to the SOC chip via at least one of the following protocols: ISAPI (Internet Server Application Programming Interface), HIK SDK (Hikvision Software Development Kit), and a default proprietary protocol. The SOC chip sends connection requests to the SSD chip via either SATA or PCIe. The SSD chip sends a first response to the SOC chip via either SATA or PCIe. The SOC chip sends a second response to the client via at least one of the following protocols: ISAPI, HIK SDK, and a default proprietary protocol. The client sends data connection establishment requests and log retrieval requests to the SOC chip via at least one of the following protocols: ISAPI, HIK SDK, and a default proprietary protocol. Based on the data connection establishment request, the SOC chip establishes a data connection with the client, which is a data connection established via at least one of the following protocols: HTTP, HIK SDK, and a default proprietary protocol. The SOC chip retrieves log data to be sent from the SSD chip and sends the log data back to the client via the data connection, which is a data connection established via either SATA or PCIe and a data connection established via at least one of the following protocols: HTTP, HIK SDK, and a default proprietary protocol. In actual use, the aforementioned preset private protocol can be Hikvision protocol or Ezviz protocol, etc.

[0130] In this embodiment of the application, when the SOC chip obtains log data from the SSD chip, it can obtain the log data in one go or in segments.

[0131] In one possible implementation, the SOC chip is specifically used to send a request to the SSD chip to obtain the length information of the target log.

[0132] SSD chip 102 is specifically used to identify and feed back the length information of the target log to the SOC chip after receiving a length information acquisition request;

[0133] SOC chip 101 is specifically used to send a log acquisition request to the SSD chip after receiving the length information, requesting the SSD chip to export the target log in one go, and to receive the target log fed back by the SSD chip.

[0134] In this embodiment, the SOC chip obtains log data from the SSD chip in a one-time acquisition manner. This can be achieved by the SOC chip sending a single request to the SSD chip to retrieve the log data, followed by the SSD chip returning the entire log data to the SOC chip, instead of sending multiple log requests. Specifically, the SOC chip sends a request to the SSD chip to retrieve the log length information. Upon receiving this request, the SSD chip returns the log length information to the SOC chip. After receiving the length information, the SOC chip then sends a log retrieval request to the SSD chip requesting that it export the log data in one go. The SSD chip then exports the entire log data to the SOC chip in a single transaction.

[0135] In another possible implementation, the SOC chip can obtain log data from the SSD chip through multiple loops.

[0136] SOC chip 101 is specifically used to send a request to the SSD chip to obtain the attribute information of the target log, wherein the attribute information of the target log includes the total length of the target log and the length of each export.

[0137] Specifically, after receiving the attribute information retrieval request, the SSD chip 102 feeds back the attribute information of the target log to the SOC chip.

[0138] SOC chip 101 is specifically used to calculate the number of loops based on the total length of the target log and the length of each export after receiving the attribute information of the target log; to obtain log entries from the SSD chip in a loop based on the calculated number of loops; and to assemble the log entries obtained in a loop into packets to obtain the target log.

[0139] In one possible implementation, the SOC chip is specifically used to send a request to the SSD chip to obtain the attribute information of the target log via at least one of SATA and PCIe, wherein the attribute information of the target log includes the total length of the target log and the length of each export.

[0140] SSD chip 102 is specifically used to feed back the attribute information of the target log to the SOC chip through at least one of SATA and PCIe;

[0141] SOC chip 101 is specifically used to obtain log entries cyclically through at least one of SATA and PCIe based on the calculated number of loops; and to assemble the cyclically obtained log entries into packets using at least one of HTTP protocol, HIK SDK protocol, and preset private protocol to obtain the target log.

[0142] Specifically, the SOC chip can calculate the number of loops by receiving the total length of the logs and the length of each read, and then repeatedly send log export requests to the SSD chip. After receiving each log export request, the SSD chip will send back one log data, until the SOC chip determines that it has received all the log data based on the total length of the logs, and then stops sending log export requests.

[0143] For example, see Figure 3When the SSD recorder in this embodiment is a DVR / NVR and the SSD chip is a BGA SSD chip, the user can log in to the DVR / NVR's IE client on a PC (Personal Computer). The user can export the logs by clicking the "Export SSD Log Information" button. After the user clicks, the IE client can send a log retrieval request to the DVR / NVR through the network interface. After the DVR / NVR receives the log retrieval request, it can send the log retrieval request to the BGA SSD chip through the SOC chip using the data channel or management channel. After the BGA SSD chip receives the log retrieval request sent by the SOC chip through the data channel or management channel, it can return ready information to the SOC chip through the data channel or management channel. Then, the SOC chip sends the ready information to the IE client. After the IE client receives the readiness message, it can establish a data connection with the DVR / NVR using HTTP protocol and request log information. Upon receiving the connection request, the DVR / NVR can create an HTTP connection between the SOC chip and the client. The SOC chip can then send a request to the BGA SSD chip via the data or management channel to retrieve the log length and the length of each read operation. Upon receiving this request, the BGA SSD chip checks its stored log information, obtains the corresponding log length and read length, and sends this information back to the SOC chip. The SOC chip then calculates the number of loops for log retrieval based on the received log length and read length, and retrieves logs repeatedly according to this number of loops. After each loop, the logs are packaged according to the HTTP protocol, and the packaged logs are sent to the IE client through the established HTTP connection between the SOC chip and the client. Finally, the IE client saves and analyzes the received log data. In practical use, the SOC chip can also retrieve all logs from the GBA SSD chip in a loop, package them using HTTP, and then send them to the IE client.

[0144] In actual use, if the logs obtained by the user through the client do not contain the logs the user expects, the relevant logs can be checked through command output.

[0145] In one possible implementation, the SOC chip is further configured to receive a query request for a specified log sent by a client, wherein the query request is used to request the SOC chip to query whether the SSD chip stores a specified log, and the query request includes identification information of the specified log; generate a control instruction corresponding to the query request containing the identification information of the specified log, and send the control instruction to the SSD chip, wherein the control instruction is used to control the SSD chip to check whether it stores the specified log;

[0146] The SSD chip 102 is also used to parse the control command after receiving the control command to obtain the identification information of the specified log; check whether it has stored the specified log according to the identification information of the specified log, and obtain the result information; and feed the result information back to the SOC chip.

[0147] The SOC chip 101 is also used to receive result information and forward the result information to the client.

[0148] In one possible implementation, a management channel is also included between the SOC chip and the SSD chip;

[0149] SOC chip 101 is specifically used to send control commands for specified logs to the SSD chip through a data channel or a management channel.

[0150] SSD chip 102 is specifically used to forward result information to the SOC chip through a data channel or a management channel.

[0151] In one possible implementation, the result information includes the target log when the SSD chip itself stores the specified log, and the result information is a no-storage prompt when the SSD chip itself does not store the specified log.

[0152] SSD chip 102 is specifically used to send target log information back to the SOC chip through the data channel or management channel when it has stored the target log; and to send a no-storage prompt message to the SOC chip through the data channel or management channel when it has not stored the target log.

[0153] In this embodiment, when the client communicates with the SSD recorder, it can do so via a webpage on the client or an application running on the client. Specifically, the client can be a customized dedicated terminal or a general-purpose terminal, such as a computer. For example, see... Figure 4When the SSD recorder in this embodiment is a DVR / NVR and the management channel is a UART, the user can send control commands to the DVR / NVR via a client using a UART tool. Then, the SOC chip in the DVR / NVR can send control commands to the BGA SSD chip in the DVR / NVR via the management channel UART (Universal Asynchronous Receiver / Transmitter Management Channel). These control commands can be requests for the BGA SSD chip to check if it stores the target log. Upon receiving the control command, the BGA SSD chip in the DVR / NVR can parse it and check if it stores the log data. If it does, it sends the target log back via the data channel between the BGA SSD chip and the SOC chip. If it does not store the log, it sends a no-storage message via the management channel UART. After receiving this feedback, the SOC chip can send feedback via the data connection between itself and the client, thereby enabling the investigation of relevant logs through command output.

[0154] In one possible implementation, a management channel is also included between the SOC chip and the SSD chip. The management channel is at least one of GPIO, UART, RS232 (asynchronous transfer standard interface), SMBus (System Management Bus), and I2C.

[0155] SOC chip 101 is also used to obtain the status information of the SSD chip through at least one of GPIO, UART, RS232, SMBus, and I2C.

[0156] In one possible implementation, the SOC chip is also used to generate and send alarm information based on the acquired SSD chip status information when it is determined that the SSD chip status information meets preset alarm conditions.

[0157] Specifically, the status information of the SSD chip in this embodiment may include the SSD chip's temperature, remaining capacity, etc. For example, the SOC chip can obtain information such as the current temperature of the SSD chip through at least one of GPIO, UART, RS232, SMBus, and I2C. When the current temperature is detected to be greater than a preset alarm threshold, a temperature alarm can be generated. In one example, the SOC chip can perform module upgrades on the SSD chip through a data channel or a management channel, and the SOC chip can obtain the SSD's log information through the management channel or the data channel.

[0158] In one possible implementation, the control terminals of the power modules of the SOC chip and the SSD chip are connected.

[0159] The SOC chip 101 is also used to send a level signal to the power module through at least one of GPIO, UART, RS232, SPI, and SMBus to control the SSD chip to restart when a target restart command is received, or when the SSD chip is determined to be in an abnormal state based on the obtained SSD chip status information, wherein the target restart command is used to instruct the SSD chip to restart.

[0160] In one possible implementation, an abnormal state of the SSD chip includes the inability to recognize the SSD chip through the data channel and / or management channel.

[0161] In one possible implementation, the control terminals of the power modules of the SOC chip and the SSD chip are connected.

[0162] SOC chip 101 is specifically used to input a first level signal to the power control pin of the power module through at least one of GPIO, UART, RS232, SMBus, and I2C to power off the SSD chip; after a preset time, it inputs a second level signal to the power control pin of the power module through at least one of GPIO, UART, RS232, SMBus, and I2C to power on the SSD chip.

[0163] In practical use, the aforementioned first-level signal and second-level signal can be a high-level signal and a low-level signal, or a low-level signal and a high-level signal, respectively. For example, the SOC chip inputs a high-level signal to the power control pin of the SSD chip's power module via at least one of GPIO, UART, RS232, SMBus, and I2C to power off the SSD chip; after a preset time, it inputs a low-level signal to the power control pin of the SSD chip's unit module via at least one of GPIO, UART, RS232, SMBus, and I2C to power on the SSD chip. For example, see... Figure 5 The SOC chip can write audio and video data to the SSD chip or read data from the SSD chip through the data channel; the SOC chip can control the SSD power switch through the GPIO in the management channel.

[0164] For example, see Figure 6The method described in this application manages the SSD chip through the SOC chip. Specifically, when the SOC chip cannot recognize the SSD chip or the SSD chip is offline, the SOC chip can control the power switch of the SSD chip through the GPIO interface of the management channel to restore the SSD's operation. The specific steps include: the SOC identifies the SSD through the data channel; the SOC sets the SSD identification status to obtain the SSD's status; it determines whether the SSD exists; if it exists, it returns and obtains the status again at preset intervals; if it does not exist, it pulls the GPIO pin in the management channel high to power off the SSD; after waiting for 30 seconds, it pulls the GPIO pin in the management channel low to power on the SSD.

[0165] As can be seen, the method implemented in this application can obtain the status of the SSD chip through the SOC chip, and control the SSD chip to power off and restart when the SSD chip cannot be recognized or the SSD chip is offline, so as to realize storage.

[0166] A second aspect of this application provides a remote log export method applied to an SSD recorder. The SSD recorder includes a SOC chip and an SSD chip, which are connected via a data channel. The client is located at the remote end of the SSD recorder.

[0167] See Figure 7 The above methods include:

[0168] Step S71: Receive a communication request sent by the client through the SOC chip, wherein the client is located at the remote end of the SSD recorder, and the communication request indicates that the client requests to communicate with the SOC chip; send a connection request to the SSD chip through the SOC chip using the data channel, wherein the connection request indicates that the SOC chip requests to communicate with the SSD chip.

[0169] Step S72: After receiving the connection request, the SSD chip sends a first response message to the SOC chip via the data channel. The first response message indicates that the SSD chip currently allows communication.

[0170] Step S73: After receiving the first response information, the SOC chip sends a second response information to the client, indicating that both the SOC chip and the SSD chip are currently allowed to communicate; the SOC chip receives a data connection establishment request and a log retrieval request sent by the client after receiving the second response information, wherein the data connection establishment request indicates that the client requests to establish a data connection with the SOC chip, and the log retrieval request includes the identification information of the target log; the SOC chip establishes a data connection with the client based on the data connection establishment request; and the SOC chip sends a log retrieval request to the SSD chip using the data channel.

[0171] Step S74: After receiving the log acquisition request, the SSD chip sends the target log to the SOC chip via the data channel.

[0172] Step S75: Receive the target log fed back by the SSD chip through the SOC chip; send the target log back to the client through the data connection via the SOC chip.

[0173] In one possible implementation, the client sends a communication request to the SOC chip via a first protocol; the SOC chip sends a second response message to the client via the first protocol; the client sends a data connection establishment request and a log retrieval request to the SOC chip via the first protocol; the SOC chip establishes a data connection with the client based on the data connection establishment request, which is to establish a data connection using the second protocol; the SOC chip feeds back the target log to the client through the established data connection between the SSD chip and the client, which is to feed back the target log to the client through the data connection using the second protocol.

[0174] In one possible implementation, the first protocol is at least one of ISAPI protocol, HIK SDK protocol, and preset private protocol; and / or, the second protocol is at least one of HTTP protocol, HIK SDK protocol, and preset private protocol; and / or, the data channel is at least one of SATA and PCIe.

[0175] In one possible implementation, the SOC chip sends a request to the SSD chip to obtain the length information of the target log; after receiving the request, the SSD chip identifies and sends the length information of the target log back to the SOC chip; after receiving the length information, the SOC chip sends a log acquisition request to the SSD chip requesting the SSD chip to export the target log all at once, and receives the target log back from the SSD chip.

[0176] In one possible implementation, the SOC chip sends a request to the SSD chip to obtain the attribute information of the target log, wherein the attribute information of the target log includes the total length of the target log and the length of each export; after receiving the attribute information request, the SSD chip feeds back the attribute information of the target log to the SOC chip; after receiving the attribute information of the target log, the SOC chip calculates the number of loops based on the total length of the target log and the length of each export; based on the calculated number of loops, log entries are repeatedly obtained from the SSD chip; the repeatedly obtained log entries are packaged to obtain the target log;

[0177] In one possible implementation, the SOC chip sends a request to the SSD chip to obtain the attribute information of the target log using at least one of SATA and PCIe, wherein the attribute information of the target log includes the total length of the target log and the length of each export; the SSD chip feeds back the attribute information of the target log to the SOC chip using at least one of SATA and PCIe; the SOC chip obtains log entries cyclically using at least one of SATA and PCIe according to the calculated number of loops; and the cyclically obtained log entries are packaged using at least one of HTTP protocol, HIK SDK protocol, and preset private protocol to obtain the target log.

[0178] In one possible implementation, the SOC chip receives a query request for a specified log from the client. The query request, which requests the SOC chip to check whether the SSD chip stores a specified log, includes identification information for the specified log. A control command, containing the identification information of the specified log, is generated corresponding to the query request and sent to the SSD chip. This control command instructs the SSD chip to check whether it stores the specified log. Upon receiving the control command, the SSD chip parses it to obtain the identification information of the specified log. It then checks whether it stores the specified log based on the identification information, obtaining a result. This result is fed back to the SOC chip. Finally, the SOC chip receives the result and forwards it to the client.

[0179] In one possible implementation, a management channel is also included between the SOC chip and the SSD chip; the SOC chip sends control commands for specified logs to the SSD chip via a data channel or a management channel; and the SSD chip forwards result information to the SOC chip via a data channel or a management channel.

[0180] In one possible implementation, the result information includes the target log when the SSD chip itself stores the specified log, and the result information is a no-storage prompt when the SSD chip itself does not store the specified log; specifically, the SSD chip is used to feed back the target log information to the SOC chip through the data channel or management channel when it stores the target log, and to feed back the no-storage prompt to the SOC chip through the data channel or management channel when it does not store the target log.

[0181] In one possible implementation, a management channel is further included between the SOC chip and the SSD chip. The management channel is at least one of GPIO, UART, RS232, SMBus, and I2C. The SOC chip is also used to obtain the status information of the SSD chip through at least one of GPIO, UART, RS232, SMBus, and I2C.

[0182] In one possible implementation, the SOC chip generates and sends alarm information based on the acquired SSD chip status information when it is determined that the SSD chip status information meets the preset alarm conditions.

[0183] In one possible implementation, the control terminals of the power modules of the SOC chip and the SSD chip are connected; when the SOC chip receives a target restart command, or when it is determined that the SSD chip is in an abnormal state based on the obtained SSD chip status information, it sends a level signal to the power module through at least one of GPIO, UART, RS232, SPI, and SMBus to control the SSD chip to restart, wherein the target restart command is used to instruct the SSD chip to restart;

[0184] In one possible implementation, an abnormal state of the SSD chip includes the inability to recognize the SSD chip through the data channel and / or management channel.

[0185] In one possible implementation, the control terminals of the power modules of the SOC chip and the SSD chip are connected; the SOC chip inputs a first-level signal to the power control pin of the power module using at least one of GPIO, UART, RS232, SMBus, and I2C to power off the SSD chip; after a preset time, a second-level signal is input to the power control pin of the power module using at least one of GPIO, UART, RS232, SMBus, and I2C to power on the SSD chip.

[0186] As can be seen, the method of this application embodiment allows a client to send a communication request to an SSD recorder. After the SOC chip in the SSD recorder receives the communication request, it forwards it to the SSD chip, then receives the response information from the SSD chip and sends the response information back to the client. Finally, the client establishes a data connection with the SSD recorder, and the SOC chip obtains the log data stored in the SSD chip and sends it back to the client, thereby realizing remote log export. This not only makes log export convenient but also reduces labor costs.

[0187] A third aspect of this application provides a remote log export system, see [link to relevant documentation]. Figure 8 The system includes a client 801 and an SSD recorder. The SSD recorder includes a SOC chip 802 and an SSD chip 803. The SOC chip 802 and the SSD chip 803 are connected through a data channel. The client is located at the remote end of the SSD recorder.

[0188] Client 801 is used to send communication requests to the SOC chip;

[0189] The SOC chip 802 is used to receive communication requests sent by the client, where the client is located at the remote end of the SSD recorder, and the communication request indicates that the client requests to communicate with the SOC chip; and to send connection requests to the SSD chip through the data channel, where the connection request indicates that the SOC chip requests to communicate with the SSD chip.

[0190] SSD chip 803 is used to send a first response message to the SOC chip through the data channel after receiving a connection request. The first response message indicates that the SSD chip currently allows communication.

[0191] The SOC chip 802 is also used to send a second response message to the client after receiving the first response message, wherein the second response message indicates that both the SOC chip and the SSD chip are currently allowed to communicate.

[0192] Client 801 is also used to, after receiving the second response information, generate and send a data connection establishment request and a log acquisition request to the SOC chip. The data connection establishment request indicates that the client requests to establish a data connection with the SOC chip, and the log acquisition request includes the identification information of the target log.

[0193] The SOC chip 802 is also used to receive data connection establishment requests and log retrieval requests; establish a data connection with the client based on the data connection establishment request; and send a log retrieval request to the SSD chip through the data channel.

[0194] The SSD chip 803 is also used to send the target log to the SOC chip via the data channel after receiving a log retrieval request;

[0195] The SOC chip 802 is also used to receive target logs fed back by the SSD chip; and to feed back the target logs to the client via a data connection.

[0196] In one possible implementation, the client sends a communication request to the SOC chip via a first protocol; the SOC chip sends a second response message to the client via the first protocol; the client sends a data connection establishment request and a log retrieval request to the SOC chip via the first protocol; the SOC chip establishes a data connection with the client based on the data connection establishment request, which is to establish a data connection using the second protocol; the SOC chip feeds back the target log to the client through the established data connection between the SSD chip and the client, which is to feed back the target log to the client through the data connection using the second protocol.

[0197] In one possible implementation, the first protocol is at least one of ISAPI protocol, HIK SDK protocol, and preset private protocol; and / or, the second protocol is at least one of HTTP protocol, HIK SDK protocol, and preset private protocol; and / or, the data channel is at least one of SATA and PCIe.

[0198] In one possible implementation, the SOC chip is specifically used to send a target log length information acquisition request to the SSD chip; the SSD chip is specifically used to identify and feed back the target log length information to the SOC chip after receiving the length information acquisition request; the SOC chip is specifically used to send a log acquisition request to the SSD chip requesting the SSD chip to export the target log all at once after receiving the length information, and to receive the target log fed back by the SSD chip.

[0199] In one possible implementation, the SOC chip is specifically used to send a request to the SSD chip to obtain attribute information of the target log, wherein the attribute information of the target log includes the total length of the target log and the length of each export; the SSD chip, after receiving the attribute information acquisition request, specifically feeds back the attribute information of the target log to the SOC chip; the SOC chip, specifically used to calculate the number of loops based on the total length of the target log and the length of each export after receiving the attribute information of the target log; to repeatedly obtain log entries from the SSD chip based on the calculated number of loops; and to assemble the repeatedly obtained log entries into packets to obtain the target log;

[0200] In one possible implementation, the SOC chip is specifically used to send a request to the SSD chip to obtain the attribute information of the target log via at least one of SATA and PCIe, wherein the attribute information of the target log includes the total length of the target log and the length of each export; the SSD chip is specifically used to feed back the attribute information of the target log to the SOC chip via at least one of SATA and PCIe; the SOC chip is specifically used to obtain log entries cyclically via at least one of SATA and PCIe according to the calculated number of loops; and to assemble the cyclically obtained log entries into packets via at least one of HTTP protocol, HIK SDK protocol, and preset private protocol to obtain the target log;

[0201] In one possible implementation, the SOC chip is further configured to receive a query request for a specified log sent by a client, wherein the query request requests the SOC chip to check whether the SSD chip stores a specified log, and the query request includes identification information of the specified log; generate a control instruction corresponding to the query request containing the identification information of the specified log, and send the control instruction to the SSD chip, wherein the control instruction controls the SSD chip to check whether it stores the specified log; the SSD chip is further configured to, upon receiving the control instruction, parse the control instruction to obtain the identification information of the specified log; check whether it stores the specified log based on the identification information of the specified log to obtain result information; and feed back the result information to the SOC chip; the SOC chip is further configured to receive the result information and forward the result information to the client;

[0202] In one possible implementation, a management channel is further included between the SOC chip and the SSD chip; the SOC chip is specifically used to send control commands for a specified log to the SSD chip via a data channel or a management channel; the SSD chip is specifically used to forward result information to the SOC chip via a data channel or a management channel.

[0203] In one possible implementation, the result information includes the target log when the SSD chip itself stores the specified log, and the result information is a no-storage prompt when the SSD chip itself does not store the specified log; specifically, the SSD chip is used to feed back the target log information to the SOC chip through the data channel or management channel when it stores the target log, and to feed back the no-storage prompt to the SOC chip through the data channel or management channel when it does not store the target log.

[0204] In one possible implementation, a management channel is further included between the SOC chip and the SSD chip. The management channel is at least one of GPIO, UART, RS232, SMBus, and I2C. The SOC chip is also used to obtain the status information of the SSD chip through at least one of GPIO, UART, RS232, SMBus, and I2C.

[0205] In one possible implementation, the SOC chip is also used to generate and send alarm information based on the acquired SSD chip status information when it is determined that the SSD chip status information meets preset alarm conditions.

[0206] In one possible implementation, the SOC chip and the power module of the SSD chip are connected to the control terminal; the SOC chip is also used to send a level signal to the power module through at least one of GPIO, UART, RS232, SPI, and SMBus to control the SSD chip to restart when it receives a target restart command or determines that the SSD chip is in an abnormal state based on the obtained SSD chip status information, wherein the target restart command is used to instruct the SSD chip to restart;

[0207] In one possible implementation, an abnormal state of the SSD chip includes the inability to recognize the SSD chip through the data channel and / or management channel.

[0208] In one possible implementation, the control terminals of the power modules of the SOC chip and the SSD chip are connected; the SOC chip is specifically used to input a first level signal to the power control pin of the power module through at least one of GPIO, UART, RS232, SMBus, and I2C to power off the SSD chip; after a preset time, it inputs a second level signal to the power control pin of the power module through at least one of GPIO, UART, RS232, SMBus, and I2C to power on the SSD chip.

[0209] As can be seen, the system of this application embodiment allows a client to send a communication request to an SSD recorder. After the SOC chip in the SSD recorder receives the communication request, it forwards it to the SSD chip, then receives the response information from the SSD chip and sends the response information back to the client. Finally, the client establishes a data connection with the SSD recorder, and the SOC chip obtains the log data stored in the SSD chip and sends it back to the client, thereby realizing remote log export. This not only makes log export convenient but also reduces labor costs.

[0210] The communication bus mentioned in the above electronic devices can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. This communication bus can be divided into address bus, data bus, control bus, etc. For ease of illustration, only one thick line is used to represent it in the diagram, but this does not mean that there is only one bus or one type of bus.

[0211] The communication interface is used for communication between the aforementioned electronic devices and other devices.

[0212] The memory may include random access memory (RAM) or non-volatile memory (NVM), such as at least one disk storage device. Optionally, the memory may also be at least one storage device located remotely from the aforementioned processor.

[0213] The processors mentioned above can be general-purpose processors, including central processing units (CPUs), network processors (NPs), etc.; they can also be digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components.

[0214] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid state disk (SSD)).

[0215] It should be noted that, in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0216] The various embodiments in this specification are described in a related manner. Similar or identical parts between embodiments can be referred to mutually. Each embodiment focuses on describing the differences from other embodiments. In particular, the system and method embodiments are basically similar to the SSD recorder embodiments, so the description is relatively simple; relevant parts can be referred to the description of the method embodiments.

[0217] The above description is merely a preferred embodiment of this application and is not intended to limit the scope of protection of this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application are included within the scope of protection of this application.

Claims

1. An SSD video recorder, characterized in that, The SSD recorder includes a SOC chip and an SSD chip, and the SOC chip and the SSD chip are connected through a data channel. The SOC chip is used to receive communication requests sent by a client, wherein the client is located at a remote end of the SSD recorder, and the communication request indicates that the client requests to communicate with the SOC chip; and to send connection requests to the SSD chip through the data channel, wherein the connection request indicates that the SOC chip requests to communicate with the SSD chip. The SSD chip is configured to send a first response message to the SOC chip via the data channel after receiving the connection request, wherein the first response message indicates that the SSD chip currently allows communication; The SOC chip is further configured to, after receiving the first response information, send a second response information to the client, wherein the second response information indicates that both the SOC chip and the SSD chip are currently allowed to communicate; receive a data connection establishment request and a log retrieval request sent by the client after receiving the second response information, wherein the data connection establishment request indicates that the client requests to establish a data connection with the SOC chip, and the log retrieval request includes the identification information of the target log; establish a data connection with the client based on the data connection establishment request; and send the log retrieval request to the SSD chip through the data channel. The SSD chip is also used to send the target log to the SOC chip through the data channel after receiving the log acquisition request; The SOC chip is also used to receive the target log fed back by the SSD chip; and to feed back the target log to the client through the data connection.

2. The SSD recorder according to claim 1, Its features are, in, The client sends a communication request to the SOC chip via a first protocol; The SOC chip sends the second response information to the client via the first protocol; The client sends data connection establishment requests and log acquisition requests to the SOC chip through the first protocol. The SOC chip establishes a data connection with the client based on the data connection establishment request, which is a data connection of the second protocol; the SOC chip feeds back the target log to the client through the established data connection between the SSD chip and the client, which is a data connection of the second protocol.

3. The SSD recorder according to claim 2, characterized in that, The first protocol is at least one of the following: ISAPI protocol, HIK SDK protocol, and preset private protocol; And / or, The second protocol is at least one of the following: HTTP protocol, HIK SDK protocol, and preset private protocol; And / or, The data channel is at least one of SATA and PCIe.

4. The SSD recorder according to claim 1, characterized in that, The SOC chip is specifically used to send a request to the SSD chip to obtain the length information of the target log. The SSD chip is specifically used to identify and feed back the length information of the target log to the SOC chip after receiving the length information acquisition request; The SOC chip is specifically used to send a log acquisition request to the SSD chip after receiving the length information, requesting the SSD chip to export the target log in one go, and to receive the target log fed back by the SSD chip.

5. The SSD recorder according to claim 1, characterized in that, The SOC chip is specifically used to send a request to the SSD chip to obtain the attribute information of the target log, wherein the attribute information of the target log includes the total length of the target log and the length of each export. Specifically, after receiving the attribute information acquisition request, the SSD chip feeds back the attribute information of the target log to the SOC chip. The SOC chip is specifically used to, after receiving the attribute information of the target log, calculate the number of loops based on the total length of the target log and the length of each export; based on the calculated number of loops, cyclically obtain log entries from the SSD chip; and assemble the cyclically obtained log entries into packets to obtain the target log.

6. The SSD recorder according to claim 3, characterized in that, The SOC chip is specifically used to send a request to the SSD chip to obtain the attribute information of the target log via at least one of SATA and PCIe, wherein the attribute information of the target log includes the total length of the target log and the length of each export. The SSD chip is specifically used to feed back the attribute information of the target log to the SOC chip through at least one of SATA and PCIe. The SOC chip is specifically used to obtain log entries cyclically through at least one of SATA and PCIe based on the calculated number of cycles; and to assemble the cyclically obtained log entries into packets using at least one of HTTP protocol, HIK SDK protocol, and preset private protocol to obtain the target log.

7. The SSD recorder according to claim 1, characterized in that, The SOC chip is further configured to receive a query request for a specified log sent by a client, wherein the query request is used to request the SOC chip to query whether the specified log is stored in the SSD chip, and the query request includes the identification information of the specified log; generate a control instruction corresponding to the query request containing the identification information of the specified log, and send the control instruction to the SSD chip, wherein the control instruction is used to control the SSD chip to check whether it stores the specified log; The SSD chip is further configured to, upon receiving the control command, parse the control command to obtain the identification information of the specified log; check whether it stores the specified log based on the identification information of the specified log, and obtain result information; and feed the result information back to the SOC chip. The SOC chip is also used to receive the result information and forward the result information to the client.

8. The SSD recorder according to claim 7, characterized in that, A management channel is also included between the SOC chip and the SSD chip; The SOC chip is specifically used to send control instructions for the specified log to the SSD chip through the data channel or the management channel. The SSD chip is specifically used to forward the result information to the SOC chip through the data channel or the management channel.

9. The SSD recorder according to claim 8, characterized in that, When the SSD chip itself stores the specified log, the result information includes the target log; when the SSD chip itself does not store the specified log, the result information is a no-storage prompt. Specifically, the SSD chip is used to feed back the target log information to the SOC chip through the data channel or the management channel when it stores the target log; and to feed back the non-stored prompt information to the SOC chip through the data channel or the management channel when it does not store the target log.

10. The SSD recorder according to claim 1, characterized in that, The SOC chip and the SSD chip also include a management channel, which is at least one of GPIO, UART, RS232, SMBus, and I2C. The SOC chip is also used to obtain the status information of the SSD chip through at least one of the GPIO, UART, RS232, SMBus, and I2C.

11. The SSD recorder according to claim 10, characterized in that, The SOC chip is also used to generate and send alarm information based on the acquired status information of the SSD chip when it is determined that the status information of the SSD chip meets the preset alarm conditions.

12. The SSD recorder according to claim 11, characterized in that, The power modules of the SOC chip and the SSD chip are connected to each other. The SOC chip is further configured to send a level signal to the power module via at least one of GPIO, UART, RS232, SPI, and SMBus to control the SSD chip to restart when it receives a target restart command or when it is determined that the SSD chip is in an abnormal state based on the obtained status information of the SSD chip. The target restart command is used to instruct the SSD chip to restart.

13. The SSD recorder according to claim 12, characterized in that, The SSD chip being in an abnormal state includes the SSD chip being undetectable through the data channel and / or the management channel.

14. The SSD recorder according to claim 8, characterized in that, The power modules of the SOC chip and SSD chip are connected to each other. The SOC chip is specifically used to input a first-level signal to the power control pin of the power module through at least one of GPIO, UART, RS232, SMBus, and I2C to power off the SSD chip; after a preset time, it inputs a second-level signal to the power control pin of the power module through at least one of GPIO, UART, RS232, SMBus, and I2C to power on the SSD chip.

15. A method for exporting remote logs, characterized in that, This technology is applied to SSD video recorders, which include a SOC chip and an SSD chip. The SOC chip and the SSD chip are connected through a data channel, and the client is located at the remote end of the SSD video recorder. The method includes: The SOC chip receives communication requests sent by clients, wherein the clients are located at the remote end of the SSD recorder, and the communication requests indicate that the clients request to communicate with the SOC chip; the SOC chip also sends connection requests to the SSD chip via the data channel, wherein the connection requests indicate that the SOC chip requests to communicate with the SSD chip. After receiving the connection request, the SSD chip uses the data channel to send back a first response message to the SOC chip, wherein the first response message indicates that the SSD chip currently allows communication. After receiving the first response information, the SOC chip sends a second response information to the client, wherein the second response information indicates that both the SOC chip and the SSD chip are currently allowed to communicate. The SOC chip then receives a data connection establishment request and a log retrieval request sent by the client after receiving the second response information. The data connection establishment request indicates that the client requests to establish a data connection with the SOC chip, and the log retrieval request includes the identification information of the target log. Based on the data connection establishment request, the SOC chip establishes a data connection with the client. Finally, the SOC chip uses the data channel to send the log retrieval request to the SSD chip. After receiving the log acquisition request, the SSD chip sends the target log to the SOC chip via the data channel. The SOC chip receives the target log fed back by the SSD chip; the SOC chip uses the data connection to send the target log back to the client.

16. The method according to claim 15, characterized in that, The client sends a communication request to the SOC chip via a first protocol; the SOC chip sends a second response message to the client via the first protocol; the client sends a data connection establishment request and a log acquisition request to the SOC chip via the first protocol; the SOC chip establishes a data connection with the client based on the data connection establishment request, which is a data connection established via the second protocol; the SOC chip feeds back the target log to the client through the established data connection between the SSD chip and the client, which is a data connection established via the second protocol. And / or, The first protocol is at least one of ISAPI protocol, HIK SDK protocol, and preset private protocol; and / or, the second protocol is at least one of HTTP protocol, HIK SDK protocol, and preset private protocol; and / or, the data channel is at least one of SATA and PCIe. And / or, The SOC chip sends a request to the SSD chip to obtain the length information of the target log; after receiving the request, the SSD chip identifies and sends the length information of the target log back to the SOC chip; after receiving the length information, the SOC chip sends a request to the SSD chip to export the target log in one go, and receives the target log back from the SSD chip. And / or, The SOC chip sends a request to the SSD chip to obtain the attribute information of the target log, wherein the attribute information of the target log includes the total length of the target log and the length of each export; after receiving the attribute information request, the SSD chip feeds back the attribute information of the target log to the SOC chip; after receiving the attribute information of the target log, the SOC chip calculates the number of loops based on the total length of the target log and the length of each export; based on the calculated number of loops, log entries are repeatedly obtained from the SSD chip; the repeatedly obtained log entries are packaged to obtain the target log; And / or, The SOC chip sends a request to the SSD chip to obtain the attribute information of the target log using at least one of SATA and PCIe, wherein the attribute information of the target log includes the total length of the target log and the length of each export; the SSD chip sends the attribute information of the target log back to the SOC chip using at least one of SATA and PCIe; the SOC chip obtains log entries cyclically using at least one of SATA and PCIe according to a calculated number of loops; and the cyclically obtained log entries are packaged using at least one of HTTP protocol, HIK SDK protocol, and preset private protocol to obtain the target log. And / or, The SOC chip receives a query request for a specified log from a client. The query request, which includes the identifier information of the specified log, is used to request the SOC chip to check whether the specified log is stored in the SSD chip. A control command containing the identifier information of the specified log is generated corresponding to the query request and sent to the SSD chip. This control command controls the SSD chip to check whether it stores the specified log. Upon receiving the control command, the SSD chip parses it to obtain the identifier information of the specified log. It then checks whether it stores the specified log based on the identifier information, obtaining a result. This result is fed back to the SOC chip. Finally, the SOC chip receives the result and forwards it to the client. And / or, The SOC chip and the SSD chip also include a management channel; the SOC chip sends control commands for the specified log to the SSD chip via the data channel or the management channel; the SSD chip forwards the result information to the SOC chip via the data channel or the management channel. And / or, When the SSD chip itself stores the specified log, the result information includes the target log; when the SSD chip itself does not store the specified log, the result information is a "not stored" message. Specifically, the SSD chip is used to feed back the target log information to the SOC chip through the data channel or the management channel when it stores the target log; and to feed back the "not stored" message to the SOC chip through the data channel or the management channel when it does not store the target log. And / or, The SOC chip and the SSD chip also include a management channel, which is at least one of GPIO, UART, RS232, SMBus, and I2C; the SOC chip is also used to obtain the status information of the SSD chip through at least one of GPIO, UART, RS232, SMBus, and I2C. And / or, Based on the acquired status information of the SSD chip, the SOC chip generates and sends alarm information when it is determined that the status information of the SSD chip meets the preset alarm conditions. And / or, The SOC chip and the power module of the SSD chip are connected to the control terminal. When the SOC chip receives a target restart command, or when it is determined that the SSD chip is in an abnormal state based on the obtained status information of the SSD chip, it sends a level signal to the power module through at least one of GPIO, UART, RS232, SPI, and SMBus to control the restart of the SSD chip. The target restart command is used to instruct the SSD chip to be restarted. And / or, The SSD chip being in an abnormal state includes the SSD chip being unable to be identified through the data channel and / or the management channel; And / or, The SOC chip and the SSD chip are connected to the control terminals of their power modules. The SOC chip uses at least one of GPIO, UART, RS232, SMBus, and I2C to input a first-level signal to the power control pin of the power module to power off the SSD chip. After a preset time, the SOC chip uses at least one of GPIO, UART, RS232, SMBus, and I2C to input a second-level signal to the power control pin of the power module to power on the SSD chip.

17. A remote log export system, characterized in that, The system includes a client and an SSD recorder. The SSD recorder includes a SOC chip and an SSD chip, which are connected via a data channel. The client is located at the remote end of the SSD recorder. The client is used to send communication requests to the SOC chip; The SOC chip is used to receive communication requests sent by a client, wherein the client is located at a remote end of the SSD recorder, and the communication request indicates that the client requests to communicate with the SOC chip; and to send connection requests to the SSD chip through the data channel, wherein the connection request indicates that the SOC chip requests to communicate with the SSD chip. The SSD chip is configured to send a first response message to the SOC chip via the data channel after receiving the connection request, wherein the first response message indicates that the SSD chip currently allows communication; The SOC chip is further configured to send a second response message to the client after receiving the first response message, wherein the second response message indicates that both the SOC chip and the SSD chip are currently allowed to communicate; The client is further configured to, after receiving the second response information, generate and send a data connection establishment request and a log acquisition request to the SOC chip, wherein the data connection establishment request indicates that the client requests to establish a data connection with the SOC chip, and the log acquisition request includes the identification information of the target log; The SOC chip is also used to receive the data connection establishment request and the log acquisition request; establish a data connection with the client based on the data connection establishment request; and send the log acquisition request to the SSD chip through the data channel. The SSD chip is also used to send the target log to the SOC chip through the data channel after receiving the log acquisition request; The SOC chip is also used to receive the target log fed back by the SSD chip; and to feed back the target log to the client through the data connection.

18. The system according to claim 17, characterized in that, in, The client sends a communication request to the SOC chip via a first protocol; the SOC chip sends a second response message to the client via the first protocol; the client sends a data connection establishment request and a log acquisition request to the SOC chip via the first protocol; the SOC chip establishes a data connection with the client based on the data connection establishment request, which is a data connection established via the second protocol; the SOC chip feeds back the target log to the client through the established data connection between the SSD chip and the client, which is a data connection established via the second protocol. And / or, The first protocol is at least one of ISAPI protocol, HIK SDK protocol, and preset private protocol; and / or, the second protocol is at least one of HTTP protocol, HIK SDK protocol, and preset private protocol; and / or, the data channel is at least one of SATA and PCIe. And / or, The SOC chip is specifically used to send a target log length information acquisition request to the SSD chip; the SSD chip is specifically used to identify and feed back the target log length information to the SOC chip after receiving the length information acquisition request; the SOC chip is specifically used to send a log acquisition request to the SSD chip after receiving the length information, requesting the SSD chip to export the target log in one go, and to receive the target log fed back by the SSD chip; And / or, The SOC chip is specifically configured to send a request to the SSD chip to obtain attribute information of the target log, wherein the attribute information of the target log includes the total length of the target log and the length of each export; the SSD chip, upon receiving the attribute information request, specifically feeds back the attribute information of the target log to the SOC chip; the SOC chip, upon receiving the attribute information of the target log, calculates the number of loops based on the total length of the target log and the length of each export; cyclically obtains log entries from the SSD chip based on the calculated number of loops; and assembles the cyclically obtained log entries into packets to obtain the target log; And / or, The SOC chip is specifically configured to send a request to the SSD chip for obtaining the attribute information of the target log via at least one of SATA and PCIe, wherein the attribute information of the target log includes the total length of the target log and the length of each export; the SSD chip is specifically configured to feed back the attribute information of the target log to the SOC chip via at least one of SATA and PCIe; the SOC chip is specifically configured to cyclically obtain log entries via at least one of SATA and PCIe according to a calculated number of loops; and to assemble the cyclically obtained log entries into packets using at least one of HTTP protocol, HIK SDK protocol, and preset private protocol to obtain the target log; And / or, The SOC chip is further configured to receive a query request for a specified log sent by a client, wherein the query request requests the SOC chip to check whether the specified log is stored in the SSD chip, and the query request includes identification information of the specified log; generate a control instruction corresponding to the query request containing the identification information of the specified log, and send the control instruction to the SSD chip, wherein the control instruction controls the SSD chip to check whether it stores the specified log; the SSD chip is further configured to, upon receiving the control instruction, parse the control instruction to obtain the identification information of the specified log; check whether it stores the specified log based on the identification information of the specified log to obtain result information; and feed back the result information to the SOC chip; the SOC chip is further configured to receive the result information and forward the result information to the client; And / or, The SOC chip and the SSD chip also include a management channel; the SOC chip is specifically used to send control instructions for the specified log to the SSD chip through the data channel or the management channel; the SSD chip is specifically used to forward the result information to the SOC chip through the data channel or the management channel. And / or, When the SSD chip itself stores the specified log, the result information includes the target log; when the SSD chip itself does not store the specified log, the result information is a "not stored" message. Specifically, the SSD chip, when it stores the target log, feeds back the target log information to the SOC chip via the data channel or the management channel; when it does not store the target log, it feeds back the "not stored" message to the SOC chip via the data channel or the management channel. And / or, The SOC chip and the SSD chip also include a management channel, which is at least one of GPIO, UART, RS232, SMBus, and I2C; the SOC chip is also used to obtain the status information of the SSD chip through at least one of GPIO, UART, RS232, SMBus, and I2C. And / or, The SOC chip is also used to generate and send alarm information based on the acquired status information of the SSD chip when it is determined that the status information of the SSD chip meets the preset alarm conditions. And / or, The SOC chip is connected to the control terminal of the power module of the SSD chip; the SOC chip is also used to send a level signal to the power module through at least one of GPIO, UART, RS232, SPI, and SMBus to control the SSD chip to restart when it receives a target restart command or determines that the SSD chip is in an abnormal state based on the obtained status information of the SSD chip, wherein the target restart command is used to instruct the SSD chip to restart; And / or, The SSD chip being in an abnormal state includes the SSD chip being unable to be identified through the data channel and / or the management channel; And / or, The SOC chip and the SSD chip are connected to the control terminals of their respective power modules. Specifically, the SOC chip is used to input a first-level signal to the power control pin of the power module via at least one of GPIO, UART, RS232, SMBus, and I2C to power off the SSD chip. After a preset time, it inputs a second-level signal to the power control pin of the power module via at least one of GPIO, UART, RS232, SMBus, and I2C to power on the SSD chip.

Images