CN112363855A - Call chain data generation method, topology generation method and system and computer equipment - Google Patents
Call chain data generation method, topology generation method and system and computer equipment Download PDFInfo
- Publication number
- CN112363855A CN112363855A CN202011271375.3A CN202011271375A CN112363855A CN 112363855 A CN112363855 A CN 112363855A CN 202011271375 A CN202011271375 A CN 202011271375A CN 112363855 A CN112363855 A CN 112363855A
- Authority
- CN
- China
- Prior art keywords
- service
- call chain
- transaction
- upstream
- chain data
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/547—Remote procedure calls [RPC]; Web services
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2209/00—Indexing scheme relating to G06F9/00
- G06F2209/54—Indexing scheme relating to G06F9/54
- G06F2209/549—Remote execution
Abstract
The application relates to a call chain data generation method, a topology generation method, a system and computer equipment, wherein the call chain data generation method comprises the following steps: generating a transaction unique identifier of a transaction corresponding to the request at the entry service of the request, and transmitting the transaction unique identifier on a calling link of the request; at each service on the call link, generating call chain data for each service, the call chain data comprising: a transaction unique identification, upstream service information, and downstream service information. The topology generation method comprises the following steps: acquiring call chain data of a service; generating a transaction view angle ternary relationship group and a service view angle ternary relationship group according to the service call chain data; combining the transaction view angle ternary relationship group according to the transaction unique identifier to obtain a calling chain topology corresponding to the transaction unique identifier; and merging the service view angle ternary relation groups according to the view angle service identification to obtain a calling chain topology corresponding to the view angle service. By the method and the device, the topology analysis efficiency is improved, and the computing resources are reduced.
Description
Technical Field
The present application relates to the field of computers, and in particular, to a call chain data generation method, a topology generation method, a system, and a computer device.
Background
Internet services are typically implemented using complex, large-scale distributed clusters, with the internet services being built on different sets of software modules. A plurality of services in a distributed system have a mutual calling relationship. A user's request may involve the co-processing of several services and these processes take place on different machines, different clusters or even different rooms. The call relationships between multiple services are called call chains.
The system operation and maintenance personnel need to know that the system processes a request, a group of requests, all requests relate to calling among services and a dependency graph, and when the request processing is abnormal, the problem needs to be found quickly and accurately positioned to which link the problem is. In the related art, positioning is facilitated by invoking chain tracking.
In a distributed tracking system in the related art, a basic generation mode of a call chain is that a globally unique call chain ID (called TraceId) is allocated to a request at an entry service, and a context Span is generated for a called context object Span; each service sends the call chain information to a collection system; on the basis of collecting call chain data, the collection system cleans and integrates service data according to the traceId and the Spanisd.
However, performing call chain tracking based on the call chain data requires centralized processing and calculation of a large amount of data, and particularly under a scenario that a transaction call topological relation needs to be drawn, the resource required by the tracking system is even more than that required by the business system itself.
Disclosure of Invention
In order to solve the technical problem or at least partially solve the technical problem, the application provides a call chain data generation method, a topology generation method, a system and a computer device.
In a first aspect, the present application provides a method for generating call chain data, including: generating a transaction unique identifier of a transaction corresponding to the request at an entry service of the request, and transmitting the transaction unique identifier on a calling link of the request, wherein the calling link comprises at least one service for executing the request; at each service on the call link, generating call chain data for each service, wherein the call chain data comprises: the transaction unique identification, the upstream service information and the downstream service information, wherein the upstream service information comprises the service identifications of all upstream services of the service on the calling link, and the downstream service information comprises the service identification of the direct downstream service of the service on the calling link.
In some embodiments, at each service on the call chain, call chain data for each service is generated, including: at each service on the call link, obtaining the transaction unique identification and the upstream service information from call chain information sent by an upstream service of the service, and obtaining the service identification of the direct downstream service from the direct downstream service of the service.
In some embodiments, the method for generating call chain data further includes: generating a calling chain unique identifier at the requested entrance service, and transmitting the calling chain unique identifier on the requested calling chain; wherein the call data of each service further comprises: and calling the unique identification of the chain.
In a second aspect, the present application provides a call chain topology generation method, including: the preprocessing device acquires call chain data of a service, wherein the call chain data is generated when the service executes a request, and the call chain data comprises: the system comprises a transaction unique identifier, upstream service information and downstream service information, wherein the transaction unique identifier is used for representing a transaction corresponding to a request, the upstream service information comprises service identifiers of all upstream services of a service on a calling link, and the downstream service information comprises a service identifier of a direct downstream service of the service on the calling link; the preprocessing device generates a transaction view angle ternary relationship group and a service view angle ternary relationship group according to the call chain data of each service, wherein the transaction view angle ternary relationship group comprises the following components: a transaction unique identifier, a service identifier of the service, and a service identifier of a service immediately downstream of the service; the service view triplet includes: a service identification of a perspective service, a service identification of a service immediately upstream of the service, and a service identification of the service; the topology generation device merges the transaction view angle ternary relationship group according to the transaction unique identifier to obtain a calling chain topology corresponding to the transaction unique identifier; and merging the service view angle ternary relation groups according to the view angle service identification to obtain a calling chain topology corresponding to the view angle service.
In some embodiments, the preprocessing unit obtains call chain data of the service, including: the preprocessing device acquires call chain data of the service from a service probe of the service, wherein the service probe is arranged in the service and used for generating the call chain data of the service.
In some embodiments, the preprocessing apparatus is deployed in a distributed manner and the topology generating apparatus is deployed in a centralized manner.
In a third aspect, the present application provides a service probe apparatus, disposed in a service of a distributed system, for generating call chain data of the service, where the service probe apparatus includes: the system comprises a first generation module, a receiving module, a sending module and a second generation module, wherein the first generation module is used for generating a transaction unique identifier of a transaction corresponding to a request when the service is the entry service of the request; the receiving module is used for receiving the transaction unique identifier and the upstream service information transmitted by the upstream service of the service, wherein the upstream service information comprises the service identifiers of all the upstream services of the service on the calling link; the sending module is used for adding the service identifier of the service to the upstream service information and transmitting the transaction unique identifier and the upstream service information to the downstream service of the service when the service has the downstream service; a second generation module, configured to generate call chain data, where the call chain data includes: the system comprises a transaction unique identification, upstream service information and downstream service information, wherein the downstream service information comprises a service identification of a direct downstream service of a service on a calling link.
In a fourth aspect, the present application provides a call chain topology generating system, including: the service probe device is used for generating a transaction unique identifier of a transaction corresponding to the request at the entry service of the request and transmitting the transaction unique identifier on a calling link of the request, wherein the calling link comprises at least one service for executing the request; at each service on the call link, generating call chain data for each service, wherein the call chain data comprises: the transaction unique identification, the upstream service information and the downstream service information, wherein the upstream service information comprises service identifications of all upstream services of the service on a calling link, and the downstream service information comprises service identifications of direct downstream services of the service on the calling link; the preprocessing device is used for acquiring call chain data of each service; generating a transaction view angle ternary relationship group and a service view angle ternary relationship group according to the call chain data of each service, wherein the transaction view angle ternary relationship group comprises the following components: a transaction unique identifier, a service identifier of the service, and a service identifier of a service immediately downstream of the service; the service view triplet includes: a service identification of the perspective service, a service identification of a service immediately upstream of the service, and a service identification of the service; the topology generating device is used for combining the transaction view angle ternary relationship group according to the transaction unique identifier to obtain a calling chain topology corresponding to the transaction unique identifier; and merging the service view angle ternary relation groups according to the view angle service identification to obtain a calling chain topology corresponding to the view angle service.
In a fifth aspect, the present application provides a computer device comprising: a memory, a processor, and a computer program stored on the memory and executable on the processor; the computer program, when executed by a processor, performs the steps of a call chain data generation method.
In a sixth aspect, the present application provides a computer device comprising: a memory, a processor, and a computer program stored on the memory and executable on the processor; the computer program, when executed by the processor, performs the steps of invoking the chain topology generation method.
Compared with the prior art, the technical scheme provided by the embodiment of the application has the following advantages: according to the scheme provided by the embodiment of the application, the transaction unique identifier of the transaction corresponding to the request is generated at the entrance service of the request, and the transaction unique identifier is transmitted on the calling link of the request; at each service on the call link, generating call chain data for each service, the call chain data comprising: a transaction unique identification, upstream service information, and downstream service information. Therefore, the call topology analysis can be carried out based on the transaction unique identifier, the upstream service information and the downstream service information, the computing resources required by the topology analysis are reduced, and the analysis efficiency is improved.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and together with the description, serve to explain the principles of the application.
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly described below, and it is obvious for those skilled in the art to obtain other drawings without inventive exercise.
Fig. 1 is a flowchart of an implementation manner of a call chain data generation method provided in an embodiment of the present application;
fig. 2 is a schematic diagram of an example of a call chain data generation process provided in the embodiment of the present application;
fig. 3 is a flowchart of an implementation manner of a call chain topology generation method provided in an embodiment of the present application;
FIG. 4A is a diagram illustrating a request x provided by an embodiment of the present application;
FIG. 4B is a diagram illustrating a request y provided by an embodiment of the present application;
FIG. 5 is a block diagram of an embodiment of a service probe apparatus 500 according to an embodiment of the present disclosure;
fig. 6 is a block diagram of a structure of an implementation manner of a call chain topology generation system 600 according to an embodiment of the present application; and
fig. 7 is a hardware structure diagram of an implementation manner of a computer device according to an embodiment of the present application.
Detailed Description
It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application.
In the following description, suffixes such as "module", "component", or "unit" used to denote elements are used only for the convenience of description of the present application, and have no specific meaning by themselves. Thus, "module", "component" or "unit" may be used mixedly.
A set of requests to complete a business operation in a distributed system is referred to herein as a transaction. For example, order submission in an e-commerce system, approval signing in an OA system, etc. In this context, a service is a component in a distributed system, and multiple services cooperate to fulfill a request.
An embodiment of the present application provides a call chain data generation method, as shown in fig. 1, the method includes steps S102 to S104.
Step S102, generating a transaction unique identifier of a transaction corresponding to the request at the requested entry service, and transmitting the transaction unique identifier on the calling link of the request.
Wherein the call link includes at least one service for executing the request.
Step S104, generating call chain data of each service at each service on the call link, wherein the call chain data comprises: a transaction unique identification, upstream service information, and downstream service information.
The upstream service information comprises service identifications of all upstream services of the service on the calling link, and the downstream service information comprises service identifications of direct downstream services of the service on the calling link.
In some embodiments, at each service on the call chain, call chain data for each service is generated, including: at each service on the call link, obtaining the transaction unique identification and the upstream service information from call chain information sent by an upstream service of the service, and obtaining the service identification of the direct downstream service from the direct downstream service of the service.
In some embodiments, the method for generating call chain data further includes: generating a unique calling chain identifier, and transmitting the unique calling chain identifier on the requested calling chain; wherein the call data of each service further comprises: and calling the unique identification of the chain.
In some embodiments, the format of the CALL chain data is X-ID c _ CALL _ LIST; x is TRACE _ ID; n-NAME _ ID; d is CHILDREN _ LIST. The CALL _ LIST is a service identifier of an upstream service, the child _ LIST is a service identifier of a downstream service, the NAME _ ID is a transaction unique identifier of a transaction corresponding to a request, and the TRACE _ ID is a CALL chain unique identifier. In some examples, the transaction unique identifier is a unique identifier generated by a URL of the portal request using a MD 5-like algorithm, but the application embodiments are not limited thereto.
In some embodiments, the transaction unique identification, upstream service information, and downstream service information are passed through a chain of calls. In this document, the http protocol is taken as an example, and the unique transaction identifier and the transmission of the upstream service information are exemplarily described. When the upstream service sends an http request, inserting a request header into http data, such as X-ID (c-xx); n is yy; and n is zz, wherein c is the upstream service information (including service identifications of one or more upstream services), and n is a transaction unique identification. When the downstream application responds to the http content, inserting a response head into the responded http data, wherein the response head carries the service identification of the downstream service, and when the upstream service receives the downstream service data, analyzing the received http response head to obtain the service identification of the downstream service.
Referring to fig. 2, describing the call chain data generation method, as shown in fig. 2, the browser 100 sends a request to the distributed system 200, in fig. 2, the services on the call chain of the request are a first service 210, a second service 220, and a third service 230 in sequence, where the first service 210 serves as an entry of the request.
The process of transmitting the transaction unique identifier and the upstream service information comprises the following steps: when receiving a request of the browser 100, the first service 210 generates a transaction unique identifier of a transaction corresponding to the request; s1: the first service 210 sends its service identification and transaction unique identification to the second service 220, wherein the service identification of the first service 210 is used as the upstream service information of the second service 220; s2: the second service 220 receives the transaction unique identifier and the upstream service information sent by the first service 210, appends the service identifier of the second service 220 to the upstream service information, and transmits the upstream service information and the transaction unique identifier to the third service 230; the third service 230 receives the transaction unique identification and upstream service information delivered by the second service 220.
The process of transmitting the downstream service information and generating the call chain data comprises the following steps: s4: the second service 220 feeds back the service identification of the second service 220 to the first service 210; after receiving the service identifier of the second service 220, the first service 210 generates call chain data of the first service 210; s3: the third service 230 feeds back the service identification of the third service 230 to the second service 220; after receiving the service identifier of the third service 230, the second service 220 generates call chain data of the second service 220; the third service 230 has no downstream service and directly generates call chain data.
The contents of the transferred information and the call chain data are shown in table 1, the upstream service information is represented by C, the transaction unique identifier is represented by n, the downstream service information is represented by d, the transaction unique identifier is denoted by M, the service identifier of the first service 210 is a, the service identifier of the second service 220 is B, and the service identifier of the third service 230 is C.
Table 1 call chain data generating process data table 1
As shown in table 1, the first service 210 is an entry service during the execution of the transaction (M), has no upstream service, and the upstream service information ("c") in the call chain data is "null". The third service 230 is an end service in the execution of the transaction (M), has no downstream service, and the downstream service information (d) in the call chain data is "null".
As shown in table 1, the first service 210 writes its own service identifier a into the upstream service information "C", which becomes "C ═ a", and delivers the information to the second service 220; the second service 220 receives this information, and adds its own service identifier B to the upstream service information, which becomes "C ═ a, B", indicating that a and B are both C upstream services, as a vector, while a is B upstream service.
In some embodiment modes, when receiving a request of the browser 100, the first service 210 generates a transaction unique identifier of a transaction corresponding to the request, and a call chain ID (denoted as x herein); s1: the first service 210 sends the service identification, the call chain ID and the transaction unique identification thereof to the second service 220, wherein the service identification of the first service 210 serves as the upstream service information of the second service 220; s2: the second service 220 receives the transaction unique identifier and the upstream service information sent by the first service 210, appends the service identifier of the second service 220 to the upstream service information, and transmits the upstream service information, the call chain ID and the transaction unique identifier to the third service 230; the third service 230 receives the call chain ID, the transaction unique identification, and the upstream service information passed by the second service 220. The contents of the transferred information and call chain data are shown in table 2, and the transferred information and call chain data include a call chain ID (denoted as 4AC3 in table 2).
Table 2 call chain data generating process data table 2
The embodiment of the present application further provides a call chain topology generation method, as shown in fig. 3, the method includes steps S302 to S306.
Step S302, the preprocessing device obtains call chain data of the service, where the call chain data is generated when the service executes the request, and the call chain data includes: a transaction unique identification, upstream service information, and downstream service information.
The transaction unique identification is used for representing a transaction corresponding to the request, the upstream service information comprises service identifications of all upstream services of the service on the calling link, and the downstream service information comprises service identifications of direct downstream services of the service on the calling link.
And step S304, the preprocessing device generates a transaction view angle ternary relationship group and a service view angle ternary relationship group according to the call chain data of each service.
Wherein the transaction perspective set of ternary relationships comprises: a transaction unique identifier, a service identifier of the service, and a service identifier of a service immediately downstream of the service; the service view triplet includes: a service identification of the view service, a service identification of a service immediately upstream of the service, and a service identification of the service.
Step S306, the topology generating device merges the transaction view angle ternary relationship group according to the transaction unique identifier to obtain a calling chain topology corresponding to the transaction unique identifier; and merging the service view angle ternary relation groups according to the view angle service identification to obtain a calling chain topology corresponding to the view angle service.
The call chain topology generation method is exemplarily described below with reference to fig. 4A and 4B.
As shown in fig. 4A and 4B, the requests x and y both belong to a transaction T, where the actual path of the request x in the distributed system is shown in fig. 4A, and the actual path of the request y in the distributed system is shown in fig. 4B, which is service A, B. The transaction view and service view triplets for requests x and y are described below.
Referring to FIG. 4A, for request x, the call chain data generated by service A, B, D, E is shown in Table 3.
Table 3 example table of call chain data corresponding to request x
A service view ternary relationship group is generated according to the call chain data shown in table 3, where the form of the service view ternary relationship group data is { service identifier of view service, service identifier of direct higher level of service, service identifier of service } "which represents a relationship between a service and a caller of the service from the view point of the view service. The service view triplet for request x is shown in table 4.
Table 4 request x service view angle triplet table
| Request sequence number | Upstream service information | Service view set of ternary relations |
| x-1 (service A) | null | Is free of |
| x-2 (service B) | A | {A，A，B} |
| x-3 (service D) | A,B | {B，B，D}，{A，B，D} |
| x-4 (service E) | A,B | {B，B，E}，{A，B，E} |
Referring to FIG. 4A and Table 4, for service B, from A's perspective, an A to B call is made; for service D, from the perspective of B, a call from B to D is generated, and from the perspective of A, a call from B to D is generated; for service E, from the B perspective, a B to E call is made, and from the A perspective, a B to E call is made.
Referring to FIG. 4B, for request y, the call chain data generated by service A, B, C, D is shown in Table 5.
Table 5 example table of call chain data corresponding to request y
The service view triplet determined by request y according to the call chain data shown in table 5 is shown in table 6.
Table 6 request y service view angle triplet table
Referring to FIG. 4B and Table 6, for service B, from the perspective of A and C, a C to B call is made; for service D, from the perspective of A, B and C, a B to D call is made; for service C, from A's perspective, an A to C call is made.
The service view ternary relationship groups of the request x and the request y are summarized to obtain the topological relationship under each service view, as shown in table 7.
TABLE 7 topological relation example table for service view
Referring to table 7, the topology result for service a view is: calling from A to B for 1 time, calling from B to D for 2 times, calling from A to C for 1 time, calling from C to B for 1 time, and calling from C to D for 1 time. The topological result from the service B view is: b to D calls 2 times, B to E calls 1 time. The topological result from service C view is: c calls 1 time to B, B calls 1 time to D, C calls 1 time to D.
The above topology relationship of the service view can also be expressed as:
the topological result of the service A view is A → B (1) B → D (2) B → E (1) A → C (1) C → B (1) C → D (1);
the topological result of the service B view is B → D (2) B → E (1);
the topological result of the service C view is C → B (1) B → D (1) C → D (1).
The data format of the transaction view point ternary relationship group is { transaction unique identification, service identification of calling service, service identification of called service }, and represents the relationship of generating service calling under a certain transaction.
Referring to FIG. 4A and Table 3, the transaction view triplet for request x is shown in Table 8.
Table 8 example Table requesting transaction view angle set of triplets corresponding to x
| Service | Downstream application information | Transaction view set of ternary relationships |
| A | B | {T,A,B} |
| B | D，E | {T,B,D}；{T,B,E} |
Referring to Table 8, for request x, transaction T generates an A to B call, a B to D call, and a B to E call.
Referring to FIG. 4B and Table 5, the transaction view triplet for request y is shown in Table 9.
Table 9 request example table for transaction view angle set of triplets corresponding to y
| Service | Downstream application information | Transaction view set of ternary relationships |
| A | C | {T,A,C} |
| C | B，D | {T,C,B}；{T,C,D} |
| B | D | {T,B,D}； |
For transaction T, taking requests x and y as an example, and combining the transaction view point ternary relationship sets obtained in tables 8 and 9, the topological relationship under the view point of transaction T is determined to be: calling from A to B for 1 time, calling from B to D for 2 times, calling from B to E for 1 time, calling from A to C for 1 time, calling from C to B for 1 time, and calling from C to D for 1 time.
The above-described transaction-view topological relationship can also be expressed as: the topological result of transaction T is: a → B (1) B → D (2) B → E (1) A → C (1) C → B (1) C → D (1).
It should be understood that although only requests x and y of transaction T are shown, in practical applications, transaction T may include more requests, which are not described herein.
The embodiment of the application also provides a service probe device, which is arranged in the service of the distributed system and used for generating the call chain data of the service. In the embodiment of the application, the service probe device can be embedded into each service in the distributed system by using SDK or interceptor technology.
As shown in fig. 5, the service probe apparatus 500 includes: a first generation module 510, a receiving module 520, a transmitting module 530, and a second generation module 540.
Referring to fig. 5, the first generating module 510 is configured to generate a transaction unique identifier of a transaction corresponding to a request when the service serves a requested portal, and in this embodiment, the transaction unique identifier information may be, but is not limited to, a unique identifier generated by using an MD 5-like algorithm according to a URL of the portal request. A receiving module 520, configured to receive the transaction unique identifier and the upstream service information delivered by the upstream service of the service, where the upstream service information includes service identifiers of all upstream services of the service on the invocation link. A sending module 530, connected to the first generating module 510 and the receiving module 520, for appending the service identifier of the service to the upstream service information and transmitting the transaction unique identifier and the upstream service information to the downstream service of the service when the service has the downstream service. A second generating module 540, connected to the first generating module 510 and the receiving module 520, configured to generate call chain data, where the call chain data includes: the system comprises a transaction unique identification, upstream service information and downstream service information, wherein the downstream service information comprises a service identification of a direct downstream service of a service on a calling link.
In this document, the http protocol is taken as an example, and the unique transaction identifier and the transmission of the upstream service information are exemplarily described. When the upstream service sends an http request, the service probe device 500 inserts a request header, such as X-ID: c ═ xx, into the http data; n is yy; and n is zz, wherein c is the upstream service information (including service identifications of one or more upstream services), and n is a transaction unique identification. When the downstream application responds to the http content, the service probe device 500 inserts a response header into the responded http data, the response header carries the service identifier of the downstream service, and when the upstream service receives the downstream service data, the service probe device 500 analyzes the received http response header to obtain the service identifier of the downstream service.
Referring to fig. 4A, a service a is built in a service device 500, the service a serves as an entry of a request x, and after the service a receives the request x, a first generation module 510 generates a transaction unique identifier (denoted as T herein) of a transaction corresponding to the request x. The sending module 530 appends the service identification of the service to the upstream service information and delivers the transaction unique identification (transaction unique identification T) and the upstream service information (identification of service a) to the downstream service of the service (service B shown in fig. 4A). The second generating module 540 generates call chain data (shown in reference to table 3), where the call chain data includes: transaction unique identification, upstream service information, downstream service information, wherein the downstream service information comprises a service identification of a service (identification of service B shown in fig. 4A) directly downstream on the invocation link.
Referring to fig. 4A, the service B embeds the service apparatus 500, and the receiving module 520 receives the transaction unique identifier and the upstream service information delivered by the upstream service a of the service B. The sending module 530 appends the service identification of the service to the upstream service information and passes the transaction unique identification and the upstream service information to the downstream service D of the service. The second generating module 540 generates call chain data (shown in reference to table 3), where the call chain data includes: transaction unique identification, upstream service information, downstream service information, wherein the downstream service information comprises a service identification of a service (identification of service D shown in fig. 4A) directly downstream on the invocation link.
Referring to fig. 4A, the service D is built in the service device 500, and the receiving module 520 receives the transaction unique identifier and the upstream service information delivered by the upstream service B of the service D. Service D has no downstream service and the sending module 530 does not perform the transfer of the transaction unique identification and the upstream service information. The second generating module 540 generates call chain data (shown in reference to table 3), where the call chain data includes: the system comprises a transaction unique identifier, upstream service information and downstream service information, wherein the downstream service information is 'null'.
An embodiment of the present application further provides a call chain topology generating system, as shown in fig. 6, the call chain topology generating system 600 includes: a service probe means 610, a preprocessing means 620 and a topology generation means 630.
The service probe apparatus 610, shown in fig. 6, includes a first service probe 611 disposed in a first service a; a second service probe 612 disposed in a second service B; and a third service probe 613 disposed in the third service C.
The first service probe 611 is configured to generate a transaction unique identifier of a transaction corresponding to a request after the first service a receives the request, and transmit the transaction unique identifier on a call link of the request, where the call link includes a first service a, a second service B, and a third service C for executing the request; generating call chain data of the first service A, wherein the call chain data comprises: the transaction unique identification, the upstream service information and the downstream service information, wherein the upstream service information comprises service identifications of all upstream services of the service on the calling link, and the downstream service information comprises service identifications of direct downstream services of the service on the calling link.
The second service probe 612 is configured to receive the transaction unique identifier and the upstream service information transmitted by the first service a, generate call chain data, and transmit the transaction unique identifier and the upstream service information to the third service C by using the service identifier of the second service B as a part of the upstream service information. In some examples, the second service probe 612 is also used to return a service identification for the second service B to the first service a. The first service probe 612 receives the service identifier returned by the second service probe 612, and uses the service identifier as downstream service information in the call chain data.
The third service probe 613 is configured to receive the transaction unique identifier and the upstream service information transmitted by the second service B, and generate call chain data.
The preprocessing device 620 is connected with the service probe device 610 and used for acquiring call chain data of each service; generating a transaction view angle ternary relationship group and a service view angle ternary relationship group according to the call chain data of each service, wherein the transaction view angle ternary relationship group comprises the following components: a transaction unique identifier, a service identifier of the service, and a service identifier of a service immediately downstream of the service; the service view triplet includes: a service identification of the view service, a service identification of a service immediately upstream of the service, and a service identification of the service.
In some examples, referring to fig. 6, the pre-processing apparatus 620 includes a first pre-processing module 621 and a second pre-processing module 622. The first preprocessing module 621 is connected to the first service probe 611, and is configured to acquire call chain data of the first service a, generate a transaction view ternary relationship group and a service view ternary relationship group according to the call chain data of the first service a, and send the generated transaction view ternary relationship group and service view ternary relationship group to the topology generating device 630; a second preprocessing module 622, connected to the second service probe 622 and the third service probe 623, configured to obtain call chain data of the second service B, generate a transaction view ternary relationship group and a service view ternary relationship group according to the call chain data of the second service B, and send the generated transaction view ternary relationship group and service view ternary relationship group to the topology generating device 630; and acquiring call chain data of the third service C, generating a transaction view angle ternary relationship group and a service view angle ternary relationship group according to the call chain data of the third service C, and sending the generated transaction view angle ternary relationship group and service view angle ternary relationship group to the topology generating device 630.
It should be understood that although fig. 6 only shows the first preprocessing module 621 connected to the first service probe 611 and the second preprocessing module 622 connected to the second service probe 622 and the third service probe 623, the embodiment of the present application is not limited thereto, and in practical applications, the preprocessing module may be connected to one or more service probes to preprocess call chain data of the one or more service probes.
The topology generating device 630 is connected to the preprocessing device 620, and is configured to merge the transaction view ternary relationship group according to the transaction unique identifier to obtain a call chain topology corresponding to the transaction unique identifier; and merging the service view angle ternary relation groups according to the view angle service identification to obtain a calling chain topology corresponding to the view angle service.
In some embodiments, the preprocessing unit 620 is deployed in a distributed manner and the topology generating unit 630 is deployed in a centralized manner.
In some examples, the service probe device 610 determines at the ingress service that a transaction unique identification for the corresponding transaction is requested and passes the transaction unique identification to the downstream service through a call chain. The downstream service acquires the transaction unique identification and the upstream service information (identification of one or more upstream services) through the call chain and continues to pass through the call chain to the downstream service. And the upstream service acquires the downstream service identifier fed back by the downstream service and records the downstream service identifier in the call chain data.
In this document, the http protocol is taken as an example, and the unique transaction identifier and the transmission of the upstream service information are exemplarily described. When the upstream service sends an http request, the service probe device 610 inserts a request header, such as X-ID: c ═ xx, into the http data; n is yy; and n is zz, wherein c is the upstream service information (including service identifications of one or more upstream services), and n is a transaction unique identification. When the downstream application responds to the http content, the service probe device 610 inserts a response header into the responded http data, the response header carries the service identifier of the downstream service, and when the upstream service receives the downstream service data, the service probe device 610 analyzes the received http response header to obtain the service identifier of the downstream service.
The preprocessing device 620 splits the service view ternary relationship group according to the call chain data, and for the currently processed service, the service view ternary relationship group is represented as: { view service identity, service identity of the immediate upstream service (caller), current service identity (callee) }.
For the currently processed service, the preprocessing means 620 acquires upstream service information within call chain data of the service, loops each service identification in the upstream service information as a "service identification of view service", and sets the immediately upstream service of the current service identification as a "service identification of immediately upstream service".
The preprocessing unit 620 splits the transaction view ternary relationship group according to the call chain data, and for the currently processed service, the transaction view ternary relationship group is represented as: { transaction unique identity, current service identity (caller), downstream service identity (callee) }.
For the currently processed service, the preprocessing device 620 obtains the transaction unique identifier and the downstream service information in the call chain data of the request, loops each downstream service identifier to be used as the "downstream service identifier", sets the current service identifier as the "current service identifier", and sets the "transaction unique identifier" record in the call chain as the "transaction unique identifier".
In some embodiments, referring to fig. 6 and fig. 2, the service probe device 610 is embedded in each service in the distributed system by using an SDK or interceptor interception technology, the service probe device 610 obtains a unique identifier of the service after being started, and when the service probe device 610 collects call chain data, sends the call chain data to the preprocessing device 620 deployed in the distributed manner, and the preprocessing device 620 performs preprocessing and sends the preprocessed topology data to the topology generating device 630 deployed in the centralized manner to complete final processing.
At the ingress service (a) of the request, the service probe device 610 generates call chain data, appends the service identification of service a and the transaction unique identification of the corresponding transaction of the request to the call chain data, and passes it to the downstream service, as shown at S1 in fig. 2. The calling chain sent to the service B by the service A is X-ID, wherein c is A; x is 4AC 3; n-7 BD 2.
As shown in S2 in fig. 2, in the requested downstream service B, the call chain data generated by the upstream service a is acquired, and the unique identifier of the service B is appended to the call chain data and the transfer continues to the next-stage service C. The calling chain sent to the service C by the service B is X-ID, wherein C is A and B; x is 4AC 3; n-7 BD 2.
As shown in S3 and S4 in fig. 2, in the requested upstream service, after acquiring the feedback information generated by the downstream service, the downstream service information is recorded in the call chain data, and after the request is finished, the call chain data is reported to the preprocessing device 620.
The calling chain after the service B acquires the response of the downstream service C is X-ID (C is A); x is 4AC 3; n-7 BD 2; d ═ C.
The calling chain after the service A acquires the response of the downstream service B is X-ID (X is 4AC 3); n-7 BD 2; d ═ B.
After receiving the call chain data of the service, the preprocessing device 620 summarizes the data into preprocessing information according to the service identifier and the transaction unique identifier in the call chain. The topology generating means 630 determines the topological relation according to the preprocessed information.
The embodiment of the application also provides computer equipment. Fig. 7 is a schematic hardware structure diagram of an implementation manner of a computer device provided in an embodiment of the present application, and as shown in fig. 7, a computer device 10 according to an embodiment of the present application includes: including at least but not limited to: a memory 11 and a processor 12 communicatively coupled to each other via a system bus. It is noted that fig. 7 only shows a computer device 10 with components 11-12, but it is to be understood that not all shown components are required to be implemented, and that more or fewer components may be implemented instead.
In this embodiment, the memory 11 (i.e., a readable storage medium) includes a flash memory, a hard disk, a multimedia card, a card-type memory (e.g., SD or DX memory, etc.), a Random Access Memory (RAM), a Static Random Access Memory (SRAM), a read-only memory (ROM), an electrically erasable programmable read-only memory (EEPROM), a programmable read-only memory (PROM), a magnetic memory, a magnetic disk, an optical disk, and the like. In some embodiments, the memory 11 may be an internal storage unit of the computer device 10, such as a hard disk or a memory of the computer device 10. In other embodiments, the memory 11 may also be an external storage device of the computer device 10, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card), or the like, provided on the computer device 10. Of course, the memory 11 may also include both internal and external storage devices of the computer device 10. In this embodiment, the memory 11 is generally used for storing an operating system and various types of software installed in the computer device 10. Further, the memory 11 may also be used to temporarily store various types of data that have been output or are to be output.
Processor 12 may be a Central Processing Unit (CPU), controller, microcontroller, microprocessor, or other data Processing chip in some embodiments. The processor 12 is generally operative to control overall operation of the computer device 10. In this embodiment, the processor 12 is configured to execute the program code stored in the memory 11 or process data, such as the service probe apparatus 500 and the call chain topology generation system 600.
The present embodiment also provides a computer-readable storage medium, such as a flash memory, a hard disk, a multimedia card, a card-type memory (e.g., SD or DX memory, etc.), a Random Access Memory (RAM), a Static Random Access Memory (SRAM), a read-only memory (ROM), an electrically erasable programmable read-only memory (EEPROM), a programmable read-only memory (PROM), a magnetic memory, a magnetic disk, an optical disk, a server, an App application mall, etc., on which a computer program is stored, which when executed by a processor implements corresponding functions. The computer readable storage medium of the present embodiment is used for storing the program codes of the service probe apparatus 500 and the call chain topology generation system 600, and when executed by the processor, the program codes realize the call chain data generation method and the call chain topology generation method.
According to the method and the device, the unique transaction identifier of the request is determined at the entrance service and is transmitted to the downstream service through the call chain, the unique transaction identifier and the upstream service identifier are obtained at the downstream service through the call chain and are continuously transmitted to the downstream service through the call chain, subsequent reverse searching of transaction data through the traceId is avoided, and the calculation efficiency is improved. The upstream service acquires the downstream service identifier fed back by the downstream service and records the downstream service identifier in the call chain, so that the necessary data for calculating the transaction topology can be met, and the calculation resources are saved. The request topology ternary relation group of the service view angle and the service topology ternary relation group of the transaction view angle are split according to the call chain information, transaction data are not searched reversely according to the traceId, the requirement of distributed computing can be met, and the flexibility of the framework is improved.
It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
The above-mentioned serial numbers of the embodiments of the present application are merely for description and do not represent the merits of the embodiments.
Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solutions of the present application may be embodied in the form of a software product, which is stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a terminal (such as a mobile phone, a computer, a server, an air conditioner, or a network device) to execute the method according to the embodiments of the present application.
While the present embodiments have been described with reference to the accompanying drawings, it is to be understood that the invention is not limited to the precise embodiments described above, which are meant to be illustrative and not restrictive, and that various changes may be made therein by those skilled in the art without departing from the spirit and scope of the invention as defined by the appended claims.
Claims (10)
1. A call chain data generation method is characterized by comprising the following steps:
generating a transaction unique identifier of a transaction corresponding to a request at an entry service of the request, and transmitting the transaction unique identifier on a calling link of the request, wherein the calling link comprises at least one service for executing the request;
generating call chain data for each service at each service on the call chain, wherein the call chain data comprises: the transaction unique identification, the upstream service information and the downstream service information, wherein the upstream service information comprises service identifications of all upstream services of the service on the calling link, and the downstream service information comprises service identifications of direct downstream services of the service on the calling link.
2. The call chain data generation method according to claim 1, wherein generating call chain data for each service at each service on the call chain comprises:
at each service on the call link, obtaining the transaction unique identifier and the upstream service information from call chain information sent by an upstream service of the service, and obtaining a service identifier of a direct downstream service of the service from the direct downstream service.
3. The call chain data generation method according to claim 1 or 2, further comprising: generating a call chain unique identifier at the requested entry service, and transmitting the call chain unique identifier on the requested call link; wherein the call data of each service further comprises: the call chain is uniquely identified.
4. A call chain topology generation method, comprising:
the preprocessing device acquires call chain data of a service, wherein the call chain data is generated when the service executes a request, and the call chain data comprises: the transaction unique identification is used for representing a transaction corresponding to the request, the upstream service information comprises service identifications of all upstream services of the service on a calling link, and the downstream service information comprises service identifications of direct downstream services of the service on the calling link;
the preprocessing device generates a transaction view angle ternary relationship group and a service view angle ternary relationship group according to the call chain data of each service, wherein the transaction view angle ternary relationship group comprises: the transaction unique identifier, the service identifier of the service and the service identifier of a service immediately downstream of the service; the service view triplet includes: a service identification of a perspective service, a service identification of a service immediately upstream of the service, and a service identification of the service;
the topology generation device merges the transaction view angle ternary relationship group according to the transaction unique identifier to obtain a call chain topology corresponding to the transaction unique identifier; and merging the service view ternary relationship group according to the view service identifier to obtain a call chain topology corresponding to the view service.
5. The call chain topology generation method according to claim 4, wherein the preprocessing device obtains call chain data of the service, including: the preprocessing device acquires call chain data of a service from a service probe of the service, wherein the service probe is arranged in the service and used for generating the call chain data of the service.
6. The call chain topology generation method according to claim 4 or 5, wherein the preprocessing means is distributed deployed and the topology generation means is centralized deployed.
7. A service probe apparatus, provided in a service of a distributed system, for generating call chain data of the service, the service probe apparatus comprising: a first generating module, a receiving module, a sending module and a second generating module, wherein,
the first generating module is configured to generate a transaction unique identifier of a transaction corresponding to the request when the service is an entry service of the request;
the receiving module is configured to receive the transaction unique identifier and upstream service information transmitted by an upstream service of the service, where the upstream service information includes service identifiers of all upstream services of the service on the call link;
the sending module is configured to, when the service has a downstream service, append the service identifier of the service to the upstream service information and transmit the transaction unique identifier and the upstream service information to the downstream service of the service;
the second generating module is configured to generate call chain data, where the call chain data includes: the transaction unique identification, the upstream service information and the downstream service information, wherein the downstream service information comprises the service identification of the direct downstream service of the service on the calling link.
8. A call chain topology generation system, comprising:
the service probe device is used for generating a transaction unique identifier of a transaction corresponding to a request at an entry service of the request and transmitting the transaction unique identifier on a calling link of the request, wherein the calling link comprises at least one service for executing the request; generating call chain data for each service at each service on the call chain, wherein the call chain data comprises: the transaction unique identification, upstream service information and downstream service information, wherein the upstream service information comprises service identifications of all upstream services of the service on the calling link, and the downstream service information comprises service identifications of direct downstream services of the service on the calling link;
the preprocessing device is used for acquiring the call chain data of each service; generating a transaction view ternary relationship group and a service view ternary relationship group according to the call chain data of each service, wherein the transaction view ternary relationship group comprises: the transaction unique identifier, the service identifier of the service and the service identifier of a service immediately downstream of the service; the service view triplet includes: a service identification of a perspective service, a service identification of a service immediately upstream of the service, and a service identification of the service;
the topology generating device is used for merging the transaction view angle ternary relationship group according to the transaction unique identifier to obtain a calling chain topology corresponding to the transaction unique identifier; and merging the service view ternary relationship group according to the view service identifier to obtain a call chain topology corresponding to the view service.
9. A computer device, characterized in that the computer device comprises:
a memory, a processor, and a computer program stored on the memory and executable on the processor;
the computer program implementing the steps of the call chain data generation method according to any one of claims 1 to 3 when executed by the processor.
10. A computer device, characterized in that the computer device comprises:
a memory, a processor, and a computer program stored on the memory and executable on the processor;
the computer program realizing the steps of the call chain topology generation method according to any one of claims 4 to 6 when executed by the processor.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011271375.3A CN112363855B (en) | 2020-11-13 | 2020-11-13 | Call chain data generation method, topology generation method and system and computer equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011271375.3A CN112363855B (en) | 2020-11-13 | 2020-11-13 | Call chain data generation method, topology generation method and system and computer equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112363855A true CN112363855A (en) | 2021-02-12 |
| CN112363855B CN112363855B (en) | 2021-06-18 |
Family
ID=74515592
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011271375.3A Active CN112363855B (en) | 2020-11-13 | 2020-11-13 | Call chain data generation method, topology generation method and system and computer equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112363855B (en) |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113094157A (en) * | 2021-02-25 | 2021-07-09 | 青岛海尔科技有限公司 | Generation method and device for calling topological graph, storage medium and electronic device |
| CN114301988A (en) * | 2021-12-22 | 2022-04-08 | 中国电信股份有限公司 | Distributed calling method and device, storage medium and electronic equipment |
| CN115022410A (en) * | 2022-05-27 | 2022-09-06 | 北京有竹居网络技术有限公司 | Network request tracking method, device and equipment |
| CN116431367A (en) * | 2023-06-12 | 2023-07-14 | 中国航空结算有限责任公司 | Method, system and computer readable storage medium for modifying ticket information |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108038145A (en) * | 2017-11-23 | 2018-05-15 | 携程旅游网络技术（上海）有限公司 | Distributed Services tracking, system, storage medium and electronic equipment |
| CN109359094A (en) * | 2018-08-03 | 2019-02-19 | 挖财网络技术有限公司 | A kind of full link tracing method and device of distributed system journal |
| CN109542639A (en) * | 2018-11-06 | 2019-03-29 | 用友网络科技股份有限公司 | A kind of processing method, processing unit for ensureing micro services and calling data consistency |
| CN109600254A (en) * | 2018-11-29 | 2019-04-09 | 恒生电子股份有限公司 | The generation method and related system of full link log |
| CN109923847A (en) * | 2018-08-29 | 2019-06-21 | 华为技术有限公司 | Call discovery method, apparatus, equipment and the storage medium of link |
| CN111124819A (en) * | 2019-12-10 | 2020-05-08 | 中国建设银行股份有限公司 | Method and device for monitoring full link |
| US20200175156A1 (en) * | 2018-12-03 | 2020-06-04 | Ebay Inc. | Highly scalable permissioned block chains |
| CN111324644A (en) * | 2018-11-28 | 2020-06-23 | 中国移动通信集团浙江有限公司 | Method and device for monitoring database connection storm under large-scale micro-service architecture |
| CN111797014A (en) * | 2020-06-30 | 2020-10-20 | 中国工商银行股份有限公司 | Cross-application case tracking method and device |
-
2020
- 2020-11-13 CN CN202011271375.3A patent/CN112363855B/en active Active
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108038145A (en) * | 2017-11-23 | 2018-05-15 | 携程旅游网络技术（上海）有限公司 | Distributed Services tracking, system, storage medium and electronic equipment |
| CN109359094A (en) * | 2018-08-03 | 2019-02-19 | 挖财网络技术有限公司 | A kind of full link tracing method and device of distributed system journal |
| CN109923847A (en) * | 2018-08-29 | 2019-06-21 | 华为技术有限公司 | Call discovery method, apparatus, equipment and the storage medium of link |
| CN109542639A (en) * | 2018-11-06 | 2019-03-29 | 用友网络科技股份有限公司 | A kind of processing method, processing unit for ensureing micro services and calling data consistency |
| CN111324644A (en) * | 2018-11-28 | 2020-06-23 | 中国移动通信集团浙江有限公司 | Method and device for monitoring database connection storm under large-scale micro-service architecture |
| CN109600254A (en) * | 2018-11-29 | 2019-04-09 | 恒生电子股份有限公司 | The generation method and related system of full link log |
| US20200175156A1 (en) * | 2018-12-03 | 2020-06-04 | Ebay Inc. | Highly scalable permissioned block chains |
| CN111124819A (en) * | 2019-12-10 | 2020-05-08 | 中国建设银行股份有限公司 | Method and device for monitoring full link |
| CN111797014A (en) * | 2020-06-30 | 2020-10-20 | 中国工商银行股份有限公司 | Cross-application case tracking method and device |
Non-Patent Citations (2)
| Title |
|---|
| CONG XIE等: "A Visual Analytics Framework for the Detection of Anomalous Call Stack Trees in High Performance Computing Applications", 《IEEE TRANSACTIONS ON VISUALIZATION AND COMPUTER GRAPHICS》 * |
| 杨朝晖等: "微服务编排在网管支撑系统中的研究与应用", 《电信工程技术与标准化》 * |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113094157A (en) * | 2021-02-25 | 2021-07-09 | 青岛海尔科技有限公司 | Generation method and device for calling topological graph, storage medium and electronic device |
| CN114301988A (en) * | 2021-12-22 | 2022-04-08 | 中国电信股份有限公司 | Distributed calling method and device, storage medium and electronic equipment |
| CN115022410A (en) * | 2022-05-27 | 2022-09-06 | 北京有竹居网络技术有限公司 | Network request tracking method, device and equipment |
| CN116431367A (en) * | 2023-06-12 | 2023-07-14 | 中国航空结算有限责任公司 | Method, system and computer readable storage medium for modifying ticket information |
| CN116431367B (en) * | 2023-06-12 | 2023-09-08 | 中国航空结算有限责任公司 | Method, system and computer readable storage medium for modifying ticket information |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112363855B (en) | 2021-06-18 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112363855B (en) | Call chain data generation method, topology generation method and system and computer equipment | |
| CN109344183B (en) | Data interaction method and device, computer equipment and storage medium | |
| CN109474578B (en) | Message checking method, device, computer equipment and storage medium | |
| CN111625593B (en) | Block chain-based data processing method and device and computer equipment | |
| CN110503385B (en) | Service processing method, device, computer equipment and storage medium | |
| CN110909629B (en) | Face recognition data processing method and device, computer equipment and storage medium | |
| CN110688598A (en) | Service parameter acquisition method and device, computer equipment and storage medium | |
| CN110910143A (en) | Identity identification generation method, device, related node and medium | |
| CN112055078A (en) | Data transmission method and device, computer equipment and storage medium | |
| CN113360301A (en) | Message transmission system and method | |
| CN111539683A (en) | Contract signing method, device, equipment and medium | |
| CN112560939B (en) | Model verification method and device and computer equipment | |
| CN113626218A (en) | Data processing method, data processing device, storage medium and computer equipment | |
| CN112433925A (en) | Log generation method and device based on artificial intelligence, computer equipment and medium | |
| CN111405027B (en) | Block chain consensus result screening method, device, computer equipment and storage medium | |
| CN114595219A (en) | Data storage method, device and system | |
| CN111274017B (en) | Resource processing method and device, electronic equipment and storage medium | |
| CN114429408B (en) | Method, device, equipment and system for checking configuration file of intelligent substation | |
| CN112861004B (en) | Method and device for determining rich media | |
| CN114092246A (en) | Problem positioning method and device for financial transaction link | |
| CN113691618A (en) | Message notification method, device, message center and storage medium | |
| CN112560938A (en) | Model training method and device and computer equipment | |
| CN104572649A (en) | Data processing method, device and system for distributed storage system | |
| CN111510484B (en) | Block chain processing method, system, device, computer equipment and storage medium | |
| CN115017550B (en) | Electronic contract data processing method and device, computer equipment and medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |