CN106959878B

CN106959878B - Widget management method and mobile terminal

Info

Publication number: CN106959878B
Application number: CN201710210190.3A
Authority: CN
Inventors: 周龙
Original assignee: Nubia Technology Co Ltd
Current assignee: Nubia Technology Co Ltd
Priority date: 2017-03-31
Filing date: 2017-03-31
Publication date: 2020-03-31
Anticipated expiration: 2037-03-31
Also published as: CN106959878A

Abstract

The invention discloses a mobile terminal, a widget is installed in the mobile terminal, and the mobile terminal comprises: the acquisition module is used for acquiring the type of the installed widget when a mobile terminal user installs the widget on the mobile terminal; the judging module is used for displaying the widgets and judging whether the widgets are tool widgets or not; the query module is used for querying a background application program corresponding to the tool type widget when the widget is the tool type widget; and the processing module is used for disconnecting the data connection of the background application program. The method and the device can timely limit the tool widgets to automatically wake up the corresponding background application program, and avoid the tool widgets wasting too much electric quantity of the mobile terminal and influencing the endurance of the mobile terminal.

Description

Widget management method and mobile terminal

Technical Field

The invention relates to the technical field of mobile terminals, in particular to a widget management method and a mobile terminal.

Background

The widget (widget) is a very small application program, which may be a component of an image, a text, etc., and can operate as a local application program, so that the application program may not be limited by the size of the interface of the mobile terminal, and content such as video, map, real-time news, weather forecast, stocks, music players, etc., can be displayed on the webpage, desktop page, or other man-machine interaction interface of the mobile terminal in a personalized manner, thereby providing convenience for the mobile terminal user to use various application programs and network services.

However, with the popularization and development of widgets, widgets are being used in more and more mainstream applications. Often, a mobile terminal user sets a large number of widgets in the mobile terminal for aesthetic or personalized needs. How to effectively manage numerous widgets in the mobile terminal, avoid the widgets occupying the hardware resources of the mobile terminal, consuming the electric quantity of the mobile terminal and influencing the endurance thereof, and become a problem to be solved urgently.

Disclosure of Invention

In view of this, the present invention provides a widget management method and a mobile terminal, and aims to perform corresponding control on different types of widgets according to types of widgets, so as to prevent a part of widgets from automatically waking up corresponding application programs, which wastes electric quantity of the mobile terminal and affects endurance of the mobile terminal.

First, to achieve the above object, the present invention provides a mobile terminal, in which a widget is installed, the mobile terminal including:

the acquisition module is used for acquiring the type of the installed widget when a mobile terminal user installs the widget on the mobile terminal;

the judging module is used for displaying the widgets and judging whether the widgets are tool widgets or not;

the query module is used for querying a background application program corresponding to the tool type widget when the widget is the tool type widget; and

and the processing module is used for disconnecting the data connection of the background application program corresponding to the tool widget.

Optionally, the mobile terminal further includes a prompt module, and the prompt module is configured to:

and when the mobile terminal installs the widget, prompting a mobile terminal user to set the type of the widget, wherein the type comprises a tool class.

Optionally, the obtaining module is further configured to:

acquiring the widget name or an application program name corresponding to the widget; and

and inquiring the type of the widget from a preset widget classification table according to the widget name or the application program name, wherein the type comprises a tool class.

Optionally, the obtaining module is further configured to:

inquiring the attribute of the widget to obtain a default update frequency value of the widget; and

comparing the default update frequency value with a preset update frequency value to determine a type of the widget, the type including a tool class.

Optionally, the processing module is further configured to:

and adding an instruction for prohibiting the widget from automatically waking up the corresponding background application program in the power-saving strategy of the mobile terminal.

Compared with the prior art, the mobile terminal provided by the invention limits the tool widgets by acquiring the types of the widgets installed in the mobile terminal, so that the tool widgets are only displayed in the mobile terminal, and the corresponding background application program is not automatically awakened any more. Therefore, the personalized requirements of the mobile terminal user are met, and the situation that the tool type widget automatically wakes up the background application program, the electric quantity of the mobile terminal is wasted, and the endurance of the mobile terminal is influenced is prevented.

In addition, to achieve the above object, the present invention further provides a widget management method, where a widget is installed in a mobile terminal, the method including:

when a mobile terminal user installs a widget on the mobile terminal, acquiring the type of the installed widget;

displaying the widget and judging whether the widget is a tool widget or not;

if the widget is a tool widget, querying a background application program corresponding to the tool widget; and

and disconnecting the data connection of the background application program corresponding to the tool type widget.

Optionally, before the step of obtaining the type of the installed widget when the mobile terminal user installs the widget on the mobile terminal, the method further includes:

Optionally, the step of obtaining the type of the widget installed in the mobile terminal specifically includes:

Optionally, the step of disconnecting the data connection of the background application corresponding to the tool widget specifically includes:

Compared with the prior art, the widget management method provided by the invention has the advantages that the tool widgets are limited by acquiring the types of the widgets installed in the mobile terminal, so that the tool widgets are only displayed in the mobile terminal, and the corresponding background application program is not automatically awakened any more. Therefore, the personalized requirements of the mobile terminal user are met, and the situation that the tool type widget automatically wakes up the background application program, the electric quantity of the mobile terminal is wasted, and the endurance of the mobile terminal is influenced is prevented.

Drawings

Fig. 1 is a schematic diagram of a hardware structure of an optional mobile terminal for implementing various embodiments of the present invention;

FIG. 2 is a diagram of a wireless communication system for the mobile terminal shown in FIG. 1;

fig. 3 is a block diagram of a mobile terminal according to a first embodiment of the present invention;

FIG. 4 is a diagram of a widget classification table;

FIG. 5 is a block diagram of a mobile terminal according to a second embodiment of the present invention;

FIG. 6 is a flowchart illustrating a first embodiment of a widget management method according to the present invention;

FIG. 7 is a flowchart illustrating a second embodiment of a widget management method according to the present invention;

fig. 8 is a flowchart illustrating a third embodiment of a widget management method according to the present invention.

Reference numerals:

the objects, features and advantages of the present invention will be further explained with reference to the accompanying drawings

Detailed Description

It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.

A mobile terminal 400 implementing various embodiments of the present invention will now be described with reference to the accompanying drawings. In the following description, suffixes such as "module", "component", or "unit" used to denote elements are used only for facilitating the explanation of the present invention, and have no specific meaning in themselves. Thus, "module" and "component" may be used in a mixture.

The mobile terminal 400 may be implemented in various forms. For example, the terminal described in the present invention may include a mobile terminal such as a mobile phone, a smart phone, a notebook computer, a digital broadcast receiver, a PDA (personal digital assistant), a PAD (tablet computer), a PMP (portable multimedia player), a navigation device, and the like, and a stationary terminal such as a digital TV, a desktop computer, and the like. In the following, it is assumed that the terminal is a mobile terminal 400. However, it will be understood by those skilled in the art that the configuration according to the embodiment of the present invention can be applied to a fixed type terminal in addition to elements particularly used for moving purposes.

Fig. 1 is a schematic hardware configuration diagram of an optional mobile terminal 400 for implementing various embodiments of the present invention.

The mobile terminal 400 may include, but is not limited to, a memory 20, a controller 30, a wireless communication unit 40, a display unit 50, an input unit 60, an interface unit 80, and a power supply unit 90. Fig. 1 illustrates a mobile terminal 400 having various components, but it is to be understood that not all illustrated components are required to be implemented. More or fewer components may alternatively be implemented. The elements of the mobile terminal 400 will be described in detail below.

The wireless communication unit 40 typically includes one or more components that allow wireless point communication between the mobile terminal 400 and a wireless communication system or network. For example, the wireless communication unit may include at least one of a broadcast receiving module, a mobile communication module, a wireless internet module, a short-range communication module, and a location information module.

The broadcast receiving module receives a broadcast signal and/or broadcast associated information from an external broadcast management server via a broadcast channel. The broadcast channel may include a satellite channel and/or a terrestrial channel. The broadcast management server may be a server that generates and transmits a broadcast signal and/or broadcast associated information or a server that receives a previously generated broadcast signal and/or broadcast associated information and transmits it to a terminal. The broadcast signal may include a TV broadcast signal, a radio broadcast signal, a data broadcast signal, and the like. Also, the broadcast signal may further include a broadcast signal combined with a TV or radio broadcast signal. The broadcast associated information may also be provided via a mobile communication network, and in this case, the broadcast associated information may be received by the mobile communication module. The broadcast signal may exist in various forms, for example, it may exist in the form of an Electronic Program Guide (EPG) of Digital Multimedia Broadcasting (DMB), an Electronic Service Guide (ESG) of digital video broadcasting-handheld (DVB-H), and the like. The broadcast receiving module may receive a signal broadcast by using various types of broadcasting systems. In particular, the broadcast receiving module may receive digital broadcasting by using a digital broadcasting system such as a data broadcasting system of multimedia broadcasting-terrestrial (DMB-T), digital multimedia broadcasting-satellite (DMB-S), digital video broadcasting-handheld (DVB-H), forward link media (MediaFLO @), terrestrial digital broadcasting integrated service (ISDB-T), and the like. The broadcast receiving module may be constructed to be suitable for various broadcasting systems providing broadcast signals as well as the above-mentioned digital broadcasting system. The broadcast signal and/or broadcast associated information received via the broadcast receiving module may be stored in the memory 20 (or other type of storage medium).

The mobile communication module transmits and/or receives radio signals to and/or from at least one of a base station (e.g., access point, node B, etc.), an external terminal, and a server. Such radio signals may include voice call signals, video call signals, or various types of data transmitted and/or received according to text and/or multimedia messages.

The wireless internet module supports wireless internet access of the mobile terminal 400. The module may be internally or externally coupled to the terminal. The wireless internet access technology to which the module relates may include WLAN (wireless LAN) (Wi-Fi), Wibro (wireless broadband), Wimax (worldwide interoperability for microwave access), HSDPA (high speed downlink packet access), and the like.

The short-range communication module is a module for supporting short-range communication. Some examples of short-range communication technologies include bluetooth (TM), Radio Frequency Identification (RFID), infrared data association (IrDA), Ultra Wideband (UWB), zigbee (TM), and the like.

The location information module is a module for checking or acquiring location information of the mobile terminal 400. A typical example of the location information module is a GPS (global positioning system). According to the current technology, the GPS module calculates distance information and accurate time information from three or more satellites and applies triangulation to the calculated information, thereby accurately calculating three-dimensional current location information according to longitude, latitude, and altitude. Currently, a method for calculating position and time information uses three satellites and corrects an error of the calculated position and time information by using another satellite. In addition, the GPS module can calculate speed information by continuously calculating current position information in real time.

The output unit 50 is configured to provide output signals (e.g., audio signals, video signals, alarm signals, vibration signals, etc.) in a visual, audio, and/or tactile manner. The output unit 50 may include a display unit 51, an audio output module 52, an alarm unit 53, and the like.

The display unit 51 may display information processed in the mobile terminal 400. For example, when the mobile terminal 400 is in a phone call mode, the display unit 51 may display a User Interface (UI) or a Graphical User Interface (GUI) related to a call or other communication (e.g., text messaging, multimedia file downloading, etc.). When the mobile terminal 400 is in a video call mode or an image capturing mode, the display unit 51 may display a captured image and/or a received image, a UI or GUI showing a video or an image and related functions, and the like.

Meanwhile, when the display unit 51 and the touch panel are superimposed on each other in the form of layers to form a touch screen, the display unit 51 may function as an input device and an output device. The display unit 51 may include at least one of a Liquid Crystal Display (LCD), a thin film transistor LCD (TFT-LCD), an Organic Light Emitting Diode (OLED) display, a flexible display, a three-dimensional (3D) display, and the like. Some of these displays may be configured to be transparent to allow a user to view from the outside, which may be referred to as transparent displays, and a typical transparent display may be, for example, a TOLED (transparent organic light emitting diode) display or the like. The mobile terminal 400 may include two or more display units (or other display devices) according to certain desired embodiments, for example, the mobile terminal 400 may include an external display unit (not shown) and an internal display unit (not shown). The touch screen may be used to detect a touch input pressure as well as a touch input position and a touch input area.

The audio output module 52 may convert audio data received by the wireless communication unit 40 or stored in the memory 20 into an audio signal and output as sound when the mobile terminal 400 is in a call signal reception mode, a call mode, a recording mode, a voice recognition mode, a broadcast reception mode, or the like. Also, the audio output module 52 may provide audio output related to a specific function performed by the mobile terminal 400 (e.g., a call signal reception sound, a message reception sound, etc.). The audio output module 52 may include a speaker, a buzzer, and the like.

The alarm unit 53 may provide an output to notify the mobile terminal 400 of the occurrence of the event. Typical events may include call reception, message reception, key signal input, touch input, and the like. In addition to audio or visual output, the alarm unit 53 may provide output in different ways to notify the occurrence of an event. For example, the alarm unit 53 may provide an output in the form of vibration, and when a call, a message, or some other incoming communication (communicating communication) is received, the alarm unit 53 may provide a tactile output (i.e., vibration) to notify the user thereof. By providing such a tactile output, the user can recognize the occurrence of various events even when the user's mobile phone is in the user's pocket. The alarm unit 53 may also provide an output notifying the occurrence of an event via the display unit 51 or the audio output module 52.

The input unit 60 may generate key input data to control various operations of the mobile terminal 400 according to a command input by a user. The input unit 60 allows a user to input various types of information, and may include a keyboard, dome sheet, touch pad (e.g., a touch-sensitive member that detects changes in resistance, pressure, capacitance, and the like due to being touched), scroll wheel, joystick, and the like. In particular, when the touch pad is superimposed on the display unit 50 in the form of a layer, a touch screen may be formed.

The interface unit 80 serves as an interface through which at least one external device is connected to the mobile terminal 400. For example, the external device may include a wired or wireless headset port, an external power supply (or battery charger) port, a wired or wireless data port, a memory card port, a port for connecting a device having an identification module, an audio input/output (I/O) port, a video I/O port, an earphone port, and the like. The identification module may store various information for authenticating a user using the mobile terminal 400 and may include a User Identity Module (UIM), a Subscriber Identity Module (SIM), a Universal Subscriber Identity Module (USIM), and the like. In addition, a device having an identification module (hereinafter, referred to as an "identification device") may take the form of a smart card, and thus, the identification device may be connected with the mobile terminal 400 via a port or other connection means. The interface unit 80 may be used to receive input (e.g., data information, power, etc.) from external devices and transmit the received input to one or more elements within the mobile terminal 400 or may be used to transmit data between the mobile terminal 400 and external devices.

In addition, when the mobile terminal 400 is connected with an external cradle, the interface unit 80 may serve as a path through which power is supplied from the cradle to the mobile terminal 400 or may serve as a path through which various command signals input from the cradle are transmitted to the mobile terminal 400. Various command signals or power input from the cradle may be used as signals for recognizing whether the mobile terminal 400 is accurately mounted on the cradle.

The memory 20 may store software programs or the like for processing and controlling operations performed by the controller 30, or may temporarily store data (e.g., a phonebook, messages, still images, videos, and the like) that has been or is to be output. Also, the memory 20 may store data regarding various ways of vibration and audio signals output when a touch is applied to the touch screen.

The memory 20 may include at least one type of storage medium including a flash memory, a hard disk, a multimedia card, a card type memory (e.g., SD or DX memory, etc.), a Random Access Memory (RAM), a Static Random Access Memory (SRAM), a Read Only Memory (ROM), an Electrically Erasable Programmable Read Only Memory (EEPROM), a Programmable Read Only Memory (PROM), a magnetic memory, a magnetic disk, an optical disk, etc. Also, the mobile terminal 400 may cooperate with a network storage device that performs a storage function of the memory 20 through a network connection.

The controller 30 generally controls the overall operation of the mobile terminal. For example, the controller 30 performs control and processing related to voice calls, data communications, video calls, and the like. In addition, the controller 30 may include a multimedia module for reproducing (or playing back) multimedia data, and the multimedia module may be constructed within the controller 30 or may be constructed separately from the controller 30. The controller 30 may perform a pattern recognition process to recognize a handwriting input or a picture drawing input performed on the touch screen as a character or an image.

The power supply unit 90 receives external power or internal power and provides appropriate power required to operate the respective elements and components under the control of the controller 30.

The various embodiments described herein may be implemented in a computer-readable medium using, for example, computer software, hardware, or any combination thereof. For a hardware implementation, the embodiments described herein may be implemented using at least one of an Application Specific Integrated Circuit (ASIC), a Digital Signal Processor (DSP), a Digital Signal Processing Device (DSPD), a Programmable Logic Device (PLD), a Field Programmable Gate Array (FPGA), a processor, a controller, a microcontroller, a microprocessor, an electronic unit designed to perform the functions described herein, and in some cases, such embodiments may be implemented in the controller 30. For a software implementation, the implementation such as a process or a function may be implemented with a separate software module that allows performing at least one function or operation. The software codes may be implemented by software applications (or programs) written in any suitable programming language, which may be stored in memory 20 and executed by controller 30.

So far, the mobile terminal 400 has been described in terms of its functions. Hereinafter, the slide-type mobile terminal 400 among various types of mobile terminals 400, such as the folder-type, bar-type, swing-type, slide-type mobile terminal 400, and the like, will be described as an example for the sake of brevity. Accordingly, the present invention can be applied to any type of mobile terminal 400, and is not limited to the slide type mobile terminal 400.

The mobile terminal 400 as shown in fig. 1 may be configured to operate with communication systems such as wired and wireless communication systems and satellite-based communication systems that transmit data via frames or packets.

A communication system in which a mobile terminal 400 according to the present invention is capable of operating will now be described with reference to fig. 2.

Such communication systems may use different air interfaces and/or physical layers. For example, the air interface used by the communication system includes, for example, Frequency Division Multiple Access (FDMA), Time Division Multiple Access (TDMA), Code Division Multiple Access (CDMA), and Universal Mobile Telecommunications System (UMTS) (in particular, Long Term Evolution (LTE)), global system for mobile communications (GSM), and the like. By way of non-limiting example, the following description relates to a CDMA communication system, but such teachings are equally applicable to other types of systems.

Referring to fig. 2, a CDMA wireless communication system may include a plurality of mobile terminals 400, a plurality of Base Stations (BSs) 270, Base Station Controllers (BSCs) 275, and a Mobile Switching Center (MSC) 280. The MSC280 is configured to interface with a Public Switched Telephone Network (PSTN) 290. The MSC280 is also configured to interface with a BSC275, which may be coupled to the base station 270 via a backhaul. The backhaul may be constructed according to any of several known interfaces including, for example, E1/T1, ATM, IP, PPP, frame Relay, HDSL, ADSL, or xDSL. It will be understood that a system as shown in fig. 2 may include multiple BSCs 2750.

Each BS270 may serve one or more sectors (or regions), each sector covered by a multi-directional antenna or an antenna pointing in a particular direction being radially distant from the BS 270. Alternatively, each partition may be covered by two or more antennas for diversity reception. Each BS270 may be configured to support multiple frequency allocations, with each frequency allocation having a particular frequency spectrum (e.g., 1.25MHz,5MHz, etc.).

The intersection of partitions with frequency allocations may be referred to as a CDMA channel. The BS270 may also be referred to as a Base Transceiver Subsystem (BTS) or other equivalent terminology. In such a case, the term "base station" may be used to generically refer to a single BSC275 and at least one BS 270. The base stations may also be referred to as "cells". Alternatively, each sector of a particular BS270 may be referred to as a plurality of cell sites.

As shown in fig. 2, a Broadcast Transmitter (BT)295 transmits a broadcast signal to a mobile terminal 400 operating within the system. The broadcast receiving module 111 as shown in fig. 1 is provided at the mobile terminal 400 to receive a broadcast signal transmitted by the BT 295. In fig. 2, several Global Positioning System (GPS) satellites 300 are shown. The satellite 300 assists in locating at least one of the plurality of mobile terminals 400.

In fig. 2, a plurality of satellites 300 are depicted, but it is understood that useful positioning information may be obtained with any number of satellites. The GPS module 115 as shown in fig. 1 is generally configured to cooperate with satellites 300 to obtain desired positioning information. Other techniques that can track the location of the mobile terminal 400 may be used instead of or in addition to GPS tracking techniques. In addition, at least one GPS satellite 300 may selectively or additionally process satellite DMB transmission.

As a typical operation of a wireless communication system, the BS270 receives reverse link signals from various mobile terminals 400. The mobile terminal 400 is typically engaged in conversations, messaging, and other types of communications. Each reverse link signal received by a particular base station 270 is processed within the particular BS 270. The obtained data is forwarded to the associated BSC 275. The BSC provides call resource allocation and mobility management functions including coordination of soft handoff procedures between BSs 270. The BSCs 275 also route the received data to the MSC280, which provides additional routing services for interfacing with the PSTN 290. Similarly, the PSTN290 interfaces with the MSC280, the MSC interfaces with the BSCs 275, and the BSCs 275 accordingly control the BS270 to transmit forward link signals to the mobile terminal 400.

Based on the hardware structure of the mobile terminal 400 and the communication system, various embodiments of the present invention are proposed.

First, the present invention provides a mobile terminal 400.

Fig. 3 is a block diagram of a mobile terminal 400 according to a first embodiment of the present invention. In this embodiment, the mobile terminal 400 may be divided into one or more modules, and the one or more modules are stored in the memory 20 and executed by one or more controllers (the controller 30 in this embodiment) to complete the present invention. For example, in fig. 3, the mobile terminal 400 includes an obtaining module 401, a determining module 402, an inquiring module 403, and a processing module 404. The module referred to in the present invention refers to a series of computer program instruction segments capable of performing specific functions, which are more suitable than programs for describing the execution process of software in the mobile terminal 400. The detailed description of the functions of the functional modules 401 and 404 will be described below. Wherein:

the obtaining module 401 is configured to obtain a type of an installed widget when a mobile terminal user installs the widget on the mobile terminal.

Generally, widgets are applied to more and more applications as they are popularized and applied. For example, common application programs that support widget functionality include, but are not limited to, weather forecast applications, real-time news applications, music player applications, video applications, picture applications, notes applications, sports applications, calendar applications, clock applications, and the like. The mobile terminal user may add widgets of the above-mentioned application on the display interface (e.g., desktop page) of the mobile terminal 400 to meet the personalized needs thereof. It should be noted that, in this embodiment, when a mobile terminal user adds a widget of the application program on a display interface (e.g., a desktop page) of the mobile terminal 400, the obtaining module 401 obtains a type of the widget added by the mobile terminal user.

Further, according to the functional features of different applications, the widgets of the different applications can be generally classified into two categories: tool-like widgets and non-tool-like widgets. The tool-based widgets include, but are not limited to, clock-based widgets (e.g., desktop clocks), measurement-based widgets (e.g., rulers), wallpaper-based widgets, picture-based widgets, calendar-based widgets, and the like. Such widgets generally have the following functional characteristics: the widget is added only for providing an aesthetic effect for the display interface of the mobile terminal 400, or is added only for providing convenience for the user of the mobile terminal (the corresponding application program can be opened by clicking the widget), and the function or information provided by the widget itself is relatively fixed, and the application server or the network service does not need to be connected in real time for updating the information (for example, the measurement tool is not changed generally). In addition, the non-tool widgets include, but are not limited to, weather forecast widgets, real-time news widgets, music player widgets, video widgets, sports widgets, and the like. Such widgets generally have the following functional characteristics: the widget provides multiple functions, the information provided by the widget changes frequently, and the application server or the network service needs to be connected in real time to update the information (for example, the weather forecast type widget needs to update the temperature and humidity values displayed in the widget interface in real time along with the change of the temperature and humidity).

In this embodiment, a widget classification table may be preset in the mobile terminal 400, and the widget classification table counts and stores basic information of all common widgets. The basic information of the widget may include, but is not limited to, a widget name, an application name corresponding to the widget, a widget type, and the like. According to the widget classification table, the obtaining module 401 may first obtain a name of a widget installed in the mobile terminal 400 or a name of an application program corresponding to the widget, and then query a type of the widget from the widget classification table according to the obtained name of the widget or the name of the application program, so as to determine whether the widget installed in the mobile terminal 400 is a tool widget or a non-tool widget. For example, as shown in fig. 4, when the obtaining module 401 obtains the widget name of the widget, which is "ink weather", the obtaining module 401 may find that the application program corresponding to the widget name "ink weather" is an application "ink weather" by querying the widget classification table shown in fig. 4, and the corresponding widget type is a non-tool type.

The determining module 402 is configured to display the widget and determine whether the widget installed on the mobile terminal 400 is a tool widget.

Generally, a mobile terminal user may choose to add one or more widgets on the interface of the mobile terminal 400 according to personalized requirements, and whether the widget selected to be added is a tool widget or a non-tool widget, the widget selected to be added by the mobile terminal user should be preferentially displayed according to the requirements of the mobile terminal user.

The query module 403 is configured to query a background application corresponding to the tool type widget when the widget is the tool type widget.

Generally, a widget refers to a part of program code of an application program installed on a user computer or a mobile device, and may be embedded in a display interface of the computer or the mobile device to update and display data such as text or pictures of a part of an original application program through the computer, the mobile device locally or through the internet, in order to assist a user in using various application programs and network services. In general, the normal operation of the widget needs to be supported by the application corresponding to the widget, that is, when the mobile terminal user adds the widget on the display interface of the mobile terminal 400, the widget wakes up the application corresponding to the widget and runs in the background of the mobile terminal 400, so as to support the update of the data displayed by the widget. Therefore, when the widget installed in the mobile terminal 400 is a tool widget, the query module 403 may query, according to the name of the installed widget, an application program corresponding to the widget, which runs in the background of the mobile terminal 400.

The processing module 404 is configured to disconnect the data connection of the background application corresponding to the tool type widget.

As can be seen from the foregoing, the tool widget generally only serves to provide an aesthetic effect for the display interface of the mobile terminal 400, or only to facilitate the use of the mobile terminal user, the function or information provided by the widget itself is relatively fixed, and often there is no need to connect to an application server or a network service in real time to update information. Therefore, the tool widget only needs to be displayed, and the application program corresponding to the tool widget does not need to be continuously run in the background of the mobile terminal 400 to be connected with the network or the application server in real time. Therefore, in this embodiment, when the widget is a tool widget, the processing module 404 directly disconnects the data connection of the background application corresponding to the tool widget.

It should be noted that, the disconnecting of the data connection of the background application corresponding to the tool widget in this embodiment means that the background application is kept silent in the background of the mobile terminal 400 and does not respond to the automatic wake-up of the tool widget by disconnecting the data connection between the background application and the application server or the web service, disconnecting the communication between the tool widget and the corresponding background application, and the like. For example, when the widget is a tool widget, the processing module 404 may add an instruction to prohibit the tool widget from automatically waking up a corresponding background application in the power saving policy of the mobile terminal 400.

It should be noted that the background application program only does not respond to the automatic wake-up of the corresponding widget any more, and if it is detected that the mobile terminal user wants to start the application program through a preset operation (for example, a touch operation of clicking an interface of the tool widget), the background application program should be woken up, and in response to the preset operation, the background application program enters the background running state again. Moreover, since the background application program is not killed directly in the embodiment, when the background application program is operated and started by a user, the speed is faster than that of directly starting the corresponding application program.

Through the function module 401 and 404, the mobile terminal 400 provided by the present invention determines the tool widget installed in the mobile terminal 400 by obtaining the type of the widget installed in the mobile terminal 400 by the user, and further limits the tool widget, so that the tool widget is only displayed on the display interface of the mobile terminal 400, and the background application corresponding to the tool widget no longer responds to the automatic wake-up of the tool widget, and keeps silent. Therefore, on the basis of meeting the personalized requirements of the mobile terminal user, the method prevents the background application program corresponding to the tool widget from continuously running and continuously responding to the automatic awakening of the tool widget, so that the waste of the electric quantity of the mobile terminal 400 is avoided, and the endurance of the mobile terminal 400 is influenced; and the problem that the starting speed is too slow when the application program is awakened again because the application program corresponding to the tool widget is killed directly is avoided.

Further, based on the above-described first embodiment of the mobile terminal 400 of the present invention, a second embodiment of the mobile terminal 400 of the present invention is proposed.

Fig. 5 is a block diagram of a mobile terminal 400 according to a second embodiment of the present invention. In this embodiment, the mobile terminal 400 further includes a prompt module 405, where:

the prompting module 405 is configured to prompt a mobile terminal user to set a type of the widget when the widget is installed in the mobile terminal 400, where the type includes a tool class.

From the foregoing, widgets can be generally classified into tool-type widgets and non-tool-type widgets according to their functional characteristics. Also, in the first embodiment, the type of the widget is obtained by first obtaining the name of the widget or the application name corresponding to the widget, and then querying from a preset widget classification table according to the obtained widget name or application name. In contrast, in this embodiment, a prompting module 405 is added, and when the prompting module 405 detects that the mobile terminal user adds a widget to the display interface of the mobile terminal 400, the prompting module prompts the mobile terminal user to select a type of the added widget. For example, the prompting module 405 may provide a pull-down menu, which includes two options, namely a tool type widget and a non-tool type widget, and when a mobile terminal user adds a widget, the prompting module 405 displays or pops up the pull-down menu and prompts the user to make a selection.

Further, in this embodiment, after the mobile terminal user selects the type of the widget, the prompt module 405 may further obtain the name of the widget, and further store the name of the widget and the type selected by the user in a data table, so as to automatically identify the type of the widget when the same widget is subsequently added to the display interface of the mobile terminal 400 again, thereby avoiding repeated operations of the mobile terminal user.

In addition, it should be added that the present embodiment is to add the prompting module 405, and select the type of the widget manually by the mobile terminal user in a prompting manner. In other embodiments, the widget type may also be determined by combining the widget classification table in the first embodiment with the hinting module 405 in this embodiment. Specifically, for example, when it is detected that a mobile terminal user adds a widget to the display interface of the mobile terminal 400, a name of the widget installed in the mobile terminal 400 or a name of an application corresponding to the widget is obtained first, and then the type of the widget is queried from a widget classification table according to the obtained name of the widget or the name of the application; if the widget name and the application name corresponding to the widget are not found in the widget classification table, the prompting module 405 prompts the mobile terminal user to manually select the type of the added widget.

Through the functional module 405, the mobile terminal 400 provided by the present invention prompts the mobile terminal user to select the type of the added widget by detecting that the mobile terminal user adds the widget to the display interface of the mobile terminal 400, so that the type of the widget can be manually selected when the mobile terminal user selects to add the widget. Meanwhile, the widget information of the type determined by the mobile terminal user is stored, and the type of the widget can be directly identified when the widget is added repeatedly next time, so that repeated operation of the user is avoided.

Further, based on the first and second embodiments of the mobile terminal 400 of the present invention, a third embodiment of the mobile terminal 400 of the present invention is proposed. Wherein:

the obtaining module 401 is further configured to query the attribute of the widget and obtain a default update frequency value of the widget.

Generally, when a developer develops a widget, default attributes of the widget are preset, including, but not limited to, update frequency, size, trigger condition, etc. of the widget. The update frequency of the widget refers to a frequency value at which the widget regularly obtains data information from an application program corresponding to the widget through a network service or an application server to update data information displayed on the widget. The update frequency value may be obtained by calling a function of the feature. For example, in the widget development work of the Android system, a developer may issue a widget through an appwidget provider, which is inherited from broadcastreever and can receive widget-related broadcasts, such as update, deletion, opening, and disabling of the widget. The AppWidget provider comprises a broadcast processing function onUpdate (), and the update frequency value of the widget preset by a developer can be obtained by calling the broadcast processing function onUpdate ().

The obtaining module 401 is further configured to compare the default update frequency value with a preset update frequency value to determine a type of the widget, where the type includes a tool class.

Generally, when the widget is a tool widget such as a clock widget, a measurement tool widget, a wallpaper widget, a picture widget, a calendar widget, etc., the developer sets the default update frequency value of the widget to a small value, for example, once a day or once every few days, etc. When the widget is a non-tool widget such as a weather forecast widget, a real-time news widget, a music player widget, a video widget, a sports widget, or the like, the developer sets the default update frequency value of the widget to a larger value, for example, once an hour or once every half hour. It can be seen that the default update frequency values set by the developer when developing tool-type widgets and non-tool-type widgets are very different. Therefore, in this embodiment, the obtaining module 401 may first obtain a default widget update frequency value preset by a widget developer, and then determine whether the widget is a tool widget or a non-tool widget according to the default widget update frequency value. For example, the obtaining module 401 may determine a widget with a default update frequency value higher than once every two hours (i.e., a preset update frequency value) as a non-tool widget, and determine a widget with a default update frequency value not higher than once every two hours as a tool widget.

Through the functional module 401, the mobile terminal 400 provided by the present invention obtains the default update frequency value preset by the developer for the widget, and compares the default update frequency value with the preset update frequency value, so as to determine whether the widget is a tool widget or a non-tool widget, thereby providing a new method for automatically determining the widget type and improving the accuracy of widget type determination.

In addition, the invention also provides a widget management method.

Fig. 6 is a schematic flow chart of the first embodiment of the widget management method according to the present invention. In this embodiment, the execution order of the steps in the flowchart shown in fig. 6 may be changed and some steps may be omitted according to different requirements. The widget management method comprises the following steps:

step S601, when the mobile terminal user installs the widget on the mobile terminal, the type of the installed widget is obtained.

Generally, widgets are applied to more and more applications as they are popularized and applied. For example, common application programs that support widget functionality include, but are not limited to, weather forecast applications, real-time news applications, music player applications, video applications, picture applications, notes applications, sports applications, calendar applications, clock applications, and the like. The mobile terminal user may add widgets of the above-mentioned application on the display interface (e.g., desktop page) of the mobile terminal 400 to meet the personalized needs thereof. It should be noted that, in this embodiment, when a mobile terminal user adds a widget of the application program on a display interface (e.g., a desktop page) of the mobile terminal 400, the type of the widget added by the mobile terminal user is obtained.

In this embodiment, a widget classification table may be preset in the mobile terminal 400, and the widget classification table counts and stores basic information of all common widgets. The basic information of the widget may include, but is not limited to, a widget name, an application name corresponding to the widget, a widget type, and the like. According to the widget classification table, a name of a widget installed in the mobile terminal 400 or a name of an application program corresponding to the widget may be first obtained, and then, according to the obtained name of the widget or the name of the application program, a type of the widget is queried from the widget classification table, so as to determine whether the widget installed in the mobile terminal 400 is a tool widget or a non-tool widget. For example, as shown in fig. 4, when the widget name of the widget is acquired as "ink weather", it can be known that the application program corresponding to the widget name "ink weather" is the "ink weather" application by querying the widget classification table shown in fig. 4, and the corresponding widget type is the non-tool type.

Step S602, displaying the widget, and determining whether the widget installed on the mobile terminal 400 is a tool widget.

Step S603, when the widget is a tool widget, querying a background application corresponding to the tool widget.

Generally, a widget refers to a part of program code of an application program installed on a user computer or a mobile device, and may be embedded in a display interface of the computer or the mobile device to update and display data such as text or pictures of a part of an original application program through the computer, the mobile device locally or through the internet, in order to assist a user in using various application programs and network services. In general, the normal operation of the widget needs to be supported by the application corresponding to the widget, that is, when the mobile terminal user adds the widget on the display interface of the mobile terminal 400, the widget wakes up the application corresponding to the widget and runs in the background of the mobile terminal 400, so as to support the update of the data displayed by the widget. Therefore, when the widget installed in the mobile terminal 400 is a tool widget, the application program corresponding to the widget running in the background of the mobile terminal 400 may be queried according to the name of the installed widget.

Step S604, disconnecting the data connection of the background application program corresponding to the tool type widget.

As can be seen from the foregoing, the tool widget generally only serves to provide an aesthetic effect for the display interface of the mobile terminal 400, or only to facilitate the use of the mobile terminal user, the function or information provided by the widget itself is relatively fixed, and often there is no need to connect to an application server or a network service in real time to update information. Therefore, the tool widget only needs to be displayed, and the application program corresponding to the tool widget does not need to be continuously run in the background of the mobile terminal 400 to be connected with the network or the application server in real time. Therefore, in this embodiment, when the widget is a tool widget, the data connection of the background application corresponding to the tool widget is directly disconnected.

It should be noted that, the disconnecting of the data connection of the background application corresponding to the tool widget in this embodiment refers to a method of disconnecting the data connection between the background application and the application server or the web service, disconnecting the communication between the tool widget and the corresponding background application, and the like, so that the background application is silent in the background of the mobile terminal 400 and does not respond to the automatic wake-up of the tool widget. For example, when the widget is a tool widget, an instruction for prohibiting the tool widget from automatically waking up a corresponding background application may be added to the power saving policy of the mobile terminal 400.

Through the steps S601-604, the widget management method provided by the present invention determines the tool widget installed in the mobile terminal 400 by obtaining the type of the widget installed in the mobile terminal 400 by the user, and further limits the tool widget, so that the tool widget is only displayed on the display interface of the mobile terminal 400, and the background application corresponding to the tool widget no longer responds to the automatic wake-up of the tool widget, and keeps silent. Therefore, on the basis of meeting the personalized requirements of the mobile terminal user, the method prevents the background application program corresponding to the tool widget from continuously running and continuously responding to the automatic awakening of the tool widget, so that the waste of the electric quantity of the mobile terminal 400 is avoided, and the endurance of the mobile terminal 400 is influenced; and the problem that the starting speed is too slow when the application program is awakened again because the application program corresponding to the tool widget is killed directly is avoided.

Further, based on the above first embodiment of the widget management method according to the present invention, a second embodiment of the widget management method according to the present invention is proposed.

Fig. 7 is a schematic flow chart illustrating an implementation of the widget management method according to the second embodiment of the present invention. In this embodiment, before the step S601, the widget management method further includes:

step S605, when the mobile terminal 400 installs the widget, prompting the mobile terminal user to set the type of the widget, where the type includes a tool class.

From the foregoing, widgets can be generally classified into tool-type widgets and non-tool-type widgets according to their functional characteristics. Also, in the first embodiment, the type of the widget is obtained by first obtaining the name of the widget or the application name corresponding to the widget, and then querying from a preset widget classification table according to the obtained widget name or application name. In contrast, the present embodiment prompts the mobile terminal user to select the type of widget added when it is detected that the mobile terminal user adds a widget to the display interface of the mobile terminal 400. For example, a drop-down menu may be provided that includes both options for tool-like widgets and non-tool-like widgets, which is displayed or popped up when a mobile terminal user adds a widget and prompts the user to make a selection.

Further, in this embodiment, after the mobile terminal user selects the type of the widget, the name of the widget may be obtained, and the name of the widget and the type selected by the user are stored in a data table correspondingly, so that when the same widget is added to the display interface of the mobile terminal 400 again in the following process, the type of the widget is automatically identified, and repeated operations of the mobile terminal user are avoided.

In addition, it is to be added that, in other embodiments, the widget type may also be obtained first by obtaining a name of a widget installed in the mobile terminal 400 or a name of an application program corresponding to the widget when it is detected that a mobile terminal user adds the widget to a display interface of the mobile terminal 400, and then querying the type of the widget from the widget classification table according to the obtained name of the widget or the name of the application program; if the widget name and the application program name corresponding to the widget are not inquired in the widget classification table, a mobile terminal user is prompted to manually select the type of the added widget.

Through the step S605, the widget management method provided by the present invention prompts the mobile terminal user to select the type of the added widget when detecting that the mobile terminal user adds a widget to the display interface of the mobile terminal 400, so that the type of the widget can be manually selected when the mobile terminal user selects to add the widget. Meanwhile, the widget information of the type determined by the mobile terminal user is stored, and the type of the widget can be directly identified when the widget is added repeatedly next time, so that repeated operation of the user is avoided.

Further, a third embodiment of the widget management method of the present invention is proposed based on the above-described first and second embodiments of the widget management method of the present invention.

Fig. 8 is a schematic flow chart illustrating an implementation of the third embodiment of the widget management method according to the present invention. In this embodiment, the step S601 specifically includes:

step S701, inquiring the attributes of the widgets and acquiring the default update frequency value of the widgets.

Step S702, comparing the default update frequency value with a preset update frequency value to determine the type of the widget, where the type includes a tool class.

Generally, when the widget is a tool widget such as a clock widget, a measurement tool widget, a wallpaper widget, a picture widget, a calendar widget, etc., the developer sets the default update frequency value of the widget to a small value, for example, once a day or once every few days, etc. When the widget is a non-tool widget such as a weather forecast widget, a real-time news widget, a music player widget, a video widget, a sports widget, or the like, the developer sets the default update frequency value of the widget to a larger value, for example, once an hour or once every half hour. It can be seen that the default update frequency values set by the developer when developing tool-type widgets and non-tool-type widgets are very different. Therefore, in this embodiment, a default widget update frequency value preset by a widget developer may be obtained first, and then whether the widget is a tool widget or a non-tool widget may be determined according to the default widget update frequency value. For example, a widget whose default update frequency value is higher than once every two hours (i.e., a preset update frequency value) may be determined as a non-tool widget, and a widget whose default update frequency value is not higher than once every two hours may be determined as a tool widget.

Through the steps S701 to S702, the widget management method provided by the present invention obtains the default update frequency value preset by the developer for the widget, and compares the default update frequency value with the preset update frequency value, thereby determining whether the widget is a tool widget or a non-tool widget, providing a new method for automatically determining the widget type, and improving the accuracy of widget type determination.

The above-mentioned serial numbers of the embodiments of the present invention are merely for description and do not represent the merits of the embodiments.

Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solutions of the present invention may be embodied in the form of a software product, which is stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a terminal device (such as a mobile phone, a computer, a server, an air conditioner, or a network device) to execute the method according to the embodiments of the present invention.

The above description is only a preferred embodiment of the present invention, and not intended to limit the scope of the present invention, and all modifications of equivalent structures and equivalent processes, which are made by using the contents of the present specification and the accompanying drawings, or directly or indirectly applied to other related technical fields, are included in the scope of the present invention.

Claims

1. A mobile terminal, wherein a widget is installed in the mobile terminal, the mobile terminal comprising:

and the processing module is used for disconnecting the data connection between the background application program corresponding to the tool type widget and an application program server or a network service.

2. The mobile terminal of claim 1, further comprising a prompting module configured to:

3. The mobile terminal of claim 1, wherein the acquisition module is further configured to:

4. The mobile terminal of claim 1, wherein the acquisition module is further configured to:

5. The mobile terminal of any of claims 1-4, wherein the processing module is further to:

6. A widget management method is applied to a mobile terminal, and is characterized in that a widget is installed in the mobile terminal, and the method comprises the following steps:

displaying the widget and judging whether the widget is a tool widget or not;

and disconnecting the data connection between the background application program corresponding to the tool type widget and an application program server or a network service.

7. The widget management method according to claim 6, wherein prior to the step of acquiring the type of installed widget when a mobile terminal user installs a widget on the mobile terminal, the method further comprises:

8. The widget management method according to claim 6, wherein the step of obtaining the type of the installed widget specifically includes:

9. The widget management method according to claim 6, wherein the step of obtaining the type of the installed widget specifically includes:

10. The widget management method according to any one of claims 6 to 9, wherein the step of disconnecting the data connection of the background application corresponding to the tool type widget specifically includes: