Multimedia informatization conference management method and system

Abstract

The invention discloses a multimedia informatization conference management method and system, and relates to the technical field of multimedia informatization conference management.The method comprises the steps that SHA256 hash calculation is carried out on extended display identification data blocks of downstream equipment before a conference, and then hash is carried out on a splicing result to obtain a topological fingerprint before the conference; converting the initial value of the number of the downstream devices of the repeats into binary vectors, performing bitwise exclusive or in sequence to obtain pre-meeting anchoring values, and constructing a topological shadow tree in combination with the mapping relation between the repeats and the downstream devices; marking a zero-topology window repetitor with the real-time downstream equipment number of 0 in the case, tracing a nearest sink node in a topological shadow tree to form a minimum influence domain, extracting an influenced display cluster identifier, and locally modifying a source cluster mapping matrix as a placeholder source; calculating an anchor value and a topological fingerprint, and verifying topological consistency through two dimensions of an anchor difference and a topological fingerprint Boolean quantity; after the conference, key data are integrated to be archived as conference management files, accurate conference topology management, efficient exception handling and problem tracing are achieved, and stable operation of the conference is guaranteed.

Description

Technical Field

[0001] This invention relates to the field of multimedia information conference management technology, specifically to multimedia information conference management methods and systems. Background Technology

[0002] Multimedia information-based conferences rely on distributed visualization links to achieve synchronous video presentation across multiple devices. These links include video sources, encoding devices, a central signal matrix, decoding modules, repeaters, and downstream display devices. Downstream display devices are divided into display clusters based on region or function to accommodate diverse presentation needs. Two key preparations must be completed before the conference: first, downstream devices must declare their display capabilities to the upstream of the link by extending display recognition data, specifying parameters such as resolution and refresh rate to adapt to the video source output; second, a secure transmission link must be established through high-bandwidth digital content protection protocols to prevent the leakage of conference content.

[0003] In actual deployments, devices often come from different manufacturers, leading to incompatibility issues in repeater forwarding logic and downstream device extended display recognition data formats. Furthermore, dynamic operations such as device wake-up, addition, and removal during meetings increase the complexity of the link operation. The current system's core technical problem lies in the lack of decoupling between real-time verification of topology consistency and encryption maintenance for high-bandwidth digital content protection. The system only completes static topology configuration before the meeting, failing to embed real-time topology consistency verification into the encryption link maintenance process. This results in the inability to accurately determine dynamic topology changes during the meeting. This problem is directly triggered in zero-topology-window scenarios. When a downstream display device wakes up, the adjacent repeater reports zero downstream devices according to specifications. However, the upstream device, without verifying the topology, misjudges this as abnormal, triggering full-link re-authentication or disabling encryption output. This leads to issues such as black screens and reduced resolution in associated display clusters. Conventional meeting monitoring methods cannot pinpoint the root cause, causing the problem to recur and severely impacting meeting continuity and display quality. Summary of the Invention

[0004] To address the shortcomings of existing technologies, this invention proposes a multimedia information conference management method and system, which solves the problem that it only completes static topology configuration and does not embed real-time topology consistency verification into the encrypted link maintenance process, resulting in the inability to accurately determine dynamic topology changes during the conference.

[0005] To achieve the above objectives, the present invention provides the following technical solution: After performing SHA256 hash calculation on the EDID data block corresponding to each downstream device that directly displays the conference video screen, a pre-conference topology fingerprint is obtained. The pre-conference topology fingerprint is a unique identifier of the overall topology of the downstream devices before the conference. The EDID data block is a data structure containing the display capability information of the downstream devices. The initial value of the number of downstream devices corresponding to each repeater is converted into a binary vector. The result obtained by performing a bitwise XOR operation on all binary vectors in sequence is marked as the pre-conference anchor value. The repeater is a device in the distributed visualization link of multimedia information conference that receives upstream signals and forwards them to downstream devices. During the conference, repeaters with zero downstream devices in real time are marked as zero-topology window repeaters. The nearest branchable convergence node is found for each zero-topology window repeater. All convergence nodes are combined to obtain the minimum influence domain. The identifiers of all display clusters whose video signals are provided by the convergence nodes in the minimum influence domain are extracted and formed into an affected display cluster identifier set. The display cluster is a set of display devices formed by grouping downstream display devices according to wall area, function, etc. The number of real-time downstream devices corresponding to each repeater is converted into a binary vector. The result of performing a bitwise XOR operation on all binary vectors is marked as the in-meeting anchor value. A bitwise XOR operation is performed on the pre-meeting anchor value and the in-meeting anchor value. The result of this bitwise XOR operation is marked as the anchor difference. The EDID data block corresponding to each downstream device during the meeting operation is obtained. After performing SHA256 hash calculation, the in-meeting topology fingerprint is obtained.

[0006] Further, obtain the pre-meeting source cluster mapping matrix. If the identifier of the displayed cluster belongs to the set of affected displayed cluster identifiers, replace the row corresponding to the identifier of the displayed cluster in the pre-meeting source cluster mapping matrix with a placeholder source and obtain a new source cluster mapping matrix. Compare the pre-meeting source cluster mapping matrix and the new source cluster mapping matrix, record the row identifiers after the mapping relationship change and form a set of changed rows. The pre-meeting source cluster mapping matrix is ​​a mapping relationship benchmark between video sources and display clusters, which is predefined by the system administrator or automated configuration process during the pre-meeting preparation stage of the meeting management system. It belongs to the basic configuration data of the control plane and consists of 0s and 1s. The rows of the pre-meeting source cluster mapping matrix correspond to the display cluster identifiers, the columns correspond to the video sources, and the placeholder sources are local static graphs that are preset by the system in multimedia information meeting management and do not involve HDCP encryption.

[0007] Furthermore, SHA256 hash calculation is performed on the EDID data block corresponding to each downstream device to obtain the EDID fingerprint of the downstream device. The EDID fingerprints of all downstream devices are concatenated in order of device number, and then SHA256 hash calculation is performed on the concatenation result to obtain the pre-meeting topology fingerprint.

[0008] Furthermore, obtain the initial value of the number of downstream devices corresponding to each repeater. The initial value of the number of downstream devices is the number of its own downstream devices reported by the repeater through the HDCP topology reporting protocol after power-on initialization. All repeaters are then combined into a repeater set. The initial value of the number of downstream devices for each repeater is converted into a binary vector. Then, a bitwise XOR operation is performed on the binary vectors of all repeaters in the repeater set, as follows: The bitwise XOR operation is performed sequentially according to the repeater number order. The same bits of the binary vectors corresponding to the two repeaters are marked as 0, and the different bits are marked as 1. The result of the bitwise XOR operation between the first and second repeaters is then XORed with the third repeater, and so on, until the bitwise XOR operation is performed on the binary vectors of all repeaters in sequence. The final value is marked as the pre-meeting anchor value.

[0009] Furthermore, based on the repeater reporting set corresponding to each repeater in the repeater set, the static mapping relationship between the repeater and the corresponding downstream device set is recorded, and these relationships are organized into a tree structure to obtain the topology shadow tree. The repeater reporting set is the set of downstream devices detected by each repeater itself. The topology shadow tree is a tree structure that can intuitively present the link attribution between the repeater and the downstream device hierarchy structure, obtained by organizing the static mapping relationship between the repeater and the corresponding downstream device set into a tree structure.

[0010] Furthermore, for each zero-topology window repeater in the set of zero-topology window repeaters, the topology shadow tree is traced upwards to find the nearest and branchable convergence node on the data transmission path of the zero-topology window repeater. All convergence nodes are integrated to form the minimum influence domain. The minimum influence domain is the set of nodes formed after the convergence nodes are integrated to narrow the scope of zero-topology window problem handling.

[0011] Furthermore, the number of real-time downstream devices corresponding to each repeater in the repeater set is converted into a binary vector. A bitwise XOR operation is performed on the binary vector of the number of real-time downstream devices corresponding to all repeaters. After performing the bitwise XOR operation in sequence, the final value is marked as the anchor value in the meeting. Obtain the pre-meeting anchor value and the in-meeting anchor value, perform a bitwise XOR operation on the pre-meeting anchor value and the in-meeting anchor value, and mark the result of this bitwise XOR operation as the anchor difference. If the anchor difference is 0, it is determined that the topology state in the in-meeting is consistent with that in the pre-meeting. If the anchor difference is not 0, it is determined that the topology state in the in-meeting fluctuates.

[0012] Furthermore, the EDID data blocks corresponding to each downstream device during the meeting are obtained, and SHA256 hash calculation is performed on the EDID data blocks to obtain the real-time EDID fingerprint of the downstream device. The real-time EDID fingerprints of all downstream devices are concatenated in order of device number, and then SHA256 hash calculation is performed on the concatenation result to obtain the meeting topology fingerprint. The pre-meeting topological fingerprint and the in-meeting topological fingerprint are compared to generate a topological fingerprint Boolean value. If the pre-meeting topological fingerprint is equal to the in-meeting topological fingerprint, the topological fingerprint Boolean value is marked as 0; if the pre-meeting topological fingerprint is not equal to the in-meeting topological fingerprint, the topological fingerprint Boolean value is marked as 1. When both the anchoring difference and the topology fingerprint Boolean value are 0, it is determined that the topology status during the meeting is completely consistent with the pre-meeting baseline. When either the anchoring difference or the topology fingerprint Boolean value is 1, it is determined that there are unexpected fluctuations or changes in the topology status during the meeting.

[0013] Furthermore, the pre-meeting topology fingerprint, pre-meeting anchor value, zero topology window repeater set, affected display cluster identifier set, change row set, anchor difference, and topology fingerprint Boolean value are combined into a set, and this set is marked as the meeting management dossier.

[0014] Furthermore, a multimedia information-based conference management system is proposed to implement the multimedia information-based conference management method and system described above, including: The pre-meeting topology baseline module performs SHA256 hash calculation on the EDID data blocks of downstream devices to obtain EDID fingerprints. It then concatenates all the data blocks in the order of device numbers and performs SHA256 hash calculation again to generate the pre-meeting topology fingerprint. It obtains the initial value of the number of downstream devices of the repeater, converts it into a binary vector, performs a bitwise XOR operation on the binary vectors of all repeaters to obtain the pre-meeting anchor value, and records the static mapping relationship between the repeater and the downstream device set according to the repeater reporting set, organizing it into a tree-like topology shadow tree. The zero-topology monitoring module marks repeaters with zero real-time downstream devices in the repeater set as zero-topology window repeaters, forming a set of zero-topology window repeaters. It traces upwards in the topology shadow tree to the nearest branchable control convergence node of each zero-topology window repeater, integrates them to form the minimum influence domain, expands the minimum influence domain downwards, extracts the display cluster identifiers that receive video signals from it, and forms a set of affected display cluster identifiers. The source cluster mapping modification module obtains the pre-meeting source cluster mapping matrix. If the displayed cluster identifier belongs to the affected displayed cluster identifier set, the corresponding row of the displayed cluster in the matrix is ​​replaced with a placeholder source, and a new source cluster mapping matrix is ​​generated. The pre-meeting source cluster mapping matrix is ​​compared with the new source cluster mapping matrix, and the row identifiers of the mapping changes are recorded to form a set of changed rows. The topology consistency verification module converts the real-time downstream device count of the repeater into a binary vector, XORs it bitwise to obtain the in-meeting anchor value, performs a bitwise XOR operation on the pre-meeting and in-meeting anchor values ​​to obtain the anchor difference, obtains the real-time EDID data block of the downstream device, hashes it using SHA256, concatenates it, and then hashes it again to obtain the in-meeting topology fingerprint, compares the pre-meeting topology fingerprint with the in-meeting topology fingerprint, generates a topology fingerprint Boolean value, and determines whether the topology is consistent or whether there are any unexpected fluctuations or changes based on the anchor difference and the topology fingerprint Boolean value. The post-meeting dossier management module combines the pre-meeting topology fingerprint, pre-meeting anchor value, zero topology window repeater set, affected display cluster identifier set, change row set, anchor difference, and topology fingerprint Boolean value into a meeting management dossier. The meeting management dossier is stored in the post-meeting sedimentation and audit database. When similar issues occur in the future, the meeting management dossier is retrieved to provide a chain of evidence for the work order.

[0015] Compared with existing technologies, it has the following advantages: This solution proposes a multimedia information-based conference management method and system that solves the problems of ambiguous topological benchmarks and lack of unified traceability in traditional management by constructing a three-dimensional pre-conference topological benchmark system. The solution performs SHA256 hash calculation on the extended display identification data block of each downstream device to obtain an extended display identification data fingerprint. This fingerprint is then concatenated by device number and hashed again using SHA256 to generate a pre-conference topological fingerprint, providing a unique identifier for the overall topology of downstream devices before the conference. The initial value of the number of downstream devices of the repeater is converted into a binary vector, and then XORed bitwise to obtain the pre-conference anchor value. Combined with the topological shadow tree organized by the static mapping relationship between the repeater and downstream devices, a benchmark system of fingerprint + anchor value + tree structure is formed. This ensures that the pre-conference topological status is quantifiable and traceable, laying a precise foundation for in-conference topological verification and avoiding misjudgments caused by the lack of a benchmark in traditional methods. To address the zero-topology-window issue, the solution precisely narrows the scope of handling, abandoning the traditional extensive end-to-end approach. The solution marks repeaters with zero downstream devices as zero-topology-window repeaters, traces upwards in the topology shadow tree to the nearest controllable aggregation node, and integrates them to form a minimal impact domain. Only the display cluster identifiers affected by the video signal in this area are extracted to form the affected display cluster identifier set. This limits the impact of the problem to the smallest area, ensuring normal display of unaffected display clusters, avoiding widespread conference interruptions caused by traditional end-to-end resets, and significantly improving conference stability. By employing a local modification mechanism for source cluster mapping, the solution breaks the chain reaction of end-to-end re-authentication triggered by zero topology windows. The solution only replaces the row corresponding to the affected display cluster identifier in the pre-meeting source cluster mapping matrix with a placeholder source. This placeholder source points to a local static graph that does not involve high-bandwidth digital content protection encryption, eliminating the need to trigger upstream device re-authentication processes. This resolves the issue of black screens and resolution degradation in associated display clusters caused by upstream devices forcibly shutting down encrypted output or re-authentication after misjudging the transient nature of zero topology windows. Simultaneously, comparing the changed row sets in the old and new matrices provides a clear operational basis for subsequent traceability. Two-dimensional topology consistency verification improves the accuracy of judgment. The solution calculates the bitwise XOR result of the anchor value during the meeting and the anchor value before the meeting, and combines it with the topology fingerprint Boolean value generated by comparing the topology fingerprint during the meeting and the topology fingerprint before the meeting. It makes a two-dimensional judgment on whether there are unexpected fluctuations in the topology during the meeting. Compared with the traditional single indicator judgment, it effectively avoids misjudgment or omission and ensures that topology anomalies can be identified in a timely and accurate manner. Post-meeting dossier management enables end-to-end problem traceability and long-term optimization. The solution integrates key data such as pre-meeting topology fingerprints, zero-topology window repeater sets, and anchoring differences into meeting management dossier archives. Subsequent similar issues can be quickly retrieved to accelerate the localization of evidence chains. Based on the dossier data, frequently affected areas can be reviewed, and targeted optimization of device connections or configurations can be performed. This promotes the upgrade of meeting management from passive handling to proactive prevention, improving the long-term operational efficiency and reliability of the system. Attached Figure Description

[0016] Figure 1 This is a schematic diagram of the method flow of the present invention. Detailed Implementation

[0017] 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.

[0018] First Embodiment

[0019] This application provides a method for managing multimedia information-based conferences; As an embodiment of this application, the method specifically includes: After performing SHA256 hash calculation on the EDID data block corresponding to each downstream device that directly displays the conference video screen, a pre-conference topology fingerprint is obtained. The pre-conference topology fingerprint is a unique identifier of the overall topology of the downstream devices before the conference. The EDID data block is a data structure containing the display capability information of the downstream devices. The initial value of the number of downstream devices corresponding to each repeater is converted into a binary vector. The result obtained by performing a bitwise XOR operation on all binary vectors in sequence is marked as the pre-conference anchor value. The repeater is a device in the distributed visualization link of multimedia information conference that receives upstream signals and forwards them to downstream devices. During the conference, repeaters with zero downstream devices in real time are marked as zero-topology window repeaters. The nearest branchable convergence node is found for each zero-topology window repeater. All convergence nodes are combined to obtain the minimum influence domain. The identifiers of all display clusters whose video signals are provided by the convergence nodes in the minimum influence domain are extracted and formed into an affected display cluster identifier set. The display cluster is a set of display devices formed by grouping downstream display devices according to wall area, function, etc. The number of real-time downstream devices corresponding to each repeater is converted into a binary vector. The result of performing a bitwise XOR operation on all binary vectors is marked as the in-meeting anchor value. A bitwise XOR operation is performed on the pre-meeting anchor value and the in-meeting anchor value. The result of this bitwise XOR operation is marked as the anchor difference. The EDID data block corresponding to each downstream device during the meeting operation is obtained. After performing SHA256 hash calculation, the in-meeting topology fingerprint is obtained.

[0020] Second Embodiment

[0021] As a second embodiment of this application, this embodiment is implemented based on the first embodiment. Please refer to [link / reference]. Figure 1 The method provided in this embodiment includes the following steps: Step 1: In the distributed visualization link of a multimedia information conference, to ensure a clear benchmark for subsequent zero-topology window detection and in-conference topology consistency verification, the connection relationship of video link devices needs to be solidified before the conference starts, generating traceable topology identifiers and benchmark values. This avoids misjudgments caused by unclear topology benchmarks during the conference, as detailed below: For each downstream device d i The corresponding EDID data block performs SHA256 hash calculation to obtain the EDID fingerprint of the downstream device. Specifically, the downstream device refers to the device at the end of the video link used to present the conference content, such as splicing controllers, LED screens and LCD walls, which directly display video images. The EDID (Extended Display Identification Data) data block corresponding to the downstream device is a data structure stored in the display device, i.e., the downstream device, which contains information related to the display capabilities supported by the device, such as resolution, refresh rate, and color space. The EDID fingerprints of all downstream devices are concatenated in order of device number, and then SHA256 hash calculation is performed on the concatenation result to obtain the pre-meeting topology fingerprint. Specifically, through the process of individual EDID fingerprints to overall concatenation and then secondary hashing, a unique identifier representing the overall topology of downstream devices before the meeting is generated, providing an accurate benchmark for verifying whether the topology has undergone unexpected changes in the future. Get each repeater r i The initial value of the number of downstream devices is the number of downstream devices reported by the repeater after power-on initialization via the HDCP topology reporting protocol. For example, repeater r1 reports three downstream devices, repeater r2 reports two downstream devices, and all repeaters are grouped into a repeater set. Specifically, in the distributed visualization link of multimedia information conferences, repeaters are a type of device used to relay video signals, extend transmission distance, or enhance signal strength. Repeaters can receive video signals from upstream devices and forward them to downstream devices, playing the role of signal transmission and ensuring stable transmission of video signals to multiple terminals. The initial value of the number of downstream devices of the repeater can be understood as device count, which refers to the number of downstream devices detected and reported by the repeater itself, that is, the number of downstream devices currently connected to the repeater (such as display screens, lower-level repeaters, and other devices that need to obtain signals from the current repeater). The HDCP topology reporting protocol is an encryption protocol used to protect digital video content. The initial value of the number of downstream devices for each repeater is converted into a binary vector. For example, the 3 of repeater r1 is converted into a binary vector 11, and the 2 of repeater r2 is converted into a binary vector 10. The binary vectors of all repeaters in the repeater set are then subjected to a bitwise XOR operation, that is, the same binary bits are 0 and different bits are 1. For example, the bitwise XOR operation of 11 of r1 and 10 of r2 is performed, and the result is 01. Then the bitwise XOR operation of 01 is performed with the repeater r3, and so on. After the bitwise XOR operation is performed on the binary vectors of all repeaters, the final value is marked as the pre-anchor value. Specifically, assuming the repeater set = {r1, r2, r3, r4}, the initial values ​​of the number of downstream devices for these four repeaters are r1=3, r2=2, r3=1, and r4=4, respectively. After converting these initial values ​​of the number of downstream devices for these four repeaters into binary vectors, they are r1=0011, r2=0010, r3=0001, and r4=0100. Performing a bitwise XOR operation on the binary vectors of all repeaters in the repeater set, the result of the bitwise XOR operation between r1 and r2 is 0001. Then, performing a bitwise XOR operation between this result and r3, we get 0000. Finally, performing a bitwise XOR operation between 0000 and r4, we get 0100. At this point, 0100 is the pre-meeting anchor value. The pre-meeting anchor value is a unified benchmark value obtained by integrating through bitwise XOR operations before the meeting starts. It is used in subsequent meetings to verify whether the overall topology of the number of downstream devices of the repeaters has experienced unexpected fluctuations. Based on each repeater r in the repeater set i The corresponding repeater reporting set records the static mapping relationship between the repeater and the corresponding downstream device set, and organizes these relationships into a tree structure to obtain the topology shadow tree. For example, repeater r1 is connected to three downstream devices, namely d1, d2, and d3, and repeater r2 is connected to two downstream devices, namely d4 and d5. The topology shadow tree can intuitively present the hierarchical structure of repeaters and downstream devices. Specifically, the repeater reporting set refers to the set of downstream devices detected by each repeater itself. The device connection relationship before the meeting starts is solidified into a tree structure. Subsequent steps can clearly determine the link affiliation of the devices through the topology shadow tree, avoiding misjudgment of the placement range due to ambiguity in the device connection relationship.

[0022] Step Two: During the multimedia information conference operation phase, it is necessary to monitor the triggering status of zero-topology windows in the distributed link in real time, accurately locate relevant repeaters, and determine the minimum impact range. This provides a basis for subsequent localized handling, avoids full-link interference, and ensures normal conference display. Specifically: When a multimedia information conference is running, repeaters with a real-time downstream device count of 0 in the repeater set are marked as zero-topology window repeaters. All zero-topology window repeaters are then combined into a zero-topology window repeater set. Specifically, a zero-topology window refers to a situation where, during the multimedia information conference, for example, when a series of video walls has just been woken up from standby, the adjacent HDCP repeater briefly reports itself as a repeater but with a valid downstream device count of 0. Some upstream devices may misjudge this state and cause display abnormalities. Therefore, during the multimedia information conference, it is necessary to obtain the real-time downstream device count corresponding to the repeater in real time to identify the zero-topology window repeaters with a real-time downstream device count of 0, accurately filter out the repeaters that trigger the zero-topology window, clarify the source of the problem, and provide target objects for subsequent narrowing down the scope of handling. For each zero-topology window repeater in the set of zero-topology window repeaters, trace upwards in the topology shadow tree to find the nearest branchable and controllable aggregation node on the data transmission path of the zero-topology window repeater, i.e., the first upstream aggregation node. Integrate all aggregation nodes to form the minimum influence domain. Specifically, assuming that the first upstream aggregation node of zero-topology window repeaters r1 and r3 in the topology shadow tree is node A, then the minimum influence domain is node A. The minimum influence domain is the set of all upstream aggregation nodes corresponding to the zero-topology window repeater. By using the minimum influence domain, the scope of handling is reduced from the entire link to the smallest area composed of upstream aggregation nodes, avoiding unnecessary interference to the normal display of the meeting due to the excessive scope of handling, and improving the accuracy and efficiency of handling. In the topology shadow tree, the minimum influence domain is expanded downwards to extract the identifiers of all display clusters whose video signals are provided by the aggregation node in the minimum influence domain, forming an affected display cluster identifier set. Specifically, the display clusters are grouped by the wall area, function, etc., to group downstream display devices. The display cluster identifier set is the set of numbers of the affected display clusters. For example, aggregation node A in the minimum influence domain provides signals to display clusters numbered 1 and 3, so the affected display cluster identifier set = {1, 3}, that is, the identifiers of the affected display clusters are determined. The affected display cluster identifier set further clarifies the range of display clusters affected by the zero topology window, providing a precise range definition for subsequent steps to modify the mapping relationship only for the affected display clusters, ensuring the operability of localized processing.

[0023] Step 3: During the meeting, the range of display clusters affected by the zero topology window has been identified. Only the mapping relationship between the video source and the display cluster needs to be locally modified for these affected clusters. A placeholder source without HDCP encryption should temporarily replace the original video source, while maintaining the encryption status and output mode of the upstream devices. This is to cut off the chain reaction of full-link re-authentication caused by the zero topology window and ensure normal display in unaffected areas, as detailed below: Obtain the pre-meeting source cluster mapping matrix. The pre-meeting source cluster mapping matrix is ​​the baseline for the mapping relationship between video sources and display clusters, which is predefined by the system administrator or automated configuration process during the pre-meeting preparation stage of the meeting management system. It belongs to the basic configuration data of the control plane of the meeting management system. The pre-meeting source cluster mapping matrix consists of 0 and 1. The rows correspond to the identifiers of the display clusters (the set of display devices grouped by region and function in the meeting, such as the main venue large screen cluster and the sub-venue small screen cluster). The columns correspond to different video sources (such as the speaker's computer signal source and the video conferencing signal source). If a certain row and column in the matrix is ​​1, it means that the display cluster subscribes to the corresponding video source, that is, the content of the video source is delivered to this display cluster. And each row has only one 1 to ensure that each display cluster receives only one unique video source. If the identifier of a display cluster belongs to the set of identifiers of affected display clusters, then the row corresponding to the identifier of that display cluster in the pre-meeting source cluster mapping matrix is ​​replaced with a placeholder source. Specifically, the placeholder source is a local static image video source preset by the system. The placeholder source points to a local static image that does not involve HDCP encryption, such as the conference background image, which does not require HDCP encryption. By modifying only the display clusters affected by the zero topology window, the unaffected display clusters still use the original video source, ensuring that most areas can be displayed normally and preventing local problems from causing full-link re-authentication. The placeholder source is a local static image and does not involve HDCP encryption. Therefore, the encryption status and committed output mode of the upstream device can remain unchanged, and there is no need to re-authenticate due to source change. This mechanism prevents the chain reaction of upstream re-authentication caused by the zero topology window, which leads to downstream devices black screen or reduced resolution. By partially modifying the row, the potential display abnormalities in the affected areas are resolved without affecting the normal video source and encrypted link in the unaffected areas, ensuring the overall display stability of the conference and achieving fine-grained control over the affected display clusters. This is different from the coarse processing of traditional full-link reset. While solving local problems, it maintains the normal operation of other parts of the system to the greatest extent. The pre-meeting source cluster mapping matrix after the mapping relationship is changed is marked as the new source cluster mapping matrix. The pre-meeting source cluster mapping matrix and the new source cluster mapping matrix are compared, and the row identifiers after the mapping relationship change are recorded and formed into a set of changed rows. The set of changed rows can accurately record the modified display cluster identifiers, providing clear change range data for subsequent steps of closed-loop management and document release, so that post-meeting archiving and review can clearly trace the operation objects of this zero topology window handling.

[0024] Step 4: When the multimedia information conference is running, the number of real-time downstream devices corresponding to each repeater in the repeater set is converted into a binary vector. A bitwise XOR operation is performed on the binary vectors of the number of real-time downstream devices corresponding to all repeaters. After performing the bitwise XOR operation in sequence, the final value is marked as the in-conference anchor value. Specifically, the generation method of the in-conference anchor value is the same as that of the pre-conference anchor value. However, the original input data of the pre-conference anchor value is the initial value of the number of downstream devices before the start of the conference, while the original input data of the in-conference anchor value is the real-time number of downstream devices during the conference. The in-conference anchor value is a unified value obtained by the bitwise XOR operation, representing the topology status during the conference. This provides a basis for subsequent comparison with the pre-conference anchor value and verification of topology consistency. The pre-meeting and in-meeting anchor values ​​are obtained. A bitwise XOR operation is performed on the pre-meeting and in-meeting anchor values. The result of this bitwise XOR operation is marked as the anchor difference. If the anchor difference is 0, it is determined that the in-meeting topology is consistent with the pre-meeting state. If the anchor difference is not 0, it is determined that the in-meeting topology fluctuates. Specifically, the anchor difference is the bitwise XOR result of the in-meeting anchor value and the pre-meeting anchor value, which is used to determine whether the in-meeting topology is consistent with the pre-meeting state. By judging the anchor difference, it is possible to quickly verify whether the in-meeting topology has changed unexpectedly due to the zero topology window, providing direct evidence for the decoupling of topology consistency and encryption activation. Obtain the data from each downstream device during the conference operation. i The corresponding EDID data block is subjected to SHA256 hash calculation to obtain the real-time EDID fingerprint of the downstream device. The real-time EDID fingerprints of all downstream devices are concatenated in order of device number, and then SHA256 hash calculation is performed on the concatenation result to obtain the topology fingerprint of the meeting. The pre-meeting topological fingerprint and the in-meeting topological fingerprint are compared to generate a topological fingerprint Boolean value. If the pre-meeting topological fingerprint is equal to the in-meeting topological fingerprint, the topological fingerprint Boolean value is marked as 0. If the pre-meeting topological fingerprint is not equal to the in-meeting topological fingerprint, the topological fingerprint Boolean value is marked as 1. Specifically, the topology is verified from the perspective of the overall device set to see if it has changed. This complements the anchor value verification. The topological fingerprint focuses on whether the individual device has changed, while the anchor value focuses on whether the number of downstream repeaters has fluctuated. When both the anchoring difference and the topology fingerprint Boolean value are 0, it is determined that the topology status during the meeting is completely consistent with the pre-meeting baseline. When either the anchoring difference or the topology fingerprint Boolean value is 1, it is determined that there are unexpected fluctuations or changes in the topology status during the meeting. When the determination result is that there are unexpected fluctuations or changes in the topology status during the meeting, it indicates that the topology structure of the meeting link has undergone unexpected changes in two dimensions: device composition (whether the overall characteristics of the devices have changed as reflected by the topology fingerprint) or the relationship of the number of downstream devices of the repeater (whether the collective characteristics of the number of downstream devices connected to the repeater have fluctuated as reflected by the anchoring value). It is necessary to investigate the repeater's operating status, the physical connection and EDID configuration of downstream devices, and the topology reporting interaction between devices in the meeting link, locate the specific cause of the topology anomaly, and carry out targeted handling.

[0025] Step 5: After the meeting, quantitative evidence strongly correlated with the zero-topology window needs to be integrated into the meeting management dossier and connected to the post-meeting archiving and auditing stage of the multimedia information meeting management process. This will enable full-process traceability and closed-loop management of zero-topology window issues, providing data support for subsequent problem review and equipment upgrades. Specifically: The pre-meeting topology fingerprint, pre-meeting anchor value, zero topology window repeater set, affected display cluster identifier set, change row set, anchor difference, and topology fingerprint Boolean value are combined into a set, and this set is marked as the meeting management dossier. Specifically, the meeting management dossier is an unambiguous and traceable set of evidence, providing a unified basis for tracing the zero topology window issue throughout the post-meeting process. The meeting management files are stored in the post-meeting data storage and audit database of the multimedia information-based meeting management system as an important part of the meeting operation record, thus meeting the compliance and traceability requirements of meeting management. When similar zero-topology window issues occur later, the corresponding meeting management dossier is retrieved. The data in the meeting management dossier is used to provide a computable and reproducible chain of evidence for the issue work order, which can accelerate the problem location and resolution. For example, if a certain display cluster reappears in a new issue, the common problems of repeaters in that area can be analyzed by combining historical dossiers. If the identifier of a certain display cluster frequently appears in the set of identifiers of affected display clusters, it can be determined from the volume data that there is room for optimization in the device connection or configuration of that area, providing data guidance for transformation work such as physical connection adjustment and device firmware upgrade. For example, if a certain display cluster is affected multiple times due to the zero topology window, the power-on wake-up logic and topology reporting mechanism of its upstream repeater can be checked in a targeted manner. Specifically, by using meeting management files, a closed-loop management system is implemented to handle zero-topology-window issues from the moment they are detected and resolved during the meeting to the subsequent archiving, review, and improvement. This transforms the experience gained from handling zero-topology-window issues in a single meeting into a basis for long-term optimization of the meeting system, thereby enhancing the sustainability and accuracy of multimedia information-based meeting management.

[0026] Third Embodiment

[0027] A multimedia information-based conference management system is proposed to implement the multimedia information-based conference management method described above, including: The pre-meeting topology baseline module performs SHA256 hash calculation on the EDID data blocks of downstream devices to obtain EDID fingerprints. It then concatenates all the data blocks in the order of device numbers and performs SHA256 hash calculation again to generate the pre-meeting topology fingerprint. It obtains the initial value of the number of downstream devices of the repeater, converts it into a binary vector, performs a bitwise XOR operation on the binary vectors of all repeaters to obtain the pre-meeting anchor value, and records the static mapping relationship between the repeater and the downstream device set according to the repeater reporting set, organizing it into a tree-like topology shadow tree. The zero-topology monitoring module marks repeaters with zero real-time downstream devices in the repeater set as zero-topology window repeaters, forming a set of zero-topology window repeaters. It traces upwards in the topology shadow tree to the nearest branchable control convergence node of each zero-topology window repeater, integrates them to form the minimum influence domain, expands the minimum influence domain downwards, extracts the display cluster identifiers that receive video signals from it, and forms a set of affected display cluster identifiers. The source cluster mapping modification module obtains the pre-meeting source cluster mapping matrix. If the displayed cluster identifier belongs to the affected displayed cluster identifier set, the corresponding row of the displayed cluster in the matrix is ​​replaced with a placeholder source, and a new source cluster mapping matrix is ​​generated. The pre-meeting source cluster mapping matrix is ​​compared with the new source cluster mapping matrix, and the row identifiers of the mapping changes are recorded to form a set of changed rows. The topology consistency verification module converts the real-time downstream device count of the repeater into a binary vector, XORs it bitwise to obtain the in-meeting anchor value, performs a bitwise XOR operation on the pre-meeting and in-meeting anchor values ​​to obtain the anchor difference, obtains the real-time EDID data block of the downstream device, hashes it using SHA256, concatenates it, and then hashes it again to obtain the in-meeting topology fingerprint, compares the pre-meeting topology fingerprint with the in-meeting topology fingerprint, generates a topology fingerprint Boolean value, and determines whether the topology is consistent or whether there are any unexpected fluctuations or changes based on the anchor difference and the topology fingerprint Boolean value. The post-meeting dossier management module combines the pre-meeting topology fingerprint, pre-meeting anchor value, zero topology window repeater set, affected display cluster identifier set, change row set, anchor difference, and topology fingerprint Boolean value into a meeting management dossier. The meeting management dossier is stored in the post-meeting sedimentation and audit database. When similar issues occur in the future, the meeting management dossier is retrieved to provide a chain of evidence for the work order.

[0028] The above embodiments are only used to illustrate the technical methods of the present invention and are not intended to limit it. Although the present invention has been described in detail with reference to preferred embodiments, those skilled in the art should understand that modifications or equivalent substitutions can be made to the technical methods of the present invention without departing from the spirit and scope of the technical methods of the present invention.

Claims

1. A multimedia information-based conference management method, characterized in that, include: After performing SHA256 hash calculation on the EDID data block corresponding to each downstream device that directly displays the conference video screen, a pre-conference topology fingerprint is obtained. The pre-conference topology fingerprint is a unique identifier of the overall topology of the downstream devices before the conference. The EDID data block is a data structure containing the display capability information of the downstream devices. The initial value of the number of downstream devices corresponding to each repeater is converted into a binary vector. The result obtained by performing a bitwise XOR operation on all binary vectors in sequence is marked as the pre-conference anchor value. The repeater is a device in the distributed visualization link of multimedia information conference that receives upstream signals and forwards them to downstream devices. During the conference, repeaters with zero downstream devices in real time are marked as zero-topology window repeaters. The nearest branchable convergence node is found for each zero-topology window repeater. All convergence nodes are combined to obtain the minimum influence domain. The identifiers of all display clusters whose video signals are provided by the convergence nodes in the minimum influence domain are extracted and formed into an affected display cluster identifier set. The display cluster is a set of display devices formed by grouping downstream display devices according to wall area, function, etc. The number of real-time downstream devices corresponding to each repeater is converted into a binary vector. The result of performing a bitwise XOR operation on all binary vectors is marked as the in-meeting anchor value. A bitwise XOR operation is performed on the pre-meeting anchor value and the in-meeting anchor value. The result of this bitwise XOR operation is marked as the anchor difference. The EDID data block corresponding to each downstream device during the meeting operation is obtained. After performing SHA256 hash calculation, the in-meeting topology fingerprint is obtained.

2. The multimedia information conference management method according to claim 1, characterized in that, Also includes: Obtain the pre-meeting source cluster mapping matrix. If the identifier of the displayed cluster belongs to the set of affected displayed cluster identifiers, replace the corresponding row of the identifier of the displayed cluster in the pre-meeting source cluster mapping matrix with a placeholder source and obtain a new source cluster mapping matrix. Compare the pre-meeting source cluster mapping matrix and the new source cluster mapping matrix, record the row identifiers after the mapping relationship changes, and form a set of changed rows. The pre-meeting source cluster mapping matrix is ​​a mapping relationship benchmark between video sources and display clusters, which is predefined by the system administrator or automated configuration process during the pre-meeting preparation stage of the meeting management system. It belongs to the basic configuration data of the control plane and consists of 0s and 1s. The rows of the pre-meeting source cluster mapping matrix correspond to the display cluster identifiers, the columns correspond to the video sources, and the placeholder sources are local static graphs that are preset by the system in multimedia information meeting management and do not involve HDCP encryption.

3. The multimedia information conference management method according to claim 2, characterized in that, The calculation method for pre-meeting topological fingerprints includes: Perform SHA256 hash calculation on the EDID data block corresponding to each downstream device to obtain the EDID fingerprint of the downstream device. Concatenate all the EDID fingerprints of the downstream devices in the order of device number, and then perform SHA256 hash calculation on the concatenation result to obtain the pre-meeting topology fingerprint.

4. The multimedia information conference management method according to claim 3, characterized in that, include: Get the initial value of the number of downstream devices corresponding to each repeater. The initial value of the number of downstream devices is the number of its own downstream devices reported by the repeater through the HDCP topology reporting protocol after power-on initialization. Combine all repeaters into a repeater set. The initial value of the number of downstream devices for each repeater is converted into a binary vector. Then, a bitwise XOR operation is performed on the binary vectors of all repeaters in the repeater set, as follows: The bitwise XOR operation is performed sequentially according to the repeater number order. The same bits of the binary vectors corresponding to the two repeaters are marked as 0, and the different bits are marked as 1. The result of the bitwise XOR operation between the first and second repeaters is then XORed with the third repeater, and so on, until the bitwise XOR operation is performed on the binary vectors of all repeaters in sequence. The final value is marked as the pre-meeting anchor value.

5. The multimedia information conference management method according to claim 4, characterized in that, include: Based on the repeater reporting set corresponding to each repeater in the repeater set, the static mapping relationship between the repeater and the corresponding downstream device set is recorded, and these relationships are organized into a tree structure to obtain the topology shadow tree. The repeater reporting set is the set of downstream devices detected by each repeater itself. The topology shadow tree is a tree structure that can intuitively show the link attribution between the repeater and the downstream device hierarchy by organizing the static mapping relationship between the repeater and the corresponding downstream device set into a tree structure.

6. The multimedia information conference management method according to claim 5, characterized in that, include: For each zero-topology window repeater in the set of zero-topology window repeaters, trace upwards in the topology shadow tree to find the nearest and branchable convergence node on the data transmission path of the zero-topology window repeater. Integrate all convergence nodes to form the minimum influence domain. The minimum influence domain is the set of nodes formed by integrating the convergence nodes to narrow the scope of zero-topology window problem handling.

7. The multimedia information conference management method according to claim 6, characterized in that, include: Convert the number of real-time downstream devices corresponding to each repeater in the repeater set into a binary vector. Perform a bitwise XOR operation on the binary vector of the number of real-time downstream devices corresponding to all repeaters. After performing the bitwise XOR operation in sequence, mark the final value as the anchor value in the meeting. Obtain the pre-meeting anchor value and the in-meeting anchor value, perform a bitwise XOR operation on the pre-meeting anchor value and the in-meeting anchor value, and mark the result of this bitwise XOR operation as the anchor difference. If the anchor difference is 0, it is determined that the topology state in the in-meeting is consistent with that in the pre-meeting. If the anchor difference is not 0, it is determined that the topology state in the in-meeting fluctuates.

8. The multimedia information conference management method according to claim 7, characterized in that, include: Obtain the EDID data blocks corresponding to each downstream device during the meeting, perform SHA256 hash calculation on the EDID data blocks to obtain the real-time EDID fingerprint of the downstream device, concatenate the real-time EDID fingerprints of all downstream devices in order of device number, and then perform SHA256 hash calculation on the concatenation result to obtain the meeting topology fingerprint. The pre-meeting topological fingerprint and the in-meeting topological fingerprint are compared to generate a topological fingerprint Boolean value. If the pre-meeting topological fingerprint is equal to the in-meeting topological fingerprint, the topological fingerprint Boolean value is marked as 0; if the pre-meeting topological fingerprint is not equal to the in-meeting topological fingerprint, the topological fingerprint Boolean value is marked as 1. When both the anchoring difference and the topology fingerprint Boolean value are 0, it is determined that the topology status during the meeting is completely consistent with the pre-meeting baseline. When either the anchoring difference or the topology fingerprint Boolean value is 1, it is determined that there are unexpected fluctuations or changes in the topology status during the meeting.

9. The multimedia information conference management method according to claim 8, characterized in that, include: The pre-meeting topology fingerprint, pre-meeting anchor value, zero topology window repeater set, affected display cluster identifier set, change row set, anchor difference, and topology fingerprint Boolean value are combined into a set, and this set is marked as the meeting management dossier.

10. A multimedia information-based conference management system, used to implement the multimedia information-based conference management method as described in any one of claims 1-9, characterized in that, include: The pre-meeting topology baseline module performs SHA256 hash calculation on the EDID data blocks of downstream devices to obtain EDID fingerprints. It then concatenates all the data blocks in the order of device numbers and performs SHA256 hash calculation again to generate the pre-meeting topology fingerprint. It obtains the initial value of the number of downstream devices of the repeater, converts it into a binary vector, performs a bitwise XOR operation on the binary vectors of all repeaters to obtain the pre-meeting anchor value, and records the static mapping relationship between the repeater and the downstream device set according to the repeater reporting set, organizing it into a tree-like topology shadow tree. The zero-topology monitoring module marks repeaters with zero real-time downstream devices in the repeater set as zero-topology window repeaters, forming a set of zero-topology window repeaters. It traces upwards in the topology shadow tree to the nearest branchable control convergence node of each zero-topology window repeater, integrates them to form the minimum influence domain, expands the minimum influence domain downwards, extracts the display cluster identifiers that receive video signals from it, and forms a set of affected display cluster identifiers. The source cluster mapping modification module obtains the pre-meeting source cluster mapping matrix. If the displayed cluster identifier belongs to the affected displayed cluster identifier set, the corresponding row of the displayed cluster in the matrix is ​​replaced with a placeholder source, and a new source cluster mapping matrix is ​​generated. The pre-meeting source cluster mapping matrix is ​​compared with the new source cluster mapping matrix, and the row identifiers of the mapping changes are recorded to form a set of changed rows. The topology consistency verification module converts the real-time downstream device count of the repeater into a binary vector, XORs it bitwise to obtain the in-meeting anchor value, performs a bitwise XOR operation on the pre-meeting and in-meeting anchor values ​​to obtain the anchor difference, obtains the real-time EDID data block of the downstream device, hashes it using SHA256, concatenates it, and then hashes it again to obtain the in-meeting topology fingerprint, compares the pre-meeting topology fingerprint with the in-meeting topology fingerprint, generates a topology fingerprint Boolean value, and determines whether the topology is consistent or whether there are any unexpected fluctuations or changes based on the anchor difference and the topology fingerprint Boolean value. The post-meeting dossier management module combines the pre-meeting topology fingerprint, pre-meeting anchor value, zero topology window repeater set, affected display cluster identifier set, change row set, anchor difference, and topology fingerprint Boolean value into a meeting management dossier. The meeting management dossier is stored in the post-meeting sedimentation and audit database. When similar issues occur in the future, the meeting management dossier is retrieved to provide a chain of evidence for the work order.

Images