A method and apparatus for network-free isolation and linkage between desktop host and AI entry point
By generating structured host state signals and establishing local network-free communication links, the problem of blurred interaction boundaries and inconsistent state transmission between the desktop host and the AI entry point is solved. This enables network-free state-isolated linkage between the desktop and the AI entry point, improving operational stability and interaction consistency, and supporting rapid iteration of AI capabilities.
Patent Information
- Application Number
- CN202611193865.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-08-07
- Publication Date
- 2026-11-10
AI Technical Summary
In existing technologies, the linkage scheme between the desktop host and the AI entry point has problems such as deep coupling, which makes it easy for AI backend abnormalities to be transmitted to the desktop main link and insufficient operational stability, or completely independent operation, which leads to poor interactive linkage and inability to synchronize the interface state. It is difficult to balance the high availability of the desktop with the rapid iteration of the AI capability link and the consistency of the interactive experience.
By acquiring the preset linkage contract and state encapsulation specifications, host state encapsulation rules and local communication channel parameters are generated, a local network-free communication link is established, structured host state signals are transmitted, desktop state data is parsed, and the AI entry interaction interface is independently managed to achieve network-free state isolation linkage.
It achieves complete decoupling between the desktop and the AI entry point, avoids abnormal transmission of AI backend, improves desktop operation stability and consistency of interactive experience, supports rapid iteration and independent operation and maintenance of AI capabilities, and adapts to the needs of rapid upgrades of multiple backends.
Smart Images

Figure CN123068145A_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the field of artificial intelligence technology, specifically to a method and apparatus for isolating and linking a desktop host and an AI entry point in a network-free state. Background Technology
[0002] With the rapid development of AI-powered smart terminal devices, AI entry points have become standard interactive interfaces for devices such as smart cash registers, smart tablets, and POS terminals. Their backends can connect to various AI capability components, including cloud-based model services, edge-side model runtimes, local intelligent agent sandboxes, and system capability gateways, to meet the intelligent interaction needs of different scenarios. The desktop host, as the core system entry point of the smart terminal, undertakes core functions such as main interface display, window management, and user interaction scheduling. Its operational stability directly affects the overall availability of the device. In actual deployment, the AI entry point needs to achieve interactive linkage with the desktop host, such as window attachment, sliding interaction, and lifecycle synchronization, to ensure the smoothness and consistency of user operations. However, at the same time, AI backend components are characterized by short iteration cycles, high update frequency, and volatile operating states. If the architecture design of both is unreasonable, changes and failures in AI capabilities can easily be transmitted to the desktop main link.
[0003] Existing solutions for integrating desktops and AI entry points suffer from two main technical drawbacks. The first is a deeply coupled solution, where the AI entry logic is directly integrated into the desktop host process. The desktop directly connects to various AI backend services and manages the AI's operational status. In this solution, the desktop process must handle additional functions such as AI protocol adaptation, network connectivity, and model service status maintenance. Upgrades, restarts, and abnormal failures of the AI backend directly impact the stability of the desktop's main link, potentially causing the desktop process to crash. Furthermore, the desktop process introduces security risks due to access to AI access credentials and system gateway permissions, and AI capability iterations require simultaneous modifications to the desktop program, resulting in low iteration efficiency. The second is a completely independent solution, where the AI entry point runs as an independent application or floating window, without deep integration with the desktop host. While this solution achieves decoupling, the AI entry point cannot obtain host state information such as window identifiers, lifecycles, scrolling progress, and visibility. This makes it difficult to achieve smooth scrolling interaction with the desktop, precise window hierarchy adaptation, and synchronized state recovery. The user experience is fragmented, and the integration with the desktop cannot be quickly restored after an abnormal restart.
[0004] In summary, the current AI smart device field has not yet formed a complete technical solution for isolating and linking the desktop and AI entry point. It cannot simultaneously ensure the operational stability of the desktop main link, the independent iteration of the AI capability link, and the consistency of the interactive experience. It is also difficult to adapt to application scenarios where the rapid evolution of AI backend components and the high availability requirements of the desktop coexist. Summary of the Invention
[0005] In view of the aforementioned problems, this application is proposed to provide a method and apparatus for isolated linkage between a desktop host and an AI entry point in a network-free state, which overcomes or at least partially solves the aforementioned problems, comprising: A method for isolating and linking a desktop host and an AI entry point in a network-free state includes the following steps: Obtain the preset linkage contract and state encapsulation specification, and generate host state encapsulation rules and local communication channel parameters through the linkage contract and the state encapsulation specification; The desktop running state is encapsulated into a structured host state signal according to the host state encapsulation rules. A local network-free communication link is established based on the local communication channel parameters; The structured host status signal is sent to the AI entry point via the local network-free communication link, and the desktop status data is obtained by parsing. Based on the desktop status data, the AI entry interaction interface is determined, and the isolated linkage in the absence of network is completed.
[0006] Furthermore, the step of obtaining a preset linkage contract and state encapsulation specification, and generating host state encapsulation rules and local communication channel parameters through the linkage contract and the state encapsulation specification, includes: Obtain the preset linkage contract file and state encapsulation specification file; the linkage contract only contains local service identifier, message type definition and communication protocol information; Parse the service identifier and communication protocol information in the linkage contract to generate local communication channel parameters; The state field definitions and data format requirements in the state encapsulation specification are parsed to generate host state encapsulation rules.
[0007] Furthermore, the step of encapsulating the desktop running state into a structured host state signal according to the host state encapsulation rule includes: Collect the current window identifier, lifecycle state, visibility state, swipe interaction progress and back event on the desktop to obtain desktop running status data; Based on the host state encapsulation rules, the desktop running state data is regularized and formatted to encapsulate and generate a structured host state signal.
[0008] Furthermore, the step of establishing a local network-less communication link based on the local communication channel parameters includes: The local communication channel parameters are analyzed to determine the target AI entry service identifier and inter-process communication protocol type; Initiate a local service binding request based on the target AI entry service identifier, and establish a cross-process communication connection according to the inter-process communication protocol type; After the communication connection is verified, a local networkless communication link is generated for transmitting structured host status signals.
[0009] Furthermore, the step of sending the structured host state signal to the AI entry point via the local network-free communication link and parsing it to obtain desktop state data includes the following steps: The structured host status signal is sent to the AI entry service via the local network-free communication link. The AI entry service performs format verification and protocol parsing on the received structured host state signals; Extract the window identifier, lifecycle, visibility, and interaction progress fields from the signal to obtain desktop state data for interface synchronization.
[0010] Furthermore, the step of determining the AI entry interaction interface based on the desktop status data and completing the offline isolation linkage step includes: Based on the desktop status data, adjust and determine the window position, display level, visibility and lifecycle status of the AI entry interaction interface to complete the interface status synchronization; The AI capability chain can be managed independently within its own process through the AI portal service; By synchronizing interface status and independently managing AI capability links, the desktop host and AI entry point can achieve isolated linkage in the absence of network access.
[0011] Furthermore, the method also includes disconnection state caching and state replay steps, including: When a local network communication link is detected to be disconnected, the desktop host caches the last generated structured host state signal and initiates a reconnection request according to the preset backoff strategy. After successfully reconnecting and rebuilding the local network-free communication link, the desktop host will replay the cached structured host state signals to the AI entry service; The AI gateway service restores the state of the AI gateway interface based on the replayed structured host state signal and independently rebuilds the AI capability chain.
[0012] A device for isolating and linking a desktop host and an AI entry point in a network-free state, the device implementing the steps of the aforementioned method for isolating and linking a desktop host and an AI entry point in a network-free state: include: The acquisition module is used to acquire preset linkage contracts and state encapsulation specifications, and generate host state encapsulation rules and local communication channel parameters through the linkage contracts and state encapsulation specifications. The structured host state signal module is used to encapsulate the desktop running state into a structured host state signal according to the host state encapsulation rules. A local network-free communication link module is used to establish a local network-free communication link based on the local communication channel parameters. The desktop status data module is used to send the structured host status signal to the AI entry point through the local network-free communication link and parse it to obtain desktop status data; The AI entry interaction interface module is used to determine the AI entry interaction interface based on the desktop status data, and to complete the isolation linkage in the absence of network status.
[0013] A computer electronic device includes a processor, a memory, and a computer program stored in the memory and capable of running on the processor, wherein the computer program, when executed by the processor, implements the method described in any of the preceding descriptions.
[0014] A computer-readable storage medium storing a computer program that, when executed by a processor, implements the method described in any of the preceding claims.
[0015] This application has the following advantages: In the embodiments of this application, compared with the shortcomings of the prior art where the deep coupling between the desktop host and the AI entry point leads to the easy transmission of AI backend abnormalities to the desktop main link and insufficient desktop operation stability, or the complete independent operation of the two leads to poor interaction and linkage and the inability to synchronously restore the interface state, this application provides a desktop host and AI entry point isolation linkage solution based on standardized state encapsulation and local network-free communication. Specifically, it involves: obtaining a preset linkage contract and state encapsulation specification, and generating host state encapsulation rules and local communication channel parameters through the linkage contract and the state encapsulation specification; encapsulating the desktop operation state into a structured host state signal according to the host state encapsulation rules; establishing a local network-free communication link according to the local communication channel parameters; sending the structured host state signal to the AI entry point through the local network-free communication link, and parsing to obtain desktop state data; determining the AI entry point interaction interface based on the desktop state data, and completing the network-free state isolation linkage. By pre-setting linkage contracts and state encapsulation specifications, and generating host state encapsulation rules and local communication channel parameters in advance, this solution addresses the problems of ambiguous interaction boundaries between the desktop and AI entry point, inconsistent state transmission interfaces, and difficulty in managing coupling relationships in existing solutions. It achieves the effect of clarifying the scope of interaction between the two at the contract level, only stipulating host state-related fields and local communication rules, and not involving any AI backend configuration information. This prevents the desktop process from accessing sensitive parameters such as AI backend addresses, access keys, and model identifiers, thus strengthening the permission isolation boundary between the two. Attached Figure Description
[0016] To more clearly illustrate the technical solution of this application, the drawings used in the description of this application will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.
[0017] Figure 1 This is a flowchart illustrating the steps of a method for isolating and linking a desktop host and an AI entry point in a network-free state, as provided in an embodiment of this application. Figure 2 This is a structural block diagram of a desktop host and AI entry point isolation linkage device without network status, provided in one embodiment of this application; Figure 3 This is a schematic diagram of the structure of a computer device provided in an embodiment of the present invention; 1. Computer equipment; 2. External devices; 3. Processing unit; 4. Bus; 5. Network adapter; 6. I / O interface; 7. Display; 8. Memory; 9. Random access memory; 10. Cache memory; 11. Storage system; 12. Program / utility; 13. Program module. Detailed Implementation
[0018] To make the objectives, features, and advantages of this application more apparent and understandable, the application will be further described in detail below with reference to the accompanying drawings and specific embodiments. Obviously, the described embodiments are only some, not all, of the embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application without inventive effort are within the scope of protection of this application.
[0019] The inventors discovered through analysis of existing technologies that the current AI smart device field has not yet formed a complete technical solution for isolating and linking the desktop and AI entry point. It is unable to simultaneously ensure the operational stability of the desktop main link, the independent iteration of the AI capability link, and the consistency of the interactive experience, making it difficult to adapt to application scenarios where the rapid evolution of AI backend components and the high availability requirements of the desktop coexist.
[0020] Reference Figure 1 This paper illustrates a method for isolating and linking a desktop host and an AI entry point in a network-free state, comprising the following steps: S110. Obtain the preset linkage contract and state encapsulation specification, and generate host state encapsulation rules and local communication channel parameters through the linkage contract and the state encapsulation specification. S120. The desktop running state is encapsulated into a structured host state signal according to the host state encapsulation rules. S130. Establish a local network-free communication link based on the local communication channel parameters; S140. The structured host status signal is sent to the AI entry point through the local network-free communication link, and the desktop status data is obtained by parsing. S150. Determine the AI entry interaction interface based on the desktop status data to complete the isolation linkage in the absence of network.
[0021] In the embodiments of this application, compared with the shortcomings of the prior art where the deep coupling between the desktop host and the AI entry point leads to the easy transmission of AI backend abnormalities to the desktop main link and insufficient desktop operation stability, or the complete independent operation of the two leads to poor interaction and linkage and the inability to synchronously restore the interface state, this application provides a desktop host and AI entry point isolation linkage solution based on standardized state encapsulation and local network-free communication. Specifically, it involves: obtaining a preset linkage contract and state encapsulation specification, and generating host state encapsulation rules and local communication channel parameters through the linkage contract and the state encapsulation specification; encapsulating the desktop operation state into a structured host state signal according to the host state encapsulation rules; establishing a local network-free communication link according to the local communication channel parameters; sending the structured host state signal to the AI entry point through the local network-free communication link, and parsing to obtain desktop state data; determining the AI entry point interaction interface based on the desktop state data, and completing the network-free state isolation linkage.
[0022] By pre-setting linkage contracts and state encapsulation specifications, and generating host state encapsulation rules and local communication channel parameters in advance, this solution addresses the problems of ambiguous interaction boundaries between the desktop and AI entry point, inconsistent state transmission interfaces, and difficulty in managing coupling relationships in existing solutions. It achieves the effect of clarifying the scope of interaction between the two at the contract level, only stipulating host state-related fields and local communication rules, and not involving any AI backend configuration information. This prevents the desktop process from accessing sensitive parameters such as AI backend addresses, access keys, and model identifiers, thus strengthening the permission isolation boundary between the two.
[0023] By encapsulating the desktop running state into structured host state signals according to rules and completing state transmission based on local network-free communication links, the technology solves the problem in existing coupled solutions where the desktop needs to directly connect to AI backend services and rely on network connections and AI service running states. It achieves the effect that the entire state interaction is completed only through local inter-process communication, without establishing any network connections or relying on the AI backend running state. Upgrades, restarts, and failures of the AI backend will not be transmitted to the desktop main link, effectively ensuring the stability and availability of the desktop core processes.
[0024] By analyzing desktop status data at the AI entry point, independently determining the interactive interface, and autonomously managing the AI capability chain, this solution addresses the issues in existing solutions where the desktop must assume AI capability management responsibilities and AI capability iterations require simultaneous modifications to the desktop program. It achieves the effect of the AI capability chain running completely independently of the desktop process, and the replacement, expansion, and maintenance of the AI backend do not require changes to the desktop host code, significantly improving the iteration efficiency and deployment flexibility of AI capabilities. Simultaneously, it achieves precise synchronization of interface status based on structured status signals, balancing chain isolation with smooth and consistent user interaction.
[0025] By leveraging the technical features of a layered, isolated, and interconnected architecture, this solution resolves the technical contradictions inherent in existing solutions, which cannot simultaneously balance high desktop stability, independent AI iteration, and consistent interactive linkage. It achieves complete decoupling between the desktop main link and the AI capability link, enabling them to interact and link solely through standardized local status signals. This not only ensures the operational reliability of the core desktop entry point but also supports the rapid evolution and independent operation and maintenance of AI capabilities. It can fully adapt to the multi-backend, rapid iteration, and high availability requirements of AI smart devices.
[0026] It's important to note that the desktop host and the AI entry point only interact with each other on pure host-level state information such as window attachment, lifecycle, and interaction progress. No AI business data, backend configurations, or permission credentials are transmitted. The scheduling, connection, and operation of the entire AI capability chain, including the AI runtime, intelligent agent backend, model service, and system capability gateway, are completely converged within the AI entry point service, thoroughly decoupled from the desktop main chain. This architecture differs from both the traditional negative one screen solution where the desktop and business pages are deeply bound, and the completely independent floating window solution. It enables smooth interaction and linkage between the AI entry point and the desktop while ensuring high stability and availability of the desktop main process, fully adapting to the multi-backend parallel and rapid iterative upgrade scenarios of AI intelligent devices.
[0027] As described in step S110, a preset linkage contract and state encapsulation specification are obtained, and host state encapsulation rules and local communication channel parameters are generated through the linkage contract and the state encapsulation specification.
[0028] It's important to note that by pre-setting contracts and specifications, the state encapsulation standard, communication connection rules, and core linkage logic are decoupled. The linkage contract and state encapsulation specification support configurable deployment. When subsequent adjustments to state fields, communication protocols, or service identifiers are needed, only the corresponding configuration files need to be modified to take effect, without altering the core business logic of the desktop host and AI entry point, demonstrating excellent maintainability and scalability. Furthermore, all encapsulation rules and communication parameters generated in this step are designed solely around local state interaction, without introducing any AI backend-related configuration information throughout the process, thus establishing a strong isolation boundary between the two from the initialization stage.
[0029] In one embodiment of the present invention, the specific process of step S110, "obtaining a preset linkage contract and state encapsulation specification, and generating host state encapsulation rules and local communication channel parameters through the linkage contract and the state encapsulation specification", can be further described in conjunction with the following description.
[0030] As described in the following steps, obtain the preset linkage contract file and state encapsulation specification file; the linkage contract only contains local service identifier, message type definition and communication protocol information; It should be noted that the aforementioned linkage contract only stipulates the basic rules for local interaction between the desktop host and the AI entry point, completely eliminating all information related to the AI capability link, such as the AI backend address, model identifier, access key, service port, and system gateway permissions. This blocks the path for the desktop process to obtain AI backend configuration from the source of the contract definition, fundamentally avoiding business-level coupling dependencies between the two. The state encapsulation specification document clearly defines the field composition, data type, value range, and serialization format standard of the host state signals, ensuring that the encapsulation operation on the desktop side and the parsing operation on the AI entry point side follow a unified data standard, guaranteeing the accuracy and consistency of cross-process state transmission.
[0031] As described in the following steps, parse the service identifier and communication protocol information in the linkage contract to generate local communication channel parameters; It's important to note that the local communication channel parameters are used to build a purely local cross-process communication channel. All parameters are generated based on local service location and communication protocol configuration, without involving any network IP address, network port, or remote service configuration. The communication link established based on these parameters is entirely independent of the network environment. Even if the device is in a completely network-free state, it can still normally complete the status interaction and linkage between the desktop and the AI entry point. The channel parameters correspond to the local inter-process communication protocol and are compatible with various local communication mechanisms such as Messenger, Binder, and AIDL. The communication scope is strictly limited to different processes on the same device. Status data does not leave the local machine, ensuring low latency and high reliability of status transmission while avoiding the risk of information leakage caused by transmitting status data over the network.
[0032] As described in the following steps, the state field definitions and data format requirements in the state encapsulation specification are parsed to generate host state encapsulation rules.
[0033] It should be noted that the encapsulation rules are designed in strict accordance with the principle of minimum necessity. They define field constraints and format requirements only around the desktop's own running state, and do not involve AI-related data such as AI session content, backend connection status, model identification, and system tool execution information. This ensures that the signals output by the desktop encapsulation only carry the host's own window and interaction state, further consolidating the isolation boundary between the desktop and the AI capability link from the data level, and preventing AI-related information from back-penetrating into the desktop's main process.
[0034] The host state encapsulation rules clearly define the naming conventions, data types, value ranges, and serialization formats for core state fields such as window identifier, lifecycle state, visibility state, swipe interaction progress, and back event. This allows for field standardization and format unification of raw runtime states collected from the desktop, ensuring that desktop hosts with different hardware configurations and system versions can output structured host state signals with a consistent format. This guarantees the universality and accuracy of state parsing at the AI entry point. Furthermore, these encapsulation rules are independent of the linkage contract. When adding new interaction state types or adjusting the granularity of state fields, only updating the state encapsulation specifications and simultaneously refreshing the encapsulation rules is required for the changes to take effect. No modifications to the communication contract or underlying link logic are needed, allowing for flexible adaptation to the state synchronization needs of more interaction scenarios while maintaining the isolation boundary.
[0035] As described in step S120, the desktop running state is encapsulated into a structured host state signal according to the host state encapsulation rules.
[0036] It's important to note that the desktop host at this stage only handles its own native window, lifecycle, and interaction state. It does not generate any AI business requests, connect to any AI backend services, or inject any AI-related configuration information. This ensures a clear boundary of responsibility between the desktop process and the AI capability link from a data production perspective. The encapsulated structured host state signals serve as the sole carrier of state interaction between the desktop and the AI entry point. They possess a unified field structure and data format, ensuring the accuracy of cross-process transmission parsing and limiting the scope of interaction to the host state dimension, thus preventing AI business data from penetrating the desktop side.
[0037] In one embodiment of the present invention, the specific process of "encapsulating the desktop running state into a structured host state signal according to the host state encapsulation rules" in step S120 can be further described in conjunction with the following description.
[0038] As described in the following steps, collect the current window identifier, lifecycle state, visibility state, swipe interaction progress and back event of the desktop to obtain desktop running status data; It should be noted that the collected desktop running status data are all native running information held by the desktop process itself, covering window attachment attributes, process lifecycle, interface visibility, user interaction progress and system rollback commands. All of these fall within the native responsibilities of the desktop host and can be obtained without connecting to any external services or additional permissions.
[0039] Window identifiers are used for window hierarchy attachment and alignment of the AI entry interface; lifecycle states are used to synchronize the start and stop of the AI entry and resource scheduling; visibility and scrolling progress are used to achieve smooth interactive animations between the desktop and the AI entry; and back events are used to synchronize the interface exit logic. All state fields are only used to describe the desktop's own running and interactive state and do not contain any business information related to the AI backend, model services, or system gateway, ensuring the purity and isolation of state transmission from the data source.
[0040] As described in the following steps, the desktop running status data is standardized in terms of field regularization and format according to the host state encapsulation rules, and encapsulated to generate a structured host state signal.
[0041] It should be noted that the encapsulation operation only performs field regularization and format standardization processing. It strictly follows the host state encapsulation rules to unify field naming, convert data types, and encapsulate the original state data in serialization format. It does not modify the original semantics of the state, does not add any AI business fields, and does not inject any backend configuration information, ensuring that the encapsulated signal only carries the desktop host's own running state.
[0042] Standardized structured signals have a unified data structure and parsing rules, which can reduce format parsing errors in cross-process communication, improve the reliability of state transmission, and facilitate the caching and persistence of state signals on the desktop side, providing a standardized data foundation for state replay and interface recovery after service disconnection. At the same time, the encapsulation rules are configurable and extensible, and when adding new interactive state types, only the rules need to be updated to adapt, without changing the underlying communication link and the core logic of the AI entry point.
[0043] As described in step S130, a local network-free communication link is established based on the local communication channel parameters.
[0044] It should be noted that the established local network-free communication link is only used to transmit structured host state signals and abstract entry interaction states. It does not carry AI business requests, backend configuration information, access credentials, or system tool call instructions. This completely isolates the desktop main link from the AI capability link at the transmission channel level, preventing network status and service fluctuations of the AI backend from being transmitted to the desktop process through the transmission channel. The establishment and maintenance of the link are entirely managed by the desktop host's state bridging module, without intruding on the desktop's main business logic. Even if the link is abnormally disconnected, it will not affect the normal operation of the desktop main interface, ensuring the high availability of the desktop's core functions.
[0045] In one embodiment of the present invention, the specific process of "establishing a local network-free communication link based on the local communication channel parameters" in step S130 can be further described in conjunction with the following description.
[0046] As described in the following steps, the local communication channel parameters are parsed to determine the target AI entry service identifier and the inter-process communication protocol type; It should be noted that all local communication channel parameters are derived from the preset linkage contract, containing only two types of information: local service identifier and inter-process communication protocol type. They do not carry any network IP address, service port, remote interface path, or AI backend configuration parameters. From the parameter source, the communication scope is limited to processes within the local machine. The target AI entry service identifier is used to locate the corresponding AI entry service process in the local service registry. The inter-process communication protocol type determines the specific implementation method of cross-process communication, adapting to various local communication mechanisms such as Messenger, Binder, and AIDL. The communication boundary is strictly controlled within the process space of the same device, and data never leaves the local machine. This ensures low latency and high reliability of state transmission while eliminating the security risk of state data leakage over the network.
[0047] As described in the following steps, a local service binding request is initiated based on the target AI entry service identifier, and a cross-process communication connection is established according to the inter-process communication protocol type; It's important to note that the service binding request is initiated only for the AI entry service running on the local machine. This is a binding operation for a local service component within the system, requiring no network permissions and not relying on an external network environment. Even if the device is completely offline, service binding and communication connection establishment can still be completed normally. The binding process only verifies the component identity and communication protocol compatibility of the local service; it does not check the status of the AI backend service, model loading, or system gateway permissions. Whether the AI capability links within the AI entry service are ready or running normally does not affect the result of the local service binding, further decoupling the operational status of the desktop main link and the AI capability link. After the connection is established, the desktop host only holds the communication channel handle and does not obtain process data, AI session information, or backend configurations within the AI entry service, maintaining the permission boundaries and data isolation between the two.
[0048] As described in the following steps, after the communication connection is verified, a local networkless communication link is generated for transmitting structured host state signals.
[0049] It's important to note that the generated local network-free communication link is a dedicated state transmission channel. Its sole purpose is to transmit structured host state signals and abstract entry interaction states between the desktop host and the AI entry service. It does not handle AI business data forwarding, backend request relaying, or system command pass-through. This channel purpose solidifies the isolated linkage boundary between the two. After the link is established, connectivity and format compatibility checks are performed to ensure that both parties can send and receive state signals normally according to the agreed encapsulation rules. It is only officially activated after the check passes. Simultaneously, the link maintains a connection state identifier for subsequent disconnection detection, backoff reconnection, and state cache triggering, providing channel-layer support for stable linkage throughout the entire lifecycle. Anomalies in this link will only affect the state synchronization effect between the AI entry and the desktop, and will not interrupt the operation of the desktop's main functions or interfere with the independent operation of the AI capability links within the AI entry.
[0050] As described in step S140, the structured host status signal is sent to the AI entry point through the local network-free communication link, and the desktop status data is obtained by parsing.
[0051] It should be noted that the entire state transmission is completed based on the local inter-process communication link, without passing through any network nodes or depending on the network environment. Even if the device is completely offline, the state transmission can still be completed normally, completely avoiding the impact of network fluctuations and remote service failures on the interaction between the desktop and the entry point. The transmitted content is limited to structured host state signals and does not contain any AI backend addresses, access keys, model identifiers, session content, or system tool states. The desktop host only acts as a state producer to send signals and does not parse or perceive the internal business operation state of the AI entry point, strictly implementing the isolation boundary between the two at the transmission level.
[0052] In one embodiment of the present invention, the specific process of step S140, "sending the structured host status signal to the AI entry point through the local network-free communication link and parsing to obtain desktop status data," can be further explained in conjunction with the following description.
[0053] As described in the following steps, the structured host status signal is sent to the AI entry service through the local network-free communication link; It should be noted that the transmission of structured host state signals is uniformly triggered by the desktop host's state bridging module. The transmission timing is synchronized with changes in desktop interaction state. When the user performs operations such as swiping, returning, or switching pages, or when the desktop lifecycle or window state changes, the latest state signal is generated and sent in real time, ensuring that the AI entry point can synchronously perceive changes in desktop state. The transmission process strictly follows the message format and communication sequence agreed upon in the linkage contract, transmitting only host state data within the agreed scope, without including any AI business requests, backend configuration information, or system control commands. At the same time, the AI entry point only transmits the abstract entry interaction state back to the desktop, without transmitting AI session content, model connection status, or system tool execution details, ensuring that bidirectional data transmission is strictly limited to the scope of state linkage and does not exceed the isolation boundary.
[0054] As described in the following steps, the AI entry service performs format verification and protocol parsing on the received structured host state signals; It's important to note that format validation and protocol parsing are both completed independently within the AI entry service process. The desktop host does not participate in the parsing process and is unaware of the business application of the parsing results. The validation phase verifies the signal's format compliance, field integrity, and data legality. Only signals conforming to the host's state encapsulation rules are parsed, filtering out illegal fields and abnormal data to prevent unauthorized data from entering the AI entry service, ensuring the security and stability of the link. The parsing process strictly adheres to preset encapsulation rules, adapting corresponding parsing logic for different inter-process communication protocols. It is compatible with various native communication mechanisms such as Messenger, Binder, and AIDL, ensuring consistent state parsing results across different communication channels and providing unified and accurate state input for subsequent interface synchronization.
[0055] As described in the following steps, extract the window identifier, lifecycle, visibility, and interaction progress fields from the signal to obtain desktop state data for interface synchronization.
[0056] It should be noted that the extracted desktop state data consists entirely of window, lifecycle, and interaction attributes at the host level. This data is used solely for state synchronization and layout adjustment of the AI entry interface and does not participate in the business logic processing of the AI capability chain, nor is it passed as a parameter to the cloud model, the edge runtime, or the system capability gateway. The extracted data fields comprehensively cover all state information required for window attachment, display hierarchy, visibility control, and interactive animation matching. This supports precise alignment, smooth sliding, and lifecycle synchronization between the AI entry and the desktop, ensuring a smooth and consistent interactive experience while maintaining chain isolation. The extracted desktop state data is only cached within the AI entry service and is not passed back to the desktop host process, avoiding redundant overhead and state chaos caused by circular state data transmission.
[0057] As described in step S150, the AI entry interaction interface is determined based on the desktop status data to complete the isolation linkage in the absence of network.
[0058] It should be noted that by parallel processing of interface state synchronization and independent management of AI capability links, the interaction and linkage between the desktop and the AI entry point are completed, while the responsibilities and operational isolation of the two are clearly defined.
[0059] The AI entry point's interface rendering, interaction logic, and AI capability scheduling are all completed autonomously within its own process. It only uses host status signals transmitted from the desktop as the external basis for interface layout and status synchronization, without relying on the desktop process to provide any AI business support. The desktop host only acts as a state data source, not participating in the AI entry point's interface rendering, unaware of the AI business's operational status, or undertaking any AI capability management functions, truly achieving deep decoupling between the desktop main link and the AI capability link. The entire linkage is completed based solely on local communication without network access, without relying on any network environment. Even if the device is offline, it can still achieve normal desktop and AI entry point status synchronization and interface linkage, adapting to the complex operating environment of AI smart devices.
[0060] In one embodiment of the present invention, the specific process of "determining the AI entry interaction interface based on the desktop status data and completing the offline isolation linkage" described in step S150 can be further explained in conjunction with the following description.
[0061] As described in the following steps, based on the desktop status data, adjust and determine the window position, display level, visibility and lifecycle status of the AI entry interaction interface to complete the interface status synchronization; It's important to note that the interface state synchronization is a purely UI-level state alignment operation. It only adjusts the window attributes and display state of the AI entry interface based on the host state passed from the desktop, such as window size, lifecycle, and interaction progress. It does not involve any AI business logic processing, nor does it trigger connections or calls to the AI backend. Specifically, the window identifier is used for the hierarchical attachment and coordinate alignment of the AI entry interface and the desktop window, ensuring that the entry interface and the desktop are in the same window hierarchy. The sliding interaction progress controls the displacement, transparency, and animation progress of the AI entry, achieving smooth linkage between desktop sliding and entry activation / collapse. The lifecycle and visibility state are used to synchronize the resource loading, pausing, releasing, and show / hide logic of the AI entry, ensuring that the entry lifecycle remains coordinated with the desktop host. This synchronization mechanism is not limited to a specific entry UI form; it can adapt to desktop-attached entry types such as the negative one screen and side-sliding bars, as well as overlay entry types such as floating panels and global pop-ups, possessing broad scenario adaptability.
[0062] As described in the following steps, AI capability links can be managed independently within their own processes through the AI entry service; It's important to note that the management of the AI capability pipeline is entirely centralized within the AI entry service process. This encompasses the connection scheduling, status maintenance, anomaly handling, and switching / upgrade of all AI backend components, including cloud model channels, edge model runtime, local intelligent agent sandbox, and high-privilege system capability gateways. All operations are executed independently by the AI entry service; the desktop host does not store, perceive, or connect to any AI backend's addresses, keys, ports, model identifiers, or runtime status. Upgrades, restarts, switching, or failures of the AI capability pipeline are all handled and recovered within the AI entry process, without being transmitted to the desktop host process via communication links. This ensures the normal operation and core operations of the desktop main interface, guaranteeing the stability and high availability of the desktop main pipeline from an architectural perspective. Furthermore, the iterative optimization of the AI capability pipeline can be performed independently without synchronously modifying the desktop host program, significantly improving the evolution efficiency and deployment flexibility of AI capabilities.
[0063] As described in the following steps, the desktop host and AI entry point are isolated and linked in a network-free state by synchronizing the interface state and independently managing the AI capability link.
[0064] It's important to note that the desktop host and the AI capability link are completely isolated, with no direct or indirect network connections or business dependencies between them. The desktop and AI entry point only interact locally through structured host state signals, ensuring a smooth and consistent interactive experience. The desktop main link focuses on core desktop functions, while the AI entry point focuses on AI capability scheduling and interaction. Their responsibilities are clearly defined, and their operations do not interfere with each other. This architecture solves both the problems of AI backend anomalies dragging down the desktop main link and low iteration efficiency in traditional coupled solutions, and the problems of fragmented interaction and inability to synchronize states in completely independent solutions. It can support rapid iteration and flexible deployment of AI capabilities while ensuring the stability of the core desktop, fully adapting to the operational needs of AI smart devices.
[0065] In one embodiment of the present invention, the method further includes a disconnection state buffering and state replay step, comprising: When a local network communication link is detected to be disconnected, the desktop host caches the last generated structured host state signal and initiates a reconnection request according to the preset backoff strategy. After successfully reconnecting and rebuilding the local network-free communication link, the desktop host will replay the cached structured host state signals to the AI entry service; The AI gateway service restores the state of the AI gateway interface based on the replayed structured host state signals and independently reconstructs the AI capability chain. It should be noted that the design is intended for scenarios where the AI entry service operates independently and is prone to process termination due to system resource scheduling, version upgrades, abnormal failures, or unexpected disconnection of communication links. Without breaking the isolation boundary between the desktop and the AI capability link, it achieves automatic reconnection after disconnection and seamless recovery of the linkage status, effectively improving the operational reliability and environmental adaptability of the entire linkage solution.
[0066] When a communication link is detected to be disconnected, the desktop host only caches the last generated structured host state signal. The cached content is strictly limited to the desktop's own window, lifecycle, and interaction state. It does not save any AI session content, backend connection state, model identifiers, or system tool execution data. The caching operation does not break the isolation boundary between the two. Reconnection requests are executed using a preset backoff strategy, which gradually reduces the reconnection frequency by increasing the time interval to avoid frequent reconnections consuming system resources. The entire disconnection detection, state caching, and reconnection process is independently handled by the desktop's state bridging module, without interfering with the normal operation of the desktop's main interface. Abnormalities and restarts of the AI entry service will not be transmitted to the desktop's main link, ensuring the continuous availability of the desktop's core functions.
[0067] After successful reconnection, the cached host state signal is transmitted through the state replay mechanism. This eliminates the need for users to re-execute interactive operations such as swiping, calling up, or switching visibility. It provides the AI entry service with a complete and up-to-date desktop state, quickly restoring the window position, display hierarchy, visibility, and animation progress of the AI entry interface. This achieves seamless restoration of the linked state, effectively avoiding the loss of entry state and fragmented user interaction after service restarts. After restoring the interface state, the AI entry service independently rebuilds and restores the AI capability link. It can autonomously choose to reconnect to the original backend or switch to a backup AI channel based on the current operating environment. The entire AI link restoration process is executed within the AI entry process; the desktop host does not participate in, perceive, or interfere with the AI backend's reconnection and switching logic. Any anomalies or delays during the AI link restoration process will not negatively affect the operation of the main desktop link.
[0068] This disconnection caching and state replay mechanism works in deep collaboration with the core isolation and linkage architecture. Under normal circumstances, it achieves isolated linkage between the desktop and the AI entry point through standardized state encapsulation and local network-free communication. In abnormal scenarios, it achieves rapid recovery of the linkage state through state caching and replay. At the same time, it always maintains the independent control characteristics of the AI capability link, which not only ensures the operational stability of the desktop main entry point, but also takes into account the connection reliability and state consistency of the AI entry point. It can fully adapt to the complex operating environment of AI smart devices with multiple processes running independently, dynamic scheduling of system resources, and frequent iteration and upgrades of the AI backend.
[0069] As the device embodiment is basically similar to the method embodiment, the description is relatively simple, and relevant parts can be found in the description of the method embodiment.
[0070] Reference Figure 2 This illustration shows an embodiment of a desktop host and AI entry point isolation linkage device for network-free states, wherein the device implements the steps of the desktop host and AI entry point isolation linkage method described in any of the above claims: include: The acquisition module 210 is used to acquire a preset linkage contract and state encapsulation specification, and generate host state encapsulation rules and local communication channel parameters through the linkage contract and the state encapsulation specification. The structured host state signal module 220 is used to encapsulate the desktop running state into a structured host state signal according to the host state encapsulation rules. Local network-free communication link module 230 is used to establish a local network-free communication link based on the local communication channel parameters; Desktop status data module 240 is used to send the structured host status signal to the AI entry point through the local network-free communication link and parse it to obtain desktop status data. AI entry interaction interface module 250 is used to determine the AI entry interaction interface based on the desktop status data and complete the isolation linkage in the absence of network status.
[0071] In one embodiment of the present invention, the acquisition module 210 includes: The preset file acquisition submodule is used to acquire preset linkage contract files and status encapsulation specification files; the linkage contract only contains local service identifiers, message type definitions and communication protocol information; The local communication channel parameter submodule is used to parse the service identifier and communication protocol information in the linkage contract and generate local communication channel parameters. The host state encapsulation rules submodule is used to parse the state field definitions and data format requirements in the state encapsulation specification and generate host state encapsulation rules.
[0072] In one embodiment of the present invention, the structured host state signal module 220 includes: The runtime status acquisition submodule is used to collect the current window identifier, lifecycle status, visibility status, swipe interaction progress and back event of the desktop to obtain desktop runtime status data; The state standardization encapsulation submodule is used to perform field regularization and format standardization on the desktop running state data according to the host state encapsulation rules, and encapsulate it to generate a structured host state signal.
[0073] In one embodiment of the present invention, the local network-less communication link module 230 includes: The channel parameter parsing submodule is used to parse the local communication channel parameters and determine the target AI entry service identifier and inter-process communication protocol type; The service binding request submodule is used to initiate a local service binding request based on the target AI entry service identifier and establish a cross-process communication connection according to the inter-process communication protocol type. The communication link generation submodule is used to generate a local networkless communication link for transmitting structured host status signals after the communication connection verification is successful.
[0074] In one embodiment of the present invention, the desktop status data module 240 includes: The status signal sending submodule is used to send the structured host status signal to the AI entry service through the local network-free communication link; The signal verification and parsing submodule is used to perform format verification and protocol parsing on the received structured host state signals; The status field extraction submodule is used to extract the window identifier, lifecycle, visibility, and interaction progress fields from the signal to obtain desktop status data for interface synchronization.
[0075] In one embodiment of the present invention, the AI entry interaction interface module 250 includes: The interface state synchronization submodule is used to adjust and determine the window position, display level, visibility and lifecycle state of the AI entry interaction interface based on the desktop state data, so as to complete the interface state synchronization. The AI Link Independent Management Submodule is used to independently manage the AI capability link within its own process through the AI entry service; The isolated linkage execution submodule is used to achieve isolated linkage between the desktop host and the AI entry point in the absence of network by synchronizing the interface status and independently managing the AI capability link.
[0076] In one embodiment of the present invention, the device further includes a disconnection state buffer and state replay module, comprising: The disconnection cache and reconnection submodule is used to cache the last generated structured host state signal when the local network communication link is detected to be disconnected, and initiate a reconnection request according to the preset backoff strategy. The status signal replay submodule is used to replay the cached structured host status signals to the AI entry service after successful reconnection and reconstruction of the local network-free communication link. The State Link Recovery Submodule is used by the AI Entry Service to restore the state of the AI Entry Interaction Interface based on the replayed structured host state signals, and to independently rebuild the AI capability link.
[0077] Reference Figure 3 The diagram illustrates a computer device for implementing a method for isolating and linking a desktop host and an AI entry point in a network-free state, which may specifically include the following: The aforementioned computer device 1 is in the form of a general-purpose computing device. The components of the computer device 1 may include, but are not limited to: one or more processors or processing units 3, memory 8, and a bus 4 connecting different system components (including memory 8 and processing unit 3).
[0078] Bus 4 represents one or more of several bus architectures, including memory buses or memory controllers, peripheral buses, graphics acceleration ports, processors, or local buses using any of the various bus architectures. For example, these architectures include, but are not limited to, the Industry Standard Architecture (ISA) bus, the Micro Channel Architecture (MAC) bus, the Enhanced ISA bus, the Audio / Video Electronics Standards Association (VESA) local bus, and the Peripheral Component Interconnect (PCI) bus.
[0079] Computer device 1 typically includes a variety of computer system readable media. These media can be any available media that can be accessed by computer device 1, including volatile and non-volatile media, removable and non-removable media.
[0080] Memory 8 may include computer system readable media in the form of volatile memory, such as random access memory 9 and / or cache memory 10. Computer device 1 may further include other removable / non-removable, volatile / non-volatile computer system storage media. By way of example only, storage system 11 may be used to read and write non-removable, non-volatile magnetic media (commonly referred to as a "hard disk drive"). Although Figure 3 As not shown, a disk drive for reading and writing to a removable non-volatile disk (such as a "floppy disk") and an optical disk drive for reading and writing to a removable non-volatile optical disk (such as a CD-ROM, DVD-ROM, or other optical media) may be provided. In these cases, each drive may be connected to bus 4 via one or more data media interfaces. The memory may include at least one program product having a set (e.g., at least one) of program modules 13 configured to perform the functions of the embodiments of this application.
[0081] A program / utility 12 having a set (at least one) of program modules 13 may be stored, for example, in memory. Such program modules 13 include—but are not limited to—an operating system, one or more application programs, other program modules 13, and program data. Each or some combination of these examples may include an implementation of a network environment. Program modules 13 typically perform the functions and / or methods described in the embodiments of this application.
[0082] Computer device 1 can also communicate with one or more external devices 2 (e.g., keyboard, pointing device, monitor 7, camera, etc.), and with one or more devices that enable an operator to interact with computer device 1, and / or with any device that enables computer device 1 to communicate with one or more other computing devices (e.g., network card, modem, etc.). This communication can be performed through I / O interface 6. Furthermore, computer device 1 can communicate with one or more networks (e.g., local area network (LAN)), wide area network (WAN), and / or public networks (e.g., the Internet) through network adapter 5, and can also exchange data via medical data network protocols such as ICD protocol, DICOM protocol, and HL7 protocol. Figure 3 As shown, network adapter 5 communicates with other modules of computer device 1 via bus 4. It should be understood that, although... Figure 3Not shown, it can be combined with computer device 1 to use other hardware and / or software modules, including but not limited to: microcode, device drivers, redundant processing unit 3, external disk drive array, RAID system, tape drive and data backup storage system 11, etc.
[0083] The processing unit 3 executes various functional applications and data processing by running programs stored in memory 8, such as implementing a method for isolating and linking a desktop host and an AI entry point in a network-free state, as provided in the embodiments of this application.
[0084] That is, when the above-mentioned processing unit 3 executes the above-mentioned program, it achieves the following: obtaining the preset linkage contract and state encapsulation specification, and generating the host state encapsulation rule and local communication channel parameters through the linkage contract and the state encapsulation specification; The desktop running state is encapsulated into a structured host state signal according to the host state encapsulation rules. A local network-free communication link is established based on the local communication channel parameters; The structured host status signal is sent to the AI entry point via the local network-free communication link, and the desktop status data is obtained by parsing. The AI entry interaction interface is determined based on the desktop status data, and the linkage is completed in the absence of network isolation.
[0085] In the embodiments of this application, this application also provides a computer-readable storage medium storing a computer program thereon, which, when executed by a processor, implements a method for isolating and linking a desktop host and an AI entry point in a network-free state as provided in all embodiments of this application.
[0086] That is, when the program is executed by the processor, it implements the following: obtaining the preset linkage contract and state encapsulation specification, and generating the host state encapsulation rules and local communication channel parameters through the linkage contract and the state encapsulation specification; The desktop running state is encapsulated into a structured host state signal according to the host state encapsulation rules. A local network-free communication link is established based on the local communication channel parameters; The structured host status signal is sent to the AI entry point via the local network-free communication link, and the desktop status data is obtained by parsing. Based on the desktop status data, the AI entry interaction interface is determined, and the isolated linkage in the absence of network is completed.
[0087] Any combination of one or more computer-readable media may be used. A computer-readable medium can be a computer-readable signal medium or a computer-readable storage medium. A computer-readable storage medium can be, for example—but not limited to—an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples (a non-exhaustive list) of computer-readable storage media include: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, optical storage device, magnetic storage device, or any suitable combination thereof. In this document, a computer-readable storage medium can be any tangible medium that contains or stores a program that can be used by or in connection with an instruction execution system, apparatus, or device.
[0088] Computer-readable signal media may include data signals propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such propagated data signals may take various forms, including—but not limited to—electromagnetic signals, optical signals, or any suitable combination thereof. Computer-readable signal media may also be any computer-readable medium other than computer-readable storage media, capable of sending, propagating, or transmitting programs for use by or in connection with an instruction execution system, apparatus, or device.
[0089] Computer program code for performing the operations of this application can be written in one or more programming languages or a combination thereof. These programming languages include object-oriented programming languages—such as Java, Smalltalk, and C++—and conventional procedural programming languages—such as the "C" language or similar programming languages. The program code can be executed entirely on the operator's computer, partially on the operator's computer, as a standalone software package, partially on the operator's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the operator's computer via any type of network—including a local area network (LAN) or wide area network (WAN) that is compatible with medical network standards such as HL7 for HIS, RIS, and LIS systems—or it can be connected to an external computer (e.g., via the Internet using an Internet service provider). The various embodiments in this specification are described in a progressive manner, with each embodiment focusing on the differences from other embodiments. Similar or identical parts between embodiments can be referred to interchangeably.
[0090] Although preferred embodiments of the present application have been described, those skilled in the art, upon learning the basic inventive concept, can make other changes and modifications to these embodiments. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments as well as all changes and modifications falling within the scope of the embodiments of the present application.
[0091] Finally, it should be noted that in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or terminal device 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, article, or terminal device. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or terminal device that includes said element.
[0092] The above provides a detailed description of a method and apparatus for isolating and linking a desktop host and an AI entry point in a network-free state, as provided in this application. Specific examples have been used to illustrate the principles and implementation methods of this application. The descriptions of the above embodiments are only for the purpose of helping to understand the method and its core ideas. At the same time, for those skilled in the art, there will be changes in the specific implementation methods and application scope based on the ideas of this application. Therefore, the content of this specification should not be construed as a limitation of this application.
Claims
1. A method for isolated linkage between a desktop host and an AI entry point in a network-free state, characterized in that, Including the following steps: Obtain the preset linkage contract and state encapsulation specification, and generate host state encapsulation rules and local communication channel parameters through the linkage contract and the state encapsulation specification; The desktop running state is encapsulated into a structured host state signal according to the host state encapsulation rules. A local network-free communication link is established based on the local communication channel parameters; The structured host status signal is sent to the AI entry point via the local network-free communication link, and the desktop status data is obtained by parsing. Based on the desktop status data, the AI entry interaction interface is determined, and the isolated linkage in the absence of network is completed.
2. The method according to claim 1, characterized in that, The step of obtaining a preset linkage contract and state encapsulation specification, and generating host state encapsulation rules and local communication channel parameters through the linkage contract and state encapsulation specification, includes: Obtain the preset linkage contract file and state encapsulation specification file; the linkage contract only contains local service identifier, message type definition and communication protocol information; Parse the service identifier and communication protocol information in the linkage contract to generate local communication channel parameters; The state field definitions and data format requirements in the state encapsulation specification are parsed to generate host state encapsulation rules.
3. The method according to claim 1, characterized in that, The step of encapsulating the desktop running state into a structured host state signal according to the host state encapsulation rules includes: Collect the current window identifier, lifecycle state, visibility state, swipe interaction progress and back event on the desktop to obtain desktop running status data; Based on the host state encapsulation rules, the desktop running state data is regularized and formatted to encapsulate and generate a structured host state signal.
4. The method according to claim 1, characterized in that, The step of establishing a local network-less communication link based on the local communication channel parameters includes: The local communication channel parameters are analyzed to determine the target AI entry service identifier and inter-process communication protocol type; Initiate a local service binding request based on the target AI entry service identifier, and establish a cross-process communication connection according to the inter-process communication protocol type; After the communication connection is verified, a local networkless communication link is generated for transmitting structured host status signals.
5. The method according to claim 1, characterized in that, The step of sending the structured host state signal to the AI entry point via the local network-free communication link and parsing it to obtain desktop state data includes the following steps: The structured host status signal is sent to the AI entry service via the local network-free communication link. The AI entry service performs format verification and protocol parsing on the received structured host state signals; Extract the window identifier, lifecycle, visibility, and interaction progress fields from the signal to obtain desktop state data for interface synchronization.
6. The method according to claim 1, characterized in that, The step of determining the AI entry interaction interface based on the desktop status data and completing the offline isolation linkage step includes: Based on the desktop status data, adjust and determine the window position, display level, visibility and lifecycle status of the AI entry interaction interface to complete the interface status synchronization; The AI capability chain can be managed independently within its own process through the AI portal service; By synchronizing interface status and independently managing AI capability links, the desktop host and AI entry point can achieve isolated linkage in the absence of network access.
7. The method according to claim 1, characterized in that, The method further includes disconnection state caching and state replay steps, including: When a local network communication link is detected to be disconnected, the desktop host caches the last generated structured host state signal and initiates a reconnection request according to the preset backoff strategy; After successfully reconnecting and rebuilding the local network-free communication link, the desktop host will replay the cached structured host state signals to the AI entry service; The AI gateway service restores the state of the AI gateway interface based on the replayed structured host state signal and independently rebuilds the AI capability chain.
8. A device for isolating and linking a desktop host and an AI entry point in a network-free state, characterized in that, The device implements the steps of the method for isolating and linking desktop host and AI entry point in a network-free state as described in any one of claims 1-7: include: The acquisition module is used to acquire preset linkage contracts and state encapsulation specifications, and generate host state encapsulation rules and local communication channel parameters through the linkage contracts and state encapsulation specifications. The structured host state signal module is used to encapsulate the desktop running state into a structured host state signal according to the host state encapsulation rules. A local network-free communication link module is used to establish a local network-free communication link based on the local communication channel parameters. The desktop status data module is used to send the structured host status signal to the AI entry point through the local network-free communication link and parse it to obtain desktop status data; The AI entry interaction interface module is used to determine the AI entry interaction interface based on the desktop status data, and to complete the isolation linkage in the absence of network status.
9. A computer electronic device, characterized in that, It includes a processor, a memory, and a computer program stored in the memory and capable of running on the processor, wherein the computer program, when executed by the processor, implements the method as described in any one of claims 1 to 7.
10. A computer-readable storage medium, characterized in that, A computer program is stored on the computer-readable storage medium, which, when executed by a processor, implements the method as described in any one of claims 1 to 7.
