Access system and access method of Internet of Things platform and electronic equipment
By constructing a "protocol black box" architecture that integrates multiple protocol adapters, the problem of high development and maintenance costs for IoT platforms in multi-protocol environments is solved, achieving efficient protocol access and data processing, and improving the system's flexibility and response efficiency.
Patent Information
- Application Number
- CN202511042522.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-07-28
- Publication Date
- 2025-11-14
AI Technical Summary
When faced with multiple communication protocols and complex scenario requirements, IoT platforms struggle to achieve rapid and flexible protocol integration, resulting in high development and maintenance costs, and limited system response efficiency and scalability.
We construct a "protocol black box" architecture that integrates multiple protocol adapters. By providing a unified northbound interface through the access client, we shield the differences in underlying protocols, realize protocol connection and standardized data processing, reduce development and maintenance costs, and complete protocol conversion and data unification at the edge.
It significantly reduces the development and maintenance costs of multi-protocol interoperability, improves the system's flexibility, scalability and response efficiency, and reduces the computing and communication burden on the central platform.
Smart Images

Figure CN120956749A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of network technology, and in particular to an access system, access method and electronic device for an Internet of Things (IoT) platform. Background Technology
[0002] With the rapid development of Internet of Things (IoT) technology, the demand for interconnectivity between various terminal devices and platforms is increasing daily. However, with the explosive growth in the types and numbers of IoT devices, and the increasing diversification and flexibility of scenario-based requirements, IoT platforms need to interface with a large number of devices and systems from different manufacturers. This results in a complex array of communication interfaces and protocols that IoT platforms need to interface with, posing challenges to protocol parsing and communication, especially in cases with complex scenario requirements, hindering rapid development and integration. Summary of the Invention
[0003] This application provides an access system, access method, and electronic device for an Internet of Things (IoT) platform to alleviate or solve one or more technical problems existing in the prior art.
[0004] In a first aspect, embodiments of this application provide an access system for an Internet of Things (IoT) platform, comprising: a protocol resource management module, the protocol resource management module including multiple protocol adapters, each protocol adapter corresponding to a variety of communication protocols; and an access client, the access client being configured to receive communication configuration information from multiple callers, wherein the communication configuration information of each caller includes the caller's protocol configuration information and communication performance configuration information, the caller's protocol configuration information matching the communication protocol applicable to the caller, and the caller's communication performance configuration information matching the communication performance of the IoT platform and / or the access system; the access client is further configured to, for each caller: construct parallel protocol channels and message channels between the caller and its matched protocol adapters according to the caller's protocol configuration information, and control the communication performance of the protocol channels connected to the caller according to the caller's communication performance configuration information.
[0005] In one implementation, the communication performance configuration information includes traffic rate limiting information and / or the number of connection threads.
[0006] In one embodiment, the protocol channel is used to perform protocol connection processing according to the protocol configuration information and communication performance configuration information of the caller to which it is connected, wherein the protocol connection processing includes at least one of the following: protocol connection initialization, establishing a protocol connection, disconnecting a protocol connection, and reconnecting a protocol.
[0007] In one implementation, the message channel is used to process the messages it transmits in order to provide the caller with a message having a preset data model, wherein the message processing method includes at least one of data packaging, data format conversion and normalization processing.
[0008] In one embodiment, the access client includes: a protocol configuration submodule, used to receive communication protocol configuration information from the caller, verify the communication protocol configuration information, and associate it with the corresponding protocol channel; a lifecycle management submodule, used to receive protocol lifecycle control instructions from the caller and output them to the corresponding protocol channel; and a message processing submodule, used to interact with the caller.
[0009] In one embodiment, the communication protocol includes at least one of the following: a terminal device standard communication protocol, a third-party platform communication protocol, an extended protocol, and a custom protocol.
[0010] Secondly, embodiments of this application provide an access method for an Internet of Things (IoT) platform, applied to an access client of an access system. The access system includes a protocol resource management module, which includes multiple protocol adapters, each corresponding to a different communication protocol. The method includes: receiving communication configuration information from a target caller, wherein the communication configuration information includes protocol configuration information and communication performance configuration information, the protocol configuration information matching the communication protocol applicable to the target caller, and the communication performance configuration information matching the communication performance of the IoT platform; determining a corresponding target protocol adapter from the multiple protocol adapters based on the protocol configuration information, and constructing a target protocol channel between the target caller and the target protocol adapter to establish a communication connection between the target caller and the target protocol adapter, and controlling the communication performance of the protocol channel connected to the caller based on the caller's communication performance configuration information; constructing a target message channel between the target caller and the target protocol adapter, and transmitting messages between the target caller and the target protocol adapter through the target message channel, wherein the target protocol channel and the target message channel are parallel channels.
[0011] In one implementation, the communication performance configuration information includes traffic rate limiting information and / or the number of connection threads.
[0012] In one implementation, the protocol channel is used to perform protocol connection processing according to the protocol configuration information and communication performance configuration information of the caller to which it is connected, wherein the protocol connection processing includes at least one of: protocol connection initialization, establishing a protocol connection, disconnecting a protocol connection, and reconnecting a protocol; and / or, the message channel is used to process the messages it transmits to provide the target caller with a message having a preset data model.
[0013] Thirdly, embodiments of this application provide an electronic device, including a memory, a processor, and a computer program stored in the memory, wherein the processor implements any of the methods of embodiments of this application when executing the computer program.
[0014] According to the technical solution of this application embodiment, by integrating multiple protocol adapters, each corresponding to a communication protocol, unified access to terminal device protocols and third-party platform protocols is supported. Through the access client, the system provides a unified Northbound Interface, through which the caller can configure the relevant parameters of the required protocol without needing to concern itself with the implementation details of the underlying protocol. By encapsulating coarse-grained functions such as protocol connection and message transmission, and completing protocol conversion and data standardization processing at the edge, data from different protocols are uniformly converted into a standard data model before output. Developers only need to focus on this standard format for data parsing and business development, significantly reducing the development and maintenance costs of multi-protocol integration. Simultaneously, by pushing protocol processing logic down to the edge, the computational and communication burden on the central platform is effectively reduced, improving the system's flexibility, scalability, and response efficiency.
[0015] The above description is only an overview of the technical solution of this application. In order to better understand the technical means of this application, it can be implemented according to the contents of the specification. In order to make the above and other objects, features and advantages of this application more obvious and understandable, specific embodiments of this application are given below. Attached Figure Description
[0016] In the accompanying drawings, unless otherwise specified, the same reference numerals throughout the various drawings denote the same or similar parts or elements. These drawings are not necessarily drawn to scale. It should be understood that these drawings depict only some embodiments according to this application and should not be construed as limiting the scope of this application.
[0017] Figure 1 This diagram illustrates the architecture of an access system for an Internet of Things (IoT) platform provided in an embodiment of this application.
[0018] Figure 2 This diagram illustrates the architecture of an access system for another IoT platform provided in an embodiment of this application.
[0019] Figure 3 A flowchart illustrating the access method of the Internet of Things platform provided in this application embodiment is shown.
[0020] Figure 4 A block diagram of an electronic device provided in an embodiment of this application is shown. Detailed Implementation
[0021] In the following description, only certain exemplary embodiments are briefly described. As those skilled in the art will recognize, the described embodiments can be modified in various ways without departing from the concept or scope of this application. Therefore, the drawings and description are considered to be exemplary in nature and not restrictive.
[0022] To facilitate understanding of the technical solutions of the embodiments of this application, the relevant technologies of the embodiments of this application are described below. The following relevant technologies are optional solutions and can be combined with the technical solutions of the embodiments of this application in any way, and all of them fall within the protection scope of the embodiments of this application.
[0023] With the explosive growth in the types and number of IoT devices, the complexity and diversity of different communication protocols are becoming increasingly prominent. When implementing multi-protocol access, IoT platforms need to master and adapt to the technical details of various protocols, leading to a sharp increase in the complexity of the system's communication interfaces and protocol support. For example, when a platform needs to interface with two different platforms based on the Message Queuing Telemetry Transport (MQTT) protocol, due to differences in configuration parameters such as server addresses and authentication methods, developers often need to write two independent sets of interface logic, significantly increasing development and maintenance costs. Especially when facing complex business scenarios, existing methods struggle to achieve fast and flexible protocol integration, affecting the system's response efficiency and scalability.
[0024] To address these issues, the industry has proposed various solutions, the basic idea of which is to adopt modular design, that is, to encapsulate the implementation logic of different protocols into independent modules. For example, protocols such as Message Queuing Telemetry Transport Protocol (MQTT) and Kafka distributed stream processing platform are encapsulated as independent components, and developers can call the corresponding protocol module for integration as needed. This approach improves the maintainability and scalability of protocol modules, but when facing multiple callers with the same protocol but different protocol configurations, repeated development and configuration are still required, failing to fundamentally reduce development costs.
[0025] To address the aforementioned shortcomings, this application aims to provide an access solution for an IoT platform. This access solution can be understood as constructing a "protocol black box" architecture, which can shield the differences in underlying communication protocols, improve the consistency and flexibility of protocol access, and thus effectively reduce the development and maintenance costs of multi-protocol access.
[0026] The technical solution of this application and how it solves the aforementioned technical problems are described in detail below with specific embodiments. The listed specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments.
[0027] Figure 1 This diagram illustrates the architecture of the access system for the IoT platform provided in an embodiment of this application. Figure 1 As shown, the access system of this IoT platform includes: an access client (transport client) and a protocol resource management module.
[0028] The protocol resource management module includes multiple protocol adapters, each corresponding to a different communication protocol. These communication protocols include, but are not limited to: standard communication protocols for terminal devices, third-party platform communication protocols, extended protocols, and custom protocols. Standard communication protocols for terminal devices include, for example, the Modbus Transmission Control Protocol (Modbus TCP), Controller Area Network (CAN), and Zigbee, primarily used for communication between terminal devices and the IoT platform.
[0029] Third-party platform communication protocols, such as Hypertext Transfer Protocol (HTTP), Transmission Control Protocol / Internet Protocol (TCP / IP), Message Queuing Telemetry Transport Protocol (MQTT), Kafka distributed stream processing platform, and User Datagram Protocol (UDP), are mainly used for communication between IoT platforms and external platforms or systems.
[0030] Extended protocols are protocols that extend or adapt the functionality of existing standard protocols to meet the communication needs of specific service scenarios, such as adding security mechanisms, data compression, adaptive transmission control, and other functions.
[0031] Custom protocols refer to dedicated communication protocols developed independently based on specific service requirements or device characteristics. Their data format, interaction flow, and control logic are defined by the user or developer.
[0032] Each protocol adapter corresponds to a specific communication protocol. The protocol adapters adopt a modular design, can exist as plug-ins, and follow a unified interface specification, thereby enabling dynamic loading and management of communication protocols.
[0033] The access client can be hardware, such as at least one of a personal computer (PC), smartphone, tablet computer, Internet of Things device (IoT device), or server; or it can be an application (APP) or software module deployed on the above-mentioned electronic devices.
[0034] The access client is used to receive communication configuration information from multiple callers. The communication configuration information of each caller includes the caller's protocol configuration information and communication performance configuration information. The caller's protocol configuration information matches the communication protocol applicable to the caller, and the caller's communication performance configuration information matches the communication performance of the IoT platform.
[0035] In this context, the "caller" can be understood as an entity that invokes the access system provided in this application embodiment, such as an upper-layer application of the access system. An upper-layer application refers to a service system, application program, or software module that uses the communication capabilities, data model, or control interface of this access system to implement functions such as management, data processing, and service scheduling for terminal devices or third-party platforms. For example, an upper-layer application could be an industrial control center, a central control platform in a smart building, an enterprise-level business system, or a data platform.
[0036] Protocol configuration information consists of configuration parameters that match the communication protocol, such as the type of communication protocol, connection parameters (e.g., IP address, port number, etc.), authentication information (e.g., username, password, certificate, etc.), and data format (e.g., JSON, XML, binary, etc.).
[0037] Communication performance configuration information is matched with the communication performance of the IoT platform and / or access system. This information includes, for example, traffic rate limiting, the number of connection threads, and the number of concurrent connections. Through this configuration, communication resources for each caller can be rationally allocated and controlled, preventing system overload or performance degradation caused by excessive resource consumption by individual connections. This ensures the reliability and response efficiency of communication under high load conditions, enabling refined performance management and quality of service control.
[0038] Furthermore, for each caller, the access client is also used to determine the corresponding protocol adapter based on the caller's protocol configuration information. For example, it determines the corresponding protocol adapter based on the type of communication protocol, and then builds parallel protocol channels and message channels between the caller and the protocol adapter, respectively.
[0039] Parallelism can be understood as establishing multiple independent communication paths between the caller and the protocol adapter simultaneously, each used for protocol interaction and data transmission, without interference. By constructing parallel protocol channels and message channels, protocol parsing and data transmission can be executed independently without blocking each other, improving communication efficiency and system response speed. Simultaneously, it enhances the modularity and scalability of the communication architecture, facilitating subsequent functional expansion or protocol upgrades, and improving system stability and multitasking capabilities.
[0040] The access client can also control the communication performance of the protocol channel connected to the caller based on the caller's communication performance configuration information. For example, the access client can dynamically adjust the protocol channel's traffic rate limit, the number of connection threads, or the number of concurrent connections based on the caller's communication performance configuration information. By dynamically controlling the communication performance of the protocol channel, differentiated resource allocation and fine-grained management for different callers are achieved, preventing system resources from being excessively occupied by a single caller. This avoids system overload or response delays, improves the overall system's load balancing capabilities and operational stability, and ensures service quality in multi-caller scenarios.
[0041] For example, the protocol resource management module can be deployed on the same entity as the access client, or the protocol resource management module can be deployed on different entities than the access client. The entity can be an application, service, instance, software-form functional module, virtual machine, container or cloud server, or hardware device or hardware chip with data processing function.
[0042] This application provides an access solution for an IoT platform, the core of which lies in constructing a "protocol black box" architecture. This architecture integrates multiple protocol adapters, each corresponding to a communication protocol, supporting unified access for terminal device protocols and third-party platform protocols. Through the access client, the system provides a unified northbound interface, through which the caller can configure the relevant parameters of the required protocol without needing to concern themselves with the implementation details of the underlying protocol. The protocol black box encapsulates coarse-grained functions such as protocol connection and message transmission, and performs protocol conversion and data standardization processing at the edge, uniformly converting data from different protocols into a standard data model before output. Developers only need to focus on this standard format for data parsing and business development, significantly reducing the development and maintenance costs of multi-protocol integration. Simultaneously, by pushing protocol processing logic down to the edge, it effectively reduces the computational and communication burden on the central platform, improving the system's flexibility, scalability, and response efficiency.
[0043] Figure 2 This diagram illustrates the architecture of the access system for the IoT platform provided in an embodiment of this application. Figure 2 As shown, the access client includes: a protocol configuration submodule, used to receive communication protocol configuration information from the caller, verify the communication protocol configuration information, and associate it with the corresponding protocol channel; a protocol lifecycle management submodule, used to receive protocol lifecycle control instructions from the caller and output them to the corresponding protocol channel; and a message processing submodule, used to interact with messages with the caller.
[0044] The protocol configuration submodule is responsible for protocol configuration, mainly defining and validating protocol configurations. For example, it validates protocol configuration information such as protocol type, connection parameters, authentication information, and data format to ensure their legitimacy. After validation, it associates the protocol with the corresponding protocol adapter through the protocol channel.
[0045] For example, when using the Kafka Protocol, the protocol configuration information provided by the caller needs to be validated to ensure that it contains the necessary configuration items required by the Kafka distributed stream processing platform, such as: Kafka Broker Address (broker) information; Topic Name; Authentication method, such as a secure communication protocol based on Simple Authentication and Security Layer / Secure Sockets Layer (SASL / SSL); Message data format, such as JSON format, Avro format (an open-source format), etc.
[0046] After successful verification, the access client converts these protocol configuration information into the internal configuration format supported by the Kafka protocol plugin, such as parameters like bootstrap.servers (to specify the initial boot server address), topic (to specify the message topic), and security.protocol (to specify the secure communication protocol), so that the protocol channel can subsequently complete the connection and communication management of the Kafka protocol.
[0047] The lifecycle management submodule is responsible for receiving protocol lifecycle control instructions from the caller, such as start, stop, and reconnect operations. These operations are implemented by calling interfaces or sending control commands. The start operation is used to build protocol channels and message channels, establishing a connection between the access system and the device or platform; the stop operation is used to actively close the protocol connection and release resources; the reconnect operation attempts to re-establish the connection according to the communication performance configuration strategy (such as exponential backoff or maximum retries) after an abnormal connection is lost.
[0048] The message processing submodule is responsible for transmitting data communication between the caller (such as an upper-layer application) and the access system, including messages of the types of requests, responses, and events.
[0049] In one implementation, the protocol channel is used to perform protocol connection processing according to the protocol configuration information and communication performance configuration information of the caller to which it is connected, wherein the protocol connection processing includes at least one of the following: protocol connection initialization, establishing a protocol connection, disconnecting a protocol connection, and protocol reconnection.
[0050] A protocol channel is a logical channel responsible for binding and interacting with a specific communication protocol. After creation, the protocol channel, based on the protocol configuration information provided by the caller, searches for and loads the corresponding protocol adapter from the protocol resource management module, thereby obtaining the relevant communication protocol resources. These communication protocol resources encapsulate the specific communication logic of the protocol, including connection establishment, data interaction, and exception handling capabilities. The protocol channel then binds the acquired communication protocol resources to itself, forming a protocol processing unit with actual communication capabilities.
[0051] Through this binding relationship, the protocol channel can perform protocol connection processing operations based on the protocol resource. These operations include: protocol connection initialization (loading and initializing communication parameters according to protocol configuration information); establishing a protocol connection (creating an actual communication link with the corresponding device or third-party platform based on the selected protocol type, such as MQTT, HTTP, Modbus TCP, etc., once initialization is complete); disconnecting the protocol connection (safely closing the connection and releasing occupied resources to avoid unnecessary system load upon receiving a disconnect command); and reconnecting the protocol (automatically attempting to re-establish the connection in case of network interruption or connection abnormality, ensuring the continuity and reliability of data transmission). This function is particularly suitable for long-term operation under unstable network conditions in IoT environments.
[0052] In this way, the protocol channel realizes the connection and communication link of the corresponding communication protocol, shields the complexity of the underlying protocol implementation, and improves the flexibility and maintainability of communication protocol access.
[0053] In one implementation, the message channel is used to process the messages it transmits to provide a message with a preset data model to the caller, wherein the message processing method includes at least one of data packaging, data format conversion and normalization processing.
[0054] The message channel is responsible for receiving, processing, and transmitting protocol data after the protocol communication is established. Once the protocol channel has established a communication connection, the message channel retrieves the data processing logic matching the current communication protocol from the corresponding protocol adapter based on the protocol configuration information. It then performs a series of processing operations on the received messages based on this logic. These operations include: data packaging, which encapsulates raw data (such as the device's raw byte stream, register values, message body, etc.) into structured message objects, adding necessary context information or metadata for easier subsequent processing and identification; data format conversion, which unifies heterogeneous data formats generated by different protocols into preset standard data formats (such as JSON, XML, unified binary structure, etc.), ensuring that the caller can parse the data consistently; and normalization, which standardizes the converted data, eliminating data differences between devices or platforms and outputting a unified data model (preset data model). This allows the caller (upper-layer application) to focus on the unified model without needing to concern itself with the specific data structure of the underlying protocol.
[0055] Through the aforementioned message processing mechanism, the message channel achieves unified modeling and processing of heterogeneous protocol data, improving the system's compatibility, scalability, and development efficiency, while reducing the complexity of data parsing and processing in a multi-protocol environment.
[0056] Figure 3 This diagram illustrates a flowchart of an access method for an IoT platform provided in an embodiment of this application. This method can be applied to access systems, such as those provided by… Figure 1 or Figure 2 The access client shown executes the command. For example... Figure 3 As shown, the method may include steps S301 to S303.
[0057] Step S301: Receive communication configuration information from the target caller, wherein the communication configuration information includes protocol configuration information and communication performance configuration information. The protocol configuration information matches the communication protocol applicable to the target caller, and the communication performance configuration information matches the communication performance of the IoT platform.
[0058] The target caller can be any caller, such as any upper-layer application of the access system, that is, a service system, application, or software module that uses the communication capabilities, data model, or control interface of this access system. Detailed explanations of the communication configuration information can be found above and will not be repeated here.
[0059] For example, upon receiving the communication configuration information, the access client first performs verification and conversion processing. For instance, when the target caller uses the Kafka distributed stream processing platform (Kafka) protocol, it needs to verify whether it contains necessary configuration items such as the Kafka server address (broker), topic name, security authentication method (e.g., SASL / SSL), and message format (e.g., JSON, Avro). After successful verification, these configuration items are converted into the internal configuration format required by the Kafka protocol plugin, such as bootstrap.servers, topic, and security.protocol, for subsequent use by the protocol channel.
[0060] Step S302: Determine the corresponding target protocol adapter from multiple protocol adapters according to the protocol configuration information, and build a target protocol channel between the target caller and the target protocol adapter to establish a communication connection between the target caller and the target protocol adapter. Control the communication performance of the protocol channel connected to the caller according to the caller's communication performance configuration information.
[0061] The access client determines the target protocol adapter that matches the current protocol type from multiple protocol adapters integrated in the protocol resource management module, based on the target caller's protocol configuration information. Each protocol adapter encapsulates the communication logic and lifecycle management capabilities of the corresponding protocol.
[0062] Subsequently, the access client establishes a target protocol channel between the target caller and the target protocol adapter. The protocol channel is a logical channel responsible for binding and interacting with a specific protocol, used to perform operations such as protocol connection initialization, establishing a protocol connection, disconnecting a protocol connection, and reconnecting to the protocol. Through this protocol channel, the target caller can establish a communication connection with the target device or a third-party platform.
[0063] Furthermore, the access client dynamically controls the communication performance of the protocol channel based on communication performance configuration information. For example, it controls the message transmission rate based on configured traffic rate limiting information, and controls resource allocation based on the number of connection threads or concurrent connections. This enables differentiated resource management for different callers, preventing excessive consumption of system resources by a single caller and improving the overall system's load balancing capabilities and operational stability.
[0064] Step S303: Establish a target message channel between the target caller and the target protocol adapter, and transmit messages between the target caller and the target protocol adapter through the target message channel, wherein the target protocol channel and the target message channel are parallel channels.
[0065] The access client further constructs a target message channel between the target caller and the target protocol adapter. This target message channel and the target protocol channel are parallel channels, each undertaking different responsibilities for protocol connection management and message transmission processing.
[0066] Specifically, after the protocol communication is established, the message channel is responsible for packaging, converting, and normalizing the transmitted messages to output messages with a preset data model. For example, it parses and converts heterogeneous data such as raw bytes, register values, and message bodies from the device into a unified data model, such as a standardized JSON structure or binary format, so that the caller only needs to focus on the unified data model for business processing and does not need to care about the differences in the underlying protocol.
[0067] By designing parallel protocol and message channels, the system decouples protocol connection control from data transmission processing, improving communication efficiency and system response speed, and enhancing the modularity and scalability of the communication architecture.
[0068] It should be noted that the application scenarios or examples provided in this application are for ease of understanding, and this application does not specifically limit the application of the technical solutions. Furthermore, the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties. The collection, use, and processing of related data must comply with the relevant laws, regulations, and standards of the relevant countries and regions, and corresponding operation entry points are provided for users to choose to authorize or refuse.
[0069] Corresponding to the IoT platform access method provided in the embodiments of this application, the embodiments of this application provide an IoT platform access device applied to an access client of an access system. The access device includes: a communication configuration information receiving module, configured to receive communication configuration information from a target caller, wherein the communication configuration information includes protocol configuration information and communication performance configuration information, the protocol configuration information matching the communication protocol applicable to the target caller, and the communication performance configuration information matching the communication performance of the IoT platform and / or the access system; a channel construction module, configured to determine a corresponding target protocol adapter from a plurality of protocol adapters according to the protocol configuration information, and construct a target protocol channel between the target caller and the target protocol adapter to establish a communication connection between the target caller and the target protocol adapter, and control the communication performance of the protocol channel connected to the caller according to the caller's communication performance configuration information; construct a target message channel between the target caller and the target protocol adapter, and transmit messages between the target caller and the target protocol adapter through the target message channel, wherein the target protocol channel and the target message channel are parallel channels.
[0070] In one implementation, the communication performance configuration information includes traffic rate limiting information and / or the number of connection threads.
[0071] In one embodiment, the protocol channel is used to perform protocol connection processing according to the protocol configuration information and communication performance configuration information of the caller to which it is connected, wherein the protocol connection processing includes at least one of the following: protocol connection initialization, establishing a protocol connection, disconnecting a protocol connection, and reconnecting a protocol.
[0072] In one implementation, the message channel is used to process the messages it transmits in order to provide the target caller with a message having a preset data model.
[0073] The functions of each module in each device in the embodiments of this application can be found in the corresponding description in the above method, and they have corresponding beneficial effects, which will not be repeated here.
[0074] Figure 4 A schematic block diagram of an example electronic device 400 that can be used to implement embodiments of the present disclosure is shown. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device may also represent various forms of mobile devices, such as personal digital assistants, cellular phones, smartphones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely illustrative and are not intended to limit the implementation of the present disclosure described and / or claimed herein.
[0075] like Figure 4 As shown, device 400 includes a computing unit 401, which can perform various appropriate actions and processes based on a computer program stored in read-only memory (ROM) 402 or a computer program loaded from storage unit 408 into random access memory (RAM) 403. RAM 403 may also store various programs and data required for the operation of device 400. The computing unit 401, ROM 402, and RAM 403 are interconnected via a bus 404. An input / output (I / O) interface 405 is also connected to bus 404.
[0076] Multiple components in device 400 are connected to I / O interface 405, including: input unit 406, such as keyboard, mouse, etc.; output unit 407, such as various types of monitors, speakers, etc.; storage unit 408, such as disk, optical disk, etc.; and communication unit 409, such as network card, modem, wireless transceiver, etc. Communication unit 409 allows device 400 to exchange information / data with other devices through computer networks such as the Internet and / or various telecommunications networks.
[0077] The computing unit 401 can be various general-purpose and / or special-purpose processing components with processing and computing capabilities. Some examples of the computing unit 401 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various special-purpose artificial intelligence (AI) computing chips, various computing units running machine learning model algorithms, digital signal processors (DSPs), and any suitable processor, controller, microcontroller, etc. The computing unit 401 performs the various methods and processes described above, such as the methods described above. For example, in some embodiments, the methods of the embodiments of this application can be implemented as computer software programs tangibly contained in a machine-readable medium, such as a storage unit (Storage) 408. In some embodiments, part or all of the computer program can be loaded and / or installed on the device 400 via a ROM (Read-Only Memory) 402 and / or a communication unit (Communication) 409. When a computer program is loaded into RAM (Random Access Memory) 403 and executed by computing unit 401, one or more steps of the method described above can be performed. Alternatively, in other embodiments, computing unit 401 may be configured to perform the methods of embodiments of this application by any other suitable means (e.g., by means of firmware).
[0078] Various embodiments of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard parts (ASSPs), systems-on-chips (SoCs), complex programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various embodiments may include implementations in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which may be a dedicated or general-purpose programmable processor, capable of receiving data and instructions from a memory system, at least one input device, and at least one output device, and transmitting data and instructions to the memory system, the at least one input device, and the at least one output device.
[0079] The program code used to implement the methods of this disclosure may be written in any combination of one or more programming languages. This program code may be provided to a processor or controller of a general-purpose computer, special-purpose computer, or other programmable data processing apparatus, such that when executed by the processor or controller, the program code causes the functions / operations specified in the flowcharts and / or block diagrams to be implemented. The program code may be executed entirely on a machine, partially on a machine, as a standalone software package partially on a machine and partially on a remote machine, or entirely on a remote machine or server.
[0080] In the context of this disclosure, a machine-readable medium can be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, apparatus, or device. A machine-readable medium can be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium can be, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination of the foregoing. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, compact disc read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.
[0081] To provide interaction with a user, the systems and techniques described herein can be implemented on a computer having: a display device for displaying information to the user, such as a cathode ray tube (CRT) or liquid crystal display (LCD) monitor; and a keyboard and pointing device (e.g., a mouse or trackball) through which the user provides input to the computer. Other types of devices can also be used to provide interaction with the user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including sound input, voice input, or tactile input).
[0082] The systems and technologies described herein can be implemented in computing systems that include backend components (e.g., as data servers), or computing systems that include middleware components (e.g., application servers), or computing systems that include frontend components (e.g., user computers with a graphical user interface or web browser through which a user can interact with implementations of the systems and technologies described herein), or computing systems that include any combination of such backend, middleware, or frontend components. The components of the system can be interconnected via digital data communication (e.g., communication networks) of any form or medium. Examples of communication networks include local area networks (LANs), wide area networks (WANs), and the Internet. The computer system can include clients and servers. Clients and servers are generally geographically distant from each other and typically interact via communication networks. Client-server relationships are created by computer programs running on respective computers and having client-server relationships with each other. Servers can be cloud servers, servers for distributed systems, or servers incorporating blockchain technology. Embodiments of this application provide a computer-readable storage medium storing a computer program that, when executed by a processor, implements the methods provided in the embodiments of this application.
[0083] This application provides a computer program product, including a computer program that, when executed by a processor, implements the methods provided in this application. In the above embodiments, it can be implemented wholly or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented wholly or partially as a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the flow or function according to this application is generated.
[0084] This application also provides a chip including a processor for calling and executing instructions stored in a memory, causing a communication device with the chip installed to perform the method provided in this application.
[0085] This application also provides a chip, including: an input interface, an output interface, a processor, and a memory. The input interface, output interface, processor, and memory are connected through an internal connection path. The processor is used to execute code in the memory. When the code is executed, the processor is used to execute the method provided in the application embodiment.
[0086] In the description of this specification, references to terms such as "one embodiment," "some embodiments," "example," "specific example," or "some examples," etc., indicate that a specific feature, structure, material, or characteristic described in connection with that embodiment or example is included in at least one embodiment or example of this application. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in one or more embodiments or examples. Moreover, without contradiction, those skilled in the art can combine and integrate the different embodiments or examples described in this specification, as well as the features of those different embodiments or examples.
[0087] Furthermore, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one of that feature. In the description of this application, "a plurality of" means two or more, unless otherwise explicitly specified.
[0088] Any process or method described in the flowchart or otherwise herein can be understood as representing a module, segment, or portion of code comprising one or more executable instructions for implementing a particular logical function or process. Furthermore, the scope of the preferred embodiments of this application includes additional implementations in which functions may be performed not in the order shown or discussed, including substantially simultaneously or in reverse order depending on the functionality involved.
[0089] The above description is merely an exemplary embodiment of this application, but the scope of protection of this application is not limited thereto. Any person skilled in the art can easily conceive of various variations or substitutions within the technical scope described in this application, and these should all be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.
Claims
1. An access system for an Internet of Things (IoT) platform, characterized in that, include: A protocol resource management module, which includes multiple protocol adapters, each of which corresponds to a different communication protocol; An access client is configured to receive communication configuration information from multiple callers, wherein the communication configuration information of each caller includes the caller's protocol configuration information and communication performance configuration information, the caller's protocol configuration information is matched with the communication protocol applicable to the caller, and the caller's communication performance configuration information is matched with the communication performance of the IoT platform and / or the access system. The access client is also configured to, for each caller, construct parallel protocol channels and message channels between the caller and its matching protocol adapter according to the caller's protocol configuration information, and control the communication performance of the protocol channels connected to the caller according to the caller's communication performance configuration information.
2. The system according to claim 1, characterized in that, The communication performance configuration information includes traffic rate limiting information and / or the number of connection threads.
3. The system according to claim 1, characterized in that, The protocol channel is used to perform protocol connection processing according to the protocol configuration information and communication performance configuration information of the caller to which it is connected. The protocol connection processing method includes at least one of the following: protocol connection initialization, establishing a protocol connection, disconnecting a protocol connection, and reconnecting a protocol.
4. The system according to claim 1, characterized in that, The message channel is used to process the messages it transmits in order to provide the caller with a message having a preset data model. The message processing method includes at least one of data packaging, data format conversion and normalization processing.
5. The system according to any one of claims 1 to 4, characterized in that, The access clients include: The protocol configuration submodule is used to receive the communication protocol configuration information from the caller, verify the communication protocol configuration information, and associate it with the corresponding protocol channel. The lifecycle management submodule is used to receive the protocol lifecycle control instructions from the caller and output them to the corresponding protocol channel; The message processing submodule is used to interact with the caller.
6. The system according to any one of claims 1 to 4, characterized in that, The communication protocol includes at least one of the following: standard communication protocol for terminal devices, communication protocol for third-party platforms, extended protocol, and custom protocol.
7. An access method for an Internet of Things (IoT) platform, applied to an access client of an access system, characterized in that, The access system includes a protocol resource management module, which includes multiple protocol adapters, each corresponding to a different communication protocol; the method includes: Receive communication configuration information from the target caller, wherein the communication configuration information includes protocol configuration information and communication performance configuration information, the protocol configuration information is matched with the communication protocol applicable to the target caller, and the communication performance configuration information is matched with the communication performance of the IoT platform; The corresponding target protocol adapter is determined from the plurality of protocol adapters according to the protocol configuration information, and a target protocol channel is constructed between the target caller and the target protocol adapter to establish a communication connection between the target caller and the target protocol adapter. The communication performance of the protocol channel connected to the caller is controlled according to the communication performance configuration information of the caller. A target message channel is established between the target caller and the target protocol adapter, and messages are transmitted between the target caller and the target protocol adapter through the target message channel, wherein the target protocol channel and the target message channel are parallel channels.
8. The method according to claim 7, characterized in that, The communication performance configuration information includes traffic rate limiting information and / or the number of connection threads.
9. The method according to claim 7 or 8, characterized in that, The protocol channel is used to perform protocol connection processing according to the protocol configuration information and communication performance configuration information of the caller to which it is connected. The protocol connection processing includes at least one of the following: protocol connection initialization, establishing a protocol connection, disconnecting a protocol connection, and reconnecting a protocol connection; and / or, the message channel is used to process the messages it transmits in order to provide the target caller with a message having a preset data model.
10. An electronic device comprising a memory, a processor, and a computer program stored in the memory, wherein the processor, when executing the computer program, implements the method of any one of claims 7 to 9.
Citation Information
Cited By
Charging protocol loading method, charging equipment and computer readable storage medium
CN121664909A