A management device for multiple decoding devices in a local area network

Abstract

This invention relates to the field of decoding equipment technology, specifically to a management device and method for multiple decoding devices within a local area network. By using a master device as the primary signaling sender, the device manages the decoding devices, avoiding the resource consumption issues associated with using a management server for control in existing technologies. Through the combined use of a signaling caching module and a database configuration and configuration file writing module, low-latency synchronization of complete information can be achieved while increasing fault tolerance. Data storage and backup are performed according to actual business needs, eliminating the need for additional backup servers. Through the cooperation of a streaming media signaling negotiation module and a streaming media sharing module, this device can achieve optimal line streaming and sharing within the device, ensuring that the streaming capabilities of the streaming devices fully meet the needs of pushing multiple streams.

Description

Technical Field

[0001] This invention relates to the field of decoding equipment technology, specifically to a management device for multiple decoding devices within a local area network. Background Technology

[0002] With technological advancements and market demands, the number of decoding devices used simultaneously in certain scenarios is no longer limited to one or a few. The more decoding devices used, the more complex the management becomes. Currently, the management and scheduling of multiple decoding devices are typically controlled by a dedicated management server, and the forwarding of related data and media streams also largely resides on the server. This often results in significant server resource consumption, and data backups frequently require additional backup servers. Summary of the Invention

[0003] To address the aforementioned technical problems, this invention provides a management device for multiple decoding devices within a local area network.

[0004] To achieve the above objectives, the present invention provides the following technical solution: a multi-decoding device management device within a local area network, comprising a multicast domain and several devices connected to the multicast domain via multicast signaling. These devices are elected to form a master device and several slave devices. The master device includes a unicast communication module, an external information receiving module, and a service processing module connected to the output of the external information receiving module. The unicast communication module enables communication between the master device and the slave devices. The external information receiving module receives control commands from the web and clients. The service processing module of the master device performs judgment and processing on the information. The output of the service processing module is connected to a multicast communication module, a signaling buffer module, a database, and a configuration file writing module. The multicast communication module of the master device enables multicast communication with the multicast domain. The signaling buffer module of the master device stores the information processed by the service processing module. The system performs temporary backups and caching, and reissues failure signaling. After the master device's service processing module determines whether a message needs processing, messages that do not need processing and messages that require processing are processed and then written to the database and configuration file writing module to save data information after each instruction execution. The slave device includes a multicast communication module connected to the multicast domain and a unicast communication module connected to the master device. The output of the slave device's multicast communication module is connected to the service processing module, which is used to judge and process messages. The output of the slave device's service processing module is connected to the database and configuration file writing module. After the slave device's service processing module determines whether a message needs processing, messages that do not need processing and messages that require processing are processed and then written to the database and configuration file writing module to save data information after each instruction execution.

[0005] Furthermore, the master device also includes a streaming media signaling negotiation module connected to the service processing module. The input end of the streaming media signaling negotiation module is connected to an external encoding and pushing end and is used for processing various media stream protocols and distributing instructions on how each device should receive the media stream. The output ends of the service processing modules of both the master device and the slave device are connected to streaming media synchronization modules. The streaming media synchronization modules are connected to the multicast domain and are used to forward media streams between devices.

[0006] Furthermore, when a device needs to pull a certain stream, the streaming media signaling negotiation module of the master device will select the device with the least load to pull the stream based on the current number of streams pulled by each device. This device with the least load is called the master stream pulling device. After the master stream pulling device successfully pulls the data stream, it sends the stream to the multicast domain in a multicast manner through the multicast communication module. Then, the device that actually needs to pull the stream can directly pull the stream in the multicast domain through the streaming media synchronization module.

[0007] Furthermore, the output of the unicast communication module of the master device is sequentially connected to a device registration module, a device information synchronization module, and a device election module for master device election; the output of the device election module is connected to the multicast communication module; the slave device also includes a device registration module for master device election, and the output of the device registration module is connected to the unicast communication module.

[0008] Furthermore, when the slave device receives a message through the multicast communication module and fails to process the message sent by the master device through the service processing module, it will proactively send a failure message to the master device in unicast form through the unicast communication module, carrying the failure message sequence number. When the master device receives the failure message sent by the slave device through the unicast communication module, it will query the complete information of the message from the signaling cache module in the master device according to the message sequence number, and then send the multicast message again through the multicast communication module of the master device. When sending the message again, it will carry the device ID that needs to receive the information. When other slave devices receive this message, they will directly discard the message.

[0009] Furthermore, when the service processing modules of the master and slave devices receive a message, they can convert it into a corresponding multicast message according to the message type. While processing the message itself, the master device can transmit the message to the multicast domain via the multicast communication module, and then distribute it to all slave devices through the multicast domain. Whether a slave device or the master device processes these messages, the service processing module will determine whether the message needs its own processing. If not, it only needs to write to the database or configuration file; if so, it processes the message and writes it to the database and configuration file.

[0010] Compared with the prior art, the beneficial effects of the present invention are as follows: The local area network multi-decoding device management device provided by the present invention uses the master device as the main signaling sender to manage the devices between decoding devices, avoiding the problem of consuming server resources when using a management server for control in the prior art; by utilizing the joint cooperation of the signaling caching module and the database configuration and configuration file writing module, it can achieve low-latency synchronization of complete information while increasing fault tolerance, and perform data storage and backup according to actual business and needs, without the need to add a backup server; through the cooperation of the streaming media signaling negotiation module and the streaming media sharing module, the device can achieve optimal line streaming and sharing within the device, enabling the streaming device to fully meet the needs of pushing multiple streams. Attached Figure Description

[0011] Figure 1 This is a network diagram of decoding devices in the existing technology;

[0012] Figure 2 This is the network diagram after the master device is elected in this invention;

[0013] Figure 3 A schematic diagram of the signaling communication structure between the master device, multicast domain, and slave devices. Detailed Implementation

[0014] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention. For those skilled in the art, the specific meaning of the terms in the present invention can be understood according to the specific circumstances.

[0015] The present invention provides a multi-decoding device management device for a local area network, which mainly includes a multicast domain and several devices that are communicatively connected to the multicast domain. The devices include several slave devices elected and a master device. The master device and the slave devices communicate with the multicast domain via multicast, while the slave devices communicate with the master device via unicast.

[0016] The main device contains an external information receiving module and a service processing module connected to the output of the external information receiving module. The external information receiving module receives control commands from the web and clients. The output of the service processing module is connected to a multicast communication module, a signaling buffer module, a database, and a configuration file writing module. The service processing module processes the external information received by the external information receiving module and determines whether the message needs processing. Processed messages are synchronized to the multicast communication module and the signaling buffer module. The multicast communication module enables multicast communication with the multicast domain to send information to slave devices via multicast. The signaling buffer module temporarily backs up and caches the processed information and reissues failed signaling to increase the device's fault tolerance. After the service processing module determines whether processing is needed, messages that do not need processing and messages that do need processing are processed and then written to the database and configuration file writing modules, allowing these modules to store data after command execution.

[0017] The master device also includes a unicast communication module, which enables communication between the master and slave devices by sending messages to designated slave devices via TCP unicast. The output of the unicast communication module is connected to a device registration module. After confirming the master device, each slave device actively initiates a registration signal to the master device, and the master device's device registration module sets the device ID for each slave device. The output of the device registration module is connected to a device information synchronization module, which in turn is connected to a device election module. The device election module is connected to a multicast communication module and is used to elect a master device. After a slave device registers, the master device sends information about all devices to all slave devices through the device information synchronization module, the device election module, and the multicast communication module, achieving device information synchronization.

[0018] During the master device election process, after each device is running normally and connected to the network, its election module sends a designated signal to a specified multicast port in the multicast domain via a multicast communication module. This designated signal mainly carries the device's model, serial number, and IP address; this is referred to as the election signal. Subsequently, each device receives the election signal from the multicast domain. Upon receiving the election signal, it first determines whether a master device exists according to relevant rules. If not, it determines the device based on model priority rules and serial number size. If the current device's priority is higher than the priority of the received election message, it returns an election failure signal to the device via unicast communication module. The entire election process lasts for 3 minutes after the device starts up and sends multicast messages normally. If no unicast election failure message is received from other devices within 3 minutes, the current device is considered the master device. Figure 1The network diagram is shown after the master device is elected. Once the master device is determined, it immediately sends an election result signal via multicast communication module to notify other devices of the successful master election. Upon receiving this message, all devices cease sending election signals and instead initiate registration with the master device via unicast communication module through the device registration module, carrying their own device information and capabilities. After receiving the registration information via unicast communication module, the master device uses the device registration module to register the slave device information. Subsequently, the device information synchronization module synchronizes the information of all slave devices, and after processing by the device election module, the device information is sent to all devices via multicast communication module.

[0019] The device includes a multicast communication module that connects to a multicast domain. This allows the multicast communication module to read messages from the multicast domain and for messages from the device to be transmitted to the multicast domain via the multicast communication module. The output of the multicast communication module is also connected to a service processing module. This service processing module enables the device to judge and process the read messages. The output of the service processing module is connected to a streaming media synchronization module, a database, and a configuration file writing module. The streaming media synchronization module connects to the multicast domain to enable streaming media sharing. The service processing module determines whether a message needs processing; messages that do not need processing, as well as messages that require processing, are processed and then written to the database and configuration file modules.

[0020] Each slave device also includes a device registration module. After the master device is confirmed, the device registration module of each slave device actively initiates a registration signal to the master device through the unicast communication module. The output of the device registration module is connected to the unicast communication module. The device registration module is used to elect the master device, and the unicast communication module is used to establish communication with the master device.

[0021] When the service processing modules of the master and slave devices receive a message, they can convert it into a corresponding multicast message based on the message type. While processing the message itself, the master device can also transmit the message to the multicast domain via the multicast communication module, and then distribute it to all slave devices through the multicast domain. Whether a slave device or the master device processes these messages, the service processing module will determine whether the message needs its own processing. If not, it only needs to write to the database or configuration file; if so, it processes the message and writes it to the database and configuration file. Therefore, the database and configuration file writing module in this system uses a real-time backup method, meaning it doesn't simply back up the data, but processes and synchronizes data according to actual business needs.

[0022] The entire system involves numerous streaming devices, leading to situations where many devices need to stream the same stream simultaneously. In such cases, the streaming capabilities of the push devices are often insufficient to handle the demands of multiple streams. Therefore, the output of the main device's service processing module is also connected to a streaming media signaling negotiation module and a streaming media synchronization module. The main device's streaming media signaling negotiation module connects to an external encoding and push end. This module handles various media stream protocols and directs information to each device on how to receive media streams, enabling the selection of the appropriate main streaming device. The streaming media synchronization module connects to the multicast domain and is used for media stream forwarding, primarily between devices, to facilitate information sharing within the multicast domain and enable streaming.

[0023] When a device needs to pull a specific stream, the master device's streaming media signaling negotiation module selects the device with the lowest load based on the current number of streams being pulled by each device. This selected pulling device is referred to as the master pulling device for that stream. The master pulling device allocates a designated multicast port for the stream and multicasts a notification to all devices. Once the master pulling device successfully pulls the data stream, it sends the stream to the multicast domain via the multicast communication module. Devices that actually need to pull the stream can then directly pull it from the multicast domain through the streaming media synchronization module. If other new devices want to pull the same stream, they can also pull it directly from the multicast domain through the streaming media synchronization module, reducing the need to pull streams from the push devices and thus reducing the bandwidth usage of the push devices.

[0024] The signaling communication of this device uses multicast as the primary method and unicast as a secondary method. All messages sent by the master device are backed up in the signaling buffer module. The information exchange method between the master and slave devices is as follows: Figure 1 As shown, all service information is sent by the master device via multicast communication module and multicast domain. The master device can carry the slave device ID; otherwise, it is assumed that all slave devices must process the message through the service processing module. When a slave device receives a message through the multicast communication module and fails to process the message sent by the master device through the service processing module, it will proactively send a failure message to the master device via unicast communication module, carrying the failure message sequence number. When the master device receives the failure message from the slave device via unicast communication module, it will query the signaling cache module for the complete message information based on this message sequence number, and then resend the multicast message through the multicast communication module. This resend will carry the device ID that needs to receive the information. When other slave devices receive this message, they will discard it directly.

[0025] It will be apparent to those skilled in the art that the present invention is not limited to the details of the exemplary embodiments described above, and that the invention can be implemented in other specific forms without departing from its spirit or essential characteristics. Therefore, the embodiments should be considered in all respects as exemplary and non-limiting, and the scope of the invention is defined by the appended claims rather than the foregoing description. Thus, all variations falling within the meaning and scope of equivalents of the claims are intended to be included within the present invention. No reference numerals in the claims should be construed as limiting the scope of the claims.

Claims

1. A management device for multiple decoding devices within a local area network, characterized in that: It includes a multicast domain and several devices that are connected to the multicast domain via multicast signaling. These devices are elected to form a master device and several slave devices. The master device contains a unicast communication module, an external information receiving module, and a service processing module connected to the output of the external information receiving module. The unicast communication module is used to realize communication between the master device and the slave device; the external information receiving module is used to receive control commands issued by the web and the client; the service processing module of the master device is used to judge and process the information; the output end of the service processing module is connected to the multicast communication module, the signaling buffer module, the database and the configuration file writing module; The multicast communication module of the master device is used to realize multicast communication with the multicast domain; the signaling cache module of the master device is used to temporarily back up and cache the information processed by the service processing module, and to resend the failed signaling; after the service processing module of the master device determines whether the message needs to be processed, the messages that do not need to be processed and the messages that need to be processed can be written to the database and configuration file writing module after processing to save the data information after each instruction is executed. The slave device includes a multicast communication module connected to the multicast domain and a unicast communication module connected to the master device. The output of the multicast communication module of the slave device is connected to the service processing module, which is used to judge and process messages. The output of the service processing module of the slave device is connected to the database and configuration file writing module. After the service processing module of the slave device judges whether a message needs to be processed, messages that do not need to be processed and messages that need to be processed are processed and then written to the database and configuration file writing module to save the data information after each instruction is executed. When a device needs to pull a certain stream, the streaming media signaling negotiation module of the master device will select the device with the least load to pull the stream based on the current number of streams being pulled by each device. This device with the least load is called the master stream pulling device. After the master stream pulling device successfully pulls the data stream, it will send the stream to the multicast domain in a multicast manner through the multicast communication module. Then, the device that actually needs to pull the stream can directly pull the stream from the multicast domain through the streaming media synchronization module. When the slave device receives a message through the multicast communication module and fails to process the message sent by the master device through the service processing module, it will proactively send a failure message to the master device in unicast form through the unicast communication module, carrying the failure message sequence number. When the master device receives the failure message sent by the slave device through the unicast communication module, it will query the complete message information from the signaling cache module in the master device according to the message sequence number, and then send the multicast message again through the multicast communication module of the master device. When sending the message again, it will carry the device ID that needs to receive the information. When other slave devices receive this message, they will discard the message directly.

2. The local area network multi-decoding device management device according to claim 1, characterized in that: The master device also includes a streaming media signaling negotiation module connected to the service processing module. The input end of the streaming media signaling negotiation module is connected to an external encoding and pushing end and is used for processing various media stream protocols and distributing instructions on how each device should receive the media stream. The output ends of the service processing modules of both the master device and the slave device are connected to streaming media synchronization modules. The streaming media synchronization modules are connected to the multicast domain and are used to forward media streams between devices.

3. The local area network multi-decoding device management device according to claim 1, characterized in that: The output of the unicast communication module of the master device is sequentially connected to a device registration module, a device information synchronization module, and a device election module for master device election; the output of the device election module is connected to the multicast communication module; the slave device also includes a device registration module for master device election, and the output of the device registration module is connected to the unicast communication module.

4. The local area network multi-decoding device management device according to claim 1, characterized in that: When the service processing modules of the master and slave devices receive a message, they can convert it into a corresponding multicast message according to the message type. While processing the message, the master device can also transmit the message to the multicast domain through the multicast communication module, and then send it to all slave devices through the multicast domain. When processing these messages, whether it is a slave device or a master device, the service processing module will determine whether the message needs to be processed by itself. If it does not need to be processed, it only needs to write to the database or configuration file. If it needs to be processed, it will be processed and written to the database and configuration file.

Images