A method and system for centralized control and management of multi-protocol equipment in cultural tourism projects

By using global time base synchronization and latency characteristic detection, the problem of cross-platform and multi-protocol unified management of equipment control systems in cultural tourism projects has been solved, achieving precise synchronization and intelligent management of heterogeneous devices, and improving user experience and system efficiency.

CN123123468APending Publication Date: 2026-11-17BEIJING DASHENG TIANYI CULTURE COMMUNICATION CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202611438301.1
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2026-09-16
Publication Date
2026-11-17

AI Technical Summary

Technical Problem

Existing equipment control systems for cultural and tourism projects lack cross-platform access capabilities and unified management solutions for multiple protocols, resulting in inconsistent equipment execution times and user experience defects, as well as a lack of intelligent management functions.

Method used

Employing a global time base synchronization unit and a delay characteristic detection unit, the system performs clock calibration and delay compensation on each device through a multi-protocol adapter engine, achieving precise synchronization control across protocol devices, and providing intelligent management through a visual editor and health monitoring unit.

Benefits of technology

It achieves millisecond-level synchronous control over a general IP network, reducing system deployment costs and operational complexity, supporting unified management of multiple heterogeneous protocols and device health monitoring, and improving user experience.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123123468A_ABST
    Figure CN123123468A_ABST
Patent Text Reader

Abstract

This invention discloses a centralized control and management method and system for multi-protocol devices in cultural tourism projects, relating to the field of automated control technology for cultural tourism project equipment. The method first uses a multi-protocol adapter engine to perform clock calibration on each protocol adapter instance via NTP or PTP protocol. Each protocol adapter instance sends a probe command to the target device, calculating unidirectional transmission delay characteristic parameters based on round-trip delay. Then, the protocol adapter instances calculate delay compensation values ​​based on a unified time base and delay characteristic parameters, generating protocol data packets carrying pre-compensated execution timestamps. Finally, heterogeneous devices with different network delay characteristics execute action commands synchronously at a unified physical time after delay compensation. This achieves precise synchronous control across protocol devices, solving the problem of inconsistent execution times caused by differences in transmission delay.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This invention relates to the field of automated control technology for equipment in cultural and tourism projects, specifically to a centralized control and management method and system for multi-protocol equipment in cultural and tourism projects. Background Technology

[0002] With the rapid development of the cultural tourism industry, the types and quantities of equipment used in scenic spots, theme parks, live performances, and urban light shows have increased dramatically, encompassing various types such as lighting equipment, audio equipment, video equipment, special effects equipment, and mechanical equipment. These devices typically employ different communication protocols, including RtP, UDP, OSC, WebSocket, HTTP, MQTT, Art-Net, DMX512, and MIDI, resulting in a serious protocol fragmentation problem.

[0003] Existing technologies suffer from the following main problems: limited control methods and lack of cross-platform capabilities. Traditional cultural and tourism equipment control systems rely on dedicated hardware controllers or client software, making cross-platform access impossible for users via general web browsers; limited protocol adaptation solutions and difficulties in unified management of multiple protocols. Existing systems typically support only a limited number of protocols, lacking a unified management solution for various heterogeneous protocols; lack of precise synchronous control capabilities across protocol devices. In scenarios such as live performances and light shows, existing technologies do not consider the transmission latency differences between devices using different protocols, leading to inconsistent execution times of actions by different devices when the backend server issues commands simultaneously, resulting in user experience defects such as audio-visual asynchrony; and a lack of intelligent management functions. Existing systems primarily focus on real-time control, lacking intelligent functions such as visualized program scheduling, precise time-line-based scheduling, equipment health monitoring, and multi-level access control, making it difficult to meet the increasingly complex management and control needs of large-scale cultural and tourism projects.

[0004] In summary, there is an urgent need for a web-based centralized control and management solution for cultural and tourism project equipment that supports unified access for multi-protocol devices and enables precise synchronous control of cross-protocol devices. Summary of the Invention

[0005] The purpose of this invention is to provide a method and system for centralized control and management of multi-protocol devices for cultural and tourism projects, so as to solve the problems mentioned in the background art.

[0006] To achieve the above objectives, the present invention provides the following technical solution: a method for centralized control and management of multi-protocol equipment in cultural tourism projects, comprising the following steps:

[0007] S1. Global time base establishment and delay characteristic detection: The multi-protocol adapter engine performs clock calibration on each protocol adapter instance through NTP or PTP protocol. Each protocol adapter instance sends a detection command to the target device. It calculates and maintains the one-way transmission delay characteristic parameters of each target device according to the round-trip delay. The delay characteristic parameters include at least the average delay value and the delay standard deviation.

[0008] S2. Protocol Conversion and Delay Compensation Timestamp Appending: The front-end web application sends a device control request, and the back-end server routes the control command to the corresponding protocol adapter instance. The protocol adapter instance maps the standardized instruction opcode to the original protocol instruction code corresponding to the target device protocol and encapsulates the instruction parameters. The protocol adapter instance calculates the delay compensation value based on the unified time base and the one-way transmission delay characteristic parameters, and generates a protocol data packet carrying a pre-compensation execution timestamp. The pre-compensation execution timestamp is equal to the original execution timestamp minus the delay compensation value.

[0009] S3. Concurrent execution according to the compensated timestamp: The protocol adapter instance sends the protocol data packet carrying the pre-compensated execution timestamp to the target device, so that heterogeneous devices with different network latency characteristics can synchronously execute action instructions at the unified physical time after latency compensation.

[0010] Preferably, the multi-protocol adapter engine adopts a plug-in architecture, with each protocol adapter existing as an independent dynamic link library or module. A unified adapter loader dynamically loads the corresponding adapter instance at runtime according to the device protocol type. The multi-protocol adapter engine includes at least RtP adapter, UDP adapter, OSC adapter, WebSocket adapter, HTTP adapter, MQTT adapter, Art-Net adapter, DMX512 adapter, and MIDI adapter. Each adapter implements a unified connect, disconnect, send, and onData standard interface.

[0011] Preferably, the delay detection process specifically includes: each protocol adapter instance sending at least three detection commands to the target device, recording the sending time T1 and receiving response time T4 for each detection, calculating the round-trip delay Rt = T4 - T1 - device processing time, taking the average value of multiple detections Rt as the average round-trip delay, using Rt / 2 as the estimated value of one-way transmission delay, and calculating the one-way delay standard deviation Q of multiple detections; the delay compensation value is calculated according to Tc = Tp + k × Q, where k is a configurable safety factor ranging from 1.0 to 3.0; when the protocol adapter instance detects that the delay standard deviation Q exceeds a preset threshold, it automatically triggers re-detection and dynamically updates the delay characteristic parameters.

[0012] Preferably, it also includes S4, automatic device discovery: the backend server obtains the device's fingerprint information through UDP broadcast or MQTT subscription. The fingerprint information includes MAC address, IP address, open port number, protocol feature field and device model identifier string. The fingerprint information is matched with a preset device feature library to identify the device type and supported protocol types. Based on the identification results, device configuration information is automatically generated and stored in the device registry. The corresponding protocol adapter instance is loaded and a communication connection is established with the device.

[0013] Preferably, each record in the device feature library includes the device model, device type, supported communication protocols, and corresponding feature matching rules. Each field in the fingerprint information is compared with the feature matching rules one by one. When the matching degree reaches 0.85, the identification is successful. When the matching degree is between 0.5 and 0.85, it is marked as pending confirmation and prompts for manual confirmation. When the matching degree is less than 0.5, it is marked as an unknown device and the fingerprint information is recorded for the feature library to be updated.

[0014] Preferably, it also includes S5, visual program scheduling: The backend server provides a visual timeline editor, receives the CUE point sequence created by the user, each CUE point includes at least a device action list, execution time offset, and duration parameters. The backend server converts the execution time offset of each CUE point into an absolute execution timestamp carrying device-level latency compensation according to the unified time base and the latency characteristic parameters, forming synchronized program data and storing it. When the user creates or moves a CUE point, the backend server detects whether there are conflicting CUE points acting on the same device under the same time offset. If so, it highlights the conflict area and provides automatic adjustment suggestions.

[0015] Preferably, the CUE point also includes fade-in / fade-out transition effect parameters, and multiple intermediate state instructions between the initial state and the target state are generated by an interpolation algorithm. The interpolation algorithm supports four curve types: linear, exponential, logarithmic, and S-shaped. The multiple intermediate state instructions are evenly distributed in time order within the duration parameter, and are sent out and executed sequentially after being appended with an incremental timestamp based on the unified time base and delay compensation.

[0016] Preferably, it also includes S6, schedule scheduling and synchronous execution: when the scheduling engine of the backend server triggers program playback according to the schedule scheduling rules, it calls synchronous program data and sends it to the multi-protocol adapter engine; the multi-protocol adapter engine sends protocol data packets concurrently through each protocol adapter instance according to the absolute execution timestamp of each CUE point after delay compensation, so as to realize the synchronous execution of program actions. The schedule scheduling rules include execution cycle, execution time, associated program identifier and priority parameters. When there are multiple trigger conflicts at the same time, they are arbitrated according to priority.

[0017] Preferably, it also includes S7, device health monitoring: the multi-protocol adapter engine sends heartbeat detection signals to the target device through each protocol adapter instance according to a preset heartbeat cycle. When no response is received for more than a preset number of consecutive times, the device is determined to be offline. The backend server sends an electrical parameter query command to the target device that supports electrical parameter feedback through the protocol adapter instance, or indirectly obtains electrical parameter data by communicating with the smart meter on the device's power supply circuit. The real-time electrical parameters are compared with a preset threshold. When the threshold is exceeded, a graded alarm message is generated and notified through multiple channels.

[0018] Preferably, a multi-protocol centralized control and management system for cultural tourism projects includes: a front-end web application module, used to provide a device control interface, a visual timeline editor interface, and a device status monitoring interface, sending control requests via HTTP protocol and receiving device status push via WebSocket protocol; a back-end server module, including a multi-protocol adapter engine, a device registry, a program scheduling management unit, a schedule engine, and a device health monitoring unit; and a database module, used to store device configuration information, program scheduling data, schedule rules, and device status history records; the multi-protocol adapter engine adopts a plug-in architecture, with a built-in global time base synchronization unit and a latency characteristic detection unit: the global time base synchronization unit performs clock calibration on each protocol adapter instance via NTP or PTP protocol to establish a unified time base; the latency characteristic detection unit sends a request to the target device during the initialization phase of each protocol adapter instance. The system prepares to send probe commands, calculates and maintains the one-way transmission delay characteristic parameters of each target device corresponding to the protocol type; the multi-protocol adapter engine adds a delay-compensated execution timestamp to the converted protocol data packets according to the unified time base and the delay characteristic parameters, so that heterogeneous devices with different network delay characteristics can synchronously execute actions at the compensated unified physical time; the device registry is used to store device configuration information and delay characteristic parameters; the program scheduling management unit is used to store CUE point sequences and convert the execution time offset into an absolute execution timestamp carrying delay compensation, and store it as synchronous program data; the schedule scheduling engine is used to trigger program playback according to the schedule scheduling rules, call the synchronous program data and send it to the multi-protocol adapter engine, which then concurrently executes device actions according to the delay-compensated absolute execution timestamp; the device health monitoring unit is used to detect device anomalies through heartbeat detection and electrical parameter monitoring.

[0019] The technical effects and advantages of this invention are as follows:

[0020] 1. This method and system for centralized control and management of multi-protocol devices in cultural tourism projects creatively integrates two independent technical branches—protocol adaptation and transmission delay compensation—by embedding a global time base synchronization unit and a delay characteristic detection unit within the protocol adapter engine. Addressing the inherent differences in network transmission delay characteristics among devices with different protocol types, this invention actively detects and dynamically calculates the corresponding delay compensation value for each device and pre-compensates the execution timestamp of each control command, enabling heterogeneous devices with different network delay characteristics to execute actions synchronously at a unified physical time after compensation.

[0021] 2. The multi-protocol centralized control and management method and system for cultural tourism projects directly embeds the delay characteristic parameters of each device obtained by delay detection into the process of generating program scheduling data. The execution time offset of each CUE point is converted into an absolute execution timestamp carrying device-level delay compensation when stored, rather than being temporarily compensated at runtime.

[0022] 3. The multi-protocol centralized control and management method and system for cultural and tourism projects analyzes the correlation between electrical parameters and delay characteristic parameters obtained by the health monitoring unit. When the standard deviation of the network delay Q of the device exceeds the preset threshold, the system automatically triggers re-probing and updates the delay characteristic parameters, thereby dynamically correcting the compensation timestamps in all subsequent program scheduling data.

[0023] 4. This method and system for centralized control and management of multi-protocol devices for cultural and tourism projects can achieve millisecond-level synchronous control of cross-protocol devices under general IP network conditions by building NTP / PTP time base synchronization and delay detection compensation mechanism in the protocol adapter engine software layer. No additional hardware investment is required, which reduces system deployment costs and operation and maintenance complexity. Attached Figure Description

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

[0025] Figure 1 This is an overview flowchart of the multi-protocol device centralized control and management method of the present invention;

[0026] Figure 2 This is a timing diagram of the delay detection and delay compensation mechanism in step S1 of the present invention;

[0027] Figure 3 This is a flowchart attached to step S2 of the present invention, which involves protocol conversion and delay compensation timestamps.

[0028] Figure 4 This is a flowchart of the concurrent execution of sub-step S3 of the present invention according to the compensated timestamp;

[0029] Figure 5 This is a flowchart of sub-step S4, automatic device discovery, of the present invention;

[0030] Figure 6 This is a flowchart of step S5 of the present invention, which visualizes program arrangement.

[0031] Figure 7 This is a flowchart of step S6, scheduling and synchronous execution, of the present invention;

[0032] Figure 8 This is a flowchart of step S7, device health monitoring, of the present invention.

[0033] Figure 9 This is a schematic diagram of the overall system architecture of the present invention;

[0034] Figure 10 This is a diagram of the multi-protocol adapter engine architecture of the present invention. Detailed Implementation

[0035] 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, and 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.

[0036] This invention discloses a method and system for centralized control and management of multi-protocol devices in cultural tourism projects, according to the appendix. Figures 1 to 10 As shown.

[0037] Example 1: A method for centralized control and management of multi-protocol devices in cultural tourism projects, specifically including the following steps:

[0038] Step S1: Establishing a global time base and detecting delay characteristics.

[0039] The backend server starts a multi-protocol adapter engine, which adopts a plug-in architecture. The engine includes an adapter loader and an adapter manager. The adapter loader scans the preset plug-in directory, identifies the classes that implement the standard adapter interface, and establishes a mapping index table between protocol types and adapter classes. The adapter manager is responsible for maintaining the lifecycle of all loaded adapter instances, including instantiation, caching, destruction, and exception recovery. The engine preloads nine protocol adapters: RtP, UDP, OSC, WebSocket, HTTP, MQTT, Art-Net, DMX512, and MIDI. All adapters uniformly encapsulate the four standard interfaces: connect, disconnect, send, and onData.

[0040] The engine has a built-in global time base synchronization unit that performs clock calibration on each protocol adapter instance through the NTP protocol to establish a unified time base. The establishment of a unified time base allows the execution timestamps of all subsequent control commands to be compared and scheduled under the same time reference system.

[0041] Each protocol adapter instance performs a latency probing process during the initialization phase. Taking the Art-Net protocol adapter as an example, the adapter sends an ArtPoll probe command to the target Art-Net device, records the sending time T1, the target device responds with an ArtPollReply data packet, the adapter records the receiving time T4, and calculates the round-trip latency Rt = T4 - T1 - device processing time.

[0042] To improve detection accuracy, each protocol adapter instance sends at least three detection commands to the target device, takes the average value of multiple detections Rt as the average round-trip delay, uses Rt / 2 as the estimated one-way transmission delay Tp, and calculates the one-way delay standard deviation Q of multiple detections.

[0043] The delay compensation value is calculated using the following formula:

[0044] Tc = Tp + k × Q

[0045] Where k is a configurable safety factor, ranging from 1.0 to 3.0. When k=1.0, the compensation covers about 84% of the delayed samples, when k=2.0, it covers about 95%, and when k=3.0, it covers about 99.7%. For scenarios requiring high synchronization accuracy, it is recommended to use k=2.0.

[0046] The protocol adapter instance continuously monitors changes in the network environment during operation. When it detects that the latency standard deviation Q exceeds a preset threshold, it automatically triggers a re-probing and dynamically updates the latency characteristic parameters to adapt to changes in the network environment.

[0047] Step S2: Protocol conversion and delay compensation timestamp appending.

[0048] The front-end web application sends a control request carrying the target device identifier and standardized operating instructions to the back-end server via the HTTP POST method.

[0049] The adapter instance parses standardized control commands, extracts standard instruction opcodes and instruction parameters, and retrieves the built-in protocol mapping table. The protocol mapping table is a hash table maintained internally by the adapter, used to map the unified standardized opcodes within the system to the original instruction codes corresponding to the protocols of each target device.

[0050] After mapping is complete, the adapter encapsulates the instruction parameters according to the data frame format of the target device protocol, including byte order conversion, data type serialization, checksum calculation, and length field filling.

[0051] The adapter instance calculates the delay compensation value based on the unified time base provided by the global time base synchronization unit and the one-way transmission delay characteristic parameters corresponding to the target device, and generates a protocol data packet carrying a pre-compensation execution timestamp. The pre-compensation execution timestamp is equal to the original execution timestamp minus the delay compensation value.

[0052] Step S3: Execute concurrently according to the compensated timestamp.

[0053] The protocol adapter instance sends the protocol data packet carrying the pre-compensated execution timestamp to the target device. In the case of multiple devices executing simultaneously, each protocol adapter instance sends the protocol data packet concurrently according to its own calculated pre-compensated execution timestamp, so that heterogeneous devices with different network latency characteristics can execute the action command synchronously at the same physical time after latency compensation.

[0054] Step S4: Device automatically discovers.

[0055] The backend server scans for online devices on the local area network via UDP broadcast. The target address for the UDP broadcast is the subnet broadcast address, and the port is a preset discovery port list. The system sends formatted discovery request messages sequentially according to the preset discovery port list, then opens a listening window to wait for device responses. The response timeout is 3000 milliseconds. At the same time, it subscribes to a specified topic via MQTT to obtain information on online devices in the cloud.

[0056] For response messages, the system collects fingerprint information such as the MAC address, IP address, open port number, protocol feature fields in the response data packet, and device model identification string of each device. The protocol feature fields include the fixed magic number of the first N bytes of the response message, the protocol version number field, and the protocol type declaration field actively reported by the device.

[0057] The backend server matches the collected device fingerprints against a pre-built device feature database. This database is a pre-constructed relational database where each record contains the device model, device type, supported communication protocols, feature matching rules, and matching weights. The matching process involves comparing each fingerprint field against the matching rules in the feature database one by one, assigning a sub-score to each matching item, and then weighted summing the results to obtain the overall matching degree.

[0058] When the overall matching degree reaches the preset threshold of 0.85, the identification is successful. The device type and supported protocol type are automatically identified. Devices with a matching degree between 0.5 and 0.85 are marked as pending confirmation and prompt for manual confirmation. Devices with a matching degree below 0.5 are marked as unknown devices and the original fingerprint information is recorded for subsequent feature database updates.

[0059] Based on the identification results, the system automatically generates complete configuration information including device identifier, device name, device type, protocol type, IP address, port number and connection parameters, and stores it in the device registry. Then, based on the device configuration information, it loads the corresponding protocol adapter instance and establishes a communication connection with the device.

[0060] Step S5: Visualize the program arrangement.

[0061] The backend provides a web-based visual timeline editor to the frontend, supporting drag-and-drop editing of program flows. Users can create multiple CUE control points on the timeline. The backend server converts the execution time offset of each CUE point into an absolute execution timestamp carrying device-level latency compensation based on a unified time base and the latency characteristics parameters of each target device. When a user creates or moves a CUE point, the backend server traverses the existing CUE point sequence to detect whether there are conflicting CUE points acting on the same device with the same time offset. If a conflict is detected, the conflict area is highlighted in the editor interface and automatic adjustment suggestions are provided.

[0062] The fade-in / fade-out transition effect generates multiple intermediate state instructions between the initial state and the target state through an interpolation algorithm. After the arrangement is completed, the system sorts all CUE points by time offset and stores them as structured program data, including the total program duration, program identifier, version number and timestamp.

[0063] Step S6: Schedule scheduling and synchronous execution.

[0064] The backend server's scheduling engine automatically triggers program playback based on the user-configured schedule rules. Users configure program scheduling rules in the system, including execution cycle, fixed execution time, associated program identifier, and priority parameters.

[0065] Users can also configure special scheduling schemes for holidays, which can be specified by three methods: Gregorian calendar date, lunar calendar date and relative date. The scheduling engine adopts a time wheel algorithm to implement all rules into the memory time wheel. The engine's built-in scanning thread checks every 100 milliseconds to see if any tasks have expired.

[0066] When the trigger condition is reached, the scheduling engine automatically calls the corresponding program data and sends it to the multi-protocol adapter engine. The multi-protocol adapter engine, based on the absolute execution timestamp of each CUE point in the synchronized program data carrying device-level delay compensation, sends protocol data packets concurrently through each protocol adapter instance to achieve synchronous execution of program actions.

[0067] In the event of a conflict triggered by multiple programs at the same time, the engine arbitrates the conflict based on priority parameters, and executes all conflicting tasks in descending order of priority. Tasks with the same priority are executed in order of creation time. If a high-priority task takes too long to execute, causing a low-priority task to be delayed, the system records a delay log and notifies the administrator. Holiday scheduling rules have a higher priority than regular rules.

[0068] The scheduling engine also supports manual pause, resume, skip, and immediate execution operations, and all operations are logged.

[0069] Step S7: Equipment health monitoring.

[0070] The multi-protocol adapter engine sends heartbeat detection signals to the target device through each protocol adapter instance according to a preset heartbeat period. The default heartbeat period is 30 seconds and can be modified by configuration. RtP devices send specific heartbeat commands, Art-Net devices determine their online status by listening to their periodically broadcast ArtPollReply packets, and MQTT devices infer their online status by checking the last message time of the subscribed topic.

[0071] If no response is received for 3 consecutive times, the device is determined to be offline and a critical alarm is generated.

[0072] Meanwhile, the backend server sends electrical parameter query commands to target devices that support electrical parameter feedback through each protocol adapter instance, and receives real-time electrical parameter data in the response. For devices that do not support active reporting of electrical parameters, the system provides two indirect acquisition methods: First, establish communication with the smart meter or power management module on the device's power supply circuit and query electrical parameters using the circuit number as an index; Second, deploy an external current transformer and voltage acquisition module on the power supply line and report the data to the gateway via ZigBee or LoRa.

[0073] Real-time electrical parameters include operating voltage, operating current, active power, and power factor. The system compares the real-time values ​​with preset threshold ranges. Thresholds can be set separately according to device type. Based on the magnitude of exceeding the threshold, three levels of alarms are defined: exceeding the upper limit by 120% is severe, exceeding 110% to 120% is moderate, and exceeding 100% to 110% is minor.

[0074] Alarm information is pushed through multiple channels, including system pop-ups, SMS, email, WeChat Work, and DingTalk groups. The system records the results of each heartbeat and electrical parameter query, forming a health history database that supports trend analysis and predictive maintenance.

[0075] Example 2: A multi-protocol centralized control and management system for cultural tourism projects

[0076] This embodiment uses the above method to construct a complete multi-protocol centralized control and management system for cultural tourism projects. The system adopts a front-end and back-end separation architecture, including a front-end web application module, a back-end server module, and a database module.

[0077] The front-end web application module is a lightweight browser-based interface that requires no client installation. It integrates functions such as device control, status monitoring, timeline program scheduling, area management, permission configuration, and alarm viewing. The front-end uses HTTP to issue commands and configure parameters, and WebSocket to receive device status and alarm information in real time and refresh the page. The front-end interface adopts a responsive design and is compatible with PC, tablet, and mobile browsers. The front-end uses the Vue.js framework for component-based development and uses the ECharts library to display visual charts of device status data, including electrical parameter trend charts and device online rate statistics.

[0078] The backend server module is the core of the system. The pluggable multi-protocol adapter engine is compatible with nine mainstream cultural and tourism equipment communication protocols. It realizes device access, protocol conversion and data interaction through a unified standard interface. The engine has a built-in global time base synchronization unit and latency characteristic detection unit. The device registry manages all device file information in a unified manner, providing data support for command routing and device adaptation. The program scheduling management unit realizes visualized program editing and data storage. The schedule engine realizes intelligent task scheduling and conflict arbitration. The device health monitoring unit realizes heartbeat detection, electrical parameter monitoring and hierarchical alarm. The backend is built with the Spring Boot framework and adopts a microservice architecture design. Protocol adaptation, program management, scheduling engine, user management and log service are separated into independent microservice modules. The modules communicate with each other through RESTful API or message queue.

[0079] The database module uses a relational database to store data. The database persistently stores all device configurations, program scheduling data, scheduling rules, alarm records, historical device status data, and user permission data. For scenarios with a large amount of historical device status data, the system uses a time-series database as an auxiliary storage to improve the writing and querying performance of time-series data. The database is configured with master-slave replication and regular backup strategies.

[0080] In particular, the system as a whole can achieve unified access, centralized management and control, intelligent orchestration, automatic scheduling and proactive operation and maintenance of all heterogeneous intelligent devices in cultural and tourism projects.

[0081] It should be noted that, in this document, relational terms such as "first" and "second" are used merely to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the term "include" or any other variations thereof is intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that includes a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the statement "includes a..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0082] The foregoing has shown and described the basic principles, main features, and advantages of the present invention. Those skilled in the art should understand that the present invention is not limited to the above embodiments. The embodiments and descriptions in the specification are merely illustrative of the principles of the invention. Various changes and modifications can be made to the invention without departing from its spirit and scope, and all such changes and modifications fall within the scope of the present invention as claimed. The scope of protection of this invention is defined by the appended claims and their equivalents.

Claims

1. A method for centralized control and management of multi-protocol equipment in cultural tourism projects, characterized in that, Includes the following steps: S1. Global time base establishment and delay characteristic detection: The multi-protocol adapter engine performs clock calibration on each protocol adapter instance through NTP or PTP protocol. Each protocol adapter instance sends a detection command to the target device. It calculates and maintains the one-way transmission delay characteristic parameters of each target device according to the round-trip delay. The delay characteristic parameters include at least the average delay value and the delay standard deviation. S2. Protocol Conversion and Delay Compensation Timestamp Appendage: The front-end web application sends a device control request, and the back-end server routes the control command to the corresponding protocol adapter instance; the protocol adapter instance maps the standardized instruction opcode to the original protocol instruction code corresponding to the target device protocol and encapsulates the instruction parameters. The protocol adapter instance calculates the delay compensation value based on the unified time base and the one-way transmission delay characteristic parameter, and generates a protocol data packet carrying a pre-compensation execution timestamp, wherein the pre-compensation execution timestamp is equal to the original execution timestamp minus the delay compensation value; S3. Concurrent execution according to the compensated timestamp: The protocol adapter instance sends the protocol data packet carrying the pre-compensated execution timestamp to the target device, so that heterogeneous devices with different network latency characteristics can synchronously execute action instructions at the unified physical time after latency compensation.

2. The method according to claim 1, characterized in that, The multi-protocol adapter engine adopts a plug-in architecture, with each protocol adapter existing as an independent dynamic link library or module. A unified adapter loader dynamically loads the corresponding adapter instance at runtime based on the device protocol type. The multi-protocol adapter engine includes at least RtP adapter, UDP adapter, OSC adapter, WebSocket adapter, HTTP adapter, MQTT adapter, Art-Net adapter, DMX512 adapter, and MIDI adapter. Each adapter implements a unified connect, disconnect, send, and onData standard interface.

3. The method according to claim 1, characterized in that, The delay detection process specifically includes: each protocol adapter instance sending at least three detection commands to the target device, recording the sending time T1 and receiving response time T4 for each detection, calculating the round-trip delay Rt = T4 - T1 - device processing time, taking the average value of multiple detections Rt as the average round-trip delay, using Rt / 2 as the estimated one-way transmission delay, and calculating the one-way delay standard deviation Q of multiple detections; the delay compensation value is calculated according to Tc = Tp + k × Q, where k is a configurable safety factor ranging from 1.0 to 3.0; when the protocol adapter instance detects that the delay standard deviation Q exceeds a preset threshold, it automatically triggers re-detection and dynamically updates the delay characteristic parameters.

4. The method according to claim 1, characterized in that, It also includes S4, automatic device discovery: the backend server obtains the device's fingerprint information through UDP broadcast or MQTT subscription. The fingerprint information includes MAC address, IP address, open port number, protocol feature field and device model identifier string; the fingerprint information is matched with a preset device feature library to identify the device type and supported protocol types; based on the identification results, device configuration information is automatically generated and stored in the device registry, and the corresponding protocol adapter instance is loaded to establish a communication connection with the device.

5. The method according to claim 4, characterized in that, Each record in the device feature database includes the device model, device type, supported communication protocols, and corresponding feature matching rules. Each field in the fingerprint information is compared with the feature matching rules one by one. When the matching degree reaches 0.85, the identification is successful. When the matching degree is between 0.5 and 0.85, it is marked as pending confirmation and prompts for manual confirmation. When the matching degree is less than 0.5, it is marked as an unknown device and the fingerprint information is recorded for the feature database to be updated.

6. The method according to claim 1, characterized in that, It also includes S5 and visual program scheduling: The backend server provides a visual timeline editor that receives user-created CUE point sequences. Each CUE point contains at least a list of device actions, execution time offset, and duration parameters. The backend server converts the execution time offset of each CUE point into an absolute execution timestamp carrying device-level delay compensation based on the unified time base and the delay characteristic parameters, forming synchronized program data and storing it. When a user creates or moves a CUE point, the backend server detects whether there are conflicting CUE points acting on the same device with the same time offset. If so, the conflicting area is highlighted and automatic adjustment suggestions are provided.

7. The method according to claim 6, characterized in that, The CUE point also includes fade-in and fade-out transition effect parameters. Multiple intermediate state instructions between the initial state and the target state are generated by an interpolation algorithm. The interpolation algorithm supports four curve types: linear, exponential, logarithmic, and S-shaped. The multiple intermediate state instructions are evenly distributed in time order within the duration parameter and are executed sequentially after being appended with an incremental timestamp based on the unified time base and delay compensation.

8. The method according to claim 1, characterized in that, It also includes S6, schedule scheduling and synchronous execution: When the scheduling engine of the backend server triggers program playback according to the schedule scheduling rules, it calls synchronous program data and sends it to the multi-protocol adapter engine; The multi-protocol adapter engine sends protocol data packets concurrently through each protocol adapter instance according to the absolute execution timestamp of each CUE point after delay compensation, so as to realize the synchronous execution of program actions; The schedule scheduling rules include execution cycle, execution time, associated program identifier and priority parameters, and when there are multiple trigger conflicts at the same time, they are arbitrated according to priority.

9. The method according to claim 1, characterized in that, It also includes S7, device health monitoring: the multi-protocol adapter engine sends heartbeat detection signals to the target device through each protocol adapter instance according to a preset heartbeat cycle, and determines that the device is offline when no response is received for more than a preset number of consecutive times; The backend server sends electrical parameter query commands to target devices that support electrical parameter feedback through a protocol adapter instance, or indirectly obtains electrical parameter data by communicating with smart meters on the device's power supply circuit; it compares real-time electrical parameters with preset thresholds, and generates tiered alarm information and notifies users through multiple channels when the thresholds are exceeded.

10. A centralized control and management system for multi-protocol equipment in cultural tourism projects, used to execute the method according to any one of claims 1 to 9, characterized in that, include: The front-end web application module provides a device control interface, a visual timeline editor interface, and a device status monitoring interface. It sends control requests via the HTTP protocol and receives device status pushes via the WebSocket protocol. The backend server module includes a multi-protocol adapter engine, a device registry, a program scheduling management unit, a schedule engine, and a device health monitoring unit; The database module is used to store device configuration information, program scheduling data, scheduling rules, and device status history. The multi-protocol adapter engine adopts a plug-in architecture and has a built-in global time base synchronization unit and a latency characteristic detection unit. The global time base synchronization unit performs clock calibration on each protocol adapter instance through NTP or PTP protocol to establish a unified time base. The latency characteristic detection unit sends a detection command to the target device during the initialization phase of each protocol adapter instance, calculates and maintains the one-way transmission latency characteristic parameters of each target device for the corresponding protocol type. The multi-protocol adapter engine adds a latency-compensated execution timestamp to the converted protocol data packets according to the unified time base and the latency characteristic parameters, so that heterogeneous devices with different network latency characteristics can perform actions synchronously at the compensated unified physical time. The device registry is used to store device configuration information and latency characteristic parameters; The program scheduling management unit is used to store the CUE point sequence and convert the execution time offset into an absolute execution timestamp carrying delay compensation, and store it as synchronous program data; The scheduling engine is used to trigger program playback according to the scheduling rules, call synchronous program data and send it to the multi-protocol adapter engine, which then executes the device actions concurrently according to the absolute execution timestamp with delay compensation. The equipment health monitoring unit is used to detect equipment malfunctions through heartbeat detection and electrical parameter monitoring.