Method and system for multi-platform access of terminal equipment

Abstract

The present invention belongs to the technical field of audio and video conferencing methods and systems, and specifically relates to a method and system for multi-platform access of terminal devices; the method includes: obtaining information on installed and uninstalled conference application software; identifying applications required for the current conference; determining whether the installation package is retained locally; obtaining operating data and network status before uninstallation; comparing the current and historical network environments, and determining the availability of cached packages in combination with operating records; and deciding to call the cache or re-download and install based on the judgment results. The system includes multiple functional modules, which respectively implement information acquisition, operating data extraction, network status analysis, and decision execution. The invention can intelligently switch installation paths according to network fluctuations and historical application status, thereby improving conference access efficiency and system stability, and is particularly suitable for flexible deployment scenarios of multi-platform conference terminals.

Description

Technical Field

[0001] The present invention belongs to the technical field of audio and video conferencing methods and systems, and particularly relates to a method and system for multi-platform access of terminal equipment. Background Art

[0002] In recent years, with the continuous development of audio and video communication technologies and the digital transformation of enterprise work methods, conference terminal equipment has become a key infrastructure for remote collaboration. This is especially true in multi-platform office scenarios, where enterprises coexist with self-built video conferencing platforms, public cloud conferencing services (such as Zoom, Teams, and Tencent Meeting), and third-party audio and video service systems. The compatibility and accessibility of conference terminal equipment are receiving increasing attention.

[0003] Most existing conference terminal devices are primarily designed for single-platform adaptation. Their hardware and software resource configurations, communication protocols, and authentication mechanisms are typically optimized for specific conference platforms, which limits the device's flexibility and versatility to a certain extent. When users need to switch between different conference systems or access multiple platforms simultaneously, they often need to deploy multiple terminal devices or rely on additional auxiliary equipment such as soft switches and transcoding servers. This not only increases deployment and maintenance costs but also leads to increased system latency and decreased stability. Furthermore, due to differences between platforms in audio and video codec standards, access protocols, signaling processing procedures, and user authentication methods, existing technologies struggle to achieve seamless adaptation across multiple platforms.

[0004] Especially in industries like government, finance, and education, the conferencing environment is more complex, requiring both private deployment platforms and access to external public conferencing systems. This places higher demands on the multi-platform compatibility of conferencing terminals. Dynamically identifying and integrating multiple mainstream conferencing platforms within a unified terminal architecture, enabling fast, stable, and secure multi-platform access, has become a pressing technical challenge.

[0005] Therefore, there is an urgent need for a method and system for multi-platform access of conference terminal devices. By improving the connection architecture, access strategy and protocol adaptation mechanism, the compatibility and intelligent recognition capabilities of conference terminals for multiple audio and video platforms can be improved, thereby improving the access efficiency and collaborative experience of remote conferences and meeting actual usage needs in various scenarios. Summary of the Invention

[0006] In view of the above problems, the present invention aims to provide a method for multi-platform access of a terminal device, comprising the following steps:

[0007] S1. Obtain the conference application software installed on the conference terminal device:

[0008] Reading the conference application software previously installed in the conference terminal device and marking it as an alternative;

[0009] S2. Determine the conference application software required by the current device:

[0010] Identify the conference application software required for the current conference activity and designate it as the conference application software to be loaded;

[0011] S3. Evaluate whether the installation package of the conference application software already exists in the cache:

[0012] First, determine whether the conference application software has been uninstalled. If not, directly call the application software to access the conference; if it has been uninstalled, execute the next step;

[0013] S4. Check whether the installation package of the conference application software is retained in the cache:

[0014] Determine whether the installation package of the conference application software is saved in the cache before uninstallation; if not, obtain the installation package of the conference application software from the cloud, and call to enter the conference after the installation is completed;

[0015] S5. If the installation package has been cached, obtain the running data before uninstallation:

[0016] Extract the usage records and operation stability data of the conference application software before the last uninstallation as a reference;

[0017] S6. Use the above data to compare the current network environment with the last operating environment to see if they are consistent:

[0018] Determine whether the current access network status is the same as the network environment of the conference application software before uninstallation; based on the determination result, execute one of installing the software using a cache installation package, downloading a cloud installation package to install the software, and re-downloading the official version to install the software.

[0019] In a preferred technical solution, the “executing one of installing the software using a cached installation package, downloading a cloud installation package, or re-downloading the official version based on the judgment result” includes:

[0020] S7. If they are consistent, determine whether there was an abnormality in the last operation:

[0021] If no failures occurred during the last operation, you can use the cached installation package to complete the installation and call the conference application software to join the meeting; if there was an abnormality during the last operation, you need to download the cloud installation package and reinstall it;

[0022] S8. If the network environments are inconsistent, compare the network status levels of the two:

[0023] Compare the current network environment with the environment before uninstallation and classify the new network into three situations: better than the original network, equal to the original network, or worse than the original network:

[0024] S81. The new network is better than the original network:

[0025] Determine whether the abnormal operation of the conference application software before uninstallation is caused by network problems. If there is an abnormality, download a new installation package directly from the cloud. If there is no abnormality, continue to use the cached installation package;

[0026] S82. The new network is equal to the original network:

[0027] Determine whether the abnormal operation is caused by network problems. If there is no abnormality, use the cached installation package. If there is an abnormality, obtain the installation package from the cloud and reinstall it;

[0028] S83. The new network is inferior to the original network:

[0029] You need to re-download and install the latest official version of the conference application software installation package, and then join the meeting after completion.

[0030] In a preferred technical solution, S1 includes obtaining the installation record and uninstallation record of the conference application in the conference terminal device, the installation record includes the name of the application software and the time point of installation completion, and the uninstallation record includes the name of the application software and the time point of uninstallation completion.

[0031] In a preferred technical solution, the step S4 includes querying the uninstallation record of the conference application software to be loaded. If the installation package at that time is found to be retained, it is determined to be cached. If not, it is determined to be not cached.

[0032] In a preferred technical solution, the S5 includes counting the historical running time of the conference application software to be loaded and the last running time before uninstallation.

[0033] In a preferred technical solution, the historical running time is used as the benchmark time, and is compared with the last running time for judgment.

[0034] In a preferred technical solution, if the difference between the two is less than or equal to a predetermined threshold, it is considered that the last operation was normal; if the difference exceeds the predetermined threshold, it is considered that the last operation was abnormal.

[0035] In a preferred technical solution, both S81 and S82 include determining whether the last operation was abnormal. The determination step includes obtaining the end time point of the last operation and extracting the network status or usage within half an hour before the time. On this basis, the new and old network statuses are compared to determine whether it is caused by a network problem.

[0036] In a preferred technical solution, when determining whether the anomaly is caused by network reasons, it also includes further extracting user feedback information and determining the causal relationship based on the comparison between the anomaly description in the feedback and the actual anomaly time.

[0037] In a preferred technical solution, in steps S7, S81, and S82, if it is determined that downloading from the cloud is not necessary, the relevant data is automatically integrated to generate an access request, and the cache installation package is called to complete the installation and access of the conference application software.

[0038] The present invention also provides a terminal device multi-platform access system to implement the method, including:

[0039] A first acquisition module is used to acquire the conference application software installed in the conference terminal device;

[0040] The second acquisition module is used to determine the conference application software required to be called for the current conference task;

[0041] A determination module, used to determine whether the installation package of the required conference application software has been saved in the device cache;

[0042] The third acquisition module is used to obtain the operation data before uninstallation and the network status information when it was last used;

[0043] A first comparison module is used to compare whether the network environment before uninstallation is consistent with the current network environment;

[0044] The second comparison module is used to compare the quality of the new and old network environments;

[0045] The fourth acquisition module is used to obtain the historical running time and last usage time of the conference application software;

[0046] Statistics module, used to count changes in network status and fluctuations during use;

[0047] The execution module is used to summarize all the above monitoring conclusions and analysis results and make corresponding installation and access operations.

[0048] Beneficial effects

[0049] The present invention provides a method and system for multi-platform access of conference terminal devices, which can effectively improve the adaptability and access efficiency of conference terminals to various conference application software, and has the following beneficial effects:

[0050] 1. The present invention can quickly determine the user's frequently used conference application software by identifying and analyzing the historical installation records of the device, avoiding repeated downloads and redundant matching, and improving access response speed.

[0051] 2. The present invention is equipped with a cache detection mechanism and an uninstall package judgment module, which can automatically switch the installation mode based on whether the installation package is retained in the cache, complete local rapid recovery installation without relying on the cloud, and improve the system's independent operation capability.

[0052] 3. By introducing a historical operation data and network status comparison mechanism, the present invention can predict the reliability of the cached installation package before access, and automatically choose to use the cached installation package or re-download it based on the last operation result, thereby avoiding known problems and improving operation stability.

[0053] 4. The present invention compares the levels of the current network environment with the network environment before uninstallation, combines operation abnormality judgment and user feedback information, and realizes multi-dimensional tracing and intelligent judgment of the causes of operation abnormalities, which significantly enhances the system's adaptability and fault tolerance.

[0054] 5. Without the need for cloud intervention, the present invention can achieve rapid reinstallation and intelligent call of uninstalled conference software, reducing network occupancy and access delay, and is particularly suitable for usage scenarios with large fluctuations in network conditions or frequent access needs.

[0055] In summary, the present invention not only improves the intelligence level and execution efficiency of multi-platform access of conference terminals, but also enhances the flexibility and stability of the system while ensuring user access experience, and has strong practical value and promotion prospects. BRIEF DESCRIPTION OF THE DRAWINGS

[0056] Figure 1 Schematic diagram of the method flow of the present invention;

[0057] Figure 2 Schematic diagram of the system structure of the present invention. DETAILED DESCRIPTION

[0058] In order to deepen the understanding of the present invention, the present invention will be further described in detail below with reference to the examples. The examples are only used to explain the present invention and do not constitute a limitation on the scope of protection of the present invention.

[0059] Example 1

[0060] according to Figure 1 As shown, this embodiment provides a method for multi-platform access of terminal devices, which is suitable for conference terminal environments with multiple conference application software adaptation requirements. It aims to achieve rapid access, intelligent judgment and cache reuse of different conference platforms to improve conference response efficiency and terminal operation stability.

[0061] The specific steps include:

[0062] Step S1: Obtain the conference application software installed in the conference terminal device:

[0063] The system first scans and identifies previously installed conference applications on the conference terminal devices, extracting their installation and uninstallation records. Installation records include the application name and the corresponding installation completion time, while uninstallation records include the application name and the corresponding uninstallation completion time. The identification results serve as a candidate for subsequent loading decisions.

[0064] Step S2: Determine the conference application software required by the current device:

[0065] Based on the conference scheduling information or user-specified content, the system determines the conference application software required to be called for the current conference activity, marks it as an object to be loaded, and enters the loading evaluation process.

[0066] Step S3: Evaluate whether the installation package of the conference application software already exists in the cache:

[0067] First, determine whether the app has been uninstalled. If not, you can directly call the existing app on the device to access the meeting without reloading it. If it has been uninstalled, proceed to the next step.

[0068] Step S4: Check whether the installation package of the conference application software is retained in the cache:

[0069] Checks the system's uninstall history to see if the previous installation package is retained. If so, the system considers the installation package cached. If not, the system automatically pulls the required package from the cloud and completes the installation before entering the meeting process.

[0070] Step S5: If the installation package has been cached, obtain the running data before uninstallation:

[0071] If the cache exists, the system will further extract the running data of the conference application software before uninstallation, including historical running time, last running time, stability records, error logs, etc.

[0072] The historical running time is used as a benchmark value and compared with the last running time. If the two are similar, the operation is stable. If the difference is obvious, abnormal termination or freezing may occur.

[0073] Step S6: Use the above data to compare the current network environment with the last operating environment to see if they are consistent:

[0074] The system extracts basic information about the current access network (including signal strength, stability level, network type, etc.) and compares and analyzes it with the network status recorded when the conference application was run before uninstallation.

[0075] Construct a judgment function , used to output whether the cached installation package can be used currently. Its core input variables include:

[0076] : The stability rate of the last operation (a value between 0 and 1);

[0077] : Current network environment parameter vector (including bandwidth, delay, and packet loss rate);

[0078] : The network environment parameter vector when last used;

[0079] : The difference between the current network and the network before uninstallation (Euclidean distance);

[0080] : Network difference threshold (empirically set).

[0081] Determination formula:

[0082]

[0083] in:

[0084] : Whether the cached installation package is available (1 means available, 0 means unavailable);

[0085] : Stability score threshold, the default value is 0.8;

[0086] : Network environment similarity tolerance, set according to network parameter dimensions.

[0087] Step S7: If they are consistent, determine whether there was an abnormality in the last operation:

[0088] When the two network states are consistent, the system uses the last run as a reference. If the last run was stable and without anomalies, you can continue to install the app using the locally cached installation package. If an error is found in the run log or an abnormal termination is detected, the local cache is automatically abandoned and the official installation package is obtained from the cloud for reinstallation.

[0089] Step S8: If the network environments are inconsistent, compare the network status levels of the two:

[0090] When a change in the network environment is detected, the new and old network status levels are further divided into three situations:

[0091] S81: The new network is better than the original network:

[0092] Determine whether the previous run was abnormal due to a network problem. If so, re-download the package. If not, reuse the cached package.

[0093] S82: The new network is equal to the original network:

[0094] Further determine whether there was an exception last time. If there was no exception, continue to use the cache. If there was an exception, download a new installation package.

[0095] S83: The new network is inferior to the original network:

[0096] The system automatically chooses to re-obtain the latest official installation package from the cloud to ensure the adaptability of the operating environment and the stability of the software version.

[0097] During the above-mentioned network anomaly judgment process, the system also includes further analysis functions: extracting the end time point of the last operation, and looking back at the network status and usage fluctuations in the previous half hour, comparing it with the abnormal time period, and analyzing whether it is caused by network reasons; at the same time, it can synchronously read the feedback information submitted by the user, match the feedback description with the actual abnormal time, so as to further confirm the causal relationship of the fault and enhance the system's recognition accuracy of the source of the abnormality.

[0098] On the premise that it is finally determined that cloud download is not required, the system can automatically integrate operation data, network environment assessment results and installation cache information, generate a structured access request, and call the local cache installation package to complete the reinstallation of the conference application software and conference access.

[0099] Through the above-mentioned implementation mode, the present invention realizes the rapid identification of multi-platform conference applications by the conference terminal, intelligent cache judgment, historical operation data evaluation, network environment comparison and feedback closed-loop verification, effectively improving the response speed and stability of conference access, reducing the probability of repeated resource downloads and system crashes, and is particularly suitable for actual application scenarios with limited device resources or unstable network environment.

[0100] Example 2

[0101] like Figure 2 As shown, this embodiment also provides a terminal device multi-platform access system for executing the terminal device multi-platform access method described above, which can realize the automatic identification, cache judgment, historical operation data analysis and intelligent installation access of the conference terminal to various conference application software, thereby improving the system operation efficiency and network adaptability.

[0102] The system includes the following modules:

[0103] The first acquisition module is used to obtain information about conference application software that is or has been installed on the conference terminal device. This module retrieves the device's local installation and uninstallation records, identifies the application name, installation completion time, and uninstallation time, and forms a complete application usage trajectory, which serves as the basic data source for subsequent operations.

[0104] The second acquisition module is used to determine the conference application software required for the current conference task. This module identifies the current conference information (such as the conference link, scheduling platform, or user selection), matches the conference application software required by the corresponding conference platform, and designates it as the application to be loaded.

[0105] The determination module is used to determine whether the installation package of the conference application software to be loaded is already saved in the local cache. If the application has not been uninstalled, this module will guide the user to directly call the existing application to join the conference. If it has been uninstalled, the module will enter the installation package status determination process to determine whether the installation package was retained before the uninstallation.

[0106] The third acquisition module, if the installation package is present, retrieves the pre-installation operational data of the conference application, including runtime, crash logs, operational anomaly records, and network status information from the last use. This module automatically extracts operational stability indicators and network environment parameters from this log data.

[0107] The first comparison module is used to compare the network environment before the uninstallation with the network environment currently connected to the device. This module determines the similarity between the two network environments by comparing key parameters such as network type, signal strength, and stability level, which serves as a reference for subsequent determination of cached packet availability.

[0108] The second comparison module is used to further compare the quality levels of the current network and the historical network when the network environment is inconsistent, and determine whether the new network is better than, equal to, or worse than the original network, so as to decide whether the cached installation package can continue to be used or whether the latest version of the installation package needs to be obtained from the cloud again.

[0109] The fourth acquisition module is used to obtain the historical running time of the conference application software and the last running time before uninstallation, and compare and analyze the two. If the two are similar, it can be determined that the last operation was normal; if the difference exceeds a predetermined threshold, it is preliminarily determined that there is an operating anomaly.

[0110] The statistics module is used to comprehensively analyze the fluctuations of various indicators during use, including network signal changes, loading time differences, user feedback anomaly records, etc., to further assist in anomaly tracing and operation stability judgment.

[0111] The execution module integrates the analysis conclusions of all the above modules and makes the final installation and access decision. If the cached package is determined to be usable, it directly calls the cached installation package to complete the installation and login of the conference application software. If the cached package is determined to have operational risks or the network environment is degraded, it automatically downloads the latest version of the installation package from the cloud and completes the conference access. The execution module also generates access requests, initiates logging, and ensures that subsequent actions can be traced and optimized.

[0112] Through the above system, various functional modules operate in coordination, enabling efficient access, stable operation and intelligent updates of conference terminals to multi-platform conference applications without user intervention, maintaining good compatibility and user experience in multi-network switching environments and complex equipment conditions. It is particularly suitable for application scenarios such as multi-platform conference scheduling and mobile terminal collaborative office.

[0113] The basic principles, main features, and advantages of the present invention are shown and described above. Those skilled in the art should understand that the present invention is not limited to the foregoing embodiments. The foregoing embodiments and descriptions are merely illustrative of the principles of the present invention. Various changes and modifications may be made to the present invention without departing from the spirit and scope of the present invention. Such changes and modifications are intended to fall within the scope of the present invention. The scope of protection claimed in the present invention is defined by the appended claims and their equivalents.

Claims

1. A method for multi-platform access of a terminal device, characterized in that: The following steps are involved: S1. Obtaining conference application software installed in the conference terminal device: reading conference application software previously installed in the conference terminal device and marking them as alternative options; S2. Determine the conference application software required by the current device: Identify the conference application software required to be called for the current conference activity and designate it as the conference application software to be loaded; S3. Evaluate whether the installation package of the conference application software already exists in the cache: first determine whether the conference application software has been uninstalled. If not, directly call the application software to access the conference; if it has been uninstalled, execute the next step; S4. Detecting whether the installation package of the conference application software is retained in the cache: determining whether the installation package of the conference application software is stored in the cache before the software is uninstalled; if not, obtaining the installation package of the conference application software from the cloud, and invoking the package to enter the conference after the installation is complete; querying the uninstallation record of the loaded conference application software; if the installation package is retained, determining that the software is cached; if not, determining that the software is not cached; S5. If the installation package has been cached, obtain the running data before uninstallation: extract the usage record and running stability related data of the conference application software before the last uninstallation as a reference; S6. Using the above data, compare the current network environment with the last operating environment to determine whether it is consistent: determine whether the current network state is the same as the network environment of the conference application software before uninstallation, and based on the determination result, perform one of the following steps: installing the software using a cached installation package, downloading a cloud installation package, or re-downloading the official version; S7. If the network environment is consistent, determine whether there was an abnormality in the last operation: If no failure occurred during the last operation, use the cached installation package to complete the installation and call the conference application software to join the meeting; if there was an abnormality during the last operation, download the cloud installation package and reinstall it; S8. If the network environments are inconsistent, compare the network status levels of the two networks. Compare the current network environment with the environment before uninstallation and classify the new network into three situations: better than the original network, equal to the original network, or worse than the original network. S81. The new network is better than the original network: Determine whether the conference application software is running abnormally before uninstallation due to network problems. If so, download a new installation package directly from the cloud. If not, continue to use the cached installation package. S82. The new network is equal to the original network: Determine whether the abnormal operation is caused by network problems. If there is no abnormality, use the cached installation package. If there is an abnormality, obtain the installation package from the cloud and reinstall it; S83. The new network is inferior to the original network: Re-download and install the latest official version of the conference application software installation package, and then join the meeting after completion.

2. The method for multi-platform access of a terminal device according to claim 1, characterized in that: The S1 includes obtaining the installation record and uninstallation record of the conference application in the conference terminal device, wherein the installation record includes the name of the application software and the time point of installation completion, and the uninstallation record includes the name of the application software and the time point of uninstallation completion.

3. The method for multi-platform access of a terminal device according to claim 1, characterized in that: The S5 includes counting the historical running time of the conference application software to be loaded and the last running time before uninstallation.

4. The method for multi-platform access of a terminal device according to claim 3, characterized in that: Use the historical running time as the benchmark and compare it with the last running time.

5. The method for multi-platform access of a terminal device according to claim 4, characterized in that: If the difference is less than or equal to the predetermined threshold, the previous operation is considered normal; if the difference exceeds the predetermined threshold, the previous operation is considered abnormal.

6. The method for multi-platform access of a terminal device according to claim 1, characterized in that: Both S81 and S82 include determining whether the last operation was abnormal. The determination step includes obtaining the end time point of the last operation and extracting the network status or usage within half an hour before the time. On this basis, the new and old network statuses are compared to determine whether the cause is a network problem.

7. The method for multi-platform access of a terminal device according to claim 6, characterized in that: When determining whether the anomaly is caused by network reasons, it also includes further extracting user feedback information and determining the causal relationship based on the comparison of the anomaly description in the feedback with the actual anomaly time.

8. The method for multi-platform access of a terminal device according to claim 1, characterized in that: In the steps S7, S81 and S82, if it is determined that downloading from the cloud is not necessary, the relevant data is automatically integrated to generate an access request, and the cache installation package is called to complete the installation and access of the conference application software.

9. A terminal device multi-platform access system, used to implement the method according to any one of claims 1 to 8, characterized in that: include: A first acquisition module is used to acquire the conference application software installed in the conference terminal device; The second acquisition module is used to determine the conference application software required to be called for the current conference task; A determination module, used to determine whether the installation package of the required conference application software has been saved in the device cache; The third acquisition module is used to obtain the operation data before uninstallation and the network status information when it was last used; A first comparison module is used to compare whether the network environment before uninstallation is consistent with the current network environment; The second comparison module is used to compare the quality of the new and old network environments; The fourth acquisition module is used to obtain the historical running time and last usage time of the conference application software; Statistics module, used to count changes in network status and fluctuations during use; The execution module is used to summarize all the above monitoring conclusions and analysis results and make corresponding installation and access operations.

Images