CN106408304B - Account security management method and device - Google Patents
Account security management method and device Download PDFInfo
- Publication number
- CN106408304B CN106408304B CN201610857709.2A CN201610857709A CN106408304B CN 106408304 B CN106408304 B CN 106408304B CN 201610857709 A CN201610857709 A CN 201610857709A CN 106408304 B CN106408304 B CN 106408304B
- Authority
- CN
- China
- Prior art keywords
- account
- target account
- security management
- target
- interface
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
- G06Q20/401—Transaction verification
- G06Q20/4014—Identity check for transactions
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/382—Payment protocols; Details thereof insuring higher security of transaction
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
- G06Q20/401—Transaction verification
- G06Q20/4014—Identity check for transactions
- G06Q20/40145—Biometric identity checks
Landscapes
- Business, Economics & Management (AREA)
- Engineering & Computer Science (AREA)
- Accounting & Taxation (AREA)
- Computer Security & Cryptography (AREA)
- Finance (AREA)
- Strategic Management (AREA)
- Physics & Mathematics (AREA)
- General Business, Economics & Management (AREA)
- General Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- Telephonic Communication Services (AREA)
- Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
Abstract
The disclosure relates to an account security management method and device. Wherein, the method comprises the following steps: acquiring a target account selected from preset security management accounts, wherein the security management accounts are accounts included in applications needing security management; calling out a security management interface corresponding to the target account from the application corresponding to the target account; and under the condition that the authentication information of the user is acquired from the security management interface, sending the target account and the authentication information to the application corresponding to the target account, wherein the target account and the authentication information are used for requesting the corresponding server for security management of the target account by the application corresponding to the target account. According to the method and the device, the safety management interface is provided through each application, so that the safety management of each safety management account can be uniformly carried out, the speed of carrying out safety management on a plurality of accounts can be increased, the operation time is shortened, and the loss of users is reduced.
Description
Technical Field
The present disclosure relates to the field of internet technologies, and in particular, to a method and an apparatus for managing account security.
Background
With the continuous development and improvement of computer technology and the wide application of the internet, the human society irreversibly enters the information-based era. The network provides a convenient information transfer mode and a brand-new life mode for the human, and simultaneously creates a new crime approach, namely phishing. In recent years, the phishing methods are diversified and varied, so that people can be defended.
Once found to be deceived, the account is frozen by logging in to the bank, purse, etc., and is sometimes withdrawn for many times, resulting in irretrievable economic loss.
Disclosure of Invention
To overcome the problems in the related art, the present disclosure provides an account security management method and apparatus.
According to a first aspect of the embodiments of the present disclosure, there is provided an account security management method, including:
acquiring a target account selected from preset security management accounts, wherein the security management accounts are accounts included in applications needing security management;
calling out a security management interface corresponding to the target account from the application corresponding to the target account;
and under the condition that the authentication information of the user is acquired from the security management interface, sending the target account and the authentication information to the application corresponding to the target account, wherein the target account and the authentication information are used for requesting the corresponding server for security management of the target account by the application corresponding to the target account.
For the above method, in a possible implementation manner, invoking a security management interface corresponding to the target account from an application corresponding to the target account includes: calling out a key modification interface corresponding to the target account from the application corresponding to the target account;
under the condition that the authentication information of the user is acquired from the security management interface, the step of sending the target account and the authentication information to the application corresponding to the target account comprises the following steps: and under the condition that a key to be verified and a key to be modified of a user are obtained from the password modification interface, sending the target account, the key to be verified and the key to be modified to an application corresponding to the target account.
For the above method, in a possible implementation manner, invoking a security management interface corresponding to the target account from an application corresponding to the target account further includes: calling out a frozen account interface corresponding to the target account from the application corresponding to the target account;
under the condition that the authentication information of the user is acquired from the security management interface, the target account and the authentication information are sent to the application corresponding to the target account, and the method further comprises the following steps: and under the condition that a key to be verified of a user is obtained from the frozen account interface, sending the target account and the key to be verified to an application corresponding to the target account.
For the above method, in a possible implementation manner, invoking a security management interface corresponding to the target account from an application corresponding to the target account further includes: calling a unfreezing account interface corresponding to the target account from the application corresponding to the target account;
under the condition that the authentication information of the user is acquired from the security management interface, the target account and the authentication information are sent to the application corresponding to the target account, and the method further comprises the following steps: and under the condition that a key to be verified of a user is obtained from the unfreezing account interface, sending the target account and the key to be verified to an application corresponding to the target account.
For the above method, in a possible implementation manner, the method further includes:
and after the security management of the target account is completed, acquiring the next account of the target account selected from preset security management accounts as the target account.
For the above method, in a possible implementation manner, the method further includes:
acquiring a target application selected from each application needing security management;
calling out a security management interface from the target application;
under the condition that an account to be set of a user and corresponding verification information thereof are obtained from a security management interface of the target application, the account to be set and the corresponding verification information thereof are sent to the target application, and the account to be set and the corresponding verification information thereof are used for requesting a server corresponding to the target application to perform key verification on the account to be set;
and under the condition that the account to be set passes the verification, saving the account to be set as a safety management account.
According to a second aspect of the embodiments of the present disclosure, there is provided an account security management apparatus, including:
the system comprises a first acquisition module, a second acquisition module and a third acquisition module, wherein the first acquisition module is used for acquiring a target account selected from preset security management accounts, and the security management accounts are accounts included in applications needing security management;
the first calling module is used for calling out a security management interface corresponding to the target account from the application corresponding to the target account;
the first sending module is used for sending the target account and the verification information to an application corresponding to the target account under the condition that the verification information of a user is obtained from the security management interface, wherein the target account and the verification information are used for requesting the corresponding server to perform security management on the target account by the application corresponding to the target account.
For the apparatus described above, in one possible implementation manner, the first callout module includes: the first calling-out submodule is used for calling out a modified key interface corresponding to the target account from the application corresponding to the target account; the first transmitting module includes: and the first sending submodule is used for sending the target account, the key to be verified and the key to be modified to the application corresponding to the target account under the condition of acquiring the key to be verified and the key to be modified of the user from the password modification interface.
For the apparatus described above, in a possible implementation manner, the first callout module further includes: the second calling sub-module is used for calling out a frozen account interface corresponding to the target account from the application corresponding to the target account; the first transmitting module further comprises: and the second sending submodule is used for sending the target account and the key to be verified to the application corresponding to the target account under the condition that the key to be verified of the user is obtained from the frozen account interface.
For the apparatus described above, in a possible implementation manner, the first callout module further includes: a third calling sub-module, configured to call out a unfreezing account interface corresponding to the target account from the application corresponding to the target account; the first transmitting module further comprises: and the third sending submodule is used for sending the target account and the key to be verified to the application corresponding to the target account under the condition that the key to be verified of the user is obtained from the unfreezing account interface.
For the above apparatus, in a possible implementation manner, the apparatus further includes:
and the second acquisition module is used for acquiring the next account of the target account selected from preset safety management accounts as the target account after the safety management of the target account is completed.
For the above apparatus, in a possible implementation manner, the apparatus further includes:
the third acquisition module is used for acquiring a target application selected from various applications needing security management;
the second calling module is used for calling out a security management interface from the target application;
the second sending module is used for sending the account to be set and the corresponding verification information thereof to the target application under the condition that the account to be set and the corresponding verification information thereof of the user are obtained from the security management interface of the target application, wherein the account to be set and the corresponding verification information thereof are used for requesting the server to carry out key verification on the account to be set by the target application;
and the storage module is used for storing the account to be set as a safety management account under the condition that the verification of the account to be set passes.
According to a third aspect of the embodiments of the present disclosure, there is provided an account security management apparatus, including:
a processor;
a memory for storing processor-executable instructions;
wherein the processor is configured to:
acquiring a target account selected from preset security management accounts, wherein the security management accounts are accounts included in applications needing security management;
calling out a security management interface corresponding to the target account from the application corresponding to the target account;
and under the condition that the authentication information of the user is acquired from the security management interface, sending the target account and the authentication information to the application corresponding to the target account, wherein the target account and the authentication information are used for requesting the corresponding server for security management of the target account by the application corresponding to the target account.
The technical scheme provided by the embodiment of the disclosure can have the following beneficial effects: the target account can be selected from the preset safety management accounts, and the safety management interface is provided through each application, so that the safety management of each safety management account is realized uniformly, the speed of performing safety management on a plurality of accounts can be improved, the operation time is reduced, and the user loss is reduced.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and together with the description, serve to explain the principles of the disclosure.
FIG. 1 is a flow diagram illustrating a method for account security management, according to an example embodiment.
FIG. 2 is a flow diagram illustrating a method for account security management in accordance with another exemplary embodiment.
FIG. 3 is a block diagram illustrating an account security management apparatus in accordance with an exemplary embodiment.
Fig. 4 is a block diagram illustrating an account security management apparatus according to another exemplary embodiment.
Fig. 5 is a block diagram illustrating an account security management apparatus according to another exemplary embodiment.
Detailed Description
Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the exemplary embodiments below are not intended to represent all implementations consistent with the present disclosure. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present disclosure, as detailed in the appended claims.
Fig. 1 is a flowchart illustrating an account security management method according to an exemplary embodiment, where the account security management method may be used in a terminal, as shown in fig. 1, and includes the following steps.
In step 101, a target account selected from preset security management accounts is acquired, where the security management account is an account included in each application that needs to be security managed.
In step 102, a security management interface corresponding to the target account is called from an application corresponding to the target account.
In step 103, when the authentication information of the user is acquired from the security management interface, the target account and the authentication information are sent to the application corresponding to the target account, and the target account and the authentication information are used for requesting, by the application corresponding to the target account, a corresponding server to perform security management on the target account.
In this embodiment, a client (application for short) of various application programs may be installed on a terminal such as a mobile phone or a computer, and some applications may need to be managed safely. For example, an internet banking application (app) of various banks, an app of various payment instruments, an app of various financial instruments, and the like. In the account security management method of this embodiment, for each application that needs to be security-managed, authentication information such as an account number and a login name that can be supported by each application may be stored in advance, so that a security management account for each application is generated in advance. One application may pre-store one security management account or multiple security management accounts. For example, a user may have multiple savings card accounts at a bank, and all of the multiple savings card accounts may be saved as security management accounts. If the situation that the security management needs to be performed uniformly occurs, for example, when phishing or abnormal operation of the account is found, the target account can be selected from the pre-stored security management accounts, and the corresponding security management interface, for example, the account interface is blocked, can be called from the application corresponding to the security management account. Then, after the user inputs authentication information such as a password, a fingerprint, a voiceprint, etc. from the interface, the target account and its corresponding password may be sent to the application (client), and sent by the application to a corresponding server, for example: a password authentication server of a certain bank. And after receiving the target account and the corresponding password, the server verifies whether the password is accurate. If the password is correct, the server may freeze the target account. The server may also send a notification of successful freeze, or the like, to the application.
According to the embodiment, the security management interfaces are provided through the applications, so that the security management of all the security management accounts can be uniformly performed, the speed of performing the security management on a plurality of accounts can be increased, the operation time is shortened, and the user loss is reduced.
Fig. 2 is a flowchart illustrating an account security management method according to another exemplary embodiment, and as shown in fig. 2, the account security management method may be used in a terminal, and includes the above-mentioned steps 101 to 103.
In addition, in the account security management method, before step 101, the method may further include:
And 204, under the condition that the account to be set passes the verification, saving the account to be set as a safety management account.
In the account security management method, different applications may support different security management items. For example, some applications support modifying passwords, some applications support freezing accounts, and some applications support unfreezing accounts. The associated app may provide a security management interface for modifying passwords, freezing and unfreezing accounts, and the like. The user can enter other authentication information except the password in advance through the interfaces to form a security management account corresponding to each application. If the information is leaked or cheated, the password can be input in sequence to be encrypted or frozen quickly, so that the operation time is effectively shortened, and great loss is reduced for users. The database may be used to store authentication information other than the password of each account as the security management account.
For example, apps that support online payments, such as payroll, hundredth wallet, wechat wallet, qq wallet, palmtop bank, etc., may provide an interface for password modification, an interface for quick frozen accounts, and an interface for quick unfreezing (an example of a security management interface). This is then achieved by means of a tool supporting a registration and login interface, for example security management software installed on the terminal device. After the user logs in, the displayed function modules, such as the function modules of password changing, account freezing, account unfreezing and the like, can be seen.
Taking the frozen account as an example, the process of uniformly adding the security management account is as follows:
if the user selects to freeze an account, a frozen account interface (an example of a security management interface) may be entered. The user clicks the "+" sign (or other button indicating addition of a secure management account) on the frozen account interface and the app frozen account interface supporting the frozen account may pop up. The user inputs information such as a user name, a password and the like from the frozen account interface. If the verification is successful after the input, the password can be cleared, and other authentication information such as account numbers and the like can be reserved in the database. If a plurality of apps support the account freezing function on the terminal, the user can pop up a selectable app list, and the user selects one app at a time to add one or more corresponding security management accounts. After the security management account of a certain app is added, the next app can be sequentially added according to the list or an optional app list can be returned, and after the user selects another app, the security management account corresponding to the app is continuously added. If the user continues to select other apps with the point "+" sign, the app that was previously added to the security management account may not be included in the list of optional apps that is popped up at this time. In addition, corresponding security management accounts can be sequentially added to all apps in the optional app list until all apps supporting use are added, and the adding process is finished. Or, according to the selection of the user, after adding the corresponding security management account to part of the apps in the selectable app list, ending the adding process.
In a possible implementation manner, if a function of uniformly modifying the key is required to be implemented, in the account security management method, step 102 may include: and calling out a modified key interface corresponding to the target account from the application corresponding to the target account. Step 103 may include: and under the condition that a key to be verified and a key to be modified of a user are obtained from the password modification interface, sending the target account, the key to be verified and the key to be modified to an application corresponding to the target account.
In one possible implementation manner, if the function of uniformly freezing the accounts needs to be implemented, in the account security management method, step 102 may include: and calling out a frozen account interface corresponding to the target account from the application corresponding to the target account. Step 103 may include: and under the condition that a key to be verified of a user is obtained from the frozen account interface, sending the target account and the key to be verified to an application corresponding to the target account. In addition, in addition to sending the target account and the key to be authenticated to the application corresponding to the target account, an indication of whether the application corresponding to the target account agrees to freeze the account may also be sent to the application corresponding to the target account. The indication may be sent with the target account and the key to be authenticated, or may be sent separately.
In a possible implementation manner, if the function of uniformly unfreezing the account is required to be implemented, in the account security management method, step 102 may include: and calling a unfreezing account interface corresponding to the target account from the application corresponding to the target account. Step 103 may include: and under the condition that a key to be verified of a user is obtained from the unfreezing account interface, sending the target account and the key to be verified to an application corresponding to the target account. In addition, in addition to sending the target account and the key to be authenticated to the application corresponding to the target account, an indication of whether the application corresponding to the target account agrees to unfreeze the account may be sent to the application corresponding to the target account. The indication may be sent with the target account and the key to be authenticated, or may be sent separately.
In one possible implementation manner, after step 103, the account security management method further includes:
and 104, after the security management of the target account is completed, acquiring a next account of the target account selected from preset security management accounts as the target account. And then, for the currently selected target account, repeating the steps 101 to 103 until the security management of all the security management accounts is completed.
Taking the frozen account as an example, the process of uniformly performing security management is as follows:
when the quick freeze account function is required to be used. The registered user logs in the tool and selects the frozen account submodule. The facility may read all of the frozen information for the registered user from the database (e.g., including the security management accounts that can support the frozen function). If the freezing is performed in sequence according to the arrangement sequence of the security management accounts, a frozen account interface of the app corresponding to the first security management account to be frozen can appear first. A password (i.e., an example of a key to be authenticated) is filled from the app's frozen account interface, and if the password is correct, it can be immediately frozen. And popping up a frozen account interface of the app corresponding to the next security management account after the first security management account is successfully frozen. If the password is forgotten, the password can be retrieved, an app frozen account interface corresponding to the current security management account can be skipped, and a frozen account interface of the app corresponding to the next security management account is popped up. Of course, it is also possible to not sequentially freeze the security management accounts according to the arrangement order of the security management accounts, but return to the interface of the selectable security management accounts after each security management account is frozen, and the user himself selects which account needs to be frozen.
For the functions of encrypting and unfreezing accounts, the processes of uniformly adding security management accounts and uniformly performing security management are similar to those of the frozen accounts, and are not described again here. It should be noted that the security management interface called out when the secret is changed is a modified secret key interface, and the security management interface called out when the account is thawed is an thawing account interface. When the key modification interface, the account freezing interface and the account unfreezing interface are called out, various information can be interacted with the application through one interface at one time, and various information can be interacted with the application through a plurality of interfaces for a plurality of times. For example, when the password needs to be modified, an interface of "please input the original password" may be called first, and then interfaces of "please input the new password" and "please input the password again" may be called, so that the account number, the original password, and the new password are sent to the client of the application through interaction with the client of the application through a plurality of interfaces. The interface also comprises a plurality of input boxes, and the contents of 'original password', 'new password' and the like can be input in the interface. For another example, when the account needs to be frozen, the interface of "please input the password" may be called first, and then the interface of "whether to freeze the account" may be called. An interface may also be called up that includes an input box "please enter password" and a "freeze account" button.
According to the embodiment, the security management interfaces are provided through the applications, so that the security management of all the security management accounts can be uniformly performed, the speed of performing the security management on a plurality of accounts can be increased, the operation time is shortened, and the user loss is reduced.
For example, the present disclosure may associate all online banking-related apps into one tool, and fill in the tool with authentication information of the apps in advance, except for passwords. When the user is cheated, the user opens the tool and fills the passwords in sequence to quickly change the password or freeze the account, so that a lot of loss is reduced for the user in time.
FIG. 3 is a block diagram illustrating an account security management apparatus in accordance with an exemplary embodiment. Referring to fig. 3, the apparatus may include a first obtaining module 31, a first calling-out module 33, and a first transmitting module 35.
A first obtaining module 31, configured to obtain a target account selected from preset security management accounts, where the security management account is an account included in each application that needs to be security managed;
a first call-out module 33, configured to call out a security management interface corresponding to the target account from an application corresponding to the target account;
the first sending module 35 is configured to, when authentication information of a user is acquired from the security management interface, send the target account and the authentication information to an application corresponding to the target account, where the target account and the authentication information are used for requesting, by the application corresponding to the target account, a corresponding server to perform security management on the target account.
According to the embodiment, the security management interfaces are provided through the applications, so that the security management of all the security management accounts can be uniformly performed, the speed of performing the security management on a plurality of accounts can be increased, the operation time is shortened, and the user loss is reduced.
Fig. 4 is a block diagram illustrating an account security management apparatus according to another exemplary embodiment. Referring to fig. 4, the apparatus may include a first obtaining module 31, a first calling-out module 33 and a first transmitting module 35 similar to fig. 3.
In a possible implementation manner, the first callout module 33 may include a first callout submodule 331, and the first sending module 35 may include a first sending submodule 351. The first calling sub-module 331 is configured to call out a modified key interface corresponding to the target account from an application corresponding to the target account. The first sending sub-module 351 is configured to send the target account, the key to be verified, and the key to be modified to the application corresponding to the target account when the key to be verified and the key to be modified of the user are obtained from the password modification interface. Through the first calling out submodule and the first sending submodule, the function of uniformly modifying the key for a plurality of safety management accounts can be realized.
In a possible implementation manner, the first callout module 33 may further include a second callout submodule 333, and the first sending module 35 may further include a second sending submodule 353. The second calling sub-module 333 is configured to call out the frozen account interface corresponding to the target account from the application corresponding to the target account. The second sending submodule 353 is configured to send the target account and the key to be verified to the application corresponding to the target account under the condition that the key to be verified of the user is obtained from the frozen account interface. Through the second calling-out submodule and the second sending submodule, the function of uniformly freezing accounts can be realized for a plurality of safety management accounts.
In a possible implementation manner, the first callout module 33 may further include a third callout submodule 335, and the first sending module 35 may further include a third sending submodule 355. The third calling sub-module 335 is configured to call out a unfreezing account interface corresponding to the target account from the application corresponding to the target account. The third sending submodule 355 is configured to send the target account and the key to be verified to the application corresponding to the target account when the key to be verified of the user is obtained from the unfreezing account interface. Through the third calling out submodule and the third sending submodule, the function of uniformly unfreezing accounts can be realized for a plurality of safety management accounts.
In a possible implementation, the apparatus may further include a second obtaining module 37. And the second selection module is used for acquiring the next account of the target account selected from preset safety management accounts as the target account after the safety management of the target account is completed.
In one possible implementation, the apparatus may further include:
a third obtaining module 38, configured to obtain a target application selected from applications that need to be subjected to security management;
a second call-out module 39, configured to call out a security management interface from the target application;
a second sending module 40, configured to send an account to be set and verification information corresponding to the account to be set to the target application when a security management interface of the target application obtains the account to be set and the verification information corresponding to the account, where the account to be set and the verification information corresponding to the account to be set are used for the target application to request a server corresponding to the account to be set to perform key verification;
a saving module 41, configured to save the account to be set as a security management account when the account to be set passes verification.
With regard to the apparatus in the above-described embodiment, the specific manner in which each module performs the operation has been described in detail in the embodiment related to the method, and will not be elaborated here.
According to the embodiment, the security management interfaces are provided through the applications, so that the security management of all the security management accounts can be uniformly performed, the speed of performing the security management on a plurality of accounts can be increased, the operation time is shortened, and the user loss is reduced.
Fig. 5 is a block diagram illustrating an account security management apparatus 800 according to another exemplary embodiment. For example, the apparatus 800 may be a mobile phone, a computer, a digital broadcast terminal, a messaging device, a game console, a tablet device, a medical device, an exercise device, a personal digital assistant, and the like.
Referring to fig. 5, the apparatus 800 may include one or more of the following components: processing component 802, memory 804, power component 806, multimedia component 808, audio component 810, input/output (I/O) interface 812, sensor component 814, and communication component 816.
The processing component 802 generally controls overall operation of the device 800, such as operations associated with display, telephone calls, data communications, camera operations, and recording operations. The processing components 802 may include one or more processors 820 to execute instructions to perform all or a portion of the steps of the methods described above. Further, the processing component 802 can include one or more modules that facilitate interaction between the processing component 802 and other components. For example, the processing component 802 can include a multimedia module to facilitate interaction between the multimedia component 808 and the processing component 802.
The memory 804 is configured to store various types of data to support operations at the apparatus 800. Examples of such data include instructions for any application or method operating on device 800, contact data, phonebook data, messages, pictures, videos, and so forth. The memory 804 may be implemented by any type or combination of volatile or non-volatile memory devices such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disks.
The multimedia component 808 includes a screen that provides an output interface between the device 800 and a user. In some embodiments, the screen may include a Liquid Crystal Display (LCD) and a Touch Panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive an input signal from a user. The touch panel includes one or more touch sensors to sense touch, slide, and gestures on the touch panel. The touch sensor may not only sense the boundary of a touch or slide action, but also detect the duration and pressure associated with the touch or slide operation. In some embodiments, the multimedia component 808 includes a front facing camera and/or a rear facing camera. The front camera and/or the rear camera may receive external multimedia data when the device 800 is in an operating mode, such as a shooting mode or a video mode. Each front camera and rear camera may be a fixed optical lens system or have a focal length and optical zoom capability.
The audio component 810 is configured to output and/or input audio signals. For example, the audio component 810 includes a Microphone (MIC) configured to receive external audio signals when the apparatus 800 is in an operational mode, such as a call mode, a recording mode, and a voice recognition mode. The received audio signals may further be stored in the memory 804 or transmitted via the communication component 816. In some embodiments, audio component 810 also includes a speaker for outputting audio signals.
The I/O interface 812 provides an interface between the processing component 802 and peripheral interface modules, which may be keyboards, click wheels, buttons, etc. These buttons may include, but are not limited to: a home button, a volume button, a start button, and a lock button.
The sensor assembly 814 includes one or more sensors for providing various aspects of state assessment for the device 800. For example, the sensor assembly 814 may detect the open/closed status of the device 800, the relative positioning of components, such as a display and keypad of the device 800, the sensor assembly 814 may also detect a change in the position of the device 800 or a component of the device 800, the presence or absence of user contact with the device 800, the orientation or acceleration/deceleration of the device 800, and a change in the temperature of the device 800. Sensor assembly 814 may include a proximity sensor configured to detect the presence of a nearby object without any physical contact. The sensor assembly 814 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, the sensor assembly 814 may also include an acceleration sensor, a gyroscope sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.
The communication component 816 is configured to facilitate communications between the apparatus 800 and other devices in a wired or wireless manner. The device 800 may access a wireless network based on a communication standard, such as WiFi, 2G or 3G, or a combination thereof. In an exemplary embodiment, the communication component 816 receives a broadcast signal or broadcast related information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communication component 816 further includes a Near Field Communication (NFC) module to facilitate short-range communications. For example, the NFC module may be implemented based on Radio Frequency Identification (RFID) technology, infrared data association (IrDA) technology, Ultra Wideband (UWB) technology, Bluetooth (BT) technology, and other technologies.
In an exemplary embodiment, the apparatus 800 may be implemented by one or more Application Specific Integrated Circuits (ASICs), Digital Signal Processors (DSPs), Digital Signal Processing Devices (DSPDs), Programmable Logic Devices (PLDs), Field Programmable Gate Arrays (FPGAs), controllers, micro-controllers, microprocessors or other electronic components for performing the above-described account security management methods.
In an exemplary embodiment, a non-transitory computer-readable storage medium comprising instructions, such as the memory 804 comprising instructions, executable by the processor 820 of the device 800 to perform the account security management method described above is also provided. For example, the non-transitory computer readable storage medium may be a ROM, a Random Access Memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, and the like.
Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This application is intended to cover any variations, uses, or adaptations of the disclosure following, in general, the principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.
It will be understood that the present disclosure is not limited to the precise arrangements described above and shown in the drawings and that various modifications and changes may be made without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.
Claims (13)
1. An account security management method, comprising:
acquiring a target account selected from preset security management accounts, wherein the security management accounts are accounts included in applications needing security management;
calling out a security management interface corresponding to the target account from the application corresponding to the target account;
and under the condition that the authentication information of the user is acquired from the security management interface, sending the target account and the authentication information to the application corresponding to the target account, wherein the target account and the authentication information are used for requesting the corresponding server for security management of the target account by the application corresponding to the target account.
2. The method of claim 1,
calling out a security management interface corresponding to the target account from the application corresponding to the target account, wherein the security management interface comprises: calling out a key modification interface corresponding to the target account from the application corresponding to the target account;
under the condition that the authentication information of the user is acquired from the security management interface, the step of sending the target account and the authentication information to the application corresponding to the target account comprises the following steps: and under the condition that a key to be verified and a key to be modified of a user are obtained from the key modification interface, sending the target account, the key to be verified and the key to be modified to an application corresponding to the target account.
3. The method of claim 1,
calling out a security management interface corresponding to the target account from the application corresponding to the target account, and further comprising: calling out a frozen account interface corresponding to the target account from the application corresponding to the target account;
under the condition that the authentication information of the user is acquired from the security management interface, the target account and the authentication information are sent to the application corresponding to the target account, and the method further comprises the following steps: and under the condition that a key to be verified of a user is obtained from the frozen account interface, sending the target account and the key to be verified to an application corresponding to the target account.
4. The method of claim 1,
calling out a security management interface corresponding to the target account from the application corresponding to the target account, and further comprising: calling a unfreezing account interface corresponding to the target account from the application corresponding to the target account;
under the condition that the authentication information of the user is acquired from the security management interface, the target account and the authentication information are sent to the application corresponding to the target account, and the method further comprises the following steps: and under the condition that a key to be verified of a user is obtained from the unfreezing account interface, sending the target account and the key to be verified to an application corresponding to the target account.
5. The method of any one of claims 1 to 4, further comprising:
and after the security management of the target account is completed, acquiring the next account of the target account selected from preset security management accounts as the target account.
6. The method of any of claims 1 to 4, further comprising:
acquiring a target application selected from each application needing security management;
calling out a security management interface from the target application;
under the condition that an account to be set of a user and corresponding verification information thereof are obtained from a security management interface of the target application, the account to be set and the corresponding verification information thereof are sent to the target application, and the account to be set and the corresponding verification information thereof are used for requesting a server corresponding to the target application to perform key verification on the account to be set;
and under the condition that the account to be set passes the verification, saving the account to be set as a safety management account.
7. An account security management apparatus, comprising:
the system comprises a first acquisition module, a second acquisition module and a third acquisition module, wherein the first acquisition module is used for acquiring a target account selected from preset security management accounts, and the security management accounts are accounts included in applications needing security management;
the first calling module is used for calling out a security management interface corresponding to the target account from the application corresponding to the target account;
the first sending module is used for sending the target account and the verification information to an application corresponding to the target account under the condition that the verification information of a user is obtained from the security management interface, wherein the target account and the verification information are used for requesting the corresponding server to perform security management on the target account by the application corresponding to the target account.
8. The apparatus of claim 7,
the first callout module includes: the first calling-out submodule is used for calling out a modified key interface corresponding to the target account from the application corresponding to the target account;
the first transmitting module includes: and the first sending submodule is used for sending the target account, the key to be verified and the key to be modified to the application corresponding to the target account under the condition of acquiring the key to be verified and the key to be modified of the user from the key modification interface.
9. The apparatus of claim 7,
the first callout module further comprises: the second calling sub-module is used for calling out a frozen account interface corresponding to the target account from the application corresponding to the target account;
the first transmitting module further comprises: and the second sending submodule is used for sending the target account and the key to be verified to the application corresponding to the target account under the condition that the key to be verified of the user is obtained from the frozen account interface.
10. The apparatus of claim 7,
the first callout module further comprises: a third calling sub-module, configured to call out a unfreezing account interface corresponding to the target account from the application corresponding to the target account;
the first transmitting module further comprises: and the third sending submodule is used for sending the target account and the key to be verified to the application corresponding to the target account under the condition that the key to be verified of the user is obtained from the unfreezing account interface.
11. The apparatus of any one of claims 7 to 10, further comprising:
and the second acquisition module is used for acquiring the next account of the target account selected from preset safety management accounts as the target account after the safety management of the target account is completed.
12. The apparatus of any one of claims 7 to 10, further comprising:
the third acquisition module is used for acquiring a target application selected from various applications needing security management;
the second calling module is used for calling out a security management interface from the target application;
the second sending module is used for sending the account to be set and the corresponding verification information thereof to the target application under the condition that the account to be set and the corresponding verification information thereof of the user are obtained from the security management interface of the target application, wherein the account to be set and the corresponding verification information thereof are used for requesting the server to carry out key verification on the account to be set by the target application;
and the storage module is used for storing the account to be set as a safety management account under the condition that the verification of the account to be set passes.
13. An account security management apparatus, comprising:
a processor;
a memory for storing processor-executable instructions;
wherein the processor is configured to:
acquiring a target account selected from preset security management accounts, wherein the security management accounts are accounts included in applications needing security management;
calling out a security management interface corresponding to the target account from the application corresponding to the target account;
and under the condition that the authentication information of the user is acquired from the security management interface, sending the target account and the authentication information to the application corresponding to the target account, wherein the target account and the authentication information are used for requesting the corresponding server for security management of the target account by the application corresponding to the target account.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610857709.2A CN106408304B (en) | 2016-09-27 | 2016-09-27 | Account security management method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610857709.2A CN106408304B (en) | 2016-09-27 | 2016-09-27 | Account security management method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN106408304A CN106408304A (en) | 2017-02-15 |
| CN106408304B true CN106408304B (en) | 2020-02-07 |
Family
ID=57997680
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610857709.2A Active CN106408304B (en) | 2016-09-27 | 2016-09-27 | Account security management method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN106408304B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107943382B (en) * | 2017-10-27 | 2020-06-05 | 贝壳找房(北京)科技有限公司 | One-key entry method for house source information |
| CN111090853B (en) * | 2019-12-27 | 2023-04-07 | 咪咕文化科技有限公司 | Account management method, system, electronic equipment and storage medium |
Family Cites Families (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8005732B2 (en) * | 2003-12-31 | 2011-08-23 | American Express Travel Related Services Company, Inc. | System for reducing information required to open a new account |
| CN101262347A (en) * | 2008-01-22 | 2008-09-10 | 好旺角（厦门）电子科技有限公司 | Anti-theft method for network account |
| CN103023875B (en) * | 2012-11-21 | 2015-09-02 | 北京荣之联科技股份有限公司 | A kind of account management system and method |
| CN104486417B (en) * | 2014-12-16 | 2018-05-25 | 上海斐讯数据通信技术有限公司 | Account safety management system and method based on cloud service |
| CN105282162B (en) * | 2015-10-30 | 2019-03-08 | 小米科技有限责任公司 | The processing method and processing device of account management business |
| CN105491048A (en) * | 2015-12-10 | 2016-04-13 | 小米科技有限责任公司 | Account management method and apparatus |
-
2016
- 2016-09-27 CN CN201610857709.2A patent/CN106408304B/en active Active
Also Published As
| Publication number | Publication date |
|---|---|
| CN106408304A (en) | 2017-02-15 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106709399B (en) | Fingerprint identification method and device | |
| CN106453052B (en) | Message interaction method and device | |
| CN106170004B (en) | Method and device for processing verification code | |
| CN105847243B (en) | Method and device for accessing intelligent camera | |
| US10313870B2 (en) | Identity verification method and apparatus, and storage medium | |
| CN105656948A (en) | Account login method and device | |
| CN107230060B (en) | Account loss reporting method and device | |
| CN109039990B (en) | Behavior verification method and device based on verification code | |
| CN109039860B (en) | Method and device for sending and displaying message and method and device for identity authentication | |
| CN106210238B (en) | Short message storage method and device | |
| CN106204046A (en) | The method and device that order pays | |
| RU2636686C2 (en) | Method and device for sending information in voice service | |
| CN110049062B (en) | Verification code verification method, device, system, server, electronic equipment and storage medium | |
| CN111368232A (en) | Password sharing reflux method and device, electronic equipment and storage medium | |
| US9667784B2 (en) | Methods and devices for providing information in voice service | |
| CN106529277A (en) | Message preview method and device | |
| CN107145771B (en) | Application program unlocking method and device and terminal | |
| CN105681261A (en) | Security authentication method and apparatus | |
| CN109246094B (en) | User terminal verification method, device and storage medium | |
| CN111917728A (en) | Password verification method and device | |
| CN105303120B (en) | Short message reading method and device | |
| CN106372943A (en) | Message processing method and device | |
| CN106611112A (en) | Application program safe processing method, device and equipment | |
| CN106651379A (en) | Payment method and device | |
| CN106408304B (en) | Account security management method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |