Intelligent agent deployment method and device

Abstract

The embodiment of the invention provides an agent deployment method and device, and the method is applied to a configuration center, and comprises the steps: receiving registration information sent when an atomic power service and an application service are started; receiving service dependency information sent by the application service; constructing a service dependency relationship graph according to the service dependency information, and determining configuration dependency coverage according to the service dependency relationship graph, the service access address and the service configuration information; and when it is determined that the configuration dependency coverage meets a preset coverage threshold, determining that deployment of the target agent is completed. According to the method, full-process automation from parameter configuration to state verification is achieved, the operation and maintenance threshold is remarkably reduced while efficient and accurate agent deployment is guaranteed, and technical support is provided for intelligent transformation of enterprises.

Description

Technical Field

[0001] This specification relates to the field of intelligent agent technology, and particularly to an intelligent agent deployment method. This specification also relates to an intelligent agent deployment apparatus, a computing device, a computer-readable storage medium, and a computer program product. Background Technology

[0002] As enterprises accelerate their intelligent transformation, intelligent agents, as the core carriers of automation and intelligence, have been widely applied in customer service, process management, data analysis, and other fields. However, in actual deployment, the complexity and dynamism of intelligent agent systems bring many challenges to configuration management.

[0003] For example, intelligent agent applications typically consist of multiple modules, each requiring the configuration of numerous parameters, including model version, API (Application Programming Interface) keys, and service dependencies. Manual configuration is highly susceptible to errors that can lead to service anomalies, such as incorrect port number configuration causing functional failure. Furthermore, dynamic parameters generated in containerized deployment environments (such as random ports and dynamic IPs) must be manually acquired and updated on-site, lacking automated tools. In addition, deployment often involves non-technical personnel with limited understanding of specialized parameters (such as model hyperparameters and encryption keys), further increasing the risk of configuration errors. Summary of the Invention

[0004] In view of this, one or more embodiments of this specification provide an agent deployment method, an agent deployment device, a computing device, a computer-readable storage medium, and a computer program product to solve the technical problems in the prior art where agent deployment is highly dependent on manual operation, resulting in low efficiency, high error rate, and high maintenance difficulty.

[0005] According to a first aspect of one or more embodiments of this specification, an agent deployment method is provided, applied to a configuration center, comprising: Receive registration information sent when the atomic capability service and application service start up, wherein the registration information includes service access address and service configuration information; Receive service dependency information sent by the application service, wherein the service dependency information is used to represent at least one atomic capability service that the application service depends on; Based on the service dependency information, a service dependency graph is constructed, and based on the service dependency graph, the service access address, and the service configuration information, the configuration dependency coverage is determined. If the configuration dependency coverage meets the preset coverage threshold, the target agent is determined to be deployed successfully, wherein the target agent is collaboratively constructed based on the atomic capability service and the application service.

[0006] According to a second aspect of one or more embodiments of this specification, an intelligent agent deployment apparatus is provided, applied to a configuration center, comprising: The registration information receiving module is configured to receive registration information sent when the atomic capability service and application service start up, wherein the registration information includes service access address and service configuration information; The dependency information receiving module is configured to receive service dependency information sent by the application service, wherein the service dependency information is used to represent at least one atomic capability service that the application service depends on. The dependency coverage determination module is configured to construct a service dependency graph based on the service dependency information, and determine the configuration dependency coverage based on the service dependency graph, the service access address, and the service configuration information. The agent deployment module is configured to determine that the target agent deployment is complete when the configuration dependency coverage meets a preset coverage threshold, wherein the target agent is collaboratively constructed based on the atomic capability service and the application service.

[0007] According to a third aspect of one or more embodiments of this specification, a computing device is provided, comprising: Memory and processor; The memory is used to store computer programs / instructions, and the processor is used to execute the computer programs / instructions, which, when executed by the processor, implement the steps of the above-described intelligent agent deployment method.

[0008] According to a fourth aspect of one or more embodiments of this specification, a computer-readable storage medium is provided that stores a computer program / instructions that, when executed by a processor, implement the steps of the above-described agent deployment method.

[0009] According to a fifth aspect of one or more embodiments of this specification, a computer program product is provided, including a computer program / instructions that, when executed by a processor, implement the steps of the above-described intelligent agent deployment method.

[0010] The intelligent agent deployment method provided in one or more embodiments of this specification is applied to a configuration center, comprising: receiving registration information sent by an atomic capability service and an application service at startup, wherein the registration information includes a service access address and service configuration information; receiving service dependency information sent by the application service, wherein the service dependency information is used to represent at least one atomic capability service on which the application service depends; constructing a service dependency graph based on the service dependency information, and determining a configuration dependency coverage based on the service dependency graph, the service access address, and the service configuration information; and determining that the target intelligent agent deployment is complete when the configuration dependency coverage meets a preset coverage threshold, wherein the target intelligent agent is collaboratively constructed based on the atomic capability service and the application service.

[0011] Specifically, this intelligent agent deployment method first automates the registration information reporting of each service upon startup, achieving automated collection and reporting of service parameters and avoiding manual configuration. Second, it constructs a service dependency graph by receiving service dependency information declared by application services and calculates configuration dependency coverage by combining service access addresses and service configuration information. This provides deployment personnel with a real-time view of the intelligent agent deployment status, allowing non-technical personnel to intuitively understand the deployment status, quickly identify missing dependent services, and reduce reliance on specialized knowledge. Furthermore, by setting a preset coverage threshold as the standard for intelligent agent deployment completion, the method automatically confirms the deployment completion status when the configuration dependency coverage meets the preset threshold, significantly shortening the verification time for intelligent agent deployment. This method achieves full-process automation from parameter configuration to status verification, ensuring efficient and accurate intelligent agent deployment while significantly reducing the operational threshold and providing technical support for enterprise intelligent transformation. Attached Figure Description

[0012] To more clearly illustrate the technical solutions in the embodiments or prior art of this specification, the drawings used in the description of the embodiments or prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in this specification. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0013] Figure 1 This is an execution flowchart of an intelligent agent deployment method provided in one embodiment of this specification; Figure 2 This is a flowchart of an embodiment of an intelligent agent deployment method provided in this specification; Figure 3 This is an application diagram of an agent deployment method provided in one embodiment of this specification; Figure 4This is a schematic diagram of the structure of an intelligent agent deployment device provided in one embodiment of this specification; Figure 5 This is a structural block diagram of a computing device provided in one embodiment of this specification. Detailed Implementation

[0014] To enable those skilled in the art to better understand the technical solutions in this specification, the technical solutions in the embodiments of this specification will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this specification, and not all embodiments. Based on the embodiments in this specification, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of this specification.

[0015] This specification uses specific terms to describe embodiments thereof. Terms such as "an embodiment," "one embodiment," and / or "some embodiments" refer to a particular feature, structure, or characteristic associated with at least one embodiment of this specification. Therefore, it should be emphasized and noted that references to "an embodiment," "one embodiment," or "an alternative embodiment" in different locations throughout this specification do not necessarily refer to the same embodiment. Furthermore, those skilled in the art can combine and integrate the different embodiments or examples described herein, as well as the features of those different embodiments or examples, without contradiction.

[0016] The terminology used in one or more embodiments of this specification is for the purpose of describing particular embodiments only and is not intended to be limiting of the one or more embodiments of this specification. The singular forms “a,” “an,” “an,” “the,” and “the” as used in one or more embodiments of this specification and the appended claims are also intended to include the plural forms unless the context clearly indicates otherwise. It should also be understood that the term “and / or” as used in one or more embodiments of this specification includes any or all possible combinations of one or more associated listed items.

[0017] The terms “comprising,” “including,” or any other variations thereof are intended to cover a non-exclusive inclusion, such that a process, method, product, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, product, or apparatus. Without further limitation, the presence of additional identical or equivalent elements in the process, method, product, or apparatus that includes said elements is not excluded.

[0018] Although the terms "first," "second," etc., may be used to describe various information in one or more embodiments of this specification, this information should not be limited to these terms. These terms are only used to distinguish information of the same type from one another. For example, "first" may also be referred to as "second," and similarly, "second" may also be referred to as "first," without departing from the scope of one or more embodiments of this specification. Ordinal numbers such as "first," "second," etc., do not necessarily indicate order; often they are used to facilitate the distinction of objects. For example, "first server" and "second server" usually refer to two servers. To distinguish these two servers, they are described as "first server" and "second server." Of course, sometimes these two servers may be the same server.

[0019] Depending on the context, the word "if" as used here can be interpreted as "when," "when," or "in response to determination."

[0020] In this specification, unless explicitly stated otherwise, "receiving and sending data" does not necessarily mean direct receiving and sending; it can also mean indirect receiving and sending. For example, A receiving data sent by B can be understood as A directly receiving the data sent by B, or it can be understood as A indirectly receiving the data sent by B through other entities such as C. Similarly, B sending data to A can be understood as B sending the data directly to A, or it can be understood as B indirectly sending the data to A through other entities such as C. Here, C can be one entity, or it can be two or more entities.

[0021] In this specification, unless explicitly stated otherwise, the relationships between structures can be direct or indirect. For example, when describing "A is connected to B," unless it is explicitly stated that A and B are directly connected, it should be understood that A can be directly connected to B or indirectly connected to B. Similarly, when describing "A is on top of B," unless it is explicitly stated that A is directly above B (AB is adjacent and A is above B), it should be understood that A can be directly above B or indirectly above B (AB is separated by other elements, and A is above B). And so on.

[0022] The user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in one or more embodiments of this specification are all information and data authorized by the user or fully authorized by all parties. The collection, use and processing of related data shall comply with the relevant laws, regulations and standards of the relevant regions, and corresponding operation entry points shall be provided for users to choose to authorize or refuse.

[0023] The technical solutions provided in one or more embodiments of this specification can employ deep learning models with relatively large model parameter scales. Here, "large model" is merely an example, and the one or more embodiments of this specification do not limit the number of model parameters supported by the deep learning model used, aiming to meet actual needs. The deep learning models involved in one or more embodiments of this specification can be artificial intelligence-based language models (LM), multimodal models (MM), large language models (LLM), multimodal pre-training models, etc.

[0024] In practical applications, large models only require a small number of samples to fine-tune the pre-trained model before they can be applied to different tasks. Large models can be widely used in fields such as Natural Language Processing (NLP) and Computer Vision. Specifically, they can be applied to computer vision tasks such as Visual Question Answering (VQA), Image Captioning (IC), and Image Generation, as well as NLP tasks such as text-based sentiment classification, text summarization, and machine translation. The main application scenarios for large models include digital assistants, intelligent robots, search, online education, office software, e-commerce, and intelligent design.

[0025] The following explains the terms and concepts used in one or more embodiments of this specification.

[0026] Configuration Center: In a microservice architecture, the configuration center is a system that centrally manages the configuration information of all services, solving the pain points of traditional configurations being scattered and difficult to update dynamically. It achieves separation of configuration and code through unified storage, dynamic push, and version control, supporting multi-environment isolation and access control.

[0027] Intelligent agent: An intelligent agent is an entity that can perceive its environment and take autonomous actions to achieve a specific goal. It can be software, hardware, or a system.

[0028] Large models: Large models are machine learning models with a large number of parameters and complex computational structures, usually referring to deep learning models.

[0029] Multimodal large models: Multimodal large models are deep learning models capable of handling multiple data types (text, images, audio, video, etc.) and achieving more complex tasks through cross-modal interaction. For example, generating videos or answering questions after inputting images and text.

[0030] Docker: An open-source containerization platform that allows developers to package applications and their dependencies into lightweight, portable containers that can run in any Docker-enabled environment.

[0031] A Kubernetes cluster is a container orchestration system consisting of multiple nodes used to automate the deployment, scaling, and management of containerized applications. Kubernetes is often abbreviated as K8s.

[0032] Webhook: A user-defined HTTP (Hypertext Transfer Protocol) callback mechanism. When a specific event occurs, the server sends an HTTP request to a pre-configured URL (Uniform Resource Identifier), enabling event-driven integration.

[0033] YAML: YAML Ain't Markup Language, a human-readable data serialization format commonly used in configuration files (such as Kubernetes and Docker Compose).

[0034] JSON: JavaScript Object Notation, a lightweight data interchange format that is easy for humans to read and write, and also easy for machines to parse and generate.

[0035] Embedding. In artificial intelligence, it refers to the technique of mapping high-dimensional discrete data (such as words or images) to a low-dimensional continuous vector space, which facilitates model processing and similarity calculation.

[0036] Reranker: In information retrieval or recommendation systems, a re-ranking mechanism is used to perform a secondary sorting of initial search results to improve relevance or ranking quality. It is commonly used in RAG (Retrieval-Augmented Generation) systems.

[0037] As enterprises accelerate their intelligent transformation, intelligent agents, as the core carriers of automation and intelligence, have been widely applied in customer service, process management, data analysis, and other fields. However, in actual deployment, the complexity and dynamism of intelligent agent systems bring many challenges, especially in configuration management, where the following pain points exist: Complex configuration parameters and susceptibility to human error: Intelligent agent applications typically consist of multiple modules, each involving numerous parameters (such as model version, API keys, service dependencies, etc.). For example, a typical intelligent agent system may contain dozens of service components, each requiring configuration of critical parameters such as IP address, port, URI, and authentication information. Manually configuring these parameters is not only time-consuming and labor-intensive but also prone to service startup failures or functional malfunctions due to negligence or misoperation. For instance, when a company deployed an intelligent customer service system, an incorrect configuration of the voice recognition service port number caused the voice interaction function to completely fail, necessitating redeployment and troubleshooting, resulting in project interruption and wasted resources.

[0038] Dynamic parameters need to be generated on-site, relying on manual input: During service deployment, many parameters (such as service IP address, domain name, and port) need to be dynamically generated based on the actual operating environment. For example, containerized agent services (such as Docker or Kubernetes clusters) will be assigned random ports or dynamic domain names, and this information needs to be obtained in real time after the service starts and populated into the configuration file. However, the current lack of automation tools means that operations and maintenance personnel need to manually record and modify the configuration files.

[0039] The deployment of intelligent agents is challenging for non-technical personnel, posing significant configuration difficulties. This is because agent deployment often involves cross-departmental collaboration, and on-site deployment personnel may not be service developers and may lack understanding of parameter meanings. For example, when deploying a production monitoring agent, a manufacturing company's operations team mistakenly set the "maximum number of retries" parameter to 0, causing the system to directly interrupt service under abnormal conditions instead of retrying and recovering as expected. Furthermore, some parameters (such as model hyperparameters and encryption keys) require specialized knowledge for correct configuration, making it difficult for non-technical personnel to identify errors and further increasing configuration risks.

[0040] To solve the above technical problems, there are two implementation solutions: Solution 1, "Configuration is centrally generated and pushed by the configuration center" and Solution 2, "Customers manually fill in the configuration on-site".

[0041] Option 1: Centrally manage the configuration parameters of all services through a configuration center, and automatically generate a complete configuration before deployment, which is then pushed to the container or service instance at the customer's site via the network. Its core principle includes the following steps: Centralized configuration management: All service configuration parameters (such as IP address, port, URI, model version, API key, etc.) are stored in the cloud configuration center; the configuration center supports multi-environment isolation (development, testing, production) and access control to ensure the consistency and security of configuration.

[0042] Automated generation and distribution: During the deployment phase, the configuration center dynamically generates complete configuration files based on preset rules (such as service dependencies and resource allocation strategies); and pushes the configuration to the service instances at the customer's site through long polling or long connection mechanisms (such as Webhook).

[0043] Dynamic update capability: Supports real-time updates of runtime configurations (such as adjusting service ports or switching model versions), which take effect without restarting the service.

[0044] Disadvantages of Option 1: Data security risks: The network connection between the customer's site and the public cloud configuration center may violate corporate security policies. For example, some financial or security institutions require all data to be processed in a closed loop within the internal network, prohibiting the transmission of sensitive configuration information (such as IP addresses and authentication keys) over the public network. Unpredictable dynamic parameters: Some parameters (such as the IP address of containerized deployments and temporarily generated ports) need to be dynamically obtained when starting services at the customer's site and cannot be generated in advance in the configuration center.

[0045] Option 2: This option requires operations personnel or the customer to manually enter configuration parameters during deployment, typically through a configuration file or interactive interface. Its core principle includes the following steps: Localized operation: All configuration parameters are generated on-site at the customer's location, without relying on external network connections; configuration files are stored in YAML, JSON, or text format for service startup.

[0046] Flexible adaptation: On-site personnel can adjust parameters according to the actual network environment (such as IP allocation, port conflicts) to meet non-standard requirements.

[0047] Disadvantages of Option 2: High configuration error rate: The number of parameters is enormous (e.g., IPs, ports, and dependencies of dozens of service components), and some parameters have complex meanings (e.g., model hyperparameters, encryption algorithms). Non-technical personnel may misfill or overlook key fields (e.g., failure to configure the load balancer address). Difficult problem localization: Services may fail to start due to configuration errors during deployment, but the error messages are not intuitive (e.g., "connection timeout" may be caused by incorrect IP addresses or port conflicts). Troubleshooting requires checking configuration files layer by layer, which is time-consuming and prone to omissions.

[0048] To address the aforementioned technical deficiencies, one or more embodiments of this specification provide an agent deployment method that achieves automatic service registration and dependency management through a configuration center, thereby realizing full automation of the agent deployment process. One or more embodiments of this specification also relate to an agent deployment apparatus, a computing device, a computer-readable storage medium, and a computer program product, which will be described in detail in the following embodiments.

[0049] The technical solutions provided in the various embodiments of this specification are described in detail below with reference to the accompanying drawings.

[0050] See Figure 1 , Figure 1 This is an execution flowchart of an intelligent agent deployment method provided in one embodiment of this specification.

[0051] Step 102: Start the configuration center.

[0052] Specifically, the startup of the configuration center can be understood as the configuration center starting as the core coordination component, completing its own service initialization (such as loading basic configuration, establishing the service registry storage structure, starting the service listening port, accurately receiving registration requests from each service component, initializing the health detection module, and preparing for subsequent dependency verification) and obtaining a stable network access endpoint (fixed IP address or domain name), providing an access foundation for subsequent service registration and discovery.

[0053] Step 104: Start the atomic capability service.

[0054] Specifically, the startup of an atomic capability service can be understood as the sequential startup and execution of each atomic capability service (including the basic model, embedded / reordering services, voice services, etc.). First, it reads the access address of the configuration center from the pre-configured environment variables and initiates a registration request to the configuration center based on this address, registering its own service metadata (including dynamically generated IP addresses, ports, and service configuration parameters). Upon receiving the registration information reported by the atomic capability service startup, the configuration center performs format validation on the registration information, such as verifying the validity of the IP address and port range to prevent invalid configurations. If the validation is successful, the service instance of the atomic capability service is entered into the service registry.

[0055] Step 106: Start the primary application service.

[0056] Specifically, the startup of a Level 1 application service can be understood as follows: after starting, the Level 1 application service automatically performs two operations. First, it reads the access address of the configuration center from the pre-configured environment variables and requests the access addresses and configuration information of the atomic capability services it depends on from the configuration center. Based on the access addresses and configuration information of the atomic capability services, it checks the availability of the atomic capability services (e.g., performing basic network probing on the access addresses of each dependent atomic capability service to ensure route reachability; using the configuration information of the atomic capability services, it calls the health check interface of each dependent atomic capability service and performs health checks based on the internal status of the atomic capability services returned by the interface, such as whether the dependent database connection is normal and whether the internal thread pool is healthy). Then, it completes its own initialization (e.g., loading its own project model, rule engine, initializing internal cache, etc.) and health self-check (including but not limited to process status, key project indicators, etc.). Only after it starts up without errors and the dependencies are verified successfully does the Level 1 application service officially register with the configuration center. Based on the access address of the configuration center, it initiates a registration request to the configuration center and registers its own service metadata (including dynamically generated IP address, port, and service configuration parameters, etc.).

[0057] The configuration center receives and verifies the registration information reported by the primary application service upon startup. It performs format validation on this registration information, such as verifying the validity of the IP address and port range to prevent invalid configurations. If the validation is successful, the service instance of the primary application service is entered into the service registry. Communication links with its dependent atomic capability services are automatically established. Based on this, the configuration center builds a service dependency graph, recording the successfully established dependency connections.

[0058] Step 108: Start the secondary application service.

[0059] Specifically, the startup of a secondary application service can be understood as the automatic execution of registration and multi-level dependency acquisition operations after the secondary application service starts. First, it reads the access address of the configuration center from the pre-configured environment variables, and requests information about its dependent atomic capability services and primary application services from the configuration center based on the access address. After checking that the atomic capability services and primary application services are available based on this information, it completes its own initialization (such as loading its own project model, rule engine, initializing internal cache, etc.) and health self-check (including but not limited to process status, key project indicators, etc.). Only when it starts up without errors and the dependency verification is passed, does the secondary application service officially register with the configuration center and register its own service metadata (including dynamically generated IP address, port and service configuration parameters, etc.).

[0060] The configuration center receives and verifies the registration information reported by the secondary application service upon startup. It performs format validation on this registration information, such as verifying the validity of the IP address and port range to prevent invalid configurations. If the validation is successful, the service instance of the secondary application service is entered into the service registry. The secondary application service automatically establishes communication links with its dependent primary application services and atomic capability services. Based on this, the configuration center updates the service dependency graph, fully recording cross-level dependency connections.

[0061] Step 110: Configure dependency coverage calculation.

[0062] Specifically, configuration dependency coverage calculation can be understood as the configuration center verifying the integrity of dependency relationships between service instances by traversing all dependency connections in the constructed service dependency graph. Based on the verification results, the number of successfully established dependency connections is counted, and the configuration dependency coverage is calculated as (number of established dependency connections / total number of dependency connections × 100%). This configuration dependency coverage can also be synchronized to the visual agent deployment status view in real time.

[0063] Step 112: Agent Deployment.

[0064] Specifically, agent deployment can be understood as follows: when the configuration dependency coverage reaches a preset coverage threshold of 100%, it automatically confirms that all service dependencies have been correctly established. At this point, the target agent is fully ready and can be officially deployed to the project. Conversely, when the configuration dependency coverage does not reach the preset coverage threshold, the missing dependency connections and their specific reasons can be clearly marked in the visualized agent deployment status view, thereby achieving accurate quantitative evaluation and visual display of the agent deployment status.

[0065] The agent deployment method provided in one or more embodiments of this specification firstly involves atomic capability services automatically registering their service capabilities as basic components. First-level application services obtain the required atomic service addresses through declarative dependencies, and second-level application services further establish cross-level service connections, forming end-to-end automated configuration. This eliminates error-prone steps such as manually configuring IP addresses and port parameters in traditional deployments, ensuring accurate establishment of service dependencies and avoiding deployment failures due to configuration errors. Secondly, based on configuration dependency coverage calculations, a precise metric for the agent deployment process is constructed. By tracking the connection status in the service dependency graph in real time, not only are quantitative indicators of agent deployment progress provided, but also the specific missing dependency components can be accurately located. This fine-grained visual management enables deployment personnel to quickly identify faulty components, significantly shortening the time-consuming troubleshooting process in traditional deployments. Simultaneously, by automatically determining the agent deployment completion status through preset coverage thresholds, subjective biases from manual judgment are avoided, and it is ensured that the agent is only put into operation when it reaches full readiness, significantly improving the reliability of the agent deployment process. Specifically, this intelligent agent deployment method transforms intelligent agent deployment from a manual operation that relies on professional experience to an automated operation. While ensuring accurate configuration, it significantly reduces the operation and maintenance threshold, providing technical support for the rapid deployment and stable operation and maintenance of enterprise intelligent systems.

[0066] See Figure 2 , Figure 2 This is a flowchart of an intelligent agent deployment method provided in one embodiment of this specification.

[0067] From a programming perspective, the entity executing the process can be a program hosted on an application server or application terminal. It can be understood that this method can be executed by any device, equipment, platform, or cluster of devices with computing and processing capabilities.

[0068] like Figure 2 As shown, the process may include the following steps: Step 202: Receive the registration information sent when the Atomic Capability Service and Application Service start up.

[0069] The registration information includes the service access address and service configuration information.

[0070] Specifically, the intelligent agent deployment method provided in one or more embodiments of this specification can be applied to the deployment of various complex intelligent agent systems, including but not limited to enterprise-level intelligent customer service system deployment: In customer service systems containing multiple modules such as speech recognition, natural language processing, dialogue management, and knowledge base retrieval, the intelligent agent deployment method provided in the embodiments of this specification can automatically establish inter-module dependency links. When the voice service version is upgraded or the project logic service is expanded, this method can dynamically update the service address and recalculate the coverage, ensuring that the customer service system maintains service continuity during the update process and achieving zero-downtime upgrades. Financial risk control and data analysis platform: For risk control systems that need to integrate multiple data sources, real-time computing engines, and risk models, the intelligent agent deployment method provided in the embodiments of this specification can ensure the correct connection of services such as data preprocessing, feature calculation, and model inference through dependency graphs. When model services are dynamically switched, the integrity of the new dependency links can be accurately verified, ensuring the reliable operation of the risk control decision-making process. Industrial IoT detection and early warning system: In industrial scenarios that require interfacing with multiple device protocols, real-time data processing, and early warning notifications, the intelligent agent deployment method provided in the embodiments of this specification can effectively manage the layered dependencies between edge computing services and cloud services. When new sensor types or analysis algorithms are added, the system can automatically identify unread dependent components, guiding on-site personnel to quickly complete the expansion deployment and significantly reducing the difficulty of on-site debugging. Medical and Health Detection and Diagnosis Platform: In scenarios integrating medical device data, image analysis services, and expert diagnostic systems, the intelligent agent deployment method provided in the embodiments of this specification ensures the secure and accurate flow of patient data between multiple processing modules through rigorous configuration verification. Any anomaly in a service instance will be immediately reflected in the coverage index, ensuring the stable operation and rapid fault recovery of the medical system. Smart City Traffic Dispatch System: Facing the complex interactions of services such as traffic flow monitoring, signal optimization, and route planning, the intelligent agent deployment method provided in the embodiments of this specification ensures the collaborative work of each subsystem through real-time coverage detection. When the computing service in a certain area becomes unavailable due to network interruption, the fault point can be immediately located and a backup service can be activated to maintain the normal operation of the overall traffic dispatch system. Of course, the intelligent agent deployment method provided in the embodiments of this specification can also be used in other intelligent agent systems that require autonomous decision-making, real-time response, resource optimization, and large-scale collaboration, which will not be exhaustively listed here.

[0071] Atomic capability services can be understood as independent service components that cannot be further subdivided, providing a single, basic, and complete technical capability. Atomic capability services encapsulate specific technical implementation details and provide basic capability support to the outside world through standard interfaces. For example, atomic capability services include, but are not limited to: speech recognition service (used to convert audio streams into text in real time), large model inference service (providing basic large model text generation and understanding capabilities), embedding service (used to convert text into high-dimensional vector representations), and reranker service (used to finely filter and rerank the initial list returned by the embedding service), etc.

[0072] Application services can be understood as services tailored to specific project scenarios or user needs. They achieve specific project logic and complex functions by combining and orchestrating multiple atomic capability services. Application services are responsible for transforming basic technical capabilities into concrete project value. For example, application services include, but are not limited to: user registration services (relying on atomic capability services such as mobile phone number verification service, verification code sending service, and password encryption service), order fulfillment services (relying on atomic capability services such as inventory deduction service, payment invocation service, and logistics order placement service), and intelligent customer service dialogue services (relying on atomic capability services such as speech recognition service, knowledge base query service, and TTS (Text-to-Speech) synthesis service).

[0073] In addition, application services can also include primary application services and secondary application services. Primary application services sit atop atomic capability services and are responsible for combining and orchestrating multiple individual atomic capability services into a complete, reusable project function. For example, primary application services include intelligent customer service dialogue services (used to handle a complete customer service dialogue round, relying on atomic capability services such as speech recognition services, large model services, and knowledge base retrieval services) and order risk control services (used to determine whether an order is at risk, relying on atomic capability services such as user profiling services, geolocation services, and anti-fraud model services). Secondary application services sit atop primary application services and are closer to the end user or specific external systems. They can be understood as gateways for user interaction or adapters for specific scenarios, generally used for adaptation and forwarding. For example, secondary application services include target mini-program customer service backend services (used as a bridge between the target mini-program and the internal intelligent customer service system, relying on the primary application service: intelligent customer service dialogue service, and can also directly rely on the atomic capability service: file processing service, which is used to process images sent by users in the mini-program) and company website online customer service plugin backend services (used to provide online chat functionality for the company website, relying on the primary application service: intelligent customer service dialogue service).

[0074] In practical applications, if a project is very complex, there may be third-level, fourth-level, and even more layers of application services. For example, a large e-commerce system might be divided into atomic capability services: user service, product service, inventory service, payment service, etc.; first-level application services: order processing service (relying on atomic capability services such as user service, product service, inventory service, and payment service) and recommendation service (relying on atomic capability services such as user service and product service); second-level application services: shopping cart service (relying on first-level application services such as order processing service and recommendation service) and checkout service (relying on first-level application services such as order processing service and atomic capability services such as payment service); and third-level application services: mobile backend service (relying on second-level application services such as shopping cart service and checkout service). For ease of understanding, the embodiments in this specification only use first-level and second-level application services as examples for explanation.

[0075] Registration information can be understood as the service access address and service configuration information submitted to the configuration center by the service instance (atomic capability service and application service) at startup. The service access address can be understood as the unique accessible endpoint of the service instance in the network. It can be in the form of an IP address (directly using a network layer numerical identifier to locate the service instance) or a domain name (using an easy-to-remember string name to locate the service, resolved to an actual IP address by the DNS (Domain Name System)). Service configuration information can be understood as the various parameters required for the service instance to run, including but not limited to basic operating parameters (such as service name, service version, operating environment, etc.), network and communication configuration parameters (such as listening address and port, timeout settings, rate limiting thresholds, etc.), dependent service connection information (such as database connection, caching service, message queue), and security-related parameters (such as authentication method, key, sensitive information encryption method, etc.).

[0076] Specifically, the registration information sent when the atomic capability service and application service are started includes: Receive the first registration information sent when the atomic capability service starts, wherein the first registration information includes the atomic capability service access address and the atomic capability service configuration information; as well as The system receives second registration information sent when the application service starts, wherein the second registration information includes the application service access address and the application service configuration information.

[0077] The first registration information can be understood as the registration information submitted by the atomic capability service to the configuration center when it starts up. This includes the atomic capability service access address and the atomic capability service configuration information. The atomic capability service access address can be understood as the uniquely accessible endpoint of the atomic capability service instance in the network, and the atomic capability service configuration information can be understood as the various parameters required for the atomic capability service instance to run.

[0078] The second registration information can be understood as the registration information submitted by the application service to the configuration center when it starts up. This includes the application service access address and the application service configuration information. The application service access address can be understood as the unique accessible endpoint of the application service instance in the network, and the application service configuration information can be understood as the various parameters required for the application service instance to run.

[0079] In practice, the configuration center acts as the executor, responsible for receiving and processing automatic registration requests from various services. When an atomic capability service starts, it proactively initiates a connection through the pre-configured configuration center address, submitting first registration information including its own network address and detailed configuration parameters. When an application service starts, it also proactively initiates a connection through the pre-configured configuration center address, submitting second registration information including its own network address and detailed configuration parameters. After receiving the first and second registration information, the configuration center performs format validation on the received information, such as verifying the validity of the IP address and port range to prevent invalid configurations. If the validation is successful, the atomic capability service and application service are added to the service registry.

[0080] The agent deployment method provided in one or more embodiments of this specification solves the technical problems of low efficiency and error-proneness of manual configuration by automating and centrally managing the first registration information of atomic capability services and the second registration information of application services. The atomic capability services and application services automatically report their precise network addresses and configuration parameters upon startup, thus avoiding various connection failures and functional abnormalities caused by manually recording IP ports and transcribing configuration items.

[0081] In addition, the first registration information is automatically sent to the configuration center by reading the central address of the configuration center pre-configured in the runtime environment when the atomic capability service starts. as well as The second registration information is automatically sent to the configuration center when the application service starts by reading the central address of the configuration center pre-configured in the runtime environment.

[0082] The central address of the configuration center, pre-configured in the runtime environment, can be understood as an environment variable that is set in advance in the container or operating system environment where the atomic capability service and application service will run before startup. The value of this environment variable is the fixed network address through which the configuration center provides services. When the atomic capability service and application service start, they read the pre-configured central address of the configuration center from the runtime environment and proactively report their registration information.

[0083] Specifically, the process from configuration center startup to service pre-configuration includes two phases. The first phase is configuration center startup and address fixing: In the entire intelligent agent system deployment, the configuration center is the first to start. As a foundational platform service, it can be started by the operations team through a deployment platform (such as Kubernetes). During startup, the deployment platform assigns a stable network address to the configuration center, visible to other services within the cluster—this is the configuration center's central address. The second phase involves pre-configuring the configuration center's central address for atomic capability services and application services: After the configuration center is running stably, the deployment phase for atomic capability services and application services begins. Operations personnel or CI (Continuous Integration) / CD (Continuous Delivery) systems pre-declare the configuration center's central address environment variable in the deployment definitions of various services (atomic capability services, application services) through a deployment platform (such as Kubernetes). When the deployment platform instantiates a service container, it injects the configuration center's central address into its runtime environment before the container starts. This pre-configuration mechanism ensures that each atomic capability service and application service automatically obtains the configuration center's central address upon startup, enabling automatic service registration.

[0084] In practice, during the service startup phase, the atomic capability service and the application service first obtain the central address of the pre-defined configuration center from their runtime environment variables, and then automatically initiate a registration request based on that central address. This process is entirely driven by the atomic capability service and the application service themselves, without external triggering or manual intervention, achieving end-to-end automation from environment awareness to service registration.

[0085] The agent deployment method provided in one or more embodiments of this specification achieves complete automation of service discovery through a combination of pre-configured environment variables and an automatic registration mechanism, eliminating the technical problems of configuration errors and low efficiency caused by manual intervention. Atomic capability services and application services can autonomously perceive the central address of the configuration center and proactively complete registration, not only avoiding connection failures caused by manually recording and entering network addresses, but also significantly improving the efficiency of agent deployment.

[0086] Step 204: Receive the service dependency information sent by the application service.

[0087] The service dependency information is used to represent at least one atomic capability service that the application service depends on.

[0088] Specifically, while receiving the first and second registration information actively reported by the atomic capability services and application services at startup, the configuration center also receives the service dependency information sent by the application services, and returns the registration information of the atomic capability services that the application services depend on to the application services based on the service dependency information.

[0089] Service dependency information can be understood as the list of downstream services that an application service declares to the configuration center when it registers, which are necessary for its normal operation.

[0090] Continuing with the previous example, if the application service includes a first-level application service and a second-level application service, when the configuration center receives service dependency information from the first-level application service, this service dependency information indicates at least one atomic capability service that the first-level application service depends on. That is, the service dependency information clarifies at least one atomic capability service that the first-level application service needs to call to complete its own project capability. When the configuration center receives service dependency information from the second-level application service, this service dependency information indicates at least one first-level application service, or at least one first-level application service and at least one atomic capability service that the second-level application service depends on. That is, the service dependency information clarifies at least one first-level application service, or at least one first-level application service and at least one atomic capability service that the second-level application service needs to call to complete its own project capability.

[0091] In practice, upon startup, the application service first submits a service dependency declaration (service dependency information) to the configuration center. For example, based on its pre-defined project logic requirements, the application service organizes the identifiers of its dependent atomic capability services, or the identifiers of its dependent downstream application services and atomic capability services, into structured data and sends it to the configuration center via the dependency declaration interface. The configuration center receives the service dependency declaration and returns the service access addresses and service configuration information of all services the application service depends on. The application service verifies the service access addresses and service configuration information of all its dependent services. After confirming that all dependent services are available, the application service completes its own initialization and health self-check. Once it has started without errors and the dependency verification is successful, the application service reports its own service access address and service configuration information to the configuration center.

[0092] Step 206: Construct a service dependency graph based on the service dependency information, and determine the configuration dependency coverage based on the service dependency graph, the service access address, and the service configuration information.

[0093] Among them, the service dependency graph can be understood as a service topology graph, a graphical data structure that uses nodes to represent atomic capability services and application services, and directed edges to represent the dependencies between services. It can intuitively display the connection topology and dependency hierarchy of each service in the deployment of an intelligent agent.

[0094] Configuration dependency coverage can be understood as an indicator that quantifies the completeness of agent deployment, reflecting the overall readiness status of agent deployment.

[0095] Continuing with the previous example, when the application service includes first-level application services and second-level application services, the specific implementation of service dependency information and service dependency relationship graph is as follows: The application services include primary application services and secondary application services; The receipt of service dependency information sent by the application service includes: Receive first-level service dependency information sent by the first-level application service, wherein the first-level service dependency information is used to represent at least one atomic capability service that the first-level application service depends on; Receive secondary service dependency information sent by the secondary application service, wherein the secondary service dependency information is used to indicate at least one primary application service that the secondary application service depends on, or at least one primary application service and at least one atomic capability service that it depends on. The step of constructing a service dependency graph based on the service dependency information includes: Construct a service dependency graph based on the first-level application service, at least one atomic capability service that the first-level application service depends on, the second-level application service, at least one first-level application service that the second-level application service depends on, or at least one first-level application service and at least one atomic capability service that the second-level application service depends on.

[0096] Specifically, the configuration center first receives first-level service dependency information from first-level application services. This information explicitly specifies one or more atomic capability services that need to be invoked. Then, it receives second-level service dependency information from second-level application services. This information explicitly states that it includes dependencies on one or more first-level application services, and may also include direct dependencies on one or more atomic capability services. Based on this hierarchical dependency data, the configuration center can construct a service dependency graph that presents multi-level call relationships. This graph clearly shows the complete dependency chain from second-level application services to first-level application services and then to atomic capability services, forming a panoramic view of the system service topology.

[0097] The agent deployment method provided in one or more embodiments of this specification achieves accurate modeling and visualization of complex dependency relationships by collecting and processing service dependency information in a layered manner. The dependencies of first-level application services on atomic capability services, and the mixed dependencies of second-level application services on first-level services and atomic capability services, are fully mapped to the service dependency graph, forming a clear hierarchical topology. This service dependency graph provides accurate fault location capabilities for agent deployment. When an anomaly occurs in a service at a certain level, its impact scope can be quickly identified based on this service dependency graph, significantly improving troubleshooting efficiency.

[0098] Furthermore, when the service access address includes both atomic capability service access addresses and application service access addresses, and the service configuration information includes both atomic capability service configuration information and application service configuration information, the configuration dependency coverage of the entire intelligent agent deployment system can be calculated based on the atomic capability service access addresses, application service access addresses, atomic capability service configuration information, and application service configuration information, combined with the service dependency graph. The specific implementation method is as follows: The step of determining configuration dependency coverage based on the service dependency graph, the service access address, and the service configuration information includes: Based on the service dependency graph, the atomic capability service access address, the application service access address, the atomic capability service configuration information, and the application service configuration information, the configuration dependency coverage is determined.

[0099] In practice, the configuration center verifies the validity of each dependency connection in the service dependency graph based on the established service dependency graph, combined with the service access addresses and service configuration information provided during the registration of atomic capability services and application services. By statistically analyzing the ratio of the number of verified dependency connections to the total number of connections in the service dependency graph, the precise configuration dependency coverage is calculated, thereby quantitatively reflecting the configuration completeness status of the entire intelligent agent deployment system.

[0100] The agent deployment method provided in one or more embodiments of this specification, based on a full-link check of the service dependency graph, ensures that no dependent connections are missed. Furthermore, the joint verification of service access addresses (atomic capability service access addresses and application service access addresses) and service configuration information (atomic capability service configuration information and application service configuration information) fundamentally guarantees the actual availability of dependent connections. This configuration dependency coverage calculation mechanism can promptly detect configuration deficiencies and other issues, providing reliable quality assurance for agent deployment and significantly reducing the risk of operational failures due to incomplete configuration.

[0101] Specifically, the configuration dependency coverage is calculated based on the service registration status of each node in the service dependency graph. The specific implementation is as follows: The step of determining configuration dependency coverage based on the service dependency graph, the atomic capability service access address, the application service access address, the atomic capability service configuration information, and the application service configuration information includes: Based on the atomic capability service access address and the atomic capability service configuration information, perform atomic capability service verification on the atomic capability service, obtain the atomic capability service verification result, and determine the registration status of the atomic capability service based on the atomic capability service verification result. Based on the application service access address and the application service configuration information, the application service is verified to obtain the application service verification result, and the registration status of the application service is determined based on the application service verification result. The configuration dependency coverage is determined based on the service dependency graph, the registration status of the atomic capability service, and the registration status of the application service.

[0102] The atomic capability service verification can be understood as the configuration center checking the atomic capability service access address and configuration information reported by the atomic capability service at startup to confirm their legality and validity. For example, the configuration center performs automated format verification on the IP address, port, and other parameters reported by the atomic capability service at startup, including basic rule checks such as the legality of the IP address format and the validity of the port range.

[0103] The result of the atomic capability service verification can be understood as either successful or unsuccessful verification.

[0104] Application service verification can be understood as the configuration center checking the application service access address and configuration information reported by the application service at startup to confirm their legality and validity. For example, the configuration center performs automated format verification on parameters such as IP address and port reported by the application service at startup, including basic rule checks such as the legality of the IP address format and the validity of the port range.

[0105] The application service verification result can be understood as either successful or unsuccessful application service verification.

[0106] The registration status of an atomic capability service can be understood as whether the atomic capability service has successfully passed the verification and has been accepted as an available service by the configuration center; similarly, the registration status of an application service can be understood as whether the application service has successfully passed the verification and has been accepted as an available service by the configuration center.

[0107] Configuration dependency coverage can be understood as the ratio of the number of established dependency connections to the total number of dependency connections, calculated based on the service dependency graph and the registration status of each service, to reflect the completeness of the agent deployment.

[0108] In practice, the configuration center first performs atomic capability service verification based on the atomic capability service access address and configuration information. Based on the completeness and compliance of the atomic capability service access address and configuration information, the verification result is obtained, and the registration status of the atomic capability service is determined accordingly. Subsequently, the configuration center performs application service verification based on the application service access address and configuration information. Based on the completeness and compliance of the application service access address and configuration information, the verification result is obtained, and the registration status of the application service is determined accordingly. After obtaining the accurate registration status of all services, the configuration center conducts a comprehensive analysis in conjunction with the service dependency graph. By statistically analyzing the ratio of established valid dependency connections to total dependency connections, the accurate configuration dependency coverage is calculated.

[0109] The agent deployment method provided in one or more embodiments of this specification verifies atomic capability services and application services, ensuring the network reachability and configuration correctness of each service, preventing invalid configurations, and providing a fundamental guarantee for the validity of dependencies. Based on a comprehensive analysis of the service dependency graph and the registration status of each service, the completeness of the agent deployment is accurately obtained. This allows for the timely detection of dependency breaks caused by service unavailability or configuration errors, significantly improving the quality of agent deployment.

[0110] Specifically, determining the configuration dependency coverage based on the service dependency graph, the registration status of the atomic capability service, and the registration status of the application service includes: Traverse the dependency edges in the service dependency graph, wherein the dependency edges are used to represent the dependency relationship between the service provider and the service consumer on which the service provider depends. The service provider is any one of the application services, and the service consumer is at least one atomic capability service among the atomic capability services, at least one application service among the application services, or at least one application service among the application services and at least one atomic capability service among the atomic capability services. Based on the registration status of the atomic capability service and the registration status of the application service, determine the registration status of the service provider and the registration status of the service consumer on which the service provider depends; The establishment status of the dependency edge is determined based on the registration status of the service provider and the registration status of the service consumer on which the service provider depends. Calculate the configuration dependency coverage based on the establishment status of the dependency edges.

[0111] In this context, a dependency edge can be understood as a directed edge connecting multiple service nodes in a service dependency graph. It represents the dependency relationship between the service provider and the service consumer, and the direction can be from the service consumer to the service provider.

[0112] A service consumer can be understood as the initiator in a dependency relationship edge. It is typically an application service that needs to call one or more atomic capability services, or other downstream application services and one or more atomic capability services, to complete its own functions. In other words, a service consumer can be understood as an application service that depends on other services. It obtains the registration information of the service providers it depends on from the configuration center for subsequent calls, and therefore needs to read the registration information reported by the services it depends on from the configuration center.

[0113] A service provider can be understood as the dependent party in a dependency relationship edge. It can be an atomic capability service, another application service, or a combination of another application service and an atomic capability service. In other words, a service provider can be understood as the service that actually provides the project's capabilities and reports its registration information to the configuration center.

[0114] For example, the atomic capability services are the speech recognition service and the large model service; the first-level application service is the intelligent customer service service; and the second-level application service is the target mini-program backend service. When the speech recognition service and the large model service start, they write their registration information to the configuration center. Similarly, when the intelligent customer service service starts, it also writes its registration information to the configuration center and declares its dependency on the speech recognition service and the large model service. The target mini-program backend service also writes its registration information to the configuration center and declares its dependency on the intelligent customer service service, or its dependency on both the intelligent customer service service and the large model service. Therefore, in dependency edge 1 (where the intelligent customer service service calls the speech recognition service and the large model service), the service consumer is the intelligent customer service service, and the service provider is the speech recognition service and the large model service. In dependency edge 2 (where the target mini-program backend service calls the intelligent customer service service), the service consumer is the target mini-program backend service, and the service provider is the intelligent customer service service.

[0115] The establishment status of a dependency edge can be understood as whether a single dependency edge has been effectively established. The establishment status of each dependency edge depends on the registration status of the service provider and service consumer in that dependency edge.

[0116] In practice, the configuration center first traverses all dependency edges in the service dependency graph, verifying the registration status of the service provider and service consumer associated with each dependency edge. Based on the registration status of the atomic capability services and application services obtained earlier, the configuration center determines the registration status of the service provider and service consumer in each dependency edge, and then determines the establishment status of the dependency edge, i.e., whether the dependency edge has been successfully established. After determining the establishment status of all dependency edges, the number of successfully established dependency edges is counted, and the ratio of this number to the total number of dependency edges is calculated to obtain the accurate configuration dependency coverage, providing a quantitative evaluation basis for the deployment quality of the intelligent agent.

[0117] The agent deployment method provided in one or more embodiments of this specification achieves accurate calculation of configuration dependency coverage by traversing the dependency graph and combining it with the service registration status. Firstly, fine-grained state verification based on dependency edges accurately identifies the actual establishment status of each dependency connection, avoiding overall misjudgment due to anomalies in a single service. The coverage calculation method through graph traversal clearly demonstrates the completeness and reliability of the agent deployment. Subsequently, when the configuration dependency coverage does not meet expectations, it can accurately locate the specific missing dependencies, guiding operations personnel to quickly locate and repair problematic services, significantly improving troubleshooting efficiency and agent deployment success rate, ensuring the agent system quickly reaches a fully ready state.

[0118] In practical applications, registration status includes registered and unregistered states. Depending on the registration status of the atomic capability service and the application service, the registration status of the service provider and service consumer in each dependency edge will also differ. The specific implementation is as follows: The registration status includes registered status and unregistered status; Determining the registration status of the service provider and the service consumer on which the service provider depends, based on the registration status of the atomic capability service and the registration status of the application service, includes: Based on the registration status of the atomic capability service and the registration status of the application service, determine the registered or unregistered status of the service provider and the registered or unregistered status of at least one service consumer on which the service provider depends; Determining the establishment status of the dependency edge based on the registration status of the service provider and the registration status of the service consumer on which the service provider depends includes: If it is determined that the registration status of the service provider and the registration status of the service consumer on which the service provider depends are both registered, then the establishment status of the dependency edge is determined to be established. or If the registration status of the service provider and the service consumer on which the service provider depends are both registered, or if either is unregistered, then the establishment status of the dependency edge is determined to be unestablished.

[0119] Using the previous example, the atomic capability service is the speech recognition service; the first-level application service is the intelligent customer service service, which depends on the speech recognition service; and the second-level application service is the target mini-program backend service, which depends on the intelligent customer service service.

[0120] If the voice recognition service, intelligent customer service, and target mini-program backend service are all successfully registered.

[0121] Therefore, the dependency edge is defined as follows: the intelligent customer service depends on the speech recognition service, the service provider (speech recognition service) is registered, and the service consumer (intelligent customer service service) is registered. Thus, the establishment status of this dependency edge is "established".

[0122] If the voice recognition service registration is unsuccessful.

[0123] In the dependency relationship edge: the intelligent customer service depends on the speech recognition service, the service provider: the speech recognition service is registered but not registered, and the service consumer: the intelligent customer service service is registered but not registered. Therefore, the establishment status of this dependency relationship edge is not established.

[0124] In practice, the configuration center can determine the registration status of the service provider and service consumer in each dependency edge based on the registration information of the registered atomic capability services and the registration information of the registered application services. The status is either registered or unregistered. Only when both the service provider and service consumer in a dependency edge are registered can the dependency edge be considered established. If either the service provider or service consumer in a dependency edge is unregistered, the dependency edge is considered unestablished.

[0125] The agent deployment method provided in one or more embodiments of this specification is based on a strict determination mechanism of the registration status of service providers and service consumers of dependency edges (the corresponding dependency edges are only considered established when both the service provider and the service consumer have successfully registered). This effectively avoids false readiness caused by unilateral service anomalies and ensures that the configuration dependency coverage can truly reflect the availability of the agent system.

[0126] Once the establishment status of all dependency edges in the service dependency graph is determined, the configuration dependency coverage can be accurately calculated based on the establishment status of those edges. The specific implementation method is as follows: The establishment status includes an established status and an unestablished status; The step of calculating the configuration dependency coverage based on the establishment status of the dependency edges includes: Based on the establishment status of the dependency edges, determine the number of dependency edges in the established state and the number of dependency edges in the unestablished state. The configuration dependency coverage is calculated based on the number of dependency edges in the established state, the number of dependency edges in the unestablished state, and the total number of dependency edges in the service dependency graph.

[0127] The established state indicates that the dependency edge has been successfully established; the unestablished state indicates that the dependency edge has not yet been successfully established.

[0128] The total number of dependency edges can be understood as the sum of all dependency edges in the service dependency graph.

[0129] In practice, the configuration center first categorizes and counts the states of all dependency edges in the service dependency graph, summarizing the number of dependency edges in both the established and non-established states. Based on this statistical result, the configuration center calculates the ratio between the number of established dependency edges and the total number of dependency edges in the service dependency graph to obtain an accurate configuration dependency coverage value. For example, if the number of established dependency edges is 2 and the total number of dependency edges in the service dependency graph is also 2, then the configuration dependency coverage is 100%; if the number of established dependency edges is 1 and the total number of dependency edges in the service dependency graph is also 2, then the configuration dependency coverage is 50%.

[0130] The agent deployment method provided in one or more embodiments of this specification, based on the classification and statistics of the establishment status of dependency edges, can clearly present the distribution of established and unestablished dependency connections, providing an intuitive quantitative indicator for the agent deployment progress. By configuring dependency coverage, not only is the overall integrity of the agent deployment objectively reflected, but the dynamic progress of the agent deployment process can also be displayed through numerical trends, significantly improving the real-time observation experience of agent deployment.

[0131] Step 208: If the configuration dependency coverage meets the preset coverage threshold, the target intelligent agent is determined to be deployed. The target intelligent agent is constructed collaboratively based on the atomic capability service and the application service.

[0132] The preset coverage threshold can be understood as a pre-defined standard value for the completion of agent deployment. For example, the preset coverage threshold can be set to 100%, meaning that the agent deployment can only be considered complete when all service dependencies are correctly established. Of course, this preset coverage threshold can also be adjusted according to actual needs, and can be set to 99% or 98%, etc.

[0133] A target intelligent agent can be understood as a complete intelligent system composed of multiple atomic capability services and application services at different levels, which are collaboratively combined through dependencies. For example, a target intelligent agent could be an intelligent customer service system, which is constructed collaboratively by multiple services such as atomic capability services (speech recognition service) and application services (dialogue management service).

[0134] Once deployment is complete, it can be understood as the target intelligent agent reaching a runnable state, meaning that all services have been registered, all inter-service dependencies have been established, and the target intelligent agent has the ability to process project requests normally.

[0135] Specifically, the configuration center continuously monitors the real-time status of the agent deployment. When it detects that the current configuration dependency coverage has reached a preset coverage threshold (e.g., 100%), the configuration center can mark the target agent status as "deployment complete" and generate a deployment completion notification containing a service topology diagram, health status summary, and configuration integrity report, which is then sent to relevant system and management personnel through the operation and maintenance channel. At the same time, the runtime detection mode is activated to continuously ensure the stable operation of the agent system.

[0136] To further enhance the deployment experience of intelligent agents, the configuration dependency coverage can be displayed to operations and maintenance personnel in a visual manner. The specific implementation method is as follows: After determining the configuration dependency coverage, the process also includes: If the configuration dependency coverage is determined to meet the preset coverage threshold, the configuration dependency coverage will be displayed through a visual interface.

[0137] Specifically, after confirming that the configuration dependency coverage has reached the preset coverage threshold, the configuration center can visualize it through a visual interface. For example, the configuration dependency coverage is first displayed in the dashboard of the operations and maintenance management platform, dynamically presented as a circular progress bar, with green indicating the achievement status. Simultaneously, in the topology view interface, all established dependency edges are highlighted, and a "deployment complete" status indicator is displayed in the overview panel of the intelligent agent deployment. Reports containing details of dependency establishment at each service level can also be automatically generated, visually displaying the establishment status of each dependency edge through color coding (green / red). When operations personnel click on specific values, the visualization interface can display detailed registration status and verification results of atomic capability services and application services.

[0138] The agent deployment method provided in one or more embodiments of this specification displays configuration dependency coverage in real time through a visual interface, providing the operations and maintenance team with an intuitive understanding of the deployment status. The visual and graphical display clarifies the complex dependencies of the agent system, significantly lowering the information comprehension threshold. Operations and maintenance personnel can quickly grasp the overall readiness status of the agent system without in-depth analysis of underlying data, significantly improving operational efficiency.

[0139] In addition, after determining the configuration dependency coverage, the following steps are also included: If it is determined that the configuration dependency coverage does not meet the preset coverage threshold, the configuration dependency coverage and the dependency edges whose establishment status is not established are displayed through a visual interface.

[0140] Specifically, when the configuration dependency coverage does not reach the preset coverage threshold, the configuration center can display the configuration dependency coverage and the dependency edges whose establishment status is not established to the operations and maintenance personnel through a visual interface. For example, the configuration center can immediately trigger an alert in the alarm area of ​​the visual interface, displaying the difference between the current configuration dependency coverage and the preset coverage threshold with a red progress bar and a clear indicator. It can also mark the edges of unestablished dependencies in the service topology diagram as flashing red or highlighted, and automatically generate a list of unestablished dependencies, detailing the missing services and their relationships. Simultaneously, this visual interface can also provide a one-click diagnostic function to quickly locate the cause of a specific service's registration failure and provide repair suggestions. For example, if registration information verification fails due to an invalid IP address format, the repair suggestion can be "Please check the network configuration of this service and correct its IP address to a valid IP address"; or if a health check is abnormal due to a service process not responding, the repair suggestion can be "Log in to the host where the service is located and use a certain command to check if the service process is running," etc.

[0141] The agent deployment method provided in one or more embodiments of this specification, when the configuration dependency coverage does not meet the preset coverage threshold, visually displays the configuration dependency coverage and dependency edges in the non-established state through a visual interface. This enables the operation and maintenance team to quickly identify deployment anomalies, narrowing the scope of deployment anomaly investigation from the system level to specific service links. This visual early warning mechanism significantly shortens the fault location time, enabling operation and maintenance personnel to specifically repair problematic services, significantly improving the fault recovery efficiency of the agent deployment process, and effectively ensuring the deployment progress and quality of the agent system.

[0142] In addition, the configuration center will receive dynamic parameter updates from each service in real time to ensure the real-time availability of the intelligent agent system. The specific implementation method is as follows: After the deployment of the target intelligent agent is completed, the process also includes: The system receives update registration information sent by the atomic capability service and / or the application service when dynamic parameters change during operation. The update registration information includes the update service access address and / or update service configuration information. If the atomic capability service and / or the application service are determined to be service providers based on the dependency edges in the service dependency graph, the update service access address and / or update service configuration information are sent to at least one service consumer that the service provider depends on.

[0143] Updating registration information can be understood as a parameter change data packet sent to the configuration center by atomic capability services and / or application services during operation due to changes in dynamic parameters (such as IP address, port, configuration parameters, etc.). This data packet contains the updated service access address and / or service configuration information.

[0144] Dynamic parameter changes can be understood as real-time changes in network location or operating parameters of atomic capability services and / or application services during operation due to reasons such as elastic scaling, fault migration, or hot configuration updates.

[0145] Specifically, when an atomic capability service or application service undergoes parameter changes during operation, it proactively sends updated registration information, including the new service access address and / or new service configuration information, to the configuration center. Upon receiving the updated registration information, the configuration center immediately identifies whether the service is a service provider or a service consumer in the service dependency graph. If the service is determined to be a service provider, it traces back to identify all service consumers that depend on it. Subsequently, the configuration center pushes the updated service access address and service configuration information to these service consumers in real time, ensuring that the dependency chain can adapt to the dynamic changes of the underlying services in a timely manner and maintain the overall connectivity of the intelligent agent system.

[0146] The agent deployment method provided in one or more embodiments of this specification effectively ensures the stability and continuity of the agent system during operation by establishing an automatic synchronization mechanism for parameter changes. When services (atomic capability services and / or application services) change due to expansion, migration, or configuration adjustments, the configuration center can automatically synchronize the updated connection information to all relevant services, ensuring that the communication links between services remain normal. This automated update mechanism avoids connection interruptions caused by changes in service access addresses or configuration parameters, significantly reducing the need for manual intervention and maintenance.

[0147] The intelligent agent deployment method provided in one or more embodiments of this specification firstly integrates the service startup and configuration registration processes through a lightweight service governance model of "registration upon startup," forming a bidirectional configuration synchronization mechanism that achieves a near-"zero-configuration" deployment experience without manual intervention. Secondly, a configuration integrity verification mechanism based on dependency topology introduces the concept of "configuration dependency coverage," transforming service dependencies into quantifiable health indicators and upgrading configuration validity verification from "whether it is started" to "whether it is callable." Finally, a deployment feedback system oriented towards operation and maintenance transforms complex dependency configuration issues into intuitive health status prompts, significantly reducing the operation and maintenance threshold and enabling the deployment process to be detectable, diagnosable, and recoverable. These features collectively construct an efficient and reliable intelligent agent deployment solution.

[0148] See Figure 3 , Figure 3 This is a schematic diagram illustrating an application of an agent deployment method provided in one embodiment of this specification.

[0149] Step 302: Start the configuration center.

[0150] Specifically, the configuration center startup can be understood as the configuration center starting first. After startup, it immediately provides its own IP address or domain name to the outside world (service providers and service consumers), becoming the "anchor point" for the subsequent startup process of the entire intelligent agent system.

[0151] Step 304: Start the atomic capability service.

[0152] Specifically, the startup of an atomic capability service can be understood as the startup of an atomic capability service (including but not limited to model-based services, embedding services, reranker services, voice services, etc.). This involves reading the central address of the pre-configured configuration center in the runtime environment and reporting its own atomic capability service access address (IP address or domain name) and configuration information to the configuration center. Simultaneously, the configuration center updates the service providers based on the registered atomic capability services (treating registered atomic capability services as available service providers).

[0153] Step 306: Start the primary application service.

[0154] Specifically, the startup of a Level 1 application service can be understood as follows: The Level 1 application service reads the central address of the pre-configured configuration center in the runtime environment, retrieves and verifies the atomic service access addresses and configuration information of all its dependent atomic capability services from the configuration center. After confirming that all its dependent atomic capability services are available, the Level 1 application service completes its own initialization and health self-check. Once it has started without errors and its dependencies have been verified, the Level 1 application service reports its own Level 1 application service access address (IP address or domain name) and configuration information to the configuration center.

[0155] In addition, the configuration center updates the service providers based on the registered first-level application services (the first-level application services that are about to be registered are regarded as available service providers).

[0156] Step 308: Start the secondary application service.

[0157] Specifically, the startup of a secondary application service can be understood as follows: The secondary application service reads the central address of the pre-configured configuration center in the runtime environment, obtains and verifies the access addresses and configuration information of all primary application services it depends on, as well as the atomic service access addresses and configuration information of all atomic capability services. After confirming that all its dependent primary application services and atomic capability services are available, the secondary application service completes its own initialization and health self-check. Once it has started successfully and its dependencies have been verified, the secondary application service reports its own secondary application service access address (IP address or domain name) and configuration information to the configuration center.

[0158] Furthermore, the configuration center updates service providers based on the registered secondary application services (the registered secondary application services are considered available service providers). In practice, the configuration center continuously updates service providers; whenever any service starts and registers with it, an update operation is performed to refresh its service registry. The configuration center then compares this updated service registry with the service dependency graph. If it finds that any dependent service in any dependency edge of the service dependency graph is not yet registered, it returns an "uncovered" state and continues to wait. If it finds that all dependent services in all dependency edges of the service dependency graph are registered, it returns a "covered" state and performs a health check. Once the health check reaches 100%, the agent deployment is considered successful, the agent system is fully ready, and it can officially provide stable services.

[0159] The intelligent agent deployment method provided in one or more embodiments of this specification ensures that all configuration transmission and storage are completed within the customer's intranet, effectively eliminating the risk of cross-network data leakage. A dynamic parameter generation and reporting mechanism enables each service to automatically generate and report key parameters upon startup, with the configuration center receiving updates in real time, avoiding configuration gaps due to unknown parameters. The configuration center's automatic verification and dependency management functions validate the format of service-reported parameters and dynamically construct a topology graph based on service dependencies, checking the integrity of the dependency chain in real time. A health inspection and visualization detection system continuously tracks the service registration status, outputting real-time configuration completion. When all dependencies are satisfied, it is automatically marked as 100% healthy; otherwise, incomplete items are clearly displayed, significantly improving the efficiency of locating operational problems.

[0160] Corresponding to the above method embodiments, this specification also provides embodiments of an intelligent agent deployment device. Figure 4 This is a schematic diagram of the structure of an intelligent agent deployment device provided in one embodiment of this specification. Figure 4 As shown, this device is used in a configuration center and includes: The registration information receiving module 402 is configured to receive registration information sent when the atomic capability service and application service start up, wherein the registration information includes service access address and service configuration information; The dependency information receiving module 404 is configured to receive service dependency information sent by the application service, wherein the service dependency information is used to represent at least one atomic capability service that the application service depends on. The dependency coverage determination module 406 is configured to construct a service dependency graph based on the service dependency information, and determine the configuration dependency coverage based on the service dependency graph, the service access address, and the service configuration information. The agent deployment module 408 is configured to determine that the target agent deployment is complete when the configuration dependency coverage meets a preset coverage threshold, wherein the target agent is collaboratively constructed based on the atomic capability service and the application service.

[0161] Optionally, the registration information receiving module 402 is further configured to: Receive the first registration information sent when the atomic capability service starts, wherein the first registration information includes the atomic capability service access address and the atomic capability service configuration information; as well as The system receives second registration information sent when the application service starts, wherein the second registration information includes the application service access address and the application service configuration information.

[0162] Optionally, the dependency coverage determination module 406 is further configured to: Based on the service dependency graph, the atomic capability service access address, the application service access address, the atomic capability service configuration information, and the application service configuration information, the configuration dependency coverage is determined.

[0163] Optionally, the dependency coverage determination module 406 is further configured to: Based on the atomic capability service access address and the atomic capability service configuration information, perform atomic capability service verification on the atomic capability service, obtain the atomic capability service verification result, and determine the registration status of the atomic capability service based on the atomic capability service verification result. Based on the application service access address and the application service configuration information, the application service is verified to obtain the application service verification result, and the registration status of the application service is determined based on the application service verification result. The configuration dependency coverage is determined based on the service dependency graph, the registration status of the atomic capability service, and the registration status of the application service.

[0164] Optionally, the dependency coverage determination module 406 is further configured to: Traverse the dependency edges in the service dependency graph, wherein the dependency edges are used to represent the dependency relationship between the service provider and the service consumer on which the service provider depends. The service provider is any one of the application services, and the service consumer is at least one atomic capability service among the atomic capability services, at least one application service among the application services, or at least one application service among the application services and at least one atomic capability service among the atomic capability services. Based on the registration status of the atomic capability service and the registration status of the application service, determine the registration status of the service provider and the registration status of the service consumer on which the service provider depends; The establishment status of the dependency edge is determined based on the registration status of the service provider and the registration status of the service consumer on which the service provider depends. Calculate the configuration dependency coverage based on the establishment status of the dependency edges.

[0165] Optionally, the establishment state includes an established state and an unestablished state; The dependency coverage determination module 406 is further configured as follows: Based on the establishment status of the dependency edges, determine the number of dependency edges in the established state and the number of dependency edges in the unestablished state. The configuration dependency coverage is calculated based on the number of dependency edges in the established state, the number of dependency edges in the unestablished state, and the total number of dependency edges in the service dependency graph.

[0166] Optionally, the registration status includes a registered status and an unregistered status; The dependency coverage determination module 406 is further configured as follows: Based on the registration status of the atomic capability service and the registration status of the application service, determine the registered or unregistered status of the service provider and the registered or unregistered status of at least one service consumer on which the service provider depends; The dependency coverage determination module 406 is further configured as follows: If it is determined that the registration status of the service provider and the registration status of the service consumer on which the service provider depends are both registered, then the establishment status of the dependency edge is determined to be established. or If the registration status of the service provider and the service consumer on which the service provider depends are both registered, or if either is unregistered, then the establishment status of the dependency edge is determined to be unestablished.

[0167] Optionally, the device further includes: The first visualization module is configured as follows: If it is determined that the configuration dependency coverage does not meet the preset coverage threshold, the configuration dependency coverage and the dependency edges whose establishment status is not established are displayed through a visual interface.

[0168] Optionally, the device further includes: The second visualization module is configured as follows: If the configuration dependency coverage is determined to meet the preset coverage threshold, the configuration dependency coverage will be displayed through a visual interface.

[0169] Optionally, the first registration information is automatically sent to the configuration center by reading the central address of the configuration center pre-configured in the runtime environment when the atomic capability service starts. as well as The second registration information is automatically sent to the configuration center when the application service starts by reading the central address of the configuration center pre-configured in the runtime environment.

[0170] Optionally, the application service includes primary application services and secondary application services; The dependency information receiving module 404 is further configured to: Receive first-level service dependency information sent by the first-level application service, wherein the first-level service dependency information is used to represent at least one atomic capability service that the first-level application service depends on; Receive secondary service dependency information sent by the secondary application service, wherein the secondary service dependency information is used to indicate at least one primary application service that the secondary application service depends on, or at least one primary application service and at least one atomic capability service that it depends on. The dependency coverage determination module 406 is further configured as follows: Construct a service dependency graph based on the first-level application service, at least one atomic capability service that the first-level application service depends on, the second-level application service, at least one first-level application service that the second-level application service depends on, or at least one first-level application service and at least one atomic capability service that the second-level application service depends on.

[0171] Optionally, the device further includes: The parameter update module is configured as follows: The system receives update registration information sent by the atomic capability service and / or the application service when dynamic parameters change during operation. The update registration information includes the update service access address and / or update service configuration information. If the atomic capability service and / or the application service are determined to be service providers based on the dependency edges in the service dependency graph, the update service access address and / or update service configuration information are sent to at least one service consumer that the service provider depends on.

[0172] It is understood that the modules mentioned above refer to computer programs or program segments used to perform one or more specific functions. Furthermore, the distinction between these modules does not imply that the actual program code must also be separate.

[0173] For ease of description, the above devices are described by dividing them into various modules or units based on their functions. Of course, when implementing one or more of these specifications, the functions of each module or unit can be implemented in the same or different software and / or hardware, or a module that performs the same function can be implemented by a combination of multiple sub-modules or sub-units, etc. The device embodiments described above are merely illustrative. For example, the division of units is only a logical functional division; in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed.

[0174] The above is a schematic scheme of an agent deployment device according to this embodiment. It should be noted that the technical solution of this agent deployment device and the technical solution of the agent deployment method described above belong to the same concept. For details not described in detail in the technical solution of the agent deployment device, please refer to the description of the technical solution of the agent deployment method described above.

[0175] See Figure 5 , Figure 5 This is a structural block diagram of a computing device according to one embodiment of this specification. The components of the computing device 500 include, but are not limited to, a memory 510 and a processor 520. The processor 520 is connected to the memory 510 via a bus 530, and a database 550 is used to store data.

[0176] The computing device 500 also includes an access device 540, which enables the computing device 500 to communicate via one or more networks 560. Examples of these networks include Public Switched Telephone Network (PSTN), Local Area Network (LAN), Wide Area Network (WAN), Personal Area Network (PAN), or combinations of communication networks such as the Internet. The access device 540 may include one or more of any type of wired or wireless network interface (e.g., a network interface card (NIC)), such as an IEEE 802.11 Wireless Local Area Network (WLAN) wireless interface, a Wi-MAX (Worldwide Interoperability for Microwave Access) interface, an Ethernet interface, a Universal Serial Bus (USB) interface, a cellular network interface, a Bluetooth interface, a Near Field Communication (NFC) interface, and so on.

[0177] In one embodiment of this application, the aforementioned components of the computing device 500 and Figure 5 Other components, not shown, can also be connected to each other, for example, via a bus. It should be understood that... Figure 5 The block diagram of the computing device shown is for illustrative purposes only and is not intended to limit the scope of this application. Those skilled in the art can add or replace other components as needed.

[0178] The computing device 500 can be any type of stationary or mobile computing device, including mobile computers or mobile computing devices (e.g., tablet computers, personal digital assistants, laptop computers, notebook computers, netbooks, etc.), mobile phones (e.g., smartphones), wearable computing devices (e.g., smartwatches, smart glasses, etc.) or other types of mobile devices, or stationary computing devices such as desktop computers or personal computers (PCs). The computing device 500 can also be a mobile or stationary server.

[0179] The processor 520 is used to execute the following computer program / instructions, which, when executed by the processor, implement the steps of the above-described agent deployment method.

[0180] The above is an illustrative scheme of a computing device according to this embodiment. It should be noted that the technical solution of this computing device and the technical solution of the above-described agent deployment method belong to the same concept. For details not described in detail in the technical solution of the computing device, please refer to the description of the technical solution of the above-described agent deployment method.

[0181] An embodiment of this specification also provides a computer-readable storage medium storing a computer program / instructions that, when executed by a processor, implement the steps of the above-described intelligent agent deployment method.

[0182] The various embodiments in this specification are described in a progressive manner. Similar or identical parts between embodiments can be referred to interchangeably. Each embodiment focuses on its differences from other embodiments. In particular, the computer-readable storage medium embodiments are described simply because they are substantially similar to the agent deployment method embodiments; relevant details can be found in the descriptions of the agent deployment method embodiments.

[0183] An embodiment of this specification also provides a computer program product, including a computer program / instructions that, when executed by a processor, implement the steps of the above-described intelligent agent deployment method.

[0184] The above is an illustrative scheme of a computer program product according to this embodiment. It should be noted that the technical solution of this computer program product and the technical solution of the above-described intelligent agent deployment method belong to the same concept. For details not described in detail in the technical solution of the computer program product, please refer to the description of the technical solution of the above-described intelligent agent deployment method.

[0185] The various embodiments in this specification are described in a progressive manner, and the same or similar parts between the embodiments can be referred to mutually. Each embodiment focuses on describing the differences from other embodiments. In particular, for the embodiments of [apparatus, device, system], since they are basically similar to the method embodiments, the description is relatively simple, and the relevant parts can be referred to the description of the method embodiments. The [apparatus, device, system] provided in the embodiments of this specification correspond to the methods, and therefore the [apparatus, device, system] also has similar beneficial technical effects as the corresponding methods. Since the beneficial technical effects of the methods have been described in detail above, the beneficial technical effects of the corresponding [apparatus, device, system] will not be repeated here.

[0186] The foregoing has described specific embodiments of this specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims may be performed in a different order than that shown in the embodiments and may still achieve the desired result. Furthermore, the processes depicted in the drawings do not necessarily require a specific or sequential order to achieve the desired result. In some embodiments, multitasking and parallel processing are possible or may be advantageous.

[0187] In the 1990s, improvements to a technology could be clearly distinguished as either hardware improvements (e.g., improvements to the circuit structure of diodes, transistors, switches, etc.) or software improvements (improvements to methodology). However, with technological advancements, many methodological improvements today can be considered direct improvements to hardware circuit structures. Designers almost always obtain the corresponding hardware circuit structure by programming the improved methodology into the hardware circuit. Therefore, it cannot be said that a methodological improvement cannot be implemented using hardware physical modules. For example, a Programmable Logic Device (PLD) (such as a Field Programmable Gate Array (FPGA)) is such an integrated circuit whose logic function is determined by the user programming the device. Designers can program a digital system themselves to "integrate" it onto a PLD, without needing chip manufacturers to design and manufacture dedicated integrated circuit chips. Furthermore, nowadays, instead of manually manufacturing integrated circuit chips, this programming is mostly implemented using "logic compiler" software. Similar to the software compiler used in program development, the original code before compilation must also be written in a specific programming language, called a Hardware Description Language (HDL). There are many HDLs, such as ABEL (Advanced Boolean Expression Language), AHDL (Altera Hardware Description Language), Confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), Lava, Lola, MyHDL, PALASM, and RHDL (Ruby Hardware Description Language). Currently, the most commonly used are VHDL (Very-High-Speed ​​Integrated Circuit Hardware Description Language) and Verilog. Those skilled in the art should also understand that by simply performing some logic programming on the method flow using one of these hardware description languages ​​and programming it into an integrated circuit, the hardware circuit implementing the logical method flow can be easily obtained.

[0188] The controller can be implemented in any suitable manner. For example, it can take the form of a microprocessor or processor and a computer-readable medium storing computer-readable program code (e.g., software or firmware) executable by the (micro)processor, logic gates, switches, application-specific integrated circuits (ASICs), programmable logic controllers, and embedded microcontrollers. Examples of controllers include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicon Labs C8051F320. A memory controller can also be implemented as part of the control logic of the memory. Those skilled in the art will also recognize that, in addition to implementing the controller in purely computer-readable program code form, the same functionality can be achieved by logically programming the method steps to make the controller take the form of logic gates, switches, application-specific integrated circuits, programmable logic controllers, and embedded microcontrollers. Therefore, such a controller can be considered a hardware component, and the means included therein for implementing various functions can also be considered as structures within the hardware component. Alternatively, the means for implementing various functions can be considered as both software modules implementing the method and structures within the hardware component.

[0189] The systems, devices, modules, or units described in the above embodiments can be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer. Specifically, a computer can be, for example, a personal computer, laptop computer, cellular phone, camera phone, smartphone, personal digital assistant, media player, navigation device, email device, game console, tablet computer, wearable device, or any combination of these devices.

[0190] For ease of description, the above devices are described separately by function as various units. Of course, in implementing this application, the functions of each unit can be implemented in one or more software and / or hardware.

[0191] Those skilled in the art will understand that one or more embodiments of this specification can be provided as a method, system, or computer program product. Therefore, the invention can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the invention can take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0192] This invention is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart illustrations and / or block diagrams. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0193] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0194] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0195] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0196] Memory may include non-persistent storage in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of computer-readable media.

[0197] Computer-readable media includes both permanent and non-permanent, removable and non-removable media that can store information using any method or technology. Information can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital character versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.

[0198] This application can be described in the general context of computer-executable instructions, such as program modules, that are executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc., that perform a specific task or implement a specific abstract data type. This application can also be practiced in distributed computing environments where tasks are performed by remote processing devices connected via a communication network. In distributed computing environments, program modules can reside in local and remote computer storage media, including storage devices.

[0199] The above description is merely an embodiment of this application and is not intended to limit the scope of this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of the claims of this application.

Claims

1. A method for deploying intelligent agents, applied to a configuration center, comprising: Receive registration information sent when the atomic capability service and application service start up, wherein the registration information includes service access address and service configuration information; Receive service dependency information sent by the application service, wherein the service dependency information is used to represent at least one atomic capability service that the application service depends on; Based on the service dependency information, a service dependency graph is constructed, and based on the service dependency graph, the service access address, and the service configuration information, the configuration dependency coverage is determined. If the configuration dependency coverage meets the preset coverage threshold, the target agent is determined to be deployed successfully, wherein the target agent is collaboratively constructed based on the atomic capability service and the application service.

2. The agent deployment method according to claim 1, wherein receiving the registration information sent when the atomic capability service and application service are started includes: Receive the first registration information sent when the atomic capability service starts, wherein the first registration information includes the atomic capability service access address and the atomic capability service configuration information; as well as The system receives second registration information sent when the application service starts, wherein the second registration information includes the application service access address and the application service configuration information.

3. The agent deployment method according to claim 2, wherein determining the configuration dependency coverage based on the service dependency graph, the service access address, and the service configuration information includes: Based on the service dependency graph, the atomic capability service access address, the application service access address, the atomic capability service configuration information, and the application service configuration information, the configuration dependency coverage is determined.

4. The agent deployment method according to claim 3, wherein determining the configuration dependency coverage based on the service dependency graph, the atomic capability service access address, the application service access address, the atomic capability service configuration information, and the application service configuration information includes: Based on the atomic capability service access address and the atomic capability service configuration information, perform atomic capability service verification on the atomic capability service, obtain the atomic capability service verification result, and determine the registration status of the atomic capability service based on the atomic capability service verification result. Based on the application service access address and the application service configuration information, the application service is verified to obtain the application service verification result, and the registration status of the application service is determined based on the application service verification result. The configuration dependency coverage is determined based on the service dependency graph, the registration status of the atomic capability service, and the registration status of the application service.

5. The agent deployment method according to claim 4, wherein determining the configuration dependency coverage based on the service dependency graph, the registration status of the atomic capability service, and the registration status of the application service includes: Traverse the dependency edges in the service dependency graph, wherein the dependency edges are used to represent the dependency relationship between the service provider and the service consumer on which the service provider depends. The service provider is any one of the application services, and the service consumer is at least one atomic capability service among the atomic capability services, at least one application service among the application services, or at least one application service among the application services and at least one atomic capability service among the atomic capability services. Based on the registration status of the atomic capability service and the registration status of the application service, determine the registration status of the service provider and the registration status of the service consumer on which the service provider depends; The establishment status of the dependency edge is determined based on the registration status of the service provider and the registration status of the service consumer on which the service provider depends. Calculate the configuration dependency coverage based on the establishment status of the dependency edges.

6. The agent deployment method according to claim 5, wherein the establishment state includes an established state and an unestablished state; The step of calculating the configuration dependency coverage based on the establishment status of the dependency edges includes: Based on the establishment status of the dependency edges, determine the number of dependency edges in the established state and the number of dependency edges in the unestablished state. The configuration dependency coverage is calculated based on the number of dependency edges in the established state, the number of dependency edges in the unestablished state, and the total number of dependency edges in the service dependency graph.

7. The agent deployment method according to claim 5, wherein the registration status includes a registered status and an unregistered status; Determining the registration status of the service provider and the service consumer on which the service provider depends, based on the registration status of the atomic capability service and the registration status of the application service, includes: Based on the registration status of the atomic capability service and the registration status of the application service, determine the registered or unregistered status of the service provider and the registered or unregistered status of at least one service consumer on which the service provider depends; Determining the establishment status of the dependency edge based on the registration status of the service provider and the registration status of the service consumer on which the service provider depends includes: If it is determined that the registration status of the service provider and the registration status of the service consumer on which the service provider depends are both registered, then the establishment status of the dependency edge is determined to be established. or If the registration status of the service provider and the service consumer on which the service provider depends are both registered, or if either is unregistered, then the establishment status of the dependency edge is determined to be unestablished.

8. The agent deployment method according to claim 6, further comprising, after determining the configuration dependency coverage: If it is determined that the configuration dependency coverage does not meet the preset coverage threshold, the configuration dependency coverage and the dependency edges whose establishment status is not established are displayed through a visual interface.

9. The agent deployment method according to any one of claims 1-8, further comprising, after determining the configuration dependency coverage: If the configuration dependency coverage is determined to meet the preset coverage threshold, the configuration dependency coverage will be displayed through a visual interface.

10. The intelligent agent deployment method according to claim 2, wherein the first registration information is automatically sent to the configuration center by reading the center address of the configuration center pre-configured in the running environment when the atomic capability service is started; as well as The second registration information is automatically sent to the configuration center when the application service starts by reading the central address of the configuration center pre-configured in the runtime environment.

11. The agent deployment method according to any one of claims 1-8, wherein the application service includes a primary application service and a secondary application service; The receipt of service dependency information sent by the application service includes: Receive first-level service dependency information sent by the first-level application service, wherein the first-level service dependency information is used to represent at least one atomic capability service that the first-level application service depends on; Receive secondary service dependency information sent by the secondary application service, wherein the secondary service dependency information is used to indicate at least one primary application service that the secondary application service depends on, or at least one primary application service and at least one atomic capability service that it depends on. The step of constructing a service dependency graph based on the service dependency information includes: Construct a service dependency graph based on the first-level application service, at least one atomic capability service that the first-level application service depends on, the second-level application service, at least one first-level application service that the second-level application service depends on, or at least one first-level application service and at least one atomic capability service that the second-level application service depends on.

12. The agent deployment method according to any one of claims 5-8, further comprising, after the determination of the target agent deployment is completed: The system receives update registration information sent by the atomic capability service and / or the application service when dynamic parameters change during operation. The update registration information includes the update service access address and / or update service configuration information. If the atomic capability service and / or the application service are determined to be service providers based on the dependency edges in the service dependency graph, the update service access address and / or update service configuration information are sent to at least one service consumer that the service provider depends on.

13. An agent deployment device, applied in a configuration center, comprising: The registration information receiving module is configured to receive registration information sent when the atomic capability service and application service start up, wherein the registration information includes service access address and service configuration information; The dependency information receiving module is configured to receive service dependency information sent by the application service, wherein the service dependency information is used to represent at least one atomic capability service that the application service depends on. The dependency coverage determination module is configured to construct a service dependency graph based on the service dependency information, and determine the configuration dependency coverage based on the service dependency graph, the service access address, and the service configuration information. The agent deployment module is configured to determine that the target agent deployment is complete when the configuration dependency coverage meets a preset coverage threshold, wherein the target agent is collaboratively constructed based on the atomic capability service and the application service.

14. A computing device, comprising: Memory and processor; The memory is used to store computer programs / instructions, and the processor is used to execute the computer programs / instructions, which, when executed by the processor, implement the steps of the agent deployment method according to any one of claims 1 to 12.

15. A computer-readable storage medium storing a computer program / instructions that, when executed by a processor, implement the steps of the agent deployment method according to any one of claims 1 to 12.

16. A computer program product comprising a computer program / instructions that, when executed by a processor, implement the steps of the agent deployment method according to any one of claims 1 to 12.

Images