An outdoor travel and culture landscape performance linkage control system and method

Abstract

The application provides an outdoor travel and culture landscape performance linkage control system and method, a communication equipment model is constructed, basic information and extended attributes of the communication equipment are defined; new equipment is added, and a communication instruction analysis template and a function instruction set of the new equipment are constructed; a fault rule library is constructed according to the type of the equipment; a to-be-accessed equipment is created as an accessed equipment, a fusion performance program is prepared, a performance time period is set, and a light program, a linkage effect and a corresponding trigger time point of the accessed equipment are prepared according to requirements; state data of the accessed equipment in a performance scene execution process are collected in real time, whether the current equipment type is in the fault rule library is matched, and a fault or a fault recovery is generated based on a matching result. The application can quickly respond to the online demand of a travel project, realize multi-system performance linkage control, and improve the experience and operation efficiency of a night tour project.

Description

TECHNICAL FIELD

[0001] The present application relates to the field of cultural tourism intelligence, and specifically relates to an outdoor cultural tourism landscape performance linkage control system and method. BACKGROUND ART

[0002] Night tours have become a new scenario that meets the demands for in-depth experience and social communication. The traditional mode of scenic spots where visitors only sightsee during the daytime and leave at night can no longer adapt to the needs of industrial upgrading. Extending tourists' staying time through night tours and tapping the potential of secondary consumption has become a common consensus in the industry.

[0003] At present, the integration of cultural IP with technologies such as light and shadow shows and immersive performances has become a core means to attract tourists. Cases such as the Tang Dynasty Ever-bright City in Xi'an and the Zigong Lantern Festival have verified the traffic effect of culture + technology. However, with the continuous launch of night tour cultural tourism projects, problems of fragmented multi-systems and the lack of integrated management and control modes are widespread in the industry. The specific manifestations are limitations in device protocol adaptation and insufficient model compatibility, which lead to the inability to quickly respond to the launch requirements of cultural tourism projects, and the failure of multi-system performance linkage control, which seriously affects the experience and operation efficiency of night tour projects. SUMMARY OF THE INVENTION

[0004] In view of the shortcomings in the prior art, the present application provides an outdoor cultural tourism landscape performance linkage control system and method.

[0005] In order to solve the above technical problems, the present application is achieved through the following technical solutions.

[0006] An outdoor cultural tourism landscape performance linkage control system, comprising: a communication device model construction module, configured to define basic information, extended attributes and communication protocols of the communication device to construct a communication device model; a new device parsing module, configured to add a new device, construct a communication instruction parsing template and a functional instruction set for the new device, support parsing and assembling of hexadecimal protocols and JSON format protocols, so as to be compatible with protocols of devices from different manufacturers; a fault rule base construction module, configured to construct a fault rule base according to the type of the device; a device access and configuration module, configured to create a to-be-accessed device as an accessed device, wherein when the accessed device is a performance device, importing of materials is supported; when the accessed device is an intelligent control device, defining a protocol parsing format according to the manufacturer protocol of the accessed device, and configuring each service control instruction; a program compilation module, configured to compile integrated performance programs, set performance time periods, and compile lighting programs, linkage effects and corresponding trigger time points of the accessed device as required. The fault handling module is used to collect the status data of the access device in real time during the execution of the scenario and match whether the current device type is in the fault rule base, and generate or restore the fault based on the matching result.

[0007] As one possible implementation, the communication device model construction module is specifically configured as follows: The basic information definition unit is used to define the basic information of the communication device; wherein, the basic information of the communication device includes type code, type name, device category, device manufacturer, version, status detection method, status detection mechanism, and detection time; An extended attribute definition unit is used to define extended attributes for different types of communication devices; wherein, the extended attributes of the communication device include English device name, Chinese device name, whether it is required, data type, and default value; The protocol definition unit is used to define the communication protocols, message formats, and connection modes of different types of communication devices.

[0008] As one possible implementation, the newly added device parsing module includes a hexadecimal instruction set construction submodule, which is specifically configured as follows: The first message format definition unit is used to define the message format; wherein, the message format includes the verification flag, version flag, validation flag, data area length and position in the identifier protocol message header; The first instruction set construction unit is used to construct the functional instruction set. When the function code is a receive data instruction, the bytes in the data area are identified, and the data content of the corresponding length is extracted according to the data type and data size, and bound to a custom identifier. When the function code is a send data instruction, the identifier and the size of the corresponding data are defined in the template, and the data is filled to generate a data packet when the instruction is called.

[0009] As one possible implementation, the newly added device parsing module includes a JSON instruction set construction submodule, which is specifically configured as follows: The second message format definition unit is used to define the message format; wherein, the message format includes field identifier name, data type and data size; The second instruction set construction unit is used to construct a functional instruction set. It defines the identifier, data type, and data size of each field based on the key-value pattern, and maps the data according to the identifier, data type, and data size of each field when parsing or assembling data packets.

[0010] As one possible implementation, the fault rule base construction module includes the following rule content: alarm source, device type, alarm level, validity period, triggering condition, alarm type, whether to automatically process, recovery condition, timeout shutdown mechanism, and whether to enable whitelist policy; wherein, the alarm source includes threshold alarm and service alarm, and the triggering condition includes communication status, current, voltage, and power parameters.

[0011] As one possible implementation, the device access and configuration module includes an access device creation unit, which is used to add the device to be accessed and set the basic information and device parameters of the device to be accessed; wherein, The basic information of the device to be connected includes the device code, device name, device type, device model, device specifications, project to which it belongs, device address, and parent device. The device parameters of the device to be connected are attribute parameters related to the dynamic linkage of the device to be connected.

[0012] As one possible implementation, the program compilation module is specifically configured as follows: When the access device is a landscape lighting fixture, the relative time point of the performance and the program to be performed are configured; wherein, the program to be performed includes video footage; When the access device is a cultural and tourism device, the relative time point of the performance and the performance scene are configured; wherein, the performance scene includes video material, light pole material and music material; When the access device is a linkage device, the relative time point of linkage and the linkage scenario are configured; wherein, the linkage device includes fountains and fog forests, and the linkage scenario includes combinations of control commands; When the access device is a high-voltage electrical device, the relative time point of the configuration control and the control scenario are configured; wherein, the control scenario includes the opening and closing of the loop.

[0013] As one possible implementation, both the linkage device and the high-voltage equipment support synchronous triggering mode and sequential triggering mode; wherein, The synchronous triggering mode adopts a multi-threaded task mechanism and triggers in batches through a time trigger mode. The sequential triggering mode triggers instructions in sequence by defining the delay time for each instruction.

[0014] As one possible implementation, when the fault handling module matches a fault rule base, it includes: Based on the status data of the access device, check whether the device exists in the whitelist; if it does, no fault is generated. Based on the status data of the access device, determine whether the data reporting time is within the set time period; if not, no fault is generated. Based on the status data of the access device, the triggering conditions are verified; if they are not met, no fault is generated. Based on the status data of the access device, the fault information to be generated is compared with the fault database. If the fault exists in the fault database, the fault is updated; otherwise, a fault is generated. Based on the status data of the access device, determine whether the fault database meets the recovery conditions; if so, restore the fault information.

[0015] A method for coordinated control of outdoor cultural tourism landscape performances, applied to any of the systems described above, includes the following steps: Define the basic information, extended attributes, and communication protocols of the communication device to construct a communication device model; Add new devices and construct communication instruction parsing templates and function instruction sets for the new devices, supporting the parsing and assembly of hexadecimal and JSON format protocols to ensure compatibility with protocols from different manufacturers; Build a fault rule base based on the type of equipment; Create the device to be connected as an access device. When the access device is a rendering device, it supports importing materials. When the access device is an intelligent control device, define the protocol parsing format according to the manufacturer's protocol of the access device and configure each service control command. Compile integrated performance programs, set performance time periods, and compile lighting programs, linkage effects, and corresponding trigger time points for the access devices according to requirements; The system collects and matches the status data of the access devices during the execution of the scenario in real time, checks whether the current device type is in the fault rule base, and generates or recovers faults based on the matching results. This application, by adopting the above technical solution, has significant technical effects: (1) It realizes the flexible construction and unlimited expansion of the device model, and improves the system compatibility. This application constructs a communication device model, defines the communication attributes, management attributes and business attributes of the device, and supports the unlimited expansion of attributes. It breaks the limitation of traditional systems on specific device types, so that the system can adapt to the access of hardware devices from different manufacturers and of different types, solves the problem of insufficient model compatibility in the prior art, and lays the foundation for the integration of multiple business scenarios.

[0016] (2) This application enables multi-device fusion performance and unified arrangement, improving the system's linkage control capabilities. It configures corresponding attributes based on the type of device to be connected and sets the performance time period, trigger time point, and performance content within a unified fusion performance program. This allows the system to integrate heterogeneous devices into the same timeline for unified arrangement and control, solving the problem of linkage control failure caused by the fragmentation of traditional multi-system systems, and realizing the integrated group control of various businesses such as landscape, cultural tourism, and control equipment.

[0017] (3) Intelligent closed-loop fault handling is achieved, improving the system's operation and maintenance efficiency and stability. This application constructs a fault rule base, collects equipment status data in real time for matching, and automatically generates fault information or recovery information based on the matching results, while simultaneously notifying users via message push. This mechanism achieves automated closed-loop processing from fault discovery and judgment to notification, eliminating the need for manual real-time polling of equipment status. It effectively solves the problems of delayed fault response and difficult operation and maintenance under traditional methods, ensuring the stable execution of outdoor cultural tourism performance scenarios. Attached Figure Description

[0018] To more clearly illustrate the technical solutions in the embodiments of this application 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 this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0019] Figure 1 This is an overall schematic diagram of an embodiment of the system in this application; Figure 2 This is a schematic diagram of the processing flow of an embodiment of the system in this application; Figure 3 This is a schematic diagram of the processing flow of the fault handling module in the system embodiment of this application; Figure 4 This is a flowchart illustrating an embodiment of the method of this application. Detailed Implementation

[0020] The present application will be further described in detail below with reference to the embodiments. The following embodiments are explanations of the present application, but the present application is not limited to the following embodiments. Unless otherwise specified, the features in the following embodiments can be combined with each other.

[0021] Example 1: In one embodiment, an outdoor cultural tourism landscape performance linkage control system, such as Figure 1 and Figure 2As shown, it includes a communication equipment model construction module 100, a new equipment parsing module 200, a fault rule base construction module 300, a device access and configuration module 400, a program compilation module 500, and a fault handling module 600.

[0022] The communication equipment model building module 100 is used to construct communication equipment models. In specific implementations, communication equipment includes, but is not limited to, landscape equipment, cultural and tourism equipment, fountain equipment, and music equipment. These communication devices come from different brands and manufacturers, and their models may vary. Therefore, it is necessary to define models for these communication devices. For each type of communication equipment, its communication attributes, management attributes, and business attributes are defined, and the attributes can be infinitely expanded.

[0023] In another embodiment, the communication device model construction module 100 includes a basic information definition unit, an extended attribute definition unit, and a protocol definition unit.

[0024] The basic information definition unit is used to define the basic information of the communication device; wherein, the type code, type name, device category, device manufacturer, version, status detection method, and status detection mechanism are defined, and the status detection mechanism is divided into supported or unsupported.

[0025] The extended attribute definition unit is used to define extended attributes for different types of communication devices; wherein, the extended attributes include English device name, Chinese device name, whether it is required, data type, and default value, etc.

[0026] The protocol definition unit is used to define the communication protocols, message formats, and connection modes of different types of communication devices.

[0027] A new device parsing module 200 is added to add devices and construct the communication instruction parsing template and function instruction set of the added devices. It supports the parsing and assembly of hexadecimal protocol and JSON format protocol to be compatible with the protocols of devices from different manufacturers. It includes a device addition submodule, a hexadecimal instruction set construction submodule and a JSON instruction set construction submodule.

[0028] A new device submodule is added to create the device to be accessed as an access device, and calls the communication device model construction module 100 to configure basic information and extended attributes for the access device, thereby completing the basic access configuration of the device to be accessed.

[0029] In another embodiment, the hexadecimal instruction set construction submodule is specifically configured as follows: The first message format definition unit is used to define the message format; wherein, the message format includes the verification flag, version flag, validation flag, data area length and position in the identifier protocol message header.

[0030] The first instruction set construction unit is used to construct the function instruction set. For different function codes, a parsing template is constructed. Specifically: (1) When the function code is a receive data instruction, each byte in the data area is identified and mapped to the data area according to the defined protocol. The data is parsed according to the data size defined in the protocol, and the corresponding length of data content is extracted according to the data type and data size. For example, 4 bytes are extracted from the data area for int type, 4 bytes are extracted from the data area for float type, and 1 byte is extracted from the data area for byte type. The extracted data content is bound to a custom identifier. (2) When the function code is a send data instruction, the identifier and the size of the corresponding data are defined in the template according to the definition of the protocol format. When the send instruction is called, the instruction in the instruction set is called to fill the identifier data to quickly generate a complete data packet.

[0031] In another embodiment, the JSON instruction set construction submodule is specifically configured as follows: The second message format definition unit is used to define the message format; wherein, the message format includes field identifier name, data type and data size.

[0032] The second instruction set construction unit is used to build functional instruction sets. Based on different functions, it constructs corresponding instruction protocol parsing templates, specifically: defining the identifier, data type, and data size of each field using a key-value pattern, and mapping based on the field identifiers during data packet parsing or assembly. Parsing or assembling data packets involves parsing based on the identifier, data type, and data size of each field.

[0033] The fault rule base construction module 300 is used to build a fault rule base according to the type of equipment.

[0034] In another embodiment, different fault alarm rules are constructed according to the type of device. The rule content of the fault rule base includes: alarm source, device type, alarm level, validity period, triggering condition, alarm type, whether to automatically process, recovery condition, timeout shutdown mechanism, and whether to enable whitelist policy. The alarm source includes threshold alarms and service alarms. The triggering condition includes communication status, current, voltage and power parameters. The device includes all devices that have been connected and those that are to be connected.

[0035] Device status data is reported, and after reporting, it is matched against rules for the corresponding device type and alarm source as threshold alarm. Based on these rules, judgments are made and processed. For example, when the current is less than a set current, a current fault alarm is triggered; when the voltage is less than a set threshold voltage, an undervoltage alarm is triggered. A whitelist operation is supported to exclude specific devices from detection within the validity period.

[0036] The device access and configuration module 400 is used to create a device to be accessed as an access device. When the access device is a rendering device, it supports importing materials; when the access device is an intelligent control device, it defines the protocol parsing format according to the manufacturer's protocol of the access device and configures various service control commands. The device access and configuration module includes an access device creation unit and a device configuration unit. In another embodiment, the access device creation unit is used to add the device to be accessed and set the basic information and device parameters of the device to be accessed; wherein, the basic information of the device to be accessed includes the device code, device name, device type, device model, device specifications, project to which it belongs, device address, and parent device; the device parameters of the device to be accessed are attribute parameters related to the dynamic linkage of the device to be accessed, for example, the device parameters corresponding to the power gateway device include gateway number, meter mounting, transformer ratio coefficient, manufacturer name, etc.

[0037] In another embodiment, the device configuration unit is used to determine the type of the access device and perform differentiated configuration according to different types. Specifically, when the access device is a performance device, such as a lighting effect performance device, it supports importing materials, including but not limited to lighting materials, video materials, image materials, music materials, etc.; when the access device is an intelligent control device, such as a fountain or fog system, it defines the protocol parsing format according to the manufacturer's protocol of the access device and configures various business control instructions to achieve protocol adaptation of devices from different manufacturers.

[0038] The program production module 500 is used to produce integrated performance programs. In practice, the performance time period is first set, and then the lighting program of the performance equipment is produced according to the performance requirements on site, and the corresponding trigger time point is set. The linkage effect of the intelligent control equipment is also produced and the trigger time point is set.

[0039] In another embodiment, the program compilation module is specifically configured as follows: When the access device is a landscape lighting fixture (performance device), the relative time point of the performance and the program to be performed are configured; wherein, the program to be performed includes video material.

[0040] When the access device is a cultural and tourism device (performance device), the relative time point of the performance and the performance scene are configured; wherein, the performance scene includes video material, light pole material and music material.

[0041] When the access device is a linked device (intelligent control device), the relative time point and the linked scenario are configured; wherein, the linked device includes a fountain, a fog system, and the linked scenario includes a combination of control commands. The linked device supports protocols including TCP, UDP, ARTNET, OSC, and Modbus, etc.

[0042] When the access device is a high-voltage electrical device (intelligent control device), the relative time point of the control and the control scenario are configured; wherein, the control scenario includes the opening and closing of the loop.

[0043] In another embodiment, the intelligent control devices (linkage devices and power equipment) both support synchronous triggering mode and sequential triggering mode; wherein, the synchronous triggering mode adopts a multi-threaded task mechanism and performs batch triggering through time trigger mode; the sequential triggering mode defines the delay time for each instruction triggering and triggers the instructions sequentially.

[0044] Fault handling module 600, such as Figure 3 As shown, the system is used to collect the status data of the access devices during the execution of the scenario simulation in real time, match the current device type with the fault rule base, and generate or recover faults based on the matching results. The scenario simulation can be executed manually as needed on-site, or it can be automatically executed at preset times by setting a schedule.

[0045] In another embodiment, when the fault processing module 600 matches the fault rule base, the process is as follows: (1) When a fault rule base is matched: (1.1) Verify whether the device exists in the whitelist based on the collected data (status data of the access device). If the device exists, no fault is generated.

[0046] (1.2) Verify whether the data reporting time is within the set time period based on the collected data. If it is not within the set time period, no fault will be generated.

[0047] (1.3) Verify the triggering conditions based on the collected data. If the conditions are not met, no fault will be generated.

[0048] (1.4) Based on the collected data, the fault information to be generated is compared with the fault database. If the fault exists in the fault database, the fault is updated. If the fault does not exist in the fault database, the fault is generated.

[0049] (1.5) Determine whether the fault database meets the recovery conditions based on the collected data. If it does, restore the fault information.

[0050] The generated or recovered fault information is notified to the responsible person via push notification, which can be sent via SMS, WeChat, or internal system messages.

[0051] (2) When no fault rule base is matched, the process is exited and no fault information is generated.

[0052] Example 2: A method for coordinated control of outdoor cultural and tourism landscape performances, such as Figure 4 As shown, the method applied to the above system includes the following steps: S100: Define the basic information, extended attributes, and communication protocols of the communication device to construct a communication device model; S200: Add a new device and build the communication instruction parsing template and function instruction set for the new device, supporting the parsing and assembly of hexadecimal protocol and JSON format protocol to be compatible with the protocols of devices from different manufacturers; S300: Build a fault rule base based on the type of equipment; S400: Create the device to be accessed as an access device. When the access device is a rendering device, it supports importing materials. When the access device is an intelligent control device, it defines the protocol parsing format according to the manufacturer's protocol of the access device and configures various service control instructions. S500: Compile integrated performance programs, set performance time periods, and compile lighting programs, linkage effects, and corresponding trigger time points for the access devices according to requirements; S600: Real-time acquisition of the status data of the access devices during the execution of the scenario and matching whether the current device type is in the fault rule base, and generation or recovery of faults based on the matching results. All changes and modifications made without departing from the spirit and scope of this application, and all equivalent technical solutions, also fall within the scope of this application.

[0053] The various embodiments in this specification are described in a progressive manner, with each embodiment focusing on the differences from other embodiments. The same or similar parts between the various embodiments can be referred to each other.

[0054] Those skilled in the art will understand that embodiments of this application can be provided as methods, apparatus, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0055] This application is described with reference to flowchart illustrations and / or block diagrams of the method, terminal device (system), and computer program product according to this application. It should be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing terminal device to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing terminal device, generate instructions for implementing the flowchart. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0056] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing terminal device to operate in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0057] These computer program instructions can also be loaded onto a computer or other programmable data processing terminal equipment, causing a series of operational steps to be performed on the computer or other programmable terminal equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable terminal equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0058] It should be noted that: The phrase "an embodiment" or "an embodiment" used in this specification means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of this application. Therefore, the phrase "an embodiment" or "an embodiment" appearing in various places throughout the specification does not necessarily refer to the same embodiment.

[0059] Furthermore, it should be noted that the shapes and names of the parts and components described in the specific embodiments described in this specification may differ. All equivalent or simple variations made to the structure, features, and principles described in this application are included within the scope of protection of this application. Those skilled in the art to which this application pertains may make various modifications or additions to the described specific embodiments or use similar methods to substitute them, as long as they do not deviate from the structure of this application or exceed the scope defined by the claims, all of which should fall within the scope of protection of this application.

Claims

1. A linkage control system for outdoor cultural tourism landscape performances, characterized in that, include: The communication device model building module is used to define the basic information, extended attributes, and communication protocols of the communication device to build a communication device model. A new device parsing module is added to add devices and construct the communication instruction parsing template and function instruction set for the added devices. It supports the parsing and assembly of hexadecimal protocol and JSON format protocol to ensure compatibility with the protocols of devices from different manufacturers. The fault rule base construction module is used to build a fault rule base according to the type of equipment. The device access and configuration module is used to create the device to be accessed as an access device. When the access device is a rendering device, it supports importing materials. When the access device is an intelligent control device, the protocol parsing format is defined according to the manufacturer's protocol of the access device, and the various service control instructions are configured. The program production module is used to produce integrated performance programs, set performance time periods, and produce lighting programs, linkage effects, and corresponding trigger time points for the access devices according to requirements. The fault handling module is used to collect the status data of the access device in real time during the execution of the scenario and match whether the current device type is in the fault rule base, and generate or restore the fault based on the matching result.

2. The system according to claim 1, characterized in that, The communication device model construction module is specifically configured as follows: The basic information definition unit is used to define the basic information of the communication device; wherein, the basic information of the communication device includes type code, type name, device category, device manufacturer, version, status detection method, status detection mechanism, and detection time; An extended attribute definition unit is used to define extended attributes for different types of communication devices; wherein, the extended attributes of the communication device include English device name, Chinese device name, whether it is required, data type, and default value; The protocol definition unit is used to define the communication protocols, message formats, and connection modes of different types of communication devices.

3. The system according to claim 1, characterized in that, The newly added device parsing module includes a hexadecimal instruction set construction submodule, which is specifically configured as follows: The first message format definition unit is used to define the message format; wherein, the message format includes the verification flag, version flag, validation flag, data area length and position in the identifier protocol message header; The first instruction set construction unit is used to construct the functional instruction set. When the function code is a receive data instruction, the bytes in the data area are identified, and the data content of the corresponding length is extracted according to the data type and data size, and bound to a custom identifier. When the function code is a send data instruction, the identifier and the size of the corresponding data are defined in the template, and the data is filled to generate a data packet when the instruction is called.

4. The system according to claim 1, characterized in that, The newly added device parsing module includes a JSON instruction set construction submodule, which is specifically configured as follows: The second message format definition unit is used to define the message format; wherein, the message format includes field identifier name, data type and data size; The second instruction set construction unit is used to construct a functional instruction set. It defines the identifier, data type, and data size of each field based on the key-value pattern, and maps the data according to the identifier, data type, and data size of each field when parsing or assembling data packets.

5. The system according to claim 1, characterized in that, In the fault rule base construction module The rules in the fault rule base include: alarm source, device type, alarm level, validity period, triggering condition, alarm type, whether to handle automatically, recovery condition, timeout shutdown mechanism, and whether to enable whitelist policy; wherein, the alarm source includes threshold alarms and service alarms, and the triggering condition includes communication status, current, voltage, and power parameters.

6. The system according to claim 1, characterized in that, The device access and configuration module includes an access device creation unit, which is used to add the device to be accessed and set the basic information and device parameters of the device to be accessed; wherein... The basic information of the device to be connected includes the device code, device name, device type, device model, device specifications, project to which it belongs, device address, and parent device. The device parameters of the device to be connected are attribute parameters related to the dynamic linkage of the device to be connected.

7. The system according to claim 1, characterized in that, The program compilation module is specifically configured as follows: When the access device is a landscape lighting fixture, the relative time point of the performance and the program to be performed are configured; wherein, the program to be performed includes video footage; When the access device is a cultural and tourism device, the relative time point of the performance and the performance scene are configured; wherein, the performance scene includes video material, light pole material and music material; When the access device is a linkage device, the relative time point of linkage and the linkage scenario are configured; wherein, the linkage device includes fountains and fog forests, and the linkage scenario includes combinations of control commands; When the access device is a high-voltage electrical device, the relative time point of the configuration control and the control scenario are configured; wherein, the control scenario includes the opening and closing of the loop.

8. The system according to claim 7, characterized in that, Both the linkage device and the high-voltage equipment support synchronous triggering mode and sequential triggering mode; wherein... The synchronous triggering mode adopts a multi-threaded task mechanism and triggers in batches through a time trigger mode. The sequential triggering mode triggers instructions in sequence by defining the delay time for each instruction.

9. The outdoor cultural tourism landscape performance linkage control system according to claim 1, characterized in that, When the fault handling module matches a fault rule base, it includes: Based on the status data of the access device, check whether the device exists in the whitelist; if it does, no fault is generated. Based on the status data of the access device, determine whether the data reporting time is within the set time period; if not, no fault is generated. Based on the status data of the access device, the triggering conditions are verified; if they are not met, no fault is generated. Based on the status data of the access device, the fault information to be generated is compared with the fault database. If the fault exists in the fault database, the fault is updated; otherwise, a fault is generated. Based on the status data of the access device, determine whether the fault database meets the recovery conditions; if so, restore the fault information.

10. A method for coordinated control of outdoor cultural tourism landscape performances, characterized in that, The system applied to any one of claims 1-9 includes the following steps: Define the basic information, extended attributes, and communication protocols of the communication device to construct a communication device model; Add new devices and construct communication instruction parsing templates and function instruction sets for the new devices, supporting the parsing and assembly of hexadecimal and JSON format protocols to ensure compatibility with protocols from different manufacturers; Build a fault rule base based on the type of equipment; Create the device to be connected as an access device. When the access device is a rendering device, it supports importing materials. When the access device is an intelligent control device, define the protocol parsing format according to the manufacturer's protocol of the access device and configure each service control command. Compile integrated performance programs, set performance time periods, and compile lighting programs, linkage effects, and corresponding trigger time points for the access devices according to requirements; The system collects and matches the status data of the access devices during the execution of the scenario in real time, checks whether the current device type is in the fault rule base, and generates or recovers faults based on the matching results.

Images