Intelligent community multi-system fusion linkage method and system

Abstract

The application discloses a smart community multi-system fusion linkage method and system, the method comprising: acquiring system registration information of a plurality of community business systems; determining object field mapping relationship and event field mapping relationship according to a community object model and a unified event model; standardizing business object data to obtain unified community object data and generate community object association data; when a source event is generated, converting the source event into a standardized event and publishing the standardized event to an event linkage channel; matching a cross-system linkage rule based on the standardized event, determining a target community business system, a target response action and an action parameter; generating a linkage instruction according to interface adaptation information and receiving an action execution result to generate a linkage disposal record. Thus, the correlation degree of multi-source business data and the cross-business event disposal collaboration efficiency can be improved, and the business system expansion and maintenance complexity can be reduced.

Description

Technical Field

[0001] This application relates to the field of smart community system integration technology, and in particular to a method and system for the integration and linkage of multiple smart community systems. Background Technology

[0002] With the continuous improvement of digitalization in urban community management, smart communities are gradually becoming an important direction for the development of property management, public safety, convenience services, and facility operation and maintenance. Smart communities typically require digital management of various operations, including personnel access, equipment operation, on-site inspections, anomaly alarms, work order processing, and vehicle parking, to improve community operation and management efficiency and the ability to handle emergencies. In practical applications, various hardware and software systems are often deployed within the community, each undertaking different business functions and continuously generating data related to community residents, on-site conditions, and business events.

[0003] In related technologies, various business systems in smart communities are typically built and deployed separately according to specific business needs. These different systems vary in data collection methods, business object descriptions, event recording methods, and operation entry points. When community administrators need to handle cross-business scenarios, they often need to view data from multiple systems separately, rely on human experience to determine the relationships between events, and then execute subsequent handling operations through the appropriate systems. Although some smart community platforms can centrally display or interface with data from multiple business systems, they usually focus more on business data aggregation and single-function management. They still have shortcomings in data association, event coordination, handling collaboration, and rapid response across multiple business scenarios. This results in numerous human intervention steps between the discovery and handling of abnormal events, and subsequent additions of new business systems or adjustments to business handling processes are easily limited by the existing system structure and interface methods.

[0004] Therefore, in the multi-business collaborative management of smart communities, the low degree of correlation of multi-source business data within the community, the insufficient efficiency of cross-business event handling and collaboration, and the high complexity of business system expansion and maintenance have become urgent problems to be solved. Summary of the Invention

[0005] This application provides a method and system for the integration and linkage of multiple systems in a smart community, aiming to solve the problems of low correlation between multi-source business data within the community, insufficient efficiency in cross-business event handling and collaboration, and high complexity in business system expansion and maintenance in the multi-business collaborative management of existing technologies in smart communities.

[0006] Firstly, a method for the integrated and coordinated operation of multiple systems in a smart community, the method comprising: Obtain system registration information of multiple community business systems that are connected to the unified management platform of the smart community. The system registration information includes business object fields, event fields, publishable event types and executable response actions corresponding to each community business system. The multiple community business systems include at least an inspection image acquisition system, an edge intelligent analysis system and an access control management system. Based on the preset community object model and unified event model, the object field mapping relationship and event field mapping relationship corresponding to each of the community business systems are determined respectively; Based on the object field mapping relationship, the business object data reported by each community business system is standardized to obtain unified community object data, and community object association data is generated according to the object identifier, location information and object association relationship in the unified community object data. When any of the aforementioned community business systems generates a source event, the source event is converted into a standardized event based on the event field mapping relationship, and the standardized event is published to the event linkage channel; Based on the source system information, event type information, location information, and event load information in the standardized event, the pre-configured cross-system linkage rules are matched to determine the target community business system, target response action, and action parameters corresponding to the standardized event. Based on the interface adaptation information of the target community business system, the target response action and the action parameters are converted into a linkage instruction that can be executed by the target community business system, and the linkage instruction is sent to the target community business system so that the target community business system executes the corresponding response action; Receive the action execution result returned by the target community business system, and generate a linkage handling record based on the standardized event, the cross-system linkage rules and the action execution result.

[0007] Optionally, in the above solution, obtaining the system registration information of multiple community business systems accessing the unified management platform of the smart community includes: Receive system access requests sent by community business systems to be accessed, and parse the system access requests to obtain system type information, system identification information, and interface access information; Based on the system type information, obtain the business object description information, event description information, and action capability description information corresponding to the community business system to be accessed; Based on the business object description information, determine the business object fields that the community business system to be connected can report; based on the event description information, determine the event types and event fields that the community business system to be connected can publish; based on the action capability description information, determine the response actions that the community business system to be connected can execute. The system identification information, the interface access information, the business object field, the event field, the publishable event type, and the executable response action are associated and stored to obtain the system registration information.

[0008] Optionally, in the above scheme, determining the object field mapping relationship and event field mapping relationship corresponding to each of the community business systems based on the preset community object model and unified event model includes: Based on the business object fields, the object candidate mapping relationship is obtained by matching the object standard fields in the community object model with the business object fields. The event candidate mapping relationship is obtained by matching the event fields with the event standard fields in the unified event model. Perform mandatory field validation and field type validation on the candidate object mapping relationship and the candidate event mapping relationship to obtain the candidate mapping relationship that passes the validation; Configure field conversion rules for the candidate mapping relationships that have passed the verification to obtain the object field mapping relationship and the event field mapping relationship. The field conversion rules include at least one of the following: field name conversion rules, field format conversion rules, and field value conversion rules.

[0009] Optionally, in the above scheme, the standardization of business object data reported by each community business system based on the object field mapping relationship to obtain unified community object data, and the generation of community object association data based on the object identifier, location information, and object association relationship in the unified community object data, includes: Obtain the original business object data reported by the community business system, and extract object attribute data from the original business object data according to the object field mapping relationship to obtain candidate community object data; The candidate community object data is processed by object identifier completion and attribute format normalization to obtain the unified community object data. Based on the object identifier and location information in the unified community object data, the unified community object data belonging to the same community spatial range or the same business entity are associated and matched to obtain the object association relationship; The unified community object data and the object association relationship are bound together to generate the community object association data.

[0010] Optionally, in the above scheme, when any of the community business systems generates a source event, converting the source event into a standardized event based on the event field mapping relationship, and publishing the standardized event to the event linkage channel, includes: Receive a source event generated by any of the aforementioned community business systems, identify the source system identifier and source event type corresponding to the source event, and obtain the event identification result; Based on the event identification result, the corresponding event field mapping relationship is invoked, and event content data is extracted from the source event based on the event field mapping relationship to obtain candidate event data; The candidate event data is processed by generating event identifiers, normalizing timestamps, completing location information, and encapsulating event payloads to obtain the standardized events. Based on the event type and location information in the standardized event, the event publishing topic is determined, and the standardized event is published to the event linkage channel according to the event publishing topic.

[0011] Optionally, in the above scheme, the step of matching pre-configured cross-system linkage rules based on the source system information, event type information, location information, and event load information in the standardized event to determine the target community business system, target response action, and action parameters corresponding to the standardized event includes: The cross-system linkage rules are analyzed to obtain the rule triggering conditions, candidate target systems, candidate response actions, and parameter generation templates; The source system information, event type information, location information, and event load information are extracted from the standardized events, and event matching features are generated by combining them with the community object association data. The event matching features are matched with the rule triggering conditions to obtain candidate linkage rules; Based on the rule priority and action conflict handling strategy in the candidate linkage rules, the target linkage rule is determined from the candidate linkage rules; Based on the candidate target system, candidate response action, and parameter generation template in the target linkage rules, the target community business system, the target response action, and the action parameters are determined.

[0012] Optionally, in the above scheme, the step of generating a template based on the candidate target system, candidate response action, and parameters in the target linkage rules, and determining the target community business system, the target response action, and the action parameters, includes: Based on the candidate target systems, the target community business systems to be linked are determined, resulting in a target system set; Based on the candidate response actions, the target response actions corresponding to each of the target community business systems are determined, resulting in a set of target actions; A template is generated based on the parameters, and the parameters required for the action are extracted from the standardized event and the community object association data to obtain candidate action parameters. The candidate action parameters are converted in format and their integrity is verified to obtain the action parameters corresponding to the target action set.

[0013] Optionally, in the above scheme, the step of converting the target response action and the action parameters into a linkage instruction executable by the target community business system based on the interface adaptation information of the target community business system, and sending the linkage instruction to the target community business system, includes: Based on the interface adaptation information of the target community business system, determine the interface calling method and action instruction format corresponding to the target community business system; Based on the interface call method, the action instruction format, the target response action, and the action parameters, candidate linkage instructions are generated. The candidate linkage instructions are subjected to permission verification and call parameter verification to obtain the linkage instructions that pass the verification. According to the execution order corresponding to the target linkage rule, the verified linkage instruction is sent to the target community business system.

[0014] Optionally, in the above scheme, receiving the action execution result returned by the target community business system and generating a linkage handling record based on the standardized event, the cross-system linkage rules, and the action execution result includes: Receive action execution feedback returned by the target community business system in response to the linkage instruction, and obtain the action execution result; The linkage execution status is determined based on the execution result of the action, and the linkage execution status includes at least one of the following: execution success status, execution failure status, and partial execution success status. When the linkage execution status is in the execution failure state or the partial execution success state, a compensation processing strategy is determined according to the target linkage rule, and a compensation processing result is generated based on the compensation processing strategy. The standardized event, the target linkage rule, the linkage instruction, the action execution result, the linkage execution status, and the compensation processing result are associated and recorded to generate the linkage handling record.

[0015] Secondly, a smart community multi-system integrated and interconnected system, the system comprising: The system registration module is used to obtain the system registration information of multiple community business systems that are connected to the unified management platform of smart communities. The system registration information includes business object fields, event fields, publishable event types and executable response actions corresponding to each community business system. The multiple community business systems include at least an inspection image acquisition system, an edge intelligent analysis system and an access control management system. The mapping relationship determination module is used to determine the object field mapping relationship and event field mapping relationship corresponding to each of the community business systems based on the preset community object model and unified event model. The object standardization module is used to standardize the business object data reported by each of the community business systems based on the object field mapping relationship to obtain unified community object data, and generate community object association data according to the object identifier, location information and object association relationship in the unified community object data. The event standardization module is used to convert the source event into a standardized event based on the event field mapping relationship when any of the community business systems generates a source event, and to publish the standardized event to the event linkage channel. The rule matching module is used to match pre-configured cross-system linkage rules based on the source system information, event type information, location information and event load information in the standardized event, and determine the target community business system, target response action and action parameters corresponding to the standardized event; The linkage instruction generation module is used to convert the target response action and the action parameters into a linkage instruction that can be executed by the target community business system according to the interface adaptation information of the target community business system, and send the linkage instruction to the target community business system so that the target community business system executes the corresponding response action; The action record generation module is used to receive the action execution results returned by the target community business system, and generate a linkage action record based on the standardized event, the cross-system linkage rules and the action execution results.

[0016] Compared with the prior art, this application has at least the following beneficial effects: This application, based on further analysis and research into existing technological problems, recognizes that existing technologies suffer from low correlation between multi-source business data within smart communities, insufficient efficiency in cross-business event handling and collaboration, and high complexity in business system expansion and maintenance. By acquiring system registration information from multiple community business systems, it first clarifies the business object fields, event fields, publishable event types, and executable response actions of each system, enabling the unified smart community management platform to grasp the data sources and action capabilities of different systems. Furthermore, based on the community object model and unified event model, it determines the mapping relationships between object fields and event fields, and standardizes business object data and source events. This transforms information on personnel, equipment, locations, events, and actions, originally scattered across different systems, into a unified expression form. Community object association data is generated based on object identifiers, location information, and object association relationships, thereby improving the efficiency of multi-source business data. The application improves the correlation between multiple business data sources in smart communities and enhances the efficiency of cross-business event handling. It also reduces the complexity of expansion and maintenance caused by differences in system interfaces and changes in business linkage. This addresses the problems of low correlation between multiple business data sources, insufficient efficiency of cross-business event handling, and high complexity of business system expansion and maintenance in the background technology. Attached Figure Description

[0017] Figure 1 This is a flowchart illustrating a method for the integration and linkage of multiple systems in a smart community, as provided in one embodiment of this application. Detailed Implementation

[0018] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0019] In one embodiment, such as Figure 1 As shown, a method for the integrated operation of multiple systems in a smart community is provided, including the following steps: Obtain system registration information of multiple community business systems that are connected to the unified management platform of the smart community. The system registration information includes business object fields, event fields, publishable event types and executable response actions corresponding to each community business system. The multiple community business systems include at least an inspection image acquisition system, an edge intelligent analysis system and an access control management system. Based on the preset community object model and unified event model, the object field mapping relationship and event field mapping relationship corresponding to each of the community business systems are determined respectively; Based on the object field mapping relationship, the business object data reported by each community business system is standardized to obtain unified community object data, and community object association data is generated according to the object identifier, location information and object association relationship in the unified community object data. When any of the aforementioned community business systems generates a source event, the source event is converted into a standardized event based on the event field mapping relationship, and the standardized event is published to the event linkage channel; Based on the source system information, event type information, location information, and event load information in the standardized event, the pre-configured cross-system linkage rules are matched to determine the target community business system, target response action, and action parameters corresponding to the standardized event. Based on the interface adaptation information of the target community business system, the target response action and the action parameters are converted into a linkage instruction that can be executed by the target community business system, and the linkage instruction is sent to the target community business system so that the target community business system executes the corresponding response action; Receive the action execution result returned by the target community business system, and generate a linkage handling record based on the standardized event, the cross-system linkage rules and the action execution result.

[0020] In one possible implementation, the smart community multi-system integration and linkage method described in claim 1 can be executed by a unified smart community management platform. The unified smart community management platform can be deployed on a server, cloud server, edge server, or cloud-edge collaborative system in the community property management center, for unified management of business object data, business events, and linkage actions generated by different business systems within the community. The multiple community business systems include at least a patrol image acquisition system, an edge intelligent analysis system, and an access control management system. Specifically, the patrol image acquisition system can be an image acquisition system for property patrols, on-site photography, on-site video recording, and work order recording; the edge intelligent analysis system can be an edge intelligent processing system for accessing community devices, performing edge intelligent recognition, detecting device status, identifying alarm events, and generating work orders; and the access control management system can be an access control system for personnel access control, visitor management, stranger recognition, and access control device management. Through the above limitations, different business systems can have clear system identities and functional boundaries within the unified platform.

[0021] In one possible implementation, the unified management platform for smart communities obtains system registration information from multiple community business systems connected to the platform. This system registration information can be proactively reported by each community business system during registration with the platform, or it can be obtained by the platform through a preset access template, interface configuration file, or system adapter. The system registration information includes at least business object fields, event fields, publishable event types, and executable response actions. Specifically, business object fields may include personnel identifiers, device identifiers, building, floor, room number, parking space, access control point, camera point, work order object, and object status; event fields may include event identifiers, event types, event occurrence time, event occurrence location, event source, event content, event level, on-site image address, on-site video address, and work order number; publishable event types may include access events, inspection events, alarm events, work order events, device events, and parking space events; and executable response actions may include taking photos, recording video, creating work orders, tracking personnel, opening access control, switching to backup equipment, triggering alarm notifications, elevator emergency landing, and recording evidence information.

[0022] In one possible implementation, the unified management platform for smart communities determines the object field mapping relationships and event field mapping relationships corresponding to each community business system based on a preset community object model and a unified event model. The community object model is used to uniformly describe objects such as personnel, equipment, spatial locations, parking spaces, work orders, access control points, and camera points within the community. It can include object type, unique identifier, attribute information, association relationships, and event list. Attribute information can include name, location information, status, owner, creation time, and update time. Association relationships can be used to represent the ownership or business relationships between community objects; for example, a person belongs to a certain house, equipment is located on a certain floor, an access control point is associated with a certain entrance / exit, and a patrol photo is associated with a certain work order. The unified event model is used to uniformly describe events generated by different systems. It can include event ID, source system, event type, timestamp, location information, event payload, and metadata. Event payload can include personnel ID, personnel name, action, result, on-site photos, on-site videos, and work order number; metadata can include event priority, tags, and processing status.

[0023] In one possible implementation, the unified management platform for smart communities standardizes the business object data reported by various community business systems based on object field mapping relationships to obtain unified community object data. Specifically, the platform can map raw fields from different systems to standard fields in the community object model. For example, it maps "door number" in the access control management system to "device identifier," "shooting point" in the inspection image acquisition system to "location information," and "device online status" in the edge intelligent analysis system to "status." After obtaining the unified community object data, the platform generates community object association data based on the object identifier, location information, and object association relationships in the unified community object data. The community object association data can be used to characterize the correspondence between community spaces, equipment, personnel, work orders, and events, providing a basis for subsequent event linkage rule matching.

[0024] In one possible implementation, when any community business system generates a source event, the unified management platform for the smart community converts the source event into a standardized event based on the event field mapping relationship, and publishes the standardized event to the event linkage channel. The event linkage channel can be implemented using an event bus, message queue, publish-subscribe channel, or an internal event distribution channel within the platform. Source events can be stranger access events, visitor access events, or access control anomaly events generated by the access control management system; inspection anomaly reporting events, on-site evidence collection events, or work order record events generated by the inspection image acquisition system; or device offline events, fire alarm detection events, parking space occupancy events, or security alarm events generated by the edge intelligent analysis system. By converting source events from different sources into standardized events, the platform can carry event information from different systems in a unified format.

[0025] In one possible implementation, the unified management platform for smart communities matches pre-configured cross-system linkage rules based on source system information, event type information, location information, and event load information in standardized events. This determines the target community business system, target response action, and action parameters corresponding to the standardized event. Cross-system linkage rules can be generated using configuration files, a visual configuration interface, or low-code configuration. Taking low-code configuration as an example, a rule can include a rule name, triggering conditions, target system, response action, and action parameters. Triggering conditions can include matching conditions for the source system, event type, and event load fields. Action parameters can be extracted from standardized events or associated data of community objects; for example, the location in the standardized event can be used as the photo location, the personnel identifier as the personnel tracking parameter, and the alarm type as the reason for access control opening or recording.

[0026] In one possible implementation, the unified management platform for smart communities converts the target response actions and action parameters into executable linkage instructions for the target community business systems based on the interface adaptation information of the target community business systems, and then sends the linkage instructions to the target community business systems. The interface adaptation information may include the interface address, interface protocol, authentication method, parameter format, action code, and return result format of the target community business systems. Through this interface adaptation information, the platform can convert target response actions within the unified platform into interface call requests that specific systems can recognize. For example, "taking photos for evidence" is converted into a photo-taking interface request for an inspection image acquisition system, "creating a work order" is converted into a work order creation request for an edge intelligent analysis system, and "opening all access control systems" is converted into batch door-opening instructions for an access control management system.

[0027] In one possible implementation, after the target community business system executes the linkage command, it returns the action execution result to the unified smart community management platform. The action execution result may include information such as execution success, execution failure, partial success, reason for failure, execution time, returned data, on-site image address, on-site video address, and work order number. The unified smart community management platform generates linkage handling records based on standardized events, cross-system linkage rules, and action execution results. These linkage handling records can be used for subsequent auditing, retrospective analysis, operation and maintenance analysis, property management evaluation, and event closed-loop management.

[0028] For example, in a stranger tailing scenario, the access control system generates a stranger access event. The smart community unified management platform converts this event into a standardized event and publishes it to the event linkage channel. After the event matches the stranger tailing linkage rules, the platform identifies the inspection image acquisition system as one of the target community business systems and determines automatic photo recording as the target response action. Simultaneously, it identifies the edge intelligent analysis system as another target community business system and determines security tracking as the target response action. The platform generates photo-taking instructions and personnel tracking instructions respectively and receives the corresponding execution results, forming a linkage response record. As another example, in a fire alarm scenario, the edge intelligent analysis system generates a fire alarm detection event. After the platform matches the fire alarm linkage rules, it triggers the access control system to open the access control, triggers the edge intelligent analysis system to execute elevator emergency landing or alarm handling, and triggers the inspection image acquisition system to start recording, thus forming a cross-system emergency response chain.

[0029] This embodiment of the smart community unified management platform first clarifies the data fields and action capabilities of each community business system based on system registration information. Then, it transforms the scattered business object data and source events into a unified expression form through a community object model and a unified event model. Furthermore, it uses event linkage channels and cross-system linkage rules to complete target system determination, action parameter generation, linkage command issuance, and result recording. This improves the correlation between multi-source business data within the community, reduces manual switching and coordination in cross-business event handling, and lowers the dependence on modifying existing system interfaces for new linkage scenarios. This addresses the problems of low correlation between multi-source business data, insufficient efficiency in cross-business event handling collaboration, and high complexity in business system expansion and maintenance in smart community multi-business collaborative management.

[0030] In this embodiment, obtaining the system registration information of multiple community business systems accessing the unified management platform of the smart community includes: Receive system access requests sent by community business systems to be accessed, and parse the system access requests to obtain system type information, system identification information, and interface access information; Based on the system type information, obtain the business object description information, event description information, and action capability description information corresponding to the community business system to be accessed; Based on the business object description information, determine the business object fields that the community business system to be connected can report; based on the event description information, determine the event types and event fields that the community business system to be connected can publish; based on the action capability description information, determine the response actions that the community business system to be connected can execute. The system identification information, the interface access information, the business object field, the event field, the publishable event type, and the executable response action are associated and stored to obtain the system registration information.

[0031] In this embodiment, determining the object field mapping relationship and event field mapping relationship corresponding to each of the community business systems based on the preset community object model and unified event model includes: Based on the business object fields, the object candidate mapping relationship is obtained by matching the object standard fields in the community object model with the business object fields. The event candidate mapping relationship is obtained by matching the event fields with the event standard fields in the unified event model. Perform mandatory field validation and field type validation on the candidate object mapping relationship and the candidate event mapping relationship to obtain the candidate mapping relationship that passes the validation; Configure field conversion rules for the candidate mapping relationships that have passed the verification to obtain the object field mapping relationship and the event field mapping relationship. The field conversion rules include at least one of the following: field name conversion rules, field format conversion rules, and field value conversion rules.

[0032] In this embodiment, the standardization of business object data reported by each community business system based on the object field mapping relationship to obtain unified community object data, and the generation of community object association data based on the object identifier, location information, and object association relationship in the unified community object data, includes: Obtain the original business object data reported by the community business system, and extract object attribute data from the original business object data according to the object field mapping relationship to obtain candidate community object data; The candidate community object data is processed by object identifier completion and attribute format normalization to obtain the unified community object data. Based on the object identifier and location information in the unified community object data, the unified community object data belonging to the same community spatial range or the same business entity are associated and matched to obtain the object association relationship; The unified community object data and the object association relationship are bound together to generate the community object association data.

[0033] In this embodiment, when any of the community business systems generates a source event, converting the source event into a standardized event based on the event field mapping relationship, and publishing the standardized event to the event linkage channel, includes: Receive a source event generated by any of the aforementioned community business systems, identify the source system identifier and source event type corresponding to the source event, and obtain the event identification result; Based on the event identification result, the corresponding event field mapping relationship is invoked, and event content data is extracted from the source event based on the event field mapping relationship to obtain candidate event data; The candidate event data is processed by generating event identifiers, normalizing timestamps, completing location information, and encapsulating event payloads to obtain the standardized events. Based on the event type and location information in the standardized event, the event publishing topic is determined, and the standardized event is published to the event linkage channel according to the event publishing topic.

[0034] In this embodiment, the step of matching pre-configured cross-system linkage rules based on the source system information, event type information, location information, and event load information in the standardized event to determine the target community business system, target response action, and action parameters corresponding to the standardized event includes: The cross-system linkage rules are analyzed to obtain the rule triggering conditions, candidate target systems, candidate response actions, and parameter generation templates; The source system information, event type information, location information, and event load information are extracted from the standardized events, and event matching features are generated by combining them with the community object association data. The event matching features are matched with the rule triggering conditions to obtain candidate linkage rules; Based on the rule priority and action conflict handling strategy in the candidate linkage rules, the target linkage rule is determined from the candidate linkage rules; Based on the candidate target system, candidate response action, and parameter generation template in the target linkage rules, the target community business system, the target response action, and the action parameters are determined.

[0035] In this embodiment, the step of generating a template based on the candidate target system, candidate response action, and parameters in the target linkage rules, and determining the target community business system, the target response action, and the action parameters, includes: Based on the candidate target systems, the target community business systems to be linked are determined, resulting in a target system set; Based on the candidate response actions, the target response actions corresponding to each of the target community business systems are determined, resulting in a set of target actions; A template is generated based on the parameters, and the parameters required for the action are extracted from the standardized event and the community object association data to obtain candidate action parameters. The candidate action parameters are converted in format and their integrity is verified to obtain the action parameters corresponding to the target action set.

[0036] In this embodiment, the step of converting the target response action and the action parameters into an executable linkage instruction for the target community business system based on the interface adaptation information of the target community business system, and sending the linkage instruction to the target community business system, includes: Based on the interface adaptation information of the target community business system, determine the interface calling method and action instruction format corresponding to the target community business system; Based on the interface call method, the action instruction format, the target response action, and the action parameters, candidate linkage instructions are generated. The candidate linkage instructions are subjected to permission verification and call parameter verification to obtain the linkage instructions that pass the verification. According to the execution order corresponding to the target linkage rule, the verified linkage instruction is sent to the target community business system.

[0037] In this embodiment, receiving the action execution result returned by the target community business system and generating a linkage handling record based on the standardized event, the cross-system linkage rules, and the action execution result includes: Receive action execution feedback returned by the target community business system in response to the linkage instruction, and obtain the action execution result; The linkage execution status is determined based on the execution result of the action, and the linkage execution status includes at least one of the following: execution success status, execution failure status, and partial execution success status. When the linkage execution status is in the execution failure state or the partial execution success state, a compensation processing strategy is determined according to the target linkage rule, and a compensation processing result is generated based on the compensation processing strategy. The standardized event, the target linkage rule, the linkage instruction, the action execution result, the linkage execution status, and the compensation processing result are associated and recorded to generate the linkage handling record.

[0038] In one embodiment, a method for three-dimensional fusion of multiple systems in a smart community is provided, including: Step S1: Establish a unified data model, which includes a community object model and a unified event model; Step S2: The watermark camera, smart body box, and access control brain systems standardize their data according to the unified data model described above; Step S3: Establish an event linkage engine, subscribe to events from various systems, and configure cross-system linkage rules; Step S4: When an event is generated by the source system, the event is standardized into a unified event model and published to the event bus; Step S5: The event linkage engine matches the linkage rules, routes the event to the target system, and executes the response action.

[0039] The community object model includes object type, unique identifier, attribute information, association relationship, and event list. The attribute information includes name, location, status, owner, creation time, and update time.

[0040] The unified event model includes event ID, source system, event type, timestamp, location information, event payload, and metadata. The event payload includes personnel ID, personnel name, action, result, on-site photos, on-site videos, and work order number.

[0041] The linkage rules in step S3 are configured using YAML format, including rule name, triggering conditions, target system, and response action. The triggering conditions include matching the source system, event type, and event load field.

[0042] This embodiment also includes a low-code extension step: when adding a new system, it is only necessary to adapt to the unified data model interface, register to the event bus, and configure the linkage rules. There is no need to modify the existing system, and the access cycle is shortened from 2-4 weeks to 2-4 days.

[0043] This embodiment also includes typical linkage scenarios: Stranger tailing linkage: When the access control brain detects a stranger passing through, it triggers the watermark camera to automatically take pictures and record, and triggers the smart body box security agent to track, with a response time of <300ms; Fire alarm linkage: When the smart box detects a fire alarm, it triggers the access control brain to open all access control doors, triggers the smart box to force the elevator to land on the first floor, and triggers the watermark camera to start recording. The response time is less than 100ms. Inspection detection linkage: When the watermark camera detects an anomaly and reports it, the smart agent box is triggered to create a work order, with a response time of <500ms; Parking space occupancy linkage: When the smart box detects that a parking space is occupied, it triggers the watermark camera to take a picture for evidence and triggers the smart box to create a parking relocation work order, with a response time of <500ms.

[0044] In one embodiment, a cross-system event linkage method is provided, applied to a smart community scenario, including: Step S1: The source system generates events and standardizes these events into a unified event model; Step S2: Publish the standardized event to the event bus; Step S3: The event linkage engine subscribes to the event bus and matches the pre-configured linkage rules; Step S4: Determine the target system and response action based on the matching linkage rules; Step S5: Route the event to the target system and execute the response action; Step S6: Record the linkage log and return the execution result.

[0045] In this embodiment, the linkage rule matching in step S3 specifically includes: The triggering conditions of the linkage rules are parsed, including the matching of source system, event type, and event load fields; Iterate through all linkage rules, and when the source system, event type, and event load fields all match, it is considered a successful match; When a match is successful, obtain the target system and response action; When multiple rules match successfully, they are executed in order of priority.

[0046] The specific actions to perform in step S5 include: Transform the response action into an interface call to the target system; Execute the API call and wait for the result. When the execution is successful, a success log is recorded; When execution fails, a failure log is recorded and an alarm notification is triggered.

[0047] This embodiment also includes a step for dynamically updating linkage rules: Supports dynamically adding, modifying, and deleting linkage rules at runtime; After the linkage rules are updated, they will take effect without restarting the system; It supports version management of linkage rules and allows rollback to historical versions.

[0048] In one embodiment, a smart community multi-system integrated and interconnected system is provided, comprising: The system registration module is used to obtain the system registration information of multiple community business systems that are connected to the unified management platform of smart communities. The system registration information includes business object fields, event fields, publishable event types and executable response actions corresponding to each community business system. The multiple community business systems include at least an inspection image acquisition system, an edge intelligent analysis system and an access control management system. The mapping relationship determination module is used to determine the object field mapping relationship and event field mapping relationship corresponding to each of the community business systems based on the preset community object model and unified event model. The object standardization module is used to standardize the business object data reported by each of the community business systems based on the object field mapping relationship to obtain unified community object data, and generate community object association data according to the object identifier, location information and object association relationship in the unified community object data. The event standardization module is used to convert the source event into a standardized event based on the event field mapping relationship when any of the community business systems generates a source event, and to publish the standardized event to the event linkage channel. The rule matching module is used to match pre-configured cross-system linkage rules based on the source system information, event type information, location information and event load information in the standardized event, and determine the target community business system, target response action and action parameters corresponding to the standardized event; The linkage instruction generation module is used to convert the target response action and the action parameters into a linkage instruction that can be executed by the target community business system according to the interface adaptation information of the target community business system, and send the linkage instruction to the target community business system so that the target community business system executes the corresponding response action; The action record generation module is used to receive the action execution results returned by the target community business system, and generate a linkage action record based on the standardized event, the cross-system linkage rules and the action execution results.

[0049] The specific implementation details of each module can be found in the above description of the methods for integrating and linking multiple systems in a smart community, and will not be repeated here.

[0050] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

Claims

1. A method for the integrated linkage of multiple systems in a smart community, characterized in that, The method, applied to a unified management platform for smart communities, includes: Obtain system registration information of multiple community business systems that are connected to the unified management platform of the smart community. The system registration information includes business object fields, event fields, publishable event types and executable response actions corresponding to each community business system. The multiple community business systems include at least an inspection image acquisition system, an edge intelligent analysis system and an access control management system. Based on the preset community object model and unified event model, the object field mapping relationship and event field mapping relationship corresponding to each of the community business systems are determined respectively; Based on the object field mapping relationship, the business object data reported by each community business system is standardized to obtain unified community object data, and community object association data is generated according to the object identifier, location information and object association relationship in the unified community object data. When any of the aforementioned community business systems generates a source event, the source event is converted into a standardized event based on the event field mapping relationship, and the standardized event is published to the event linkage channel; Based on the source system information, event type information, location information, and event load information in the standardized event, the pre-configured cross-system linkage rules are matched to determine the target community business system, target response action, and action parameters corresponding to the standardized event. Based on the interface adaptation information of the target community business system, the target response action and the action parameters are converted into a linkage instruction that can be executed by the target community business system, and the linkage instruction is sent to the target community business system so that the target community business system executes the corresponding response action; Receive the action execution result returned by the target community business system, and generate a linkage handling record based on the standardized event, the cross-system linkage rules and the action execution result.

2. The method for multi-system integration and linkage in smart communities according to claim 1, characterized in that, The process of obtaining system registration information for multiple community business systems connected to the unified management platform of the smart community includes: Receive system access requests sent by community business systems to be accessed, and parse the system access requests to obtain system type information, system identification information, and interface access information; Based on the system type information, obtain the business object description information, event description information, and action capability description information corresponding to the community business system to be accessed; Based on the business object description information, determine the business object fields that the community business system to be connected can report; based on the event description information, determine the event types and event fields that the community business system to be connected can publish; based on the action capability description information, determine the response actions that the community business system to be connected can execute. The system identification information, the interface access information, the business object field, the event field, the publishable event type, and the executable response action are associated and stored to obtain the system registration information.

3. The method for multi-system integration and linkage in smart communities according to claim 2, characterized in that, The step of determining the object field mapping relationship and event field mapping relationship corresponding to each of the community business systems based on the preset community object model and unified event model includes: Based on the business object fields, the object candidate mapping relationship is obtained by matching the object standard fields in the community object model with the business object fields. The event candidate mapping relationship is obtained by matching the event fields with the event standard fields in the unified event model. Perform mandatory field validation and field type validation on the candidate object mapping relationship and the candidate event mapping relationship to obtain the candidate mapping relationship that passes the validation; Configure field conversion rules for the candidate mapping relationships that have passed the verification to obtain the object field mapping relationship and the event field mapping relationship. The field conversion rules include at least one of the following: field name conversion rules, field format conversion rules, and field value conversion rules.

4. The method for multi-system integration and linkage in smart communities according to claim 1, characterized in that, Based on the object field mapping relationship, the business object data reported by each of the community business systems is standardized to obtain unified community object data. Then, based on the object identifier, location information, and object association relationships in the unified community object data, community object association data is generated, including: Obtain the original business object data reported by the community business system, and extract object attribute data from the original business object data according to the object field mapping relationship to obtain candidate community object data; The candidate community object data is processed by object identifier completion and attribute format normalization to obtain the unified community object data. Based on the object identifier and location information in the unified community object data, the unified community object data belonging to the same community spatial range or the same business entity are associated and matched to obtain the object association relationship; The unified community object data and the object association relationship are bound together to generate the community object association data.

5. The method for multi-system integration and linkage in smart communities according to claim 4, characterized in that, When any of the community business systems generates a source event, the source event is converted into a standardized event based on the event field mapping relationship, and the standardized event is published to the event linkage channel, including: Receive a source event generated by any of the aforementioned community business systems, identify the source system identifier and source event type corresponding to the source event, and obtain the event identification result; Based on the event identification result, the corresponding event field mapping relationship is invoked, and event content data is extracted from the source event based on the event field mapping relationship to obtain candidate event data; The candidate event data is processed by generating event identifiers, normalizing timestamps, completing location information, and encapsulating event payloads to obtain the standardized events. Based on the event type and location information in the standardized event, the event publishing topic is determined, and the standardized event is published to the event linkage channel according to the event publishing topic.

6. The method for multi-system integration and linkage in smart communities according to claim 5, characterized in that, The process involves matching pre-configured cross-system linkage rules based on the source system information, event type information, location information, and event load information in the standardized event to determine the target community business system, target response action, and action parameters corresponding to the standardized event, including: The cross-system linkage rules are analyzed to obtain the rule triggering conditions, candidate target systems, candidate response actions, and parameter generation templates; The source system information, event type information, location information, and event load information are extracted from the standardized events, and event matching features are generated by combining them with the community object association data. The event matching features are matched with the rule triggering conditions to obtain candidate linkage rules; Based on the rule priority and action conflict handling strategy in the candidate linkage rules, the target linkage rule is determined from the candidate linkage rules; Based on the candidate target system, candidate response action, and parameter generation template in the target linkage rules, the target community business system, the target response action, and the action parameters are determined.

7. The method for multi-system integration and linkage in smart communities according to claim 6, characterized in that, The step of generating a template based on the candidate target system, candidate response action, and parameters in the target linkage rules, and determining the target community business system, the target response action, and the action parameters, includes: Based on the candidate target systems, the target community business systems to be linked are determined, resulting in a target system set; Based on the candidate response actions, the target response actions corresponding to each of the target community business systems are determined, resulting in a set of target actions; A template is generated based on the parameters, and the parameters required for the action are extracted from the standardized event and the community object association data to obtain candidate action parameters. The candidate action parameters are converted in format and their integrity is verified to obtain the action parameters corresponding to the target action set.

8. The method for multi-system integration and linkage in smart communities according to claim 7, characterized in that, The step of converting the target response action and the action parameters into an executable linkage instruction for the target community business system based on the interface adaptation information of the target community business system, and sending the linkage instruction to the target community business system, includes: Based on the interface adaptation information of the target community business system, determine the interface calling method and action instruction format corresponding to the target community business system; Based on the interface call method, the action instruction format, the target response action, and the action parameters, candidate linkage instructions are generated. The candidate linkage instructions are subjected to permission verification and call parameter verification to obtain the linkage instructions that pass the verification. According to the execution order corresponding to the target linkage rule, the verified linkage instruction is sent to the target community business system.

9. The method for multi-system integration and linkage in smart communities according to claim 8, characterized in that, The step of receiving the action execution result returned by the target community business system and generating a linkage handling record based on the standardized event, the cross-system linkage rules, and the action execution result includes: Receive action execution feedback returned by the target community business system in response to the linkage instruction, and obtain the action execution result; The linkage execution status is determined based on the execution result of the action, and the linkage execution status includes at least one of the following: execution success status, execution failure status, and partial execution success status. When the linkage execution status is in the execution failure state or the partial execution success state, a compensation processing strategy is determined according to the target linkage rule, and a compensation processing result is generated based on the compensation processing strategy. The standardized event, the target linkage rule, the linkage instruction, the action execution result, the linkage execution status, and the compensation processing result are associated and recorded to generate the linkage handling record.

10. A smart community multi-system integrated linkage system, characterized in that, The system includes: The system registration module is used to obtain the system registration information of multiple community business systems that are connected to the unified management platform of smart communities. The system registration information includes business object fields, event fields, publishable event types and executable response actions corresponding to each community business system. The multiple community business systems include at least an inspection image acquisition system, an edge intelligent analysis system and an access control management system. The mapping relationship determination module is used to determine the object field mapping relationship and event field mapping relationship corresponding to each of the community business systems based on the preset community object model and unified event model. The object standardization module is used to standardize the business object data reported by each of the community business systems based on the object field mapping relationship to obtain unified community object data, and generate community object association data according to the object identifier, location information and object association relationship in the unified community object data. The event standardization module is used to convert the source event into a standardized event based on the event field mapping relationship when any of the community business systems generates a source event, and to publish the standardized event to the event linkage channel. The rule matching module is used to match pre-configured cross-system linkage rules based on the source system information, event type information, location information and event load information in the standardized event, and determine the target community business system, target response action and action parameters corresponding to the standardized event; The linkage instruction generation module is used to convert the target response action and the action parameters into a linkage instruction that can be executed by the target community business system according to the interface adaptation information of the target community business system, and send the linkage instruction to the target community business system so that the target community business system executes the corresponding response action; The action record generation module is used to receive the action execution results returned by the target community business system, and generate a linkage action record based on the standardized event, the cross-system linkage rules and the action execution results.

Images