WO2024002232A1

WO2024002232A1 - Data processing method, apparatus and system, edge server, electronic device, and storage medium

Info

Publication number: WO2024002232A1
Application number: PCT/CN2023/103799
Authority: WO
Inventors: 胡锐; 刘学生; 李小进; 龚辉
Original assignee: 中兴通讯股份有限公司
Priority date: 2022-07-01
Filing date: 2023-06-29
Publication date: 2024-01-04
Also published as: CN117370297A

Abstract

The present application relates to the technical field of data processing, and provides a data processing method, a data processing apparatus, an edge server, a data processing system, an electronic device, and a computer readable storage medium. The data processing method comprises: when it is determined that first call chain data is data corresponding to a service based on a cross-data center, marking the first call chain data to generate a cross-domain identifier; and storing the cross-domain identifier and the first call chain data in the edge server, so that the edge server synchronizes the first call chain data to a central server.

Description

Data processing methods, devices and systems, edge servers, electronic equipment, storage media

Cross-references to related applications

This application claims priority from Chinese patent application No. 202210767296.4 filed on July 1, 2022. The contents of this Chinese patent application are incorporated herein by reference in their entirety.

Technical field

This application relates to the field of data processing technology, specifically to data processing methods, data processing devices, edge servers, data processing systems, electronic equipment and computer-readable storage media.

Background technique

At present, an enterprise can establish branches in multiple places and build communication connections between multiple branches through the distributed network within the enterprise. In the process of data operation and maintenance between multiple branches, it is usually necessary to A distributed call chain is used to realize data transmission.

However, in the process of calling data across data centers, incomplete call chain collection failures are prone to occur, which reduces the operation and maintenance efficiency of the entire system; and the related centralized storage method of call chain information across data centers is also It is easy to cause data to occupy a large amount of private network bandwidth during transmission and reduce data transmission efficiency.

public content

In a first aspect, embodiments of the present application provide a data processing method, including: when it is determined that the first call chain data is based on data corresponding to cross-data center services, marking the first call link data and generating a cross-data center data processing method. Domain identification; and saving the cross-domain identification and the first call chain data to the edge server, so that the edge server can synchronize the first call chain data to the central server.

In a second aspect, embodiments of the present application provide a data processing method, which includes: obtaining a cross-domain identifier and first call chain data sent by a data processing device, where the first call chain data is data corresponding to services based on cross-data centers; generating a storage identifier corresponding to the first call chain data; saving the cross-domain identifier and the first call chain data according to the storage identifier; and synchronizing the first call chain data to the central server.

In a third aspect, embodiments of the present application provide a data processing device, including: a marking module configured to, when it is determined that the first call chain data is based on data corresponding to cross-data center services, marking and generating a cross-domain identification; and a storage module configured to save the cross-domain identification and the first call chain data to the edge server, so that the edge server can synchronize the first call chain data to the central server.

In the fourth aspect, embodiments of the present application provide an edge server, including: an acquisition module configured to acquire the cross-domain identification and first call chain data sent by the data processing device. The first call chain data is based on business correspondence across data centers. data; a generation module configured to generate a storage identifier corresponding to the first call chain data; a save module configured to save the cross-domain identifier and the first call chain data based on the storage identifier; and a synchronization module configured to save the first call chain data Data is synchronized to the central server.

In a fifth aspect, embodiments of the present application provide a data processing system, including: a communication-connected data processing device, an edge server, and a central server; a data processing device configured to execute the first step of the present application. The data processing method in the second aspect; the edge server is configured to execute the data processing method in the second aspect of this application; the central server is configured to obtain the first call chain data synchronized by the edge server; in response to the query request sent by the user terminal, based on The query identifier in the query request obtains the first call chain data, and feeds the first call chain data back to the user terminal; the first call chain data is based on business correspondence across data centers.

In a sixth aspect, embodiments of the present application provide an electronic device, including: at least one processor; and a memory on which at least one computer program is stored. When the at least one computer program is executed by at least one processor, at least one process The device implements the data processing method in the embodiment of this application.

In a seventh aspect, embodiments of the present application provide a computer-readable storage medium. The computer-readable storage medium stores a computer program. When the computer program is executed by a processor, the data processing method in the embodiment of the present application is implemented.

Regarding the above embodiments and other aspects of the application and the manner in which they may be implemented, further description is provided in the description of the drawings, the detailed description and the claims.

Description of drawings

Figure 1 shows a schematic flowchart of a method for processing call chain data between different data centers provided by an embodiment of the present application.

Figure 2 shows a schematic diagram of a processing system for call chain data reported across clouds provided by an embodiment of the present application.

Figure 3 shows a schematic diagram of the processing system for cross-cloud query call chain data provided by the embodiment of the present application.

Figure 4 shows a schematic flowchart of the data processing method provided by the embodiment of the present application.

Figure 5 shows a schematic diagram of the query front-end interface provided by the embodiment of the present application.

Figure 6 shows a schematic diagram of the statistics front-end interface provided by the embodiment of the present application.

Figure 7 shows a schematic flowchart of the data processing method provided by the embodiment of the present application.

Figure 8 shows a block diagram of the data processing system provided by the embodiment of the present application.

Figure 9 shows a block diagram of the data processing system provided by the embodiment of the present application.

Figure 10 shows a schematic flowchart of the working method of the data processing system provided by the embodiment of the present application.

Figure 11 shows a schematic flowchart of a method for collecting first call chain data provided by an embodiment of the present application.

Figure 12 shows a schematic flowchart of a method for processing first call chain data by an edge call chain server provided by an embodiment of the present application.

Figure 13 shows a schematic flowchart of the first call chain data query method provided by the embodiment of the present application.

Figure 14 shows a schematic flowchart of a method for processing call chain data corresponding to financial microservices in the financial system provided by the embodiment of the present application.

Figure 15 shows a schematic flowchart of a method for processing call chain data corresponding to a charging microservice in a communication operator's charging system provided by an embodiment of the present application.

Figure 16 shows a schematic flowchart of a method for processing call chain data corresponding to a cloud-based game scene microservice provided by an embodiment of the present application.

Figure 17 shows a block diagram of a data processing device provided by an embodiment of the present application.

Figure 18 shows a block diagram of the edge server provided by the embodiment of the present application.

Figure 19 shows a structural diagram of an exemplary hardware architecture of a computing device capable of implementing the data processing method and apparatus according to embodiments of the present application.

Detailed ways

In order to make the purpose, technical solutions and advantages of the present application more clear, the embodiments of the present application will be described in detail below with reference to the accompanying drawings. It should be noted that, as long as there is no conflict, the embodiments in this application and the features in the embodiments can be arbitrarily combined with each other.

With the rapid expansion of Internet business, software architecture has become increasingly complex. In order to adapt to the high concurrent requests of massive users, more and more components in the system have begun to adopt distributed architecture. For example, the monolithic architecture is split into multiple microservice architectures, the in-service cache is turned into a distributed cache; the communication between service components adopts the interaction of distributed communication messages, etc. Different components make the distributed network become More complex and difficult to manage.

With the increase in the complexity of communication systems and users' needs for disaster recovery and other aspects, in government and enterprise distributed application scenarios, more and more enterprises will adopt the "two places and three centers" model to build their own communication networks . For example, FIG. 1 shows a schematic flowchart of a method for processing call chain data between different data centers provided by an embodiment of the present application. As shown in FIG. 1 , the main center server 110 is communicatively connected with the local disaster recovery center server 120 and the remote disaster recovery center server 130 .

The main center server 110 needs to perform data synchronization with the local disaster recovery center server 120, and the local disaster recovery center server 120 also needs to perform asynchronous log replay and other services with the remote disaster recovery center server 130.

In the process of processing different business data, the first application may call data across multiple data centers (for example, the first application on the local disaster recovery center server 120 calls the main center server 110 The data on the data nodes corresponding to the first group 111, or the data on the data nodes corresponding to the second group 112, or the data on the data nodes corresponding to the third group 113, etc.), and the first application may also Interact with second applications deployed on other data centers (for example, interact between the first application on the local disaster recovery center server 120 and the second application on the remote disaster recovery center server 130, etc.). In the above process, the call chain data is based on the data corresponding to the business across data centers, which is prone to incomplete collection of the call chain and reduces the operation and maintenance efficiency of the entire system. Moreover, since data are all centrally stored on the main central server 110, it is easy for the main central server 110 to occupy a large amount of private network bandwidth and reduce data transmission efficiency when interacting with other servers.

Figure 2 shows a schematic diagram of a processing system for call chain data reported across clouds provided by an embodiment of the present application. As shown in Figure 2, when application D in the self-built computer room transmits data to the public network access point on the public cloud, it will occupy the public network bandwidth and private network bandwidth. However, the cost of public network traffic, and the public network There are many limitations on network stability, which reduces the user experience of Application D.

Cross-cloud query means that the original link data is stored in the current cloud network, and a user's query request is sent to multiple cloud servers respectively, so that multiple cloud servers can aggregate the query results and then perform unified processing, which can reduce Transmission costs in the public network.

Figure 3 shows a schematic diagram of the processing system for cross-cloud query call chain data provided by the embodiment of the present application. As shown in 3, when application C in the self-built computer room interacts with an application in the public cloud (for example, application A or application B) through the intranet access point, multiple data processing terminals need to be deployed in the public cloud. , for access by multiple applications, but the public cloud does not support functions such as statistical analysis of quantile and global call chain data, which reduces the management efficiency of call chain data in the network.

Embodiments of the present application provide a data processing method, a data processing device, an edge server, a data processing system, an electronic device, and a computer-readable storage medium.

Figure 4 shows a schematic flowchart of the data processing method provided by the embodiment of the present application. The data processing method can be applied to data processing devices. As shown in Figure 4, the data processing method in the embodiment of the present application includes but is not limited to the following steps S401 and S402.

Step S401: When it is determined that the first call chain data is based on data corresponding to cross-data center services, mark the first call link data and generate a cross-domain identification.

Step S402: Save the cross-domain identification and the first call chain data to the edge server, so that the edge server can synchronize the first call chain data to the central server.

In the data processing method provided by this application, when it is determined that the first call chain data is based on data corresponding to cross-data center services, the first call link data is marked to generate a cross-domain identifier to distinguish Other call chain data that do not operate cross-domain, reduce the proportion of incomplete call chain collection failures, and ensure the integrity of data corresponding to cross-data center business analysis; save cross-domain identification and first call chain data to the edge server, for the edge server to transfer the first call chain number Data synchronization to the central server can reduce the storage space wasted due to centralized storage of call chain data, reduce the frequency of reporting call chain data, improve data transmission efficiency, and reduce the consumption of private network bandwidth.

In some embodiments, after performing step S402 of saving the cross-domain identification and the first call chain data to the edge server for the edge server to synchronize the first call chain data to the central server, the data processing method further includes :

Send a synchronization request to the edge server for the edge server to synchronize the first call chain data to the central server according to the target address in the synchronization request; and respond to the synchronization response fed back by the central server to determine that the edge server has completed the first call chain data synchronization.

The destination address is the network address of the central server.

By sending a synchronization request to the edge server, the edge server can synchronize the first call chain data to the central server based on the target address in the synchronization request, so that the central server can obtain cross-data center call chain data to facilitate subsequent data analysis. , and ensure that when analyzing call chain data, the proportion of incomplete call chain collection failures is reduced and the accuracy of data analysis is improved.

In some embodiments, after performing step S402 of saving the cross-domain identification and the first call chain data to the edge server for the edge server to synchronize the first call chain data to the central server, the data processing method further includes : Obtain the query request; and query the edge server and/or central server according to the query identifier to obtain the first call chain data.

The query request includes a query identifier, and the query identifier corresponds to the storage identifier of the first call chain data.

For example, a query request can be sent to the edge server and/or the central server. When a server stores the first call chain data corresponding to the query identifier, the first call chain data can be obtained.

Because the call chain data based on cross-data centers is not only stored on the central server, but also on the edge server, sending query requests to the edge server and/or the central server can facilitate different devices to access this cross-data center call chain. Query and use data to reduce the proportion of faults caused by incomplete call chain collection.

In some embodiments, after querying the edge server and/or the central server according to the query identifier and obtaining the first call chain data, the data processing method further includes: based on the tree structure, displaying the corresponding data of the first call chain The category of the data center to which the microservice belongs; and/or, based on the graph structure, display the processing time information of the microservice corresponding to the first call chain data.

For example, FIG. 5 shows a schematic diagram of the query front-end interface provided by the embodiment of the present application. As shown in Figure 5, the left half of Figure 5 uses a tree structure to respectively display microservice 1, microservice 2 and public services included in data center 1; and microservice 3 and microservice 4 included in data center 2. For example, if microservice 1 corresponds to the first call chain data, the right half of Figure 5 will display the calling process of the first call chain data based on the graph structure (for example, the "Call Chain Display" in Figure 5). This allows users to clearly view the calling process of the call chain data corresponding to different microservices.

traceId represents the query identifier (such as 12445, etc.) for the user to input the query identifier they want to query, and click the "Query" button to obtain relevant information about the call chain data corresponding to the query identifier, and intuitively display the call chain data to users to improve the user experience.

In some embodiments, the data processing method further includes: when it is determined that the second call chain data is based on data corresponding to services occurring in the same data center, saving the second call chain data to the edge server.

It should be noted that the call chain data corresponding to the business occurring in the same data center does not need to be aggregated to the central server, thus saving the storage space of the central server. At the same time, it also reduces the consumption of private network bandwidth during data interaction. consumption, reducing the cost of network communication.

In some embodiments, when it is determined that the first call chain data is based on data corresponding to cross-data center services in step S401, before marking the first call link data and generating a cross-domain identification, the The above data processing methods also include:

Obtain the registration information of the microservice corresponding to the first call chain data from the registration server; obtain the storage address of the target data corresponding to the first call chain data; and based on the registration address of the microservice and the first call chain data Use the storage address of the target data corresponding to the chain data to determine whether the first call chain data is based on data corresponding to cross-data center services.

The registration information includes the registration address of the microservice; the target data is the data that the microservice expects to obtain.

By comparing the registration address of the microservice and the storage address of the target data corresponding to the first call chain data, it can be clarified whether the microservice needs to use data from other data centers when processing business data.

When it is determined that the registration address of the microservice is different from the storage address of the target data corresponding to the first call chain data, it is determined that the first call chain data corresponding to the microservice is data corresponding to the business based on the cross-data center; after determining When the registration address of the microservice is the same as the storage address of the target data corresponding to the first call chain data, it is determined that the first call chain data corresponding to the microservice is not based on data corresponding to cross-data center business, that is, the first call Chain data is the call chain data corresponding to the business occurring in the data center.

Based on the determination of the type of the first call chain data, it can be clarified whether the first call chain data needs to be synchronized to the central server, thereby reducing the consumption of transmission bandwidth during data transmission and saving transmission costs.

In some implementations, the first call chain data is data corresponding to financial microservices in the financial system. Saving the cross-domain identification and the first call chain data to the edge server in step S402, so that the edge server can synchronize the first call chain data to the central server, can be implemented in the following manner:

At each preset interval (for example, 3 hours, or 5 hours, etc.), the storage address corresponding to the first call chain data is obtained from the edge server; based on the storage address corresponding to the first call chain data and the network address of the central server, a generated a synchronization request; and sending a synchronization request to the edge server for the edge server to synchronize the first call chain data to the central server based on the storage address corresponding to the first call chain data and the network address of the central server.

The storage address corresponding to the first call chain data is an address determined by the edge server based on the data offset information of the last time it obtained the call chain data.

For example, the data offset information of the last time the call chain data was obtained includes the storage address offset length and the storage first address. Then the storage address offset length and the storage first address can be added together to obtain the first call chain data correspondence. storage address, thereby speeding up the acquisition of the first call chain data.

By obtaining the storage address corresponding to the first call chain data, the first call chain data can be quickly and accurately obtained. Then, based on the network address of the central server, a synchronization request is sent to the edge server, so that the edge server can send the first call chain data to the central server based on the network address of the central server, speeding up the synchronization efficiency of the first call chain data, Ensure safe storage of data.

In some embodiments, the first call chain data is data corresponding to the charging microservice in the charging system of the communication operator (for example, data generated by querying bills, etc., or charging standards, etc.). Saving the cross-domain identification and the first call chain data to the edge server in step S402, so that the edge server can synchronize the first call chain data to the central server, can be implemented in the following manner:

Analyze the first call chain data to determine the billing area information to which the billing microservice corresponding to the first call chain data belongs; and according to the billing area level corresponding to the billing microservice, combine the cross-domain identification and the first call chain The data is saved to the edge server corresponding to the billing area level.

The charging area information includes the charging area level corresponding to the charging microservice. For example, the charging area level may include at least one of a provincial charging area, a municipal charging area, and a county charging area.

By obtaining the billing area level corresponding to the billing microservice, the specific billing standard can be clarified, and the cross-domain identification and first call chain data can be quickly and accurately saved to the edge server corresponding to the billing area level to facilitate the edge. The server performs billing to ensure the normal communication of terminals and protect the interests of operators.

In some implementations, the first call chain data is data corresponding to the cloud-based game scene microservice. The game scene microservice includes the game scene rendering microservice and its corresponding billing microservice. The game scene rendering microservice is deployed at the edge. On the server, the target data of the billing microservice corresponding to the game scene rendering microservice is stored on the public cloud server.

For example, when a terminal needs to render a game scene, it needs to be served through the game scene rendering microservice deployed on the nearest edge server. However, correspondingly, the cost information generated by the game scene rendering needs to be provided through the game scene rendering microservice deployed on the public cloud. The billing microservice is implemented on the server, thus generating the first call chain data across data centers.

By deploying the game scene rendering microservice on the edge server, it is convenient for the terminal to obtain the data it needs from the edge server, improving the service efficiency with the terminal; and the goal of the billing microservice corresponding to the game scene rendering microservice is Data is stored on the public cloud server, which enables the public cloud server to accurately bill services performed on multiple different edge servers, improving billing accuracy.

In some embodiments, after the cross-domain identification and the first call chain data are saved to the edge server so that the edge server can synchronize the first call chain data to the central server, the data processing further includes: sending the data to the public cloud server. Send a data statistics request; respond to the statistical response fed back by the public cloud server, obtain statistical results; and display the statistical results.

The data statistics request is used to count information on the use of a preset amount of call chain data within a preset period of time. The statistical results may include: at least one of: statistical start time, statistical end time, statistical type, and usage information corresponding to the call chain data.

For example, FIG. 6 shows a schematic diagram of the statistics front-end interface provided by the embodiment of the present application. As shown in Figure 6, the user enters the start time and end time to be counted in the "Statistical Time Period" input window, and enters the statistical type corresponding to the call chain data expected to be obtained in the "Statistical Type" and clicks " "Statistics Button" will display in the "Statistical Result Display" the information used by the preset number of call chain data determined based on the statistical type during the period from the start time to the end time.

Through the above statistics of call chain data, the call status of the call chain data corresponding to a certain statistical type on the public cloud server can be clarified, which facilitates the query of users or operation and maintenance personnel, so that based on the display of statistical results, it is possible to quickly and easily locate possible Improve the efficiency of management and maintenance of call chain data by handling failures.

Figure 7 shows a schematic flowchart of the data processing method provided by the embodiment of the present application. This method can be applied to edge servers. As shown in Figure 7, the data processing method in the embodiment of the present application includes but is not limited to the following steps S701 to S704.

Step S701: Obtain the cross-domain identifier and first call chain data sent by the data processing device.

The first call chain data is based on business correspondence across data centers.

Step S702: Generate a storage identifier corresponding to the first call chain data.

Step S703: Save the cross-domain identifier and the first call chain data according to the storage identifier.

Step S704: Synchronize the first call chain data to the central server.

In some implementations, synchronizing the first call chain data to the central server in step S704 includes: responding to the synchronization request sent by the data processing device, obtaining the target address in the synchronization request; and synchronizing the first call chain data according to the target address. Synchronize to central server.

The destination address is the network address of the central server.

In the data processing method provided by this application, by obtaining the cross-domain identification and the first call chain data sent by the data processing device, it can be determined based on the cross-domain identification that the first call chain data is data corresponding to the business across data centers, and it can Distinguish cross-data center call chain data from other call chain data that does not cross-domain operations to reduce the proportion of incomplete call chain collection failures; generate a storage identifier corresponding to the first call chain data, and save the cross-domain call chain data based on the storage identifier. Domain identification and first call chain data can reduce the frequency of call chain data reported to the central server and improve data transmission efficiency; synchronize the first call chain data to the central server so that the central server can handle cross-data center business The corresponding data is analyzed to meet the needs of data analysis and reduce the storage space of the central server wasted due to centralized storage of call chain data.

Figure 8 shows a block diagram of the data processing system provided by the embodiment of the present application. As shown in Figure 8, the data processing system includes but is not limited to the following equipment: a communication-connected data processing device 801, an edge server 802, a central server 803, and a user terminal 804.

The data processing device 801 is configured to determine that the first call chain data is based on cross-data center services. In the case of corresponding data, the first call link data is marked to generate a cross-domain identification; the cross-domain identification and the first call chain data are saved to the edge server 802 for the edge server 802 to synchronize the first call chain data. To the central server 803.

The edge server 802 is configured to obtain the cross-domain identification and the first call chain data sent by the data processing device 801. The first call chain data is data corresponding to the business based on the cross-data center; generate a storage identification corresponding to the first call chain data; Save the cross-domain identification and the first call chain data according to the storage identification; synchronize the first call chain data to the central server 803.

The central server 803 is configured to obtain the first call chain data synchronized by the edge server 802; in response to the query request sent by the user terminal 804, obtain the first call chain data based on the query identifier in the query request, and feed the first call chain data back to User terminal 804; the first call chain data is data corresponding to services based on cross-data centers.

In the data processing system provided by this application, the data processing device 801 sends the cross-domain identification and the first call chain data to the edge server 802. Based on the cross-domain identification, it can be clear that the first call chain data is based on cross-data center business correspondence. The data can distinguish cross-data center call chain data from other call chain data that does not cross-domain operations, reducing the proportion of incomplete call chain collection failures; the edge server 802 generates a storage identifier corresponding to the first call chain data. , saving the cross-domain identifier and the first call chain data according to the storage identifier can reduce the frequency of the call chain data reported to the central server 803 and improve the data transmission efficiency; the edge server 802 synchronizes the first call chain data to the central server 803, This allows the central server 803 to analyze data corresponding to cross-data center services, meet the needs of data analysis, and reduce the storage space of the central server wasted due to centralized storage of call chain data.

Figure 9 shows a block diagram of the data processing system provided by the embodiment of the present application. As shown in Figure 9, the data processing system includes but is not limited to the following equipment: the first center call chain server 901, the second center call chain server 902, the first edge call chain server 903, the second edge call chain server 904, registration Server 905, user terminal 906 and multiple call chain data processing devices (eg, call chain data processing device A, call chain data processing device B, call chain data processing device C, call chain data processing device D, etc.).

The first edge call chain server 903 includes a first call chain synchronizer 9031; the second edge call chain server 904 includes a second call chain synchronizer 9041.

The call chain data processing device is configured to collect distributed call chain data. The call chain data processing device may be in the same processing process as its corresponding microservice, or may be in a different processing process as its corresponding microservice.

The first central call chain server 901 or the second central call chain server 902 is configured to store distributed call chain data and analyze the stored call chain data to obtain statistical results. In some embodiments, the second central call chain server 902 may be deployed in a specific data center.

In some implementations, the first central call server 902 may also be configured to display the queried call chain data to the user terminal 906 . Alternatively, the call chain data processing device may also be used to display the usage information and/or statistical information of the queried call chain data to the user terminal 906 .

The first edge call chain server 903 or the second edge call chain server 904 is configured to store distributed call chain data inside each data center.

The first call chain synchronizer 9031 is configured to synchronize call chain data corresponding to cross-data center services stored in the first edge call chain server 903 to the first central call chain server 901; and corresponding to the services implemented within this data center The corresponding call chain data does not need to be synchronized to the first central call chain server 901.

The second call chain synchronizer 9041 is configured to synchronize call chain data corresponding to cross-data center services stored in the second edge call chain server 904 to the first central call chain server 901; and corresponding to the services implemented within the data center The corresponding call chain data does not need to be synchronized to the first central call chain server 901.

The registration server 905 is configured to provide multiple call chain data processing devices with the registration information of the microservice corresponding to the call chain data that they need. The registration information may include: the registration address of the microservice and other information.

It should be noted that the above component devices are only divided through logical relationships. In different application scenarios, different component devices can also be combined and deployed to increase the flexibility of the device's functions.

Figure 10 shows a schematic flowchart of the working method of the data processing system provided by the embodiment of the present application. As shown in Figure 10, the working method of the data processing system includes but is not limited to the following steps S1010 to S1030.

Step S1010: The call chain data processing device A marks the first call chain data, generates a cross-domain identifier corresponding to the first call chain data, and reports the first call chain data and its corresponding cross-domain identifier to the first call chain data. The edge calls the chain server 903.

The first call chain data is data generated based on cross-data center services. Moreover, the first edge call chain server 903 and the call chain data processing device A belong to the same data center.

Step S1020: After receiving the first call chain data and its corresponding cross-domain identification, the first edge call chain server 903 saves the first call chain data to the local storage space based on the cross-domain identification, and at the same time, saves the first call chain data to the local storage space. The first call chain data is synchronized to the first central call chain server 901.

Step S1030, when the user terminal 906 inputs the query identifier in the query front-end interface, the second center call chain server 902 in the background interacts with the first center call chain server 901, and/or, with the first edge call chain server 903 interaction, obtain the first call chain data corresponding to the query identifier, and display the first call chain data through the query front-end interface.

In this embodiment, by determining whether the first call chain data is data generated based on cross-data center services, the cross-data center call chain data can be specially marked to facilitate subsequent processing, and the first edge call chain The server 903 only synchronizes the call chain data with the cross-domain identifier to the first central call chain server 902, which can reduce the consumption of private network bandwidth between data centers when aggregating the call chain and reduce the transmission cost of network bandwidth. Since the first central call chain server 902 only aggregates call chain data with cross-domain identification (that is, call chain data generated based on cross-data center calls), a large amount of call chain data within the data center is stored at the edge. On the call chain server, the data storage pressure and computing pressure of the first central call chain server 902 can be reduced. When the user terminal requests to display the call chain data, it can reduce the proportion of incomplete call chain collection failures, ensure the display integrity of the call chain data, and enable the first central call chain server 902 to handle cross-data center business correspondence. Complete analysis of call chain data improves query efficiency and meets the needs of user terminals.

In some embodiments, the call chain data processing device A in step S1010 marks the first call chain data and generates a cross-domain identifier corresponding to the first call chain data; and combines the first call chain data and its corresponding Reporting the cross-domain identity to the first edge call chain server 903 can also be implemented in the following manner.

Figure 11 shows a schematic flowchart of a method for collecting first call chain data provided by an embodiment of the present application. As shown in Figure 11, the method of collecting first call chain data includes but is not limited to the following steps S1011 to S1015.

Step S1011: The microservice in the call chain data processing device A obtains the registration information of the microservice corresponding to the first call chain data from the registration server 905; and obtains the storage address of the target data corresponding to the first call chain data.

The registration information includes the registration address of the microservice, and the target data is the data that the microservice expects to obtain.

Step S1012: The microservice in the call chain data processing device A compares the registration address of the microservice with the storage address of the target data corresponding to the first call chain data to determine whether the first call chain data is based on cross-data center Business corresponding data.

If it is determined that the first call chain data is based on data corresponding to cross-data center services, step S1013 is executed; if it is determined that the first call chain data is not based on data corresponding to cross-data center services, step S1014 is executed.

Step S1013: The call chain data processing device A marks the first call chain data and generates a cross-domain identifier corresponding to the first call chain data.

After step S1013 is executed, jump to step S1015.

Step S1014, the call chain data processing device A does not mark the first call chain data specially, but only sends the first call chain data to the first edge call chain server 903.

Step S1015: The first edge call chain server 903 stores the obtained first call chain data.

In some embodiments, after receiving the first call chain data and its corresponding cross-domain identification, the first edge call chain server 903 in step S1020 saves the first call chain data to the local server based on the cross-domain identification. storage space. At the same time, synchronizing the first call chain data to the first central call chain server 901 can also be implemented in the following manner.

Figure 12 shows a schematic flowchart of a method for processing first call chain data by an edge call chain server provided by an embodiment of the present application. As shown in Figure 12, the edge call chain server's method for processing the first call chain data includes but is not limited to the following steps S1021 to S1025.

When it is determined that the first call chain data has a cross-domain identification corresponding to it, the first call chain data corresponding to the cross-domain identification needs to be stored in a specific storage area (for example, a cross-domain data storage area); when When it is determined that the first call chain data does not have a corresponding cross-domain identifier, the first call chain data only needs to be stored in a common storage area (such as a local storage area, etc.).

Step S1021, the first call chain synchronizer 9031 obtains the first call chain data through a scheduled task.

In some implementations, the first call chain synchronizer 9031 and the first edge call chain server 903 may also be two different devices. The first call chain synchronizer 9031 determines the first edge call chain server through active listening. Whether the first call chain data in 903 needs to be synchronized; and if it is determined that data synchronization is required, obtain the first call chain data from the first edge call chain server 903.

Step S1022: The first call chain synchronizer 9031 determines whether the first call chain data contains a cross-domain identifier.

If it is determined that the first call chain data has a cross-domain identifier, step S1023 is executed; if it is determined that the first call chain data does not have a cross-domain identifier, the process ends.

Step S1023: Obtain the TraceId corresponding to the first call chain data.

Step S1024: The first call chain synchronizer 9031 obtains the first call chain data from the first edge call chain server 903 of the data center based on the TraceId.

Step S1025: The first call chain synchronizer 9031 reports the obtained first call chain data to the first central call chain server 901.

After the above processing steps, the call chain data corresponding to the business based on cross-data centers is collected into the first central call chain server 901, and the call chain data corresponding to the business based on one data center is collected to each data center. In the edge call chain server (for example, the first edge call chain server 903), it is convenient to carry out differentiated management of different call chain data and improve the data management efficiency.

In some embodiments, when the user terminal 906 inputs the query identifier in the query front-end interface in step S1030, the second center call chain server 902 in the background interacts with the first center call chain server 901, and/or, with The interaction of the first edge call chain server 903 to obtain the first call chain data corresponding to the query identifier and display the first call chain data through the query front-end interface can also be implemented in the following manner.

Figure 13 shows a schematic flowchart of the first call chain data query method provided by the embodiment of the present application. As shown in Figure 13, the query method of the first call chain data includes but is not limited to the following steps S1031 to S1036.

Step S1031: The user terminal 906 generates a query request based on the query front-end interface.

The query request may include: Query ID. For example, you can generate a query request by entering the query ID (TraceId) on the query front-end interface.

Step S1032, the user terminal 906 sends the query request to the first central call chain server 901 to complete the query operation.

For example, you can query by clicking the "Query" button on the query front-end interface. The request is sent.

Step S1033: Determine whether the call chain data corresponding to TraceId is queried in the first central call chain server 901. If it is determined that the call chain data corresponding to TraceId is queried, step S1036 is executed; if the call chain data corresponding to TraceId is not queried, step S1034 is executed.

Step S1034, the user terminal 906 sends the query request to each edge call chain server, and waits for the query results fed back by each edge call chain server.

Each edge call chain server may include a first call chain edge server 903, and/or a second call chain edge server 904.

Step S1035: Determine whether the call chain data corresponding to the query identifier is queried in the query response fed back by at least one edge call chain server. If it is determined that no call chain data corresponding to the query identifier is found in the query responses fed back by each edge call chain server, the process ends; if at least one edge call chain server returns query responses corresponding to the query identifier. Call the chain data and execute step S1036.

Step S1036: Display the obtained query results on the query front-end interface.

Through the above processing of different types of call chain data, the adaptability of distributed calls in complex application environments can be enhanced.

In different application scenarios, the above data processing methods can be used to improve the management efficiency of call chain data. For example, a large enterprise distributes its own data centers in different cities and deploys different applications in these data centers, and some specific applications are only deployed in some specific data centers. Applications in other data centers call these For specific applications, cross-data center data calls will occur, resulting in cross-data center call chain data.

For example, the financial microservices in the financial system are only deployed in the data center in location A, while applications in the Human Resources (HR) system or applications in the Enterprise Resource Planning (ERP) system can be deployed In data centers across the country. During the process of business processing, applications in the HR system or applications in the ERP system may call the financial microservices of the financial system deployed in the data center at location A, thus generating cross-data center call chain data.

Figure 14 shows a schematic flowchart of a method for processing call chain data corresponding to financial microservices in the financial system provided by the embodiment of the present application. As shown in Figure 14, the method for processing call chain data corresponding to the financial microservices in the financial system includes but is not limited to the following steps S1401 to S1408.

Step S1401: The microservice in the HR system queries the address information of the financial microservice in the financial system through the registration server 905.

Step S1402: The microservice in the HR system determines whether the financial microservice is in the same data center as the microservice in the HR system through the address information of the financial microservice in the financial system returned by the registration server 905.

Step S1403, when it is determined that the financial microservice and the microservice in the HR system are not in the same data center, the call chain data processing device corresponding to the microservice in the HR system performs cross-domain marking on the first call chain data, and generates The cross-domain identifier corresponding to the first call chain data.

The first call chain data is used to represent the call relationship data between the financial microservices and the microservices in the HR system.

Step S1404: The call chain data processing device corresponding to the microservice in the HR system sends the first call chain data and its corresponding cross-domain identifier to the edge call chain server of the data center to which the HR system belongs, so that the edge call chain service Store the first call chain data and its corresponding cross-domain identifier.

While executing step S1404, step S1405 also needs to be executed.

Step S1405: The call chain data processing device corresponding to the microservice in the HR system sends the first call chain data and its corresponding cross-domain identification to the central call chain server of the data center to which the HR system belongs.

Step S1406: The call chain synchronizer in the data center to which the HR system belongs periodically triggers the acquisition of call chain data corresponding to cross-data center services through a timer.

For example, the call chain synchronizer can obtain the offset information of the last call chain data obtained from its own memory, and use this offset information as the starting address to obtain the offset information from the data center to which the HR system belongs. Pull the call chain data including the cross-domain identifier from the edge call chain server.

When the call chain synchronizer obtains the query identification (TraceId) corresponding to the call chain data including the cross-domain identification, it can obtain the TraceId corresponding to the TraceId from the edge call chain server in the data center to which the HR system belongs. Complete call chain data, and send the complete call chain data corresponding to the TraceId to the central call chain server in the data center to which the HR system belongs.

Step S1407, when the user inputs a TraceId into the call chain query interface and expects to query the call chain data corresponding to the TraceId, the user terminal used by the user will generate a query request based on the TraceId and send the query request to the central call chain. Query on the server and/or edge call chain server.

Step S1408: When the query result fed back by the central call chain server and/or the edge call chain server is obtained, the query result is displayed on the call chain query interface.

Through the above-mentioned processing of cross-data center call chain data between applications in the HR system and financial microservices of the financial system deployed in the data center at location A, the proportion of incomplete call chain collection failures can be reduced. Reduce the storage space wasted due to centralized storage of call chain data, reduce the frequency of reporting call chain data, improve data transmission efficiency, and reduce the consumption of private network bandwidth.

In the data processing process of telecom operators' servers, a multi-level data center architecture will also be used to deploy virtual network function (Virtual Network Feature, VNF) applications in different telecom systems in different data centers and deploy them in multiple VNF applications in the multi-level data center will also complete corresponding communication services through mutual calls.

For example, operators deploy billing microservices in provincial data centers, and terminal access microservices and identity authentication microservices are deployed in county-level data centers. When a terminal accesses the telecommunications network, the accounting microservice, terminal access microservice and identity authentication microservice need to cooperate with each other to achieve network access of the terminal device.

Figure 15 shows a schematic flowchart of a method for processing call chain data corresponding to a charging microservice in a communication operator's charging system provided by an embodiment of the present application. As shown in Figure 15, the method for processing the call chain data corresponding to the charging microservice in the charging system of the communication operator includes but is not limited to the following steps S1501 to S1509.

Step S1501: The call chain data processing device corresponding to the terminal access microservice sends an information acquisition request to the registration server 905 to obtain the target service address information corresponding to the charging microservice.

Step S1502, in response to the information acquisition response returned by the registration server 905, the terminal accesses the call chain data processing device corresponding to the microservice to determine that the charging microservice is deployed in a provincial data center.

Step S1503: The call chain data processing device corresponding to the terminal access microservice performs cross-domain marking on the call chain data between the terminal access microservice and the billing microservice, and generates a cross-domain identification corresponding to the call chain data; And the call chain data between the terminal access microservice and the billing microservice and its corresponding cross-domain identification are sent to the edge call chain server in the county-level data center.

The edge call chain server in the county-level data center and the call chain data processing device corresponding to the terminal access microservice are in the same data center.

Step S1504: After receiving the call chain data between the terminal access microservice and the billing microservice, the edge call chain server in the county-level data center stores the call chain data and the corresponding cross-domain identification.

Step S1505: The call chain synchronizer in the county-level data center determines whether there is new call chain data with a cross-domain identification on the edge call chain server by monitoring the edge call chain server.

Step S1506: When the call chain synchronizer determines that there is new call chain data with a cross-domain identifier on the edge call chain server, it obtains the TraceId corresponding to the call chain data, and based on the TraceId, from the same county level Get complete information about the call chain data from the edge call chain server in the data center.

Step S1507: The call chain synchronizer sends the obtained call chain data between the terminal access microservice and the billing microservice and its corresponding cross-domain identification to the central call chain server of the provincial data center.

Step S1508, when the operation and maintenance personnel enter the TraceId on the distributed call chain query interface in the provincial data center and click the query button, the central call chain server in the provincial data center will generate a query request based on the TraceId. And send the query request to the edge call chain server for query, or query the local memory of the central call chain server to obtain the call chain data corresponding to the TraceId.

Step S1509: If it is determined that the call chain data corresponding to the TraceId is obtained, the call chain data is displayed on the distributed call chain query interface.

Through the above processing of cross-data center call chain data between the accounting microservice deployed in the provincial data center and the terminal access microservice deployed in each county-level data center, it is possible to reduce the inefficiency of call chain collection. The complete proportion of fault occurrences enables terminals to quickly and accurately access the communication network and improve communication transmission efficiency.

In some implementations, in order to improve the user experience of mobile terminals, major public cloud vendors are actively deploying edge clouds and deploying different types of applications directly in edge clouds to reduce the interaction between mobile terminals and backend servers. time delay. However, due to the limited resources of the edge cloud, part of the data in the background server that interacts closely with the mobile terminal is usually isolated and deployed separately in the edge cloud. But other parts of the data in the backend server are still deployed in the public cloud. This allows the data in the edge cloud to interact with other parts of the data still deployed in the public cloud through preset interfaces.

For example, a game development server will deploy the game scene rendering microservice on the edge cloud. The game scene rendering microservice is mainly used for business interaction with mobile terminals; and the game's authentication microservices and billing microservices are for of components are still deployed in the public cloud. When a mobile terminal creates a game scene, the game scene microservice deployed in the edge cloud needs to interact with the authentication microservice and charging microservice deployed in the public cloud, thus generating cross-data center call chain data.

Figure 16 shows a schematic flowchart of a method for processing call chain data corresponding to a cloud-based game scene microservice provided by an embodiment of the present application. As shown in Figure 16, the method for processing the call chain data corresponding to the cloud-based game scene microservice includes but is not limited to the following steps S1601 to S1612.

Step S1601: The mobile terminal starts to create a game scene and sends a creation request to the game scene rendering microservice deployed in the edge cloud.

Step S1602: The call chain data processing device corresponding to the game scene rendering microservice sends an information acquisition request to the registration server 905 to obtain the target service address information corresponding to the charging microservice corresponding to the game scene rendering microservice.

Step S1603: In response to the information acquisition response returned by the registration server 905, the call chain data processing device corresponding to the game scene rendering microservice determines that the charging microservice is deployed in the public cloud.

Step S1604: The call chain data processing device corresponding to the game scene rendering microservice performs cross-domain marking on the call chain data between the game scene rendering microservice and the charging microservice, and generates a cross-domain identification corresponding to the call chain data; and The call chain data between the game scene rendering microservice and the charging microservice and its corresponding cross-domain identification are sent to the edge call chain server deployed in the edge cloud.

Step S1605: After receiving the call chain data and its corresponding cross-domain identification between the game scene rendering microservice and the charging microservice, the edge call chain server deployed in the edge cloud sends the call chain data and its corresponding cross-domain identification. Identity is stored.

Step S1606: The edge call chain server corresponding to the game scene rendering microservice periodically triggers the start of the call chain synchronizer through a timer.

The edge call chain server and the call chain synchronizer are both located in the same data center (such as edge cloud).

Step S1607: The call chain synchronizer obtains the offset information of the last call chain data obtained from its own storage.

Step S1608: Using the offset of the call chain data as a starting point, the call chain synchronizer pulls the call chain data including the cross-domain identifier from the edge call chain server of the edge cloud.

Step S1609: The call chain synchronizer analyzes the call chain data including the cross-domain identifier and obtains TraceId corresponding to the call chain data; and based on the TraceId, complete information of the call chain data between the game scene rendering microservice and the charging microservice is obtained from the edge call chain server of the edge cloud.

Step S1610: The call chain synchronizer sends the obtained complete information of the call chain data between the game scene rendering microservice and the charging microservice to the central call chain server of the public cloud.

Step S1611, when the operation and maintenance personnel of the public cloud input the time period information and statistics type that need to be counted on the distributed call chain query interface in the public cloud, the central call chain server on the public cloud will based on the obtained time period information and statistics type, to perform statistics on call chain data and obtain statistical results.

Step S1612: Display statistical results on the distributed call chain query interface.

Through the above processing of the call chain data between the game scene rendering microservice and the charging microservice, it is possible to reduce the proportion of incomplete call chain collection failures, enable the terminal to quickly and accurately render the scene in the game, and improve user usage. experience.

The equipment according to the embodiments of the present application will be introduced in detail below with reference to the accompanying drawings. Figure 17 shows a block diagram of a data processing device provided by an embodiment of the present application. As shown in Figure 17, the data processing device 1700 includes but is not limited to the following modules: a marking module 1701 and a storage module 1702.

The marking module 1701 is configured to mark the first calling link data and generate a cross-domain identification when it is determined that the first calling link data is based on data corresponding to cross-data center services.

The storage module 1702 is configured to save the cross-domain identification and the first call chain data to the edge server, so that the edge server can synchronize the first call chain data to the central server.

It should be noted that the data processing device 1700 in this embodiment can implement the data processing method applied to the data processing device in the embodiment of this application.

According to the data processing device provided by this application, when it is determined that the first call chain data is data corresponding to cross-data center services through the marking module 1701, the first call link data is marked and a cross-domain identifier is generated, using In order to distinguish other call chain data that do not operate across domains, reduce the proportion of incomplete call chain collection failures, and ensure the integrity of data corresponding to cross-data center business analysis; the storage module 1702 combines the cross-domain identifier with the first The first call chain data is saved to the edge server for the edge server to synchronize the first call chain data to the central server, which can reduce the storage space wasted due to centralized storage of call chain data, reduce the frequency of reporting call chain data, and improve data transmission efficiency while reducing the consumption of private network bandwidth.

Figure 18 shows a block diagram of the edge server provided by the embodiment of the present application. As shown in Figure 18, the edge server 1800 includes but is not limited to the following modules: an acquisition module 1801, a generation module 1802, a saving module 1803, and a synchronization module 1804.

The acquisition module 1801 is configured to acquire the cross-domain identification and first call chain data sent by the data processing device. The first call chain data is data corresponding to services based on cross-data centers.

The generating module 1802 is configured to generate a storage identification corresponding to the first call chain data.

The saving module 1803 is configured to save the cross-domain identification and the first call chain data according to the storage identification.

The synchronization module 1804 is configured to synchronize the first call chain data to the central server.

It should be noted that the edge server 1800 in this embodiment can implement the data processing method applied to the edge server in the embodiment of this application.

According to the edge server in the embodiment of the present application, the cross-domain identification and the first call chain data sent by the data processing device are obtained through the acquisition module 1801. Based on the cross-domain identification, it can be determined that the first call chain data is based on data corresponding to the cross-data center business. , can distinguish cross-data center call chain data from other call chain data that does not cross-domain operations, and reduce the proportion of failures in incomplete call chain collection; the generation module 1802 generates a storage identifier corresponding to the first call chain data, The saving module 1803 saves the cross-domain identifier and the first call chain data according to the storage identifier, which can reduce the frequency of reporting the call chain data to the central server and improve the data transmission efficiency; the synchronization module 1804 synchronizes the first call chain data to the central server to This enables the central server to analyze data corresponding to cross-data center businesses to meet the needs of data analysis and reduce the storage space of the central server wasted due to centralized storage of call chain data.

It is to be understood that this application is not limited to the specific configurations described above and illustrated in the drawings. and processing. For the convenience and simplicity of description, detailed descriptions of known methods are omitted here, and for the specific working processes of the systems, modules and units described above, reference can be made to the corresponding processes in the foregoing methods, which will not be described again here.

As shown in Figure 19, computing device 1900 includes an input device 1901, an input interface 1902, a central processing unit 1903, a memory 1904, an output interface 1905, and an output device 1906. The input interface 1902, the central processing unit 1903, the memory 1904, and the output interface 1905 are connected to each other through the bus 1907. The input device 1901 and the output device 1906 are connected to the bus 1907 through the input interface 1902 and the output interface 1905 respectively, and then to other parts of the computing device 1900. Component connections.

The input device 1901 receives input information from the outside and transmits the input information to the central processor 1903 through the input interface 1902; the central processor 1903 processes the input information based on computer-executable instructions stored in the memory 1904 to generate output information. The output information is temporarily or permanently stored in the memory 1904 and then transmitted to the output device 1906 through the output interface 1905; the output device 1906 outputs the output information to the outside of the computing device 1900 for use by the user.

In some embodiments, the computing device shown in FIG. 19 may be implemented as an electronic device, and the electronic device may include: a memory configured to store a computer program; and a processor configured to execute the computer program stored in the memory. , to perform the above data processing method.

In some embodiments, the computing device shown in Figure 19 may be implemented as a data processing system, which may include: a memory configured to store a computer program; a processor configured to execute the computer program stored in the memory , to perform the above data processing method.

Embodiments of the present application also provide a computer-readable storage medium, which stores a computer program. When the computer program is executed by a processor, the above-mentioned data processing method is implemented.

The above descriptions are only exemplary embodiments of the present application and are not used to limit the protection scope of the present application. Generally speaking, the various embodiments of the present application may be implemented in hardware or special purpose circuitry, software, logic, or any combination thereof. For example, some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software that may be executed by a controller, microprocessor, or other computing device, although the application is not limited thereto.

Embodiments of the present application may be implemented by a data processor of the mobile device executing computer program instructions, for example in a processor entity, or by hardware, or by a combination of software and hardware. Computer program instructions may be assembly instructions, instruction set architecture (ISA) instructions, machine instructions, machine-related instructions, microcode, firmware instructions, state setting data, or source code written in any combination of one or more programming languages or object code.

Any block diagram of a logic flow in the figures of this application may represent program steps, or may represent interconnected logic circuits, modules, and functions, or may represent a combination of program steps and logic circuits, modules, and functions. Computer programs can be stored on memory. The memory may be of any type suitable to the local technical environment and may be implemented using any suitable data storage technology, such as, but not limited to, read only memory (ROM), random access memory (RAM), optical storage devices and systems (digital versatile disc DVD or CD), etc. Computer-readable media may include non-transitory storage media. The data processor may be of any type suitable for the local technical environment, such as, but not limited to, general purpose computers, special purpose computers, microprocessors, digital signal processors (DSP), application specific integrated circuits (ASIC), programmable logic devices (FGPA) and processors based on multi-core processor architecture.

A detailed description of exemplary embodiments of the present application has been provided above, by way of illustrative and non-limiting examples. However, considering the accompanying drawings and claims, various modifications and adjustments to the above embodiments will be apparent to those skilled in the art without departing from the scope of the present application. Accordingly, the proper scope of the application will be determined from the claims.

Claims

A data processing method including:

When it is determined that the first call link data is based on data corresponding to cross-data center services, mark the first call link data to generate a cross-domain identification; and

The cross-domain identification and the first call chain data are saved to an edge server, so that the edge server can synchronize the first call chain data to the central server.
The method according to claim 1, further comprising:

Saving the cross-domain identification and the first call chain data to the edge server, so that after the edge server synchronizes the first call chain data to the central server, it sends a synchronization request to the edge server, For the edge server to synchronize the first call chain data to the central server according to the target address in the synchronization request, where the target address is the network address of the central server; and

In response to the synchronization response fed back by the central server, it is determined that the edge server has completed synchronization of the first call chain data.
The method of claim 1, further comprising:

The cross-domain identification and the first call chain data are saved to the edge server so that the edge server can obtain a query request after synchronizing the first call chain data to the central server, wherein the query The request includes a query identifier corresponding to the storage identifier of the first call chain data; and

Query at least one of the edge server or the central server according to the query identifier to obtain the first call chain data.
The method of claim 3, further comprising:

Query at least one of the edge server or the central server based on the query identifier, and after obtaining the first call chain data, perform at least one of the following operations:

Based on the tree structure, display the category of the data center to which the microservice corresponding to the first call chain data belongs; or,

Based on the graph structure, the processing time information of the microservice corresponding to the first call chain data is displayed.
The method of claim 1, further comprising:

When it is determined that the second call chain data is based on data corresponding to services occurring in the same data center, the second call chain data is saved to the edge server.
The method of claim 1, further comprising:

When it is determined that the first call chain data is data corresponding to cross-data center services, the first call link data is marked and the cross-domain identifier is obtained from the registration server before the cross-domain identification is generated. Call the registration information of the microservice corresponding to the chain data, where the registration information includes the registration address of the microservice;

Obtain the storage address of the target data corresponding to the first call chain data, where the target data is the data that the microservice expects to obtain; and

Based on the registration address of the microservice and the storage address of the target data corresponding to the first call chain data, it is determined whether the first call chain data is based on data corresponding to cross-data center services.
The method according to any one of claims 1 to 6, wherein the first call chain number The data is the data corresponding to the financial microservices in the financial system;

Saving the cross-domain identification and the first call chain data to the edge server so that the edge server can synchronize the first call chain data to the central server includes:

At every preset time interval, obtain the storage address corresponding to the first call chain data from the edge server, where the storage address corresponding to the first call chain data is based on the last time the edge server obtained the call chain. The address determined by the data offset information of the data;

Generate a synchronization request based on the storage address corresponding to the first call chain data and the network address of the central server; and

Send the synchronization request to the edge server, so that the edge server synchronizes the first call chain data to the first call chain data based on the storage address corresponding to the first call chain data and the network address of the central server. central server.
The method according to any one of claims 1 to 6, wherein the first call chain data is data corresponding to the charging microservice in the charging system of the communication operator;

Saving the cross-domain identification and the first call chain data to the edge server so that the edge server can synchronize the first call chain data to the central server includes:

Analyze the first call chain data to determine the billing area information to which the charging microservice corresponding to the first call chain data belongs, wherein the charging area information includes the charging area information corresponding to the charging microservice. fee area level; and

According to the charging area level corresponding to the charging microservice, the cross-domain identification and the first call chain data are saved to the edge server corresponding to the charging area level.
The method according to any one of claims 1 to 6, wherein the first call chain data is data corresponding to a cloud-based game scene microservice, wherein the game scene microservice includes a game scene rendering microservice. and its corresponding billing microservice. The game scene rendering microservice is deployed on the edge server, and the target data of the billing microservice corresponding to the game scene rendering microservice is stored on the public cloud server.
The method of claim 9, further comprising:

The cross-domain identification and the first call chain data are saved to the edge server, so that after the edge server synchronizes the first call chain data to the central server, the data statistics are sent to the public cloud server. Request, wherein the data statistics request is used to count the information that a preset amount of call chain data is used within a preset time period;

Obtain statistical results in response to the statistical response fed back by the public cloud server; and

Display the statistical results.
A data processing method including:

Obtain the cross-domain identification and first call chain data sent by the data processing device, wherein the first call chain data is data corresponding to services based on cross-data centers;

Generate a storage identification corresponding to the first call chain data;

Save the cross-domain identification and the first call chain data according to the storage identification; and

Synchronize the first call chain data to the central server.
The method according to claim 11, characterized in that, synchronizing the first call chain data to the central server includes:

In response to the synchronization request sent by the data processing device, obtain the target address in the synchronization request, wherein the target address is the network address of the central server; and

Synchronize the first call chain data to the central server according to the target address.
A data processing device including:

A marking module configured to mark the first calling link data and generate a cross-domain identification when it is determined that the first calling link data is based on data corresponding to cross-data center services; and

A storage module configured to save the cross-domain identification and the first call chain data to an edge server, so that the edge server can synchronize the first call chain data to the central server.
An edge server that includes:

The acquisition module is configured to acquire the cross-domain identification and the first call chain data sent by the data processing device, wherein the first call chain data is data corresponding to the business based on the cross-data center;

A generation module configured to generate a storage identification corresponding to the first call chain data;

a saving module configured to save the cross-domain identification and the first call chain data according to the storage identification; and

A synchronization module configured to synchronize the first call chain data to the central server.
A data processing system, including: a communication-connected data processing device, an edge server and a central server;

The data processing device is configured to perform the data processing method according to any one of claims 1 to 10;

The edge server is configured to perform the data processing method according to any one of claims 11 to 12;

The central server is configured to obtain the first call chain data synchronized by the edge server; in response to the query request sent by the user terminal, obtain the first call chain data based on the query identifier in the query request, and The first call chain data is fed back to the user terminal; wherein the first call chain data is data corresponding to services across data centers.
An electronic device including:

at least one processor; and

A memory having at least one computer program stored thereon, which when executed by the at least one processor causes the at least one processor to implement the data as claimed in any one of claims 1 to 12 Approach.
A computer-readable storage medium stores a computer program. When the computer program is executed by a processor, the data processing method according to any one of claims 1 to 12 is implemented.