Communication link tracking method and device, electronic equipment and storage medium
By acquiring and processing link data in a two-level deployed system, the cross-region link tracking problem is solved, and the cross-region link is fully tracked, supporting fault location and performance tuning.
Patent Information
- Application Number
- CN202410988956.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-07-23
- Publication Date
- 2024-12-03
AI Technical Summary
The overall business link caused by the two-level deployment method is relatively long, and it is difficult for both systems to track cross-region call links, and it is impossible to effectively locate faults, perform performance tuning and user behavior analysis.
By obtaining link data from the called side system, determining whether it is cross-region data, obtaining tracking identifiers, and obtaining the first-level and second cascade data from the call side and the called side system for data processing, realizing cross-region data Link tracking.
It realizes complete tracking of cross-region links, which facilitates fault location, performance tuning and user behavior analysis.
Smart Images

Figure CN119071201A_ABST
Abstract
Description
Technical Field
[0001] The present disclosure relates to the field of data processing technology, and in particular to a communication link tracking method, device, electronic device and storage medium. Background Art
[0002] The two-level deployment method results in a long overall business link. The systems on both sides monitor their own operating status separately, and cannot track the cross-region call links on both sides, and cannot effectively locate faults, optimize performance, and analyze user behavior.
[0003] In view of this, how to track the cross-region links on both sides becomes a technical problem that needs to be solved urgently. Summary of the invention
[0004] In view of this, the purpose of the present disclosure is to provide a communication link tracking method, device, electronic device and storage medium to solve or partially solve the above technical problems.
[0005] Based on the above purpose, the first aspect of the present disclosure provides a communication link tracking method, the method comprising:
[0006] Acquire link data from the called side system, and determine whether the link data is cross-region data sent from the calling side system to the called side system;
[0007] In response to determining that the link data is cross-region data sent from a calling-side system to a called-side system, acquiring a tracking identifier from the link data;
[0008] Acquire first cascade data from the calling side system according to the tracking identifier, and acquire second cascade data from the called side system according to the tracking identifier;
[0009] Data processing is performed on the first cascade data and the second cascade data to obtain tracking data.
[0010] Based on the same inventive concept, the second aspect of the present disclosure provides a communication link tracking device, comprising:
[0011] A determination module is configured to obtain link data from the called side system and determine whether the link data is cross-region data sent from the calling side system to the called side system;
[0012] a tracking identifier acquisition module, configured to acquire a tracking identifier from the link data in response to determining that the link data is cross-region data sent from a calling side system to a called side system;
[0013] a cascade data acquisition module, configured to acquire first cascade data from the calling side system according to the tracking identifier, and acquire second cascade data from the called side system according to the tracking identifier;
[0014] The data processing module is configured to perform data processing on the first cascade data and the second cascade data to obtain tracking data.
[0015] Based on the same inventive concept, the third aspect of the present disclosure proposes an electronic device, including a memory, a processor, and a computer program stored in the memory and executable by the processor, wherein the processor implements the method as described above when executing the computer program.
[0016] Based on the same inventive concept, a fourth aspect of the present disclosure proposes a non-transitory computer-readable storage medium, wherein the non-transitory computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a computer to execute the method as described above.
[0017] As can be seen from the above, the present disclosure provides a communication link tracking method, device, electronic device and storage medium. Link data is obtained from the called side system, and it is determined whether the link data is cross-region data sent from the calling side system to the called side system. When the link data is cross-region data sent from the calling side system to the called side system, a tracking identifier is obtained from the link data, and the first cascade data is obtained from the calling side system according to the tracking identifier, and the second cascade data is obtained from the called side system according to the tracking identifier, and the first cascade data and the second cascade data are processed to obtain tracking data. In this way, the cross-region link data sent from the calling side system to the called side system can be tracked, and the tracking of the complete data link can be achieved, thereby facilitating fault location, performance tuning and user behavior analysis. BRIEF DESCRIPTION OF THE DRAWINGS
[0018] In order to more clearly illustrate the technical solutions in the present disclosure or related technologies, the drawings required for use in the embodiments or related technical descriptions are briefly introduced below. Obviously, the drawings described below are only embodiments of the present disclosure. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.
[0019] Figure 1 A schematic diagram of headquarters link tracking and provincial-side link tracking according to an embodiment of the present disclosure;
[0020] Figure 2 A flowchart of a method for tracking a communication link according to an embodiment of the present disclosure;
[0021] Figure 3 A schematic diagram of cross-region link tracking according to an embodiment of the present disclosure;
[0022] Figure 4 It is a structural schematic diagram of a communication link tracking device according to an embodiment of the present disclosure;
[0023] Figure 5 It is a schematic diagram of the structure of an electronic device according to an embodiment of the present disclosure. DETAILED DESCRIPTION
[0024] In order to make the objectives, technical solutions and advantages of the present disclosure more clearly understood, the present disclosure is further described in detail below in combination with specific embodiments and with reference to the accompanying drawings.
[0025] It should be noted that, unless otherwise defined, the technical terms or scientific terms used in the embodiments of the present disclosure should be understood by people with ordinary skills in the field to which the present disclosure belongs. The "first", "second" and similar words used in the embodiments of the present disclosure do not indicate any order, quantity or importance, but are only used to distinguish different components. "Including" or "comprising" and similar words mean that the elements or objects appearing before the word cover the elements or objects listed after the word and their equivalents, without excluding other elements or objects. "Connect" or "connected" and similar words are not limited to physical or mechanical connections, but can include electrical connections, whether direct or indirect. "Up", "down", "left", "right" and the like are only used to indicate relative positional relationships. When the absolute position of the described object changes, the relative positional relationship may also change accordingly.
[0026] Based on the description of the background technology, the two-level business middle platform is divided into a headquarters and a provincial deployment mode. The headquarters is responsible for business statistics, and the provincial side is responsible for the construction of their own application systems. The two-level deployment mode leads to a long overall business link. The headquarters and the provincial side monitor their own operating status separately. If there is a problem with the cross-region call link between the headquarters and the provincial side, it will become very difficult to quickly locate the fault.
[0027] The two-level business platform is divided into two systems, the headquarters and the provincial side. Link tracking has multiple protocols and versions, so it is difficult for the headquarters and the provincial side to establish a unified link tracking system. Figure 1 As shown in the figure, the headquarters link tracking system only tracks the headquarters link data, and the provincial link tracking system only tracks the provincial link data. In this way, the operation status of the headquarters and the provincial side are monitored separately, but cross-region call monitoring is rarely involved, and complete data link tracking cannot be achieved, and fault location, performance tuning and user behavior analysis cannot be effectively performed.
[0028] As mentioned above, how to track the cross-region links on both sides has become an important research issue.
[0029] Based on the above description, if Figure 2 As shown, the communication link tracking method proposed in this embodiment includes:
[0030] Step 101, obtaining link data from the called side system, and determining whether the link data is cross-region data sent from the calling side system to the called side system.
[0031] Step 102: In response to determining that the link data is cross-region data sent from the calling side system to the called side system, a tracking identifier is obtained from the link data.
[0032] Step 103: acquiring first cascade data from the calling side system according to the tracing identifier, and acquiring second cascade data from the called side system according to the tracing identifier.
[0033] Step 104: Process the first cascade data and the second cascade data to obtain tracking data.
[0034] When it comes to specific implementation, Figure 3 FIG. 1 is a schematic diagram of cross-region link tracking according to an embodiment of the present disclosure. Figure 3 As shown, the link data sent from the calling side system to the called side system is cross-zone data, and the data between the calling side system and the called side system is an actual call.
[0035] When the link data is cross-zone data sent from the calling side system to the called side system, obtain the tracking identifier TraceId that meets the first preset rule, and send the tracking identifier TraceId to the message middleware. The calling side system sends the link data to the calling side link tracking system, and the called side system sends the link data to the called side link tracking system. The message middleware obtains the first cascade data from the calling side link tracking system according to the tracking identifier TraceId, and obtains the second cascade data from the called side link tracking system.
[0036] Determine whether the first cascade data and the second cascade data meet the second preset rule. When the first cascade data and the second cascade data meet the second preset rule, splice the first cascade data and the second cascade data to obtain spliced data. Convert the spliced data into standard data in a preset format. Visualize the standard data to obtain tracking data.
[0037] Among them, link calls are between the calling side system and the calling side link tracking system, between the called side system and the called side link tracking system, between the called side system and the message middleware, between the calling side link tracking system and the message middleware, and between the called side link tracking system and the message middleware.
[0038] Through the above embodiment, link data is obtained from the called side system, and it is determined whether the link data is cross-region data sent from the calling side system to the called side system. When the link data is cross-region data sent from the calling side system to the called side system, a tracking identifier is obtained from the link data, and the first cascade data is obtained from the calling side system according to the tracking identifier, and the second cascade data is obtained from the called side system according to the tracking identifier, and the first cascade data and the second cascade data are processed to obtain tracking data. In this way, the cross-region link data sent from the calling side system to the called side system can be tracked, and the tracking of the complete data link can be achieved, thereby facilitating fault location, performance tuning and user behavior analysis.
[0039] In some embodiments, step 101 includes:
[0040] Step 1011: Acquire link data from the called side system and determine the information field of the link data.
[0041] Step 1012: Determine the area identification field of the link data from the information field of the link data.
[0042] Step 1013: determine, based on the area identification field, whether the link data is cross-area data sent from the calling side system to the called side system.
[0043] In specific implementation, the information field of the link data is represented as CollectInfo, and the data structure is Map <CollectInfo,Map<Key,Value> >.
[0044] Among them, the data structure Map of the information field<Key,Value> Includes: AreaTag field. The corresponding key-value pair of the link data of the calling system is<AreaTag,Calling> ; The key-value pair corresponding to the link data of the called side system is<AreaTag,Called> . Data structure Map of information field<Key,Value> It also includes other fields, among which the area identification field AreaTag is a required field, and other fields can be expanded as required.
[0045] When the area identification field of the link data is<AreaTag,Calling> becomes<AreaTag,Called> , then the link data is the cross-region data sent from the calling side system to the called side system.
[0046] Through the above scheme, the regional source of the link data can be determined according to the regional identification field, and whether the link data is cross-region data sent from the calling side system to the called side system can be accurately judged according to the regional identification field.
[0047] In some embodiments, step 102 includes:
[0048] Step 1021, in response to determining that the region identification field is changed from the calling side region to the called side region, determining that the link data is cross-region data sent from the calling side system to the called side system.
[0049] Step 1022, determining whether the information field of the link data satisfies a first preset rule.
[0050] Step 1023: In response to determining that the information field satisfies a first preset rule, obtaining a tracking identifier from the link data.
[0051] In a specific implementation, when the link data is cross-region data sent from the calling side system to the called side system, and the information field of the link data satisfies the first preset rule, the tracking identifier TraceId is obtained from the link data.
[0052] After obtaining the tracing identifier TraceId, the tracing identifier TraceId is sent to the message middleware, so that the message middleware obtains the first cascade data from the calling side link tracing system and the second cascade data from the called side link tracing system according to the tracing identifier TraceId.
[0053] Through the above solution, when the link data is cross-region data sent from the calling side system to the called side system, and the information field of the link data satisfies the first preset rule, the tracking identifier TraceId is obtained from the link data. In this way, the obtained tracking identifier TraceId satisfies the cross-region data and the first preset rule.
[0054] In some embodiments, step 1022 includes:
[0055] Step 10221, obtaining the field quantity of the information field.
[0056] Step 10222: In response to determining that the number of fields is greater than a preset number threshold, the information fields are traversed and it is determined whether the traversed multiple information fields meet the corresponding first preset rule.
[0057] In specific implementation, the number of fields in the information field is the data structure Map of the information field<Key,Value> When the number of fields in the information field is greater than the preset number threshold, that is, the field length is greater than the preset length threshold, it means that the link data has multiple information fields. In this way, when determining the tracking identifier that meets the first preset rule from the link data, by traversing the information field and judging whether the multiple information fields meet the corresponding first preset rule, it is possible to determine in the link data that each information field meets the corresponding first preset rule.
[0058] For example, the preset quantity threshold is 1. When the data structure Map of the information field<Key,Value> The field length is greater than 1, indicating that the information field includes other fields in addition to the area identification field AreaTag. The information field Key is traversed to obtain the tracking identification TraceId whose information field Key satisfies the corresponding first preset rule. In this way, the determined tracking identification TraceId is the tracking identification TraceId of cross-area data and satisfies the first preset rule.
[0059] Through the above solution, through traversal processing, it is possible to judge whether multiple information fields meet the corresponding first preset rule. In this way, the tracking identifier TraceId of cross-region data that meets the first preset rule can be obtained, making the determined tracking identifier TraceId more accurate.
[0060] In some embodiments, the first preset rule includes at least one of the following: a response status rule, a user coding rule, and a response time rule; step 10222 includes:
[0061] Step 102221, traverse the information field to obtain at least one of the response status field, the user code field and the response time field.
[0062] Step 102222, determine whether the response status field satisfies the response status rule.
[0063] And / or, step 102223, determining whether the user code field satisfies the user code rule.
[0064] And / or, step 102224, determining whether the response time field satisfies the response time rule.
[0065] In specific implementation, the data structure Map of the information field<Key,Value> In addition to the area identification field AreaTag, it may also include: a response status field StatusCode, a user code field UserId, and a response time field StatusTime.
[0066] Among them, the area identification field AreaTag is a required field, and the response status field StatusCode, the user code field UserId and the response time field StatusTime can be expanded as required.
[0067] When the response status field in the information field of the link data satisfies the response status rule, the user code field satisfies the user code rule, and the response time field satisfies the response time rule, it indicates that the link data is cross-zone data and satisfies the first preset rule, and the tracking identifier TraceId of the link data is obtained.
[0068] Through the above scheme, when the response status field, user code field and response time field of the link data meet the corresponding first preset rule, the tracking identifier TraceId of the link data is obtained. In this way, the tracking identifier TraceId of the cross-zone data that meets the response status rule, user code rule and response time rule can be obtained, making the determined tracking identifier TraceId more accurate.
[0069] In some embodiments, step 102222 includes: step 102222A, determining whether the response status field is in a response success status.
[0070] In specific implementation, the response status field StatusCode includes a response success status and a response failure status.<StatusCode,Success> , the response failure status is<StatusCode,Error> . Determine whether the response status field StatusCode is a successful response status<StatusCode,Success> For example, when locating data faults, filter the link data with a successful response status. The response status rule is to filter the link data with a successful response status.<StatusCode,Success> .
[0071] Step 102223 includes: Step 102223A, determining whether the user code field is in the first preset user list, or determining whether the user code field is not in the second preset user list.
[0072] In specific implementation, the user code field UserId determines whether the user code field UserId is in the first preset user list, or determines whether the user code field UserId is not in the second preset user list. For example, when analyzing the user behavior of the data, when analyzing the operation information of users 123, 456, and 789, the user code rule is to filter the user code field<UserId,”123,456,789”> The processing logic is to determine whether the user code is among 123, 456, and 789.
[0073] Step 102224 includes: Step 102224A, determining whether the response time field is within a preset response time.
[0074] In specific implementation, the response time field StatusTime is used to determine whether the response time field StatusTime is within the preset response time. For example, when optimizing data performance, when analyzing link calls with a response time less than or equal to 20ms, the response time rule is to filter the response time field<StatusTime,20> ,The processing logic is to filter the link calls with response time ≤ 20ms.
[0075] Through the above scheme, by judging whether the response status field is in a successful response status, the link data in a successful response status can be screened, and the link data can be fault-located. By judging whether the user code field is in the first preset user list, the link data in the first preset user list can be screened, and the behavior analysis of the users in the first preset list can be performed. By judging whether the user code field is not in the second preset user list, the link data not in the second preset user list can be screened, and the behavior analysis of users outside the second preset list can be performed. By judging whether the response time field is within the preset response time, the link data within the preset response time can be screened, and the performance of the link data can be optimized. In this way, the tracking identifier TraceId that crosses the zone data and satisfies the response status rule, the user code rule, and the response time rule can be obtained, so that the determined tracking identifier TraceId is more accurate.
[0076] In some embodiments, step 104 includes:
[0077] Step 1041: Determine whether the first cascade data and the second cascade data satisfy a second preset rule.
[0078] Step 1042: In response to determining that the first concatenated data and the second concatenated data satisfy a second preset rule, concatenate the first concatenated data and the second concatenated data to obtain concatenated data.
[0079] Step 1043: convert the spliced data into standard data in a preset format.
[0080] Step 1044: Visualize the standard data to obtain tracking data.
[0081] In specific implementation, the calling side system sends the link data to the calling side link tracking system, and the called side system sends the link data to the called side link tracking system. The message middleware obtains the first cascade data from the calling side link tracking system and the second cascade data from the called side link tracking system according to the tracking identifier TraceId.
[0082] The second preset rule includes at least one of the following: a response status rule, a user coding rule, and a response time rule.
[0083] The second preset rule may not be related to the first preset rule. For example, when optimizing data performance, when analyzing link calls with response time greater than or equal to 25ms, the response time rule is to filter the response time field.<StatusTime,25> , the processing logic is to filter the link calls with response time ≥ 25ms. Since the first preset rule is to filter the link data with response time ≤ 20ms, and the second preset rule is to filter the first cascade data and the second cascade data with response time ≥ 25ms, there is no first cascade data and second cascade data in the link data that meet the second preset rule. For another example, the second preset rule is other field rules except the response status rule, user coding rule and response time rule, and the first cascade data and the second cascade data that meet other field rules can be further filtered.
[0084] The second preset rule and the first preset rule may also be associated with each other. For example, when locating a fault on data, the link data with a successful response status is filtered, and the response status rule is to filter the link data with a successful response status.<StatusCode,Success> When analyzing user behavior data, when analyzing the operation information of users other than 123, the user coding rule is to filter the user coding field<UserId,”123”> , the processing logic is to filter the user code is not 123. When optimizing the performance of the data, when analyzing the link call with a response time less than or equal to 10ms, the response time rule is to filter the response time field<StatusTime,10> , the processing logic is to filter the link calls with response time ≤ 10ms. The second preset rule is equivalent to a subset of the first preset rule. In this way, after filtering out the tracking identifiers that meet the first preset rule from the link data, the first cascade data and the second cascade data that meet the second preset rule are further filtered, thereby achieving accurate data filtering, so that the filtered first cascade data and the second cascade data can better meet the needs of users.
[0085] When the first cascade data and the second cascade data meet the second preset rule, the first cascade data and the second cascade data are spliced to obtain spliced data, the spliced data is converted into standard data in a preset format, and the standard data is visualized to obtain tracking data.
[0086] Through the above solution, the cross-region data sent from the calling side system to the called side system is tracked and processed to obtain the tracking data. The tracking data can be used for fault location, performance tuning and user behavior analysis.
[0087] Through the above embodiment, link data is obtained from the called side system, and it is determined whether the link data is cross-region data sent from the calling side system to the called side system. When the link data is cross-region data sent from the calling side system to the called side system, a tracking identifier is obtained from the link data, and the first cascade data is obtained from the calling side system according to the tracking identifier, and the second cascade data is obtained from the called side system according to the tracking identifier, and the first cascade data and the second cascade data are processed to obtain tracking data. In this way, the cross-region link data sent from the calling side system to the called side system can be tracked, and the tracking of the complete data link can be achieved, thereby facilitating fault location, performance tuning and user behavior analysis.
[0088] It should be noted that the embodiments of the present disclosure may be further described in the following manner:
[0089] The terms used in this disclosure are explained as follows:
[0090] Link tracking: refers to a method of recording and displaying the processing process of a request in a distributed system.
[0091] Transparent transmission protocol standardization: All applications in the entire link need to follow the same set of protocol transparent transmission standards to ensure that the link context can be fully transparently transmitted between applications in different languages without any problems such as link disconnection or context loss. The current mainstream open source transparent transmission protocols include Jaeger, Sky Walking, and Zip Kin.
[0092] Trace: A trace represents the complete call track of an entry request in the IT system and its associated data set. Among them, the globally unique link trace identifier (TraceId) is the most representative attribute. Only through TraceId can the link data of the same request scattered in different nodes be accurately associated, realizing the "deterministic association" value of request granularity.
[0093] Basic object (Span): The basic object that carries link information is Span, which has the following properties: OperationName: describes the behavioral semantics of the current interface, such as / api / createOrder represents the execution of an action to create an order. SpanId / ParentSpanId: The hierarchical identifier of the interface call, used to restore the hierarchical call relationship within the Trace. Start / FinishTime: The start and end time of the interface call, the difference between the two is the duration of this call. StatusCode: Response status, indicating whether the call is successful or failed. Tags&Events: Additional call information, Tags can be used to extend the semantics.
[0094] Extended semantics (Tags): It is a set of key-value pairs consisting of {Key:Value}, which describes the specific attributes of this interface call. For example, if UserType is added to Tags, the link behavior status of a certain type of user (such as VIP users) can be observed. If the device type is added to Tags, the performance differences of different devices can be compared.
[0095] Single request trace back is the most basic function of distributed link tracking, which records all service nodes that a request passes through and the corresponding node status information (interface name, time consumption, status code, etc.). Single request trace back is an effective means to diagnose the cause of specific request anomalies / timeouts, and can quickly locate abnormal nodes.
[0096] Figure 3 FIG. 1 is a schematic diagram of cross-region link tracking according to an embodiment of the present disclosure. Figure 3 As shown in FIG. 1 , the specific process of cross-region link tracking includes:
[0097] Step 1: Add the collection information field Collect Info to the Span attribute Tags of the basic object of link data. The data structure is Map <CollectInfo,Map<Key,Value> >. Among them, Map<Key,Value> Extensible: Area identification field AreaTag, the corresponding key-value pair of calling side link data is<AreaTag,Calling> ; The response status field StatusCode is normally<StatusCode,Success> , the exception is<StatusCode,Error> ; User code field UserId, when analyzing the operation information of user 123, the user code rule is<UserId,123> ; Response time field StatusTime, when analyzing a link call with a response time of 20ms, the response time rule is<StatusTime,20> ; AreaTag is a required field, and other fields can be expanded as needed.
[0098] Step 2: The calling system link enters the called system, and the protocol conversion is performed according to the rule engine. The area identification field AreaTag of the link data entering the called system changes. The area identification field AreaTag is changed from<AreaTag,Calling> becomes<AreaTag,Called> , the area identification field AreaTag can be used to determine whether the link data is cross-area data.<Key,Value> If the length is greater than 1, it means that CollectInfo includes multiple fields. In this case, the Key is traversed and further filtered according to the corresponding value of the Key to select the trace identifier TraceId that meets the cross-region data and the preset rules.
[0099] Step 3: Send the filtered trace identifier TraceId to the message middleware.
[0100] Step 4: The calling side system uploads the link data Trace to the calling side link tracking system, and the called side system uploads the link data Trace to the called side link tracking system. Determine whether the message middleware has received the tracking identifier TraceId. When the message middleware receives the tracking identifier TraceId, it obtains the corresponding cascade data from the calling side link tracking system and the called side link tracking system according to the tracking identifier TraceId. The cascade data is filtered and processed, and the preset filtering rules are read from the configuration file and can be dynamically added or deleted to further select the cascade data that meets the requirements.
[0101] Step 5, performing splicing processing on the filtered cascade data to obtain spliced data.
[0102] Step 6: convert the spliced data to convert the spliced data into standard data in a preset format.
[0103] Step 7: Visualize the standard data to obtain the tracking data, and perform single request trace back according to the tracking identifier TraceId and the calling sequence to achieve data analysis.
[0104] Through the above-mentioned embodiments, the problem that cross-region calls between the headquarters and the provincial side of the two-level business center cannot be tracked, and complete cross-region link tracking can be achieved, thereby facilitating fault location, performance tuning and user behavior analysis.
[0105] It should be noted that the method of the embodiment of the present disclosure can be performed by a single device, such as a computer or a server. The method of the present embodiment can also be applied in a distributed scenario and completed by multiple devices cooperating with each other. In the case of such a distributed scenario, one of the multiple devices can only perform one or more steps in the method of the embodiment of the present disclosure, and the multiple devices will interact with each other to complete the described method.
[0106] It should be noted that the above describes some embodiments of the present disclosure. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recorded in the claims can be performed in an order different from that in the above embodiments and still achieve the desired results. In addition, the processes depicted in the accompanying drawings do not necessarily require the specific order or continuous order shown to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.
[0107] Based on the same inventive concept, corresponding to any of the above-mentioned embodiments and methods, the present disclosure also provides a communication link tracking device.
[0108] refer to Figure 4 , the communication link tracking device comprises:
[0109] The judgment module 301 is configured to obtain link data from the called side system and judge whether the link data is cross-region data sent from the calling side system to the called side system;
[0110] The tracking identifier acquisition module 302 is configured to acquire a tracking identifier from the link data in response to determining that the link data is cross-region data sent from the calling side system to the called side system;
[0111] The cascade data acquisition module 303 is configured to acquire first cascade data from the calling side system according to the tracking identifier, and acquire second cascade data from the called side system according to the tracking identifier;
[0112] The data processing module 304 is configured to perform data processing on the first cascade data and the second cascade data to obtain tracking data.
[0113] In some embodiments, the determination module 301 includes:
[0114] An information field determination unit is configured to obtain link data from the called side system and determine the information field of the link data;
[0115] an area identification field determining unit, configured to determine the area identification field of the link data from the information field of the link data;
[0116] The cross-region data determination unit is configured to determine whether the link data is cross-region data sent from the calling side system to the called side system according to the area identification field.
[0117] In some embodiments, the tracking identifier acquisition module 302 includes:
[0118] a cross-region data determination unit configured to, in response to determining that the region identification field is changed from a calling side region to a called side region, determine that the link data is cross-region data sent from a calling side system to a called side system;
[0119] A field determination unit, configured to determine whether the information field of the link data satisfies a first preset rule;
[0120] The tracking identifier acquiring unit is configured to acquire a tracking identifier from the link data in response to determining that the information field satisfies a first preset rule.
[0121] In some embodiments, the field determination unit includes:
[0122] A field quantity acquisition subunit is configured to acquire the field quantity of the information field;
[0123] The field judgment subunit is configured to, in response to determining that the number of fields is greater than a preset number threshold, traverse the information fields and judge whether the traversed multiple information fields meet the corresponding first preset rule.
[0124] In some embodiments, the first preset rule includes at least one of the following: a response status rule, a user coding rule, and a response time rule; the field judgment subunit is specifically configured as follows:
[0125] A traversal subunit is configured to perform traversal processing on the information field to obtain at least one of a response status field, a user code field and a response time field;
[0126] a response status judgment subunit, configured to judge whether the response status field satisfies a response status rule; and / or,
[0127] A user code determination subunit is configured to determine whether the user code field satisfies a user code rule; and / or,
[0128] The response time judgment subunit is configured to judge whether the response time field satisfies the response time rule.
[0129] In some embodiments, the response status determination subunit is specifically configured to: determine whether the response status field is a response success state;
[0130] The user code determination subunit is specifically configured to: determine whether the user code field is in the first preset user list, or determine whether the user code field is not in the second preset user list;
[0131] The response time determination subunit is specifically configured to determine whether the response time field is within a preset response time.
[0132] In some embodiments, the data processing module 304 includes:
[0133] a data judging unit, configured to judge whether the first concatenated data and the second concatenated data satisfy a second preset rule;
[0134] a data splicing unit, configured to, in response to determining that the first concatenated data and the second concatenated data satisfy a second preset rule, perform splicing processing on the first concatenated data and the second concatenated data to obtain spliced data;
[0135] A data conversion unit, configured to convert the spliced data into standard data in a preset format;
[0136] The data visualization unit is configured to perform visualization processing on the standard data to obtain tracking data.
[0137] For the convenience of description, the above device is described by dividing it into various modules according to its functions. Of course, when implementing the present disclosure, the functions of each module can be implemented in the same or multiple software and / or hardware.
[0138] The device of the above embodiment is used to implement the corresponding communication link tracking method in any of the above embodiments, and has the beneficial effects of the corresponding method embodiment, which will not be repeated here.
[0139] Based on the same inventive concept, corresponding to any of the above-mentioned embodiments and methods, the present disclosure also provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the program, the communication link tracking method described in any of the above embodiments is implemented.
[0140] Figure 5 A more specific schematic diagram of the hardware structure of an electronic device provided in this embodiment is shown, and the device may include: a processor 1010, a memory 1020, an input / output interface 1030, a communication interface 1040, and a bus 1050. The processor 1010, the memory 1020, the input / output interface 1030, and the communication interface 1040 are connected to each other through the bus 1050 in the device.
[0141] The processor 1010 can be implemented by a general-purpose CPU (Central Processing Unit), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits, and is used to execute relevant programs to implement the technical solutions provided in the embodiments of this specification.
[0142] The memory 1020 may be implemented in the form of ROM (Read Only Memory), RAM (Random Access Memory), static storage device, dynamic storage device, etc. The memory 1020 may store an operating system and other application programs. When the technical solutions provided in the embodiments of this specification are implemented by software or firmware, the relevant program codes are stored in the memory 1020 and are called and executed by the processor 1010.
[0143] The input / output interface 1030 is used to connect the input / output module to realize information input and output. The input / output module can be configured in the device as a component (not shown in the figure), or it can be externally connected to the device to provide corresponding functions. The input device may include a keyboard, a mouse, a touch screen, a microphone, various sensors, etc., and the output device may include a display, a speaker, a vibrator, an indicator light, etc.
[0144] The communication interface 1040 is used to connect a communication module (not shown in the figure) to realize communication interaction between the device and other devices. The communication module can realize communication through a wired mode (such as USB (Universal Serial Bus), network cable, etc.), or through a wireless mode (such as mobile network, WIFI (Wireless Fidelity), Bluetooth, etc.).
[0145] The bus 1050 includes a path that transmits information between the various components of the device (eg, the processor 1010, the memory 1020, the input / output interface 1030, and the communication interface 1040).
[0146] It should be noted that, although the above device only shows the processor 1010, the memory 1020, the input / output interface 1030, the communication interface 1040 and the bus 1050, in the specific implementation process, the device may also include other components necessary for normal operation. In addition, it can be understood by those skilled in the art that the above device may also only include the components necessary for implementing the embodiments of the present specification, and does not necessarily include all the components shown in the figure.
[0147] The electronic device of the above embodiment is used to implement the corresponding communication link tracking method in any of the above embodiments, and has the beneficial effects of the corresponding method embodiment, which will not be described in detail here.
[0148] Based on the same inventive concept, corresponding to any of the above-mentioned embodiments, the present disclosure also provides a non-transitory computer-readable storage medium, wherein the non-transitory computer-readable storage medium stores computer instructions, and the computer instructions are used to enable the computer to execute the communication link tracking method described in any of the above embodiments.
[0149] The computer-readable medium of this embodiment includes permanent and non-permanent, removable and non-removable media, and information storage can be implemented by any method or technology. Information can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, read-only compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device.
[0150] The computer instructions stored in the storage medium of the above embodiment are used to enable the computer to execute the communication link tracking method described in any of the above embodiments, and have the beneficial effects of the corresponding method embodiments, which will not be repeated here.
[0151] Those skilled in the art should understand that the discussion of any of the above embodiments is merely illustrative and is not intended to imply that the scope of the present disclosure (including the claims) is limited to these examples. Based on the concept of the present disclosure, the technical features in the above embodiments or different embodiments may be combined, the steps may be implemented in any order, and there are many other variations of the different aspects of the embodiments of the present disclosure as described above, which are not provided in detail for the sake of simplicity.
[0152] In addition, to simplify the description and discussion, and in order not to make the embodiments of the present disclosure difficult to understand, the known power / ground connections to the integrated circuit (IC) chips and other components may or may not be shown in the provided figures. In addition, the device can be shown in the form of a block diagram to avoid making the embodiments of the present disclosure difficult to understand, and this also takes into account the fact that the details of the implementation of these block diagram devices are highly dependent on the platform on which the embodiments of the present disclosure will be implemented (that is, these details should be fully within the scope of understanding of those skilled in the art). Where specific details (e.g., circuits) are set forth to describe exemplary embodiments of the present disclosure, it is apparent to those skilled in the art that the embodiments of the present disclosure can be implemented without these specific details or with changes in these specific details. Therefore, these descriptions should be considered illustrative rather than restrictive.
[0153] Although the present disclosure has been described in conjunction with specific embodiments of the present disclosure, many replacements, modifications and variations of these embodiments will be apparent to those skilled in the art from the foregoing description. For example, other memory architectures (e.g., dynamic RAM (DRAM)) may use the embodiments discussed.
[0154] The embodiments of the present disclosure are intended to cover all such substitutions, modifications and variations that fall within the broad scope of the appended claims. Therefore, any omissions, modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the embodiments of the present disclosure should be included in the scope of protection of the present disclosure.
Claims
1. A method for tracking a communication link, characterized in that: The method comprises: Acquire link data from the called side system, and determine whether the link data is cross-region data sent from the calling side system to the called side system; In response to determining that the link data is cross-region data sent from a calling-side system to a called-side system, acquiring a tracking identifier from the link data; Acquire first cascade data from the calling side system according to the tracking identifier, and acquire second cascade data from the called side system according to the tracking identifier; Data processing is performed on the first cascade data and the second cascade data to obtain tracking data.
2. The method according to claim 1, characterized in that The acquiring link data from the called side system and determining whether the link data is cross-region data sent from the calling side system to the called side system includes: Acquire link data from the called side system and determine the information field of the link data; Determine the area identification field of the link data from the information field of the link data; It is determined according to the area identification field whether the link data is cross-area data sent from the calling side system to the called side system.
3. The method according to claim 2, characterized in that In response to determining that the link data is cross-region data sent from the calling side system to the called side system, obtaining a tracking identifier from the link data includes: In response to determining that the region identification field is changed from the calling side region to the called side region, determining that the link data is cross-region data sent from the calling side system to the called side system; Determining whether the information field of the link data satisfies a first preset rule; In response to determining that the information field satisfies a first preset rule, a tracking identifier is obtained from the link data.
4. The method according to claim 3, characterized in that The determining whether the information field of the link data satisfies a first preset rule includes: Obtaining the number of fields of the information field; In response to determining that the number of fields is greater than a preset number threshold, the information fields are traversed, and it is determined whether the traversed multiple information fields meet the corresponding first preset rule.
5. The method according to claim 4, characterized in that The first preset rule includes at least one of the following: a response status rule, a user coding rule, and a response time rule; The traversing the information fields and determining whether the traversed multiple information fields satisfy the corresponding first preset rule includes: Performing traversal processing on the information field to obtain at least one of a response status field, a user code field, and a response time field; Determining whether the response status field satisfies a response status rule; and / or, Determine whether the user code field satisfies the user code rule; and / or, It is determined whether the response time field satisfies a response time rule.
6. The method according to claim 5, characterized in that The determining whether the response status field satisfies a response status rule includes: Determine whether the response status field is in a successful response status; The determining whether the user code field satisfies the user code rule includes: Determine whether the user code field is in the first preset user list, or determine whether the user code field is not in the second preset user list; The determining whether the response time field satisfies a response time rule includes: Determine whether the response time field is within a preset response time.
7. The method according to claim 1, characterized in that The performing data processing on the first cascade data and the second cascade data to obtain tracking data includes: Determining whether the first concatenated data and the second concatenated data satisfy a second preset rule; In response to determining that the first concatenated data and the second concatenated data satisfy a second preset rule, performing splicing processing on the first concatenated data and the second concatenated data to obtain spliced data; Converting the spliced data into standard data in a preset format; The standard data is visualized to obtain tracking data.
8. A communication link tracking device, characterized in that: include: A determination module is configured to obtain link data from the called side system and determine whether the link data is cross-region data sent from the calling side system to the called side system; a tracking identifier acquisition module, configured to acquire a tracking identifier from the link data in response to determining that the link data is cross-region data sent from a calling side system to a called side system; a cascade data acquisition module, configured to acquire first cascade data from the calling side system according to the tracking identifier, and acquire second cascade data from the called side system according to the tracking identifier; The data processing module is configured to perform data processing on the first cascade data and the second cascade data to obtain tracking data.
9. An electronic device, characterized in that: The method comprises a memory, a processor and a computer program stored in the memory and executable on the processor, wherein when the processor executes the program, the method according to any one of claims 1 to 7 is implemented.
10. A non-transitory computer-readable storage medium, characterized in that: The non-transitory computer-readable storage medium stores computer instructions, and the computer instructions are used to cause a computer to execute the method according to any one of claims 1 to 7.
