A Transaction Path Tracking Method, Device and Equipment Based on a Distributed System

Abstract

The present application discloses a transaction path tracking method, device and equipment based on a distributed system, which can perform micro-service level tracking on the transaction path. The method includes: First, collect transaction data in the distributed system according to a preset file specification, and write the transaction data into a data collection file with a fixed file name. Then, perform serialization processing on it to obtain a global event tracking number, and write the global event tracking number into the data collection file with a fixed file name. Next, use the global event tracking number to traverse the transaction data in the distributed application system according to the pre-constructed global event tracking number domain to obtain the transaction details of each distributed micro-service unit. Furthermore, a tracking number range can be generated according to the global event tracking numbers of the start point and the end point of the transaction path to which the transaction data belongs, and a transaction path corresponding to the transaction data can be generated according to the transaction details corresponding to the distributed micro-service units within the tracking number range.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular, to a transaction path tracking method, device, and equipment based on a distributed system. Background Art

[0002] Currently, with the rapid development of banking business, traditional centralized application systems gradually show some drawbacks, such as a long change time window for the application system, a large scope of business impact, and difficulties in infrastructure expansion.

[0003] Therefore, the distributed microservice transformation of banking application systems has gradually become a trend. The distributed architecture has advantages such as microservices, high performance, high elasticity, low cost, and low coupling. Due to the high requirements of banking business for business continuity, each commercial bank often uses cloud infrastructure across geographical regions and data centers to achieve distributed transformation. Therefore, how to implement transaction link tracking for distributed application systems across geographical regions and data centers is one of the key technologies for realizing the operation monitoring of distributed application systems. However, the existing transaction path tracking methods are mainly based on centralized systems, and it is impossible to track the transaction path for the internal microservice status of distributed systems. Therefore, how to implement the tracking of transaction links for distributed application systems across geographical regions and data centers is an urgent problem to be solved. Summary of the Invention

[0004] The main purpose of the embodiments of this application is to provide a transaction path tracking method, device, and equipment based on a distributed system, which can serialize the transaction detail data of the distributed system and its internal microservice units, so as to track and display the transaction path at the microservice level through the association relationship of the transaction data corresponding to each microservice unit on the transaction path.

[0005] In a first aspect, the embodiments of this application provide a transaction path tracking method based on a distributed system, including:

[0006] Collect the transaction data to be tracked in the distributed system according to a preset file specification, and write the transaction data into a data collection file with a fixed file name; the transaction data includes transaction volume, success rate, processing time, and response time;

[0007] Perform serialization processing on the transaction data to obtain a global event tracking number corresponding to the transaction data, and write the global event tracking number into the data collection file with the fixed file name;

[0008] Use the global event tracking number to traverse the transaction data in the distributed application system according to the pre-constructed global event tracking number domain, and obtain the transaction details corresponding to each distributed microservice unit;

[0009] Generate a tracking number range based on the global event tracking numbers of the start and end points of the transaction path to which the transaction data belongs, and generate the transaction path corresponding to the transaction data according to the transaction details corresponding to the distributed microservice units within the tracking number range.

[0010] Optionally, after collecting the transaction data to be tracked in the distributed system according to the preset file specification and writing the transaction data into a data collection file with a fixed file name, the method further includes:

[0011] Switch the data collection file according to the date or size.

[0012] Optionally, the global event tracking number is used to concatenate the front-end and back-end distributed systems and each microservice unit within the distributed system; different microservice units within the distributed system correspond to different internal transaction serial numbers and global event tracking numbers.

[0013] Optionally, after traversing the transaction data in the distributed application system using the global event tracking number according to the pre-constructed global event tracking number domain to obtain the transaction details corresponding to each distributed microservice unit, the method further includes:

[0014] Display the transaction details corresponding to each distributed microservice unit according to different data dimensions.

[0015] In a second aspect, an embodiment of the present application further provides a transaction path tracking device based on a distributed system, including:

[0016] A collection unit, configured to collect the transaction data to be tracked in the distributed system according to the preset file specification and write the transaction data into a data collection file with a fixed file name; the transaction data includes transaction volume, success rate, processing time, and response time;

[0017] A processing unit, configured to perform serialization processing on the transaction data to obtain the global event tracking number corresponding to the transaction data, and write the global event tracking number into the data collection file with a fixed file name;

[0018] A traversal unit, configured to traverse the transaction data in the distributed application system using the global event tracking number according to the pre-constructed global event tracking number domain to obtain the transaction details corresponding to each distributed microservice unit;

[0019] A generation unit, configured to generate a tracking number range based on the global event tracking numbers of the start and end points of the transaction path to which the transaction data belongs, and generate the transaction path corresponding to the transaction data according to the transaction details corresponding to the distributed microservice units within the tracking number range.

[0020] Optionally, the device further includes:

[0021] A switching unit, configured to, after collecting the transaction data to be tracked in the distributed system according to a preset file specification and writing the transaction data into a data collection file with a fixed file name, switch the data collection file according to the date or size.

[0022] Optionally, the global event tracking number is used to concatenate the front-end and back-end distributed systems and each microservice unit inside the distributed system; different microservice units in the distributed system correspond to different internal transaction serial numbers and global event tracking numbers.

[0023] Optionally, the device further includes:

[0024] A display unit, configured to, after traversing the transaction data in the distributed application system by using the global event tracking number and according to a pre-constructed global event tracking number domain to obtain the transaction details corresponding to each distributed microservice unit, display the transaction details corresponding to each distributed microservice unit according to different data dimensions.

[0025] An embodiment of the present application further provides a transaction path tracking device based on a distributed system, including: a processor, a memory, and a system bus;

[0026] The processor and the memory are connected through the system bus;

[0027] The memory is used to store one or more programs, and the one or more programs include instructions, and when the instructions are executed by the processor, the processor is caused to execute any implementation manner of the above-mentioned transaction path tracking method based on a distributed system.

[0028] An embodiment of the present application further provides a computer-readable storage medium, in which instructions are stored, and when the instructions are run on a terminal device, the terminal device is caused to execute any implementation manner of the above-mentioned transaction path tracking method based on a distributed system.

[0029] A transaction path tracking method, device and equipment based on a distributed system provided by an embodiment of the present application first collect transaction data to be tracked in the distributed system according to a preset file specification, and write the transaction data into a data collection file with a fixed file name; wherein, the transaction data includes transaction volume, success rate, processing time, and response time. Then, the transaction data is serialized to obtain a global event tracking number corresponding to the transaction data, and the global event tracking number is written into the data collection file with a fixed file name. Next, using the global event tracking number, the transaction data in the distributed application system is traversed according to the pre-constructed global event tracking number domain to obtain the transaction details corresponding to each distributed microservice unit. Furthermore, a tracking number range can be generated according to the global event tracking numbers of the start point and the end point of the transaction path to which the transaction data belongs, and the transaction path corresponding to the transaction data can be generated according to the transaction details corresponding to the distributed microservice units within the tracking number range. Thus, the transaction detail data of the distributed system and the internal microservice units can be serialized to track the transaction path at the microservice level through the association relationship of the transaction data corresponding to each microservice unit on the transaction path. BRIEF DESCRIPTION OF THE DRAWINGS

[0030] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the following will briefly introduce the drawings required for use in the description of the embodiments or the prior art. Obviously, the following drawings are some embodiments of the present application. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative efforts.

[0031] Figure 1 It is a schematic flowchart of a transaction path tracking method based on a distributed system provided by an embodiment of the present application;

[0032] Figure 2 It is a schematic structural diagram of a transaction path tracking method based on a distributed system provided by an embodiment of the present application;

[0033] Figure 3 It is a schematic composition diagram of a transaction path tracking device based on a distributed system provided by an embodiment of the present application. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0034] At present, with the rapid development of banking business, the distributed microservices transformation of banking application systems has gradually become a trend. The distributed architecture has the advantages of microservices, high performance, high elasticity, low cost, and low coupling. Due to the high requirements of banking business for business continuity, commercial banks often adopt cloud infrastructure across geographical regions and data centers to achieve distributed transformation. Therefore, how to implement the transaction link tracking of distributed application systems across geographical regions and data centers is one of the key technologies for realizing the operation monitoring of distributed application systems. However, the existing transaction path tracking methods are mainly based on centralized systems, and it is impossible to track the transaction path for the internal microservice status of distributed systems. Therefore, how to track the transaction link of distributed application systems across geographical regions and data centers is an urgent problem to be solved.

[0035] To solve the above defects, the embodiments of the present application provide a transaction path tracking method based on a distributed system. First, according to the preset file specification, the transaction data to be tracked in the distributed system is collected, and the transaction data is written into a data collection file with a fixed file name. Among them, the transaction data includes transaction volume, success rate, processing time, and response time. Then, the transaction data is serialized to obtain the global event tracking number corresponding to the transaction data, and the global event tracking number is written into the data collection file with a fixed file name. Next, using the global event tracking number, according to the pre-constructed global event tracking number domain, the transaction data in the distributed application system is traversed to obtain the transaction details corresponding to each distributed microservice unit. Furthermore, according to the global event tracking numbers of the start point and the end point of the transaction path to which the transaction data belongs, a tracking number range is generated, and according to the transaction details corresponding to the distributed microservice units within the tracking number range, the transaction path corresponding to the transaction data is generated. Thus, it is possible to serialize the transaction detail data of the distributed system and its internal microservice units, and track the transaction path at the microservice level through the association relationship of the transaction data corresponding to each microservice unit on the transaction path.

[0036] To make the objectives, technical solutions, and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are some, but not all, of the embodiments of the present application. All other embodiments obtained by those of ordinary skill in the art based on the embodiments of the present application without creative efforts shall fall within the protection scope of the present application.

[0037] First Embodiment

[0038] See Figure 1 , which is a schematic flowchart of a transaction path tracking method based on a distributed system provided in this embodiment. The method includes the following steps:

[0039] S101: Collect the transaction data to be tracked in the distributed system according to the preset file specification, and write the transaction data into a data collection file with a fixed file name. Among them, the transaction data includes transaction volume, success rate, processing time, and response time.

[0040] In this embodiment, in order to track the transaction link of a distributed application system across geographical regions and data centers, for example, as Figure 2 shown, when there is data exchange between Center 1 and Center 2, in order to track the transaction link therein, it is first necessary to define the domain of the data collection file storing the transaction data, and set the standard format of the file. For example, the data collection file can be preset as the format of an Excel table. Each column in this table can respectively represent information such as the internal transaction serial number corresponding to the transaction data, transaction volume, success rate, processing time, response time, global event tracking number (such as number 1001, etc.). Based on this, the transaction data to be tracked in the distributed system can be collected according to the preset file specification, and the collected transaction data can be written into a data collection file with a fixed file name. For example, it can be written into an Excel table with a fixed file name determined according to business classification. For example, the transaction data belonging to business classification 1 can be written into data collection table 1, and the transaction data belonging to business classification 2 can be written into data collection table 2, etc. Among them, the transaction data includes transaction information such as transaction volume, success rate, processing time, and response time.

[0041] In a possible implementation manner of this embodiment, for the data collection file with a fixed file name, it can be switched according to the date or size to improve the data processing efficiency.

[0042] S102: Serialize the transaction data to obtain the global event tracking number corresponding to the transaction data, and write the global event tracking number into the data collection file with a fixed file name.

[0043] In this embodiment, in order to track the transaction link of a distributed application system across geographical regions and data centers, it is also necessary to pre-define the internal transaction serial number field. Different internal transaction serial numbers represent different distributed microservice units. For example, microservice unit 1 represents Center 1, and microservice unit 2 represents Center 2, etc. In this way, after the transaction data such as transaction volume, success rate, processing time, and response time are collected in real time by the second level through step S101, the transaction detail data of each microservice unit in the distributed system can be serialized to obtain the global event tracking number corresponding to the transaction data, and the global event tracking number is written into the data collection file with a fixed file name. Among them, the global event tracking number is used to concatenate the front-end and back-end distributed systems and the microservice units inside the distributed system.

[0044] S103: Use the global event tracking number to traverse the transaction data in the distributed application system according to the pre-constructed global event tracking number domain, and obtain the transaction details corresponding to each distributed microservice unit.

[0045] In this embodiment, after obtaining the global event tracking number corresponding to the transaction data through step S102, further use the global event tracking number to traverse the transaction data in the distributed application system according to the pre-constructed global event tracking number domain, and obtain the transaction details corresponding to each distributed microservice unit. Specifically, the transaction data in the data collection file of the distributed application system can be traversed through the global event tracking number domain. If the start and end sequence numbers in the file name are within this global tracking number range, the corresponding transaction details can be searched. Starting from the record with the sender node number being empty, the transaction records are concatenated through fields such as the receiver node number and the transaction sequence number.

[0046] It should be noted that the distributed system differentiates internal microservice units through the internal transaction sequence number domain, that is, different microservice units correspond to different internal transaction sequence numbers and global event tracking numbers.

[0047] S104: Generate a tracking number range according to the global event tracking numbers at the start and end of the transaction path to which the transaction data belongs, and generate the transaction path corresponding to the transaction data according to the transaction details corresponding to the distributed microservice units within the tracking number range.

[0048] In this embodiment, after obtaining the transaction details corresponding to each distributed microservice unit through step S103, further the transaction details corresponding to each distributed microservice unit can be displayed according to different data dimensions, that is, different views are used to display different business data, and early warnings are given to the index data through baseline management.

[0049] For example: The transaction volume view can be used to display the transaction volume of the distributed system and each microservice unit, and supports real-time refresh and summarization by time. The success rate view is used to display the business success rate of the currently selected distributed system and each microservice unit, and supports real-time refresh and summarization by time. And the processing time view and the response time view are used to display the application logic processing time-consuming of the currently selected distributed system and each microservice unit and the response time of the backend system, and support real-time refresh and summarization by time, etc.

[0050] On this basis, further, a tracking number range can be generated according to the global event tracking numbers of the start point and the end point of the transaction path to which the transaction data belongs, and an end-to-end transaction path can be formed by the distributed microservice units within the tracking number range according to the transaction details corresponding to the distributed microservice units within the tracking number range, serving as the transaction path corresponding to the transaction data, thereby realizing the tracking of the transaction path of the distributed system.

[0051] In this way, through the above steps S101 - S104, the transaction details of each microservice unit of the banking distributed system are collected, processed, and drilled down, and the transaction processing status and early warning of the distributed system are displayed in real time through the comparison with the baseline data. Through the end-to-end transaction data processing, the tracking of the transaction path of the distributed system is realized.

[0052] In summary, a transaction path tracking method based on a distributed system provided in this embodiment first collects the transaction data to be tracked in the distributed system according to a preset file specification and writes the transaction data into a data collection file with a fixed file name; where the transaction data includes transaction volume, success rate, processing time, and response time. Then, the transaction data is serialized to obtain the global event tracking number corresponding to the transaction data and the global event tracking number is written into the data collection file with a fixed file name. Next, using the global event tracking number, the transaction data in the distributed application system is traversed according to the pre-constructed global event tracking number domain to obtain the transaction details corresponding to each distributed microservice unit. Furthermore, a tracking number range can be generated according to the global event tracking numbers of the start point and the end point of the transaction path to which the transaction data belongs, and a transaction path corresponding to the transaction data can be generated according to the transaction details corresponding to the distributed microservice units within the tracking number range. Thus, the transaction detail data of the distributed system and its internal microservice units can be serialized to track the transaction path at the microservice level through the association relationship of the transaction data corresponding to each microservice unit on the transaction path.

[0053] Second Embodiment

[0054] This embodiment will introduce a transaction path tracking device based on a distributed system. For related content, please refer to the above method embodiment.

[0055] See Figure 3 , which is a schematic diagram of the composition of a transaction path tracking device based on a distributed system provided in this embodiment. The device includes:

[0056] A collection unit 301, configured to collect the transaction data to be tracked in the distributed system according to a preset file specification and write the transaction data into a data collection file with a fixed file name; the transaction data includes transaction volume, success rate, processing time, and response time;

[0057] A processing unit 302, configured to serialize the transaction data to obtain a global event tracking number corresponding to the transaction data, and write the global event tracking number into a data acquisition file with a fixed file name;

[0058] A traversal unit 303, configured to use the global event tracking number to traverse the transaction data in the distributed application system according to a pre-constructed global event tracking number domain, so as to obtain transaction details corresponding to each distributed microservice unit;

[0059] A generation unit 304, configured to generate a tracking number range according to the global event tracking numbers of the start point and the end point of the transaction path to which the transaction data belongs, and generate a transaction path corresponding to the transaction data according to the transaction details corresponding to the distributed microservice units within the tracking number range.

[0060] In an implementation manner of this embodiment, the device further includes:

[0061] A switching unit, configured to switch the data acquisition file according to the date or size after collecting the transaction data to be tracked in the distributed system according to a preset file specification and writing the transaction data into a data acquisition file with a fixed file name.

[0062] In an implementation manner of this embodiment, the global event tracking number is used to connect the front-end and back-end distributed systems and each microservice unit inside the distributed system; different microservice units in the distributed system correspond to different internal transaction serial numbers and global event tracking numbers.

[0063] In an implementation manner of this embodiment, the device further includes:

[0064] A display unit, configured to display the transaction details corresponding to each distributed microservice unit according to different data dimensions after using the global event tracking number to traverse the transaction data in the distributed application system according to a pre-constructed global event tracking number domain to obtain the transaction details corresponding to each distributed microservice unit.

[0065] In summary, a transaction path tracking device based on a distributed system provided in this embodiment first collects transaction data to be tracked in the distributed system according to a preset file specification, and writes the transaction data into a data collection file with a fixed file name. The transaction data includes transaction volume, success rate, processing time, and response time. Then, the transaction data is serialized to obtain a global event tracking number corresponding to the transaction data, and the global event tracking number is written into the data collection file with a fixed file name. Next, using the global event tracking number, the transaction data in the distributed application system is traversed according to the pre-constructed global event tracking number domain to obtain transaction details corresponding to each distributed microservice unit. Furthermore, a tracking number range can be generated based on the global event tracking numbers of the start and end points of the transaction path to which the transaction data belongs, and a transaction path corresponding to the transaction data can be generated based on the transaction details corresponding to the distributed microservice units within the tracking number range. Thus, the transaction detail data of the distributed system and the internal microservice units can be serialized to track the transaction path at the microservice level through the association relationship of the transaction data corresponding to each microservice unit on the transaction path.

[0066] Further, an embodiment of the present application also provides a transaction path tracking device based on a distributed system, including: a processor, a memory, and a system bus;

[0067] The processor and the memory are connected through the system bus;

[0068] The memory is used to store one or more programs, and the one or more programs include instructions that, when executed by the processor, cause the processor to execute any implementation method of the above-mentioned transaction path tracking method based on a distributed system.

[0069] Further, an embodiment of the present application also provides a computer-readable storage medium, in which instructions are stored. When the instructions run on a terminal device, the terminal device is caused to execute any implementation method of the above-mentioned transaction path tracking method based on a distributed system.

[0070] From the description of the above embodiments, those skilled in the art can clearly understand that all or part of the steps in the above embodiment methods can be implemented by means of software plus a necessary general hardware platform. Based on such an understanding, the technical solution of the present application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. The computer software product can be stored in a storage medium, such as ROM / RAM, magnetic disk, optical disk, etc., and includes several instructions for causing a computer device (which can be a personal computer, a server, or a network communication device such as a media gateway, etc.) to execute the methods described in each embodiment or some parts of the embodiments of the present application.

[0071] It should be noted that the embodiments in this specification are described in a progressive manner. Each embodiment focuses on the differences from other embodiments. For the similarities and common parts among the embodiments, reference can be made to each other. For the devices disclosed in the embodiments, since they correspond to the methods disclosed in the embodiments, the descriptions are relatively simple. For the relevant parts, reference can be made to the descriptions in the method section.

[0072] It should also be noted that in this text, relational terms such as "first" and "second" are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any actual relationship or order between these entities or operations. Moreover, the term "comprising", "including" or any other variant thereof is intended to cover non-exclusive inclusion, so that a process, method, article or device comprising a series of elements not only includes those elements, but also includes other elements not expressly listed, or further includes elements inherent to such process, method, article or device. Without further limitation, an element defined by the statement "comprising one..." does not exclude the existence of additional identical elements in the process, method, article or device comprising the said element.

[0073] The above description of the disclosed embodiments enables those skilled in the art to implement or use the present application. Various modifications to these embodiments will be obvious to those skilled in the art, and the general principles defined herein can be implemented in other embodiments without departing from the spirit or scope of the present application. Therefore, the present application will not be limited to the embodiments shown herein, but will be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A transaction path tracking method based on a distributed system, characterized in that, Including: Collect the transaction data to be tracked in the distributed system according to the preset file specification, and write the transaction data into a data collection file with a fixed file name; the transaction data includes transaction volume, success rate, processing time, and response time; Perform serialization processing on the transaction data to obtain the global event tracking number corresponding to the transaction data, and write the global event tracking number into the data collection file with the fixed file name; Use the global event tracking number to traverse the transaction data in the data collection file of the distributed system according to the pre-constructed global event tracking number domain. If the start and end sequence numbers in the file name are within this global tracking number range, the corresponding transaction details can be searched to obtain the transaction details corresponding to each distributed microservice unit; Generate a tracking number range according to the global event tracking numbers of the start and end points of the transaction path to which the transaction data belongs, and generate the transaction path corresponding to the transaction data according to the transaction details corresponding to the distributed microservice units within the tracking number range.

2. The method according to claim 1, wherein After collecting the transaction data to be tracked in the distributed system according to the preset file specification and writing the transaction data into a data collection file with a fixed file name, the method further includes: Switch the data collection file according to the date or size.

3. The method according to claim 1, wherein The global event tracking number is used to concatenate the front-end and back-end distributed systems and each microservice unit inside the distributed system; different microservice units inside the distributed system correspond to different internal transaction sequence numbers and global event tracking numbers.

4. The method according to claim 1, wherein After using the global event tracking number to traverse the transaction data in the data collection file of the distributed system according to the pre-constructed global event tracking number domain, and if the start and end sequence numbers in the file name are within this global tracking number range, the corresponding transaction details can be searched to obtain the transaction details corresponding to each distributed microservice unit, the method further includes: Display the transaction details corresponding to each distributed microservice unit according to different data dimensions.

5. A transaction path tracking device based on a distributed system, characterized in that, Including: A collection unit, configured to collect the transaction data to be tracked in the distributed system according to the preset file specification, and write the transaction data into a data collection file with a fixed file name; the transaction data includes transaction volume, success rate, processing time, and response time; A processing unit, configured to perform serialization processing on the transaction data to obtain the global event tracking number corresponding to the transaction data, and write the global event tracking number into the data collection file with the fixed file name; A traversal unit, configured to use the global event tracking number to traverse the transaction data in the data collection file of the distributed system according to the pre-constructed global event tracking number domain. If the start and end sequence numbers in the file name are within this global tracking number range, the corresponding transaction details can be searched to obtain the transaction details corresponding to each distributed microservice unit; A generating unit, configured to generate a range of tracking numbers according to the global event tracking numbers of the start point and the end point of the transaction path to which the transaction data belongs, and generate a transaction path corresponding to the transaction data according to the transaction details corresponding to the distributed microservice units within the range of tracking numbers.

6. The device according to claim 5, characterized in that The apparatus further includes: A switching unit, configured to switch the data acquisition file according to the date or size after collecting the transaction data to be tracked in the distributed system according to a preset file specification and writing the transaction data into a data acquisition file with a fixed file name.

7. The device according to claim 5, characterized in that, The global event tracking number is used to concatenate the front-end and back-end distributed systems and each microservice unit inside the distributed system; different microservice units inside the distributed system correspond to different internal transaction serial numbers and global event tracking numbers.

8. The device according to claim 5, characterized in that, The apparatus further includes: A display unit, configured to traverse the transaction data in the data acquisition file of the distributed system by using the global event tracking number according to a pre-constructed global event tracking number domain, and if the start and end sequence numbers in the file name are within the range of this global tracking number, the corresponding transaction details can be searched to obtain the transaction details corresponding to each distributed microservice unit, and then display the transaction details corresponding to each distributed microservice unit according to different data dimensions.

9. A transaction path tracking device based on a distributed system, characterized in that, Comprising: A processor, a memory, and a system bus; The processor and the memory are connected through the system bus; The memory is used to store one or more programs, and the one or more programs include instructions, and when the instructions are executed by the processor, the processor is caused to execute the method according to any one of claims 1-4.

10. A computer-readable storage medium, characterized in that, Instructions are stored in the computer-readable storage medium, and when the instructions are run on the terminal device, the terminal device is caused to execute the method according to any one of claims 1-4.

Images