Intelligent conference information interaction architecture and system

Abstract

The invention relates to a smart conference information interaction architecture and system, and a central hardware architecture is connected with each conference terminal and an equipment terminal, and obtains the equipment operation information of each equipment terminal and the task demand information of each conference terminal. The system software architecture establishes data interaction with the central hardware architecture, the conference terminal and the equipment terminal, and comprises a terminal calling module which is configured to control the central hardware architecture to issue task starting signals to the conference terminal and the equipment terminal. The task processing module is configured to obtain external transmission data and package a data interface; starting a system task, and issuing a service demand according to the service logic of the system task; assembling a network data protocol according to the data interface and the service demand; and a network data protocol is synchronized to the central hardware architecture, the conference terminal and the equipment terminal through the terminal calling module to establish data interaction among the three. The invention provides a lightweight intelligent conference center system which can be quickly and conveniently accessed to an equipment terminal and enrich the use modes of an intelligent conference.

Description

Technical Field

[0001] The present application relates to the field of smart conference interaction technology, and in particular to a smart conference information interaction architecture and system. Background Art

[0002] Smart conference refers to a form of conference that uses modern network information technology to technically implement and support the entire process of conference resource management, pre-conference preparation, conference affairs implementation, on-site organization, conference service, post-conference management, query analysis, etc. The smart conference system integrates multiple functions such as appointment, notification, approval, sign-in, management, minutes, video management and conference equipment management, etc., to achieve efficient organization and convenient management of meetings.

[0003] At present, with the development of various intelligent devices, such as AI voice devices, projection devices, writing and input devices, more possibilities are given to the hardware of smart conferences. However, the conference systems that can be used to access intelligent devices generally have strong database and data communication capabilities, large costs and volumes, and conference systems with small data volumes cannot meet the recognition and access requirements of various intelligent devices for the time being, and their use is relatively limited. Summary of the invention

[0004] Based on the above analysis, in order to solve the problem that the conference systems currently available for accessing smart devices generally have strong database and data communication capabilities, large costs and volumes, and small data-level conference systems are temporarily unable to meet the identification and access needs of various smart devices and have large usage restrictions, an embodiment of the present invention provides a smart conference information interaction architecture and system.

[0005] The present application embodiment provides a smart conference information interaction architecture, including: The central hardware architecture is configured to connect to each conference terminal and device terminal respectively, and obtain the device operation information of each device terminal and the task requirement information of each conference terminal; The system software architecture establishes data interaction with the central hardware architecture, the conference terminal and the device terminal, including: The terminal calling module is configured to control the central hardware architecture to send a task start signal to the conference terminal and the device terminal; wherein the task start signal is used to control the conference terminal and the device terminal to start and generate outbound data; The task processing module is configured to perform the following steps: Acquire the outbound data and encapsulate the data interface; Start the system task and issue business requirements according to the business logic of the system task; Assembling a network data protocol according to the data interface and the business requirements; The network data protocol is synchronized to the central hardware architecture, the conference terminal and the device terminal through the terminal calling module to establish data interaction among the three.

[0006] The smart conference information interaction architecture of the embodiment of the present application, the central hardware architecture is connected to each conference terminal and device terminal respectively, and obtains the equipment operation information of each device terminal and the task requirement information of each conference terminal. The system software architecture establishes data interaction with the central hardware architecture, conference terminals and device terminals, including: a terminal calling module, which is configured to control the central hardware architecture to send task start signals to conference terminals and device terminals. The task processing module is configured to obtain outbound data and encapsulate data interfaces; start system tasks, and issue business requirements according to the business logic of system tasks; assemble network data protocols according to data interfaces and business requirements; synchronize network data protocols to the central hardware architecture, conference terminals and device terminals through the terminal calling module, and establish data interaction among the three. Based on this, a lightweight smart conference center system is provided, which can quickly and easily access device terminals and enrich the usage mode of smart conferences.

[0007] As one of the optional embodiments, the central hardware architecture establishes a connection with the device terminal via a serial communication method; Wherein, the serial communication mode includes RS485 / RS232 communication.

[0008] As one of the optional embodiments, the central hardware architecture establishes data communication with the conference terminal through a communication protocol matching the serial port communication mode.

[0009] As one of the optional embodiments, the central hardware architecture is an embedded system; the terminal calling module is further configured to perform the following steps: Initialize the system memory, GPIO pin configuration, I2C driver, serial port driver registration and communication protocol driver registration of the central hardware architecture; Initialize system parameters and read FLASH to update configuration files; Initialize the serial communication protocol part and encapsulate the LIB library; Enable ATE self-test tasks and timer tasks to monitor embedded system performance.

[0010] As one of the optional embodiments, the conference terminal includes an MQTT client and / or a SOCKET client; The terminal calling module is configured to control the central hardware architecture to send a task start signal to the conference terminal and the device terminal, comprising the steps of: After the ATE self-check task is completed for more than a set period of time, a task start signal is sent to the conference terminal and the device terminal.

[0011] As one of the optional embodiments, the process of the conference terminal starting and generating outbound data includes the steps of: Start the communication task of collecting the conference terminal, initialize the local real-time data memory and local interaction parameter information Text of the conference terminal; The process of the device terminal starting and generating outbound data includes the following steps: Start various database tasks of the device terminal.

[0012] As one of the optional embodiments, the device terminal corresponds one-to-one to the network data protocol.

[0013] As one of the optional embodiments, the process of synchronizing the network data protocol to the central hardware architecture, the conference terminal and the device terminal through the terminal calling module to establish data interaction among the three includes the steps of: Data interaction between the central hardware architecture and the conference terminal is achieved through the network data protocol.

[0014] As one of the optional embodiments, the process of synchronizing the network data protocol to the central hardware architecture, the conference terminal and the device terminal through the terminal calling module to establish data interaction among the three includes the steps of: The central hardware architecture is controlled to call the hardware abstraction layer and instruct the function pointer to perform a callback, and establish data interaction with the device terminal through a corresponding data interface.

[0015] An embodiment of the present application also provides a smart conference information interaction system, including a conference terminal, a device terminal, and a smart conference information interaction architecture as described in any of the above embodiments.

[0016] In the smart conference information interaction system of the embodiment of the present application, the central hardware architecture is connected to each conference terminal and device terminal respectively, and obtains the equipment operation information of each device terminal and the task requirement information of each conference terminal. The system software architecture establishes data interaction with the central hardware architecture, conference terminals and device terminals, including: a terminal calling module, which is configured to control the central hardware architecture to send task start signals to conference terminals and device terminals. The task processing module is configured to obtain outbound data and encapsulate data interfaces; start system tasks, and send business requirements according to the business logic of system tasks; assemble network data protocols according to data interfaces and business requirements; synchronize network data protocols to the central hardware architecture, conference terminals and device terminals through the terminal calling module to establish data interaction among the three. Based on this, a lightweight smart conference center system is provided, which can quickly and easily access device terminals and enrich the usage mode of smart conferences. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] Figure 1 A module structure diagram of a smart conference information interaction architecture according to an embodiment of an application; Figure 2 A workflow diagram of a smart conference information interaction architecture according to an embodiment of an application; Figure 3 This is the implementation logic diagram of the center hardware architecture. DETAILED DESCRIPTION

[0018] In order to make the purpose, technical scheme and advantages of the embodiments of the present application clearer, the technical scheme of the embodiments of the present application will be clearly and completely described below in conjunction with the drawings of the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, rather than all of the embodiments. Based on the described embodiments of the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0019] Unless otherwise defined, the technical terms or scientific terms used in this application should be understood by people with ordinary skills in the field to which this application belongs. "First", "second" and similar words used in this application do not indicate any order, quantity or importance, but are only used to distinguish different components. "Include" or "comprise" and similar words mean that the elements or objects appearing before the word cover the elements or objects listed after the word and their equivalents, without excluding other elements or objects. "Connect" or "connected" and similar words are not limited to physical or mechanical connections, but may include electrical connections, whether direct or indirect. "Up", "down", "left", "right" and the like are only used to indicate relative positional relationships. When the absolute position of the described object changes, the relative positional relationship may also change accordingly.

[0020] In order to keep the following description of the embodiments of the present application clear and concise, the present application omits detailed descriptions of some known functions and known components.

[0021] An embodiment of the present application provides a smart conference information interaction architecture.

[0022] Figure 1 This is a module structure diagram of the smart conference information interaction architecture of an application embodiment, such as Figure 1 As shown, the smart conference information interaction architecture of an application embodiment includes: The central hardware architecture 100 is configured to connect to each conference terminal and device terminal respectively, and obtain device operation information of each device terminal and task requirement information of each conference terminal; The system software architecture 101 establishes data interaction with the central hardware architecture 100, the conference terminal and the device terminal.

[0023] Among them, Figure 1 As shown, the system software architecture 101 includes a terminal calling module 1010 and a task processing module 1011 .

[0024] The terminal calling module 1010 is configured to control the central hardware architecture 100 to send a task start signal to the conference terminal and the device terminal; wherein the task start signal is used to control the conference terminal and the device terminal to start and generate outbound data; The task processing module 1011 is configured to perform the following steps: Acquire the outbound data and encapsulate the data interface; Start the system task and issue business requirements according to the business logic of the system task; Assembling a network data protocol according to the data interface and the business requirements; The network data protocol is synchronized to the central hardware architecture 100, the conference terminal and the device terminal through the terminal calling module 1010 to establish data interaction among the three.

[0025] The central hardware architecture 100 serves as a relay station for each conference terminal and each device terminal and as a center for data interaction. Based on the principle of lightweight data interaction, the central hardware architecture 100 preferably adopts an embedded system to reduce the use of processors, and realizes the setting interaction with the conference terminal and the device terminal by limiting the communication method.

[0026] Preferably, the central hardware architecture 100 establishes a connection with the device terminal via a serial communication method; Wherein, the serial communication mode includes RS485 / RS232 communication.

[0027] The central hardware architecture 100 establishes data communication with the conference terminal through a communication protocol matching the serial port communication mode.

[0028] Among them, the central hardware architecture 100 supports RS485 / RS232 communication, and the communication protocol matching the serial port communication mode can adopt a lightweight communication protocol such as Modbus RTU mode.

[0029] Preferably, the communication between the central hardware architecture 100 and the cloud simultaneously adopts a lightweight network protocol, such as the MQTT Internet of Things protocol, and supports the Bluetooth V4.2 protocol, so as to facilitate adaptation to various types of device terminals under the ESP32 system architecture and realize lightweight multi-type device terminal access.

[0030] Based on this, Figure 2 This is a workflow diagram of the smart conference information interaction architecture of an application embodiment, such as Figure 2 As shown, the central hardware architecture 100 is an embedded system; the terminal calling module 1010 is also configured to perform the following steps: Initialize the system memory, GPIO pin configuration, I2C driver, serial port driver registration and communication protocol driver registration of the central hardware architecture 100; Initialize system parameters and read FLASH to update configuration files; Initialize the serial communication protocol part and encapsulate the LIB library; Enable ATE self-test tasks and timer tasks to monitor embedded system performance.

[0031] Among them, the embedded system based on the central hardware architecture 100 is an ESP32 system, which ensures the stability of its own circuit through initialization operation and ATE self-test for subsequent processing.

[0032] The preferred ESP32 system conveniently and quickly supports new equipment in large halls, supports one-to-one communication, supports MQTTqos=2 retransmission network data packet mechanism, and can realize the step execution of the task processing module 1011 of this application.

[0033] Among them, the task processing module 1011 and the terminal calling module 1010 are both external processors for realizing control interaction with the central hardware architecture 100. A large amount of data load and data calculation of the smart conference information are on the side of the central hardware architecture 100, so the task processing module 1011 and the terminal calling module 1010 can use lightweight processors or tap into the lightweight data processing of smart devices, which have lower processing requirements and data requirements.

[0034] Preferably, the conference terminal includes an MQTT client and / or a SOCKET client; The terminal calling module 1010 is configured to control the process of the central hardware architecture 100 sending a task start signal to the conference terminal and the device terminal, including the steps of: After the ATE self-check task is completed for more than a set period of time, a task start signal is sent to the conference terminal and the device terminal.

[0035] The set time period is 5-15 seconds, preferably 10 seconds. According to the ATE self-check being normal, a task start signal is sent to the conference terminal and the device terminal to ensure the normal subsequent conference communication.

[0036] Due to its lightweight design, the system software architecture 101 does not support communication with devices that are not in the Modbus protocol standard. The amount of data transmitted between devices at one time is small and the communication rate is low (maximum support 115200bps). It does not support dual-send Socket and MQTT protocols. Therefore, the communication rate is adjusted through the encapsulation of the data interface and subsequent steps, such as Figure 2 As shown, the process of starting and generating outbound data by the conference terminal includes the steps of: Start the communication task of collecting the conference terminal, initialize the local real-time data memory and local interaction parameter information Text of the conference terminal; The process of the device terminal starting and generating outbound data includes the following steps: Start various database tasks of the device terminal.

[0037] The adjusted device terminals correspond to the network data protocols one by one. The system software architecture 101 is modularly distributed, the internal functions of the modules are encapsulated into API data interfaces, and the modules are low-coupled and high-cohesive, which is convenient for developers to quickly start calling interfaces, support rapid expansion of new device terminals, and support expansion of peripheral serial port driver libraries. The system software architecture 101 supports customized requirements, and packages real-time data information and setting parameter related information according to information such as module SN and device terminal type.

[0038] Therefore, the encapsulation based on the data interface and the independent type of device terminal correspond to a type of communication protocol at this time. For example, device A corresponds to protocol A.

[0039] Preferably, Figure 2 As shown, the process of synchronizing the network data protocol to the central hardware architecture 100, the conference terminal and the device terminal through the terminal calling module 1010 to establish data interaction among the three includes the steps of: The data interaction between the central hardware architecture 100 and the conference terminal is realized through the network data protocol.

[0040] The process of synchronizing the network data protocol to the central hardware architecture 100, the conference terminal and the device terminal through the terminal calling module 1010 to establish data interaction among the three includes the steps of: The central hardware architecture 100 is controlled to call the hardware abstraction layer and instruct the function pointer to perform a callback, and establish data interaction with the device terminal through a corresponding data interface.

[0041] In the above steps, the hardware abstraction layer is called in communication; the function pointer is called back and the corresponding protocol interface is used, so that the data interaction between the central hardware architecture 100 and the device terminal is quickly established and realized.

[0042] In terms of task sequence: 1-N, find specific models based on tasks, execute specific practices (benchmark barcodes), conference information tasks can be expanded or reduced; scheduling tasks can be configured during initialization, and the data interaction between the central hardware architecture 100 and the conference terminal is complete and fast. Figure 3 As shown, in the implementation logic of the central hardware architecture 100, based on the independent deployment of the data interface, there is a high degree of freedom in the access of the conference terminal services and device terminals.

[0043] In the smart conference information interaction architecture of the embodiment of the present application, the central hardware architecture 100 is connected to each conference terminal and device terminal respectively to obtain the device operation information of each device terminal and the task requirement information of each conference terminal. The system software architecture 101 establishes data interaction with the central hardware architecture 100, the conference terminal and the device terminal, including: a terminal calling module 1010, which is configured to control the central hardware architecture 100 to send a task start signal to the conference terminal and the device terminal. The task processing module 1011 is configured to obtain outbound data and encapsulate the data interface; start the system task, and send business requirements according to the business logic of the system task; assemble the network data protocol according to the data interface and business requirements; synchronize the network data protocol to the central hardware architecture 100, the conference terminal and the device terminal through the terminal calling module 1010, and establish data interaction among the three. Based on this, a lightweight smart conference center system is provided, which can quickly and conveniently access the device terminal and enrich the usage mode of the smart conference.

[0044] An embodiment of the present application also provides a smart conference information interaction system, including a conference terminal, a device terminal, and a smart conference information interaction architecture as described in any of the above embodiments.

[0045] In the smart conference information interaction system of the embodiment of the present application, the central hardware architecture is connected to each conference terminal and device terminal respectively, and obtains the equipment operation information of each device terminal and the task requirement information of each conference terminal. The system software architecture establishes data interaction with the central hardware architecture, conference terminals and device terminals, including: a terminal calling module, which is configured to control the central hardware architecture to send task start signals to conference terminals and device terminals. The task processing module is configured to obtain outbound data and encapsulate data interfaces; start system tasks, and send business requirements according to the business logic of system tasks; assemble network data protocols according to data interfaces and business requirements; synchronize network data protocols to the central hardware architecture, conference terminals and device terminals through the terminal calling module to establish data interaction among the three. Based on this, a lightweight smart conference center system is provided, which can quickly and easily access device terminals and enrich the usage mode of smart conferences.

[0046] There are a few points to note about this application: (1) The drawings of the embodiments of the present application only relate to the structures related to the embodiments of the present application, and other structures may refer to the general design.

[0047] (2) For the sake of clarity, the thickness and size of layers or structures are exaggerated in the drawings used to describe the embodiments of the present invention. It is understood that when an element such as a layer, film, region, or substrate is referred to as being "on" or "under" another element, the element may be "directly" "on" or "under" the other element, or there may be intervening elements.

[0048] (3) In the absence of conflict, the embodiments of the present application and the features in the embodiments may be combined with each other to obtain new embodiments. The above are only specific implementation methods of the present application, but the protection scope of the present application is not limited thereto. The protection scope of the present application shall be based on the protection scope of the claims.

[0049] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0050] The above embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the patent application. It should be pointed out that, for a person of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the patent application shall be subject to the attached claims.

Claims

1. A smart conference information interaction architecture, characterized in that: include: The central hardware architecture is configured to connect to each conference terminal and device terminal respectively, and obtain the device operation information of each device terminal and the task requirement information of each conference terminal; The system software architecture establishes data interaction with the central hardware architecture, the conference terminal and the device terminal, including: The terminal calling module is configured to control the central hardware architecture to send a task start signal to the conference terminal and the device terminal; wherein the task start signal is used to control the conference terminal and the device terminal to start and generate outbound data; The task processing module is configured to perform the following steps: Acquire the outbound data and encapsulate the data interface; Start the system task and issue business requirements according to the business logic of the system task; Assembling a network data protocol according to the data interface and the business requirements; The network data protocol is synchronized to the central hardware architecture, the conference terminal and the device terminal through the terminal calling module to establish data interaction among the three.

2. According to claim 1, the smart conference information interaction architecture is characterized in that: The central hardware architecture establishes a connection with the device terminal via serial communication; Wherein, the serial communication mode includes RS485 / RS232 communication.

3. The smart conference information interaction architecture according to claim 2 is characterized in that: The central hardware architecture establishes data communication with the conference terminal through a communication protocol matching the serial port communication mode.

4. The smart conference information interaction architecture according to claim 3 is characterized in that: The central hardware architecture is an embedded system; the terminal calling module is also configured to perform the following steps: Initialize the system memory, GPIO pin configuration, I2C driver, serial port driver registration and communication protocol driver registration of the central hardware architecture; Initialize system parameters and read FLASH to update configuration files; Initialize the serial communication protocol part and encapsulate the LIB library; Enable ATE self-test tasks and timer tasks to monitor embedded system performance.

5. The smart conference information interaction architecture according to claim 4 is characterized in that: The conference terminal includes an MQTT client and / or a SOCKET client; The terminal calling module is configured to control the central hardware architecture to send a task start signal to the conference terminal and the device terminal, comprising the steps of: After the ATE self-check task is completed for more than a set period of time, a task start signal is sent to the conference terminal and the device terminal.

6. The smart conference information interaction architecture according to claim 5 is characterized in that: The process of starting and generating outbound data by the conference terminal includes the following steps: Start the communication task of collecting the conference terminal, initialize the local real-time data memory and local interaction parameter information Text of the conference terminal; The process of the device terminal starting and generating outbound data includes the following steps: Start various database tasks of the device terminal.

7. The smart conference information interaction architecture according to claim 1 is characterized in that: The device terminals correspond one to one to the network data protocols.

8. The smart conference information interaction architecture according to claim 1 is characterized in that: The process of synchronizing the network data protocol to the central hardware architecture, the conference terminal and the device terminal through the terminal calling module to establish data interaction among the three includes the steps of: Data interaction between the central hardware architecture and the conference terminal is achieved through the network data protocol.

9. The smart conference information interaction architecture according to claim 1 is characterized in that: The process of synchronizing the network data protocol to the central hardware architecture, the conference terminal and the device terminal through the terminal calling module to establish data interaction among the three includes the steps of: The central hardware architecture is controlled to call the hardware abstraction layer and instruct the function pointer to perform a callback, and establish data interaction with the device terminal through a corresponding data interface.

10. A smart conference information interaction system, characterized in that: It includes a conference terminal, a device terminal and a smart conference information interaction architecture as described in any one of claims 1 to 9.

Images