CN114827253B - Intelligent building networking system based on cloud edge object model - Google Patents
Intelligent building networking system based on cloud edge object model Download PDFInfo
- Publication number
- CN114827253B CN114827253B CN202210346144.7A CN202210346144A CN114827253B CN 114827253 B CN114827253 B CN 114827253B CN 202210346144 A CN202210346144 A CN 202210346144A CN 114827253 B CN114827253 B CN 114827253B
- Authority
- CN
- China
- Prior art keywords
- unit
- data
- service
- request
- interface
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 230000006855 networking Effects 0.000 title claims description 5
- 238000003032 molecular docking Methods 0.000 claims abstract description 16
- 230000001360 synchronised effect Effects 0.000 claims description 18
- 238000000034 method Methods 0.000 claims description 11
- 238000012550 audit Methods 0.000 claims description 9
- 230000000737 periodic effect Effects 0.000 claims description 9
- 238000012545 processing Methods 0.000 claims description 6
- 238000012546 transfer Methods 0.000 claims description 5
- 210000001503 joint Anatomy 0.000 claims description 4
- 230000008569 process Effects 0.000 claims description 4
- 238000013507 mapping Methods 0.000 claims description 3
- 238000004806 packaging method and process Methods 0.000 claims description 3
- 238000004140 cleaning Methods 0.000 claims 1
- 238000010586 diagram Methods 0.000 description 10
- 238000011160 research Methods 0.000 description 6
- 230000006872 improvement Effects 0.000 description 3
- 230000008859 change Effects 0.000 description 2
- 238000010276 construction Methods 0.000 description 2
- 238000005259 measurement Methods 0.000 description 2
- 238000012163 sequencing technique Methods 0.000 description 2
- 238000013475 authorization Methods 0.000 description 1
- 238000013480 data collection Methods 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 230000009191 jumping Effects 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
- XLYOFNOQVPJJNP-UHFFFAOYSA-N water Substances O XLYOFNOQVPJJNP-UHFFFAOYSA-N 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computing Systems (AREA)
- Health & Medical Sciences (AREA)
- General Health & Medical Sciences (AREA)
- Medical Informatics (AREA)
- Computer Hardware Design (AREA)
- Computer Security & Cryptography (AREA)
- General Engineering & Computer Science (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The invention discloses an intelligent building internet of things system based on cloud edge object models, which has various docking cloud forms, simple standardized definition of the object models, simple application docking and reasonable service data utilization. The invention discloses an Internet of things system based on a cloud edge object model, which comprises a manufacturer system (1), a project end (2), a cloud Internet of things platform (3) and an application end (4); the project end (2) also comprises a system data acquisition unit (29) and a system theme reporting unit (210); the cloud internet of things platform (3) further comprises a system object model (39); one end of the system theme reporting unit (210) is connected with the system data acquisition unit (29), and the other end of the system theme reporting unit is connected with the system object model (39).
Description
Technical Field
The invention belongs to the technical field of internet of things platforms, and particularly relates to an intelligent building internet of things system based on a cloud edge object model.
Background
In the field of intelligent building internet of things, equipment is generally divided according to system types, wherein the system generally refers to systems in a building, such as a power supply and distribution system, a water supply and drainage system and the like, the category refers to category classification of equipment of a certain type of system, such as a power supply and distribution system, the category classification generally comprises high-voltage power distribution equipment, a low-voltage power distribution cabinet, standby power supply equipment, a low-voltage power distribution cabinet and the like, the category refers to types of equipment of a certain type of system, such as the type of the high-voltage power distribution equipment category comprises a high-voltage incoming cabinet, a high-voltage metering cabinet, a high-voltage outgoing cabinet, a high-voltage power distribution cabinet, a high-voltage contact cabinet and the like. Each device category has a system category type attribute, typically specifying standard measurement points, i.e., attributes, events and services, for the system category type.
What is called the object model, studies are on attributes, events and services. The attribute is a device measuring point and represents which numerical characteristics or capability data display the device has; the event is triggered by an intelligent system, such as regional intrusion alarm, and the time, position, image snapshot or video file information of the event need to be reported; the service is a task that the business request of the application side needs to cooperatively complete on the project, such as door opening operation of the access control system.
Equipment object model mainly studied is an object model established by equipment attributes, equipment events and equipment services, and the object relationship is referred to fig. 1. The equipment attribute is usually a measuring point of the equipment, taking an access control system/an access control card reader as an example, and mainly comprises a door position, a card name, an event state, a security state, a card number, a switch state, an operation state and the like; the equipment events mainly comprise card synchronization events, pass events, faults, pass prohibition events, alarm events, face synchronization events and the like; the equipment service mainly comprises the steps of obtaining a property two-dimensional code, obtaining a visitor two-dimensional code, adding face authorization information, locking a door, opening a door, adding/deleting personnel information and the like.
The existing cloud-edge-based internet of things platform adopts the distributed structure of fig. 2, and comprises a manufacturer system, a project end, a cloud-end internet of things platform and an application end. The cloud internet of things is accessed by using equipment, the data reporting mode adopts equipment attributes (namely measuring points) to report the data, or events and services are added to the equipment, and the data reporting mode adopts the equipment attributes, the equipment events and the equipment services to report the data.
As shown in fig. 2, the manufacturer system includes individual intelligent systems within individual buildings.
As shown in fig. 2, the project end includes a device data acquisition unit 21, a message queue 22, a device theme reporting unit 23, a service logic analysis unit 24, a data configuration and display unit 25, a database 26, a device periodic history data unit 27, and a system external interface unit 28. The device data acquisition unit 21 is connected with the message queue 22 and the data configuration and display unit 25; the message queue 22 is connected with the device data acquisition unit 21, the device theme reporting unit 23, the business logic analysis unit 24 and the device periodicity historical data unit 27; the business logic analysis unit 24 is connected with the database 26, the data configuration and display unit 25 is connected with the database 26 and the user, and the system external interface unit is connected with the database 26 and the application.
As shown in fig. 2, the cloud internet of things platform includes a device model 31, a business logic analysis unit 32, a database 33, a data configuration and presentation unit 34, a message queue 35, an API interface service 36, a history data unit 37, and a log audit 38. The equipment object model 31 is externally connected with the equipment theme reporting unit 23, and internally connected with the API interface service 36, the historical data unit 37 and the business logic analysis unit 32 respectively; the business logic analysis unit 32 is respectively connected with the equipment object model 31, the database 33, the message queue 35 and the API interface service 36; the database 33 is respectively connected with the data configuration and display unit 34, the history data unit 37, the business logic analysis unit 32 and the API interface service 36; the data configuration and display unit 34 is connected with the user externally and connected with the database 33 internally; the message queue 35 is respectively connected with the business logic analysis unit 32, the log audit 38 and the application software 41; the API interface service 36 is connected to the equipment model 31, the business logic analysis unit 32, the database 33, and the application software 41, respectively; the historical data unit 37 is connected with the equipment object model 31 and the database 33 respectively; the log audit 38 is coupled to the message queue 35.
However, the above-mentioned internet of things platform has the following drawbacks:
1. the docking cloud is single in form and limited to the equipment object model. For system access where certain business data is not study-object-oriented by a single device or a combination of multiple devices, it is not straightforward to define a device object model. Such as a parking lot system, obtain a travel record of a certain period of time, or TOP10 ranking of the number of vehicle travel per month, etc.
2. The standardized definition of object models is difficult. When a service requirement defines a device service standardization definition, the service itself is separated from a fixed device and cannot be defined.
3. The application docking platform interface is relatively complex. The standard interfaces provided by the internet of things platform are limited, the number of application ends of the internet of things platform items is increased, the requirements are continuously changed, diversified application requirements are acquired from the limited standard interfaces, and the application ends can be indirectly acquired only by performing secondary data processing necessarily; secondly, the standardized interface is established by the dimension of the equipment, the range is relatively narrow, and when the system is used as the dimension for data statistics, the requirement is difficult to directly meet.
4. And repeating construction of service data. If the parking lot system is used, the application end obtains the ranking of the entering times of TOP10 vehicles per month, and supposing that the manufacturer has such records, the cloud application needs to perform secondary processing and repeated storage of data.
In summary, the problems with the prior art are: the cloud edge object model-based internet of things system has the advantages of single butt-joint cloud end form, difficulty in defining equipment object models, complex butt-joint of internet of things platform interfaces and repeated construction of service data.
Disclosure of Invention
The invention aims to provide an intelligent building networking system based on a cloud edge object model, which has various docking cloud forms, simple standardized definition of the object model, simple application docking and reasonable service data utilization.
The technical scheme for realizing the purpose of the invention is as follows:
an intelligent building internet of things system based on a cloud edge object model comprises a manufacturer system, a project end, a cloud end internet of things platform and an application end;
the project end also comprises a system data acquisition unit and a system theme reporting unit; the cloud internet of things platform further comprises a system object model;
the system data acquisition unit is used for south-facing docking manufacturer systems and north-facing pushing equipment attributes, system events and system service data;
the system theme reporting unit is used for acquiring system events and system services from the system data acquisition unit, reporting the system events to the cloud internet of things platform, transmitting the system data acquisition unit according to the application end system service request transmitted by the cloud internet of things platform, and returning the system service request to complete a service result in an original way;
the system object model is used for meeting the requirements of project end butt joint and other units of the cloud end for obtaining system object model data to provide support;
one end of the system theme reporting unit is connected with the system data acquisition unit, and the other end of the system theme reporting unit is connected with the system object model.
Compared with the prior art, the invention has the remarkable advantages that:
1. the docking cloud forms are various: according to the invention, events and services are reconstructed from the dimension of the system, the system is supported to be connected with the cloud end, and the system which is not a single device or a combination of a plurality of devices and is a study object can be connected without directly defining a device object model; the docking cloud has various forms;
2. the standardized definition of the object model is simple: the invention constructs event and service definition from the system, solves the problem that service data is not a pain point of system access taking a single device as a research object or a plurality of devices as a research object;
3. the application docking is simple: taking inquiring a parking lot system and a travel record of a certain period of time as an example, the method of the slave equipment object model is that the architecture diagram can refer to fig. 2, and application software firstly needs to acquire which equipment of the parking lot system from an internet of things platform interface; secondly, circularly acquiring records of a certain period of time through the equipment; integrating the records of the devices again, sequencing the records according to time, and packaging the data for use; the method of the slave system object model can be realized by only one step of API request. The specific method is that the architecture diagram can refer to fig. 3 and 4, a parking lot travel record of a certain period of time is acquired through a generalized synchronous API request interface of system service, request data is directly forwarded to a project end, and the project end returns an API request result.
4. And (3) reasonably utilizing service data: by adopting the Internet of things system, when the intelligent manufacturer effective data exists in the manufacturer, the service request of the business can be submitted to the project end in a system object model access mode, and the project end directly returns the result, so that the business data can be reasonably utilized.
The invention is described in further detail below with reference to the drawings and the detailed description.
Drawings
FIG. 1 is a schematic diagram of the object relationships of a prior art plant model.
Fig. 2 is a schematic structural diagram of an internet of things system based on a cloud edge object model in the prior art.
Fig. 3 is a schematic structural diagram of the intelligent building internet of things system based on cloud edge object model.
Fig. 4 is an internal structural view of the system object model in fig. 3.
FIG. 5 is a schematic diagram of the object relationships of the system object model.
FIG. 6 is a timing diagram of the intelligent building networking system of FIG. 3 based on cloud edge object model.
In the figure, a manufacturer system 1, a project end 2, a cloud Internet of things platform 3, an application end 4, an intelligent manufacturer system 11,
the system comprises a device data acquisition unit 21, a first message queue 22, a device subject reporting unit 23, a first business logic analysis unit 24, a first data configuration and display unit 25, a first database 26, a device periodic history data unit 27, a system external interface unit 28, a system data acquisition unit 29, a system subject reporting unit 210,
equipment object model 31, second business logic analysis unit 32, second database 33, second data configuration and presentation unit 34, second message queue 35, api interface service 36, historical data unit 37, log audit 38, system object model 39,
an external network interface 391, an api request service unit 392, a data configuration unit 393, a heartbeat interface unit 394, a synchronous interface unit 395, an asynchronous interface unit 396, a data push unit 397, a memory database 398, a service request unit 399, an unstructured data transfer unit 3910, an edge login queue 3911, a task queue unit 3912, a service analysis unit 3913, an edge login authentication unit 3914, a protocol transfer unit 3915 and a data receiving unit 3916.
Detailed Description
As shown in FIG. 3, the intelligent building Internet of things system based on the cloud edge object model comprises a manufacturer system 1, a project end 2, a cloud end Internet of things platform 3 and an application end 4.
The factory system 1 includes individual intelligent factory systems 11 within an intelligent building.
The project end 2 comprises a device data acquisition unit 21, a first message queue 22, a device theme reporting unit 23, a first business logic analysis unit 24, a first data configuration and display unit 25, a first database 26, a device periodic history data unit 27 and a system external interface unit 28.
The device data acquisition unit 21 is externally connected with the intelligent manufacturer system 11, and internally connected with the first message queue 22 and the first data configuration and display unit 25 respectively;
the device theme reporting unit 23 is externally connected with the cloud internet of things platform 3, and internally connected with the first message queue 22;
the first business logic analysis unit 24 is connected to the first message queue 22 and the first database 26, respectively;
the input of the device periodic history data unit 27 is connected to the first message queue 22 and the output is connected to the first database 26;
the system external interface unit 28 has an input connected to the first message queue 22 and an output connected to the first database 26;
the output of the first data configuration and presentation unit 25 is connected to a first database 26.
The device data acquisition unit 21 is configured to acquire the device data configured by the first data configuration and display unit 25, perform data docking with a southbound intelligent manufacturer system, map the measurement point address of the manufacturer to a device attribute, push the changed attribute value to the first message queue 22, and use the device code as the identifier for the pushed theme;
a first message queue 22 for carrying all device theme data hubs and providing device data to each required unit.
The device theme reporting unit 23 is configured to implement two functions, namely, subscribe all device data to the first message queue 22, clean the data according to a configuration rule, and report the cleaned data to the device object model 31 according to device attributes; secondly, subscribing the equipment topic data of all the item ends to the equipment object model 31 to realize the equipment control of the item ends by the cloud;
the first business logic analysis unit 24 is configured to obtain data of statistics required to be completed for the page from the first database 26, and store the analyzed result into the first database 26, such as alarm rules, scene linkage, and statistical related information of object models;
a first data configuration and display unit 25 for configuring and displaying system data to a user;
a first database 26 for storing structured data and unstructured data, wherein the structured data comprises user configuration data, equipment status and attribute records, alarm rules, scene linkage records, equipment attribute periodic historical data and the like; unstructured data includes files, pictures, video, and the like;
a device periodicity history data unit 27, configured to obtain the stored device and periodicity rule configured by the user from the first database 26, and store device attribute data;
an external interface unit 28 of the system, which is used for providing real-time, history and application control data support for the project-side application;
the above composition and connection relationship are the same as those of the prior art.
The improvement points of the invention are that:
object relation improvement: modifying from fig. 1 to fig. 5, the system and services under the system class type in fig. 1 are associated under the system.
The structural relationship is improved, as shown in fig. 3, namely, the project end 2 further comprises:
the system data acquisition unit 29 is used for docking the system of the intelligent manufacturer in the south direction and pushing the data of equipment attributes, system events and system services in the north direction;
the system theme reporting unit 210 is configured to acquire a system event and a system service from the system data acquisition unit 29, report the system event to the cloud internet of things platform 3, forward the system service request to the system data acquisition unit 29 according to the application end 4 system service request forwarded by the cloud internet of things platform 3, and return a system service request to complete a service result.
The system event adopts a data uplink mode to report the platform; the system service is that the application software 41 issues a request to the system object model 39, and forwards the request to the system theme reporting unit 210, and then forwards the request to the system data acquisition unit 29, where the service request is completed, and the result is returned in the original way.
As shown in fig. 3, the cloud internet of things platform 3 includes a device object model 31, a second business logic analysis unit 32, a second database 33, a second data configuration and presentation unit 34, a second message queue 35, an API interface service 36, a history data unit 37, and a log audit 38. The equipment object model 31 is externally connected with the equipment theme reporting unit 23, and internally connected with the API interface service 36, the historical data unit 37 and the second business logic analysis unit 32 respectively; the second business logic analysis unit 32 is respectively connected with the equipment object model 31, the second database 33, the second message queue 35 and the API interface service 36; the second database 33 is connected to the second data configuration and presentation unit 34, the history data unit 37, the second business logic analysis unit 32 and the API interface service 36, respectively; the second data configuration and display unit 34 is connected to the user externally and to the second database 33 internally; the second message queue 35 is respectively connected with the second business logic analysis unit 32, the log audit 38 and the application software 41; the API interface service 36 is connected to the equipment object model 31, the second business logic analysis unit 32, the second database 33, and the application software 41, respectively; the historical data unit 37 is connected with the equipment model 31 and the second database 33 respectively; the log audit 38 is coupled to the second message queue 35.
As an improvement of the present invention, the cloud internet of things platform 3 further includes:
the system object model 39 is used for meeting the requirements of the project end docking and other units in the cloud to acquire system object model data to provide support, and the detailed description jumps to fig. 4;
the system object model 39 is externally connected with the system theme reporting unit 210, and internally connected with the business logic analysis unit 32, the API interface service 36 and the historical data unit 37 respectively;
as shown in fig. 4, the internal structure of the system object model 39 in fig. 3 is schematically shown.
The system object model 39 includes:
an external network interface 391 for physically connecting other elements in fig. 3;
an API request service unit 392, configured to initiate a service data request to the system' object model by an application end;
the heartbeat interface unit 393 is used for classifying the service requests of the API request service unit 392 for requesting interfaces and is used for keeping heartbeats by the application account and the object model;
a data configuration unit 394, configured to classify the service request of the API request service unit 392 request interface, and set a user callback address;
a synchronization interface unit 395, configured to classify the service request of the API request service unit 392 for requesting the interface, where the application end requests the service data from the project end, and the request is a return result;
an asynchronous interface unit 396, which classifies the service request of the interface requested by the API request service unit 392, and is used for the application end to request the service data from the project end, and the request is a multiple return result;
a data pushing unit 397, configured to push a system event, or forward a service request initiated by the asynchronous interface unit 396;
the memory database 398 is used for side login information and state, service analysis information and the like;
the structured data comprises platform data such as the state of project end service, the record of a system object model, equipment attribute record, alarm rule, scene linkage record and the like;
unstructured data includes file storage services, object storage services, and the like;
a service request unit 399, configured to interact with the side login queue 3911 in order to query whether the project side system is online, in a data request processing procedure of the synchronous interface unit 395 or the asynchronous interface unit 396;
an unstructured data transferring unit 3910, configured to transfer unstructured data to a memory database 398, where the unstructured data includes data such as files, videos, and pictures;
an edge login queue 3911 for storing basic information of the project end login;
the task queue unit 3912 is configured to store data request information of the synchronous interface unit 395 or the asynchronous interface unit 396, so as to facilitate service analysis;
the service analysis unit 3913 is configured to unpack the received network data, and then process the service;
an edge login authentication unit 3914 for authenticating and authenticating an item end login;
the service forwarding unit 3915 is configured to package a request for service data and forward the package to the project end;
a service receiving unit 3916 configured to collect network data;
the API request service unit 392 is connected to the external network interface 391, the heartbeat interface unit 393, the data configuration unit 394, the synchronous interface unit 395, and the asynchronous interface unit 396, respectively;
the memory database 398 is respectively connected to the heartbeat interface unit 393, the data configuration unit 394, the service request unit 399, the edge login queue 3911 and the service analysis unit 3913;
the side login authentication unit 3914 is connected to the external network interface 391 and the side login queue 3911 respectively;
the side login queue 3911 is further connected to a service request unit 399;
the service request unit 399 is also connected with a synchronous interface unit 395, a task queue unit 3912 and an asynchronous interface unit 396, respectively;
the service forwarding unit 3915 is connected to the task queue unit 3912 and the external network interface 391;
the data pushing unit 397 is respectively connected with the external network interface 391, the unstructured data transferring unit 3910 and the service analyzing unit 3913;
the data receiving unit 3916 is connected to the service analyzing unit 3913 and the external network interface 391;
the service resolving unit 3913 is further connected to the task queue unit 3912.
Fig. 6 is a processing timing diagram of the intelligent building internet of things based on the cloud edge object model.
The working process of the present invention will be described in detail with reference to fig. 6:
1) Initializing: the intelligent manufacturer logs in with the project end system object model;
2) And (3) login: the project end system object model is registered with the cloud system object model.
3) Login returns: the project end object model logs in the cloud;
4) And (3) platform login: the application end logs in to an Internet of things platform;
5) Setting a callback: the application end receives a data return interface pushed by the platform, and mainly returns a system event and an asynchronous request interface;
6) Timing maintenance heartbeat packet: a timing heartbeat is established between the application end and the platform, so that the platform can timely sense the existence of the application end;
7) Subscribing to device properties: the application end obtains real-time data of equipment attributes;
8) Device attribute change: when the measuring point of the manufacturer equipment changes, the data is forwarded to the project end equipment object model;
9) Reporting device attributes: mapping the equipment measuring points of the manufacturer into equipment attributes, and reporting the equipment attributes to a cloud equipment object model;
10 Rule forwarding: the equipment object model is normally and regularly forwarded, and massive equipment data are forwarded to a message queue;
11 Push device attribute data): pushing the equipment data to an application end by a message queue, wherein the premise of pushing is that the application end subscribes to the attribute data of the equipment;
wherein steps 7) to 11) are device attribute processes;
12 Manufacturer event change: namely, the project end system object model receives the event of the manufacturer;
13 Reporting system events): the event of the manufacturer is received, and the event of the manufacturer is converted into a system event according to the event mapping relation and is forwarded to a cloud system object model;
14 Push system event): namely, the system object model pushes the event to the application end;
15 Synchronous interface service request): namely, an application end initiates a synchronous service data request to a platform, which refers to system service;
16 Forwarding the synchronous service request: namely, the system object model forwards the system service to the project end;
17 Organizing service request data): namely, after the project end receives the system service, judging whether the data is required to be requested again from the manufacturer at present, if not, jumping to 20), otherwise, continuing;
18 Request vendor data: namely, the project end system service initiates a business data request to a manufacturer;
19 Return manufacturer data: namely, the project end system service receives manufacturer data;
20 Synchronous service request return): namely, the system service data is returned;
21 Return synchronous service request): namely, the application end receives the system service return;
22 Asynchronous request interface return: when the system service needs to return for a plurality of times, the flow repeats steps 15) to 21), and the current step is continuously executed.
23 Continuously pushing asynchronous request data; i.e. the application receives the subsequent data of the system service.
The working steps of the system event are 12) to 10);
the working steps of the synchronous interface of the system service are 15) to 21);
the asynchronous interface working steps of the system service are 15) to 23).
According to the invention, the system data acquisition unit 29 and the system theme reporting unit 210 are additionally arranged in the project end 2, and the system object model 39 is additionally arranged in the cloud internet of things platform 3. The following advantages are obtained:
according to the system, events and services are reconstructed from the dimension of the system, the system object model is supported to be in butt joint with the cloud end, the butt joint cloud end is diversified, and the technical problem of system access for a research object which does not take a single device as the research object or a plurality of devices as the research object is solved; as shown in fig. 3, the data link relationship of the system object model is, in order, application software 41, API interface service 38, system object model 39, system topic reporting unit 210, system data collection unit 29, and intelligent vendor system 11.
The invention constructs event and service definition from the system, solves the technical problem that the service data is not a single device or a plurality of devices are combined to be a research object; the standardized definition of the object model is simple.
The application docking is simple. Taking inquiring a parking lot system and a travel record of a certain period of time as an example, the method of the slave equipment object model is that the architecture diagram can refer to fig. 2, and application software firstly needs to acquire which equipment of the parking lot system from an internet of things platform interface; secondly, circularly acquiring records of a certain period of time through the equipment; integrating the records of the devices again, sequencing the records according to time, and packaging the data for use; the method of the slave system object model can be realized by only one step of API request. Specifically, referring to fig. 3, the architecture diagram may refer to fig. 3, where the application software 41 needs to call a synchronous API request interface of the system object model 39, obtain a travel record of a parking lot for a certain period of time, directly forward the system service to the system theme reporting unit 210, then forward the system service to the system data collecting unit 29 by the system theme reporting unit 210, complete a service request of the system service by the system data collecting unit 29, and return a result in a return path.
By adopting the Internet of things system, when the intelligent manufacturer effective data exists in the manufacturer, the service request of the business can be submitted to the project end in a system object model access mode, and the project end directly returns the result, so that the business data can be reasonably utilized.
Claims (1)
1. An intelligent building networking system based on a cloud edge object model comprises a manufacturer system (1), a project end (2), a cloud end Internet of things platform (3) and an application end (4); the method is characterized in that:
the project end (2) also comprises a system data acquisition unit (29) and a system theme reporting unit (210); the cloud internet of things platform (3) further comprises a system object model (39);
the system data acquisition unit (29) is used for pushing data of equipment attributes, system events and system services in the north direction of the south direction docking manufacturer system (1);
the system theme reporting unit (210) is used for acquiring system events and system services from the system data acquisition unit (29), reporting the system events to the cloud internet of things platform (3), forwarding the system service requests to the system data acquisition unit (29) according to the application end (4) forwarded by the cloud internet of things platform (3), and returning the system service requests to complete service results in the original way;
the system object model (39) is used for meeting the requirements of project end docking and other units in the cloud to acquire system object model data for providing support;
one end of the system theme reporting unit (210) is connected with the system data acquisition unit (29), and the other end of the system theme reporting unit is connected with the system object model (39);
the manufacturer system (1) comprises intelligent manufacturer systems (11) in intelligent buildings;
the project end (2) further comprises a device data acquisition unit (21), a first message queue (22), a device theme reporting unit (23), a first business logic analysis unit (24), a first data configuration and display unit (25), a first database (26), a device periodic historical data unit (27) and a system external interface unit (28);
the device data acquisition unit (21) is used for acquiring the device data configured by the first data configuration and display unit (25), performing data butt joint with a southward intelligent manufacturer system, mapping the measuring point address of the manufacturer into device attributes, pushing the changed attribute values to the first message queue (22), and adopting device codes as identifiers for the pushed subjects;
a first message queue (22) for carrying all device theme data hubs providing device data to each required unit;
the device theme reporting unit (23) is used for subscribing all device data from the first message queue (22), cleaning the data according to configuration rules, and reporting the cleaned data to the device object model (31) according to device attributes; the cloud terminal is used for subscribing the equipment topic data of all the item terminals to the equipment object model (31) so as to realize the equipment control of the item terminals by the cloud terminal;
the first business logic analysis unit (24) is used for acquiring data of statistics required to be completed of the page from the first database (26), and storing the analyzed result into the first database (26);
a first data configuration and presentation unit (25) for configuring and presenting system data to a user;
a first database (26) for storing structured data and unstructured data, the structured data comprising user configuration data, device status and attribute records, alarm rules, scene linkage records, device attribute periodic history data; unstructured data includes files, pictures and video;
a device periodicity history data unit (27) for acquiring stored devices and periodicity rules configured by a user from the first database (26) and storing device attribute data;
an external interface unit (28) of the system is used for providing real-time, historical and application control data support for project-side applications;
the device data acquisition unit (21) is externally connected with the intelligent manufacturer system (11), and is internally connected with the first message queue (22) and the first data configuration and display unit (25) respectively;
the device theme reporting unit (23) is externally connected with the cloud internet of things platform (3), and internally connected with the first message queue (22);
the first business logic analysis unit (24) is respectively connected with the first message queue (22) and the first database (26);
the input end of the periodic history data unit (27) of the equipment is connected with the first message queue (22), and the output end of the periodic history data unit is connected with the first database (26);
the system is characterized in that the input end of an external interface unit (28) is connected with a first message queue (22), and the output end of the external interface unit is connected with a first database (26);
the output end of the first data configuration and display unit (25) is connected with a first database (26);
the system data acquisition unit (29) and the system theme reporting unit (210) are connected with the first message queue (22), and the system data acquisition unit (29) is connected with the intelligent manufacturer system (11) in the south direction;
the cloud internet of things platform (3) further comprises an equipment object model (31), a second business logic analysis unit (32), a second database (33), a second data configuration and display unit (34), a second message queue (35), an API interface service (36), a historical data unit (37) and a log audit (38);
the equipment object model (31) is externally connected with the equipment theme reporting unit (23), and is internally connected with the second business logic analysis unit (32), the API interface service (36) and the historical data unit (37) respectively;
the second business logic analysis unit (32) is also respectively connected with a second database (33), a second message queue (35), an API interface service (36) and a system object model (39);
the second message queue (35) is also respectively connected with a log audit (38) and application software (41);
the second database (33) is further connected to a second data configuration and presentation unit (34), a history data unit (37) and an API interface service (36), respectively;
the API interface service (36) is also respectively connected with a system object model (39) and application software (41);
the system object model (39) comprises:
an external network interface (391) for physical connection of the internal unit to an external network;
an API request service unit (392) for the application end to initiate a service data request to the system object model;
the heartbeat interface unit (393) is used for classifying the service requests of the API request service unit (392) requesting interfaces and is used for keeping heartbeats by applying account numbers and object models;
a data configuration unit (394) for classifying the service requests of the API request service unit (392) request interface and setting the callback address of the user;
a synchronous interface unit (395) for classifying the service requests of the API request service unit (392) request interface, which is used for the application end to request the service data to the project end, and the request is a return result;
an asynchronous interface unit (396) for classifying the service requests of the API request service unit (392) request interface, which is used for the application end to request the service data to the project end, and the request is a multi-time return result;
a data pushing unit (397) for pushing system events or forwarding service requests initiated by the asynchronous interface unit (396);
the memory database (398) is used for storing side login information, state and service analysis information;
a service request unit (399) for interacting with the side login queue (3911) to inquire whether the project side system is on-line in the data request processing process of the synchronous interface unit (395) or the asynchronous interface unit (396);
an unstructured data transferring unit (3910) for transferring unstructured data into an in-memory database (398) comprising file, video and picture data;
an edge login queue (3911) for storing basic information of the project end login;
the task queue unit (3912) is used for storing data request information of the synchronous interface unit (395) or the asynchronous interface unit (396) so as to be convenient for service analysis;
a service analysis unit (3913) for unpacking the received network data and then processing the service;
an edge login authentication unit (3914) for authenticating and authenticating an item edge login;
the service forwarding unit (3915) is used for packaging the request of the service data and forwarding the request to the project end;
a service receiving unit (3916) for receiving network data;
the API request service unit (392) is respectively connected with an external network interface (391), a heartbeat interface unit (393), a data configuration unit (394), a synchronous interface unit (395) and an asynchronous interface unit (396);
the memory database (398) is respectively connected with the heartbeat interface unit (393), the data configuration unit (394), the service request unit (399), the side login queue (3911) and the service analysis unit (3913);
the side login authentication unit (3914) is respectively connected with the external network interface (391) and the side login queue (3911);
the side login queue (3911) is also connected with a service request unit (399);
the service request unit (399) is also respectively connected with the synchronous interface unit (395), the task queue unit (3912) and the asynchronous interface unit (396);
the service forwarding unit (3915) is respectively connected with the task queue unit (3912) and the external network interface (391);
the data pushing unit (397) is respectively connected with the external network interface (391), the unstructured data transfer unit (3910) and the service analysis unit (3913);
the data receiving unit (3916) is respectively connected with the service analysis unit (3913) and the external network interface (391);
the service analysis unit (3913) is also connected with the task queue unit (3912) and the unstructured data transfer unit (3910).
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210346144.7A CN114827253B (en) | 2022-04-01 | 2022-04-01 | Intelligent building networking system based on cloud edge object model |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210346144.7A CN114827253B (en) | 2022-04-01 | 2022-04-01 | Intelligent building networking system based on cloud edge object model |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114827253A CN114827253A (en) | 2022-07-29 |
| CN114827253B true CN114827253B (en) | 2024-02-23 |
Family
ID=82533445
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210346144.7A Active CN114827253B (en) | 2022-04-01 | 2022-04-01 | Intelligent building networking system based on cloud edge object model |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114827253B (en) |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106713428A (en) * | 2016-12-08 | 2017-05-24 | 中国电信股份有限公司物联网分公司 | Business operation support system applied to Internet-of-things self-management platform |
| CN110995617A (en) * | 2019-10-31 | 2020-04-10 | 南京戎光软件科技有限公司 | MQTT-based data transmission method, device, computer equipment and storage medium |
| CN111835826A (en) * | 2020-06-09 | 2020-10-27 | 国网信息通信产业集团有限公司 | Cloud edge cooperative linkage system suitable for smart internet of things system |
| CN112383631A (en) * | 2020-11-17 | 2021-02-19 | 珠海大横琴科技发展有限公司 | Regional Internet of things platform and data processing method based on regional Internet of things platform |
| CN112379653A (en) * | 2020-12-01 | 2021-02-19 | 国能信控互联技术有限公司 | Smart power plant management and control system based on micro-service architecture |
| CN113054743A (en) * | 2021-03-16 | 2021-06-29 | 国电南瑞科技股份有限公司 | Internet of things terminal data access system and method suitable for power distribution cloud master station |
| CN113805867A (en) * | 2021-08-24 | 2021-12-17 | 中通服咨询设计研究院有限公司 | Internet of things platform based on visual static script engine |
| WO2022012285A1 (en) * | 2020-07-16 | 2022-01-20 | 中国能源建设集团湖南省电力设计院有限公司 | Multi-source integrated multi-platform energy information management system |
| CN114253242A (en) * | 2021-12-21 | 2022-03-29 | 上海纽酷信息科技有限公司 | VPN-based Internet of things cloud equipment data acquisition system |
-
2022
- 2022-04-01 CN CN202210346144.7A patent/CN114827253B/en active Active
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106713428A (en) * | 2016-12-08 | 2017-05-24 | 中国电信股份有限公司物联网分公司 | Business operation support system applied to Internet-of-things self-management platform |
| CN110995617A (en) * | 2019-10-31 | 2020-04-10 | 南京戎光软件科技有限公司 | MQTT-based data transmission method, device, computer equipment and storage medium |
| CN111835826A (en) * | 2020-06-09 | 2020-10-27 | 国网信息通信产业集团有限公司 | Cloud edge cooperative linkage system suitable for smart internet of things system |
| WO2022012285A1 (en) * | 2020-07-16 | 2022-01-20 | 中国能源建设集团湖南省电力设计院有限公司 | Multi-source integrated multi-platform energy information management system |
| CN112383631A (en) * | 2020-11-17 | 2021-02-19 | 珠海大横琴科技发展有限公司 | Regional Internet of things platform and data processing method based on regional Internet of things platform |
| CN112379653A (en) * | 2020-12-01 | 2021-02-19 | 国能信控互联技术有限公司 | Smart power plant management and control system based on micro-service architecture |
| CN113054743A (en) * | 2021-03-16 | 2021-06-29 | 国电南瑞科技股份有限公司 | Internet of things terminal data access system and method suitable for power distribution cloud master station |
| CN113805867A (en) * | 2021-08-24 | 2021-12-17 | 中通服咨询设计研究院有限公司 | Internet of things platform based on visual static script engine |
| CN114253242A (en) * | 2021-12-21 | 2022-03-29 | 上海纽酷信息科技有限公司 | VPN-based Internet of things cloud equipment data acquisition system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114827253A (en) | 2022-07-29 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111355780B (en) | Internet of things monitoring management method and system based on block chain | |
| CN100568193C (en) | The system and method that is used for performance management in the multilayer computing environment | |
| Wang et al. | Complex event processing in epc sensor network middleware for both rfid and wsn | |
| CN111813570A (en) | Event-driven message interaction method for power Internet of things | |
| CN108270640B (en) | Information interoperation consistency test method for intelligent marketing and distribution information integration system | |
| CN104980525A (en) | Pervasive mobile computing frame based on state middleware | |
| CN105760449A (en) | Multi-source heterogeneous data cloud pushing method | |
| CN103258027A (en) | Context awareness service platform based on intelligent terminal | |
| CN103607476A (en) | System and method for distributed multi-stage persistence of huge number of messages | |
| CN112347105B (en) | General data service platform based on resource tree | |
| CN108710644A (en) | One kind is about government affairs big data processing method | |
| CN106713428A (en) | Business operation support system applied to Internet-of-things self-management platform | |
| CN201919010U (en) | Website accessing performance monitoring system | |
| CN117424638B (en) | Network slice management method, device and storage medium based on satellite-ground fusion | |
| CN114827253B (en) | Intelligent building networking system based on cloud edge object model | |
| CN112711625B (en) | Bidirectional self-adaptive multi-source heterogeneous big data dynamic processing method | |
| CN116743886A (en) | Industrial control equipment data acquisition system based on Internet of things | |
| Chattopadhyay et al. | Web based RFID asset management solution established on cloud services | |
| CN115658742A (en) | Identification analysis method and system for field-level active identification carrier | |
| CN115374101A (en) | Rail transit station level data management system | |
| CN112948019A (en) | Endowment intelligent terminal service integration method based on edge computing architecture | |
| CN110602159A (en) | Data processing method and system | |
| CN106991129B (en) | Real-time database system based on SOA (service oriented architecture) framework power dispatching system and implementation method | |
| CN111031132A (en) | Industrial Internet system architecture based on standard communication protocol and implementation method thereof | |
| CN103259680A (en) | Device information collecting terminal for security technology and protection facility supervisory system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |