Digital object query method for distributed link tracking framework

Abstract

The invention discloses a digital object query method, device and equipment oriented to a distributed link tracking framework and a readable storage medium, and belongs to the field of distributed data networking, and the method comprises the steps: obtaining a data request message for digital object data; extracting a current request task and context link information from the data request message, and executing the current request task; according to the node information of the local network node and the task content of the current request task, updating context link information, and according to an execution result obtained by executing the current request task, updating the task content of the current request task; and jointly storing the updated context link information and the updated current request task as an updated data request message. Through the established data request message which has low code invasiveness and is convenient to query the link data structure, the problem that the link data tracking and debugging mode is complex in the distributed data networking information interaction process is solved.

Description

Technical Field

[0001] The present application belongs to the field of distributed digital networking, and specifically relates to a digital object query method, device, equipment and readable storage medium for a distributed link tracking framework. Background Art

[0002] In the context of modern information technology and big data applications, the Digital Internet, as a virtual data network based on the Internet, has achieved interconnection and interoperability of heterogeneous, heterogeneous, and sovereign data through standardized protocols, greatly promoting the use and value of data.

[0003] At present, the distributed digital object development framework is widely used in the digital networking system to realize flexible distributed digital object operations. In order to ensure the application of the distributed digital object development framework in complex heterogeneous data space, the distributed digital object development framework also needs to provide corresponding link tracking functions to ensure the record of data transmission.

[0004] However, the open source link tracking framework of the existing distributed digital object development framework generally does not support automatic processing in multi-threaded scenarios, which makes it difficult for developers to effectively track and debug in multi-threaded or asynchronous situations. At the same time, since the link tracking function requires additional data transmission, it also has a significant impact on the performance of the original service, making it difficult to meet the needs of large-scale traffic acceptance. Summary of the invention

[0005] The present application aims to provide a digital object query method, device, equipment and readable storage medium for a distributed link tracking framework, at least to solve the problem of complex link data tracking and debugging methods in the process of information interaction in a distributed digital network.

[0006] In a first aspect, an embodiment of the present application discloses a digital object query method for a distributed link tracking framework, which is applied to a local network node of a distributed network, including:

[0007] Acquire a data request message for digital object data; the data request message includes a currently requested task and context link information stored together; the currently requested task is used to characterize the task content for the digital object in the local network node; the context link information is used to characterize the task content and processing order for each execution task in the task group where the currently requested task is located in different network nodes of the distributed network, for the digital object;

[0008] Extracting the current request task and the context link information from the data request message, and executing the current request task;

[0009] updating the context link information according to the node information of the local network node and the task content of the current request task, and updating the task content of the current request task according to the execution result obtained by executing the current request task;

[0010] The updated context link information and the updated current request task are stored together as an updated data request message.

[0011] In a second aspect, the embodiment of the present application further discloses a digital object query device for a distributed link tracking framework, which is applied to a local network node of a distributed network, including:

[0012] A message acquisition module, used to acquire a data request message for digital object data; the data request message includes a currently requested task and context link information stored together; the currently requested task is used to characterize the task content for the digital object in the local network node; the context link information is used to characterize the task content and processing order for each execution task in the task group where the currently requested task is located in different network nodes of the distributed network.

[0013] An information extraction module, used to extract the current request task and the context link information from the data request message, and execute the current request task;

[0014] An information updating module, used to update the context link information according to the node information of the local network node and the task content of the current request task, and to update the task content of the current request task according to the execution result obtained by executing the current request task;

[0015] The message integration module is used to store the updated context link information and the updated current request task together as an updated data request message.

[0016] In a third aspect, an embodiment of the present application further discloses an electronic device, comprising a processor and a memory, wherein the memory stores programs or instructions that can be run on the processor, and when the program or instructions are executed by the processor, the steps of the method described in the first aspect are implemented.

[0017] In a fourth aspect, an embodiment of the present application further discloses a readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, the steps of the method described in the first aspect are implemented.

[0018] In summary, in the embodiment of the present application, based on storing the current request task and context link information together in the data request message, a comprehensive record of the digital object task content and processing order is achieved, ensuring that the context information of each execution task can be accurately transmitted and shared in different nodes of the distributed network, thereby improving the integrity and consistency of data tracking, and thus solving the problem of being difficult to effectively track and debug in multi-threaded or asynchronous situations in the prior art, ensuring the accuracy and integrity of data transmission records in complex heterogeneous data spaces; and then by extracting and updating the current request task and context link information from the data request message during the transmission of the data request message, ensuring the real-time update and synchronization of link information and task content, solving the problem of insufficient automatic processing capability of the link tracking function in the prior art in multi-threaded scenarios, ensuring the accuracy of task execution and the integrity of link information, maintaining the continuity and consistency of link information, and also reducing the impact on system performance, and improving the ability to undertake large-scale traffic. Therefore, based on the method of the embodiment of the present application, by establishing a data request message with low code intrusion and easy to query link data structure, the problem of complex link data tracking and debugging methods in the distributed digital network information interaction process is solved. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] In the attached picture:

[0020] Figure 1 It is a flowchart of the steps of a digital object query method for a distributed link tracking framework provided by an embodiment of the present application;

[0021] Figure 2 is a flowchart of the activation operation behavior provided by an embodiment of the present application;

[0022] Figure 3 This is a flowchart of the end operation behavior provided by the embodiment of the present application;

[0023] Figure 4 It is a flowchart of another method for querying digital objects in a distributed link tracking framework provided by an embodiment of the present application;

[0024] Figure 5 This is a flowchart of obtaining active operation behaviors in the current thread provided by an embodiment of the present application;

[0025] Figure 6 It is a flow chart of forwarding data requests in a digital networking switch according to command types;

[0026] Figure 7 It is a flow chart of data request forwarding in a digital networking switch according to gateway type;

[0027] Figure 8It is a flowchart of the steps of a digital object query method for a distributed link tracking framework provided for a data requesting network node;

[0028] Fig. 9 It is a block diagram of a digital object query device for a distributed link tracking framework provided by an embodiment of the present application;

[0029] Fig.10 is a block diagram of an electronic device according to an embodiment of the present application;

[0030] Fig.11 It is a block diagram of an electronic device of another embodiment provided by the embodiments of the present application. DETAILED DESCRIPTION

[0031] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0032] The terms "first", "second", etc. in the specification and claims of the present application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable under appropriate circumstances, so that the embodiments of the present application can be implemented in an order other than those illustrated or described here, and the objects distinguished by "first", "second", etc. are generally of one type, and the number of objects is not limited. For example, the first object can be one or more. In addition, "and / or" in the specification and claims represents at least one of the connected objects, and the character " / " generally indicates that the objects associated with each other are in an "or" relationship.

[0033] The Internet of Things is a logical network formed by data pragmatics as the first-order entity. Data pragmatics and data resources all come from various data spaces and are managed autonomously by each space. In each space, the Internet of Things infrastructure is accessed through the Internet of Things switch. Users can find the digital object in one or more data spaces through the identifier of the digital object. In this process, the Internet of Things application client will initiate a data request message (DataObjectInterfaceProtocol, DOIP) request for the digital object data. The request will pass through multiple Internet of Things gateways and Internet of Things switches, and it is possible to retrieve digital objects from data warehouses in multiple data spaces and merge data. Therefore, this link is quite complex, so we need a distributed link tracking framework designed specifically for the Internet of Things.

[0034] To this end, the corresponding solution should be able to meet the following functional requirements:

[0035] The data network link tracking framework needs to be able to track and record the call links between different components in the data network system, including cross-service, cross-process and cross-server calls. All DOIP requests and related function calls from the user request to the final user request return must be fully connected in series with the same link identifier, so that developers can view the DOIP call time, call parameters, response parameters and call sequence from the link tracking interface;

[0036] The link tracking framework not only records the entire call link process, but also integrates the log data required by developers into the link. In this way, developers can obtain more abundant call execution information in addition to basic information.

[0037] And meet the following non-functional requirements:

[0038] The link tracking function should be independent of the system developed by the developer. Excessive modification of the original system code will increase the complexity of system maintenance and upgrades, and may lead to performance degradation and instability. Therefore, the design of the link tracking function should be streamlined and decoupled from the original system to minimize the modification requirements of the system code.

[0039] The functions provided by the link tracking framework will not only be frequently called in various processes of the system, but will also directly affect the overall operating efficiency and stability of the system. Therefore, it is crucial to ensure the high performance of the link tracking framework itself, which will directly affect the system's monitoring quality, troubleshooting efficiency, and overall smoothness of operation.

[0040] Considering that the purpose of link lifecycle management in a distributed system is to manage the relationship between several operation behaviors (Span) generated during the operation of the system. The set of system calls with causal relationships belongs to a data class (Tracer) used to manage spans. The focus is to manage the causal relationship between different spans while minimizing the impact on the original system code. When several spans are carried out simultaneously in concurrent scenarios, it is necessary to find the parent span relationship for the newly created span in any thread. In existing link tracking solutions, thread local storage (ThreadLocalStorage) technology is widely used as a sharing solution for the lifecycle of calls in the link. When using ThreadLocalStorage to save the lifecycle variable (Scope) of the Span, a lifecycle variable manager (ScopeManager) only needs one local thread (ThreadLocal) to manage the lifecycle of the link call. This ensures that each thread has its own currently active Scope object instance. Therefore, the related operations of Span are performed in the way of obtaining the currently active Span, activating a Span, and closing a Span.

[0041] Therefore, based on the consideration of the above requirements, Figure 1 As shown, a digital object query method for a distributed link tracking framework provided in this embodiment is applied to a local network node of a distributed network.

[0042] The method may include the following steps:

[0043] Step 101: Obtain a data request message for digital object data.

[0044] Among them, the data request message includes the currently requested task and context link information stored together; the currently requested task is used to characterize the task content for the digital object in the local network node; the context link information is used to characterize the task content and processing order for the digital object for each execution task in the task group where the currently requested task is located in different network nodes of the distributed network.

[0045] In some embodiments of the present application, a data request message for digital object data is obtained. The data request message contains the current request task and context link information. The current request task is used to describe the specific operation content of the digital object on the local network node. The context link information is used to describe the content and processing order of each execution task in the task group where the current request task is located in different nodes of the distributed network. This information is stored together in the data request message to ensure that in a distributed environment, each node can accurately transmit and share the context information of the task, thereby achieving comprehensive tracking of the task execution process.

[0046] For example, in a digital networking system, a user initiates a digital object query request through a digital networking application client. The request is encapsulated as a data request message, which contains the current request task and context link information. The current request task may be "query the metadata of a digital object", and the context link information records the processing steps and sequence of the request in the previous node. For example, a data request message may contain the following information: Current request task: query the metadata of the digital object ID 12345; context link information: node A has been processed, and node B is processing. Then when the local network node receives the data request message, it will extract the current request task and context link information to prepare for subsequent task execution and link tracking.

[0047] Step 102: extract the current request task and context link information from the data request message, and execute the current request task.

[0048] In some embodiments of the present application, the current request task and context link information are extracted from the data request message, and the current request task is executed. The current request task contains the specific operation content that needs to be performed on the local network node, and the context link information records the processing steps and sequence of the task at each node in the distributed network. By extracting this information, the local network node can accurately understand the execution background of the current task and perform corresponding operations according to the task content, thereby ensuring the smooth execution of the task and the integrity of the link information.

[0049] For example, in a digital networking system, a local network node receives a data request message that contains the current request task and context link information. Assuming that the current request task is "query the metadata of the digital object with ID 12345", the context link information records the processing steps and sequence of the request in the previous node, such as "node A has been processed, node B is processing". Then, the local network node first extracts the current request task and context link information from the data request message. Then, based on the content of the current request task, the local network node performs a query operation to retrieve the metadata of the digital object with ID 12345 from the digital object repository. After executing the current request task, the local network node returns the result and updates the context link information to reflect the latest processing status. In this way, the link information during the entire task execution process can be kept complete and consistent.

[0050] like Figure 2 As shown in the figure, when a new operation behavior instance needs to be created to express the process executed by the current system, the following steps will be followed:

[0051] A1: Create a new operation behavior instance that carries information based on the current system context information.

[0052] A2: Create a new lifecycle variable instance through the lifecycle variable manager.

[0053] A3: Bind the new lifecycle variable instance and the new operation behavior instance together. At this time, the created lifecycle variable object will be responsible for managing the lifecycle of the operation behavior.

[0054] A4: Get the active lifecycle variable instance corresponding to the current thread from the thread local storage in the lifecycle variable manager.

[0055] A5: Set the active lifecycle variable instance as the parent lifecycle variable of the newly created lifecycle variable instance. At this time, when there are multiple layers of parent lifecycle variable instances, their existence is similar to a linked list.

[0056] A6: Store the new lifecycle variable object instance in the thread local storage of the lifecycle variable manager and return the newly activated operation behavior object.

[0057] In the subsequent process, the lifecycle variables in the lifecycle variable manager will manage the parent-child relationship between operation behaviors.

[0058] Correspondingly, such as Figure 3 As shown in the figure, when a certain part of the system program is executed, the distributed tracking system needs to end the corresponding operation behavior instance and report the link data to the tracking system backend. At this time, the following steps will be performed:

[0059] B1: Get the lifecycle variable object instance corresponding to the operation behavior.

[0060] B2: After obtaining, determine whether the active lifecycle variable of the current thread stored in the lifecycle variable manager that manages this lifecycle variable is itself. If the judgment result is no, execute the B3 process; if the judgment result is yes, execute the B4-B6 process:

[0061] B3: Report an error.

[0062] B4: Restore the parent lifecycle variables stored in the lifecycle variable manager to the thread local storage.

[0063] B5: Destroy the current life cycle variable to end the life cycle management of the current operation behavior.

[0064] B6: Report the link data of this operation behavior.

[0065] Step 103, updating the context link information according to the node information of the local network node and the task content of the current request task, and updating the task content of the current request task according to the execution result obtained by executing the current request task.

[0066] In some embodiments of the present application, the context link information will be updated based on the node information of the local network node and the task content of the current request task, and the task content of the current request task will be updated based on the execution result obtained by executing the current request task. The node information of the local network node includes the node's identification, location, processing capability, etc. The task content of the current request task is a specific operation instruction. After executing the current request task, the execution result needs to be recorded and the context link information needs to be updated to reflect the latest processing status. This process ensures the accuracy of task execution and the integrity of link information.

[0067] For example, in a digital networking system, the local network node successfully executes the current request task of "querying the metadata of the digital object ID 12345". Assume that the node information of the local network node is "node B" and the execution result is "the metadata of the digital object ID 12345 is {…}". Then, the local network node first updates the context link information based on the node information and the task content of the current request task. For example, the context link information is updated to "node A has been processed, node B has been processed". Then, according to the execution result obtained by executing the current request task, the task content of the current request task is updated. For example, the task content of the current request task is updated to "the metadata of the digital object ID 12345 has been queried". In this way, the real-time update and synchronization of the context link information and task content are ensured, so that subsequent nodes can accurately understand the execution background and latest status of the task, thereby improving the integrity and consistency of data tracking.

[0068] Step 104 : Store the updated context link information and the updated current request task together as an updated data request message.

[0069] In some embodiments of the present application, the updated context link information and the updated current request task are stored together as an updated data request message. After executing the current request task and updating the relevant information, the updated information needs to be repackaged into a new data request message. This step ensures that all nodes can obtain the latest link information and task content when processing tasks, thereby ensuring the continuity and consistency of task execution.

[0070] For example, in a digital networking system, the local network node "Node B" has successfully executed the task of "querying the metadata of the digital object ID 12345" and updated the context link information and the task content of the current request task. Assume that the updated context link information is "Node A has been processed, Node B has been processed", and the updated task content of the current request task is "The metadata of the digital object ID 12345 has been queried". The local network node repackages this updated information into a new data request message. The new data request message contains the following content: Updated context link information: Node A has been processed, Node B has been processed, updated current request task: The metadata of the digital object ID 12345 has been queried. By storing this information together as an updated data request message, it is ensured that in subsequent task processing, each node can obtain the latest task status and link information, thereby improving the integrity and consistency of data tracking.

[0071] In summary, in the embodiment of the present application, based on storing the current request task and context link information together in the data request message, a comprehensive record of the digital object task content and processing order is achieved, ensuring that the context information of each execution task can be accurately transmitted and shared in different nodes of the distributed network, thereby improving the integrity and consistency of data tracking, and thus solving the problem of being difficult to effectively track and debug in multi-threaded or asynchronous situations in the prior art, ensuring the accuracy and integrity of data transmission records in complex heterogeneous data spaces; and then by extracting and updating the current request task and context link information from the data request message during the transmission of the data request message, ensuring the real-time update and synchronization of link information and task content, solving the problem of insufficient automatic processing capability of the link tracking function in the prior art in multi-threaded scenarios, ensuring the accuracy of task execution and the integrity of link information, maintaining the continuity and consistency of link information, and also reducing the impact on system performance, and improving the ability to undertake large-scale traffic. Therefore, based on the method of the embodiment of the present application, by establishing a data request message with low code intrusion and easy to query link data structure, the problem of complex link data tracking and debugging methods in the distributed digital network information interaction process is solved.

[0072] Figure 4 Another digital object query method for a distributed link tracking framework provided in an embodiment of the application is applied to a local network node of a distributed network. The method may include the following steps:

[0073] Step 201: Obtain a data request message for digital object data.

[0074] Among them, the data request message includes the currently requested task and context link information stored together; the currently requested task is used to characterize the task content for the digital object in the local network node; the context link information is used to characterize the task content and processing order for the digital object for each execution task in the task group where the currently requested task is located in different network nodes of the distributed network.

[0075] The method shown in this step has been explained in step 101 and will not be repeated here.

[0076] Step 202: extract the current request task and context link information from the data request message, and execute the current request task.

[0077] The method shown in this step has been explained in step 102 and will not be repeated here.

[0078] Step 203, updating the context link information according to the node information of the local network node and the task content of the current request task, and updating the task content of the current request task according to the execution result obtained by executing the current request task.

[0079] The method shown in this step has been explained in step 103 and will not be repeated here.

[0080] Optionally, in order to update the context link information according to the node information of the local network node and the task content of the current requested task, step 203 includes the following sub-steps:

[0081] Sub-step 2031, determining the node number of the local network node according to the node information of the local network node, and determining the task type number corresponding to the task content of the current request task according to the current request task.

[0082] In some embodiments of the present application, in order to further simplify the data complexity of the context link information, the node number of the local network node is determined based on the node information of the local network node, and the task type number corresponding to the task content of the current request task is determined based on the current request task. The node number is an identifier used to uniquely identify the local network node, and is usually assigned by the system when the node is initialized. The task type number is an identifier used to identify the type of the currently requested task, which is determined based on the task content. By determining the node number and the task type number, basic data can be provided for subsequent context link information updates.

[0083] For example, in a digital networking system, the local network node "Node B" receives a data request message, and the current request task is "query the metadata of the digital object ID 12345". First, the system determines the node number of the local network node based on the node information, for example, the node number of "Node B" is "002". Next, the system determines the task type number based on the task content of the current request task. Assume that the task type number of the "query digital object metadata" task is "01". Therefore, the task type number of the current request task is "01". In this way, the system determines the node number "002" of the local network node and the task type number "01" of the current request task. These numbers will be used for subsequent context link information updates to ensure that the link information during task execution is accurate and complete.

[0084] Sub-step 2032, concatenate the node number and the task type number to obtain context link update data.

[0085] In some embodiments of the present application, the node number and the task type number are spliced ​​to obtain context link update data. The node number and the task type number respectively identify the type of the local network node and the current request task. By splicing these two numbers together, a unique context link update data can be generated to record the execution of the current request task in the local network node. This splicing operation ensures the uniqueness and traceability of the link information, and provides a basis for subsequent link information updates.

[0086] For example, in a digital networking system, the local network node "Node B" has determined the node number as "002", and the task type number of the current request task is "01". In order to generate context link update data, the system concatenates the node number "002" and the task type number "01". Then the concatenated context link update data is "00201". This data indicates that a request task with a task type of "query digital object metadata" (number 01) was executed on Node B (number 002). In this way, the system generates unique context link update data for recording and tracking the execution of the current request task.

[0087] Sub-step 2033 , taking the context link information as a data sequence and taking the context link update data as an added item of the data sequence, and adding them to the context link information, so as to obtain updated context link information.

[0088] In some embodiments of the present application, the context link information is taken as a data sequence, and the context link update data is taken as an addition to the data sequence, and added to the context link information to obtain updated context link information. The context link information records the processing steps and sequence of each node in the distributed network. By adding the context link update data to the context link information, it can be ensured that the processing status of each node is accurately recorded, thereby achieving comprehensive tracking and monitoring of the task execution process.

[0089] For example, in a digital networking system, the local network node "Node B" has generated the context link update data "002-01", indicating that a request task with a task type of "query digital object metadata" has been executed on Node B. Assume that the current context link information is "00100", indicating that a task with a task type of "initialization request" has been executed on Node A before. Then in order to update the context link information, the system adds the context link update data "00201" as an addition to the data sequence to the existing context link information "00100". The updated context link information is "0010000201". In this way, the system records the processing status of each node in the context link information to ensure the integrity and consistency of the task execution process. In this way, when subsequent nodes receive the updated context link information, they can accurately understand the execution background and latest status of the task, thereby improving the integrity and consistency of data tracking.

[0090] Optionally, when the task type of the current request task is a local processing task, in order to update the task content of the current request task according to the execution result obtained by executing the current request task, step 203 includes the following sub-steps:

[0091] Sub-step 2034, based on the current request task, determine the task group corresponding to the current request task, and search for the subsequent request task of the current request task from the task group.

[0092] In some embodiments of the present application, a task group corresponding to the current request task will be determined based on the current request task, and a subsequent request task of the current request task will be found from the task group. A task group refers to a collection of multiple related request tasks in a distributed network, and these tasks are executed in sequence in a certain order. A subsequent request task refers to a task that needs to be executed immediately after the current request task is completed. By determining the task group and finding the subsequent request task, the continuous execution of the task and the integrity of the link information can be ensured.

[0093] For example, in a digital networking system, the local network node "Node B" is processing a data request message, and the current request task is "querying metadata for digital object ID 12345". The system first determines that the task belongs to the "digital object query" task group based on the current request task. The task group contains multiple related request tasks, such as "querying metadata", "obtaining data content", "verifying data integrity", etc. The system then searches the task group for the successor request task of the current request task. Assume that in the task group, the successor request task of the current request task is "obtaining data content for digital object ID 12345". In this way, the system determines the successor request task of the current request task, providing a basis for subsequent task execution and link information update.

[0094] Sub-step 2035, when a subsequent request task is found, the task content of the subsequent request task is updated to the new current request task.

[0095] In some embodiments of the present application, when a subsequent request task is found, the task content of the subsequent request task is updated to the new current request task. The subsequent request task refers to the task that needs to be executed immediately after the current request task is completed. By updating the task content of the subsequent request task to the new current request task, the continuous execution of the task and the integrity of the link information can be ensured, thereby achieving comprehensive tracking and monitoring of the task execution process.

[0096] For example, in the digital networking system, the local network node "Node B" has completed the current request task "query the metadata of the digital object ID 12345" and found the subsequent request task "obtain the data content of the digital object ID 12345" in the task group. The system updates the task content of the subsequent request task to the new current request task. Specifically, the content of the new current request task is "obtain the data content of the digital object ID 12345". In this way, the system ensures the continuous execution of the task, so that the subsequent task processing can proceed smoothly and the link information can be kept complete and consistent.

[0097] Sub-step 2036, when the subsequent request task cannot be found, the preset stop task is updated to the new current request task.

[0098] In some embodiments of the present application, in contrast to sub-step 2035, the preset stop task will be updated to a new current request task when the subsequent request task cannot be found. The preset stop task refers to the system default end task when there is no subsequent request task in the task group. By updating the preset stop task to the new current request task, the integrity of the task execution process and the continuity of the link information can be ensured, and the system can correctly end the execution of the current task group even in the absence of a subsequent request task.

[0099] For example, in a digital networking system, the local network node "Node B" has completed the current request task "Query metadata of digital object ID 12345" and tries to find a subsequent request task in the task group. However, the system finds that there is no subsequent request task in the task group. In this case, the system updates the preset stop task to the new current request task. The preset stop task may be "End task group execution and record log." Specifically, the content of the new current request task is "End task group execution and record log." In this way, the system ensures the integrity of the task execution process, and even in the absence of a subsequent request task, the system can correctly end the execution of the current task group and record relevant link information.

[0100] like Figure 5 As shown, in the specific execution process of step 2034 to step 2036, it is necessary to obtain the active Span of the current thread. The following steps will be performed:

[0101] C1: Get the lifecycle variable corresponding to the current thread through the thread local storage in the lifecycle variable manager;

[0102] C2: If the obtained lifecycle variable is empty, an empty operation behavior is returned;

[0103] C3: If the obtained lifecycle variable is not empty, the bound operation behavior is obtained from the lifecycle variable;

[0104] C4: Returns the obtained operation behavior as an instance.

[0105] Step 204 : Store the updated context link information and the updated current request task together as an updated data request message.

[0106] The method shown in this step has been described in step 104 and will not be repeated here.

[0107] Step 205: Send the execution result obtained by executing the current requested task as a task log to the log management device.

[0108] The log management device records the execution result, the current request task corresponding to the execution result, and the corresponding relationship between the task groups to which the current request task belongs.

[0109] In some embodiments of the present application, the execution result obtained by executing the current request task will be sent to the log management device as a task log. The log management device is responsible for recording the corresponding relationship between the execution result, the current request task and the task group where the current request task is located. This process ensures that the detailed information of the task execution is accurately recorded and stored, which is convenient for subsequent query and analysis. By sending the task log to the log management device, it is possible to achieve comprehensive monitoring and tracking of the task execution process, thereby improving the observability and debugging efficiency of the system.

[0110] For example, in a digital networking system, the local network node "node B" successfully executes the task of "querying the metadata of the digital object ID 12345" and obtains the execution result. Assume that the execution result is "the metadata of the digital object ID 12345 is {...}". Then the local network node sends the execution result as a task log to the log management device. The task log contains the following information: execution result: the metadata of the digital object ID 12345 is {...}, the current request task: query the metadata of the digital object ID 12345, the task group where the current request task is located: node A has been processed, node B has been processed. Then the log management device will record this information after receiving the task log, and establish a corresponding relationship between the execution result, the current request task and the task group. In this way, the system administrator can query the execution details and link information of each task through the log management device, thereby improving the observability and debugging efficiency of the system. In some embodiments of the present application, special tag information (Tag) information can also be added to the log information to further help users query the log.

[0111] Optionally, when the current request task of the updated data request message is a forwarding task, the embodiment of the present application further provides the following additional steps:

[0112] Step 206: In the distributed network, determine a target network node corresponding to the updated data request message, and send the updated data request message to the target network node.

[0113] The target network node is a network node other than the local network node in the distributed network.

[0114] In some embodiments of the present application, a target network node corresponding to the updated data request message is determined in the distributed network, and the updated data request message is sent to the target network node. The target network node is a network node other than the local network node in the distributed network. This step is applicable to the case where the current request task is a forwarding task. By determining the target network node and sending the updated data request message to the node, it is ensured that the task can continue to be executed in the distributed network, thereby achieving complete processing of the task and continuity of link information.

[0115] For example, in a digital networking system, after the local network node "Node B" completes the current request task, it determines that the current request task is a forwarding task. Assume that the updated data request message contains the following information: updated context link information: Node A has been processed, Node B has been processed, updated current request task: forward the metadata request for the digital object ID 12345, the local network node "Node B" needs to send the updated data request message to the target network node "Node C". First, Node B determines that the target network node is "Node C" based on the routing information of the distributed network. Then, Node B sends the updated data request message to Node C. Then, after Node C receives the updated data request message, it continues to process the request to ensure the continuous execution of the task in the distributed network. In this way, the complete processing of the task and the continuity of the link information are ensured, and the integrity and consistency of data tracking are improved.

[0116] Optionally, in the case where the local network node is not directly connected to the target network node, in order to send the updated data request message to the target network node, step 206 includes the following sub-steps:

[0117] Sub-step 2061, determining a target data exchange network node in the distributed network.

[0118] The target data exchange network node is a data exchange network node in the distributed network that is connected to the local network node and the target network node respectively.

[0119] In some embodiments of the present application, a target data exchange network node is determined in a distributed network. The target data exchange network node refers to a data exchange network node connected to a local network node and a target network node in a distributed network. When the local network node is not directly connected to the target network node, by determining the target data exchange network node, the transit and forwarding of the data request message can be achieved, thereby ensuring that the data request message can smoothly reach the target network node.

[0120] For example, in a data networking system, the local network node "Node A" needs to send an updated data request message to the target network node "Node C". Since Node A is not directly connected to Node C, the system needs to determine a target data exchange network node to transfer the message. Then the system first searches the distributed network for a data exchange network node that is connected to both Node A and Node C. Suppose the system finds a data exchange network node "Exchange Node B", which is connected to both Node A and Node C. In this way, the system determines the target data exchange network node "Exchange Node B" for transferring and forwarding the updated data request message. In this way, it ensures that the data request message can be smoothly transmitted from the local network node A to the target network node C, thereby improving the reliability and integrity of data transmission.

[0121] like Figure 6 As shown, in some embodiments of the present application, when the data exchange network node is a data network switch, it will be responsible for forwarding data requests between different data spaces.

[0122] In the process of interaction between the data networking switch and the data space, in order to ensure that the complete link of a request will not be interrupted in the switch application, after receiving the request, the specific operation will be carried out according to the following process:

[0123] M1: Submit the request to the switch processing module (SwitchHander) to determine whether the request is a switch configuration operation;

[0124] Next, if the request is a switch configuration operation, steps M2 to M5 are executed to create an operation behavior according to the corresponding setting operation and end the operation behavior after execution; if the request is not a switch configuration command, steps M6 to M10 are executed to use the corresponding DOIP request client to process the request:

[0125] M2: Determine the type of configuration operation;

[0126] M3: Create configuration operations according to request type;

[0127] M4: Execute the corresponding configuration operation;

[0128] M5: End the configuration operation to return the result;

[0129] M6: Request to be transferred to the digital object processor;

[0130] M7: Determine which type of interactive client the request should be given to;

[0131] M8: Create a corresponding handover operation according to the judgment result of step M7;

[0132] M9: Execute the created transfer operation;

[0133] M10: End the handover operation to return the result.

[0134] M3: If the request is not a switch configuration command, the request will be handed over to the Digital Object Handler (DOHandler) for processing, and then it will be determined which type of interactive client the request needs to be given to, and according to its interaction type, the corresponding switch function (SwitchFunction) will be used.

[0135] like Figure 7 As shown, in some embodiments of the present application, the gateway application divides the traffic types into three types, and performs specific operations according to the following processes according to the three different situations:

[0136] S1: When the request is management traffic, it does not need to be forwarded and only needs local operation;

[0137] S2: When the traffic received by the gateway application is the internal traffic of the data space, there is no need to forward the request to the switch. The address of the target data exchange network node can be obtained directly through the identity resolution system of the space and sent directly;

[0138] S3: When the traffic received by the gateway application is not the internal traffic of the data space, it is necessary to send the traffic to the data exchange network node bound to the corresponding gateway. This data exchange network node is responsible for finding the address of the target data exchange network node to forward the traffic.

[0139] Sub-step 2062, sending the updated data request message to the target switching network node, so that the target switching network node forwards the updated data request message to the target network node.

[0140] In some embodiments of the present application, the updated data request message is sent to the target switching network node so that the target switching network node forwards the updated data request message to the target network node. The target switching network node plays the role of transferring and forwarding data request messages in the distributed network. When the local network node is not directly connected to the target network node, the data request message can be transferred through the target switching network node to ensure that the data request message can smoothly reach the target network node, thereby achieving complete processing of the task and continuity of link information.

[0141] For example, in a data networking system, the local network node "Node A" needs to send an updated data request message to the target network node "Node C". Since Node A is not directly connected to Node C, the system has determined that the target data exchange network node is "Exchange Node B". Node A sends the updated data request message to Exchange Node B. Specifically, Node A transmits the data request message to the address of Exchange Node B through the network protocol. After receiving the data request message, Exchange Node B forwards the message to the target network node "Node C" according to its internal routing rules. In this way, even if the two are not directly connected, it ensures that the data request message can be smoothly transmitted from the local network node A to the target network node C.

[0142] In one embodiment of the present application, when the local network node is a data requesting network node, such as Figure 8 As shown, the digital object query method for the distributed link tracking framework provided in the embodiment of the present application can also be performed according to the following steps:

[0143] Step 301 , in response to a first execution command for a request task in a task group, determining the request task corresponding to the first execution command as a current request task.

[0144] In some embodiments of the present application, the data requesting network node will respond to the first execution command of the request task in the task group and determine the request task corresponding to the first execution command as the current request task. In a distributed network, the request task in the task group may contain multiple execution commands. The first execution command refers to the first command executed in the task group. By determining the request task corresponding to the first execution command as the current request task, the execution order of the tasks and the accuracy of the context link information can be ensured, thereby providing a basis for subsequent task execution and link tracking.

[0145] For example, in a digital networking system, a user initiates a digital object query task containing multiple steps at a data request network node. Assume that the first execution command in the task group is "query the metadata of the digital object with ID 12345". When the local network node receives the execution command, the system determines the request task corresponding to the execution command as the current request task. Specifically, the local network node recognizes that this is the first execution command in the task group and marks it as the current request task. The content of the current request task is "query the metadata of the digital object with ID 12345", and this task will serve as the starting point for subsequent task execution and link tracking.

[0146] Step 302: Add the target code segment to the determined current request task, so as to use the current request task with the target code segment as a data request message.

[0147] The target code segment is used to store context link information.

[0148] In some embodiments of the present application, the data requesting network node will add a target code segment to the determined current requesting task, so as to use the current requesting task with the target code segment as a data requesting message. The target code segment is used to store context link information, which includes the processing steps and sequence of the task at each node in the distributed network. By adding the target code segment to the current requesting task, it is possible to ensure that the context link information is accurately recorded and transmitted during the task execution process, thereby achieving comprehensive tracking and monitoring of the task execution process.

[0149] For example, in a digital networking system, the local network node "Node A" determines that the current request task is "querying the metadata of the digital object ID 12345". In order to ensure that the context link information can be accurately recorded and transmitted during the task execution process, Node A adds a target code segment to the current request task. The target code segment is used to store context link information, for example: current node: Node A, task content: query the metadata of the digital object ID 12345, context link information: empty (because this is the first execution command); then by adding the target code segment, Node A sends the current request task with the target code segment as a data request message. In this way, when subsequent nodes receive the data request message, they can extract and update the context link information from the target code segment, and continue to execute tasks based on this information, thereby ensuring the integrity and consistency of the task execution process.

[0150] Step 303: Obtain a data request message for the digital object data.

[0151] Among them, the data request message includes the currently requested task and context link information stored together; the currently requested task is used to characterize the task content for the digital object in the local network node; the context link information is used to characterize the task content and processing order for the digital object for each execution task in the task group where the currently requested task is located in different network nodes of the distributed network.

[0152] The method shown in this step has been explained in step 101 and will not be repeated here.

[0153] Step 304: extract the current request task and context link information from the data request message, and execute the current request task.

[0154] The method shown in this step has been explained in step 102 and will not be repeated here.

[0155] Step 305, updating the context link information according to the node information of the local network node and the task content of the current request task, and updating the task content of the current request task according to the execution result obtained by executing the current request task.

[0156] The method shown in this step has been explained in step 103 and will not be repeated here.

[0157] Step 306: Store the updated context link information and the updated current request task together as an updated data request message.

[0158] The method shown in this step has been described in step 104 and will not be repeated here.

[0159] In summary, in the embodiment of the present application, based on storing the current request task and context link information together in the data request message, a comprehensive record of the digital object task content and processing order is achieved, ensuring that the context information of each execution task can be accurately transmitted and shared in different nodes of the distributed network, thereby improving the integrity and consistency of data tracking, and thus solving the problem of being difficult to effectively track and debug in multi-threaded or asynchronous situations in the prior art, ensuring the accuracy and integrity of data transmission records in complex heterogeneous data spaces; and then by extracting and updating the current request task and context link information from the data request message during the transmission of the data request message, ensuring the real-time update and synchronization of link information and task content, solving the problem of insufficient automatic processing capability of the link tracking function in the prior art in multi-threaded scenarios, ensuring the accuracy of task execution and the integrity of link information, maintaining the continuity and consistency of link information, and also reducing the impact on system performance, and improving the ability to undertake large-scale traffic. Therefore, based on the method of the embodiment of the present application, by establishing a data request message with low code intrusion and easy to query link data structure, the problem of complex link data tracking and debugging methods in the distributed digital network information interaction process is solved.

[0160] refer to Fig. 9 , which shows a digital object query device 40 for a distributed link tracking framework provided by an embodiment of the present application, applied to a local network node of a distributed network, including:

[0161] The message acquisition module 401 is used to acquire a data request message for digital object data; the data request message includes a currently requested task and context link information stored together; the currently requested task is used to represent the task content for the digital object in the local network node; the context link information is used to represent the task content and processing order of each execution task in the task group where the currently requested task is located in different network nodes of the distributed network for the digital object;

[0162] The information extraction module 402 is used to extract the current request task and context link information from the data request message and execute the current request task;

[0163] The information updating module 403 is used to update the context link information according to the node information of the local network node and the task content of the current request task, and to update the task content of the current request task according to the execution result obtained by executing the current request task;

[0164] The message integration module 404 is used to store the updated context link information and the updated current request task together as an updated data request message.

[0165] Optionally, in the case where the local network node is a data requesting network node, the device 40 further includes:

[0166] An initial command acquisition module, configured to respond to a first execution command for a request task in the task group and determine the request task corresponding to the first execution command as a current request task;

[0167] The message generation module is used to add a target code segment to the determined current request task so as to use the current request task with the target code segment as a data request message; the target code segment is used to store context link information.

[0168] Optionally, the information updating module 403 includes:

[0169] The number confirmation submodule is used to determine the node number of the local network node according to the node information of the local network node, and determine the task type number corresponding to the task content of the current request task according to the current request task;

[0170] A number concatenation submodule is used to concatenate the node number with the task type number to obtain context link update data;

[0171] The information injection submodule is used to take the context link information as a data sequence and the context link update data as an added item of the data sequence, and add them to the context link information to obtain the updated context link information.

[0172] Optionally, when the task type of the current request task is a local processing task, the information updating module 403 includes:

[0173] The task confirmation submodule is used to determine the task group corresponding to the current request task according to the current request task, and to find the subsequent request task of the current request task from the task group;

[0174] The update submodule is used to update the task content of the subsequent request task to the new current request task when the subsequent request task is found;

[0175] The termination submodule is used to update the preset stop task to the new current request task when the subsequent request task cannot be found.

[0176] Optionally, when the current request task of the updated data request message is a forwarding task, the device 40 further includes:

[0177] The message sending module is used to determine the target network node corresponding to the updated data request message in the distributed network, and send the updated data request message to the target network node; the target network node is a network node other than the local network node in the distributed network.

[0178] Optionally, when the local network node is not directly connected to the target network node, the message sending module includes:

[0179] The target node confirmation submodule is used to determine the target data exchange network node in the distributed network; the target data exchange network node is a data exchange network node in the distributed network that is connected to the local network node and the target network node respectively;

[0180] The message sending submodule is used to send the updated data request message to the target switching network node, so that the target switching network node forwards the updated data request message to the target network node.

[0181] In summary, in the embodiment of the present application, based on storing the current request task and context link information together in the data request message, a comprehensive record of the digital object task content and processing order is achieved, ensuring that the context information of each execution task can be accurately transmitted and shared in different nodes of the distributed network, thereby improving the integrity and consistency of data tracking, and thus solving the problem of being difficult to effectively track and debug in multi-threaded or asynchronous situations in the prior art, ensuring the accuracy and integrity of data transmission records in complex heterogeneous data spaces; and then by extracting and updating the current request task and context link information from the data request message during the transmission of the data request message, ensuring the real-time update and synchronization of link information and task content, solving the problem of insufficient automatic processing capability of the link tracking function in the prior art in multi-threaded scenarios, ensuring the accuracy of task execution and the integrity of link information, maintaining the continuity and consistency of link information, and also reducing the impact on system performance, and improving the ability to undertake large-scale traffic. Therefore, based on the method of the embodiment of the present application, by establishing a data request message with low code intrusion and easy to query link data structure, the problem of complex link data tracking and debugging methods in the distributed digital network information interaction process is solved.

[0182] Reference Fig.10 , the electronic device 500 may include one or more of the following components: a processing component 502 , a memory 504 , a power component 506 , a multimedia component 508 , an audio component 510 , an input / output (I / O) interface 512 , a sensor component 514 , and a communication component 516 .

[0183] The processing component 502 generally controls the overall operation of the electronic device 500, such as operations associated with display, phone calls, data communications, camera operations, and recording operations. The processing component 502 may include one or more processors 520 to execute instructions to complete all or part of the steps of the above-mentioned method. In addition, the processing component 502 may include one or more modules to facilitate the interaction between the processing component 502 and other components. For example, the processing component 502 may include a multimedia module to facilitate the interaction between the multimedia component 508 and the processing component 502.

[0184] The memory 504 is used to store various types of data to support the operation of the electronic device 500. Examples of such data include instructions for any application or method operating on the electronic device 500, contact data, phone book data, messages, pictures, multimedia, etc. The memory 504 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk or optical disk.

[0185] The power supply component 506 provides power to the various components of the electronic device 500. The power supply component 506 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power to the electronic device 500.

[0186] The multimedia component 508 includes an interface that provides an output interface between the electronic device 500 and the user. In some embodiments, the interface may include a liquid crystal display (LCD) and a touch panel (TP). If the interface includes a touch panel, the interface may be implemented as a touch screen to receive input signals from the user. The touch panel includes one or more touch sensors to sense touch, slide, and gestures on the touch panel. The touch sensor may not only sense the boundaries of the touch or slide action, but also detect the duration and pressure associated with the touch or slide operation. In some embodiments, the multimedia component 508 includes a front camera and / or a rear camera. When the electronic device 500 is in an operating mode, such as a shooting mode or a multimedia mode, the front camera and / or the rear camera may receive external multimedia data. Each front camera and rear camera may be a fixed optical lens system or have a focal length and optical zoom capability.

[0187] The audio component 510 is used to output and / or input audio signals. For example, the audio component 510 includes a microphone (MIC), and when the electronic device 500 is in an operating mode, such as a call mode, a recording mode, and a voice recognition mode, the microphone is used to receive an external audio signal. The received audio signal can be further stored in the memory 504 or sent via the communication component 516. In some embodiments, the audio component 510 also includes a speaker for outputting audio signals.

[0188] The input / output I / O interface 512 provides an interface between the processing component 502 and the peripheral interface module, which may be a keyboard, a click wheel, buttons, etc. These buttons may include but are not limited to: a home button, a volume button, a start button, and a lock button.

[0189] The sensor assembly 514 includes one or more sensors for providing various aspects of status assessment for the electronic device 500. For example, the sensor assembly 514 can detect the open / closed state of the electronic device 500, the relative positioning of components, such as the display and keypad of the electronic device 500, and the sensor assembly 514 can also detect the position change of the electronic device 500 or a component of the electronic device 500, the presence or absence of user contact with the electronic device 500, the orientation or acceleration / deceleration of the electronic device 500, and the temperature change of the electronic device 500. The sensor assembly 514 may include a proximity sensor configured to detect the presence of nearby objects without any physical contact. The sensor assembly 514 may also include an optical sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, the sensor assembly 514 may also include an accelerometer, a gyroscope sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.

[0190] The communication component 516 is used to facilitate wired or wireless communication between the electronic device 500 and other devices. The electronic device 500 can access a wireless network based on a communication standard, such as WiFi, a carrier network (such as 2G, 3G, 4G or 5G), or a combination thereof. In an exemplary embodiment, the communication component 516 receives a broadcast signal or broadcast-related information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communication component 516 also includes a near field communication (NFC) module to facilitate short-range communication. For example, the NFC module can be implemented based on radio frequency identification (RFID) technology, infrared data association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology and other technologies.

[0191] In an exemplary embodiment, the electronic device 500 may be implemented by one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic components to implement the methods provided in the embodiments of the present application.

[0192] In an exemplary embodiment, a non-transitory computer-readable storage medium including instructions is also provided, such as a memory 504 including instructions, and the instructions can be executed by a processor 520 of an electronic device 500 to perform the above method. For example, the non-transitory storage medium can be a ROM, a random access memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, etc.

[0193] Fig.11600 is a block diagram of an electronic device 600 according to another embodiment of the present invention. For example, the electronic device 600 may be provided as a server. Fig.11 , the electronic device 600 includes a processing component 622, which further includes one or more processors, and a memory resource represented by a memory 632, for storing instructions that can be executed by the processing component 622, such as an application. The application stored in the memory 632 may include one or more modules, each corresponding to a set of instructions. In addition, the processing component 622 is configured to execute instructions to perform the method provided in the embodiment of the present application.

[0194] The electronic device 600 may also include a power supply component 626 configured to perform power management of the electronic device 600, a wired or wireless network interface 650 configured to connect the electronic device 600 to a network, and an input / output (I / O) interface 658. The electronic device 600 may operate based on an operating system stored in the memory 632, such as Windows Server TM, Mac OS X TM, Unix TM, Linux TM, FreeBSD TM or the like.

[0195] Those skilled in the art will readily appreciate other embodiments of the present application after considering the specification and practicing the application disclosed herein. The present application is intended to cover any modification, use or adaptation of the present application, which follows the general principles of the present application and includes common knowledge or customary techniques in the art that are not disclosed in the present disclosure. The specification and examples are intended to be exemplary only, and the true scope and spirit of the present application are indicated by the following claims.

[0196] It should be understood that the present application is not limited to the precise structures that have been described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present application is limited only by the appended claims.

Claims

1. A digital object query method for a distributed link tracking framework, applied to a local network node of a distributed network, characterized in that: include: Obtaining a data request message for digital object data; The data request message includes the currently requested task and context link information stored together; The current request task is used to represent the task content for the digital object at the local network node; The context link information is used to characterize the task content and processing order of each execution task in the task group where the current request task is located in different network nodes of the distributed network, on the digital object; Extracting the current request task and the context link information from the data request message, and executing the current request task; updating the context link information according to the node information of the local network node and the task content of the current request task, and updating the task content of the current request task according to the execution result obtained by executing the current request task; The updated context link information and the updated current request task are stored together as an updated data request message.

2. The method according to claim 1, characterized in that In the case where the local network node is a data requesting network node, before obtaining the data requesting message for the digital object data, the method further includes: In response to a first execution command for a request task in a task group, determining the request task corresponding to the first execution command as the current request task; A target code segment is added to the determined current request task, so that the current request task with the target code segment is used as the data request message; the target code segment is used to store context link information.

3. The method according to claim 1, characterized in that The updating of the context link information according to the node information of the local network node and the task content of the current requested task includes: Determine the node number of the local network node according to the node information of the local network node, and determine the task type number corresponding to the task content of the current request task according to the current request task; Concatenate the node number with the task type number to obtain context link update data; The context link information is taken as a data sequence, and the context link update data is taken as an additional item of the data sequence and added to the context link information to obtain updated context link information.

4. The method according to claim 1, characterized in that In the case where the task type of the current request task is a local processing task, updating the task content of the current request task according to the execution result obtained by executing the current request task includes: According to the current request task, determine the task group corresponding to the current request task, and search for the subsequent request task of the current request task from the task group; When the subsequent request task is found, the task content of the subsequent request task is updated to the new current request task; In the case that the subsequent request task cannot be found, the preset stop task is updated to the new current request task.

5. The method according to claim 1, characterized in that In the case where the current request task of the updated data request message is a forwarding task, the method further includes: In the distributed network, a target network node corresponding to the updated data request message is determined, and the updated data request message is sent to the target network node; the target network node is a network node other than the local network node in the distributed network.

6. The method according to claim 5, characterized in that In a case where the local network node is not directly connected to the target network node, sending the updated data request message to the target network node includes: Determining a target data exchange network node in the distributed network; the target data exchange network node is a data exchange network node in the distributed network that is connected to the local network node and the target network node respectively; The updated data request message is sent to the target switching network node, so that the target switching network node forwards the updated data request message to the target network node.

7. The method according to claim 1, characterized in that The method further comprises: The execution result obtained by executing the current request task is sent to the log management device as a task log; the log management device records the execution result, the current request task corresponding to the execution result, and the corresponding relationship between the task group to which the current request task belongs.

8. A digital object query device for a distributed link tracking framework, characterized in that: Local network nodes for distributed networks, including: A message acquisition module, used to acquire a data request message for digital object data; the data request message includes a currently requested task and context link information stored together; the currently requested task is used to characterize the task content for the digital object in the local network node; the context link information is used to characterize the task content and processing order for each execution task in the task group where the currently requested task is located in different network nodes of the distributed network. An information extraction module, used to extract the current request task and the context link information from the data request message, and execute the current request task; An information updating module, used to update the context link information according to the node information of the local network node and the task content of the current request task, and to update the task content of the current request task according to the execution result obtained by executing the current request task; The message integration module is used to store the updated context link information and the updated current request task together as an updated data request message.

9. An electronic device, characterized in that: include: A processor, a memory for storing instructions executable by the processor; The processor is configured to execute the instructions to implement the method according to any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that: When the instructions in the computer-readable storage medium are executed by a processor of an electronic device, the electronic device is enabled to perform the method as claimed in any one of claims 1 to 7.

Images