Trace data processing method, medium, main routing node, and sub routing node
By configuring the target base address of the storage space on the main routing node and converting it into a routing protocol format, tracing data can be directly routed to the target storage space, solving the problem of low tracing data processing efficiency in SoC design and achieving more efficient data transmission and storage.
Patent Information
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- SANECHIPS TECH CO LTD
- Filing Date
- 2025-11-06
- Publication Date
- 2026-07-02
AI Technical Summary
In multi-processor, multi-cluster SoC designs, the processing efficiency of tracking data is low, resulting in high latency and a high risk of data loss. Existing technologies have not been able to effectively solve this problem.
After receiving the tracing data provided by the sub-routing node, the main routing node configures the target base address of the storage space and converts the tracing data into a routing protocol format, directly routing it to the storage space indicated by the target base address, thus avoiding the cumbersome path of transmitting to an external system and then back.
It effectively shortens the data propagation path, reduces latency, improves overall processing efficiency, and enhances network transparency and control.
Smart Images

Figure CN2025132917_02072026_PF_FP_ABST
Abstract
Description
Tracking data processing methods and media, main routing node, and sub-routing nodes.
[0001] Cross-reference to related applications
[0002] This application claims priority to Chinese Patent Application No. 202411925608.5, filed on December 25, 2024, entitled “Tracking Data Processing Method and Medium, Main Routing Node, Sub-Router Node”, the entire contents of which are incorporated herein by reference. Technical Field
[0003] This application relates to the field of communication technology, and in particular to tracking data processing methods and storage media, master routing nodes, and sub-routing nodes. Background Technology
[0004] With the rapid development of communication technology, the design of System-on-Chips (SoCs) is becoming increasingly complex, not only containing multiple processor cores but also often employing multi-cluster architectures to meet the demands for high performance and high energy efficiency. In this multi-processor, multi-cluster SoC design, the wireless mesh network serves as a core component, responsible for efficiently connecting the various processing units and ensuring smooth data and instruction transmission. Therefore, to ensure system stability and performance optimization, the debugging and tracing of the mesh network becomes particularly important.
[0005] When a SoC design includes multiple processing cores and multiple clusters, the sources of trace data become diverse. Therefore, an automated system is typically used to collect data from all trace sources throughout the system, including trace data from the mesh network. However, since trace data ultimately needs to be stored in system memory, which is mounted on the mesh network, a relatively long trace data propagation path is created. That is, trace data output from the mesh network is first transmitted to an external automated system, merged with information from other trace sources, then transmitted back to the mesh network, and finally stored in system memory, resulting in low trace data processing efficiency. Summary of the Invention
[0006] The main purpose of this application is to provide a tracking data processing method, storage medium, main routing node, and sub-routing node, aiming to solve the technical problem of low processing efficiency of tracking data.
[0007] To achieve the above objectives, this application proposes a tracking data processing method. The method is applied to a master routing node and includes: upon receiving tracking data provided by a sub-routing node, configuring a target base address for a storage space used to store the tracking data; converting the tracking data into a routing protocol format to obtain routing tracking data; and routing the routing tracking data to the storage space indicated by the target base address.
[0008] To achieve the above objectives, this application proposes a tracking data processing method. The method is applied to a sub-routing node and includes: generating tracking data based on transaction data transmitted by the mounted network device; sending the tracking data to a master routing node, wherein the tracking data is configured to: allow the master routing node to configure a target base address for the storage space used to store the tracking data; convert the tracking data into a routing protocol format to obtain routing tracking data; and then route the routing tracking data to the storage space indicated by the target base address.
[0009] Furthermore, to achieve the above objectives, this application also proposes a tracking data processing apparatus. The apparatus is applied to a main routing node and includes: a configuration module configured to configure a target base address for a storage space used to store the tracking data when receiving tracking data provided by a sub-routing node; a conversion module configured to convert the tracking data into a routing protocol format to obtain routing tracking data; and a routing module configured to route the routing tracking data to the storage space indicated by the target base address.
[0010] Furthermore, to achieve the above objectives, this application also proposes a tracking data processing apparatus. The apparatus is applied to a sub-routing node and includes: a generation module configured to generate tracking data based on transaction data transmitted by the mounted network device; and a sending module configured to send the tracking data to a master routing node. The tracking data is configured to: allow the master routing node to configure a target base address for the storage space used to store the tracking data; convert the tracking data into a routing protocol format to obtain routing tracking data; and then route the routing tracking data to the storage space indicated by the target base address.
[0011] To achieve the above objectives, this application proposes a master routing node, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor. The computer program is configured to implement the steps of the tracking data processing method described above.
[0012] To achieve the above objectives, this application provides a sub-routing node, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor. The computer program is configured to implement the steps of the tracking data processing method described above.
[0013] Furthermore, to achieve the above objectives, this application also proposes a storage medium, which is a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, it implements the steps of the tracking data processing method described above.
[0014] Furthermore, to achieve the above objectives, this application also proposes a computer program product, which includes a computer program that, when executed by a processor, implements the steps of the tracking data processing method described above. Attached Figure Description
[0015] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.
[0016] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, for those skilled in the art, other drawings can be obtained based on these drawings without creative effort.
[0017] Figure 1 is a flowchart illustrating the tracking data processing method provided in Embodiment 1 of this application.
[0018] Figure 2 is a schematic diagram of a scenario provided in Embodiment 1 of the tracking data processing method of this application;
[0019] Figure 3 is a flowchart of a more complete embodiment of the tracking data processing method of this application;
[0020] Figure 4 is a flowchart of a more complete embodiment of the data processing method of this application in the second embodiment;
[0021] Figure 5 is a schematic diagram of the frame structure of a tracking data processing device according to this application;
[0022] Figure 6 is a schematic diagram of the frame structure of another tracking data processing device of this application;
[0023] Figure 7 is a schematic diagram of the hardware operating environment of the main routing node involved in the tracking data processing method in this application embodiment;
[0024] Figure 8 is a schematic diagram of the hardware operating environment of the sub-routing node involved in the tracking data processing method in this application embodiment.
[0025] The purpose, features, and advantages of this application will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. Detailed Implementation
[0026] It should be understood that the specific embodiments described herein are merely illustrative of the technical solutions of this application and are not intended to limit this application.
[0027] To better understand the technical solution of this application, a detailed description will be provided below in conjunction with the accompanying drawings and some implementation methods.
[0028] In conventional techniques, tracing data is ultimately stored in system memory, which is mounted on the mesh network. This creates a relatively long tracing data propagation path: tracing data output from the mesh network is first transmitted to an external automated system, merged with information from other trace sources, and then transmitted back to the mesh network before finally being stored in system memory. This results in low processing efficiency. Furthermore, if the automated system operates at a lower frequency than the mesh network, or if the mesh network's tracing data output lacks backpressure, or if downstream nodes are slow to process the data, significant latency can occur, increasing the risk of tracing data loss from the mesh network.
[0029] This application provides a tracking data processing method applied to a master routing node. Upon receiving tracking data from a sub-routing node, the method configures the target base address of the storage space where the tracking data is ultimately stored. The tracking data is then converted into a routing protocol format to obtain routing tracking data. The converted tracking data can then be directly routed to the storage space indicated by the target base address, without needing to be sent to an external system and then back to the storage space. This effectively shortens the tracking data propagation path, reduces latency, and improves overall processing efficiency.
[0030] Referring to Figure 1, which is a flowchart of the first embodiment of the tracking data processing method of this application.
[0031] It should be noted that a mesh network, also known as a wireless mesh network, is a distributed network topology. Referring to Figure 2, in a mesh network, the master router node 201 and multiple child router nodes 202 work together to form a seamless coverage network. The entity executing the tracing data processing method can be the master router node 201 in the mesh network, responsible for communicating with other network devices (including child router nodes) and forwarding data packets. The tracing data processing method includes the following steps.
[0032] Step A10: Upon receiving tracing data provided by the sub-routing node, configure the target base address for the storage space used to store the tracing data.
[0033] In one feasible embodiment, each sub-routing node in the mesh network can generate corresponding tracing data based on the transaction data transmitted by the network devices it is attached to, and send it to the master routing node. Upon receiving the tracing data provided by each sub-routing node, the master routing node configures the target base address for the storage space of the tracing data, wherein the storage space can be the system memory where the tracing data will ultimately be stored.
[0034] The base address is the starting address of a specific memory region allocated to the trace data in the storage space.
[0035] Understandably, debugging and tracing are both indispensable key aspects of chip design. The main purpose of debugging is to locate problems that arise during the design process using a series of tools and methods. For example, simulation tools can be used to model the chip's behavior and compare it with expected results to identify discrepancies; or a debug interface can be used to communicate with the chip and monitor the processor's status and program execution in real time; or components such as debug registers, debug control units, and debug subsystems can be used to obtain the chip's internal state, thereby setting breakpoints and catching exceptions. Tracing, on the other hand, is mainly used to record detailed information about the chip's operation, including instruction execution and data flow; this information can be called trace data.
[0036] For example, the master routing node can be configured with a debug tracing controller and additional register resources to configure the target base address of the storage space for the tracing data when it receives tracing data provided by the sub-routing node.
[0037] Step A20: Convert the tracing data into a routing protocol format to obtain routing tracing data.
[0038] In one feasible embodiment, to avoid the cumbersome propagation path of tracing data being first sent to an external automated system during transmission, merged with information from other tracing data sources, and then transmitted back to the mesh network, the master routing node performs protocol format conversion on the tracing data, transforming it into a routing protocol format to obtain routing tracing data.
[0039] The routing protocol format, also known as the routing protocol format used by mesh networks, can also be referred to as the bus protocol format for mesh transaction transmission.
[0040] Step A30: The routing tracing data is routed to the storage space indicated by the target base address.
[0041] In one feasible embodiment, since the tracking data has been converted into a routing protocol format, the master routing node can directly route the tracking data to the storage space indicated by the target base address, instead of outputting the tracking data to an external automated system through the dedicated tracking bus interface, merging it with information from other tracking data sources, and then transmitting it back to the mesh network. Instead, it can directly route the tracking data to the storage space where it is ultimately stored through the mesh network, effectively shortening the tracking data propagation path, reducing latency, and improving overall processing efficiency.
[0042] For example, the master routing node can be configured with a debug tracing controller and have resources added to it for a transfer bridge module, thereby converting the tracing data into a routing protocol format, obtaining routing tracing data, and routing it to the storage space indicated by the target base address.
[0043] For example, the main routing node in the mesh network can be pre-configured to receive tracing data from the child routing nodes, configure the target base address, convert the tracing data to a routing protocol format, and then route the tracing data to the storage space indicated by the target base address. For instance, the mesh network can be configured through the JTAG (Joint Test Action Group) interface of an external debugger. Once the main routing node is configured, the external debugger's JTAG interface can be closed to prevent users from modifying the configuration information during use.
[0044] It is understood that in the mesh network of this application embodiment, if the entire system is scanned by an external debugger, the topology relationship scanned will not include the tracking data path from the mesh network to the automated system, but the tracking data path still actually exists.
[0045] In this embodiment, upon receiving tracing data provided by a sub-routing node, the target base address of the storage space for storing the final tracing data is configured; then, the tracing data is converted into a routing protocol format to obtain routing tracing data; the converted tracing data can then be directly routed to the storage space indicated by the target base address, without needing to be sent to an external system and then transferred back to the storage space, thereby effectively shortening the tracing data propagation path, reducing latency, and improving overall processing efficiency.
[0046] Based on the first embodiment described above, a second embodiment of the tracking data processing method of this application is proposed. In this embodiment, before the step of converting the tracking data into a routing protocol format in step A20, the following steps are also included.
[0047] Step A21: Insert timestamps into the tracking data.
[0048] In one feasible embodiment, the master routing node may insert timestamps into the tracking data, for example, by adding a marker or record representing a specific point in time.
[0049] For example, timestamps can be SoC timer information, thereby aligning and tracking event sequences within the SoC.
[0050] In this embodiment, by inserting timestamps into the tracking data, the sequential relationship of the tracking data can be determined, or the time delay of transactions being transmitted and processed between these nodes can be measured and estimated, so as to ensure data consistency and improve the convenience of data tracking and auditing.
[0051] In one feasible implementation, prior to step A20, the step of converting the tracking data into a routing protocol format, the method further includes:
[0052] Step A22: According to the preset alignment rules, identify the frame header of the tracking data and perform alignment processing on the tracking data.
[0053] In one feasible embodiment, the frame header is the beginning of the data frame, containing necessary control information for data synchronization, address identification, protocol type identification, etc. The master routing node can then parse and trace the beginning of the data according to preset alignment rules to find and identify the frame header; it then arranges and organizes the data according to specific rules or formats to ensure data correctness and efficient processing, thus achieving data alignment.
[0054] Alignment rules refer to the rules for formatting, encoding, or arranging frame headers according to specific communication protocols or data format requirements, including the length of the frame header, the order of fields, the data type and format of fields, etc.
[0055] For example, alignment processing may include: padding with extra bytes to ensure that the length of the data frame meets specific requirements, adjusting the position of fields to conform to a specific arrangement order, etc.
[0056] In this embodiment, by identifying the frame header of the tracking data and aligning the tracking data, the efficiency of tracking data processing can be improved, and the subsequent analysis and processing of the data can be facilitated.
[0057] In one feasible implementation, step A10, configuring the target base address of the storage space for storing tracking data, includes: step A11, incrementing the base address of the previous route to obtain the target base address of the storage space for storing tracking data.
[0058] In one feasible embodiment, the master routing node obtains the target base address of the storage space for the final storage of the tracing data by incrementing the base address used in the previous routing tracing data.
[0059] Address auto-increment means starting from a base address and gradually increasing it by a certain step size until the base address is determined or accessed.
[0060] In this embodiment, the target base address for storing tracking data is determined by incrementing the address, which effectively simplifies the complexity of memory management and improves the readability and maintainability of the code.
[0061] To aid in understanding the above technical solutions, a more complete embodiment of the tracking data processing method is provided. Referring to Figure 3, in step A101, the master routing node configures its control parameters to receive tracking data provided by the sub-routing node and perform subsequent processing. In step A102, upon receiving the tracking data from the sub-routing node, the master routing node inserts a timestamp into the tracking data, identifies the frame header of the tracking data according to a preset alignment rule, and then performs alignment processing on the tracking data. In step A103, the master routing node configures the target base address of the storage space for the tracking data. In step A104, the master routing node converts the tracking data into a routing protocol format to obtain routing tracking data. In step A105, the master routing node routes the routing tracking data to the storage space indicated by the target base address. By shortening the tracking data propagation path, latency is reduced and overall processing efficiency is improved.
[0062] Based on the first and / or second embodiments described above, a third embodiment of the tracking data processing method of this application is proposed. In this embodiment, the tracking data processing method is applied to a sub-routing node, which is an important component of the Mesh network and can communicate wirelessly with the main routing node or other sub-routing nodes. The tracking data processing method includes the following steps.
[0063] Step B10: Generate tracking data based on the transaction data transmitted by the mounted network device.
[0064] In one feasible embodiment, in a mesh network, sub-routing nodes can monitor and record transaction data transmitted through the network devices they are connected to (e.g., system memory, matrices, etc.), including but not limited to the sending and receiving of data packets, network requests and responses, etc. Sub-routing nodes can generate corresponding tracing data based on this transaction data.
[0065] The network device being mounted refers to the network device connected to the routing node.
[0066] For example, a sub-router node is equipped with a debug tracing module, which can monitor the transaction data transmitted by the devices mounted on the router node and generate tracing data.
[0067] Step B20: Send tracing data to the master routing node. The tracing data is configured to: provide the master routing node with the target base address for the storage space used to store the tracing data; convert the tracing data into a routing protocol format to obtain routing tracing data; and then route the routing tracing data to the storage space indicated by the target base address.
[0068] In one feasible embodiment, the sub-routing node sends the generated tracing data to the master routing node so that the master routing node can configure the target base address of the storage space used to store the tracing data, convert the tracing data into a routing protocol format to obtain routing tracing data, and then route the routing tracing data to the storage space indicated by the target base address.
[0069] In this embodiment, by monitoring the transaction data transmitted by the network devices attached to the sub-routing nodes and generating corresponding tracking data, the transparency and control of the network can be enhanced, thereby helping to maintain an efficient, secure and reliable network environment.
[0070] In one feasible implementation, step B10, which generates tracking data based on the transaction data transmitted by the mounted network device, includes the following steps.
[0071] Step B11: Obtain the transaction data transmitted by the network device according to the preset monitoring parameters.
[0072] In one feasible embodiment, a sub-routing node can monitor the network devices it is attached to based on pre-configured monitoring parameters, thereby obtaining the transaction data transmitted by the network devices. The monitoring parameters may include: the monitored device number, data channel number, field group number, monitoring method, etc.
[0073] Step B12: Extract the fields of interest from the transaction data according to the preset tracking data type, and generate tracking data.
[0074] In one feasible embodiment, by configuring specific tracking data types, sub-routing nodes can capture data packets related to specific protocols, source addresses, destination addresses, ports, etc., and extract fields of interest to generate tracking data containing key fields, thereby reducing interference from irrelevant data and improving the processing efficiency of tracking data.
[0075] In one feasible implementation, step B10, the step of generating tracking data based on the transaction data transmitted by the mounted network device, includes: step B13, determining the target data length based on the tracking data type to which the transaction data belongs; and step B14, converting the transaction data into the target data length to obtain the tracking data.
[0076] In one feasible embodiment, different data lengths are pre-set for each tracking data type, and then the sub-routing node determines the target data length that matches the tracking data according to the tracking data type to which the transaction data belongs; then the transaction data is converted into the target data length to obtain the tracking data.
[0077] In this embodiment, transaction data is converted into the corresponding target data length to ensure that data of the same type have a uniform length, thereby reducing the overhead of data processing, optimizing storage, and improving data processing efficiency.
[0078] To aid in understanding the above technical solutions, a more complete embodiment two of the tracking data processing method is provided. Referring to Figure 4, in step B101, the sub-routing node pre-configures monitoring parameters to capture data packets related to specific protocols, source addresses, destination addresses, ports, etc. In step B102, the sub-routing node extracts the fields of interest from the captured transaction data according to the pre-configured tracking data type. In step B103, the sub-routing node determines the target data length based on the tracking data type to which the extracted fields of interest belong, and then converts the fields to the target data length to obtain tracking data. In step B104, the sub-routing node sends the tracking data to the master routing node so that the master routing node can configure the target base address for the storage space used to store the tracking data, convert the tracking data into a routing protocol format to obtain routing tracking data, and then route the routing tracking data to the storage space indicated by the target base address. By monitoring the transaction data transmitted by the network devices connected to the sub-routing node and generating corresponding tracking data, network transparency and control capabilities can be enhanced, thereby helping to maintain an efficient, secure, and reliable network environment. The main routing node reduces latency and improves overall processing efficiency by shortening the path of tracking data propagation.
[0079] It should be noted that the above examples are only for understanding this application and do not constitute a limitation on the data processing method of this application. Any simple modifications based on this technical concept are within the protection scope of this application.
[0080] This application provides a tracking data processing apparatus. Referring to FIG5, the apparatus is applied to a main routing node. The apparatus includes: a configuration module 11, configured to configure a target base address for a storage space used to store tracking data when receiving tracking data provided by a sub-routing node; a conversion module 12, configured to convert the tracking data into a routing protocol format to obtain routing tracking data; and a routing module, configured to route the routing tracking data to the storage space indicated by the target base address.
[0081] The tracking data processing apparatus provided in this application, employing the tracking data processing method described in the above embodiments, can solve the technical problem of low tracking data processing efficiency. Compared with related technologies, the beneficial effects of the tracking data processing apparatus provided in this application are the same as those of the tracking data processing method described in the above embodiments, and other technical features in the tracking data processing apparatus are the same as those disclosed in the methods of the above embodiments, and will not be repeated here.
[0082] This application embodiment also provides another tracking data processing apparatus. Referring to FIG6, the apparatus is applied to a sub-routing node. The apparatus includes: a generation module 21, configured to generate tracking data based on transaction data transmitted by the mounted network device; and a sending module 22, configured to send the tracking data to the main routing node. The tracking data is configured to: allow the main routing node to configure the target base address of the storage space used to store the tracking data, convert the tracking data into a routing protocol format to obtain routing tracking data, and then route the routing tracking data to the storage space indicated by the target base address.
[0083] The tracking data processing apparatus provided in this application, employing the tracking data processing method described in the above embodiments, can solve the technical problem of low tracking data processing efficiency. Compared with related technologies, the beneficial effects of the tracking data processing apparatus provided in this application are the same as those of the tracking data processing method described in the above embodiments, and other technical features in the tracking data processing apparatus are the same as those disclosed in the methods of the above embodiments, and will not be repeated here.
[0084] This application provides a master routing node, which includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, which are executed by the at least one processor to enable the at least one processor to perform the tracking data processing method in the first embodiment described above.
[0085] Referring to Figure 7 below, schematic diagrams of the structure of a main routing node suitable for implementing embodiments of this application are shown. The main routing node in embodiments of this application may include, but is not limited to, mobile terminals such as mobile phones, laptops, digital broadcast receivers, PDAs (Personal Digital Assistants), PADs (Portable Application Description), PMPs (Portable Media Players), in-vehicle terminals (e.g., in-vehicle navigation terminals), and fixed terminals such as digital TVs and desktop computers. The main routing node shown in Figure 7 is merely an example and should not impose any limitations on the functionality and scope of use of embodiments of this application.
[0086] As shown in Figure 7, the main routing node may include a processing device 1001 (e.g., a central processing unit, a graphics processing unit, etc.), which can perform various appropriate actions and processes according to a program stored in read-only memory (ROM) 1002 or a program loaded from storage device 1003 into random access memory (RAM) 1004. RAM 1004 also stores various programs and data required for the operation of the main routing node. The processing device 1001, ROM 1002, and RAM 1004 are interconnected via bus 1005. Input / output (I / O) interface 1006 is also connected to the bus. Typically, the following systems can be connected to I / O interface 1006: input devices 1007 including, for example, touchscreens, touchpads, keyboards, mice, image sensors, microphones, accelerometers, gyroscopes, etc.; output devices 1008 including, for example, liquid crystal displays (LCDs), speakers, vibrators, etc.; storage devices 1003 including, for example, magnetic tapes, hard disks, etc.; and communication devices 1009. Communication device 1009 allows the main routing node to communicate wirelessly or wiredly with other devices to exchange data. While the figure shows a main routing node with various systems, it should be understood that implementation or possession of all the systems shown is not required. More or fewer systems may be implemented alternatively.
[0087] Specifically, according to the embodiments disclosed in this application, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments disclosed in this application include a computer program product comprising a computer program carried on a computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via a communication device, or installed from storage device 1003, or installed from ROM 1002. When the computer program is executed by processing device 1001, it performs the functions defined in the methods of the embodiments disclosed in this application.
[0088] The main routing node provided in this application embodiment employs the tracking data processing method described in the above embodiments, which can solve the technical problem of low tracking data processing efficiency. Compared with related technologies, the beneficial effects of the main routing node provided in this application embodiment are the same as those of the tracking data processing method provided in the above embodiments, and other technical features of the main routing node are the same as those disclosed in the previous embodiment method, and will not be repeated here.
[0089] It should be understood that the various parts disclosed in this application can be implemented using hardware, software, firmware, or a combination thereof. In the description of the above embodiments, features, structures, materials, or characteristics can be combined in any suitable manner in one or more embodiments or examples.
[0090] The above are merely embodiments of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.
[0091] This application embodiment also provides a sub-routing node, each sub-routing node comprising: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to perform the tracking data processing method in the first embodiment described above.
[0092] Referring to Figure 8 below, schematic diagrams of the structures of sub-routing nodes suitable for implementing embodiments of this application are shown. The sub-routing nodes in the embodiments of this application may include, but are not limited to, mobile terminals such as mobile phones, laptops, digital broadcast receivers, PDAs (Personal Digital Assistants), PADs (Portable Application Description), PMPs (Portable Media Players), in-vehicle terminals (e.g., in-vehicle navigation terminals), and fixed terminals such as digital TVs and desktop computers. The sub-routing node shown in Figure 8 is merely an example and should not impose any limitations on the functionality and scope of use of the embodiments of this application.
[0093] As shown in Figure 8, a sub-routing node may include a processing device 2001 (e.g., a central processing unit, a graphics processing unit, etc.), which can perform various appropriate actions and processes according to a program stored in read-only memory (ROM) 2002 or a program loaded from storage device 2003 into random access memory (RAM) 2004. RAM 2004 also stores various programs and data required for the operation of the sub-routing node. The processing device 2001, ROM 2002, and RAM 2004 are interconnected via bus 2005. Input / output (I / O) interface 2006 is also connected to the bus. Typically, the following systems can be connected to I / O interface 2006: input devices 2007 including, for example, touchscreens, touchpads, keyboards, mice, image sensors, microphones, accelerometers, gyroscopes, etc.; output devices 2008 including, for example, liquid crystal displays (LCDs), speakers, vibrators, etc.; storage devices 2003 including, for example, magnetic tapes, hard disks, etc.; and communication devices 2009. Communication device 2009 allows sub-routing nodes to communicate wirelessly or wiredly with other devices to exchange data. While the figure shows sub-routing nodes with various systems, it should be understood that implementation or possession of all the systems shown is not required. More or fewer systems may be implemented alternatively.
[0094] Specifically, according to the embodiments disclosed in this application, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments disclosed in this application include a computer program product comprising a computer program carried on a computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via a communication device, or installed from storage device 2003, or installed from ROM 2002. When the computer program is executed by processing device 2001, it performs the functions defined in the methods of the embodiments disclosed in this application.
[0095] The sub-routing node provided in this application embodiment, employing the tracking data processing method described in the above embodiments, can solve the technical problem of low tracking data processing efficiency. Compared with related technologies, the beneficial effects of the sub-routing node provided in this application embodiment are the same as those of the tracking data processing method provided in the above embodiments, and other technical features in this sub-routing node are the same as those disclosed in the method of the previous embodiment, and will not be repeated here.
[0096] It should be understood that the various parts disclosed in this application can be implemented using hardware, software, firmware, or a combination thereof. In the description of the above embodiments, features, structures, materials, or characteristics can be combined in any suitable manner in one or more embodiments or examples.
[0097] The above are merely embodiments of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.
[0098] This application provides a computer-readable storage medium having computer-readable program instructions (i.e., a computer program) stored thereon, which are used to execute the tracking data processing method in the above embodiments.
[0099] The computer-readable storage medium provided in this application embodiment may be, for example, a USB flash drive, but is not limited to, electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices, or any combination thereof. An example of a computer-readable storage medium may include, but is not limited to: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In this embodiment, the computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, system, or device. The program code contained on the computer-readable storage medium may be transmitted using any suitable medium, including but not limited to: wires, optical cables, RF (Radio Frequency), etc., or any suitable combination thereof.
[0100] The aforementioned computer-readable storage medium may be included in the sub-routing node and / or the main routing node; or it may exist independently and not be assembled into the sub-routing node and / or the main routing node.
[0101] The aforementioned computer-readable storage medium carries one or more programs that, when executed by the master routing node, cause the master routing node to: generate trace data based on the transaction data transmitted by the mounted network device; send the trace data to the master routing node, wherein the trace data is configured to: allow the master routing node to configure the target base address of the storage space used to store the trace data, convert the trace data into a routing protocol format to obtain routing trace data, and then route the routing trace data to the storage space indicated by the target base address.
[0102] When one or more of the above procedures are executed by the sub-routing node, the sub-routing node: upon detecting the access of the master routing node, generates a configuration message, wherein the configuration message carries the currently stored first virtual LAN identifier, which is used for configuring virtual LAN identifiers; and sends the configuration message to the master routing node.
[0103] Computer program code for performing the operations of this application can be written in one or more programming languages or a combination thereof, including object-oriented programming languages such as Java, Smalltalk, and C++, and conventional procedural programming languages such as the "C" language or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network—including a Local Area Network (LAN) or a Wide Area Network (WAN)—or can be connected to an external computer (e.g., via the Internet using an Internet service provider).
[0104] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this application. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.
[0105] The modules described in the embodiments of this application can be implemented in software or hardware. The names of the modules do not necessarily limit the functionality of the unit itself.
[0106] The readable storage medium provided in this application embodiment is a computer-readable storage medium that stores computer-readable program instructions (i.e., a computer program) for executing the above-described tracking data processing method, thereby solving the technical problem of low tracking data processing efficiency. Compared with related technologies, the beneficial effects of the computer-readable storage medium provided in this application embodiment are the same as the beneficial effects of the tracking data processing method provided in the above embodiments, and will not be repeated here.
[0107] The above are only some embodiments of this application and do not limit the patent scope of this application. All equivalent structural transformations made under the technical concept of this application and using the contents of the specification and drawings of this application, or direct / indirect applications in other related technical fields, are included in the patent protection scope of this application.
Claims
1. A method for processing tracking data, the method being applied to a master routing node, the method comprising: Upon receiving tracing data provided by a sub-routing node, configure the target base address for the storage space used to store the tracing data; The tracing data is converted into a routing protocol format to obtain routing tracing data; The routing tracing data is routed to the storage space indicated by the target base address.
2. The method as described in claim 1, wherein, Prior to the step of converting the tracking data into a routing protocol format, the method further includes: Insert timestamps into the tracking data.
3. The method as described in claim 1, wherein, Prior to the step of converting the tracking data into a routing protocol format, the method further includes: According to the preset alignment rules, the frame header of the tracking data is identified, and the tracking data is aligned.
4. The method of claim 1, wherein, The step of configuring the target base address of the storage space used to store the tracking data includes: The base address of the previous route is incremented to obtain the target base address of the storage space used to store the tracking data.
5. A tracking data processing method, wherein the method is applied to a sub-routing node, the method comprising: Based on the transaction data transmitted by the connected network devices, generate tracking data; The tracing data is sent to the master routing node, wherein the tracing data is configured to: allow the master routing node to configure the target base address for the storage space used to store the tracing data, convert the tracing data into a routing protocol format to obtain routing tracing data, and then route the routing tracing data to the storage space indicated by the target base address.
6. The tracking data processing method as described in claim 5, wherein, The step of generating tracking data based on the transaction data transmitted by the mounted network device includes: Based on preset monitoring parameters, acquire the transaction data transmitted by the network device; Based on the preset tracking data type, extract the fields of interest from the transaction data and generate the tracking data.
7. The tracking data processing method as described in claim 5, wherein, The step of generating tracking data based on the transaction data transmitted by the mounted network device includes: Determine the target data length based on the tracking data type to which the transaction data belongs; The transaction data is converted to the target data length to obtain the tracking data.
8. A master routing node, the master routing node comprising: A memory, a processor, and a computer program stored in the memory and executable on the processor, the computer program being configured to implement the steps of the tracking data processing method as described in any one of claims 1 to 4.
9. A sub-routing node, the sub-routing node comprising: A memory, a processor, and a computer program stored in the memory and executable on the processor, the computer program being configured to implement the steps of the tracking data processing method as described in any one of claims 5 to 7.
10. A storage medium, the storage medium being a computer-readable storage medium, the storage medium storing a computer program, the computer program being executed by a processor to implement the steps of the tracking data processing method as described in any one of claims 1 to 7.