CN112235413A - Universal Internet of things interface management platform - Google Patents
Universal Internet of things interface management platform Download PDFInfo
- Publication number
- CN112235413A CN112235413A CN202011149413.8A CN202011149413A CN112235413A CN 112235413 A CN112235413 A CN 112235413A CN 202011149413 A CN202011149413 A CN 202011149413A CN 112235413 A CN112235413 A CN 112235413A
- Authority
- CN
- China
- Prior art keywords
- rule engine
- module
- logic
- processing
- request
- 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.)
- Granted
Links
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
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/546—Message passing systems or structures, e.g. queues
-
- 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]
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
- G06F2009/45595—Network integration; Enabling network access in virtual machine instances
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2209/00—Indexing scheme relating to G06F9/00
- G06F2209/54—Indexing scheme relating to G06F9/54
- G06F2209/547—Messaging middleware
-
- 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
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Medical Informatics (AREA)
- General Health & Medical Sciences (AREA)
- Health & Medical Sciences (AREA)
- Computing Systems (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
- Computer And Data Communications (AREA)
Abstract
The invention discloses a universal Internet of things interface management platform, which comprises a protocol server, a rule engine, a basic module, a logic module, a database and a management module, wherein the protocol server is used for storing a plurality of protocol data; the protocol server is connected with the client service, the preposed rule engine is arranged at the rear end of the protocol server, the basic module is arranged at the rear end of the preposed rule engine, the logic module and the database are arranged at the rear end of the basic module in parallel, the logic module and the database are provided with the postposition rule engine, and the management module is arranged at the rear end of the postposition rule engine; the problem that the protocol of the EMQX lacks multi-application management capability is solved.
Description
Technical Field
The invention relates to the technical field of Internet of things cloud management, in particular to a universal Internet of things interface management platform.
Background
The existing IOT service platform solution or platform comprises an EMQX, a China Mobile OneNet, an Ali cloud Internet of things platform and the like.
The EMQX has narrow supporting protocol and can not be flexibly and elastically deployed according to specific implementation conditions; aiming at the access of different applications, a unified management platform cannot be provided, and different applications are relatively independent and lack certain interconnection capacity; only supporting protocols such as MQTT/MQTTS, HTTP/HTTPS, Websocket/Websocket and the like; and the performance problem of the EMQX in the actual deployment can cause the memory overflow, and the long-time operation can cause the serious problem of the downtime of the server. The China Mobile OneNet platform and the Ali cloud Internet of things platform support various Internet of things protocols, so that the problem that the protocols of the EMQX are not wide enough can be well solved, but the two platforms are only provided as services and cannot be elastically combined according to the self needs. Both have drawbacks in multi-application management and do not provide corresponding application management portals or functional modules.
Disclosure of Invention
The invention aims to provide a universal Internet of things interface management platform, and solves the problem that an EMQX protocol lacks multi-application management capability.
In order to solve the technical problems, the invention adopts the following technical scheme:
a general thing networking interface management platform which characterized in that: the system comprises a protocol server, a rule engine, a basic module, a logic module, a database and a management module; the protocol server bears the capability of responding to the service request, bearing the service and guaranteeing the service of each protocol and is provided with a plurality of protocol interfaces; the rule engine receives data input, explains the business rules and makes business decisions according to the business rules, and comprises a front rule engine and a rear rule engine; the basic module comprises an oAuth module, a user module and an equipment module and is responsible for processing basic services; the logic module is responsible for logic operation and setting a logic structure; the database stores and manages data; the management module manages specific user requests; the protocol server is connected with the client service, the preposed rule engine is arranged at the rear end of the protocol server, the basic module is arranged at the rear end of the preposed rule engine, the logic module and the database are arranged at the rear end of the basic module in parallel, the logic module and the database are provided with the postposition rule engine, and the management module is arranged at the rear end of the postposition rule engine.
Further, the protocol server is provided with a route processing module, and the route processing module reads the address in each data packet and then decides how to transmit.
Further, after the service is accessed to the interface, the following procedures are implemented:
s1, receiving the request: after the platform receives a request from a client/terminal/node, a corresponding protocol server processing application in the platform correctly obtains the client request, and the client request is uniformly summarized to a routing processing service;
s2: and (3) routing processing: after receiving different requests, the route processing service judges the route and verifies the data matching judgment and distribution;
s3: a front rule engine: the filtered route enters the middleware of the preposed rule engine for processing;
s4: and (3) service logic: after the processing of the rule engine is finished, the application logic in the actual logic module is entered, and according to different services, developers need to develop different service logics;
s5 post rules Engine response: after the business logic module finishes processing, corresponding data is carried out on the request or corresponding data is published (in a protocol of a publish/subscribe mode) after the middleware of the rule engine is arranged in a post.
Further, when two or more services have the same user data, or similar user processing logic, the services share the user module in the base module.
Further, the preposed rule engine middleware is called before actual service logic processing is carried out and is used for identity verification or permission judgment of a module needing preposed processing; the post-arranged rule engine middleware is called after the actual business logic is processed, is used for responding certain actions, and does not influence the actual business logic under the condition that the processing result of the rule engine middleware is not important or whether the processing result is required to be successful or not.
Furthermore, a request must correctly match protocols, routes and service logics, if a certain module cannot be correctly matched, the request is invalid, and the middleware of the post-rule engine does not make a requirement, so that the correct response of the application is not influenced even if the middleware of the post-rule engine cannot be correctly matched or the execution fails after matching; if the preposed rule engine middleware exists, the matching is required to be correct and the execution can be correct, otherwise, the request is regarded as invalid; if not, the response of the application is not affected; the front rule engine and the rear rule engine respectively exist independently or simultaneously, and the front rule engine and the rear rule engine can be mutually coupled by business logic and do not influence each other.
Compared with the prior art, the invention has the beneficial effects that:
the scheme provides a scheme capable of flexibly combining multiple Internet of things protocols so as to deal with different application scenes and realize different functions and requirements; and can be used as a container to carry out a flexible distributed deployment solution.
The scheme supports protocols such as Socket access, HTTP/HTTPS, Websocket/Websockets, MQTT/MQTTS, CoAP and the like. Different Internet of things applications can be supported by supporting protocols such as Socket, MQTT and CoAP. Meanwhile, the self-supporting HTTP and Websocket can conveniently support various requirements and functions and can conveniently provide a uniform or self-defined management entrance.
Besides supporting various internet and internet of things protocols, the multi-application unified access is realized, the request of each application is forwarded in parallel, and the scheme can uniformly manage each application and comprises functional modules of application authentication, data management, data visualization and the like.
Because the self-supporting protocol comprises the HTTP protocol, the WebSocket protocol and the like, a user can select to deploy the unified application management module according to actual conditions.
The scheme solves the problems of protocol shortage of EMQX and multi-application management capability, meanwhile, the scheme can also be used for splitting or combining each module according to actual implementation to realize an optimal or minimized solution, each implementation is used as a node to carry out flexible distributed deployment, the implementation of the distributed deployment is adopted, and the scheme also provides an entrance for flexibly managing each node, so that the problems of singleness and inflexibility of China Mobile OneNet and Ariyun Internet of things platforms are solved.
Drawings
FIG. 1 is a schematic view of the structure of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, the present invention is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.
The specific embodiment is as follows:
as shown in the figure, the universal internet of things interface management platform comprises a protocol server, a rule engine, a basic module, a logic module, a database and a management module; the protocol server bears the response service request, bears the service and ensures the normal operation of the service of each protocol, and is provided with a plurality of protocol interfaces, such as MQTT Broker, a TCP/IP server, HTTP/RESTful, Websocket, CoAP and other interfaces of various protocols so as to correspond to the services connected under different protocol rules. The rule engine receives the data transmitted by the protocol server, inputs the data, explains the business rules and makes corresponding business decisions according to the business rules. If a service request accesses a record stored in the database and copies the record, the rule engine performs corresponding operation after receiving the record. In the setting, the rule engine comprises a front rule engine and a rear rule engine which are elastically combined, the two rule engines are responsible for different works, and a front rule engine middleware is called before actual business logic processing is carried out and is used for identity verification or a module needing front processing for authority judgment; the post-arranged rule engine middleware is called after the actual business logic is processed, is used for responding certain actions, is mainly used for responding multiple applications of the business, and does not influence the actual business logic under the condition that the processing result of the post-arranged rule engine middleware is unimportant or whether the processing result is required to be successful or not. The basic module comprises an oAuth module, a user module and an equipment module, and is responsible for processing basic services according to specific requirements of the services, such as reading data of a certain sensor. The logic module is responsible for logic operation and setting a logic structure, some requests which need to carry out logic operation enter the logic module to be processed, when the database needs to be accessed, the requests can be accessed through the logic module, and some simple accesses can be carried out from the basic module. The database stores and manages data. And the management module manages specific user requests and presents response results. In the device, a specific data connection structure of the platform is that a protocol server is connected with a client service, a preposed rule engine is arranged at the rear end of the protocol server, a basic module is arranged at the rear end of the preposed rule engine, a logic module and a database are arranged at the rear end of the basic module in parallel, the logic module is connected with the database, a postposition rule engine is arranged behind the logic module and the database, and a management module is arranged at the rear end of the postposition rule engine.
In the device, in order to better perform operation and response on requests of different protocols, a protocol server is provided with a route processing module, the route processing module reads an address in each data packet and then determines how to transmit the data packet, after a platform receives the request from a client/terminal/node, a corresponding protocol server in the platform processes and applies the request to correctly obtain the client request, the client request is collected to a route processing service in a unified mode, and after the route processing service receives different requests, the route is judged and verified, mainly data matching, demand judgment and data distribution are performed.
In the device, the specific flow of data entering the platform is as follows:
s1: a client makes a service request;
s2: the protocol server receives the request, when the platform receives the request from the client/terminal/node, the corresponding protocol server side processing application in the platform correctly obtains the client request, and the client request is uniformly summarized to the routing processing service;
s3: after receiving different requests, the route processing service judges and verifies the route;
s4: a front rule engine: the filtered route enters the middleware of the preposed rule engine for processing;
s5: and (3) service processing: after the rule engine processing is finished, a part of the basic business is processed through the basic module, and has special requirements, if the business processed logically enters the application logic in the actual logic module for processing, according to different businesses, developers need to develop different business logics, set different logics and perform different logic processing;
s6: the post rules engine responds with: after the business logic module finishes processing, the request is correspondingly processed and fed back to the management module for specific management or displaying or publishing corresponding data (in a protocol of a publish/subscribe mode) after the middleware of the rule engine is arranged in the back.
In this process, a relatively optimized response is that when two or more services have the same user data, or similar user processing logic, the services share the user module in the base module.
The scheme provides a scheme capable of flexibly combining multiple Internet of things protocols so as to deal with different application scenes and realize different functions and requirements; and can be used as a container for flexible distributed deployment.
The scheme supports protocols such as Socket access, HTTP/HTTPS, Websocket/Websockets, MQTT/MQTTS, CoAP and the like. Different Internet of things applications can be supported by supporting protocols such as Socket, MQTT and CoAP. Meanwhile, the self-supporting HTTP and Websocket can conveniently support various requirements and functions and can conveniently provide a uniform or self-defined management entrance.
Besides supporting various internet and internet of things protocols, the multi-application unified access is realized, the request of each application is forwarded in parallel, and the scheme can uniformly manage each application and comprises functional modules of application authentication, data management, data visualization and the like.
Because the self-supporting protocol comprises the HTTP protocol, the WebSocket protocol and the like, a user can select to deploy the unified application management module according to actual conditions.
The scheme solves the problems of protocol shortage of EMQX and multi-application management capability, meanwhile, the scheme can also be used for splitting or combining each module according to actual implementation to realize an optimal or minimized solution, each implementation is used as a node to carry out flexible distributed deployment, the implementation of the distributed deployment is adopted, and the scheme also provides an entrance for flexibly managing each node, so that the problems of singleness and inflexibility of China Mobile OneNet and Ariyun Internet of things platforms are solved.
Reference throughout this specification to "one embodiment," "another embodiment," "an embodiment," "a preferred embodiment," or the like, means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment described generally in this application. The appearances of the same phrase in various places in the specification are not necessarily all referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with any embodiment, it is submitted that it is within the scope of the invention to effect such feature, structure, or characteristic in connection with other embodiments.
Although the invention has been described herein with reference to a number of illustrative embodiments thereof, it should be understood that numerous other modifications and embodiments can be devised by those skilled in the art that will fall within the spirit and scope of the principles of this disclosure. More specifically, various variations and modifications are possible in the component parts and/or arrangements of the subject combination arrangement within the scope of the disclosure, the drawings and the appended claims. In addition to variations and modifications in the component parts and/or arrangements, other uses will also be apparent to those skilled in the art.
Claims (6)
1. A general thing networking interface management platform which characterized in that: the system comprises a protocol server, a rule engine, a basic module, a logic module, a database and a management module; the protocol server undertakes normal operation of response service requests, undertaking services and guaranteeing services of each protocol and is provided with a plurality of protocol interfaces; the rule engine receives data input, explains the business rules and makes business decisions according to the business rules, and comprises a front rule engine and a rear rule engine; the basic module comprises an oAuth module, a user module and an equipment module and is responsible for processing basic services; the logic module is responsible for logic operation and setting a logic structure; the database stores and manages data; the management module manages specific user requests; the protocol server is connected with the client service, the preposed rule engine is arranged at the rear end of the protocol server, the basic module is arranged at the rear end of the preposed rule engine, the logic module and the database are arranged at the rear end of the basic module in parallel, the logic module and the database are provided with the postposition rule engine, and the management module is arranged at the rear end of the postposition rule engine.
2. The universal internet of things interface management platform according to claim 1, wherein: the protocol server is provided with a route processing module which reads the address in each data packet and then decides how to transmit.
3. The universal internet of things interface management platform according to claim 1, wherein: after the service is accessed to the interface, the method is realized according to the following procedures:
s1, receiving the request: after the platform receives a request from a client/terminal/node, a corresponding protocol server processing application in the platform correctly obtains the client request, and the client request is uniformly summarized to a routing processing service;
s2: and (3) routing processing: after receiving different requests, the route processing service judges and verifies the route;
s3: a front rule engine: the filtered route enters the middleware of the preposed rule engine for processing;
s4: and (3) service logic: after the processing of the rule engine is finished, the application logic in the actual logic module is entered, and according to different services, developers need to develop different service logics;
s5: the post rules engine responds with: after the business logic module finishes processing, corresponding data is carried out on the request or corresponding data is issued after the middleware of the rule engine is arranged in the rear position.
4. The universal internet of things interface management platform according to claim 2, wherein: when two or more services have the same user data, or similar user processing logic, the services share the user module in the base module.
5. The universal internet of things interface management platform according to claim 1, wherein: the preposed rule engine middleware is called before actual business logic processing is carried out and is used for identity verification or permission judgment of a module needing preposed processing; the post-arranged rule engine middleware is called after the actual business logic is processed, is used for responding certain actions, and does not influence the actual business logic under the condition that the processing result of the rule engine middleware is not important or whether the processing result is required to be successful or not.
6. The universal internet of things interface management platform according to claim 1, wherein: one request must match the protocol, route, service logic correctly, if some module can't match correctly, it is invalid for the request, then the middleware of the postpositional rule engine does not make the requirement, even if the middleware of the postpositional rule engine can't match correctly, or the execution fails after matching, it does not affect the correct response of the application; if the preposed rule engine middleware exists, the matching is required to be correct and the execution can be correct, otherwise, the request is regarded as invalid; if not, the response of the application is not affected; the front rule engine and the rear rule engine respectively exist independently or simultaneously, and the front rule engine and the rear rule engine can be mutually coupled by business logic and do not influence each other.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011149413.8A CN112235413B (en) | 2020-10-23 | 2020-10-23 | Universal Internet of things interface management platform |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011149413.8A CN112235413B (en) | 2020-10-23 | 2020-10-23 | Universal Internet of things interface management platform |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112235413A true CN112235413A (en) | 2021-01-15 |
| CN112235413B CN112235413B (en) | 2022-11-15 |
Family
ID=74110372
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011149413.8A Active CN112235413B (en) | 2020-10-23 | 2020-10-23 | Universal Internet of things interface management platform |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112235413B (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113612848A (en) * | 2021-08-09 | 2021-11-05 | 北京百度网讯科技有限公司 | Internet of things data receiving method, Internet of things platform and Internet of things system |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103825811A (en) * | 2013-10-11 | 2014-05-28 | 江苏飞尚安全监测咨询有限公司 | Implementation scheme for accessing sensor protocol self-identification IOT (internet of things) gateway |
| US20170006039A1 (en) * | 2015-06-30 | 2017-01-05 | Mist Systems, Inc. | Access enforcement at a wireless access point |
| US20190102411A1 (en) * | 2017-09-29 | 2019-04-04 | Oracle International Corporation | Rule-based autonomous database cloud service framework |
| CN110098953A (en) * | 2019-03-29 | 2019-08-06 | 南京邮电大学 | The things-internet gateway hierarchical control framework of rule-based engine |
| CN110601876A (en) * | 2019-08-20 | 2019-12-20 | 西安向南网络信息科技有限公司 | Intelligent Internet of things platform |
| CN110868316A (en) * | 2019-09-29 | 2020-03-06 | 上海上实龙创智慧能源科技股份有限公司 | Internet of things platform architecture based on rule engine |
-
2020
- 2020-10-23 CN CN202011149413.8A patent/CN112235413B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103825811A (en) * | 2013-10-11 | 2014-05-28 | 江苏飞尚安全监测咨询有限公司 | Implementation scheme for accessing sensor protocol self-identification IOT (internet of things) gateway |
| US20170006039A1 (en) * | 2015-06-30 | 2017-01-05 | Mist Systems, Inc. | Access enforcement at a wireless access point |
| US20190102411A1 (en) * | 2017-09-29 | 2019-04-04 | Oracle International Corporation | Rule-based autonomous database cloud service framework |
| CN110098953A (en) * | 2019-03-29 | 2019-08-06 | 南京邮电大学 | The things-internet gateway hierarchical control framework of rule-based engine |
| CN110601876A (en) * | 2019-08-20 | 2019-12-20 | 西安向南网络信息科技有限公司 | Intelligent Internet of things platform |
| CN110868316A (en) * | 2019-09-29 | 2020-03-06 | 上海上实龙创智慧能源科技股份有限公司 | Internet of things platform architecture based on rule engine |
Non-Patent Citations (3)
| Title |
|---|
| ASGHAR等: "" .Design and simulation of energy efficiency in node based on MQTT protocol in Internet of Things"", 《2015 INTERNATIONAL CONFERENCE ON GREEN COMPUTING AND INTERNET OF THINGS (ICGCIOT). IEEE COMPUTER SOCIETY》 * |
| 吴尧: ""基于云平台的工业互联网管控系统的研究与设计"", 《中国优秀硕士学位论文全文数据库》 * |
| 郑少斌: ""支持多协议的微服务化物联网平台研究与实现"", 《中国优秀硕士学位论文全文数据库》 * |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113612848A (en) * | 2021-08-09 | 2021-11-05 | 北京百度网讯科技有限公司 | Internet of things data receiving method, Internet of things platform and Internet of things system |
| CN113612848B (en) * | 2021-08-09 | 2023-09-22 | 北京百度网讯科技有限公司 | Internet of things data receiving method, internet of things platform and Internet of things system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112235413B (en) | 2022-11-15 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109889551B (en) | Method for accessing intelligent hardware to Internet of things cloud platform | |
| CN106856434B (en) | Method and device for converting access request | |
| KR102046700B1 (en) | Message bus service directory | |
| US20200344189A1 (en) | Communication method and communication apparatus | |
| US6591304B1 (en) | Dynamic, scaleable attribute filtering in a multi-protocol compatible network access environment | |
| CN114124451B (en) | Data processing method and system for Internet of things equipment and computer storage medium | |
| US20070101022A1 (en) | Sharing data in scalable software blade architecture | |
| CN107528891B (en) | Websocket-based automatic clustering method and system | |
| CN108712457A (en) | Back-end server dynamic load method of adjustment and device based on Nginx reverse proxys | |
| CN113572689A (en) | Microservice gateway management method, system, device, readable storage medium and product | |
| CN110636127B (en) | Communication processing method and system between information data | |
| CN112738184B (en) | Plug-in dynamic registration distributed micro-service gateway system | |
| US11025738B2 (en) | Systems and methods for determining a destination location for transmission of packetized data in a network system based on an application server attribute | |
| CN114398176A (en) | Service access method, device, electronic equipment and storage medium | |
| CN114025021A (en) | Communication method, system, medium and electronic device across Kubernetes cluster | |
| CN112187903B (en) | Message pushing method and device and message service system | |
| CN103116655A (en) | Clustered data query method, client side and system | |
| CN105071965B (en) | A kind of management system of the network equipment | |
| CN112235413B (en) | Universal Internet of things interface management platform | |
| CN112286705A (en) | Kubernetes-based container web service interface aggregation system | |
| CN110138753A (en) | Distributed message service system, method, equipment and computer readable storage medium | |
| CN111600929B (en) | Transmission line detection method, routing strategy generation method and proxy server | |
| CN111427703A (en) | Industrial data real-time display method and system | |
| CN111130905A (en) | Distributed cluster-based log level dynamic adjustment method | |
| CN111385324A (en) | Data communication method, device, equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |