Log data processing method and system and computer equipment

Abstract

The invention is suitable for the technical field of computers, and provides a log data processing method and system and computer device.The method comprises the steps that under the condition that a log downloading demand exists, a downloading node sends a log downloading request to a service node; the service node sends a log uploading request to a terminal device with a non-fixed network address through the platform node based on the log downloading request; the terminal equipment uploads target log data to a target server based on the log uploading request, and feeds back a log uploading event to the platform node; the service node receives the log uploading event sent by the platform node, and feeds back uploading information to the downloading node based on the log uploading event; and the downloading node obtains the uploading information fed back by the service node, and downloads the target log data from the target server based on the downloading address after the target log data is uploaded. According to the method and the device, the log data of the terminal equipment can be remotely acquired under the condition that the network address of the terminal equipment dynamically changes.

Description

Technical Field

[0001] The present application belongs to the field of computer technology, and in particular, relates to a log data processing method, system and computer device. Background Art

[0002] With the development of technology, remote devices that access business systems through mobile networks (such as various in-vehicle devices in in-vehicle systems) are becoming more and more intelligent. The network addresses of these remote devices are dynamically changing and non-fixed, and are usually scattered in different locations. When a remote device fails, technicians need to extract its locally stored log data for fault analysis and troubleshooting. However, due to the dynamic characteristics of the network address, it becomes infeasible to directly access and read the log data through the network address.

[0003] In the related art, obtaining local log data of remote devices usually relies on manual on-site operations, that is, technicians need to go to the location of each remote device and copy the log data using media such as USB flash drives. This method is not only difficult to centrally obtain log data of multiple remote devices in a timely manner, but also consumes a lot of human resources, is inefficient, and cannot meet the needs of modern efficient management and rapid response. Summary of the invention

[0004] In view of this, the embodiments of the present application provide a log data processing method, system and computer device, which can remotely obtain the log data of a terminal device when the network address of the terminal device changes dynamically.

[0005] A first aspect of an embodiment of the present application provides a log data processing method, characterized in that it is applied to a log data processing system, the log data processing system includes a terminal device, a platform node, a service node and a download node, the network address of the terminal device is a non-fixed network address and stores log data, the platform node is communicatively connected to the terminal device and stores the real-time network address of the terminal device, the service node is communicatively connected to the download node and the platform node respectively, and the log data processing method includes: In the case where there is a demand for log downloading, the downloading node sends a log downloading request to the service node, where the log downloading request indicates the log data to be downloaded and the terminal device where the log data is located; The service node sends a log upload request to the terminal device via the platform node based on the log download request; The terminal device uploads the target log data to the target server based on the log upload request, and feeds back a log upload event to the platform node, wherein the log upload event includes a download address of the target log data on the target server; The service node receives the log upload event sent by the platform node, and feeds back upload information to the download node based on the log upload event, wherein the upload information includes a download address of the target log data on the target server; The download node obtains the upload information fed back by the service node, and after the target log data is uploaded, downloads the target log data from the target server based on the download address.

[0006] In an implementation of the first aspect, the method further includes: When receiving the log upload request, the terminal device generates a log reporting task adapted to the log upload request, and feeds back a task identifier of the log reporting task to the platform node; The platform node feeds back the task identifier to the download node via the service node; The download node obtains the upload information from the service node based on the task identifier.

[0007] In an implementation of the first aspect, the log upload event further includes: the task identifier and the upload progress of the target log data, and the feeding back the log upload event to the platform node includes: The terminal device feeds back a log upload event to the platform node based on the upload progress of the target log data, so that the relevant node can obtain the upload progress of the target log data according to the task identifier, and the relevant node is directly or indirectly communicated with the platform node.

[0008] In an implementation of the first aspect, the log upload event includes a task identifier of a log reporting task and an upload progress of the target log data, and the log reporting task is adapted to the log upload request; The step of sending a log upload request to the terminal device via the platform node further includes: The service node receives the task identifier sent by the platform node; The service node sends the task identifier to the download node; The business node receives the log upload event sent by the platform node, and then further includes: The service node updates and stores the log upload event associated with the task identifier based on the task identifier carried in the log upload event.

[0009] In an implementation of the first aspect, the upload information further includes: information indicating whether the target log data is successfully uploaded; and the download node obtains the upload information fed back by the service node, including: The download node periodically sends a query request carrying the task identifier to the service node; In response to the query request, the service node feeds back the upload information to the download node based on the log upload event associated with the task identifier.

[0010] In an implementation of the first aspect, the service node sends a log upload request to the terminal device via the platform node based on the log download request, including: The service node determines a target server from at least one server managed by the platform node; The service node generates a log upload request based on the log download request and the target server; The service node sends the log upload request to the terminal device via the platform node.

[0011] In an implementation of the first aspect, the service node determines a target server from at least one server managed by the platform node, including: If the preset storage mode is default storage, the service node determines a server carrying a default identifier among at least one server managed by the platform node as a target server; If the preset storage mode is dynamic storage, the service node selects a target server from at least one server managed by the platform node based on an evaluation index, where the evaluation index is used to evaluate the status of the storage pool of the server.

[0012] A second aspect of an embodiment of the present application provides a log data processing method, which is applied to a terminal device, wherein the network address of the terminal device is a non-fixed network address and log data is stored, and the log data processing method includes: Receiving a log upload request sent by a platform node, wherein the platform node stores the real-time network address of the terminal device; Based on the log upload request, the target log data is uploaded to the target server, and the log upload event is fed back to the relevant node via the platform node. The log upload event includes the download address of the target log data on the target server. The relevant node is indirectly or directly connected to the platform node.

[0013] In an implementation of the second aspect, the log upload event further includes a task identifier of a log reporting task and a log upload progress of target log data, the log reporting task is adapted to the log upload request, and the feedback of the log upload event to the relevant node via the platform node includes: Obtain at least one preset progress feedback point; If the upload progress of the target log data reaches the progress feedback point, a corresponding log upload event is generated, and the corresponding log upload event is fed back to the relevant nodes via the platform node.

[0014] A third aspect of the embodiments of the present application provides a log data processing method, which is applied to a service node. The service node is respectively connected to the download node and the platform node in communication, the platform node is connected to the terminal device in communication and stores the real-time network address of the terminal device, the network address of the terminal device is a non-fixed network address and stores log data, and the log data processing method includes: Receiving a log download request sent by the download node, wherein the log download request indicates the log data to be downloaded and the terminal device where the log data is located; Based on the log download request, a log upload request is sent to the terminal device via the platform node, wherein the log upload request instructs the terminal device to upload target log data to a target server and feeds back a log upload event to the platform node; Receiving the log upload event sent by the platform node; Feedback upload information to the download node based on the log upload event, where the upload information includes a download address of the target log data on the target server.

[0015] In an implementation of the third aspect, the feeding back the upload information to the download node based on the log upload event includes: receiving a query request for upload information sent by the download node, wherein the query request includes a task identifier of the log reporting task, and the log reporting task is adapted to the log upload request; Based on the query request, query the log upload event associated with the task identifier; Based on the queried log upload event, the upload information is fed back to the download node.

[0016] A fourth aspect of the embodiments of the present application provides a log data processing method, which is applied to a download node, wherein the download node is communicatively connected to a service node, the service node is communicatively connected to a platform node, the platform node is communicatively connected to a terminal device and stores a real-time network address of the terminal device, the network address of the terminal device is a non-fixed network address and stores log data, and the log data processing method includes: In the case of a log download demand, a log download request is sent to the business node, the log download request indicates the log data to be downloaded and the terminal device where the log data is located, and is used to trigger the business node to send a log upload request to the terminal device via the platform node, the log upload request instructs the terminal device to upload the target log data to the target server, and feeds back a log upload event based on the upload progress of the log data; Acquire upload information fed back by the service node based on the log upload event, wherein the upload information includes: a download address of the target log data on the target server; After the target log data is uploaded, the target log data is downloaded from the target server based on the download address.

[0017] In an implementation manner of the fourth aspect, the sending a log download request to the service node further includes: Receiving a task identifier sent by the service node, the task identifier is used to associate a log upload event of a log reporting task, and the log reporting task is adapted to the log upload request; The obtaining of the upload information fed back by the business node based on the log upload event also includes: sending a query request for the upload information to the business node, the query request including the task identifier, and the query request is used to instruct the business node to feed back the upload information.

[0018] A fifth aspect of an embodiment of the present application provides a log data processing device, which is matched with a log data processing system, and the log data processing device includes: A first sending module, configured to, when there is a demand for log downloading, cause the downloading node to send a log downloading request to the service node, wherein the log downloading request indicates the log data to be downloaded and the terminal device where the log data is located; A second sending module, configured for the service node to send a log upload request to the terminal device via the platform node based on the log download request; A log uploading module, used for the terminal device to upload target log data to the target server based on the log upload request, and to feedback a log upload event to the platform node, wherein the log upload event includes a download address of the target log data on the target server; A first feedback module, configured for the service node to receive the log upload event sent by the platform node, so as to feedback upload information to the download node based on the log upload event, wherein the upload information includes a download address of the target log data on the target server; The download module is used for the download node to obtain the upload information fed back by the service node, and after the target log data is uploaded, based on the download address, download the target log data from the target server.

[0019] A sixth aspect of an embodiment of the present application provides a log data processing device, which is deployed on a terminal device, wherein the network address of the terminal device is a non-fixed network address and stores log data, and the log data processing device includes: A first receiving module, configured to receive a log upload request sent by a platform node, wherein the platform node stores a real-time network address of the terminal device; The upload module is used to upload the target log data to the target server based on the log upload request, and feedback the log upload event to the relevant node through the platform node. The log upload event includes: the download address of the target log data on the target server, and the relevant node is indirectly or directly communicated with the platform node.

[0020] A seventh aspect of the embodiments of the present application provides a log data processing device, which is deployed on a service node, wherein the service node is respectively connected to a download node and a platform node, wherein the platform node is connected to a terminal device and stores a real-time network address of the terminal device, wherein the network address of the terminal device is a non-fixed network address and stores log data, wherein the log data processing device includes: A second receiving module, configured to receive a log download request sent by the download node, wherein the log download request indicates the log data to be downloaded and the terminal device where the log data is located; A third sending module is used to send a log upload request to the terminal device via the platform node based on the log download request, wherein the log upload request instructs the terminal device to upload target log data to a target server and feeds back a log upload event to the platform node; A third receiving module, used to receive the log upload event sent by the platform node; The second feedback module is used to feed back upload information to the download node based on the log upload event, where the upload information includes the upload progress of the target log data and the download address of the target log data on the target server.

[0021] An eighth aspect of the embodiments of the present application provides a log data processing device, which is deployed in a download node, wherein the download node is communicatively connected to a service node, wherein the service node is communicatively connected to a platform node, wherein the platform node is communicatively connected to a terminal device and stores a real-time network address of the terminal device, wherein the network address of the terminal device is a non-fixed network address and stores log data, wherein the log data processing device includes: A fourth sending module is used to send a log download request to the business node when there is a log download demand, the log download request indicates the log data to be downloaded and the terminal device where the log data is located, and is used to trigger the business node to send a log upload request to the terminal device via the platform node, the log upload request instructs the terminal device to upload target log data to the target server, and instructs the terminal device to feedback the log upload event to the platform node; An acquisition module, used to acquire the upload information fed back by the service node based on the log upload event, wherein the upload information includes: a download address of the target log data on the target server; The second downloading module is used to download the target log data from the target server based on the download address after the target log data is uploaded.

[0022] A ninth aspect of an embodiment of the present application provides a log data processing system, the log data processing system comprising a terminal device, a download node, a service node and a platform node; the network address of the terminal device is a non-fixed network address and stores log data, the platform node is communicatively connected to the terminal device and stores the real-time network address of the terminal device, and the service node is communicatively connected to the download node and the platform node respectively; The download node is used to: when there is a log download demand, send a log download request to the service node, wherein the log download request indicates the log data to be downloaded and the terminal device where the log data is located; The service node is used to: send a log upload request to the terminal device via the platform node based on the log download request; The terminal device is used to: upload target log data to a target server based on the log upload request, and feedback a log upload event to the platform node, wherein the log upload event includes a download address of the target log data on the target server; The service node is further used to: receive the log upload event sent by the platform node, and feed back upload information to the download node based on the log upload event, wherein the upload information includes a download address of the target log data on the target server; The download node is further used to: obtain the upload information fed back by the service node, and after the target log data is uploaded, download the target log data from the target server based on the download address.

[0023] The tenth aspect of an embodiment of the present application provides a computer device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the computer device is a terminal device, the processor executes the computer program to implement the method described in the second aspect above; when the computer device is a service node, the processor executes the computer program to implement the method described in the third aspect above; when the computer device is a download node, the processor executes the computer program to implement the method described in the fourth aspect above.

[0024] The first aspect of the embodiment of the present application constructs an efficient and flexible log data processing system by integrating terminal devices, platform nodes, service nodes and download nodes, which is particularly suitable for situations where terminal devices have non-fixed network addresses. When there is a log download demand, the download node initiates a log download request, coordinates through the service node, and uses the platform node to trigger a log upload request. The terminal device responds to the log upload request, uploads the target log data to the target server, and feeds back the log upload event through the platform node. Subsequently, the service node receives the log upload event and feeds back to the download node, so that the download node can directly obtain the required target log data from the target server according to the provided download address. In this way, remote acquisition of log data of non-fixed address terminals in a dynamic network environment is achieved.

[0025] The second aspect of the embodiment of the present application is that the platform node stores the real-time network address of the terminal device. When it is necessary to upload log data, the terminal device receives the log upload request sent by the platform node. Based on the log upload request, the terminal device uploads the target log data to the target server, and based on the upload progress of the target log data, the terminal device feeds back the log upload event to the platform node to indicate the upload progress of the target log data and the download address of the target log data on the target server to the relevant nodes that are indirectly or directly connected to the platform node. In this way, it is possible to remotely obtain the log data of the terminal device when the network address of the terminal device changes dynamically.

[0026] In the third aspect of the embodiment of the present application, the service node receives a log download request from a download node, and sends a log upload request to the terminal device where the log data indicated by the log download request is located through the platform node. The log upload request can not only instruct the terminal device to upload the target log data to the target server, but also instruct the terminal device to feedback the log upload event to the platform node based on the upload progress of the target log data. Based on this, the service node can receive the log upload event forwarded by the platform node, and can feedback the upload information to the download node based on the received log upload event, including the upload progress of the target log data and the download address of the target log data on the target server. In this way, the log data of the terminal device can be remotely obtained when the network address of the terminal device changes dynamically.

[0027] In the fourth aspect of the embodiment of the present application, when there is a log download demand, the download node first sends a log download request to the business node that can indicate the log data to be downloaded and the terminal device where the log data is located. Since the log download request can trigger the business node to send a log upload request to the terminal device via the platform node, it can instruct the terminal device to upload the target log data to the target server based on the log upload request, and feedback the log upload event based on the upload progress of the log data. Then the download node obtains the upload information fed back by the business node based on the log upload event. Finally, after the upload progress of the target log data included in the upload information indicates that the target log data has been uploaded, the target log data is downloaded from the target server based on the download address of the target log data included in the upload information on the target server. In this way, it is possible to remotely obtain the log data of the terminal device when the network address of the terminal device changes dynamically.

[0028] It can be understood that the beneficial effects of the fifth to tenth aspects mentioned above can be found in the relevant descriptions in the first, second, third or fourth aspects mentioned above, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0029] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0030] Figure 1 is a schematic diagram of the system structure of the log data processing system provided in an embodiment of the present application; Figure 2 is a flow chart of a log data processing method applied to a terminal device provided in an embodiment of the present application; Figure 3It is a flowchart of a method for executing a log reporting task provided in an embodiment of the present application; Figure 4 It is a flow chart of the method for breakpoint-resume transmission of log data provided by an embodiment of the present application; Figure 5 is a flow chart of a log data processing method applied to a service node provided in an embodiment of the present application; Figure 6 It is a flow chart of an execution method for feeding back upload information to a download node provided in an embodiment of the present application; Figure 7 is a flow chart of a log data processing method applied to a download node provided in an embodiment of the present application; Figure 8 It is a data interaction flow diagram of the log data processing method provided in an embodiment of the present application; Fig. 9 is a schematic diagram of a log data processing device provided in an embodiment of the present application; Fig.10 is a schematic diagram of a log data processing device located at a terminal device provided in an embodiment of the present application; Fig.11 is a schematic diagram of a log data processing device located at a service node provided in an embodiment of the present application; Fig.12 is a schematic diagram of a log data processing device located at a download node provided in an embodiment of the present application; Fig.13 It is a schematic diagram of a computer device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0031] In the following description, specific details such as specific system structures, technologies, etc. are provided for the purpose of illustration rather than limitation, so as to provide a thorough understanding of the embodiments of the present application. However, it should be clear to those skilled in the art that the present application may also be implemented in other embodiments without these specific details. In other cases, detailed descriptions of well-known systems, devices, circuits, and methods are omitted to prevent unnecessary details from obstructing the description of the present application.

[0032] It should be understood that when used in the present specification and the appended claims, the term "comprising" indicates the presence of described features, wholes, steps, operations, elements and / or components, but does not exclude the presence or addition of one or more other features, wholes, steps, operations, elements, components and / or combinations thereof.

[0033] As used in the specification and appended claims of this application, the term "if" can be interpreted as "when" or "uponce" or "in response to determining" or "in response to detecting", depending on the context. Similarly, the phrase "if it is determined" or "if [described condition or event] is detected" can be interpreted as meaning "uponce it is determined" or "in response to determining" or "uponce [described condition or event] is detected" or "in response to detecting [described condition or event]", depending on the context.

[0034] In addition, in the description of the present application specification and the appended claims, the terms "first", "second", "third", etc. are only used to distinguish the descriptions and cannot be understood as indicating or implying relative importance.

[0035] References to "one embodiment" or "some embodiments" etc. described in the specification of this application mean that one or more embodiments of the present application include specific features, structures or characteristics described in conjunction with the embodiment. Therefore, the statements "in one embodiment", "in some embodiments", "in some other embodiments", "in some other embodiments", etc. that appear in different places in this specification do not necessarily refer to the same embodiment, but mean "one or more but not all embodiments", unless otherwise specifically emphasized in other ways. The terms "including", "comprising", "having" and their variations all mean "including but not limited to", unless otherwise specifically emphasized in other ways.

[0036] In one embodiment, Figure 1 As shown, Figure 1 The system architecture of the log data processing system for implementing the log data processing method provided in the embodiment of the present application. Figure 1 As shown, the log data processing system includes a download node 100, a service node 200, a platform node 300, at least one server 400 (the server in the log processing system may also be referred to as a log server), and at least one terminal device 500. The terminal device 500 directly communicates with the platform node 300 and the log server 400 through a mobile network. The platform node 300 stores the real-time network address of the terminal device 500, the download node 100 directly communicates with the service node 200, and the service node 200 directly communicates with the platform node 300.

[0037] The terminal device 500 is pre-registered on the platform node 300. The network address of the terminal device 500 is a non-fixed network address and stores log data. The platform node 300 is used to manage the log server and terminal device in the log management system. The platform node is connected to the terminal device for communication and stores the real-time network address of the terminal device. The download node 100, the service node 200, the platform node 300, the log server 400 and the terminal device 500 cooperate with each other to implement a log processing method for the log data of the terminal device.

[0038] The download node is used to: send a log download request to the business node when there is a demand for log downloading, and the log download request indicates the log data to be downloaded and the terminal device where the log data is located. The business node is used to: send a log upload request to the terminal device via the platform node based on the log download request. The terminal device is used to: upload the target log data to the target server based on the log upload request, and feedback the log upload event to the platform node, and the log upload event includes the download address of the target log data on the target server. The business node is also used to: receive the log upload event sent by the platform node, and feedback the upload information to the download node based on the log upload event, and the upload information includes the download address of the target log data on the target server. The download node is also used to: obtain the upload information fed back by the business node, and after the target log data is uploaded, download the target log data from the target server based on the download address.

[0039] In the application, the terminal device 500 generally refers to a computing resource point set at the edge of the log data processing network. The terminal device may refer to a device with computing, storage and network functions, such as an IoT sensor, a smart camera, an industrial control system, an on-board device on a vehicle, etc.

[0040] In the application, the download node, business node, platform node, and log server can be an independent physical server, or a server cluster or distributed system composed of multiple physical servers. They can also be cloud servers that provide basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, network services, cloud communications, middleware services, domain name services, security services, content delivery networks (CDNs), and big data and artificial intelligence platforms.

[0041] In one embodiment, based on Figure 1 The log processing system shown in FIG. 1 provides a log data processing method, such as Figure 2 As shown, the method is performed by the terminal device, the platform node and the download node in the log data processing system in collaboration with each other, and the specific implementation process includes the following steps S101 to S105: Step S101: When there is a demand for log downloading, the download node sends a log download request to the service node, where the log download request indicates the log data to be downloaded and the terminal device where the log data is located.

[0042] In the application, the download node provides an access entry to the access user of the log data processing system. The access entry may include but is not limited to the following forms: browser access based on the access address or access through the application package. The download node provides the access user with a log download interface, which includes the function item for entering the log export parameters. The log export parameters at least include the log data to be downloaded and the terminal device where the log element is located. They may also include but are not limited to the log type, time range, etc. according to actual needs. The log types include but are not limited to operation logs, print debug logs, coredump files, dmesg files, configuration files, image index files, video index files, IPC logs, 4G logs, MCU logs, etc. Among them, the IPC log is the log data generated by the network camera (IP CAMERA, IPC). The coredump file contains the memory, register status, stack pointer, memory management information, etc. when the program is running. The dmesg file is used to detect and control the system kernel ring buffer to help users understand the system startup information.

[0043] In the application, the download node receives the log download request triggered by the access user and sends the log download request to the service node. The log download request indicates the log data to be downloaded (ie, the log data adapted to the log export parameters) and the terminal device where the log data is located.

[0044] Step S102: Based on the log download request, the service node sends a log upload request to the terminal device via the platform node.

[0045] In the application, the log download request is also used to trigger the service node to send a log upload request to the terminal device via the platform node. The log upload request instructs the terminal device to upload the target log data to the target server and feedback the log upload event based on the upload progress of the log data.

[0046] In the application, the terminal device will be pre-registered on the platform node, communicate directly with the platform node and be managed by the platform node. The platform node saves the real-time network address of the terminal device in the mobile network. The platform node stores the device information of the terminal device, which includes the network address of the device, the device type, etc. The business node generates a log upload request based on the received log download request and the relevant information obtained from the platform node for indicating the target server, and sends the log upload request to the terminal device through the platform node to instruct the terminal device to automatically feedback the log upload event to the platform node. The relevant information indicating the target server includes the fixed network address IP and port of the target server, and the verification information required for secure access to the log server.

[0047] Step S103: the terminal device uploads the target log data to the target server based on the log upload request, and feeds back a log upload event to the platform node, where the log upload event includes a download address of the target log data on the target server.

[0048] In the application, the terminal device accesses the log data processing system based on the mobile communication network (such as 4G network), and the network address of the terminal device changes dynamically. The local storage space of the terminal device stores the log data describing its own operating status. In view of the non-fixed nature of the network address of the terminal device, the method of directly extracting the log data of the terminal device through the network address may result in incomplete or lost log data. In addition, since the network address of the log server in the log processing system is fixed, when receiving the log upload request sent by the platform node, the terminal device can first report its own log data to the designated log server with a fixed network address, and then other nodes can obtain the log data of the terminal device from the designated log server.

[0049] In the application, after receiving the log upload request, the terminal device will also feedback the corresponding log upload event to the platform node during the process of reporting the target log data. The log upload event includes attribute information describing the log upload situation, including at least the download address of the target log data on the target server. There is a corresponding relationship between the log upload event, the log upload request, and the log download. The download address is the network address provided by the target server to read the stored target log data.

[0050] Step S104, the service node receives the log upload event sent by the platform node, and feeds back upload information to the download node based on the log upload event, where the upload information includes the download address of the target log data on the target server.

[0051] In the application, the business node receives the log upload event sent by the platform node and saves the log upload event in the local storage space (such as database, disk, etc.). Based on the log upload event, the business node can feedback the upload information to the download node under the specified conditions. The upload information can at least include the download address of the target log data on the target server, so that the download node can complete the download operation of the target log data based on the upload information. The specified condition can be receiving a query request for the upload information sent by the download node.

[0052] Step S105, the download node obtains the upload information fed back by the service node, and after the target log data is uploaded, downloads the target log data from the target server based on the download address.

[0053] In the application, the download node obtains the download link from the upload information fed back by the business node. When it is determined that the target log data has been uploaded, the target log data is directly downloaded from the target server according to the download address.

[0054] In the application, the upload information may also include information indicating whether the target log data has been successfully uploaded. The download node reads the information indicating whether the target log data has been successfully uploaded and determines whether the target log data has been uploaded. When it is determined that the target log data has been uploaded, the target log data is directly downloaded from the target server according to the download address included in the upload information. The information indicating whether the target log data has been successfully uploaded may be the upload progress of the target log data. If the upload progress of the target log data is 100%, it can be determined that the target log data has been uploaded. After the download is completed, the download node also exports the target log data according to the log format specified by the accessing user and provides it to the accessing user.

[0055] In this embodiment, by integrating terminal devices, platform nodes, business nodes and download nodes, an efficient and flexible log data processing system is constructed, which is particularly suitable for situations where terminal devices have non-fixed network addresses. When there is a log download demand, the download node initiates a log download request, which is coordinated by the business node and uses the platform node to trigger a log upload request. The terminal device responds to the log upload request, uploads the target log data to the target server, and feeds back the log upload event through the platform node. Subsequently, the business node receives the log upload event and feeds back to the download node, so that the download node can directly obtain the required target log data from the target server according to the provided download address. In this way, remote acquisition of log data of non-fixed address terminals in a dynamic network environment is achieved.

[0056] In one embodiment, the implementation process of the method for obtaining upload information of target log data includes: When the terminal device receives a log upload request, it generates a log reporting task that is compatible with the log upload request and feeds back the task identifier of the log reporting task to the platform node; the platform node feeds back the task identifier to the download node via the business node; the download node obtains the upload information from the business node based on the task identifier.

[0057] In the application, the terminal device creates a log reporting task that can run asynchronously for the received log upload request. The asynchronously running log reporting task is used to perform the actual processing of reporting the target log data to the target server. In order to facilitate the relevant nodes in the log processing system to track the upload information of the target log data, the terminal device will also feedback a task identifier that uniquely identifies the log reporting task to the platform node, and then send the task identifier to the business node and the download node in sequence through the platform node. The business node establishes a corresponding relationship between the task identifier and the log upload event. The download node queries the adapted log upload event from the business node based on the task identifier, obtains the upload information, and implements tracking and processing for the log reporting task.

[0058] In this embodiment, by generating a log reporting task adapted to the log upload request and feeding back a unique task identifier to the platform node, asynchronous processing and efficient management of log data upload are achieved.

[0059] In one embodiment, when the terminal device implements log reporting based on the log reporting task, the log upload event matching the log upload task also includes: a task identifier and the upload progress of the target log data. The implementation process of the terminal device feeding back the log upload event to the platform node is as follows: the terminal device feeds back the log upload event to the platform node based on the upload progress of the target log data, so that the relevant nodes can obtain the upload progress of the target log data according to the task identifier, and the relevant nodes are directly or indirectly communicated with the platform node.

[0060] In the application, the upload of target log data usually takes a long time. The terminal device can feedback the log upload event adapted to the log upload task to the platform node based on the upload progress of the target log data. At this time, the log upload event includes the task identifier and the upload progress. In this way, the relevant nodes in the log data processing system can determine the upload progress of the target log data according to the task identifier, and the relevant nodes are directly or indirectly connected to the platform node.

[0061] In this embodiment, by adding the task identifier and upload progress information to the log upload event, the terminal device can dynamically feedback the progress of the log upload to the platform node. This process can ensure that the relevant nodes (such as business nodes or download nodes) can directly or indirectly track the status of a specific log upload task in real time through the platform node.

[0062] In one embodiment, when the log upload event includes the task identifier of the log reporting task and the upload progress of the target log data, the log reporting task is adapted to the log upload request. After the business node sends the log upload request to the terminal device via the platform node, the following operations can also be performed: the business node receives the task identifier sent by the platform node; the business node sends the task identifier to the download node; after the business node receives the log upload event sent by the platform node, the business node can also perform the following operations: the business node updates the log upload event associated with the task identifier based on the task identifier carried by the log upload event.

[0063] In the application, when the log upload event includes the task identifier of the log reporting task and the upload progress of the target log data, the business node updates the log upload event associated with the task identifier stored in the local storage space according to the task identifier and the log upload event received from the platform node. On the other hand, the task identifier is sent to the download node so that the download node can obtain the upload information of the target log data based on the task identifier, and the upload information is determined based on the log upload event adapted to the task identifier.

[0064] In this embodiment, by including the task identifier and the upload progress of the target log data in the log upload event, the business node can update the log upload event associated with the task identifier through the information received from the platform node, thereby ensuring the consistency between the log upload event stored by the business node and the task identifier.

[0065] In one embodiment, the upload information also includes: information indicating whether the target log data has been uploaded successfully; the implementation process of the download node obtaining the upload information fed back by the business node is as follows: the download node periodically sends a query request carrying the task identifier to the business node; in response to the query request, the business node feeds back the upload information to the download node based on the log upload event associated with the task identifier.

[0066] In the application, the upload information also includes information indicating whether the target log data has been successfully uploaded. The download node can periodically send a query request (i.e., polling method) carrying a task identifier to the business node based on a preset interval (such as 3 seconds, 5 seconds, etc.). The query request is used to query the upload information of the target log data. For example, the download node sends a query request every 3 seconds. The business node responds to the request and feeds back the upload information. Since the upload information also includes information indicating whether the target log data has been successfully uploaded, if it is determined based on the upload information that the target log data has not been uploaded, upload information with different upload progress can be obtained by polling. The polling after the target log data is successfully uploaded will obtain the upload information containing an upload progress of 100%.

[0067] In this embodiment, by adding status information indicating whether the target log data is successfully uploaded to the upload information, and using the download node to periodically send a query request carrying a task identifier to the business node, real-time tracking and confirmation of the log upload result is achieved.

[0068] In one embodiment, Figure 2 The implementation process of step S102 is as follows: the business node determines the target server from at least one server managed by the platform node; the business node generates a log upload request based on the log download request and the target server; the business node sends the log upload request to the terminal device via the platform node.

[0069] In the application, the log upload request sent by the business node to the terminal device via the platform node carries the relevant information of the target server. After the business node receives the log download request sent by the download node, it first selects the target server from at least one server managed by the platform node. Among them, the selection of the target server is related to the storage method. The storage method includes default storage and dynamic storage. Default storage refers to pre-setting the default server as the target server. Dynamic storage refers to dynamically selecting the target server according to the status of the server's storage pool.

[0070] In this embodiment, through the collaborative work of the business node and the platform node, efficient and flexible target server selection and generation and sending of log upload requests are achieved, which significantly improves the efficiency and reliability of log data processing.

[0071] In one embodiment, the specific implementation process of determining the target server from at least one server managed by the platform node is as follows: if the preset storage method is default storage, the server carrying the default identifier in at least one server managed by the platform node is determined as the target server; if the preset storage method is dynamic storage, based on the evaluation index, the target server is selected from at least one server managed by the platform node; wherein the evaluation index includes at least one of the following: the remaining capacity of the server's storage pool, the health status of the server's storage pool, and the evaluation index is used to evaluate the status of the server's storage pool.

[0072] In the application, if the preset storage mode is default storage, a server carrying a default identifier will be selected as the target server from at least one server managed by the platform node. If the preset storage mode is dynamic storage, the target server will be selected from at least one server associated with the platform node based on the evaluation index. The evaluation index is used to evaluate the status of the server's storage pool, and the evaluation index includes the remaining capacity of the server's storage pool and the performance of the storage pool (such as I / O throughput).

[0073] In applications, for dynamic storage, in addition to the business node automatically selecting based on the evaluation indicators, the business node can also read external storage configuration information and select a target server that matches the storage configuration information from multiple servers based on the storage configuration information. The storage configuration information can be obtained by authorized users based on the remaining capacity of the storage pool of each server and the performance configuration of the storage pool. The storage configuration information can be saved in a file of a specified format.

[0074] Exemplarily, taking the remaining capacity of the storage pool as an evaluation indicator, the business node determines the remaining capacity of the storage pool of each server in at least one server managed by the platform node; randomly or conditionally selects the target server from the servers whose remaining capacity reaches a preset remaining capacity threshold, such as directly selecting the server with the largest remaining capacity in the server storage pool as the target server.

[0075] In this embodiment, the platform node intelligently selects the target server according to the preset storage method. When storing by default, the server carrying the default identifier is automatically selected as the target server, which simplifies the selection process and ensures consistency. In dynamic storage mode, the system intelligently selects the optimal target server from multiple servers based on evaluation indicators. This not only improves the flexibility and adaptability of storage resource allocation, but also optimizes storage performance according to actual conditions, avoiding data loss or upload failure due to insufficient storage space or poor health. By introducing evaluation indicators for intelligent decision-making, the stability and reliability of the system are enhanced, while also ensuring the safe storage and efficient management of log data.

[0076] Next, we will explain Figure 1 In the log data processing system shown, the terminal device, the service node, and the download node independently execute the specific process of the corresponding log data processing method.

[0077] In one embodiment, based on Figure 1 The log processing system shown in FIG. 1 provides a log data processing method, such as Figure 3 As shown, this method is applied to Figure 1 Taking the terminal device in as an example, the network address of the terminal device is a non-fixed network address and log data is stored. The terminal device implements the log data processing method including the following steps S201 to S202: Step S201, receiving a log upload request sent by a platform node, where the platform node stores the real-time network address of the terminal device.

[0078] Step S202, based on the log upload request, upload the target log data to the target server, and feedback the log upload event to the relevant nodes through the platform node. The log upload event includes: the download address of the target log data on the target server, and the indirect or direct communication connection between the relevant node and the platform node.

[0079] In the application, after the terminal device receives the log upload request, it first creates a log reporting task and immediately feeds back the task identifier of the log reporting task to the platform node for direct communication. The task identifier is used to uniquely identify the log reporting task. Then, the terminal device asynchronously executes the log reporting task and uploads the target log data adapted to the log export parameters to the target server. And based on the upload progress of the target log data, the log upload event is fed back to the platform node. The log upload event encapsulates the upload progress of the target log data and the download address of the target log data on the target server. Based on the log upload event, the terminal device can indicate the upload progress of the target log data and the download address of the target log data on the target server to the relevant nodes. The relevant nodes are indirectly or directly connected to the platform nodes. The relevant nodes can be download nodes, business nodes, etc. in the log data processing system.

[0080] In this embodiment, the platform node stores the real-time network address of the terminal device. When it is necessary to upload log data, the terminal device receives the log upload request sent by the platform node. Based on the log upload request, the terminal device uploads the target log data to the target server, and based on the upload progress of the target log data, the terminal device feeds back the log upload event to the platform node, so as to indicate the upload progress of the target log data and the download address of the target daily data on the target server to the relevant nodes indirectly or directly connected to the platform node. In this way, the log data of the terminal device can be remotely obtained when the network address of the terminal device changes dynamically.

[0081] In one embodiment, Figure 4 As shown, Figure 3 The implementation process of step 202 includes the following steps S301 to S303: Step S301, detect whether the task identifier exists and obtain the detection result.

[0082] In the application, the server (also called log server) in the log data processing system supports breakpoint resumption. For the target log data, in the same log reporting task, the terminal device can perform one or multiple log uploads based on the current mobile network conditions. After receiving the target log data, the target server will return the download address of the target log data in the target server to the terminal device. The terminal device saves the corresponding task identifier and download address, and establishes an association between the task identifier and the download address. Each time the log data is reported based on the log reporting task, the terminal device first detects whether the task identifier of the log reporting task already exists locally to determine whether the log reporting task has been interrupted, and performs specific log data reporting processing based on the detection result.

[0083] Step S302: If the detection result indicates that the task identifier exists, the breakpoint position of the target log data is determined, and the remaining data of the target log data is continuously transmitted to the target server starting from the breakpoint position.

[0084] In the application, if the task identifier of the corresponding log reporting task already exists, it means that the log reporting task has been interrupted, and the currently executed log data reporting is not the first reporting of the target log data. Based on this, the terminal device first determines the breakpoint position of the target log data, and then starts from the breakpoint position and continues to transmit the remaining data of the target log data to the target server.

[0085] Step S303: if the detection result indicates that there is no task identifier, the target log data is uploaded to the target server starting from the start position of the target log data, and the target server is informed of the association relationship between the target log data and the task identifier.

[0086] In the application, if there is no task identifier for the corresponding log reporting task, for the first upload of the target log data, the target log data is uploaded directly to the target server from the starting position of the target log data, and the relationship between the target log data and the task identifier is indicated to the target server.

[0087] In this embodiment, the consistency of the log upload operation is ensured through the query of the task identifier and the breakpoint-resume mechanism, and the upload can be accurately resumed even in the case of poor network conditions or interruptions in the upload process. In this way, not only the success rate and integrity of log upload can be improved, but also the fault tolerance and user experience of the log data processing system can be enhanced, which is particularly suitable for scenarios with unstable networks or large file uploads, and ensures the efficiency and reliability of log data processing.

[0088] In one embodiment, the log upload event also includes the task identifier of the log reporting task and the log upload progress of the target log data. The log reporting task is adapted to the log upload request. The specific implementation process of feeding back the log upload event to the relevant nodes through the platform node is as follows: obtain at least one preset progress feedback point; if the upload progress of the target log data reaches the progress feedback point, generate a corresponding log upload event, and feed back the corresponding log upload event to the relevant nodes through the platform node.

[0089] In the application, the progress feedback point is used to indicate the upload progress point where log upload event feedback is required during the log data upload process. When the terminal device is uploading the target log data, it can monitor the upload progress based on one or more preset progress feedback points. Whenever the upload progress reaches a certain progress feedback point, the terminal device will generate a corresponding log upload event and promptly feedback this log upload event to the platform node.

[0090] Exemplarily, the progress feedback points are set to 20%, 50%, 80%, 100%, etc. Then, when the upload progress of the target log data reaches 20%, 50%, 80%, 100%, the log upload event will be fed back to the platform node.

[0091] In this embodiment, by setting preset progress feedback points, log upload events are generated and fed back according to the upload progress during the log data upload process, which significantly enhances the transparency and controllability of the log upload process.

[0092] In one embodiment, Figure 5 As shown, a log data processing method is provided, which is applied to Figure 1 The business node in is taken as an example to illustrate, the business node is respectively connected to the download node and the platform node in communication, the platform node is connected to the terminal device in communication and stores the real-time network address of the terminal device, the network address of the terminal device is a non-fixed network address and stores log data, and the log data processing method includes the following steps S401 to S404: Step S401: receiving a log download request sent by a download node, where the log download request indicates the log data to be downloaded and the terminal device where the log data is located.

[0093] In the application, the service node communicates with the download node and the platform node respectively. The access user of the log data processing system can send a log download request to the service node through the download node. The log download request indicates the log data to be downloaded and the terminal device where the log data is located.

[0094] Step S402: Based on the log download request, a log upload request is sent to the terminal device via the platform node. The log upload request instructs the terminal device to upload target log data to the target server and feeds back the log upload event to the platform node.

[0095] In the application, after receiving the log download request, the service node selects a target server from at least one server managed by the platform node, then generates a log upload request based on the log download request, and forwards the log upload request to the terminal device through the platform node. The log upload request instructs the terminal device to upload the target log data to the target server. At the same time, the terminal device is instructed to feedback the log upload event to the platform node.

[0096] Step S403: receiving a log upload event sent by the platform node.

[0097] In the application, the business node receives the log upload event sent by the platform node and saves the log upload event in the local storage space (such as a database, etc.).

[0098] Step S404: Feedback upload information to the download node based on the log upload event, where the upload information includes the download address of the target log data on the target server.

[0099] In the application, the service node may also feed back the upload information to the download node based on the log upload event. The service node may feed back the upload information to the download node based on the log upload event when receiving a query request for the upload information sent by the download node.

[0100] In this embodiment, the service node receives a log download request from a download node, and sends a log upload request to the terminal device where the log data indicated by the log download request is located through the platform node. The log upload request can not only instruct the terminal device to upload the target log data to the target server, but also instruct the terminal device to feedback the log upload event to the platform node based on the upload progress of the target log data. Based on this, the service node can receive the log upload event forwarded by the platform node, and can feedback the upload information to the download node based on the received log upload event, including the upload progress of the target log data and the download address of the target log data on the target server. In this way, the log data of the terminal device can be remotely obtained when the network address of the terminal device changes dynamically.

[0101] In one embodiment, Figure 6 As shown, the implementation process of feeding back the upload information to the download node includes the following steps S501 to S503: Step S501: receiving a query request for upload information sent by a download node, wherein the query request includes a task identifier of a log reporting task, and the log reporting task is adapted to the log upload request.

[0102] Step S502: based on the query request, query the log upload event associated with the task identifier.

[0103] Step S503: Based on the queried log upload event, the upload information is fed back to the download node.

[0104] In the application, after the business node receives the log upload event fed back by the platform node, it will save the log upload event to the local storage space (such as a database, etc.). In the process of the terminal device asynchronously executing the log reporting task for the target log data, if the download node needs to track the upload progress of the target log data, it can send a query request carrying the task identifier to the business node. The business node receives the query request, and based on the task identifier carried in the query request, queries the local storage space for the log upload event associated with the task identifier, reads the upload progress of the target log data, the task identifier, and the download address on the target server from the queried log upload event to form the upload information, and feeds back the upload information to the download node.

[0105] In this embodiment, the business node receives the upload result query request and feeds back the upload information, thereby achieving efficient tracking and management of the log upload progress and improving the transparency and reliability of log data processing.

[0106] In one embodiment, Figure 7 As shown, a log data processing method is provided, which is applied to Figure 1 Taking the download node in as an example, the download node is connected to the business node in communication, the business node is connected to the platform node in communication, the platform node is connected to the terminal device in communication and stores the real-time network address of the terminal device, the network address of the terminal device is a non-fixed network address and stores log data, and the log data processing method includes the following steps S601 to S603: Step S601, when there is a need to download logs, sends a log download request to the business node. The log download request indicates the log data to be downloaded and the terminal device where the log data is located, and is used to trigger the business node to send a log upload request to the terminal device via the platform node. The log upload request instructs the terminal device to upload the target log data to the target server, and instructs the terminal device to feedback the log upload event to the platform node.

[0107] Step S602: Obtain upload information fed back by the business node based on the log upload event, where the upload information includes: a download address of the target log data on the target server.

[0108] In the application, there is a corresponding relationship between the log download request sent by the download node, the log upload request received by the terminal device, and the log upload event fed back by the terminal device. After the download node sends the log download request to the service node, the terminal device receives the log upload request corresponding to the log download request, uploads the target log data to the target server, and at the same time feeds back the log upload event to the service node via the platform node, and the service node saves the log upload event. Based on this, the download node can obtain the upload information based on the log upload event feedback from the service node, and the upload information at least includes the download address of the target log data on the target server.

[0109] Step S603: after the target log data is uploaded, the target log data is downloaded from the target server based on the download address.

[0110] In this embodiment, when there is a log download demand, the download node first sends a log download request to the business node that can indicate the log data to be downloaded and the terminal device where the log data is located. Since the log download request can trigger the business node to send a log upload request to the terminal device via the platform node, it can instruct the terminal device to upload the target log data to the target server based on the log upload request, and feedback the log upload event based on the upload progress of the log data. Then the download node obtains the upload information fed back by the business node based on the log upload event. Finally, after the upload progress of the target log data included in the upload information indicates that the target log data has been uploaded, the target log data is downloaded from the target server based on the download address of the target log data included in the upload information on the target server. In this way, it is possible to remotely obtain the log data of the terminal device when the network address of the terminal device changes dynamically.

[0111] In one embodiment, after the download node sends a log download request to the business node, it also includes: receiving a task identifier sent by the business node, the task identifier is used to associate the log upload event of the log reporting task, and the log reporting task is adapted to the log upload request; and before obtaining the upload information fed back by the business node based on the log upload event, it also includes: sending a query request for the upload information to the business node, the query request includes the task identifier, and the query request is used to instruct the business node to feed back the upload information.

[0112] In the application, the terminal device creates a log reporting task that is compatible with the log upload request, and feeds back the task identifier that uniquely identifies the log reporting task to the business node and the download node in turn through the transmission channel of platform node -> business node -> download node. The business node establishes an association between the task identifier and the log upload event in the local storage space. The download node queries the upload information from the business node by sending an upload result query request carrying the task identifier to the business node. The upload result query request is used to instruct the business node to feed back the upload information that is compatible with the task identifier.

[0113] In this embodiment, after sending a log download request, the download node receives a task identifier from the business node, which is used to associate the log reporting task and its upload event, ensuring the traceability of each reporting task. Subsequently, before obtaining the upload information, the download node sends an upload result query request containing the task identifier to the business node, instructing the business node to feedback the upload information. Not only does it ensure the accuracy and timeliness of the uploaded information, but it also enhances the transparency of the system, allowing users to monitor the progress of log uploads in real time and quickly respond to any potential problems. In addition, by associating the upload event with the task identifier, the query process of the upload status is simplified, the response speed and operating efficiency of the system are improved, the integrity and reliability of the log data processing are ensured, and the entire log management process is optimized.

[0114] The log data processing method provided in the embodiment of the present application realizes the remote acquisition of log data of non-fixed address terminals in a dynamic network environment by integrating terminal devices, platform nodes, service nodes and download nodes. It is suitable for application scenarios where log data in a mobile or dynamic network environment needs to be frequently processed. The log data processing method provided in the embodiment of the present application is applied to the log data processing scenario supported by the vehicle-mounted device management platform as an example for explanation. In the application, the vehicle-mounted device management platform is an application system for managing and monitoring the operating status of the vehicle. The log data processing system, as a subsystem in the vehicle-mounted device management platform, can collect log data from each vehicle-mounted device in the vehicle in a centralized manner to provide corresponding services. These services generally include but are not limited to driving monitoring, route monitoring, vehicle health inspection, event reporting and remote control functions. In the log data processing scenario supported by the vehicle-mounted device management platform, the various types of vehicle-mounted devices managed by the vehicle-mounted device management platform are the terminal devices of the aforementioned log data processing system, and the log server used to store log data is the aforementioned server. The vehicle-mounted device accesses the log data processing system through the mobile network. The network address of the vehicle-mounted device is dynamically changing and not fixed, and the network address of the log server is fixed. In this scenario, the download node is an independent functional module in the vehicle-mounted equipment management platform and can be called a download center. The service node mainly provides vehicle-mounted services, such as driving monitoring, route monitoring, etc., including reporting of vehicle-mounted equipment events, text-to-speech intercom, etc. The platform node can be used to manage resources such as log servers and vehicle-mounted equipment, such as adding, deleting, modifying, and querying vehicle-mounted equipment information, and configuring data for vehicle-mounted equipment.

[0115] Based on the above description, for the log data processing scenarios supported by the vehicle-mounted device management platform, the specific process of log data processing is realized through interaction and collaboration between the download node, business node, platform node, log server, and vehicle-mounted device. Figure 8 As shown, the specific implementation process is as follows: First, the following steps are performed in the initial stage: The vehicle-mounted device performs 1. Registering to the platform node. The vehicle-mounted device is registered to the platform node of the log data processing system through a preset communication protocol. The platform node saves the device information of the vehicle-mounted device. The device information includes the network address of the vehicle-mounted device, such as the network address IP, port, etc., which is used when the interface is called later. Then, the access user finds that there is a problem with the target vehicle-mounted device. At this time, there is a log download demand for the target log data of the target vehicle-mounted device. Each node collaboratively performs the following steps: The access user performs 2. Sending a log download request to the download node, the log download request carries log export parameters, the log export parameters include log type, log time range, and log export parameters are used to determine the target log data to be exported. The download node performs 3. Sending a log download request to the business node, which is essentially to pass the log export parameters to the business node. Then, in the target log server determination stage, the following steps are performed: The business node performs 4. Obtaining the local storage configuration from the platform node, where the local storage configuration describes the relevant information of all log servers managed by the platform node. The business node performs 5. Selecting the target log server and sending the relevant information of the target log server to the platform node. The platform node executes 6. Sends the relevant information of the target log server to the target vehicle-mounted device. The target vehicle-mounted device executes 7. Performs configuration return. In essence, after the target vehicle-mounted device receives the relevant information of the target log server, it feedbacks to the platform node that the configuration information has been successfully received. The business node executes 8. Calls the (general) log export interface provided by the platform node, and sends the log export parameters to the platform node. In the application, the platform node encapsulates the log export interfaces of various types of vehicle-mounted devices to obtain a general log export interface that is compatible with various types of vehicle-mounted devices. The business node executes 9. Calls the relevant interface provided by the target vehicle-mounted device to send the log export parameters to the target vehicle-mounted device. In essence, based on the log download request, a log upload request is sent to the vehicle-mounted device via the platform node.

[0116] Next, the process of realizing log data reporting includes the following steps: the vehicle-mounted device executes 10. Create a log reporting task, and at the same time executes 11.1. Feedback the task identifier Guid of the log reporting task to the platform node, the platform node executes 11.2. Feedback the task identifier Guid to the business node, and the business node executes 11.3. Feedback the task identifier Guid to the download node. The target vehicle-mounted device executes 12.1 to report the target log data to the target log server. And receive the download link of the log returned by the target log server. When the upload progress reaches 20% (the progress feedback point referred to in the previous text), the target vehicle-mounted device executes 12.2 and feeds back the log upload event to the platform node. The log upload event encapsulates the task identifier Guid, the log download address, the upload progress, the error information, etc. The platform node executes 12.3. Feedback the log upload event to the business node. The business node executes 13. Store the log upload event in the database. The download node optionally executes step 14. Send an upload result query request to the download node, and the upload result query request carries the Guid. The business node queries the log upload event based on the upload result query request and feedbacks the log upload result. Since the upload progress is 20%, the result of unsuccessful upload can be directly returned. Since the target log data has not been uploaded, the target vehicle device continues to execute 15.1. Report the remaining target log data and receive the log download link returned by the target log server. If the upload progress reaches 100%, the target vehicle device executes 15.2 and feedbacks the log upload event (upload progress is 100%) to the platform node. Then the platform node executes 15.3 to feedback the log upload event to the business node. The business node executes 16. Store the log upload event in the database. Feedback the log upload event to the platform node based on the upload progress of the target log data, and feedback the log upload event to the business node through the platform node. The download node optionally executes step 17. Send an upload result query request to the download node. The upload result query request carries Guid. The business node queries the log upload event based on the upload result query request and feedbacks the log upload result. At this time, the upload progress is 100%, and the result of successful upload can be directly returned.

[0117] After the target log data is successfully reported, the download node executes 18. Download the target log data from the target log server. The target log server feeds back the target log data to the download node. 19. The user downloads the target log data from the download node and analyzes the problem.

[0118] In this embodiment, the log data processing for the vehicle-mounted device with non-fixed network address is realized through the collaborative work between the download node, the service node, the platform node and the vehicle-mounted device. Specifically, when there is a log download demand, the download node sends a log download request to the service node, indicating the required log data and the vehicle-mounted device where it is located. After receiving the request, the service node triggers the vehicle-mounted device to upload the log data to the target log server through the platform node, and feedbacks the log upload event during the upload process, reporting the upload progress and the download address of the target log data. The platform node saves the real-time network address of the vehicle-mounted device as an intermediary to ensure that the vehicle-mounted device can be accurately found and instructed to upload the log even when the network address changes. Based on the upload information obtained from the service node, the download node downloads the log data from the target log server according to the provided download address after confirming that the log data upload is completed. In this way, not only the log extraction problem caused by the dynamic change of the network address of the vehicle-mounted device is solved, the integrity and accuracy of the log data are guaranteed, but also the flexibility and scalability of the log data processing system are improved, the access of multiple types of vehicle-mounted devices is supported, the transparency and controllability of log data management are enhanced, and the log processing efficiency is significantly improved. In this way, the log processing system can respond to log data download needs in a timely manner, simplify the log data collection process, reduce manual intervention, and provide accurate data support for subsequent business processing based on log data.

[0119] The present application also provides a log data processing device for executing the steps in the above log data processing method embodiment. Fig. 9 As shown, the log data processing device 900 provided in the embodiment of the present application includes: The first sending module 910, when there is a log download demand, the download node sends a log download request to the service node, where the log download request indicates the log data to be downloaded and the terminal device where the log data is located.

[0120] The second sending module 920, the business node sends a log upload request to the terminal device via the platform node based on the log download request.

[0121] Log upload module 930, the terminal device uploads the target log data to the target server based on the log upload request, and feeds back the log upload event to the platform node. The log upload event includes the download address of the target log data on the target server.

[0122] The first feedback module 940 is used for the business node to receive the log upload event sent by the platform node, so as to feedback the upload information to the download node based on the log upload event, and the upload information includes the download address of the target log data on the target server.

[0123] The download module 950 is used for the download node to obtain the upload information fed back by the service node, and after the target log data is uploaded, download the target log data from the target server based on the download address.

[0124] In one embodiment, the log upload event also includes: a task identifier and the upload progress of the target log data. The feedback module is also used for the terminal device to feedback the log upload event to the platform node based on the upload progress of the target log data, so that the relevant node can obtain the upload progress of the target log data according to the task identifier. The relevant node is directly or indirectly communicated with the platform node.

[0125] In one embodiment, the log upload event includes the task identifier of the log reporting task and the upload progress of the target log data. The log reporting task is adapted to the log upload request. The second sending module is also used for the business node to receive the task identifier sent by the platform node; the business node sends the task identifier to the download node; the business node updates and stores the log upload event associated with the task identifier based on the task identifier carried by the log upload event.

[0126] In one embodiment, the upload information also includes: information indicating whether the target log data has been uploaded successfully; the download module is also used for the download node to periodically send a query request carrying a task identifier to the business node; in response to the query request, the business node feeds back the upload information to the download node based on the log upload event associated with the task identifier.

[0127] In one embodiment, the second sending module is also used by the business node to determine the target server from at least one server managed by the platform node; the business node generates a log upload request based on the log download request and the target server; the business node sends the log upload request to the terminal device via the platform node.

[0128] In one embodiment, the second sending module is also used to, if the preset storage method is default storage, the business node determines a server carrying a default identifier in at least one server managed by the platform node as a target server; if the preset storage method is dynamic storage, the business node selects a target server from at least one server managed by the platform node based on an evaluation indicator, and the evaluation indicator is used to evaluate the status of the server's storage pool.

[0129] The embodiment of the present application also provides a log data processing device, which is used to execute the steps in the above log data processing method embodiment. The log data processing device is deployed in a terminal device, the network address of the terminal device is a non-fixed network address and stores log data. Fig.10 As shown, the log data processing device 1000 provided in the embodiment of the present application includes: The first receiving module 1010 is used to receive a log upload request sent by a platform node, and the platform node stores a real-time network address of the terminal device.

[0130] The upload module 1020 is used to upload the target log data to the target server based on the log upload request, and to feedback the log upload event to the relevant nodes via the platform node. The log upload event includes: the download address of the target log data on the target server, and the indirect or direct communication connection between the relevant nodes and the platform node.

[0131] In one embodiment, the log upload event also includes the task identifier of the log reporting task and the log upload progress of the target log data. The log reporting task is adapted to the log upload request. The upload module is also used to obtain at least one preset progress feedback point. If the upload progress of the target log data reaches the progress feedback point, a corresponding log upload event is generated, and the corresponding log upload event is fed back to the relevant nodes via the platform node.

[0132] The embodiment of the present application also provides a log data processing device for executing the steps in the above log data processing method embodiment. The log data processing device is deployed in the service node. The service node is respectively connected to the download node and the platform node, the platform node is connected to the terminal device and stores the real-time network address of the terminal device, the network address of the terminal device is a non-fixed network address and stores log data. Fig.11 As shown, the log data processing device 1100 provided in the embodiment of the present application includes: The second receiving module 1110 is used to receive a log download request sent by a download node, where the log download request indicates the log data to be downloaded and the terminal device where the log data is located.

[0133] The third sending module 1120 is used to send a log upload request to the terminal device via the platform node based on the log download request, the log upload request instructs the terminal device to upload target log data to the target server, and feeds back the log upload event to the platform node.

[0134] The third receiving module 1130 is used to receive the log upload event sent by the platform node.

[0135] The second feedback module 1140 is used to feed back upload information to the download node based on the log upload event, where the upload information includes a download address of the target log data on the target server.

[0136] In one embodiment, the second feedback module is also used to receive a query request for upload information sent by the download node, the query request includes a task identifier of the log reporting task, and the log reporting task is adapted to the log upload request; based on the query request, query the log upload event associated with the task identifier; based on the queried log upload event, feedback the upload information to the download node.

[0137] The embodiment of the present application also provides a log data processing device for executing the steps in the above log data processing method embodiment. The log data processing device is deployed in the download node. The download node is connected to the service node in communication, the service node is connected to the platform node in communication, the platform node is connected to the terminal device in communication and stores the real-time network address of the terminal device, the network address of the terminal device is a non-fixed network address and stores log data. Fig.12 As shown, the log data processing device 1200 provided in the embodiment of the present application includes: The fourth sending module 1210 is used to send a log download request to the business node when there is a log download demand. The log download request indicates the log data to be downloaded and the terminal device where the log data is located, and is used to trigger the business node to send a log upload request to the terminal device via the platform node. The log upload request instructs the terminal device to upload the target log data to the target server, and instructs the terminal device to feedback the log upload event to the platform node.

[0138] The acquisition module 1220 is used to acquire the upload information fed back by the service node based on the log upload event, where the upload information includes: the download address of the target log data on the target server.

[0139] The second downloading module 1230 is used to download the target log data from the target server based on the download address after the target log data is uploaded.

[0140] In one embodiment, the fourth sending module is also used to receive a task identifier sent by the business node, and the task identifier is used to associate the log upload event of the log reporting task, and the log reporting task is adapted to the log upload request; accordingly, the acquisition module is also used to send a query request for the uploaded information to the business node, and the query request includes the task identifier, and the query request is used to instruct the business node to feedback the uploaded information.

[0141] In application, each module in the log data processing device may be a software program module, or may be implemented by different logic circuits integrated in a processor, or may be implemented by multiple distributed processors.

[0142] Fig.13 A computer device (such as a computer device for implementing log data processing) provided in an embodiment of the present application Figure 1A schematic diagram of the structure of a download node, business node, platform node, or terminal device in the system. Fig.13 As shown, the computer device 1300 of this embodiment includes: at least one processor 1310 ( Fig.13 Only one is shown in the figure), a memory 1320, and a computer program 1330 stored in the memory 1320 and executable on the at least one processor 1310, wherein the processor 1310 implements the steps of any of the above-mentioned log data processing method embodiments when executing the computer program 1330.

[0143] The computer device 1300 may include, but is not limited to, a processor 1310 and a memory 1320. Those skilled in the art will appreciate that Fig.13 This is only an example of the computer device 1300 and does not constitute a limitation on the computer device 1300 . The computer device 1300 may include more or fewer components than shown in the figure, or a combination of certain components, or different components. For example, it may also include input and output devices, network access devices, etc.

[0144] The processor 1310 may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or the processor may be any conventional processor, etc.

[0145] In some embodiments, the memory 1320 may be an internal storage unit of the computer device 1300, such as a hard disk or memory of the computer device 1300. In other embodiments, the memory 1320 may also be an external storage device of the computer device 1300, such as a plug-in hard disk, a smart media card (SMC), a secure digital (SD) card, a flash card, etc. equipped on the computer device 1200. Further, the memory 1220 may also include both an internal storage unit of the computer device 1200 and an external storage device. The memory 1220 is used to store an operating system, an application program, a boot loader (BootLoader), data, and other programs, such as the program code of the computer program. The memory 1320 may also be used to temporarily store data that has been output or is to be output.

[0146] It should be noted that the information interaction, execution process, etc. between the above-mentioned devices / units are based on the same concept as the method embodiment of the present application. Their specific functions and technical effects can be found in the method embodiment part and will not be repeated here.

[0147] The technicians in the relevant field can clearly understand that for the convenience and simplicity of description, only the division of the above-mentioned functional units and modules is used as an example for illustration. In practical applications, the above-mentioned function allocation can be completed by different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above. The functional units and modules in the embodiment can be integrated in a processing unit, or each unit can exist physically separately, or two or more units can be integrated in one unit. The above-mentioned integrated unit can be implemented in the form of hardware or in the form of software functional units. In addition, the specific names of the functional units and modules are only for the convenience of distinguishing each other, and are not used to limit the scope of protection of this application. The specific working process of the units and modules in the above-mentioned system can refer to the corresponding process in the aforementioned method embodiment, which will not be repeated here.

[0148] An embodiment of the present application further provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps in the above-mentioned method embodiments can be implemented.

[0149] An embodiment of the present application provides a computer program product. When the computer program product runs on a mobile terminal, the mobile terminal can implement the steps in the above-mentioned method embodiments when executing the computer program product.

[0150] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the present application implements all or part of the processes in the above-mentioned embodiment method, which can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a computer-readable storage medium, and the computer program can implement the steps of the above-mentioned various method embodiments when executed by the processor. Among them, the computer program includes computer program code, and the computer program code can be in source code form, object code form, executable file or some intermediate form. The computer-readable medium may at least include: any entity or device that can carry the computer program code to the device / terminal device, recording medium, computer memory, read-only memory (ROM), random access memory (RAM), electric carrier signal, telecommunication signal and software distribution medium. For example, a USB flash drive, a mobile hard disk, a disk or an optical disk.

[0151] In the above embodiments, the description of each embodiment has its own emphasis. For parts that are not described or recorded in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0152] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0153] In the embodiments provided in the present application, it should be understood that the disclosed devices / network equipment and methods can be implemented in other ways. For example, the device / network equipment embodiments described above are merely schematic. For example, the division of the modules or units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0154] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0155] The embodiments described above are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, a person skilled in the art should understand that the technical solutions described in the aforementioned embodiments may still be modified, or some of the technical features may be replaced by equivalents. Such modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present application, and should all be included in the protection scope of the present application.

Claims

1. A log data processing method, characterized in that: Applied to a log data processing system, the log data processing system includes a terminal device, a platform node, a service node and a download node, the network address of the terminal device is a non-fixed network address and stores log data, the platform node is connected to the terminal device in communication and stores the real-time network address of the terminal device, the service node is connected to the download node and the platform node in communication, and the log data processing method includes: In the case where there is a demand for log downloading, the downloading node sends a log downloading request to the service node, where the log downloading request indicates the log data to be downloaded and the terminal device where the log data is located; The service node sends a log upload request to the terminal device via the platform node based on the log download request; The terminal device uploads the target log data to the target server based on the log upload request, and feeds back a log upload event to the platform node, wherein the log upload event includes a download address of the target log data on the target server; The service node receives the log upload event sent by the platform node, and feeds back upload information to the download node based on the log upload event, wherein the upload information includes a download address of the target log data on the target server; The download node obtains the upload information fed back by the service node, and after the target log data is uploaded, downloads the target log data from the target server based on the download address.

2. The log data processing method according to any one of claims 1, characterized in that: The method further comprises: When receiving the log upload request, the terminal device generates a log reporting task adapted to the log upload request, and feeds back a task identifier of the log reporting task to the platform node; The platform node feeds back the task identifier to the download node via the service node; The download node obtains the upload information from the service node based on the task identifier.

3. The log data processing method according to claim 2, characterized in that: The log upload event also includes: the task identifier and the upload progress of the target log data, and the feedback of the log upload event to the platform node includes: The terminal device feeds back a log upload event to the platform node based on the upload progress of the target log data, so that the relevant node can obtain the upload progress of the target log data according to the task identifier, and the relevant node is directly or indirectly communicated with the platform node.

4. The log data processing method according to claim 1, characterized in that: The log upload event includes a task identifier of a log reporting task and an upload progress of the target log data, and the log reporting task is adapted to the log upload request; The step of sending a log upload request to the terminal device via the platform node further includes: The service node receives the task identifier sent by the platform node; The service node sends the task identifier to the download node; The business node receives the log upload event sent by the platform node, and then further includes: The service node updates and stores the log upload event associated with the task identifier based on the task identifier carried in the log upload event.

5. The log data processing method according to claim 4, characterized in that: The upload information also includes: information indicating whether the target log data is successfully uploaded; the download node obtains the upload information fed back by the service node, including: The download node periodically sends a query request carrying the task identifier to the service node; In response to the query request, the service node feeds back the upload information to the download node based on the log upload event associated with the task identifier.

6. The log data processing method according to any one of claims 1 to 5, characterized in that: The service node sends a log upload request to the terminal device via the platform node based on the log download request, including: The service node determines a target server from at least one server managed by the platform node; The service node generates a log upload request based on the log download request and the target server; The service node sends the log upload request to the terminal device via the platform node.

7. The log data processing method according to claim 6, characterized in that: The service node determines a target server from at least one server managed by the platform node, including: If the preset storage mode is default storage, the service node determines a server carrying a default identifier among at least one server managed by the platform node as a target server; If the preset storage mode is dynamic storage, the service node selects a target server from at least one server managed by the platform node based on an evaluation index, where the evaluation index is used to evaluate the status of the storage pool of the server.

8. A log data processing method, characterized in that: Applied to a terminal device, the network address of the terminal device is a non-fixed network address and log data is stored, and the log data processing method includes: Receiving a log upload request sent by a platform node, wherein the platform node stores the real-time network address of the terminal device; Based on the log upload request, the target log data is uploaded to the target server, and the log upload event is fed back to the relevant node via the platform node. The log upload event includes: the download address of the target log data on the target server, and the relevant node is indirectly or directly communicated with the platform node.

9. The log data processing method according to claim 8, characterized in that: The log upload event also includes a task identifier of the log reporting task and a log upload progress of the target log data, the log reporting task is adapted to the log upload request, and the feedback of the log upload event to the relevant node via the platform node includes: Obtain at least one preset progress feedback point; If the upload progress of the target log data reaches the progress feedback point, a corresponding log upload event is generated, and the corresponding log upload event is fed back to the relevant nodes via the platform node.

10. A log data processing method, characterized in that: Applied to a service node, the service node is respectively connected to a download node and a platform node, the platform node is connected to a terminal device and stores a real-time network address of the terminal device, the network address of the terminal device is a non-fixed network address and stores log data, and the log data processing method includes: Receiving a log download request sent by the download node, wherein the log download request indicates the log data to be downloaded and the terminal device where the log data is located; Based on the log download request, a log upload request is sent to the terminal device via the platform node, wherein the log upload request instructs the terminal device to upload target log data to a target server and feeds back a log upload event to the platform node; Receiving the log upload event sent by the platform node; Feedback upload information to the download node based on the log upload event, where the upload information includes a download address of the target log data on the target server.

11. The log data processing method according to claim 10, characterized in that: The feeding back the upload information to the download node based on the log upload event includes: Receiving a query request for upload information sent by the download node, the query request including a task identifier of a log reporting task, the log reporting task being adapted to the log upload request; Based on the query request, query the log upload event associated with the task identifier; Based on the queried log upload event, the upload information is fed back to the download node.

12. A log data processing method, characterized in that: Applied to a download node, the download node is connected to a service node in communication, the service node is connected to a platform node in communication, the platform node is connected to a terminal device in communication and stores a real-time network address of the terminal device, the network address of the terminal device is a non-fixed network address and stores log data, and the log data processing method includes: In the case of a log download demand, a log download request is sent to the business node, the log download request indicates the log data to be downloaded and the terminal device where the log data is located, and is used to trigger the business node to send a log upload request to the terminal device via the platform node, the log upload request instructs the terminal device to upload the target log data to the target server, and instructs the terminal device to feedback the log upload event to the platform node; Acquire upload information fed back by the service node based on the log upload event, wherein the upload information includes: a download address of the target log data on the target server; After the target log data is uploaded, the target log data is downloaded from the target server based on the download address.

13. The log data processing method according to claim 12, characterized in that: The sending of the log download request to the service node further includes: Receiving a task identifier sent by the service node, the task identifier is used to associate a log upload event of a log reporting task, and the log reporting task is adapted to the log upload request; The obtaining of the upload information fed back by the service node based on the log upload event also includes: A query request for the uploaded information is sent to the service node, wherein the query request includes the task identifier, and the query request is used to instruct the service node to feed back the uploaded information.

14. A log data processing system, characterized in that: The log data processing system includes a terminal device, a download node, a service node and a platform node; the network address of the terminal device is a non-fixed network address and stores log data, the platform node is connected to the terminal device in communication and stores the real-time network address of the terminal device, and the service node is connected to the download node and the platform node in communication, respectively; The download node is used to: when there is a log download demand, send a log download request to the service node, wherein the log download request indicates the log data to be downloaded and the terminal device where the log data is located; The service node is used to: send a log upload request to the terminal device via the platform node based on the log download request; The terminal device is used to: upload target log data to a target server based on the log upload request, and feedback a log upload event to the platform node, wherein the log upload event includes a download address of the target log data on the target server; The service node is further used to: receive the log upload event sent by the platform node, and feed back upload information to the download node based on the log upload event, wherein the upload information includes a download address of the target log data on the target server; The download node is further used to: obtain the upload information fed back by the service node, and after the target log data is uploaded, download the target log data from the target server based on the download address.

15. A computer device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the computer device is a terminal device, the processor implements the method according to claim 8 or 9 when executing the computer program; When the computer device is a service node, the processor implements the method according to claim 10 or 11 when executing the computer program; When the computer device is a download node, the processor implements the method according to claim 12 or 13 when executing the computer program.

Images