Multi-screen global retail terminal group control management and end-side multi-device collaborative interaction system and method

Abstract

The application relates to the technical field of unmanned retail. A multi-screen global retail terminal group control management and end-side multi-device cooperative interaction system comprises a server group control subsystem and an end-side multi-screen cooperation subsystem arranged in a retail terminal; the server group control subsystem is used for issuing remote terminal control instructions, state monitoring and strategy scheduling to at least one retail terminal through a network; the end-side multi-screen cooperation subsystem comprises at least two advertising screens, an aerial imaging screen, a transaction screen and an end-side coordinator, and each device is communicatively connected through a local area network, wherein the end-side coordinator is used for receiving the terminal control instructions issued by the server group control subsystem and performing event data broadcasting and data synchronization.

Description

Technical Field

[0001] This application relates to the field of unmanned retail technology, and more specifically, to a multi-screen omni-channel retail terminal group control management and end-side multi-device collaborative interaction system and method. Background Technology

[0002] As unmanned retail terminal scenarios expand further, retail terminals are evolving towards multi-screen functionality to meet diverse interaction and marketing needs. However, current retail terminals generally adopt a "multi-screen independent" operating mode: there is a lack of a unified underlying collaborative architecture between various display devices such as advertising screens, aerial imaging screens, and transaction screens, resulting in fragmented advertising displays, product interactions, and transaction processes.

[0003] In existing technologies, heterogeneous devices within retail terminals (running on different operating systems) lack a globally integrated control solution. When users select products on the transaction screen, other display devices often cannot achieve real-time content synchronization, resulting in a disjointed user marketing experience. Furthermore, due to the lack of a unified message distribution mechanism, cross-screen interactions suffer from extremely high latency. In addition, existing unmanned retail systems rely excessively on cloud-based command issuance and lack an architecture that can organically combine cloud-based group control strategies with local multi-device collaboration. This makes it difficult for the system to achieve batch, high-real-time, integrated multi-device collaboration in complex retail scenarios.

[0004] In summary, the core problem of existing retail terminal systems lies in the lack of a system that can deeply integrate "server group control" and "device-side heterogeneous multi-screen collaboration" at the architectural level, resulting in significant bottlenecks in multi-screen linkage interaction and batch management of retail terminals. Summary of the Invention

[0005] The main purpose of this application is to provide a multi-screen, full-domain retail terminal group control management and terminal-side multi-device collaborative interaction system and method to solve the technical problems in the background art.

[0006] To achieve the above objectives, the first aspect of this application proposes a multi-screen, full-domain retail terminal group control management and terminal-side multi-device collaborative interaction system, comprising: Server group control subsystem and terminal-side multi-screen collaboration subsystem set up in retail terminals; The server group control subsystem is used to remotely issue terminal control commands, monitor status, and schedule strategies for at least one retail terminal via the network. The terminal-side multi-screen collaborative subsystem includes at least two advertising screens, one aerial imaging screen, one transaction screen, and a terminal-side coordinator. Each device establishes a communication connection through a local area network. The terminal-side coordinator is used to receive terminal control commands issued by the server group control subsystem and to broadcast event data and synchronize data. The aerial imaging screen is used to display the corresponding content of user interaction at the retail terminal based on the event data; the advertising screen is used to switch the displayed content based on the event data; and the transaction screen is used to perform product selection, payment transactions, and shared status synchronization based on the event data.

[0007] In some possible implementations, the server group control subsystem includes an HTTP interface module, a group control scheduling module, and an MQTT message broker module; The HTTP interface module is communicatively connected to the group control and scheduling module, and is used to receive external control requests and send the control requests to the group control and scheduling module. The group control scheduling module is communicatively connected to the MQTT message broker module and is used to parse the external control request for the target retail terminal, split the instruction and schedule the processing, and generate the corresponding terminal control instruction. The MQTT message broker module is communicatively connected to each of the retail terminals and is used to send the terminal control commands to the end-side coordinator in the corresponding retail terminal, so that the end-side coordinator can broadcast event data and synchronize status to the advertising screen, the aerial imaging screen and the transaction screen through the end-side message bus.

[0008] In some feasible implementations, the group control scheduling module is configured as follows: The received external control request is parsed by the target terminal to form terminal group information, geographical area information and instruction priority information, and a corresponding instruction scheduling queue is generated. When a high-priority terminal control instruction is received, the execution process of the low-priority terminal control instruction is interrupted and the high-priority terminal control instruction is executed first. The MQTT message broker module is configured as follows: According to the instruction scheduling queue, terminal control instructions are sent to the corresponding retail terminals to realize unicast control, multicast control or broadcast control of multiple retail terminals.

[0009] In some feasible implementations, the terminal-side multi-screen collaboration subsystem also includes a unified event model; The event data is constructed based on the unified event model, which adopts a unified JSON Schema. The unified JSON Schema includes an event type field, a sender identifier field, a timestamp field, a payload data field, and a priority field. The end-side coordinator is used to publish the event data via the end-side message bus; The advertising screen and the aerial imaging screen are used to parse the event data and perform corresponding content display or status synchronization based on the parsing results.

[0010] In some feasible implementations, the server group control subsystem also includes a terminal registration and exception handling module; The terminal registration and anomaly handling module is used to receive the identification information and hardware fingerprint information of the retail terminal when the retail terminal is connected, and generate corresponding session credentials for the retail terminal to establish an encrypted communication connection. The terminal registration and anomaly handling module is also used to detect the heartbeat status and command response status of the retail terminal. If the retail terminal is detected to be abnormally offline or the command response times out, the module will perform command resending, session refresh, or anomaly alarm processing.

[0011] In some possible implementations, the end-side coordinator is used to maintain the multi-screen collaborative operation on the end side when the communication interruption of the server group control subsystem is detected, and to perform transaction status maintenance, inventory status maintenance and transaction data encryption caching based on the local rule engine; The end-side coordinator is also used to perform automatic verification of the encrypted cached transaction data after resuming communication with the server group control subsystem, and to synchronize the verified transaction data to the server group control subsystem.

[0012] In some feasible implementation methods, the terminal-side multi-screen collaboration subsystem also includes a user identification module and an environment perception module; The user identification module is used to acquire user identity information and / or user gesture input information, and generate corresponding user feature data and / or user interaction identification data; The environmental perception module is used to acquire pedestrian flow statistics within a preset distance range centered on the retail terminal, and send the pedestrian flow statistics to the server group control subsystem; The server group control subsystem is used to dynamically adjust the advertising content delivery strategy based on the user characteristic data and the pedestrian flow statistics, and push personalized advertising content to the corresponding advertising screens. The end-side coordinator is used to generate corresponding event data based on the user interaction identification data; The transaction screen is used to perform the corresponding product selection operation based on the event data and display the corresponding product information.

[0013] Secondly, this application provides a method for multi-screen omni-channel retail terminal group control management and terminal-side multi-device collaborative interaction, applied to the aforementioned multi-screen omni-channel retail terminal group control management and terminal-side multi-device collaborative interaction system, including: Receive terminal control commands issued by the server group control subsystem; Based on the terminal control instructions, corresponding event data is generated, and the event data is broadcast to each heterogeneous screen through the terminal-side message bus; Receive user interaction input information and generate corresponding interaction event data; Based on the interactive event data, corresponding product selection, advertising content switching, and shared status synchronization are performed.

[0014] In some feasible implementation methods, the step of receiving terminal control commands issued by the server group control subsystem includes: The external control request is parsed by the target terminal to form terminal grouping information, geographical area information and instruction priority information; A corresponding instruction scheduling queue is generated based on the terminal grouping information, geographical region information, and instruction priority information. Upon receiving a high-priority terminal control instruction, the execution process of the low-priority terminal control instruction is interrupted, and the high-priority terminal control instruction is executed first.

[0015] In some feasible implementations, after the step of generating corresponding event data based on the terminal control command and broadcasting the event data to each heterogeneous screen via the terminal-side message bus, the method further includes: Acquire user identification information and / or user gesture input information, and generate corresponding user feature data and / or user interaction identification data; Obtain pedestrian flow statistics within a preset range; Based on the user characteristic data and the pedestrian flow statistics, the advertising content delivery strategy is dynamically adjusted and corresponding personalized advertising content is pushed. Based on the user interaction recognition data, perform the corresponding product selection operation and display the corresponding product information.

[0016] The technical solutions provided by the embodiments of this application may include the following beneficial effects: This application fundamentally solves the problem of fragmented interaction caused by the independent operating environment and lack of a unified coordination mechanism of existing multi-screen devices in retail terminals by constructing a two-layer architecture comprising a server group control subsystem and an end-side multi-screen collaboration subsystem. By setting up an end-side coordinator, unified logical management of advertising screens, aerial imaging screens, and transaction screens is achieved, connecting the previously isolated heterogeneous screens to a unified message interaction system via a local area network. Utilizing the remote command issuance and policy scheduling capabilities of the server group control subsystem, combined with the event data broadcasting and synchronization mechanism of the end-side coordinator, it ensures that multi-screen devices can coordinate actions in real time and with low latency after receiving unified commands, realizing a closed-loop linkage between advertising display, user interaction, and product transactions. This system architecture not only improves the efficiency of integrated control of multiple devices in retail terminals but also significantly optimizes the user's immersive marketing experience and enhances the real-time response and operational stability of terminals in the entire retail scenario through the deep integration of group control and end-side collaboration. Attached Figure Description

[0017] The accompanying drawings, which form part of this application, are used to provide a further understanding of the application and to make other features, objects, and advantages of the application more apparent. The illustrative embodiments and descriptions of this application are used to explain the application and do not constitute an undue limitation of the application. In the drawings: Figure 1 The flowchart of a multi-screen omni-channel retail terminal group control management and terminal-side multi-device collaborative interaction method provided in this application. Detailed Implementation

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

[0019] The following explanations of some terms used in this application are provided to aid in understanding the technical solution of this application: JSON Schema is a data structure validation standard based on the JSON (JavaScript Object Notation) format.

[0020] SQLite is an extremely lightweight, embedded open-source database. Unlike traditional databases, it does not require the installation of separate server software. Instead, the entire database is embedded as a single file into an app or control program, making it ideal for efficiently storing data on edge devices such as unmanned retail terminals and mobile phones.

[0021] AES-256 is a widely used advanced encryption standard algorithm that uses a 256-bit long key to encrypt data with high strength, ensuring the security of offline data.

[0022] A WebSocket server is a backend server program or hardware node that can receive, process, and maintain WebSocket protocol connections in network communication.

[0023] A UUID (Universally Unique Identifier) ​​is a device or data identifier that is absolutely unique in both spatial and temporal dimensions and is generated by a specific algorithm.

[0024] In the first aspect, this application provides a multi-screen omni-channel retail terminal group control management and end-side multi-device collaborative interaction system, including a server group control subsystem and an end-side multi-screen collaborative subsystem set in the retail terminal.

[0025] The server group control subsystem is used to remotely issue terminal control commands, monitor status, and schedule strategies for at least one retail terminal via the network.

[0026] Specifically, the server group control subsystem includes an HTTP interface module, a group control scheduling module, and an MQTT message broker module.

[0027] The HTTP interface module is communicatively connected to the group control and scheduling module, and is used to receive external control requests and send the control requests to the group control and scheduling module.

[0028] The group control scheduling module is communicatively connected to the MQTT message broker module and is used to parse the external control request for the target retail terminal, split the instruction, and schedule the processing, and generate the corresponding terminal control instruction.

[0029] The MQTT message broker module is communicatively connected to each of the retail terminals and is used to send the terminal control commands to the end-side coordinator in the corresponding retail terminal, so that the end-side coordinator can broadcast event data and synchronize status to the advertising screen, the aerial imaging screen and the transaction screen through the end-side message bus.

[0030] It should be noted that the server group control subsystem, as the core of the cloud control and strategy orchestration of the entire multi-screen full-domain retail terminal group control management and end-side multi-device collaborative interaction system, is used to remotely issue terminal control commands, monitor status and schedule strategies for at least one retail terminal via the network.

[0031] Specifically, in order to effectively combine macro-control at the management end with high-concurrency real-time response at the terminal side, the server group control subsystem includes the following: 1. The specific structure and working principle of the HTTP interface module: The HTTP interface module serves as the network receiving boundary and data synchronization gateway of the server group control subsystem. Its input end is connected to the external control initiator (specifically the server group control subsystem) via the network, and its output end is connected to the group control scheduling module within the server group control subsystem.

[0032] In practical implementation, the HTTP interface module is used to receive batch control requests, configuration distribution requests, or upgrade requests initiated by the server group control subsystem. Since the control requests initiated by the server group control subsystem are typically directed towards macro-management strategies or multiple retail terminals, after receiving these external control requests, the HTTP interface module parses the network protocol and standardizes the data format of the external control requests, and then sends the external control requests to the internally connected group control scheduling module, thereby completing the synchronous import of control data from the server group control subsystem.

[0033] 2. The group control scheduling module is connected in series between the HTTP interface module and the MQTT message broker module, and is used to transform the external control request into a device-level concurrent scheduling strategy. Specifically, the group control scheduling module is communicatively connected to the MQTT message broker module, and is used to parse the external control request for the target retail terminal, split the instruction, and schedule the request, and generate corresponding terminal control instructions.

[0034] In the specific implementation process, the group control scheduling module is configured as follows: The received external control request is parsed by the target terminal to form terminal group information, geographical area information and instruction priority information, and a corresponding instruction scheduling queue is generated. When a high-priority terminal control instruction is received, the execution process of the low-priority terminal control instruction is interrupted and the high-priority terminal control instruction is executed first.

[0035] The specific structure and working principle of the group control and scheduling module: Multi-dimensional attribute parsing and instruction decomposition: When the group control scheduling module receives the external control request, its internal group control engine first parses the target scope parameters carried in the request. By comparing the static attributes and dynamic tags of the devices maintained on the server side, the external control request is transformed into corresponding terminal grouping information (used to identify a set of devices belonging to a specific product category or specific operational attribute), geographical area information (used to identify a set of devices belonging to a specific administrative division or specific gridded geographical location), and instruction priority information preset by the server group control subsystem or assigned according to the urgency of the business. Based on this, the group control scheduling module, through its internal instruction decomposition logic, breaks down a macro-level batch business request into atomic terminal control instructions for a single retail terminal, each containing specific data payloads (such as specific advertising material identifiers or control actions).

[0036] Construction of the instruction scheduling queue: After the terminal control instructions are generated, the group control scheduling module internally constructs a dynamic instruction scheduling queue. This queue is linearly ordered according to the instruction priority information carried by each terminal control instruction. Under normal operating conditions, the control instructions in the instruction scheduling queue are delivered to the underlying transmission channel serially or concurrently in a multi-threaded manner, according to their priority from high to low.

[0037] When the group control scheduling module is executing a routine control task (e.g., delivering low-priority regional promotional advertising content update instructions in queue order), if it receives an emergency terminal control instruction with high priority (e.g., a specific device fault reset instruction, an emergency lock-up instruction for all personnel, or an emergency security policy issuance request manually triggered by the server group control subsystem), the scheduling mechanism within the group control scheduling module will trigger a preemption procedure. Specifically, the group control scheduling module will interrupt the sending or delivery process of the currently executing low-priority terminal control instruction, suspend its sending status or temporarily remove it from the current active sending channel, and prioritize the allocation of computing and network bandwidth resources of the server group control subsystem to execute and deliver the high-priority terminal control instruction. Only after the high-priority terminal control instruction is successfully delivered and receives a response confirmation from the terminal side will the group control scheduling module resume the execution of the previously interrupted low-priority terminal control instruction, thereby ensuring, in principle, millisecond-level real-time response and highly reliable control scheduling of core control instructions.

[0038] 3. The specific structure and working principle of the MQTT message broker module: The MQTT message broker module serves as an asynchronous high-concurrency transmission path between the server group control subsystem and the terminal physical devices. Its input end receives the terminal control commands from the group control scheduling module, and its output end communicates with each of the retail terminals through a long network connection channel.

[0039] In the specific implementation process, the MQTT message broker module is configured as follows: According to the instruction scheduling queue, terminal control instructions are sent to the corresponding retail terminals to realize unicast control, multicast control or broadcast control of multiple retail terminals.

[0040] The specific principles for implementing the three control modes at the network protocol layer and the topic routing layer are as follows: The implementation principle of unicast control is as follows: When the terminal control command issued by the group control scheduling module is directed to a single device identifier (device_id), the MQTT message broker module publishes the terminal control command to a dedicated control topic with unique addressing characteristics that is exclusive to that specific terminal (e.g., / cmd / {device_id}). Only that specific retail terminal will subscribe to and receive the commands under this topic, thereby realizing precise individual control logic such as single device fault reset and single-machine personalized parameter configuration without interfering with other devices.

[0041] The implementation principle of multicast control is as follows: When the terminal control command carries specific terminal group information or geographical region information, the MQTT message broker module publishes the command to a public topic corresponding to that group label or geographical grid (e.g., / cmd / group / {region_east}). All retail terminals belonging to that specific group or located in that specific geographical region (e.g., East China region) can simultaneously and concurrently receive and parse the control command because they have all subscribed to the multicast topic. This, in principle, realizes multicast group control for synchronous regional promotional activities or batch updates of local multi-terminal advertising content.

[0042] The broadcast control mechanism works as follows: When the terminal control command has global coverage, the MQTT message broker module publishes the command to a global root control topic (e.g., / cmd / all) that is subscribed to by all devices across the network. All registered retail terminals distributed in various locations can receive the command payload simultaneously, thereby driving a synchronized response across the entire network. This supports highly interconnected scenarios such as global firmware upgrades, emergency policy issuance, or all-device locking and unlocking.

[0043] When the end-side coordinator within the corresponding retail terminal (which can also be a transaction screen within the retail terminal) receives the terminal control command delivered by the MQTT message broker module via a long network connection, the end-side coordinator, acting as the core of the end-side interaction command, broadcasts event data and synchronizes status to the advertising screens, aerial imaging screens, and the transaction screen (which acts as the local coordinator) located within the same retail terminal in the form of event data publication via the end-side local wired LAN message bus (i.e., the end-side message bus). Combined with the end-side coordinator's LAN bus pass-through, the macro-level control commands of the server group control subsystem can penetrate network boundaries, driving real-time content linkage and strong status consistency synchronization across heterogeneous multi-screen end-side devices.

[0044] The terminal-side multi-screen collaborative subsystem includes at least two advertising screens, one aerial imaging screen, one transaction screen, and a terminal-side coordinator. Each device establishes a communication connection through a local area network.

[0045] The end-side coordinator is used to receive terminal control commands issued by the server group control subsystem and to broadcast event data and synchronize data.

[0046] Furthermore, the aerial imaging screen is used to present the corresponding content of the user's interaction on the retail terminal based on the event data, the advertising screen is used to switch the displayed content based on the event data, and the transaction screen is used to perform product selection, payment transactions, and shared status synchronization based on the event data.

[0047] It should be noted that the terminal-side multi-screen collaborative subsystem also includes a unified event model. The event data is constructed based on the unified event model, which adopts a unified JSON Schema. The unified JSON Schema includes an event type field, a sender identifier field, a timestamp field, a payload data field, and a priority field. The terminal-side coordinator is used to publish the event data through the terminal-side message bus. The advertising screen and the aerial imaging screen are used to parse the event data and perform corresponding content display or status synchronization based on the parsing results (the advertising screen, aerial imaging screen, and transaction screen mentioned in this application all refer to intelligent display terminals that integrate computing processing units and operating systems (or: collaborative terminals composed of display panels and corresponding control boards). The process of parsing event data is specifically implemented by the processor built into each screen running the corresponding software program (or protocol parsing module), which is not improved in this application).

[0048] The end-side coordinator is used to maintain multi-screen collaborative operation on the end side when communication interruption of the server group control subsystem is detected, and to perform transaction status maintenance, inventory status maintenance and encrypted caching of transaction data based on the local rule engine; in addition, the end-side coordinator is also used to perform automatic reconciliation and verification of the encrypted cached transaction data after communication with the server group control subsystem is restored, and to synchronize the verified transaction data to the server group control subsystem.

[0049] In practical implementation, the at least two advertising screens, the aerial imaging screen, and the transaction screen integrating the end-side coordinator function, all located inside the retail terminal, are connected via wired network cables to a local network switch located inside the retail terminal, thereby constructing an independent closed-loop local area network (LAN) architecture at the physical layer. This LAN communication architecture operates based on the standard TCP / IP protocol suite, and its data transmission is confined to the internal local network environment of the retail terminal, independent of external wide area network connections. Therefore, even under extreme conditions of external network fluctuations or interruptions, the physical display devices within the end-side multi-screen collaboration subsystem can still maintain high-bandwidth, low-latency local data packet interaction with the end-side coordinator.

[0050] Based on the aforementioned closed-loop LAN architecture, when a communication interruption with the server group control subsystem is detected, the transaction screen, which integrates the end-side coordinator function, uses a locally running lightweight database (such as SQLite) and rule engine to perform real-time localized state machine maintenance on the current transaction status and the inventory status within the retail terminal. Simultaneously, the transaction screen invokes a locally built-in encryption algorithm (such as AES-256) to encrypt each order and transaction data generated during offline periods at the database level or field level, and securely stores it on local non-volatile storage media. During this period, the transaction screen continues to broadcast status events to the advertising screen and the aerial imaging screen via the local network switch to ensure uninterrupted multi-screen collaborative interaction. After communication with the server group control subsystem is restored, the transaction screen, acting as an end-side coordinator, first initiates an automatic reconciliation and verification program. It performs differential reconciliation and anti-tampering verification between the locally encrypted cached offline transaction flow and the initial account status on the server side. After confirming that the data integrity and consistency are correct, it packages and uploads the verified transaction data to the server group control subsystem through the differential synchronization mechanism to complete the final consistency synchronization of the entire domain data.

[0051] In the aforementioned end-side multi-screen collaboration subsystem, the end-side coordinator serves as a protocol bridge and event distribution hub connecting the server group control subsystem and the local multi-device network. It has the following functions: Network command reception: The end-side coordinator receives terminal control commands issued by the server group control subsystem through a network channel.

[0052] Event Broadcasting and Data Synchronization: After receiving the terminal control command, the end-side coordinator converts the terminal control command into event data conforming to the unified interaction specification of the end-side through the built-in protocol parsing module (or: the internally running command parsing program). The end-side coordinator uses the built-in local message broker service module (referring to the core communication middleware program deployed locally (on the end-side) of the retail terminal, responsible for receiving, routing, and distributing various device events and control commands within the local closed-loop LAN, realizing high-concurrency, low-latency, and loosely coupled data interaction between various heterogeneous display devices on the end-side) to publish the event data through the end-side message bus.

[0053] Operating principle of the end-side message bus: In its specific implementation, the end-side message bus adopts a subscription / publish mechanism based on a lightweight network communication protocol. Specifically, a local WebSocket server runs on the transaction screen that integrates the end-side coordinator function, and the at least two advertising screens and the one aerial imaging screen act as clients connected to the local WebSocket server. When the end-side coordinator injects the event data into the end-side message bus, the local WebSocket server will replicate the event data multiple times and distribute it to all screen device clients that maintain a connection. This enables real-time transparent transmission of control commands, broadcasting of event data, and high synchronization of multi-screen shared states within the local area network environment.

[0054] Furthermore, the terminal-side multi-screen collaboration subsystem utilizes the functional division of multiple screens to achieve a closed-loop linkage between user interaction behavior and marketing display. Each screen executes differentiated local response actions based on the event data received from the terminal-side message bus, specifically including the following: The terminal-side multi-screen collaboration subsystem also includes a user identification module and an environment perception module; The user identification module is used to acquire user identity information and / or user gesture input information, and generate corresponding user feature data and / or user interaction identification data; The environmental perception module is used to acquire pedestrian flow statistics within a preset distance range centered on the retail terminal, and send the pedestrian flow statistics to the server group control subsystem; The server group control subsystem is used to dynamically adjust the advertising content delivery strategy based on the user characteristic data and the pedestrian flow statistics, and push personalized advertising content to the corresponding advertising screens. The end-side coordinator is used to generate corresponding event data based on the user interaction identification data; The transaction screen is used to perform the corresponding product selection operation based on the event data and display the corresponding product information.

[0055] Furthermore, in the actual operation of the aforementioned multi-screen collaborative subsystem, the functional division of multiple screens is utilized to achieve a closed-loop linkage between user interaction behavior and marketing display. The specific implementation process is as follows: The terminal-side multi-screen collaboration subsystem continuously collects data on external environmental features and user actions through the built-in user identification module and environmental perception module. To meet privacy protection and data security compliance requirements, both the user identification module and the environmental perception module have unauthorized de-identification and anonymization mechanisms embedded in their hardware and underlying driver layers. Specifically, when the user identification module acquires user identification information or user gesture input information, its local dedicated image signal processor (ISP) immediately removes raw image features that can pinpoint personal biometric characteristics from a temporary memory buffer, extracting only abstract facial contour geometric feature vectors and non-specific age and gender probability intervals. Immediately after data output, the temporary memory buffer is physically erased, ensuring that local and subsequently transmitted data are anonymized quantitative features that cannot be traced back to a specific individual. Simultaneously, the environmental perception module uses the retail terminal as its physical center, acquiring pedestrian flow statistics within a preset distance range using infrared beams or depth sensors. This data only includes the count and distance distribution of moving physical shapes within the environment, without retaining any personal privacy information, thus ensuring privacy compliance throughout the entire process at the data source.

[0056] Under normal network conditions, the environment perception module sends the pedestrian flow statistics and the de-identified user feature data to the server group control subsystem. However, to address WAN transmission latency caused by WAN jitter or bandwidth limitations, the edge-side multi-screen collaboration subsystem also incorporates an edge-cloud dual-track advertising decision alignment mechanism. The edge-side coordinator's non-volatile memory pre-stores a default general advertising strategy matrix (i.e., a backup plan). When the network link detection thread detects that network latency exceeds a preset response threshold (e.g., blocking time exceeds 3 seconds) or the connection is completely interrupted, the system triggers an edge computing degradation strategy. The edge-side coordinator automatically intercepts the reporting request to the server group control subsystem and instead uses the local rule engine to call the general advertising strategy matrix, directly performing localized recommendations based on the locally collected user feature data, thus achieving local autonomous marketing display under network outage or high latency conditions.

[0057] Specifically, the system triggers the edge computing degradation strategy through the following steps: When a communication interruption is detected, the end-side coordinator activates the local rule engine and retrieves the pre-set lightweight decision model. Simultaneously, the end-side coordinator uses the user identification module to perform differentiated feature extraction on the independent spatial areas faced by the two advertising screens, one aerial imaging screen, and one transaction screen, respectively, to generate de-identified user feature data corresponding to each screen. The de-identified user feature data and environmental perception data corresponding to each screen are then used as input variables and substituted into the lightweight decision model. The lightweight decision model is run to perform independent parallel calculations on the de-identified user feature data corresponding to each screen, so as to dynamically update the real-time weight scores of each ad tag under each of the two advertising screens, the aerial imaging screen and the transaction screen, and sort them from high to low according to the real-time weight scores, and output the ad material identifier with the highest score for each screen. The end-side coordinator distributes the advertising material identifiers corresponding to each screen through the end-side message bus, so that the two corresponding advertising screens play the corresponding differentiated advertising video files in full screen based on the received corresponding identifiers, and the aerial imaging screen calls the locally stored black background 3D motion effect material to play aerial floating imaging based on the received corresponding identifiers, and the transaction screen embeds and plays the corresponding differentiated marketing content in its preset secondary rendering window based on the received corresponding identifiers without interfering with the interaction of the main transaction window.

[0058] It should be noted that when the end-side coordinator determines that the communication link with the server group control subsystem is interrupted, the end-side coordinator intercepts the original transaction data request that is about to be sent to the server group control subsystem locally, so as to prevent the original transaction data request from being sent to the external communication link.

[0059] Subsequently, the edge coordinator synchronously activates the local rule engine and retrieves a pre-installed lightweight decision model (the lightweight decision model is an existing, already trained lightweight decision model). To achieve personalized marketing on heterogeneous screens during offline operation, feature collection must be differentiated at the source. At this time, the edge coordinator performs differentiated feature extraction through the user identification module; wherein, the user identification module contains multiple independent collection devices, each facing a different physical space area: For the two advertising screens: the user identification module acquires the overall characteristics of passing pedestrians through a collection device facing the far-field channel area, and generates de-identified user feature data corresponding to each of the two advertising screens.

[0060] For aerial imaging screens: The user identification module dynamically captures the characteristics (such as facial orientation and dwell time) of potential users who linger in front of the device and show curiosity through a collection device facing the focal area in the middle of the aircraft, and generates de-identified user feature data corresponding to the aerial imaging screen.

[0061] For the transaction screen: The user identification module accurately extracts the characteristics of the user currently selecting goods or preparing to settle the transaction in front of the screen through the collection device facing the near-field operation area, and generates de-identified user feature data corresponding to the transaction screen.

[0062] Finally, the edge coordinator takes the de-identified user feature data corresponding to each of the above screens, along with the environmental perception data, as input variables and substitutes them into the lightweight decision model.

[0063] When the end-side coordinator runs the lightweight decision model, it performs independent parallel computation on the de-identified user feature data corresponding to each screen.

[0064] During the calculation process, the lightweight decision model compares and calculates each input variable with locally pre-set advertising tags. For two advertising screens, the lightweight decision model calculates the score of each advertising tag under the current pedestrian flow characteristics; for the aerial imaging screen, the lightweight decision model calculates the score of advertising tags with strong visual impact based on the user's dwell time; for the transaction screen, the lightweight decision model combines the individual characteristics of the current user to calculate the score of advertising tags related to cross-selling or product exchange.

[0065] After the calculation is completed, the local rule engine sorts the real-time weight scores of each advertising tag from high to low locally, and automatically extracts the first place after sorting each screen, and outputs the advertising material identifier with the highest score for each of the two advertising screens, the aerial imaging screen and the transaction screen.

[0066] After all the advertising creative identifiers have been output, the edge coordinator injects the advertising creative identifiers corresponding to each screen into the edge message bus for targeted distribution: Actions of the two advertising screens: After receiving their respective advertising material identifiers from the terminal message bus, the two advertising screens call up the corresponding differentiated advertising video files locally and play them in full screen to attract people in the far field.

[0067] Actions of the aerial imaging screen: After receiving the corresponding advertising material identifier from the terminal message bus, the aerial imaging screen calls upon locally stored black-background 3D animation material to perform aerial levitation imaging playback. Since the black background does not display screen borders during aerial imaging, it presents a borderless, levitation 3D visual effect in physical space, thus blocking the viewer's gaze.

[0068] Actions of the transaction screen: After receiving the corresponding advertising material identifier from the terminal message bus, the transaction screen maintains the normal interaction of the main transaction window where the current user is selecting or paying, without interfering with or covering it; at the same time, the transaction screen embeds and plays differentiated marketing content that matches the user's operation in its preset secondary rendering window (such as an independent display area on the side or bottom of the screen).

[0069] In summary, even in a communication interruption state where network support is completely lost, the edge-based coordinator fully realizes a closed loop of autonomous marketing display where multiple screens perform their respective functions and are tailored to individual users.

[0070] When wide area network transmission is smooth, the system adopts a joint inference strategy that combines initial screening at the endpoint with precise calculation by the server group control subsystem to reduce the pressure of data transmission to external communication links and the computational pressure on the server group control subsystem itself. The specific execution steps include: First, perform the initial screening and capacity offloading process on the client side: The end-side coordinator uses multiple independent acquisition devices included in the user identification module to perform differentiated feature extraction on the independent spatial areas faced by the two advertising screens, one aerial imaging screen, and one transaction screen, and generates de-identified user feature data corresponding to each screen.

[0071] To avoid transmission bottlenecks caused by directly uploading massive amounts of high-dimensional data, the edge coordinator uses the de-identified user feature data corresponding to each screen as input variables and pre-calculates them in the local lightweight decision model. The lightweight decision model quickly filters out low-relevance ad tags locally, generating a set of candidate ad tags for each screen. Subsequently, the edge coordinator uploads the low-volume set of candidate ad tags, along with pedestrian flow statistics collected by the environment perception module, to the server group control subsystem in real time.

[0072] Secondly, execute the final adjudication process based on global multi-dimensional factors: After receiving the reported data, the server group control subsystem invokes its internal dynamic recommendation algorithm. Since the received data has already undergone local dehydration and initial filtering by the end-side coordinator, the data processing throughput pressure on the server group control subsystem is fundamentally eliminated.

[0073] At this point, the server group control subsystem performs multi-dimensional interleaving calculations on the received candidate ad tag set and the pedestrian flow statistics, along with the historical transaction data across all terminals, long-term user consumption behavior habits, and macro-level business district heat data stored internally by the server group control subsystem. Specifically, the pedestrian flow statistics and the macro-level business district heat data are jointly mapped to an "environmental heat index," while the candidate ad tag set and the historical transaction data across all terminals are jointly mapped to "target audience profile tags."

[0074] If the current environmental heat index exceeds the preset high-density threshold, and the audience profile tags show specific sudden group preference characteristics across the entire network, the server group control subsystem uses its cross-terminal global dimension advantage to conduct a second-level review of the candidate ad tag set, determines the ad material identifier with the highest score for each screen, and pushes the ad material identifier to the corresponding end-side coordinators.

[0075] Subsequently, after receiving the various advertising material identifiers, the end-side coordinator distributes them through the end-side message bus to drive each screen to independently load the corresponding marketing materials and perform differentiated playback.

[0076] Throughout the entire multi-screen autonomous operation, regardless of whether the wide area network transmission is smooth or communication is interrupted, if a user performs an interactive action in front of the aerial imaging screen, the system will trigger a local closed-loop linkage process for all screen behaviors in parallel. Specifically, the end-side coordinator generates standardized corresponding event data in real time based on the user interaction recognition data captured by the user recognition module and injects it into the end-side message bus. The transaction screen and the advertising screen, running under different operating system environments, execute differentiated local responses after receiving the event data distributed by the end-side message bus. The transaction screen, based on the event data, performs the corresponding product selection operation and displays the corresponding product information in linkage without physical contact with the screen. The advertising screen, on the other hand, synchronously switches to a deep marketing screen that matches the product.

[0077] It should be noted that the principles behind the unified event model and cross-operating system compatibility are as follows: To eliminate communication barriers between the aerial imaging screen, the advertising screen, and the transaction screen caused by heterogeneous operating systems (such as the cross-platform environment of Windows and Android), the terminal-side multi-screen collaboration subsystem also includes a unified event model.

[0078] Specifically, a unified JSON Schema structure is used: the event data is constructed based on the unified event model, which is defined using a standardized unified JSON Schema text structure. The unified JSON Schema standardizes the following five core logical fields in the data dictionary, including: Event Type field: Used to explicitly define the specific business attributes of the interaction event (such as user proximity event, product selection event, payment completion event, or server group control subsystem forced control event).

[0079] Sender Identifier Field: Used to record the specific physical device ID that generated and sent the event data, so that the receiver can trace the source and perform closed-loop routing.

[0080] Timestamp field: Records the absolute physical time of event generation, used for determining the order of multiple concurrent events and discarding expired events.

[0081] Payload data field: Used to carry the specific parameter key-value pairs required for the execution of this event (such as specific product SKU codes, advertising material IDs, transaction deduction amounts, and other key operational data).

[0082] Priority field: Defines the urgency of the event when it is executed on the device side, and is used to guide the screen terminal to interrupt the current rendering stream to respond to this event first.

[0083] Since the unified JSON Schema uses a standard text data format that is independent of the development language, the advertising screen running in the Android system environment and the aerial imaging screen running in the Windows system environment can both use their respective underlying standard text parsers to deserialize and parse the event data stream received through the terminal message bus.

[0084] Based on the parsed field results, the screen terminal calls the corresponding local hardware driver or display window to execute the corresponding content display or state synchronization. To prevent network jitter or bus retransmission from causing screen rendering anomalies, the payload data field also contains a unique UUID feature code. After parsing this feature code, the advertising screen and the aerial imaging screen compare it with local historical execution records. If it is a duplicate event, it is automatically discarded, thus ensuring the idempotency of events and the consistency of screen synchronization in principle for cross-system collaboration on the terminal side.

[0085] For example, taking a scenario where a user selects a specific product using contactless gestures as an example, the text data flow process of the unified event model is illustrated. When the user performs an air-pointing gesture in front of the air imaging screen, the air imaging screen (the sender) captures the action through an external sensor and converts it into an event data stream conforming to the unified JSON Schema text structure.

[0086] In this specific event data stream, the detailed text mappings of each core logical field are as follows: The event type field is assigned a specific character identifier (such as PRODUCT_SELECTED) that indicates that the product has been selected. The sender identifier field is assigned a unique device code that identifies the current aerial imaging screen hardware entity. The timestamp field is assigned the absolute physical time in milliseconds when the current gesture was triggered; The priority field is assigned a value representing a high-level response (such as the value 3), which indicates that the receiving device must immediately preempt the current normal rendering stream; The payload data field encapsulates the core parameters of this transaction in key-value pairs, including: a randomly generated globally unique UUID feature code (used to uniquely identify the single gesture action), the standard SKU code of the target product (used to locate the product specification), and the media resource index ID of the corresponding advertising material.

[0087] The edge message bus copies and broadcasts the text event data stream containing the five core fields. Upon receiving this text data stream, the advertising screen running on the Android system first performs deserialization extraction using its local standard text parser.

[0088] To ensure consistent screen synchronization and prevent anomalies caused by network retransmissions, the control program of the advertising screen first extracts the UUID feature code from the payload data field and compares it in real time with a pre-set "historical executed event feature code queue" in local memory. If the comparison result shows that the UUID feature code already exists in the historical queue, the event is determined to be a duplicate redundant event of bus retransmission, and the advertising screen automatically discards it silently without triggering any screen redrawing action; if the comparison result shows that the UUID feature code is appearing for the first time, the advertising screen stores the feature code in the queue and immediately retrieves the corresponding product promotion video pre-stored in local memory according to the parsed media resource index ID for adaptive full-screen playback.

[0089] At the same time, the transaction screen also parses the same SKU code and automatically adds the corresponding product item to the local virtual shopping cart without the need for a physical touch screen, thus achieving strong synchronization of heterogeneous screen behavior across operating systems at the plain text protocol layer.

[0090] To address the technical shortcomings of retail terminal core functions being paralyzed due to fluctuations in external wide area networks, the terminal-side multi-screen collaboration subsystem possesses robust local autonomy and self-healing capabilities after network outages. Specifically, it includes the following: The end-side coordinator is used to maintain the multi-screen collaborative operation on the end side when the communication interruption of the server group control subsystem is detected, and to perform transaction status maintenance, inventory status maintenance and transaction data encryption caching based on the local rule engine. The end-side coordinator is also used to perform automatic verification of the encrypted cached transaction data after resuming communication with the server group control subsystem, and to synchronize the verified transaction data to the server group control subsystem.

[0091] It should be noted that, during the actual operation of the aforementioned end-side multi-screen collaboration subsystem, the specific execution process of the local autonomy and network outage self-healing capabilities is as follows: During periods of external communication interruption, when a user initiates a product selection or purchase request on the transaction screen, the local rule engine integrated within the end-side coordinator exercises business decision-making authority in place of the server group control subsystem. The local rule engine invokes pre-set pricing strategies and settlement rules stored in the end-side non-volatile memory to perform offline settlement determination for the current order and generates a time-sensitive temporary transaction voucher locally. This ensures that the purchase process on the transaction screen can proceed without relying on verification by the external server group control subsystem.

[0092] After the shipping unit within the retail terminal performs picking and shipping operations, the local rules engine accesses the local database snapshot within the end-side coordinator in real time. It then directly deducts and updates the corresponding inventory quantity locally, thereby maintaining the actual inventory status of the retail terminal in real time to avoid overselling. For transaction logs, inventory change logs, and user behavior logs generated offline, the end-side coordinator uses a local encryption algorithm at the software layer to convert plaintext data into ciphertext data streams and securely stores them in a local non-volatile physical cache for isolated storage, protecting the data security of local accounts.

[0093] Once the external network is restored and the network link probing thread within the end-side coordinator receives the handshake feedback from the server group control subsystem, the end-side coordinator exits local autonomous mode and initiates the network restoration data alignment process. The end-side coordinator first reads the encrypted data stream accumulated during the offline period from the non-volatile physical cache medium and recovers the plaintext data using the decryption key. Subsequently, the end-side coordinator performs automatic reconciliation verification. This verification compares transaction sequence numbers before and after the network outage, checks inventory continuity differences, and performs a bidirectional cross-comparison between the locally recovered transaction records and the server group control subsystem's transaction records. It automatically identifies and eliminates duplicate or conflicting transactions caused by network retransmission to maintain the accuracy of the end-side data. After the automatic reconciliation verification is completed and the data is confirmed to be correct, the end-side coordinator synchronizes the verified difference transaction data and the final inventory deduction result to the server group control subsystem through the restored external network long connection channel. This completes data backfilling in the database within the server group control subsystem, restoring the entire network's data state to a synchronized operating state.

[0094] In one embodiment, the server group control subsystem further includes a terminal registration and exception handling module.

[0095] The terminal registration and anomaly handling module is used to receive the identification information and hardware fingerprint information of the retail terminal when the retail terminal is connected, and generate corresponding session credentials for the retail terminal to establish an encrypted communication connection. The terminal registration and anomaly handling module is also used to detect the heartbeat status and command response status of the retail terminal. If the retail terminal is detected to be abnormally offline or the command response times out, the module will perform command resending, session refresh, or anomaly alarm processing.

[0096] Specifically, when the retail terminal connects, its internal end-side coordinator initiates an access request to the server group control subsystem through an external communication link.

[0097] At this time, the terminal registration and exception handling module receives the identification information and hardware fingerprint information sent by the end-side coordinator. After successful verification, the terminal registration and exception handling module generates corresponding session credentials and sends the session credentials to the end-side coordinator, so that the end-side coordinator can formally establish an encrypted communication connection with the server group control subsystem based on the session credentials.

[0098] After the encrypted communication connection is established, the end-side coordinator sends lightweight heartbeat data packets to the remote end at preset time intervals. The terminal registration and anomaly handling module then monitors the heartbeat status and command response status of the end-side coordinator in real time to identify the fault delay status of the external wide area network. Smooth network transmission status: If the terminal registration and anomaly handling module receives the heartbeat data packet normally within the preset time interval and determines that there is no network fault delay, the server group control subsystem will normally execute the aforementioned global multi-dimensional dynamic advertising recommendation, sorting and distribution.

[0099] Network fluctuations and delays (disaster recovery retry): If a network failure and delay occur, causing the control commands sent by the terminal registration and anomaly handling module to the end-side coordinator to encounter response timeouts, the terminal registration and anomaly handling module will immediately execute command retransmission processing at the remote end to cope with short-term sudden network delays.

[0100] Complete network disconnection (anomaly determination): If the external network failure delay continues to worsen, causing the heartbeat data packet to fail to arrive within the preset monitoring period, the terminal registration and anomaly handling module will formally determine that the retail terminal is abnormally offline based on the severe failure delay of the heartbeat response, and will perform session refresh processing accordingly, while performing anomaly alarm processing remotely.

[0101] It should be noted that when the terminal registration and anomaly handling module determines that the retail terminal is abnormally offline due to a severe failure delay in the heartbeat response at the remote end, the local end-side coordinator is also experiencing a network failure delay at the physical site.

[0102] Specifically, due to network failure delays, the original transaction data requests sent by the end-side coordinator to the external communication link encounter continuous physical timeouts; when the duration or number of physical timeouts exceeds a locally preset judgment threshold, the end-side coordinator officially determines locally that it is currently in a communication interruption state.

[0103] Upon determining that communication is interrupted, the end-side coordinator intercepts the original transaction data request locally, preventing it from continuing to be sent to the external communication link. Simultaneously, it activates the local rule engine and retrieves the pre-set lightweight decision model locally, enabling the two advertising screens, one aerial imaging screen, and one transaction screen to completely switch to the edge computing degradation strategy, thereby utilizing the local bus to complete the operation of real-time multi-screen interactive linkage.

[0104] In the various embodiments of this application, the advertising screen, aerial imaging screen, and transaction screen are all standard display and interactive devices known in the art. The innovation of this application lies in constructing a logical architecture and control method for multi-screen, full-domain retail terminal group control management and multi-device collaborative interaction on the terminal side, rather than improving the hardware structure or internal circuitry of the aforementioned screen modules themselves. Each screen module only serves as a terminal node executing event data issued by the terminal coordinator, connected to the terminal coordinator through a common communication interface. Therefore, this application does not impose any limitations on the specific selection, physical parameters, or appearance structure of the aforementioned screen modules. Those skilled in the art can directly configure and integrate them using existing market-standard equipment according to the actual retail scenario requirements.

[0105] like Figure 1 As shown, in a second aspect, this application provides a method for multi-screen omni-channel retail terminal group control management and terminal-side multi-device collaborative interaction, applied to the aforementioned multi-screen omni-channel retail terminal group control management and terminal-side multi-device collaborative interaction system, comprising: S100 receives terminal control commands issued by the server group control subsystem; S200, generate corresponding event data based on the terminal control command, and broadcast the event data to each heterogeneous screen through the terminal-side message bus; S300 receives user interaction input information and generates corresponding interaction event data; S400, based on the interactive event data, perform corresponding product selection, advertising content switching, and shared status synchronization.

[0106] In one embodiment, the step of receiving terminal control instructions issued by the server group control subsystem includes: S101, the external control request is parsed by the target terminal to form terminal grouping information, geographical area information and instruction priority information; S102, generate a corresponding instruction scheduling queue based on the terminal grouping information, geographical area information and instruction priority information; S103, upon receiving a high-priority terminal control instruction, interrupt the execution process of the low-priority terminal control instruction and execute the high-priority terminal control instruction first.

[0107] In one embodiment, after the step of generating corresponding event data based on the terminal control command and broadcasting the event data to each heterogeneous screen via the terminal-side message bus, the following steps are included: S201, Obtain user identification information and / or user gesture input information, and generate corresponding user feature data and / or user interaction identification data; S202, Obtain pedestrian flow statistics within a preset range; S203, dynamically adjust the advertising content delivery strategy based on the user characteristic data and the pedestrian flow statistics, and push corresponding personalized advertising content; S204, perform the corresponding product selection operation based on the user interaction recognition data, and display the corresponding product information.

[0108] It should be noted that for a detailed description of a multi-screen omni-channel retail terminal group control management and terminal-side multi-device collaborative interaction method, please refer to the aforementioned multi-screen omni-channel retail terminal group control management and terminal-side multi-device collaborative interaction system, which will not be repeated here.

[0109] It should be noted that the steps shown in the flowchart in the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions, and although a logical order is shown in the flowchart, in some cases the steps shown or described may be executed in a different order than that shown here.

[0110] Obviously, those skilled in the art should understand that the various units or steps of this application described above can be implemented using general-purpose computing devices. They can be centralized on a single computing device or distributed across a network of multiple computing devices. Optionally, they can be implemented using computer-executable program code, thereby storing them in a storage device for execution by a computing device, or fabricating them separately as individual integrated circuit modules, or fabricating multiple modules or steps into a single integrated circuit module. Thus, this application is not limited to any particular combination of hardware and software.

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

Claims

1. A multi-screen, full-domain retail terminal group control management and terminal-side multi-device collaborative interaction system, characterized in that, include: Server group control subsystem and terminal-side multi-screen collaboration subsystem set up in retail terminals; The server group control subsystem is used to remotely issue terminal control commands, monitor status, and schedule strategies for at least one retail terminal via the network. The terminal-side multi-screen collaborative subsystem includes at least two advertising screens, one aerial imaging screen, one transaction screen, and a terminal-side coordinator. Each device establishes a communication connection through a local area network. The terminal-side coordinator is used to receive terminal control commands issued by the server group control subsystem and to broadcast event data and synchronize data. The aerial imaging screen is used to display the corresponding content of user interaction at the retail terminal based on the event data; the advertising screen is used to switch the displayed content based on the event data; and the transaction screen is used to perform product selection, payment transactions, and shared status synchronization based on the event data.

2. The multi-screen omni-channel retail terminal group control management and terminal-side multi-device collaborative interaction system as described in claim 1, characterized in that, The server group control subsystem includes an HTTP interface module, a group control scheduling module, and an MQTT message broker module. The HTTP interface module is communicatively connected to the group control and scheduling module, and is used to receive external control requests and send the control requests to the group control and scheduling module. The group control scheduling module is communicatively connected to the MQTT message broker module and is used to parse the external control request for the target retail terminal, split the instruction and schedule the processing, and generate the corresponding terminal control instruction. The MQTT message broker module is communicatively connected to each of the retail terminals and is used to send the terminal control commands to the end-side coordinator in the corresponding retail terminal, so that the end-side coordinator can broadcast event data and synchronize status to the advertising screen, the aerial imaging screen and the transaction screen through the end-side message bus.

3. The multi-screen omni-channel retail terminal group control management and terminal-side multi-device collaborative interaction system as described in claim 2, characterized in that, The group control scheduling module is configured as follows: The received external control request is parsed by the target terminal to form terminal group information, geographical area information and instruction priority information, and a corresponding instruction scheduling queue is generated. When a high-priority terminal control instruction is received, the execution process of the low-priority terminal control instruction is interrupted and the high-priority terminal control instruction is executed first. The MQTT message broker module is configured as follows: According to the instruction scheduling queue, terminal control instructions are sent to the corresponding retail terminals to realize unicast control, multicast control or broadcast control of multiple retail terminals.

4. The multi-screen omni-channel retail terminal group control management and terminal-side multi-device collaborative interaction system as described in claim 1, characterized in that, The terminal-side multi-screen collaboration subsystem also includes a unified event model; The event data is constructed based on the unified event model, which adopts a unified JSON Schema. The unified JSON Schema includes an event type field, a sender identifier field, a timestamp field, a payload data field, and a priority field. The end-side coordinator is used to publish the event data via the end-side message bus; The advertising screen, the aerial imaging screen, and the transaction screen are used to parse the event data and perform corresponding content display or status synchronization based on the parsing results.

5. The multi-screen omni-channel retail terminal group control management and terminal-side multi-device collaborative interaction system as described in claim 2, characterized in that, The server group control subsystem also includes a terminal registration and anomaly handling module; The terminal registration and anomaly handling module is used to receive the identification information and hardware fingerprint information of the retail terminal when the retail terminal is connected, and generate corresponding session credentials for the retail terminal to establish an encrypted communication connection. The terminal registration and anomaly handling module is also used to detect the heartbeat status and command response status of the retail terminal. If the retail terminal is detected to be abnormally offline or the command response times out, the module will perform command resending, session refresh, or anomaly alarm processing.

6. The multi-screen omni-channel retail terminal group control management and terminal-side multi-device collaborative interaction system as described in claim 1, characterized in that, The end-side coordinator is used to maintain the multi-screen collaborative operation on the end side when the communication interruption of the server group control subsystem is detected, and to perform transaction status maintenance, inventory status maintenance and transaction data encryption caching based on the local rule engine. The end-side coordinator is also used to perform automatic verification of the encrypted cached transaction data after resuming communication with the server group control subsystem, and to synchronize the verified transaction data to the server group control subsystem.

7. The multi-screen omni-channel retail terminal group control management and terminal-side multi-device collaborative interaction system as described in claim 1, characterized in that, The terminal-side multi-screen collaboration subsystem also includes a user identification module and an environment perception module; The user identification module is used to acquire user identity information and / or user gesture input information, and generate corresponding user feature data and / or user interaction identification data; The environmental perception module is used to acquire pedestrian flow statistics within a preset distance range centered on the retail terminal, and send the pedestrian flow statistics to the server group control subsystem; The server group control subsystem is used to dynamically adjust the advertising content delivery strategy based on the user characteristic data and the pedestrian flow statistics, and push personalized advertising content to the corresponding advertising screens. The end-side coordinator is used to generate corresponding event data based on the user interaction identification data; The transaction screen is used to perform the corresponding product selection operation based on the event data and display the corresponding product information.

8. A method for multi-screen omni-channel retail terminal group control management and terminal-side multi-device collaborative interaction, characterized in that, The multi-screen omni-channel retail terminal group control management and terminal-side multi-device collaborative interaction system applied to any one of claims 1-7 includes: Receive terminal control commands issued by the server group control subsystem; Based on the terminal control instructions, corresponding event data is generated, and the event data is broadcast to each heterogeneous screen through the terminal-side message bus; Receive user interaction input information and generate corresponding interaction event data; Based on the interactive event data, corresponding product selection, advertising content switching, and sharing status synchronization are performed.

9. The method for multi-screen omni-channel retail terminal group control management and multi-device collaborative interaction as described in claim 8, characterized in that, The step of receiving terminal control commands issued by the server group control subsystem includes: The external control request is parsed by the target terminal to form terminal grouping information, geographical area information and instruction priority information; A corresponding instruction scheduling queue is generated based on the terminal grouping information, geographical region information, and instruction priority information. Upon receiving a high-priority terminal control instruction, the execution process of the low-priority terminal control instruction is interrupted, and the high-priority terminal control instruction is executed first.

10. The multi-screen omni-channel retail terminal group control management and terminal-side multi-device collaborative interaction method as described in claim 8, characterized in that, After the step of generating corresponding event data based on the terminal control command and broadcasting the event data to each heterogeneous screen through the terminal-side message bus, the following steps are included: Acquire user identification information and / or user gesture input information, and generate corresponding user feature data and / or user interaction identification data; Obtain pedestrian flow statistics within a preset range; Based on the user characteristic data and the pedestrian flow statistics, the advertising content delivery strategy is dynamically adjusted and corresponding personalized advertising content is pushed. Based on the user interaction recognition data, perform the corresponding product selection operation and display the corresponding product information.

Images