CN112039945A - Third-party application docking method and system based on fire-fighting Internet of things platform - Google Patents
Third-party application docking method and system based on fire-fighting Internet of things platform Download PDFInfo
- Publication number
- CN112039945A CN112039945A CN202010737456.1A CN202010737456A CN112039945A CN 112039945 A CN112039945 A CN 112039945A CN 202010737456 A CN202010737456 A CN 202010737456A CN 112039945 A CN112039945 A CN 112039945A
- Authority
- CN
- China
- Prior art keywords
- fire
- data
- party application
- fighting
- message queue
- 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 57
- 238000003032 molecular docking Methods 0.000 title claims abstract description 43
- 238000012545 processing Methods 0.000 claims abstract description 21
- 230000006855 networking Effects 0.000 claims abstract description 5
- 230000003993 interaction Effects 0.000 claims description 9
- 210000001503 joint Anatomy 0.000 claims description 3
- XLYOFNOQVPJJNP-UHFFFAOYSA-N water Substances O XLYOFNOQVPJJNP-UHFFFAOYSA-N 0.000 claims description 3
- 230000008901 benefit Effects 0.000 abstract description 3
- 230000015654 memory Effects 0.000 description 18
- 230000005291 magnetic effect Effects 0.000 description 10
- 230000008569 process Effects 0.000 description 7
- 238000005516 engineering process Methods 0.000 description 5
- 238000004590 computer program Methods 0.000 description 4
- 230000006870 function Effects 0.000 description 4
- 230000003287 optical effect Effects 0.000 description 4
- 238000004458 analytical method Methods 0.000 description 3
- 230000009286 beneficial effect Effects 0.000 description 3
- 238000010586 diagram Methods 0.000 description 3
- 238000012986 modification Methods 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 230000005540 biological transmission Effects 0.000 description 2
- 230000008859 change Effects 0.000 description 2
- 238000005034 decoration Methods 0.000 description 2
- 230000004044 response Effects 0.000 description 2
- 230000003068 static effect Effects 0.000 description 2
- 206010063385 Intellectualisation Diseases 0.000 description 1
- 238000003491 array Methods 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000012795 verification Methods 0.000 description 1
- 230000003936 working memory Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/0631—Management of faults, events, alarms or notifications using root cause analysis; using analysis of correlation between notifications, alarms or events based on decision criteria, e.g. hierarchy, tree or time analysis
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
- H04L63/0807—Network architectures or network communication protocols for network security for authentication of entities using tickets, e.g. Kerberos
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
- H04L63/083—Network architectures or network communication protocols for network security for authentication of entities using passwords
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/53—Network services using third party service providers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/55—Push-based network services
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computing Systems (AREA)
- Computer Hardware Design (AREA)
- Computer Security & Cryptography (AREA)
- General Engineering & Computer Science (AREA)
- Health & Medical Sciences (AREA)
- General Health & Medical Sciences (AREA)
- Medical Informatics (AREA)
- Alarm Systems (AREA)
Abstract
The invention relates to the technical field of third-party application docking in a fire-fighting Internet of things, and provides a third-party application docking method and system based on a fire-fighting Internet of things platform, wherein the method comprises the following steps: s1: the method comprises the steps that fire fighting equipment installed on a building is connected into a fire fighting Internet of things platform, fire fighting data collected by the fire fighting equipment are obtained, and the fire fighting data are routed to the fire fighting Internet of things platform; s2: the fire-fighting Internet of things platform provides the fire-fighting data to a third-party application in a real-time pushing mode including providing an http access interface and a message queue; s3: and the third-party application performs processing including fault removal on the received fire fighting data. Can dock the application and the fire control thing networking platform of third party to do benefit to the application of third party and can directly obtain fire control data from fire control thing networking platform, do subsequent processing to the fire control data.
Description
Technical Field
The invention relates to the technical field of third-party application docking in a fire-fighting Internet of things, in particular to a third-party application docking method and system based on a fire-fighting Internet of things platform.
Background
The internet of things is proposed in the last 90 th century in the united states, and means that sensors, controllers, machines, personnel, objects and the like are connected together in a new mode by using communication technologies such as local networks or the internet and the like to form networks for people-to-objects, object-to-object connection and information, remote management control and intellectualization. The internet of things is an extension of the internet, comprises the internet and all resources on the internet, and is compatible with all applications of the internet.
In the field of fire protection, the system also has a fire protection internet of things of the system, and team personnel for maintaining fire protection, buildings, equipment on the buildings and the like need to be connected together. Based on the fire-fighting internet of things, a platform of the fire-fighting internet of things is generally established, and all information related to fire fighting is displayed.
When the application of the third party needs to acquire the fire-fighting data, it is impossible that the application of each third party goes to a building to set the acquisition equipment to directly acquire the fire-fighting data. The platform of the fire-fighting Internet of things has huge fire-fighting data, so that the fire-fighting data is the most available, and if the application of a third party can directly acquire the data from the platform of the fire-fighting Internet of things, great ergodicity can be provided for the third party platform. At the moment, the problem of how to dock the application of the third party with the fire-fighting internet of things platform is related, and a method capable of realizing the docking of the application of the third party with the fire-fighting internet of things platform is urgently needed to be found so as to be beneficial to the fact that the application of the third party can directly acquire fire-fighting data from the fire-fighting internet of things platform.
Disclosure of Invention
In order to solve the problems, the invention aims to provide a third-party application docking method and system based on a fire-fighting internet of things platform.
The above object of the present invention is achieved by the following technical solutions:
a third party application docking method based on a fire-fighting Internet of things platform comprises the following steps:
s1: the method comprises the steps that fire fighting equipment installed on a building is connected into a fire fighting Internet of things platform, fire fighting data collected by the fire fighting equipment are obtained, and the fire fighting data are routed to the fire fighting Internet of things platform;
s2: the fire-fighting Internet of things platform provides the fire-fighting data to a third-party application in a real-time pushing mode including providing an http access interface and a message queue;
the http access interface mode is as follows: providing the http access interface aiming at historical data in the fire-fighting data, and calling the http access interface to acquire the historical data when the historical data needs to be inquired by the third-party application; the message queue real-time pushing mode is as follows: for fault data needing to be processed immediately in the fire protection data, when a fault occurs, when the fire protection Internet of things platform receives the fault data collected by the fire protection equipment, the fault data is immediately pushed to the third party application in a real-time pushing mode through the message queue, so that the fault on the building can be processed in time;
s3: and the third-party application performs processing including fault removal on the received fire fighting data.
Further, the http access interface specifically includes:
establishing a corresponding http access interface aiming at each historical data comprising building list data, building point position information, building fire alarm information, building fault information, building hidden danger information, building supervision information, building linkage information, building equipment state timely data information and building equipment state historical data information, wherein the http access interface comprises a request URL, request parameters and return parameters;
when the historical data needs to be obtained, the third-party application transmits the request parameters to the fire-fighting Internet of things platform through the corresponding request parameter URL of the http access interface according to needs, and sends an http request to the fire-fighting Internet of things platform, and the fire-fighting Internet of things platform provides the third-party application with data matched with the type of the returned parameters.
Further, before the third-party application sends a request through the http access interface, the fire fighting internet of things platform further needs to verify the identity of the third-party application, which specifically includes:
the third-party application provides a docking request to the fire-fighting Internet of things platform, and the fire-fighting Internet of things platform distributes a user name and a password to the third-party application;
before the third-party application sends an http request and obtains the historical data, calling the http access interface for logging in through the request parameters including the user name and the password, and returning a token for marking the identity of the third-party application by the fire-fighting Internet of things platform;
when the historical data are obtained, a token for marking the identity of the third-party application is transmitted into a request header of the http access interface, the http access interface is called, and the fire-fighting Internet of things platform returns the historical data within the third-party application permission range;
wherein the token for marking the identity of the third-party application is: a token string containing identity information of the third party application generated by a JWT rights authentication encryption tool.
Further, the message queue is pushed in real time, specifically:
respectively establishing a server side of the message queue on the fire-fighting Internet of things platform, establishing a client side of the message queue on the third-party application, and realizing data interaction between the server side and the client side by adopting a RabbitMQ message queue framework;
the server is connected to the RabbitMQ message queue frame, the fault data is created and issued, and after the issuance is finished, the connection with the RabbitMQ message queue frame is closed;
and the client is connected to the RabbitMQ message queue frame, acquires the fault data and closes the connection with the RabbitMQ message queue frame after the acquisition is completed.
Further, before performing real-time pushing of the message queue, the method further includes:
setting information including a server domain name, a server user name, a server password and a server port number on the server;
and before the client acquires the fault data and establishes connection with the RabbitMQ message queue framework, the client needs to bind information including the domain name of the server, the user name of the server, the password of the server and the port number of the server.
A third party application docking system based on a fire-fighting Internet of things platform comprises: the system comprises a fire-fighting data acquisition module, a third-party application docking module and a fire-fighting data processing module;
the fire fighting data acquisition module is used for connecting fire fighting equipment installed on a building into a fire fighting Internet of things platform, acquiring fire fighting data acquired by the fire fighting equipment and routing the fire fighting data to the fire fighting Internet of things platform;
the third-party application docking module is used for providing the fire-fighting data to the third-party application by the fire-fighting Internet of things platform in a real-time pushing mode including providing an http access interface and a message queue; the http access interface mode is as follows: providing the http access interface aiming at historical data in the fire-fighting data, and calling the http access interface to acquire the historical data when the historical data needs to be inquired by the third-party application; the message queue real-time pushing mode is as follows: for fault data needing to be processed immediately in the fire protection data, when a fault occurs, when the fire protection Internet of things platform receives the fault data collected by the fire protection equipment, the fault data is immediately pushed to the third party application in a real-time pushing mode through the message queue, so that the fault on the building can be processed in time;
and the fire-fighting data processing module is used for providing the third-party application with the received fire-fighting data to perform processing including fault removal.
Further, the third party application docking module further includes:
the http access interface establishing unit is used for establishing a corresponding http access interface aiming at each historical data including building list data, building point position information, current fire alarm of a building, current faults of the building, building water system-pressure gauge data and current building supervision information, wherein the http access interface comprises a request URL (uniform resource locator), request parameters and return parameters; when the historical data needs to be obtained, the third-party application transmits an http request to the fire-fighting Internet of things platform through the request parameter URL of the corresponding http access interface according to the request parameter needed, and the fire-fighting Internet of things platform provides the returned data matched with the type of the returned parameter for the third-party application;
the message queue establishing unit is used for establishing a server side of the message queue on the fire-fighting Internet of things platform, establishing a client side of the message queue on the third-party application, and realizing data interaction between the server side and the client side by adopting a RabbitMQ message queue framework; the server is connected to the RabbitMQ message queue frame, the fault data is created and issued, and after the issuance is finished, the connection with the RabbitMQ message queue frame is closed; and the client is connected to the RabbitMQ message queue frame, acquires the fault data and closes the connection with the RabbitMQ message queue frame after the acquisition is completed.
A third-party application docking method for a data platform specifically comprises the following steps: providing two modes of an http access interface and a real-time pushing of a message queue;
the http access interface mode is as follows: aiming at historical data, providing the http access interface, and calling the http access interface to acquire the historical data when the third-party application needs to inquire the historical data;
the message queue real-time pushing mode is as follows: for data needing to be processed immediately, when the data platform receives the data, the data is immediately pushed to the third-party application in a real-time pushing mode through the message queue, so that the data can be processed in time;
further, the http access interface specifically includes:
establishing a corresponding http access interface aiming at each type of historical data, wherein the http access interface comprises a request URL, request parameters and return parameters;
when the historical data needs to be obtained, the third-party application transmits an http request to the data platform through the request parameter URL of the corresponding http access interface according to the request parameter needed, and the data platform provides the returned data matched with the type of the returned parameter for the third-party application;
further, the message queue is pushed in real time, specifically:
respectively establishing a server side of the message queue on the data platform, establishing a client side of the message queue on the third-party application, and realizing data interaction between the server side and the client side by adopting a RabbitMQ message queue framework;
the server is connected to the RabbitMQ message queue frame, creates and releases the data needing to be processed immediately, and closes the connection with the RabbitMQ message queue frame after the release is finished;
and the client is connected to the RabbitMQ message queue frame, acquires the data needing to be processed immediately, and closes the connection with the RabbitMQ message queue frame after the acquisition is completed.
Compared with the prior art, the invention has at least one of the following beneficial effects:
(1) by providing the third-party application docking method based on the fire-fighting Internet of things platform, the method specifically comprises the following steps: s1: the method comprises the steps that fire fighting equipment installed on a building is connected into a fire fighting Internet of things platform, fire fighting data collected by the fire fighting equipment are obtained, and the fire fighting data are routed to the fire fighting Internet of things platform; s2: the fire-fighting Internet of things platform provides the fire-fighting data to a third-party application in a real-time pushing mode including providing an http access interface and a message queue; the http access interface mode is as follows: providing the http access interface aiming at historical data in the fire-fighting data, and calling the http access interface to acquire the historical data when the historical data needs to be inquired by the third-party application; the message queue real-time pushing mode is as follows: for fault data needing to be processed immediately in the fire protection data, when a fault occurs, when the fire protection Internet of things platform receives the fault data collected by the fire protection equipment, the fault data is immediately pushed to the third party application in a real-time pushing mode through the message queue, so that the fault on the building can be processed in time; s3: and the third-party application performs processing including fault removal on the received fire fighting data. According to the technical scheme, the application of the third party is in butt joint with the fire-fighting Internet of things platform, so that the application of the third party can directly acquire fire-fighting data from the fire-fighting Internet of things platform, and subsequent processing is performed on the fire-fighting data. The invention respectively adopts two different modes of real-time pushing of an http access interface and a message queue aiming at two types of data with different response levels of historical data and fault data, the http access interface is called when the historical data needs to be obtained, the historical data can be obtained, and the fault data with high response level and needing to be immediately processed by a manager is pushed in real time through the message queue. And the fault data can be processed in time under the condition of ensuring the effective utilization of server resources.
(2) Before a third-party application sends a request through the http access interface, the fire fighting internet of things platform further needs to verify the identity of the third-party application, and specifically comprises the following steps: the third-party application provides a docking request to the fire-fighting Internet of things platform, and the fire-fighting Internet of things platform distributes a user name and a password to the third-party application; before the third-party application sends an http request and obtains the historical data, calling the http access interface for logging in through the request parameters including the user name and the password, and returning a token for marking the identity of the third-party application by the fire-fighting Internet of things platform; when the historical data are obtained, a token for marking the identity of the third-party application is transmitted into a request header of the http access interface, the http access interface is called, and the fire-fighting Internet of things platform returns the historical data within the third-party application permission range; wherein the token for marking the identity of the third-party application is: a token string containing identity information of the third party application generated by a JWT rights authentication encryption tool. Through establishing the technical scheme, identity verification is carried out on the third-party application, the fact that the third-party application capable of acquiring the fire protection data on the fire protection Internet of things platform is authorized by the user is ensured, and the fact that the fire protection data are maliciously stolen by other people is avoided. Meanwhile, after identity authentication is set for the third-party application, different authorities can be bound on different identities, and the third-party application can only acquire fire-fighting data within the authority range of the third-party application.
(3) Before the real-time pushing of the message queue, the method further comprises the following steps: setting information including a server domain name, a server user name, a server password and a server port number on the server; and before the client acquires the fault data and establishes connection with the RabbitMQ message queue framework, the client needs to bind information including the domain name of the server, the user name of the server, the password of the server and the port number of the server. In the technical scheme, when the third party is applied to acquiring the fire-fighting data, the server domain name, the server user name, the server password and the server port number of the server corresponding to the Internet of things platform must be bound, so that the safety of real-time pushing of the message queue is ensured.
Drawings
FIG. 1 is an overall flow chart of a third-party application docking method based on a fire-fighting Internet of things platform according to the invention;
FIG. 2 is an overall structure diagram of a third-party application docking system based on a fire-fighting Internet of things platform according to the invention;
fig. 3 is a structural diagram of a third party application docking module in the third party application docking system based on the fire-fighting internet of things platform.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
As used herein, the singular forms "a", "an", "the" and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms "comprises" and/or "comprising," when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
In the field of fire protection, the system also has a fire protection internet of things of the system, and team personnel for maintaining fire protection, buildings, equipment on the buildings and the like need to be connected together. Based on the fire-fighting internet of things, a platform of the fire-fighting internet of things is generally established, and all information related to fire fighting is displayed. When the application of the third party needs to acquire the fire-fighting data, it is impossible that the application of each third party goes to a building to set the acquisition equipment to directly acquire the fire-fighting data. The platform of the fire-fighting Internet of things has huge fire-fighting data, so that the fire-fighting data is the most available, and if the application of a third party can directly acquire the data from the platform of the fire-fighting Internet of things, great ergodicity can be provided for the third party platform. At the moment, the problem of how to dock the application of the third party with the fire-fighting internet of things platform is related, and a method capable of realizing the docking of the application of the third party with the fire-fighting internet of things platform is urgently needed to be found so as to be beneficial to the fact that the application of the third party can directly acquire fire-fighting data from the fire-fighting internet of things platform.
Based on the application scenarios and the technical problems, the core thought of the invention is as follows: the method comprises the steps that the fire protection data are provided for third-party application in a mode of providing an http access interface and pushing a message queue in real time, the application of the third party is in butt joint with a fire protection Internet of things platform, so that the application of the third party can directly obtain the fire protection data from the fire protection Internet of things platform, and subsequent processing is carried out on the fire protection data.
The invention has the following remarkable characteristics: the third party application does not need to set fire fighting equipment on the building by oneself to carry out the collection of fire control data, and the fire control data just can be obtained to the thing networking platform that inserts us directly, has saved a series of flows such as hardware analysis, data routing.
First embodiment
As shown in fig. 1, the overall flowchart of the third-party application docking method based on the fire-fighting internet of things platform of the present invention includes the following steps:
s1: the fire fighting equipment installed on the building is connected into the fire fighting Internet of things platform, the fire fighting data collected by the fire fighting equipment is acquired, and the fire fighting data is routed to the fire fighting Internet of things platform.
Specifically, in this embodiment, before the third party application performs data docking with the fire protection internet of things platform, the fire protection internet of things platform needs to save fire protection data collected by fire protection equipment installed on a building on a database corresponding to the fire protection internet of things platform. The process of hardware analysis and data routing for the fire fighting equipment is related, and is not described herein.
For example, aiming at historical data, various fire fighting equipment installed on a European supermarket building uploads fire fighting data, and the fire fighting data are stored in a database corresponding to a fire fighting Internet of things platform through hardware analysis and data routing; aiming at fault data, various fire fighting devices on the European supermarket building are analyzed by hardware and sent by kafka, and the fire fighting Internet of things platform can receive the fault data uploaded by the kafka.
S2: the fire-fighting Internet of things platform provides the fire-fighting data for third-party application in a manner of providing an http access interface and pushing a message queue in real time.
(1) The application scenario of the http access interface mode is as follows: and providing the http access interface aiming at historical data in the fire-fighting data, and calling the http access interface to acquire the historical data when the third-party application needs to inquire the historical data.
The http access interface comprises the following specific processes:
and establishing a corresponding http access interface aiming at each historical data comprising building list data, building point position information, building fire alarm information, building fault information, building hidden danger information, building supervision information, building linkage information, building equipment state timely data information and building equipment state historical data information, wherein the http access interface comprises a request URL, request parameters and return parameters. It should be noted that the above mentioned types of history data are only examples, and in practical applications, different history data are designed according to actual requirements, and operations such as adding, modifying, deleting and the like are performed at any time.
An example of an actual http access interface is listed below for explaining the http access interface of the present invention:
the interface functions as follows: obtaining a building list of a currently logged-in user
HTTP request mode: GET (GET tool)
Request URL: http:// openapi. layer. cn: 8886/layer/building/list
Request parameters:
returning parameters:
when the historical data needs to be obtained, the third-party application transmits the request parameters to the fire-fighting Internet of things platform through the corresponding request parameter URL of the http access interface according to needs, and sends an http request to the fire-fighting Internet of things platform, and the fire-fighting Internet of things platform provides the third-party application with data matched with the type of the returned parameters.
Further, before the third-party application sends a request through the http access interface, the fire fighting internet of things platform further needs to verify the identity of the third-party application, which specifically includes:
the third-party application provides a docking request to the fire-fighting Internet of things platform, and the fire-fighting Internet of things platform distributes a user name and a password to the third-party application. Because the fire-fighting data has certain confidentiality, the application needs to be provided for the fire-fighting Internet of things platform in advance, and the subsequent access operation can be performed only after the fire-fighting Internet of things platform distributes and provides the corresponding user name and password.
Before the third-party application sends an http request and obtains the historical data, the http access interface used for logging in is called through the request parameters including the user name and the password, and the fire-fighting Internet of things platform returns a token used for marking the identity of the third-party application. User information is contained in the token, the token is carried for access in subsequent access, and the identity of the third-party application can be confirmed by the fire-fighting Internet of things platform.
And when the historical data is obtained, a token for marking the identity of the third-party application is transmitted into a request head of the http access interface, the http access interface is called, and the fire-fighting Internet of things platform returns the historical data in the third-party application permission range. The advantage of design like this has avoided the fire control data to reveal for other fire control thing networking platforms not authorized application while, can also increase the authority to the third party application at the background, returns the fire control data that the third party application of corresponding identity can obtain according to the authority.
Wherein the token for marking the identity of the third-party application is: a token string containing identity information of the third party application generated by a JWT rights authentication encryption tool.
(2) The application scenario of the message queue real-time pushing mode is as follows: aiming at the fault data needing to be processed immediately in the fire-fighting data, when a fault occurs, when the fire-fighting Internet of things platform receives the fault data collected by the fire-fighting equipment, the fault data is pushed to the third party application in a real-time pushing mode through the message queue, so that the fault on the building can be processed in time.
The message queue is pushed in real time, and the specific process is as follows:
and respectively establishing a server side of the message queue on the fire-fighting Internet of things platform, establishing a client side of the message queue on the third-party application, and realizing data interaction between the server side and the client side by adopting a RabbitMQ message queue framework.
And the server is connected to the RabbitMQ message queue framework, creates and releases the fault data, and closes the connection with the RabbitMQ message queue framework after the release is completed.
And the client is connected to the RabbitMQ message queue frame, acquires the fault data and closes the connection with the RabbitMQ message queue frame after the acquisition is completed.
The following provides examples of several types of fault data, which are issued by a server and received by a client:
data received from fire alarm
Second, data of fault acceptance
Thirdly, processing the data of the fire alarm
Fourthly, processing fault data
Before the real-time pushing of the message queue, the method further comprises the following steps:
setting information including a server domain name, a server user name, a server password and a server port number on the server;
before the client acquires the fault data and establishes connection with the RabbitMQ message queue framework, the client needs to bind information including the server domain name, the server user name, the server password and the server port number, so that the safety of real-time pushing of the message queue is ensured.
S3: and the third-party application performs processing including fault removal on the received fire fighting data.
Specifically, in this embodiment, after the third-party application receives the fire-fighting data, if the fire-fighting data is failure data, the third-party application assigns the dockee to process the fire-fighting data quickly.
Second embodiment
As shown in fig. 2, it is an overall structure diagram of a third party application docking system based on a fire-fighting internet of things platform, and it includes: the system comprises a fire-fighting data acquisition module 1, a third-party application butt-joint module 2 and a fire-fighting data processing module 3;
the fire fighting data acquisition module 1 is used for connecting fire fighting equipment installed on a building into a fire fighting Internet of things platform, acquiring fire fighting data acquired by the fire fighting equipment and routing the fire fighting data to the fire fighting Internet of things platform;
the third-party application docking module 2 is used for providing the fire-fighting data to the third-party application by the fire-fighting Internet of things platform in a real-time pushing mode including providing an http access interface and a message queue; the http access interface mode is as follows: providing the http access interface aiming at historical data in the fire-fighting data, and calling the http access interface to acquire the historical data when the historical data needs to be inquired by the third-party application; the message queue real-time pushing mode is as follows: for fault data needing to be processed immediately in the fire protection data, when a fault occurs, when the fire protection Internet of things platform receives the fault data collected by the fire protection equipment, the fault data is immediately pushed to the third party application in a real-time pushing mode through the message queue, so that the fault on the building can be processed in time;
and the fire-fighting data processing module 3 is used for providing the third-party application with processing including fault removal aiming at the received fire-fighting data.
Further, as shown in fig. 3, the third-party application docking module 2 further includes:
the http access interface establishing unit 21 is configured to establish a corresponding http access interface for each historical data, including building list data, building point location information, a current fire alarm of a building, a current fault of the building, building water system-pressure gauge data, and current building supervision information, where the http access interface includes a request URL, a request parameter, and a return parameter; when the historical data needs to be obtained, the third-party application transmits an http request to the fire-fighting Internet of things platform through the request parameter URL of the corresponding http access interface according to the request parameter needed, and the fire-fighting Internet of things platform provides the returned data matched with the type of the returned parameter for the third-party application;
in the http access interface establishing unit 21, before the third party application sends the request through the http access interface, the platform of the fire fighting internet of things further needs to verify the identity of the third party application, which specifically includes: the third-party application provides a docking request to the fire-fighting Internet of things platform, and the fire-fighting Internet of things platform distributes a user name and a password to the third-party application; before the third-party application sends an http request and obtains the historical data, calling the http access interface for logging in through the request parameters including the user name and the password, and returning a token for marking the identity of the third-party application by the fire-fighting Internet of things platform; when the historical data are obtained, a token for marking the identity of the third-party application is transmitted into a request header of the http access interface, the http access interface is called, and the fire-fighting Internet of things platform returns the historical data within the third-party application permission range; wherein the token for marking the identity of the third-party application is: a token string containing identity information of the third party application generated by a JWT rights authentication encryption tool.
The message queue establishing unit 22 is configured to establish a server of the message queue on the platform of the fire fighting internet of things, establish a client of the message queue on the third party application, and implement data interaction between the server and the client by using a RabbitMQ message queue framework; the server is connected to the RabbitMQ message queue frame, the fault data is created and issued, and after the issuance is finished, the connection with the RabbitMQ message queue frame is closed; and the client is connected to the RabbitMQ message queue frame, acquires the fault data and closes the connection with the RabbitMQ message queue frame after the acquisition is completed.
In the message queue establishing unit 22, before performing real-time pushing of the message queue, the method further includes: setting information including a server domain name, a server user name, a server password and a server port number on the server; and before the client acquires the fault data and establishes connection with the RabbitMQ message queue framework, the client needs to bind information including the domain name of the server, the user name of the server, the password of the server and the port number of the server.
Third embodiment
Different from the first embodiment, the present embodiment provides a third-party application docking method for a data platform, which specifically includes two modes, namely providing an http access interface and pushing a message queue in real time. The method in the embodiment can be applied to all the computing fields needing to realize the interface between the third-party application and the data platform. The third-party application docking of the fire-fighting internet of things platform is only one of the most typical application scenarios of the invention.
The http access interface mode is as follows: aiming at historical data, providing the http access interface, and calling the http access interface to acquire the historical data when the third-party application needs to inquire the historical data;
the message queue real-time pushing mode is as follows: for data needing to be processed immediately, when the data platform receives the data, the data is immediately pushed to the third-party application in a real-time pushing mode through the message queue, so that the data can be processed in time;
further, the http access interface specifically includes:
establishing a corresponding http access interface aiming at each type of historical data, wherein the http access interface comprises a request URL, request parameters and return parameters;
when the historical data needs to be obtained, the third-party application transmits an http request to the data platform through the request parameter URL of the corresponding http access interface according to the request parameter needed, and the data platform provides the returned data matched with the type of the returned parameter for the third-party application;
further, the message queue is pushed in real time, specifically:
respectively establishing a server side of the message queue on the data platform, establishing a client side of the message queue on the third-party application, and realizing data interaction between the server side and the client side by adopting a RabbitMQ message queue framework;
the server is connected to the RabbitMQ message queue frame, creates and releases the data needing to be processed immediately, and closes the connection with the RabbitMQ message queue frame after the release is finished;
and the client is connected to the RabbitMQ message queue frame, acquires the data needing to be processed immediately, and closes the connection with the RabbitMQ message queue frame after the acquisition is completed.
A computer readable storage medium storing computer code which, when executed, performs the method as described above. Those skilled in the art will appreciate that all or part of the steps in the methods of the above embodiments may be implemented by associated hardware instructed by a program, which may be stored in a computer-readable storage medium, and the storage medium may include: read Only Memory (ROM), Random Access Memory (RAM), magnetic or optical disks, and the like.
The above description is only a preferred embodiment of the present invention, and the protection scope of the present invention is not limited to the above embodiments, and all technical solutions belonging to the idea of the present invention belong to the protection scope of the present invention. It should be noted that modifications and embellishments within the scope of the invention may occur to those skilled in the art without departing from the principle of the invention, and are considered to be within the scope of the invention.
The technical features of the embodiments described above may be arbitrarily combined, and for the sake of brevity, all possible combinations of the technical features in the embodiments described above are not described, but should be considered as being within the scope of the present specification as long as there is no contradiction between the combinations of the technical features.
It should be noted that the above embodiments can be freely combined as necessary. The foregoing is only a preferred embodiment of the present invention, and it should be noted that, for those skilled in the art, various modifications and decorations can be made without departing from the principle of the present invention, and these modifications and decorations should also be regarded as the protection scope of the present invention.
The software program of the present invention can be executed by a processor to implement the steps or functions described above. Also, the software programs (including associated data structures) of the present invention can be stored in a computer readable recording medium, such as RAM memory, magnetic or optical drive or diskette and the like. Additionally, some of the steps or functionality of the present invention may be implemented in hardware, for example, as circuitry that cooperates with the processor to perform various functions or steps. The method disclosed by the embodiment shown in the embodiment of the present specification can be applied to or realized by a processor. The processor may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method may be performed by integrated logic circuits of hardware in a processor or instructions in the form of software. The Processor may be a general-purpose Processor, including a Central Processing Unit (CPU), a Network Processor (NP), and the like; but also Digital Signal Processors (DSPs), Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) or other Programmable logic devices, discrete Gate or transistor logic devices, discrete hardware components. The various methods, steps and logic blocks disclosed in the embodiments of the present specification may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of a method disclosed in connection with the embodiments of the present specification may be embodied directly in a hardware decoding processor, or in a combination of hardware and software modules in the decoding processor. The software module may be located in ram, flash memory, rom, prom, or eprom, registers, etc. storage media as is well known in the art. The storage medium is located in a memory, and a processor reads information in the memory and completes the steps of the method in combination with hardware of the processor.
Embodiments also provide a computer readable storage medium storing one or more programs that, when executed by an electronic system including a plurality of application programs, cause the electronic system to perform the method of embodiment one. And will not be described in detail herein.
Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.
The systems, devices, modules or units illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product with certain functions. One typical implementation device is a computer. In particular, the computer may be, for example, a personal computer, a laptop computer, a cellular telephone, a camera phone, a smartphone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices. Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave. It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
In addition, some of the present invention can be applied as a computer program product, such as computer program instructions, which when executed by a computer, can invoke or provide the method and/or technical solution according to the present invention through the operation of the computer. Program instructions which invoke the methods of the present invention may be stored on a fixed or removable recording medium and/or transmitted via a data stream on a broadcast or other signal-bearing medium and/or stored within a working memory of a computer device operating in accordance with the program instructions. An embodiment according to the invention herein comprises an apparatus comprising a memory for storing computer program instructions and a processor for executing the program instructions, wherein the computer program instructions, when executed by the processor, trigger the apparatus to perform a method and/or solution according to embodiments of the invention as described above.
Claims (10)
1. A third party application docking method based on a fire-fighting Internet of things platform is characterized by comprising the following steps:
s1: the method comprises the steps that fire fighting equipment installed on a building is connected into a fire fighting Internet of things platform, fire fighting data collected by the fire fighting equipment are obtained, and the fire fighting data are routed to the fire fighting Internet of things platform;
s2: the fire-fighting Internet of things platform provides the fire-fighting data to a third-party application in a real-time pushing mode including providing an http access interface and a message queue;
the http access interface mode is as follows: providing the http access interface aiming at historical data in the fire-fighting data, and calling the http access interface to acquire the historical data when the historical data needs to be inquired by the third-party application; the message queue real-time pushing mode is as follows: for fault data needing to be processed immediately in the fire protection data, when a fault occurs, when the fire protection Internet of things platform receives the fault data collected by the fire protection equipment, the fault data is immediately pushed to the third party application in a real-time pushing mode through the message queue, so that the fault on the building can be processed in time;
s3: and the third-party application performs processing including fault removal on the received fire fighting data.
2. The fire-fighting internet of things platform-based third-party application docking method according to claim 1, wherein the http access interface specifically is:
establishing a corresponding http access interface aiming at each historical data comprising building list data, building point position information, building fire alarm information, building fault information, building hidden danger information, building supervision information, building linkage information, building equipment state timely data information and building equipment state historical data information, wherein the http access interface comprises a request URL, request parameters and return parameters;
when the historical data needs to be obtained, the third-party application transmits the request parameters to the fire-fighting Internet of things platform through the corresponding request parameter URL of the http access interface according to needs, and sends an http request to the fire-fighting Internet of things platform, and the fire-fighting Internet of things platform provides the third-party application with data matched with the type of the returned parameters.
3. The fire fighting internet of things platform-based third party application docking method according to claim 2, wherein before the third party application sends the request through the http access interface, the fire fighting internet of things platform further needs to verify the identity of the third party application, specifically:
the third-party application provides a docking request to the fire-fighting Internet of things platform, and the fire-fighting Internet of things platform distributes a user name and a password to the third-party application;
before the third-party application sends an http request and obtains the historical data, calling the http access interface for logging in through the request parameters including the user name and the password, and returning a token for marking the identity of the third-party application by the fire-fighting Internet of things platform;
when the historical data are obtained, a token for marking the identity of the third-party application is transmitted into a request header of the http access interface, the http access interface is called, and the fire-fighting Internet of things platform returns the historical data within the third-party application permission range;
wherein the token for marking the identity of the third-party application is: a token string containing identity information of the third party application generated by a JWT rights authentication encryption tool.
4. The fire-fighting internet of things platform-based third-party application docking method according to claim 1, wherein the message queue is pushed in real time, and specifically comprises:
respectively establishing a server side of the message queue on the fire-fighting Internet of things platform, establishing a client side of the message queue on the third-party application, and realizing data interaction between the server side and the client side by adopting a RabbitMQ message queue framework;
the server is connected to the RabbitMQ message queue frame, the fault data is created and issued, and after the issuance is finished, the connection with the RabbitMQ message queue frame is closed;
and the client is connected to the RabbitMQ message queue frame, acquires the fault data and closes the connection with the RabbitMQ message queue frame after the acquisition is completed.
5. The fire-fighting internet of things platform-based third-party application docking method according to claim 4, wherein before the message queue is pushed in real time, the method further comprises:
setting information including a server domain name, a server user name, a server password and a server port number on the server;
and before the client acquires the fault data and establishes connection with the RabbitMQ message queue framework, the client needs to bind information including the domain name of the server, the user name of the server, the password of the server and the port number of the server.
6. The utility model provides a third party uses butt joint system based on fire control thing networking platform which characterized in that includes: the system comprises a fire-fighting data acquisition module, a third-party application docking module and a fire-fighting data processing module;
the fire fighting data acquisition module is used for connecting fire fighting equipment installed on a building into a fire fighting Internet of things platform, acquiring fire fighting data acquired by the fire fighting equipment and routing the fire fighting data to the fire fighting Internet of things platform;
the third-party application docking module is used for providing the fire-fighting data to the third-party application by the fire-fighting Internet of things platform in a real-time pushing mode including providing an http access interface and a message queue; the http access interface mode is as follows: providing the http access interface aiming at historical data in the fire-fighting data, and calling the http access interface to acquire the historical data when the historical data needs to be inquired by the third-party application; the message queue real-time pushing mode is as follows: for fault data needing to be processed immediately in the fire protection data, when a fault occurs, when the fire protection Internet of things platform receives the fault data collected by the fire protection equipment, the fault data is immediately pushed to the third party application in a real-time pushing mode through the message queue, so that the fault on the building can be processed in time;
and the fire-fighting data processing module is used for providing the third-party application with the received fire-fighting data to perform processing including fault removal.
7. The fire-fighting internet of things platform-based third-party application docking system according to claim 6, wherein the third-party application docking module further comprises:
the http access interface establishing unit is used for establishing a corresponding http access interface aiming at each historical data including building list data, building point position information, current fire alarm of a building, current faults of the building, building water system-pressure gauge data and current building supervision information, wherein the http access interface comprises a request URL (uniform resource locator), request parameters and return parameters; when the historical data needs to be obtained, the third-party application transmits an http request to the fire-fighting Internet of things platform through the request parameter URL of the corresponding http access interface according to the request parameter needed, and the fire-fighting Internet of things platform provides the returned data matched with the type of the returned parameter for the third-party application;
the message queue establishing unit is used for establishing a server side of the message queue on the fire-fighting Internet of things platform, establishing a client side of the message queue on the third-party application, and realizing data interaction between the server side and the client side by adopting a RabbitMQ message queue framework; the server is connected to the RabbitMQ message queue frame, the fault data is created and issued, and after the issuance is finished, the connection with the RabbitMQ message queue frame is closed; and the client is connected to the RabbitMQ message queue frame, acquires the fault data and closes the connection with the RabbitMQ message queue frame after the acquisition is completed.
8. A third party application docking method of a data platform is characterized by specifically comprising two modes of providing an http access interface and pushing a message queue in real time;
the http access interface mode is as follows: aiming at historical data, providing the http access interface, and calling the http access interface to acquire the historical data when the third-party application needs to inquire the historical data;
the message queue real-time pushing mode is as follows: and aiming at the data needing to be processed immediately, when the data platform receives the data, the data is immediately pushed to the third-party application in a real-time pushing mode through the message queue, so that the data can be processed in time.
9. The third-party application docking method for the data platform according to claim 8, wherein the http access interface specifically is:
establishing a corresponding http access interface aiming at each type of historical data, wherein the http access interface comprises a request URL, request parameters and return parameters;
when the historical data needs to be obtained, the third-party application transmits an http request to the data platform through the request parameter URL of the corresponding http access interface according to the request parameter needed, and the data platform provides the returned data matched with the type of the returned parameter for the third-party application;
the message queue real-time pushing specifically comprises the following steps:
respectively establishing a server side of the message queue on the data platform, establishing a client side of the message queue on the third-party application, and realizing data interaction between the server side and the client side by adopting a RabbitMQ message queue framework;
the server is connected to the RabbitMQ message queue frame, creates and releases the data needing to be processed immediately, and closes the connection with the RabbitMQ message queue frame after the release is finished;
and the client is connected to the RabbitMQ message queue frame, acquires the data needing to be processed immediately, and closes the connection with the RabbitMQ message queue frame after the acquisition is completed.
10. A computer readable storage medium storing computer code which, when executed, performs the method of any of claims 1 to 5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010737456.1A CN112039945A (en) | 2020-07-28 | 2020-07-28 | Third-party application docking method and system based on fire-fighting Internet of things platform |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010737456.1A CN112039945A (en) | 2020-07-28 | 2020-07-28 | Third-party application docking method and system based on fire-fighting Internet of things platform |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112039945A true CN112039945A (en) | 2020-12-04 |
Family
ID=73583342
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010737456.1A Pending CN112039945A (en) | 2020-07-28 | 2020-07-28 | Third-party application docking method and system based on fire-fighting Internet of things platform |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112039945A (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112651807A (en) * | 2020-12-31 | 2021-04-13 | 浙江子不语电子商务有限公司 | Standard price system management system |
| CN112800139A (en) * | 2021-02-23 | 2021-05-14 | 浪潮云信息技术股份公司 | Third-party application data synchronization system based on message queue |
| CN112966236A (en) * | 2021-03-03 | 2021-06-15 | 广东粤安科技股份有限公司 | Intelligent fire-fighting management system and method |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103957248A (en) * | 2014-04-21 | 2014-07-30 | 中国科学院软件研究所 | Public real-time data management cloud service platform based on Internet of Things |
| US20170039390A1 (en) * | 2015-08-08 | 2017-02-09 | James Alexander KING | Methods and systems for privacy preserving third party extension |
| CN109040301A (en) * | 2018-09-05 | 2018-12-18 | 四川创客知佳科技有限公司 | Wisdom security protection data system based on Internet of Things |
| CN111091677A (en) * | 2019-12-13 | 2020-05-01 | 上海凌泽信息科技有限公司 | Remote alarm fire extinguishing system and method |
-
2020
- 2020-07-28 CN CN202010737456.1A patent/CN112039945A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103957248A (en) * | 2014-04-21 | 2014-07-30 | 中国科学院软件研究所 | Public real-time data management cloud service platform based on Internet of Things |
| US20170039390A1 (en) * | 2015-08-08 | 2017-02-09 | James Alexander KING | Methods and systems for privacy preserving third party extension |
| CN109040301A (en) * | 2018-09-05 | 2018-12-18 | 四川创客知佳科技有限公司 | Wisdom security protection data system based on Internet of Things |
| CN111091677A (en) * | 2019-12-13 | 2020-05-01 | 上海凌泽信息科技有限公司 | Remote alarm fire extinguishing system and method |
Non-Patent Citations (3)
| Title |
|---|
| 周健: "RabbitMQ消息队列在城市智慧综合管廊监控与报警集成管控平台上的应用", 《工业控制计算机》 * |
| 赵守香等: "《大数据分析与应用》", 31 December 2015 * |
| 郭逸尚: "广域环境下消防数据采集与存储管理系统", 《中国优秀博硕士学位论文全文数据库（硕士）信息科技辑》 * |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112651807A (en) * | 2020-12-31 | 2021-04-13 | 浙江子不语电子商务有限公司 | Standard price system management system |
| CN112800139A (en) * | 2021-02-23 | 2021-05-14 | 浪潮云信息技术股份公司 | Third-party application data synchronization system based on message queue |
| CN112966236A (en) * | 2021-03-03 | 2021-06-15 | 广东粤安科技股份有限公司 | Intelligent fire-fighting management system and method |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112039945A (en) | Third-party application docking method and system based on fire-fighting Internet of things platform | |
| CN104184832B (en) | Data submission method and device in network application | |
| CN109981653B (en) | Web vulnerability scanning method | |
| CN108712413B (en) | Identity verification method and equipment | |
| US10491621B2 (en) | Website security tracking across a network | |
| US11997134B2 (en) | Detecting device masquerading in application programming interface (API) transactions | |
| US8914864B1 (en) | Temporary virtual identities in a social networking system | |
| TW202113722A (en) | Data processing method, device and system based on block chain and electronic equipment | |
| CN105577602A (en) | Data pushing method and data pushing device based on open application programming interface | |
| CN107104923A (en) | A kind of account binding and the method and device of business processing | |
| CN112291264B (en) | Security control method, device, server and storage medium | |
| CN107403108A (en) | A kind of method and system of data processing | |
| WO2017080393A1 (en) | Method and apparatus for acquiring ip address | |
| CN104902033B (en) | Log in address recording method and device | |
| CN106254328A (en) | A kind of access control method and device | |
| CN115243112A (en) | Device that surveillance video traced to source | |
| CN109981533A (en) | A kind of ddos attack detection method, device, electronic equipment and storage medium | |
| CN109428924B (en) | Application online state maintenance method, access layer assembly, application system and equipment | |
| CN107506355A (en) | Object group technology and device | |
| CN111832862B (en) | Flow management method and system based on block chain | |
| CN106357651A (en) | Method for geographically limiting IP access on CDN | |
| CN105490993B (en) | Method and device for preventing Cookie tracking in browser | |
| JP5805321B2 (en) | Determining the physical location of the client | |
| CN109688140B (en) | Information processing method and information processing device | |
| CN112565380A (en) | Fire-fighting Internet of things data access method and system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20201204 |