Terminal equipment multi-platform access method and system
By identifying historical installation records and comparing network environments in terminal devices, fast and stable access to multi-platform conference terminals is achieved, solving the problem of insufficient equipment flexibility and stability in the prior art, and improving access efficiency and system adaptability.
Patent Information
- Application Number
- CN202510857184.1
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-06-25
- Publication Date
- 2025-07-25
- Estimated Expiration
- 2045-06-25
AI Technical Summary
Existing conference terminal equipment is difficult to achieve seamless adaptation in a multi-platform environment, resulting in insufficient equipment flexibility and universality, increasing deployment and operation and maintenance costs, and low stability and access efficiency in complex network environment scenarios.
By obtaining the historical installation records of the terminal device, identifying the current application software, judging the cache status, combining historical operation data with the network environment, intelligently selecting the cache or cloud installation path to achieve fast and stable multi-platform access.
It improves the adaptability and access efficiency of conference terminals to multiple platforms, reduces repeated downloads and network occupation, enhances the adaptability and stability of the system, and is suitable for scenarios with large fluctuations in network conditions.
Smart Images

Figure CN120371327A_ABST
Abstract
Description
Technical Field
[0001] The present invention belongs to the technical field of audio - video conferencing methods and systems, and particularly relates to a method and system for multi - platform access of terminal devices. Background Art
[0002] In recent years, with the continuous development of audio - video communication technology and the digital transformation of enterprise office methods, conference terminal devices have become one of the important infrastructure for remote collaboration. Especially in the office scenarios where multiple platforms run in parallel, such as the co - existence environment of enterprise - built video conferencing platforms, public cloud conferencing services (such as Zoom, Teams, Tencent Meeting, etc.), and third - party audio - video service systems, the compatibility and access capabilities of conference terminal devices have received increasing attention.
[0003] Most existing conference terminal devices are mainly adapted to a single platform. Their software and hardware resource configurations, communication protocols, and authentication mechanisms are usually optimized for specific conference platforms, which to a certain extent limits the flexibility and versatility of the devices. 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 devices such as soft - switching systems and transcoding servers, which not only increases the deployment and operation and maintenance costs, but also brings problems such as increased system latency and decreased stability. In addition, due to differences in audio - video coding and decoding standards, access protocols, signaling processing procedures, user authentication methods, etc. among various platforms, it is difficult for existing technologies to achieve seamless adaptation to multiple platforms.
[0004] Especially in industries such as government, finance, and education, the conference environment is more complex, with both privately - deployed platforms and the need to access external public conference systems, which puts higher requirements on the multi - platform compatible access capabilities of conference terminals. How to dynamically identify and be compatible with multiple mainstream conference platforms under a unified terminal architecture, and achieve fast, stable, and secure multi - platform access has become a technical problem that urgently needs to be solved.
[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 - video platforms can be improved, thereby enhancing the access efficiency and collaboration experience of remote conferences and meeting the actual usage requirements in various scenarios. Summary of the Invention
[0006] Aiming at the above problems, the object of the present invention is to propose: A method for multi - platform access of terminal devices, including the following steps: S1. Obtain the installed conference application software in the conference terminal device: Read the conference application software that has been installed in the conference terminal device and identify it as an alternative. S2. Determine the conference application software required by the current device: Identify the conference application software to be invoked 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 it has not been uninstalled, directly call the application software to access the conference; if it has been uninstalled, proceed to the next step. S4. Detect whether the installation package of the conference application software is retained in the cache: Determine whether the installation package of the conference application software was saved in the cache before uninstallation; if it was not retained, obtain the installation package of the conference application software from the cloud, and after installation, call it to enter the conference. S5. If the installation package is already cached, obtain the running data before uninstallation: Extract the usage records and data related to running stability of the conference application software before the last uninstallation as a reference basis. S6. Use the above data to compare whether the current network is the same as the previous running environment: Determine whether the current network access status is the same as the network environment of the conference application software before uninstallation; based on the judgment result, respectively execute one of installing the software using the cached installation package, downloading the installation package from the cloud to install the software, and reinstalling the official version by downloading.
[0007] In a preferred technical solution, the "respectively execute one of installing the software using the cached installation package, downloading the installation package from the cloud to install the software, and reinstalling the official version by downloading based on the judgment result" includes: S7. If they are the same, determine whether there was an abnormality in the previous run: If there was no fault during the previous run, the installation package in the cache can be used to complete the installation and call the conference application software to access the conference; if there was an abnormal run previously, the installation package needs to be downloaded from the cloud for reinstallation. S8. If the network environments are different, compare the network status levels of the two: Compare the current network access environment with the previous environment and classify it into three situations: the new network is better than the original network, equal to the original network, or lower than the original network. S81. The new network is better than the original network: Determine whether the abnormal operation of the conference application software before uninstallation was caused by network problems. If there was an abnormality, directly download a new installation package from the cloud; if there was no abnormality, the cached installation package can continue to be used. S82. The new network is equal to the original network: Determine whether the operation is abnormal due to network problems. If there is no abnormality, use the cached installation package. If there is an abnormality, obtain the installation package from the cloud again and reinstall it. S83. The new network is inferior to the original network: Then it is necessary to download and install the official latest version of the conference application software installation package again. After completion, connect to the conference.
[0008] In a preferred technical solution, the 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 when the installation is completed. The uninstallation record includes the name of the application software and the time point when the uninstallation is completed.
[0009] In a preferred technical solution, the 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 judged to be cached. If not found, it is judged not to be cached.
[0010] In a preferred technical solution, the S5 includes counting the historical running duration of the conference application software to be loaded and the last running duration before uninstallation.
[0011] In a preferred technical solution, the historical running duration is used as the reference duration, and it is compared and judged with the last running duration.
[0012] In a preferred technical solution, if it is judged that 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.
[0013] In a preferred technical solution, both in the S81 and S82, it includes judging whether the last operation was abnormal. The judging step includes obtaining the end time point of the last operation, and extracting the network status or usage within half an hour before this time point. On this basis, comparing the new and old network statuses to judge whether it is caused by network problems.
[0014] In a preferred technical solution, when judging whether it is caused by network reasons for the abnormality, it further includes extracting user feedback information, and determining the causal relationship based on the comparison between the abnormal description in the feedback and the actual abnormal time.
[0015] In a preferred technical solution, in the steps of S7, S81, and S82, if it is judged that there is no need to download from the cloud, relevant data is automatically integrated to generate an access request, and the cached installation package is called to complete the installation and access of the conference application software.
[0016] The present invention also provides a multi-platform access system for terminal devices to implement the above method, including: The 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 invoked for the current conference task; The judgment module is used to judge whether the installation package of the required conference application software has been saved in the device cache; The third acquisition module is used to acquire the running data before uninstallation and the network status information at the last use; The 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 old and new network environments; The fourth acquisition module is used to acquire the historical running duration and the last use duration of the conference application software; The statistics module is used to count the network status changes and the fluctuations during the use process; The execution module is used to summarize all the above monitoring conclusions and analysis results and make corresponding installation and access operations.
[0017] Beneficial effects The present invention provides a method and system for multi-platform access of a conference terminal device, which can effectively improve the adaptation ability and access efficiency of the conference terminal to various conference application software, and has the following beneficial effects: 1. By identifying and analyzing the device's historical installation records, the present invention can quickly determine the user's commonly used conference application software, avoid repeated downloads and redundant matching, and improve the access response speed.
[0018] 2. The present invention is provided with a cache detection mechanism and an uninstalled package judgment module, which can automatically switch the installation method based on whether the installation package is retained in the cache, and complete the local quick recovery installation without relying on the cloud, improving the independent operation ability of the system.
[0019] 3. By introducing a comparison mechanism of historical running data and network status, the present invention can predict the reliability of the cached installation package before access, and automatically select to use the cached installation package or re-download according to the last running result, so as to avoid known problems and improve the running stability.
[0020] 4. By comparing the levels of the current network environment and the network environment before uninstallation, combining the running anomaly judgment and user feedback information, the present invention realizes multi-dimensional traceability and intelligent judgment of the reasons for running anomalies, significantly enhancing the self-adaptability and fault tolerance ability of the system.
[0021] 5. Without the intervention of the cloud, the present invention can realize the quick reinstallation and intelligent call of the uninstalled conference software, reduce network occupancy and access delay, and is especially suitable for use scenarios with large network condition fluctuations or frequent access requirements.
[0022] In summary, the present invention not only improves the intelligent level and execution efficiency of multi-platform access of the conference terminal, but also enhances the flexibility and stability of the system while ensuring the user access experience, and has strong practical value and promotion prospects. BRIEF DESCRIPTION OF THE DRAWINGS
[0023] Figure 1 is a schematic flowchart of the method of the present invention; Figure 2 is a schematic structural diagram of the system of the present invention. DETAILED DESCRIPTION OF THE EMBODIMENTS
[0024] To deepen the understanding of the present invention, the present invention will be further described in detail below in conjunction with embodiments. These embodiments are only used to explain the present invention and do not constitute a limitation to the protection scope of the present invention.
[0025] Embodiment 1 According to Figure 1 as shown, this embodiment provides a method for multi-platform access of terminal devices, which is applicable to a conference terminal environment with adaptation requirements for various conference application software, aiming to achieve rapid access, intelligent judgment and cache reuse of different conference platforms, so as to improve the conference response efficiency and the terminal operation stability.
[0026] Specifically, it includes the following steps: Step S1: Obtain the installed conference application software in the conference terminal device: The system first scans and identifies the conference application software previously installed in the conference terminal device, extracts its installation record and uninstall record information. Among them, the installation record includes the application name and the corresponding installation completion time point, and the uninstall record includes the application name and the uninstall completion time point. The recognition result will be used as an alternative for subsequent loading judgment.
[0027] Step S2: Judge the conference application software required by the current device: According to the conference scheduling information or the user-specified content, the system judges the conference application software required for the current conference activity and marks it as the object to be loaded, and enters the loading evaluation process.
[0028] Step S3: Evaluate whether the installation package of the conference application software already exists in the cache: First, judge whether the application has been uninstalled. If it has not been uninstalled, the existing application in the device can be directly called to achieve conference access without reloading; if it has been uninstalled, continue to execute the next step.
[0029] Step S4: Detect whether the installation package of the conference application software is retained in the cache: Query whether the installation package before uninstallation is retained in the system uninstallation record. If the installation package has been retained, it is judged to be in the cached state; if the installation package is not retained, the system automatically pulls the required installation package from the cloud, and enters the meeting process after installation is completed.
[0030] Step S5: If the installation package is cached, obtain the running data before uninstallation: When the cache exists, the system will further extract the running data of the conference application software before uninstallation, including historical running duration, last running duration, stability record, error log, etc.
[0031] Among them, the historical running duration is used as a reference value and compared with the last running duration for judgment: if the two are similar, it indicates stable operation; if there is an obvious difference, there may be abnormal termination or lag phenomena.
[0032] Step S6: Use the above data to compare whether the current network is the same as the previous running environment: The system extracts the basic information of the currently connected 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.
[0033] Construct a judgment function , which is used to output whether the cached installation package can be used currently. Its core input variables include: : The previous running stability rate (a value between 0 and 1); : The current network environment parameter vector (including bandwidth, latency, packet loss rate); : The network environment parameter vector when used last time; : The difference degree (Euclidean distance) between the current network and the network before uninstallation; : The network difference threshold (empirically set).
[0034] Judgment formula:
[0035] Where: : Whether the cached installation package is available (1 means available, 0 means unavailable); : The stability score threshold, with a default value of 0.8; : The tolerance of network environment similarity, set according to the network parameter dimension.
[0036] Step S7: If they are consistent, determine whether there was an exception in the previous run: When the two network states are consistent, the system uses the previous run situation as a reference. If the previous run was stable without exceptions, the locally cached installation package can be used to install the application; if error records or termination exceptions are found in the run log, the local cache is automatically abandoned and the official installation package is obtained from the cloud for reinstallation.
[0037] Step S8: If the network environments are inconsistent, compare the network state levels of the two: When a change in the network environment is detected, the new and old network state levels are further divided into three cases: S81: The new network is better than the original network: Determine whether the previous run was abnormal due to problems with the original network. If there were abnormalities, it is recommended to download again; if there were no abnormalities, the cached package can be reused.
[0038] S82: The new network is equal to the original network: Further determine whether the previous time was abnormal. If there were no abnormalities, continue to use the cache; if there were abnormalities, download a new installation package.
[0039] S83: The new network is inferior to the original network: The system automatically selects to obtain the latest official installation package from the cloud again to ensure the adaptability of the operating environment and the stability of the software version.
[0040] During the above network exception judgment process, the system also includes a further analysis function: extract the end time point of the previous run, and backtrack the network state and usage fluctuations within the previous half hour, and compare them in combination with the abnormal time period to analyze whether it was caused by network reasons; at the same time, the feedback information submitted by the user can be synchronously read, and the feedback description is matched with the actual abnormal time, so as to further confirm the cause and effect relationship of the failure and enhance the system's recognition accuracy of the source of the exception.
[0041] On the premise that it is finally determined that there is no need to download from the cloud, the system can automatically integrate the operation data, network environment evaluation results, and installation cache information, generate a structured access request, and call the locally cached installation package to complete the reinstallation of the conference application software and conference access.
[0042] Through the above implementation methods, the present invention realizes the rapid recognition of multi-platform conference applications by the conference terminal, intelligent judgment of caching, evaluation of historical operation data, comparison of network environments, and feedback closed-loop verification, effectively improving the response speed and stability of conference access, reducing the probability of resource duplication downloads and system crashes, and is particularly suitable for actual application scenarios where device resources are limited or the network environment is unstable.
[0043] Embodiment 2 As Figure 2As shown in the figure, this embodiment also provides a multi-platform access system for terminal devices, which is used to execute the above-mentioned multi-platform access method for terminal devices, and can realize the automatic recognition, cache judgment, historical operation data analysis and intelligent installation access of conference terminals to a variety of conference application software, improving the system operation efficiency and network adaptability.
[0044] The system includes the following modules: The first acquisition module is used to acquire the information of the conference application software that has been installed or has ever been installed in the conference terminal device. This module can retrieve the installation records and uninstallation records on the device locally, identify the name of the application software, the installation completion time point and the uninstallation time point, so as to form a complete application usage track, which serves as the basic data source for subsequent operations.
[0045] The second acquisition module is used to determine the conference application software required to be called for the current conference task. This module identifies the current conference information (such as 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.
[0046] The judgment module is used to judge whether the installation package of the above-mentioned conference application software to be loaded is already saved in the local cache. If the application has not been uninstalled, this module will guide to directly call the existing application to access the conference; if it has been uninstalled, it will enter the installation package status judgment process to judge whether the installation package has been retained before uninstallation.
[0047] The third acquisition module is used to acquire the operation data of the conference application software before uninstallation, including operation duration, crash logs, operation exception records, and network status information at the last use, in the case where the installation package exists. This module supports automatically extracting operation stability indicators and network environment parameters according to the log data.
[0048] The first comparison module is used to compare whether the network environment before uninstallation is consistent with the network environment accessed by the current device. This module judges the similarity degree of the two network environments by comparing key parameters such as network type, signal strength, and stability level, as a reference basis for subsequent judgment of the availability of the cache package.
[0049] The second comparison module is used to further compare the quality levels of the current network and the historical network in the case of inconsistent network environments, and judge whether the new network is better than, equal to, or worse than the original network, so as to decide whether the cache installation package can continue to be used or the latest version installation package needs to be retrieved from the cloud.
[0050] The fourth acquisition module is used to acquire the historical operation duration of the conference application software and the last operation duration before uninstallation, and compare and analyze the two. If the two are similar, it can be judged that the last operation was normal; if the difference exceeds the predetermined threshold, it is initially considered that there is an operation anomaly.
[0051] A statistical module for comprehensively analyzing the fluctuations of various indicators during use, including network signal changes, loading time differences, abnormal user feedback records, etc., to further assist in abnormal traceability and judgment of operation stability.
[0052] An execution module for integrating the analysis conclusions of all the above modules and making a final installation and access decision. If it is determined that the cache package can be used, the cache installation package is directly called to complete the installation and login of the conference application software; if it is determined that there are running risks in the cache package or the network environment deteriorates, the latest version of the installation package is automatically downloaded from the cloud and the conference access is completed. The execution module can also generate access requests, start the log recording process, and ensure that subsequent behaviors can be traced and optimized.
[0053] Through the above system, each functional module operates in coordination, and can, without user intervention, achieve efficient access, stable operation, and intelligent update of the conference terminal to multi-platform conference applications, maintain good compatibility and user experience in multi-network switching environments and complex device conditions, and is particularly suitable for application scenarios such as multi-platform conference scheduling and mobile terminal collaborative office.
[0054] The above has shown and described the basic principles, main features, and advantages of the present invention. Those skilled in the art should understand that the present invention is not limited by the above embodiments. What is described in the above embodiments and the specification only illustrates the principles of the present invention. Without departing from the spirit and scope of the present invention, the present invention will have various changes and improvements, and all these changes and improvements fall within the scope of the present invention claimed. The scope of protection claimed by the present invention is defined by the appended claims and their equivalents.
Claims
1. A method for a terminal device to access multiple platforms, characterized in that It includes the following steps: S1. Obtain the installed conference application software in the conference terminal device: Read the conference application software that has been installed in the conference terminal device before, and identify it as an alternative; S2. Determine the conference application software required by the current device: Identify the conference application software 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 it has not been uninstalled, directly call the application software to access the conference; if it has been uninstalled, proceed to the next step; S4. Detect whether the installation package of the conference application software is retained in the cache: Determine whether the installation package of the conference application software was saved in the cache before it was uninstalled; if it was not retained, obtain the installation package of the conference application software from the cloud, and after completion of installation, call it to enter the conference; S5. If the installation package has been cached, obtain the running data before uninstallation: Extract the usage records and data related to running stability of the conference application software before the last uninstallation as a reference; S6. Use the above data to compare whether the current network is the same as the previous running environment: Determine whether the current accessed network status is the same as the network environment of the conference application software before uninstallation, and respectively execute one of installing the software using the cached installation package, downloading the cloud installation package to install the software, and reinstalling the official version by downloading based on the judgment result.
2. The method for multi-platform access of the terminal device according to claim 1, characterized in that: The "respectively execute one of installing the software using the cached installation package, downloading the cloud installation package to install the software, and reinstalling the official version by downloading based on the judgment result" specifically includes: S7. If the network environments are the same, determine whether there was an abnormality in the previous running: If no failure occurred during the previous running, use the installation package in the cache to complete the installation and call the conference application software to access the conference; if there was an abnormality in the previous running, download the cloud installation package for reinstallation; S8. If the network environments are different, compare the network status levels of the two: Compare the currently accessed network environment with the environment before uninstallation, and classify it into three situations: the new network is better than the original network, equal to the original network, or lower than the original network; S81. The new network is better than the original network: Determine whether the abnormal running of the conference application software before uninstallation was caused by network problems. If there was an abnormality, directly download a new installation package from the cloud; if there was no abnormality, continue to use the cached installation package; S82. The new network is equal to the original network: Determine whether the abnormal running was caused by network problems. If there was no abnormality, use the cached installation package; if there was an abnormality, obtain the installation package from the cloud again and reinstall; S83. The new network is inferior to the original network: Then redownload and install the installation package of the official latest version of the conference application software, and then access the conference after completion.
3. The method for multi-platform access of the terminal device according to claim 1, characterized in that: The S1 includes obtaining the installation records and uninstallation records of the conference applications in the conference terminal device. The installation records include the names of the application software and the time points when the installation was completed, and the uninstallation records include the names of the application software and the time points when the uninstallation was completed; S4 includes querying the uninstallation record of the conference application software to be loaded. If the installation package at that time is retained after the query, it is judged as cached; if not, it is judged as not cached.
4. The method for multi-platform access of the terminal device according to claim 1, wherein: S5 includes counting the historical running duration of the conference application software to be loaded and the last running duration before uninstallation.
5. The method for multi-platform access of the terminal device according to claim 4, wherein: The historical running duration is used as the reference duration, and it is compared and judged with the last running duration.
6. The method for multi-platform access of a terminal device according to claim 5, characterized in that: If it is judged that the difference is less than or equal to the predetermined threshold, it is considered that the last run was normal; if the difference exceeds the predetermined threshold, it is considered that the last run was abnormal.
7. The method for multi-platform access of the terminal device according to claim 1, wherein: Both S81 and S82 include judging whether the last run was abnormal. The judging step includes obtaining the end time point of the last run and extracting the network status or usage within the first half hour before this time point. On this basis, the new and old network statuses are compared to judge whether it is caused by a network problem.
8. The method for multi-platform access of a terminal device according to claim 7, wherein: When judging whether it is caused by a network problem, it also includes further extracting user feedback information and determining the causal relationship based on the comparison between the abnormal description in the feedback and the actual abnormal time.
9. The method for multi-platform access of the terminal device according to claim 1, characterized in that: In steps S7, S81, and S82, if it is judged that there is no need to download from the cloud, relevant data is automatically integrated to generate an access request, and the cached installation package is called to complete the installation and access of the conference application software.
10. A multi-platform access system for a terminal device, which is used to implement the method described in any one of claims 1 to 9, and is characterized in that, It includes: The 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; The judgment module is used to judge whether the installation package of the required conference application software has been saved in the device cache; The third acquisition module is used to acquire the running data before uninstallation and the network status information during the last use; The 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 acquire the historical running duration and the last usage duration of the conference application software; The statistics module is used to count the changes in the network status and the fluctuations during the usage process; The execution module is used to summarize all the above monitoring conclusions and analysis results and perform corresponding installation and access operations.
Citation Information
Patent Citations
Method and equipment for terminal service processing
CN103249027A
Method and system for upgrading communication device based on single memory area
CN104503811A
Method and device for restoring backup data
CN105677513A
Application software installation and / or operation method and device, electronic equipment and storage medium
CN114035812A
Cross-platform multi-mobile application access management method and system
CN116405239A