A method, storage medium and terminal for establishing information sharing between plug-ins

Abstract

This application discloses a method, storage medium, and terminal for establishing information sharing between plugins, used to trigger the opening of an application using a plugin, thereby improving the interaction efficiency between plugins. This application provides a method for establishing information sharing between plugins, applied to a terminal whose operating system is configured with a first plugin, an application, and a second plugin. The method includes: calling the first plugin to obtain first information input by an operation object, and triggering the application to open to send the first information to the application; running the application to write the first information into an application group file, and triggering the second plugin to perform a first update operation; and calling the second plugin to obtain the first information from the application group file and execute the control function of the second plugin according to the first information.

Description

Technical Field

[0001] The embodiments of the present application relate to the technical field of client plug-ins, and more particularly to a method, storage medium, and terminal for establishing information sharing between plug-ins. Background Art

[0002] At present, in order to implement the file sharing mechanism, the operating system on the mobile terminal needs to transmit information between different plug-ins so that multiple plug-ins can read and write group files at the same time, thereby achieving the purpose of file sharing. However, for security reasons, the operating system on the mobile terminal cannot implement the file sharing mechanism for some plug-ins, that is, the file sharing between a certain plug-in and other plug-ins is disabled. For example, if a plug-in (i.e., plug-in a) does not have the permission to write to the group file, another plug-in cannot obtain the information that plug-in a needs to write, that is, the operating system will restrict the permission of some plug-ins to read or write group files, reducing the interaction efficiency between plug-ins.

[0003] For example, the operating system on the mobile terminal can realize the phone management function required by the user. If the user wants to report a certain phone number, he must copy the number himself, then manually open the call report plug-in, and then manually paste and submit operations to complete the reporting operation of the harassing call. The harassing phone number entered by the user may not be written to the group file, and the call blocking plug-in cannot read the group file, so the call blocking plug-in cannot timely intercept the harassing phone number set by the user. Summary of the invention

[0004] The embodiments of the present application provide a method, storage medium and terminal for establishing information sharing between plug-ins, which are used to use plug-ins to trigger the opening of applications and improve the interaction efficiency between plug-ins.

[0005] The embodiments of the present application provide the following technical solutions:

[0006] On the one hand, an embodiment of the present application provides a method for establishing information sharing between plug-ins, the method being applied to a client, wherein the operating system of the client is configured with a first plug-in, an application, and a second plug-in, wherein the method comprises:

[0007] calling the first plug-in to obtain first information input by a user, and triggering the application to open, so as to send the first information to the application;

[0008] Running the application to write the first information into an application group file and trigger the second plug-in to perform a first update operation;

[0009] The second plug-in is called to obtain the first information from the application group file, and the control function of the second plug-in is executed according to the first information.

[0010] On the other hand, an embodiment of the present application further provides a client, wherein an operating system of the client is configured with a first plug-in, an application program, and a second plug-in, wherein the client includes:

[0011] a first plug-in operation module, configured to call the first plug-in to obtain first information input by a user, and trigger the application to open, so as to send the first information to the application;

[0012] an application operation module, configured to run the application to write the first information into an application group file and trigger the second plug-in to perform a first update operation;

[0013] The second plug-in operation module is used to call the second plug-in to obtain the first information from the application group file and execute the control function of the second plug-in according to the first information.

[0014] In the aforementioned aspect, the constituent modules of the client may also execute the steps described in the aforementioned aspect and various possible implementations. For details, see the aforementioned description of the aforementioned aspect and various possible implementations.

[0015] On the other hand, an embodiment of the present application further provides a method for managing caller numbers based on call records, the method being applied to a caller management client having a call report plug-in and a caller mark management plug-in installed thereon, for managing caller numbers on a mobile terminal, the caller management client being installed thereon; wherein the method comprises:

[0016] Receiving a first trigger operation of a user on a communication number in a recent call record page of the mobile terminal;

[0017] In response to the first trigger operation, activating and displaying a call report management control;

[0018] Receiving a second trigger operation for the incoming call report management control, and displaying an incoming call mark management page on the recent call record page; wherein the incoming call mark management page displays at least one mark management label and at least one mark management control;

[0019] Receiving a third trigger operation of the user on a tag management label and / or a tag management control of the incoming call tag management page;

[0020] In response to the third trigger operation, a prompt message indicating successful marking of the communication number is displayed on the incoming call marking management page.

[0021] On the other hand, an embodiment of the present application further provides a call management client, wherein the call management client is installed with a call report plug-in and a call mark management plug-in for marking and managing the call number on the mobile terminal, and the call management client is installed on the mobile terminal; wherein the call management client includes:

[0022] A receiving module, configured to receive a first trigger operation of a user on a communication number in a recent call record page of the mobile terminal;

[0023] A processing module, configured to activate and display a call report management control in response to the first trigger operation;

[0024] The receiving module is further configured to receive a second trigger operation for the incoming call report management control,

[0025] A sending module, configured to display an incoming call mark management page on the recent call record page; wherein the incoming call mark management page displays at least one mark management label and at least one mark management control;

[0026] The receiving module is further used to receive a third trigger operation of the user on the tag management label and / or the tag management control of the incoming call tag management page;

[0027] The sending module is further configured to display a successful marking prompt message for the communication number on the incoming call marking management page in response to the third trigger operation.

[0028] On the other hand, an embodiment of the present application provides a terminal, which includes: a processor and a memory; the memory is used to store instructions; the processor is used to execute the instructions in the memory, so that the terminal executes any method as described in the aforementioned aspect.

[0029] On the other hand, an embodiment of the present application provides a computer-readable storage medium, wherein the computer-readable storage medium stores instructions, which, when executed on a computer, enable the computer to execute the methods described in the above aspects.

[0030] In an embodiment of the present application, the operating system of the client is configured with a first plug-in, an application, and a second plug-in. First, the first plug-in is called to obtain the first information input by the user, and the application is triggered to open to send the first information to the application. Next, the application is run to write the first information into the application group file, and the second plug-in is triggered to perform the first update operation. Finally, the second plug-in is called to obtain the first information from the application group file, and the control function of the second plug-in is executed according to the first information. In the embodiment of the present application, the two plug-ins in the client do not need to interact directly. After the first plug-in obtains the first information, the first plug-in can trigger the application to open, so that the application can obtain the first information. The application can also write the first information into the application group file. The application also triggers the second plug-in to perform the first update operation. The second plug-in can obtain the first information from the application group file under the triggering of the application. Finally, the second plug-in can execute the control function of the second plug-in according to the first information. In the embodiment of the present application, the first plug-in is called to trigger the application to open, so that the interaction efficiency between the plug-ins can be improved. BRIEF DESCRIPTION OF THE DRAWINGS

[0031] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for use in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the embodiments of the present application. For those skilled in the art, other drawings can also be obtained based on these drawings.

[0032] Figure 1 A flowchart of a method for establishing information sharing between plug-ins provided in an embodiment of the present application;

[0033] Figure 2a A flowchart of calling a first plug-in to obtain first information input by a user provided in an embodiment of the present application;

[0034] Figure 2b A schematic diagram of a flow chart of triggering an application to be opened to send first information to the application provided in an embodiment of the present application;

[0035] Figure 3 A flowchart of another method for establishing information sharing between plug-ins provided in an embodiment of the present application;

[0036] Figure 4a A schematic diagram of the reporting process of a harassing phone number provided in an embodiment of the present application;

[0037] Figure 4b A schematic diagram of a process for updating a harassing phone number to a system interception library provided in an embodiment of the present application;

[0038] Figure 5A schematic diagram of a plug-in triggering the opening of a main App provided in an embodiment of the present application;

[0039] Figure 6 A schematic diagram of the interaction flow between an application and two plug-ins in a harassing phone number reporting scenario provided in an embodiment of the present application;

[0040] Figure 7a A schematic diagram of a recent call record interface of a client provided in an embodiment of the present application;

[0041] Figure 7b A schematic diagram of a user reporting a harassing phone number provided in an embodiment of the present application;

[0042] Figure 7c A schematic diagram of the recent call record interface of the client provided in the application embodiment pulling up the report page of the mobile phone manager;

[0043] Figure 7d A schematic diagram of a user marking a phone number as a harassing phone number provided in an embodiment of the application;

[0044] Figure 7e A schematic diagram of automatically opening the mobile phone manager from the recent call record interface of the client provided in the application embodiment;

[0045] Figure 7f A schematic diagram of a mark type displayed when a user returns to the recent call record interface provided by an embodiment of the present application;

[0046] Figure 7g A schematic diagram of a client timely displaying harassing phone numbers provided in an embodiment of the present application;

[0047] Figure 8a A schematic diagram of the structure of a client provided in an embodiment of the present application;

[0048] Figure 8b A schematic diagram of the composition structure of a first plug-in operation module provided in an embodiment of the present application;

[0049] Figure 8c A schematic diagram of the composition structure of another first plug-in operation module provided in an embodiment of the present application;

[0050] Fig. 9 A schematic diagram of the composition structure of a terminal in which the method for establishing information sharing between plug-ins provided in an embodiment of the present application is applied. DETAILED DESCRIPTION

[0051] The embodiments of the present application provide a method, storage medium and terminal for establishing information sharing between plug-ins, which are used to use plug-ins to trigger the opening of applications and improve the interaction efficiency between plug-ins.

[0052] In order to make the purpose, features, and advantages of the embodiments of the present application more obvious and easy to understand, the technical solutions in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the embodiments described below are only part of the embodiments of the present application, not all of them. All other embodiments obtained by those skilled in the art based on the embodiments in the embodiments of the present application belong to the scope of protection of the embodiments of the present application.

[0053] The terms "including" and "having" and any variations thereof in the specification and claims of the embodiments of the present application and the above-mentioned drawings are intended to cover non-exclusive inclusions, so that a process, method, system, product or apparatus that includes a series of units is not necessarily limited to those units, but may include other units not expressly listed or inherent to these processes, methods, products or apparatuses.

[0054] The following are detailed descriptions of each.

[0055] An embodiment of the method for establishing information sharing between plug-ins in the embodiment of the present application can be specifically applied to the control function execution scenario of the plug-in in the client-based operating system. In the embodiment of the present application, at least two different types of plug-ins are configured in the operating system of the client. The plug-ins configured on the operating system can execute specific control functions. Different plug-ins can be used in different plug-in control function execution scenarios. For example, in the scenario of reporting harassing phone numbers, the plug-in configured on the operating system can be a call report plug-in, or a call blocking and identity recognition plug-in. For example, in a web page interception scenario, the plug-in configured on the operating system can be a web page detection plug-in, or a web page interception plug-in. For example, in an intelligent voice system interaction scenario, the plug-in configured on the operating system can be a voice recognition plug-in, or an instruction execution plug-in.

[0056] In the embodiment of the present application, in addition to configuring at least two different types of plug-ins in the client's operating system, the client's operating system is also configured with an application. The application has multiple implementation methods for different execution scenarios of the plug-in's control function. An example is given below. In the scenario of reporting harassing phone numbers, the application configured on the operating system may be a phone management application, such as the "Mobile Manager" application on the terminal. For another example, in a web page interception scenario, the application configured on the operating system may be a web page management application. For another example, in an intelligent voice system interaction scenario, the application configured on the operating system may be an intelligent voice control application.

[0057] See also Figure 1 As shown, a method for establishing information sharing between plug-ins provided in one embodiment of the present application may include the following steps:

[0058] 101. Call a first plug-in to obtain first information input by a user.

[0059] In an embodiment of the present application, a first plug-in is run in the operating system of the client, and the first plug-in can obtain the first information input by the user. For example, the user can swipe left on the display interface of the client. When the user swipes left, the client calls the first plug-in to obtain the first information input by the user. The first information input by the user in the client is used to indicate the control function that the user needs to implement. For example, in a harassing phone number reporting scenario, the first information input by the user can be the harassing phone number reported by the user. It is not limited that the first information can also include the user's report type and whether to intercept. For example, in a web page interception scenario, the first information input by the user can be the web page address reported by the user. For example, in an intelligent voice system interaction scenario, the first information input by the user can be the user's voice command.

[0060] In some embodiments of the present application, Figure 2a As shown, step 101 calls the first plug-in to obtain the first information input by the user, including:

[0061] 1011. Loading a first plug-in on a display interface of a client;

[0062] 1012. Calling a first plug-in to receive first information input by a user on a display interface;

[0063] 1013. Detect a completion instruction input by the user on the display interface. When the completion instruction is detected, trigger the execution of the following step 102: trigger the application to open to send the first information to the application.

[0064] The client has a touch screen, which may have a display interface. The user may issue a trigger instruction on the touch screen to interact with the client. The first plug-in is loaded in the operating system of the client, for example, the first plug-in is loaded on the display interface of the client. The user first "swipes left" on the display interface and then enters the first information. At this time, the first plug-in can receive the first information entered by the user. When the user completes the input on the display interface, the user can enter a completion instruction. The first plug-in can detect whether the user issues a completion instruction. When the completion instruction is not detected, it means that the user may continue to enter new information. At this time, the first plug-in can continue to receive new information entered by the user. When the first plug-in detects the completion instruction, it means that the user has completed the information input. At this time, the first plug-in determines that the user will not enter any more information. The client can trigger the subsequent step 102: triggering the application to open to send the first information to the application.

[0065] 102. Triggering an application to open to send first information to the application.

[0066] In an embodiment of the present application, after the first plug-in obtains the first information input by the user, the first plug-in can trigger the opening of the application, wherein the client's operating system has an application pre-installed, and the application and the first plug-in are pre-configured in the client's operating system based on the same plug-in control function execution scenario, and the first plug-in can open the application. For example, the first plug-in can pull the user graphical interface (UI) displayed by the application extension, so that the first plug-in can send the first information to the application. For the specific implementation scenario of the first plug-in and the application, the above examples are detailed.

[0067] In the embodiment of the present application, the operating system of the client may be an IOS system or an Android system. Based on the different system types of the operating system of the client, the triggering opening method between the first plug-in and the application is also different. For example, the operating system of the client may be an IOS system, and the client may use a link address to pull up the extended interface of the application so that the operating system of the client can run the application. The link address may specifically be a uniform resource locator (URL).

[0068] In some embodiments of the present application, Figure 2b As shown, step 102 triggers the application to open to send the first information to the application, including:

[0069] 1021. Encapsulate the first information into the link address;

[0070] 1022. Calling an open link address interface of the application program to send a link address to the application program. The open link address interface is used to trigger the application program to run on a display interface of the client.

[0071] Among them, after the first plug-in obtains the first information input by the user, the first plug-in encapsulates the first information and encapsulates the first information into a link address, for example, the first information is encapsulated into a URL. The application is configured with an open link address interface, and the first plug-in can call the open link address interface. For example, the open link address interface can be the openURL interface of the application. The first plug-in uses the open link address interface to pass the aforementioned link address. Since the first information is encapsulated in the link address, the application can start running after the open link address interface is called and display it to the user on the display interface of the client. For example, the client switches from displaying the first plug-in to displaying the application. The specific application running on the display interface of the client can be determined according to the specific control function execution scenario of the plug-in. For details, see the aforementioned example description of the application.

[0072] In some embodiments of the present application, the first plug-in is a call report plug-in, and the application is a phone management application. The aforementioned step 102 triggers the application to open to send the first information to the application, including:

[0073] The incoming call report plug-in is called to trigger the phone management application to run on the display interface of the client, and the harassing phone number mark information input by the user is sent to the phone management application.

[0074] Among them, the first plug-in can be a call report plug-in, and the application can be a phone management application, for example, it can be a "Mobile Manager" main App. The call report plug-in will encapsulate the first information consisting of the harassing phone number reported by the user, the selected mark type, whether to intercept, etc. into a URL, and call the openURL interface of the application to automatically open the Mobile Manager main App, so that the Mobile Manager main App can use the openURL interface to receive the encapsulated first information. The Mobile Manager main App parses the encapsulated first information and can obtain the harassing phone number reported by the user, the selected mark type, whether to intercept, and other information content.

[0075] In some embodiments of the present application, calling the first plug-in to call the open link address interface of the application program includes:

[0076] Get the view control class of the first plug-in;

[0077] Traverse the event response chain of the view control class to determine the terminal user interface response class of the first plug-in;

[0078] Get the user interface application object associated with the terminal user interface response class;

[0079] The application is called to run according to the user interface application object.

[0080] Among them, the first plug-in running in the client's operating system includes a view control class, which is used to implement the client's view control function, for example, the view control class can be a ViewController class. After obtaining the view control class, the first plug-in can traverse the event response chain of the view control class, and multiple user interface response classes are associated in the event response chain. For example, the user interface response class can be a UIResponder class. Multiple user interface response classes with an association relationship in the event response chain are associated in sequence. For example, the first plug-in can use the view control class to associate with the first user interface response class in the event response chain, and then the first user interface response class associates the next user interface response class in the event response chain. The next user interface response class continues to associate the next user interface response class in the event response chain until the first plug-in determines the last terminal user interface response class in the first plug-in, that is, the terminal user interface response class. After the first plug-in determines the terminal user interface response class, the first plug-in can also obtain the user interface application object associated with the terminal user interface response class, wherein the user interface application object is an object that triggers the running of the application, for example, the user interface application object can be the UIApplication object of the application. After the first plug-in determines the user interface application object of the application, it calls the application to run according to the user interface application object, so that the application can run on the display interface of the client under the triggering of the first plug-in.

[0081] An example is given below. In the scenario of reporting harassing phone numbers, the client can traverse the event response chain of the ViewController class of the plug-in. The ViewController class first finds the UIResponder class in the event response chain. Among them, ViewController inherits from UIResponder. UIResponder is the base class for handling users and screens in the iOS system. ViewController is the class for handling App interfaces. For example, the logic in the interface displayed in the recent call log can be managed by a ViewController. UIResponder can use the nextResponder method to get the next UIResponder of a UIResponder, thereby traversing the entire event response chain of a UIResponder. Finally, by traversing the event response chain of the ViewController class of the plug-in, the UIApplication object of the main App can be found, so that the main App can be called to run. In this way, the openURL: method of the main App can be called to pass in the URL Scheme of the main App to pull up the main App, and the relevant information can be passed from the URLScheme to the main App, thereby achieving the purpose of communication between the plug-in and the main App, and realizing the purpose of communication and data transmission between the plug-in and the main App.

[0082] 103. Run the application to write the first information into the application group file and trigger the second plug-in to perform the first update operation.

[0083] In the embodiment of the present application, after the client calls the first plug-in to trigger the application to run, the application can obtain the first information from the first plug-in, and then the application writes the first information into the application group file, wherein the application group file can store the information received by the application, and the application group file is used to realize data sharing between the application and the plug-in. For example, the application group file can be an App Group file, and the use of the App Group file can realize the file sharing mechanism in the iOS system, and the main App and the plug-in can read and write files in the App Group at the same time, thereby achieving the purpose of data sharing.

[0084] In an embodiment of the present application, the application writes the first information into the application group file, and the application can also trigger the second plug-in to read the information in the application group file, for example, the application triggers the second plug-in to perform the first update operation, wherein the second plug-in is another plug-in different from the first plug-in pre-configured in the client's operating system, and the second plug-in needs to obtain the first information of the first plug-in, and the second plug-in can be triggered to run by the application. For example, in the scenario of reporting harassing phone numbers, the first plug-in configured on the operating system can be a call report plug-in, and the second plug-in configured on the operating system can be a call blocking and identity recognition plug-in. For another example, in a web page interception scenario, the first plug-in configured on the operating system can be a web page detection plug-in, and the second plug-in can be a web page interception plug-in. For another example, in an intelligent voice system interaction scenario, the first plug-in configured on the operating system can be a voice recognition plug-in, and the second plug-in can be an instruction execution plug-in.

[0085] In some embodiments of the present application, step 103 calls the second plug-in to obtain the first information from the application group file, including:

[0086] Invoking a second plug-in to read the first information from a local information repository of the application group file;

[0087] The first information is updated into a system information base of the client.

[0088] Among them, after the application obtains the first information from the first plug-in, the application can store the first information in the local information library of the application group file. The second plug-in can read the local information library of the application group file under the trigger of the application to read the first information from the local information library. After the second plug-in reads the first information, the second plug-in can also use the first information to update the system information library of the client, so that the first information can be obtained in time in the system information library of the client. When the second plug-in executes the control function of the second plug-in, it can extract the first information based on the system information library, so that the second plug-in can execute the control function of the second plug-in according to the first information. For example, the first information may include: a harassing phone number provided by the user, a mark type, and whether to intercept. When the second plug-in runs on the display interface of the client, the second plug-in can identify whether the current incoming call number is a harassing phone number according to the first information, and determine whether to intercept the current phone number according to the first information, and determine the displayed mark type.

[0089] 104. Call the second plug-in to obtain the first information from the application group file, and execute the control function of the second plug-in according to the first information.

[0090] In an embodiment of the present application, after the second plug-in is triggered by the application, the second plug-in executes a first update operation, and the first update operation refers to the second plug-in obtaining the first information from the application group file under the triggering of the application. After the second plug-in obtains the first information, the second plug-in can execute the control function of the second plug-in according to the first information, that is, the second plug-in can respond to the first update operation and execute the control function of the second plug-in itself. For example, in the scenario of reporting harassing phone numbers, the second plug-in can be a call blocking and identity identification plug-in, and the control function of executing the second plug-in can be marking and intercepting harassing phone numbers. For another example, in the scenario of web page interception, the second plug-in can be a web page interception plug-in, and the control function of executing the second plug-in can be intercepting illegal web pages. For another example, in the scenario of intelligent voice system interaction, the second plug-in can be an instruction execution plug-in, and the control function of executing the second plug-in can be controlling the client's operating system behavior according to voice instructions.

[0091] In some embodiments of the present application, the second plug-in is a call blocking and identification plug-in; step 104 calls the second plug-in to obtain the first information from the application group file, and executes the control function of the second plug-in according to the first information, including:

[0092] The call blocking and identification plug-in is called to obtain the harassing phone number marking information from the application group file, and then the phone number marked by the harassing phone number marking information is displayed on the display interface of the client as a harassing phone number.

[0093] Among them, the first plug-in can be a call report plug-in, and the application can be a phone management application, such as the "Mobile Manager" main App. The call report plug-in will encapsulate the first information consisting of the harassing phone number reported by the user, the selected mark type, whether to intercept, etc. into a URL, and call the openURL interface of the application to automatically open the Mobile Manager main App, so that the Mobile Manager main App can use the openURL interface to receive the encapsulated first information. The Mobile Manager main App parses the encapsulated first information and can obtain the harassing phone number reported by the user, the selected mark type, whether to intercept, etc. The call blocking and identification plug-in obtains the harassing phone number mark information from the application group file, and displays the harassing phone number mark information on the display interface of the client. The marked phone number is a harassing phone number, and the current harassing phone number can be intercepted, and the mark type corresponding to the harassing phone number can be displayed.

[0094] In some embodiments of the present application, Figure 3As shown, after step 101 calls the first plug-in to obtain the first information input by the user, the method for establishing information sharing between plug-ins provided in the embodiment of the present application may further include the following steps in addition to executing the aforementioned steps 101 to 104:

[0095] 105. Call the first plug-in to send first information to the application server.

[0096] The client can also interact with the application server. For example, when the application running on the client's operating system is the mobile phone manager main App, the application server can be the mobile phone manager backend server. After obtaining the first information input by the user, the first plug-in can also send the first information to the application server. For example, the first information can be a report information sent by the user.

[0097] 106. Run the application to receive second information sent by the application server according to the first information.

[0098] After receiving the first information, the application server may analyze the first information. For example, the application server counts whether the number of reports of harassing phone numbers reported by users reaches a threshold value based on the first information. The application server may determine whether to send the second information based on the first information. When the conditions for sending the second information are met, the application server may send the second information to the application based on the first information. For example, when the number of reports of harassing phone numbers reported by users reaches a threshold value, the application server sends an interception instruction to the application.

[0099] 107. Write the second information into the application group file, and trigger the second plug-in to perform a second update operation.

[0100] The application program running on the client can receive the second information sent by the application program server according to the first information, and then the application program writes the second information into the application program group file and triggers the second plug-in to perform the second update operation.

[0101] 108. Call the second plug-in to obtain second information from the application group file, and execute the control function of the second plug-in according to the second information.

[0102] The second plug-in can obtain the second information from the application group file and execute the control function of the second plug-in according to the second information. It should be noted that the way the second plug-in reads the second information and the control function executed based on the second information are similar to the way the second plug-in processes the first information, which will not be repeated here.

[0103] Through the description of the embodiment of the present application in the above embodiment, it can be known that the operating system of the client is configured with a first plug-in, an application, and a second plug-in. First, the first plug-in is called to obtain the first information input by the user, and then the application is triggered to open to send the first information to the application. Next, the application is run to write the first information into the application group file, and the second plug-in is triggered to perform the first update operation. Finally, the second plug-in is called to obtain the first information from the application group file, and the control function of the second plug-in is executed according to the first information. In the embodiment of the present application, the two plug-ins in the client do not need to interact directly. After the first plug-in obtains the first information, the first plug-in can trigger the application to open, so that the application can obtain the first information. The application can also write the first information into the application group file. The application also triggers the second plug-in to perform the first update operation. The second plug-in can obtain the first information from the application group file under the triggering of the application. Finally, the second plug-in can execute the control function of the second plug-in according to the first information. In the embodiment of the present application, calling the first plug-in to trigger the application to open can improve the interaction efficiency between plug-ins.

[0104] In order to better understand and implement the above-mentioned solutions in the embodiments of the present application, the following examples are given for specific explanation by using corresponding application scenarios.

[0105] Next, the execution process of the method for establishing information sharing between plug-ins provided in the embodiment of the present application is explained by taking the harassing phone number reporting scenario as an example. For example, the first plug-in is a call report plug-in, the application is a phone management application, and the second plug-in is a call blocking and identity recognition plug-in. For example, the application can be the "Mobile Manager" main App, and the application server can be the "Mobile Manager" background server.

[0106] In the embodiment of the present application, the client has the function of integrating iOS harassment blocking, so that the user can see the report result immediately in the system call record interface after reporting, and the system phone can display the type marked by the user the next time the number calls.

[0107] First, the call report plug-in in the embodiment of the present application is introduced. The call report plug-in refers to the Short Messaging Service (SMS) and call report (Call Reporting). The call report is a plug-in launched by the iOS operating system version 11 for reporting harassing text messages and phone calls. This plug-in can be implemented to display the reporting page on the system's recent call record page and report the reporting information to the configured URL, thereby enriching its own harassing call library.

[0108] The call report plug-in is an interface for detecting incoming call numbers in the iOS system. It can provide users with a convenient function to quickly mark call records. At the same time, it can report the marked numbers and marking types to the cloud to enrich the existing number library. Figure 4a As shown, it is a schematic diagram of the reporting process of harassing phone numbers provided in the embodiment of the present application. After the user swipes left on the display interface of the client, the report page is called up. After the user reports to the call report plug-in on the display interface of the client, the call report plug-in can obtain 1. The reporting type selected by the user, 2. After the user clicks "Finish", the call report plug-in can detect the user's completion, and then the client reports to the application server. For example, when the number of reports of the harassing phone number reported by the user reaches the threshold, the application server sends an interception instruction to the application. In the embodiment of the present application, the path in the user's reporting process is shorter, and there is no need to manually enter the App, and the operation can be completed directly in the system call record.

[0109] Furthermore, in order to enable users to feel that the mark is effective in real time, Figure 4b As shown, it is a flow chart of updating the harassing phone number to the system interception library provided by the embodiment of the present application. After the client obtains 1. the reporting type selected by the user and 2. the user clicks "Complete", the client can automatically jump to the phone management application from the first plug-in, and then the client automatically updates the local harassing interception library, and then automatically updates the system interception library, so as to realize the real-time effect of the harassing phone numbers marked by the user.

[0110] Specifically, the client calls the call report plug-in to pass the tag and number to the phone management application to update the local harassment blocking library. For example, first update the harassment blocking library in the App Group file, then notify the call and identity plug-in (that is, App extension), call the call and identity App extension to read the harassment blocking library in the App Group group file, and update the harassment blocking library of the iOS system.

[0111] Next, an example is given to illustrate the automatic redirection process of the call report plug-in to the mobile phone manager application. For example, the mobile phone manager application implements the redirection URLScheme to pass parameters, where URLScheme is a redirection method used to locate App resources in the iOS system. Developers can define their own URL schemes. For example, the URL scheme of the mobile phone manager is mqqsecure: / / , and parameters can be added after the URL scheme, such as mqqsecure: / / abc? a=parama&b=paramb, etc. The third-party App uses the call system interface openURL to pass the URL scheme to the method parameters to open the App. The App can parse the parameters of the third-party App to achieve communication between Apps. For App extensions, the URL scheme can also be used to communicate with the main App or other Apps.

[0112] Next, the process of opening an application program triggered by a plug-in is first illustrated. For example, in the aforementioned embodiment, the first plug-in can trigger the opening of an application program. For details, see the description of the first plug-in triggering the opening of an application program in step 102 in the aforementioned embodiment.

[0113] like Figure 5 As shown in the figure, it is a schematic diagram of a plug-in triggering the main App to open provided in the embodiment of the present application. The main App of the mobile phone manager can realize the jump from the call report plug-in to the main App. The specific process is as follows: the main App and the plug-in are two different processes, so they cannot communicate normally, and file sharing and normal jumps are also disabled by the system. In the embodiment of the present application, the client can traverse the event response chain of the plug-in's ViewController and find the UIApplication object of the main App, such as Figure 5 As shown, ViewController (for example, ViewController is a UIResponder) is used to continuously traverse its event response chain to find the UIApplication object of the main App, so that some methods of the main App can be called. In this way, the openURL: method of the main App can be called to pass in the URL Scheme of the main App to launch the main App, and the relevant information is transmitted by the URLScheme, thereby achieving the purpose of communication between the plug-in and the main App, solving the problem of communication and data transmission between the plug-in and the main App.

[0114] In an embodiment of the present application, the first plug-in may be a call blocking and identification plug-in (Call Blocking and Identification). Next, the first plug-in is used as an example of a call blocking and identification plug-in. Call blocking and identification is a plug-in launched in iOS operating system version 10 for marking and blocking harassing calls. The plug-in can write its own harassing call library into the system interception library, thereby displaying the marking information on the call record page when a harassing call comes in, and even achieving the function of blocking harassing calls.

[0115] In an embodiment of the present application, the second plug-in can be a call blocking and identity identification plug-in. The following is an example of the second plug-in being a call blocking and identity identification plug-in. The main App can use the local interception library to write to the system interception database, thereby updating the marking information of the recent call records.

[0116] Since Mobile Manager solves the problem of the plug-in marking data communicating with the main App, the marking data can be passed to the main App after marking with the call report plug-in. The main App then uses the system interface of the call blocking and identity recognition plug-in to update the marking data to the system interception database, so that the user's marked type can be immediately seen in the recent call records, and the system can also correctly display the user's marked type the next time a call is received from this number.

[0117] Finally, let’s introduce the App Group file. The App Group file is a file sharing mechanism introduced in iOS operating system version 8. The main app and plug-ins can read and write files in the App Group at the same time, thereby achieving the purpose of data sharing. The plug-in can also be called App extension.

[0118] Based on the foregoing introduction, it can be seen that the embodiment of the present application uses an interface that integrates the iOS system, shortens the user's operation path, solves the problem of communication between the plug-in and the main App, achieves real-time display of marked data, and real-time update of the local interception library, protecting users from secondary harassment.

[0119] like Figure 6 As shown, it is a schematic diagram of the interaction process between the application and the two plug-ins in the harassing phone number reporting scenario provided in the embodiment of the present application. The user first swipes left on the display interface of the client to call up the reporting page. The call report plug-in and the call blocking and identity recognition plug-in are pre-configured plug-ins on the iOS operating system. Next, the interaction process between the mobile phone manager main app and the call report plug-in and the call blocking and identity recognition plug-in in the iOS system is introduced, which mainly includes:

[0120] S01. The call report plug-in first obtains: 1. The phone number returned by the system. 2. The tag type selected by the user. 3. Whether to intercept.

[0121] The first plug-in may be the aforementioned call report plug-in. The client first calls the call report plug-in, the user swipes left on the call log page to call out the call report plug-in of the mobile phone manager, and then selects the mark type. At this time, the UI interface displayed by the App extension is used in the system's recent call log interface to obtain the user input information.

[0122] S02. The user clicks Finish.

[0123] S03, calling back the system interface to report. The system automatically reports the json data of the phone number and tag type to the application server.

[0124] When the user clicks Done, the call report plug-in will pass the information about the number reported by the user, the selected tag type, and whether to intercept to the system interface. The system interface triggers a network request to send the information to the mobile manager backend server.

[0125] When the number of reports exceeds the threshold, the mobile manager backend server will issue an interception instruction. After receiving the data reported by the client (the client here refers to the mobile manager App extended call report), the mobile manager backend server will store the data in the database and regularly organize the data in the database into a compressed encrypted file and store it in the content delivery network (Content Delivery Network, CDN). When the App is activated, the client (the client here refers to the mobile manager main App) will initiate a network request to pull this compressed file, so that the harassment interception library in the App Group can be updated.

[0126] The above steps S01 to S03 are detailed examples of step 101 in the above embodiment.

[0127] S04. OpenURL automatically opens the phone management application.

[0128] The above step S04 is a detailed example of step 102 in the above embodiment.

[0129] S11, allicaiton: parse parameters in handleOpenURL:.

[0130] S12. Parsing results in: 1. phone number, 2. tag type, 3. whether to intercept.

[0131] S13. Write the parsed data into the App Group file to trigger the plug-in update.

[0132] The call report plug-in will encapsulate the information such as the number reported by the user, the selected tag type, and whether to block into a URL, and call openURL to automatically open the main mobile manager app.

[0133] After automatically entering the main App of the mobile manager, the main App parses the information passed and writes the information into the App Group file. At the same time, the main App calls the system interface to trigger the call blocking and identity recognition plug-in to perform a refresh operation.

[0134] The above steps S11 to S13 are detailed examples of step 103 in the above embodiment.

[0135] S14. When the number of reported numbers exceeds a threshold, the number is sent to a telephone management application, and the telephone management application parses the update tag library sent from the cloud.

[0136] S15. Parse the sent tag database.

[0137] S21. Receive an update request.

[0138] S22. Read the App Group file content.

[0139] S23. Write the content in the App Group into the system interception library.

[0140] S24. Refresh the system recent call page UI.

[0141] The call blocking and identification plug-in receives a refresh request from the main App, reads the tag information in the App Group file (for example, including: harassing phone number, tag type, whether to block), and writes it into the system blocking library.

[0142] After call blocking and identity recognition are written into the system interception library, the UI of the recent call record interface is automatically updated, so that the user-marked type will be displayed in the recent call record page. The next time the number calls again, its marked type will also be displayed on the call record page.

[0143] The above steps S21 to S25 are detailed examples of step 104 in the above embodiment.

[0144] The embodiments of the present application can shorten the operation path for users to report harassing calls, and can also update the user's local harassment interception library in real time to protect the user from secondary harassment.

[0145] In the embodiment of the present application, the iOS system call report plug-in and call blocking and identification plug-in are integrated to provide users with the function of quickly marking harassing calls in the recent call log. Users can quickly mark calls by swiping left in the recent call log and immediately see the marked type in the recent call log.

[0146] The embodiment of the present application also provides a method for managing caller numbers based on call records. The method is applied to a caller management client installed with a call report plug-in and a caller mark management plug-in to manage caller numbers on a mobile terminal. The mobile terminal is installed with a caller management client, for example, the caller management client can be a mobile phone manager (or a mobile phone manager main app). The method provided in the embodiment of the present application includes the following steps:

[0147] S31. Receive a first trigger operation from a user on a communication number in a recent call record page of a mobile terminal.

[0148] In the embodiment of the present application, a call management client is installed on the mobile terminal, and the call management client can be used to mark and manage the caller numbers on the mobile terminal. A call report plug-in and a call mark management plug-in are installed in the call management client, wherein the call report plug-in is used to obtain the communication number in the recent call record page of the user for the mobile terminal. For example, the communication number in the recent call record page of the mobile terminal can be obtained. For example, Figure 7a A schematic diagram of the recent call record interface of the client provided in an embodiment of the present application, in the system's recent call records, for example, the call record displayed is the call record of the mobile phone number 13312345678.

[0149] S32: In response to the first trigger operation, activate and display the incoming call report management control.

[0150] In an embodiment of the present application, after detecting a first trigger operation of a user for a communication number, the call management client can activate and display a call report management control in response to the first trigger operation. The call report management control can be a control displayed to the user on the call management client. For example, Figure 7b This is a schematic diagram of a user reporting a harassing phone number provided in an embodiment of the present application. When you swipe left on the number you want to mark, "Report" will appear.

[0151] In some embodiments of the present application, in response to the first trigger operation, activating and displaying the incoming call report management control includes:

[0152] The incoming call report plug-in is called, and when the first trigger operation is detected, the incoming call report management control is activated and displayed.

[0153] Among them, the call management client can call the call report plug-in, and the call report plug-in detects whether the first trigger operation issued by the user can be detected. If the call report plug-in detects the first trigger operation issued by the user, the call report plug-in activates and displays the call report management control.

[0154] S33. Receive a second trigger operation for the incoming call report management control, and display an incoming call mark management page on the recent call record page; wherein the incoming call mark management page displays at least one mark management label and at least one mark management control.

[0155] In an embodiment of the present application, after the call management client displays the call report management control to the user, the user can issue a second trigger operation for the call report management control, and the call management client receives the second trigger operation and then displays the call tag management page on the recent call record page. Among them, the call tag management page can be used to receive the user's tag information for the communication number. For example, at least one tag management label and at least one tag management control are displayed on the call tag management page. There is no limit on the number of tag management labels and the number of tag management controls displayed on the call tag management page, and they can be flexibly configured in combination with specific application scenarios.

[0156] The following are some examples: Figure 7c A schematic diagram of the recent call record interface of the client provided in the application embodiment pulling up the report page of the mobile phone manager. The user clicks Report to pull up the report page of the mobile phone manager in the system's recent call record interface. Figure 7c In the figure, the number of mark management tags is 6 for illustration, for example, the mark management tags may include: advertising and promotion, real estate agency, fraudulent calls, express delivery, taxi, other harassment, etc.

[0157] S34: Receive a third trigger operation of the user on a tag management label and / or a tag management control on the incoming call tag management page.

[0158] In an embodiment of the present application, the call management client can display a tag management label and / or a tag management control on the call tag management page, and the user can issue a third trigger operation for the tag management label and / or the tag management control on the call tag management page. The call management client receives the user's third trigger operation, for example Figure 7d A schematic diagram of a user marking a phone number as a harassing phone number provided in an embodiment of the application, where the user selects the report type as a harassing call.

[0159] S35. In response to the third trigger operation, a prompt message indicating successful marking of the communication number is displayed on the incoming call marking management page.

[0160] In the embodiment of the present application, after the call management client detects the third trigger operation of the user, the call management client obtains the type of mark of a communication number by the user, and the call management client marks the communication number as a corresponding type, and then displays a successful marking prompt information for the communication number on the call mark management page, so that the user can see the prompt that the call management client has successfully marked on the call mark management page, for example, Figure 7e A schematic diagram of automatically opening the mobile phone manager on the client's recent call record interface provided in the application embodiment. After the user clicks Complete, the call report plug-in will automatically open the mobile phone manager main App in the system's recent call interface. Before opening the mobile phone manager, the iOS system displays an extended version of the mobile phone manager on the recent call record interface.

[0161] In some embodiments of the present application, in response to the third trigger operation, after displaying a successful marking prompt message for the communication number on the incoming call marking management page, the method provided in the embodiment of the present application further includes the following steps:

[0162] The caller tag management plug-in is called to open the caller management client on the recent call record page, so that the caller management client writes the tag management information for the communication number.

[0163] After the successful marking prompt message for the communication number is displayed on the caller mark management page, the caller mark management plug-in can be called to reopen the caller management client on the recent call record page, and the caller management client writes the mark management information for the communication number. Figure 7f A schematic diagram of displaying the marking type when a user returns to the recent call record interface provided in an embodiment of the present application, the call management client writes the marking information, and when the user returns to the system's recent call interface again, he can see the harassment type he marked.

[0164] In some embodiments of the present application, in response to the third trigger operation, after displaying a successful marking prompt message for the communication number on the incoming call marking management page, the method provided in the embodiment of the present application further includes the following steps:

[0165] When receiving a second call message for the communication number, the communication number is displayed as a harassing phone number on the call mark management page, and the call to the communication number is blocked.

[0166] In the embodiment of the present application, the interception of a certain communication number by the call management client takes effect immediately. If there is another call from the communication number in the mobile terminal, when the call management client receives the second call information for the communication number, it will display the communication number as a harassing phone number on the call mark management page and intercept the call from the communication number, so that real-time interception of a certain communication number can be achieved. For example, Figure 7g The client provided in the embodiment of the present application promptly displays a schematic diagram of a harassing phone number. The next time the number makes a call, the type of mark can be seen on the call interface.

[0167] It should be noted that, for the aforementioned method embodiments, for the sake of simplicity, they are all expressed as a series of action combinations, but those skilled in the art should be aware that the embodiments of the present application are not limited by the described order of actions, because according to the embodiments of the present application, certain steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also be aware that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily required by the embodiments of the present application.

[0168] In order to better implement the above-mentioned solution of the embodiment of the present application, relevant devices for implementing the above-mentioned solution are also provided below.

[0169] See also Figure 8a As shown, an embodiment of the present application provides a client 800, wherein the operating system of the client 800 is configured with a first plug-in, an application program, and a second plug-in, wherein the client 800 includes: a first plug-in operation module 801, an application program operation module 802, and a second plug-in operation module 803, wherein:

[0170] The first plug-in operation module 801 is used to call the first plug-in to obtain the first information input by the user; and trigger the opening of the application to send the first information to the application;

[0171] An application operation module 802, configured to run the application to write the first information into an application group file and trigger the second plug-in to perform a first update operation;

[0172] The second plug-in operation module 803 is used to call the second plug-in to obtain the first information from the application group file and execute the control function of the second plug-in according to the first information.

[0173] In some embodiments of the present application, Figure 8b As shown, the first plug-in operation module 801 includes:

[0174] A first plug-in loading unit 8011 is used to load the first plug-in on the display interface of the client;

[0175] An information receiving unit 8012 is used to call the first plug-in to receive the first information input by the user on the display interface;

[0176] The instruction detection unit 8013 is used to call the first plug-in to detect the completion instruction input by the user on the display interface. When the completion instruction is detected, the following steps are triggered: the application is triggered to open to send the first information to the application.

[0177] In some embodiments of the present application, Figure 8c As shown, the first plug-in operation module 801 includes:

[0178] An information encapsulation unit 8014 is used to encapsulate the first information into a link address;

[0179] The interface calling unit 8015 is used to call the open link address interface of the application to send the link address to the application, and the open link address interface is used to trigger the application to run on the display interface of the client.

[0180] In some embodiments of the present application, the interface calling unit 8015 is specifically used to obtain the view control class of the first plug-in; traverse the event response chain of the view control class to determine the terminal user interface response class of the first plug-in; obtain the user interface application object associated with the terminal user interface response class; and call the application to run according to the user interface application object.

[0181] In some embodiments of the present application, the first plug-in operation module 801 is further used to call the first plug-in to obtain the first information input by the user, and then send the first information to the application server;

[0182] The application operation module 802 is further configured to receive second information sent by the application server according to the first information;

[0183] The application operation module 802 is further used to write the second information into the application group file and trigger the second plug-in to perform a second update operation;

[0184] The second plug-in operation module 803 is further used to call the second plug-in to obtain the second information from the application group file, and execute the control function of the second plug-in according to the second information.

[0185] In some embodiments of the present application, the first plug-in is a call report plug-in, and the application is a phone management application;

[0186] The first plug-in operation module 801 is specifically used to call the incoming call report plug-in to trigger the phone management application to run on the display interface of the client, and send the harassing phone number mark information input by the user to the phone management application.

[0187] In some embodiments of the present application, the second plug-in is a call blocking and identification plug-in;

[0188] The second plug-in operation module 803 is specifically used to call the call blocking and identification plug-in to trigger the acquisition of the harassing phone number marking information from the application group file, and then display the phone number marked by the harassing phone number marking information as a harassing phone number on the display interface of the client.

[0189] Through the above description of the embodiment of the present application, it can be known that the operating system of the client is configured with a first plug-in, an application, and a second plug-in. First, the first plug-in is called to obtain the first information input by the user, and then the application is triggered to open to send the first information to the application. Next, the application is run to write the first information into the application group file, and the second plug-in is triggered to perform the first update operation. Finally, the second plug-in is called to obtain the first information from the application group file, and the control function of the second plug-in is executed according to the first information. In the embodiment of the present application, the two plug-ins in the client do not need to interact directly. After the first plug-in obtains the first information, the first plug-in can trigger the application to open, so that the application can obtain the first information. The application can also write the first information into the application group file. The application also triggers the second plug-in to perform the first update operation. The second plug-in can obtain the first information from the application group file under the trigger of the application. Finally, the second plug-in can execute the control function of the second plug-in according to the first information. In the embodiment of the present application, calling the first plug-in to trigger the application to open can improve the interaction efficiency between plug-ins.

[0190] The embodiment of the present application further provides a call management client, wherein the call management client is installed with a call report plug-in and a call mark management plug-in, for marking and managing the call number on the mobile terminal, and the call management client is installed on the mobile terminal; wherein the call management client includes:

[0191] A receiving module, configured to receive a first trigger operation of a user on a communication number in a recent call record page of the mobile terminal;

[0192] A processing module, configured to activate and display a call report management control in response to the first trigger operation;

[0193] The receiving module is further configured to receive a second trigger operation for the incoming call report management control,

[0194] A sending module, configured to display an incoming call mark management page on the recent call record page; wherein the incoming call mark management page displays at least one mark management label and at least one mark management control;

[0195] The receiving module is further used to receive a third trigger operation of the user on the tag management label and / or the tag management control of the incoming call tag management page;

[0196] The sending module is further configured to display a successful marking prompt message for the communication number on the incoming call marking management page in response to the third trigger operation.

[0197] In some embodiments of the present application, the processing module is used to call the incoming call report plug-in, and when the first trigger operation is detected, activate and display the incoming call report management control.

[0198] In some embodiments of the present application, the processing module is used to respond to the third trigger operation, after displaying a prompt message of successful marking for the communication number on the caller marking management page, call the caller marking management plug-in to open the caller management client on the recent call record page, so that the caller management client writes the marking management information for the communication number.

[0199] In some embodiments of the present application, the processing module is used to display the communication number as a harassing phone number on the call mark management page when receiving the second call information for the communication number, and intercept the call to the communication number.

[0200] The present application embodiment also provides another terminal, such as Fig. 9 For the sake of convenience, only the parts related to the embodiments of the present application are shown. For specific technical details not disclosed, please refer to the method part of the embodiments of the present application. The terminal can be any terminal device including a mobile phone, a tablet computer, a PDA (Personal Digital Assistant), a POS (Point of Sales), a car computer, etc., taking the mobile phone as an example:

[0201] Fig. 9 FIG. 1 is a block diagram showing a partial structure of a mobile phone related to a terminal provided in an embodiment of the present application. Fig. 9The mobile phone includes: a radio frequency (RF) circuit 910, a memory 920, an input unit 930, a display unit 940, a sensor 950, an audio circuit 960, a wireless fidelity (WiFi) module 970, a processor 980, and a power supply 990. Those skilled in the art will understand that Fig. 9 The mobile phone structure shown in the figure does not constitute a limitation on the mobile phone, and may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently.

[0202] Combine the following Fig. 9 A detailed introduction to the various components of the mobile phone:

[0203] The RF circuit 910 can be used for receiving and sending signals during the process of sending and receiving information or making calls. In particular, after receiving the downlink information of the base station, it is sent to the processor 980 for processing; in addition, the designed uplink data is sent to the base station. Generally, the RF circuit 910 includes but is not limited to an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier (Low Noise Amplifier, LNA), a duplexer, etc. In addition, the RF circuit 910 can also communicate with the network and other devices through wireless communication. The above-mentioned wireless communication can use any communication standard or protocol, including but not limited to the Global System of Mobile communication (Global System of Mobile communication, GSM), General Packet Radio Service (General Packet Radio Service, GPRS), Code Division Multiple Access (Code Division Multiple Access, CDMA), Wideband Code Division Multiple Access (Wideband Code Division Multiple Access, WCDMA), Long Term Evolution (Long Term Evolution, LTE), email, Short Messaging Service (SMS), etc.

[0204] The memory 920 can be used to store software programs and modules. The processor 980 executes various functional applications and data processing of the mobile phone by running the software programs and modules stored in the memory 920. The memory 920 can mainly include a program storage area and a data storage area, wherein the program storage area can store an operating system, an application required for at least one function (such as a sound playback function, an image playback function, etc.), etc.; the data storage area can store data created according to the use of the mobile phone (such as audio data, a phone book, etc.), etc. In addition, the memory 920 can include a high-speed random access memory, and can also include a non-volatile memory, such as at least one disk storage device, a flash memory device, or other volatile solid-state storage devices.

[0205] The input unit 930 can be used to receive input digital or character information, and to generate key signal input related to the user settings and function control of the mobile phone. Specifically, the input unit 930 may include a touch panel 931 and other input devices 932. The touch panel 931, also known as a touch screen, can collect the user's touch operation on or near it (such as the user's operation on the touch panel 931 or near the touch panel 931 using any suitable object or accessory such as a finger, stylus, etc.), and drive the corresponding connection device according to a pre-set program. Optionally, the touch panel 931 may include two parts: a touch detection device and a touch controller. Among them, the touch detection device detects the user's touch orientation, detects the signal brought by the touch operation, and transmits the signal to the touch controller; the touch controller receives the touch information from the touch detection device, converts it into contact coordinates, and then sends it to the processor 980, and can receive and execute commands sent by the processor 980. In addition, the touch panel 931 can be implemented in various types such as resistive, capacitive, infrared, and surface acoustic waves. In addition to the touch panel 931, the input unit 930 may further include other input devices 932. Specifically, the other input devices 932 may include but are not limited to one or more of a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, a mouse, a joystick, and the like.

[0206] The display unit 940 can be used to display information input by the user or information provided to the user and various menus of the mobile phone. The display unit 940 may include a display panel 941. Optionally, the display panel 941 may be configured in the form of a liquid crystal display (LCD), an organic light-emitting diode (OLED), etc. Further, the touch panel 931 may cover the display panel 941. When the touch panel 931 detects a touch operation on or near it, it is transmitted to the processor 980 to determine the type of touch event. Subsequently, the processor 980 provides a corresponding visual output on the display panel 941 according to the type of touch event. Although in Fig. 9 In the embodiment, the touch panel 931 and the display panel 941 are used as two independent components to realize the input and output functions of the mobile phone, but in some embodiments, the touch panel 931 and the display panel 941 can be integrated to realize the input and output functions of the mobile phone.

[0207] The mobile phone may also include at least one sensor 950, such as a light sensor, a motion sensor, and other sensors. Specifically, the light sensor may include an ambient light sensor and a proximity sensor, wherein the ambient light sensor may adjust the brightness of the display panel 941 according to the brightness of the ambient light, and the proximity sensor may turn off the display panel 941 and / or the backlight when the mobile phone is moved to the ear. As a type of motion sensor, the accelerometer sensor can detect the magnitude of acceleration in all directions (generally three axes), and can detect the magnitude and direction of gravity when stationary. It can be used for applications that identify the posture of the mobile phone (such as horizontal and vertical screen switching, related games, magnetometer posture calibration), vibration recognition related functions (such as pedometer, tapping), etc.; as for other sensors that can be configured in the mobile phone, such as gyroscopes, barometers, hygrometers, thermometers, infrared sensors, etc., they will not be repeated here.

[0208] The audio circuit 960, the speaker 961, and the microphone 962 can provide an audio interface between the user and the mobile phone. The audio circuit 960 can transmit the received audio data to the speaker 961 after converting the received audio data into an electrical signal, which is converted into a sound signal for output; on the other hand, the microphone 962 converts the collected sound signal into an electrical signal, which is received by the audio circuit 960 and converted into audio data, and then the audio data is output to the processor 980 for processing, and then sent to another mobile phone through the RF circuit 910, or the audio data is output to the memory 920 for further processing.

[0209] WiFi is a short-range wireless transmission technology. The mobile phone can help users send and receive emails, browse web pages and access streaming media through the WiFi module 970. It provides users with wireless broadband Internet access. Fig. 9A WiFi module 970 is shown, but it is understandable that it is not an essential component of the mobile phone and can be omitted as needed without changing the essence of the invention.

[0210] The processor 980 is the control center of the mobile phone. It uses various interfaces and lines to connect various parts of the entire mobile phone. By running or executing software programs and / or modules stored in the memory 920, and calling data stored in the memory 920, it executes various functions of the mobile phone and processes data, thereby monitoring the mobile phone as a whole. Optionally, the processor 980 may include one or more processing units; preferably, the processor 980 may integrate an application processor and a modem processor, wherein the application processor mainly processes the operating system, user interface, and application programs, and the modem processor mainly processes wireless communications. It is understandable that the above-mentioned modem processor may not be integrated into the processor 980.

[0211] The mobile phone also includes a power supply 990 (such as a battery) for supplying power to various components. Preferably, the power supply can be logically connected to the processor 980 through a power management system, so that the power management system can manage charging, discharging, power consumption and other functions.

[0212] Although not shown, the mobile phone may also include a camera, a Bluetooth module, etc., which will not be described in detail here.

[0213] In the embodiment of the present application, the processor 980 included in the terminal also has a function of controlling the execution of the method flow for establishing information sharing between plug-ins executed by the terminal.

[0214] It should also be noted that the device embodiments described above are merely schematic, wherein the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the scheme of this embodiment. In addition, in the device embodiment drawings provided in the embodiments of the present application, the connection relationship between the modules indicates that there is a communication connection between them, which may be specifically implemented as one or more communication buses or signal lines. A person of ordinary skill in the art can understand and implement it without paying creative labor.

[0215] Through the description of the above implementation mode, the technicians in the field can clearly understand that the embodiment of the present application can be implemented by means of software plus necessary general hardware, and of course, it can also be implemented by special hardware including special integrated circuits, special CPUs, special memories, special components, etc. In general, all functions completed by computer programs can be easily implemented with corresponding hardware, and the specific hardware structure used to implement the same function can also be various, such as analog circuits, digital circuits or special circuits. However, for the embodiment of the present application, software program implementation is a better implementation mode in more cases. Based on such an understanding, the technical solution of the embodiment of the present application is essentially or the part that contributes to the prior art can be embodied in the form of a software product, which is stored in a readable storage medium, such as a computer floppy disk, a U disk, a mobile hard disk, a read-only memory (ROM, Read-Only Memory), a random access memory (RAM, Random Access Memory), a disk or an optical disk, etc., including a number of instructions to enable a computer device (which can be a personal computer, a server, or a network device, etc.) to execute the method described in each embodiment of the embodiment of the present application.

[0216] To sum up, the above embodiments are only used to illustrate the technical solutions of the embodiments of the present application, rather than to limit them. Although the embodiments of the present application are described in detail with reference to the above embodiments, those skilled in the art should understand that they can still modify the technical solutions recorded in the above embodiments, or replace some of the technical features therein by equivalents. However, these modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present application.

Claims

1. A method for establishing information sharing between plug-ins, characterized in that: The method is applied to a terminal, wherein a first plug-in, an application program, and a second plug-in are configured in an operating system of the terminal, wherein the first plug-in and the second plug-in are different, and the first plug-in and the second plug-in are communicatively connected with the application program, wherein the method comprises: Loading the first plug-in on the display interface of the terminal; The first plug-in is called to receive first information input by the operation object on the display interface, and detect a completion instruction input by the operation object on the display interface, and when the completion instruction is detected, the following steps are triggered: encapsulating the first information into a link address, and then calling an open link address interface of the application to send the link address to the application, wherein the open link address interface is used to trigger the application to run on the display interface of the terminal; Running the application to write the first information into an application group file and triggering the second plug-in to perform a first update operation; the first update operation refers to the second plug-in acquiring the first information from the application group file under the triggering of the application; The second plug-in is called to read the first information from the local information base of the application group file, and then the first information is updated to the system information base of the terminal.

2. The method according to claim 1, characterized in that: The calling of the application program's open link address interface includes: Get the view control class of the first plug-in; Traversing the event response chain of the view control class to determine the terminal operation object interface response class of the first plug-in; Acquire the operation object interface application object associated with the terminal operation object interface response class; The application object calls the application program to run according to the operation object interface.

3. The method according to claim 1, characterized in that After calling the first plug-in to obtain the first information input by the operation object, the method further includes: Invoking the first plug-in to send the first information to an application server; Running the application to receive second information sent by the application server according to the first information, then writing the second information into the application group file, and triggering the second plug-in to perform a second update operation; The second plug-in is called to obtain the second information from the application group file, and the control function of the second plug-in is executed according to the second information.

4. A method for managing incoming call number tags based on logs, characterized in that: The method is applied to a call management terminal installed with a call report plug-in and a call mark management plug-in, for marking and managing the incoming call number on the mobile terminal, the mobile terminal is installed with the call management terminal, and the call management terminal is used to implement the method according to any one of claims 1 to 3; wherein the method comprises: Receiving a first trigger operation of an operation object for a communication number in a recent log page of the mobile terminal; In response to the first trigger operation, activating and displaying a call report management control; Receiving a second trigger operation for the incoming call report management control, and displaying an incoming call mark management page on the recent log page; wherein the incoming call mark management page displays at least one mark management label and at least one mark management control; Receiving a third trigger operation of the operation object on the tag management label and / or the tag management control of the incoming call tag management page; In response to the third trigger operation, a prompt message indicating successful marking of the communication number is displayed on the incoming call marking management page.

5. The method according to claim 4, characterized in that The step of activating and displaying a call report management control in response to the first trigger operation includes: The incoming call report plug-in is called, and when the first trigger operation is detected, the incoming call report management control is activated and displayed.

6. The method according to claim 4, characterized in that In response to the third trigger operation, after displaying a prompt message indicating that the communication number has been successfully marked on the incoming call mark management page, the method further includes: The incoming call mark management plug-in is called to open the incoming call management terminal on the recent log page, so that the incoming call management terminal writes the mark management information for the communication number.

7. The method according to any one of claims 5 to 6, characterized in that In response to the third trigger operation, after displaying a prompt message indicating that the communication number has been successfully marked on the incoming call mark management page, the method further includes: When receiving a second incoming call message for the communication number, the communication number is displayed as a nuisance phone number on the incoming call mark management page, and the incoming calls to the communication number are blocked.

8. A terminal, characterized in that: The operating system of the terminal is configured with a first plug-in, an application, and a second plug-in, the first plug-in and the second plug-in are different, the first plug-in and the second plug-in are communicatively connected with the application, wherein the terminal includes: a first plug-in operation module, configured to call the first plug-in to obtain first information input by an operation object, and trigger the application to open, so as to send the first information to the application; an application operation module, configured to run the application to write the first information into an application group file and trigger the second plug-in to perform a first update operation; the first update operation refers to the second plug-in obtaining the first information from the application group file under the triggering of the application; A second plug-in operation module, used for calling the second plug-in to read the first information from the local information base of the application group file, and then update the first information to the system information base of the terminal; The first plug-in operation module includes: A first plug-in loading unit, configured to load the first plug-in on a display interface of the terminal; An information receiving unit, configured to call the first plug-in to receive first information input by the operation object on the display interface; an instruction detection unit, configured to call the first plug-in to detect a completion instruction input by the operation object on the display interface, and trigger the following steps when the completion instruction is detected: triggering the application to open so as to send the first information to the application; The first plug-in operation module includes: An information encapsulation unit, used for encapsulating the first information into a link address; The interface calling unit is used to call the open link address interface of the application to send the link address to the application, and the open link address interface is used to trigger the application to run on the display interface of the terminal.

9. The terminal according to claim 8, characterized in that: The interface calling unit is specifically used to obtain the view control class of the first plug-in; traverse the event response chain of the view control class to determine the terminal user interface response class of the first plug-in; obtain the user interface application object associated with the terminal user interface response class; and call the application to run according to the user interface application object.

10. The terminal according to claim 8, characterized in that: The first plug-in operation module is further used to call the first plug-in to obtain the first information input by the user, and then send the first information to the application server; The application operation module is further used to receive second information sent by the application server according to the first information; The application operation module is further used to write the second information into the application group file and trigger the second plug-in to perform a second update operation; The second plug-in operation module is further used to call the second plug-in to obtain the second information from the application group file and execute the control function of the second plug-in according to the second information.

11. A call management client, characterized in that: The call management client is installed with a call report plug-in and a call mark management plug-in for marking and managing the caller number on the mobile terminal. The call management client is installed on the mobile terminal, and the call management terminal is used to implement the method according to any one of claims 4 to 7; wherein the call management client includes: A receiving module, configured to receive a first trigger operation of a user on a communication number in a recent call record page of the mobile terminal; A processing module, configured to activate and display a call report management control in response to the first trigger operation; The receiving module is further configured to receive a second trigger operation for the incoming call report management control, A sending module, configured to display an incoming call mark management page on the recent call record page; wherein the incoming call mark management page displays at least one mark management label and at least one mark management control; The receiving module is further used to receive a third trigger operation of the user on the tag management label and / or the tag management control of the incoming call tag management page; The sending module is further configured to display a successful marking prompt message for the communication number on the incoming call marking management page in response to the third trigger operation.

12. The call management client according to claim 11, characterized in that: The processing module is used to call the incoming call report plug-in, and when the first trigger operation is detected, activate and display the incoming call report management control.

13. The call management client according to claim 11, characterized in that: The processing module is used to respond to the third trigger operation, after displaying a prompt message that the marking is successful for the communication number on the caller marking management page, call the caller marking management plug-in to open the caller management client on the recent call record page, so that the caller management client writes the marking management information for the communication number.

14. The call management client according to any one of claims 12 to 13, characterized in that: The processing module is used to display the communication number as a harassing phone number on the call mark management page when receiving the second call information for the communication number, and intercept the call to the communication number.

15. A computer-readable storage medium comprising instructions, which, when executed on a computer, causes the computer to execute the method according to any one of claims 1 to 3, or 4 to 7.

16. A terminal, characterized in that: The terminal includes: a processor and a memory; The memory is used to store instructions; The processor is used to execute the instructions in the memory to perform the method according to any one of claims 1 to 3, or 4 to 7.

Images