Intelligent store music management system based on cloud control

Abstract

This invention provides a cloud-based intelligent store music management system, comprising a cloud management platform and client software deployed on terminals in various stores. The cloud management platform includes: a device and store management module, a media resource library module, a playback strategy engine module, a command issuance and data synchronization module, and a monitoring and log analysis module. The client software includes: a system service masquerading module, a multi-start and protection module, an identity identification and management module, an audio device exclusivity and control module, and a network communication module. This invention addresses the problems of poor stability, susceptibility to human and software interference, and inability to achieve efficient centralized management and refined scheduling in existing store music playback systems. It provides an intelligent store music management system that ensures continuous online playback service, resists local interference, and supports unified cloud control and intelligent scheduling.

Description

Technical Field

[0001] This invention relates to the field of agricultural information technology, and in particular to a cloud-based intelligent store music management system. Background Technology

[0002] With the rise of new retail and experiential consumption, ambient music in stores is becoming increasingly important as a key element in shaping brand image, influencing customer emotions, and increasing dwell time. Unified background music management can strengthen the overall cohesiveness of a chain brand, while intelligent music scheduling can dynamically adjust the atmosphere based on time of day, customer flow, and promotional activities, thereby improving operational efficiency and customer experience.

[0003] However, existing in-store music playback solutions mostly use consumer-grade player software or simple hardware playback devices, which have revealed many technical bottlenecks in actual large-scale deployment and long-term operation and maintenance, as follows: (1) Ordinary media player software runs on the store's local computer. Employees can easily close the software, adjust the volume, or switch to other audio sources, causing background music playback to be interrupted or deviate from the uniform standard. After the computer is restarted, the media player software often fails to start automatically, requiring manual intervention, which increases the management burden.

[0004] (2) The audio focus grabbing or system prompts generated by instant messaging software, web browsers, other media players, etc. that are always running on the store's computer will seriously interfere with the pure playback of background music, and may even cause the player process to be suspended or terminated by the operating system's resource management mechanism.

[0005] (3) The existing solution lacks a protection mechanism for the player client process itself. Once the client crashes and exits due to program abnormalities, system resource shortages, or other reasons, it cannot be automatically recovered, resulting in long-term playback interruptions.

[0006] (4) The playback systems of each store are independent of each other, and the headquarters cannot monitor the music playback status of each store in real time. Music content updates require store staff to manually copy or download music using USB drives, which is inefficient and prone to errors.

[0007] Therefore, there is an urgent need to develop an intelligent store music management system that can overcome the above-mentioned defects, has high reliability, strong anti-interference capabilities, and supports centralized cloud management and intelligent scheduling. Summary of the Invention

[0008] To address at least one of the technical problems mentioned above, this invention provides a cloud-based intelligent store music management system. Through an innovative client-side local protection mechanism, a multi-identity system, and a cloud-coordinated audio control strategy, it achieves high availability, centralized management, and intelligent playback of music playback services.

[0009] The present invention solves the technical problem by adopting the following technical solution: A cloud-based intelligent store music management system includes: a cloud management platform and client software deployed on terminals in each store; wherein: The cloud management platform includes: The device and store management module is used to register and manage terminals in each store, and generate a unique client identity for each terminal; The media library module is used to store and manage audio files; The playback strategy engine module is used to create and manage playback strategy templates; The instruction issuance and data synchronization module is used to issue the playback strategy template, audio file list and configuration instructions to one or more designated store terminals through a secure communication link; The monitoring and log analysis module is used to receive the operational status information reported by each store terminal and to visualize and issue alarms. The client software includes: The system service masquerading module is used to encapsulate the core playback and control logic of the client software into an operating system service process, and configure the registration name and description information of the service process as strings similar to those of the core components of the operating system, and its binary file is stored in the system protection directory. The multi-startup and protection module provides at least two independent startup triggering and process protection mechanisms to ensure that the service process can be automatically recovered after abnormal termination. The identity identification and management module is used to generate, encrypt, store, and dynamically verify the client identity identifier, and supports cloud-based identity recovery based on hardware fingerprints; The audio device exclusive control module runs in the service process and is used to forcibly lock the system volume through the underlying audio application programming interface, manage the audio focus of other audio processes, and monitor the status of audio output devices. The network communication module is used for encrypted communication with the cloud management platform, receiving instructions and resource lists, and reporting the client's operating status. The network communication module uses a WebSocket long-lived connection with the cloud management platform for heartbeat information reporting and real-time instruction reception, and employs a TLS-based encrypted hypertext transfer security protocol for file downloads, supporting breakpoint resume functionality.

[0010] Furthermore, the multi-startup and guardian module provides at least two independent startup triggering and process guardian mechanisms, including at least two of the following: System service auto-start mechanism: Service processes are automatically started by the service control manager when the operating system starts, and are set to automatic or automatic delayed start mode; Registry startup daemon mechanism: A daemon startup entry is created in the system registry startup items. This daemon startup entry points to a daemon script. The daemon script is used to periodically check the running status of the service process and perform a service restart operation when a process is detected to be missing. Scheduled task triggering mechanism: A scheduled task with the highest privileges is created in the operating system's task scheduler. This scheduled task is used to periodically execute a health check script. The health check script is used to detect the existence of service processes and the status of audio playback activity, and to perform repair operations when an anomaly is detected. File association startup protection mechanism: Modify the opening method of a preset file type and associate it with a launcher program. When the multi-startup and guardian module detects that the service process has failed to repair continuously, it will trigger the launcher program by simulating the execution of that type of file to attempt to restore the service.

[0011] Furthermore, when performing repair operations, the daemon script or health check script also includes at least one of the following operations: forcibly terminating residual instances of the service process, checking and repairing the registry key configuration of the service process, and reporting alarm information to the cloud management platform.

[0012] Furthermore, the identity identification and management module adopts a dual storage and dynamic verification mechanism, specifically including: Encrypted registry storage: The client's identity is encrypted using an encryption algorithm and stored in a key-value pair in the operating system registry with a deceptive name and deep path; Distributed storage of the file system: The client identity is split into multiple data fragments and embedded or appended to non-executable files in different system directories; Cloud Binding and Recovery: The client's identity identifier is bound to the hardware fingerprint of the store terminal on the cloud management platform; when the locally stored identity identifier is lost or damaged, the client software initiates an identity recovery request to the cloud based on the hardware fingerprint, and re-acquires the client's identity identifier after successful verification.

[0013] Furthermore, the audio device exclusivity and control module includes at least one of the following sub-modules: Volume Force Lock Submodule: Used to periodically reset the volume of a target audio session to a preset value sent from the cloud via the core audio application programming interface, and briefly lock the volume control interface to prevent external modifications. Audio focus preemption and retention submodule: This module is used to declare the audio session type as media playback to the operating system and continuously request audio focus during playback; when it detects that another process is occupying audio focus and outputting sound, it performs operations such as lowering the volume of the other process, muting it, or requesting the system to lower the background music volume to avoid other audio streams. Device Status Monitoring and Recovery Submodule: Used to register as a notification receiver for audio device events, listen for changes in the default audio output device in real time, and automatically switch to the currently available default device or report device anomaly alarms to the cloud when a device is detected to be removed.

[0014] Furthermore, the playback strategy template created by the playback strategy engine module supports at least one of the following rule definitions: Playback rules based on time periods allow you to specify playlists and volume values ​​for different time periods. Playback rules based on store tags specify that the same playback strategy should be applied to groups of stores with specific tags; Insertion rules based on priority and triggering conditions specify that the current playlist will be interrupted and specified audio content will be played when preset conditions are met.

[0015] The beneficial effects of this invention are as follows: This invention, through the collaboration of a system service camouflage module and a multi-startup and protection module, deeply embeds the playback client into the operating system's underlying layer, making it as difficult for ordinary users and malicious software to interfere with or terminate it, just like a critical system service. Even if the client process crashes abnormally or is forcibly terminated, it can automatically resume operation through multiple protection paths in a very short time, ensuring uninterrupted background music playback for extended periods, greatly reducing the need for manual maintenance intervention in stores. The cloud management platform provides chain enterprises with a central control brain, enabling unified management of music playback in thousands of stores. Headquarters managers can easily formulate complex playback strategies across regions, time periods, and store types, and issue them with a single click. Music content updates and strategy adjustments are reduced from the traditional hours / days of manual intervention to minutes, greatly improving the agility and consistency of brand management. Real-time feedback and analysis of playback data provide strong data support for operational decisions. By running at the system service level and utilizing the underlying Core Audio... The API's audio device exclusive control module enables mandatory, high-precision locking of playback volume, completely resolving the persistent problem of easily tampered volume. Simultaneously, intelligent audio focus management and device status monitoring ensure stable background music output under various complex software environments and hardware change scenarios, guaranteeing a pure and consistent auditory experience for customers. The automated operation and maintenance system significantly reduces reliance on the IT skills of frontline store staff and the workload of on-site / remote support personnel at headquarters. The system's self-healing capability reduces the risk of business interruption due to playback failures, enhancing brand image. Centralized management and resource distribution also save network bandwidth resources and manual maintenance costs. Furthermore, the infrastructure of this invention is not limited to music playback; its highly reliable client can serve as an edge node for store digital management, and in the future, it can be smoothly expanded to support more business scenarios such as video advertising playback, digital signage content management, and device IoT data collection, protecting the company's long-term investment. Attached Figure Description

[0016] Figure 1 This is a system architecture diagram of the present invention. Detailed Implementation

[0017] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0018] refer to Figure 1This invention provides a cloud-based intelligent store music management system, comprising: a cloud management platform and client software deployed on terminals in various stores; wherein: The cloud management platform includes: The device and store management module is used to register and manage terminals in each store, and generate a unique client identity for each terminal; The media library module is used to store and manage audio files; The playback strategy engine module is used to create and manage playback strategy templates, which define music playback rules based on time, store tags, and / or priority. The instruction issuance and data synchronization module is used to issue the playback strategy template, audio file list and configuration instructions to one or more designated store terminals through a secure communication link; The monitoring and log analysis module is used to receive the operational status information reported by each store terminal and to visualize and issue alarms. The client software includes: The system service masquerading module encapsulates the core playback and control logic of the client software into an operating system service process. The registration name and description of this service process are configured to strings similar to those of core operating system components, and its binary file is stored in the system protection directory. The system service masquerading module sets the registration name, display name, and description of the service process to strings highly similar to at least one of "Windows Audio," "Cryptographic Services," or "Windows Audio Endpoint Builder." The binary file of the service process is installed in a subdirectory of the System32 directory or a hidden subdirectory under the Program Files directory, and an access control list is set to allow only system and administrator accounts to read and execute it.

[0019] The multi-startup and protection module provides at least two independent startup triggering and process protection mechanisms to ensure that the service process can be automatically recovered after abnormal termination. The identity identification and management module is used to generate, encrypt, store, and dynamically verify the client identity identifier, and supports cloud-based identity recovery based on hardware fingerprints; The audio device exclusive control module runs in the service process and is used to forcibly lock the system volume through the underlying audio application programming interface, manage the audio focus of other audio processes, and monitor the status of audio output devices. The network communication module is used for encrypted communication with the cloud management platform, receiving instructions and resource lists, and reporting the client's operating status. The network communication module uses a WebSocket long-lived connection with the cloud management platform for heartbeat information reporting and real-time instruction reception, and employs a TLS-based encrypted hypertext transfer security protocol for file downloads, supporting breakpoint resume functionality.

[0020] The client software may also include a local encrypted cache for storing audio files downloaded from the cloud management platform; the audio files undergo integrity verification before storage.

[0021] The playback strategy template created by the playback strategy engine module supports at least one of the following rule definitions: Playback rules based on time periods allow you to specify playlists and volume values ​​for different time periods. Playback rules based on store tags specify that the same playback strategy should be applied to groups of stores with specific tags; Insertion rules based on priority and triggering conditions specify that the current playlist will be interrupted and specified audio content will be played when preset conditions are met.

[0022] The multi-startup and guardian module provides at least two independent startup triggering and process guardian mechanisms, including at least two of the following: System service auto-start mechanism: Service processes are automatically started by the service control manager when the operating system starts, and are set to automatic or automatic delayed start mode; Registry startup daemon mechanism: A daemon startup entry is created in the system registry startup items. This daemon startup entry points to a daemon script. The daemon script is used to periodically check the running status of the service process and perform a service restart operation when a process is detected to be missing. Scheduled task triggering mechanism: A scheduled task with the highest privileges is created in the operating system's task scheduler. This scheduled task is used to periodically execute a health check script. The health check script is used to detect the existence of service processes and the status of audio playback activity, and to perform repair operations when an anomaly is detected. File association startup protection mechanism: Modify the opening method of a preset file type and associate it with a launcher program. When the multi-startup and guardian module detects that the service process has failed to repair continuously, it will trigger the launcher program by simulating the execution of that type of file to attempt to restore the service.

[0023] When performing repair operations, the daemon script or health check script may also include at least one of the following operations: forcibly terminating any remaining instances of the service process, checking and repairing the registry key configuration of the service process, and reporting alarm information to the cloud management platform.

[0024] The identity identification and management module adopts a dual storage and dynamic verification mechanism, specifically including: Encrypted registry storage: The client's identity is encrypted using an encryption algorithm and stored in a key-value pair in the operating system registry with a deceptive name and deep path; Distributed storage of the file system: The client identity is split into multiple data fragments and embedded or appended to non-executable files in different system directories; Cloud Binding and Recovery: The client's identity identifier is bound to the hardware fingerprint of the store terminal on the cloud management platform; when the locally stored identity identifier is lost or damaged, the client software initiates an identity recovery request to the cloud based on the hardware fingerprint, and re-acquires the client's identity identifier after successful verification.

[0025] The audio device exclusive control module includes at least one of the following sub-modules: Volume Force Lock Submodule: Used to periodically reset the volume of a target audio session to a preset value sent from the cloud via the core audio application programming interface, and briefly lock the volume control interface to prevent external modifications. Audio focus preemption and retention submodule: This module is used to declare the audio session type as media playback to the operating system and continuously request audio focus during playback; when it detects that another process is occupying audio focus and outputting sound, it performs operations such as lowering the volume of the other process, muting it, or requesting the system to lower the background music volume to avoid other audio streams. Device Status Monitoring and Recovery Submodule: Used to register as a notification receiver for audio device events, listen for changes in the default audio output device in real time, and automatically switch to the currently available default device or report device anomaly alarms to the cloud when a device is detected to be removed.

[0026] The working steps of the system of this invention are as follows: (1) Initialization and registration: When the client software runs for the first time at the store terminal, it generates a unique identity identifier, collects hardware information and encrypts and reports it to the cloud management platform for registration and verification binding; (2) Strategy and resource synchronization: The cloud management platform pushes the matching playback strategy template and media resource list to the client according to the store group and tags to which the client belongs; the client downloads and verifies the required audio files to the local encrypted cache according to the list; (3) Local playback and protection execution: The client software runs in the form of a disguised system service, plays music according to the playback strategy template, monitors the health status of the service process through the multi-start and guardian module, and locks the volume and manages the audio focus through the audio device exclusive and control module; (4) Status reporting and monitoring: The client software regularly reports heartbeat information to the cloud management platform, including the current playback status, system resource usage, and abnormal events; (5) Remote intervention and control: The cloud management platform sends operation instructions to the designated client in real time. The operation instructions include switching playlists, inserting notifications, adjusting volume, or restarting client services. The client executes the operation instructions first after receiving them.

[0027] The local playback and protection execution steps further include: when the operating system starts, the fake system service is automatically started through the service control manager; at the same time, a first guardian script is triggered by the registry startup item, and a second health check script is triggered by the scheduled task, and the two monitor the running status and audio playback activities of the fake system service in parallel at different frequencies and different detection depths; when either monitoring mechanism detects that the service process is missing or the playback is abnormal, the corresponding service restart or repair process is executed.

[0028] Furthermore, in the strategy and resource synchronization steps, when the client downloads audio files, it prioritizes obtaining them through the content distribution network node and supports peer-to-peer acceleration of file transfer from other synchronized client nodes within the same local area network.

[0029] Furthermore, in the remote intervention and control process, the instructions issued by the cloud management platform have a high priority identifier; after receiving a high priority instruction, the client software interrupts the currently executing non-critical task, immediately parses and executes the instruction, and sends the execution result back to the cloud after execution is completed.

[0030] This invention, through the collaboration of a system service camouflage module and a multi-startup and protection module, deeply embeds the playback client into the operating system's underlying layer, making it as difficult for ordinary users and malicious software to interfere with or terminate it, just like a critical system service. Even if the client process crashes abnormally or is forcibly terminated, it can automatically resume operation through multiple protection paths in a very short time, ensuring uninterrupted background music playback for extended periods, greatly reducing the need for manual maintenance intervention in stores. The cloud management platform provides chain enterprises with a central control brain, enabling unified management of music playback in thousands of stores. Headquarters managers can easily formulate complex playback strategies across regions, time periods, and store types, and issue them with a single click. Music content updates and strategy adjustments are reduced from the traditional hours / days of manual intervention to minutes, greatly improving the agility and consistency of brand management. Real-time feedback and analysis of playback data provide strong data support for operational decisions. By running at the system service level and utilizing the underlying Core Audio... The API's audio device exclusive control module enables mandatory, high-precision locking of playback volume, completely resolving the persistent problem of easily tampered volume. Simultaneously, intelligent audio focus management and device status monitoring ensure stable background music output under various complex software environments and hardware change scenarios, guaranteeing a pure and consistent auditory experience for customers. The automated operation and maintenance system significantly reduces reliance on the IT skills of frontline store staff and the workload of on-site / remote support personnel at headquarters. The system's self-healing capability reduces the risk of business interruption due to playback failures, enhancing brand image. Centralized management and resource distribution also save network bandwidth resources and manual maintenance costs. Furthermore, the infrastructure of this invention is not limited to music playback; its highly reliable client can serve as an edge node for store digital management, and in the future, it can be smoothly expanded to support more business scenarios such as video advertising playback, digital signage content management, and device IoT data collection, protecting the company's long-term investment.

[0031] 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 of the technical features; and these modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present invention.

Claims

1. A cloud-based intelligent store music management system, characterized in that, include: A cloud-based management platform and client software deployed at various store terminals; among which: The cloud management platform includes: The device and store management module is used to register and manage terminals in each store, and generate a unique client identity for each terminal; The media library module is used to store and manage audio files; The playback strategy engine module is used to create and manage playback strategy templates; The instruction issuance and data synchronization module is used to issue the playback strategy template, audio file list and configuration instructions to one or more designated store terminals through a secure communication link; The monitoring and log analysis module is used to receive the operational status information reported by each store terminal and to visualize and issue alarms. The client software includes: The system service masquerading module is used to encapsulate the core playback and control logic of the client software into an operating system service process, and configure the registration name and description information of the service process as strings similar to those of the core components of the operating system, and its binary file is stored in the system protection directory. The multi-startup and protection module provides at least two independent startup triggering and process protection mechanisms to ensure that the service process can be automatically recovered after abnormal termination. The identity identification and management module is used to generate, encrypt, store, and dynamically verify the client identity identifier, and supports cloud-based identity recovery based on hardware fingerprints; The audio device exclusive control module runs in the service process and is used to forcibly lock the system volume through the underlying audio application programming interface, manage the audio focus of other audio processes, and monitor the status of audio output devices. The network communication module is used for encrypted communication with the cloud management platform, receiving instructions and resource lists, and reporting the client's operating status. The network communication module uses a WebSocket long-lived connection with the cloud management platform for heartbeat information reporting and real-time instruction reception, and employs a TLS-based encrypted hypertext transfer security protocol for file downloads, supporting breakpoint resume functionality.

2. The cloud-based intelligent store music management system according to claim 1, characterized in that, The multi-startup and guardian module provides at least two independent startup triggering and process guardian mechanisms, including at least two of the following: System service auto-start mechanism: Service processes are automatically started by the service control manager when the operating system starts, and are set to automatic or automatic delayed start mode; Registry startup daemon mechanism: A daemon startup entry is created in the system registry startup items. This daemon startup entry points to a daemon script. The daemon script is used to periodically check the running status of the service process and perform a service restart operation when a process is detected to be missing. Scheduled task triggering mechanism: A scheduled task with the highest privileges is created in the operating system's task scheduler. This scheduled task is used to periodically execute a health check script. The health check script is used to detect the existence of service processes and the status of audio playback activity, and to perform repair operations when an anomaly is detected. File association startup protection mechanism: Modify the opening method of a preset file type and associate it with a launcher program. When the multi-startup and guardian module detects that the service process has failed to repair continuously, it will trigger the launcher program by simulating the execution of that type of file to attempt to restore the service.

3. The cloud-based intelligent store music management system according to claim 2, characterized in that, When performing repair operations, the daemon script or health check script may also include at least one of the following operations: forcibly terminating any remaining instances of the service process, checking and repairing the registry key configuration of the service process, and reporting alarm information to the cloud management platform.

4. The cloud-based intelligent store music management system according to claim 3, characterized in that, The identity identification and management module adopts a dual storage and dynamic verification mechanism, specifically including: Encrypted registry storage: The client's identity is encrypted using an encryption algorithm and stored in a key-value pair in the operating system registry with a deceptive name and deep path; Distributed storage of the file system: The client identity is split into multiple data fragments and embedded or appended to non-executable files in different system directories; Cloud Binding and Recovery: The client's identity identifier is bound to the hardware fingerprint of the store terminal on the cloud management platform; when the locally stored identity identifier is lost or damaged, the client software initiates an identity recovery request to the cloud based on the hardware fingerprint, and re-acquires the client's identity identifier after successful verification.

5. The cloud-based intelligent store music management system according to claim 4, characterized in that, The audio device exclusive control module includes at least one of the following sub-modules: Volume Force Lock Submodule: Used to periodically reset the volume of a target audio session to a preset value sent from the cloud via the core audio application programming interface, and briefly lock the volume control interface to prevent external modifications. Audio focus preemption and retention submodule: This module is used to declare the audio session type as media playback to the operating system and continuously request audio focus during playback; when it detects that another process is occupying audio focus and outputting sound, it performs operations such as lowering the volume of the other process, muting it, or requesting the system to lower the background music volume to avoid other audio streams. Device Status Monitoring and Recovery Submodule: Used to register as a notification receiver for audio device events, listen for changes in the default audio output device in real time, and automatically switch to the currently available default device or report device anomaly alarms to the cloud when a device is detected to be removed.

6. The cloud-based intelligent store music management system according to claim 5, characterized in that, The playback strategy template created by the playback strategy engine module supports at least one of the following rule definitions: Playback rules based on time periods allow you to specify the playlist and volume values ​​for different time periods. Playback rules based on store tags specify that the same playback strategy should be applied to groups of stores with specific tags; Insertion rules based on priority and triggering conditions specify that the current playlist will be interrupted and specified audio content will be played when preset conditions are met.

Images