CN105245517A - Application locking method, device and system - Google Patents
Application locking method, device and system Download PDFInfo
- Publication number
- CN105245517A CN105245517A CN201510642859.7A CN201510642859A CN105245517A CN 105245517 A CN105245517 A CN 105245517A CN 201510642859 A CN201510642859 A CN 201510642859A CN 105245517 A CN105245517 A CN 105245517A
- Authority
- CN
- China
- Prior art keywords
- promise
- breaking
- user account
- terminal
- application
- 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.)
- Granted
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/10—Network architectures or network communication protocols for network security for controlling access to devices or network resources
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services
Abstract
The invention discloses an application locking method, device and system, and belongs to the field of electronic technology applications. The method comprises the following steps: receiving a dishonesty blacklist sent by an application server, wherein user account numbers having preset dishonesty behaviors are recorded in the dishonesty blacklist; when a new user account number is added in the dishonesty blacklist, determining a target terminal identifier corresponding to the new user account number; and sending a locking instruction to a terminal corresponding to the target terminal identifier, wherein the locking instruction is used for indicating to lock applications in the terminal. A cloud server in the application locking method disclosed by the invention receives the dishonesty blacklist sent by the application server, and sends the locking instruction to the terminal corresponding to the user account number recorded in the dishonesty blacklist, so that the triggering mechanism of locking the applications in the terminal is enriched, and the dishonest behavior of a user is appropriately punished to reduce the dishonesty rate of the user. The application locking method, device and system disclosed by the invention are used for locking applications.
Description
Technical field
The disclosure relates to application of electronic technology field, the locking means of particularly a kind of application, Apparatus and system.
Background technology
Cloud Server is a kind of simply efficient, safe and reliable calculation server, user by terminal in Cloud Server after registered user's account, this user account and terminal can be bound by Cloud Server, afterwards, the data upload such as associated person information, message registration, photo can back up in Cloud Server by terminal.
In correlation technique, when the lost terminal of user, user can send lock instruction, after terminal receives this lock instruction by Cloud Server to the terminal of binding with this user account, the application of installing in terminal can be locked, to avoid the leakage of users personal data.
Summary of the invention
In order to solve the problem in correlation technique, present disclose provides a kind of locking means of application, Apparatus and system.Described technical scheme is as follows:
According to the first aspect of disclosure embodiment, provide a kind of locking means of application, the method comprises:
Receive the blacklist of breaking one's promise that application server sends, in this blacklist of breaking one's promise, record the user account that default discreditable behavior occurs;
When there being newly-increased user account during this breaks one's promise blacklist, determine the target terminal mark that this newly-increased user account is corresponding;
The terminal corresponding to this target terminal mark sends lock instruction, and this lock instruction is used to indicate and locks the application in terminal.
Optionally, the method also comprises:
Receive the white list of breaking one's promise that application server sends, in this white list of breaking one's promise, record the user account occurring to preset releasing behavior of breaking one's promise;
Determine the unlock terminal mark that user account that this is broken one's promise in white list is corresponding;
The terminal corresponding to this unlock terminal mark sends unlock command, and this unlock command is used to indicate and unlocks to the application in terminal.
Optionally, this sends lock instruction to the terminal that this target terminal mark is corresponding, comprising:
Obtain the target application mark that this application server is corresponding;
Generate this lock instruction, this lock instruction comprises this target application mark;
The terminal corresponding to this target terminal mark sends this lock instruction, and this lock instruction is used to indicate and locks other application in terminal except the application of this target application mark correspondence.
Optionally, what this target application mark was corresponding is applied as financial application, these other be applied as other financial application;
Or, these other be applied as all application except the application corresponding except this target application mark of installing in terminal.
Optionally, the method also comprises:
Contrast this blacklist of breaking one's promise whether identical with the user account recorded in the blacklist of breaking one's promise prestored;
When this blacklist of breaking one's promise is not identical with the user account recorded in this blacklist of breaking one's promise prestored, detects this user account of breaking one's promise in blacklist and whether there is Unrecorded user account in this blacklist of breaking one's promise prestored;
If this user account of breaking one's promise in blacklist exists Unrecorded user account in this blacklist of breaking one's promise prestored, this Unrecorded user account is defined as the user account that this is newly-increased.
Optionally, the method also comprises:
Identify corresponding terminal to this target terminal and send mark of breaking one's promise, the terminal of this target terminal mark correspondence writes to the predeterminated position in operating system for mark of this being broken one's promise, and this mark of breaking one's promise performs the predetermined registration operation to operating system for forbidding.
Optionally, the method also comprises:
The terminal corresponding to this unlock terminal mark sends mark erasing instruction of breaking one's promise, and identifies corresponding terminal will be arranged in the mark erasing of breaking one's promise of operating system predeterminated position according to this mark erasing instruction of breaking one's promise to make this unlock terminal.
Optionally, the method also comprises:
Detect in the user account of breaking one's promise in blacklist prestored and whether there is the user account recorded in this white list of breaking one's promise;
If there is the user account recorded in this white list of breaking one's promise in the user account that what this prestored break one's promise in blacklist, the user account recorded in white list of this being broken one's promise is deleted from this breaks one's promise blacklist.
According to the second aspect of disclosure embodiment, provide a kind of locking means of application, described method comprises:
Whether the user account registered in monitoring and measuring application server there is default discreditable behavior;
When this default discreditable behavior occurs this user account, this user account is recorded to and breaks one's promise in blacklist;
This blacklist of breaking one's promise is sent to Cloud Server.
Optionally, the method also comprises:
Monitor the user account recorded in this blacklist of breaking one's promise whether to occur to preset releasing behavior of breaking one's promise;
The user account recorded in this breaks one's promise blacklist occur this preset break one's promise releasing behavior time, this user account is recorded to and breaks one's promise in white list;
This white list of breaking one's promise is sent to this Cloud Server.
Optionally, whether the user account registered in monitoring and measuring application server there is default discreditable behavior, comprising:
Obtain the credit record of this user account, in this credit record, record loaning bill information and the refund information of this user account;
Detect in this credit record the loaning bill information whether existing and do not refund;
When there is the loaning bill information of not refunding in this credit record, judge that the date of formation of this loaning bill information of not refunding is whether in predetermined period;
When the date of formation of the loaning bill information that this is not refunded is in predetermined period, determine that default discreditable behavior does not occur this user account; Or,
When the date of formation of the loaning bill information that this is not refunded is not in predetermined period, determine that this user account occurs to preset discreditable behavior.
Optionally, whether the user account recorded in this blacklist of breaking one's promise of this monitoring occurs to preset releasing behavior of breaking one's promise, and comprising:
When monitoring arbitrary user account generation refund behavior of registering in this application server, judge whether the user account of this generation refund behavior is recorded in this and breaks one's promise in blacklist;
When the user account of this generation refund behavior is recorded in this blacklist of breaking one's promise, obtain the credit record of the user account of this generation refund behavior, in this credit record, record loaning bill information and the refund information of this user account;
Judge whether the refund amount of money recorded in this refund information is less than predetermined threshold value;
When this refund amount of money is less than this predetermined threshold value, determine that this user account does not occur to preset releasing behavior of breaking one's promise; Or,
When this refund amount of money is not less than this predetermined threshold value, determine that this user account occurs to preset releasing behavior of breaking one's promise.
Optionally, whether the user account registered in this monitoring and measuring application server there is default discreditable behavior, comprising:
The discreditable behavior reporting information that the terminal that the user account receiving this registration logs in sends, this terminal is when continuous n false release action being detected, display authorization information input frame, this discreditable behavior reporting information is that this terminal detects that the authorization information of the user's input received at this authorization information input frame sends time different from the authorization information preset, and this n is for presetting integer value;
According to this discreditable behavior reporting information, determine that this user account occurs to preset discreditable behavior.
Optionally, whether the user account recorded in this blacklist of breaking one's promise of this monitoring occurs to preset releasing behavior of breaking one's promise, and comprising:
Releasing behavior of the breaking one's promise reporting information that the terminal that the user account receiving this registration logs in sends, this terminal is when receiving unblock triggering command, display authorization information input frame, this releasing behavior reporting information of breaking one's promise is that this terminal detects that the authorization information of the user's input received in this authorization information input frame sends time identical with the authorization information preset;
According to this releasing behavior reporting information of breaking one's promise, determine that this user account occurs to preset releasing behavior of breaking one's promise.
According to the third aspect of disclosure embodiment, provide a kind of locking means of application, the method comprises:
Receive the lock instruction that Cloud Server sends, to be this Cloud Server have during newly-increased user account this lock instruction in the blacklist of breaking one's promise that the application server received sends sends, this lock instruction is used to indicate and locks the application in terminal, records the user account that default discreditable behavior occurs in this blacklist of breaking one's promise;
According to this lock instruction, the application in terminal is locked.
Optionally, the method also comprises:
Receive the unlock command that Cloud Server sends, this unlock command be this Cloud Server receive that application server sends break one's promise white list time send, this unlock command is used to indicate and unlocks to the application in terminal, records the user account occurring to preset releasing behavior of breaking one's promise in this white list of breaking one's promise;
According to this unlock command, the application in this terminal is unlocked.
Optionally, this lock instruction also comprises target application mark, and this locks the application in terminal according to this lock instruction, comprising:
According to this lock instruction, other application in terminal except the application of this target application mark correspondence are locked.
Optionally, what this target application mark was corresponding is applied as financial application, these other be applied as other financial application;
Or, these other be applied as all application except the application corresponding except this target application mark of installing in terminal.
Optionally, the method also comprises:
Receive the mark of breaking one's promise that Cloud Server sends, this mark of breaking one's promise performs the predetermined registration operation to operating system for forbidding;
Mark of this being broken one's promise writes to the predeterminated position in the operating system of this terminal.
Optionally, the method also comprises:
Receive the mark erasing instruction of breaking one's promise that Cloud Server sends;
Detect predeterminated position in this operating system and whether there is mark of breaking one's promise;
When this predeterminated position exists this mark of breaking one's promise, according to this mark erasing instruction of breaking one's promise, the mark erasing of breaking one's promise of operating system predeterminated position will be arranged in.
Optionally, the method also comprises:
When continuous n false release action being detected, display authorization information input frame, this n is for presetting integer value;
The authorization information of user's input is received in this authorization information input frame;
Whether the authorization information detecting this user input is identical with the authorization information preset;
When the authorization information that this user inputs is identical with the authorization information that this is preset, send discreditable behavior reporting information to application server.
Optionally, the method also comprises:
When receiving unblock triggering command, display authorization information input frame;
The authorization information of user's input is received in this authorization information input frame;
Whether the authorization information detecting this user input is identical with the authorization information preset;
When the authorization information that this user inputs is identical with the authorization information that this is preset, send to application server releasing behavior reporting information of breaking one's promise.
According to the fourth aspect of disclosure embodiment, provide a kind of locking device of application, this device comprises:
First receiver module, is configured to the blacklist of breaking one's promise receiving application server transmission, records the user account that default discreditable behavior occurs in this blacklist of breaking one's promise;
First determination module, is configured to when there being newly-increased user account in this blacklist of breaking one's promise that this first receiver module receives, and determines the target terminal mark that this newly-increased user account is corresponding;
First sending module, the terminal transmission lock instruction that this target terminal mark being configured to determine to this first determination module is corresponding, this lock instruction is used to indicate and locks the application in terminal.
Optionally, this device also comprises:
Second receiver module, is configured to the white list of breaking one's promise receiving application server transmission, records the user account occurring to preset releasing behavior of breaking one's promise in this white list of breaking one's promise;
Second determination module, is configured to determine the unlock terminal mark that this user account of breaking one's promise in white list that this second receiver module receives is corresponding;
Second sending module, the terminal transmission unlock command that this unlock terminal mark being configured to determine to this second determination module is corresponding, this unlock command is used to indicate and unlocks to the application in terminal.
Optionally, this first sending module, comprising: obtain submodule, generate submodule and send submodule;
This acquisition submodule, is configured to obtain target application mark corresponding to this application server;
This generation submodule, is configured to generate this lock instruction, and this lock instruction comprises this target application mark that this acquisition submodule obtains;
This transmission submodule, is configured to this lock instruction sending the generation of this generation submodule to the terminal that this target terminal mark is corresponding, and this lock instruction is used to indicate and locks other application in terminal except the application of this target application mark correspondence.
Optionally, what this target application mark that this acquisition submodule obtains was corresponding is applied as financial application, these other be applied as other financial application;
Or, these other be applied as all application except the application corresponding except this target application mark of installing in terminal.
Optionally, this device also comprises: contrast module, first detection module and the 3rd determination module;
This contrast module, whether this blacklist of breaking one's promise being configured to contrast the reception of this first receiver module is identical with the user account recorded in the blacklist of breaking one's promise prestored;
This first detection module, be configured to this contrast module contrast this blacklist of breaking one's promise not identical with the user account recorded in this blacklist of breaking one's promise prestored time, detect this user account of breaking one's promise in blacklist and whether there is Unrecorded user account in this blacklist of breaking one's promise prestored;
3rd determination module, is configured to detect that this user account of breaking one's promise in blacklist exists Unrecorded user account in this blacklist of breaking one's promise prestored when this first detection module, this Unrecorded user account is defined as the user account that this is newly-increased.
Optionally, this device also comprises: the 3rd sending module;
3rd sending module, the terminal being configured to this target terminal mark correspondence determined to this first determination module sends mark of breaking one's promise, the terminal of this target terminal mark correspondence writes to the predeterminated position in operating system for mark of this being broken one's promise, this mark of breaking one's promise performs the predetermined registration operation to operating system for forbidding.
Optionally, this device also comprises: the 4th sending module;
4th sending module, the terminal being configured to this unlock terminal mark correspondence determined to this second determination module sends mark erasing instruction of breaking one's promise, and will be arranged in breaking one's promise of operating system predeterminated position indicate erasing with the terminal making this unlock terminal identify correspondence according to this mark erasing instruction of breaking one's promise.
Optionally, this device also comprises:
Second detection module, is configured to detect in this user account of breaking one's promise in blacklist prestored the user account whether existing and record in this white list of breaking one's promise of this second receiver module reception;
Removing module, there is the user account recorded in this white list of breaking one's promise if be configured in this user account of breaking one's promise in blacklist prestored of this second detection module detection, the user account recorded in white list of this being broken one's promise is deleted from this breaks one's promise blacklist.
According to the 5th aspect of disclosure embodiment, provide a kind of locking device of application, this device comprises:
First monitoring modular, whether the user account being configured to register in monitoring and measuring application server there is default discreditable behavior;
First logging modle, is configured to, when this default discreditable behavior occurs this user account of this first monitoring module monitors, be recorded to by this user account and break one's promise in blacklist;
First sending module, is configured to this blacklist of breaking one's promise sending this first logging modle record to Cloud Server.
Optionally, this device also comprises: the second monitoring modular, the second logging modle and the second sending module;
Whether this second monitoring modular, be configured to monitor the user account recorded in this blacklist of breaking one's promise and occur to preset releasing behavior of breaking one's promise;
This second logging modle, the user account being configured to record in this blacklist of breaking one's promise of this second monitoring module monitors occur this preset break one's promise releasing behavior time, this user account is recorded to and breaks one's promise in white list;
This second sending module, is configured to this white list of breaking one's promise sending this second logging modle record to this Cloud Server.
Optionally, this first monitoring modular, comprising: the first acquisition submodule, the first detection sub-module, first judge that submodule, first determines that submodule and second determines submodule;
This first acquisition submodule, is configured to the credit record obtaining this user account, records loaning bill information and the refund information of this user account in this credit record;
This first detection sub-module, is configured to detect this and first obtains in this credit record that submodule obtains whether there is the loaning bill information of not refunding;
This first judges submodule, be configured to when this first obtain there is the loaning bill information of not refunding in this credit record that submodule obtains time, judge that the date of formation of this loaning bill information of not refunding is whether in predetermined period;
This first determines submodule, be configured to when this first judge that submodule judges that the date of formation of this loaning bill information of not refunding is in predetermined period time, determine that default discreditable behavior does not occur this user account;
This second determines submodule, be configured to when this first judge that submodule judges that the date of formation of this loaning bill information of not refunding is not in predetermined period time, determine that this user account occurs to preset discreditable behavior.
Optionally, this second monitoring modular, comprising: second judges that submodule, second obtains submodule, the 3rd and judges that submodule, the 3rd determines that submodule and the 4th determines submodule;
This second judges submodule, being configured to when monitoring arbitrary user account generation refund behavior of registering in this application server, judging whether the user account of this generation refund behavior is recorded in this and breaks one's promise in blacklist;
This second acquisition submodule, be configured to when the user account of this generation refund behavior is recorded in this blacklist of breaking one's promise, obtain the credit record of the user account of this generation refund behavior, in this credit record, record loaning bill information and the refund information of this user account;
3rd judges submodule, and whether the refund amount of money being configured to record in this refund information judging that this second acquisition submodule obtains is less than predetermined threshold value;
3rd determines submodule, is configured to when the 3rd judges that submodule judges that this refund amount of money is less than this predetermined threshold value, determines that this user account does not occur to preset releasing behavior of breaking one's promise;
4th determines submodule, is configured to when the 3rd judges that submodule judges that this refund amount of money is not less than this predetermined threshold value, determines that this user account occurs to preset releasing behavior of breaking one's promise.
Optionally, this first monitoring modular, also comprises: first receives submodule and the 5th determines submodule;
This first reception submodule, the discreditable behavior reporting information that the terminal that the user account being configured to receive this registration logs in sends, this terminal is when continuous n false release action being detected, display authorization information input frame, this discreditable behavior reporting information is that this terminal detects that the authorization information of the user's input received at this authorization information input frame sends time different from the authorization information preset, and this n is for presetting integer value;
5th determines submodule, is configured to this discreditable behavior reporting information received according to this first reception submodule, determines that this user account occurs to preset discreditable behavior.
Optionally, this second monitoring modular, also comprises: second receives submodule and the 6th determines submodule;
This second reception submodule, releasing behavior of the breaking one's promise reporting information that the terminal that the user account being configured to receive this registration logs in sends, this terminal is when receiving unblock triggering command, display authorization information input frame, this releasing behavior reporting information of breaking one's promise is that this terminal detects that the authorization information of the user's input received in this authorization information input frame sends time identical with the authorization information preset;
6th determines submodule, is configured to this releasing behavior reporting information of breaking one's promise received according to this second reception submodule, determines that this user account occurs to preset releasing behavior of breaking one's promise.
According to the 6th aspect of disclosure embodiment, provide a kind of locking device of application, this device comprises:
First receiver module, be configured to the lock instruction receiving Cloud Server transmission, to be this Cloud Server have during newly-increased user account this lock instruction in the blacklist of breaking one's promise that the application server received sends sends, this lock instruction is used to indicate and locks the application in terminal, records the user account that default discreditable behavior occurs in this blacklist of breaking one's promise;
Locking module, is configured to this lock instruction received according to this first receiver module, locks the application in terminal.
Optionally, this device also comprises: the second receiver module and unlocked state;
This second receiver module, be configured to the unlock command receiving Cloud Server transmission, this unlock command be this Cloud Server receive that application server sends break one's promise white list time send, this unlock command is used to indicate and unlocks to the application in terminal, records the user account occurring to preset releasing behavior of breaking one's promise in this white list of breaking one's promise;
This unlocked state, is configured to this unlock command received according to this second receiver module, unlocks to the application in this terminal.
Optionally, the lock instruction that this first receiver module receives also comprises target application mark;
This locking module, comprising: locking submodule;
This locking submodule, is configured to according to this lock instruction, locks other application in terminal except the application of this target application mark correspondence.
Optionally, what this target application mark was corresponding is applied as financial application, these other be applied as other financial application;
Or, these other be applied as all application except the application corresponding except this target application mark of installing in terminal.
Optionally, this device also comprises: the 3rd receiver module and writing module;
3rd receiver module, is configured to the mark of breaking one's promise receiving Cloud Server transmission, and this mark of breaking one's promise performs the predetermined registration operation to operating system for forbidding;
This writing module, is configured to the predeterminated position write to by this mark of breaking one's promise that the 3rd receiver module receives in the operating system of this terminal.
Optionally, this device also comprises: the 4th receiver module, first detection module and erasing module;
4th receiver module, is configured to the mark erasing instruction of breaking one's promise receiving Cloud Server transmission;
This first detection module, is configured to detect predeterminated position in this operating system and whether there is mark of breaking one's promise;
This erasing module, is configured to detect that this predeterminated position exists this mark of breaking one's promise when this first detection module, according to the mark erasing instruction of breaking one's promise that the 4th receiver module receives, will be arranged in the mark erasing of breaking one's promise of operating system predeterminated position.
Optionally, this device also comprises: the first display module, the 5th receiver module, the second detection module and the first sending module;
This first display module, is configured to when continuous n false release action being detected, display authorization information input frame, and this n is for presetting integer value;
5th receiver module, is configured to the authorization information receiving user's input in this authorization information input frame of this first display module display;
This second detection module, whether the authorization information being configured to detect this user input that the 5th receiver module receives is identical with the authorization information preset;
This first sending module, is configured to, when this second detection module detects that the authorization information that this user inputs is different from the authorization information that this is preset, send discreditable behavior reporting information to application server.
Optionally, this device also comprises: the second display module, the 6th receiver module, the 3rd detection module and the second sending module;
This second display module, is configured to when receiving unblock triggering command, display authorization information input frame;
6th receiver module, is configured to the authorization information receiving user's input in this authorization information input frame of this second display module display;
3rd detection module, whether the authorization information being configured to detect this user input that the 6th receiver module receives is identical with the authorization information preset;
This second sending module, is configured to, when the 3rd detection module detects that the authorization information that this user inputs is identical with the authorization information that this is preset, send to application server releasing behavior reporting information of breaking one's promise.
According to the 7th aspect of disclosure embodiment, provide a kind of locking device of application, this device comprises:
Processor;
For storing the memory of the executable instruction of this processor;
Wherein, this processor is configured to:
Receive the blacklist of breaking one's promise that application server sends, in this blacklist of breaking one's promise, record the user account that default discreditable behavior occurs;
When there being newly-increased user account during this breaks one's promise blacklist, determine the target terminal mark that this newly-increased user account is corresponding;
The terminal corresponding to this target terminal mark sends lock instruction, and this lock instruction is used to indicate and locks the application in terminal.
According to the eighth aspect of disclosure embodiment, provide a kind of locking device of application, this device comprises:
Processor;
For storing the memory of the executable instruction of this processor;
Wherein, this processor is configured to:
Whether the user account registered in monitoring and measuring application server there is default discreditable behavior;
When this default discreditable behavior occurs this user account, this user account is recorded to and breaks one's promise in blacklist;
This blacklist of breaking one's promise is sent to Cloud Server.
According to the 9th aspect of disclosure embodiment, provide a kind of locking device of application, this device comprises:
Processor;
For storing the memory of the executable instruction of this processor;
Wherein, this processor is configured to:
Receive the lock instruction that Cloud Server sends, to be this Cloud Server have during newly-increased user account this lock instruction in the blacklist of breaking one's promise that the application server received sends sends, this lock instruction is used to indicate and locks the application in terminal, records the user account that default discreditable behavior occurs in this blacklist of breaking one's promise;
According to this lock instruction, the application in terminal is locked.
According to the tenth aspect of disclosure embodiment, provide a kind of locking system of application, this system comprises: Cloud Server, application server and terminal;
This Cloud Server comprises the locking device of the arbitrary described application of fourth aspect;
This application server comprises the locking device of the arbitrary described application in the 5th aspect;
This terminal comprises the locking device of the arbitrary described application in the 6th aspect
According to the 11 aspect of disclosure embodiment, provide a kind of locking system of application, this system comprises:
Cloud Server, application server and terminal;
This Cloud Server comprises the locking device of the application described in the 7th aspect;
This application server comprises the locking device of the application described in eighth aspect;
This terminal comprises the locking device of the application described in the 9th aspect.
The technical scheme that embodiment of the present disclosure provides can comprise following beneficial effect:
Locking means, the Apparatus and system of a kind of application that disclosure embodiment provides, Cloud Server can receive the blacklist of breaking one's promise that application server sends, and records the user account that default discreditable behavior occurs in this blacklist of breaking one's promise.When there being newly-increased user account during this breaks one's promise blacklist, Cloud Server can determine the target terminal mark that this newly-increased user account is corresponding, and send lock instruction to the terminal that this target terminal mark is corresponding, this lock instruction is used to indicate and locks the application in terminal, therefore enriched and line-locked trigger mechanism has been entered to the application in terminal, and suitable disciplining as a warning is carried out to the discreditable behavior of user, the rate of breaking one's promise of user can be reduced.
Should be understood that, it is only exemplary that above general description and details hereinafter describe, and can not limit the disclosure.
Accompanying drawing explanation
In order to be illustrated more clearly in embodiment of the present disclosure, below the accompanying drawing used required in describing embodiment is briefly described, apparently, accompanying drawing in the following describes is only embodiments more of the present disclosure, for those of ordinary skill in the art, under the prerequisite not paying creative work, other accompanying drawing can also be obtained according to these accompanying drawings.
Fig. 1 is the schematic diagram of the implementation environment involved by locking means of a kind of application according to an exemplary embodiment;
Fig. 2 is the flow chart of the locking means of a kind of application according to an exemplary embodiment;
Fig. 3 is the flow chart of the locking means that the another kind according to an exemplary embodiment is applied;
Fig. 4 is the flow chart of another locking means applied according to an exemplary embodiment;
Fig. 5-1 is the flow chart of another locking means applied according to an exemplary embodiment;
Fig. 5-2 is method flow diagrams of the default discreditable behavior of a kind of application server monitoring according to an exemplary embodiment;
Fig. 5-3 is method flow diagrams of the default discreditable behavior of another kind of application server monitoring according to an exemplary embodiment;
Fig. 5-4 is schematic diagrames that a kind of terminal demonstration authorization information input frame is shown according to an exemplary embodiment;
Fig. 5-5 is method flow diagrams that a kind of Cloud Server according to an exemplary embodiment determines whether newly-increased user account;
Fig. 5-6 is method flow diagrams of a kind of Cloud Server transmission lock instruction according to an exemplary embodiment;
Fig. 5-7 is method flow diagrams of the default releasing behavior of breaking one's promise of a kind of application server monitoring according to an exemplary embodiment;
Fig. 5-8 is method flow diagrams of the default releasing behavior of breaking one's promise of another kind of application server monitoring according to an exemplary embodiment;
Fig. 6-1 is the block diagram of the locking device of a kind of application according to an exemplary embodiment;
Fig. 6-2 is the block diagrams of the locking device that the another kind according to an exemplary embodiment is applied;
Fig. 6-3 is block diagrams of a kind of first sending module according to an exemplary embodiment;
Fig. 7-1 is the block diagram of another locking device applied according to an exemplary embodiment;
Fig. 7-2 is block diagrams of another locking device applied according to an exemplary embodiment;
Fig. 7-3 is block diagrams of a kind of first monitoring modular according to an exemplary embodiment;
Fig. 7-4 is block diagrams of a kind of second monitoring modular according to an exemplary embodiment;
Fig. 7-5 is block diagrams of another kind first monitoring modular according to an exemplary embodiment;
Fig. 7-6 is block diagrams of another kind second monitoring modular according to an exemplary embodiment;
Fig. 8-1 is the block diagram of another locking device applied according to an exemplary embodiment;
Fig. 8-2 is block diagrams of another locking device applied according to an exemplary embodiment;
Fig. 8-3 is block diagrams of a kind of locking module according to an exemplary embodiment;
Fig. 9 is the block diagram of another locking device applied according to an exemplary embodiment;
Figure 10 is the block diagram of the locking device of a kind of application according to an exemplary embodiment;
Figure 11 is the block diagram of the locking device of a kind of application according to an exemplary embodiment.
Accompanying drawing to be herein merged in specification and to form the part of this specification, shows and meets embodiment of the present disclosure, and is used from specification one and explains principle of the present disclosure.
Embodiment
In order to make object of the present disclosure, technical scheme and advantage clearly, be described in further detail the disclosure below in conjunction with accompanying drawing, obviously, described embodiment is only a part of embodiment of the disclosure, instead of whole embodiments.Based on the embodiment in the disclosure, those of ordinary skill in the art are not making other embodiments all obtained under creative work prerequisite, all belong to the scope of disclosure protection.
Fig. 1 is the schematic diagram of the implementation environment involved by locking means of a kind of application according to an exemplary embodiment.This implementation environment can comprise: Cloud Server 110, application server 120 and terminal 130.Cloud Server 110 and application server 120 can be station servers, or the server cluster be made up of some station servers, or a cloud computing service center.Terminal 130 can be smart mobile phone, computer, multimedia player, electronic reader, Wearable device etc.Cloud Server 110, can be set up by cable network or wireless network between application server 120 and terminal 130 and connect.
Wherein application server 120 is for when the user account generation discreditable behavior registered in this application server, the blacklist of breaking one's promise recording this user account is sent to Cloud Server 110, Cloud Server 110 sends lock instruction for the terminal 130 corresponding to the user account that records in breaking one's promise blacklist to this, and terminal 130 can according to the application in this lock instruction locking terminal.
Fig. 2 is the flow chart of the locking means of a kind of application according to an exemplary embodiment, and the method can be applied in the Cloud Server 110 shown in Fig. 1, and as shown in Figure 2, the method comprises:
In step 201, receive the blacklist of breaking one's promise that application server sends, in this blacklist of breaking one's promise, record the user account that default discreditable behavior occurs.
In step 202., when there being newly-increased user account during this breaks one's promise blacklist, determine the target terminal mark that this newly-increased user account is corresponding.
In step 203, the terminal corresponding to this target terminal mark sends lock instruction, and this lock instruction is used to indicate and locks the application in terminal.
In sum, the locking means of a kind of application that disclosure embodiment provides, Cloud Server can receive the blacklist of breaking one's promise that application server sends, and records the user account that default discreditable behavior occurs in this blacklist of breaking one's promise.When there being newly-increased user account during this breaks one's promise blacklist, Cloud Server can determine the target terminal mark that this newly-increased user account is corresponding, and send lock instruction to the terminal that this target terminal mark is corresponding, this lock instruction is used to indicate and locks the application in terminal, therefore enriched and line-locked trigger mechanism has been entered to the application in terminal, and suitable disciplining as a warning is carried out to the discreditable behavior of user, the rate of breaking one's promise of user can be reduced.
Optionally, the method also comprises:
Receive the white list of breaking one's promise that application server sends, in this white list of breaking one's promise, record the user account occurring to preset releasing behavior of breaking one's promise;
Determine the unlock terminal mark that user account that this is broken one's promise in white list is corresponding;
The terminal corresponding to this unlock terminal mark sends unlock command, and this unlock command is used to indicate and unlocks to the application in terminal.
Optionally, this sends lock instruction to the terminal that this target terminal mark is corresponding, comprising:
Obtain the target application mark that this application server is corresponding;
Generate this lock instruction, this lock instruction comprises this target application mark;
The terminal corresponding to this target terminal mark sends this lock instruction, and this lock instruction is used to indicate and locks other application in terminal except the application of this target application mark correspondence.
Optionally, what this target application mark was corresponding is applied as financial application, these other be applied as other financial application;
Or, these other be applied as all application except the application corresponding except this target application mark of installing in terminal.
Optionally, the method also comprises:
Contrast this blacklist of breaking one's promise whether identical with the user account recorded in the blacklist of breaking one's promise prestored;
When this blacklist of breaking one's promise is not identical with the user account recorded in this blacklist of breaking one's promise prestored, detects this user account of breaking one's promise in blacklist and whether there is Unrecorded user account in this blacklist of breaking one's promise prestored;
If this user account of breaking one's promise in blacklist exists Unrecorded user account in this blacklist of breaking one's promise prestored, this Unrecorded user account is defined as the user account that this is newly-increased.
Optionally, the method also comprises:
Identify corresponding terminal to this target terminal and send mark of breaking one's promise, the terminal of this target terminal mark correspondence writes to the predeterminated position in operating system for mark of this being broken one's promise, and this mark of breaking one's promise performs the predetermined registration operation to operating system for forbidding.
Optionally, the method also comprises:
The terminal corresponding to this unlock terminal mark sends mark erasing instruction of breaking one's promise, and identifies corresponding terminal will be arranged in the mark erasing of breaking one's promise of operating system predeterminated position according to this mark erasing instruction of breaking one's promise to make this unlock terminal.
Optionally, the method also comprises:
Detect in this user account of breaking one's promise in blacklist prestored and whether there is the user account recorded in this white list of breaking one's promise;
If there is the user account recorded in this white list of breaking one's promise in the user account that what this prestored break one's promise in blacklist, the user account recorded in white list of this being broken one's promise is deleted from this breaks one's promise blacklist.
In sum, the locking means of a kind of application that disclosure embodiment provides, Cloud Server can receive the blacklist of breaking one's promise that application server sends, and records the user account that default discreditable behavior occurs in this blacklist of breaking one's promise.When there being newly-increased user account during this breaks one's promise blacklist, Cloud Server can determine the target terminal mark that this newly-increased user account is corresponding, and send lock instruction to the terminal that this target terminal mark is corresponding, this lock instruction is used to indicate and locks the application in terminal, therefore enriched and line-locked trigger mechanism has been entered to the application in terminal, and suitable disciplining as a warning is carried out to the discreditable behavior of user, the rate of breaking one's promise of user can be reduced.
Fig. 3 is the flow chart of the locking means that the another kind according to an exemplary embodiment is applied, and the method can be applied in the application server 120 shown in Fig. 1, and as shown in Figure 3, the method comprises:
In step 301, whether the user account registered in monitoring and measuring application server there is default discreditable behavior.
In step 302, when this default discreditable behavior occurs this user account, this user account is recorded to and breaks one's promise in blacklist.
In step 303, this blacklist of breaking one's promise is sent to Cloud Server.
In sum, the locking means of a kind of application that disclosure embodiment provides, whether the user account that application server can be registered in monitoring and measuring application server there is default discreditable behavior, when there is this default discreditable behavior in this user account, being recorded to by this user account breaks one's promise in blacklist, and send this blacklist of breaking one's promise to Cloud Server, so that cloud service sends lock instruction to the terminal that this user account is corresponding, this lock instruction is used to indicate and locks the application in terminal, therefore enriched and line-locked trigger mechanism has been entered to the application in terminal, and suitable disciplining as a warning is carried out to the discreditable behavior of user, the rate of breaking one's promise of user can be reduced.
The method also comprises:
Monitor the user account recorded in this blacklist of breaking one's promise whether to occur to preset releasing behavior of breaking one's promise;
The user account recorded in this breaks one's promise blacklist occur this preset break one's promise releasing behavior time, this user account is recorded to and breaks one's promise in white list;
This white list of breaking one's promise is sent to this Cloud Server.
Optionally, whether the user account registered in this monitoring and measuring application server there is default discreditable behavior, comprising:
Obtain the credit record of this user account, in this credit record, record loaning bill information and the refund information of this user account;
Detect in this credit record the loaning bill information whether existing and do not refund;
When there is the loaning bill information of not refunding in this credit record, judge that the date of formation of this loaning bill information of not refunding is whether in predetermined period;
When the date of formation of the loaning bill information that this is not refunded is in predetermined period, determine that default discreditable behavior does not occur this user account; Or,
When the date of formation of the loaning bill information that this is not refunded is not in predetermined period, determine that this user account occurs to preset discreditable behavior.
Optionally, whether the user account recorded in this blacklist of breaking one's promise of this monitoring occurs to preset releasing behavior of breaking one's promise, and comprising:
When monitoring arbitrary user account generation refund behavior of registering in this application server, judge whether the user account of this generation refund behavior is recorded in this and breaks one's promise in blacklist;
When the user account of this generation refund behavior is recorded in this blacklist of breaking one's promise, obtain the credit record of the user account of this generation refund behavior, in this credit record, record loaning bill information and the refund information of this user account;
Judge whether the refund amount of money recorded in this refund information is less than predetermined threshold value;
When this refund amount of money is less than this predetermined threshold value, determine that this user account does not occur to preset releasing behavior of breaking one's promise; Or,
When this refund amount of money is not less than this predetermined threshold value, determine that this user account occurs to preset releasing behavior of breaking one's promise.
Optionally, whether the user account registered in this monitoring and measuring application server there is default discreditable behavior, comprising:
The discreditable behavior reporting information that the terminal that the user account receiving this registration logs in sends, this terminal is when continuous n false release action being detected, display authorization information input frame, this discreditable behavior reporting information is that this terminal detects that the authorization information of the user's input received at this authorization information input frame sends time different from the authorization information preset, and this n is for presetting integer value;
According to this discreditable behavior reporting information, determine that this user account occurs to preset discreditable behavior.
Optionally, whether the user account recorded in this blacklist of breaking one's promise of this monitoring occurs to preset releasing behavior of breaking one's promise, and comprising:
Releasing behavior of the breaking one's promise reporting information that the terminal that the user account receiving this registration logs in sends, this terminal is when receiving unblock triggering command, display authorization information input frame, this releasing behavior reporting information of breaking one's promise is that this terminal detects that the authorization information of the user's input received in this authorization information input frame sends time identical with the authorization information preset;
According to this releasing behavior reporting information of breaking one's promise, determine that this user account occurs to preset releasing behavior of breaking one's promise.
In sum, the locking means of a kind of application that disclosure embodiment provides, whether the user account that application server can be registered in monitoring and measuring application server there is default discreditable behavior, when there is this default discreditable behavior in this user account, being recorded to by this user account breaks one's promise in blacklist, and send this blacklist of breaking one's promise to Cloud Server, so that cloud service sends lock instruction to the terminal that this user account is corresponding, this lock instruction is used to indicate and locks the application in terminal, therefore enriched and line-locked trigger mechanism has been entered to the application in terminal, and suitable disciplining as a warning is carried out to the discreditable behavior of user, the rate of breaking one's promise of user can be reduced.
Fig. 4 is the flow chart of another locking means applied according to an exemplary embodiment, and the method can be applied in the application server 130 shown in Fig. 1, and as shown in Figure 4, the method comprises:
In step 401, receive the lock instruction that Cloud Server sends, to be this Cloud Server have during newly-increased user account this lock instruction in the blacklist of breaking one's promise that the application server received sends sends, this lock instruction is used to indicate and locks the application in terminal, records the user account that default discreditable behavior occurs in this blacklist of breaking one's promise.
In step 402, according to this lock instruction, the application in terminal is locked.
In sum, the locking means of a kind of application that disclosure embodiment provides, terminal can receive the lock instruction that Cloud Server sends, to be this Cloud Server have during newly-increased user account this lock instruction in the blacklist of breaking one's promise that the application server received sends sends, this lock instruction is used to indicate and locks the application in terminal, therefore enriched and line-locked trigger mechanism has been entered to the application in terminal, and suitable disciplining as a warning is carried out to the discreditable behavior of user, the rate of breaking one's promise of user can be reduced.
Optionally, the method also comprises:
Receive the unlock command that Cloud Server sends, this unlock command be this Cloud Server receive that application server sends break one's promise white list time send, this unlock command is used to indicate and unlocks to the application in terminal, records the user account occurring to preset releasing behavior of breaking one's promise in this white list of breaking one's promise;
According to this unlock command, the application in this terminal is unlocked.
Optionally, this lock instruction also comprises target application mark, and this locks the application in terminal according to this lock instruction, comprising:
According to this lock instruction, other application in terminal except the application of this target application mark correspondence are locked.
Optionally, what this target application mark was corresponding is applied as financial application, these other be applied as other financial application; Or, these other be applied as all application except the application corresponding except this target application mark of installing in terminal.
Optionally, the method also comprises:
Receive the mark of breaking one's promise that Cloud Server sends, this mark of breaking one's promise performs the predetermined registration operation to operating system for forbidding;
Mark of this being broken one's promise writes to the predeterminated position in the operating system of this terminal.
Optionally, the method also comprises:
Receive the mark erasing instruction of breaking one's promise that Cloud Server sends;
Detect predeterminated position in this operating system and whether there is mark of breaking one's promise;
When this predeterminated position exists this mark of breaking one's promise, according to this mark erasing instruction of breaking one's promise, the mark erasing of breaking one's promise of operating system predeterminated position will be arranged in.
Optionally, the method also comprises:
When continuous n false release action being detected, display authorization information input frame, this n is for presetting integer value;
The authorization information of user's input is received in this authorization information input frame;
Whether the authorization information detecting this user input is identical with the authorization information preset;
When the authorization information that this user inputs is different from the authorization information that this is preset, send discreditable behavior reporting information to application server.
Optionally, the method also comprises:
When receiving unblock triggering command, display authorization information input frame;
The authorization information of user's input is received in this authorization information input frame;
Whether the authorization information detecting this user input is identical with the authorization information preset;
When the authorization information that this user inputs is identical with the authorization information that this is preset, send to application server releasing behavior reporting information of breaking one's promise.
In sum, the locking means of a kind of application that disclosure embodiment provides, terminal can receive the lock instruction that Cloud Server sends, to be this Cloud Server have during newly-increased user account this lock instruction in the blacklist of breaking one's promise that the application server received sends sends, this lock instruction is used to indicate and locks the application in terminal, therefore enriched and line-locked trigger mechanism has been entered to the application in terminal, and suitable disciplining as a warning is carried out to the discreditable behavior of user, the rate of breaking one's promise of user can be reduced.
Fig. 5-1 is the flow chart of another locking means applied according to an exemplary embodiment, and the method can be applied in the implementation environment shown in Fig. 1, and as shown in fig. 5-1, the method comprises:
In step 501, whether the user account registered in application server monitoring and measuring application server there is default discreditable behavior.
In the disclosed embodiments, this application server can be the application server of financial class, and this default discreditable behavior can for the debt behavior preset.When there is default discreditable behavior in the user corresponding to user account, application server can by monitoring to the operation produced of this user account the discreditable behavior determining this user, therefore, also can think that application server can be monitored this user account and whether default discreditable behavior is occurred.User is in this financial class application server after registered user's account, not only this financial class application server Investment & Financing can be passed through, this financial class application server apply for loan can also be passed through, in order to the refund behavior of monitor user ', application server can periodically or the user account registered in real-time this application server of detection whether there is default discreditable behavior.In the disclosed embodiments, the method for application server monitoring discreditable behavior can be realized by two kinds of modes:
Fig. 5-2 is method flow diagrams of the default discreditable behavior of a kind of application server monitoring according to an exemplary embodiment, and as shown in Fig. 5-2, in the first implementation, the method comprises:
In step 5011a, obtain the credit record of user account, in this credit record, record loaning bill information and the refund information of this user account.
The credit record of the user account registered in this application server of acquisition that application server can be periodic or real-time, and the loaning bill information recorded in credit record by each user account and refund information judge whether this user account default discreditable behavior occurs.Example, suppose that this application server is financial server, the user account registered in this financial server comprises: 1234 and 4321, then the credit record of these two user accounts of financial server acquisition can be as shown in table 1, loaning bill information in the credit record of wherein user account 1234 comprises: 1. the time: 2015.05.01, borrows money: 5000 yuan; Refund information is: nothing.Loaning bill information in the credit record of user account 4321 comprises: 1. the time: 2015.07.01, borrows money: 1000 yuan; Refund information is: 1: the time: 2015.08.01, refunds: 1000 yuan.
Table 1
In step 5012a, detect in this credit record the loaning bill information whether existing and do not refund.
When there is the loaning bill information of not refunding in this credit record, perform step 5013a; When there is not the loaning bill information of not refunding in this credit record, perform step 5014a.
In the disclosed embodiments, loaning bill information in the credit record of each user account and refund information can one_to_one corresponding, if arbitrary loaning bill information does not have refund information corresponding with it in credit record, or the amount of money of refunding in refund information corresponding is with it less than the borrowing balance in this loaning bill information, then application server can determine to there is the loaning bill information of not refunding in the credit record of this user account, now can perform step 5013a; If there is not the loaning bill information of not refunding in credit record, application server can determine that default discreditable behavior does not occur this user account, namely performs step 5014a.Example, suppose that the credit record that application server obtains is as shown in table 1, wherein, in the credit record of user account 1234, loaning bill information: 1. time: 2015.05.01 borrows money: 5000 yuan do not have refund information corresponding with it, then application server can determine to there is the loaning bill information of not refunding in the credit record of this user account 1234, now can perform step 5013.And in the credit record of user account 4321, loaning bill information is: 1. time: 2015.07.01 borrows money: 1000 yuan, refund information corresponding is with it: 1: the time: 2015.08.01 refunds: 1000 yuan, the refund amount of money in wherein refund information equals the borrowing balance in loaning bill information, therefore application server can determine there is not the loaning bill information of not refunding in the credit record of this user account 4321, and now application server can terminate the detection to this user account 4321.
In step 5013a, judge that the date of formation of this loaning bill information of not refunding is whether in predetermined period.
When the date of formation of the loaning bill information that this is not refunded is in predetermined period, perform step 5014a; When the date of formation of the loaning bill information that this is not refunded is not in predetermined period, perform step 5015a.
Payment period can be preset with in application server, when there is the loaning bill information of not refunding in the credit record of application server determination user account, can also further according to current temporal information, judge that the date of formation of this loaning bill information is whether in this payment period preset, when the date of formation of the loaning bill information that this is not refunded is in predetermined period, application server can determine that the refund behavior of this user account is not also exceeded the time limit, and can perform step 5014a; When the date of formation of the loaning bill information that this is not refunded is not in predetermined period, application server can determine that the refund behavior of this user account is exceeded the time limit, and now performs step 5015a.
Example, suppose that the payment period preset in application server is 3 months, current time is 2015.09.01, then according to the loaning bill information in the credit record of user account 1234: 1. time: 2015.05.01 borrows money: 5000 yuan known, the date of formation of this loaning bill information is 2015.05.01, existing 4 months of distance current time 2015.09.01, has exceeded the payment period that this is preset: 3 months, therefore application server can perform step 5015a.
It should be noted that, in actual applications, this payment period preset can also set according to the borrowing balance of user, such as, when borrowing balance is less, the payment period preset is shorter, when borrowing balance is larger, this payment period preset then can correspondingly extend, and disclosure embodiment does not limit this.
In step 5014a, determine that default discreditable behavior does not occur this user account.
When the date of formation of the loaning bill information that this is not refunded is in predetermined period, application server can determine that the refund behavior of this user account is not also exceeded the time limit, and determines that default discreditable behavior does not occur this user account.
In step 5015a, determine that this user account occurs to preset discreditable behavior.
When the date of formation of the loaning bill information that this is not refunded is not in predetermined period, application server can determine that the refund behavior of this user account is exceeded the time limit, and determines that this user account occurs to preset discreditable behavior.Example, application server can determine that default discreditable behavior occurs the user corresponding to user account 1234.
In the disclosed embodiments, according to the credit record of user account, application server is except judging whether this user account default discreditable behavior occurs, the discreditable behavior reporting information that can also send according to terminal judges.Fig. 5-3 is method flow diagrams of the default discreditable behavior of another kind of application server monitoring according to an exemplary embodiment, and as shown in Fig. 5-3, in the second implementation, the method comprises:
In step 5011b, terminal, when continuous n false release action being detected, shows authorization information input frame.
In the disclosed embodiments, when the lost terminal of user, reveal to prevent the user profile stored in terminal, false release threshold value can be preset with: n in terminal, this n, for presetting integer value, when terminal detects continuous n false release action, can show authorization information input frame.Example, Fig. 5-4 is schematic diagrames that a kind of terminal demonstration authorization information input frame is shown according to an exemplary embodiment, suppose that the false release threshold value n preset in terminal is 5, then when terminal is when continuous 5 false release actions being detected, authorization information input frame 500 can be shown in the interface shown in Fig. 5-4, and the information of display response, such as: which day is your birthday?
In step 5012b, terminal receives the authorization information of user's input in this authorization information input frame.
Example, suppose that the information that user inputs in the authorization information input frame 500 shown in Fig. 5-4 is: 1980.01.01, then terminal can receive this authorization information by authorization information input frame: 1980.01.01.
In step 5013b, whether the authorization information that terminal detects this user input is identical with the authorization information preset.
Can store default authorization information in terminal, after terminal receives this authorization information by authorization information input frame, the authorization information that this user can be inputted contrasts with the authorization information preset, and whether the authorization information detecting user's input is correct.
In step 5014b, when the authorization information that this user inputs is different from the authorization information that this is preset, terminal sends discreditable behavior reporting information to application server.
When terminal detects that the authorization information that user inputs is different from the authorization information preset stored in terminal, terminal can determine that the behavior of this user is discreditable behavior, and sends discreditable behavior reporting information to application server.Example, suppose that the authorization information preset stored in terminal is: 1981.02.01, then because the information of user's input: 1980.01.01 is different from the authorization information that this is preset, terminal can determine that this terminal may be lost, and sends discreditable behavior reporting information to application server.
In step 5015b, application server, according to this discreditable behavior reporting information, determines that this user account occurs to preset discreditable behavior.
After application server receives the discreditable behavior reporting information of terminal transmission, according to the user account logged in this terminal, can determine that this user account occurs to preset discreditable behavior.Example, suppose the application program being provided with financial class in this terminal, the account that terminal logs in the application program of this financial class is 4321, then after application server receives the discreditable behavior reporting information of this terminal transmission, user account can be determined: the user corresponding to 4321 there occurs default discreditable behavior.
In step 502, when this default discreditable behavior occurs this user account, this user account is recorded to and breaks one's promise in blacklist by application server.
This user account can be recorded to and break one's promise in blacklist after determining to occur the user account of this default discreditable behavior by application server.Example, suppose that application server is in above-mentioned steps 501, the user account presetting discreditable behavior determined by the first implementation is: 1234, the user account presetting discreditable behavior determined by the second implementation is: 4321, then these two user accounts can be recorded to and break one's promise in blacklist by application server, this blacklist can be: 1234,4321.
In step 503, application server sends this blacklist of breaking one's promise to Cloud Server.
Example, application server sends this blacklist of breaking one's promise to Cloud Server and can be: 1234,4321.
In step 504, when there being newly-increased user account during this breaks one's promise blacklist, Cloud Server determines the target terminal mark that this newly-increased user account is corresponding.
In the disclosed embodiments, the corresponding relation of user account and terminal iidentification can be stored in Cloud Server, after cloud server to blacklist of breaking one's promise, can according to the blacklist of breaking one's promise prestored in Cloud Server, determine user account newly-increased in this blacklist of breaking one's promise received, and according to the corresponding relation of this user account and terminal iidentification, determine the target terminal mark that this newly-increased user account is corresponding.Fig. 5-5 is method flow diagrams that a kind of Cloud Server according to an exemplary embodiment determines whether newly-increased user account, and as illustrated in fig. 5-5, the method comprises:
In step 5041, contrast this blacklist of breaking one's promise whether identical with the user account recorded in the blacklist of breaking one's promise prestored.
When this blacklist of breaking one's promise is not identical with the user account recorded in this blacklist of breaking one's promise prestored, perform step 5042; When this blacklist of breaking one's promise is identical with the user account recorded in the blacklist of breaking one's promise that this prestores, terminate.
In the disclosed embodiments, cloud service according to this blacklist of breaking one's promise, can upgrade the blacklist of breaking one's promise stored and store after receiving the blacklist of breaking one's promise of application server transmission at every turn.If this is broken one's promise, blacklist is identical with the user account recorded in the blacklist of breaking one's promise that this prestores, then Cloud Server can determine that this blacklist of breaking one's promise does not upgrade, and terminates the flow process determining newly-increased blacklist.Example, suppose that the user account recorded in the blacklist of breaking one's promise prestored in Cloud Server is: 0000,1111,4321, then due to cloud server to blacklist of breaking one's promise in the user account that records: 1234,4321 is different from the user account recorded in the blacklist of breaking one's promise that this prestores, and Cloud Server can perform step 5042.
In step 5042, detect this user account of breaking one's promise in blacklist and whether there is Unrecorded user account in this blacklist of breaking one's promise prestored.
When cloud server to blacklist of breaking one's promise not identical with the user account recorded in the blacklist of breaking one's promise prestored time, Cloud Server can continue to detect this user account of breaking one's promise in blacklist and whether there is Unrecorded user account in this blacklist of breaking one's promise prestored, if this user account of breaking one's promise in blacklist exists Unrecorded user account in this blacklist of breaking one's promise prestored, perform step 5043; If this user account of breaking one's promise in blacklist does not exist Unrecorded user account in this blacklist of breaking one's promise prestored, terminate.Example, suppose that the user account recorded in the blacklist of breaking one's promise prestored in Cloud Server is: 0000,1111,4321, cloud server to blacklist of breaking one's promise in the user account that records be: 1234,4321, then Cloud Server can detect this user account of breaking one's promise in blacklist: 1234, and 4321 exist Unrecorded user account in this blacklist of breaking one's promise prestored: 1234.
In step 5043, this Unrecorded user account is defined as the user account that this is newly-increased.
Cloud Server by breaking one's promise in blacklist of being recorded in that application server sends, and can not be recorded in the user account that the user account of breaking one's promise in blacklist prestored is defined as increasing newly.Example, this can be the user account of record by Cloud Server: 1234 are defined as the user account increased newly.
It should be noted that, in actual applications, what this newly-increased user account can also be added into that this prestores by Cloud Server breaks one's promise in blacklist.
In the disclosed embodiments, user can in the Cloud Server corresponding to terminal operating system registered user's account, when after user in the terminal login user account, the terminal iidentification of this user account and this terminal can be sent to cloud service by terminal automatically, if user has logged in same user account in multiple terminal simultaneously, then the plurality of terminal all have sent the terminal iidentification of this user account and the plurality of terminal to Cloud Server, accordingly, the corresponding relation of this user account and the plurality of terminal iidentification can be stored in Cloud Server.Example, suppose that user has logged in user account simultaneously in mobile phone and computer: 0000, the terminal iidentification of this mobile phone is 00-00-00-00-1F-2C, the terminal iidentification of this computer is 00-00-00-00-1F-2D, and this mobile phone and computer have sent user account and terminal iidentification respectively to Cloud Server, then the user account stored in cloud service: the terminal iidentification corresponding to 1234 can comprise: 00-00-00-00-1F-2C and 00-00-00-00-1F-2D.
Further, after the user account increased newly is determined in cloud service, can according to the corresponding relation of this user account and terminal iidentification, terminal iidentification corresponding to newly-increased user account is defined as target terminal mark, if this user account is to there being multiple terminal iidentification, then the plurality of terminal iidentification all can be defined as target terminal mark by Cloud Server.Wherein, this terminal iidentification can be the media interviews control (English: MediaAccessControl of terminal; Being called for short: MAC) address, also can be that the mobile device international identity code of this terminal is (English: InternationalMobileEquipmentIdentity; IMEI) or the sequence number that dispatches from the factory of this terminal be called for short:, disclosure embodiment does not limit.Example, suppose that the terminal iidentification in the corresponding relation of user account and the terminal iidentification stored in Cloud Server is the MAC Address of terminal, this corresponding relation can be as shown in table 2, and wherein, the terminal iidentification of user account 1234 correspondence is: 11-22-33-44-1F-2C; The terminal iidentification of user account 4321 correspondence is: 44-33-22-11-1F-2C.Then Cloud Server can corresponding relation according to this table 2, the user account newly-increased by this: the terminal iidentification corresponding to 1234: 11-22-33-44-1F-2C is defined as target terminal mark.
Table 2
In step 505, Cloud Server sends lock instruction to the terminal that this target terminal mark is corresponding.
This lock instruction is used to indicate and locks the application in terminal.Example, Cloud Server can identify to this target terminal: the terminal that 11-22-33-44-1F-2C is corresponding sends lock instruction.
It should be noted that, if the newly-increased mark of the target terminal corresponding to user account that Cloud Server is determined comprises multiple terminal iidentification, then Cloud Server can send lock instruction to the plurality of target terminal mark.Example, if the newly-increased user account that Cloud Server is determined is 0000, then according to the corresponding relation shown in table 2, this newly-increased target terminal corresponding to user account 0000 is designated: 00-00-00-00-1F-2C and 00-00-00-00-1F-2D, then Cloud Server can send lock instruction respectively to the terminal corresponding to these two target terminal mark 00-00-00-00-1F-2C and 00-00-00-00-1F-2D.
In the disclosed embodiments, the lock instruction that Cloud Server sends can also comprise target application mark, so that terminal can according to this lock instruction, other application in terminal except the application of this target application mark correspondence are locked, presets to ensure that user can be performed by the application that this target application mark is corresponding releasing behavior of breaking one's promise.Fig. 5-6 is method flow diagrams of a kind of Cloud Server transmission lock instruction according to an exemplary embodiment, and as seen in figs. 5-6, the method that Cloud Server sends lock instruction can comprise:
In step 5051, obtain the target application mark that application server is corresponding.
Cloud Server can obtain to its send break one's promise blacklist application server corresponding to target application mark.Example, suppose that sending to Cloud Server the application server of blacklist of breaking one's promise is xx financial server, then Cloud Server can obtain this target application mark corresponding to xx financial server: xx finance.
In step 5052, generate lock instruction, this lock instruction comprises this target application mark.
In the disclosed embodiments, after Cloud Server gets target application mark, lock instruction can be generated according to this target application mark.Example, the lock instruction that Cloud Server generates can comprise: target application identifies: xx finance.
In step 5053, the terminal corresponding to this target terminal mark sends this lock instruction.
This lock instruction comprises target application mark, and this lock instruction is used to indicate and locks other application in terminal except the application of this target application mark correspondence.In the disclosed embodiments, the application of this target application mark correspondence can be financial application, these other be applied as other financial application, namely after terminal receives lock instruction, other financial application outside financial application corresponding for this target application mark can be locked, to make user that other financial application cannot be used to consume, and after financial application corresponding to this target application mark must be used to refund, terminal just can be made to unlock as early as possible.Or, these other be applied as all application except the application corresponding except this target application mark of installing in terminal, namely after terminal receives lock instruction, all application outside the financial application of this target application mark correspondence can be locked, supervise user to use this financial application to complete as early as possible with this and preset releasing behavior of breaking one's promise.Example, suppose that the target application that lock instruction comprises is designated xx finance, then this lock instruction can indicate and lock other application in terminal except xx finance.
It should be noted that, the lock instruction that Cloud Server generates is except comprising this target application mark, the application identities that other are preset can also be comprised, the such as system such as phone, note application identities, after terminal receives this lock instruction, can other application except the application that this target application identifies and default application identities is corresponding be locked.
In step 506, terminal, according to this lock instruction, locks the application in terminal.
In the disclosed embodiments, the lock instruction that the Cloud Server that terminal receives sends can also comprise target application mark, after terminal receives this lock instruction, other application in terminal except the application of this target application mark correspondence can be locked, therefore the application that in terminal, this target application mark is corresponding can also normally use, so that user can be completed by this application and preset releasing behavior of breaking one's promise, such as refunded in time by xx financial applications, to ensure that other application in terminal can unlock in time.Therefore, the locking means of the application that the embodiment of the present invention provides, has not only enriched the trigger mechanism of locking application, effectively can also discipline as a warning, reduce the rate of breaking one's promise of user to the discreditable behavior of user.
In step 507, Cloud Server sends to the terminal that this target terminal mark is corresponding mark of breaking one's promise.
This mark of breaking one's promise performs the predetermined registration operation to operating system for forbidding.This predetermined registration operation can be again the operation of installing operating system, i.e. brush machine operation.
In step 508, terminal mark of this being broken one's promise writes to predeterminated position in operating system.
When after terminal locking application, in order to avoid user removes locking to application by the operating system changed in terminal, the mark of breaking one's promise that Cloud Server sends can also be write to the predeterminated position in terminal operating system by terminal, and this mark of breaking one's promise performs the predetermined registration operation to operating system for forbidding.This predetermined registration operation can be again the operation of installing operating system, i.e. brush machine operation.When user passes through the operating system in brush machine program change terminal, if the mark of breaking one's promise that brush machine Programmable detection writes to operating system predeterminated position, can stop performing brush machine flow process.
In step 509, whether application server is monitored the user account recorded in this blacklist of breaking one's promise and is occurred to preset and to break one's promise releasing behavior.
Application server is being broken one's promise in blacklist after recording user account, and whether can also detect the user account recorded in this blacklist of breaking one's promise in real time or periodically and occur to preset releasing behavior of breaking one's promise, this presets releasing behavior of breaking one's promise can for the refund behavior preset.
In the disclosed embodiments, the break one's promise method of releasing behavior of application server monitoring can be realized by two kinds of modes:
Fig. 5-7 is method flow diagrams of the default releasing behavior of breaking one's promise of a kind of application server monitoring according to an exemplary embodiment, and as illustrated in figs. 5-7, in the first implementation, the method comprises:
In step 5091a, when monitoring arbitrary user account generation refund behavior of registering in this application server, judge whether the user account of this generation refund behavior is recorded in this and breaks one's promise in blacklist.
In the disclosed embodiments, when application server monitors arbitrary user account generation refund behavior, the user account recorded in the blacklist of breaking one's promise stored in this user account and application server can be contrasted, when the user account of this generation refund behavior is recorded in this blacklist of breaking one's promise, perform step 5092a; When the user account of this generation refund behavior is not recorded in this blacklist of breaking one's promise, terminate.Example, suppose that the blacklist of breaking one's promise stored in application server is: 1234,4321, then when application server monitors user account: when refund behavior occurs the user corresponding to 1234, the user account of this generation refund behavior can be judged: 1234 are recorded in this blacklist of breaking one's promise: 1234, in 4321, therefore step 5092a can be performed.If application server judges that the user account of this generation refund behavior is not recorded in this and breaks one's promise in blacklist, then application server can determine that this refund behavior performs in the payment period preset, and therefore application server can terminate the monitoring to this user account.
It should be noted that, when application server monitors arbitrary user account generation refund behavior of registering in this application server, also need to upgrade according to refund date of this refund behavior and the credit record of the refund amount of money to this user account.Example, suppose that the user account that refund behavior occurs is: 1234, the date that refund behavior occurs this user is: 2015.09.02, the refund amount of money is 5000 yuan, then application server upgrades the refund information in the credit record of this user account, credit record after renewal can be as shown in table 3, wherein user account: the refund information after 1234 renewals is: 1. the time: 2015.05.09, refunds: 5000 yuan.
Table 3
In step 5092a, obtain the credit record of the user account of this generation refund behavior, in this credit record, record loaning bill information and the refund information of this user account.Perform step 5093a.
When the user account of this generation refund behavior is recorded in this blacklist of breaking one's promise, in order to judge whether the user that this user account is corresponding occurs to preset releasing behavior of breaking one's promise further, application server can also obtain the credit record of this user account, and judges more accurately according to the loaning bill information in this credit record and refund information.Example, suppose that the user account that refund behavior occurs is: 1234, then application server can from the corresponding relation of the user account shown in table 3 and credit record, this user account obtained: the credit record of 1234, the credit record that application server obtains can be: loaning bill information: 1. time: 2015.05.01 borrows money: 5000 yuan; Refund information: 1. time: 2015.09.02 refunds: 5000 yuan.
In step 5093a, judge whether the refund amount of money recorded in this refund information is less than predetermined threshold value.
In the disclosed embodiments, this predetermined threshold value can be arranged according to the borrowing balance in loaning bill information, such as this predetermined threshold value can be 70% or 80% of borrowing balance etc., application server can according to the borrowing balance in loaning bill information, calculate this predetermined threshold value, and then judge whether the refund amount of money is less than this predetermined threshold value, when application server judges that this refund amount of money is less than this predetermined threshold value, perform step 5094a; When this refund amount of money is not less than this predetermined threshold value, perform step 5095a.Example, suppose that this predetermined threshold value is 80% of borrowing balance, then application server is according to the borrowing balance in loaning bill information: 5000 yuan, the predetermined threshold value calculated is 4000 yuan, because the refund amount of money recorded in the refund information of this user account is 5000 yuan, be not less than this predetermined threshold value, therefore can perform step 5095a.
In step 5094a, determine that this user account does not occur to preset releasing behavior of breaking one's promise.
When application server judges that this refund amount of money is less than this predetermined threshold value, application server can determine that the user that this user account is corresponding does not complete refund, and then determines that this user account does not occur to preset releasing behavior of breaking one's promise.
In step 5095a, determine that this user account occurs to preset releasing behavior of breaking one's promise.
When application server judges that this refund amount of money is not less than this predetermined threshold value, application server can determine that the refund behavior of this user account reaches default refund requirement, and then determines that this user account occurs to preset releasing behavior of breaking one's promise.Example, application server can determine user account: the user corresponding to 1234 there occurs and presets releasing behavior of breaking one's promise.
In the disclosed embodiments, according to the credit record of user account, application server is except judging whether this user account occurs to preset releasing behavior of breaking one's promise, releasing behavior of the breaking one's promise reporting information that can also send according to terminal judges.Fig. 5-8 is method flow diagrams of the default releasing behavior of breaking one's promise of another kind of application server monitoring according to an exemplary embodiment, and as viewed in figures 5-8, the method comprises
In step 5091b, terminal, when receiving unblock triggering command, shows authorization information input frame.
In the disclosed embodiments, when terminal because the mode shown in above-mentioned steps 5011b to step 5015b causes the application lock timing in terminal, terminal can also receive unblock triggering command, this unblock triggering command can be triggered by the predetermined registration operation of user, this predetermined registration operation can for press key in terminal and volume key simultaneously, or longly press volume key etc.After terminal receives this unblock triggering command, can show authorization information input frame, to point out user's input validation information, this authorization information input frame can as shown in Fig. 5-4.
In step 5092b, terminal receives the authorization information of user's input in this authorization information input frame.
Example, suppose that the information that user inputs in the authorization information input frame 500 shown in Fig. 5-4 is: 1981.02.01, then terminal can receive this authorization information by authorization information input frame: 1981.02.01.
In step 5093b, whether the authorization information that terminal detects this user input is identical with the authorization information preset.
Can store default authorization information in terminal, after terminal receives this authorization information by authorization information input frame, the authorization information that this user can be inputted contrasts with the authorization information preset, and whether the authorization information detecting user's input is correct.
In step 5094b, when the authorization information that this user inputs is identical with the authorization information that this is preset, terminal sends to application server releasing behavior reporting information of breaking one's promise.
When terminal detects that the authorization information that user inputs is identical with the authorization information preset stored in terminal, terminal can determine that the behavior of this user is for releasing behavior of breaking one's promise, and sends to application server releasing behavior reporting information of breaking one's promise.Example, suppose that the authorization information preset stored in terminal is: 1981.02.01, then because the information of user's input: 1981.02.01 is identical with the authorization information that this is preset, terminal can determine that this terminal has been got back in user's hand, and sends to application server releasing behavior reporting information of breaking one's promise.
In step 5095b, application server, according to this releasing behavior reporting information of breaking one's promise, determines that this user account occurs to preset releasing behavior of breaking one's promise.
After application server receives releasing behavior of the breaking one's promise reporting information of terminal transmission, according to the user account logged in this terminal, can determine that this user account occurs to preset releasing behavior of breaking one's promise.Example, suppose the application program being provided with financial class in this terminal, the account that terminal logs in the application program of this financial class is 4321, then after application server receives releasing behavior of the breaking one's promise reporting information of this terminal transmission, user account can be determined: the user corresponding to 4321 there occurs and presets releasing behavior of breaking one's promise.
In step 510, the user account recorded in this breaks one's promise blacklist occur this preset break one's promise releasing behavior time, this user account is recorded to and breaks one's promise in white list by application server.
After application server determines that this default releasing behavior of breaking one's promise occurs the user account recorded in this blacklist of breaking one's promise, this user account can be recorded to breaks one's promise in white list, after this to be broken one's promise, white list is sent to Cloud Server, Cloud Server can send unlock command to the terminal corresponding to the user account recorded during this breaks one's promise white list.Example, suppose that the blacklist of breaking one's promise stored in application server is: 0000,1111,4321,1234, and application server is in above-mentioned steps 509, the user account presetting releasing behavior of breaking one's promise determined by the first implementation is: 1234, the user account presetting releasing behavior of breaking one's promise determined by the second implementation is: 4321, and these two user accounts be all recorded in prestore break one's promise in blacklist, then application server can by these two user accounts: 1234,4321 are recorded to and break one's promise in white list.
Need illustrate time, in actual applications, application server determine the user account recorded in this blacklist of breaking one's promise occur this preset break one's promise releasing behavior time, this user account can also be deleted by application server from blacklist of breaking one's promise.
In step 511, application server sends this white list of breaking one's promise to this Cloud Server.
Example, application server sends this white list of breaking one's promise to Cloud Server and can be: 1234,4321.
In step 512, Cloud Server determines the unlock terminal mark that user account that this is broken one's promise in white list is corresponding.
In the disclosed embodiments, the corresponding relation of user account and terminal iidentification can be stored in Cloud Server, after cloud server to white list of breaking one's promise, according to the corresponding relation of this user account and terminal iidentification, the terminal iidentification corresponding to the user account recorded can be defined as unlock terminal mark in white list of breaking one's promise.Example, suppose that the corresponding relation of user account and the terminal iidentification stored in Cloud Server is as shown in table 2, wherein, the terminal iidentification of user account 1234 correspondence is: 11-22-33-44-1F-2C; The terminal iidentification of user account 4321 correspondence is: 44-33-22-11-1F-2C.Then Cloud Server can corresponding relation according to this table 2, and the user account recorded in white list of this being broken one's promise: the terminal iidentification of the terminal iidentification corresponding to 1234: 11-22-33-44-1F-2C and user account 4321 correspondence is: 44-33-22-11-1F-2C is defined as unlock terminal mark.
In step 513, Cloud Server sends unlock command to the terminal that this unlock terminal mark is corresponding.
This unlock command is used to indicate and unlocks to the application in terminal.Example, Cloud Server can identify to this unlock terminal: the terminal that 11-22-33-44-1F-2C and 44-33-22-11-1F-2C is corresponding sends unlock command respectively.
In the step 514, terminal, according to this unlock command, unlocks to the application in terminal.
Terminal iidentification is, after the terminal of 11-22-33-44-1F-2C and 44-33-22-11-1F-2C receives the unlock command of Cloud Server transmission, can unlock to the application in terminal.
In step 515, Cloud Server detects in this user account of breaking one's promise in blacklist prestored whether there is the user account recorded in this white list of breaking one's promise.
Cloud Server, after the white list of breaking one's promise receiving application server transmission, can also detect the user account whether existing in the user account of breaking one's promise in blacklist prestored and record in this white list of breaking one's promise.
In step 516, if there is the user account recorded in this white list of breaking one's promise in this user account of breaking one's promise in blacklist prestored, the Cloud Server user account recorded in white list of this being broken one's promise is deleted from this breaks one's promise blacklist.
In order to the blacklist synchronized update of breaking one's promise that stores in application server, Cloud Server can upgrade the blacklist of breaking one's promise prestored according to the user account recorded in this white list of breaking one's promise.Example, suppose that the blacklist of breaking one's promise prestored in Cloud Server is: 0000,1111,4321,1234, the white list of breaking one's promise that application server sends to Cloud Server is: 1234,4321, due to two user accounts recorded in this white list of breaking one's promise all be recorded in prestore break one's promise in blacklist, then this breaks one's promise the user account recorded in white list by Cloud Server: 1234,4321 delete from this breaks one's promise blacklist, delete the blacklist of breaking one's promise after this user account can be: 0000,1111.
In step 517, Cloud Server sends to terminal mark erasing instruction of breaking one's promise.
Because Cloud Server is when sending lock instruction to terminal, also have sent mark of breaking one's promise, after terminal unlocks to the application in terminal, in order to avoid this mark of breaking one's promise has an impact to terminal renewal rewards theory system, Cloud Server can also send to terminal mark erasing instruction of breaking one's promise, and this mark erasing instruction of breaking one's promise is used to indicate the mark of breaking one's promise of predeterminated position in terminal erase operation system.
In step 518, terminal detects predeterminated position in this operating system and whether there is mark of breaking one's promise.
After terminal receives this mark erasing instruction of breaking one's promise, need first to detect predeterminated position in operating system and whether there is mark of breaking one's promise, if predeterminated position does not exist this mark of breaking one's promise in operating system, then terminal is without the need to performing this mark erasing instruction of breaking one's promise.
In step 519, when this predeterminated position exists this mark of breaking one's promise, according to this mark erasing instruction of breaking one's promise, the mark erasing of breaking one's promise of operating system predeterminated position will be arranged in.
When this predeterminated position exist this break one's promise mark time, in order to avoid this mark of breaking one's promise has an impact to terminal renewal rewards theory system, terminal can according to this mark erasing instruction of breaking one's promise, and will be arranged in the mark erasing of breaking one's promise of operating system predeterminated position.
It should be noted that, the sequencing of the step of the locking means of the application that disclosure embodiment provides can suitably adjust, step also according to circumstances can carry out corresponding increase and decrease, example, step 508 can perform to step 511 before step 505, and step 507, step 508 and step 517 can according to circumstances be deleted to step 519.Anyly be familiar with those skilled in the art in the technical scope that the disclosure discloses, the method changed can be expected easily, all should be encompassed within protection range of the present disclosure, therefore repeat no more.
In sum, the locking means of a kind of application that disclosure embodiment provides, terminal can receive the lock instruction that Cloud Server sends, to be this Cloud Server have during newly-increased user account this lock instruction in the blacklist of breaking one's promise that the application server received sends sends, this lock instruction is used to indicate and locks the application in terminal, therefore enriched and line-locked trigger mechanism has been entered to the application in terminal, and suitable disciplining as a warning is carried out to the discreditable behavior of user, the rate of breaking one's promise of user can be reduced.
Fig. 6-1 is the block diagram of the locking device 600 of a kind of application according to an exemplary embodiment, and as in Figure 6-1, this device comprises:
First receiver module 601, is configured to the blacklist of breaking one's promise receiving application server transmission, records the user account that default discreditable behavior occurs in this blacklist of breaking one's promise.
First determination module 602, is configured to when there being newly-increased user account in this blacklist of breaking one's promise that this first receiver module receives, and determines the target terminal mark that this newly-increased user account is corresponding.
First sending module 603, the terminal transmission lock instruction that this target terminal mark being configured to determine to this first determination module is corresponding, this lock instruction is used to indicate and locks the application in terminal.
In sum, the locking device of a kind of application that disclosure embodiment provides, Cloud Server can receive the blacklist of breaking one's promise that application server sends, and records the user account that default discreditable behavior occurs in this blacklist of breaking one's promise.When there being newly-increased user account during this breaks one's promise blacklist, Cloud Server can determine the target terminal mark that this newly-increased user account is corresponding, and send lock instruction to the terminal that this target terminal mark is corresponding, this lock instruction is used to indicate and locks the application in terminal, therefore enriched and line-locked trigger mechanism has been entered to the application in terminal, and suitable disciplining as a warning is carried out to the discreditable behavior of user, the rate of breaking one's promise of user can be reduced.
Fig. 6-2 is the block diagrams of the locking device 600 that the another kind according to an exemplary embodiment is applied, and as in fig. 6-2, this device comprises:
First receiver module 601, is configured to the blacklist of breaking one's promise receiving application server transmission, records the user account that default discreditable behavior occurs in this blacklist of breaking one's promise.
First determination module 602, is configured to when there being newly-increased user account in this blacklist of breaking one's promise that this first receiver module receives, and determines the target terminal mark that this newly-increased user account is corresponding.
First sending module 603, the terminal transmission lock instruction that this target terminal mark being configured to determine to this first determination module is corresponding, this lock instruction is used to indicate and locks the application in terminal.
Second receiver module 604, is configured to the white list of breaking one's promise receiving application server transmission, records the user account occurring to preset releasing behavior of breaking one's promise in this white list of breaking one's promise.
Second determination module 605, is configured to determine the unlock terminal mark that this user account of breaking one's promise in white list that this second receiver module receives is corresponding.
Second sending module 606, the terminal transmission unlock command that this unlock terminal mark being configured to determine to this second determination module is corresponding, this unlock command is used to indicate and unlocks to the application in terminal.
Contrast module 607, whether the blacklist of breaking one's promise being configured to contrast the reception of this first receiver module is identical with the user account recorded in the blacklist of breaking one's promise prestored.
First detection module 608, be configured to this contrast module contrast this blacklist of breaking one's promise not identical with the user account recorded in this blacklist of breaking one's promise prestored time, detect this user account of breaking one's promise in blacklist and whether there is Unrecorded user account in this blacklist of breaking one's promise prestored.
3rd determination module 609, is configured to detect that this user account of breaking one's promise in blacklist exists Unrecorded user account in this blacklist of breaking one's promise prestored when this first detection module, this Unrecorded user account is defined as the user account that this is newly-increased.
3rd sending module 610, the terminal being configured to this target terminal mark correspondence determined to this first determination module sends mark of breaking one's promise, the terminal of this target terminal mark correspondence writes to the predeterminated position in operating system for mark of this being broken one's promise, this mark of breaking one's promise performs the predetermined registration operation to operating system for forbidding.
4th sending module 611, the terminal being configured to this unlock terminal mark correspondence determined to this second determination module sends mark erasing instruction of breaking one's promise, and will be arranged in breaking one's promise of operating system predeterminated position indicate erasing with the terminal making this unlock terminal identify correspondence according to this mark erasing instruction of breaking one's promise.
Second detection module 612, is configured to detect in this user account of breaking one's promise in blacklist prestored the user account whether existing and record in the white list of breaking one's promise of this second receiver module reception.
Removing module 613, there is the user account recorded in this white list of breaking one's promise if be configured in this user account of breaking one's promise in blacklist prestored of this second detection module detection, the user account recorded in white list of this being broken one's promise is deleted from this breaks one's promise blacklist.
Optionally, Fig. 6-3 is block diagrams of a kind of first sending module according to an exemplary embodiment, and as shown in Fig. 6-3, this first sending module 603, comprising: obtain submodule 6031, generate submodule 6032 and send submodule 6033;
This acquisition submodule 6031, is configured to obtain target application mark corresponding to this application server.
This generation submodule 6032, is configured to generate this lock instruction, and this lock instruction comprises this target application mark that this acquisition submodule obtains.
This transmission submodule 6033, be configured to this lock instruction sending the generation of this generation submodule to the terminal that this target terminal mark is corresponding, this lock instruction is used to indicate and locks other application in terminal except the application of this target application mark correspondence.
Optionally, what this target application mark that this acquisition submodule 6031 obtains was corresponding is applied as financial application, these other be applied as other financial application; Or, these other be applied as all application except the application corresponding except this target application mark of installing in terminal.
In sum, the locking device of a kind of application that disclosure embodiment provides, Cloud Server can receive the blacklist of breaking one's promise that application server sends, and records the user account that default discreditable behavior occurs in this blacklist of breaking one's promise.When there being newly-increased user account during this breaks one's promise blacklist, Cloud Server can determine the target terminal mark that this newly-increased user account is corresponding, and send lock instruction to the terminal that this target terminal mark is corresponding, this lock instruction is used to indicate and locks the application in terminal, therefore enriched and line-locked trigger mechanism has been entered to the application in terminal, and suitable disciplining as a warning is carried out to the discreditable behavior of user, the rate of breaking one's promise of user can be reduced.
Fig. 7-1 is the block diagram of another locking device 700 applied according to an exemplary embodiment, and as shown in Fig. 7-1, this device comprises:
First monitoring modular 701, whether the user account being configured to register in monitoring and measuring application server there is default discreditable behavior.
First logging modle 702, is configured to, when this default discreditable behavior occurs this user account of this first monitoring module monitors, be recorded to by this user account and break one's promise in blacklist.
First sending module 703, is configured to this blacklist of breaking one's promise sending this first logging modle record to Cloud Server.
In sum, the locking device of a kind of application that disclosure embodiment provides, whether the user account that application server can be registered in monitoring and measuring application server there is default discreditable behavior, when there is this default discreditable behavior in this user account, being recorded to by this user account breaks one's promise in blacklist, and send this blacklist of breaking one's promise to Cloud Server, so that cloud service sends lock instruction to the terminal that this user account is corresponding, this lock instruction is used to indicate and locks the application in terminal, therefore enriched and line-locked trigger mechanism has been entered to the application in terminal, and suitable disciplining as a warning is carried out to the discreditable behavior of user, the rate of breaking one's promise of user can be reduced.
Fig. 7-2 is block diagrams of another locking device 700 applied according to an exemplary embodiment, and as shown in Fig. 7-2, this device comprises:
First monitoring modular 701, whether the user account being configured to register in monitoring and measuring application server there is default discreditable behavior.
First logging modle 702, is configured to, when this default discreditable behavior occurs this user account of this first monitoring module monitors, be recorded to by this user account and break one's promise in blacklist.
First sending module 703, is configured to this blacklist of breaking one's promise sending this first logging modle record to Cloud Server.
Whether the second monitoring modular 704, be configured to monitor the user account recorded in this blacklist of breaking one's promise and occur to preset releasing behavior of breaking one's promise.
Second logging modle 705, the user account being configured to record in this blacklist of breaking one's promise of this second monitoring module monitors occur this preset break one's promise releasing behavior time, this user account is recorded to and breaks one's promise in white list.
Second sending module 706, is configured to this white list of breaking one's promise sending this second logging modle record to this Cloud Server.
Fig. 7-3 is block diagrams of a kind of first monitoring modular according to an exemplary embodiment, as shown in Fig. 7-3, this first monitoring modular 701, comprising: first obtains submodule 7011, first detection sub-module 7012, first judges that submodule 7013, first determines that submodule 7014 and second determines submodule 7015;
This first acquisition submodule 7011, is configured to the credit record obtaining this user account, records loaning bill information and the refund information of this user account in this credit record.
This first detection sub-module 7012, is configured to detect this and first obtains in this credit record that submodule obtains whether there is the loaning bill information of not refunding.
First judges submodule 7013, be configured to when this first obtain there is the loaning bill information of not refunding in this credit record that submodule obtains time, judge that the date of formation of this loaning bill information of not refunding is whether in predetermined period.
First determines submodule 7014, be configured to when this first judge that submodule judges that the date of formation of this loaning bill information of not refunding is in predetermined period time, determine that default discreditable behavior does not occur this user account.
Second determines submodule 7015, be configured to when this first judge that submodule judges that the date of formation of this loaning bill information of not refunding is not in predetermined period time, determine this user account occur preset discreditable behavior.
Fig. 7-4 is block diagrams of a kind of second monitoring modular according to an exemplary embodiment, as shown in Fig. 7-4, this second monitoring modular 704, comprising: second judges that submodule 7041, second obtains submodule 7042, the 3rd and judges that submodule 7043, the 3rd determines that submodule 7044 and the 4th determines submodule 7045.
This second judges submodule 7041, being configured to when monitoring arbitrary user account generation refund behavior of registering in this application server, judging whether the user account of this generation refund behavior is recorded in this and breaks one's promise in blacklist.
This second acquisition submodule 7042, be configured to when the user account of this generation refund behavior is recorded in this blacklist of breaking one's promise, obtain the credit record of the user account of this generation refund behavior, in this credit record, record loaning bill information and the refund information of this user account.
3rd judges submodule 7043, and whether the refund amount of money being configured to record in this refund information judging that this second acquisition submodule obtains is less than predetermined threshold value.
3rd determines submodule 7044, is configured to when the 3rd judges that submodule judges that this refund amount of money is less than this predetermined threshold value, determines that this user account does not occur to preset releasing behavior of breaking one's promise.
4th determines submodule 7045, is configured to when the 3rd judges that submodule judges that this refund amount of money is not less than this predetermined threshold value, determines that this user account occurs to preset releasing behavior of breaking one's promise.
Fig. 7-5 is block diagrams of another kind first monitoring modular according to an exemplary embodiment, and as shown in Fig. 7-5, this first monitoring modular 701, also comprises: first receives submodule 7016 and the 5th determines submodule 7017.
This first reception submodule 7016, the discreditable behavior reporting information that the terminal that the user account being configured to receive this registration logs in sends, this terminal is when continuous n false release action being detected, display authorization information input frame, this discreditable behavior reporting information is that this terminal detects that the authorization information of the user's input received at this authorization information input frame sends time different from the authorization information preset, and this n is for presetting integer value.
5th determines submodule 7017, is configured to this discreditable behavior reporting information received according to this first reception submodule, determines that this user account occurs to preset discreditable behavior.
Fig. 7-6 is block diagrams of another kind second monitoring modular according to an exemplary embodiment, and as shown in Fig. 7-6, this second monitoring modular 704, also comprises: second receives submodule 7046 and the 6th determines submodule 7047.
This second reception submodule 7046, releasing behavior of the breaking one's promise reporting information that the terminal that the user account being configured to receive this registration logs in sends, this terminal is when receiving unblock triggering command, display authorization information input frame, this releasing behavior reporting information of breaking one's promise is that this terminal detects that the authorization information of the user's input received in this authorization information input frame sends time identical with the authorization information preset.
6th determines submodule 7047, is configured to this releasing behavior reporting information of breaking one's promise received according to this second reception submodule, determines that this user account occurs to preset releasing behavior of breaking one's promise.
In sum, the locking device of a kind of application that disclosure embodiment provides, whether the user account that application server can be registered in monitoring and measuring application server there is default discreditable behavior, when there is this default discreditable behavior in this user account, being recorded to by this user account breaks one's promise in blacklist, and send this blacklist of breaking one's promise to Cloud Server, so that cloud service sends lock instruction to the terminal that this user account is corresponding, this lock instruction is used to indicate and locks the application in terminal, therefore enriched and line-locked trigger mechanism has been entered to the application in terminal, and suitable disciplining as a warning is carried out to the discreditable behavior of user, the rate of breaking one's promise of user can be reduced.
Fig. 8-1 is the block diagram of another locking device applied according to an exemplary embodiment, and as shown in Fig. 8-1, the locking device 800 of this application of installation comprises:
First receiver module 801, be configured to the lock instruction receiving Cloud Server transmission, to be this Cloud Server have during newly-increased user account this lock instruction in the blacklist of breaking one's promise that the application server received sends sends, this lock instruction is used to indicate and locks the application in terminal, records the user account that default discreditable behavior occurs in this blacklist of breaking one's promise.
Locking module 802, is configured to this lock instruction received according to this first receiver module, locks the application in terminal.
In sum, the locking device of a kind of application that disclosure embodiment provides, terminal can receive the lock instruction that Cloud Server sends, to be this Cloud Server have during newly-increased user account this lock instruction in the blacklist of breaking one's promise that the application server received sends sends, this lock instruction is used to indicate and locks the application in terminal, therefore enriched and line-locked trigger mechanism has been entered to the application in terminal, and suitable disciplining as a warning is carried out to the discreditable behavior of user, the rate of breaking one's promise of user can be reduced.
Fig. 8-2 is block diagrams of another locking device 800 applied according to an exemplary embodiment, and as shown in Fig. 8-2, this device comprises:
First receiver module 801, be configured to the lock instruction receiving Cloud Server transmission, to be this Cloud Server have during newly-increased user account this lock instruction in the blacklist of breaking one's promise that the application server received sends sends, this lock instruction is used to indicate and locks the application in terminal, records the user account that default discreditable behavior occurs in this blacklist of breaking one's promise.
Locking module 802, is configured to this lock instruction received according to this first receiver module, locks the application in terminal.
Second receiver module 803, be configured to the unlock command receiving Cloud Server transmission, this unlock command be this Cloud Server receive that application server sends break one's promise white list time send, this unlock command is used to indicate and unlocks to the application in terminal, records the user account occurring to preset releasing behavior of breaking one's promise in this white list of breaking one's promise.
Unlocked state 804, is configured to this unlock command received according to this second receiver module, unlocks to the application in this terminal.
3rd receiver module 805, is configured to the mark of breaking one's promise receiving Cloud Server transmission, and this mark of breaking one's promise performs the predetermined registration operation to operating system for forbidding.
Writing module 806, is configured to the predeterminated position write to by this mark of breaking one's promise that the 3rd receiver module receives in the operating system of this terminal.
4th receiver module 807, is configured to the mark erasing instruction of breaking one's promise receiving Cloud Server transmission.
First detection module 808, is configured to detect predeterminated position in this operating system and whether there is mark of breaking one's promise.
Erasing module 809, is configured to detect that this predeterminated position exists this mark of breaking one's promise when this first detection module, according to the mark erasing instruction of breaking one's promise that the 4th receiver module receives, will be arranged in the mark erasing of breaking one's promise of operating system predeterminated position.
First display module 810, is configured to when continuous n false release action being detected, and display authorization information input frame, this n is for presetting integer value.
5th receiver module 811, is configured to the authorization information receiving user's input in this authorization information input frame of this first display module display.
Second detection module 812, whether the authorization information being configured to detect this user input that the 5th receiver module receives is identical with the authorization information preset.
First sending module 813, is configured to, when this second detection module detects that the authorization information that this user inputs is different from the authorization information that this is preset, send discreditable behavior reporting information to application server.
Second display module 814, is configured to when receiving unblock triggering command, display authorization information input frame.
6th receiver module 815, is configured to the authorization information receiving user's input in this authorization information input frame of this second display module display.
3rd detection module 816, whether the authorization information being configured to detect this user input that the 6th receiver module receives is identical with the authorization information preset.
Second sending module 817, is configured to, when the 3rd detection module detects that the authorization information that this user inputs is identical with the authorization information that this is preset, send to application server releasing behavior reporting information of breaking one's promise.
Optionally, the lock instruction that this first receiver module 801 receives also comprises target application mark.
Fig. 8-3 is block diagrams of a kind of locking module according to an exemplary embodiment, and as shown in Fig. 8-3, this locking module 802, comprising: locking submodule 8021;
This locking submodule 8021, is configured to according to this lock instruction, locks other application in terminal except the application of this target application mark correspondence.
Optionally, what this target application mark was corresponding is applied as financial application, these other be applied as other financial application; Or, these other be applied as all application except the application corresponding except this target application mark of installing in terminal.
In sum, the locking device of a kind of application that disclosure embodiment provides, terminal can receive the lock instruction that Cloud Server sends, to be this Cloud Server have during newly-increased user account this lock instruction in the blacklist of breaking one's promise that the application server received sends sends, this lock instruction is used to indicate and locks the application in terminal, therefore enriched and line-locked trigger mechanism has been entered to the application in terminal, and suitable disciplining as a warning is carried out to the discreditable behavior of user, the rate of breaking one's promise of user can be reduced.
About the device in above-described embodiment, wherein the concrete mode of modules executable operations has been described in detail in about the embodiment of the method, will not elaborate explanation herein.
Fig. 9 is the block diagram of the locking device 900 of a kind of application according to an exemplary embodiment.Such as, device 900 may be provided in a server.With reference to Fig. 9, device 900 comprises processing components 922, and it comprises one or more processor further, and the memory resource representated by memory 932, such as, for storing the instruction that can be performed by processing unit 922, application program.The application program stored in memory 932 can comprise each module corresponding to one group of instruction one or more.In addition, processing components 922 is configured to perform instruction, and to perform the locking means of above-mentioned application, the method comprises:
Receive the blacklist of breaking one's promise that application server sends, in this blacklist of breaking one's promise, record the user account that default discreditable behavior occurs;
When there being newly-increased user account during this breaks one's promise blacklist, determine the target terminal mark that this newly-increased user account is corresponding;
The terminal corresponding to this target terminal mark sends lock instruction, and this lock instruction is used to indicate and locks the application in terminal.
Optionally, the method also comprises:
Receive the white list of breaking one's promise that application server sends, in this white list of breaking one's promise, record the user account occurring to preset releasing behavior of breaking one's promise;
Determine the unlock terminal mark that user account that this is broken one's promise in white list is corresponding;
The terminal corresponding to this unlock terminal mark sends unlock command, and this unlock command is used to indicate and unlocks to the application in terminal.
Optionally, this sends lock instruction to the terminal that this target terminal mark is corresponding, comprising:
Obtain the target application mark that this application server is corresponding;
Generate this lock instruction, this lock instruction comprises this target application mark;
The terminal corresponding to this target terminal mark sends this lock instruction, and this lock instruction is used to indicate and locks other application in terminal except the application of this target application mark correspondence.
Optionally, what this target application mark was corresponding is applied as financial application, these other be applied as other financial application;
Or, these other be applied as all application except the application corresponding except this target application mark of installing in terminal.
Optionally, the method also comprises:
Contrast this blacklist of breaking one's promise whether identical with the user account recorded in the blacklist of breaking one's promise prestored;
When this blacklist of breaking one's promise is not identical with the user account recorded in this blacklist of breaking one's promise prestored, detects this user account of breaking one's promise in blacklist and whether there is Unrecorded user account in this blacklist of breaking one's promise prestored;
If this user account of breaking one's promise in blacklist exists Unrecorded user account in this blacklist of breaking one's promise prestored, this Unrecorded user account is defined as the user account that this is newly-increased.
Optionally, the method also comprises:
Identify corresponding terminal to this target terminal and send mark of breaking one's promise, the terminal of this target terminal mark correspondence writes to the predeterminated position in operating system for mark of this being broken one's promise, and this mark of breaking one's promise performs the predetermined registration operation to operating system for forbidding.
Optionally, the method also comprises:
The terminal corresponding to this unlock terminal mark sends mark erasing instruction of breaking one's promise, and identifies corresponding terminal will be arranged in the mark erasing of breaking one's promise of operating system predeterminated position according to this mark erasing instruction of breaking one's promise to make this unlock terminal.
Optionally, the method also comprises:
Detect in this user account of breaking one's promise in blacklist prestored and whether there is the user account recorded in this white list of breaking one's promise;
If there is the user account recorded in this white list of breaking one's promise in the user account that what this prestored break one's promise in blacklist, the user account recorded in white list of this being broken one's promise is deleted from this breaks one's promise blacklist.
Device 900 can also comprise the power management that a power supply module 926 is configured to final controlling element 900, and a wired or wireless network interface 950 is configured to device 900 to be connected to network, and input and output (I/O) interface 958.Device 900 can operate the operating system based on being stored in memory 932, such as WindowsServerTM, MacOSXTM, UnixTM, LinuxTM, FreeBSDTM or similar.
In sum, the locking device of a kind of application that disclosure embodiment provides, Cloud Server can receive the blacklist of breaking one's promise that application server sends, and records the user account that default discreditable behavior occurs in this blacklist of breaking one's promise.When there being newly-increased user account during this breaks one's promise blacklist, Cloud Server can determine the target terminal mark that this newly-increased user account is corresponding, and send lock instruction to the terminal that this target terminal mark is corresponding, this lock instruction is used to indicate and locks the application in terminal, therefore enriched and line-locked trigger mechanism has been entered to the application in terminal, and suitable disciplining as a warning is carried out to the discreditable behavior of user, the rate of breaking one's promise of user can be reduced.
Figure 10 is the block diagram of the locking device 1000 of a kind of application according to an exemplary embodiment.Such as, device 1000 may be provided in a server.With reference to Figure 10, device 1000 comprises processing components 1022, and it comprises one or more processor further, and the memory resource representated by memory 1032, such as, for storing the instruction that can be performed by processing unit 1022, application program.The application program stored in memory 1032 can comprise each module corresponding to one group of instruction one or more.In addition, processing components 1022 is configured to perform instruction, and to perform the locking means of above-mentioned application, the method comprises:
Whether the user account registered in monitoring and measuring application server there is default discreditable behavior;
When this default discreditable behavior occurs this user account, this user account is recorded to and breaks one's promise in blacklist;
This blacklist of breaking one's promise is sent to Cloud Server.
Optionally, the method also comprises:
Monitor the user account recorded in this blacklist of breaking one's promise whether to occur to preset releasing behavior of breaking one's promise;
The user account recorded in this breaks one's promise blacklist occur this preset break one's promise releasing behavior time, this user account is recorded to and breaks one's promise in white list;
This white list of breaking one's promise is sent to this Cloud Server.
Optionally, whether the user account registered in monitoring and measuring application server there is default discreditable behavior, comprising:
Obtain the credit record of this user account, in this credit record, record loaning bill information and the refund information of this user account;
Detect in this credit record the loaning bill information whether existing and do not refund;
When there is the loaning bill information of not refunding in this credit record, judge that the date of formation of this loaning bill information of not refunding is whether in predetermined period;
When the date of formation of the loaning bill information that this is not refunded is in predetermined period, determine that default discreditable behavior does not occur this user account; Or,
When the date of formation of the loaning bill information that this is not refunded is not in predetermined period, determine that this user account occurs to preset discreditable behavior.
Optionally, whether the user account recorded in this blacklist of breaking one's promise of this monitoring occurs to preset releasing behavior of breaking one's promise, and comprising:
When monitoring arbitrary user account generation refund behavior of registering in this application server, judge whether the user account of this generation refund behavior is recorded in this and breaks one's promise in blacklist;
When the user account of this generation refund behavior is recorded in this blacklist of breaking one's promise, obtain the credit record of the user account of this generation refund behavior, in this credit record, record loaning bill information and the refund information of this user account;
Judge whether the refund amount of money recorded in this refund information is less than predetermined threshold value;
When this refund amount of money is less than this predetermined threshold value, determine that this user account does not occur to preset releasing behavior of breaking one's promise; Or,
When this refund amount of money is not less than this predetermined threshold value, determine that this user account occurs to preset releasing behavior of breaking one's promise.
Optionally, whether the user account registered in this monitoring and measuring application server there is default discreditable behavior, comprising:
The discreditable behavior reporting information that the terminal that the user account receiving this registration logs in sends, this terminal is when continuous n false release action being detected, display authorization information input frame, this discreditable behavior reporting information is that this terminal detects that the authorization information of the user's input received at this authorization information input frame sends time different from the authorization information preset, and this n is for presetting integer value;
According to this discreditable behavior reporting information, determine that this user account occurs to preset discreditable behavior.
Optionally, whether the user account recorded in this blacklist of breaking one's promise of this monitoring occurs to preset releasing behavior of breaking one's promise, and comprising:
Releasing behavior of the breaking one's promise reporting information that the terminal that the user account receiving this registration logs in sends, this terminal is when receiving unblock triggering command, display authorization information input frame, this releasing behavior reporting information of breaking one's promise is that this terminal detects that the authorization information of the user's input received in this authorization information input frame sends time identical with the authorization information preset;
According to this releasing behavior reporting information of breaking one's promise, determine that this user account occurs to preset releasing behavior of breaking one's promise.
Device 1000 can also comprise the power management that a power supply module 1026 is configured to final controlling element 1000, and a wired or wireless network interface 1050 is configured to device 1000 to be connected to network, and input and output (I/O) interface 1058.Device 1000 can operate the operating system based on being stored in memory 1032, such as WindowsServerTM, MacOSXTM, UnixTM, LinuxTM, FreeBSDTM or similar.
In sum, the locking device of a kind of application that disclosure embodiment provides, whether the user account that application server can be registered in monitoring and measuring application server there is default discreditable behavior, when there is this default discreditable behavior in this user account, being recorded to by this user account breaks one's promise in blacklist, and send this blacklist of breaking one's promise to Cloud Server, so that cloud service sends lock instruction to the terminal that this user account is corresponding, this lock instruction is used to indicate and locks the application in terminal, therefore enriched and line-locked trigger mechanism has been entered to the application in terminal, and suitable disciplining as a warning is carried out to the discreditable behavior of user, the rate of breaking one's promise of user can be reduced.
Figure 11 is the block diagram of the locking device 1100 of a kind of application according to an exemplary embodiment.Such as, device 1100 can be mobile phone, computer, digital broadcast terminal, messaging devices, game console, flat-panel devices, Medical Devices, body-building equipment, personal digital assistant etc.
With reference to Figure 11, device 1100 can comprise following one or more assembly: processing components 1102, memory 1104, power supply module 1106, multimedia groupware 1108, audio-frequency assembly 1110, the interface 1112 of I/O (I/O), sensor cluster 1114, and communications component 1116.
The integrated operation of the usual control device 1100 of processing components 1102, such as with display, call, data communication, camera operation and record operate the operation be associated.Processing components 1102 can comprise one or more processor 1120 to perform instruction, to complete all or part of step of above-mentioned method.In addition, processing components 1102 can comprise one or more module, and what be convenient between processing components 1102 and other assemblies is mutual.Such as, processing components 1102 can comprise multi-media module, mutual with what facilitate between multimedia groupware 1108 and processing components 1102.
Memory 1104 is configured to store various types of data to be supported in the operation of device 1100.The example of these data comprises for any application program of operation on device 1100 or the instruction of method, contact data, telephone book data, message, picture, video etc.Memory 1104 can be realized by the volatibility of any type or non-volatile memory device or their combination, as static RAM (SRAM), Electrically Erasable Read Only Memory (EEPROM), Erasable Programmable Read Only Memory EPROM (EPROM), programmable read only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, disk or CD.
The various assemblies that power supply module 1106 is device 1100 provide electric power.Power supply module 1106 can comprise power-supply management system, one or more power supply, and other and the assembly generating, manage and distribute electric power for device 1100 and be associated.
Multimedia groupware 1108 is included in the screen providing an output interface between described device 1100 and user.In certain embodiments, screen can comprise liquid crystal display (LCD) and touch panel (TP).If screen comprises touch panel, screen may be implemented as touch-screen, to receive the input signal from user.Touch panel comprises one or more touch sensor with the gesture on sensing touch, slip and touch panel.Described touch sensor can the border of not only sensing touch or sliding action, but also detects the duration relevant to described touch or slide and pressure.In certain embodiments, multimedia groupware 1108 comprises a front-facing camera and/or post-positioned pick-up head.When device 1100 is in operator scheme, during as screening-mode or video mode, front-facing camera and/or post-positioned pick-up head can receive outside multi-medium data.Each front-facing camera and post-positioned pick-up head can be fixing optical lens systems or have focal length and optical zoom ability.
Audio-frequency assembly 1110 is configured to export and/or input audio signal.Such as, audio-frequency assembly 1110 comprises a microphone (MIC), and when device 1100 is in operator scheme, during as call model, logging mode and speech recognition mode, microphone is configured to receive external audio signal.The audio signal received can be stored in memory 1104 further or be sent via communications component 1116.In certain embodiments, audio-frequency assembly 1110 also comprises a loud speaker, for output audio signal.
I/O interface 1112 is for providing interface between processing components 1102 and peripheral interface module, and above-mentioned peripheral interface module can be keyboard, some striking wheel, button etc.These buttons can include but not limited to: home button, volume button, start button and locking press button.
Sensor cluster 1114 comprises one or more transducer, for providing the state estimation of various aspects for device 1100.Such as, sensor cluster 1114 can detect the opening/closing state of device 1100, the relative positioning of assembly, such as described assembly is display and the keypad of device 1100, the position of all right checkout gear 1100 of sensor cluster 1114 or device 1100 assemblies changes, the presence or absence that user contacts with device 1100, the variations in temperature of device 1100 orientation or acceleration/deceleration and device 1100.Sensor cluster 1114 can comprise proximity transducer, be configured to without any physical contact time detect near the existence of object.Sensor cluster 1114 can also comprise optical sensor, as CMOS or ccd image sensor, for using in imaging applications.In certain embodiments, this sensor cluster 1114 can also comprise acceleration transducer, gyro sensor, Magnetic Sensor, pressure sensor or temperature sensor.
Communications component 1116 is configured to the communication being convenient to wired or wireless mode between device 1100 and other equipment.Device 1100 can access the wireless network based on communication standard, as WiFi, 2G or 3G, or their combination.In one exemplary embodiment, communications component 1116 receives from the broadcast singal of external broadcasting management system or broadcast related information via broadcast channel.In one exemplary embodiment, described communications component 1116 also comprises near-field communication (NFC) module, to promote junction service.Such as, can based on radio-frequency (RF) identification (RFID) technology in NFC module, Infrared Data Association (IrDA) technology, ultra broadband (UWB) technology, bluetooth (BT) technology and other technologies realize.
In the exemplary embodiment, device 1100 can be realized, for performing said method by one or more application specific integrated circuit (ASIC), digital signal processor (DSP), digital signal processing appts (DSPD), programmable logic device (PLD), field programmable gate array (FPGA), controller, microcontroller, microprocessor or other electronic components.
In the exemplary embodiment, additionally provide a kind of non-transitory computer-readable recording medium comprising instruction, such as, comprise the memory 1104 of instruction, above-mentioned instruction can perform said method by the processor 1120 of device 1100.Such as, described non-transitory computer-readable recording medium can be ROM, random access memory (RAM), CD-ROM, tape, floppy disk and optical data storage devices etc.
A kind of non-transitory computer-readable recording medium, when the instruction in described storage medium is performed by the processor of device 1100, make device 1100 can perform a kind of locking means of application, described method comprises:
Receive the lock instruction that Cloud Server sends, to be this Cloud Server have during newly-increased user account this lock instruction in the blacklist of breaking one's promise that the application server received sends sends, this lock instruction is used to indicate and locks the application in terminal, records the user account that default discreditable behavior occurs in this blacklist of breaking one's promise;
According to this lock instruction, the application in terminal is locked.
Optionally, the method also comprises:
Receive the unlock command that Cloud Server sends, this unlock command be this Cloud Server receive that application server sends break one's promise white list time send, this unlock command is used to indicate and unlocks to the application in terminal, records the user account occurring to preset releasing behavior of breaking one's promise in this white list of breaking one's promise;
According to this unlock command, the application in this terminal is unlocked.
Optionally, this lock instruction also comprises target application mark, and this locks the application in terminal according to this lock instruction, comprising:
According to this lock instruction, other application in terminal except the application of this target application mark correspondence are locked.
Optionally, what this target application mark was corresponding is applied as financial application, these other be applied as other financial application;
Or, these other be applied as all application except the application corresponding except this target application mark of installing in terminal.
Optionally, the method also comprises:
Receive the mark of breaking one's promise that Cloud Server sends, this mark of breaking one's promise performs the predetermined registration operation to operating system for forbidding;
Mark of this being broken one's promise writes to the predeterminated position in the operating system of this terminal.
Optionally, the method also comprises:
Receive the mark erasing instruction of breaking one's promise that Cloud Server sends;
Detect predeterminated position in this operating system and whether there is mark of breaking one's promise;
When this predeterminated position exists this mark of breaking one's promise, according to this mark erasing instruction of breaking one's promise, the mark erasing of breaking one's promise of operating system predeterminated position will be arranged in.
Optionally, the method also comprises:
When continuous n false release action being detected, display authorization information input frame, this n is for presetting integer value;
The authorization information of user's input is received in this authorization information input frame;
Whether the authorization information detecting this user input is identical with the authorization information preset;
When the authorization information that this user inputs is identical with the authorization information that this is preset, send discreditable behavior reporting information to application server.
Optionally, the method also comprises:
When receiving unblock triggering command, display authorization information input frame;
The authorization information of user's input is received in this authorization information input frame;
Whether the authorization information detecting this user input is identical with the authorization information preset;
When the authorization information that this user inputs is identical with the authorization information that this is preset, send to application server releasing behavior reporting information of breaking one's promise.
In sum, the locking device of a kind of application that disclosure embodiment provides, terminal can receive the lock instruction that Cloud Server sends, to be this Cloud Server have during newly-increased user account this lock instruction in the blacklist of breaking one's promise that the application server received sends sends, this lock instruction is used to indicate and locks the application in terminal, therefore enriched and line-locked trigger mechanism has been entered to the application in terminal, and suitable disciplining as a warning is carried out to the discreditable behavior of user, the rate of breaking one's promise of user can be reduced.
Those skilled in the art, at consideration specification and after putting into practice invention disclosed herein, will easily expect other embodiment of the present disclosure.The application is intended to contain any modification of the present disclosure, purposes or adaptations, and these modification, purposes or adaptations are followed general principle of the present disclosure and comprised the undocumented common practise in the art of the disclosure or conventional techniques means.Specification and embodiment are only regarded as exemplary, and true scope of the present disclosure and spirit are pointed out by claim below.
Should be understood that, the disclosure is not limited to precision architecture described above and illustrated in the accompanying drawings, and can carry out various amendment and change not departing from its scope.The scope of the present disclosure is only limited by appended claim.
Claims (49)
1. a locking means for application, it is characterized in that, described method comprises:
Receive the blacklist of breaking one's promise that application server sends, described in break one's promise in blacklist and record the user account that default discreditable behavior occurs;
When there being newly-increased user account in described blacklist of breaking one's promise, determine the target terminal mark that described newly-increased user account is corresponding;
The terminal corresponding to described target terminal mark sends lock instruction, and described lock instruction is used to indicate and locks the application in terminal.
2. method according to claim 1, is characterized in that, described method also comprises:
Receive the white list of breaking one's promise that application server sends, described in break one's promise the user account recording in white list and occur to preset releasing behavior of breaking one's promise;
The unlock terminal mark that the user account of breaking one's promise described in determining in white list is corresponding;
The terminal corresponding to described unlock terminal mark sends unlock command, and described unlock command is used to indicate and unlocks to the application in terminal.
3. method according to claim 1, is characterized in that, the described terminal corresponding to described target terminal mark sends lock instruction, comprising:
Obtain the target application mark that described application server is corresponding;
Generate described lock instruction, described lock instruction comprises described target application mark;
The terminal corresponding to described target terminal mark sends described lock instruction, and described lock instruction is used to indicate and locks other application in terminal except the application of described target application mark correspondence.
4. method according to claim 3, is characterized in that, what described target application mark was corresponding is applied as financial application, and described other are applied as other financial application;
Or described other are applied as all application except the application of described target application mark correspondence of installing in terminal.
5. method according to claim 1, is characterized in that, described method also comprises:
Whether blacklist of breaking one's promise described in contrast is identical with the user account recorded in the blacklist of breaking one's promise prestored;
When described blacklist of breaking one's promise is not identical with the user account recorded in the described blacklist of breaking one's promise prestored, Unrecorded user account in the blacklist of breaking one's promise prestored described in whether the user account of breaking one's promise described in detection in blacklist exists;
If described in break one's promise user account in blacklist exist described in Unrecorded user account in the blacklist of breaking one's promise that prestores, described Unrecorded user account is defined as described newly-increased user account.
6. method according to claim 1, is characterized in that, described method also comprises:
The terminal corresponding to described target terminal mark sends mark of breaking one's promise, and identifies corresponding terminal described mark of breaking one's promise write to predeterminated position in operating system to make described target terminal, described in break one's promise mark for forbidding the predetermined registration operation of execution to operating system.
7. method according to claim 2, is characterized in that, described method also comprises:
The terminal corresponding to described unlock terminal mark sends mark erasing instruction of breaking one's promise, with make described unlock terminal identify corresponding terminal according to described in the mark of breaking one's promise that mark erasing instruction will be arranged in operating system predeterminated position of breaking one's promise wipe.
8. method according to claim 2, is characterized in that, described method also comprises:
Detect in the user account of breaking one's promise in blacklist that prestores the user account recorded in white list of breaking one's promise described in whether existing;
If described in exist in the user account of breaking one's promise in blacklist that prestores described in break one's promise the user account recorded in white list, then the user account recorded in described white list of breaking one's promise is deleted from described blacklist of breaking one's promise.
9. a locking means for application, it is characterized in that, described method comprises:
Whether the user account registered in monitoring and measuring application server there is default discreditable behavior;
When described default discreditable behavior occurs described user account, described user account is recorded to and breaks one's promise in blacklist;
To blacklist of breaking one's promise described in Cloud Server transmission.
10. method according to claim 9, is characterized in that, described method also comprises:
Whether the user account recorded in blacklist of breaking one's promise described in monitoring occurs to preset releasing behavior of breaking one's promise;
The user account that records in described blacklist of breaking one's promise occurs describedly to preset when breaking one's promise releasing behavior, is recorded to by described user account and breaks one's promise in white list;
To white list of breaking one's promise described in described Cloud Server transmission.
11. methods according to claim 9, is characterized in that, whether the user account registered in described monitoring and measuring application server default discreditable behavior occurs, and comprising:
Obtain the credit record of described user account, in described credit record, record loaning bill information and the refund information of described user account;
Detect in described credit record the loaning bill information whether existing and do not refund;
When there is the loaning bill information of not refunding in described credit record, whether date of formation of the loaning bill information of not refunding described in judgement is in predetermined period;
When the date of formation of described loaning bill information of not refunding is in predetermined period, determine that default discreditable behavior does not occur described user account; Or,
When the date of formation of described loaning bill information of not refunding is not in predetermined period, determine that described user account occurs to preset discreditable behavior.
12. methods according to claim 10, is characterized in that, whether the user account recorded in blacklist of breaking one's promise described in described monitoring occurs to preset releasing behavior of breaking one's promise, and comprising:
When monitoring arbitrary user account generation refund behavior of registering in described application server, judge the user account of described generation refund behavior is broken one's promise in blacklist described in whether being recorded in;
When in blacklist of breaking one's promise described in the user account of described generation refund behavior is recorded in, obtain the credit record of the user account of described generation refund behavior, in described credit record, record loaning bill information and the refund information of described user account;
Judge whether the refund amount of money recorded in described refund information is less than predetermined threshold value;
When the described refund amount of money is less than described predetermined threshold value, determine that described user account does not occur to preset releasing behavior of breaking one's promise; Or,
When the described refund amount of money is not less than described predetermined threshold value, determine that described user account occurs to preset releasing behavior of breaking one's promise.
13. methods according to claim 9, is characterized in that, whether the user account registered in described monitoring and measuring application server default discreditable behavior occurs, and comprising:
The discreditable behavior reporting information that the terminal that the user account receiving described registration logs in sends, described terminal is when continuous n false release action being detected, display authorization information input frame, described discreditable behavior reporting information is that described terminal detects that the authorization information of the user's input received at described authorization information input frame sends time different from the authorization information preset, and described n is for presetting integer value;
According to described discreditable behavior reporting information, determine that described user account occurs to preset discreditable behavior.
14. methods according to claim 10, is characterized in that, whether the user account recorded in blacklist of breaking one's promise described in described monitoring occurs to preset releasing behavior of breaking one's promise, and comprising:
Releasing behavior of the breaking one's promise reporting information that the terminal that the user account receiving described registration logs in sends, described terminal is when receiving unblock triggering command, display authorization information input frame, described in releasing behavior reporting information of breaking one's promise be that described terminal detects that the authorization information of the user's input received in described authorization information input frame sends time identical with default authorization information;
According to described releasing behavior reporting information of breaking one's promise, determine that described user account occurs to preset releasing behavior of breaking one's promise.
The locking means of 15. 1 kinds of application, it is characterized in that, described method comprises:
Receive the lock instruction that Cloud Server sends, to be described Cloud Server have during newly-increased user account described lock instruction in the blacklist of breaking one's promise that the application server received sends sends, described lock instruction is used to indicate and locks the application in terminal, described in break one's promise in blacklist and record the user account that default discreditable behavior occurs;
According to described lock instruction, the application in terminal is locked.
16. methods according to claim 15, is characterized in that, described method also comprises:
Receive the unlock command that Cloud Server sends, described unlock command be described Cloud Server receive that application server sends break one's promise white list time send, described unlock command is used to indicate and unlocks to the application in terminal, described in break one's promise the user account recording in white list and occur to preset releasing behavior of breaking one's promise;
According to described unlock command, the application in described terminal is unlocked.
17. methods according to claim 15, is characterized in that, described lock instruction also comprises target application mark, described according to described lock instruction, locks, comprising the application in terminal:
According to described lock instruction, other application in terminal except the application of described target application mark correspondence are locked.
18. methods according to claim 17, is characterized in that, what described target application mark was corresponding is applied as financial application, and described other are applied as other financial application;
Or described other are applied as all application except the application of described target application mark correspondence of installing in terminal.
19. methods according to claim 15, is characterized in that, described method also comprises:
Receive the mark of breaking one's promise that Cloud Server sends, described in break one's promise mark for forbidding the predetermined registration operation of execution to operating system;
Described mark of breaking one's promise is write to the predeterminated position in the operating system of described terminal.
20. methods according to claim 16, is characterized in that, described method also comprises:
Receive the mark erasing instruction of breaking one's promise that Cloud Server sends;
Detect predeterminated position in described operating system and whether there is mark of breaking one's promise;
When mark of breaking one's promise described in described predeterminated position existence, according to described mark erasing instruction of breaking one's promise, the mark erasing of breaking one's promise of operating system predeterminated position will be arranged in.
21. methods according to claim 15, is characterized in that, described method also comprises:
When continuous n false release action being detected, display authorization information input frame, described n is for presetting integer value;
The authorization information of user's input is received in described authorization information input frame;
Whether the authorization information detecting described user input is identical with the authorization information preset;
When the authorization information that described user inputs is identical with described default authorization information, send discreditable behavior reporting information to application server.
22. methods according to claim 15, is characterized in that, described method also comprises:
When receiving unblock triggering command, display authorization information input frame;
The authorization information of user's input is received in described authorization information input frame;
Whether the authorization information detecting described user input is identical with the authorization information preset;
When the authorization information that described user inputs is identical with described default authorization information, send to application server releasing behavior reporting information of breaking one's promise.
The locking device of 23. 1 kinds of application, it is characterized in that, described device comprises:
First receiver module, is configured to receive the blacklist of breaking one's promise that application server sends, described in break one's promise in blacklist and record the user account that default discreditable behavior occurs;
First determination module, is configured to, when there being newly-increased user account in blacklist of breaking one's promise described in described first receiver module receives, determine the target terminal mark that described newly-increased user account is corresponding;
First sending module, the terminal transmission lock instruction that the described target terminal mark being configured to determine to described first determination module is corresponding, described lock instruction is used to indicate and locks the application in terminal.
24. devices according to claim 23, is characterized in that, described device also comprises: the second receiver module, the second determination module, the second sending module;
Described second receiver module, is configured to receive the white list of breaking one's promise that application server sends, described in break one's promise the user account recording in white list and occur to preset releasing behavior of breaking one's promise;
Described second determination module, the unlock terminal mark that the user account being configured to determine to break one's promise in white list described in described second receiver module reception is corresponding;
Described second sending module, the terminal transmission unlock command that the described unlock terminal mark being configured to determine to described second determination module is corresponding, described unlock command is used to indicate and unlocks to the application in terminal.
25. devices according to claim 23, is characterized in that, described first sending module, comprising: obtain submodule, generate submodule and send submodule;
Described acquisition submodule, is configured to obtain target application mark corresponding to described application server;
Described generation submodule, is configured to generate described lock instruction, and described lock instruction comprises the described target application mark that described acquisition submodule obtains;
Described transmission submodule, be configured to the described lock instruction sending the generation of described generation submodule to the terminal that described target terminal mark is corresponding, described lock instruction is used to indicate and locks other application in terminal except the application of described target application mark correspondence.
26. devices according to claim 25, is characterized in that, what the described target application mark that described acquisition submodule obtains was corresponding is applied as financial application, and described other are applied as other financial application;
Or described other are applied as all application except the application of described target application mark correspondence of installing in terminal.
27. devices according to claim 23, is characterized in that, described device also comprises: contrast module, first detection module and the 3rd determination module;
Described contrast module, be configured to described first receiver module of contrast receive described in blacklist of breaking one's promise whether identical with the user account recorded in the blacklist of breaking one's promise prestored;
Described first detection module, be configured to when blacklist of breaking one's promise described in described contrast module contrasts is not identical with the user account recorded in the described blacklist of breaking one's promise prestored, Unrecorded user account in the blacklist of breaking one's promise prestored described in whether the user account of breaking one's promise described in detection in blacklist exists;
Described 3rd determination module, Unrecorded user account in the blacklist of breaking one's promise prestored described in the user account being configured to break one's promise in blacklist described in detecting when described first detection module exists, is defined as described newly-increased user account by described Unrecorded user account.
28. devices according to claim 23, is characterized in that, described device also comprises: the 3rd sending module;
Described 3rd sending module, the terminal being configured to the described target terminal mark correspondence determined to described first determination module sends mark of breaking one's promise, identify corresponding terminal to make described target terminal and described mark of breaking one's promise write to predeterminated position in operating system, described in mark of breaking one's promise perform the predetermined registration operation to operating system for forbidding.
29. devices according to claim 24, is characterized in that, described device also comprises: the 4th sending module;
Described 4th sending module, terminal corresponding to the described unlock terminal mark being configured to determine to described second determination module sends mark erasing instruction of breaking one's promise, with make described unlock terminal identify corresponding terminal according to described in the mark of breaking one's promise that mark erasing instruction will be arranged in operating system predeterminated position of breaking one's promise wipe.
30. devices according to claim 24, is characterized in that, described device also comprises: the second detection module and removing module;
Described second detection module, be configured to detect in the user account of breaking one's promise in blacklist prestored whether exist described second receiver module receive described in break one's promise the user account recorded in white list;
Described removing module, if be configured to described second detection module detect described in exist in the user account of breaking one's promise in blacklist that prestores described in break one's promise the user account recorded in white list, then the user account recorded in described white list of breaking one's promise is deleted from described blacklist of breaking one's promise.
The locking device of 31. 1 kinds of application, it is characterized in that, described device comprises:
First monitoring modular, whether the user account being configured to register in monitoring and measuring application server there is default discreditable behavior;
First logging modle, is configured to, when described default discreditable behavior occurs the described user account of described first monitoring module monitors, be recorded to by described user account and break one's promise in blacklist;
First sending module, is configured to blacklist of breaking one's promise described in the described first logging modle record of Cloud Server transmission.
32. devices according to claim 31, is characterized in that, described device also comprises: the second monitoring modular, the second logging modle and the second sending module;
Described second monitoring modular, whether the user account that being configured to breaks one's promise described in monitoring records in blacklist occurs to preset releasing behavior of breaking one's promise;
Described second logging modle, is configured to the user account that records in blacklist of breaking one's promise described in described second monitoring module monitors and occurs describedly to preset when breaking one's promise releasing behavior, be recorded to by described user account and break one's promise in white list;
Described second sending module, is configured to white list of breaking one's promise described in the described second logging modle record of described Cloud Server transmission.
33. devices according to claim 31, is characterized in that, described first monitoring modular, comprising: the first acquisition submodule, the first detection sub-module, first judge that submodule, first determines that submodule and second determines submodule;
Described first obtains submodule, is configured to the credit record obtaining described user account, records loaning bill information and the refund information of described user account in described credit record;
Described first detection sub-module, is configured to detect described first and obtains in the described credit record of submodule acquisition whether there is the loaning bill information of not refunding;
Described first judges submodule, be configured to when described first obtain there is the loaning bill information of not refunding in the described credit record that submodule obtains time, whether date of formation of the loaning bill information of not refunding described in judgement in predetermined period;
Described first determines submodule, be configured to when described first judge submodule judge described in date of formation of loaning bill information of not refunding in predetermined period time, determine that default discreditable behavior does not occur described user account;
Described second determines submodule, be configured to when described first judge submodule judge described in date of formation of loaning bill information of not refunding not in predetermined period time, determine that described user account occurs to preset discreditable behavior.
34. devices according to claim 32, is characterized in that, described second monitoring modular, comprising: second judges that submodule, second obtains submodule, the 3rd and judges that submodule, the 3rd determines that submodule and the 4th determines submodule;
Described second judges submodule, is configured to when monitoring arbitrary user account generation refund behavior of registering in described application server, judges the user account of described generation refund behavior is broken one's promise in blacklist described in whether being recorded in;
Described second obtains submodule, be configured to when in blacklist of breaking one's promise described in the user account of described generation refund behavior is recorded in, obtain the credit record of the user account of described generation refund behavior, in described credit record, record loaning bill information and the refund information of described user account;
Described 3rd judges submodule, and whether the refund amount of money being configured to record in the described refund information judging that described second acquisition submodule obtains is less than predetermined threshold value;
Described 3rd determines submodule, is configured to when the described 3rd judges that submodule judges that the described refund amount of money is less than described predetermined threshold value, determines that described user account does not occur to preset releasing behavior of breaking one's promise;
Described 4th determines submodule, is configured to when the described 3rd judges that submodule judges that the described refund amount of money is not less than described predetermined threshold value, determines that described user account occurs to preset releasing behavior of breaking one's promise.
35. devices according to claim 31, is characterized in that, described first monitoring modular, also comprises: first receives submodule and the 5th determines submodule;
Described first receives submodule, the discreditable behavior reporting information that the terminal that the user account being configured to receive described registration logs in sends, described terminal is when continuous n false release action being detected, display authorization information input frame, described discreditable behavior reporting information is that described terminal detects that the authorization information of the user's input received at described authorization information input frame sends time different from the authorization information preset, and described n is for presetting integer value;
Described 5th determines submodule, is configured to the described discreditable behavior reporting information receiving submodule reception according to described first, determines that described user account occurs to preset discreditable behavior.
36. devices according to claim 32, is characterized in that, described second monitoring modular, also comprises: second receives submodule and the 6th determines submodule;
Described second receives submodule, releasing behavior of the breaking one's promise reporting information that the terminal that the user account being configured to receive described registration logs in sends, described terminal is when receiving unblock triggering command, display authorization information input frame, described in releasing behavior reporting information of breaking one's promise be that described terminal detects that the authorization information of the user's input received in described authorization information input frame sends time identical with default authorization information;
Described 6th determines submodule, is configured to break one's promise releasing behavior reporting information according to described second reception submodule reception, determines that described user account occurs to preset releasing behavior of breaking one's promise.
The locking device of 37. 1 kinds of application, it is characterized in that, described device comprises:
First receiver module, be configured to the lock instruction receiving Cloud Server transmission, to be described Cloud Server have during newly-increased user account described lock instruction in the blacklist of breaking one's promise that the application server received sends sends, described lock instruction is used to indicate and locks the application in terminal, described in break one's promise in blacklist and record the user account that default discreditable behavior occurs;
Locking module, is configured to the described lock instruction received according to described first receiver module, locks the application in terminal.
38., according to device according to claim 37, is characterized in that, described device also comprises: the second receiver module and unlocked state;
Described second receiver module, be configured to the unlock command receiving Cloud Server transmission, described unlock command be described Cloud Server receive that application server sends break one's promise white list time send, described unlock command is used to indicate and unlocks to the application in terminal, described in break one's promise the user account recording in white list and occur to preset releasing behavior of breaking one's promise;
Described unlocked state, is configured to the described unlock command received according to described second receiver module, unlocks to the application in described terminal.
39., according to device according to claim 37, is characterized in that,
The lock instruction that described first receiver module receives also comprises target application mark;
Described locking module, comprising: locking submodule;
Described locking submodule, is configured to according to described lock instruction, locks other application in terminal except the application of described target application mark correspondence.
40., according to device according to claim 39, is characterized in that, what described target application mark was corresponding is applied as financial application, and described other are applied as other financial application;
Or described other are applied as all application except the application of described target application mark correspondence of installing in terminal.
41., according to device according to claim 37, is characterized in that, described device also comprises: the 3rd receiver module and writing module;
Described 3rd receiver module, is configured to receive the mark of breaking one's promise that Cloud Server sends, described in break one's promise mark for forbidding the predetermined registration operation of execution to operating system;
Said write module, is configured to the predeterminated position write to by mark of breaking one's promise described in described 3rd receiver module reception in the operating system of described terminal.
42., according to device according to claim 38, is characterized in that, described device also comprises: the 4th receiver module, first detection module and erasing module;
Described 4th receiver module, is configured to the mark erasing instruction of breaking one's promise receiving Cloud Server transmission;
Described first detection module, is configured to detect predeterminated position in described operating system and whether there is mark of breaking one's promise;
Described erasing module, is configured to when described first detection module detects that described predeterminated position to be broken one's promise mark described in existing, and according to the mark erasing instruction of breaking one's promise that described 4th receiver module receives, the mark of breaking one's promise that will be arranged in operating system predeterminated position is wiped.
43., according to device according to claim 37, is characterized in that, described device also comprises: the first display module, the 5th receiver module, the second detection module and the first sending module;
Described first display module, is configured to when continuous n false release action being detected, display authorization information input frame, and described n is for presetting integer value;
Described 5th receiver module, is configured to the authorization information receiving user's input in the described authorization information input frame of described first display module display;
Described second detection module, whether the authorization information being configured to detect described user's input that described 5th receiver module receives is identical with the authorization information preset;
Described first sending module, is configured to when described second detection module detects that the authorization information that described user inputs is different from described default authorization information, sends discreditable behavior reporting information to application server.
44., according to device according to claim 37, is characterized in that, described device also comprises: the second display module, the 6th receiver module, the 3rd detection module and the second sending module;
Described second display module, is configured to when receiving unblock triggering command, display authorization information input frame;
Described 6th receiver module, is configured to the authorization information receiving user's input in the described authorization information input frame of described second display module display;
Described 3rd detection module, whether the authorization information being configured to detect described user's input that described 6th receiver module receives is identical with the authorization information preset;
Described second sending module, is configured to when described 3rd detection module detects that the authorization information that described user inputs is identical with described default authorization information, sends to application server releasing behavior reporting information of breaking one's promise.
The locking device of 45. 1 kinds of application, is characterized in that, comprising:
Processor;
For storing the memory of the executable instruction of described processor;
Wherein, described processor is configured to:
Receive the blacklist of breaking one's promise that application server sends, described in break one's promise in blacklist and record the user account that default discreditable behavior occurs;
When there being newly-increased user account in described blacklist of breaking one's promise, determine the target terminal mark that described newly-increased user account is corresponding;
The terminal corresponding to described target terminal mark sends lock instruction, and described lock instruction is used to indicate and locks the application in terminal.
The locking device of 46. 1 kinds of application, is characterized in that, comprising:
Processor;
For storing the memory of the executable instruction of described processor;
Wherein, described processor is configured to:
Whether the user account registered in monitoring and measuring application server there is default discreditable behavior;
When described default discreditable behavior occurs described user account, described user account is recorded to and breaks one's promise in blacklist;
To blacklist of breaking one's promise described in Cloud Server transmission.
The locking device of 47. 1 kinds of application, is characterized in that, comprising:
Processor;
For storing the memory of the executable instruction of described processor;
Wherein, described processor is configured to:
Receive the lock instruction that Cloud Server sends, to be described Cloud Server have during newly-increased user account described lock instruction in the blacklist of breaking one's promise that the application server received sends sends, described lock instruction is used to indicate and locks the application in terminal, described in break one's promise in blacklist and record the user account that default discreditable behavior occurs;
According to described lock instruction, the application in terminal is locked.
The locking system of 48. 1 kinds of application, it is characterized in that, described system comprises: Cloud Server, application server and terminal;
Described Cloud Server comprises the locking device of the arbitrary described application of claim 23 to 30;
Described application server comprises the locking device of the arbitrary described application of claim 31 to 36;
Described terminal comprises the locking device of the arbitrary described application of claim 37 to 44.
The locking system of 49. 1 kinds of application, it is characterized in that, described system comprises: Cloud Server, application server and terminal;
Described Cloud Server comprises the locking device of application according to claim 45;
Described application server comprises the locking device of application according to claim 46;
Described terminal comprises the locking device of application according to claim 47.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510642859.7A CN105245517B (en) | 2015-09-30 | 2015-09-30 | Locking means, the apparatus and system of application |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510642859.7A CN105245517B (en) | 2015-09-30 | 2015-09-30 | Locking means, the apparatus and system of application |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN105245517A true CN105245517A (en) | 2016-01-13 |
| CN105245517B CN105245517B (en) | 2018-06-12 |
Family
ID=55043017
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201510642859.7A Active CN105245517B (en) | 2015-09-30 | 2015-09-30 | Locking means, the apparatus and system of application |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN105245517B (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106920163A (en) * | 2016-08-23 | 2017-07-04 | 阿里巴巴集团控股有限公司 | The method and apparatus for releasing account restriction |
| CN111163215A (en) * | 2019-12-11 | 2020-05-15 | 上海传英信息技术有限公司 | Application running method, terminal and computer readable storage medium |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101114907A (en) * | 2006-07-28 | 2008-01-30 | 腾讯科技（深圳）有限公司 | Method and system for managing and filtering black list |
| EP2076057A1 (en) * | 2006-10-13 | 2009-07-01 | Huawei Technologies Co., Ltd. | Method, system and device for realizing information locking |
| CN101772006A (en) * | 2009-12-30 | 2010-07-07 | 中兴通讯股份有限公司 | Method and system for locking mobile terminal based on device management protocol |
| CN102244858A (en) * | 2011-08-01 | 2011-11-16 | 王冬梅 | Method for mobile terminal to possess communication function of locking and unlocking, and mobile terminal thereof |
| CN104219196A (en) * | 2013-05-29 | 2014-12-17 | 腾讯科技（深圳）有限公司 | Service locking method, service unlocking method, device and system |
-
2015
- 2015-09-30 CN CN201510642859.7A patent/CN105245517B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101114907A (en) * | 2006-07-28 | 2008-01-30 | 腾讯科技（深圳）有限公司 | Method and system for managing and filtering black list |
| EP2076057A1 (en) * | 2006-10-13 | 2009-07-01 | Huawei Technologies Co., Ltd. | Method, system and device for realizing information locking |
| CN101772006A (en) * | 2009-12-30 | 2010-07-07 | 中兴通讯股份有限公司 | Method and system for locking mobile terminal based on device management protocol |
| CN102244858A (en) * | 2011-08-01 | 2011-11-16 | 王冬梅 | Method for mobile terminal to possess communication function of locking and unlocking, and mobile terminal thereof |
| CN104219196A (en) * | 2013-05-29 | 2014-12-17 | 腾讯科技（深圳）有限公司 | Service locking method, service unlocking method, device and system |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106920163A (en) * | 2016-08-23 | 2017-07-04 | 阿里巴巴集团控股有限公司 | The method and apparatus for releasing account restriction |
| CN111163215A (en) * | 2019-12-11 | 2020-05-15 | 上海传英信息技术有限公司 | Application running method, terminal and computer readable storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN105245517B (en) | 2018-06-12 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN104238875A (en) | Application corner mark addition method and device | |
| CN105847243B (en) | Method and device for accessing intelligent camera | |
| CN105653323A (en) | Application program management method and device | |
| CN104008348A (en) | Application program control method, application program control device and terminal | |
| CN105160239A (en) | Application program access restriction method and apparatus | |
| CN105550860A (en) | Payment method and device | |
| CN103986833A (en) | Abnormal condition monitoring method and device | |
| CN103888601B (en) | Information prompting method, device and terminal | |
| CN103914337B (en) | Service calling method, device and terminal | |
| CN105072079A (en) | Account logon method, account logon device and terminal device | |
| CN106454392A (en) | Live broadcast processing method, device and terminal | |
| CN110400405B (en) | Method, device and medium for controlling access control | |
| CN105204804A (en) | Mode switching method, device and system | |
| CN105678549A (en) | Payment method and device | |
| CN105553963A (en) | Control method and device of positioning services | |
| CN104951377A (en) | Exception handling method and device for smart home terminal | |
| CN105654533A (en) | Picture editing method and picture editing device | |
| CN105335062A (en) | Information editing operation processing method and apparatus | |
| CN105068848A (en) | System upgrading method and apparatus | |
| CN108804244A (en) | Data transmission method for uplink, device and storage medium | |
| CN104125267A (en) | Account protection method, device and terminal equipment | |
| CN106021072A (en) | Information display method and device | |
| CN105487758A (en) | Method and device for popup control of application software, and terminal equipment | |
| CN104615931A (en) | Prompt dialog box display control method and device | |
| CN107341657A (en) | Payment process method, apparatus and terminal based on application program |
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 |