CN106790126B

CN106790126B - Account authorization method and device of application program and terminal

Info

Publication number: CN106790126B
Application number: CN201611228724.7A
Authority: CN
Inventors: 曹坤
Original assignee: SHENZHEN GWELLTIMES TECHNOLOGY Co Ltd
Current assignee: Shenzhen Gwelltimes Technology Co., Ltd.
Priority date: 2016-12-27
Filing date: 2016-12-27
Publication date: 2019-12-24
Anticipated expiration: 2036-12-27
Also published as: CN106790126A

Abstract

The embodiment of the invention discloses a method, a device and a terminal for authorizing an account of an application program, wherein the method comprises the following steps: the method comprises the steps that a terminal establishes an account authorization object list corresponding to an application program, wherein the account authorization object list comprises at least one authorization object, and each authorization object is used for representing a terminal; and the terminal sends account authorization information to the authorization objects in the account authorization object list according to a preset sending strategy, so that the authorization objects log in corresponding application programs by using the account authorization information. Therefore, the information transfer processing is realized in an account authorization mode.

Description

Account authorization method and device of application program and terminal

Technical Field

The invention relates to the technical field of internet, in particular to a method, a device and a terminal for account authorization of an application program.

Background

With the development of science and technology, terminals, especially intelligent terminals, have been applied to various fields of social development to become an integral part of people's work and life, and the functions of terminals are continuously expanded by application programs carried in terminals, and the development of the application programs is gradually optimizing and expanding the functions of the terminals.

At present, in order to meet the work and life requirements of people, various application programs are continuously emerged, for example, thousands of application programs such as social contact, entertainment and learning provide convenience for work and life of people, and people can establish real-time connection with friends through the social contact application programs, realize business exchange with customers and know big things at any time and any place; relaxing the mind and body through entertainment related applications such as video, music, games, etc. However, too many application programs bring much trouble to users, and most application programs can be used only after the users register and log in, so that the users can receive corresponding information only after logging in by using the account and the password corresponding to the application programs, especially the management of the account of the users in the application programs related to the privacy information of the users is stricter, and only one terminal is allowed to log in at the same time. When the amount of information received by the application program in a short time is too large, or the user logs in the application program for a time-out, problems that the information currently sent to the user cannot be processed by the user for the first time or the information reception fails, and other people cannot process the information instead, may cause significant loss to the user once the reception or processing of important information is missed.

Disclosure of Invention

In order to solve the technical problem, embodiments of the present invention provide a method, an apparatus, and a terminal for account authorization of an application program, so that information transfer processing can be implemented in an account authorization manner, and information processing efficiency is improved.

In order to achieve the above purpose, the technical solution of the embodiment of the present invention is realized as follows:

the embodiment of the invention provides an account authorization method for an application program, which comprises the following steps:

the method comprises the steps that a terminal establishes an account authorization object list corresponding to an application program, wherein the account authorization object list comprises at least one authorization object, and each authorization object is used for representing a terminal;

and the terminal sends account authorization information to the authorization objects in the account authorization object list according to a preset sending strategy, so that the authorization objects log in corresponding application programs by using the account authorization information.

In the foregoing scheme, the preset sending policy includes: and when the login time of the application program of the terminal exceeds a preset time threshold value, or when the information quantity received by the application program of the terminal in the preset time is more than a preset information quantity threshold value, the terminal sends account authorization information to an authorization object in the account authorization object list.

In the above scheme, the sending, by the terminal, account authorization information to the authorization object in the account authorization object list includes: the terminal sends the account authorization information to the 1 st authorization object in the account authorization object list;

when the terminal receives account authorization receiving information of the ith authorization object, the terminal stops sending authorization information to authorization objects arranged behind the ith authorization object in the account authorization object list;

when the terminal receives account authorization refusing information of the ith authorization object, the terminal sends authorization information to the (i + 1) th authorization object in the account authorization object list; i is an integer greater than 0;

the account authorization acceptance information of the ith authorization object is used for indicating the ith authorization object to accept the account authorization of the terminal; and the account authorization rejection information of the ith authorization object is used for indicating that the ith authorization object rejects the account authorization of the terminal.

In the above scheme, the sending, by the terminal, account authorization information to the authorization object in the account authorization object list includes: and the terminal simultaneously sends account authorization information to all the authorization objects in the account authorization object list.

In the above scheme, after the terminal establishes the account authorization object list corresponding to the application program, the method further includes: the terminal receives an account authorization application sent by an authorization object in the account authorization object list;

correspondingly, the preset sending strategy comprises the following steps: the terminal sends the account authorization information to a part or all of authorization objects which send the account authorization application; or the terminal refuses to send the account authorization information to part or all of authorization objects which send the account authorization application.

In the above scheme, the account authorization information includes: the identification information of the application program, the login account and the login password of the application program.

The implementation of the invention also provides a device for authorizing the account of the application program, which comprises the following steps: a building module and a sending module, wherein,

the system comprises an establishing module, a processing module and a display module, wherein the establishing module is used for establishing an account authorization object list corresponding to an application program, the account authorization object list comprises at least one authorization object, and each authorization object is used for representing a terminal;

and the sending module is used for sending account authorization information to the authorization objects in the account authorization object list according to a preset sending strategy so that the authorization objects log in the corresponding application programs by using the account authorization information.

In the foregoing scheme, the sending module is specifically configured to send the account authorization information to the authorization object in the account authorization object list when the login time of the application program of the terminal exceeds a preset time threshold, or when the amount of information received by the application program of the terminal within a preset time is greater than a preset information amount threshold.

In the above scheme, the sending module is specifically configured to send the account authorization information to a 1 st authorization object in the account authorization object list;

when the terminal is determined to receive account authorization receiving information of the ith authorization object, stopping sending authorization information to authorization objects arranged behind the ith authorization object in the account authorization object list;

when the terminal is determined to receive account authorization refusing information of the ith authorization object, authorization information is sent to the (i + 1) th authorization object in the account authorization object list; i is an integer greater than 0;

The embodiment of the invention also provides a terminal which comprises a device for authorizing the account of any application program.

According to the account authorization method, the account authorization device and the terminal of the application program, the terminal establishes an account authorization object list corresponding to the application program, the account authorization object list comprises at least one authorization object, and each authorization object is used for representing one terminal; and the terminal sends account authorization information to the authorization objects in the account authorization object list according to a preset sending strategy, so that the authorization objects log in corresponding application programs by using the account authorization information. Compared with the prior art, the embodiment of the invention realizes the information transfer processing in an account authorization mode.

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 front view of a mobile terminal according to a first embodiment of the present invention;

fig. 4 is a rear view of a mobile terminal according to a first embodiment of the present invention;

FIG. 5 is a flowchart of a method for account authorization of an application according to a first embodiment of the present invention;

FIG. 6 is a flowchart of a method for account authorization of an application according to a second embodiment of the present invention;

fig. 7 is a terminal interaction diagram according to a second embodiment of the present invention;

FIG. 8 is a flowchart of a method for account authorization of an application according to a third embodiment of the present invention;

FIG. 9 is a flowchart of a fourth embodiment of a method for account authorization of an application according to the present invention;

FIG. 10 is a diagram illustrating terminal account authorization in an embodiment of the present invention;

fig. 11 is a schematic structural diagram of a device for account authorization of an application according to an embodiment of the present invention.

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 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 may be implemented in various forms. For example, the terminal described in the embodiments of the present invention may include a mobile terminal such as a mobile phone, a smart phone, a notebook computer, a digital broadcast receiver, a Personal Digital Assistant (PDA), a PAD computer (PAD), a Portable Multimedia Player (PMP), a navigation device, and the like, and a fixed 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. 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 diagram of a hardware structure of an optional mobile terminal for implementing various embodiments of the present invention.

The mobile terminal 100 may include a wireless communication unit 110, an audio/video (a/V) input unit 120, a user input unit 130, a sensing unit 140, an output unit 150, a memory 160, an interface unit 170, a controller 180, and a power supply unit 190, etc. Fig. 1 illustrates a mobile terminal 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. Elements of the mobile terminal will be described in detail below.

The wireless communication unit 110 typically includes one or more components that allow radio communication between the mobile terminal 100 and a wireless communication system or network. For example, the wireless communication unit may include at least one of a broadcast receiving module 111, a mobile communication module 112, a wireless internet module 113, a short-range communication module 114, and a location information module 115.

The broadcast receiving module 111 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 112. 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 111 may receive a signal broadcast by using various types of broadcasting systems. In particular, the broadcast receiving module 111 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 111 may be constructed to be suitable for various broadcasting systems that provide broadcast signals as well as the above-mentioned digital broadcasting systems. The broadcast signal and/or broadcast associated information received via the broadcast receiving module 111 may be stored in the memory 160 (or other type of storage medium).

The mobile communication module 112 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 113 supports wireless internet access of the mobile terminal. The module may be internally or externally coupled to the terminal. The wireless internet access technology to which the module relates may include Wireless Local Area Network (WLAN) (Wi-Fi), wireless broadband (Wibro), worldwide interoperability for microwave access (Wimax), High Speed Downlink Packet Access (HSDPA), and the like.

The short-range communication module 114 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 115 is a module for checking or acquiring location information of the mobile terminal. A typical example of the location information module is a Global Positioning System (GPS). According to the current technology, the location information module 115, which is a GPS, 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 115 can calculate speed information by continuously calculating current position information in real time.

The a/V input unit 120 is used to receive an audio or video signal. The a/V input unit 120 may include a camera 121 and a microphone 1220, and the camera 121 processes image data of still pictures or video obtained by an image capturing apparatus in a video capturing mode or an image capturing mode. The processed image frames may be displayed on the display unit 151. The image frames processed by the cameras 121 may be stored in the memory 160 (or other storage medium) or transmitted via the wireless communication unit 110, and two or more cameras 121 may be provided according to the construction of the mobile terminal. The microphone 122 may receive sounds (audio data) via the microphone in a phone call mode, a recording mode, a voice recognition mode, or the like, and can process such sounds into audio data. The processed audio (voice) data may be converted into a format output transmittable to a mobile communication base station via the mobile communication module 112 in case of a phone call mode. The microphone 122 may implement various types of noise cancellation (or suppression) algorithms to cancel (or suppress) noise or interference generated in the course of receiving and transmitting audio signals.

The user input unit 130 may generate key input data according to a command input by a user to control various operations of the mobile terminal. The user input unit 130 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, etc. due to being touched), scroll wheel, joystick, etc. In particular, when the touch pad is superimposed on the display unit 151 in the form of a layer, a touch screen may be formed.

The sensing unit 140 detects a current state of the mobile terminal 100 (e.g., an open or closed state of the mobile terminal 100), a position of the mobile terminal 100, presence or absence of contact (i.e., touch input) by a user with the mobile terminal 100, an orientation of the mobile terminal 100, acceleration or deceleration movement and direction of the mobile terminal 100, and the like, and generates a command or signal for controlling an operation of the mobile terminal 100. For example, when the mobile terminal 100 is implemented as a slide-type mobile phone, the sensing unit 140 may sense whether the slide-type phone is opened or closed. In addition, the sensing unit 140 can detect whether the power supply unit 190 supplies power or whether the interface unit 170 is coupled with an external device.

The interface unit 170 serves as an interface through which at least one external device is connected to the mobile terminal 100. 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 100 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 100 via a port or other connection means. The interface unit 170 may be used to receive input (e.g., data information, power, etc.) from an external device and transmit the received input to one or more elements within the mobile terminal 100 or may be used to transmit data between the mobile terminal and the external device.

In addition, when the mobile terminal 100 is connected with an external cradle, the interface unit 170 may serve as a path through which power is supplied from the cradle to the mobile terminal 100 or may serve as a path through which various command signals input from the cradle are transmitted to the mobile terminal. Various command signals or power input from the cradle may be used as signals for recognizing whether the mobile terminal is accurately mounted on the cradle. The output unit 150 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 150 may include a display unit 151, an audio output module 152, an alarm unit 153, and the like.

The display unit 151 may display information processed in the mobile terminal 100. For example, when the mobile terminal 100 is in a phone call mode, the display unit 151 may display a User's 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 100 is in a video call mode or an image capturing mode, the display unit 151 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 151 and the touch pad are overlapped with each other in the form of a layer to form a touch screen, the display unit 151 may serve as an input device and an output device. The display unit 151 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 see from the outside, which may be referred to as transparent displays, and a typical transparent display may be, for example, a Transparent Organic Light Emitting Diode (TOLED) display or the like. Depending on the particular desired implementation, the mobile terminal 100 may include two or more display units (or other display devices), for example, the mobile terminal 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 152 may convert audio data received by the wireless communication unit 110 or stored in the memory 160 into an audio signal and output as sound when the mobile terminal 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 152 may provide audio output related to a specific function performed by the mobile terminal 100 (e.g., a call signal reception sound, a message reception sound, etc.). The audio output module 152 may include a speaker, a buzzer, and the like.

The alarm unit 153 may provide an output to notify the mobile terminal 100 of the occurrence of an event. Typical events may include call reception, message reception, key signal input, touch input, and the like. In addition to audio or video output, the alarm unit 153 may provide output in different ways to notify the occurrence of an event. For example, the alarm unit 153 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 153 may provide a tactile output (i.e., vibration) to inform 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 153 may also provide an output notifying the occurrence of an event via the display unit 151 or the audio output module 152.

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

The memory 160 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, and the like. Also, the mobile terminal 100 may cooperate with a network storage device that performs a storage function of the memory 160 through a network connection.

The controller 180 generally controls the overall operation of the mobile terminal. For example, the controller 180 performs control and processing related to voice calls, data communications, video calls, and the like. In addition, the controller 180 may include a multimedia module 181 for reproducing (or playing back) multimedia data, and the multimedia module 181 may be constructed within the controller 180 or may be constructed separately from the controller 180. The controller 180 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 190 receives external power or internal power and provides appropriate power required to operate various elements and components under the control of the controller 180.

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 180. 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 the memory 160 and executed by the controller 180.

Up to now, the mobile terminal has been described in terms of its functions. Hereinafter, a slide-type mobile terminal among various types of mobile terminals, such as a folder-type, bar-type, swing-type, slide-type mobile terminal, 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, and is not limited to a slide type mobile terminal.

The mobile terminal 100 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 according to the present invention is operable 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, the CDMA wireless communication system may include a plurality of mobile terminals 100, 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 275.

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 the mobile terminal 100 operating within the system. A broadcast receiving module 111 as shown in fig. 1 is provided at the mobile terminal 100 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 100.

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 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 the wireless communication system, the BS270 receives reverse link signals from various mobile terminals 100. The mobile terminal 100 is generally 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 100.

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

The technical solution in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention.

First embodiment

The first embodiment of the invention provides an account authorization method for an application program, which can be applied to a terminal.

Here, the terminal described above may be a fixed terminal having a display screen, or may be a mobile terminal having a display screen.

The above-mentioned fixed terminal may be a computer, and the above-mentioned mobile terminal includes but is not limited to a mobile phone, a notebook computer, a camera, a PDA, a PAD, a PMP, a navigation device, and the like. The terminal can be connected to the internet, wherein the connection mode can be through a mobile internet network provided by an operator, and can also be through accessing a wireless access point to perform network connection.

Here, if the mobile terminal has an operating system, the operating system may be UNIX, Linux, Windows, Android (Android), Windows Phone, or the like.

The type, shape, size, and the like of the display screen on the terminal are not limited, and the display screen on the terminal may be a liquid crystal display screen, for example.

In a first embodiment of the present invention, the display screen is used to provide a human-computer interaction interface for a user, and when the mobile terminal is a mobile phone, fig. 3 is a front view of the mobile terminal according to the first embodiment of the present invention, and fig. 4 is a rear view of the mobile terminal according to the first embodiment of the present invention.

Fig. 5 is a flowchart of a method for account authorization of an application according to a first embodiment of the present invention, and as shown in fig. 5, the method includes:

step 500: the method comprises the steps that a terminal establishes an account authorization object list corresponding to an application program, the account authorization object list comprises at least one authorization object, and each authorization object is used for representing a terminal.

In actual implementation, the source of the authorization object in the account authorization object list may be a terminal address list, a buddy list of the authorization object application program a, or a buddy list of a specific application program.

Each authorization object is used for representing a terminal, and the authorization object can perform account authorization operation only when the terminal is used for logging in a related application program.

Step 501: and the terminal sends account authorization information to the authorization objects in the account authorization object list according to a preset sending strategy, so that the authorization objects log in corresponding application programs by using the account authorization information.

Preferably, the preset sending policy may include: and when the login time of the application program of the terminal exceeds a preset time threshold value, or when the information quantity received by the application program of the terminal in the preset time is more than a preset information quantity threshold value, the terminal sends account authorization information to an authorization object in the account authorization object list.

Illustratively, when the current network state is poor, the user logs in the application program a overtime, or the amount of information received by the application program a in a unit time is greater than a preset information amount threshold, and the received information is in an "unread" state, the terminal a sends account authorization information to an authorization object in an account authorization object list, so as to authorize other users to log in the application program a by using their own accounts and help to process related information.

Optionally, the terminal may also actively send account authorization information to the authorization objects in the account authorization object list, and this way may be that the user actively asks others to help to handle mails, video/telephone conferences, etc. when the user is busy.

Optionally, before the terminal sends the account authorization information to the authorization object in the account authorization object list according to a preset sending policy, the method further includes: the terminal sends an account authorization notification to an authorization object in the account authorization object list according to a preset sending strategy, and the account authorization notification is used for prompting the authorization object to receive account authorization so that the authorization object judges whether to accept current account authorization. When the authorization object accepts account authorization, returning account authorization acceptance information; and returning account authorization refusing information when the authorization object refuses account authorization.

Further, the terminal sends account authorization information to the authorization objects in the account authorization object list, including: the terminal sends the account authorization information to the 1 st authorization object in the account authorization object list;

It can be understood that the authorization objects in the account authorization object list are sequentially arranged according to a certain arrangement rule, and the terminal sequentially sends the authorization information according to the order of authorization. For example, the terminal sends the authorization information to the 1 st authorization object, and when the 1 st authorization object refuses account authorization, the terminal sends the authorization information to the 2 nd authorization object; when the 1 st authorization object receives account authorization, the authorization information is stopped from being sent to the 2 nd authorization object. If all the authorization objects in the account authorization object list reject account authorization, at this time, the account authorization information is retransmitted according to the sending method, a new account authorization object list can also be established, and then the account authorization information is sent to the new account authorization object list according to the sending method.

The terminal sends account authorization information to the authorization object in the account authorization object list, and may further include: and the terminal simultaneously sends account authorization information to all the authorization objects in the account authorization object list.

In practical implementation, when a user needs to complete account authorization quickly, account authorization information can be sent to all authorization objects simultaneously, and an account is authorized to an authorization object which returns 'account authorization acceptance information' at the fastest speed, or the account is authorized to all authorization objects which return 'account authorization acceptance information'.

Optionally, the account authorization information may include: the identification information of the application program, the login account and the login password of the application program.

And after the authorization object accepts account authorization, the authorization object logs in a corresponding application program by using the account authorization information to execute corresponding operation.

Another optional scheme is that after the terminal establishes an account authorization object list corresponding to the application program, the terminal receives an account authorization application sent by an authorization object in the account authorization object list;

It can be understood that, an authorization object in the account authorization list may also actively apply for account authorization, and when a plurality of authorization objects simultaneously apply for account authorization, the accounts may be authorized to the authorization object with the top arrangement order according to the arrangement order of the authorization objects in the list, or each applied authorization object may obtain account authorization. For example, the 2 nd, 4 th and 5 th authorization objects simultaneously apply for authorization of the account to the 2 nd authorization object, or the 2 nd, 4 th and 5 th authorization objects all obtain account authorization.

In order to further embody the object of the present invention, the above-mentioned scheme is further exemplified on the basis of the first embodiment of the present invention.

Second embodiment

Fig. 6 is a flowchart of a method for account authorization of an application according to a second embodiment of the present invention, as shown in fig. 6, the flowchart includes:

step 600: and the terminal A starts the account authorization function of the application program A.

In the embodiment of the invention, the corresponding account authorization function can be set for each application program in the terminal, so that more targeted account management can be realized, and whether the account authorization function needs to be started or not is judged according to the specific function and the different importance of each application program.

Step 601: the terminal A establishes an account authorization object list, and the initialization of i is set to 1.

In actual implementation, the terminal a establishes an authorized object list corresponding to the application a by using a friend who is allowed to receive the information of the application a, where the authorized object list includes N pieces of authorized object information, and N is an integer greater than 0. The authorization object information includes: the mobile phone number of the authorization object, the account number of the authorization object application program A, or the account number of the authorization object in a certain specified application program. And corresponding account authorization object lists B, C and the like can be established for the application programs B, C and the like. And when account authorization management is carried out on each application program, using the corresponding account authorization object list.

In this step, the user may sort the authorized objects according to the trust level, and authorize the account of the application a to the authorized object with the highest trust level first.

Illustratively, the account authorization object list includes friend 1, friend 2, friend 3 to friend N. The friends in the account authorization object list are sorted according to the trust level, account authorization can be performed on the friends in sequence from high to low according to the trust level when the friends are subjected to account authorization, and once the friends receive account authorization of the application program A, account authorization on other friends in the account authorization list is stopped.

In this step, after the terminal a establishes the account number authorized object list, it sets i to 1 initially. And when i is larger than the total number of friends (i.e. N) set in the list, i is set to 1.

Step 602: and the terminal A sends an account authorization notice to a friend terminal i in the account authorization object list.

Step 603: after receiving the account authorization notification, the friend terminal i determines whether to accept account authorization of the terminal a, and if so, executes step 604; if not, step 605 is performed.

Here, the account authorization notification is used to remind the friend terminal i to currently receive an account authorization from the terminal a, and the friend terminal i can select to accept/reject the current account authorization and generate corresponding "account authorization acceptance information"/"account authorization rejection information".

Step 604: and the friend terminal i sends account authorization acceptance information to the terminal A, and executes the step 606.

Step 605: and the friend terminal i sends account authorization rejection information to the terminal A, and executes the step 606.

Step 606: the terminal A judges whether account authorization acceptance information is received, if so, the step 607 is executed; if not, go to step 608.

Step 607: and the terminal A sends the authorization information of the application program A to the friend terminal i, and the friend terminal i starts to receive all new messages of the application program A of the terminal A.

In actual implementation, the authorization information of the application program a may be identification information, an account number, and password information of the application program a, the terminal a encrypts the identification information, the account number, and the password information of the application program a to generate an encrypted file and sends the encrypted file to the friend terminal i, and the friend terminal i logs in the application program a by using the account number and the password in the encrypted file according to the identification information of the application program a and processes related information.

Step 608: after i is added by 1, judging whether i is larger than N, if so, returning to the step 600; if not, return to step 602.

It can be understood that when the value of i added by 1 is greater than N, it indicates that all the friends in the currently established account authorization object list cannot accept account authorization of the application a of the terminal a, and at this time, the process may return to step 600 to establish a new account authorization object list, or send authorization information to the authorization object again.

Fig. 7 is a terminal interaction diagram according to a second embodiment of the present invention, and as shown in fig. 7, after receiving an account authorization notification sent by a terminal a, a friend terminal i may select to click an "accept" or "reject" button; sending an authorization receiving prompt message to a terminal A after a friend terminal i selects to receive account authorization, and sending account authorization information to the friend terminal i after the terminal A confirms that the friend terminal i receives account authorization; after receiving the account authorization information, the friend terminal i can select to immediately log in the application program A by using the authorization information, and can also select to log in later.

Third embodiment

To further illustrate the object of the present invention, the first embodiment of the present invention is further exemplified.

Fig. 8 is a flowchart of a method for account authorization of an application according to a third embodiment of the present invention, where as shown in fig. 8, the flowchart includes:

step 800: the terminal A starts an account authorization function and establishes an account authorization object list.

In the embodiment of the invention, the terminal A uses the same account authorization object list to execute account authorization operation on all application programs, when a user establishes the account authorization object list, the selected authorization objects are often fixed friends, and the authorization objects in the account authorization object list corresponding to each application program have small difference, so that in order to avoid complicated authorization setting, the authorization objects of all application programs can be set to be the same, and after the account authorization function is started, the account authorization object lists used by each application program are the same.

Step 801: and the terminal A sends account authorization information to all the authorization objects in the account authorization object list.

Here, the account authorization information may include: the method comprises the following steps that account authorization prompt information of the terminal A, identification information of an application program authorized by the terminal A, an account and password information.

Step 802: after receiving the authorization information, the authorization object selects whether to accept account authorization of the terminal a, and if so, executes step 803; if not, go to step 804.

Step 803: the authorization object sends account authorization acceptance information to the terminal A and starts to receive all new messages of the application program authorized by the terminal A.

It can be understood that, after the terminal a sends account authorization information to all authorization objects in the account authorization object list at the same time, all authorized terminals can log in to corresponding applications according to the authorization information and start to receive all new messages of the applications authorized by the terminal a.

In the embodiment of the invention, in order to simplify the operation steps, after the authorization object confirms to accept the account authorization, the authorization object can immediately log in and start to receive the new message of the authorized application program, and the corresponding account and password information is issued without the need of confirming again by the terminal A. The operation times are reduced, and the user experience is improved.

Step 804: and the authorization object sends account authorization refusing information to the terminal A.

Fourth embodiment

To further illustrate the object of the present invention, the first embodiment of the present invention is further illustrated.

Fig. 9 is a flowchart of a method for account authorization of an application according to a fourth embodiment of the present invention, where as shown in fig. 9, the flowchart includes:

step 900: and the terminal A starts the account authorization function of the application program B.

Step 901: and the terminal A establishes an account authorization object list of the application program B.

Optionally, the authorization object source in the account authorization object list may be at least one of: the terminal A address list, the friend list of a user specified certain application program and the friend list of the application program B.

It should be noted that the order of opening the account authorization function and establishing the account authorization object list is not strict, or a default account authorization object list may be established in advance, and when the account authorization function is re-opened each time, the user is prompted whether to modify the default account authorization object list, or the default account authorization object list is directly used, and when the user needs to modify, the modification is performed again.

Step 902: and the friend terminal in the account authorization object list of the application program B sends an account authorization application of the application program B to the terminal A.

In the embodiment of the invention, friends in the account authorization object list of the application program B of the terminal A can also actively apply account authorization to the terminal A to acquire information in the account of the application program B of the terminal A. The priorities of the friends applying account authorization to the terminal a in the account authorization object list can be the same, that is, the order of friend application does not need to be set in the account authorization object list. When a plurality of friends in the list need to use the account of the application program B of the user, the user can simultaneously apply for account authorization, and the user can choose to accept or reject part or all of the account authorization application.

For example, in some applications such as games, videos, and music, a user may establish an account authorization object list and allow friends in the list to apply account authorization to the user, so if the user's account is a privileged user (e.g., a member user), the user may allow the friends to log in when the user does not use the application, so as to implement sharing of privileged resources.

Step 903: after receiving an account authorization application of an application program B sent by a friend terminal, a terminal A judges whether to receive the account authorization application of the friend terminal, and if not, executes step 904; if so, step 905 is performed.

In this step, after the terminal a receives the account authorization application of the application program B sent by at least one friend terminal, according to the account use condition of the current application program B, it may select to accept or reject part or all of the account authorization application.

Step 904: and the terminal A sends the information of refusing the account authorization application to the friend terminal.

Optionally, when the number of times that the terminal a rejects the application for account authorization of the friend terminal C is greater than the rejection number threshold, the friend terminal C may be deleted from the list of account authorization objects for filtering the application information for account authorization after the friend terminal C.

Step 905: and the terminal A sends the information of receiving the account authorization application to the friend terminal and simultaneously sends the authorization information of the application program B.

In actual implementation, the terminal a may further set account authorization conditions of the application program B, including account authorization time limit, account authorization number limit, and the like.

Step 906: and the friend terminal logs in the application program B by using the authorization information.

Fig. 10 is a schematic diagram illustrating terminal account authorization in an embodiment of the present invention, as shown in fig. 10, a friend terminal 1 to a friend terminal N may simultaneously send an account authorization application to a terminal a, and after determining whether account authorization is performed, the terminal a returns account authorization permission information and authorization information to a friend terminal that permits the account authorization application; and returning the account authorization refusing information to the friend terminal refusing the authorization application, or not sending any information.

The terminal establishes an account authorization object list corresponding to the application program, wherein the account authorization object list comprises at least one authorization object, and each authorization object is used for representing one terminal. And the terminal sends account authorization information to the authorization objects in the account authorization object list according to a preset sending strategy, so that the authorization objects log in corresponding application programs by using the account authorization information. Compared with the prior art, the embodiment of the invention realizes the information transfer processing in an account authorization mode.

Fifth embodiment

Aiming at the method of the embodiment of the invention, the embodiment of the invention also provides a device for authorizing the account of the application program.

Fig. 11 is a schematic structural diagram of a device for account authorization of an application according to an embodiment of the present invention, and as shown in fig. 11, the device includes: a setup module 1100 and a sending module 1101, wherein,

an establishing module 1100, configured to establish an account authorization object list corresponding to an application, where the account authorization object list includes at least one authorization object, and each authorization object is used to represent a terminal;

a sending module 1101, configured to send account authorization information to an authorization object in the account authorization object list according to a preset sending policy, so that the authorization object logs in a corresponding application program by using the account authorization information.

Preferably, the sending module 1101 is specifically configured to send the account authorization information to the authorization object in the account authorization object list when the login time of the application program of the terminal exceeds a preset time threshold, or when the amount of information received by the application program of the terminal within a preset time is greater than a preset information amount threshold.

Preferably, the sending module 1101 is specifically configured to send the account authorization information to a 1 st authorization object in the account authorization object list;

Preferably, the sending module 1101 is specifically configured to send account authorization information to all authorization objects in the account authorization object list at the same time.

Optionally, the sending module 1101 is further configured to receive an account authorization application sent by an authorization object in the account authorization object list;

Preferably, the account authorization information includes: the identification information of the application program, the login account and the login password of the application program.

In practical applications, the establishing module 1100 and the sending module 1101 may be implemented by a Central Processing Unit (CPU), a microprocessor Unit (MPU), a Digital Signal Processor (DSP), a Field Programmable Gate Array (FPGA), or the like in the terminal.

As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of a hardware embodiment, a software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, optical storage, and the like) having computer-usable program code embodied therein.

The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

The above description is only a preferred embodiment of the present invention, and is not intended to limit the scope of the present invention.

Claims

1. A method for account authorization of an application program, the method comprising:

the terminal sends account authorization information to an authorization object in the account authorization object list according to a preset sending strategy, so that the authorization object logs in a corresponding application program by using the account authorization information;

the preset sending strategy comprises the following steps: when the login time of the application program of the terminal exceeds a preset time threshold value, or when the information amount received by the application program of the terminal in a preset time is larger than a preset information amount threshold value, the terminal sends account authorization information to an authorization object in the account authorization object list;

the sending account authorization information to the authorization object in the account authorization object list includes:

sending account authorization information to authorization objects in the account authorization object list, and if all authorization objects in the account authorization object list reject account authorization, resending the account authorization information according to the account authorization object list; or establishing a new account authorization object list, and sending account authorization information according to the new account authorization object list.

2. The method according to claim 1, wherein the terminal sends account authorization information to the authorization objects in the account authorization object list, and the method comprises: the terminal sends the account authorization information to the 1 st authorization object in the account authorization object list;

3. The method according to claim 1, wherein the terminal sends account authorization information to the authorization objects in the account authorization object list, and the method comprises: and the terminal simultaneously sends account authorization information to all the authorization objects in the account authorization object list.

4. The method according to claim 1, wherein after the terminal establishes the list of account authorized objects corresponding to the application program, the method further comprises: the terminal receives an account authorization application sent by an authorization object in the account authorization object list;

5. The method of claim 1, wherein the account authorization information comprises: the identification information of the application program, the login account and the login password of the application program.

6. An apparatus for account authorization of an application, the apparatus being located in a terminal, the apparatus comprising: a building module and a sending module, wherein,

the sending module is used for sending account authorization information to the authorization objects in the account authorization object list according to a preset sending strategy so that the authorization objects log in the corresponding application programs by using the account authorization information;

the sending module is specifically configured to send account authorization information to an authorization object in the account authorization object list when login time of the application program of the terminal exceeds a preset time threshold or when information amount received by the application program of the terminal within a preset time is greater than a preset information amount threshold;

7. The apparatus according to claim 6, wherein the sending module is specifically configured to send the account authorization information to a 1 st authorization object in the account authorization object list;

8. A terminal, characterized in that it comprises the apparatus of any of claims 6 and 7.