Internet of Things platform multi-protocol intelligent adaptation system and method based on DASS capability

Abstract

The invention discloses an Internet of Things platform multi-protocol intelligent adaptation system and method based on DASS capability, and the system comprises the steps: a DASS core layer collects a routing decision context in real time, generates a routing decision instruction used for dynamically selecting an optimal protocol adapter instance according to the routing decision context, and transmits the routing decision instruction to a protocol adaptation layer; the protocol adaptation layer receives a routing decision instruction, and calls a pre-stored protocol adapter instance according to the decision instruction; performing protocol conversion on interaction information between the physical equipment layer and the DASS core layer by using the protocol adapter instance; the DASS core layer sends a standardized UDM message subjected to protocol conversion to a platform service layer; through plug-in dynamic adaptation and an intelligent routing mechanism, efficient and unified management of multiple protocols of the Internet of Things is realized, the access cost is remarkably reduced, and the system agility and the resource utilization efficiency are improved.

Description

Technical Field

[0001] This invention belongs to the field of communication protocol adaptation, specifically relating to a multi-protocol intelligent adaptation system and method for IoT platforms based on DASS capabilities. Background Technology

[0002] The rapid evolution of IoT technology has spurred the demand for interconnectivity among massive numbers of heterogeneous devices, and multi-protocol adaptation has become a core bottleneck restricting the large-scale development of platforms. Currently, mainstream IoT platforms generally face the challenge of diverse device communication protocols. Existing technical solutions mainly follow three paths: First, deploying dedicated protocol gateway hardware (such as MQTT gateways and Modbus-to-TCP gateways) to complete the conversion from protocol to platform standard protocols at the edge; second, building protocol parsing middleware at the platform access layer, developing independent parsing service modules for different protocols; and third, providing customized SDKs for devices, shielding protocol differences by encapsulating a unified interface.

[0003] The above solutions have revealed significant systemic flaws in practical applications. In terms of development efficiency, the protocol adaptation logic is deeply coupled with specific devices, requiring the development of a complete codebase from scratch for new protocols. Reusability is less than 30%, resulting in integration cycles lasting weeks or even months, making it difficult to respond to agile business needs. Regarding architectural flexibility, protocol capabilities are fixed at compile time, making it impossible to dynamically load or unload protocol plugins at runtime. Version upgrades require service interruptions, and hot expansion and canary releases are not supported. In terms of data processing, protocol conversion is concentrated at the gateway or platform entry point, easily becoming a performance bottleneck in high-concurrency scenarios. Furthermore, the lack of a unified data model means that heterogeneous formats (binary, JSON, XML) must be parsed individually by upper-layer applications, leading to high costs for data semantic understanding.

[0004] Security mechanisms for different protocols (such as CoAP's DTLS and MQTT's TLS) need to be configured independently, and authentication, encryption, and authorization policies cannot be uniformly governed across protocols, creating a security vulnerability. At the same time, resource-constrained devices lack dynamic negotiation capabilities and cannot select the optimal protocol based on real-time context such as power consumption and bandwidth, resulting in wasted energy and communication efficiency. Summary of the Invention

[0005] This invention provides a multi-protocol intelligent adaptation system and method for IoT platforms based on DASS capabilities. Through plug-in dynamic adaptation and intelligent routing mechanisms, it achieves efficient and unified management of multiple IoT protocols, significantly reducing access costs and improving system agility and resource utilization efficiency.

[0006] To achieve the above objectives, the technical solution adopted by the present invention is as follows:

[0007] The first aspect of the present invention provides a multi-protocol intelligent adaptation system for an Internet of Things platform based on DASS capabilities, comprising a physical device layer, a protocol adaptation layer, a DASS core layer, and a platform service layer that are sequentially connected in communication.

[0008] The DASS core layer collects routing decision context in real time, generates routing decision instructions for dynamically selecting the optimal protocol adapter instance based on the routing decision context, and sends the routing decision instructions to the protocol adaptation layer.

[0009] The protocol adaptation layer receives routing decision instructions and calls pre-stored protocol adapter instances according to the decision instructions; it uses the protocol adapter instances to perform protocol conversion on the interaction information between the physical device layer and the DASS core layer; the DASS core layer sends standardized UDM messages that have undergone protocol conversion to the platform service layer.

[0010] This invention's DASS core layer collects routing decision context in real time and dynamically generates optimal protocol adapter selection instructions, enabling the platform to adaptively switch communication protocols based on device status, network quality, and service requirements. This breaks through the limitations of traditional static protocol binding and achieves continuous optimization of communication efficiency and resource consumption.

[0011] Furthermore, the protocol adaptation layer is configured with a protocol plugin management port, which updates the protocol plugins within the protocol adaptation layer; loads the protocol plugins to obtain protocol adapter instances; and the protocol adaptation layer has a built-in protocol parser.

[0012] In the uplink direction, the protocol parser decodes the original protocol message of the physical device layer by calling the protocol adapter instance and attaches the protocol context to obtain structured data; the protocol adaptation layer submits the structured data to the DASS core layer;

[0013] In the downlink direction, the protocol parser serializes the standardized UDM messages of the DASS core layer into device management messages by calling the protocol adapter instance; after the protocol adaptation layer executes the security policy, the device management messages are sent to the physical device layer.

[0014] The protocol adaptation layer of this invention configures a protocol plugin management port, which supports hot-swapping, canary release, and version rollback of protocol plugins. This allows new protocol adaptations to be added without reconstructing the underlying framework. They can be reused by registering them as independent plugins, which significantly improves the agility of protocol extensions and reduces development and maintenance costs.

[0015] Furthermore, the DASS core layer includes a unified data transformation engine and a Kafka bus;

[0016] The unified data conversion engine converts the structured data submitted by the protocol adaptation layer into standardized UDM messages, which are then pushed to the platform service layer via the Kafka bus. The Kafka bus receives instructions from the platform service layer and sends them to the unified data conversion engine, which converts the platform service layer instructions into standardized UDM messages and sends them to the protocol adaptation layer.

[0017] This invention combines a unified data conversion engine with the Kafka bus to convert structured data submitted by the protocol adaptation layer into standardized UDM messages in real time. Asynchronous decoupled transmission via the Kafka bus significantly improves system throughput and reliability, avoiding performance bottlenecks caused by synchronous blocking. Similarly, the downlink direction receives platform service layer instructions via the Kafka bus and converts them back into UDM messages, achieving standardized encapsulation and unified scheduling of uplink and downlink data streams, thereby simplifying application development complexity.

[0018] Furthermore, the DASS core layer includes an intelligent routing engine; the intelligent routing engine communicatively connects the protocol adaptation layer and the platform service layer.

[0019] The intelligent routing engine includes a context collector, a routing policy library, a decision-maker, and an executor;

[0020] In response to the received structured data being a new device connection request, the context collector parses the new device connection request to obtain the device context; the decision-maker retrieves routing policy rules from the routing policy library based on the device context; and the executor generates a routing decision instruction based on the routing policy rules and sends it to the protocol adaptation layer.

[0021] The context collector periodically collects network context and platform context; in response to receiving instructions from the platform service layer, the decision context is composed of device context, network context and platform context; the decision maker calculates the optimal protocol adapter instance based on the routing decision context, generates a routing decision instruction and sends it to the protocol adaptation layer;

[0022] The protocol adaptation layer selects a protocol adapter instance based on the routing decision instruction and informs the new device of the communication protocol and configuration to be used through the LPNP response.

[0023] In this invention, the context collector periodically collects multi-dimensional context from devices, networks, and platforms, providing a comprehensive and real-time data foundation for routing decisions. The decision maker uses this information to retrieve routing policy rules and calculate the optimal protocol adapter instance. The executor then informs the device of the protocol and configuration to be used via LPNP response, achieving automation and intelligence in protocol selection. This significantly enhances communication efficiency and resource utilization, while also supporting dynamic protocol switching by devices in different scenarios, ensuring business continuity and service quality.

[0024] Furthermore, the device context includes device battery level, device signal strength, and a list of supported protocols; the network context includes network latency, network jitter, and packet loss rate; and the platform context includes the load of each protocol adapter and service priority.

[0025] The multi-dimensional data acquisition mechanism in this invention can accurately reflect the device's operating status, network link quality, and platform service capabilities, providing high-quality decision input for the intelligent routing engine. This ensures the accuracy and effectiveness of routing strategies, avoids suboptimal protocol selection due to missing information, and further improves the reliability and practicality of dynamic routing.

[0026] Furthermore, the DASS core layer is equipped with a unified security service engine; the unified security service engine includes an identity authentication unit, a key management unit, and an authorization verification unit.

[0027] The unified security service engine receives device credentials sent by the physical device layer, and the identity authentication unit verifies the device identity based on the device credentials and issues an access token.

[0028] The key management unit executes AES-GCM or ChaCha20-Poly1305 encryption algorithms to encrypt and decrypt the interactive information between the DASS core layer and the protocol adaptation layer.

[0029] The permission verification unit is used to verify whether the device within the physical device layer has the permission to execute platform service layer instructions.

[0030] In this invention, the identity authentication unit uniformly verifies device credentials and issues access tokens, avoiding the need for redundant development of authentication mechanisms for different protocols; the key management unit adopts strong encryption algorithms such as AES-GCM or ChaCha20-Poly1305 to ensure the confidentiality and integrity of information exchanged between the DASS core layer and the protocol adaptation layer; and the permission verification unit provides fine-grained access control to prevent unauthorized devices from executing high-risk commands.

[0031] Furthermore, the platform service layer communicates with the application layer, and the platform service layer includes a data storage unit and a rule engine; the data storage unit obtains standardized UDM messages transformed by the DASS core layer by subscribing to the Kafka bus, and stores the standardized UDM messages;

[0032] The application layer retrieves standardized UDM messages from the platform service layer for device monitoring and generates business instructions, which are then submitted to the rule engine of the platform service layer. The rule engine triggers preset logic based on the business instructions, transforms them into platform service layer instructions, and returns them to the DASS core layer for execution.

[0033] In this invention, the platform service layer subscribes to the Kafka bus through the data storage unit to obtain standardized UDM messages for persistence. The rule engine triggers preset logic based on business instructions submitted by the application layer and transforms them into platform service layer instructions, which are then returned to the DASS core layer for execution. This achieves the separation of responsibilities between data storage, rule processing, and business applications. This design allows the application layer to complete device monitoring and business orchestration simply by interacting with the standardized data model, without needing to understand the differences in underlying protocols. This greatly reduces the development threshold, improves business response speed and system scalability, and ensures the standardization and consistency of data flow.

[0034] The second aspect of this invention provides a multi-protocol intelligent adaptation method for an IoT platform based on DASS capabilities, specifically including:

[0035] Receive and parse new device connection requests to obtain device context; select the optimal protocol adapter instance based on the device context using routing; establish a protocol connection between the new device and the protocol adapter layer;

[0036] The protocol connection is used to send the original protocol messages of the physical device layer. The DASS core layer and protocol adaptation layer convert the original protocol messages into standardized UDM messages. The platform service layer performs device management, rule triggering and data storage on the standardized UDM messages.

[0037] Periodically collect network context and platform context; in response to received instructions from the platform service layer, the decision context is composed of device context, network context, and platform context; calculate the optimal protocol adapter instance based on the routing decision context, and dynamically adjust the protocol adapter instances for device connections within the physical device layer; inform the new device of the communication protocol and configuration to be used through LPNP response;

[0038] The protocol adapter instance is used to convert platform service layer instructions into device management messages; the physical device layer receives and executes the device management messages.

[0039] This invention establishes a closed-loop intelligent management system for the entire lifecycle of devices. By periodically collecting multi-dimensional context and dynamically adjusting protocol adapter instances, combined with the LPNP lightweight negotiation mechanism, it achieves continuous optimization of protocol selection and seamless switching of device connections, ensuring business continuity and communication reliability.

[0040] Furthermore, the original protocol messages of the physical device layer are sent using the protocol connection. These messages are then transformed into standardized UDM messages by the DASS core layer and protocol adaptation layer, specifically including:

[0041] The physical device layer generates and sends the original protocol message to the protocol adaptation layer; the original protocol message from the physical device layer is decoded, and a protocol context is appended to obtain structured data, which is then submitted to the DASS core layer; the structured data from the protocol adaptation layer is converted into a standardized UDM message and pushed to the platform service layer via the Kafka bus.

[0042] In this invention, the protocol adaptation layer decodes the additional protocol context to form structured data, and the unified data conversion engine converts it into UDM messages and pushes them to the platform service layer via the Kafka bus, ensuring the stability and order of massive device data uploads.

[0043] Furthermore, the platform service layer instructions are converted into device management messages using a protocol adapter instance, specifically including:

[0044] The platform service layer instructions are converted into standardized UDM messages and sent to the protocol adaptation layer. The protocol adaptation layer calls the protocol adapter instance to serialize the standardized UDM messages of the DASS core layer into device management messages. After executing the security policy, the device management messages are sent to the physical device layer.

[0045] In this invention, the security policy execution ensures that every downlink instruction is authenticated and encrypted to prevent unauthorized access and data tampering. At the same time, it decouples serialization from policy execution, improving the flexibility and maintainability of the downlink channel.

[0046] Furthermore, the protocol plugins within the protocol adaptation layer are updated by the protocol plugin management port; the protocol plugins are parsed to obtain the protocol identifier, version, and dependency declarations; after verifying runtime environment compatibility based on the protocol identifier, version, and dependency declarations, the protocol plugins and dependency libraries are dynamically loaded using an isolated class loader; the protocol plugins are instantiated to obtain protocol adapter instances; and the protocol adapter instances are registered to the PBT repository within the protocol adaptation layer.

[0047] This invention achieves dynamic updates of protocol plugins through a protocol plugin management port. By combining the parsing of protocol identifiers, versions, and dependency declarations with runtime environment compatibility verification, it ensures that only compatible and secure plugins are loaded, effectively preventing system crashes caused by version conflicts or missing dependencies. Using an isolated class loader to dynamically load plugins and dependency libraries achieves runtime isolation between different protocol adapters, avoiding dependency conflicts and fault propagation between plugins and ensuring the stability of the core system. After plugin instantiation, they are uniformly registered to the PBT repository, forming a centralized protocol adapter management mechanism. This supports rapid access and hot deployment of new protocols, significantly shortening the protocol extension cycle and improving system maintainability and scalability.

[0048] Compared with the prior art, the beneficial effects of the present invention are as follows:

[0049] In this invention, the DASS core layer collects routing decision context in real time and generates dynamic selection instructions, breaking through the limitations of traditional static protocol binding. This enables the system to adaptively match the optimal protocol adapter instance based on the real-time status of devices, networks, platforms, etc., and complete protocol switching without interrupting services, thereby optimizing communication efficiency and resource consumption.

[0050] In this invention, the protocol adaptation layer completes the protocol conversion by calling pre-stored adapter instances, eliminating the need to repeatedly develop the underlying parsing logic. New protocols only need to be registered as plugins to reuse the upper-layer framework, significantly shortening the access cycle and reducing development costs. The DASS core layer outputs standardized UDM messages to the platform service layer, unifying heterogeneous protocol data into a single data model within the platform, completely eliminating the burden of understanding multi-protocol semantics for upper-layer applications and simplifying the data processing flow. Attached Figure Description

[0051] Figure 1 This is a structural diagram of the IoT platform multi-protocol intelligent adaptation system provided in Embodiment 1 of the present invention;

[0052] Figure 2 This is a flowchart for establishing a protocol connection provided in Embodiment 2 of the present invention;

[0053] Figure 3 This is a flowchart of the device data uplink processing provided in Embodiment 2 of the present invention;

[0054] Figure 4 This is a flowchart of the intelligent routing process for downlink commands provided in Embodiment 2 of the present invention;

[0055] Figure 5 This is a flowchart of the dynamic protocol plugin management process provided in Embodiment 2 of the present invention. Detailed Implementation

[0056] The present invention will be further described below with reference to the accompanying drawings. The following embodiments are only used to more clearly illustrate the technical solution of the present invention, and should not be used to limit the scope of protection of the present invention.

[0057] Example 1

[0058] like Figure 1 As shown, this embodiment provides a multi-protocol intelligent adaptation system for an IoT platform based on DASS capabilities, including a physical device layer, a protocol adaptation layer, a DASS core layer, and a platform service layer that are connected in sequence.

[0059] The protocol adaptation layer is configured with a protocol plugin management port, which updates the protocol plugins within the protocol adaptation layer. Each protocol plugin is equipped with an XML / YAML description file, which declares metadata such as protocol ID, version, supported features (QoS, security mechanisms), data format, and default port, for automatic discovery and configuration by the engine.

[0060] The protocol plugin is loaded to obtain a protocol adapter instance; the protocol adaptation layer contains multiple independent protocol adapter instances (MQTT, CoAP, HTTP, LwM2M, Modbus, OPC-UA, etc.).

[0061] The protocol adaptation layer has a built-in protocol parser; in the uplink direction, the protocol parser decodes the original protocol message of the physical device layer by calling the protocol adapter instance and attaches the protocol context to obtain structured data; the protocol adaptation layer submits the structured data to the DASS core layer;

[0062] In the downlink direction, the protocol parser serializes the standardized UDM messages of the DASS core layer into device management messages by calling the protocol adapter instance; after the protocol adaptation layer executes the security policy, it sends the device management messages to the physical device layer.

[0063] The protocol adaptation layer supports plugin version management, canary release, and rollback mechanisms, enabling zero-downtime protocol expansion and upgrades.

[0064] The protocol adaptation layer configures a protocol plugin management port, supporting hot-swapping, canary releases, and version rollback of protocol plugins. This allows new protocol integration without reconstructing the underlying framework; simply registering the plugin independently enables the reuse of infrastructure such as connection management, security policies, and message buses, significantly enhancing system agility and scalability. The built-in protocol parser decodes raw packets and appends protocol context to form structured data in the uplink direction, and serializes standardized UDM messages into device management messages in the downlink direction, executing security policies to ensure accurate conversion and secure control of bidirectional data exchange.

[0065] The DASS core layer is equipped with an intelligent routing engine; the intelligent routing engine is communicatively connected to the protocol adaptation layer and the platform service layer.

[0066] The intelligent routing engine includes a context collector, a routing policy library, a decision-maker, and an executor;

[0067] In response to the received structured data being a new device connection request, the context collector parses the new device connection request to obtain the device context; the decision-maker retrieves routing policy rules from the routing policy library based on the device context; and the executor generates a routing decision instruction based on the routing policy rules and sends it to the protocol adaptation layer.

[0068] The context collector periodically collects network context and platform context; in response to receiving instructions from the platform service layer, the decision context is composed of device context, network context, and platform context;

[0069] The device context includes device battery level, device signal strength, and a list of supported protocols; the network context includes network latency, network jitter, and packet loss rate; and the platform context includes the load of each protocol adapter and service priority.

[0070] The decision-maker calculates the optimal protocol adapter instance based on the routing decision context and generates routing decision instructions to send to the protocol adaptation layer.

[0071] The protocol adaptation layer selects a protocol adapter instance based on the routing decision instruction and informs the new device of the communication protocol and configuration to be used through the LPNP response.

[0072] The intelligent routing engine configured within the DASS core layer achieves dynamic routing decisions based on multiple dimensions of context, including device power, signal strength, supported protocol list, network latency, jitter, packet loss rate, platform load, and service priority, through the coordinated operation of the context collector, routing policy library, decision maker, and executor. This enables the platform to adaptively select the optimal protocol adapter instance based on real-time conditions and inform the device of the communication protocol and configuration to be used through LPNP responses. This breaks through the limitations of traditional static protocol binding and achieves continuous optimization of communication efficiency and resource consumption.

[0073] The DASS core layer is equipped with a unified data transformation engine and a Kafka bus.

[0074] In the uplink direction, the unified data conversion engine converts the structured data submitted by the protocol adaptation layer into standardized UDM messages. These standardized UDM messages are pushed to the platform service layer via the Kafka bus. The standardized UDM messages include: "deviceId": a unique device identifier for the platform; "timestamp": a data point timestamp; "attributes": key-value pairs (e.g., {"firmware": "v1.2"}); "telemetry": time-series telemetry data (e.g., `{"temp": 25.6, "hum": 65}`); and "commandResponse" / "event": command response or event.

[0075] In the downlink direction, the Kafka bus receives instructions from the platform service layer and sends them to the unified data conversion engine. The unified data conversion engine converts the platform service layer instructions into standardized UDM messages and sends them to the protocol adaptation layer.

[0076] The combination of a unified data transformation engine and the Kafka bus converts structured data into standardized UDM messages in real time and transmits them asynchronously and decoupled through Kafka. Uplink data is pushed to the platform service layer via Kafka, while downlink data is received from the platform and converted in reverse. This achieves standardized encapsulation and unified scheduling of uplink and downlink data streams, allowing the platform service layer to focus on business logic processing without having to worry about the details of the underlying protocols, thus simplifying the complexity of application development. At the same time, the high reliability of Kafka ensures the stability and order of data transmission across massive devices.

[0077] The DASS core layer is equipped with a unified security service engine; the unified security service engine includes an identity authentication unit, a key management unit, and an authorization verification unit.

[0078] The unified security service engine receives device credentials sent by the physical device layer, and the identity authentication unit verifies the device identity based on the device credentials and issues an access token.

[0079] The key management unit executes AES-GCM or ChaCha20-Poly1305 encryption algorithms to encrypt and decrypt the interactive information between the DASS core layer and the protocol adaptation layer.

[0080] The permission verification unit is used to verify whether the device within the physical device layer has the permission to execute platform service layer instructions.

[0081] The platform service layer communicates with the application layer. The platform service layer includes a data storage unit and a rule engine. The data storage unit obtains standardized UDM messages transformed by the DASS core layer by subscribing to the Kafka bus and stores the standardized UDM messages.

[0082] The application layer retrieves standardized UDM messages from the platform service layer for device monitoring and generates business instructions, which are then submitted to the rule engine of the platform service layer. The rule engine triggers preset logic based on the business instructions, transforms them into platform service layer instructions, and returns them to the DASS core layer for execution.

[0083] The platform service layer subscribes to the Kafka bus through the data storage unit to obtain standardized UDM messages for persistence. The rule engine triggers preset logic based on the business instructions submitted by the application layer and transforms them into platform service layer instructions, which are then returned to the DASS core layer for execution. This achieves the separation of responsibilities between data storage, rule processing, and business applications, enabling the application layer to complete device monitoring and business orchestration by interacting only with the standardized data model. This greatly reduces the development threshold and improves business response speed and system scalability.

[0084] Example 2

[0085] like Figure 3 As shown, this embodiment provides a multi-protocol intelligent adaptation method for IoT platforms based on DASS capabilities. This method is applied to the multi-protocol intelligent adaptation system for IoT platforms described in Embodiment 1. The multi-protocol intelligent adaptation method includes:

[0086] like Figure 5 As shown, the protocol plugins within the protocol adaptation layer are updated by the protocol plugin management port; the protocol plugins are parsed to obtain the protocol identifier, version, and dependency declarations; after verifying runtime environment compatibility based on the protocol identifier, version, and dependency declarations, the protocol plugins and dependency libraries are dynamically loaded using an isolated class loader; a protocol adapter instance is obtained by instantiating the protocol plugins; and the protocol adapter instance is registered to the PBT repository within the protocol adaptation layer.

[0087] The protocol plugins within the protocol adaptation layer are updated through the protocol plugin management port. The protocol identifier, version, and dependency declaration are parsed, and after verifying runtime environment compatibility, the plugins and dependency libraries are dynamically loaded using an isolated class loader. After instantiation, they are registered to the PBT repository, which realizes the standardization and isolation of plugin loading, avoids dependency conflicts between different plugins, and ensures the system stability and security during the hot-plugging process of plugins.

[0088] like Figure 2 As shown, within the physical device layer, a new device broadcasts or unicasts a connection request (containing `deviceId` (optional temporary ID), `supportedProtocols=[CoAP, MQTT-SN]`, `securityLevel=Medium`, `batteryLevel=30%`), and the protocol adaptation layer forwards the new device connection request to the DASS core layer.

[0089] The DASS core layer receives and parses new device connection requests to obtain the device context; after querying the USS to verify temporary credentials, it selects the optimal protocol adapter instance based on the device context; specifically, this includes:

[0090] First, real-time collected device, network, and platform context data are constructed into decision fact objects, triggering all matching rules in the rule base and extracting their recommended candidate protocols. Then, based on a multi-objective optimization framework, resource efficiency (power consumption and memory usage), transmission performance (latency and throughput), reliability (QoS level and retransmission mechanism), and security compliance of each protocol are scored separately. The total score is calculated by combining the priority weight of the rules, the matching degree, and the protocol switching penalty (such as connection reconstruction overhead). Finally, the optimal protocol is selected according to the score, realizing real-time dynamic adaptation of device status, network quality, and business policies.

[0091] The new device sends a response to the device via the LPNP Adapter; the new device uses CoAP and DTLS PSK to connect to the specified protocol adapter instance, establishing a protocol connection between the new device and the protocol adaptation layer.

[0092] like Figure 3 As shown, the original protocol messages of the physical device layer are sent using the protocol connection. These messages are then transformed into standardized UDM messages by the DASS core layer and protocol adaptation layer, specifically including:

[0093] The physical device layer generates and sends the original protocol message to the protocol adaptation layer. The protocol adaptation layer decodes the original protocol message from the physical device layer, identifies the device identifier and register value (`deviceSn: D-001, regAddr:0x000A, value: 25.6 (float)`). It appends the protocol context (original data + `deviceSn` + protocol type `modbus-tcp`) to the original protocol message to obtain structured data, and submits the structured data to the DASS core layer.

[0094] The DASS core layer contains a unified data conversion engine; the unified data conversion engine converts the structured data from the protocol adaptation layer into standardized UDM messages, and publishes the standardized UDM messages to the Kafka bus Topic `telemetry / Device123`.

[0095] The platform service layer's rule engine subscribes to this topic and triggers rules (such as `if temperature>30 thensend alert`); the time-series database subscribes to and stores the data.

[0096] The platform service layer manages devices, triggers rules, and stores data using standardized UDM messages.

[0097] like Figure 4 As shown, network context and platform context are collected periodically; in response to received instructions from the platform service layer, application permissions are verified (USS authorization service), and device status (online) is checked.

[0098] The platform service layer instructions are encapsulated into standard downlink messages and submitted to the intelligent routing engine (SRE). The decision context consists of device context, network context, and platform context. The intelligent routing engine (SRE) calculates the optimal protocol adapter instance based on the routing decision context and dynamically adjusts the protocol adapter instances for device connections within the physical device layer. The SRE informs the new device of the communication protocol and configuration to be used through an LPNP response.

[0099] The protocol adapter instance is used to convert platform service layer commands into device management messages, specifically including:

[0100] The platform service layer instructions are converted into standardized UDM messages and sent to the protocol adaptation layer. The protocol adaptation layer calls the protocol adapter instance to serialize the standardized UDM messages of the DASS core layer into device management messages. After executing the security policy, the device management messages are sent to the physical device layer. The physical device layer receives and executes the device management messages.

[0101] The new device sends a connection request via LPNP broadcast or unicast, containing key information such as device identifier, supported protocol list, security level, and battery level. The protocol adaptation layer forwards the request to the DASS core layer, where the context collector parses it to obtain the device context. The decision-maker retrieves routing policy rules based on the device context, network context, and platform context, calculates the optimal protocol adapter instance, and informs the device of the communication protocol and configuration to be used via an LPNP response. This enables intelligent protocol negotiation during the device access phase, allowing resource-constrained devices to select the optimal protocol during the initial connection, reducing connection establishment overhead and energy consumption.

[0102] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0103] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart... Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0104] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0105] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0106] The above description is only a preferred embodiment of the present invention. It should be noted that for those skilled in the art, several improvements and modifications can be made without departing from the technical principles of the present invention, and these improvements and modifications should also be considered within the scope of protection of the present invention.

Claims

1. A multi-protocol intelligent adaptation system for an IoT platform based on DASS capabilities, characterized in that, This includes the physical device layer, protocol adaptation layer, DASS core layer, and platform service layer, which are connected in sequence. The DASS core layer collects routing decision context in real time, generates routing decision instructions for dynamically selecting the optimal protocol adapter instance based on the routing decision context, and sends the routing decision instructions to the protocol adaptation layer. The protocol adaptation layer receives routing decision instructions, calls pre-stored protocol adapter instances according to the decision instructions, and uses the protocol adapter instances to perform protocol conversion on the interaction information between the physical device layer and the DASS core layer. The DASS core layer sends standardized UDM messages, which have undergone protocol conversion, to the platform service layer.

2. The IoT platform multi-protocol intelligent adaptation system according to claim 1, characterized in that, The protocol adaptation layer is configured with a protocol plugin management port, which updates the protocol plugins within the protocol adaptation layer; loads the protocol plugins to obtain protocol adapter instances; the protocol adaptation layer has a built-in protocol parser; In the uplink direction, the protocol parser decodes the raw protocol messages of the physical device layer by calling the protocol adapter instance and attaches the protocol context to obtain structured data; The protocol adaptation layer submits structured data to the DASS core layer; In the downlink direction, the protocol parser serializes the standardized UDM messages of the DASS core layer into device management messages by calling the protocol adapter instance; After executing the security policy, the protocol adaptation layer sends the device management message to the physical device layer.

3. The IoT platform multi-protocol intelligent adaptation system according to claim 2, characterized in that, The DASS core layer includes a unified data transformation engine and a Kafka bus; The unified data conversion engine converts the structured data submitted by the protocol adaptation layer into standardized UDM messages, which are then pushed to the platform service layer via the Kafka bus. The Kafka bus receives instructions from the platform service layer and sends them to the unified data transformation engine. The unified data transformation engine converts the platform service layer instructions into standardized UDM messages and sends them to the protocol adaptation layer.

4. The IoT platform multi-protocol intelligent adaptation system according to claim 2, characterized in that, The DASS core layer includes an intelligent routing engine; the intelligent routing engine is communicatively connected to the protocol adaptation layer and the platform service layer. The intelligent routing engine includes a context collector, a routing policy library, a decision-maker, and an executor; In response to the received structured data being a new device connection request, the context collector parses the new device connection request to obtain the device context; the decision-maker retrieves routing policy rules from the routing policy library based on the device context; and the executor generates a routing decision instruction based on the routing policy rules and sends it to the protocol adaptation layer. The context collector periodically collects network context and platform context; In response to receiving a platform service layer instruction, the decision context is composed of device context, network context, and platform context; The decision-maker calculates the optimal protocol adapter instance based on the routing decision context and generates routing decision instructions to send to the protocol adaptation layer. The protocol adaptation layer selects a protocol adapter instance based on the routing decision instruction and informs the new device of the communication protocol and configuration to be used through the LPNP response.

5. The IoT platform multi-protocol intelligent adaptation system according to claim 4, characterized in that, The device context includes device battery level, device signal strength, and a list of supported protocols; the network context includes network latency, network jitter, and packet loss rate; and the platform context includes the load of each protocol adapter and service priority.

6. The IoT platform multi-protocol intelligent adaptation system according to claim 1, characterized in that, The DASS core layer is equipped with a unified security service engine; the unified security service engine includes an identity authentication unit, a key management unit, and an authorization verification unit. The unified security service engine receives device credentials sent by the physical device layer, and the identity authentication unit verifies the device identity based on the device credentials and issues an access token. The key management unit executes AES-GCM or ChaCha20-Poly1305 encryption algorithms to encrypt and decrypt the interactive information between the DASS core layer and the protocol adaptation layer. The permission verification unit is used to verify whether the device within the physical device layer has the permission to execute platform service layer instructions.

7. The IoT platform multi-protocol intelligent adaptation system according to claim 3, characterized in that, The platform service layer communicates with the application layer. The platform service layer includes a data storage unit and a rule engine. The data storage unit obtains standardized UDM messages transformed by the DASS core layer by subscribing to the Kafka bus and stores the standardized UDM messages. The application layer retrieves standardized UDM messages from the platform service layer for device monitoring and generates business instructions, which are then submitted to the rule engine of the platform service layer. The rule engine triggers preset logic based on the business instructions, transforms them into platform service layer instructions, and returns them to the DASS core layer for execution.

8. The control method for the multi-protocol intelligent adaptation system of the Internet of Things platform according to any one of claims 1 to 7, characterized in that, include: Receive and parse new device connection requests to obtain device context; The optimal protocol adapter instance is selected by routing based on the device context; Establish a protocol connection between the new device and the protocol adaptation layer; The protocol raw message of the physical device layer is sent using the protocol connection, and the DASS core layer and protocol adaptation layer convert the protocol raw message into a standardized UDM message. The platform service layer manages devices, triggers rules, and stores data using standardized UDM messages; Periodically collect network context and platform context; in response to receiving instructions from the platform service layer, the decision context is composed of device context, network context, and platform context; Calculate the optimal protocol adapter instance based on the routing decision context, and dynamically adjust the protocol adapter instances for device connections within the physical device layer; inform the new device of the communication protocol and configuration to be used through the LPNP response; The protocol adapter instance is used to convert platform service layer instructions into device management messages; the physical device layer receives and executes the device management messages.

9. The control method according to claim 8, characterized in that, The protocol raw messages of the physical device layer are sent using the protocol connection. These messages are then transformed into standardized UDM messages by the DASS core layer and protocol adaptation layer. Specifically, this includes: The physical device layer generates and sends the original protocol message to the protocol adaptation layer; the original protocol message from the physical device layer is decoded, and a protocol context is appended to obtain structured data, which is then submitted to the DASS core layer; the structured data from the protocol adaptation layer is converted into a standardized UDM message and pushed to the platform service layer via the Kafka bus.

10. The control method according to claim 8, characterized in that, The protocol adapter instance is used to convert platform service layer commands into device management messages, specifically including: The platform service layer instructions are converted into standardized UDM messages and sent to the protocol adaptation layer. The protocol adaptation layer calls the protocol adapter instance to serialize the standardized UDM messages of the DASS core layer into device management messages. After executing the security policy, the device management messages are sent to the physical device layer.

11. The control method according to claim 8, characterized in that, The protocol plugins within the protocol adaptation layer are updated via the protocol plugin management port; the protocol plugins are parsed to obtain the protocol identifier, version, and dependency declarations; after verifying runtime environment compatibility based on the protocol identifier, version, and dependency declarations, the protocol plugins and dependency libraries are dynamically loaded using an isolated class loader; a protocol adapter instance is instantiated to obtain a protocol plugin instance; and the protocol adapter instance is registered to the PBT repository within the protocol adaptation layer.

Images