Multi-host extension method suitable for conference system

Abstract

The invention discloses a multi-host extension method suitable for a conference system. The conference system comprises a conference host, a plurality of extension hosts and a plurality of conference units. Wherein the conference host is respectively connected with the plurality of expansion hosts; each expansion host is connected with a plurality of conference units; assigning a unique number EID to each extended host, assigning a unique number UID to each conference unit, and establishing an address mapping table of the EID and the UID in the conference host; when the conference host sends data, querying the address mapping table through the UID to obtain the corresponding EID, and constructing a complete address code for broadcasting; when the conference host receives data, updating the address mapping table to dynamically map the EID of the extension host and the UID of the conference unit; moreover, the conference units only process the broadcast instructions matched with the UIDs of the conference units so as to ensure the communication efficiency, thereby breaking through the limitation of the connection number of the conference units, and improving the capacity of the conference system.

Description

Technical Field

[0001] This invention relates to a multi-host expansion method, and more particularly to a multi-host expansion method suitable for conference systems, belonging to the technical field of conference systems. Background Technology

[0002] Existing conference systems are mainly used in local meeting rooms and conference room scenarios. They consist of a conference host and multiple conference units, interconnected via an RS485 bus daisy-chain connection. The conference host not only powers each conference unit but also controls the speaking of each unit through an internal communication protocol and completes bidirectional data communication with each conference unit via the RS485 bus.

[0003] Currently, a single conference host can stably support the connection of approximately 100 conference units. However, when the number of conference units exceeds this threshold, the conference system will experience severe distortion of the RS485 signal due to insufficient power supply, excessively long cables, and too many nodes. This leads to a significant increase in the communication error rate between the conference host and the conference units, ultimately preventing the conference host from communicating and controlling the conference units normally, resulting in system failure.

[0004] However, in large conference venues, the number of conference units may reach hundreds or even thousands. Therefore, there is an urgent need to design effective conference system expansion solutions to overcome the limitations on the number of conference units that can be connected and to increase the capacity of the conference system through reasonable topology, connection methods and communication protocols. Summary of the Invention

[0005] To address the aforementioned existing technical problems, this invention provides a multi-host expansion method suitable for conference systems. This method involves cascading multiple conference hosts, connecting them daisy-chain via an independent cable. This effectively solves the problems of insufficient conference units that can be connected to a single conference host, and the inability to support a large number of conference units in a large venue.

[0006] To achieve the above technical objectives, the present invention provides a multi-host expansion method for a conference system, wherein the conference system includes a conference host, multiple expansion hosts, and multiple conference units; wherein the conference host is connected to multiple expansion hosts respectively; and each expansion host is connected to multiple conference units respectively. Assign a unique EID to each extended host and a unique UID to each conference unit, and establish an address mapping table between EID and UID in the conference host; (1) When the conference host sends data to the target conference unit: First, query the address mapping table to obtain the EID corresponding to the target conference unit UID. Then, add the EID and UID to the address field of the data packet and send the data packet to all extended hosts. When any extended host receives a data packet, it first compares the EID in the data packet with its own EID. If they are the same, it extracts the target conference unit UID and command information from the data packet, encapsulates it into an instruction format that the conference unit can recognize, and sends it to all conference units connected to it. Otherwise, the data packet is discarded. When any conference unit receives a data packet, it first compares the UID in the data packet with its own UID. If they are the same, the data packet is retained and subsequent processing is executed; otherwise, the data packet is discarded. (2) When any conference unit sends data to the conference host: First, add your own UID to the address field of the data packet, and then send the data packet to the extended host connected to you; When the extended host receives the data packet, it adds its own EID to the address field of the data packet, and then forwards the data packet to the conference host connected to it. When the conference host receives a data packet, it identifies the conference unit sending the data and the extended host forwarding the data by parsing the EID and UID in the address code of the data packet, and updates the address mapping table.

[0007] Furthermore, the conference units are connected in a daisy-chain manner and then connected to the corresponding extended host via an RS485 communication line.

[0008] Furthermore, the present invention allows for no more than 100 conference units connected to the same extended host.

[0009] Furthermore, in this invention, the extended hosts are connected in a daisy-chain manner and then connected to the same conference host via an RS485 communication line.

[0010] Furthermore, the present invention allows for no more than 100 extended hosts connected to the same conference host.

[0011] Furthermore, the present invention assigns an EID to each extended host and a UID to each conference unit via jumper switches.

[0012] Furthermore, in the address mapping table, EID and UID have a one-to-many relationship.

[0013] In summary, this invention provides the conference host with system expansion capabilities. Through a reasonable conference system topology and communication protocol design, it can effectively overcome the limitations of power supply and communication lines of a single conference host on the connection of conference units, cascading multiple small conference systems into a large conference system, thereby creating a larger conference system.

[0014] Compared with the prior art, the present invention has the following technical advantages: (1) In traditional conference systems, the conference units are powered and managed by the conference host. A single conference host can only provide reliable power and communication management for up to 100 conference units, which is insufficient for large venues that require hundreds or thousands of conference units. This invention uses a new system connection method and communication protocol design, which expands the system by cascading multiple conference hosts. Multiple expansion hosts are connected to the conference host in a daisy-chain manner through an independent cable. This effectively solves the problem of limited capacity of the conference host to connect conference units, greatly improves the system's ability to connect conference units, and has been proven in practice to meet the capacity requirements of large venues.

[0015] (2) The conference host of the present invention establishes and maintains an address mapping table between EID and UID. When the conference host sends data: it queries the address mapping table through the UID to obtain the corresponding EID, constructs a complete address code, and broadcasts it; when the conference host receives data: it updates the address mapping table to dynamically map the EID of the extended host and the UID of the conference unit. Furthermore, the conference unit only processes broadcast commands that match its own UID, ensuring communication efficiency. In this way, by identifying the hierarchical devices through EID and ensuring accurate addressing through UID, bidirectional reliable communication between the conference host, extended host, and conference unit is realized. Attached Figure Description

[0016] Figure 1 This is a block diagram of the electrical principle of the conference system used in this invention; Figure 2 This is a flowchart illustrating the data processing of the extended host and conference unit when data is sent through the conference host according to the present invention. Figure 3 This is a flowchart illustrating the data processing of the extended host and the conference host when data is sent through the conference unit according to the present invention. Detailed Implementation

[0017] To make the objectives, technical solutions, and advantages of this invention clearer, the technical solutions of this invention will be clearly and completely described below in conjunction with embodiments of this invention. In the description of this application, terms such as "connection" or "linked" are not limited to physical or mechanical connections, but can include electrical connections, whether direct or indirect. Those skilled in the art can understand the specific meaning of the above terms in this application according to the specific circumstances.

[0018] like Figure 1 As shown, this embodiment provides a multi-host expansion method suitable for a conference system. The conference system includes a conference host, multiple expansion hosts, and multiple conference units. The conference host connects to each of the multiple expansion hosts, and each expansion host connects to multiple conference units. Furthermore, each expansion host is assigned a unique identifier (EID), and each conference unit is assigned a unique identifier (UID). The conference host establishes an address mapping table between EIDs and UIDs.

[0019] In other implementations, all conference units are divided into multiple groups, with each group assigned an extension host, and all extension hosts assigned a conference host. Each group of conference units is first connected in a daisy-chain configuration, and then connected to its corresponding extension host via a dedicated extension cable. All extension hosts are first connected in a daisy-chain configuration, and then connected to the same conference host via a dedicated extension cable. Specifically, each group of conference units is connected in daisy-chain series, then connected to its corresponding extension host via a dedicated RS485 communication line. Multiple extension hosts are then connected in daisy-chain series, and finally connected to the conference host via a dedicated RS485 communication line. This grouped connection and collaborative design with the extension hosts effectively reduces the load on a single conference host and avoids signal distortion and communication problems.

[0020] In other implementations, no more than 100 expansion hosts are connected to the same conference host; and no more than 100 conference units are connected to the same expansion host. Specifically, if there are 1000 conference units, they are evenly divided into 10 groups of 100 units each, connected to 10 expansion hosts, and then each of the 10 expansion hosts is connected to the same conference host. This overcomes the connection capacity limitations of existing conference systems in large venues, significantly improving the overall connection capacity and stability of the conference system.

[0021] In other implementations, each extended host is assigned a unique number, also called an EID, via jumper switches, serving as its ID identifier. Similarly, each conference unit is assigned a unique number, also called a UID, via jumper switches, serving as its ID identifier. In practice, the EIDs of all extended hosts connected to the same conference host must be distinct to differentiate and identify each extended host. Likewise, the UIDs of all conference units connected to the same extended host must be distinct to differentiate and identify each conference unit. For example, 10 extended hosts can be assigned EIDs of 01, 02, 03, 04, 05, 06, 07, 08, 09, and 10. The 10 conference units connected to the extended host with EID 01 can be assigned UIDs of 01, 02, 03, 04, 05, 06, 07, 08, 09, and 10. The uniqueness of the EID and UID ensures that the conference host can accurately identify and control each extended host, and that each extended host can accurately identify and control each conference unit.

[0022] As can be seen from the above, the conference system used in this invention, through group connection and UID and EID identification, breaks through the limitation that a single conference host can only connect to 100 conference units, and supports a single conference host to connect to thousands of conference units, avoiding the distortion problem of RS485 signals caused by excessively long cables and too many nodes. Furthermore, through a hierarchical architecture and standardized identification management, reliable expansion of large-scale conference systems is achieved.

[0023] Before the aforementioned conference system begins operation, the conference host first establishes an EID and UID address mapping table. In practice, the EID and UID are automatically established when the conference unit completes the numbering action. When the conference host initiates a numbering command, the command is transmitted to the conference unit via the extended host, allowing the conference unit to know the EID of the extended host it is connected to. When the conference unit presses the confirmation number button, it sends its own UID information along with the conference unit's UID to the conference host via the extended host. The extended host then sends its own EID and the conference unit's UID confirmation information to the conference host, thus completing the establishment of the EID and UID address mapping table. For example, the EID and UID address mapping table established by the conference host is shown in Table 1. The EID and UID have a one-to-many relationship; UID_1 and UID_2 both correspond to EID_1, indicating that both conference units are connected to the extended host EID_1.

[0024] Table 1 Extended Host EID Meeting Unit UID EID_1 UID_1 EID_1 UID_2 EID_2 UID_3 ... ... EID_N UID_N like Figure 2As shown, when a conference host sends data to a specific conference unit: it first queries the address mapping table of EID and UID to obtain the EID corresponding to the UID of the target conference unit, then adds the EID and the UID of the target conference unit to the address field of the data packet to form the complete address code of the data packet, and then sends the data packet to all extended hosts in a broadcast manner.

[0025] When any extended host receives a data packet broadcast by the conference host, it first compares the EID address in the data packet with its own EID. If the EID is found to be exactly the same, the extended host determines that the data packet was sent by the conference host to a conference unit connected to it. In this case, the extended host extracts the target conference unit's UID and command information from the data packet, encapsulates it into a command format recognizable by the conference unit, and broadcasts it to all conference units connected to it. If the EID is found to be different from its own, the extended host determines that the data packet was sent by the conference host to a conference unit connected to another extended host. In this case, the extended host discards the data packet without further processing.

[0026] When any conference unit receives a data packet broadcast by the extended host, it first compares the UID address in the data packet with its own UID. If the UID is found to be exactly the same as its own, the conference unit determines that the data packet was specifically sent to it by the conference host, and in this case, it retains the data packet and executes the subsequent data processing flow. If the UID is found to be different from its own, the conference unit determines that the data packet was sent by the conference host to another conference unit, and in this case, the conference unit discards the data packet directly without performing any data processing.

[0027] like Figure 3 As shown, when a conference unit sends data to the conference host, it first adds its own UID to the address field of the data packet, and then broadcasts the data packet to the extended host connected to it.

[0028] When the extended host receives the data packet broadcast by the conference unit, it adds its own EID to the address field of the data packet, combines it with the conference unit's UID to form the complete address code of the data packet, and then forwards the data packet to the conference host connected to it.

[0029] When the conference host receives a data packet broadcast by the extended host, it accurately identifies the conference unit sending the data and the extended host forwarding the data by parsing the EID and UID in the address code of the data packet, and updates the EID and UID address mapping table accordingly, thereby achieving accurate parsing and processing of the uplink request.

[0030] As can be seen from the above technical solution, in the RS485 bus communication architecture, the conference host addresses the conference units using address codes. Currently, there is no direct connection between the conference units and the conference host in the conference system; instead, a hierarchical topology is used: conference units connect to corresponding extension hosts, and each extension host then connects to the conference host. This structure dictates that the communication process must follow these rules: (1) Downlink instruction transmission: The instructions sent by the conference host must first be broadcast to all extended hosts. Each extended host extracts the UID of the target conference unit by comparing the EID in the instruction (when it matches its own EID), and then forwards the broadcast instruction to the corresponding conference unit.

[0031] (2) Uplink request transmission: When a conference unit sends a request containing its own EID, it first broadcasts it to the extended host connected to it. The extended host encapsulates the conference unit's request with its own EID and forwards it to the conference host, so that the conference host can identify which conference unit sent the request and which extended host forwarded it through the EID and UID, thereby updating the address mapping table in the conference host to correctly parse the conference unit's uplink request.

[0032] (3) Address Management Mechanism: The conference host needs to maintain a mapping address table of EID and UID, realize addressing at the extended host level through EID, and locate the specific conference unit through UID. This mechanism ensures that data conflicts are avoided in multi-point communication and supports polling control of one master and multiple slaves.

[0033] In this way, bidirectional data transmission and reception communication is achieved between the conference host, multiple extended hosts, and multiple conference units. This RS485 bus communication architecture achieves hierarchical addressing through the EID identifier of the extended host, which not only retains the advantage of RS485 bus supporting multi-point communication, but also solves the bus contention problem in half-duplex mode through the master-slave polling mechanism, making it suitable for networking needs of hundreds to thousands of conference units in large venues.

[0034] The technical solutions provided by the embodiments of the present invention have been described in detail above. Specific examples have been used to illustrate the principles and implementation methods of the present invention. The description of the above embodiments is only for the purpose of helping to understand the method and core ideas of the present invention. At the same time, for those skilled in the art, based on the ideas of the present invention, modifications can be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. These modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the ideas and scope of the technical solutions of the embodiments of the present invention.

Claims

1. A multi-host expansion method suitable for conference systems, characterized in that, The conference system includes a conference host, multiple extended hosts, and multiple conference units; wherein the conference host is connected to multiple extended hosts; and each extended host is connected to multiple conference units. Assign a unique EID to each extended host and a unique UID to each conference unit, and establish an address mapping table between EID and UID in the conference host; (1) When the conference host sends data to the target conference unit: First, query the address mapping table to obtain the EID corresponding to the target conference unit UID. Then, add the EID and UID to the address field of the data packet and send the data packet to all extended hosts. When any extended host receives a data packet, it first compares the EID in the data packet with its own EID. If they are the same, it extracts the target conference unit UID and command information from the data packet, encapsulates it into an instruction format that the conference unit can recognize, and sends it to all conference units connected to it. Otherwise, the data packet is discarded directly. When any conference unit receives a data packet, it first compares the UID in the data packet with its own UID. If they are the same, the data packet is retained and subsequent processing is executed; otherwise, the data packet is discarded. (2) When any conference unit sends data to the conference host: First, add your own UID to the address field of the data packet, and then send the data packet to the extended host connected to you; When the extended host receives the data packet, it adds its own EID to the address field of the data packet, and then forwards the data packet to the conference host connected to it. When the conference host receives a data packet, it identifies the conference unit sending the data and the extended host forwarding the data by parsing the EID and UID in the address code of the data packet, and updates the address mapping table.

2. The multi-host expansion method for a conference system according to claim 1, characterized in that, The conference units are connected in a daisy-chain manner and then connected to the corresponding extended host via an RS485 communication line.

3. A multi-host expansion method for a conference system according to claim 1 or 2, characterized in that, No more than 100 conference units can be connected to the same extended host.

4. The multi-host expansion method for a conference system according to claim 1, characterized in that, The extended hosts are connected in a daisy-chain manner and then connected to the same conference host via an RS485 communication cable.

5. A multi-host expansion method for a conference system according to claim 1 or 4, characterized in that, No more than 100 expansion hosts can be connected to the same conference host.

6. A multi-host expansion method for a conference system according to claim 1, characterized in that, EIDs are assigned to each extended host and UIDs are assigned to each conference unit via jumper switches.

7. A multi-host expansion method for a conference system according to claim 1 or 6, characterized in that, The EID and UID in the address mapping table have a one-to-many relationship.

Images