WO2023098634A1

WO2023098634A1 - Information processing method and apparatus

Info

Publication number: WO2023098634A1
Application number: PCT/CN2022/134793
Authority: WO
Inventors: 李娟娟; 傅文林; 邓自立; 姜思哲
Original assignee: 阿里云计算有限公司
Priority date: 2021-12-01
Filing date: 2022-11-28
Publication date: 2023-06-08
Also published as: CN113869989A; CN113869989B

Abstract

The present application provides an information processing method and apparatus. By means of the present application, a worker of a tenant does not need to manually select a required basic service component in a server or to manually configure dependency relationships between basic service components, instead a component call link that actually appears in the server in a historical process can be directly provided to the tenant, and the component call link that actually appears in the server is often an actually available component call link (the dependency relationships between the basic service components are determined), so that labor costs can be reduced and the experience of the tenant can be improved while the actual needs of the tenant are met. Secondly, by clustering and separately selecting a component call link from each component call link set obtained by means of clustering, in order to avoid, as much as possible, providing a large number of similar component call links to the tenant, the degree of repeated push is reduced, and further the difficulty for the tenant to select a required component call link from the provided component call links is reduced.

Description

An information processing method and device

This application claims the priority of the Chinese patent application with the application number 202111451539.5 and the invention title "An Information Processing Method and Device" filed with the China Patent Office on December 01, 2021, the entire contents of which are incorporated in this application by reference .

technical field

The present application relates to the field of new generation information technology, in particular to an information processing method and device.

Background technique

With the rapid development of technology, the server has developed rapidly. Developers can deploy a large number of basic service components in the server for rent by tenants, and call the basic service components of the server when tenants need to provide services for customers. To process the customer's online data in order to provide services to customers.

For example, in an e-commerce scenario, a customer can place an order on the tenant’s e-commerce platform. After the e-commerce platform receives the request from the customer to place an order, the e-commerce platform needs to create an order. When creating an order, It is necessary to obtain the amount of the order, the order number that generated the order, the name of the product in the order, and the delivery address of the product in the order, etc.

When obtaining the amount of the order, it is necessary to obtain the selling price of the product, the discount information of the product, the discount information of the e-commerce platform, and the red envelope in the customer account.

In the above example, getting the amount of the order needs to be based on the basic service component used to get the amount, the order number of the generated order needs to be based on the basic service component used to generate the order number, and the name of the product in the order needs to be based on the method used to get the product The basic service component of the name of the name, the receiving address of the goods in the order needs to be based on the basic service component used to obtain the receiving address.

When obtaining the amount of an order based on the basic service component used to obtain the amount, it is necessary to obtain the selling price of the product, the discount information of the product, the discount information of the e-commerce platform, and the red envelope in the customer account. Among them, obtaining the selling price of the product needs to be based on the basic service component used to obtain the selling price, obtaining the discount information of the product needs to be based on a basic service component used to obtain the discount information, and obtaining the discount information of the e-commerce platform needs to be based on another The basic service components for obtaining preferential information and obtaining the red envelopes in the customer account need to be based on the basic service components for obtaining red envelopes, that is, the purpose of generating orders needs to be realized based on the corresponding basic service components.

Among them, the server connects to tenants, and tenants can be entities that need to provide services to customers, such as some e-commerce companies and some short video companies.

When tenants need to provide services to customers, they need to have the ability to provide services to customers. In order to have the ability to provide services to customers, tenants can generate service models, which can process the online data of customers. Realize the provision of services to our customers.

In order to be able to generate a service model, tenants can rent the required basic service components from the server according to their actual needs, and generate a service model. The service model includes the component identifiers of the leased basic service components and records the basic components corresponding to each component identifier. Dependencies between service components, the generated service model is deployed on the tenant's platform, and when the tenant's platform processes the customer's online data, the tenant's platform sequentially starts from the service according to the component identification and dependencies in the service model Call the basic service components in the terminal to process the online data to provide services to customers.

Among them, when the tenant rents the required basic service components from the server according to their actual needs, the staff of the tenant can manually select the required basic service components in the server based on work experience, and secondly, manually configure them based on work experience Dependencies between various basic service components.

Contents of the invention

This application shows an information processing method and device.

In the first aspect, the present application shows an information processing method, which is applied to the server, and the method includes: when the tenant needs to generate a service model with the help of the basic service components provided in the server, obtain the Multiple component call links that have actually appeared in the server. The multiple component call links are formed during the process of the server processing the real online data of the customer in the historical process; multiple component call links in the Similar component calling links are clustered to obtain at least one component calling link set; in each component calling link set, respectively select at least one component calling link applicable to the tenant; provide the selected component calling link to the tenant, To enable the tenant to at least generate a service model with the help of the provided component invocation link.

In the second aspect, the present application shows an information processing device, which is applied to the server, and the device includes: an acquisition module, used to acquire In the historical process, multiple component call links actually appeared in the server. The multiple component call links were formed during the process of the server processing the customer's real online data in the historical process; the clustering module, It is used to cluster similar component call links in multiple component call links to obtain at least one component call link set; the selection module is used to select at least one component call link set applicable to the tenant respectively A component call link; providing a module for providing a selected component call link to the tenant, so that the tenant at least generates a service model by using the provided component call link.

In a third aspect, the present application shows an electronic device, the electronic device comprising: a processor; a memory for storing instructions executable by the processor; wherein the processor is configured to perform any of the foregoing aspects method shown.

In the fourth aspect, the present application shows a non-transitory computer-readable storage medium. When the instructions in the storage medium are executed by the processor of the electronic device, the electronic device can execute the Methods.

In a fifth aspect, the present application shows a computer program product. When the instructions in the computer program product are executed by the processor of the electronic device, the electronic device can execute the method as shown in any one of the foregoing aspects.

Description of drawings

In the drawings, unless otherwise specified, the same reference numerals designate the same or similar parts or elements throughout the several drawings. The drawings are not necessarily drawn to scale. It should be understood that these drawings only depict some embodiments disclosed according to the application, and should not be regarded as limiting the scope of the application.

FIG. 1 is a flowchart of steps of an information processing method of the present application.

Fig. 2 is a flow chart of steps of a method for obtaining a component invocation link of the present application.

Fig. 3 is a flow chart of steps of a method for invoking link clustering of components in the present application.

FIG. 4 is a schematic diagram of a dependency relationship among basic service components of the present application.

FIG. 5 is a flow chart of steps of a method for selecting a component invoking link of the present application.

FIG. 6 is a structural block diagram of an information processing device of the present application.

Fig. 7 is a structural block diagram of a device of the present application.

Detailed ways

In order to make the above objects, features and advantages of the present application more obvious and comprehensible, the present application will be further described in detail below in conjunction with the accompanying drawings and specific implementation methods.

As mentioned in the background technology, when a tenant needs to use the basic service components in the server to generate a service model, the tenant needs to manually select the required basic service components in the server and manually configure the dependencies between the basic service components .

However, the inventor found that the above method requires the participation of the tenant's staff, resulting in high labor costs for the tenant.

Secondly, when the tenant's staff has little work experience, the basic service components manually selected according to the needs may not match the basic service components actually needed for online data processing, and the manual configuration of the basic service components The dependency relationship may not match the actual dependency relationship required for online data processing, resulting in the failure of the generated service model to process the customer's online data normally, resulting in the inability to provide services to the customer normally.

Therefore, the inventor proposes the desire to reduce labor costs when the tenant generates a service model with the help of the basic service components in the server, and the desire to make the generated service model conform to the actual needs of the tenant.

In order to reduce labor costs when the tenant generates a service model with the help of the basic service components in the server, and to make the generated service model conform to the actual needs of the tenant, the inventor carefully checked the real The multiple component call links that have appeared are analyzed. The multiple component call links are formed during the process of the server processing the real online data of each customer in the historical process. After careful analysis, the inventor found that , when the server processes at least some of the customers’ real online data, the component invocation chains composed of the basic service components called sequentially in the server are the same or similar, that is, the component invocation chains involved in at least some of the customers Paths can be reused.

In this case, if some customers need to use the basic service components in the server to generate service models, you can provide these customers with component calls formed during the process of the server processing other customers' real online data in the historical process Links (often actually available component call links), for these tenants to directly generate their own service models with the help of the provided component call links, or make small modifications to the provided component call links to make the modification The modified component call link meets its own actual needs, and generates its own service model with the help of the modified component call link. In this way, the tenant's workload can be reduced, labor costs can be reduced, and the generated service model can be made available and meet the tenant's actual needs as much as possible.

Referring to FIG. 1 , it shows a schematic flow chart of an information processing method of the present application. The method is applied to a server, etc., and the method includes:

In step S101, when the tenant needs to generate a service model with the help of the basic service components provided in the server, obtain multiple component call links that actually appeared in the server in the historical process, and multiple component call links It is formed in the process of the server processing the real online data of the customer in the historical process.

A large number of basic service components are configured in the server for tenants to call when providing services to customers, for example, when processing online data of customers.

A component call link includes multiple basic service components, and there are dependencies among at least some of the multiple basic service components.

For example, in the component call link, if one basic service component is called normally, another service may be called normally, and the other basic service component depends on the one basic service component.

For example, in one example, when the server processes the customer's online data submitted by the tenant, it is necessary to call the basic service component A. When calling the basic service component A, it is necessary to call the basic service component B and the basic service component C. And the basic service component D, when the basic service component D is called, the basic service component E and the basic service component F need to be called.

In the above example, the component call link includes: basic service component A, basic service component B, basic service component C, basic service component D, basic service component E, and basic service component F. And in this component call link, basic service component A depends on basic service component B, basic service component C and basic service component D, and basic service component D depends on basic service component E and basic service component F.

In the historical process, the server has processed a large amount of online data. When processing each online data, it will call some basic service components and there is a logical sequence between these basic service components. The logical sequence reflects these Dependencies between basic service components, etc.

In addition, the log file of each basic service component is recorded in the server, and the log file of the basic service component records: the component call link involved (for example, where) each time the basic service component is called in the historical process The link identification of each call, and the dependencies between other basic service components in the calling link of the components involved in each call, etc.

Through the log files of each basic service component, the server can obtain the call links of multiple components that actually appeared in the server in the historical process. For the specific acquisition method, refer to the embodiment shown in FIG. 2 , which will not be described in detail here.

In step S102, similar component calling links in multiple component calling links are clustered to obtain at least one set of component calling links.

Every two component calling links in any component calling link set are similar component calling links.

In this application, some component calling links are the same, some component calling links are different but similar, the basic service components included in the similar component calling links are similar, or, the similar component calling links include the The dependencies between the basic service components are similar, so that similar components call the links with the same or similar functions, for example, all the components that generate an order call the link or all the components that cancel the order call the link, etc.

Among them, when providing component call links to tenants, a small number of component call links can be provided to tenants to reduce the difficulty of tenant selection, etc. Therefore, similar component call links in multiple component call links can be aggregated class, at least one component call link set is obtained, and then step S103 is executed.

For the specific manner of clustering, refer to the embodiment shown in FIG. 3 , which will not be described in detail here.

In step S103, at least one component invocation link applicable to the tenant is selected from each component invocation link set.

In this application, for any set of component call links, the set of component call links often includes more than two component call links. In the scenario of providing component call links to tenants, a small amount of Component call links to reduce the difficulty of tenant selection, etc. In this way, for any set of component call links, some component call links can be selected from more than two component call links included in the component call link set To provide to the tenant, for example, select at least one component invocation link suitable for the tenant from the two or more component invocation links included in the set of component invocation links to provide to the tenant.

Wherein, for a specific selection manner, reference may be made to the embodiment shown in FIG. 4 , which will not be described in detail here.

In step S104, the selected component calling link is provided to the tenant, so that the tenant at least generates a service model by using the provided component calling link.

In one embodiment, the server can send the selected component call link to the terminal used by the tenant, so that the tenant can view the component call link on the terminal used by the tenant, and then can know which components are included in the component call link. Basic service components and the dependencies between the included basic service components, etc., and then refer to which basic service components are included in the component call link and the dependencies between the included basic service components, etc., to create your own service model, and then You can deploy the service model on your own platform, and use the service model to provide external services (such as providing services to customers, etc.).

In this application, when the tenant needs to generate a service model with the help of the basic service components provided in the server, obtain multiple component call links that actually appeared in the server in the historical process, multiple component call links It is formed when the server processes the customer's real online data in the historical process; similar component call links in multiple component call links are clustered to obtain at least one set of component call links; In the set of component invocation links, at least one component invocation link suitable for the tenant is selected respectively; the selected component invocation link is provided to the tenant, so that the tenant at least generates a service model by means of the provided component invocation link.

Through this application, the staff of the tenant does not need to manually select the required basic service components in the server and manually configure the dependencies between each basic service component, but can directly provide the tenant The component call links that actually appear in the server are often actually available component call links (the dependencies between basic service components have been determined), so that when the actual needs of tenants are met, This can reduce labor costs and improve tenant experience.

Secondly, by clustering and selecting component call links from each component call link set obtained by clustering, to avoid providing tenants with a large number of similar component call links as much as possible, reducing the degree of repeated push, and then The selection difficulty for the tenant to select the required component invocation link among the provided component invocation links is reduced.

In addition, since the component call links that actually appear in the server are often actually available component call links, it can avoid the situation that the manually configured component call links are unavailable due to lack of work experience. When the provided component invokes the link to generate the service model, it increases the possibility that the tenant can use the service model to process the online data of the customer normally, that is, the possibility that the tenant can provide services to the customer normally increases.

In an embodiment of the present application, referring to FIG. 2, step S101 can be implemented through the following process, including:

In step S201, log files of at least some of the basic service components configured in the server are acquired.

For any one of the multiple basic service components configured on the server, the log file of the basic service component records the invocation of the basic service component actually invoked by the server in the historical process.

Wherein, the log file of the basic service component may include multiple sub-files, and each sub-file is generated when the server actually invokes the basic service component in the historical process.

For example, whenever the basic service component is invoked according to the server, the basic service component is usually invoked according to a component invocation link, and the basic service component may have a relationship with other basic service components in the component invocation link. In this way, a sub-file can be generated in the log file of the basic service component, and the link identifier of the component calling link can be recorded in the sub-file, to indicate that the event that the basic service component is called this time involves the A link identifier of a component call link, and it is recorded in the sub-file that the basic service component may have a dependency relationship with other basic service components in the component call link.

In this way, the log file that implements the basic service component records the link identification of each component call link involved in the basic service component and the dependency between the basic service component and other basic service components in the component call link. relation.

For example, in one example, a developer develops multiple basic service components in advance, and configures multiple basic service components into the server, so that multiple basic service components are configured on the server.

The server can call some basic service components in turn according to the actual needs of the tenants, and the basic service components called in turn form a component call link. For example, tenants use the basic service components of the server to provide services to customers. In order to solve some actual needs of customers, tenants need to call some basic service components of the server, and a component call link is formed between the basic service components called.

When the server invokes the first basic service component according to the actual needs of the tenant, a sub-file will be generated in the log file of the first basic service component. Then generate a link ID and record the link ID in the subfile.

When the server invokes the second basic service component that the first basic service component depends on according to the actual needs of the tenant, a sub-file will be generated in the log file of the second basic service component. And record the generated link ID in the sub-file. Secondly, the dependency relationship on the second basic service component can be recorded in the sub-file, for example, the component identifier of the first basic service component that depends on the second basic service component, etc. can be recorded.

When the server invokes the third basic service component that the second basic service component depends on according to the actual needs of the tenant, a sub-file will be generated in the log file of the third basic service component. And record the generated link ID in the sub-file. Secondly, the dependency relationship on the second basic service component can be recorded in the sub-file, for example, the component identifier of the second basic service component that depends on the third basic service component, etc. can be recorded.

In this way, according to the log file of each basic service component, it is possible to restore multiple component call links that actually appeared in the server in the historical process, and the specific restoration method can refer to step S202.

These component call links actually existed in the historical process. In this way, at least part of the component call links in these component call links that actually existed in the historical process can be provided to the tenant for the tenant to generate the service model refer to.

In step S202, according to at least part of the log files of the basic service components, a plurality of component call links that actually appeared in the server in the historical process are constructed.

In an embodiment of the present application, this step can be implemented through the following process, including:

2011. Among multiple basic service components, the links recorded in the filter log file identify the same basic service components.

The link identifier recorded in the log file in any basic service component is: when the basic service component is called during the process of forming the component call link corresponding to the link identifier, the log file in the basic service component stored in.

In this application, the log files of each basic service component configured in the server include multiple sub-files.

For any sub-file in the log file of any basic service component, obtain the link identifier in the sub-file, and then log files in other basic service components in multiple basic service components except this basic service component Search for the link identifier in each sub-file in the log file, determine that the log file includes the basic service component "recording the sub-file with the link identifier", and determine the basic service component and the determined basic service component as the log file The link in identifies the same basic service component, and for each other sub-file in the log file of the basic service component and for each other sub-file in the log file of each other basic service component, perform the above operation in the same way, Then execute step 2012.

Through this step, multiple basic service components may be obtained, and the same link identifier is recorded in the log files of each basic service component in each basic service component.

For each basic service component, the process of step 2012 can be executed separately, so as to obtain the component invocation link corresponding to each basic service component.

Among the obtained multiple basic service components, some two basic service components may have the same basic service component, and some two basic service components may not have the same basic service component.

2012. Combining the filtered basic service components into a component invocation link according to the dependencies between the filtered basic service components recorded in the log files of the filtered basic service components.

Among them, for any basic service component that is screened, the log file of the basic service component records: among the basic service components that are screened, the component ID of the basic service component that depends on the basic service component, that is, the component ID The corresponding basic service component depends on the basic service component.

The same is true for every other underlying service component of the filter.

In this application, in a possible situation, there will not be two identical sub-links in the component call link and the two sub-links are dependent on the same basic service component. However, sometimes in the actual call In the process of basic service components, some basic service components may fail to be called due to some external reasons, and these basic service components will be called again until the call is successful. However, there are two components in the component call link. The above sub-links, two or more of these links form more than two sub-component call links, and the two or more sub-component call links are the same and are all dependent on the same basic service component. In fact, more than two sub-component calling links are repeated, and only one sub-component calling link in the two or more sub-component calling links needs to exist in the component calling link.

Therefore, in this case, after the component call link is obtained through combination, part of the subcomponent call links in the two or more subcomponent call links can be deleted in the combined component call link, Only one sub-component call link in the two or more sub-component call links may be reserved, so as to realize the simplification of the combined component call links.

For example, in one embodiment, after step 2012, it may be determined whether there are at least two identical subcomponent invocation links in the combined component invocation links and the same at least two subcomponent invocation links are all used by the same basic service Component dependencies. The subcomponent calling link may include one basic service component, or more than two basic service components with dependencies, etc. In the case where the same two sub-component call links exist in the combined component call link and the same at least two sub-component call links are all dependent on the same basic service component, in the combined component call link, Part of the same at least two subcomponent calling links is deleted, so that one of the at least two subcomponent calling links remains in the combined component calling links.

In another embodiment of the present application, providing the component invocation link to the tenant is for the tenant to refer to the component invocation link to generate a service model for providing to customers.

In order to improve the experience of tenants and customers, it is necessary to ensure that at least one basic service component fails to be successfully called in the component call link provided to tenants. Otherwise, after the tenant generates a service model based on this component call link, In the case of providing services to a large number of tenants according to this service model, the basic service components will still be called according to the above link, but there may also be situations where the call is not successful (for example, even if the call is repeated multiple times, the call may not be successful, etc.) , which makes it impossible for tenants to use the service model to provide services to customers normally, reducing the experience of tenants and customers.

Therefore, in another embodiment of the present application, after step 2011, it may be determined whether each basic service component with the same link ID is successfully invoked in the same component invocation link involved.

In the case that each basic service component with the same link ID is successfully invoked in the same component call link involved, then according to the log files of the filtered basic service components, the dependencies between the filtered basic service components Relationship, which combines the filtered basic service components into a component call link.

In the case that at least one basic service component fails to be invoked successfully in the above-mentioned component calling link involved in each basic service component, each basic service component with the same link identifier is discarded.

In an embodiment of the present application, the server often connects with a large number of tenants, and different tenants involve different service scenarios, for example, different tenants provide different types of services to various customers.

For example, some tenants involve short video scenarios, some tenants involve e-commerce scenarios, some tenants involve cloud storage scenarios, some tenants involve game scenarios, and some tenants involve communication and social networking scenarios, etc.

In addition, there are often a large number of basic service components configured on the server side, and the basic service components involved in different service scenarios are different.

For example, some basic service components are only used in short video scenarios, some basic service components are only used in e-commerce scenarios, some basic service components are only used in cloud storage scenarios, and some basic service components are used in It will only be used in game scenarios, and some tenants will only be used in communication and social scenarios. Of course, some basic service components may be used in more than two service scenarios.

However, tenants are often involved in some scenarios, not all scenarios.

If a certain basic service component does not involve the scene involved in the tenant, the component call link where the basic service component is located often does not involve the scene involved in the tenant, that is, the component call link where the basic service component is located It is useless to the tenant, and it is not necessary to provide the tenant with the component call link where the basic service component is located, otherwise the tenant will get a component call link that he will not actually use, which will lead to the accuracy of the provision Low and degraded tenant experience.

Therefore, in order to avoid the above situation, in another embodiment of the present application, when obtaining the log files of at least some of the basic service components configured in the server in step S201, the tenant-related service scene. The service scenarios involved by the tenant may be entered by the tenant on the server side. Then, among the multiple basic service components configured in the server, determine the basic service component involved in the service scenario. Afterwards, the log files of the basic service components involved in the service scenario can be obtained.

For example, for any basic service component configured on the server, the service scenario involved in the basic service component can be determined in advance, and stored in the corresponding relationship between the component ID of the basic service component and the service scenario involved in the basic service component. The component identification of the basic service component and the service scenarios involved in the basic service component are the same for every other basic service component configured on the server.

In this way, among the multiple basic service components configured on the server, when determining the basic service component involved in the service scenario, in the corresponding relationship between the component identifier of the basic service component and the service scenario involved in the basic service component, Find the component ID of the basic service component corresponding to the service scenario, and determine the basic service component corresponding to the found component ID as the basic service component involved in the service scenario.

In this application, the tenant can develop a service model based on the basic service component of the component call link provided by the server, so as to provide services to customers through the service model.

However, if the component call link provided to the tenant is an unavailable component call link or an available but unreliable component call link, it will cause the service model generated by the tenant according to the provided component call link to be in the actual call process Unavailability or unreliability will affect tenants' ability to provide services to customers through the service model.

Therefore, in order to avoid this situation, in the present application, it is necessary to provide a component invocation link that is normally available and highly reliable to the tenant.

In order to provide tenants with normally available and highly reliable component invocation links, in this application, the component invocation links may not be restored based on abnormal and low reliability basic service components.

In order not to restore component call links based on abnormal and low-reliability basic service components, you can not obtain the log files of abnormal and low-reliability basic service components, so that in the process of restoring component call links later, no The component call link will be restored based on the log files of abnormal and low-reliability basic service components, and the component call link will only be restored based on the log files of normal and high-reliability basic service components, so that the restored component calls The basic service components in the link are normal and highly reliable.

In order not to obtain log files of abnormal and low-reliability basic service components, when obtaining log files of at least some of the multiple basic service components configured in the server in step S201, the Status indicators of each basic service component of the configured multiple basic service components in a historical process. Among the multiple basic service components configured in the server, determine the basic service components whose state indicators meet the preset requirements. Then get the log files for the identified underlying service components.

Wherein, when obtaining the state indicators of each basic service component in the historical process of the multiple basic service components configured in the server, for any one of the multiple basic service components, you can obtain the historical process The basic service component has the first number of occurrences of the target state, and then the first number of occurrences is used as a state indicator of the basic service component in a historical process.

The target state may include a call failure state or a call abnormal state, or the target state may include other possible states other than call normal.

However, the inventors found that for the basic service component, the basic service component itself may cause the target state of the basic service component, and the target state of the basic service component that the basic service component depends on may also cause the basic The service component has the target state.

That is to say, sometimes when the basic service component has the target state, it may be caused by the basic service component itself, or it may be caused by the basic service component that the basic service component depends on.

Therefore, the obtained first occurrence times of the target state of the basic service component in the historical process not only includes: the number of times the basic service component itself causes the target state to appear in the basic service component, but also includes: the basic service component The number of times the dependent basic service component appears in the target state and causes the basic service component to appear in the target state.

The target state of the basic service component that the basic service component depends on causes the target state of the basic service component to have nothing to do with the basic service component itself causing the target state of the basic service component, that is, the basic service component that the basic service component depends on The number of occurrences of the target state caused by the target state of the basic service component should not be recorded in the first number of occurrences, otherwise the first number of occurrences will be inaccurate, and it is likely that the basic service component that meets the preset requirements will be misjudged It is a basic service component that does not meet the requirements, and if the basic service component that is misjudged as not meeting the requirements is closely related to the service scenario involved by the tenant, the tenant cannot be provided with a component call link that includes the basic service component. As a result, tenants cannot obtain component call links that are likely to be useful to tenants and that may need to be referenced, reducing the provision efficiency.

Therefore, in order to solve the above problem, in another embodiment of the present application, when obtaining the state indicators of each basic service component in the historical process of the multiple basic service components configured in the server, for multiple basic service components Any one of the basic service components in , obtain the first occurrence times of the target state of the basic service component in the historical process.

For example, the number of occurrences of the target state corresponding to the component ID of the basic service component may be found in the correspondence between the component ID of the basic service component and the number of occurrences of the target state, and used as the first number of occurrences. The correspondence between the component ID of the basic service component and the number of occurrences of the target state stores a plurality of corresponding entries, and each corresponding table item includes a component ID of the basic service component and the number of occurrences of the target state of the basic service component. first count.

And, acquire the second occurrence times of the target state of the basic service component that the basic service component directly depends on in the historical process.

For example, in the corresponding relationship between the component ID of the basic service component and the number of occurrences of the target state, the number of occurrences of the target state corresponding to the component ID of the basic service component directly dependent on the basic service component can be found, if the base If there is only one service that the service component directly depends on, the found number of occurrences of one is used as the second number of occurrences. If the basic service component directly depends on multiple services, the found numbers of occurrences can be summed to obtain the second number of occurrences.

Then at least according to the first appearance number and the second appearance number, the status index of the basic service component in the historical process is acquired. For example, the difference between the first occurrence number and the second occurrence number can be calculated and used as a status indicator of the basic service component in the historical process.

In another embodiment of the present application, referring to FIG. 3, step S102 may be implemented through the following process, including:

In step S301, the link similarity between every two component call links among the plurality of component call links is obtained respectively.

The similarity between component calling links can be determined according to the types of basic service components included in the component calling links and the dependencies between basic service components.

In some embodiments, this step can be implemented through the following processes, including:

3011. Obtain the link information of each component call link in the string form of the multiple component call links respectively, the link information in the string form includes: the string form of the basic service component included in the component call link Component IDs and dependencies between the underlying service components included in the component call chain.

Wherein, for any component call link among the plurality of component call links, the link information of the component call link in the form of a string can be obtained, and the link information of the component call link in the form of a string includes: The component identification of the basic service component included in the component calling link and the dependency relationship among the basic service components included in the component calling link. The same is true for each of the other component call chains in the plurality of component call chains.

In this application, the component identifiers of different basic service components are different.

If a certain basic service component depends on another basic service component, if it is possible to successfully call another basic service component after successfully calling a certain basic service component, then the other basic service component depends on this certain basic service component.

In an example, for example, referring to FIG. 4 , it is assumed that the component calling link includes basic service component A, basic service component B, basic service component C, basic service component D, basic service component E, and basic service component F.

And the basic service component A depends on the basic service component B, the basic service component C and the basic service component D respectively, and the basic service component D depends on the basic service component E and the basic service component F respectively.

Among them, the component ID of the basic service component A is "A", the component ID of the basic service component B is "B", the component ID of the basic service component C is "C", and the component ID of the basic service component D is "D", The component ID of the basic service component E is "E", and the component ID of the basic service component F is "F".

Then the link information in the string form of the component calling link may include [A[B C D[E F]]].

It can be seen from the link information in the string form of the component call link that the basic service component E and the basic service component F are respectively dependent on the basic service component D, and the basic service component B, the basic service component C and the basic service component D are respectively Depended on by the basic service component A.

3012. Acquire the link distance between every two component call links in the multiple component call links according to the link information in the form of a character string of each component call link in the multiple component call links.

This step can be achieved through the following processes, including:

21) Converting the link information in the string form of each component call link among the multiple component call links into vector form link information.

For any component call link of multiple component call links, in the link information of the component call link in string form, the component identifier of each basic service component in the component call link in string form Encode them separately to obtain the component identifiers in the form of vectors of each basic service component included in the component call link.

A component ID in the form of a string is a string, and a component ID in the form of a vector is a vector.

For example, encode the component identifier "A" of the basic service component A in the form of a character string to obtain the component identifier "[1 2 2 4]" of the basic service component A in the form of a vector. The same is true for base service components B, C, D, E, and F.

Then, use the component identifiers in the vector form of each basic service component included in the component call link to replace the corresponding component identifiers in the string form of the link information in the string form of the component call link to obtain the component Call the intermediate link information of the link.

For example, for any basic service component in the component call link, use the vector form component identifier of the basic service component to replace the string of the basic service component in the link information of the component call link in the string form The component identification in the form of , for each other basic service component in the calling link of this component, perform the above operation in the same way. Thus, the intermediate link of the component calling link is obtained.

Afterwards, normalize the component identifiers in the vector form of each basic service component in the intermediate link of the component call link, and obtain the link information in the vector form of the component call link.

For example, each number in each vector-form component identifier (a vector representation) in the intermediate link of the component call link is obtained respectively, the sum of the squares of each number is calculated, and the square root of the sum is calculated, Divide each number in each vector form component identifier (a vector representation) in the intermediate link of the component call link by the square root of the sum value to obtain the vector form link of the component call link information. In order to improve the accuracy rate of the link distance between the two component calling links obtained in step 22) according to the link information in the form of the vector calling links of the two components.

22) Acquiring the link distance between every two component calling links among the multiple component calling links according to the vector form link information of every two component calling links among the multiple component calling links.

For any two component call links in multiple component call links, the Euclidean distance between the vector form link information of the two component call links can be calculated, and used as the distance between the two component call links link distance, etc.

The same is true for every other two component calling links in the multiple component calling links, so that the link distance between every two component calling links in the multiple component calling links is respectively obtained.

3013. According to the link distance between every two component calling links in the multiple component calling links, respectively acquire the link similarity between every two component calling links in the multiple component calling links.

In this application, for any two component call links in multiple component call links, if the link distance between the two component call links is greater, the link between the two component call links The smaller the link similarity between the two components is, the smaller the link distance between the two component call links is, the greater the link similarity between the two component call links is.

Therefore, in an example, the reciprocal of the link distance between the calling links of the two components may be calculated to obtain the link similarity between the calling links of the two components.

In step S302, among multiple component call links, component call links whose link similarity is greater than a preset similarity are aggregated into a set of component call links.

In one embodiment of the present application, a clustering algorithm may be used to cluster multiple component call links based on the link similarity between every two component call links in the multiple component call links, to obtain at least A component called LinksCollection.

Clustering algorithms can include: dbscan (Density-Based Spatial Clustering of Applications with, density-based clustering algorithm) or k-means (k-means clustering algorithm, k-means clustering algorithm) or infomap (community discovery algorithm based on information theory )wait.

In an embodiment of the present application, referring to FIG. 5, step S103 can be implemented through the following process, including:

In step S401, the number of actual occurrences of each component call link in the component call link set in the server and/or the number of basic service components included in each component call link is obtained.

In one embodiment of the present application, the number of actual occurrences of each component invocation link in the component invocation link set in the server end may be acquired.

Wherein, for the set of component calling links, it often includes multiple component calling links.

Sometimes, some of the links in the component call link set are the same (the same can be understood as including the same basic service components and the same dependencies between the included basic service components, etc.), so this part of the links in In the historical process, it has actually appeared M times in the server, and M is equal to the number of links in this part.

Among them, for any component call link in the component call link set, if there is no component call link in the component call link set other than the component call link If the same component call link is used, it means that the component call link has actually appeared once in the server in the historical process.

Among the other component call links in the component call link set, if there are N component call links identical to the component call link, it means that the component call link is in the historical process The number of actual occurrences in the server is N+1 times, where N is a positive integer.

Or, in another embodiment of the present application, the number of basic service components respectively included in each component invocation link in the component invocation link set may be obtained.

Or, in yet another embodiment of the present application, the number of actual occurrences of each component call link in the component call link set in the server and the number of basic service components included in each component call link can be obtained .

In step S402, according to the number of actual occurrences of each component call link in the server and/or the number of basic service components included in each component call link, select the applicable component in each component call link set Invoke link for at least one component of the tenant.

In one embodiment of the present application, if what is obtained in step S401 is the number of actual occurrences of each component invocation link in the component invocation link set in the server, then in step S402, the component invocation link can be called In the link set, select at least one component to call the link in descending order of the number of times it has actually appeared in the server.

Or, in another embodiment of the present application, if what is obtained in step S401 is the number of basic service components respectively included in each component call link in the component call link set, then in step S402, the In the set of component invocation links, at least one component invocation link is selected in descending order of the number of included basic service components.

Or, in another embodiment of the present application, if each component call link in the set of component call links obtained in step S401 actually appears on the server side and each component call link includes The number of basic service components, then in step 4202, for any component call link in the component call link set, the number of times the component call link has actually appeared in the server and the component call link The number of basic service components included in the route, obtain the component call link provided score, for each other component call link in the component call link set, perform the above operations, so as to get the component call link set The score provided by each component call link, and then, in the set of component call links, at least one component call link is selected in descending order of the provided score.

Among them, when obtaining the provision score of the component call link according to the number of times the component call link has actually appeared in the server in the historical process and the number of basic service components included in the component call link, you can According to the following formula to achieve:

Wherein, in the above formula, S is the score provided by the component calling the link.

w1 is a first preset coefficient, and w2 is a second preset coefficient.

X is the number of times the component call link actually appears in the server, and Y is the number of basic service components included in the component call link.

C1 is a first preset value, and C2 is a second preset value.

C1 may include the average number of times that each component call link actually appeared in the server in the historical process and so on.

C2 may include an average value of the number of basic service components included in each component call link that has appeared in the server, and the like.

Wherein, the sum of the first preset coefficient w1 and the second preset coefficient w2 may be equal to a specific value, and the specific value includes 1, 1.5 or 2, etc., which is not limited in this application.

The first preset coefficient w1 may be greater than or equal to 0 and less than or equal to a specific value, and the second preset coefficient w2 may be greater than or equal to 0 and less than or equal to a specific value.

It should be noted that, for the method embodiment, for the sake of simple description, it is expressed as a series of action combinations, but those skilled in the art should know that the application is not limited by the described action sequence, because according to this application, certain steps may be performed in another order or simultaneously. Secondly, those skilled in the art should also know that the embodiments described in the specification are all optional embodiments, and the actions involved are not necessarily required by this application.

Referring to FIG. 6, it shows a structural block diagram of an information processing device of the present application, which is applied to the server. The device may specifically include the following modules:

The acquisition module 11 is used to obtain multiple component call links that actually appeared in the server in the historical process when the tenant needs to generate a service model with the help of the basic service components provided in the server. The multiple component call chains The route is formed by the server during the process of processing the real online data of the customer in the historical process; the clustering module 12 is used to cluster similar component call links in multiple component call links to obtain at least one A set of component call links; a selection module 13, used to select at least one component call link applicable to the tenant in each set of component call links; a providing module 14, used to provide the selected component call link to the tenant, To enable the tenant to at least generate a service model with the help of the provided component invocation link.

In some implementations, the selection module includes: a first obtaining unit, configured to obtain the number of actual occurrences of each component call link in the component call link set in the server and/or each component call link The number of basic service components included in respectively; the selection unit is used to select the number of basic service components included in each component call link according to the number of times each component call link actually appears in the server and/or the number of basic service components included in each component call link. At least one component invocation link applicable to the tenant is selected from each component invocation link set.

In some embodiments, the selection unit includes: a first selection subunit, configured to select at least one component in the component call link set in descending order of the number of actual occurrences in the server call link; or, the second selection subunit is used to select at least one component call link in the set of component call links in descending order of the number of basic service components included; or, the first acquisition The subunit is used to call a link for each component in the component call link set, according to the number of times the component call link has actually appeared in the server and the basic service components included in the component call link The quantity of the component call link is obtained to obtain the score provided by the component call link, and the third selection subunit is used to select at least one component call link in the order of the provided score from high to low in the set of component call links.

In some implementations, the clustering module includes: a second acquisition unit, configured to respectively acquire the link similarity between every two component invocation links in the plurality of component invocation links; an aggregation unit, for Aggregating component call links whose link similarity is greater than a preset similarity among multiple component call links is aggregated into a set of component call links.

In some embodiments, the second acquiring unit includes: a second acquiring subunit, configured to respectively acquire the link information in the form of a character string of each component invoking link in the plurality of component invoking links, the The link information includes: the component identification of the basic service component included in the component call link in the form of a string and the dependency relationship between the basic service components included in the component call link; the third acquisition subunit is used to The link information of each component call link in the string form of each component call link in the component call link, and obtain the link distance between every two component call links in the multiple component call links; the fourth acquisition subunit, The method is used to respectively acquire the link similarity between every two component calling links among the multiple component calling links according to the link distance between every two component calling links among the multiple component calling links.

In some implementations, the third obtaining subunit is specifically configured to: convert the link information in the form of a character string of each component call link in the plurality of component call links into link information in the form of a vector; The link information of every two component call links in the multiple component call links in vector form is obtained to obtain the link distance between every two component call links in the multiple component call links.

In some implementations, the third obtaining subunit is specifically configured to include: for any component calling link of a plurality of component calling links, in the link information in the string form of the component calling link , the component identifications in the form of character strings of each basic service component in the component invocation link are encoded separately, and the component identifications in the form of vectors of each basic service component included in the component invocation link are respectively obtained; using the component invocation The component identifiers in the form of vectors of each basic service component included in the link are respectively replaced with the corresponding component identifiers in the form of strings in the link information of the component invocation link in the form of a character string to obtain the Intermediate link information: normalize the component identifiers in vector form of each basic service component in the intermediate link of the component invocation link to obtain the vector form link information of the component invocation link.

In some implementations, the acquisition module includes: a third acquisition unit, configured to acquire log files of at least some of the basic service components configured in the server, where the log file records: basic service The link identification of the component call link involved in each call of the component in the historical process, and the dependencies between other basic service components in the component call link involved in each call; the building unit, It is used to construct call links of multiple components that actually appeared in the server in the historical process according to the log files of at least some basic service components.

In some implementations, the construction unit includes: a screening subunit, used to filter the links recorded in the log files to identify the same basic service component among multiple basic service components; Dependencies between the filtered basic service components recorded in the log files of the basic service components, and the filtered basic service components are combined into a component call link.

In some implementations, the construction unit further includes: a first determining subunit, configured to determine whether there are at least two subcomponent calling links that are the same and the same at least two subcomponent calling links in the combined component calling links All paths are dependent on the same basic service component; delete the subunit, so that there are two identical subcomponent call links in the combined component call link and the same at least two subcomponent call links are all used by the same basic service In the case of component dependence, in the combined component call link, delete some subcomponent call links in the same at least two subcomponent call links, so that at least two subcomponent call links remain in the combined component call link A child component in the call chain calls the chain.

In some implementations, the construction unit further includes: a second determination subunit, configured to determine whether each basic service component with the same link identifier is successfully invoked in the same component invocation link involved in it; the combination The sub-unit is also used for: in the case that each basic service component with the same link identifier is successfully invoked in the same component call link involved, according to the filtered basic service component recorded in the log file The dependencies between service components combine the filtered basic service components into a component call link.

In some implementations, the third obtaining unit includes: a fifth obtaining subunit, configured to obtain service scenarios involved in tenants; a first determining subunit, configured to select the basic service components configured in the server , determining the basic service component related to the service scenario; the sixth acquiring subunit is configured to acquire the log file of the basic service component related to the service scenario.

In some implementations, the third acquisition unit includes: a seventh acquisition subunit, configured to acquire the state indicators of each basic service component in the historical process of the multiple basic service components configured in the server; the second The determination subunit is used to determine the basic service components whose state indicators meet the preset requirements among the multiple basic service components configured in the server; the eighth acquisition subunit is used to obtain the log files of the determined basic service components.

In some implementations, the seventh obtaining subunit is specifically configured to: for any one of the multiple basic service components, obtain the first number of occurrences of the target state of the basic service component in the historical process, Acquiring the second number of occurrences of the target state of the basic service component that the basic service component directly depends on in the historical process; acquiring the state index of the basic service component in the historical process according to the first occurrence number and the second occurrence number.

The embodiment of the present application also provides a non-volatile readable storage medium, and one or more modules (programs) are stored in the storage medium. When the one or more modules are applied to the device, the device can execute Instructions for each method step in the embodiments of the present application.

The embodiments of the present application provide one or more machine-readable media, on which instructions are stored, and when executed by one or more processors, the electronic device executes the method described in one or more of the above embodiments. In the embodiment of the present application, the electronic device includes a server, a gateway, a sub-device, etc., and the sub-device is an Internet of Things device or the like.

Embodiments of the present disclosure can be implemented as an apparatus using any appropriate hardware, firmware, software, or any combination thereof to perform desired configurations, and the apparatus may include servers (clusters), terminal devices such as IoT devices and other electronic devices.

FIG. 7 schematically illustrates an exemplary apparatus 1300 that may be used to implement various embodiments described in this application.

For one embodiment, FIG. 7 illustrates an exemplary apparatus 1300 having one or more processors 1302, a control module (chipset) 1304 coupled to at least one of the processor(s) 1302 , memory 1306 coupled to control module 1304, non-volatile memory (NVM)/storage device 1308 coupled to control module 1304, one or more input/output devices 1310 coupled to control module 1304, and Coupled to the network interface 1312 of the control module 1304 .

The processor 1302 may include one or more single-core or multi-core processors, and the processor 1302 may include any combination of general-purpose processors or special-purpose processors (such as graphics processors, application processors, baseband processors, etc.). In some embodiments, the apparatus 1300 can serve as a server device such as a gateway in the embodiments of this application.

In some embodiments, apparatus 1300 may include one or more computer-readable media (e.g., memory 1306 or NVM/storage 1308) having instructions 1314 and in combination with the one or more computer-readable media configured to The one or more processors 1302 execute instructions 1314 to implement modules to perform the actions described in this disclosure.

For one embodiment, the control module 1304 may include any suitable interface controller to provide any suitable Interface.

The control module 1304 may include a memory controller module to provide an interface to the memory 1306 . A memory controller module may be a hardware module, a software module and/or a firmware module.

Memory 1306 may be used, for example, to load and store data and/or instructions 1314 for apparatus 1300 . For one embodiment, memory 1306 may comprise any suitable volatile memory, such as suitable DRAM. In some embodiments, memory 1306 may include Double Data Rate Quad Synchronous Dynamic Random Access Memory (DDR4 SDRAM).

For one embodiment, control module 1304 may include one or more input/output controllers to provide interfaces to NVM/storage device(s) 1308 and input/output device(s) 1310 .

For example, NVM/storage 1308 may be used to store data and/or instructions 1314 . NVM/storage 1308 may include any suitable non-volatile memory (e.g., flash memory) and/or may include any suitable non-volatile storage device(s) (e.g., one or more hard drives ( HDD), one or more compact disc (CD) drives, and/or one or more digital versatile disc (DVD) drives).

NVM/storage 1308 may include storage resources that are physically part of the device on which apparatus 1300 is installed, or may not necessarily be part of the device that are accessible by the device. For example, NVM/storage 1308 may be accessed over a network via input/output device(s) 1310 .

The input/output device(s) 1310 may provide an interface for the apparatus 1300 to communicate with any other suitable device, and the input/output device 1310 may include a communication component, a pinyin component, a sensor component, and the like. Network interface 1312 may provide an interface for device 1300 to communicate over one or more networks, and device 1300 may communicate with one or more wireless networks according to any of one or more wireless network standards and/or protocols. Components communicate wirelessly, such as accessing wireless networks based on communication standards, such as WiFi, 2G, 3G, 4G, 5G, etc., or a combination of them for wireless communication.

For one embodiment, at least one of the processor(s) 1302 may be packaged with the logic of one or more controllers of the control module 1304 (eg, a memory controller module). For one embodiment, at least one of the processor(s) 1302 may be packaged with the logic of one or more controllers of the control module 1304 to form a system-in-package (SiP). For one embodiment, at least one of the processor(s) 1302 may be integrated on the same die as the logic of the one or more controllers of the control module 1304 . For one embodiment, at least one of the processor(s) 1302 may be integrated on the same die with the logic of the one or more controllers of the control module 1304 to form a system on chip (SoC).

In various embodiments, the apparatus 1300 may be, but not limited to, a terminal device such as a server, a desktop computing device, or a mobile computing device (eg, a laptop computing device, a handheld computing device, a tablet computer, a netbook, etc.). In various embodiments, device 1300 may have more or fewer components and/or a different architecture. For example, in some embodiments, device 1300 includes one or more cameras, a keyboard, a liquid crystal display (LCD) screen (including a touchscreen display), a non-volatile memory port, multiple antennas, a graphics chip, an application-specific integrated circuit ( ASIC) and speakers.

An embodiment of the present application provides an electronic device, including: one or more processors; and one or more machine-readable media having instructions stored thereon, when executed by the one or more processors, The electronic device is caused to perform one or more of the methods described in this application.

As for the device embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and for relevant parts, please refer to the part of the description of the method embodiment.

Each embodiment in this specification is described in a progressive manner, each embodiment focuses on the difference from other embodiments, and the same and similar parts of each embodiment can be referred to each other.

Embodiments of the present application are described with reference to flowcharts and/or block diagrams of methods, terminal devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each procedure and/or block in the flowchart and/or block diagram, and a combination of procedures and/or blocks in the flowchart and/or block diagram can be realized by computer program instructions. These computer program instructions can be provided to a general-purpose computer, special purpose computer, embedded processor or processor of other programmable information processing terminal equipment to produce a machine, so that the instructions executed by the computer or other programmable information processing terminal equipment Produce means for realizing the functions specified in one or more procedures of the flowchart and/or one or more blocks of the block diagram.

These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable information processing terminal to operate in a specific manner, such that the instructions stored in the computer-readable memory produce an article of manufacture comprising instruction means, the The instruction means implements the functions specified in one or more procedures of the flowchart and/or one or more blocks of the block diagram.

These computer program instructions can also be loaded into a computer or other programmable information processing terminal equipment, so that a series of operation steps are executed on the computer or other programmable terminal equipment to produce computer-implemented processing, so that the computer or other programmable terminal equipment The instructions executed above provide steps for implementing the functions specified in one or more procedures of the flowchart and/or one or more blocks of the block diagram.

While a few examples of the embodiments of the present application have been described, additional changes and modifications can be made to these examples by those skilled in the art once the basic inventive concept is understood. Therefore, the appended claims are intended to be construed to include these embodiments and all changes and modifications that fall within the scope of the embodiments of the application.

Finally, it should also be noted that in this text, relational terms such as first and second etc. are only used to distinguish one entity or operation from another, and do not necessarily require or imply that these entities or operations, any such actual relationship or order exists. Furthermore, the term "comprises", "comprises" or any other variation thereof is intended to cover a non-exclusive inclusion such that a process, method, article, or terminal equipment comprising a set of elements includes not only those elements, but also includes elements not expressly listed. other elements identified, or also include elements inherent in such a process, method, article, or terminal equipment. Without further limitations, an element defined by the phrase "comprising a ..." does not exclude the presence of additional identical elements in the process, method, article or terminal device comprising said element.

The information processing method and device provided by this application have been introduced in detail above. In this paper, specific examples have been used to illustrate the principle and implementation of this application. The description of the above embodiments is only used to help understand the method and implementation of this application. Its core idea; at the same time, for those of ordinary skill in the art, according to the idea of this application, there will be changes in the specific implementation and application scope. limit.

Claims

An information processing method applied to a server, the method comprising:

In the case that the tenant needs to generate a service model with the help of the basic service components provided in the server, obtain the call links of multiple components that actually appeared in the server in the historical process. Formed during the process of processing the real online data of customers;

Clustering similar component call links in multiple component call links to obtain at least one set of component call links;

In each set of component invocation links, select at least one component invocation link applicable to the tenant;

The selected component invocation link is provided to the tenant, so that the tenant at least generates a service model by means of the provided component invocation link.
The method according to claim 1, wherein said selecting at least one component invocation link applicable to the tenant in each component invocation link set includes:

Obtain the number of actual occurrences of each component call link in the component call link set in the server and/or the number of basic service components included in each component call link;

According to the number of actual occurrences of each component call link in the server and/or the number of basic service components included in each component call link, select at least one applicable to the tenant in each component call link set Component call link.
The method according to claim 2, wherein, according to the number of actual occurrences of each component call link in the server and/or the number of basic service components included in each component call link, in each component Select at least one component invocation link applicable to the tenant in the invocation link set, including:

In the set of component invocation links, select at least one component invocation link in descending order of the number of actual occurrences in the server;

or,

In the set of component call links, select at least one component call link in descending order of the number of basic service components included;

or,

For each component call link in the component call link set, according to the number of times the component call link has actually appeared in the server and the number of basic service components included in the component call link, obtain the The provided score of the above-mentioned component call link, in the component call link set, select at least one component call link according to the order of the provided score from high to low.
The method according to claim 1, wherein the clustering of similar component call links in multiple component call links to obtain at least one set of component call links includes:

Respectively obtain the link similarity between every two component call links in the multiple component call links;

Aggregating component call links whose link similarity is greater than a preset similarity among multiple component call links is aggregated into a set of component call links.
The method according to claim 4, wherein said respectively obtaining the link similarity between every two component call links in the plurality of component call links comprises:

Obtain the link information of each component call link in the string form of multiple component call links respectively, the link information in the string form includes: the component in the string form of the basic service component included in the component call link Identify and depend on the basic service components included in the component call chain;

Obtain the link distance between every two component call links in the multiple component call links according to the link information in the form of a character string of each component call link in the multiple component call links;

According to the link distance between every two component calling links in the multiple component calling links, the link similarity between every two component calling links in the multiple component calling links is acquired respectively.
The method according to claim 5, wherein, according to the link information in the form of a character string of each component call link in the multiple component call links, every two component call links in the multiple component call links are acquired Link distance between links, including:

Converting the link information in the string form of each component call link in the plurality of component call links into the link information in the vector form;

A link distance between every two component call links in the multiple component call links is acquired according to the vector form link information of every two component call links in the multiple component call links.
The method according to claim 6, wherein said converting the link information in character string form of each component call link in the plurality of component call links into link information in vector form respectively comprises:

For any component call link of multiple component call links, in the link information in the string form of the component call link, in the string form of each basic service component in the component call link The component identifiers are coded separately to obtain the component identifiers in the form of vectors of each basic service component included in the component call link;

Use the component identifiers in vector form of each basic service component included in the component invocation link to replace the corresponding component identifiers in the form of strings in the link information in the form of character strings in the component invocation link, to obtain the The intermediate link information of the component call link;

The vector-form component identifiers of each basic service component in the intermediate link of the component invocation link are normalized to obtain the vector-form link information of the component invocation link.
The method according to claim 1, wherein said obtaining a plurality of component call links that actually appeared in the server during the historical process comprises:

Obtain the log files of at least some of the basic service components configured in the server. The log files record: the link of the component call link involved in each call of the basic service component in the historical process Identify, and the dependencies between other basic service components in the component call chain involved in each call;

Based on the log files of at least some of the basic service components, construct call links of multiple components that actually appeared in the server in the historical process.
The method according to claim 8, wherein, according to at least part of the log files of the basic service components, constructing a plurality of component call links that actually appeared in the server during the historical process includes:

Among multiple basic service components, the link recorded in the filter log file identifies the same basic service component;

According to the dependency relationship between the filtered basic service components recorded in the log file of the filtered basic service components, the filtered basic service components are combined into a component call link.
The method according to claim 9, wherein the method further comprises:

Determine whether there are at least two identical subcomponent invocation links in the combined component invocation links and the same at least two subcomponent invocation links are all dependent on the same basic service component;

In the case where the same two sub-component call links exist in the combined component call link and the same at least two sub-component call links are all dependent on the same basic service component, in the combined component call link, Part of the same at least two subcomponent calling links is deleted, so that one of the at least two subcomponent calling links remains in the combined component calling links.
The method according to claim 9, wherein the method further comprises:

Determine whether each basic service component with the same link ID is successfully called in the same component call link involved in it;

In the case that each basic service component with the same link ID is finally called successfully in the same component call link involved in it, and then execute the filtered basic service component according to the log file of the filtered basic service component. Dependency, the step of combining the filtered basic service components into a component call chain.
The method according to claim 8, wherein said acquiring the log files of at least some of the basic service components configured in the server comprises:

Obtain the service scenarios involved in the tenant;

Among the multiple basic service components configured in the server, determine the basic service components involved in the service scenario;

Obtain log files of basic service components related to the service scenario.
The method according to claim 8, wherein said acquiring the log files of at least some of the basic service components configured in the server comprises:

Obtain the status indicators of each basic service component in the historical process of multiple basic service components configured in the server;

Among the multiple basic service components configured in the server, determine the basic service components whose status indicators meet the preset requirements;

Get log files for identified underlying service components.
The method according to claim 13, wherein said obtaining status indicators of each basic service component in the historical process of the multiple basic service components configured in the server comprises:

For any basic service component among multiple basic service components, obtain the first occurrence number of the target state of the basic service component in the historical process, and obtain the occurrence of the basic service component that the basic service component directly depends on in the historical process the second occurrence of the target state;

The state indicators of the basic service components in the historical process are acquired according to the first occurrence times and the second occurrence times.
An electronic device comprising a memory, a processor, and a computer program stored on the memory and operable on the processor, wherein the processor implements the program described in any one of claims 1 to 14 when executing the program steps of the method.
A computer-readable storage medium, wherein a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 14 are implemented.