Intelligent driving system

Abstract

The invention discloses an intelligent driving system. The driving system is applied to the visual terminal and comprises a plurality of application programs and a central message bus. The plurality of application programs are respectively in communication connection with the central message bus, and the application programs publish operation information to the central message bus; at least one application program establishes subscription association with the central message bus so as to selectively subscribe operation information of other application programs. According to the technical scheme, application islands can be effectively avoided, the cooperation efficiency is improved, the system expansibility is improved, and the intelligence is improved.

Description

Technical Field

[0001] This invention relates to the field of computer technology, and more specifically to intelligent drive systems. Background Technology

[0002] In current operating systems, communication generally relies on the request-response model of Application Programming Interfaces (APIs). This model requires both communicating parties to pre-define each other's interface definitions and interaction logic, but it only enables one-to-one or limited one-to-many directed communication, easily leading to serious "application silos." This means different applications, services, and components struggle to collaborate efficiently. For example, changes in the state of a music playback application cannot be synchronized to the desktop background in real time. Furthermore, this request-response model limits the intelligent evolution of the desktop environment, failing to meet users' needs for personalized, contextualized, and seamlessly collaborative computing environments. In summary, this easily results in low application collaboration efficiency, poor system scalability, and insufficient intelligence. Summary of the Invention

[0003] To address the shortcomings of existing technologies, this invention provides an intelligent driving system that can effectively avoid application silos, improve collaborative efficiency, enhance system scalability, and increase intelligence.

[0004] This application provides an intelligent driving system, which is applied to a visual terminal, and the driving system includes:

[0005] Applications, wherein multiple applications are configured;

[0006] A central message bus, through which multiple applications communicate and connect, and through which the applications publish operation information;

[0007] At least one application establishes a subscription association with the central message bus to selectively subscribe to the operation information of other applications.

[0008] In one aspect, the drive system further includes:

[0009] The system service module is communicatively connected to the central message bus. The system service module publishes system messages to the central message bus, and the application selectively subscribes to the system messages. The system service module is also used to subscribe to messages from the central message bus.

[0010] In one aspect, the drive system further includes:

[0011] The user-defined component is communicatively connected to the central message bus. The user-defined component publishes custom information to the central message bus. The application selectively subscribes to the custom information. The user-defined component is also used to subscribe to messages from the central message bus.

[0012] In one aspect, the drive system further includes:

[0013] A dynamic wallpaper engine is communicatively connected to the central message bus. The dynamic wallpaper engine publishes wallpaper information to the central message bus and is also used to subscribe to messages from the central message bus. The dynamic wallpaper engine adjusts the desktop visual effects of the visualization terminal based on the information from the central message bus.

[0014] In one aspect, the drive system further includes:

[0015] The mode manager is used to customize and create at least one working mode. Each working mode is associated with corresponding dynamic wallpaper configuration parameters, notification parameters, application launch list and user-defined components.

[0016] The drive system also includes a scheduler, which is used to switch between different working modes according to preset scheduling rules.

[0017] In one aspect, the drive system further includes:

[0018] An environmental sensing module is used to sense changes in the logistics environment or digital environment of the visualization terminal in order to automatically switch working modes.

[0019] In one aspect, the drive system further includes:

[0020] A cross-platform synchronization module synchronizes data identity data based on user accounts. The data identity data includes at least working mode configuration data, application settings data, and user interface preference data. The data identity data is stored in the cloud.

[0021] In one aspect, the drive system further includes:

[0022] The application running module includes an application list parsing unit and a sandbox running environment. The application list parsing unit is used to parse the application's identity information, permission requirement information, and device support information. The sandbox running environment is used to provide an isolated running space for the application of the visualization terminal.

[0023] In one aspect, the drive system further includes:

[0024] A cross-device adaptation module adjusts the user interface presentation based on the device type of the visualization terminal to adapt to the corresponding visualization terminal.

[0025] In one aspect, the driving system also includes a contextualized semantic generation module, which is used to acquire calendar data. If a meeting is detected today, the desktop wallpaper automatically generates a meeting countdown display, and the display style matches the current desktop mode.

[0026] The beneficial effects of this invention are as follows: By constructing a communication architecture involving multiple applications and a central message bus, application silos are avoided. The central message bus acts as a unified communication hub, allowing multiple applications to interact via a publish-subscribe mechanism. This means applications do not need to pre-define the interface definitions and logic of other interacting parties; they only need to publish operation information to the bus. Other applications can selectively subscribe as needed, enabling flexible one-to-many or many-to-many communication and significantly improving application collaboration efficiency. When adding a new application, there is no need to redevelop adaptation interfaces for existing applications; simply connecting to the central message bus is sufficient to communicate with other applications, reducing system iteration and ecosystem building costs. Furthermore, the operation information of multiple applications is aggregated and flows in real-time through the central message bus, providing data interaction support for subsequent service responses and meeting users' needs for personalized and contextualized computing environments, thereby improving collaboration efficiency, system scalability, and intelligence. Attached Figure Description

[0027] To more clearly illustrate the specific embodiments of the present invention or the technical solutions in the prior art, the accompanying drawings used in the description of the specific embodiments or the prior art will be briefly introduced below. In all the drawings, similar elements or parts are generally identified by similar reference numerals. In the drawings, the elements or parts are not necessarily drawn to scale.

[0028] Figure 1 This is a schematic diagram of the functional structure of the intelligent drive system of this application. Detailed Implementation

[0029] The embodiments of the technical solution of the present invention will now be described in detail with reference to the accompanying drawings. These embodiments are merely illustrative of the technical solution of the present invention and are therefore intended to limit the scope of protection of the present invention.

[0030] It should be noted that, unless otherwise stated, the technical or scientific terms used in this application should have the ordinary meaning as understood by one of ordinary skill in the art to which this invention pertains.

[0031] like Figure 1As shown, this application provides an intelligent driving system 10, which is applied to a visual terminal. The driving system 10 includes an application program 100 and a central message bus 102.

[0032] Application 100 can be configured in multiple ways; these multiple applications 100 include music playback, document editing, desktop management, notification reminders, etc., and each application 100 undertakes different user services or system functions. Compared to the limited scenarios of a single or a few applications, the configuration of multiple applications 100 enables the system to cover a more comprehensive range of user needs.

[0033] Multiple applications 100 communicate with the central message bus 102, and each application 100 publishes operation information to the central message bus 102. On the one hand, the separate communication connection ensures that each application 100 can access the central message bus 102, eliminating the need to establish independent interfaces with other applications as in the traditional mode, thus significantly reducing the coupling between applications. On the other hand, the operation information published by each application 100 to the bus transforms the real-time dynamics of the application into a shareable information resource, which is then aggregated through the bus to form a system-level information pool. This not only solves the problem of one-way information transmission and the inability of multiple applications to obtain information synchronously in the traditional API mode, but also provides real-time and comprehensive data source support for subsequent multi-application collaboration. For example, playback status information published by a music application can be simultaneously obtained by multiple modules such as desktop background and notification components.

[0034] At least one application 100 establishes a subscription association with the central message bus 102 to selectively subscribe to the operation information of other applications 100. This subscription association mechanism breaks the limitation of traditional API models where information can only be obtained through targeted requests. Application 100 can proactively choose to subscribe to specific operation information published by other applications on the central message bus 102 according to its own functional needs, avoiding redundant transmission of irrelevant information and improving information interaction efficiency. Secondly, selective subscription gives application 100 a high degree of flexibility and autonomy. Different applications can customize their interaction logic based on their own service scenarios. For example, a notification application can subscribe to new message information from multiple social applications to achieve centralized reminders, while an office application can subscribe to schedule change information from a calendar application to achieve task linkage.

[0035] Moreover, this subscription mechanism supports one-to-many / many-to-many communication modes. Operation information published by a single application can be obtained by multiple subscribing applications simultaneously, solving the application silo problem caused by traditional API one-to-one directional communication. This allows application collaboration to shift from passive response to proactive adaptation, improving the system's collaborative efficiency and intelligence level.

[0036] In this embodiment, by constructing a communication architecture of multiple applications 100 and a central message bus 102, the situation of application silos is avoided. The central message bus 102 serves as a unified communication hub, and multiple applications 100 interact through a publish-subscribe mechanism. That is, applications 100 do not need to pre-define the interface definitions and logic of other interacting parties; they only need to publish operation information to the bus. Other applications 100 can selectively subscribe according to their needs, thereby achieving flexible one-to-many or many-to-many communication and significantly improving application collaboration efficiency. When adding a new application 100, there is no need to redevelop adaptation interfaces for existing applications; they only need to connect to the central message bus 102 to achieve communication with other applications, reducing system iteration and ecosystem building costs. In addition, the operation information of multiple applications 100 is aggregated and flows in real time through the central message bus 102, providing data interaction support for subsequent service responses, meeting users' needs for personalized and contextualized computing environments, thereby improving collaboration efficiency, system scalability, and intelligence.

[0037] In one embodiment of this application, the driving system 10 further includes a system service module 114, which is communicatively connected to the central message bus 102. The system service module 114 publishes system messages to the central message bus 102, and the application program 100 selectively subscribes to the system messages. The system service module 114 is also used to subscribe to messages from the central message bus 102. Bidirectional communication is achieved between the system service module 114 and the central message bus 102.

[0038] First, the system service module 114 undertakes the core tasks of the operating system at the bottom layer, such as device resource management, system status monitoring, and permission control. The connection between the system service module 114 and the central message bus 102 enables it to transmit key data of system operation to the application layer without going through traditional complex API interfaces. At the same time, it can also receive the interaction requirements of the application layer, building a bridge for bidirectional interaction between the system and the application 100, reducing the communication disconnect between the system service and the application 100 in the traditional architecture.

[0039] Secondly, the system service module 114 publishes system messages to the central message bus 102, providing application 100 with a real-time and comprehensive system-level data source. System messages cover core dynamics of system operation, such as processor load changes, network connection status switching, battery power fluctuations, and system time updates. This information flows uniformly through the central message bus 102, allowing application 100 to obtain system status without actively querying or calling underlying interfaces. For example, a power management application can subscribe to system messages to obtain real-time battery power data and trigger low battery reminders, while a document editing application can subscribe to network status messages to automatically enable local cache protection when the network is disconnected, significantly improving the application's responsiveness and adaptability to system dynamics.

[0040] Finally, application 100 can choose to subscribe to business-related system messages according to its own functional requirements. For example, a video application can subscribe only to processor load messages to adjust decoding performance without paying attention to other irrelevant system data. This reduces redundant information transmission and lowers the complexity of adapting to system capabilities during application development. On the other hand, system service module 114 can receive operation requests issued by application 100 by subscribing to bus messages and process and respond based on system rules. For example, when an office application issues a print job message, system service module 114 can subscribe to the message and call the printer driver to complete the printing operation, achieving seamless integration between application functions and underlying system capabilities, fundamentally improving the overall system's collaborative efficiency and service response speed.

[0041] System messages include environmental status messages and event messages. Environmental status messages mainly convey the current operating status and parameter data of the system and external environment, such as the terminal's processor load percentage, memory usage, remaining battery power, network connection type and speed, ambient light intensity, and terminal screen brightness and contrast. This provides a basis for environmental adaptation for each module. Application 100 can subscribe to environmental status messages to dynamically adjust its own functions to adapt to the current environment. For example, after a video application subscribes to processor load messages, it automatically reduces the video decoding resolution to ensure smooth operation under high load; after a dynamic wallpaper engine 101 subscribes to ambient light intensity messages, it synchronously adjusts the wallpaper brightness to match the ambient light, avoiding poor visibility in strong light or excessive brightness in low light; after a user-defined component 115 subscribes to battery power messages, it automatically hides high-power dynamic elements when the battery is low, helping the terminal save power.

[0042] Event messages primarily transmit information about specific events and operations occurring in the system or external environment, such as system startup, shutdown, hibernation, application 100 installation, uninstallation, and crashes, device hardware activation and deactivation, network connection disconnection and reconnection, battery charging start and end, and user login and logout. Event messages provide immediate response trigger signals for each module. Application 100 can subscribe to event messages to respond promptly to critical system events.

[0043] In one embodiment of this application, the driving system 10 further includes a user-defined component 115, which is communicatively connected to the central message bus 102. The user-defined component 115 publishes custom information to the central message bus 102, and the application 100 selectively subscribes to the custom information. The user-defined component 115 is also used to subscribe to messages from the central message bus 102. Through bidirectional communication with the central message bus 102, the user-defined component 115 overcomes the problem of fixed user interaction components in traditional operating systems, which cannot flexibly adapt to individual needs.

[0044] Specifically, the user-defined component 115 is created or configured by the user according to their own usage habits. Its connection with the central message bus 102 frees it from the limitations of traditional fixed components, which have single functions and cannot be linked. It can not only transform the user's personalized needs into information that can be circulated, but also receive dynamic data from the system and applications, becoming a personalized interactive node that connects the user's subjective needs with the system's objective functions.

[0045] Secondly, user-defined components 115 publish custom information to the central message bus 102, providing application 100 with personalized data sources tailored to individual user scenarios. Custom information includes user-defined content or operation commands. For example, a user-created commuting reminder component can publish daily 7:30 pm commuting preparation time information; a personal health data component can publish user-defined statistical data such as real-time heart rate and steps; and a quick operation component can publish commands to open office application groups with one click. This information flows through the central message bus 102, allowing application 100 to accurately capture users' personalized needs. For example, after a calendar application subscribes to commuting reminder information, it can synchronously generate schedule annotations; after a health application subscribes to heart rate data information, it can assist in generating health reports, enabling the system's functions to shift from generalized services to personalized adaptation.

[0046] Furthermore, application 100 can independently select and subscribe to custom information related to user needs based on service scenarios, avoiding information redundancy while accurately responding to personalized user operations and reducing the adaptation cost between the application and user needs. On the other hand, user-defined components 115 can receive dynamic data from application 100 or system services by subscribing to bus messages, enabling on-demand adjustments. For example, after a custom weather component subscribes to real-time weather messages published by system services, it can automatically update the weather display content; after a custom to-do component subscribes to task completion messages published by document applications, it can automatically mark the corresponding items in the to-do list, allowing user-defined components 115 to be upgraded from static display tools to dynamically responsive personalized interactive hubs, meeting users' needs for personalized and contextualized desktop environments.

[0047] In one embodiment of this application, the driving system 10 further includes a dynamic wallpaper engine 101, which is communicatively connected to the central message bus 102. The dynamic wallpaper engine 101 publishes wallpaper information to the central message bus 102 and is also used to subscribe to messages from the central message bus 102. The dynamic wallpaper engine 101 adjusts the desktop visual effects of the visualization terminal according to the information from the central message bus 102. Through bidirectional communication with the central message bus 102, the dynamic wallpaper engine 101 breaks through the limitations of traditional static wallpapers, which only serve a decorative function and are disconnected from the system and applications, and constructs an intelligent desktop interaction system that drives visuals and provides visual feedback.

[0048] First, traditional desktop wallpapers exist only as independent visual elements and cannot be linked with system status or application operations; however, the dynamic wallpaper engine 101, by connecting to the central message bus 102, can receive multi-source information from system services, applications 100, and user-defined components 115 on one hand, and feed back its own wallpaper configuration and status data to the central message bus 102 on the other hand, making the wallpaper a node for system information flow and providing an information input and output channel for the dynamic adjustment of subsequent visual effects.

[0049] Secondly, the dynamic wallpaper engine 101 publishes wallpaper information to the central message bus 102, providing desktop visual configuration and status data to other modules of the system, enabling multi-module collaborative adaptation. Wallpaper information includes the current visual parameters of the wallpaper (such as main color tone, particle animation rate, and dynamic element density) and functional status (such as whether it is in interactive mode or whether special effects degradation is enabled). For example, when a user manually adjusts the wallpaper brightness, the dynamic wallpaper engine 101 can publish information to the central message bus 102 that the wallpaper brightness has been adjusted to 80%. After the system service module 114 subscribes to this information, it can synchronously optimize the screen backlight parameters. After the user-defined component 115 subscribes to this information, it can adjust its own display contrast, achieving consistent adaptation of the desktop visuals with the system and components, avoiding the problem of the wallpaper's visual style being disconnected from other modules.

[0050] Finally, the dynamic wallpaper engine 101 subscribes to information from various sources on the central message bus 102, such as processor high load and network outage messages from system services, music playback rhythm and video progress messages from application 100, and commuting reminder and health data messages from user-defined components 115, transforming abstract data into intuitive visual changes. For example, when receiving a music playback rhythm message, it synchronously adjusts the particle animation rate to match the music beat; when receiving a processor high load message, it reduces the density of dynamic elements and switches the main color to a warning color; when receiving a commuting reminder message, it generates a lightweight dynamic notification icon in the corner of the wallpaper. This information-driven visual model transforms the desktop wallpaper from a passive display element into an intelligent interactive interface that reflects system status, application operations, and user needs in real time, enhancing the user's personalized and contextualized experience of the desktop environment.

[0051] In one embodiment of this application, the driving system 10 further includes a mode manager 104, which is used to customize and create at least one working mode. Each working mode is associated with corresponding dynamic wallpaper configuration parameters, notification parameters, application 100 launch list and user-defined component 115. The mode manager 104 transforms diverse user scenarios into working modes that can be called with one click, reducing the tedious problem of manually adjusting multiple settings such as wallpaper, notifications, and applications.

[0052] First, users can create at least one custom work mode, giving them a high degree of autonomy in scenario-based customization. Users can create their own exclusive work modes based on their high-frequency usage scenarios, without being limited by the system's preset fixed modes. This allows the desktop environment to accurately match individual usage habits. For example, business users can create a meeting mode, and students can create a study mode, meeting the personalized scenario needs of different groups of people.

[0053] Secondly, each working mode is associated with dynamic wallpaper configuration parameters, notification parameters, application launch list 100, and user-defined components 115, achieving integrated packaging of scenario-based settings. By binding multi-dimensional configurations to working modes, users do not need to adjust each setting individually when switching modes.

[0054] Dynamic wallpaper configuration parameters ensure visual style and scene adaptation. Notification parameters reduce scene interference; the application launch list improves scene switching efficiency; and user-defined components enhance scene functionality adaptation. This design, with one mode corresponding to one complete configuration, upgrades the desktop environment from fragmented settings to a scene-integrated solution, significantly reducing user operation costs.

[0055] The drive system 10 also includes a scheduler 103, which is used to switch between different working modes according to preset scheduling rules. The scheduler 103 triggers mode switching based on preset rules, reducing manual operation by the user and allowing the desktop environment to shift from passive adjustment to active adaptation to the scenario.

[0056] Specifically, the system switches between different working modes based on preset scheduling rules, achieving automated and intelligent mode switching. These preset scheduling rules can cover multiple dimensions, including time and scenario triggers. For example, the time dimension matches users' fixed schedules; the event dimension matches changes in the scenario environment.

[0057] With rule-triggered automated switching, users do not need to manually operate when the scene changes. For example, after commuting to the company, the system automatically switches from commuting mode to office mode, improving ease of use.

[0058] Secondly, the scheduler 103 provides support for seamless transitions between multiple scenarios. During the process of users frequently switching scenarios throughout the day, the scheduler 103 can achieve smooth mode switching based on preset rules, ensuring that the desktop environment is always adapted to the current scenario. For example, it can automatically switch from office mode to leisure mode during lunch break and automatically switch back to office mode after lunch break, avoiding settings gaps during scenario transitions and making the desktop environment a dynamically adaptable system that fits the user's behavior trajectory.

[0059] In summary, the mode manager 104 and the scheduler 103 form a collaborative closed loop from scene customization to automatic switching. The mode manager 104 is responsible for defining scene configurations, and the scheduler 103 is responsible for triggering scene switching. Together, they solve the problems of cumbersome scene settings and passive switching in traditional operating systems, providing users with a customized, automated, and scene-based desktop environment.

[0060] In one embodiment of this application, the driving system 10 further includes an environmental perception module 109. The environmental perception module 109 is used to perceive changes in the logistics environment or digital environment of the visualization terminal in order to automatically switch the working mode. As the core of the scenario triggering for automatic switching of the working mode in the driving system 10, the environmental perception module 109 breaks through the limitations of traditional mode switching that relies on manual operation or fixed time rules by actively perceiving changes in the physical and digital environment in which the visualization terminal is located. It constructs an intelligent triggering mechanism that dynamically adapts to the environment, upgrading the working mode switching from a passive response to an active adaptation to the environment.

[0061] The environmental perception module 109 can sense changes in the physical environment of the visualization terminal, enabling accurate capture of real-world scenes. These changes encompass the objective conditions of the terminal's location, such as ambient light intensity, temperature and humidity, geographical location, and device connectivity. For example, if the module senses a sudden drop in ambient light intensity or the terminal connecting to home Wi-Fi, these physical environmental signals can serve as crucial evidence for determining the user's current scene, reducing the problem of relying solely on time or manual operation to accurately match real-world scenarios.

[0062] Secondly, the environmental perception module 109 can also sense changes in the digital environment of the visual terminal to dynamically capture the system's operating status and application interactions. Changes in the digital environment encompass the terminal's internal operating data and application dynamics, such as system resource load, application activity status, network status, and battery level. For example, if the environmental perception module 109 senses multiple office applications operating simultaneously or a high system CPU load, it can determine that the user is in an office scenario; if it senses video software running and the network is high-speed WiFi, it can determine that the user is in an entertainment scenario. These digital environmental signals further enhance the accuracy of scenario judgment, making mode switching more closely match the user's actual usage behavior.

[0063] The environmental sensing module 109 also significantly reduces user operating costs. It converts captured changes in the physical / digital environment into mode-switching trigger signals, automatically matching the corresponding working mode without manual user intervention. For example, if it senses low ambient light and is connected to home Wi-Fi, it automatically switches to a nighttime relaxation mode, such as associating with a low-brightness wallpaper, muting notifications, and launching video / music applications; if it senses the user's location is at work and office software is running, it automatically switches to an office mode, such as associating with a high-contrast wallpaper, providing only work notifications, and launching the office application list; if it senses the battery level is below 15% and there is no charging connection, it automatically switches to a power-saving mode, such as associating with a low-effect wallpaper, disabling unnecessary notifications, and pausing high-power applications. This automatic adaptation mechanism, where the mode changes with the environment, reduces the adaptation lag problem where the mode remains unchanged even when the scene changes, ensuring the desktop environment always closely matches the user's physical and digital environment, maximizing ease of use and scene adaptation efficiency.

[0064] In one embodiment of this application, the driving system 10 further includes a cross-device synchronization module 107. The cross-device synchronization module 107 synchronizes data identity data based on user accounts. The data identity data includes at least configuration data for working modes, application settings data, and user interface preference data, and the data identity data is stored in the cloud. Through user account association and data synchronization stored in the cloud, a cross-device collaboration solution with one person, one identity, and consistent experience across multiple devices is constructed. Digital identity data is integrated into the cloud based on the user account, and then adapted to other terminals from the cloud.

[0065] Specifically, based on user account synchronization data and identity data, personalized configurations are linked to an identity, deeply connecting user settings to their personal accounts rather than being dependent on a single device. The identity data integrates core personalized settings within the desktop environment into a unified digital identity. This includes work mode configuration data covering all user-defined work modes and their associated parameters such as wallpapers, notifications, and application lists; application settings data including personalized parameters for each application; and user interface preference data involving visual and interactive settings such as desktop layout, icon styles, and component positions.

[0066] Secondly, storing identity data in the cloud ensures data security and durability. Even if a user replaces a new device or the original device malfunctions, they can retrieve their digital identity data from the cloud simply by logging into their corresponding user account, avoiding the need for repeated reconstruction of personalized configurations. At the same time, cloud storage supports real-time access and data updates from multiple devices. Modified working modes, application settings, and other data on one device can be synchronized to other related devices via the cloud, ensuring the consistency of digital identities across all devices.

[0067] The cross-device synchronization module 107 enables a seamless experience of carrying your digital identity data across devices. When a user logs into their personal account on a new device, the cross-device synchronization module 107 automatically retrieves and loads their digital identity data from the cloud: on a computer, it synchronously loads an office mode with a multi-application launch list and a desktop layout adapted for large screens; on a mobile phone, it synchronously loads a simplified commuting mode and touch-optimized interface preferences; on public terminals, it synchronously loads a temporary mode and basic application settings that meet privacy protection requirements. This allows users to quickly obtain a desktop environment tailored to their personal habits on different devices without having to repeatedly adjust configurations.

[0068] In one embodiment of this application, the driving system 10 further includes an application running module 105, which comprises an application manifest parsing unit and a sandbox running environment. The application manifest parsing unit is used to parse the identity information, permission requirement information, and device support information of the application 100, while the sandbox running environment is used to provide an isolated running space for the application 100 on the visual terminal. This constructs an application security operation system from two dimensions: pre-operation verification and running environment isolation. The application manifest parsing unit, as the access review node for application access to the system, standardizes application access from the source by parsing the identity information, permission requirement information, and device support information of the application 100, thus solving the problems of disordered application access and poor compatibility. The sandbox running environment, as a security isolation barrier for application operation, provides each application 100 with an independent running space isolated from the system's underlying resources and other applications, restricting disordered access to the system's core resources. This prevents individual application crashes from affecting the stability of the entire system and avoids malicious applications stealing data from other applications or damaging the system environment, ensuring application security from the operational stage. The manifest parsing unit and the sandbox running environment work together; the former ensures compliant application access, while the latter ensures secure application operation.

[0069] In one embodiment of this application, the driving system 10 further includes a cross-device adaptation module 106. The cross-device adaptation module 106 adjusts the user interface presentation according to the device type of the visualization terminal to adapt to the corresponding visualization terminal. The cross-device adaptation module 106 is the core of the intelligent desktop driving system 10 to achieve a consistent experience across multiple terminals. By actively adjusting the user interface presentation, the cross-device adaptation module 106 ensures that a compatible and convenient user experience can be provided on different types of visualization terminals.

[0070] In practical applications, the cross-device adaptation module 106 first identifies the type of visual terminal device currently running the system, such as desktop computers, smartphones, and tablets. Then, based on the hardware characteristics and usage scenarios of different devices, it adjusts the presentation of the user interface accordingly. For example, on desktop computers, which have large screen displays and keyboard and mouse interaction, the interface retains the classic combination of windowed layout, taskbar, and start menu, adapting to the precision of keyboard and mouse operation and the multitasking needs of large screens. On smartphones, which have small touch screens, the interface switches to an immersive full-screen wallpaper layout, simplifying redundant elements and optimizing touch interaction logic, such as swiping up from the bottom to bring up the taskbar or start menu, adapting to one-handed touch operation and the space limitations of small screens. On tablets, which have both large screen and touch features, the interface can also flexibly balance windowed and touch-optimized designs, taking into account both multitasking and touch convenience. By recognizing the device type and adapting the interface, the cross-device adaptation module 106 effectively solves the problem of rigid interfaces and incompatible interactions of traditional desktop systems on different terminals. This allows users to switch between different visual terminals without having to readjust the interface operation and always get a display that fits the current visual terminal.

[0071] In one embodiment of this application, the status information of the visualization terminal includes processor load data, network connection status data, and system time data; the operation information includes music playback status data and video playback progress data; and the visual effects include particle animation rate, main color tone, and dynamic element display density.

[0072] In the intelligent desktop driver system 10 of this embodiment of the application, the status information of the visual terminal, the operation information of the application 100 and the desktop visual effects are precisely corresponded through the linkage mechanism of the central message bus 102 and the dynamic wallpaper engine 101, so as to realize the real-time response of the desktop environment to the device operation and application operation.

[0073] The visual terminal's status information specifically includes processor load data, network connection status data, and system time data. Processor load data reflects the terminal's computing resource usage, such as high load or low load. Network connection status data reflects the terminal's network connection status, such as connected, disconnected, and network speed. System time data provides the terminal's current time information. Application 100's operation information focuses on music playback status data and video playback progress data, such as play, pause, music rhythm, playback duration, and progress percentage.

[0074] Desktop visual effects, including particle animation rate, primary color tone, and dynamic element display density, are the specific presentation forms in which the dynamic wallpaper engine 101 transforms the aforementioned information into intuitive visual changes. For example, when the central message bus 102 transmits high-load status information for the processor, the dynamic wallpaper engine 101 can increase the particle animation rate and switch the primary color tone to an alert color; when transmitting music playback operation information, it adjusts the particle animation rate according to the music rhythm; when transmitting network outage status information, it reduces the dynamic element display density and switches the primary color tone to an alert color. By clearly defining the correspondence between information types and visual effects, the desktop wallpaper can accurately reflect the dynamics of device operation and application operation, further enhancing the intelligence and interactivity of the desktop environment.

[0075] In one embodiment of this application, the driving system 10 further includes an identification module 108 and an environmental perception module 109.

[0076] The recognition module 108 is used to identify the user's level of focus. If deep focus is detected, the live wallpaper automatically reduces the intensity of its effects; if the user is distracted, the wallpaper triggers an interactive reminder. The recognition module 108 is mainly used to identify the user's level of focus and to make targeted adjustments to the live wallpaper effects based on the recognition results. When the recognition module 108 determines that the user is in a state of deep focus by analyzing user operation behavior, such as the frequency of keyboard and mouse operations and the duration of screen viewing, it will trigger the live wallpaper to automatically reduce the intensity of its effects, reducing visual interference such as particle animations and color changes, creating a low-interference desktop environment for the user. When the recognition module 108 detects that the user is exhibiting distracting behavior, such as frequently switching windows or not operating for a long time, it will trigger a lightweight interactive reminder through the wallpaper, such as a focus prompt icon composed of dynamic elements or gentle color flashing, to help the user return to focus without interrupting the user's current state, upgrading the desktop wallpaper from passive display to actively adapting to the user's state.

[0077] The environmental sensing module 109 is used to acquire the ambient light intensity and screen brightness of the visualization terminal, automatically adjusting the brightness and contrast based on the ambient light intensity, or generating corresponding visual elements based on the local ambient temperature and humidity. The environmental sensing module 109 focuses on adapting the desktop visuals to the external environment. On one hand, it acquires data on the ambient light intensity and screen brightness of the visualization terminal, automatically adjusting the brightness and contrast of the desktop wallpaper based on the intensity of the ambient light. For example, in strong light environments, it increases the wallpaper brightness and contrast to prevent screen content from being obscured by glare; in low light environments, it reduces brightness and switches to a softer color tone to reduce eye strain. On the other hand, the environmental sensing module 109 acquires local ambient temperature and humidity data and converts it into corresponding visual elements for the desktop wallpaper. For example, in high humidity, the wallpaper displays a slightly hazy effect; in low humidity, it presents dynamic icons related to dryness reminders. This allows the desktop wallpaper to not only adapt to ambient light to ensure visual comfort but also intuitively convey environmental information, further enriching the intelligent interaction of the desktop.

[0078] In one embodiment of this application, the driving system 10 further includes a contextualized semantic generation module 110. This module 110 acquires calendar data. If a meeting is detected today, the desktop wallpaper automatically generates a meeting countdown display, and the display style matches the current desktop mode. The contextualized semantic generation module 110 proactively conveys key information related to the user's schedule. The environment perception module 109 first acquires calendar data from the visual terminal, identifies user-related schedules through data parsing, and automatically triggers the desktop wallpaper to generate a meeting countdown display when a key schedule such as a meeting is detected today. The countdown content visually presents the remaining meeting time, such as 2 hours and 15 minutes until the 14:30 project meeting. The countdown display style matches the current work mode. For example, in work mode, the countdown uses a simple blue font and a narrow progress bar to avoid interfering with work focus; in leisure mode, the countdown can be paired with soft warm colors and simple icons, balancing information delivery and visual comfort. Through the acquisition of key information from schedule data and the design of patterned visual presentation, the scenario-based semantic generation module 110 allows users to keep track of meeting times in real time simply by looking at the desktop wallpaper, without having to manually open the calendar app. This not only improves the convenience of obtaining schedule information but also makes the desktop environment more in line with the user's actual usage scenario.

[0079] In one embodiment of this application, the driving system 10 further includes a visual rule editor 111. The visual rule editor 111 provides a drag-and-drop interface for users to independently associate desktop trigger conditions and special effects. By providing a drag-and-drop interface, the visual rule editor 111 reduces the difficulty for users to configure the association between desktop trigger conditions and special effects, allowing non-technical users to flexibly customize desktop interaction rules to meet their own needs. In actual use, users do not need to write code; they can simply drag and drop elements in the interface to complete the association configuration. For example, the trigger condition can be edited to receive a new WeChat message and a special effect, with a green light flashing in the lower right corner of the wallpaper for drag-and-drop association. Subsequently, when a new WeChat message is detected, the desktop wallpaper will automatically execute the flashing light effect. Another example is associating the trigger condition, such as the computer battery level being below 20%, with a special effect, with an orange battery level reminder progress bar displayed at the bottom of the wallpaper, providing an intuitive visual prompt when the battery is low. This drag-and-drop design allows users to define desktop interactions according to their own usage habits, transforming the desktop environment from a system-dominated fixed mode to a user-dominated personalized interaction, further enhancing the convenience and personalization capabilities of the smart desktop.

[0080] In one embodiment of this application, the driving system 10 further includes a preference analysis module 112. The preference analysis module 112 acquires historical user operation data and dynamically optimizes scheduling rules based on the historical operation data. The preference analysis module 112 dynamically optimizes the scheduling rules based on the user's historical operation data, making the switching of working modes more in line with the user's personalized usage habits and reducing manual adjustment operations.

[0081] The general preference analysis module 112 continuously collects and organizes historical operation data of users on the visual terminal. This data includes key information such as the time points when users manually switch working modes, mode selection preferences in specific scenarios, and adjustment records of automatic system scheduling. Subsequently, this historical operation data is analyzed to extract user usage patterns and preference characteristics. For example, it identifies potential habits such as users manually switching from working mode to entertainment mode after 6 PM every Friday, and users preferring to use low-brightness reading mode on rainy days. Based on these analysis results, the preference analysis module 112 dynamically optimizes the preset scheduling rules of the scheduler 103, such as automatically setting 6 PM every Friday as the trigger time for switching from working mode to entertainment mode, or adjusting the automatic trigger priority of reading mode when rainy weather is detected. This transforms the switching of working modes from a uniform logic preset by the system to a personalized adaptation that fits user habits, further improving the convenience of using the smart desktop and the fit of the user experience.

[0082] In addition, in this application, users can set priorities for configured rules. When multiple rules are triggered simultaneously, the system executes them according to priority. For example, the driver system 10 of this application is equipped with a rule conflict detection module. If a logical conflict is detected between user-configured rules, such as the main color turning red when the CPU is under high load versus the main color turning blue when the CPU is under high load, the editor will provide real-time prompts for the conflict points and offer modification suggestions to improve the rationality of rule configuration.

[0083] Secondly, the driving system 10 of this application also includes an effect evaluation module 113, which records user behavior feedback after each mode switch or wallpaper effect adjustment; and dynamically optimizes strategies based on feedback data. For example, if it is detected that 80% of users still manually open entertainment apps after automatically switching working modes, the scheduler 103 automatically adjusts the rules; if the number of times users manually adjust screen brightness decreases by 60% after using the wallpaper eye protection mode, the mode is automatically set as the default low-light environment configuration.

[0084] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, and not to limit them. Although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some or all of the technical features therein. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present invention, and they should all be covered within the scope of the claims and specification of the present invention.

Claims

1. A drive system, characterized in that, The driving system is applied to the visualization terminal, and the driving system includes: Applications, wherein multiple applications are configured; A central message bus, through which multiple applications communicate and connect, and through which the applications publish operation information; At least one application establishes a subscription association with the central message bus to selectively subscribe to the operation information of other applications.

2. The drive system according to claim 1, characterized in that, The drive system also includes: The system service module is communicatively connected to the central message bus. The system service module publishes system messages to the central message bus, and the application selectively subscribes to the system messages. The system service module is also used to subscribe to messages from the central message bus.

3. The drive system according to claim 1, characterized in that, The drive system also includes: The user-defined component is communicatively connected to the central message bus. The user-defined component publishes custom information to the central message bus. The application selectively subscribes to the custom information. The user-defined component is also used to subscribe to messages from the central message bus.

4. The drive system according to claim 3, characterized in that, The drive system also includes: A dynamic wallpaper engine is communicatively connected to the central message bus. The dynamic wallpaper engine publishes wallpaper information to the central message bus and is also used to subscribe to messages from the central message bus. The dynamic wallpaper engine adjusts the desktop visual effects of the visualization terminal based on the information from the central message bus.

5. The drive system according to claim 4, characterized in that, The drive system also includes: The mode manager is used to customize and create at least one working mode. Each working mode is associated with corresponding dynamic wallpaper configuration parameters, notification parameters, application launch list and user-defined components. The drive system also includes a scheduler, which is used to switch between different working modes according to preset scheduling rules.

6. The drive system according to claim 5, characterized in that, The drive system also includes: An environmental sensing module is used to sense changes in the logistics environment or digital environment of the visualization terminal in order to automatically switch working modes.

7. The drive system according to claim 1, characterized in that, The drive system also includes: A cross-platform synchronization module synchronizes data identity data based on user accounts. The data identity data includes at least working mode configuration data, application settings data, and user interface preference data. The data identity data is stored in the cloud.

8. The drive system according to claim 1, characterized in that, The drive system also includes: The application running module includes an application list parsing unit and a sandbox running environment. The application list parsing unit is used to parse the application's identity information, permission requirement information, and device support information. The sandbox running environment is used to provide an isolated running space for the application of the visualization terminal.

9. The drive system according to claim 1, characterized in that, The drive system also includes: A cross-device adaptation module adjusts the user interface presentation based on the device type of the visualization terminal to adapt to the corresponding visualization terminal.

10. The drive system according to claim 1, characterized in that, The driving system also includes a contextual semantic generation module, which is used to acquire calendar data. If a meeting is detected today, the desktop wallpaper will automatically generate a meeting countdown and the display style will match the current desktop mode.

Images