CN103281337B - Method, service end and the system of equipment centralized management - Google Patents
Method, service end and the system of equipment centralized management Download PDFInfo
- Publication number
- CN103281337B CN103281337B CN201310247597.5A CN201310247597A CN103281337B CN 103281337 B CN103281337 B CN 103281337B CN 201310247597 A CN201310247597 A CN 201310247597A CN 103281337 B CN103281337 B CN 103281337B
- Authority
- CN
- China
- Prior art keywords
- protocol
- equipment
- data
- driven
- service end
- 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.)
- Expired - Fee Related
Links
Landscapes
- Computer And Data Communications (AREA)
Abstract
The present invention is applicable to the communications field, it is provided that method, service end and the system of a kind of equipment centralized management, for automatic building control system, this automatic building control system includes at least one client, service end and multiple subservice system;Described method comprises the steps: that service end receives client and the equipment of a certain subservice system is controlled request;Described equipment controls request for the structuring standard interface protocol data preset;The protocol-driven corresponding according to described subservice system and described equipment control request, gather device data corresponding in described subservice system;The device data of the subservice system of described collection is converted to described structuring standard interface protocol data, and feeds back to described client.All differences equipment is carried out effectively, concentrates, is managed collectively by the method for the present invention, service end and system.
Description
Technical field
The invention belongs to the intelligence building system integration field, particularly relate to a kind of equipment centralized management
Method, service end and system.
Background technology
Along with the propelling of building intelligent construction process, extensively for illumination, burglar alarm, disappear
The building such as anti-warning, access control, public broadcasting, information issue, air-conditioning, plumbing are automatic
Change system, uses different interconnection mode, intergration model carries out system combination and information is integrated.
Along with the development of INTELLIGENT BUILDING TECHNIQUE, its system comprised and equipment are also on the increase, for
User can be understood the operation troubles state of Architectural Equipment quickly and easily and set some
Standby control, BMS system produces therewith.The core technology method realizing intelligent construction is
The system integration, the system integration of intelligent building includes that function is integrated, system integrating and software interface
Integrated, it is intellectualizing system to be developed from function to application and integrates, thus realizes intelligence
Building can carry out comprehensive and perfect integrated management.
The key issue of the system integration is to solve different sub-systems, different product interface and association
" standardization " of view, so that can reach " interconnectivity " and " interoperability " between them.
It should provide data-interface, network interface, system and application software interface.BMS system collection
The essence become is that the information realized between subsystems exchanges, each subsystem is carried out unification
Management and monitoring.First the system integration should pay close attention to the interconnectivity between each subsystem and interoperability
Problem, additionally answers attention location system linkage problem of implementation.Interconnectivity between each subsystem and watt
Operational problem, this is multi-vendor, multi-protocols, towards the architecture of various application,
Need to solve interface between various kinds of equipment, subsystem, agreement, system platform, application software,
Architectural environment, operational management etc. are all kinds of towards integrated problem.
System integrator generally uses and carries out system with automatic building control system BA for platform at present
Integrated, automatic building control system is directly and subsystem communicates alternately, the reality of the most each subsystem
Time data be converted into unified form by open industry standard interface (such as OPC interface)
It is stored in system integration data base;It addition, externally provide the OPC interface server of standard,
Support the further integrated communication ability with Third party system.This solution is building automation
Business and specialized subsystem close-coupled, the exploitation of upper-layer service application needs to pay close attention to differentiation
Underlying device characteristic and device talk agreement, be unfavorable for be absorbed in upper-layer service exploitation and subsystem
The modularity extension of system accesses, and needs to revise OPC interface service as extended new subsystem
Device is just provided that the expanded function of subsystem;It addition, above-mentioned solution does not provide unified
Facility information Description standard, it is impossible to all differences facility information carried out effectively, concentrate,
Unified management.
Summary of the invention
The purpose of the embodiment of the present invention is method, the service end providing a kind of equipment to manage concentratedly
And system, it is intended to solve existing intelligent building construction being unfavorable for, upper-layer service is developed and new
Subservice system expand problem.
The embodiment of the present invention is achieved in that a kind of method that equipment is managed concentratedly, described side
Method comprises the steps:
Service end receives client and the equipment of a certain subservice system is controlled request;Described equipment
Control request for the structuring standard interface protocol data preset;
The protocol-driven corresponding according to described subservice system and described equipment control request, adopt
Collect device data corresponding in described subservice system;
The device data of the subservice system of described collection is converted to described structuring standard connect
Mouth protocol data, and feed back to described client.
Further, the described protocol-driven corresponding according to subservice system and equipment control to ask
Ask, gather device data corresponding in subservice system and include:
Service end encapsulates described equipment according to the protocol-driven that described subservice system is corresponding and controls
Request, and send to described subservice system;
Receive described subservice system and control setting of request feedback according to the equipment after described encapsulation
Standby data.
Further, in the equipment control to a certain subservice system performing described reception client
Before system request, also include:
Service end loads device parameter and the protocol-driven of described subservice system, and described equipment is joined
Number includes equipment Foundations information, data storage rule and data alarm rule;
Data cube computation is set up according to described protocol-driven and described client.
Further, described set up data cube computation according to protocol-driven and client and specifically include:
Judge whether described protocol-driven meets default extensive interface protocol specification;
When described protocol-driven meets described extensive interface protocol specification, obtain and identify association
View drives ID;
When described protocol-driven ID is in the presence of native protocol drives in mark, run described association
View drives, and completes and the data cube computation of described client.
Further, also include:
Described service end stores the subservice system of described collection according to described data storage rule
Device data;And according to described data alarm rule, described device data carried out prison of reporting to the police
Survey.
The present invention also proposes the service end of a kind of equipment centralized management, including:
Receiver module, controls to ask for receiving the equipment to a certain subservice system of client
Ask;Described equipment controls request for the structuring standard interface protocol data preset;
Acquisition module, for according to protocol-driven corresponding to described subservice system and described in set
Standby control is asked, and gathers device data corresponding in described subservice system;
Feedback module, described for the device data of the subservice system of described collection is converted to
Structuring standard interface protocol data, and feed back to described client.
Further, described acquisition module includes:
Control performance element, encapsulate institute for the protocol-driven corresponding according to described subservice system
Equipment of stating controls request, and sends to described subservice system;
Data acquisition unit, for receiving described subservice system according to the equipment after described encapsulation
Control the device data of request feedback.
Further, also include load-on module, for loading the equipment ginseng of described subservice system
Number and protocol-driven, described device parameter includes equipment Foundations information, data storage rule sum
According to alarm rule;Link block, for setting up number according to described protocol-driven and described client
According to connection.
Further, described link block includes:
Judging unit, for judging whether described protocol-driven meets default extensive interface association
View specification;
Recognition unit, for meeting described extensive interface protocol specification when described protocol-driven
Time, obtain and identification protocol drives ID;
Run driver element, for when described protocol-driven ID is in native protocol drives mark
In the presence of, run described protocol-driven, complete and the data cube computation of described client.
The present invention also propose a kind of equipment centralized management system, including client, at least one
Subservice system and a service end, described service end includes:
Receiver module, controls to ask for receiving the equipment to a certain subservice system of client
Ask;Described equipment controls request for the structuring standard interface protocol data preset;
Acquisition module, for according to protocol-driven corresponding to described subservice system and described in set
Standby control is asked, and gathers device data corresponding in described subservice system;
Feedback module, described for the device data of the subservice system of described collection is converted to
Structuring standard interface protocol data, and feed back to described client.
Further, described acquisition module includes:
Control performance element, encapsulate institute for the protocol-driven corresponding according to described subservice system
Equipment of stating controls request, and sends to described subservice system;
Data acquisition unit, for receiving described subservice system according to the equipment after described encapsulation
Control the device data of request feedback.
Further, also include load-on module, for loading the equipment ginseng of described subservice system
Number and protocol-driven, described device parameter includes equipment Foundations information, data storage rule sum
According to alarm rule;Link block, for setting up number according to described protocol-driven and described client
According to connection.
Further, described link block includes:
Judging unit, for judging whether described protocol-driven meets default extensive interface association
View specification;
Recognition unit, for meeting described extensive interface protocol specification when described protocol-driven
Time, obtain and identification protocol drives ID;
Run driver element, for when described protocol-driven ID is in native protocol drives mark
In the presence of, run described protocol-driven, complete and the data cube computation of described client.
The embodiment of the present invention sets up a service end in automatic building control system, by former each client
Protocol conversion function is concentrated to service end, by service end provide Unified Device information Description standard,
Carry out integrated access based on subservice system Peer Mode, externally provide open, self-defining association
View drives, and to equipment unification, manages concentratedly and monitors.The building automation system of the embodiment of the present invention
System can reduce the degree of coupling of upper layer application and underlying device, it is not necessary to upper layer application and underlying device
Direct interaction, various upper layer application are absorbed in the core business exploitation of self, it is not necessary to too much pay close attention to
The underlying device characteristic of differentiation and device talk agreement, provide extendible interface protocol simultaneously
Specification, it is simple to access each seed system according to being embodied as the extension of project modularity neatly
System.The method and system of the embodiment of the present invention overcome and are not easy to modularity extension in prior art
Access subservice system, the shortcoming of independent assortment protocol-driven, solve in prior art and exist
Upper layer application too much pay close attention to device characteristics and the communication protocol of bottom subservice System level gray correlation alienation,
Cannot rapid build own service application problem.
Accompanying drawing explanation
Fig. 1 is the flow chart of the method for the equipment centralized management that the embodiment of the present invention one provides;
Fig. 2 is step S1 in the method that the equipment that the embodiment of the present invention one provides is managed concentratedly
Flow chart;
Fig. 3 is step S2 in the method that the equipment that the embodiment of the present invention one provides is managed concentratedly
Flow chart;
Fig. 4 is the structure chart of the service end of the equipment centralized management that the embodiment of the present invention two provides;
Fig. 5 is to gather mould in the service end that the equipment that the embodiment of the present invention two provides is managed concentratedly
The structure chart of block;
Fig. 6 is connection mode in the service end that the equipment that the embodiment of the present invention two provides is managed concentratedly
The structure chart of block;
Fig. 7 is the structure chart of the system of the equipment centralized management that the embodiment of the present invention three provides.
Detailed description of the invention
In order to make the purpose of the present invention, technical scheme and advantage clearer, below in conjunction with
Drawings and Examples, are further elaborated to the present invention.Should be appreciated that this place is retouched
The specific embodiment stated only in order to explain the present invention, is not intended to limit the present invention.
Embodiment one
The embodiment of the present invention one provides a kind of method that equipment is managed concentratedly, for building automation system
System, this automatic building control system includes at least one client, service end and multiple subservice system,
Subservice system can be gate control system, illuminator, air conditioning system, broadcast system and information
Delivery system etc..Client preserves configured good user profile such as user name, password etc.,
The most legal for judging the request of client.As it is shown in figure 1, the side of the embodiment of the present invention one
Method comprises the steps:
Step S1, the device parameter loading all subservice systems and protocol-driven, described in set
Standby parameter includes equipment Foundations information, data storage rule and data alarm rule, concrete such as figure
Shown in 2:
Step S101, when needing to expand new subservice system, will extend and be linked into clothes
The equipment Foundations information of the subservice system of business end configures according to Unified Device information Description standard
In the data base of service end.
Step S102, it is that sub-industry is opened in subservice system development according to extensive interface protocol specification
The protocol-driven of business system.
Step S103, the protocol-driven developed is put under the operation catalogue of service end.With
Time, by the data storage rule pre-set and data alarm rule, it is saved in service end
In data base, for later use.
Described Unified Device information Description standard is presented as the definition of described equipment Foundations information, institute
State equipment Foundations information and include subsystem gateway information, facility information and equipment dot information.Described
The attribute of subsystem gateway information include gateway identification, protocol-driven mark, Connecting quantity (as
IP address, port numbers);The attribute of described facility information includes device identification, affiliated gateway mark
Knowledge, device type, protocol-driven mark, Connecting quantity;The attribute bag of described equipment dot information
Include equipment point identification, corresponding device mark, Connecting quantity.
Described extensive interface protocol specification is not based on the device protocol of bottom, and it includes that agreement is driven
Mobile interface, agreement data structure, wherein protocol-driven interface include create protocol-driven example,
Obtain protocol-driven information, start protocol-driven service, stopping protocol-driven service, destruction association
View drives example;Wherein agreement data structure includes internal agreement instruction, internal data format.
The agreement developed for different subservice system customization according to this set extensive interface protocol specification
Drive, with equipment centralized management system for program parent load operating, the direct and sub-industry of bottom
Business system communicates alternately, the differentiation communication protocol of shielding subservice system.
Step S104, when powering on, service end loads the protocol-driven of each service sub-system automatically.
Step S105, service end detect this protocol-driven according to extensive interface protocol specification
Interface, it is judged that whether the total interface of this protocol-driven meets described extensive interface agreement rule
Model, does not meets, and abandons protocol-driven, meets then entrance step S106.
Step S106, service end obtain protocol-driven information, and protocol-driven information includes agreement
Drive mark.
This protocol-driven mark is identified by step S107, service end.
Step S108, service end judge whether there is this agreement in native protocol drives mark
Drive mark, do not exist, abandon protocol-driven, there is then entrance step S109.
Step S109, establishment protocol-driven example, run protocol-driven, and send corresponding son
The equipment Foundations information of operation system is to protocol-driven, and protocol-driven receives equipment Foundations letter
Breath, resolves Connecting quantity therein, sets up communication connection with corresponding subservice system.
Step S2, service end receive client and the equipment of a certain subservice system are controlled request;
Described equipment controls request for the structuring standard interface protocol data preset.Described equipment controls
Request can be to control the order of subservice system or obtain the request of data.
As it is shown on figure 3, step S2 specifically includes:
By structuring standard interface protocol data between step S201, client and service end
Carrying out data communication, described structuring standard interface protocol includes facility information interface, number of devices
Control to connect according to interface, historical data interface, warning message interface, equipment state interface, equipment
Mouth, information on services interface etc., functionally include logging in verification, heartbeat packet, query facility basis
Information, obtain or subscribe to equipment real-time status, subscribe to device data, subscribe to warning real time information,
Control equipment, query facility historic state, enquiry of historical data, inquiry alarm history record etc..
Step S202, when client and service end set up communication connection, according to structuring mark
The heartbeat packet function of quasi-interface protocol constantly sends heartbeat packet to service end, keeps connecting shape
State.
Step S203, client according to structuring standard interface protocol log in verifying function to
Service end sends and logs in verification request.
After the reception of step S204, service end, parsing log in verification request, take out in asking
User name, password.
Step S205, carrying out safety check according to the user name in request, password, checking should
Whether user is validated user.If not then returning failure, if then entering step S206.
Step S206, return user uniquely identify to client.
Step S207, client uniquely identify and the setting of subservice system according to the user returned
Device type, device identification or equipment point identifications etc. in standby Back ground Information, according to structuring mark
Interface format in quasi-interface protocol encapsulates various equipment and controls request, is sent to service end.Clothes
Business termination receiving unit parses user after controlling request and uniquely identifies, and is uniquely designated according to user
It provides the device data that required parameter is corresponding.
Step S3, according to protocol-driven corresponding to described subservice system and described equipment control
System request, gathers device data corresponding in described subservice system.
Service end controls request according to the protocol-driven sealed in unit that subservice system is corresponding, then will
Equipment after encapsulation controls request and is sent to the subservice system of correspondence, subservice system provide
Corresponding device data is to service end.
Step S4, the device data of the subservice system of described collection is converted to described structure
Change standard interface protocol data, and feed back to described client.
Step S5, while step S4, before or after, according to described data storage rule
Then store the device data of subservice system of described collection in data base, according to described data
Alarm rule carries out alert detecting to described device data, as met corresponding data alarm rule
Produce warning message.
The method of the embodiment of the present invention one can flexible expansion, independent assortment subservice system, have
The effect of fast distributed deployment, saves multiple upper layer application platform simultaneously and sets different bottoms
The standby system time that development agreement drives respectively, energy cost, unification and different underlying device systems
The gateway that system accesses, improves the development efficiency of upper layer application platform and develops week from reduction
Phase.
Embodiment two
The embodiment of the present invention two provides a kind of service end for equipment centralized management, this service end
Based on automatic building control system, this automatic building control system includes at least one client, service end and many
Individual sub-operation system.Subservice system can be gate control system, illuminator, air conditioning system,
Broadcast system and information issuing system etc..Client is connected with service end, for described service
End transmission equipment controls request and receives the device data from service end, service end and each seed
Operation system is connected, for carrying out data communication, monitoring various kinds of equipment with each seed system.
As shown in Figure 4, described service end 100 includes:
Load-on module 10, for loading device parameter and the protocol-driven of described subservice system,
Described device parameter includes equipment Foundations information, data storage rule and data alarm rule.Even
Connection module 70, for setting up data cube computation according to described protocol-driven and described client.
Receiver module 20, controls for receiving the equipment to a certain subservice system of client
Request;Described equipment controls request for the structuring standard interface protocol data preset.
Acquisition module 30, for the protocol-driven corresponding according to described subservice system and institute
Equipment of stating controls request, gathers device data corresponding in described subservice system.
Feedback module 40, for being converted to the device data of the subservice system of described collection
Described structuring standard interface protocol data, and feed back to described client.
Data alarm module 50, is used for according to described data alarm rule described device data
Carry out alert detecting.
Data memory module 60, for storing described collection according to described data storage rule
The device data of subservice system.
As it is shown in figure 5, acquisition module 30 includes:
Control performance element 31, for the protocol-driven envelope corresponding according to described subservice system
Fill described equipment and control request, and send to described subservice system;
Data acquisition unit 32, for receive described subservice system according to described encapsulation after
Equipment controls the device data of request feedback.
As shown in Figure 6, link block 70 includes:
Judging unit 71, for judging whether described protocol-driven meets default expansible connect
Mouth protocol specification;
Recognition unit 72, for meeting described extensive interface agreement rule when described protocol-driven
Fan Shi, obtains and identification protocol drives ID;
Run driver element 73, for driving mark when described protocol-driven ID in native protocol
In the presence of in, run described protocol-driven, complete and the data cube computation of described client.
Service end 100 operation principle of the embodiment of the present invention two is as follows:
First, load-on module 10 loads device parameter and the protocol-driven of subservice system, institute
State device parameter and include equipment Foundations information, data storage rule and data alarm rule.
When needing to expand new subservice system, service end 100 will extend the service of being linked into
The equipment Foundations information of the subservice system of end 100 is joined according to Unified Device information Description standard
Put in the data base of service end 100, and be subservice system according to extensive interface protocol specification
System opens the protocol-driven of subservice system, then the protocol-driven developed is put into service
Under the operation catalogue of end 100.Meanwhile, by the data storage rule pre-set and datagram
Police regulations then, are saved in the data base of service end 100, for later use.
Described Unified Device information Description standard is presented as the definition of described equipment Foundations information, institute
State equipment Foundations information and include subsystem gateway information, facility information and equipment dot information.Described
The attribute of subsystem gateway information include gateway identification, protocol-driven mark, Connecting quantity (as
IP address, port numbers);The attribute of described facility information includes device identification, affiliated gateway mark
Knowledge, device type, protocol-driven mark, Connecting quantity;The attribute bag of described equipment dot information
Include equipment point identification, corresponding device mark, Connecting quantity.
Described extensive interface protocol specification is not based on the device protocol of bottom, and it includes that agreement is driven
Mobile interface, agreement data structure, wherein protocol-driven interface include create protocol-driven example,
Obtain protocol-driven information, start protocol-driven service, stopping protocol-driven service, destruction association
View drives example;Wherein agreement data structure includes internal agreement instruction, internal data format.
The agreement developed for different subservice system customization according to this set extensive interface protocol specification
Drive, with equipment centralized management system for program parent load operating, the direct and sub-industry of bottom
Business system communicates alternately, the differentiation communication protocol of shielding subservice system.
When powering on, load-on module 10 loads the protocol-driven of each service sub-system automatically, connects
The judging unit 71 of module 70 detects connecing of this protocol-driven according to extensive interface protocol specification
Mouthful, it is judged that whether the total interface of this protocol-driven meets described extensive interface protocol specification,
Not meeting, abandon protocol-driven, meet, recognition unit 72 obtains protocol-driven information, association
View activation bit includes that protocol-driven identifies.Run driver element 73 to drive according to native protocol
Mark identifies finds the protocol-driven mark looked for, and does not exists, abandons protocol-driven, exist, creates
Build protocol-driven example, run protocol-driven, and send the equipment Foundations of corresponding subservice system
Information is to protocol-driven, and protocol-driven receives equipment Foundations information, resolves and joins therein connection
Number, sets up communication connection with corresponding subservice system.
Next, receiver module 20 receives client and controls to ask to the equipment of a certain subservice system
Ask;Described equipment controls request for the structuring standard interface protocol data preset.Described equipment
Controlling request can be to control the order of subservice system or obtain the request of data.
By structuring standard interface protocol data number between client and service end 100
According to communication, described structuring standard interface protocol include facility information interface, device data interface,
Historical data interface, warning message interface, equipment state interface, equipment control interface, service
Information interfaces etc., functionally include logging in verification, heartbeat packet, query facility Back ground Information, obtaining
Take or subscribe to equipment real-time status, subscription device data, subscription warning real time information, control to set
Standby, query facility historic state, enquiry of historical data, inquiry alarm history record etc..
When client sets up communication connection with service end 100, assist according to structuring standard interface
The heartbeat packet function of view constantly sends heartbeat packet to service end 100, keeps connection status.Visitor
Family end is stepped on to service end 100 transmission according to the verifying function that logs in of structuring standard interface protocol
Land verification request, receiver module 20 receives, resolve and log in verification request after, according to request
Whether middle user name, this user of password authentification are validated users.If validated user then returns use
Family uniquely identifies to client, and client uniquely identifies and subservice system according to the user returned
Equipment Foundations information in device type, device identification or equipment point identification etc., according to structure
Change the interface format in standard interface protocol and encapsulate the control request of various equipment, be sent to service end
100.Service end 100 receives after equipment controls request and parses user and uniquely identify, according to
Family is uniquely designated it and provides the device data that required parameter is corresponding.
Again, acquisition module 30 is according to protocol-driven corresponding to described subservice system and institute
Equipment of stating controls request, gathers device data corresponding in described subservice system.
Acquisition module 30 controls according to the protocol-driven sealed in unit that subservice system is corresponding please
Ask, then the equipment after encapsulation is controlled the subservice system asking to be sent to correspondence, by subservice
System provides corresponding device data to service end 100.
Finally, the device data of the subservice system of described collection is converted to by feedback module 40
Described structuring standard interface protocol data, and feed back to described client.
Feedback module 40 feed back while, before or after, data memory module 60 basis
Described data storage rule stores the device data of the subservice system of described collection to data base
In, described device data is reported by data alarm module 50 according to described data alarm rule
Police commissioner surveys, and produces warning message as met corresponding data alarm rule.
The service end 100 of the embodiment of the present invention two can flexible expansion, independent assortment subservice system
System, has the effect of fast distributed deployment, saves multiple upper layer application platform to not simultaneously
With underlying device the system time of development agreement driving, energy cost respectively, the unified and different ends
The gateway that layer device systems accesses, improve the development efficiency of upper layer application platform and from reduction
Construction cycle.
Embodiment three
The embodiment of the present invention three provides the system that a kind of equipment is managed concentratedly.As it is shown in fig. 7, this
The system of inventive embodiments three includes at least one client 200, service end 100 and many sub-industry
Business system.Subservice system can be gate control system 301, illuminator 302, air conditioning system
303, broadcast system 304 and information issuing system 305 etc..Client 200 and service end 100
It is connected, controls request for sending equipment to described service end 100 and receive from service end
The device data of 100, service end 100 is connected with each seed system, is used for and each seed
Operation system carries out data communication, monitoring various kinds of equipment.The service end of the embodiment of the present invention three
100, its structure is similar, herein to the service end 100 shown in Fig. 3 to Fig. 4 with operation principle
Repeat no more.
The foregoing is only presently preferred embodiments of the present invention, not in order to limit the present invention,
All any amendment, equivalent and improvement etc. made within the spirit and principles in the present invention,
Should be included within the scope of the present invention.
Claims (10)
1. the method for an equipment centralized management, it is characterised in that described method includes as follows
Step:
Service end receives client and the equipment of a certain subservice system is controlled request;Described equipment
Control request for the structuring standard interface protocol data preset;
The protocol-driven corresponding according to described subservice system and described equipment control request, adopt
Collect device data corresponding in described subservice system;
The device data of the subservice system of described collection is converted to described structuring standard connect
Mouth protocol data, and feed back to described client.
2. the method for claim 1, it is characterised in that described according to subservice system
Protocol-driven and equipment that system is corresponding control request, gather equipment corresponding in subservice system
Data include:
Service end encapsulates described equipment according to the protocol-driven that described subservice system is corresponding and controls
Request, and send to described subservice system;
Receive described subservice system and control setting of request feedback according to the equipment after described encapsulation
Standby data.
3. method as claimed in claim 1 or 2, it is characterised in that connect described in performing
Before receiving the equipment control request to a certain subservice system of client, also include:
Service end loads device parameter and the protocol-driven of described subservice system, and described equipment is joined
Number includes equipment Foundations information, data storage rule and data alarm rule;
Data cube computation is set up according to described protocol-driven and described client.
4. method as claimed in claim 3, it is characterised in that described according to protocol-driven
Set up data cube computation with client to specifically include:
Judge whether described protocol-driven meets default extensive interface protocol specification;
When described protocol-driven meets described extensive interface protocol specification, obtain and identify association
View drives ID;
When described protocol-driven ID is in the presence of native protocol drives in mark, run described association
View drives, and completes and the data cube computation of described client.
5. method as claimed in claim 3, it is characterised in that also include:
Described service end stores the subservice system of described collection according to described data storage rule
Device data;And according to described data alarm rule, described device data carried out prison of reporting to the police
Survey.
6. the service end of an equipment centralized management, it is characterised in that including:
Receiver module, controls to ask for receiving the equipment to a certain subservice system of client
Ask;Described equipment controls request for the structuring standard interface protocol data preset;
Acquisition module, for according to protocol-driven corresponding to described subservice system and described in set
Standby control is asked, and gathers device data corresponding in described subservice system;
Feedback module, described for the device data of the subservice system of described collection is converted to
Structuring standard interface protocol data, and feed back to described client.
7. service end as claimed in claim 6, it is characterised in that described acquisition module bag
Include:
Control performance element, encapsulate institute for the protocol-driven corresponding according to described subservice system
Equipment of stating controls request, and sends to described subservice system;
Data acquisition unit, for receiving described subservice system according to the equipment after described encapsulation
Control the device data of request feedback.
Service end the most as claimed in claims 6 or 7, it is characterised in that also include loading mould
Block, for loading device parameter and the protocol-driven of described subservice system, described device parameter
Including equipment Foundations information, data storage rule and data alarm rule;Link block, is used for
Data cube computation is set up according to described protocol-driven and described client.
9. service end as claimed in claim 8, it is characterised in that described link block includes:
Judging unit, for judging whether described protocol-driven meets default extensive interface association
View specification;
Recognition unit, for meeting described extensive interface protocol specification when described protocol-driven
Time, obtain and identification protocol drives ID;
Run driver element, for when described protocol-driven ID is in native protocol drives mark
In the presence of, run described protocol-driven, complete and the data cube computation of described client.
10. the system of equipment centralized management, it is characterised in that: include client, at least
One sub-operation system and the service end as according to any one of claim 6 to 9.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201310247597.5A CN103281337B (en) | 2013-06-20 | 2013-06-20 | Method, service end and the system of equipment centralized management |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201310247597.5A CN103281337B (en) | 2013-06-20 | 2013-06-20 | Method, service end and the system of equipment centralized management |
Publications (2)
Publication Number | Publication Date |
---|---|
CN103281337A CN103281337A (en) | 2013-09-04 |
CN103281337B true CN103281337B (en) | 2016-08-24 |
Family
ID=49063784
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN201310247597.5A Expired - Fee Related CN103281337B (en) | 2013-06-20 | 2013-06-20 | Method, service end and the system of equipment centralized management |
Country Status (1)
Country | Link |
---|---|
CN (1) | CN103281337B (en) |
Families Citing this family (15)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN104580257B (en) * | 2015-02-03 | 2018-08-03 | 厦门中智信系统集成有限公司 | Intelligent construction group's I O point interactive correspondence method |
CN104848472A (en) * | 2015-04-20 | 2015-08-19 | 广东美的暖通设备有限公司 | Air conditioner monitoring system, OPC server for air conditioner and OPC connecting method |
CN106445694A (en) * | 2015-08-12 | 2017-02-22 | 优信互联(北京)信息技术有限公司 | Application access method, device and system |
CN107360035B (en) * | 2017-07-27 | 2019-12-20 | 北京市天元网络技术股份有限公司 | Data processing method and system |
CN107240246B (en) * | 2017-08-08 | 2019-08-02 | 四川省建筑科学研究院 | A kind of architectural engineering monitoring data wireless acquisition system and method based on intelligent terminal |
CN109462613A (en) * | 2018-12-27 | 2019-03-12 | 郑州春泉节能股份有限公司 | A kind of communications protocol compatibility method |
CN110049137A (en) * | 2019-04-25 | 2019-07-23 | 广东工业大学 | A kind of instruction transmission method, collecting method and relevant apparatus |
CN111610765B (en) * | 2020-05-25 | 2022-09-30 | 珠海格力电器股份有限公司 | Distributed message control device and method and building control system |
CN111698294B (en) * | 2020-05-26 | 2022-06-21 | 珠海格力电器股份有限公司 | Automatic equipment binding method and building management system |
CN111930496B (en) * | 2020-06-18 | 2024-07-02 | 珠海格力电器股份有限公司 | Integrated control method, integrated control device, building control system, storage medium and processor |
CN112422314B (en) * | 2020-10-10 | 2022-08-30 | 烽火通信科技股份有限公司 | Method and system for collecting and reporting alarm performance data |
CN112904815A (en) * | 2021-01-18 | 2021-06-04 | 汉维科技发展有限公司 | Building intelligent system integration method |
CN112800120B (en) * | 2021-01-26 | 2023-06-06 | 政采云有限公司 | Service processing method and device |
CN114125005B (en) * | 2021-11-26 | 2023-09-22 | 日立楼宇技术(广州)有限公司 | Data processing method and device based on intelligent building system |
CN113918132A (en) * | 2021-12-13 | 2022-01-11 | 珠海市新德汇信息技术有限公司 | Equipment standardization management method, system, working method, device and storage medium |
Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2007037035A (en) * | 2005-07-29 | 2007-02-08 | Mitsubishi Electric Building Techno Service Co Ltd | Institution management system |
CN101344956A (en) * | 2008-08-26 | 2009-01-14 | 广东工业大学 | Intelligent building distributed heterogeneous system integration method |
CN101827302A (en) * | 2010-04-19 | 2010-09-08 | 中兴通讯股份有限公司 | Multi-service unified processing method and unified service platform |
CN101963803A (en) * | 2010-09-09 | 2011-02-02 | 上海数字智能化系统工程有限公司 | Intelligent building integrated system |
CN202395811U (en) * | 2011-12-15 | 2012-08-22 | 湖南省烟草公司长沙市公司 | Protocol conversion device used for intelligent BMS |
CN102662369A (en) * | 2011-12-23 | 2012-09-12 | 郭松 | System integration comprehensive management control system |
Family Cites Families (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101958817B (en) * | 2010-07-17 | 2012-09-05 | 刘利华 | Intelligent home information management system |
CN201984337U (en) * | 2011-03-24 | 2011-09-21 | 南京敏求电子科技有限公司 | Integrated ward device for prison administration and integrated monitoring system |
-
2013
- 2013-06-20 CN CN201310247597.5A patent/CN103281337B/en not_active Expired - Fee Related
Patent Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2007037035A (en) * | 2005-07-29 | 2007-02-08 | Mitsubishi Electric Building Techno Service Co Ltd | Institution management system |
CN101344956A (en) * | 2008-08-26 | 2009-01-14 | 广东工业大学 | Intelligent building distributed heterogeneous system integration method |
CN101827302A (en) * | 2010-04-19 | 2010-09-08 | 中兴通讯股份有限公司 | Multi-service unified processing method and unified service platform |
CN101963803A (en) * | 2010-09-09 | 2011-02-02 | 上海数字智能化系统工程有限公司 | Intelligent building integrated system |
CN202395811U (en) * | 2011-12-15 | 2012-08-22 | 湖南省烟草公司长沙市公司 | Protocol conversion device used for intelligent BMS |
CN102662369A (en) * | 2011-12-23 | 2012-09-12 | 郭松 | System integration comprehensive management control system |
Also Published As
Publication number | Publication date |
---|---|
CN103281337A (en) | 2013-09-04 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN103281337B (en) | Method, service end and the system of equipment centralized management | |
CN108092884A (en) | A kind of wireless access gateway system and application process | |
CN103370921B (en) | For method, equipment, gateway and the remotely administered server named the sensor device in local network | |
CN1809985A (en) | Systems and methods for managing a network using active jacks | |
CN102378162B (en) | The system and method for M2M terminal, M2M terminal remote management | |
CN103220285B (en) | Access system based on RESTful interface under ubiquitous service environment | |
CN102497397A (en) | Home furnishing monitoring system and method | |
CN102014403A (en) | Method and system for transmitting network topology information | |
CN102857566A (en) | Intelligent gateway of internet of things capable of being customized by software | |
CN108900392A (en) | A kind of method and system of smart home multiple gateway access | |
CN101262372A (en) | Method for video monitoring platform to operate and control front-end device based on SIP server cluster | |
AU2016324353A1 (en) | Mesh-networked power control devices, systems and methods | |
CN103796343B (en) | M2M gateway devices and its application process | |
CN107566217A (en) | A kind of flow control methods, device, equipment, storage medium | |
CN101567861A (en) | Data synchronization method and application system between heterogeneous application systems | |
CN102916990A (en) | Intelligent real-time online cluster dynamic management system for devices of internet of things | |
US10536397B2 (en) | Packet count-based object locking protocol | |
CN101945086A (en) | Security system access business platform for video type security gateway and information transmission method | |
CN114125005B (en) | Data processing method and device based on intelligent building system | |
CN105867314A (en) | Remote monitoring system and communication method thereof | |
CN101022364A (en) | Trap message reporting method and system warning information resource/warning agent service device | |
CN102667663A (en) | Power saving through management of sessions between a home gateway and a broadband access node | |
CN109067795A (en) | Internet of Things network communication data interactive system and method | |
CN102819455B (en) | A kind of method process being managed in application layer and management system | |
KR100932238B1 (en) | Wens-based sensor system |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
C06 | Publication | ||
PB01 | Publication | ||
C10 | Entry into substantive examination | ||
SE01 | Entry into force of request for substantive examination | ||
C14 | Grant of patent or utility model | ||
GR01 | Patent grant | ||
CF01 | Termination of patent right due to non-payment of annual fee | ||
CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20160824 Termination date: 20180620 |