Plug-in function management method, system, device and storage medium

Abstract

The application discloses a plug-in function management method, system, device and storage medium, and belongs to the technical field of computers. The method is applied to a second terminal device, the second terminal device is connected with a first terminal device through an intranet, the second terminal device and the first terminal device are installed with the same application program, and the first terminal device is installed with a target plug-in of the application program. The method comprises the following steps: the second terminal device receives a display instruction sent by the first terminal device through the intranet; and the second terminal device displays a function interface corresponding to the target plug-in based on shared data included in the display instruction, and the function interface is used for realizing the function of the target plug-in. The method sends the display instruction through the intranet, so that the sending of the display instruction is not limited by the network, and the security and transmission efficiency of the transmitted data can be improved. In addition, the function interface displayed by the second terminal device is controlled by the display instruction sent by the first terminal device, so that the function interfaces between different devices can be synchronized.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular to a method, system, device, and storage medium for managing plug-in functions. Background Technology

[0002] With the development of computer technology, the types of applications are increasing, and the types and application scope of plugins that rely on applications to achieve corresponding functions are also expanding. Therefore, it is necessary to manage plugin functions.

[0003] In related technologies, when different terminal devices have the same application installed, if they want to implement the same plugin functionality based on that application, they need to communicate with the server separately to obtain the plugin, install the plugin on each device, and then implement the corresponding functionality. In this case, implementing the same plugin functionality on multiple terminal devices is not only limited by the network, but also inefficient. Summary of the Invention

[0004] This application provides a method, system, device, and storage medium for managing plug-in functionality, which can be used to solve problems existing in related technologies. The technical solution is as follows:

[0005] In a first aspect, embodiments of this application provide a method for managing plug-in functionality. The method is applied to a second terminal device, which is connected to a first terminal device via an intranet. Both the second and first terminal devices have the same application installed, and the first terminal device has a target plug-in for that application installed. The method includes:

[0006] The second terminal device receives a display instruction sent by the first terminal device through the intranet, the display instruction including shared data related to the function of the target plugin;

[0007] The second terminal device displays a functional interface corresponding to the target plugin based on the shared data, and the functional interface is used to implement the function of the target plugin.

[0008] Secondly, embodiments of this application provide a method for managing plug-in functionality. The method is applied to a first terminal device, which is connected to a second terminal device via an intranet. Both the first and second terminal devices have the same application installed, and the first terminal device has a target plug-in for that application installed. The method includes:

[0009] The first terminal device sends a display instruction to the second terminal device through the intranet. The display instruction includes shared data related to the function of the target plugin. The display instruction is used by the second terminal device to display a functional interface corresponding to the target plugin based on the shared data. The functional interface is used to implement the function of the target plugin.

[0010] On the other hand, a management system for plug-in functions is provided. The system includes a first terminal device and a second terminal device. The first terminal device and the second terminal device are connected via an intranet. The second terminal device is used to execute the plug-in function management method described in the first aspect, and the first terminal device is used to execute the plug-in function management method described in the second aspect.

[0011] On the other hand, a computer device is provided, the computer device including a processor and a memory, the memory storing at least one computer program, the at least one computer program being loaded and executed by the processor, so that the computer device implements the management method of any of the plug-in functions described above.

[0012] On the other hand, a computer-readable storage medium is also provided, wherein at least one computer program is stored in the computer-readable storage medium, the at least one computer program being loaded and executed by a processor to enable a computer to implement the management method for any of the plug-in functions described above.

[0013] On the other hand, a computer program product or computer program is also provided, which includes computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the management method for any of the plug-in functions described above.

[0014] The technical solution provided in this application has at least the following beneficial effects:

[0015] The technical solution provided in this application is applied to a second terminal device. The second terminal device is connected to the first terminal device via an intranet. Both the second and first terminal devices have the same application installed, and the first terminal device has a target plugin for the application installed. Display commands are sent via the intranet, enabling the second terminal device to perform the same functions as the target plugin installed on the first terminal device. Furthermore, sending display commands via the intranet eliminates network limitations and improves the security and transmission efficiency of the transmitted data. Attached Figure Description

[0016] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0017] Figure 1 This is a schematic diagram of an implementation environment provided in an embodiment of this application;

[0018] Figure 2 This is a flowchart of a plug-in function management method provided in an embodiment of this application;

[0019] Figure 3 This is a flowchart illustrating a device-to-device sharing plugin function provided in an embodiment of this application;

[0020] Figure 4 This is a flowchart of a plug-in function management method provided in an embodiment of this application;

[0021] Figure 5 This is a schematic diagram illustrating the synchronization of plug-in function changes between terminal devices according to an embodiment of this application;

[0022] Figure 6 This is a schematic diagram of a split-screen display on a terminal device provided in an embodiment of this application;

[0023] Figure 7 This is a schematic diagram of a test report generation process provided in an embodiment of this application;

[0024] Figure 8 This is a flowchart illustrating the function of multiple terminal devices displaying multiple target plugins respectively, as provided in an embodiment of this application.

[0025] Figure 9 This is a schematic diagram illustrating an application scenario of a plug-in function management method provided in an embodiment of this application;

[0026] Figure 10 This is a schematic diagram of the structure of a plug-in function management device provided in an embodiment of this application;

[0027] Figure 11 This is a schematic diagram of the structure of a plug-in function management device provided in an embodiment of this application;

[0028] Figure 12 This is a schematic diagram of the structure of a management system with plug-in functionality provided in an embodiment of this application;

[0029] Figure 13 This is a schematic diagram of the structure of a server provided in an embodiment of this application;

[0030] Figure 14 This is a schematic diagram of the structure of a terminal provided in an embodiment of this application. Detailed Implementation

[0031] To make the objectives, technical solutions, and advantages of this application clearer, the embodiments of this application will be described in further detail below with reference to the accompanying drawings.

[0032] It should be noted that the terms "first," "second," etc. (if applicable) used in the specification of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented in orders other than those illustrated or described herein. The implementations described in the following exemplary embodiments do not represent all implementations consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application.

[0033] This application provides a method for managing plug-in functionality. Please refer to... Figure 1 This diagram illustrates the implementation environment of the plug-in function management method provided in this application embodiment. The implementation environment may include: a first terminal device 11 and a second terminal device 12, which establish a communication connection via an intranet in a wired or wireless manner.

[0034] An intranet is a localized network that connects various computers, external devices, and databases within a specific area to form a computer communication network, enabling data transmission between connected devices. This application does not limit the type of intranet; for example, it may include a wireless intranet using Bluetooth and / or Wi-Fi (wireless Fidelity) as the connection method, or a wired intranet using USB (Universal Serial Bus) as the connection method. Exemplarily, intranets can also be classified according to their application scenarios, such as company intranets, campus networks, and enterprise networks. Different types of intranets have different characteristics and application scenarios, and can be selected according to actual needs.

[0035] The first terminal device 11 and the second terminal device 12 are equipped with the same application, which can provide the same functionality on different terminal devices. The first terminal device 11 is equipped with a target plugin for the application, which is used to extend or update the functionality of the application.

[0036] The first terminal device 11 can display the corresponding functional interface of the installed target plugin and the data related to the function of the target plugin. For example, the function of the target plugin includes temperature display and humidity display, and the data related to the function of the target plugin includes temperature data and humidity data, such as 29 degrees Celsius and 50% humidity, thereby enabling the display of temperature and humidity on the first terminal device.

[0037] For example, the first terminal device 11 and the second terminal device 12 can share data via an intranet. Therefore, the data related to the function of the target plugin in the first terminal device 11 can be called shared data. The first terminal device 11 can send the shared data to the second terminal device 12 via the intranet, so that the second terminal device 12 can display the functional interface corresponding to the target plugin based on the shared data. The second terminal device 12 can modify the functional interface to obtain the modified first content, and the second terminal device 12 can send the first content to the first terminal device 11. The first terminal device 11 can then modify the functional interface corresponding to the target plugin displayed on the first terminal device 11 based on the first content. Optionally, the first terminal device 11 and the second terminal device 12 can be any electronic product capable of performing the methods provided in the embodiments of this application and interacting with the user through one or more means such as a keyboard, touchpad, touch screen, remote control, voice interaction or handwriting device, such as PC (Personal Computer), mobile phone, smartphone, PDA (Personal Digital Assistant), wearable device, PPC (Pocket PC), tablet computer, smart car system, smart TV, smart speaker, etc.

[0038] In one possible implementation, the implementation environment may further include a third terminal device 13. The first terminal device 11 establishes a communication connection with the second terminal device 12 and the third terminal device 13 via an intranet in a wired or wireless manner. The first terminal device 11, the second terminal device 12, and the third terminal device 13 have the same application installed. The first terminal device 11 can send shared data to the second terminal device 12 and the third terminal device 13, and the second terminal device 12 and the third terminal device 13 can display the functional interface corresponding to the target plugin based on the shared data. Optionally, if the second terminal device 12 modifies the functional interface to obtain modified first content, the second terminal device 12 can send the modified first content to the first terminal device 11, and the first terminal device 11 can send the modified first content to the third terminal device 13, so that the first terminal device 11, the second terminal device 12, and the third terminal device 13 all display the modified functional interface; that is, by modifying the functional interface through any terminal device, the modified functional interface can be displayed on any terminal device.

[0039] Those skilled in the art should understand that the first terminal device 11, the second terminal device 12, and the third terminal device 13 described above are merely examples. Other existing or future terminals that are applicable to this application should also be included within the scope of protection of this application, and are hereby incorporated by reference.

[0040] See Figure 2 , Figure 2 A flowchart illustrating a plug-in functionality management method provided in this application embodiment, which can be applied to... Figure 1 The implementation environment shown is, for example, by Figure 1 The first terminal device 11 and the second terminal device 12 shown execute the method. For example... Figure 2 As shown, the management method for this plugin function includes, but is not limited to, the following steps 201 and 202.

[0041] Step 201: The first terminal device sends a display instruction to the second terminal device through the intranet. The display instruction includes shared data related to the function of the target plugin.

[0042] In this embodiment, the first terminal device and the second terminal device are connected via an intranet. An intranet, or Local Area Network, is a regional network formed within a specific area. An intranet connects various computers, external devices, and databases within a certain area to form a computer communication network, enabling data transmission between devices connected to the intranet. As a closed network, the intranet prevents information leakage and virus attacks from external networks, thus providing high security. This embodiment does not limit the connection type between terminal devices within the intranet; for example, terminal devices can connect via Bluetooth, Wi-Fi, and USB.

[0043] The first and second terminal devices have the same application installed. This application includes executable files, libraries, and configuration files. This shared application ensures consistent deployment and configuration across different terminal devices, creating consistent installation and execution conditions for application plugins on different devices, allowing plugins of the same application to run on both the first and second terminal devices. Optionally, taking a target plugin of the application installed on the first terminal device as an example, the plugin is used to update the functionality of an existing application or implement new features. Plugins are generally transferred between terminal devices or between a network and terminal devices in the form of installation packages, facilitating centralized management of the multiple files contained within the plugin. The application can update or extend its functionality by loading the plugin installation package corresponding to the target plugin. For example, if the target plugin's function is to display the time and corresponding weather conditions, the application can add the time and weather display functionality by installing the target plugin.

[0044] For example, a plugin that performs the same function on both the first and second terminal devices is called a target plugin. The first terminal device sends a display command to the second terminal device via an intranet, controlling the second terminal device to perform the corresponding function. This display command includes shared data related to the function of the target plugin. The target plugin is a plugin already installed on the first terminal device. This embodiment does not limit the content and function of the shared data. For example, if the function of the target plugin is to display the time, the shared data includes time information and the font type corresponding to the time. Optionally, the target plugin installed on the first terminal device may be locally stored on the first terminal device, downloaded from an external network, or sent to the first terminal device by another terminal device via an intranet. This embodiment does not limit the method by which the first terminal device obtains the target plugin.

[0045] Step 202: The second terminal device receives the display instruction sent by the first terminal device through the intranet. The second terminal device displays the function interface corresponding to the target plugin based on the shared data. The function interface is used to implement the function of the target plugin.

[0046] For example, the second terminal device can implement the function corresponding to the display command sent from the first terminal device to the second terminal device as described in step 201, thereby enabling the operation of one terminal device to control the operation of another terminal device. Optionally, this operation can be applied to smart classrooms, that is, to control large-screen devices such as projectors via handheld devices, facilitating user operation.

[0047] The second terminal device displays shared data content through an installed target plugin. This shared data may include first data, second data, and third data, and one or more pieces of shared data can be used to implement the functionality of the same target plugin. For example, if the target plugin is used to display the time and the weather conditions corresponding to each hour, the first data may include time information, and the second terminal device can display the time based on this time information. The second data may include the weather information for each hour, and the second terminal device can display the weather conditions corresponding to each hour based on this second data. The third data may include the layout of the hourly and weather information. The layout includes displaying the hourly at a first position on the second terminal device's screen and displaying the weather information in a second position on the second terminal device's screen.

[0048] See Figure 3 The flowchart illustrates the function of sharing plugins between terminal devices. A first terminal device acquires the target plugin. The first and second terminal devices connect via an intranet. The first terminal device sends shared data to the second terminal device. Both devices can then display the functional interface corresponding to the target plugin based on the shared data. This functional interface includes an image display section, a table display section, and a text display section. This embodiment uses the image display section to show icons corresponding to the current weather, the table display section to show the weather conditions for the current time and each hour of the next 24 hours, and the text display section to show travel suggestions based on the weather conditions as examples.

[0049] The specific weather icons, hourly weather conditions, and travel suggestions are stored in the shared data. The second terminal device can write this shared data into different parts of the corresponding functional interface. For example, if it is currently sunny, a sunny icon can be written into the image display section; if it is expected to rain in an hour, the rain information can be written into the corresponding hourly time row in the table; and if it is expected to rain in an hour, the text "There may be light rain in the next hour; it is recommended to bring an umbrella" can be written into the text display section. Thus, the functionality of the target plugin is achieved through the aforementioned image display section, table display section, and text display section, along with the corresponding text or icons for each section.

[0050] In one possible implementation, before the second terminal device displays the functional interface corresponding to the target plugin based on the shared data, it is necessary to determine whether the second terminal device has the target plugin. This avoids sending the target plugin to the second terminal device when it already exists, which would cause duplicate target plugins to occupy the storage space of the second terminal device, and the repeated sending of target plugins would lead to wasted data traffic during data transmission.

[0051] See Figure 4 The flowchart illustrates a method for managing plugin functionality. A first terminal device sends a confirmation message to a second terminal device. This confirmation message is used by the second terminal device to determine if an installation package for the target plugin exists. If the second terminal device determines that the installation package for the target plugin does not exist based on the confirmation message, the second terminal device sends a request message to the first terminal device to request the distribution of the target plugin. The first terminal device then sends the target plugin to the second terminal device based on the request message. The second terminal device parses the target plugin and displays the corresponding functional interface based on shared data. This display process can be referred to in the relevant descriptions of steps 201 and 202, which will not be repeated here.

[0052] This application does not determine the method by which the second terminal device determines whether the target plugin exists. For example, if the confirmation information includes the name information of the target plugin, part of the code of the target plugin, etc., the second terminal device determines whether the target plugin exists by the name information of the target plugin, or by comparing part of the code of the target plugin with the existing code of the second terminal device. If the repetition rate reaches the repetition rate threshold, it is considered that the second terminal device has the target plugin.

[0053] Optionally, if the second terminal device determines that the target plugin exists based on the confirmation information, it displays the functional interface corresponding to the target plugin based on the shared data.

[0054] This application does not limit the method of installing the target plugin on the second terminal device. For example, it loads the class.dex (classes.Dalvik Executable Format) and res (resources) files contained in the target plugin. The class.dex file is the executable file format of an Android application and contains the main logic code of the target plugin. The res file is the directory in an Android application that stores various resource files, such as layout files, strings, images, and colors. These resource files, such as layout files, strings, images, and colors, are loaded and used when the application corresponding to the installation package runs to provide the functional interface corresponding to the target plugin.

[0055] In one possible implementation, if the user selects multiple second terminal devices, the first terminal device can send the same display instruction to the multiple second terminal devices in accordance with the methods described in steps 201 and 202 above, thereby controlling the multiple second terminal devices and the first terminal device to display the same content.

[0056] In one possible implementation, the second terminal device changes the functional interface and sends the changed first content to the first terminal device, so that the first terminal device changes the functional interface displayed on the first terminal device corresponding to the target plugin based on the first content.

[0057] For example, the modified first content can be obtained by modifying the functional interface corresponding to the target plugin using either the first terminal device or the second terminal device. In this embodiment of the method, after any terminal device modifies the functional interface corresponding to the target plugin, the first content can be sent to other terminal devices. See also Figure 5 The diagram shown illustrates the synchronization of data changes between terminal devices. After the second terminal device displays the functional interface corresponding to the target plugin, the second terminal device can modify the functional interface corresponding to the target plugin to obtain the modified first content. The second terminal device sends the first content to the first terminal device, and the first terminal device modifies the functional interface corresponding to the target plugin displayed on the first terminal device based on the first content.

[0058] This application uses the example of changing the functional interface of a second terminal device for illustration. Figure 5 In the schematic diagram of data change synchronization between terminal devices shown, the first terminal device and the second terminal device display the same functional interface. The process of the first terminal device and the second terminal device displaying the functional interface can be referred to the relevant descriptions of steps 201 and 202, which will not be repeated here.

[0059] For example, the functional interface can be changed through external operation to obtain the modified first content. This application embodiment does not limit the method of external operation. For example, the functional interface can be changed via touch, or via external hardware such as a keyboard and mouse, or via voice command. Optionally, the text P in the display text function section of the second terminal device can be modified to the text A via touch, and this data can be saved to the second terminal device. The original display content containing the text P can then be used as the first content.

[0060] After the first content is saved to the second terminal device, the second terminal device can send an update command to the first terminal device. This update command includes the first content, where the text corresponding to the display function is the character "A". This update command is used by the first terminal device to modify the functional interface displayed on the first terminal device that corresponds to the target plugin, based on the first content. This ensures that the content displayed on both the first and second terminal devices, after being modified by the second terminal device, displays the same content again.

[0061] In one possible implementation, in addition to being connected to the second terminal device via an intranet, the first terminal device is also connected to a third terminal device via an intranet, and the third terminal device displays the same content as the first and second terminal devices. The process of the first and third terminal devices connecting via the intranet can be referred to the relevant description in step 201, and the operation process of the first and third terminal devices displaying the same content can be referred to the operation process of the first and second terminal devices displaying the same content, which will not be repeated here. After the first terminal device receives the first content sent by the second terminal device and displays the modified content, the first terminal device sends an update instruction to the third terminal device. The update instruction includes the first content. Based on the update instruction and the first content, the third terminal device changes the functional interface displayed on the third terminal device corresponding to the target plugin, thereby making the first, second, and third terminal devices display the same content.

[0062] Optionally, in addition to connecting to the second and third terminal devices via an intranet, the first terminal device may also connect to other terminal devices via an intranet, enabling the first, second, third, and other terminal devices to display the same content. If the content displayed on the second terminal device is changed, the content displayed on the first terminal device will also be modified. After the content displayed on the first terminal device is modified, the first terminal device can choose to send an update command to the third terminal device and / or other terminal devices, so that the terminal devices receiving the update command display the same content as the first terminal device.

[0063] In one possible implementation, the display instruction further includes a display request, and the second terminal device, based on shared data, displays the functional interface corresponding to the target plugin according to the display request. That is, the first terminal device can control whether the display content of other terminal devices connected to the first terminal device is fully displayed. See also... Figure 6 The diagram illustrates a split-screen display on a terminal device. This display requirement allows control over which a terminal device connected to the first terminal device can display all the content corresponding to the target plugin's functions, or control which terminal device connected to the first terminal device can display only some of the target plugin's functions. Taking an example where the target plugin includes image, table, and text functions, the first display requirement instructs the second terminal device to display all the content corresponding to the target plugin's functions; the second display requirement instructs the third terminal device to display the content corresponding to the table and text functions; and the third display requirement instructs the Nth terminal device to display the content corresponding to the image function. Furthermore, other display requirements can instruct other terminal devices to display corresponding portions of content as needed.

[0064] In one example, the content displayed by the third terminal device (which displays the table and text functions) and the content displayed by the Nth terminal device (which displays the image functions) are combined with the content displayed by the Nth terminal device to form the content displayed by the first terminal device. This achieves the effect of splitting the content displayed by the first terminal device into two screens.

[0065] Optionally, when the first terminal device sends the target plugin and shared data, different target plugins and different shared data can be sent to different terminal devices. For example, the table function and text display function of the target plugin can be sent to the third terminal device as the first sub-target plugin, and the table and text parts of the shared data can be sent to the third terminal device as the first sub-data. The third terminal device displays the content corresponding to the table and text functions of the function interface based on the first sub-data display corresponding to the first sub-target plugin. The image function of the target plugin can be sent to the Nth terminal device as the second sub-target plugin, and the image part of the shared data can be sent to the Nth terminal device as the second sub-data. The Nth terminal device displays the content corresponding to the image function of the function interface based on the second sub-data display corresponding to the second sub-target plugin, thereby achieving the effect of splitting the content displayed by the first terminal device.

[0066] In one possible implementation, to test the performance of a target plugin on different terminal devices, a user needs to install the target plugin on each device and export test forms for the target plugin on each device. The method provided in this application allows multiple different terminal devices to be connected to a single terminal device, enabling control of the target plugin's operation on multiple devices through a single terminal device. Furthermore, because the single terminal device is connected to multiple different terminal devices, the performance status of the target plugin on multiple devices can be sent to the single terminal device, thus allowing the user to obtain the performance status of the target plugin on multiple devices through a single terminal device. See also... Figure 7 The diagram shows the test report generation process. The second terminal device obtains the running status and information of the target plugin on the second terminal device and sends the running status and information of the second terminal device to the first terminal device so that the first terminal device can generate a test form for the target plugin based on the running status and information of the second terminal device. The test form is used to analyze the performance of the target plugin on the second terminal device.

[0067] For example, the second terminal device can be a terminal device of different sizes and with different circuit boards, such as a 32-inch device, a 43-inch device, or a 71-inch device. Devices with different circuit boards refer to terminal devices of different models or configurations. For example, even among 71-inch televisions, some may use processors and operating systems from brand X, while others may use processors and operating systems from brand Y. The first terminal device sends the target plugin to multiple terminal devices of different sizes and with different circuit boards. The target plugin is tested by these multiple terminal devices, and the test results—that is, the running status of the target plugin and information from each terminal device—are sent back to the first terminal device. The running status of the target plugin includes a normal running status, meaning the target plugin runs normally on the second terminal device without errors; and an abnormal status, meaning the target plugin malfunctions on the second terminal device, which may be due to various reasons such as insufficient memory, hardware failure, or software conflicts. The information from each terminal device includes the device's size, circuit board model, operating system version, and processor model.

[0068] After multiple terminal devices send their test results as test reports to the first terminal device, the first terminal device generates a test form for the target plugin based on these results. This test form includes information about the different terminal devices and the software's running status. Users can test the software simultaneously on different device models during the software verification and self-testing phases, and can view the differences of the target plugin on different device models. Furthermore, by generating the test form through the first terminal device, all terminal device test forms can be viewed on a single terminal device, avoiding multiple file imports and exports.

[0069] In one possible implementation, the first terminal device is equipped with multiple target plugins, including a first target plugin, a second target plugin, and an Nth target plugin, etc. The first terminal device can send shared data corresponding to the functions of these different target plugins to multiple different terminal devices as needed, thereby controlling multiple different terminal devices from a single terminal device. This facilitates switching the displayed content on the multiple terminal devices; either the first target plugin can be sent to the second terminal device, or vice versa, allowing control over the display content of the second terminal device. Alternatively, the second terminal device can be controlled to display the functional interface corresponding to the first target plugin based on the first shared data, while the third terminal device can display the functional interface corresponding to the second target plugin based on the second shared data. For example, when consulting geological information, the second terminal device can display relevant geological literature, while the third terminal device can display map information, allowing the location of the geological information recorded in the relevant literature to be determined on the map. See also... Figure 8The diagram shows a flowchart illustrating the functions of multiple target plugins displayed on multiple terminal devices. The second terminal device displays an image based on the first shared data, the third terminal device displays the relevant content of text A based on the second shared data, and the Nth terminal device displays the relevant content of a table based on the Nth shared data. This allows for data correlation analysis by comparing the relevant data of the image, text A, and the table, or for cross-validation between different forms of data.

[0070] For ease of understanding, Figure 9 The illustrated plugin management method is used as an example to illustrate the method provided in this application embodiment. Figure 9 As shown, the first terminal device is connected to the second, third, fourth, and Nth terminal devices via an intranet. The first terminal device has the same application installed on the second, third, fourth, and Nth terminal devices, and the first terminal device has a target plugin for the application installed. The implementation method of the first terminal device controlling the second, third, fourth, and Nth terminal devices to implement the function of the target plugin can be referred to the relevant descriptions of steps 201 and 202 above, which will not be repeated here.

[0071] In summary, the plug-in function management method provided in this application is applied to a first terminal device and a second terminal device. The second terminal device is connected to the first terminal device via an intranet, and both devices have the same application installed. The first terminal device also has a target plug-in installed on it. This method sends display commands from the first terminal device to the second terminal device via the intranet, enabling the second terminal device to perform the same functions as the target plug-in installed on the first terminal device. Furthermore, sending display commands via the intranet eliminates network limitations and improves the security and efficiency of the transmitted data.

[0072] See Figure 10 This application provides a plugin management device, which is applied to a second terminal device connected to a first terminal device via an intranet. Both the second and first terminal devices have the same application installed, and the first terminal device has a target plugin for that application installed. The device includes:

[0073] The receiving module 1001 is used to receive a display instruction sent by the first terminal device through the intranet. The display instruction includes shared data related to the function of the target plugin.

[0074] Display module 1002 is used to display the functional interface corresponding to the target plugin based on shared data. The functional interface is used to implement the functions of the target plugin.

[0075] In one possible implementation, the device further includes:

[0076] The modification module is used to modify the functional interface and send the modified first content to the first terminal device so that the first terminal device can modify the functional interface displayed on the first terminal device corresponding to the target plugin based on the first content.

[0077] In one possible implementation, the receiving module 1001 is further configured to receive an update instruction sent by the first terminal device, the update instruction including second content.

[0078] The device also includes:

[0079] The update module is used to update the displayed functional interface according to the second content included in the update instruction, so as to display the updated functional interface.

[0080] In one possible implementation, the display instruction also includes a display requirement, and a display module 1002 is used to display the functional interface corresponding to the target plugin according to the display requirement based on shared data.

[0081] In one possible implementation, the receiving module 1002 is further configured to receive confirmation information sent by the first terminal device, the confirmation information being used to determine whether an installation package for the target plugin exists; if it is determined based on the confirmation information that no installation package exists, the receiving module 1002 sends a request message to the first terminal device to request the installation package for the target plugin; receives the installation package for the target plugin sent by the first terminal device based on the request message, and installs the target plugin based on the installation package for the target plugin.

[0082] In one possible implementation, the device further includes:

[0083] The acquisition module is used to acquire the running status of the target plugin on the second terminal device and information about the second terminal device.

[0084] The sending module is used to send information about the running status and the second terminal device to the first terminal device, so that the first terminal device can generate a test form for the target plugin based on the information about the running status and the second terminal device. The test form is used to analyze the performance of the target plugin in the second terminal device.

[0085] See Figure 11 This application provides a plugin management device, which is applied to a first terminal device. The first terminal device and a second terminal device are connected via an intranet. The first terminal device and the second terminal device have the same application installed, and the first terminal device has a target plugin for the application installed. The device includes:

[0086] The sending module 1101 is used to send a display instruction to the second terminal device via the intranet. The display instruction includes shared data related to the function of the target plugin. The display instruction is used by the second terminal device to display the function interface corresponding to the target plugin based on the shared data. The function interface is used to implement the function of the target plugin.

[0087] In one possible implementation, the device further includes:

[0088] The receiving module is used to receive the first content sent by the second terminal device. The first content is the content obtained by the second terminal device after changing the function interface.

[0089] The modification module is used to modify the functional interface displayed on the first terminal device that corresponds to the target plugin, based on the first content.

[0090] In one possible implementation, the sending module 1101 is further configured to send an update instruction to the second terminal device. The update instruction includes second content, which is obtained and sent by the second terminal device with the target plugin by changing the function interface of the target plugin, or the second content is obtained after the first terminal device updates the function interface. The update instruction is used by the second terminal device to update the function interface displayed by the second terminal device according to the second content included in the update instruction, so as to display the updated function interface.

[0091] In one possible implementation, the display instruction also includes a display requirement; the display instruction is used by the second terminal device to display the functional interface corresponding to the target plugin according to the display requirement based on shared data.

[0092] In one possible implementation, the sending module 1101 is further configured to send confirmation information to the second terminal device, the confirmation information being used by the second terminal device to determine whether the installation package of the target plugin exists; receive request information sent by the second terminal device when it is determined based on the confirmation information that the installation package does not exist; and send the installation package of the target plugin to the second terminal device based on the request information.

[0093] In one possible implementation, the receiving module is further configured to receive information sent by the second terminal device regarding the operating status of the target plug-in in the second terminal device and information about the second terminal device.

[0094] The device also includes:

[0095] The generation module is used to generate test forms for the target plugin based on the running status and information from the second terminal device. The test forms are used to analyze the performance of the target plugin on the second terminal device.

[0096] It should be noted that the apparatus provided in the above embodiments is only illustrated by the division of the above functional modules. In actual operation, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above. In addition, the apparatus and method embodiments provided in the above embodiments belong to the same concept, and their specific implementation process can be found in the method embodiments, which will not be repeated here.

[0097] See Figure 12 This application provides a management system for plug-in functionality. The system includes a first terminal device 1201 and a second terminal device 1202, connected via an intranet. The first terminal device 1201 is used to execute... Figure 2 In the corresponding method embodiment, the second terminal device 1202 is used to perform the relevant operations of the first terminal device. Figure 2 The relevant operations of the second terminal device in the corresponding method embodiment.

[0098] It should be noted that, when implementing the functions of the system provided in the above embodiments, the functions can be assigned to different entities as needed, that is, the system can be composed of different entities to complete all or part of the functions described above. Furthermore, the system and method embodiments provided in the above embodiments belong to the same concept, and their specific implementation process is detailed in the method embodiments, which will not be repeated here.

[0099] Figure 13 This is a schematic diagram of a server structure provided in an embodiment of this application. The server can vary significantly due to differences in configuration or performance. It may include one or more processors 1301 and one or more memories 1302. The one or more memories 1302 store at least one computer program, which is loaded and executed by the one or more processors 1301 to enable the server to implement the plug-in function management method provided in the various method embodiments described above. Of course, the server may also have wired or wireless network interfaces, a keyboard, and input / output interfaces for input and output. The server may also include other components for implementing device functions, which will not be elaborated upon here.

[0100] Figure 14 This is a schematic diagram of the structure of a terminal provided in an embodiment of this application. The terminal may be, for example, a smartphone, tablet computer, media player, laptop computer, or desktop computer. The terminal may also be referred to as user equipment, portable terminal, laptop terminal, desktop terminal, or other names.

[0101] Typically, a terminal includes a processor 1501 and a memory 1502.

[0102] Processor 1501 may include one or more processing cores, such as a quad-core processor, an octa-core processor, etc. Processor 1501 may be implemented using at least one hardware form selected from DSP (Digital Signal Processing), FPGA (Field-Programmable Gate Array), and PLA (Programmable Logic Array). Processor 1501 may also include a main processor and a coprocessor. The main processor, also known as a CPU (Central Processing Unit), is used to process data in the wake-up state; the coprocessor is a low-power processor used to process data in the standby state. In some embodiments, processor 1501 may integrate a GPU (Graphics Processing Unit), which is responsible for rendering and drawing the content required to be displayed on the screen. In some embodiments, processor 1501 may also include an AI (Artificial Intelligence) processor, which is used to handle computational operations related to machine learning.

[0103] The memory 1502 may include one or more computer-readable storage media, which may be non-transitory. The memory 1502 may also include high-speed random access memory and non-volatile memory, such as one or more disk storage devices or flash memory devices. In some embodiments, the non-transitory computer-readable storage media in the memory 1502 is used to store at least one instruction, which is executed by the processor 1501 to enable the terminal to implement the management method for plug-in functionality provided in the method embodiments of this application.

[0104] In some embodiments, the terminal may also optionally include: a peripheral device interface 1503 and at least one peripheral device. The processor 1501, memory 1502, and peripheral device interface 1503 can be connected via a bus or signal line. Each peripheral device can be connected to the peripheral device interface 1503 via a bus, signal line, or circuit board. Specifically, the peripheral device includes at least one of: a radio frequency circuit 1504, a display screen 1505, a camera assembly 1506, an audio circuit 1507, and a power supply 1508.

[0105] Peripheral interface 1503 can be used to connect at least one I / O (Input / Output) related peripheral device to processor 1501 and memory 1502. In some embodiments, processor 1501, memory 1502 and peripheral interface 1503 are integrated on the same chip or circuit board; in some other embodiments, any one or two of processor 1501, memory 1502 and peripheral interface 1503 can be implemented on separate chips or circuit boards, which is not limited in this embodiment.

[0106] The radio frequency (RF) circuit 1504 is used to receive and transmit RF (Radio Frequency) signals, also known as electromagnetic signals. The RF circuit 1504 communicates with communication networks and other communication devices via electromagnetic signals. The RF circuit 1504 converts electrical signals into electromagnetic signals for transmission, or converts received electromagnetic signals back into electrical signals. Optionally, the RF circuit 1504 includes: an antenna system, an RF transceiver, one or more amplifiers, a tuner, an oscillator, a digital signal processor, a codec chipset, a user identity module card, etc. The RF circuit 1504 can communicate with other terminals through at least one wireless communication protocol. This wireless communication protocol includes, but is not limited to: metropolitan area networks (MANs), various generations of mobile communication networks (2G, 3G, 4G, and 5G), wireless local area networks (WLANs), and / or WiFi (Wireless Fidelity) networks. In some embodiments, the RF circuit 1504 may also include circuitry related to NFC (Near Field Communication), which is not limited in this application.

[0107] Display screen 1505 is used to display a UI (User Interface). This UI may include graphics, text, icons, videos, and any combination thereof. When display screen 1505 is a touch display screen, it also has the ability to collect touch signals on or above its surface. These touch signals can be input as control signals to processor 1501 for processing. In this case, display screen 1505 can also be used to provide virtual buttons and / or a virtual keyboard, also known as soft buttons and / or a soft keyboard. In some embodiments, display screen 1505 can be a single screen, located on the front panel of the terminal; in other embodiments, display screen 1505 can be at least two screens, respectively located on different surfaces of the terminal or in a folded design; in other embodiments, display screen 1505 can be a flexible display screen, located on a curved or folded surface of the terminal. Furthermore, display screen 1505 can be configured as a non-rectangular, irregular shape, i.e., a non-rectangular screen. Display screen 1505 can be made of materials such as LCD (Liquid Crystal Display) or OLED (Organic Light-Emitting Diode).

[0108] The camera assembly 1506 is used to acquire images or videos. Optionally, the camera assembly 1506 includes a front-facing camera and a rear-facing camera. Typically, the front-facing camera is located on the front panel of the terminal, and the rear-facing camera is located on the back of the terminal. In some embodiments, there are at least two rear-facing cameras, which are any one of a main camera, a depth-sensing camera, a wide-angle camera, and a telephoto camera, to achieve background blurring by fusion of the main camera and the depth-sensing camera, panoramic shooting by fusion of the main camera and the wide-angle camera, VR (Virtual Reality) shooting, or other fusion shooting functions. In some embodiments, the camera assembly 1506 may also include a flash. The flash can be a single-color temperature flash or a dual-color temperature flash. A dual-color temperature flash refers to a combination of a warm-light flash and a cool-light flash, which can be used for light compensation at different color temperatures.

[0109] The audio circuit 1507 may include a microphone and a speaker. The microphone is used to collect sound waves from the user and the environment, converting the sound waves into electrical signals that are input to the processor 1501 for processing, or input to the radio frequency circuit 1504 for voice communication. For stereo sound acquisition or noise reduction purposes, multiple microphones may be used, each positioned at a different location on the terminal. The microphone may also be an array microphone or an omnidirectional microphone. The speaker is used to convert electrical signals from the processor 1501 or the radio frequency circuit 1504 into sound waves. The speaker may be a conventional diaphragm speaker or a piezoelectric ceramic speaker. When the speaker is a piezoelectric ceramic speaker, it can convert electrical signals not only into audible sound waves but also into inaudible sound waves for purposes such as distance measurement. In some embodiments, the audio circuit 1507 may also include a headphone jack.

[0110] Power supply 1508 is used to power the various components in the terminal. Power supply 1508 can be AC ​​power, DC power, a disposable battery, or a rechargeable battery. When power supply 1508 includes a rechargeable battery, the rechargeable battery can support wired or wireless charging. The rechargeable battery can also be used to support fast charging technology.

[0111] In some embodiments, the terminal further includes one or more sensors 1509. The one or more sensors 1509 include, but are not limited to: an acceleration sensor 1510, a gyroscope sensor 1511, a pressure sensor 1512, an optical sensor 1513, and a proximity sensor 1514.

[0112] Accelerometer 1510 can detect the magnitude of acceleration along the three coordinate axes of a coordinate system established by the terminal. For example, accelerometer 1510 can be used to detect the components of gravitational acceleration along the three coordinate axes. Processor 1501 can control display screen 1505 to display the user interface in either a landscape or portrait view based on the gravitational acceleration signal acquired by accelerometer 1510. Accelerometer 1510 can also be used for games or for acquiring user motion data.

[0113] The gyroscope sensor 1511 can detect the terminal's orientation and rotation angle. The gyroscope sensor 1511 can work in conjunction with the accelerometer sensor 1510 to collect the user's 3D movements on the terminal. Based on the data collected by the gyroscope sensor 1511, the processor 1501 can perform the following functions: motion sensing (e.g., changing the UI based on the user's tilt), image stabilization during shooting, game control, and inertial navigation.

[0114] The pressure sensor 1512 can be disposed on the side bezel of the terminal and / or the lower layer of the display screen 1505. When the pressure sensor 1512 is disposed on the side bezel of the terminal, it can detect the user's grip signal on the terminal, and the processor 1501 can perform left / right hand recognition or quick operation based on the grip signal collected by the pressure sensor 1512. When the pressure sensor 1512 is disposed on the lower layer of the display screen 1505, the processor 1501 can control the operable controls on the UI interface based on the user's pressure operation on the display screen 1505. The operable controls include at least one of button controls, scroll bar controls, icon controls, and menu controls.

[0115] Optical sensor 1513 is used to collect ambient light intensity. In one embodiment, processor 1501 can control the display brightness of display screen 1505 based on the ambient light intensity collected by optical sensor 1513. Specifically, when the ambient light intensity is high, the display brightness of display screen 1505 is increased; when the ambient light intensity is low, the display brightness of display screen 1505 is decreased. In another embodiment, processor 1501 can also dynamically adjust the shooting parameters of camera assembly 1506 based on the ambient light intensity collected by optical sensor 1513.

[0116] The proximity sensor 1514, also known as a distance sensor, is typically installed on the front panel of the terminal. The proximity sensor 1514 is used to detect the distance between the user and the front of the terminal. In one embodiment, when the proximity sensor 1514 detects that the distance between the user and the front of the terminal is gradually decreasing, the processor 1501 controls the display screen 1505 to switch from a screen-on state to a screen-off state; when the proximity sensor 1514 detects that the distance between the user and the front of the terminal is gradually increasing, the processor 1501 controls the display screen 1505 to switch from a screen-off state to a screen-on state.

[0117] Those skilled in the art will understand that Figure 14 The structure shown does not constitute a limitation on the terminal and may include more or fewer components than shown, or combine certain components, or use different component arrangements.

[0118] In an exemplary embodiment, a computer device is also provided, comprising a processor and a memory storing at least one computer program. The at least one computer program is loaded and executed by one or more processors to enable the computer device to implement the management method for any of the plug-in functions described above.

[0119] In an exemplary embodiment, a computer-readable storage medium is also provided, which stores at least one computer program, which is loaded and executed by the processor of a computer device to enable the computer to implement the management method of any of the plug-in functions described above.

[0120] In one possible implementation, the aforementioned computer-readable storage medium may be a read-only memory (ROM), a random access memory (RAM), a compact disc read-only memory (CD-ROM), magnetic tape, floppy disk, and optical data storage device, etc.

[0121] In an exemplary embodiment, a computer program product or computer program is also provided, which includes computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform any of the plug-in function management methods described above.

[0122] It should be noted that all information (including but not limited to user device information, user personal information, etc.), data (including but not limited to data used for analysis, stored data, displayed data, etc.), and signals involved in this application have been authorized by the user or fully authorized by all parties, and the collection, use, and processing of related data must comply with the relevant laws, regulations, and standards of the relevant countries and regions. For example, the plug-in functions and shared data involved in this application were obtained with full authorization.

[0123] It should be understood that "multiple" as used in this article refers to two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone. The character " / " generally indicates that the preceding and following related objects have an "or" relationship.

[0124] The above description is merely an exemplary embodiment of this application and is not intended to limit this application. Any modifications, equivalent substitutions, improvements, etc., made within the principles of this application should be included within the protection scope of this application.

Claims

1. A method for managing plug-in functionality, characterized in that, The method is applied to a second terminal device, which is connected to a first terminal device via an intranet. Both the second and first terminal devices have the same application installed, and the first terminal device has a target plugin for the application installed. The same application can create consistent execution conditions for the target plugin on different devices. The method includes: The second terminal device receives a display instruction sent by the first terminal device through the intranet, the display instruction including shared data related to the function of the target plugin; The second terminal device writes the shared data into different display parts of the functional interface corresponding to the target plugin. The first terminal device communicates with multiple second terminal devices in a network. The first terminal sends different subsets of the shared data to different second terminals, so that each second terminal renders different display parts of the functional interface of the target plugin. The functional interface is used to implement the function of the target plugin. The first terminal device and the second terminal devices keep data change synchronized. The second terminal device changes the functional interface and sends the changed first content to the first terminal device, so that the first terminal device changes the functional interface displayed on the first terminal device corresponding to the target plugin based on the first content. The second terminal device receives an update instruction sent by the first terminal device, the update instruction including second content; the second terminal device updates the displayed function interface according to the second content included in the update instruction, so as to display the updated function interface.

2. The method according to claim 1, characterized in that, The display instruction further includes display requirements; the second terminal device displays a functional interface corresponding to the target plugin based on the shared data display, including: The second terminal device displays the functional interface corresponding to the target plugin according to the display requirements based on the shared data.

3. The method according to claim 1, characterized in that, Before the second terminal device displays the functional interface corresponding to the target plugin based on the shared data, it further includes: The second terminal device receives confirmation information sent by the first terminal device, the confirmation information being used to determine whether the installation package of the target plugin exists; If the confirmation information determines that the installation package does not exist, the second terminal device sends a request to the first terminal device for the installation package of the target plugin. The system receives the installation package of the target plugin sent by the first terminal device based on the request information, and installs the target plugin based on the installation package.

4. The method according to claim 1, characterized in that, After the second terminal device displays the functional interface corresponding to the target plugin based on the shared data, it further includes: The second terminal device obtains the running status of the target plugin on the second terminal device and information about the second terminal device; The system sends the running status and information about the second terminal device to the first terminal device, so that the first terminal device generates a test form for the target plugin based on the running status and information about the second terminal device. The test form is used to analyze the performance of the target plugin in the second terminal device.

5. A method for managing plug-in functionality, characterized in that, The method is applied to a first terminal device, which is connected to a second terminal device via an intranet. The first and second terminal devices have the same application installed, and the first terminal device has a target plugin for the application installed. The same application can create consistent execution conditions for the target plugin on different devices. The method includes: The first terminal device sends a display instruction to the second terminal device through the intranet. The display instruction includes shared data related to the function of the target plugin. The display instruction is used by the second terminal device to write the shared data into different display parts corresponding to the functional interface of the target plugin for display. The first terminal device communicates with multiple second terminal devices in a network. The first terminal device sends different subsets of the shared data to different second terminals, so that each second terminal device renders different display parts of the functional interface of the target plugin. The functional interface is used to implement the function of the target plugin. The first terminal device and the second terminal device keep data change synchronization. The first terminal device receives first content sent by the second terminal device, the first content being content obtained by the second terminal device by changing the function interface; the first terminal device changes the function interface displayed on the first terminal device corresponding to the target plugin based on the first content; The first terminal device sends an update instruction to the second terminal device. The update instruction includes second content, which is obtained after the first terminal device updates the function interface. The update instruction is used by the second terminal device to update the function interface displayed by the second terminal device according to the second content included in the update instruction, so as to display the updated function interface.

6. The method according to claim 5, characterized in that, The display instruction also includes a display requirement; the display instruction is used by the second terminal device to display a functional interface corresponding to the target plugin based on the shared data and in accordance with the display requirement.

7. The method according to claim 5, characterized in that, After the first terminal device sends a display command to the second terminal device through the intranet, the method further includes: The first terminal device sends a confirmation message to the second terminal device, the confirmation message being used by the second terminal device to determine whether the installation package of the target plugin exists; Receive a request message sent by the second terminal device when it is determined, based on the confirmation information, that the installation package does not exist; Based on the request information, the installation package of the target plugin is sent to the second terminal device.

8. The method according to claim 5, characterized in that, After the first terminal device sends a display command to the second terminal device through the intranet, the method further includes: Receive the target plugin's running status on the second terminal device and information about the second terminal device sent by the second terminal device; A test form for the target plugin is generated based on the operating status and information of the second terminal device. The test form is used to analyze the performance of the target plugin in the second terminal device.

9. A management system with plug-in functionality, characterized in that, The system includes a first terminal device and a second terminal device, the first terminal device and the second terminal device are connected via an intranet, the second terminal device is used to execute the management method of the plug-in function according to any one of claims 1-4, and the first terminal device is used to execute the management method of the plug-in function according to any one of claims 5-8.

10. A computer device, characterized in that, The computer device includes a processor and a memory, the memory storing at least one computer program, the at least one computer program being loaded and executed by the processor to enable the computer device to implement the plug-in function management method as described in any one of claims 1 to 4, or to enable the computer device to implement the plug-in function management method as described in any one of claims 5 to 8.

11. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores at least one computer program, which is loaded and executed by a processor to enable the computer to implement the plug-in function management method as described in any one of claims 1 to 4, or to enable the computer to implement the plug-in function management method as described in any one of claims 5 to 8.

Images