Conference room deployment method, node, Internet of Things equipment and system

Abstract

The embodiment of the invention provides a conference room deployment method, a node, an Internet of Things device and a system, and relates to the technical field of cloud. The method comprises the steps that conference information sent by a cloud node is received, the conference information comprises address information of a target conference room, and a target edge node is an edge node closest to the target conference room; determining a first Internet of Things device deployed in the target conference room from the Internet of Things devices connected with the target edge node; and sending a control instruction related to the conference information to the first Internet of Things equipment according to a predetermined transmission protocol of the first Internet of Things equipment. According to the embodiment of the invention, the problems of relatively large load and long response time delay of the cloud node are avoided, the link length sent by the control instruction deployed in the conference room is reduced on the whole, the transmission efficiency is improved, and the experience feeling of conference deployers and participants can be improved.

Description

Technical Field

[0001] The present application relates to the field of cloud technology. Specifically, the present application relates to a conference room deployment method, node, Internet of Things device and system. Background Art

[0002] With the development of the Internet of Things and cloud computing, in office building scenarios, some IoT devices are usually deployed in conference rooms, so that the deployment of conference rooms can be achieved by remotely controlling the IoT devices through cloud nodes.

[0003] However, on the one hand, when the cloud node needs to manage many office locations, the burden on the cloud node will be very high. Excessive load during peak hours may lead to increased response delays. If the cloud node fails abnormally, it will affect all locations in the entire network. On the other hand, as the business expands, the cloud node has to manage office buildings all over the country and even the world. The network links for the interaction between these IoT devices and the cloud nodes will be very long, and the network time consumption will greatly affect the user experience and availability of the system. Summary of the invention

[0004] The embodiments of the present application provide a conference room deployment method, edge node, cloud node and deployment system, which can solve the above problems of the prior art. The technical solution is as follows:

[0005] In a first aspect, an embodiment of the present application provides a conference room deployment method, which is applied to a target edge node in an edge node cluster, and the method includes:

[0006] Receiving conference information sent by a cloud node, wherein the conference information includes address information of a target conference room, and the target edge node is an edge node closest to the target conference room;

[0007] Determine, from among the IoT devices connected to the target edge node, a first IoT device deployed in the target conference room;

[0008] According to a transmission protocol predetermined with the first IoT device, a control instruction related to the conference information is sent to the first IoT device.

[0009] In a second aspect, an embodiment of the present application provides a conference room deployment method, which is applied to a cloud node, and the method includes:

[0010] Determine conference information, wherein the conference information includes address information of a target conference room;

[0011] Determine an edge node closest to the target conference room from the edge node cluster as the target edge node;

[0012] The conference information is sent to the target edge node.

[0013] In a third aspect, an embodiment of the present application provides a conference room deployment method, which is applied to an Internet of Things device, and the method includes:

[0014] Receiving a control instruction related to the conference information sent by the target edge node based on a transmission protocol predetermined by the IoT device;

[0015] Wherein, the conference information includes the address information of the target conference room;

[0016] The target edge node is the edge node closest to the target conference room;

[0017] The Internet of Things device is an Internet of Things device deployed in the target conference room.

[0018] In a fourth aspect, an embodiment of the present application provides a conference room deployment system, including:

[0019] An edge node cluster, wherein the edge node cluster includes edge nodes that execute the deployment method provided in the first aspect above;

[0020] A cloud node for executing the deployment method provided in the second aspect above;

[0021] An Internet of Things device cluster, wherein the Internet of Things device cluster includes Internet of Things devices that implement the third aspect.

[0022] In a fifth aspect, an embodiment of the present application provides a target edge node in an edge node cluster, including:

[0023] A receiving module, configured to receive conference information sent by a cloud node, wherein the conference information includes address information of a target conference room, and the target edge node is an edge node closest to the target conference room;

[0024] A determination module, configured to determine a first IoT device deployed in the target conference room from among the IoT devices connected to the target edge node;

[0025] A sending module is used to send a control instruction related to the conference information to the first Internet of Things device according to a transmission protocol predetermined with the first Internet of Things device.

[0026] In a sixth aspect, an embodiment of the present application provides a cloud node, including:

[0027] A determination module, used to determine conference information, wherein the conference information includes address information of a target conference room;

[0028] The determination module is further used to determine the edge node closest to the target conference room from the edge node cluster as the target edge node;

[0029] The sending module is used to send the conference information to the target edge node.

[0030] In a seventh aspect, an embodiment of the present application provides an Internet of Things device, including:

[0031] A receiving module, configured to receive a control instruction related to conference information sent by a target edge node based on a transmission protocol predetermined by the IoT device;

[0032] Wherein, the conference information includes the address information of the target conference room;

[0033] The target edge node is the edge node closest to the target conference room;

[0034] The Internet of Things device is an Internet of Things device deployed in the target conference room.

[0035] In an eighth aspect, an embodiment of the present application provides an electronic device, comprising a memory, a processor, and a computer program stored in the memory, wherein the processor executes the computer program to implement the steps of the method provided in the first, second or third aspect above.

[0036] In a ninth aspect, an embodiment of the present application provides a computer-readable storage medium having a computer program stored thereon, and when the computer program is executed by a processor, the steps of the method provided in the first, second or third aspect are implemented.

[0037] In a tenth aspect, an embodiment of the present application provides a computer program product, including a computer program, which implements the steps of the method provided in the first, second or third aspect when the computer program is executed by a processor.

[0038] The beneficial effects of the technical solution provided by the embodiment of the present application are:

[0039] An edge node is added between the cloud node and the IoT device. Each edge node is used to manage nearby IoT devices. The IoT device only needs to focus on obtaining meeting information and forwarding the meeting information to the edge node closest to the target conference room, avoiding the problem of heavy cloud node load and large response delay. The control of the conference room is all carried out at the edge node. The transmission node sends control instructions to the first IoT device based on the transmission protocol predetermined with the first IoT device, which reduces the link length of the control instructions sent by the conference room deployment as a whole, improves the transmission efficiency, and can improve the experience of the conference deployer and participants. BRIEF DESCRIPTION OF THE DRAWINGS

[0040] Figure 1a A schematic diagram of the architecture of a serverless computing platform provided in an embodiment of the present application;

[0041] Figure 1b A schematic diagram of the system architecture of a conference room deployment scenario provided in an embodiment of the present application;

[0042] Figure 2a A schematic diagram of the conference room deployment system architecture provided for an embodiment of the present application;

[0043] Figure 2b A schematic diagram of a method for deploying a conference room provided in an embodiment of the present application;

[0044] Figure 2c A schematic diagram of a WEB page for conference deployment provided in an embodiment of the present application;

[0045] Figure 2d A schematic diagram of interaction in a scenario of booking a conference room provided in an embodiment of the present application;

[0046] Figure 3 An interactive schematic diagram of releasing a conference provided in an embodiment of the present application;

[0047] Figure 4 A schematic diagram of the architecture of a conference room deployment system provided for another embodiment of the present application;

[0048] Figure 5 A schematic diagram showing a comparison of resource consumption in a day when the same reporting cycle is not used and when the same reporting cycle is used, provided in an embodiment of the present application;

[0049] Figure 6 An interactive schematic diagram of IoT device management provided in an embodiment of the present application;

[0050] Figure 7 A flow chart of a method for deploying a conference room applied to a cloud node provided in an embodiment of the present application;

[0051] Figure 8 A schematic diagram of a process for deploying a conference room for an Internet of Things device provided in an embodiment of the present application;

[0052] Figure 9a A schematic diagram of the structure of a conference room deployment system provided in an embodiment of the present application;

[0053] Figure 9b An interactive schematic diagram of a specific application scenario provided in an embodiment of the present application;

[0054] Fig.10 A schematic diagram of the structure of a target edge node in an edge node cluster provided in an embodiment of the present application;

[0055] Fig.11 A schematic diagram of the structure of a cloud node provided in an embodiment of the present application;

[0056] Fig.12 A schematic diagram of the structure of an Internet of Things device provided in an embodiment of the present application;

[0057] Fig.13 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0058] The embodiments of the present application are described below in conjunction with the drawings in the present application. It should be understood that the implementation methods described below in conjunction with the drawings are exemplary descriptions for explaining the technical solutions of the embodiments of the present application and do not constitute a limitation on the technical solutions of the embodiments of the present application.

[0059] It will be understood by those skilled in the art that, unless specifically stated, the singular forms "one", "an" and "the" used herein may also include plural forms. It should be further understood that the terms "including" and "comprising" used in the embodiments of the present application refer to that the corresponding features can be implemented as the presented features, information, data, steps, operations, elements and / or components, but do not exclude the implementation as other features, information, data, steps, operations, elements, components and / or combinations thereof supported by the technical field. It should be understood that when we call an element "connected" or "coupled" to another element, the one element can be directly connected or coupled to the other element, or it can refer to that the one element and the other element establish a connection relationship through an intermediate element. In addition, the "connection" or "coupling" used here may include wireless connection or wireless coupling. The term "and / or" used here indicates at least one of the items defined by the term, for example, "A and / or B" can be implemented as "A", or as "B", or as "A and B".

[0060] In order to make the objectives, technical solutions and advantages of the present application clearer, the implementation methods of the present application will be further described in detail below with reference to the accompanying drawings.

[0061] First, several terms involved in this application are introduced and explained:

[0062] Serverless computing platform: also known as Serverless, refers to the concept of building and running applications that do not require server management. The serverless computing platform automates the entire process of establishing, deploying, and starting services on demand. Developers only need to register various required business functions and their resource requirements. The serverless computing platform is also a complete process for building and managing a microservice-based architecture. It differs from traditional architecture in that it is triggered by events and exists in stateless, temporary computing containers. Building serverless functions means that developers can focus on product code without having to manage and operate cloud or local servers or runtimes. The serverless computing platform truly deploys applications without involving infrastructure construction, and automatically builds, deploys, and starts services.

[0063] like Figure 1a As shown in the figure, the serverless computing platform consists of two parts: function as a service FaaS and background as a service BaaS.

[0064] Function as a Service (FaaS): Each function is a service. Functions can be written in any language. Apart from that, there is no need to worry about any operation and maintenance details, such as computing resources, elastic expansion, and can be billed by volume, and support event-driven. Backend and service, that is, many middleware technologies are integrated, and services can be called regardless of the environment, such as data as a service (database service), cache service, etc. Optionally, function as a service (FaaS) can be a cloud function. Cloud functions can run logic processing code without purchasing and managing servers. You only need to use the language to write the core code and set the conditions for the code to run, and you can run the code safely on the serverless computing platform, and you can associate events generated by cloud infrastructure and other cloud services, where cloud functions are triggered by events. Cloud functions provide an application programming interface (API), through which cloud functions can be called, and cloud gateways can be used to manage cloud functions.

[0065] The cloud gateway is a management tool in the serverless computing platform, which is used to manage all application program interfaces (APIs) corresponding to cloud functions, such as grouping and managing APIs by environment. Based on the cloud gateway, the front end can send requests to the cloud gateway, and the gateway will trigger the specific cloud function to execute the request logic. In the embodiments of the present application, the cloud gateway and cloud functions are described as a serverless computing platform.

[0066] Cloud technology is a general term for network technology, information technology, integration technology, management platform technology, application technology, etc. based on the cloud computing business model. It can form a resource pool, which can be used on demand and is flexible and convenient. Cloud computing technology will become an important support. The backend services of the technical network system require a large amount of computing and storage resources, such as video websites, picture websites and more portal websites. With the rapid development and application of the Internet industry, in the future, each item may have its own identification mark, which needs to be transmitted to the backend system for logical processing. Data of different levels will be processed separately. All kinds of industry data need strong system backing support, which can only be achieved through cloud computing.

[0067] Cloud storage is a new concept that extends and develops from the concept of cloud computing. A distributed cloud storage system (hereinafter referred to as storage system) refers to a storage system that uses cluster applications, grid technology, and distributed storage file systems to bring together a large number of different types of storage devices (storage devices are also called storage nodes) in the network through application software or application interfaces to work together and provide external data storage and business access functions.

[0068] In short, a database can be seen as an electronic filing cabinet - a place where electronic files are stored, and users can add, query, update, delete, and other operations on the data in the files. The so-called "database" is a collection of data that is stored together in a certain way, can be shared with multiple users, has as little redundancy as possible, and is independent of the application.

[0069] The conference room deployment method, edge node, cloud node, deployment system, electronic device, computer-readable storage medium and computer program product provided in this application are intended to solve the above technical problems of the prior art.

[0070] The following describes several exemplary embodiments to illustrate the technical solutions of the embodiments of the present application and the technical effects produced by the technical solutions of the present application. It should be noted that the following embodiments can refer to, draw on or combine with each other, and the same terms, similar features and similar implementation steps in different embodiments will not be described repeatedly.

[0071] Figure 1b A system architecture diagram of a conference room deployment scenario provided for an embodiment of the present application, as shown in the figure, when the conference deployer wants to deploy a conference room, the conference reservation information is configured through the front-end WEB page provided by the cloud node. Generally, the conference information includes the address information of the target conference room to be enabled, which is processed by the cloud node and the target edge node to ultimately control the operation of the IoT device deployed in the target conference room, thereby completing the reservation of the conference room.

[0072] The cloud node of the embodiment of the present application is a global controller, which is deployed in the cloud, and the edge node is a regional controller, and an edge node is used to manage IoT devices in the corresponding geographical area. A geographical area generally belongs to an edge node, and the embodiment of the present application does not limit the scope of the geographical area, for example, it can be an office building, an office park, a city, a province or even multiple provinces (for example, the central China region may include Henan Province, Hubei Province and Hunan Province).

[0073] In the related technology, the cloud node is directly connected to each IoT device. Since there are many types of IoT devices and they are produced by different manufacturers with different transmission protocols, in order to send control instructions to IoT devices, it is necessary to adapt these devices and convert the instructions into protocol content that the IoT devices can understand. Each new IoT device may introduce changes and upgrades.

[0074] The cloud node of this application does not interact directly with the IoT device, but is replaced by the edge node. This can effectively shield the differences in the transmission methods of IoT devices on the edge node side. The addition of IoT devices or the modification of device-side protocols does not require cloud upgrades, only changes on the edge side, minimizing the impact on the entire system. In addition, in the new solution, the management of equipment deployed in each office is also handed over to the edge node. The cloud node only sends meeting information to the edge node. The cloud node does not need to know which equipment is in the conference room. All inquiries, conversions, and transmissions are performed at the edge node. Overall, the link length for sending meeting information is reduced, and transmission efficiency is improved.

[0075] The cloud node of the embodiment of the present application no longer needs to connect to the IoT device, perform protocols, convert and send messages, etc. It only needs to forward the meeting reservation information to the edge node closest to the conference room, and the edge node queries the IoT device deployed in the conference room to distribute control instructions.

[0076] Figure 2a This is a schematic diagram of the conference room deployment system architecture provided in an embodiment of the present application. The system may include a terminal 101 and a first server 102.

[0077] Data can be transmitted between the first server 102 and the terminal 101 via a target protocol link, which may include a link based on a transport layer protocol, such as a Transmission Control Protocol (TCP) link or a User Datagram Protocol (UDP) link transmission and other transport layer protocols.

[0078] The first server 102 can be an independent physical server, or a server cluster or distributed system composed of multiple physical servers. It can also be a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, CDN, as well as big data and artificial intelligence platforms.

[0079] In one implementation of an embodiment of the present application, the first server 102 is a cloud server, and the first server can provide artificial intelligence cloud services, such as artificial intelligence cloud services that provide account security services (MMORPG). The so-called artificial intelligence cloud service is generally also referred to as AIaaS (AI as a Service, Chinese for "AI as a Service"). This is a mainstream service mode of an artificial intelligence platform. Specifically, the AIaaS platform will split several common AI services and provide independent or packaged services in the cloud. This service model is similar to opening an AI theme mall: all developers can access and use one or more artificial intelligence services provided by the platform through an API interface. Some senior developers can also use the AI ​​framework and AI infrastructure provided by the platform to deploy and operate their own cloud artificial intelligence services. For example, the first server can provide a network business creation service.

[0080] The terminal 101 may be any device. In one implementation of the embodiment of the present application, the terminal 101 is a terminal having a client program that can deploy a conference room.

[0081] In an embodiment of the present application, a conference room deployment method is provided, which is applied to a target edge node in an edge node cluster. The edge node cluster in the embodiment of the present application includes multiple edge nodes, each of which is used to manage IoT devices within a certain geographical range, which can be an office building, an office park, a city, etc. Figure 2b As shown, the method includes:

[0082] S2101. Receive conference information sent by a cloud node, where the conference information includes address information of a target conference room, and the target edge node is an edge node closest to the target conference room.

[0083] The conference information of the embodiment of the present application refers to information used to indicate the reservation, suspension or termination of a conference. The conference information includes the address information of the target conference room to be scheduled, suspended or terminated. The address information may include the longitude and latitude coordinates of the office building where the conference room is located, the floor where the conference room is located, the room number, etc.

[0084] The cloud node of the embodiment of the present application can provide a front-end page for developers to deploy conferences, such as Figure 2c As shown, it exemplarily shows a schematic diagram of a WEB page for conference deployment in an embodiment of the present application. As shown in the figure, the conference organizer logs in to the WEB page and can browse to the interface for booking a meeting displayed on the web page. In the interface, the conference organizer needs to set the meeting start time, meeting duration, meeting location, meeting files, etc.

[0085] In the embodiment of the present application, the cloud node does not directly send the meeting information to the IoT device, but sends the meeting information to the edge node closest to the target conference room, that is, the target edge node. In this way, the differences in the transmission methods of IoT devices can be effectively shielded on the edge node side. The addition of new devices or the modification of transmission protocols do not need to be upgraded on the cloud node, but only need to be changed on the edge node, which minimizes the impact on the entire system. In addition, in the new solution, the management of equipment deployed in each office location is also handed over to the edge service. The cloud node only sends meeting information to the edge node. The cloud node does not need to know which equipment is in the conference room. All inquiries, conversions, and transmissions are performed at the edge node. Overall, the link length for sending meeting information is reduced and the transmission efficiency is improved.

[0086] S2102: Determine a first Internet of Things device deployed in the target conference room from among the Internet of Things devices connected to the target edge node.

[0087] The target edge node is used to manage the connected IoT devices within a geographical range.

[0088] In some embodiments, the target edge node can record the IoT device information of each conference room in the form of a key-value pair. For example, the key of a key-value pair is 20F2308, and the value includes light2387aircon116mon7492TV8423. The key records the address information of the conference room: Room 2308 in the office building 20F. The value includes 4 IoT devices: a lighting device numbered 2387, a temperature and humidity control device numbered 116, a detection device numbered 7492, and a display device numbered 8423. It can be understood that each IoT device has a unique number to avoid confusion. The number can also be a combination of numbers, letters, punctuation marks, etc., which is not specifically limited in the embodiments of the present application.

[0089] The temperature and humidity regulating equipment in the embodiments of the present application may include an air conditioner, a heater, a humidifier, etc., and the embodiments of the present application do not make specific limitations.

[0090] The display device of the embodiment of the present application may include a television, a projector, a display screen, etc.

[0091] In some embodiments, the target edge node can record the device information of each IoT device in the form of a table. Please refer to Table 1, which exemplarily shows the device information table of the IoT device in the embodiment of the present application. As shown in the table, the table records the number of each IoT device, the conference room where it is located, the device type, the transmission protocol between the edge node, etc. It can be seen that the embodiment of the present application has different transmission protocols for different devices, and because the transmission protocol is updated, the latest version number will also be recorded when recording the transmission protocol. For example, 1.2v in Table 1 represents the 1.2v version of the corresponding transmission protocol. The target edge node can determine the IoT device to be controlled and the transmission protocol to be used based on the device information table.

[0092] Equipment No. Meeting Room Number Device Type Transport Protocol 1511 12G2111 illumination Protocol 1 1.2v 4512 12G2111 illumination Protocol 2.3a Df12 12G3111 Temperature and humidity control Protocol 3.1a 1zx4 12G2111 show Protocol III 4.1.1b

[0093] Table 1. Device information table of IoT devices

[0094] S2103: Send a control instruction related to the conference information to the first Internet of Things device according to a transmission protocol predetermined with the first Internet of Things device.

[0095] In the embodiment of the present application, the edge node determines and saves the transmission protocol with the IoT device, and sinks the instruction transmission to the edge node closer to the IoT device, which can reduce network time consumption.

[0096] In the embodiment of the present application, after determining the first IoT device deployed in the target conference room, the target edge node sends a control instruction related to the conference information to the first IoT device based on a predetermined transmission protocol with the first IoT device. If the conference information is a scheduled target conference room, the control instruction may be to start running at the meeting start time or a certain time before the meeting start time. If the conference information is to end the meeting, the control instruction may be to end running at the meeting end time or a certain time before the meeting end time. For example, if a certain conference information is scheduled to start a meeting at 2 pm on a certain day, the target edge node can instruct the lighting equipment and the temperature and humidity control equipment to start running 3 minutes in advance, and another conference information is scheduled to end the meeting at 3 pm on a certain day, the target edge node can instruct the temperature and humidity control equipment to stop running 5 minutes in advance, and so on.

[0097] See also Figure 2d, which exemplarily shows an interactive schematic diagram of an embodiment of the present application in the scenario of booking a conference room. As shown in the figure, first, the conference deployer books a conference room through the front-end WEB interface provided by the cloud node. The cloud node sends the conference information of the reserved conference room to the target edge node closest to the target conference room. The target edge node determines the first Internet of Things device deployed in the target conference room. The first Internet of Things device in the embodiment of the present application includes three types, namely, detection equipment, display equipment and energy consumption equipment. Among them, the detection equipment is used to collect environmental information in the conference room - such as real-time pictures of the conference room, etc., the display device is used to display information, and the energy consumption equipment is used to provide energy - such as lighting, temperature control, etc.

[0098] The control instructions sent by the target edge node of the embodiment of the present application to the display device may include files related to the meeting, so that they are displayed by the display device. The control instructions sent by the target edge node to the energy-consuming device may include the temperature range, humidity range, lighting brightness, etc. of the meeting room. The control instructions sent by the target edge node to the detection device may include the detection cycle, etc.

[0099] The embodiment of the present application adds an edge node between the cloud node and the IoT device. Each edge node is used to manage nearby IoT devices. The IoT device only needs to focus on obtaining meeting information and forwarding the meeting information to the edge node closest to the target conference room, avoiding the problem of heavy cloud node load and large response delay. The control of the conference room is all carried out at the edge node. The transmission node sends control instructions to the first IoT device based on the transmission protocol predetermined with the first IoT device, which reduces the link length of the control instructions sent by the conference room deployment as a whole, improves the transmission efficiency, and can improve the experience of the conference deployer and participants.

[0100] Based on the above embodiments, as an optional embodiment, the control instruction includes: instruction information for instructing to collect environmental information of the target conference room.

[0101] The step of sending a control instruction related to the conference information to the first IoT device further includes:

[0102] Receiving the environment information of the target conference room sent by the first Internet of Things device;

[0103] The occupancy status of the target conference room is determined according to the environmental information.

[0104] For the scenario of a scheduled meeting, the embodiment of the present application further receives the environmental information of the target conference room sent by the first IoT device after sending a control instruction to the first IoT device (in some embodiments, the first IoT device may only collect environmental information after a certain period of time after the start time of the meeting). In some embodiments, the control instruction may indicate the environmental information that the first IoT device needs to collect and the upload cycle. For example, the target edge node may instruct the first IoT device to collect information on the number of people in the conference room through a control instruction, and upload it with a 5-minute upload cycle.

[0105] In some embodiments, the environmental information may include the number of people. For example, the first IoT device collects real-time images of the conference room, and the target edge node identifies the number of people in the conference room through technologies such as face recognition or object recognition.

[0106] In some embodiments, in order to improve the privacy protection of the participants, the environmental information of the embodiment of the present application may include the carbon dioxide concentration of the conference room, and the number of people in the conference room is determined by the pre-established functional relationship between the carbon dioxide concentration and the number of people. Specifically, the Internet of Things device of the embodiment of the present application may include a carbon dioxide gas concentration detector, and carbon dioxide gas concentration detectors are set around the room and on the roof of each conference room. The carbon dioxide gas concentration detectors collected by the carbon dioxide gas concentration detectors at various locations are weighted and averaged to be used as the carbon dioxide concentration of the entire conference room.

[0107] In some embodiments, the environmental information may also include volume level. The target edge node determines whether the target conference room is occupied by someone by judging whether the volume of the target conference room exceeds a preset volume threshold.

[0108] The occupancy status of the target conference room in the embodiment of the present application, that is, whether there are still participants in the target conference room, can reflect whether the meeting in the target conference room is in progress. The embodiment of the present application determines that the occupancy status of the target conference room is unoccupied based on the environmental information, that is, no participants are located in the target conference room, and then stops running the first Internet of Things device. Specifically, when the embodiment of the present application determines that the occupancy status of the target conference room is unoccupied, a stop operation instruction can be sent to the first Internet of Things device through a transmission protocol with the first Internet of Things device, thereby realizing automatic release of the meeting without human control.

[0109] See also Figure 3, which exemplarily shows a flow chart of releasing a meeting in an embodiment of the present application, the edge node instructs the detection device to collect environmental information in the conference room at preset time intervals (for example, 30 seconds), the detection device reports the environmental information to the edge node, the edge node determines whether the conference room is occupied based on the environmental information, if it is determined that the conference room is not occupied, the edge node sends an alarm message to the cloud node, the cloud node displays the alarm message to the conference deployer for verification, the edge node also informs the cloud node of the prompt message of releasing the meeting, and sends a control instruction of releasing the meeting to the Internet of Things device in the conference room, Figure 3 In the example, the IoT devices include detection devices, display devices and energy consumption devices. The IoT devices send control instructions to the display devices to close or modify the displayed meeting information, send control instructions to the energy consumption devices to turn off the lights and air conditioners, and send control instructions to the detection devices to stop collecting environmental information.

[0110] In related technologies, edge nodes need to independently process data reported by the Internet of Things using a data processing service. The data processing service also needs to provide an API for parameter configuration, such as the period for IoT devices to report environmental information, the time required for continuous detection of non-occupancy, and so on.

[0111] With the development of cloud technology, the allocation of computing resources has become more and more abstract. Please refer to Table 2, which exemplarily shows the allocation method table of computing resources in the embodiment of the present application. Table 2 lists a total of 4 allocation methods. The first allocation method is to allocate computing resources through physical servers. The first allocation method uses physical machines as expansion units, and users completely own the entire physical computing resources; the second allocation method is to allocate computing resources through cloud virtual machines, with cloud servers as expansion units, and virtualized hardware devices. Users and other tenants share physical machine resources, and can still configure the various indicators of CVM by themselves, which is relatively simpler to deploy and iterate; the third allocation method is to allocate computing resources through container servers, with services as expansion units, virtualized operating systems, and completely consistent test and production environments, making testing and deployment very easy; the fourth allocation method is to allocate computing resources through a serverless computing platform, with functions as expansion units, and virtualized runtime environments (Runtime). It is the smallest unit of existing computing resources, with the characteristics of full automation, one-click deployment, and high scalability.

[0112] Physical Server Taking physical machines as expansion units Cloud Virtual Machines Using cloud servers as expansion units Container Services Service-based expansion unit Serverless computing platform Function as the expansion unit

[0113] Table 2 Allocation of computing resources

[0114] Serverless does not mean that there are no servers. Instead, when using Serverless, developers do not need to worry about the underlying resources, log in to the server, or optimize the server. They only need to focus on the core code snippets and skip the complex and tedious basic work. The core code snippets are completely triggered by events or requests, and the serverless computing platform automatically adjusts service resources in parallel according to the request. Serverless has nearly unlimited expansion capabilities, and no resources are running when idle. The code runs statelessly, which can easily achieve rapid iteration and extremely fast deployment.

[0115] The embodiment of the present application found that this event-triggered, on-demand resource scheduling method is very suitable for edge-deployed data analysis services, and the target edge node of the embodiment of the present application runs a server-free computing platform. In this way, the data analysis service can be simplified into a data analysis function, which is triggered by the message event subscribed by the message queue for processing, that is, the server-free computing platform of the embodiment of the present application maintains the message queue.

[0116] After the operation and maintenance personnel configure parameters such as the detection cycle and non-occupancy time (which can be stored in the database or Redis cache), each data analysis function instance is stateless and can be started and destroyed at any time.

[0117] The serverless computing platform creates a function instance of a target serverless function in response to the presence of unprocessed environmental information in the message queue, wherein the target serverless function is used to determine the occupancy of the conference room according to the environmental information;

[0118] The occupancy status of the target conference room is determined according to the function instance of the target no-service function and the unprocessed environmental information.

[0119] See also Figure 4 , which exemplarily shows an architectural diagram of a conference room deployment system of another embodiment of the present application. As shown in the figure, the edge node of the embodiment of the present application includes a service-free computing platform. The edge node replaces the data analysis service with a data analysis function, that is, the target service-free function, which is directly dispatched by the service-free computing platform. The target service-free function is triggered by a message queue, that is, when there is environmental information in the message queue, a function instance of the target service-free function is created, and the unprocessed environmental information is brought into the function instance to obtain the occupancy status of the target conference room.

[0120] Based on the above embodiments, as an optional implementation, the serverless computing platform deletes the created function instance in response to the absence of unprocessed environment information in the message queue. The serverless computing platform of the embodiment of the present application automatically scales up and down according to the load of the target serverless function, and when there is no message, all function instances will be destroyed.

[0121] Since daytime on weekdays is the peak period for IoT devices, the function instances in the embodiments of the present application will automatically expand in capacity, and on non-working days or at night, the function instances will automatically lock. At the same time, the creation and destruction of function instances are much faster than traditional distributed services, which can maximize flexible expansion and reduce resource consumption.

[0122] In the embodiment of the present application, all IoT devices within the management scope of an edge node are configured to have the same reporting cycle, such as reporting every hour. Then the target serverless function deployed on the serverless computing platform will only be pulled up when a message from the message queue is received every hour. During other idle time, the serverless platform will recycle its resources, thereby achieving more regular expansion and contraction of function instances, which is also more conducive to resource consumption.

[0123] See also Figure 5 , which exemplarily shows a schematic diagram of the comparison of resource consumption in a day when the same reporting cycle is not adopted and when the same reporting cycle is adopted. On the one hand, the reservation and release of conference rooms are random, and on the other hand, there are more conference room reservations during the day and fewer at night. As shown in the figure, when the same reporting cycle is not adopted, since IoT devices report environmental information to the message queue in each time period, the serviceless function is always triggered, and the number of function instances is always at a high level, and gradually decreases at night. When the same reporting cycle is adopted, the IoT devices of all open conference rooms will report environmental information at the same time, so the function instances show periodic expansion and contraction, and the resulting resource consumption also obviously shows periodic changes, and is not at a high level for a long time.

[0124] Based on the above embodiments, as an optional embodiment, the embodiment of the present application also includes:

[0125] The target edge node performs status detection on each connected IoT device;

[0126] Determine that a second Internet of Things device exists, and send a status of the second Internet of Things device to the cloud node so that the cloud node displays the status of the second Internet of Things device;

[0127] Among them, the second Internet of Things device is an Internet of Things device whose status switches from normal to abnormal or from abnormal to normal.

[0128] The edge node of the embodiment of the present application will perform status detection on the managed IoT devices.

[0129] There are two ways to detect the status:

[0130] 1. The IoT device actively and periodically reports heartbeat messages, which are received by the edge node. If the edge node can periodically receive the heartbeat messages reported by the IoT device, the status of the IoT device is determined to be normal; if the heartbeat message is not received for more than a time threshold (for example, 3 minutes), or if the heartbeat message is not received for multiple consecutive periods, the status of the IoT device is determined to be abnormal.

[0131] 2. The edge node periodically queries the status of the IoT device. This method requires the IoT device to support the edge node status query interface. If the query is successful, the status of the IoT device is determined to be normal. If the query fails for multiple consecutive times (for example, 3 times), the status of the IoT device is determined to be abnormal.

[0132] It should be noted that no matter which state detection method is adopted, the state detection of the embodiment of the present application is closed-loop on the edge node side, without the need to interact with the cloud node. Only when the second IoT device is determined, the edge node notifies the cloud node, and then the cloud node forwards it to the IoT device deployment personnel for the IoT device deployment personnel to perform corresponding operations. The second IoT device in the embodiment of the present application refers to an IoT device whose state switches from normal to abnormal or from abnormal to normal. That is, if the state determined by an IoT device during this state detection has not changed compared to the state determined during the previous state detection, the cloud node will not be notified.

[0133] Based on the above embodiments, as an optional embodiment, it also includes:

[0134] The target edge node receives the device addition information sent by the cloud node, wherein the device addition information includes the device information of the third IoT device to be connected, and the target edge node is the edge node closest to the third IoT device;

[0135] According to the device information of the third Internet of Things device, a connection with the third Internet of Things device is established, and the third Internet of Things device is determined to be the Internet of Things device connected to the target edge node.

[0136] In some embodiments, when the edge node records the device information of the IoT device in the form of a data table, it can also record the relevant information of the state detection method of the IoT device. Please refer to Table 3, which exemplarily shows the state detection method record table of the embodiment of the present application. The table lists the device information of three IoT devices, including device number, connection method, device IP address, detection method and location, respectively. The connection method refers to the connection method between the IoT device and the edge node. The connection method is divided into active connection and passive connection. Active connection means that the IoT device will actively connect based on the connection protocol supported by the edge node, while passive connection means that the edge node connects to the IoT device based on the IP address of the IoT device. For active connection, the edge node does not need to record the IP address of the IoT device. Further, for actively connected IoT devices, the IoT device will actively send a heartbeat message to the edge node for the edge node to perform state detection. For passively connected IoT devices, the edge node needs to query the IoT device for the state, and the IoT device returns the response information. The location recorded in Table 3 is the location of the conference room where the IoT device is located. This information can be represented by the conference room number of the conference room.

[0137] Equipment No. Connection Device IP address Detection method Location Djf23 Active connection null Heartbeat message Meeting Room 23300 23901 Passive connection 123.456.123 Accept inquiries Meeting Room 22051 B4895 Active connection 123.456.789 Accept inquiries Meeting Room 12051

[0138] Table 3 Status detection mode record table

[0139] In some embodiments, when the connection mode of the IoT device is passive connection, the edge node connection may fail because the device may not have been deployed or is not online. At this time, the edge node is also required to record the connection status of each IoT device. If the connection fails, the time of connection failure and the number of connection attempts are recorded, and the connection is re-established every preset time period.

[0140] Based on the above embodiments, as an optional embodiment, the state detection of each IoT device connected to the target edge node includes at least one of the following:

[0141] For a connected IoT device, receiving a status feedback message sent by the IoT device based on the second preset period within a preset period, and determining that the status of the IoT device is normal;

[0142] For a connected Internet of Things device, if a status feedback message sent by the Internet of Things device based on a second preset period is not received within the preset period, it is determined that the status of the Internet of Things device is abnormal.

[0143] It can be seen from the above embodiments that the status feedback message may refer to a heartbeat message actively sent by an IoT device, or may refer to a response message returned by the IoT device after receiving status query information sent by an edge node.

[0144] See also Figure 6 , which exemplarily shows an interactive schematic diagram of IoT device management in an embodiment of the present application. As shown in the figure, the IoT device deployer fills in the device information of the third IoT device to be connected to the network through the front-end page provided by the cloud node. The device information records the location, connection method, IP address, device number and other information of the third IoT device. The cloud node sends device addition information to the target edge node based on the filled-in device information. The device addition information includes the device information of the third IoT device to be connected to the network. The edge node saves the device information. For actively connected IoT devices, the edge node waits for the IoT device to actively connect to the edge node. For passively connected IoT devices, the edge node connects to the IoT device based on the IP address of the IoT device.

[0145] The edge node needs to perform status monitoring on the connected IoT devices. For actively connected IoT devices, the IoT devices will periodically report heartbeat messages. If the edge node can periodically receive heartbeat information, the IoT device status is determined to be normal. If the edge node cannot periodically receive heartbeat information, the IoT device status is determined to be abnormal. For passively connected IoT devices, the edge node periodically sends status query information to the IoT device. If the IoT device can periodically return a query response, the IoT device status is determined to be normal. If the edge node cannot periodically receive a query response, the IoT device status is determined to be abnormal.

[0146] The edge node determines the second IoT device according to the status of each connected IoT device. The second IoT device is an IoT device whose status switches from normal to abnormal or from abnormal to normal. The edge node sends an alarm message to the cloud node. The alarm message includes the device information of the second IoT device, such as the address of the device, the device number, etc. The cloud node displays the alarm message to the IoT device deployer through the front-end WEB page.

[0147] See also Figure 7 , which exemplarily shows a flow chart of a method for deploying a conference room of a cloud node according to an embodiment of the present application. As shown in the figure, the method includes:

[0148] S7101. Determine conference information, where the conference information includes address information of a target conference room;

[0149] S7102: Determine an edge node closest to the target conference room from an edge node cluster as a target edge node;

[0150] S7103. Send the conference information to the target edge node.

[0151] The cloud node of the embodiment of the present application can provide a front-end WEB page to the meeting deployer. The meeting deployer edits the meeting information on the WEB page, such as the meeting location, meeting time, PPTs involved in the meeting, etc. After the meeting deployer completes the editing, the cloud node obtains the meeting information, and then determines the edge node closest to the target meeting room, that is, the target edge node, based on the location / management scope of each edge node in the edge cluster, and then sends the meeting information to the target edge node.

[0152] The cloud node of the embodiment of the present application no longer needs to directly connect to various IoT devices to perform protocol and message conversion. It only needs to forward the meeting information to the edge node to which the conference room belongs. The edge node queries the IoT devices deployed in the conference room and distributes control instructions. This reduces the link length for sending control instructions for conference deployment as a whole and improves transmission efficiency.

[0153] Based on the above embodiments, as an optional embodiment, the deployment method on the cloud node side also includes:

[0154] Send device addition information to the target edge node;

[0155] The device addition information includes device information of a third IoT device to be connected, and the target edge node is an edge node closest to the third IoT device.

[0156] The IoT device deployer edits the device information of the third IoT device to be connected, such as the IP address, location, transmission protocol, etc. of the IoT device, through the front-end WEB interface provided by the cloud node. In response to the completion of editing the device information of the IoT device, the cloud node queries the nearest edge node according to the location of the third IoT device to be connected, and sends the device information of the third IoT device to the nearest edge node, so that the edge node can connect to and manage the third IoT device.

[0157] Based on the above embodiments, as an optional embodiment, the deployment method on the cloud node side also includes:

[0158] Receive the status and device information of the second IoT device sent by the edge node;

[0159] Display the status and device information of the second IoT device

[0160] Among them, the second Internet of Things device is an Internet of Things device whose status switches from normal to abnormal or from abnormal to normal.

[0161] The cloud node of the embodiment of the present application only receives the status and device information of the second IoT device sent by the edge node. The second IoT device refers to an IoT device whose status switches from normal to abnormal or from abnormal to normal. That is, only when an IoT device switches its status, the cloud node will know and display it to the IoT device deployer, so that the IoT device deployer can know the IoT device that needs to be processed.

[0162] See also Figure 8 , which exemplarily shows a flow chart of a method for deploying a conference room of an Internet of Things device according to an embodiment of the present application, as shown in the figure, including:

[0163] S8101, receiving a control instruction related to conference information sent by a target edge node based on a transmission protocol predetermined by the IoT device;

[0164] Wherein, the conference information includes the address information of the target conference room;

[0165] The target edge node is the edge node closest to the target conference room;

[0166] The Internet of Things device is an Internet of Things device deployed in the target conference room.

[0167] The IoT device in the embodiment of the present application is not directly connected to the cloud node, but to the edge node. Each edge node is used to connect to IoT devices within a certain range. The IoT device does not need to know the transmission protocol with each IoT device. It only needs to send the meeting information to the edge node closest to the conference room. The edge node then determines the IoT devices deployed in the conference room and the transmission protocols of these IoT devices, and sends control instructions to the IoT devices based on the corresponding transmission protocols, which reduces the length of the network link and the network time consumption and improves the transmission efficiency.

[0168] Based on the above embodiments, as an optional embodiment, the deployment method executed by the IoT device side further includes:

[0169] A status feedback message is sent to the target edge node based on a preset period, so that the target edge node determines the status of the Internet of Things device.

[0170] The edge node will perform status detection on the connected IoT devices to ensure that the IoT devices in the conference room can operate normally when the conference room is in use. The IoT device of the embodiment of the present application will periodically send status feedback messages to the target edge node so that the target edge node can determine the status of the IoT device.

[0171] It can be seen from the above embodiments that when the IoT device is passively connected, the IoT device first receives the status query information sent by the edge node based on a preset period, and then returns the response information to the edge node. When the IoT device is actively connected, the IoT device sends a heartbeat message to the edge node based on a preset period.

[0172] The present application embodiment provides a conference room deployment system, such as Figure 9a As shown, including:

[0173] An edge node cluster 901, wherein the edge node cluster includes an edge node 9011 that executes the deployment method executed by the edge node side;

[0174] A cloud node 902 for executing the deployment method executed by the cloud node side;

[0175] An IoT device cluster 903, wherein the IoT device cluster includes an IoT device 9031 that executes the above-mentioned IoT device-side execution.

[0176] See also Figure 9b , which exemplarily shows an interaction diagram of a specific application scenario provided by an embodiment of the present application. This scenario involves an IoT device deployer, a conference deployer, a cloud node, an edge node cluster, and an IoT device cluster.

[0177] The IoT device deployer edits the device information of the IoT device X to be connected through the front-end WEB page provided by the cloud node: the address of the conference room: Room C, Floor B, Building A, device type: energy-consuming device, connection mode: active connection, etc. Based on the device information of the IoT device X, the cloud node determines that the edge node D in the edge node cluster is the edge node closest to the conference room, so the cloud node sends the device information of the IoT device X to the edge node D.

[0178] The edge node D stores the device information of the IoT device X, is connected to the IoT device X, and periodically performs status detection on the IoT device X.

[0179] The conference deployer edits the conference information through the front-end WEB page provided by the cloud node, including the address of the conference room to be enabled: Room C, Floor B, Building A, and the meeting start time. The cloud node sends the conference information to the edge node D. The edge node D determines that there are two IoT devices in the conference room: IoT device X and IoT device Y, where the IoT device is a detection device. The edge node sends a control instruction 1 to the IoT device X to run 3 minutes before the meeting start time, and sends a control instruction 2 to the IoT device Y to periodically collect the environmental information of the conference room after the meeting room start time.

[0180] IoT device Y periodically collects environmental information of the conference room and reports it to edge node D. When edge node D determines that the conference room is not occupied, it sends a reminder message to the cloud node. The cloud node displays the reminder message to the conference deployer through the front-end WEB page for verification by the conference deployer. The edge node also instructs IoT device X and IoT device Y to stop running.

[0181] The embodiment of the present application also provides a target edge node in an edge node cluster, such as Fig.10 As shown, it includes: a receiving module 1001, a determining module 1002 and a sending module 1003, specifically:

[0182] The receiving module 1001 is used to receive the conference information sent by the cloud node, wherein the conference information includes the address information of the target conference room, and the target edge node is the edge node closest to the target conference room;

[0183] A determination module 1002 is used to determine a first IoT device deployed in the target conference room from among the IoT devices connected to the target edge node;

[0184] The sending module 1003 is used to send a control instruction related to the conference information to the first Internet of Things device according to a transmission protocol predetermined with the first Internet of Things device.

[0185] The device of the embodiment of the present application can execute the method on the target edge node side provided by the embodiment of the present application, and the implementation principle is similar. The actions performed by each module in the device of each embodiment of the present application correspond to the steps in the method of each embodiment of the present application. For the detailed functional description of each module of the device, please refer to the description in the corresponding method shown in the previous text, which will not be repeated here.

[0186] The present application also provides a cloud node, such as Fig.11 As shown, it includes a determination module 1101 and a sending module 1102. Specifically

[0187] A conference information determination module 1101 is used to determine conference information, wherein the conference information includes address information of a target conference room;

[0188] The edge node determination module 1101 is further configured to determine an edge node closest to the target conference room from the edge node cluster as a target edge node;

[0189] The conference information sending module 1102 is used to send the conference information to the target edge node.

[0190] The present application also provides an Internet of Things device, such as Fig.12As shown, it includes a receiving module 1201, which is used to receive a control instruction related to the conference information sent by the target edge node based on a transmission protocol predetermined by the Internet of Things device;

[0191] Wherein, the conference information includes the address information of the target conference room;

[0192] The target edge node is the edge node closest to the target conference room;

[0193] The Internet of Things device is an Internet of Things device deployed in the target conference room.

[0194] In an embodiment of the present application, an electronic device is provided, including a memory, a processor and a computer program stored in the memory, and the processor executes the above computer program to implement the steps of the conference room deployment method. Compared with the related art, it can achieve: adding edge nodes between cloud nodes and IoT devices, each edge node is used to manage nearby IoT devices, and IoT devices only need to focus on obtaining meeting information and forwarding the meeting information to the edge node closest to the target conference room, avoiding the problem of heavy cloud node load and long response delay. The control of the conference room is all carried out at the edge node, and the transmission node sends control instructions to the first IoT device based on the transmission protocol predetermined with the first IoT device, which reduces the link length of the control instructions sent by the conference room deployment as a whole, improves the transmission efficiency, and can improve the experience of the conference deployer and participants.

[0195] In an alternative embodiment, an electronic device is provided, such as Fig.13 As shown, Fig.13 The electronic device 4000 shown includes: a processor 4001 and a memory 4003. The processor 4001 and the memory 4003 are connected, such as through a bus 4002. Optionally, the electronic device 4000 may also include a transceiver 4004, which may be used for data interaction between the electronic device and other electronic devices, such as data transmission and / or data reception. It should be noted that in actual applications, the transceiver 4004 is not limited to one, and the structure of the electronic device 4000 does not constitute a limitation on the embodiments of the present application.

[0196] Processor 4001 may be a CPU (Central Processing Unit), a general-purpose processor, a DSP (Digital Signal Processor), an ASIC (Application Specific Integrated Circuit), an FPGA (Field Programmable Gate Array) or other programmable logic devices, transistor logic devices, hardware components or any combination thereof. It may implement or execute various exemplary logic blocks, modules and circuits described in conjunction with the disclosure of this application. Processor 4001 may also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of a DSP and a microprocessor, etc.

[0197] The bus 4002 may include a path to transmit information between the above components. The bus 4002 may be a PCI (Peripheral Component Interconnect) bus or an EISA (Extended Industry Standard Architecture) bus. The bus 4002 may be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Fig.13 Only one thick line is used in the diagram, but this does not mean that there is only one bus or only one type of bus.

[0198] The memory 4003 may be a ROM (Read Only Memory) or other types of static storage devices that can store static information and instructions, a RAM (Random Access Memory) or other types of dynamic storage devices that can store information and instructions, or an EEPROM (Electrically Erasable Programmable Read Only Memory), a CD-ROM (Compact Disc Read Only Memory) or other optical disk storage, optical disk storage (including compressed optical disk, laser disk, optical disk, digital versatile disk, Blu-ray disk, etc.), magnetic disk storage media, other magnetic storage devices, or any other medium that can be used to carry or store computer programs and can be read by a computer, without limitation herein.

[0199] The memory 4003 is used to store the computer program for executing the embodiment of the present application, and the execution is controlled by the processor 4001. The processor 4001 is used to execute the computer program stored in the memory 4003 to implement the steps shown in the above method embodiment.

[0200] An embodiment of the present application provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the steps and corresponding contents of the aforementioned method embodiment can be implemented.

[0201] The embodiment of the present application also provides a computer program product, including a computer program, which can implement the steps and corresponding contents of the aforementioned method embodiment when executed by a processor.

[0202] The terms "first", "second", "third", "fourth", "1", "2", etc. (if any) in the specification and claims of this application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the numbers used in this way can be interchanged where appropriate, so that the embodiments of the present application described herein can be implemented in an order other than that shown or described in the drawings.

[0203] It should be understood that, although each operation step is indicated by arrows in the flowchart of the embodiment of the present application, the implementation order of these steps is not limited to the order indicated by the arrows. Unless clearly stated herein, in some implementation scenarios of the embodiment of the present application, the implementation steps in each flowchart can be performed in other orders according to demand. In addition, some or all of the steps in each flowchart may include multiple sub-steps or multiple stages based on actual implementation scenarios. Some or all of these sub-steps or stages may be executed at the same time, and each sub-step or stage in these sub-steps or stages may also be executed at different times respectively. In different scenarios of execution time, the execution order of these sub-steps or stages may be flexibly configured according to demand, and the embodiment of the present application does not limit this.

[0204] The above is only an optional implementation method for some implementation scenarios of the present application. It should be pointed out that for ordinary technicians in this technical field, without departing from the technical concept of the solution of the present application, other similar implementation methods based on the technical ideas of the present application are also within the protection scope of the embodiments of the present application.

Claims

1. A conference room deployment method, characterized in that: Applied to a target edge node in an edge node cluster, the method comprises: Receiving conference information sent by a cloud node, wherein the conference information includes address information of a target conference room, and the target edge node is an edge node closest to the target conference room; Determine, from among the IoT devices connected to the target edge node, a first IoT device deployed in the target conference room; According to a transmission protocol predetermined with the first IoT device, a control instruction related to the conference information is sent to the first IoT device.

2. The method according to claim 1, characterized in that The control instruction includes: instruction information for instructing to collect environmental information of the target conference room; The step of sending a control instruction related to the conference information to the first IoT device further includes: Receiving the environment information of the target conference room sent by the first Internet of Things device; The occupancy status of the target conference room is determined according to the environmental information.

3. The method according to claim 2, characterized in that The target edge node runs a serverless computing platform, and the serverless computing platform maintains a message queue; The determining the occupancy status of the target conference room according to the environmental information includes: Inserting the received environment information as a message into the message queue; The serverless computing platform creates a function instance of a target serverless function in response to the presence of unprocessed environmental information in the message queue, wherein the target serverless function is used to determine the occupancy of the conference room according to the environmental information; The occupancy status of the target conference room is determined according to the function instance of the target no-service function and the unprocessed environmental information.

4. The method according to claim 3, characterized in that Also includes: In response to the absence of unprocessed environment information in the message queue, the serverless computing platform deletes the created function instance.

5. The method according to claim 2, characterized in that: Determining the occupancy status of the target conference room according to the environmental information includes: Determine, according to the environmental information, that the occupancy status of the target conference room is unoccupied, and stop running the first Internet of Things device.

6. The method according to claim 1, characterized in that Also includes: Perform status detection on each connected IoT device; Determine that a second IoT device exists, and send the status and device information of the second IoT device to the cloud node; Among them, the second Internet of Things device is an Internet of Things device whose status switches from normal to abnormal or from abnormal to normal.

7. The method according to claim 6, characterized in that The state detection of each connected IoT device includes at least one of the following: For a connected IoT device, receiving a status feedback message sent by the IoT device based on a preset period, and determining that the status of the IoT device is normal; For a connected IoT device, if a status feedback message sent by the IoT device based on a preset period is not received, it is determined that the status of the IoT device is abnormal.

8. The method according to claim 1, characterized in that Also includes: Receiving device addition information sent by the cloud node, wherein the device addition information includes device information of a third IoT device to be connected, and the target edge node is an edge node closest to the third IoT device; According to the device information of the third Internet of Things device, a connection with the third Internet of Things device is established, and the third Internet of Things device is determined to be the Internet of Things device connected to the target edge node.

9. A conference room deployment method, characterized in that: Applied to a cloud node, the method includes: Determine conference information, wherein the conference information includes address information of a target conference room; Determine an edge node closest to the target conference room from the edge node cluster as the target edge node; The conference information is sent to the target edge node.

10. The method according to claim 9, characterized in that Also includes: Send device addition information to the target edge node; The device addition information includes device information of a third IoT device to be connected, and the target edge node is an edge node closest to the third IoT device.

11. The method according to claim 9 or 10, characterized in that: Also includes: Receive the status and device information of the second IoT device sent by the edge node; Display the status and device information of the second IoT device Among them, the second Internet of Things device is an Internet of Things device whose status switches from normal to abnormal or from abnormal to normal.

12. A target edge node in an edge node cluster, characterized in that: include: A receiving module, configured to receive conference information sent by a cloud node, wherein the conference information includes address information of a target conference room, and the target edge node is an edge node closest to the target conference room; A determination module, configured to determine a first IoT device deployed in the target conference room from among the IoT devices connected to the target edge node; A sending module is used to send a control instruction related to the conference information to the first Internet of Things device according to a transmission protocol predetermined with the first Internet of Things device.

13. A cloud node, characterized in that: include: A determination module, used to determine conference information, wherein the conference information includes address information of a target conference room; The determination module is further used to determine the edge node closest to the target conference room from the edge node cluster as the target edge node; The sending module is used to send the conference information to the target edge node.

14. An electronic device comprising a memory, a processor and a computer program stored in the memory, characterized in that: The processor executes the computer program to implement the method according to any one of claims 1 to 11.

15. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the method according to any one of claims 1 to 11 is implemented.

Images