Communication method and device of Internet of Things platform, electronic equipment and medium

Abstract

The embodiment of the invention discloses a communication method and device of an Internet of Things platform, electronic equipment and a storage medium. The method comprises the steps of obtaining a target parameter set required during communication of the Internet of Things platform; according to the target parameter set, initializing a call software development kit of the Internet of Things platform; according to the target parameter set and the initialized call software development kit, triggering a communication request between a device end and the Internet of Things platform; configuring a communication plug-in and a communication interface corresponding to the communication request; constructing a cloud service corresponding to the Internet of Things cloud platform; and based on the communication plug-in, the communication interface and the cloud service, constructing a communication channel between the device end and the Internet of Things platform, so that the device end communicates with the Internet of Things platform through the communication channel, the communication cost and the operation threshold of the Internet of Things platform can be reduced, and meanwhile, the communication efficiency of the Internet of Things platform is improved. And the communication compatibility of the Internet of Things platform is improved.

Description

Technical Field

[0001] This application relates to the field of Internet of Things (IoT) technology, specifically to a communication method, device, electronic device, and storage medium for an IoT platform. Background Technology

[0002] With the integration and development of IoT technology and audio and video communication technology, the demand for real-time voice interaction between devices and users is growing. Especially in scenarios such as smart homes and remote monitoring, users urgently need to achieve low-cost and highly stable calls with IoT devices through convenient terminals (such as WeChat mini programs).

[0003] Currently, traditional IoT device voice communication solutions mostly rely on third-party audio and video SDKs or self-built communication servers, which have the following drawbacks: First, the integration cost is high, requiring separate development of communication modules for both the device and the user, and different device models need repeated adaptation, resulting in poor compatibility; second, the security authentication mechanism is imperfect, with a lack of unified standards for device authentication and data transmission encryption, making it prone to identity forgery and data leakage risks; third, the deployment complexity is high, requiring the construction of independent transcoding services and signaling servers, resulting in high operation and maintenance costs, and it is difficult to integrate with high-frequency application ecosystems such as WeChat, requiring users to download a dedicated APP, which raises the operational threshold. Summary of the Invention

[0004] This application provides a communication method, electronic device, apparatus, and storage medium for an Internet of Things (IoT) platform, which can reduce the communication cost and operational threshold of the IoT platform, while improving the communication compatibility of the IoT platform.

[0005] In a first aspect, embodiments of this application provide a communication method for an Internet of Things (IoT) platform, comprising:

[0006] Obtain the target parameter set required for communication on the IoT platform;

[0007] The communication software development kit of the IoT platform is initialized according to the target parameter set;

[0008] Based on the target parameter set and the initialized call software development kit, a communication request is triggered between the device and the IoT platform;

[0009] Configure the communication plugin and communication interface corresponding to the communication request;

[0010] Construct cloud services corresponding to the aforementioned IoT cloud platform;

[0011] Based on the aforementioned communication plugin, communication interface, and cloud service, a communication channel is constructed between the device and the IoT platform, enabling the device to communicate with the IoT platform through the communication channel.

[0012] Optionally, in some embodiments of this application, the initialization of the call software development kit of the IoT platform according to the target parameter set includes:

[0013] The initialization function corresponding to the call software development kit of the IoT platform is called, and the target parameter set is passed in.

[0014] Determine if the device is running the call software development kit for the first time;

[0015] If the device is running the call software development kit for the first time, the target token is extracted from the target parameter set, and the corresponding device registration function of the device is called.

[0016] The call software development kit of the IoT platform is initialized based on the target token and the device registration function.

[0017] Optionally, in some embodiments of this application, the initialization of the call software development kit of the IoT platform based on the target token and the device registration function includes:

[0018] The target token is transmitted to the device registration function to adjust the device registration function;

[0019] Based on the adjusted device registration function, a device registration request is triggered to the third-party platform corresponding to the device.

[0020] Upon receiving a registration success message from the third-party platform, the initialization of the call software development kit for the IoT platform is completed.

[0021] Optionally, in some embodiments of this application, triggering a communication request between the device and the IoT platform based on the target parameter set and the initialized call software development kit includes:

[0022] Extract the communication parameters that trigger the communication request from the target parameter set;

[0023] Call the call function in the aforementioned call software tool development kit;

[0024] Based on the communication parameters and the call function, a communication request is triggered between the device and the IoT platform.

[0025] Optionally, in some embodiments of this application, triggering a communication request between the device and the IoT platform based on the communication parameters and the call function includes:

[0026] The communication parameters are transmitted to the call function to adjust the call function;

[0027] Based on the adjusted call function, a communication request is triggered between the device and the IoT platform.

[0028] Optionally, in some embodiments of this application, the step of constructing a communication channel between the device and the IoT platform based on the communication plug-in, communication interface, and cloud service, so that the device can communicate with the IoT platform through the communication channel, includes:

[0029] Determine the program terminal that communicates with the device.

[0030] Initialize the communication plugin and communication interface corresponding to the program terminal;

[0031] Parse the communication interface to obtain the communication identifier corresponding to the program end;

[0032] Based on the communication identifier, the initialized program and cloud services, a communication channel is constructed between the device and the IoT platform so that the device can communicate with the IoT platform through the communication channel.

[0033] Optionally, in some embodiments of this application, the step of constructing a communication channel between the device and the IoT platform based on the communication identifier, the initialized program terminal, and the cloud service, so that the device can communicate with the IoT platform through the communication channel, includes:

[0034] Determine the voice space corresponding to the communication identifier;

[0035] Configure the multimedia stream forwarding strategy corresponding to the voice control based on cloud services;

[0036] Based on the aforementioned voice space, multimedia stream forwarding strategy, and cloud services, a communication channel is constructed between the device and the IoT platform, so that the device can communicate with the IoT platform through the communication channel.

[0037] Secondly, embodiments of this application provide a communication device for an Internet of Things (IoT) platform, comprising:

[0038] The acquisition module is used to acquire the target parameter set required for communication on the IoT platform;

[0039] An initialization module is used to initialize the call software development kit of the IoT platform according to the target parameter set;

[0040] The triggering module is used to trigger a communication request between the device and the IoT platform based on the target parameter set and the initialized call software development kit.

[0041] The configuration module is used to configure the communication plugin and communication interface corresponding to the communication request;

[0042] The building module is used to build the cloud services corresponding to the IoT cloud platform;

[0043] A communication module is used to construct a communication channel between the device and the IoT platform based on the communication plug-in, communication interface and cloud service, so that the device can communicate with the IoT platform through the communication channel.

[0044] Accordingly, this application also provides an electronic device, including a memory, a processor, and a processor program stored in the memory and executable on the processor, wherein the processor executes the program as described in any of the methods above.

[0045] This application also provides a storage medium storing a processor program that, when executed by a processor, implements any of the methods described above.

[0046] This application provides a communication method, apparatus, electronic device, and storage medium for an Internet of Things (IoT) platform. After obtaining the target parameter set required for communication on the IoT platform, the communication software development kit (SDK) of the IoT platform is initialized based on the target parameter set. Then, based on the target parameter set and the initialized SSD, a communication request is triggered between the device and the IoT platform. Next, the communication plugin and communication interface corresponding to the communication request are configured, and cloud services corresponding to the IoT cloud platform are constructed. Finally, based on the communication plugin, communication interface, and cloud services, a communication channel is constructed between the device and the IoT platform, enabling the device to communicate with the IoT platform through the communication channel. In the communication solution of the IoT platform provided in this application, different devices can connect based on a target parameter set, eliminating the need to define separate parameter systems for different devices and reducing repetitive adaptation work. Furthermore, based on the target parameter set and the initialized communication software development kit, communication requests between the device and the IoT platform are triggered, eliminating the need to develop separate device-side communication modules and significantly reducing connection costs. In addition, device authentication is performed using cloud services to avoid the risk of data leakage during transmission. Moreover, there is no need to build independent transcoding and signaling servers; room joining and audio / video forwarding can be completed by calling the software development kit. Therefore, this solution can reduce the communication costs and operational threshold of the IoT platform, while improving the communication compatibility of the IoT platform. Attached Figure Description

[0047] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0048] Figure 1 This is a flowchart illustrating the communication method of the Internet of Things platform provided in the embodiments of this application;

[0049] Figure 2 This is a schematic diagram of the structure of the communication device of the Internet of Things platform provided in the embodiments of this application;

[0050] Figure 3 This is a schematic diagram of the structure of the electronic device provided in the embodiments of this application. Detailed Implementation

[0051] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.

[0052] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element. Furthermore, components, features, and elements with the same names in different embodiments of this application may have the same meaning or different meanings, the specific meaning of which must be determined by its interpretation in that specific embodiment or further in conjunction with the context of that specific embodiment.

[0053] It should be understood that the specific embodiments described herein are merely illustrative of this application and are not intended to limit this application.

[0054] In the following description, the use of suffixes such as "module," "part," or "unit" to denote elements is solely for the purpose of illustrative purposes and has no specific meaning in itself. Therefore, "module," "part," or "unit" may be used interchangeably.

[0055] The following describes in detail the embodiments involved in this application. It should be noted that the order of description of the embodiments in this application is not intended to limit the priority of the embodiments.

[0056] This application provides a communication method, apparatus, storage medium, and smart terminal for an Internet of Things (IoT) platform. Specifically, the communication method of the IoT platform in this application can be executed by a smart terminal or a server, wherein the smart terminal can be a terminal. The terminal can be a smartphone, tablet computer, laptop computer, touch screen, game console, personal computer (PC), personal digital assistant (PDA), or other smart terminal. The terminal may also include a client, which can be a media playback client or an instant messaging client, etc.

[0057] This application provides a communication method for an Internet of Things (IoT) platform, which can be executed by an electronic device or a server. This application example illustrates the communication method of the IoT platform executed by an electronic device. The electronic device includes a touchscreen display and a processor. The touchscreen display is used to present a graphical user interface (GUI) and receive operation commands generated by the user interacting with the GUI. When the user operates the GUI through the touchscreen display, the GUI can control the local content of the electronic device in response to the received operation commands, or it can control the content on the server side in response to the received operation commands.

[0058] The communication solution for the IoT platform provided in this application allows different devices to interface based on a target parameter set, eliminating the need to define separate parameter systems for different devices and reducing repetitive adaptation work. Furthermore, based on the target parameter set and the initialized communication software development kit, communication requests between the device and the IoT platform are triggered, eliminating the need to develop separate device-side communication modules and significantly reducing integration costs. In addition, device authentication is performed using cloud services, avoiding the risk of data leakage during transmission. Moreover, there is no need to build independent transcoding and signaling servers; room joining and audio / video forwarding can be completed simply by calling the software development kit. Therefore, this solution can reduce the communication costs and operational barriers of the IoT platform, while improving the communication compatibility of the IoT platform.

[0059] The following sections provide detailed descriptions of each example. It should be noted that the order in which the embodiments are described is not intended to limit the priority of the embodiments.

[0060] A communication method for an Internet of Things (IoT) platform includes: acquiring a set of target parameters required for communication on the IoT platform; initializing a communication software development kit (SDK) for the IoT platform based on the target parameter set; triggering a communication request between a device and the IoT platform based on the target parameter set and the initialized SSD; configuring a communication plugin and communication interface corresponding to the communication request; constructing cloud services corresponding to the IoT cloud platform; and constructing a communication channel between the device and the IoT platform based on the communication plugin, communication interface, and cloud services, so that the device can communicate with the IoT platform through the communication channel.

[0061] Please see Figure 1 , Figure 1 This application provides a schematic flowchart of the communication method for an IoT platform. The specific flow of this communication method is as follows:

[0062] 101. Obtain the target parameter set required for communication on the IoT platform.

[0063] The target parameter set consists of core parameters that need to be obtained and configured in advance for communication between the device and the IoT platform. It is divided into two categories: device communication parameters and server-side room joining parameters. Device communication parameters may include: sn (device serial number), model_id (device model ID), appid (mini-program unique identifier), sn_ticket (device registration security token), and openid (WeChat user unique identifier). Server-side room joining parameters may include: appid, sn, model_id, and server_token (server authentication token).

[0064] For example, you can use an HTTP client like Postman to send a POST request to the SN ticket retrieval interface. The request body carries JSON data including the sn (e.g., voiptest1) and model_id (e.g., TVQKukFzuXOUZaKM3pjBbA). A successful response will yield the sn_ticket. In the WeChat Mini Program environment, you can execute the wx.login() method to obtain the user's openid and simultaneously call the wx.requestDeviceVoIP() function to obtain inter-device voice call permission. The specific steps depend on the actual call scenario and will not be elaborated upon here.

[0065] 102. Initialize the IoT platform's call software development kit based on the target parameter set.

[0066] Initialization refers to the process of completing basic configuration and identity association by passing key information from the target parameter set and calling the SDK's specified functions before using the IoT platform's calling software development kit (SDK) on the device. The purpose is to enable the SDK to have the basic ability to interact with the IoT platform, laying the foundation for subsequent operations such as initiating calls and transmitting audio and video streams.

[0067] The necessary parameters for device-side SDK initialization are selected from the target parameter set, including the mini-program appid, device model_id, device unique ID, and data folder path. This ensures the parameters match the actual device information and WeChat platform configuration, preventing initialization failure due to incorrect parameters. In the device-side code, the `wx_init` function provided by the call software development kit (device-side SDK) is called, passing the extracted mini-program appid, model_id, device ID, and data folder path as parameters. This function establishes the basic association between the SDK, the device, and the WeChat platform, enabling the SDK to initially support communication functionality. If the device is running the SDK for the first time, an additional `sn_ticket` (device registration security token) needs to be extracted from the target parameter set. The `wx_device_register` function in the SDK is then called, passing the `sn_ticket` to complete device registration with the backend. After successful registration, the device gains a legitimate identity to communicate with the IoT platform.

[0068] Optionally, in some embodiments of this application, the step "initializing the call software development kit of the IoT platform according to the target parameter set" may specifically include:

[0069] Call the initialization function corresponding to the IoT platform's call software development kit and pass in the target parameter set;

[0070] Determine if the device is running the call software development kit for the first time;

[0071] If the device is running the call software development kit for the first time, the target token is extracted from the target parameter set and the corresponding device registration function is called on the device.

[0072] The IoT platform's call software development kit is initialized based on the target token and the device registration function.

[0073] Extract the mini-program appid (e.g., "wx1234567890abcdef"), device model_id (e.g., "TVQKukFzuXOUZaKM3pjBbA"), device unique ID (e.g., "dev001"), and data folder path (e.g., " / data / voip / ") from the target parameter set. In the device-side code, call the wx_init function of the call SDK, passing in parameters in the form of "wx_init("wx1234567890abcdef","TVQKukFzuXOUZaKM3pjBbA","dev001"," / data / voip / ")" to complete the basic SDK initialization.

[0074] To determine if the SDK is being run for the first time on the device: Check the status identifier in the device's local storage (e.g., whether the "SDK_REGISTERED" file exists or whether there is a registration record in the registry). If the identifier does not exist, it is determined to be the first run; if it exists, it is determined to be a non-first run. Example: When the device starts the SDK for the first time, there is no "SDK_REGISTERED" file in the local " / data / voip / " path, so it is determined to be the first run.

[0075] On first run, the target token is extracted and the registration function is called: If it is the first run, the target token sn_ticket (e.g., "ticket_voiptest1_123456") is extracted from the target parameter set, and the wx_device_register function of the device SDK is called, passing sn_ticket in the form of "wx_device_register("ticket_voiptest1_123456")", to initiate a device registration request to the WeChat backend. If the wx_device_register function returns a successful registration (e.g., callback status code 200), an SDK_REGISTERED identifier file is created locally on the device. At this time, the basic configuration of wx_init and the device registration together complete the complete SDK initialization. If the registration fails (e.g., an invalid sn_ticket returns a 400 error), a valid sn_ticket needs to be obtained again. If a valid sn_ticket "ticket_voiptest1_123456" is passed, the registration is successful and the identifier file is generated, and the SDK can enter the subsequent call process.

[0076] Optionally, in some embodiments of this application, the step "initializing the call software development kit of the IoT platform according to the target token and the device registration function" may specifically include:

[0077] The target token is transmitted to the device registration function to adjust the device registration function;

[0078] Based on the adjusted device registration function, a device registration request is triggered to the corresponding third-party platform on the device side;

[0079] Upon receiving a registration success message from a third-party platform, the initialization of the IoT platform's call software development kit is completed.

[0080] The device registration function refers to a dedicated function in the IoT platform communication software development kit (device-side SDK) used to register the device identity with a specified platform. Specifically, it can be the wx_device_register function. Its core function is to associate device information with a security token, complete the legitimate identity authentication of the device on the third-party platform, and lay the foundation for subsequent SDK initialization and communication.

[0081] Third-party platforms are the core support platforms for devices to complete registration, obtain communication permissions, and transmit subsequent call signaling / code streams (such as the WeChat platform). Devices need to be authenticated by the platform before they can make calls with target programs (such as mini programs).

[0082] For example, specifically, the target token (i.e., sn_ticket, such as the security token obtained from the file by requesting the device SN and model_id) is extracted from the target parameter set. The sn_ticket is then passed as an input parameter to the device registration function wx_device_register. This parameter passing completes the function configuration adjustment, enabling the function to possess the identity credentials to initiate registration with the third-party platform. Then, the wx_device_register function, with the passed sn_ticket, is called. This function sends a device registration request to the third-party platform (WeChat backend), containing the sn_ticket and device association information (such as device SN and model_id), for the third-party platform to verify the device's legitimacy. The system waits for a response from the third-party platform. If a "registration successful" feedback message (such as a callback notification or status code) is received, it indicates that the device has completed legitimate identity registration on the third-party platform. At this point, combined with the basic configuration completed in the previous wx_init function, the complete initialization of the IoT platform call software development kit (SDK) is achieved, and the SDK can proceed to the subsequent call process.

[0083] 103. Based on the target parameter set and the initialized call software development kit, trigger the communication request between the device and the IoT platform.

[0084] In this context, a communication request refers to a request initiated by the device to the IoT platform based on the initialized call SDK, used to establish a call link. Its core purpose is to request audio and video interaction permissions with the target object (such as a WeChat mini-program user). This includes the transmission of call commands, authentication information, and communication identifiers, and is a prerequisite action for real-time calls. The device refers to the hardware device equipped with the IoT platform's call SDK (device-side SDK), which must support audio and video capture and transmission capabilities, such as smart home devices with voice functionality and remote monitoring devices. It is the entity initiating the communication request and must complete SDK initialization and device registration before it can trigger a communication request.

[0085] For example, specifically, the necessary parameters for triggering the communication request are filtered from the target parameter set, including the user's unique identifier (openid) and the identification information required by the audio / video cloud backend (payload, the content of which is agreed upon by the vendor and the cloud server backend). Simultaneously, it is confirmed that the previously initialized call SDK (device-side SDK) is functioning correctly, ensuring that the parameters match the SDK configuration. In the device-side code, the communication request triggering function provided by the initialized call SDK (such as the wx_cloudvoip_client_call function) is called. The extracted openid (such as the user identifier obtained through the WeChat mini-program wx.login()) and payload are passed to this function as input parameters. The function encapsulates the request data and prepares to initiate a call to the IoT platform. Through the called wx_cloudvoip_client_call function, a communication request is sent to the IoT platform. The request includes the device's identity information (already verified through previous registration), the target user's openid, and the payload. The system waits for the platform's response. If a "call request accepted" feedback is received (such as receiving a room_id notification for subsequent room joining), it indicates that the communication request was successfully triggered, and the channel establishment and audio / video stream transmission stages can proceed.

[0086] Optionally, in some embodiments of this application, the step "triggering a communication request between the device and the IoT platform based on the target parameter set and the initialized call software development kit" may specifically include:

[0087] Extract the communication parameters that triggered the communication request from the target parameter set;

[0088] Call the call function in the call software tool development kit;

[0089] Based on the communication parameters and call function, a communication request is triggered between the device and the IoT platform.

[0090] Communication parameters refer to the core parameters extracted from the target parameter set used to trigger communication requests between the device and the IoT platform. Examples include openid (a unique WeChat user identifier used to specify the target user for the call) and payload (agreed upon by the manufacturer and the cloud server backend to associate the audio and video stream channels between the device and the cloud server). These two parameters are essential data for initiating a communication request. Call functions refer to dedicated functions in the IoT platform's call software development kit (device-side SDK) used to initiate call requests, such as the wx_cloudvoip_client_call function. Its function is to receive communication parameters, encapsulate them into a compliant request, and initiate a call to the IoT platform. It is the core functional entry point for triggering communication requests.

[0091] For example, the necessary communication parameters for triggering the communication request, such as openid and payload, are filtered from the target parameter set. Specifically, the user's openid is obtained by executing the wx.login() method in the WeChat Mini Program environment (user authorization needs to be completed in advance), ensuring that the openid corresponds to the WeChat user who needs to make the call. The payload content (such as the channel identifier between the device and the cloud server) is defined according to the agreement between the manufacturer and the cloud server backend. This parameter will be transmitted to the cloud server along with the communication request for subsequent audio and video stream matching. Then, the call function in the call software development kit is called: confirming that the device-side call SDK has completed initialization (through the wx_init function) and device registration (through the wx_device_register function on the first run), the built-in call function wx_cloudvoip_client_call in the device-side code is called, and the extracted openid and payload are passed to the function as input parameters to complete the function call configuration. Finally, after calling the wx_cloudvoip_client_call function, the function will encapsulate the openid, payload, and device identity information (which has passed the previous registration verification) into a communication request and send it to the IoT platform (the core of which is the WeChat VoIP backend). If the request meets the platform's verification rules (such as the device identity being legitimate and the openid being valid), the communication request will be successfully triggered, and the platform will send back relevant notifications (such as room_id information used to join a voice room later), laying the foundation for the establishment of a subsequent call channel.

[0092] Optionally, in some embodiments of this application, the step "triggering a communication request between the device and the IoT platform based on communication parameters and a call function" may specifically include:

[0093] The communication parameters are transmitted to the call function to adjust the call function;

[0094] Based on the adjusted call function, a communication request is triggered between the device and the IoT platform.

[0095] For example, in the device-side code, following the parameter requirements of the `wx_cloudvoip_client_call` function, the `openid` (such as the user identifier obtained through `wx.login()`) and `payload` (such as a custom device-cloud server channel identifier) ​​are directly passed as parameters to the function. Parameter binding completes the function configuration adjustment, clearly associating the target user with the audio / video stream. Next, the `wx_cloudvoip_client_call` function, with the passed `openid` and `payload`, is executed. The function encapsulates device identity information and communication parameters, initiating a communication request to the IoT platform. If the platform verifies the parameters and device identity are valid, it will accept the request and provide relevant notifications (such as adding room_id information for the voice room later), thus triggering the communication request.

[0096] 104. Configure the communication plugin and communication interface corresponding to the communication request.

[0097] Communication plugins refer to dedicated plugins used to support VoIP calling between WeChat mini programs and devices; communication interfaces refer to interfaces used to transmit call signaling, permission requests, and notifications, mainly including two types: one is the wx.requestDeviceVoIP() interface on the mini program side (used to obtain user permission for voice calls between devices), and the other is the HTTPS interface on the cloud (used to receive message callbacks from the WeChat Open Platform, such as incoming call notifications, call status changes, etc.), which are channels to ensure normal interaction of communication requests.

[0098] For example, declare and import the communication plugin in the configuration file (such as app.json) of the WeChat Mini Program project, and ensure that the plugin version matches the solution requirements; after the plugin is imported, initialize the plugin in the relevant page code on the Mini Program side, associate it with the Mini Program appid (you need to apply for Mini Program camera cloud access permission from WeChat in advance), so that the plugin has the basic ability to interact with the WeChat backend.

[0099] In the mini-program code, the wx.requestDeviceVoIP() interface is called to initiate a request for voice call permission between devices. The interface will return the user's authorization result. Only after the user's authorization is approved can the mini-program receive communication requests (such as incoming call notifications) initiated by the device, ensuring that the communication requests meet the user's wishes.

[0100] In the cloud service of the IoT platform, an HTTPS service is set up, and the interface address of this service is configured in the corresponding WeChat Open Platform mini-program backend to receive message callbacks sent by the WeChat Open Platform (such as incoming call notification push after the device initiates a communication request, call status synchronization, etc.); at the same time, ensure that the HTTPS service supports encrypted data transmission to ensure the security of the communication interface.

[0101] 105. Construct cloud services corresponding to the Internet of Things cloud platform.

[0102] Cloud services refer to the set of core cloud capabilities that support communication between devices and IoT platforms. They are mainly used to receive message callbacks from platforms (such as WeChat Open Platform), manage voice rooms, and forward audio and video streams. They are a key hub connecting devices, clients, and IoT platforms, ensuring the stable transmission of call signaling and media streams.

[0103] Taking WeChat Mini Programs as an example, specifically, an HTTPS service that complies with the requirements of the WeChat Open Platform (with a valid SSL certificate to ensure secure data transmission) needs to be deployed. This service needs to be configured with a specified interface path to receive message callbacks sent by the WeChat Open Platform, such as call notifications and call status change notifications after a communication request is initiated by the device. In the backend of the corresponding Mini Program on the WeChat Open Platform, the interface address of this HTTPS service is configured to complete the binding of the callback address between the WeChat side and the cloud service, ensuring that the WeChat Open Platform can accurately push relevant messages to the cloud service.

[0104] Obtain and integrate the server-side SDK provided by the IoT platform (such as the WeChat VoIP related server-side SDK), call the relevant SDK interfaces in the cloud service to realize the "room joining" capability - the server needs to pass in parameters such as appid, sn, model_id, server_token (extracted from the target parameter set), complete the identity verification with the WeChat VoIP backend, and then join the voice room to obtain room_id, providing a room carrier for audio and video interaction between the device and the WeChat client;

[0105] Based on the server-side SDK configuration of audio and video forwarding function, after the cloud service receives the audio and video stream transmitted from the device, it forwards the stream to the WeChat backend through the SDK interface, and then the backend pushes it to the corresponding WeChat client. At the same time, it receives the audio and video stream from the WeChat client and forwards it to the device, realizing a closed loop of media stream for real-time audio and video communication between the two parties.

[0106] Ensure that the cloud service can identify and parse the payload transmitted by the device, and associate the audio and video streams of the specific device through the payload to avoid stream matching errors; debug the communication link between the cloud service and the WeChat backend, verify the timeliness of HTTPS service receiving callbacks and the effectiveness of server-side SDK calls (such as room joining success rate, audio and video forwarding delay, etc.), and ensure that the overall function of the cloud service meets the real-time and stability requirements of the call.

[0107] 106. Based on communication plug-ins, communication interfaces, and cloud services, construct a communication channel between the device and the IoT platform so that the device can communicate with the IoT platform through the communication channel.

[0108] A communication channel refers to a dedicated link established between a device and an IoT platform, relying on communication plug-ins, communication interfaces, and cloud services, for transmitting call signaling (such as call requests and incoming call notifications) and audio and video streams. It is the physical and logical connection carrier for realizing real-time communication between the two parties and must ensure the security, real-time performance, and stability of data transmission.

[0109] For example, the mini-program obtains user call permissions through the configured VoIP communication plugin (refer to the WeChat VoIP plugin documentation for integration) and the wx.requestDeviceVoIP() communication interface, ensuring that the mini-program has the ability to receive communication requests and process incoming call notifications, providing a user-side foundation for channel establishment. On the device side, based on the initialized call SDK (via the wx_init function), it confirms that the basic network connection with the IoT platform is normal and that device registration has been completed (via the wx_device_register function on first run), fulfilling the device-side prerequisite for initiating a communication request. The device calls the wx_cloudvoip_client_call function to initiate a communication request, carrying the openid (target user identifier) ​​and payload (device-cloud channel identifier), which is transmitted over the network to the IoT platform's cloud service.

[0110] The cloud service receives device communication request signaling forwarded by the WeChat Open Platform via an HTTPS communication interface. It then identifies the corresponding device audio and video stream channels based on the payload and simultaneously calls the server-side SDK to forward the signaling to the WeChat VoIP backend. The backend then pushes an incoming call notification to the target WeChat Mini Program (triggered by a communication plugin), completing the bidirectional connection of the signaling link. After the WeChat Mini Program user confirms answering the call via the communication plugin, the WeChat backend generates a room_id and sends it back to the cloud service. The cloud service then calls the SDK to join the voice room and simultaneously synchronizes the room_id to the device via the HTTPS interface.

[0111] The device connects to the voice room based on room_id and transmits audio and video streams to the cloud service through the established network link. The cloud service uses the server SDK to forward the audio and video streams (to the WeChat backend, and then pushes them to the mini program). At the same time, it receives the audio and video streams from the mini program and forwards them to the device.

[0112] Optionally, in some embodiments of this application, the step "building a communication channel between the device and the IoT platform based on communication plug-ins, communication interfaces, and cloud services, so that the device can communicate with the IoT platform through the communication channel" may specifically include:

[0113] Determine the program that communicates with the device.

[0114] Initialize the corresponding communication plugins and communication interfaces on the program side;

[0115] Parse the communication interface to obtain the corresponding communication identifier on the program side;

[0116] Based on the communication identifier, the initialized program and cloud services, a communication channel is built between the device and the IoT platform so that the device can communicate with the IoT platform through the communication channel.

[0117] For example, the application communicating with the device is a WeChat Mini Program. This application needs to support inter-device calling functionality and serves as the user-side carrier for receiving communication requests from the device (such as incoming call notifications) and enabling real-time audio and video interaction with the device. It must have completed the application for Mini Program camera cloud access capability in advance. Specifically, declare and import the communication plugin in the WeChat Mini Program project configuration file, associate it with the Mini Program appid that has applied for permissions, and complete the basic plugin initialization. In the Mini Program code, call the wx.requestDeviceVoIP() communication interface to initiate an inter-device voice call permission request, obtain the user authorization result, and ensure that the interface has the ability to transmit call permission-related signaling. Parse the communication interface to obtain the corresponding communication identifier for the application: call the Mini Program's wx.login() method, and obtain the user's unique identifier openid (application-side communication identifier) ​​through the interface callback triggered by this method. This identifier is used to uniquely associate with the target WeChat user and is the core basis for the device to initiate targeted communication requests. The device calls the `wx_cloudvoip_client_call` function, passing in the program-side communication identifier `openid` and the payload (device-cloud channel identifier) ​​to initiate a communication request to the cloud service. The cloud service receives the request signaling forwarded by the WeChat Open Platform through the HTTPS interface, matches the device's audio and video stream channels with the payload, and simultaneously calls the server-side SDK to forward the signaling to the WeChat VoIP backend. The backend then pushes an incoming call notification to the mini-program (which has its communication plugin initialized). After the user answers the call on the mini-program, the WeChat backend generates a `room_id` and synchronizes it to the cloud service and the device. The device and the mini-program access the voice room based on the `room_id`, and the cloud service completes the audio and video stream forwarding through the SDK, ultimately building a communication channel of "device-cloud service-WeChat backend-mini-program".

[0118] Optionally, in some embodiments of this application, the step "constructing a communication channel between the device and the IoT platform based on the communication identifier, the initialized program, and the cloud service, so that the device can communicate with the IoT platform through the communication channel" may specifically include:

[0119] Determine the voice space corresponding to the communication identifier;

[0120] Configure the multimedia stream forwarding strategy corresponding to the voice control based on cloud services;

[0121] Based on the voice space, multimedia stream forwarding strategy, and cloud services, a communication channel is constructed between the device and the IoT platform so that the device can communicate with the IoT platform through the communication channel.

[0122] Multimedia stream forwarding strategy refers to the rules for the transmission and distribution of audio and video streams between the device and the IoT platform, which are based on cloud services and server-side SDKs. The core is to use the server-side SDK to complete the bidirectional forwarding of audio and video streams from the device, cloud services, WeChat VoIP backend to WeChat client and vice versa. At the same time, the payload identifier is used to match the corresponding device stream channel to ensure the accuracy and real-time performance of audio and video transmission.

[0123] The communication identifiers include the openid (WeChat user identifier) ​​used when the device initiates a communication request and the room_id (voice room identifier) ​​received by the cloud service. When the device calls the wx_cloudvoip_client_call function and passes in the openid to initiate a call, the WeChat VoIP backend will target the WeChat client based on the openid, create a dedicated voice space, and generate a unique room_id. The cloud service receives the room_id forwarded by the WeChat Open Platform through the HTTPS interface, associates it with the payload of the device, and stores it to determine that the voice space corresponding to the room_id is the voice interaction space that the current device needs to access. Next, the server-side SDK is integrated into the cloud service, which can configure the voice room joining strategy: the server passes in parameters such as appid, sn, model_id, and server_token (extracted from the target parameter set), calls the SDK interface to join the voice space corresponding to room_id, and obtains audio and video stream forwarding permissions; then, the cloud service identifies the audio and video streams transmitted by the device through the payload, forwards them to the WeChat VoIP backend through the server-side SDK, and then pushes them to the WeChat client in the voice space; at the same time, it receives the audio and video streams from the WeChat client and forwards them to the corresponding device according to the same strategy, forming a two-way stream forwarding closed loop. Next, the device connects to the corresponding voice space based on the room_id using the initialized SDK (initialized by the wx_init function and registered by the wx_device_register function on the first run), and begins transmitting audio and video streams to the cloud service. The cloud service forwards the device's audio and video streams to the WeChat VoIP backend according to the configured multimedia stream forwarding strategy. The backend then pushes the streams to the WeChat client in the voice space. At the same time, the WeChat client's audio and video streams are forwarded back to the device, thus establishing a communication channel to support real-time communication between the two parties.

[0124] The communication method for an IoT platform provided in this application involves obtaining the target parameter set required for communication on the IoT platform, initializing the IoT platform's call software development kit (SDK) based on the target parameter set, triggering a communication request between the device and the IoT platform based on the target parameter set and the initialized SSD, configuring the communication plugin and communication interface corresponding to the communication request, and constructing the cloud service corresponding to the IoT cloud platform. Finally, based on the communication plugin, communication interface, and cloud service, a communication channel between the device and the IoT platform is constructed so that the device can communicate with the IoT platform through the communication channel. In the communication solution of the IoT platform provided in this application, different devices can connect based on a target parameter set, eliminating the need to define separate parameter systems for different devices and reducing repetitive adaptation work. Furthermore, based on the target parameter set and the initialized communication software development kit, communication requests between the device and the IoT platform are triggered, eliminating the need to develop separate device-side communication modules and significantly reducing connection costs. In addition, device authentication is performed using cloud services to avoid the risk of data leakage during transmission. Moreover, there is no need to build independent transcoding and signaling servers; room joining and audio / video forwarding can be completed by calling the software development kit. Therefore, this solution can reduce the communication costs and operational threshold of the IoT platform, while improving the communication compatibility of the IoT platform.

[0125] To facilitate better implementation of the communication method of the IoT platform according to the embodiments of this application, the embodiments of this application also provide a communication device for the IoT platform. The meanings of the terms used are the same as in the communication system of the IoT platform described above, and specific implementation details can be found in the description of the system embodiments.

[0126] Please see Figure 2 , Figure 2 This is a schematic diagram of the structure of a communication device for an IoT platform provided in an embodiment of this application. Specifically, the communication device may include an acquisition module 201, an initialization module 202, a triggering module 203, a configuration module 204, a construction module 205, and a communication module 206, as follows:

[0127] The acquisition module 201 is used to acquire the target parameter set required for communication on the IoT platform;

[0128] Initialization module 202 is used to initialize the communication software development kit of the IoT platform according to the target parameter set;

[0129] Trigger module 203 is used to trigger a communication request between the device and the IoT platform based on the target parameter set and the initialized call software development kit;

[0130] Configuration module 204 is used to configure the communication plugin and communication interface corresponding to the communication request;

[0131] Module 205 is used to build cloud services corresponding to the Internet of Things cloud platform;

[0132] The communication module 206 is used to construct a communication channel between the device and the IoT platform based on the communication plug-in, communication interface and cloud service, so that the device can communicate with the IoT platform through the communication channel.

[0133] Optionally, in some embodiments of this application, the initialization module 202 may specifically include:

[0134] The first calling unit is used to call the initialization function corresponding to the call software development kit of the IoT platform and pass in the target parameter set;

[0135] The judgment unit is used to determine whether the device is running the call software development kit for the first time.

[0136] The first extraction unit is used to extract the target token from the target parameter set and call the corresponding device registration function on the device side when the device runs the call software development kit for the first time.

[0137] An initialization unit is used to initialize the call software development kit of the Internet of Things platform according to the target token and the device registration function.

[0138] Optionally, in some embodiments of this application, the initialization unit is specifically used for:

[0139] The target token is transmitted to the device registration function to adjust the device registration function;

[0140] Based on the adjusted device registration function, a device registration request is triggered to the third-party platform corresponding to the device.

[0141] Upon receiving a registration success message from the third-party platform, the initialization of the call software development kit for the IoT platform is completed.

[0142] Optionally, in some embodiments of this application, the trigger module 203 may specifically include:

[0143] The second extraction unit is used to extract the communication parameters that trigger the communication request from the target parameter set;

[0144] The second calling unit is used to call the call function in the call software tool development kit;

[0145] The triggering unit is used to trigger a communication request between the device and the IoT platform based on the communication parameters and the call function.

[0146] Optionally, in some embodiments of this application, the triggering unit may specifically be used for:

[0147] The communication parameters are transmitted to the call function to adjust the call function;

[0148] Based on the adjusted call function, a communication request is triggered between the device and the IoT platform.

[0149] Optionally, in some embodiments of this application, the communication module 206 may specifically be used for:

[0150] Determine the program terminal that communicates with the device.

[0151] Initialize the communication plugin and communication interface corresponding to the program terminal;

[0152] Parse the communication interface to obtain the communication identifier corresponding to the program end;

[0153] Based on the communication identifier, the initialized program and cloud services, a communication channel is constructed between the device and the IoT platform so that the device can communicate with the IoT platform through the communication channel.

[0154] Optionally, in some embodiments of this application, the communication module 206 may specifically be used for:

[0155] Determine the voice space corresponding to the communication identifier;

[0156] Configure the multimedia stream forwarding strategy corresponding to the voice control based on cloud services;

[0157] Based on the aforementioned voice space, multimedia stream forwarding strategy, and cloud services, a communication channel is constructed between the device and the IoT platform, so that the device can communicate with the IoT platform through the communication channel.

[0158] This application provides a communication device for an Internet of Things (IoT) platform. After the acquisition module 201 acquires the target parameter set required for communication on the IoT platform, the initialization module 202 initializes the IoT platform's call software development kit (SDK) according to the target parameter set. Then, the triggering module 203 triggers a communication request between the device and the IoT platform according to the target parameter set and the initialized SSD. Next, the configuration module 204 configures the communication plugin and communication interface corresponding to the communication request. The construction module 205 constructs the cloud service corresponding to the IoT cloud platform. Finally, the communication module 206 constructs a communication channel between the device and the IoT platform based on the communication plugin, communication interface, and cloud service, so that the device can communicate with the IoT platform through the communication channel. In the communication solution of the IoT platform provided in this application, different devices can connect based on a target parameter set, eliminating the need to define separate parameter systems for different devices and reducing repetitive adaptation work. Furthermore, based on the target parameter set and the initialized communication software development kit, communication requests between the device and the IoT platform are triggered, eliminating the need to develop separate device-side communication modules and significantly reducing connection costs. In addition, device authentication is performed using cloud services to avoid the risk of data leakage during transmission. Moreover, there is no need to build independent transcoding and signaling servers; room joining and audio / video forwarding can be completed by calling the software development kit. Therefore, this solution can reduce the communication costs and operational threshold of the IoT platform, while improving the communication compatibility of the IoT platform.

[0159] Furthermore, embodiments of this application also provide an electronic device, such as... Figure 3 As shown, it illustrates a structural schematic diagram of the electronic device involved in the embodiments of this application, specifically:

[0160] The electronic device may include components such as a processor 301 with one or more processing cores, a memory 302 with one or more processor-readable storage media, a power supply 303, and an input unit 304. Those skilled in the art will understand that... Figure 3 The electronic device structure shown does not constitute a limitation on the electronic device and may include more or fewer components than shown, or combine certain components, or have different component arrangements. Wherein:

[0161] The processor 301 is the control center of the electronic device. It connects various parts of the electronic device via various interfaces and lines. By running or executing software programs and / or modules stored in the memory 302, and by calling data stored in the memory 302, it performs various functions and processes data, thereby providing overall monitoring of the electronic device. Optionally, the processor 301 may include one or more processing cores; preferably, the processor 301 may integrate an application processor and a modem processor, wherein the application processor mainly handles the operating system, user interface, and applications, and the modem processor mainly handles wireless communication. It is understood that the modem processor may not be integrated into the processor 301.

[0162] The memory 302 can be used to store software programs and modules. The processor 301 executes various functional applications and communication methods of the Internet of Things (IoT) platform by running the software programs and modules stored in the memory 302. The memory 302 may mainly include a program storage area and a data storage area. The program storage area may store the operating system, at least one application program required for a function (such as sound playback function, image playback function, etc.), etc.; the data storage area may store data created according to the use of the electronic device, etc. In addition, the memory 302 may include high-speed random access memory, and may also include non-volatile memory, such as at least one disk storage device, flash memory device, or other volatile solid-state storage device. Accordingly, the memory 302 may also include a memory controller to provide the processor 301 with access to the memory 302.

[0163] The electronic device also includes a power supply 303 that supplies power to various components. Preferably, the power supply 303 can be logically connected to the processor 301 through a power management system, thereby enabling functions such as charging, discharging, and power consumption management through the power management system. The power supply 303 may also include one or more DC or AC power supplies, recharging systems, power fault detection circuits, power converters or inverters, power status indicators, and other arbitrary components.

[0164] The electronic device may also include an input unit 304, which can be used to receive input digital or character information and generate keyboard, mouse, joystick, optical or trackball signal inputs related to user settings and function control.

[0165] Although not shown, the electronic device may also include a display unit, etc., which will not be described in detail here. Specifically, in this embodiment, the processor 301 in the electronic device loads the executable files corresponding to the processes of one or more applications into the memory 302 according to the following instructions, and the processor 301 runs the applications stored in the memory 302 to realize various functions, as follows:

[0166] The system acquires the target parameter set required for communication with the IoT platform; initializes the IoT platform's communication software development kit (SDK) based on the target parameter set; triggers a communication request between the device and the IoT platform based on the target parameter set and the initialized SSD; configures the communication plugin and communication interface corresponding to the communication request; constructs the cloud service corresponding to the IoT cloud platform; and constructs a communication channel between the device and the IoT platform based on the communication plugin, communication interface, and cloud service, so that the device can communicate with the IoT platform through the communication channel.

[0167] For details on the implementation of each of the above operations, please refer to the previous examples, which will not be repeated here.

[0168] In this embodiment, after obtaining the target parameter set required for communication with the IoT platform, the communication software development kit (SDK) of the IoT platform is initialized based on the target parameter set. Then, based on the target parameter set and the initialized SSD, a communication request between the device and the IoT platform is triggered. Next, the communication plugin and communication interface corresponding to the communication request are configured, and the cloud service corresponding to the IoT cloud platform is constructed. Finally, based on the communication plugin, communication interface, and cloud service, a communication channel between the device and the IoT platform is constructed so that the device can communicate with the IoT platform through the communication channel. In the communication solution of the IoT platform provided in this application, different devices can connect based on a target parameter set, eliminating the need to define separate parameter systems for different devices and reducing repetitive adaptation work. Furthermore, based on the target parameter set and the initialized communication software development kit, communication requests between the device and the IoT platform are triggered, eliminating the need to develop separate device-side communication modules and significantly reducing connection costs. In addition, device authentication is performed using cloud services to avoid the risk of data leakage during transmission. Moreover, there is no need to build independent transcoding and signaling servers; room joining and audio / video forwarding can be completed by calling the software development kit. Therefore, this solution can reduce the communication costs and operational threshold of the IoT platform, while improving the communication compatibility of the IoT platform.

[0169] Those skilled in the art will understand that all or part of the steps in the various methods of the above embodiments can be performed by instructions, or by instructions controlling related hardware. These instructions can be stored in a processor-readable storage medium and loaded and executed by a processor.

[0170] Therefore, embodiments of this application provide a storage medium storing multiple instructions that can be loaded by a processor to execute steps in the communication method of any IoT platform provided in embodiments of this application. For example, the instructions can execute the following steps:

[0171] The system acquires the target parameter set required for communication with the IoT platform; initializes the IoT platform's communication software development kit (SDK) based on the target parameter set; triggers a communication request between the device and the IoT platform based on the target parameter set and the initialized SSD; configures the communication plugin and communication interface corresponding to the communication request; constructs the cloud service corresponding to the IoT cloud platform; and constructs a communication channel between the device and the IoT platform based on the communication plugin, communication interface, and cloud service, so that the device can communicate with the IoT platform through the communication channel.

[0172] For details on the implementation of each of the above operations, please refer to the previous examples, which will not be repeated here.

[0173] The storage medium may include: read-only memory (ROM), random access memory (RAM), disk or optical disk, etc.

[0174] Since the instructions stored in the storage medium can execute the steps in the communication method of any IoT platform provided in the embodiments of this application, the beneficial effects that the communication method of any IoT platform provided in the embodiments of this application can achieve can be realized. For details, please refer to the previous embodiments, which will not be repeated here.

[0175] The communication method, apparatus, electronic device, and storage medium of an Internet of Things platform provided in the embodiments of this application have been described in detail above. Specific examples have been used to illustrate the principles and implementation methods of this application. The description of the above embodiments is only for the purpose of helping to understand the method and core ideas of this application. At the same time, for those skilled in the art, there will be changes in the specific implementation methods and application scope based on the ideas of this application. Therefore, the content of this specification should not be construed as a limitation of this application.

Claims

1. A communication method for an Internet of Things (IoT) platform, characterized in that, include: Obtain the target parameter set required for communication on the IoT platform; The communication software development kit of the IoT platform is initialized according to the target parameter set; Based on the target parameter set and the initialized call software development kit, a communication request is triggered between the device and the IoT platform; Configure the communication plugin and communication interface corresponding to the communication request; Construct cloud services corresponding to the aforementioned IoT cloud platform; Based on the aforementioned communication plugin, communication interface, and cloud service, a communication channel is constructed between the device and the IoT platform, enabling the device to communicate with the IoT platform through the communication channel.

2. The communication method according to claim 1, characterized in that, The initialization of the call software development kit (SDK) of the IoT platform based on the target parameter set includes: The initialization function corresponding to the call software development kit of the IoT platform is called, and the target parameter set is passed in. Determine if the device is running the call software development kit for the first time; If the device is running the call software development kit for the first time, the target token is extracted from the target parameter set, and the corresponding device registration function of the device is called. The call software development kit of the IoT platform is initialized based on the target token and the device registration function.

3. The communication method according to claim 2, characterized in that, The initialization of the call software development kit (SDK) of the IoT platform based on the target token and the device registration function includes: The target token is transmitted to the device registration function to adjust the device registration function; Based on the adjusted device registration function, a device registration request is triggered to the third-party platform corresponding to the device. Upon receiving a registration success message from the third-party platform, the initialization of the call software development kit for the IoT platform is completed.

4. The communication method according to claim 1, characterized in that, The step of triggering a communication request between the device and the IoT platform based on the target parameter set and the initialized call software development kit includes: Extract the communication parameters that trigger the communication request from the target parameter set; Call the call function in the aforementioned call software tool development kit; Based on the communication parameters and the call function, a communication request is triggered between the device and the IoT platform.

5. The communication method according to claim 4, characterized in that, The step of triggering a communication request between the device and the IoT platform based on the communication parameters and the call function includes: The communication parameters are transmitted to the call function to adjust the call function; Based on the adjusted call function, a communication request is triggered between the device and the IoT platform.

6. The communication method according to claim 1, characterized in that, The construction of a communication channel between the device and the IoT platform based on the communication plugin, communication interface, and cloud service, so that the device can communicate with the IoT platform through the communication channel, includes: Determine the program terminal that communicates with the device. Initialize the communication plugin and communication interface corresponding to the program terminal; Parse the communication interface to obtain the communication identifier corresponding to the program end; Based on the communication identifier, the initialized program and cloud services, a communication channel is constructed between the device and the IoT platform so that the device can communicate with the IoT platform through the communication channel.

7. The communication method according to claim 6, characterized in that, The step of constructing a communication channel between the device and the IoT platform based on the communication identifier, the initialized program terminal, and the cloud service, so that the device can communicate with the IoT platform through the communication channel, includes: Determine the voice space corresponding to the communication identifier; Configure the multimedia stream forwarding strategy corresponding to the voice control based on cloud services; Based on the aforementioned voice space, multimedia stream forwarding strategy, and cloud services, a communication channel is constructed between the device and the IoT platform, so that the device can communicate with the IoT platform through the communication channel.

8. A communication device for an Internet of Things (IoT) platform, characterized in that, include: The acquisition module is used to acquire the target parameter set required for communication on the IoT platform; An initialization module is used to initialize the call software development kit of the IoT platform according to the target parameter set; The triggering module is used to trigger a communication request between the device and the IoT platform based on the target parameter set and the initialized call software development kit. The configuration module is used to configure the communication plugin and communication interface corresponding to the communication request; The building module is used to build the cloud services corresponding to the IoT cloud platform; A communication module is used to construct a communication channel between the device and the IoT platform based on the communication plug-in, communication interface and cloud service, so that the device can communicate with the IoT platform through the communication channel.

9. An electronic device, characterized in that, include: A memory, a processor, and a processor program stored in the memory and executable on the processor, wherein the processor executes the program as steps of a communication method of an Internet of Things platform as claimed in any one of claims 1 to 7.

10. A storage medium, characterized in that, A computer processing program is stored that can be loaded by a processor and execute the communication method of the Internet of Things platform as described in any one of claims 1 to 7.

Images