CN107395673B - User risk notification method and system and storage device - Google Patents
User risk notification method and system and storage device Download PDFInfo
- Publication number
- CN107395673B CN107395673B CN201710445583.2A CN201710445583A CN107395673B CN 107395673 B CN107395673 B CN 107395673B CN 201710445583 A CN201710445583 A CN 201710445583A CN 107395673 B CN107395673 B CN 107395673B
- Authority
- CN
- China
- Prior art keywords
- user
- risk
- terminal
- risk notification
- user identifier
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- 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/75—Indicating network or usage conditions on the user display
-
- 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/535—Tracking the activity of the user
-
- 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/55—Push-based network services
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Hardware Design (AREA)
- General Engineering & Computer Science (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The embodiment of the invention discloses a user risk notification method, a user risk notification system and storage equipment, which are applied to the technical field of communication. In the method of this embodiment, when an application terminal (for example, a first user terminal) of a first user has a risk or is in risk activity, a user risk notification system sends first risk notification information to terminals of multiple users, that is, user terminals corresponding to a first application terminal and a second user identifier. Therefore, the risk of the first application terminal of a plurality of users can be reminded, so that the plurality of users can carry out certain treatment on the first application terminal to avoid the risk, and the risk avoiding probability is increased.
Description
Technical Field
The present invention relates to the field of communications technologies, and in particular, to a user risk notification method and system, and a storage device.
Background
With the rise of the internet, fraud based on the internet is bred, and the old people lacking network experience and children involved in the world are most easily cheated among internet users, so that the fraud behaviors specially aiming at the vulnerable groups are also generated in the existing fraud mode.
In the existing internet fraud protection scheme, the behavior of a user is generally identified, a message reminding is performed on a cheated user after possible fraudulent activities are identified, and the user is hoped to be prevented from being cheated by the message reminding. However, for the above mentioned disadvantaged group, when using internet products, the existing methods give a prompt to the system which is hardly noticed due to unfamiliarity with the products, etc., so that the fraud protection cannot be put into practical effect.
Disclosure of Invention
The embodiment of the invention provides a user risk notification method, a user risk notification system and a storage device, which are used for respectively sending first risk notification information to a first application terminal and a user terminal when the first application terminal has risks or is in risk activities.
A first aspect of an embodiment of the present invention provides a user risk notification method, including:
determining that a first application terminal corresponding to a first user identifier has a risk or is in risk activity;
acquiring a second user identifier which is associated with the first user identifier based on risk notification;
and respectively sending first risk notification information to the first application terminal and a user terminal corresponding to the second user identifier, wherein the first risk notification information is used for indicating that the first application terminal has risk or is in risk activity.
A second aspect of the embodiments of the present invention further provides a user risk notification system, including:
the risk determining unit is used for determining that the first application terminal corresponding to the first user identification has risks or is in risk activity;
an identifier obtaining unit, configured to obtain a second user identifier associated with the first user identifier based on a risk notification;
and the risk notification unit is used for respectively sending first risk notification information to the first application terminal and the user terminal corresponding to the second user identifier, wherein the first risk notification information is used for indicating that the first application terminal has risk or is in risk activity.
A third aspect of the embodiments of the present invention provides a storage device, where the storage device stores a plurality of instructions, and the instructions are suitable for being loaded by a processor and executing the user risk notification method according to the first aspect of the embodiments of the present invention.
The fourth aspect of the embodiments of the present invention further provides a terminal device, including a processor and a storage device, where the processor is configured to implement each instruction;
the storage device is configured to store a plurality of instructions, where the instructions are configured to be loaded by a processor and to perform the user risk notification method according to the first aspect of the embodiment of the present invention.
As can be seen, in the method of this embodiment, when one application terminal (for example, a first user terminal) of a first user has a risk or is in risk activity, the user risk notification system sends first risk notification information to terminals of multiple users, that is, the user terminals corresponding to the first application terminal and the second user identifier. Therefore, the risk of the first application terminal of a plurality of users can be reminded, so that the plurality of users can carry out certain treatment on the first application terminal to avoid the risk, and the risk avoiding probability is increased.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to these drawings without creative efforts.
Fig. 1a is a schematic diagram of a scenario to which a user risk notification method according to an embodiment of the present invention is applied;
fig. 1b is a schematic diagram of another scenario to which the user risk notification method provided in the embodiment of the present invention is applied;
FIG. 2 is a flow chart of a method for notifying a user of risk according to an embodiment of the present invention;
fig. 3 is a schematic diagram of setting an association relationship between user identifiers according to an embodiment of the present invention;
FIG. 4 is a diagram illustrating another setting of association between user identifiers according to an embodiment of the present invention;
fig. 5 is a schematic diagram of another setting of association relationship between user identifiers according to an embodiment of the present invention;
FIG. 6 is a flowchart of a method for notifying a user of risk according to an embodiment of the present invention;
fig. 7 is a schematic structural diagram of a user risk notification system according to an embodiment of the present invention;
FIG. 8 is a schematic structural diagram of another user risk notification system provided in an embodiment of the present invention;
fig. 9 is a schematic structural diagram of a server according to an embodiment of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
The terms "first," "second," "third," "fourth," and the like in the description and in the claims, as well as in the drawings, if any, are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the invention described herein are, for example, capable of operation in sequences other than those illustrated or otherwise described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.
An embodiment of the present invention provides a user risk notification method, which is mainly applied to a scenario shown in fig. 1a or fig. 1b, where the scenario shown in fig. 1a includes: the system comprises a user risk notification system, a storage system and an application system, wherein the application system comprises an application terminal and an application server, and in the case, the association relationship between user identifications is stored in the storage system; the scenario illustrated in FIG. 1b includes: the user risk notification system and the application system comprising the application terminal and the application server, in which case the association between the user identities is stored by the user risk notification system. The user risk notification system may monitor the application terminal to determine whether the application terminal is at risk or in risk activity, etc.
In the embodiment of the present invention, when the user risk notification system determines that the first application terminal corresponding to the first user identifier has a risk or is in risk activity, the user risk notification system obtains the second user identifier associated with the first user identifier based on the risk notification, and then sends the first risk notification information to the first application terminal and the user terminal corresponding to the second user identifier, respectively. Wherein the first risk notification information is used to indicate that the first application terminal is at risk or is in a risk activity. Therefore, the risk of the first application terminal of the plurality of users can be reminded, so that the plurality of users can carry out certain treatment on the first application terminal to avoid the risk, and the probability of avoiding the risk is increased.
An embodiment of the present invention provides a user risk notification method, which is a method executed by a user risk notification system in the foregoing scenario, and a flowchart is shown in fig. 2, where the method includes:
It can be understood that the user risk notification system may monitor any application terminal that has logged into the application server, and determine, according to a certain period and a certain policy, whether any application terminal (e.g., the first application terminal) has a risk or is in risk activity.
Specifically, the user risk notification system may determine whether the first application terminal has a risk or is in risk activity according to a behavior of the first application terminal, such as information of content of a message received by the first application terminal. The first application terminal having a risk means that when the first application terminal receives a risk message but does not perform any processing on the risk message, for example, when the first application terminal receives a certain message which contains risk information such as a fraud message, it is determined that the first application terminal has a risk; the first application terminal being in the risk activity means that the first application terminal performs certain processing on the risk message, for example, the first application terminal opens a link in a certain message, and if the link is a risk link, it is determined that the first application terminal is in the risk activity.
The first user identifier and the second user identifier may be user identifiers based on the same application system, for example, the first user identifier and the second user identifier are micro signals of different users, or instant communication numbers or pay bank numbers of different users; the first user identifier and the second user identifier may also be user identifiers based on different application systems, for example, the first user identifier is a micro signal or a payment treasure number, and the second user identifier is a phone number or an instant communication number or a payment treasure number. And the second subscriber identity may be one or more and the first subscriber identity may also be one or more.
In the case shown in fig. 1a, the user risk notification system may retrieve the second user identification from the storage system; in the situation as shown in fig. 1b, the user risk notification system may retrieve the second user identification in the local storage space.
The user terminal corresponding to the second user identifier may be a second application terminal, such as a wechat terminal, or an instant messaging terminal; or may be a mobile phone, such as a mobile phone corresponding to a certain phone number, where the first subscriber identity and the second subscriber identity may be based on subscriber identities of different application systems. For example, if the first user identifier is a micro signal, the first application terminal is a micro message client, the second user identifier is a mobile phone number, and the user terminal corresponding to the second user identifier is a mobile phone, the user risk notification system may send the second risk notification information to the micro message client and the mobile phone when the micro message client is at risk or in risk activity.
Further, the user risk notification system may also actively send third risk notification information to the first application terminal and the user terminal, respectively, where the third risk notification information is used to indicate types of risk messages, so as to notify the user that the terminal does not need to operate on the risk messages when receiving the types of risk messages.
Further, the user risk notification system may further send any other notification information, such as notification information related to the first subscriber identity or the second subscriber identity, to the first application terminal and the user terminal, respectively. The content of the notification information may be different according to the specific form of the first user identifier and the second user identifier.
As can be seen, in the method of this embodiment, when one application terminal (for example, a first application terminal) of a first user has a risk or is in risk activity, the user risk notification system sends first risk notification information to terminals of multiple users, that is, the user terminals corresponding to the first application terminal and the second user identifier. Therefore, the risk of the first application terminal of a plurality of users can be reminded, so that the plurality of users can carry out certain treatment on the first application terminal to avoid the risk, and the risk avoiding probability is increased.
It should be noted that, in order to implement steps 101 to 103 in the above embodiment, the association relationship between the user identifiers needs to be stored in advance. Specifically, it can be realized by the following several ways:
(1) in the case of fig. 1a described above, the setting is performed by the first application terminal, and the schematic diagram is shown in fig. 3.
a1, when the user logs on the corresponding application server by operating the first application terminal and using the first user identifier, the user can further operate the first application terminal, so that the first application terminal displays a setting interface based on the risk notification, and the setting interface includes the first setting interface bound with the second user identifier.
b1, the user can input one or more second user identifications into the first setting interface of the setting interface, and click and submit, the first application terminal will send the association request of the risk notification to the application server, and the association request includes the first user identification and the one or more second user identifications.
c1, after receiving the association request, the application server will send the first user id and the second user id to the storage system, and the storage system stores the corresponding relationship between the first user id and the second user id.
Before the application server sends the first user identifier and the second user identifier to the storage system, the application server can also send a first binding request to a user terminal corresponding to the second user identifier, wherein the first binding request is used for requesting to bind the second user identifier; after receiving the first binding request, the user terminal can display user selection information so that a user can select whether to allow the second user identifier to be bound, and if the user selects the information allowing the binding, the user terminal can send the information allowing the binding to the application server; and after receiving the information allowing binding, the application server sends the first user identifier and the second user identifier to a storage system for storage.
For example: and if the first user identifier is the micro signal 1, the first application terminal is a micro signal client, the second user identifier is a mobile phone number, and the user terminal is a mobile phone. If the user passes through the WeChat client and logs in the WeChat server by adopting the micro signal 1, the user can operate the WeChat client to enable the WeChat client to display the setting interface, and after the user inputs the mobile phone number on the setting interface, the WeChat client can carry the micro signal 1 and the mobile phone number in the association request and send the association request to the WeChat server. And then the micro-signal server sends the micro-signal 1 and the mobile phone number to a storage system for corresponding storage.
(2) In the case shown in fig. 1a, the setting is performed by the user terminal corresponding to the second user identifier.
When the user logs in the corresponding application server by operating the user terminal of the second user identifier and adopting the second user identifier, the user can further operate the user terminal, so that the user terminal displays a setting interface based on the risk notification, and the setting interface comprises a second setting interface bound with the first user identifier. Thus, a user can input one or more first user identifications into a second setting interface of the setting interface and click and submit the first user identifications, the user terminal can send an association request of the risk notification to the application server, and the association request comprises the second user identification and the one or more first user identifications.
After receiving the association request, the application server sends the first user identifier and the second user identifier to the storage system, and the storage system stores the corresponding relationship between the first user identifier and the second user identifier.
(3) In the case of fig. 1b above, the setting is performed by the first application terminal, the schematic diagram is shown in fig. 4.
a2, when the user logs on the corresponding application server by operating the first application terminal and using the first user identifier, the user can further operate the first application terminal, so that the first application terminal displays a setting interface based on the risk notification, and the setting interface includes the first setting interface bound with the second user identifier.
b2, the user can input one or more second user identifications into the first setting interface of the setting interface and click and submit, the first application terminal will directly send the association request of the risk notification to the user risk notification system, and the association request includes the first user identification and the one or more second user identifications.
It can be understood that, when sending the association request to the user risk notification system, the first application terminal first logs in the user risk notification system by using the first user identifier, and then can send the association request to the user risk notification system.
c2, the user risk notification system stores the corresponding relationship between the first user id and the second user id in the local storage space after receiving the association request.
Before the user risk notification system stores the corresponding relation, a second binding request can be sent to the first application terminal, wherein the second binding request is used for requesting to bind the first user identifier; after receiving the second binding request, the user terminal can display user selection information so that a user can select whether to allow the first user identifier to be bound, and if the user selects the information allowing the binding, the user terminal can send the information allowing the binding to a user risk notification system; and after receiving the information allowing binding, the user risk notification system stores the corresponding relation between the first user identification and the second user identification.
For example: if the user logs in the instant messaging server through the instant messaging client by adopting the instant messaging number 1, the user can operate the instant messaging client to enable the instant messaging client to display the setting interface, and after the user inputs the micro signal 2 into the setting interface, the instant messaging client can carry the micro signal 2 and the instant messaging number 1 in an association request and directly send the association request to a user risk notification system for storage.
(4) In the case shown in fig. 1b, the setting is performed by the user terminal corresponding to the second user identifier.
And when the user logs in the corresponding application server by operating the user terminal corresponding to the second user identifier and adopting the second user identifier, the user can further operate the user terminal, so that the user terminal displays a setting interface based on the risk notification, and the setting interface comprises a second setting interface bound with the first user identifier. Thus, a user can input one or more first user identifications to a second setting interface of the setting interface and click and submit, the user terminal can directly send an association request of the risk notification to the user risk notification system, and the association request comprises the second user identification and the one or more first user identifications. After receiving the association request, the user risk notification system stores the corresponding relationship between the first user identifier and the second user identifier in the local storage space.
(5) In the case shown in fig. 1b, the setting is performed by the user terminal corresponding to the second user identifier, and a schematic diagram is shown in fig. 5.
After the user logs in the corresponding user risk notification system by operating the association setting terminal, the user can further operate the association setting terminal, so that the association setting terminal displays a setting interface based on the risk notification, and the setting interface comprises a third setting interface for binding the first user identifier and the second user identifier. Therefore, a user can input one or more first user identifications and one or more second user identifications into a third setting interface of the setting interface, click and submit, the association setting terminal can directly send an association request of the risk notification to the user risk notification system, and the association request comprises the second user identifications and the first user identifications. After receiving the association request, the user risk notification system stores the corresponding relationship between the first user identifier and the second user identifier in the local storage space.
The association setting terminal is a terminal corresponding to the user risk notification system, and when a user logs in the user risk notification system through the association setting terminal, the user can log in by using any user identifier (which may be the same as or different from the first user identifier and the second user identifier).
It should be further noted that the setting interface based on the risk notification may further include a fourth setting interface, so that the user may set, through the fourth setting interface, a sending condition of the second risk notification information, for example, only send the second risk notification information to the user terminal when the user terminal corresponding to the second user identifier has a risk or is in risk activity, thereby saving network traffic. And the setting information input by the user through the fourth setting interface can also be stored in the storage system or the user risk notification system.
Therefore, when it is determined that the user terminal corresponding to the second user identifier is at risk or is in risk activity, the user risk notification system sends the second risk notification information to the user terminals corresponding to the first application terminal and the second user identifier respectively according to the setting information of the fourth setting interface, or sends the second risk notification information only to the user terminals, where the second risk notification information is used to indicate that the user terminals are at risk or in risk activity.
The method of this embodiment is applied to the scenario shown in fig. 1a, assuming that a user xiaoming is an university student, the father and the mother use few internet products, and the anti-cheating capability is low, and the xiaoming associates the xiaoming micro-signal with the micro-signal, the phone number and the QQ number of the parent through the own micro-signal client, so that the storage system stores the corresponding relationship between the xiaoming micro-signal and the micro-signal, the phone number and the QQ number of the parent, wherein the xiaoming micro-signal is the first user identifier, and the micro-signal, the phone number and the QQ number of the parent are the second user identifier. Referring to fig. 6, in this case:
in step 201, the user risk notification system will determine whether the application terminal corresponding to the micro signal, telephone number or QQ number of the Mingming parent has risk or is in risk activity according to a certain period, and if it is determined that the application terminal has risk or is in risk activity, then steps 202 and 203 are executed.
For example, if a fraudster sends a fraud message to the micro-signal of the Mingmen through the micro-signal system, the user risk notification system determines that the micro-signal client corresponding to the micro-signal of the Mingmen has a risk.
At step 202, the user risk notification system retrieves from the storage system a twilight micro-signal associated with a twilight parent's micro-signal, phone number or QQ number.
In step 203, the user risk notification system sends first risk notification information to the micro-signal of the Mingming parents, the application terminal corresponding to the telephone number or the QQ number, and the micro-signal client corresponding to the Mingming micro-signal, respectively, where the first risk notification information is used to indicate that the micro-signal of the Mingming parents, the application terminal corresponding to the telephone number or the QQ number has a risk or is in risk activity.
Therefore, the user can be on the spot or can confirm the situation with the parents in a telephone mode and the like, and the parents are prevented from being on the spot. Therefore, by the method for notifying the user risk in the embodiment, the condition that the user is cheated due to the fact that the user is not reminded in place in the existing internet cheat-preventing scheme can be avoided to a certain extent.
An embodiment of the present invention further provides a user risk notification system, a schematic structural diagram of which is shown in fig. 7, and the system may specifically include:
a risk determining unit 10, configured to determine that a first application terminal corresponding to a first user identifier has a risk or is in risk activity;
an identifier obtaining unit 11, configured to obtain, according to a first user identifier corresponding to the first application terminal determined by the risk determining unit 10, a second user identifier associated with the first user identifier based on the risk notification;
a risk notifying unit 12, configured to send first risk notification information to the first application terminal and the user terminal corresponding to the second user identifier acquired by the identifier acquiring unit 11, respectively, where the first risk notification information is used to indicate that the first application terminal has a risk or is in risk activity.
The risk notification unit 12 is further configured to send second risk notification information to the first application terminal and the user terminal, respectively, or send the second risk notification information to the user terminal, if the user terminal has a risk or is in risk activity; wherein the second risk notification information is used to indicate that the user terminal is at risk or in a risk activity.
Further, the risk notifying unit 12 is further configured to send third risk notifying information to the first application terminal and the user terminal, respectively, where the third risk notifying information is used to indicate a type of the risk message.
In this embodiment, the first user identifier and the second user identifier may be user identifiers based on the same or different application systems.
As can be seen, in the user risk notification system of this embodiment, when one of the application terminals (for example, the first user terminal) of the first user has a risk or is in risk activity, the risk notification unit 12 sends the first risk notification information to the terminals of multiple users, that is, the user terminals corresponding to the first application terminal and the second user identifier. Therefore, the risk of the first application terminal of a plurality of users can be reminded, so that the plurality of users can carry out certain treatment on the first application terminal to avoid the risk, and the risk avoiding probability is increased.
Referring to fig. 8, the user risk notification system may further include an association request unit 13, a storage unit 14, a binding request unit 15 and a related notification unit 16, in addition to the structure shown in fig. 7, wherein:
an association request unit 13, configured to receive an association request of a risk notification sent by the first application terminal or the user terminal, where the association request includes the first user identifier and the second user identifier;
a storage unit 14, configured to store a corresponding relationship between the first user identifier and the second user identifier in the association request received by the association request unit 13. In this way, the identifier obtaining unit 11 obtains the second user identifier from the correspondence stored in the storage unit 14.
A binding request unit 15, configured to send a first binding request to the user terminal after the association request unit 13 receives an association request of a risk notification sent by the first application terminal, where the first binding request is used to request to bind the second user identifier; when receiving the binding permission information sent by the user terminal, notifying the storage unit 14 to execute the step of storing the corresponding relationship; or, the binding request unit 15 is configured to send, after the association request unit 13 receives an association request of a risk notification sent by the user terminal, a second binding request to the first application terminal, where the second binding request is used to request to bind the first user identifier; when receiving the binding permission information sent by the first application terminal, notifying the storage unit 14 to execute the step of storing the corresponding relationship.
And a relevant notification unit 16, configured to send notification information relevant to the first user identifier or the second user identifier to the first application terminal and the user terminal, respectively.
The present invention also provides a server, which is schematically shown in fig. 9, and the server may generate a relatively large difference due to different configurations or performances, and may include one or more Central Processing Units (CPUs) 20 (e.g., one or more processors) and a memory 21, and one or more storage media 22 (e.g., one or more mass storage devices) for storing the application programs 221 or the data 222. Wherein the memory 21 and the storage medium 22 may be a transient storage or a persistent storage. The program stored on the storage medium 22 may include one or more modules (not shown), each of which may include a series of instruction operations for the server. Still further, the central processor 20 may be configured to communicate with the storage medium 22 to execute a series of instruction operations in the storage medium 22 on the server.
Specifically, the application programs 221 stored in the storage medium 22 include application programs for user risk notification, and the program may include the risk determining unit 10, the identifier obtaining unit 11, the risk notifying unit 12, the association requesting unit 13, the storage unit 14, the binding requesting unit 15, and the related notifying unit 16 in the user risk notification system, which are not described herein again. Still further, the central processor 20 may be configured to communicate with the storage medium 22, and execute a series of operations corresponding to the application program of the user risk notification stored in the storage medium 22 on the server.
The server may also include one or more power supplies 23, one or more wired or wireless network interfaces 24, one or more input-output interfaces 25, and/or one or more operating systems 223, such as Windows Server, Mac OS XTM, UnixTM, LinuxTM, FreeBSDTM, and the like.
The steps performed by the user risk notification system described in the above method embodiments may be based on the structure of the server shown in fig. 9.
An embodiment of the present invention further provides a storage device, where the storage device stores a plurality of instructions, and the instructions are suitable for being loaded by a processor and executing the user risk notification method in the foregoing embodiment.
The embodiment of the invention also provides terminal equipment, which comprises a processor and storage equipment, wherein the processor is used for realizing each instruction;
the storage device is configured to store a plurality of instructions for loading and executing the user risk notification method as described in the above embodiments by the processor.
Those skilled in the art will appreciate that all or part of the steps in the methods of the above embodiments may be implemented by associated hardware instructed by a program, which may be stored in a computer-readable storage medium, and the storage medium may include: read Only Memory (ROM), Random Access Memory (RAM), magnetic or optical disks, and the like.
The user risk notification method, the user risk notification system, and the storage device provided by the embodiment of the present invention are described in detail above, and a specific example is applied in the description to explain the principle and the embodiment of the present invention, and the description of the above embodiment is only used to help understanding the method and the core idea of the present invention; meanwhile, for a person skilled in the art, according to the idea of the present invention, there may be variations in the specific embodiments and the application scope, and in summary, the content of the present specification should not be construed as a limitation to the present invention.
Claims (8)
1. A user risk notification method is applied to a user risk notification system and comprises the following steps:
the user risk notification system monitors a first application terminal logged in an application server, and determines that the first application terminal corresponding to a first user identifier has a risk or is in risk activity according to a certain period and the behavior of the first application terminal; when the first application terminal opens a risk link, the first application terminal is in risk activity;
acquiring a second user identifier which is associated with the first user identifier based on risk notification; the first user identification and the second user identification are based on user identifications of different application systems;
respectively sending first risk notification information to the first application terminal and a user terminal corresponding to the second user identifier, wherein the first risk notification information is used for indicating that the first application terminal has risk or is in risk activity;
respectively sending third risk notification information to the first application terminal and the user terminal, wherein the third risk notification information is used for indicating the type of the risk message;
the method further comprises the following steps:
when an association request sent by an association setting terminal is received, storing the corresponding relation between the first user identification and the second user identification and the sending condition of the second risk notification information to a local storage space, wherein the association request comprises the second user identification, the first user identification and the sending condition of the second risk notification information;
the association setting terminal is a terminal corresponding to the user risk notification system, and the first user identifier and the second user identifier are input through a third setting interface on a setting interface based on risk notification displayed by the association setting terminal after the association setting terminal logs in the user risk notification system; the sending condition is input through a fourth setting interface on the setting interface based on the risk notification; and when the application terminal corresponding to the second user identifier has a risk or is in risk activity, respectively sending the second risk notification information to the first application terminal and the user terminal corresponding to the second user identifier according to the sending condition, or only sending the second risk notification information to the user terminal corresponding to the second user identifier.
2. The method of claim 1, wherein the method further comprises:
receiving an association request of a risk notification sent by the first application terminal or the user terminal, wherein the association request comprises the first user identification and the second user identification;
and storing the corresponding relation between the first user identification and the second user identification.
3. The method of claim 2,
after receiving the association request of the risk notification sent by the first application terminal, the method further includes: sending a first binding request to the user terminal, wherein the first binding request is used for requesting to bind the second user identifier; when receiving the binding permission information sent by the user terminal, executing the step of storing the corresponding relation; alternatively, the first and second electrodes may be,
after receiving the association request of the risk notification sent by the user terminal, the method further includes: sending a second binding request to the first application terminal, wherein the second binding request is used for requesting to bind the first user identification; and when receiving the binding permission information sent by the first application terminal, executing the step of storing the corresponding relation.
4. A user risk notification system, comprising:
the risk determining unit is used for monitoring the first application terminal logged in the application server by the user risk notifying system, and determining that the first application terminal corresponding to the first user identifier has risk or is in risk activity according to a certain period and the behavior of the first application terminal; when the first application terminal opens a risk link, the first application terminal is in risk activity;
an identifier obtaining unit, configured to obtain a second user identifier associated with the first user identifier based on a risk notification; the first user identification and the second user identification are based on user identifications of different application systems;
a risk notification unit, configured to send first risk notification information to the first application terminal and a user terminal corresponding to the second user identifier, respectively, where the first risk notification information is used to indicate that the first application terminal has a risk or is in risk activity; the risk notification unit is further configured to send third risk notification information to the first application terminal and the user terminal, respectively, where the third risk notification information is used to indicate a type of a risk message;
the association request unit is used for receiving an association request sent by an association setting terminal, wherein the association request comprises a second user identifier, a first user identifier and a sending condition of second risk notification information; the association setting terminal is a terminal corresponding to the user risk notification system, and the first user identifier and the second user identifier are input through a third setting interface on a setting interface based on risk notification displayed by the association setting terminal after the association setting terminal logs in the user risk notification system; the sending condition is input through a fourth setting interface on the setting interface based on the risk notification; when the application terminal corresponding to the second user identifier has a risk or is in risk activity, respectively sending the second risk notification information to the first application terminal and the user terminal corresponding to the second user identifier according to the sending condition, or only sending the second risk notification information to the user terminal corresponding to the second user identifier;
and the storage unit is used for storing the corresponding relation between the first user identifier and the second user identifier and the sending condition of the second risk notification information to a local storage space.
5. The system of claim 4, further comprising:
the association request unit is further configured to receive an association request of a risk notification sent by the first application terminal or the user terminal, where the association request includes the first user identifier and the second user identifier.
6. The system of claim 5, further comprising:
a binding request unit, configured to send a first binding request to the user terminal after the association request unit receives an association request of a risk notification sent by the first application terminal, where the first binding request is used to request to bind the second user identifier; when receiving the binding permission information sent by the user terminal, informing the storage unit to execute the step of storing the corresponding relation; alternatively, the first and second electrodes may be,
a binding request unit, configured to send a second binding request to the first application terminal after the association request unit receives an association request of a risk notification sent by the user terminal, where the second binding request is used to request to bind the first user identifier; and when receiving the binding permission information sent by the first application terminal, informing the storage unit to execute the step of storing the corresponding relation.
7. A memory device storing a plurality of instructions adapted to be loaded by a processor and to perform the user risk notification method according to any of claims 1 to 3.
8. A terminal device, comprising a processor and a storage device, wherein the processor is configured to implement instructions;
the storage device is configured to store a plurality of instructions for loading and executing by a processor the user risk notification method of any of claims 1 to 3.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710445583.2A CN107395673B (en) | 2017-06-14 | 2017-06-14 | User risk notification method and system and storage device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710445583.2A CN107395673B (en) | 2017-06-14 | 2017-06-14 | User risk notification method and system and storage device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN107395673A CN107395673A (en) | 2017-11-24 |
| CN107395673B true CN107395673B (en) | 2022-02-01 |
Family
ID=60331882
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710445583.2A Active CN107395673B (en) | 2017-06-14 | 2017-06-14 | User risk notification method and system and storage device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107395673B (en) |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105847371A (en) * | 2016-03-31 | 2016-08-10 | 乐视控股（北京）有限公司 | Method, server and terminal of pushing notification messages |
| CN105991553A (en) * | 2015-02-03 | 2016-10-05 | 腾讯科技（深圳）有限公司 | Message server and communication method |
| CN106412333A (en) * | 2016-11-18 | 2017-02-15 | 北京奇虎科技有限公司 | Method and system for processing message content, and mobile communication terminal |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US10523637B2 (en) * | 2015-07-22 | 2019-12-31 | Paypal, Inc. | Anonymous account security exchange |
-
2017
- 2017-06-14 CN CN201710445583.2A patent/CN107395673B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105991553A (en) * | 2015-02-03 | 2016-10-05 | 腾讯科技（深圳）有限公司 | Message server and communication method |
| CN105847371A (en) * | 2016-03-31 | 2016-08-10 | 乐视控股（北京）有限公司 | Method, server and terminal of pushing notification messages |
| CN106412333A (en) * | 2016-11-18 | 2017-02-15 | 北京奇虎科技有限公司 | Method and system for processing message content, and mobile communication terminal |
Also Published As
| Publication number | Publication date |
|---|---|
| CN107395673A (en) | 2017-11-24 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20180270182A1 (en) | Message notification method, system, and device for a communication account | |
| CN103391535B (en) | Method for allowing multiple terminals to share virtual SIM (subscriber identity module) card, as well as terminals, server and system | |
| CN110611723B (en) | Scheduling method and device of service resources | |
| CN104883657B (en) | A kind of virtual card management method and device | |
| CN108632367A (en) | Account correlating method and information-pushing method | |
| CN104021141B (en) | Method, device and system for data processing and cloud service | |
| EP2869532B1 (en) | Service apparatus and method for providing deferred message, and storage medium | |
| CN110764881A (en) | Distributed system background retry method and device | |
| CN105320880A (en) | Terminal control method and apparatus | |
| JP2014527661A (en) | Mobile payment method, apparatus and system for server and client | |
| CN112672357A (en) | Method and device for processing user account in business system and computer equipment | |
| US11093945B1 (en) | Electronic commerce fraud mitigation in a wireless communication network | |
| CN108197958B (en) | Method and device for counting off-line cattle and storage medium | |
| US10652763B2 (en) | Cellular phone message delivery testing system and method | |
| CN108881929B (en) | Method and device for setting login prompt of live broadcast room | |
| CN107395673B (en) | User risk notification method and system and storage device | |
| CN107770162A (en) | The method and device of brush present is prevented in a kind of live platform | |
| CN117041420A (en) | Voice call testing method, device and equipment | |
| CN105141586B (en) | A kind of method and system verified to user | |
| CN106302937A (en) | The based reminding method of communication harassing and wrecking and device | |
| CN107396030B (en) | Video call processing method and scheduling control terminal | |
| CN108989298A (en) | A kind of equipment safety monitoring method and device | |
| CN101867918B (en) | Real-name system registration state acquiring method, device and terminal | |
| CN106254222B (en) | A kind of network social intercourse object identity reminding method and device | |
| CN110365831B (en) | Incoming call response method, device, system, storage medium and electronic device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |