CN112365388A - Method for realizing intelligent fire fighting based on Internet of things cloud platform - Google Patents
Method for realizing intelligent fire fighting based on Internet of things cloud platform Download PDFInfo
- Publication number
- CN112365388A CN112365388A CN202011101987.8A CN202011101987A CN112365388A CN 112365388 A CN112365388 A CN 112365388A CN 202011101987 A CN202011101987 A CN 202011101987A CN 112365388 A CN112365388 A CN 112365388A
- Authority
- CN
- China
- Prior art keywords
- equipment
- data
- jumping
- information
- identification code
- 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.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 38
- 238000004519 manufacturing process Methods 0.000 claims abstract description 21
- 230000009191 jumping Effects 0.000 claims description 49
- 238000007726 management method Methods 0.000 claims description 21
- 230000005540 biological transmission Effects 0.000 claims description 10
- 230000008569 process Effects 0.000 claims description 10
- 230000000875 corresponding effect Effects 0.000 claims description 9
- 238000004458 analytical method Methods 0.000 claims description 7
- 230000002159 abnormal effect Effects 0.000 claims description 4
- 238000012545 processing Methods 0.000 claims description 4
- 238000001914 filtration Methods 0.000 claims description 3
- 230000002596 correlated effect Effects 0.000 claims description 2
- 238000010586 diagram Methods 0.000 description 7
- 238000013523 data management Methods 0.000 description 4
- 238000012423 maintenance Methods 0.000 description 3
- 238000012544 monitoring process Methods 0.000 description 3
- 238000007405 data analysis Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 230000006855 networking Effects 0.000 description 2
- 230000008439 repair process Effects 0.000 description 2
- 239000000779 smoke Substances 0.000 description 2
- 238000006243 chemical reaction Methods 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000018109 developmental process Effects 0.000 description 1
- 238000009434 installation Methods 0.000 description 1
- 239000000463 material Substances 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 239000002994 raw material Substances 0.000 description 1
- 230000001105 regulatory effect Effects 0.000 description 1
- 230000033772 system development Effects 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q50/00—Systems or methods specially adapted for specific business sectors, e.g. utilities or tourism
- G06Q50/10—Services
- G06Q50/26—Government or public services
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
-
- G—PHYSICS
- G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
- G16Y—INFORMATION AND COMMUNICATION TECHNOLOGY SPECIALLY ADAPTED FOR THE INTERNET OF THINGS [IoT]
- G16Y10/00—Economic sectors
- G16Y10/35—Utilities, e.g. electricity, gas or water
-
- G—PHYSICS
- G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
- G16Y—INFORMATION AND COMMUNICATION TECHNOLOGY SPECIALLY ADAPTED FOR THE INTERNET OF THINGS [IoT]
- G16Y40/00—IoT characterised by the purpose of the information processing
- G16Y40/10—Detection; Monitoring
Abstract
The invention relates to a method for realizing intelligent fire fighting based on an Internet of things cloud platform, wherein the cloud platform comprises a production process management subsystem, a product sale management subsystem, an after-sale service subsystem, an equipment independence information acquisition and forwarding system and an application system; the production process management subsystem uploads the manufacturing information of the equipment; the product sale management subsystem uploads the sale information of the equipment; the after-sale service subsystem uploads the after-sale information of the equipment; the equipment independence information acquisition and forwarding system acquires equipment information and converts the equipment information into standard data for storage or converts instruction data into data which can be identified by equipment and issues the data; the application system obtains specification data. The equipment independence information acquisition and forwarding system is arranged, data of different manufacturers and different equipment are respectively analyzed in a coder-decoder mode, formats of different data are unified, and therefore the purpose that any equipment can be directly connected to the system or slightly modified to be connected to the system is achieved. And the information sharing between the equipment and the supervision department is realized.
Description
Technical Field
The invention relates to the field of WEB application and the field of information transmission of the Internet of things, in particular to a method for realizing intelligent fire fighting based on a cloud platform of the Internet of things.
Background
With the deep development of the internet technology, various enterprise application systems appear in various forms, such as OA, CMS, ERP and the like, and the applications provide great convenience for daily management of enterprises. However, the existing application is excessive, and new troubles are brought to enterprises, and one enterprise, especially an enterprise with more than scale, often has a plurality of applications, and data is not communicated with each other, so that information islands and zombie systems are frequently appeared, and financial resources and material resources are wasted.
The internet of things is a technology which has emerged in recent years, so that a plurality of traditional devices have networking capability, but how to display the internet of things after networking is a great problem for a plurality of small and medium-sized enterprises, and the problem is particularly obvious for enterprises transformed from a plurality of traditional device manufacturing industries.
It is difficult to share information with regulatory authorities. Taking intelligent power utilization equipment, intelligent smoke sensing equipment and other equipment as examples, alarm data generated by the equipment can be fire alarm data, and how to share the data with a fire department in real time is a great problem because the equipment does not know where the equipment can be sold, and an access interface externally published by a local fire protection system is not uniform and standard, so that information is difficult to share.
At present, the analysis of the manufacturing management, the data management and the big data management of the equipment of the internet of things in the fire fighting industry cannot be realized on one platform.
Disclosure of Invention
Aiming at the defects, the invention provides a method for realizing intelligent fire fighting based on an Internet of things cloud platform, which can realize equipment manufacturing management, data management, big data management analysis and the like.
In order to solve the technical problems, the technical scheme of the invention is as follows: a method for realizing intelligent fire fighting based on an Internet of things cloud platform comprises a production process management subsystem, a product sale management subsystem, an after-sale service subsystem, an equipment independence information acquisition and forwarding system and an application system;
the production process management subsystem uploads the manufacturing information of the equipment;
the product sale management subsystem uploads the sale information of the equipment;
the after-sale service subsystem uploads the after-sale information of the equipment;
the equipment independence information acquisition and forwarding system acquires equipment information and converts the equipment information into standard data for storage or converts instruction data into data which can be identified by equipment and issues the data;
the application system obtains specification data.
As a preferred technical scheme, the device independence information acquisition and forwarding system analyzes a manufacturer identifier from a data message according to a protocol, queries a codec corresponding to the manufacturer from a database according to the manufacturer identifier, and then calls the codec to process data.
The preferable technical scheme comprises the following steps:
s1: determining a data transmission standard to realize the equipment for sending data through data identification;
s2: registering an equipment manufacturer and generating a unique user identification code of the equipment manufacturer;
s3: registering the device type, uploading an encoder and a decoder, and generating a unique device type identification code of the device type;
s4: registering the equipment and generating a unique equipment identification code of the equipment;
s5: and calling a decoder analysis device to upload data or calling an encoder to encode and send instruction data.
As a preferred technical solution, in step S1, the data transmission standard is: the data comprises fixed format data and non-fixed format data, the fixed format data comprises a manufacturer code of the equipment and a unique identification number of the equipment at the manufacturer, and the content of the non-fixed format data is self-defined by the equipment manufacturer.
As a preferred technical solution, in step S2, the device manufacturer registration includes the following steps:
step S21: the equipment manufacturer fills in basic information and goes to step S22;
step S22: the system checks data;
if the information is wrong or is registered, returning to the step S21 for refilling;
if the check passes to step S23;
step S23: the system generates a unique user identification code of the equipment manufacturer, and stores the unique user identification code and the basic information for later use.
As a preferred technical solution, in step S3, registering the device type includes the following steps:
step S31: the equipment manufacturer logs in the system;
step S32: filling basic information of the device type, and jumping to step S33;
step S33: the system checks the data for a check,
if the error exists, jumping to step S32, and re-filling;
if no error exists, jumping to step S34;
step S34: uploading the encoded file and the decoded file, and jumping to step S35;
step S35: the system stores the encoded file and the decoded file in a certain position of a server hard disk and records a path; jumping to step S36;
step S36: the system stores the path returned in step S35 in the database, generates the device type identification code, and saves and reserves it.
As a preferred technical solution, in step S4, the registering device includes the following steps:
step S41: selecting the device type, and jumping to step S42;
step S42: filling basic device information, and jumping to step S43;
step S43: the basic information is checked and the basic information is checked,
if there is an error, returning to step S42;
if no error, jumping to step S44;
step S44: the system generates a 15-bit unique equipment identification code, and the equipment identification code is associated with a user identification code and an equipment type identification code and is stored in a database; jumping to step S45;
step S45: returning the 15-bit unique equipment identification code to the equipment manufacturer
As a preferred technical solution, in step S5, invoking a decoder parsing device to upload data includes the following steps:
step S51: the devices are connected to the system through a socket,
if the connection is successful, the service data is sent to the system, and the step S52 is skipped;
if the connection is unsuccessful, the equipment automatically processes the exception;
step S52: the system saves the long connection with the device until the device is actively disconnected;
reading data, and analyzing a user identification code and an equipment identification code of equipment;
checking whether the equipment is registered or not through database comparison;
if the device is unregistered, the device is connected illegally, and the step S53 is skipped;
if registered, go to step S54;
step S53: disconnecting the connection and finishing the subsequent processing;
step S54: caching and storing the connection and equipment identification codes;
step S55: storing original data in a database in a correlated manner through the user identification code and the equipment identification code, and jumping to the step S56;
step S56: finding the equipment type of the equipment from the database, finding a corresponding decoder according to the equipment type, calling the decoder to analyze data, and storing the decoded data in the database in a related manner.
As a preferred technical solution, in step S6, invoking an encoder to encode the issue instruction data includes the following steps:
step S61: the service platform transmits basic information and instruction data of the equipment to the equipment independence information acquisition and forwarding system, and the system stores original data to a database; finding the device type of the device from the database according to the basic information of the device, finding a corresponding encoder according to the device type, and jumping to step S62;
step S62: loading an encoder, calling the encoder, and encoding the command data into format data which can be recognized by equipment; storing the encoded data in a database, and jumping to step S63;
step S63: searching for connection according to the equipment information;
if found, go to step S64;
if not, jumping to step S65;
step S64: sending the coded instruction data through the long connection, and ending;
step S65: if no connection is found, returning abnormal information and ending.
As a preferred technical solution, the authentication of user login of an application system includes the following steps:
step S71, obtaining the request path of the user, comparing the database records, filtering and judging whether the request is the authority resource or the non-authority resource,
if the resource is a non-permission resource, authentication is not needed, and the step S73 is skipped;
if the resource is the authority resource, checking whether the Token is carried in the user request,
if no Token exists, judging that the request is illegal, and jumping to step S75;
if so, jumping to step S72;
step S72, the database compares whether the resource authorizes the user or the user group, if so, the preliminary authentication is successful, the Token validity is checked,
if Token is valid, jumping to step S74;
if Token is invalid, jumping to step S75;
step S73, the certification is passed, log is recorded, the authority is released, and the user is allowed to operate the resource;
step S74, the effective time of Token is defaulted to 30 minutes, and the expiration time of Token is reset according to the latest operation time of the user;
step S75, authentication is failed, and a user prompt of 'illegal operation' is returned to the user.
By adopting the technical scheme, the method for realizing intelligent fire fighting based on the Internet of things cloud platform starts from the bottom layer structure, changes the traditional method, sets the equipment independence information acquisition and forwarding system on the platform, respectively analyzes the data of different manufacturers and different equipment in a codec mode, and unifies the formats of different data, thereby achieving the purpose that any equipment can be directly or slightly modified to be connected with the system. The information sharing between the equipment and the supervision department is realized, and by taking intelligent power utilization equipment, intelligent smoke sensing equipment and other equipment as examples, the alarm data generated by the equipment can be fire alarm data.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to these drawings without creative efforts.
FIG. 1 is an architectural diagram of the present invention;
FIG. 2 is an embodiment of a data transmission standard of the present invention;
FIG. 3 is a flow chart of vendor registration in an embodiment of the present invention;
FIG. 4 is a flow chart of registering device types in an embodiment of the present invention;
FIG. 5 is a flow chart of a registration apparatus in an embodiment of the present invention;
FIG. 6 is a flow chart of encoding, decoding, parsing and uploading data in an embodiment of the invention;
FIG. 7 is a diagram illustrating a codec encoding command data issuing process according to an embodiment of the present invention
FIG. 8 is a flow diagram of a production process management subsystem in an embodiment of the present invention;
FIG. 9 is a flow diagram of a product sales management subsystem in an embodiment of the invention;
FIG. 10 is a flow diagram of an after-market service subsystem in an embodiment of the present invention;
FIG. 11 is a flow diagram of a real-time monitoring subsystem in an embodiment of the present invention;
FIG. 12 is a flow diagram of an alarm subsystem of the device in an embodiment of the present invention;
FIG. 13 is a flow chart of resource authentication in an embodiment of the invention.
Detailed Description
A method for realizing intelligent fire fighting based on an Internet of things cloud platform is disclosed, as shown in figure 1, the cloud platform comprises a production process management subsystem, a product sale management subsystem, an after-sale service subsystem, an equipment independence information acquisition and forwarding system and an application system;
the production process management subsystem uploads the manufacturing information of the equipment;
the product sale management subsystem uploads the sale information of the equipment;
the after-sale service subsystem uploads the after-sale information of the equipment;
the equipment independence information acquisition and forwarding system acquires equipment information and converts the equipment information into standard data for storage or converts instruction data into data which can be identified by equipment and issues the data;
the application system obtains specification data.
Due to the fact that data of the sensing layer of the Internet of things are multi-source and heterogeneous, different devices have different interfaces and different technical standards. In order to access the Internet of things equipment with different manufacturers and different data standards to the same platform, the platform is provided with an equipment independence information acquisition and forwarding system, the equipment independence information acquisition and forwarding system analyzes a manufacturer identification from a data message according to a protocol, a database is inquired for a codec corresponding to the manufacturer according to the manufacturer identification, and then the codec is called to process data.
The method comprises the following steps:
s1: determining a data transmission standard to realize the equipment for sending data through data identification;
s2: registering an equipment manufacturer and generating a unique user identification code of the equipment manufacturer;
s3: registering the device type, uploading an encoder and a decoder, and generating a unique device type identification code of the device type;
s4: registering the equipment and generating a unique equipment identification code of the equipment;
s5: and calling a decoder analysis device to upload data or calling an encoder to encode and send instruction data.
In step S1, the data transmission standard is: the transmitted data comprises two parts of fixed format data and non-fixed format data, a manufacturer code of the equipment and a unique identification number of the equipment in the manufacturer can be analyzed from the fixed format data, and the system determines the unique equipment according to the two data; the data with the non-fixed format can be customized by each manufacturer, and the system does not make any requirements.
For example, as shown in fig. 2, the first 15 digits of the data are the user identification code, which is provided by the system during the second step of user registration and is fixed, and the rest is unchanged.
The equipment manufacturer provides basic information such as manufacturer name, contact way and the like to the platform through the production process management subsystem. The equipment manufacturer can manage the maintenance and update of own equipment, an encoder and a decoder in the system by account numbers. As shown in fig. 3, the device manufacturer registration in step S2 includes the following steps:
step S21: the equipment manufacturer fills in basic information and goes to step S22;
step S22: the system checks data;
if the information is wrong or is registered, returning to the step S21 for refilling;
if the check passes to step S23;
step S23: the system generates a unique user identification code of the equipment manufacturer, and stores the unique user identification code and the basic information for later use.
The equipment manufactured by one manufacturer can be various, the resolution of the same type of equipment is consistent, the equipment manufacturer can create different equipment types according to the requirement of the equipment manufacturer, and an encoder and a decoder are configured for each type of equipment to be responsible for the data resolution of the type of equipment. As shown in fig. 4, the step S3 of registering the device type includes the following steps:
step S31: the equipment manufacturer logs in the system;
step S32: filling basic information of the device type, and jumping to step S33;
step S33: the system checks the data for a check,
if the error exists, jumping to step S32, and re-filling;
if no error exists, jumping to step S34;
step S34: uploading the encoded file and the decoded file, and jumping to step S35;
step S35: the system stores the encoded file and the decoded file in a certain position of a server hard disk and records a path; jumping to step S36;
step S36: the system stores the path returned in step S35 in the database, generates the device type identification code, and saves and reserves it.
The decoder analyzes the data into formatted JSON data to be transmitted with the system, and the system stores, analyzes and displays the data. The encoder is reverse, the instruction received by the system is compiled into JSON data and transmitted to the intermediate system, and the system calls the encoder to convert the JSON into data which can be identified by the equipment and then transmits the data to the equipment.
The manufacturer selects the type of the equipment, specific equipment information is created under the type, a system generates a 15-bit unique identification number to be returned to the manufacturer, the identification number needs to be fixed in the first 15 bits of a data message when the equipment uploads data in the future, and the system judges which codec is used for analyzing the data according to the identification number.
As shown in fig. 5, the registering of the device in step S4 includes the steps of:
step S41: selecting the device type, and jumping to step S42;
step S42: filling basic device information, and jumping to step S43;
step S43: the basic information is checked and the basic information is checked,
if there is an error, returning to step S42;
if no error, jumping to step S44;
step S44: the system generates a 15-bit unique equipment identification code, and the equipment identification code is associated with a user identification code and an equipment type identification code and is stored in a database; jumping to step S45;
step S45: returning the 15-bit unique device identification code to the device manufacturer.
Calling a decoder analysis device to upload data: after data is uploaded, first-step analysis is carried out, the first 15 bits are taken, the data base is searched for equipment on the condition that equipment, equipment manufacturers and equipment types are stored in an associated mode, a file path of a decoder can be found necessarily through an association relation, the decoder is called dynamically, data after 15 bits are processed, and a processing result is forwarded to a platform.
As shown in fig. 6, in step S5, invoking a decoder to parse the device to upload data includes the following steps:
step S51: the devices are connected to the system through a socket,
if the connection is successful, the service data is sent to the system, and the step S52 is skipped;
if the connection is unsuccessful, the equipment automatically processes the exception;
step S52: the system saves the long connection with the device until the device is actively disconnected;
reading data, and analyzing a user identification code and an equipment identification code of equipment through fixed format data;
checking whether the equipment is registered or not through database comparison;
if the device is unregistered, the device is connected illegally, and the step S53 is skipped;
if registered, go to step S54;
step S53: disconnecting the connection and finishing the subsequent processing;
step S54: the connection and the equipment identification code are cached and stored, so that the connection can be conveniently searched when a subsequent instruction is issued;
step S55: through the equipment manufacturer information and the equipment identification number obtained in the step S52, original data are stored in the MongoDB in an associated mode, and the step S56 is skipped;
step S56: finding the device type of the device from the database, finding the corresponding codec according to the device type, calling the decoder to analyze the non-fixed segment data, converting the non-fixed segment data into formatted JSON data, and storing the decoded data in the MongoDB in a correlation manner.
The real-time monitoring subsystem, the equipment alarm subsystem, the data analysis subsystem, the data outward transmission subsystem and the like can traverse the subscribed events and notifications, and the user can check the subscribed events and notifications, such as real-time notifications, threshold value alarms and the like.
The process of calling an encoder to encode and send instruction data and the process of uploading data are opposite, and from the aspect of data format conversion, the process of converting formatted JSON data into format messages specified by equipment manufacturers is realized. As shown in fig. 7, in step S6, the step of calling the encoder to encode the issue instruction data includes the following steps:
step S61: the service platform transmits the basic information and the instruction data of the JSON-format equipment to an equipment independence information acquisition and forwarding system, and the system stores the original data to the MongoDB; finding the device type of the device from the database according to the basic information, finding the corresponding codec according to the device type, and going to step S62;
step S62: loading a coder-decoder, calling the coder to code the command data into format data which can be recognized by the user terminal; storing the encoded data in a database, and jumping to step S63;
step S63: finding a connection according to the device information, the connection being a long connection between the system and the device stored in the cache in step S54;
if so, jumping to step S64;
if not, go to step S65;
step S64: sending the coded instruction data through the long connection, and ending;
step S65: if no connection is found, returning abnormal information and ending.
As shown in fig. 8, the production process management subsystem mainly manages the purchase, use and scrap conditions of NB cards, core motherboards, and several core raw materials required for manufacturing the internet of things device, manages the production and inventory conditions of the final finished product, and synchronizes the device information to the cloud platform.
As shown in fig. 9, the product sales management subsystem mainly manages sales orders, product ex-warehouse, and product installation of products.
As shown in fig. 10, the after-sales service subsystem accepts the replacement and repair appeal from the customer, and dispatches the work in the form of a work order, and after the constructor completes the related work, the state of the work order is maintained, and the work order is completed after the department leader checks, so that the problem of dispatching is solved, and the data of the related maintenance and repair and equipment replacement can be counted in the later period.
As shown in fig. 11, the real-time monitoring subsystem displays the data uploaded by the device in real time, and displays normal data, abnormal data, and alarm data according to a predetermined definition, and if the data is alarm data, the data can be notified to the relevant responsible person at the first time through a short message, a telephone, a mobile APP message, and the like, in addition to a message and a prompt tone in the system.
As shown in fig. 12, since the devices accessing the system have independence, the system development does not know what the alarm conditions of each type of device are at the beginning, and only after the devices are accessed, the alarm condition configuration is read through the device description profile file, and after each piece of data is uploaded, asynchronous comparison is performed, and an alarm is given if the alarm condition is triggered.
The data analysis subsystem supports the inquiry and report of all data of the system; including user data, production data, order data, operation and maintenance data, alarm data, and the like. And the report generation conditions are customized, and various data formats can be derived. And the method has strict authority management, and users without authority cannot inquire related reports.
The data outward transmission subsystem is mainly used for synchronously sharing data to a fire department. The fire fighting systems needing to be accessed are connected in advance, the data of the user needs to be transmitted to which fire fighting system, and the associated parameters are configured.
As shown in fig. 13, the authentication of the user login of the application system includes the following steps:
step S71, obtaining the request path of the user, comparing the database records, filtering and judging whether the request is the authority resource or the non-authority resource,
if the resource is a non-permission resource, authentication is not needed, and the step S73 is skipped;
if the resource is the authority resource, checking whether the Token is carried in the user request,
if no Token exists, judging that the request is illegal, and jumping to step S75;
if so, jumping to step S72;
step S72, the database compares whether the resource authorizes the user or the user group, if so, the preliminary authentication is successful, the Token validity is checked,
if Token is valid, jumping to step S74;
if Token is invalid, jumping to step S75;
step S73, the certification is passed, log is recorded, the authority is released, and the user is allowed to operate the resource;
step S74, the effective time of Token is defaulted to 30 minutes, and the expiration time of Token is reset according to the latest operation time of the user;
step S75, authentication is failed, and a user prompt of 'illegal operation' is returned to the user.
After the authentication is passed, the user can perform other operations after the release.
The foregoing shows and describes the general principles, essential features, and advantages of the invention. It will be understood by those skilled in the art that the present invention is not limited to the embodiments described above, which are described in the specification and illustrated only to illustrate the principle of the present invention, but that various changes and modifications may be made therein without departing from the spirit and scope of the present invention, which fall within the scope of the invention as claimed. The scope of the invention is defined by the appended claims and equivalents thereof.
Claims (10)
1. A method for realizing intelligent fire fighting based on an Internet of things cloud platform is characterized by comprising the following steps: the cloud platform comprises a production process management subsystem, a product sale management subsystem, an after-sale service subsystem, an equipment independence information acquisition and forwarding system and an application system;
the production process management subsystem uploads the manufacturing information of the equipment;
the product sale management subsystem uploads the sale information of the equipment;
the after-sale service subsystem uploads the after-sale information of the equipment;
the equipment independence information acquisition and forwarding system acquires equipment information and converts the equipment information into standard data for storage or converts instruction data into data which can be identified by equipment and issues the data;
the application system obtains specification data.
2. The method for realizing intelligent fire fighting based on the cloud platform of the internet of things as claimed in claim 1, wherein: the equipment independence information acquisition and forwarding system analyzes a manufacturer identification from a data message according to a protocol, inquires a coder-decoder corresponding to the manufacturer from a database according to the manufacturer identification, and then calls the coder-decoder to process data.
3. The method for realizing intelligent fire fighting based on the cloud platform of the internet of things as claimed in claim 2, wherein: the method comprises the following steps:
s1: determining a data transmission standard to realize the equipment for sending data through data identification;
s2: registering an equipment manufacturer and generating a unique user identification code of the equipment manufacturer;
s3: registering the device type, uploading an encoder and a decoder, and generating a unique device type identification code of the device type;
s4: registering the equipment and generating a unique equipment identification code of the equipment;
s5: and calling a decoder analysis device to upload data or calling an encoder to encode and send instruction data.
4. The method for realizing intelligent fire fighting based on the cloud platform of the internet of things of claim 3, wherein the method comprises the following steps: in step S1, the data transmission standard is: the data comprises fixed format data and non-fixed format data, the fixed format data comprises a manufacturer code of the equipment and a unique identification number of the equipment at the manufacturer, and the content of the non-fixed format data is self-defined by the equipment manufacturer.
5. The method for realizing intelligent fire fighting based on the cloud platform of the internet of things of claim 3, wherein the method comprises the following steps: in step S2, the device manufacturer registration includes the steps of:
step S21: the equipment manufacturer fills in basic information and goes to step S22;
step S22: the system checks data;
if the information is wrong or is registered, returning to the step S21 for refilling;
if the check passes to step S23;
step S23: the system generates a unique user identification code of the equipment manufacturer, and stores the unique user identification code and the basic information for later use.
6. The method for realizing intelligent fire fighting based on the cloud platform of the internet of things of claim 3, wherein the method comprises the following steps: in step S3, registering the device type includes the steps of:
step S31: the equipment manufacturer logs in the system;
step S32: filling basic information of the device type, and jumping to step S33;
step S33: the system checks the data for a check,
if the error exists, jumping to step S32, and re-filling;
if no error exists, jumping to step S34;
step S34: uploading the encoded file and the decoded file, and jumping to step S35;
step S35: the system stores the encoded file and the decoded file in a certain position of a server hard disk and records a path; jumping to step S36;
step S36: the system stores the path returned in step S35 in the database, generates the device type identification code, and saves and reserves it.
7. The method for realizing intelligent fire fighting based on the cloud platform of the internet of things of claim 3, wherein the method comprises the following steps: in step S4, registering the device includes the steps of:
step S41: selecting the device type, and jumping to step S42;
step S42: filling basic device information, and jumping to step S43;
step S43: the basic information is checked and the basic information is checked,
if there is an error, returning to step S42;
if no error, jumping to step S44;
step S44: the system generates a 15-bit unique equipment identification code, and the equipment identification code is associated with a user identification code and an equipment type identification code and is stored in a database; jumping to step S45;
step S45: returning the 15-bit unique device identification code to the device manufacturer.
8. The method for realizing intelligent fire fighting based on the cloud platform of the internet of things of claim 3, wherein the method comprises the following steps: in step S5, invoking a decoder to parse the device to upload data, including the following steps:
step S51: the devices are connected to the system through a socket,
if the connection is successful, the service data is sent to the system, and the step S52 is skipped;
if the connection is unsuccessful, the equipment automatically processes the exception;
step S52: the system saves the long connection with the device until the device is actively disconnected;
reading data, and analyzing a user identification code and an equipment identification code of equipment;
checking whether the equipment is registered or not through database comparison;
if the device is unregistered, the device is connected illegally, and the step S53 is skipped;
if registered, go to step S54;
step S53: disconnecting the connection and finishing the subsequent processing;
step S54: caching and storing the connection and equipment identification codes;
step S55: storing original data in a database in a correlated manner through the user identification code and the equipment identification code, and jumping to the step S56;
step S56: finding the equipment type of the equipment from the database, finding a corresponding decoder according to the equipment type, calling the decoder to analyze data, and storing the decoded data in the database in a related manner.
9. The method for realizing intelligent fire fighting based on the cloud platform of the internet of things as claimed in claim 2, wherein: in step S6, the method for calling the encoder to encode the issue instruction data includes the following steps:
step S61: the service platform transmits basic information and instruction data of the equipment to the equipment independence information acquisition and forwarding system, and the system stores original data to a database; finding the device type of the device from the database according to the basic information of the device, finding a corresponding encoder according to the device type, and jumping to step S62;
step S62: loading an encoder, calling the encoder, and encoding the command data into format data which can be recognized by equipment; storing the encoded data in a database, and jumping to step S63;
step S63: searching for connection according to the equipment information;
if found, go to step S64;
if not, jumping to step S65;
step S64: sending the coded instruction data through the long connection, and ending;
step S65: if no connection is found, returning abnormal information and ending.
10. The method for realizing intelligent fire fighting based on the cloud platform of the internet of things as claimed in claim 1, wherein: authentication of user login of an application system, comprising the steps of:
step S71, obtaining the request path of the user, comparing the database records, filtering and judging whether the request is the authority resource or the non-authority resource,
if the resource is a non-permission resource, authentication is not needed, and the step S73 is skipped;
if the resource is the authority resource, checking whether the Token is carried in the user request,
if no Token exists, judging that the request is illegal, and jumping to step S75;
if so, jumping to step S72;
step S72, the database compares whether the resource authorizes the user or the user group, if so, the preliminary authentication is successful, the Token validity is checked,
if Token is valid, jumping to step S74;
if Token is invalid, jumping to step S75;
step S73, the certification is passed, log is recorded, the authority is released, and the user is allowed to operate the resource;
step S74, the effective time of Token is defaulted to 30 minutes, and the expiration time of Token is reset according to the latest operation time of the user;
step S75, authentication is failed, and a user prompt of 'illegal operation' is returned to the user.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011101987.8A CN112365388A (en) | 2020-10-15 | 2020-10-15 | Method for realizing intelligent fire fighting based on Internet of things cloud platform |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011101987.8A CN112365388A (en) | 2020-10-15 | 2020-10-15 | Method for realizing intelligent fire fighting based on Internet of things cloud platform |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112365388A true CN112365388A (en) | 2021-02-12 |
Family
ID=74507661
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011101987.8A Pending CN112365388A (en) | 2020-10-15 | 2020-10-15 | Method for realizing intelligent fire fighting based on Internet of things cloud platform |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112365388A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113542411A (en) * | 2021-07-16 | 2021-10-22 | 江苏有熊安全科技有限公司 | Fire control thing networking integrated management platform |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101582762A (en) * | 2009-04-02 | 2009-11-18 | 北京飞天诚信科技有限公司 | Method and system for identity authentication based on dynamic password |
| CN106339951A (en) * | 2016-08-29 | 2017-01-18 | 王益忠 | IoT (Internet of Things) based intelligent agricultural greenhouse managing and tracking interaction system |
| CN111131403A (en) * | 2019-12-06 | 2020-05-08 | 深圳猛犸电动科技有限公司 | Message coding and decoding method and device for Internet of things equipment |
| CN111294401A (en) * | 2020-02-10 | 2020-06-16 | 泰华智慧产业集团股份有限公司 | Internet of things equipment access method and device |
-
2020
- 2020-10-15 CN CN202011101987.8A patent/CN112365388A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101582762A (en) * | 2009-04-02 | 2009-11-18 | 北京飞天诚信科技有限公司 | Method and system for identity authentication based on dynamic password |
| CN106339951A (en) * | 2016-08-29 | 2017-01-18 | 王益忠 | IoT (Internet of Things) based intelligent agricultural greenhouse managing and tracking interaction system |
| CN111131403A (en) * | 2019-12-06 | 2020-05-08 | 深圳猛犸电动科技有限公司 | Message coding and decoding method and device for Internet of things equipment |
| CN111294401A (en) * | 2020-02-10 | 2020-06-16 | 泰华智慧产业集团股份有限公司 | Internet of things equipment access method and device |
Non-Patent Citations (1)
| Title |
|---|
| 邢艺兰 等: "NB-IoT模块与电信物联网开放平台的通信研究", 《北华航天工业学院学报》 * |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113542411A (en) * | 2021-07-16 | 2021-10-22 | 江苏有熊安全科技有限公司 | Fire control thing networking integrated management platform |
| CN113542411B (en) * | 2021-07-16 | 2024-01-05 | 江苏有熊安全科技有限公司 | Fire control thing networking integrated management platform |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US9767441B2 (en) | System for monitoring elevators and maintaining elevators | |
| CN110427785B (en) | Equipment fingerprint acquisition method and device, storage medium and electronic device | |
| CN104025516A (en) | Systems and methods of remote communication | |
| CN110554930B (en) | Data storage method and related equipment | |
| US20140082430A1 (en) | Reporting product status information using a visual code | |
| EA019680B1 (en) | Service access method and system | |
| CN110347694B (en) | Equipment monitoring method, device and system based on Internet of things | |
| CN114202187A (en) | Power equipment intelligent identification analysis coding method based on power industry | |
| CN106100931A (en) | A kind of automobile factory intelligent maintaining maintenance system | |
| CN112365388A (en) | Method for realizing intelligent fire fighting based on Internet of things cloud platform | |
| CN109088773A (en) | Fault self-recovery method, apparatus, server and storage medium | |
| CN110143502A (en) | A kind of elevator monitoring based on Internet of Things, rescue method of disposal and system | |
| CN101944768B (en) | Power equipment state monitoring method, device and system | |
| CN109612517A (en) | Analysis method, data server, monitoring device and the medium of production exception | |
| CN110569993A (en) | Intelligent maintenance and maintenance system based on big data | |
| CN111807181A (en) | Web elevator monitoring platform | |
| KR20210072473A (en) | Data collection gateway having AI module | |
| CN116861708B (en) | Method and device for constructing multidimensional model of production equipment | |
| CN108829568A (en) | A kind of data monitoring method and device | |
| CN112422626A (en) | Device independence internet of things data acquisition, analysis and forwarding method based on coder and decoder | |
| CN111258857A (en) | Server state monitoring method and system | |
| CN107463568B (en) | Method and device for acquiring historical access data | |
| CN111445035B (en) | Store equipment management system based on block chain | |
| CN103023137A (en) | Electrical power regulation and control real-time information wireless remote monitoring system | |
| KR20210081065A (en) | Data collection edge device and data collection gateway having AI module |
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 | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20210212 |