CN108718271A - Method, device, storage medium and terminal for processing friend request - Google Patents

Abstract

The embodiment of the application discloses a method, a device, a storage medium and a terminal for processing a friend request, wherein the method comprises the following steps: when a friend request is received, acquiring abnormal reference information of a requester; judging whether the requester is an abnormal user or not according to the abnormal reference information; and if the requester is an abnormal user, the friend request is shielded, and the information security of the user can be improved.

Description

Method, device, storage medium and terminal for processing friend request

technical field

The embodiments of the present application relate to the technical field of mobile terminals, and in particular to a method, device, storage medium and terminal for processing friend requests.

Background technique

With the continuous development of mobile terminals, more and more users have installed social application software on the terminals. The social application software includes the function of adding friends, and chatting can be carried out after adding friends.

At present, strangers can search for users through "shake" or "people nearby", and then initiate friend requests to users. After the user accepts the friend request, the system will prompt the user whether the new friend is a threat. However, after adding a friend who is a threat, it will affect the security of user information.

Contents of the invention

The purpose of the embodiments of the present application is to provide a friend request processing method, device, storage medium and terminal, which can improve user information security.

In the first aspect, the embodiment of the present application provides a method for processing a friend request, including:

When receiving a friend request, obtain the abnormal reference information of the requesting party;

judging whether the requester is an abnormal user according to the abnormal reference information;

If the requesting party is an abnormal user, the friend request is shielded.

In the second aspect, the embodiment of the present application provides a device for processing friend requests, including:

An acquisition module, configured to acquire abnormal reference information of the requesting party when a friend request is received;

A judging module, configured to judge whether the requester is an abnormal user according to the abnormal reference information acquired by the acquiring module;

A request processing module, configured to shield the friend request if the requester is an abnormal user.

In a third aspect, the embodiment of the present application provides a computer-readable storage medium, on which a computer program is stored, and when the program is executed by a processor, the method for processing a friend request as shown in the first aspect is implemented.

In a fourth aspect, an embodiment of the present application provides a terminal, including a memory, a processor, and a computer program stored in the memory and operable on the processor. When the processor executes the computer program, the computer program described in the first aspect is implemented. How to handle the displayed friend request.

The solution to the friend request provided in the embodiment of the present application firstly obtains the abnormal reference information of the requesting party when receiving the friend request; then, judges whether the requesting party is an abnormal user according to the abnormal reference information; finally, if the If the requesting party is an abnormal user, shielding the friend request can improve user information security.

Description of drawings

FIG. 1 is a schematic flowchart of a method for processing a friend request provided by an embodiment of the present application;

FIG. 2 is a schematic flowchart of another method for processing a friend request provided by an embodiment of the present application;

FIG. 3 is a schematic flowchart of another method for processing a friend request provided by an embodiment of the present application;

FIG. 4 is a schematic flowchart of another method for processing a friend request provided by an embodiment of the present application;

FIG. 5 is a schematic flowchart of another method for processing a friend request provided by an embodiment of the present application;

FIG. 6 is a schematic flowchart of another method for processing a friend request provided by an embodiment of the present application;

FIG. 7 is a schematic structural diagram of a device for processing a friend request provided by an embodiment of the present application;

FIG. 8 is a schematic structural diagram of a mobile terminal provided by an embodiment of the present application.

Detailed ways

The technical solution of the present application will be further described below in conjunction with the accompanying drawings and through specific implementation methods. It should be understood that the specific embodiments described here are only used to explain the present application, but not to limit the present application. In addition, it should be noted that, for the convenience of description, only some structures related to the present application are shown in the drawings but not all structures.

Before discussing the exemplary embodiments in more detail, it should be mentioned that some exemplary embodiments are described as processes or methods depicted as flowcharts. Although the flowcharts describe the steps as sequential processing, many of the steps may be performed in parallel, concurrently, or simultaneously. Additionally, the order of steps may be rearranged. The process may be terminated when its operations are complete, but may also have additional steps not included in the figure. The processing may correspond to a method, function, procedure, subroutine, subroutine, or the like.

With the continuous development of mobile terminals, more and more users have installed social application software on the terminals. The social application software includes the function of adding friends, and chatting can be carried out after adding friends. At present, strangers can search for users through "shake" or "people nearby", and then initiate friend requests to users. After the user accepts the friend request, the system will prompt the user whether the new friend is a threat. After seeing the prompt information, the user will feel uneasy and panic psychologically. And users who are threatening can obtain the user's personal information by viewing the information released by functions such as the user's circle of friends, which poses a threat to the user's information security.

The embodiment of the present application provides a friend request processing method, which can judge whether the requester is an abnormal user in the friend request stage, and if it is an abnormal user, block the friend request, thereby preventing the user from adding a friend who is threatening after adding a friend. into the blacklist to improve user information security. The specific plan is as follows:

Fig. 1 is a schematic flowchart of a method for processing a friend request provided by an embodiment of the present application. The method is used in the case where a terminal processes a friend request. The method can be executed by a mobile terminal installed with a social application program. The mobile terminal It can be smartphones, tablets, wearable devices, laptops, etc. Social applications include instant chat applications (such as WeChat, Tencent QQ or MSN, etc.) and social applications (such as Weibo or game applications with social attributes, etc.) ), the method specifically includes the following steps:

Step 110, when a friend request is received, obtain abnormal reference information of the requesting party.

The requester can find the user by scanning the QR code, shaking the mobile phone to search keywords, etc., and initiate a friend request to the user. The friend request is sent from the requesting terminal to the server, and then sent to the user terminal by the server. When the user terminal receives the friend request sent by the server, it obtains the abnormal reference information of the requesting party through the server. The abnormal reference information includes one or more of the requester's account information, login location information, complaint information, blacklisted information, and fraud information. The abnormal reference information of each user may be stored by an independent information storage server. When the user terminal receives a friend request, it obtains the requester ID, and uses the requester ID to obtain the abnormal reference information from the information storage server.

Step 120, judging whether the requester is an abnormal user according to the abnormal reference information.

Analyze the obtained abnormal reference information to determine whether the recipient is an abnormal user.

Step 130, if the requesting party is an abnormal user, block the friend request.

When blocking friend requests, cancel the display of friend requests in the foreground interface. At the same time, send feedback information to the requesting party. Feedback information may include reasons for blocking.

Step 140, if the requesting party is a non-abnormal user, output a friend request.

If the requesting party is a non-abnormal user, a friend request identifier is added in the user interface of the social application program.

The method for processing a friend request provided in the embodiment of this application firstly obtains the abnormal reference information of the requesting party when a friend request is received; then, judges whether the requesting party is an abnormal user according to the abnormal reference information; finally, if the requesting party is an abnormal user , block friend requests. Compared with prompting the friend abnormality after adding a friend, the embodiment of the present application can judge whether the requesting party is an abnormal user during the friend request stage, and if it is an abnormal user, block the friend request, or prompt the user that the requesting party has an abnormal account. If it is a non-abnormal user, output a friend request to the user, so as to avoid prompting after adding a friend, and improve user information security.

FIG. 2 is a schematic flowchart of a method for processing a friend request provided by an embodiment of the present application. As a further description of the above embodiment, it includes:

Step 210, when a friend request is received, acquire the account information of the requesting party.

The account information includes the requester's account name, phone card number, and real-name registration information. Account Information The account information can be added to the friend request when the requester sends the friend request. After receiving the friend request, the user terminal parses the friend request to obtain account information.

Step 220, judging whether the account information of the requesting party is complete.

Optionally, it is determined whether the account information lacks a phone card number. When the user makes a call through a virtual phone such as an IP phone, or the user sets a hidden caller number, the calling card number will be missing in the account information. Exemplarily, the mobile phone system of the user terminal detects whether there is a valid phone card number in the account information (whether there is any reserved information in China Mobile, China Unicom, or telecom operators). If not, it is abnormal. If present, it is non-exceptional.

Optionally, it is determined whether the account information lacks real-name authentication information. The real-name system information may be information about whether the real-name system authentication is completed. If the real-name authentication is completed, it will be marked as 1, and if the real-name authentication has not been completed, it will be marked as 0. Alternatively, the real-name information may also be the user name and ID card of the requesting party. After receiving the requester's user name and ID card, the user terminal determines whether the requester's real-name information is correct through the real-name authentication server.

Optionally, for example, the mobile phone system of the user terminal detects whether real-name authentication is performed in the account information. For example, whether there is authentication of ID card, driver's license or passport. If not, it is abnormal. If present, it is non-exceptional.

Step 230, if the account information of the requesting party is incomplete, it is determined that the requesting party is an abnormal user, and the incomplete account information includes lack of phone card number and/or lack of real-name authentication information.

Step 240, if the requesting party is an abnormal user, block the friend request.

Step 250, if the account information of the requesting party is complete, it is determined that the requesting party is a non-abnormal user.

Step 260, if the requesting party is a non-abnormal user, output a friend request.

The friend request processing method provided by the embodiment of the present application can determine whether the account is abnormal according to whether the account information is complete, and when the account information is complete, determine that the recipient is a non-abnormal user, and output a friend request, which can avoid friend requests initiated by false accounts, Improve security.

FIG. 3 is a schematic flowchart of a method for processing a friend request provided by an embodiment of the present application. As a further description of the above embodiment, it includes:

Step 310, when a friend request is received, obtain the login location information of the requesting party.

The login location information may include location information currently logged in by the requester.

Step 320, judging whether the requesting party has logged in from a different place according to the login location information.

Determine whether the requester's location information is the same as the user's current location information. The location information of the requesting party can be obtained by querying the server where the account is logged in. Optionally, the accuracy of the location information may be as accurate as a city or a country. If the requester and the user are located in the same city or country, then non-off-site login is determined. Otherwise, if the city or country where the requester and the user are located are not the same, an off-site login is determined.

Optionally, a location set of contacts that the user has contacted within a preset time is obtained, and if the location set includes the location information of the requester, it is determined that the requester is not logged in from a different place. Otherwise, if the location set does not include the location information of the requesting party, it is determined that the requesting party logs in remotely. Wherein, the preset time may be 1 month to 6 months, and may be 3 months as an option.

Exemplarily, it is determined whether the login location of the account of the requesting party is consistent with the login location of the user. If there is no login location of the requester's account in the user's contacts in the last six months, or the requester is anonymously logged in overseas, it will be determined as a remote login.

Step 330, if the requesting party logs in from a different place, it is determined that the requesting party is an abnormal user.

Step 340, if the requesting party is an abnormal user, block the friend request.

Step 350, if the requesting party does not log in from a different place, it is determined that the requesting party is a non-abnormal user.

Step 360, if the requesting party is a non-abnormal user, output a friend request.

The method for processing a friend request provided by the embodiment of the present application can determine whether the requester is logged in from a different place according to the login location information of the requester, thereby preventing users from unfamiliar regions from initiating requests to the user and improving security.

FIG. 4 is a schematic flowchart of a method for processing a friend request provided by an embodiment of the present application. As a further description of the above embodiment, it includes:

Step 410, when a friend request is received, obtain the number of complaints of the requesting party through the server.

When receiving the friend request, the terminal acquires the requester ID through the friend request. Use the requester ID to access the server to obtain the requester's historical complaint records. The historical complaint records include the time when the requester was complained and the reason for the complaint. Optionally, it may be determined whether to block friend requests according to the number of complaints. It is also possible to block friend requests when the number of complaint records meeting the preset complaint reasons exceeds the preset number of times.

Step 420, judging whether the number of complaints received by the requesting party exceeds a preset complaint threshold.

Count the number of complaints against the requesting party in the historical complaint records. The preset complaint threshold is greater than or equal to 1, which can be 1 or 3 times.

Step 430, if the number of complaints against the requesting party exceeds the preset complaint threshold, it is determined that the requesting party is an abnormal user.

Step 440, if the requesting party is an abnormal user, block the friend request.

Step 450, if the number of complaints received by the requesting party is less than the preset complaint threshold, it is determined that the requesting party is a non-abnormal user.

Step 460, if the requesting party is a non-abnormal user, output a friend request.

According to the friend request processing method provided by the embodiment of the present application, after receiving the friend request, the mobile phone system sends an application to the server for issuing the historical complaint records of the account of the requesting party. If the account has been complained by the user, it will be judged as abnormal, and then the threatening user who has been complained once or more times will be blocked to improve security.

FIG. 5 is a schematic flowchart of a method for processing a friend request provided by an embodiment of the present application. As a further description of the above embodiment, it includes:

Step 510, when a friend request is received, determine whether the requesting party is blacklisted by other users.

When receiving the friend request, the terminal acquires the requester ID through the friend request. Access the server with the supplicant ID to get the supplicant to get the list of users that blacklisted the supplicant.

Step 520, if the requesting party is blacklisted by other users, obtain the number of chat records between the requesting party and other users before being blacklisted.

Obtain the number of chat records of the requester and the user respectively according to the user list.

Step 530, judging whether the number of chat records exceeds a preset chat number threshold.

Wherein, the preset chat number threshold is less than 20, and may be 10. The number of chat records is compared with the preset chat number threshold, and the number of users whose chat records exceed the preset chat number threshold is counted. If the number of users is greater than or equal to the preset number of users, it is determined that the requester is an abnormal user. Otherwise, if the number of users is less than the preset number of users, it is determined that the requester is a non-abnormal user. Wherein, the preset number of users is 1 or 2.

Step 540, if the number of chat records exceeds the preset chat number threshold, it is determined that the requester is an abnormal user.

Step 550, if the requesting party is an abnormal user, block the friend request.

Step 560, if the number of chat records is less than the preset chat number threshold, it is determined that the requesting party is a non-abnormal user.

Step 570, if the requesting party is a non-abnormal user, output a friend request.

The friend request processing method provided by the embodiment of the present application can judge whether the requesting party is blacklisted by other users after chatting with the preset chat quantity threshold when receiving the friend request, and then judge whether the requesting party is an abnormal customer, Improve security.

FIG. 6 is a schematic flowchart of a method for processing a friend request provided by an embodiment of the present application. As a further description of the above embodiment, it includes:

Step 610, when a friend request is received, obtain chat records between the requesting party and other users.

When receiving the friend request, the terminal acquires the requester ID through the friend request. Use the requester ID to access the server to get the requester to get the chat records of the requester and other users. Other users are users that the requesting party has communicated with recently. The near term is 1 day to 30 days. Alternatively, the other users are users who blocked the requesting party or complained about the requesting party user.

Step 620, judging whether the requesting party has fraudulent behavior according to the chat records.

Analyze the chat records, and determine whether there is fraud through keyword search.

Exemplarily, the mobile phone system of the user terminal detects the historical chat information of the requesting party, focusing on the relevant records of transactions and money exchanges. When it finds that the account has verbal instigation to defraud the user's payment information, it is determined to be abnormal.

Step 630, if the requesting party has fraudulent behavior, it is determined that the requesting party is an abnormal user.

Step 640, if the requesting party is an abnormal user, block the friend request.

Step 650, if there is no fraudulent behavior by the requesting party, it is determined that the requesting party is a non-abnormal user.

Step 660, if the requesting party is a non-abnormal user, output a friend request.

The friend request processing method provided by the embodiment of the present application can analyze the chat records to determine whether there is a fraudulent behavior, and then determine whether the requesting party is an abnormal user, thereby improving security.

Optionally, the method for processing a friend request provided in the foregoing embodiments may also be executed by a server. When the server receives the friend request, it obtains the abnormal reference information of the requesting party. Determine whether the requester is an abnormal user according to the abnormal reference information. If the requesting party is an abnormal user, the friend request is blocked. If the requesting party is a non-abnormal user, a friend request is sent to the receiving party.

FIG. 7 is a schematic structural diagram of an apparatus for processing a friend request provided by an embodiment of the present application. As shown in FIG. 7 , the device includes: an acquisition module 710 , a judgment module 720 , and a request processing module 730 .

An acquisition module 710, configured to acquire abnormal reference information of the requesting party when a friend request is received;

A judging module 720, configured to judge whether the requester is an abnormal user according to the abnormal reference information obtained by the obtaining module 710;

The request processing module 730 is configured to block the friend request if the requester is an abnormal user.

Further, the acquiring module 710 is configured to acquire account information of the requesting party;

Correspondingly, the judging module 720 is configured to judge whether the account information of the requesting party is complete;

If the account information of the requesting party is incomplete, it is determined that the requesting party is an abnormal user, and the incomplete account information includes lack of phone card number and/or lack of real-name authentication information.

Further, the obtaining module 710 is configured to obtain the login location information of the requesting party;

Correspondingly, the judging module 720 is configured to judge whether the requester logs in from another place according to the log-in location information;

If the requester logs in from a different place, it is determined that the requester is an abnormal user.

Further, the obtaining module 710 is used to obtain the number of complaints of the requesting party through the server;

Correspondingly, the judging module 720 is configured to judge whether the number of times the requester is complained exceeds a preset complaint threshold;

If the number of times the requester is complained exceeds the preset complaint threshold, it is determined that the requester is an abnormal user.

Further, the obtaining module 710 is used to determine whether the requesting party is blacklisted by other users;

If the requesting party is pulled into the blacklist by other users, the number of chat records between the requesting party and the other users before being pulled into the blacklist is obtained;

Correspondingly, the judging module 720 is used to judge whether the number of chat records exceeds a preset chat number threshold;

If the number of chat records exceeds the preset chat number threshold, it is determined that the requester is an abnormal user.

Further, the obtaining module 710 is used to obtain chat records between the requesting party and other users;

Correspondingly, the judging module 720 is configured to judge whether the requesting party has fraudulent behavior according to the chat records;

If the requesting party has fraudulent behavior, it is determined that the requesting party is an abnormal user.

Further, the request processing module 730 is configured to output the friend request if the requester is a non-abnormal user.

In the device for processing a friend request provided in the embodiment of the present application, first, when the acquisition module 710 receives a friend request, it obtains the abnormal reference information of the requesting party; then, the judging module 720 judges whether the requesting party is an abnormal user according to the abnormal reference information; finally, If the requesting party is an abnormal user, the request processing module 730 blocks the friend request. Compared with prompting the friend abnormality after adding a friend, the embodiment of the present application can judge whether the requesting party is an abnormal user during the friend request stage, and if it is an abnormal user, block the friend request, or prompt the user that the requesting party has an account abnormality. If it is a non-abnormal user, output a friend request to the user, so as to avoid prompting after adding a friend, and improve user information security.

The above-mentioned device can execute the methods provided by all the foregoing embodiments of the present application, and has corresponding functional modules and beneficial effects for executing the above-mentioned methods. For technical details not exhaustively described in this embodiment, reference may be made to the methods provided in all the foregoing embodiments of the present application.

FIG. 8 is a schematic structural diagram of another terminal device provided by an embodiment of the present application. As shown in FIG. 8 , the terminal may include: a housing (not shown in the figure), a memory 801, a central processing unit (Central Processing Unit, CPU) 802 (also known as a processor, hereinafter referred to as CPU), and stored in the memory 801. Computer programs running on the processor 802, a circuit board (not shown in the figure) and a power supply circuit (not shown in the figure). The circuit board is placed inside the space surrounded by the housing; the CPU 802 and the memory 801 are arranged on the circuit board; the power supply circuit is used to supply power to each circuit or device of the terminal; The memory 801 is used to store executable program codes; the CPU 802 runs programs corresponding to the executable program codes by reading the executable program codes stored in the memory 801 .

The terminal also includes: peripheral interface 803, RF (Radio Frequency, radio frequency) circuit 805, audio circuit 806, speaker 811, power management chip 808, input/output (I/O) subsystem 809, touch screen 812, other input /control device 810 and external port 804 , these components communicate via one or more communication buses or signal lines 807 .

It should be understood that the illustrated terminal device 800 is only an example of a terminal, and that the terminal device 800 may have more or fewer components than shown in the figure, two or more components may be combined, or Different component configurations are possible. The various components shown in the figures may be implemented in hardware, software, or a combination of hardware and software including one or more signal processing and/or application specific integrated circuits.

The following describes a terminal device provided in this embodiment in detail, and the terminal device takes a smart phone as an example.

Memory 801, the memory 801 can be accessed by the CPU 802, the peripheral interface 803, etc., the memory 801 can include a high-speed random access memory, and can also include a non-volatile memory, such as one or more disk storage devices, flash memory devices , or other volatile solid-state storage devices.

Peripheral interface 803 , which can connect the input and output peripherals of the device to CPU 802 and memory 801 .

The I/O subsystem 809 , the I/O subsystem 809 can connect input and output peripherals on the device, such as a touch screen 812 and other input/control devices 810 , to the peripheral interface 803 . I/O subsystem 809 may include a display controller 8091 and one or more input controllers 8092 for controlling other input/control devices 810 . Among them, one or more input controllers 8092 receive electrical signals from or send electrical signals to other input/control devices 810, which may include physical buttons (push buttons, rocker buttons, etc.) ), dials, slide switches, joysticks, click wheels. It is worth noting that the input controller 8092 can be connected to any of the following: a keyboard, an infrared port, a USB interface, and a pointing device such as a mouse.

Wherein, according to the working principle of the touch screen and the classification of the medium for transmitting information, the touch screen 812 can be a resistive type, a capacitive sensing type, an infrared type or a surface acoustic wave type. Classified according to the installation method, the touch screen 812 can be: plug-in type, built-in type or integral type. Classified according to technical principles, the touch screen 812 can be: a touch screen with vector pressure sensing technology, a touch screen with resistive technology, a touch screen with capacitive technology, a touch screen with infrared technology or a touch screen with surface acoustic wave technology.

A touch screen 812. The touch screen 812 is an input interface and an output interface between the user terminal and the user, and displays visual output to the user. The visual output may include graphics, text, icons, videos, and the like. Optionally, the touch screen 812 sends an electrical signal triggered by the user on the touch screen (such as an electrical signal on the contact surface) to the processor 802 .

The display controller 8091 in the I/O subsystem 809 receives electrical signals from the touch screen 812 or sends electrical signals to the touch screen 812 . The touch screen 812 detects the contact on the touch screen, and the display controller 8091 converts the detected contact into an interaction with the user interface object displayed on the touch screen 812, that is, realizes human-computer interaction, and the user interface object displayed on the touch screen 812 can be a running Icons for games, icons for networking to appropriate networks, etc. It is worth noting that the device may also include an optical mouse, which is a touch-sensitive surface that does not display visual output, or that is an extension of a touch-sensitive surface formed by a touch screen.

The RF circuit 805 is mainly used to establish communication between the smart speaker and the wireless network (that is, the network side), and realize data reception and transmission between the smart speaker and the wireless network. Such as sending and receiving short messages, e-mails, etc.

The audio circuit 806 is mainly used to receive audio data from the peripheral interface 803 , convert the audio data into electrical signals, and send the electrical signals to the speaker 811 .

The speaker 811 is used to restore the voice signal received by the smart speaker from the wireless network through the RF circuit 805 into sound and play the sound to the user.

The power management chip 808 is used for power supply and power management for the hardware connected to the CPU 802 , the I/O subsystem and the peripheral interface.

In this embodiment, the central processing unit 802 is used for:

When receiving a friend request, obtain the abnormal reference information of the requesting party;

judging whether the requester is an abnormal user according to the abnormal reference information;

If the requesting party is an abnormal user, the friend request is shielded.

Further, the acquisition of abnormal reference information of the requesting party includes:

Obtain the account information of the requesting party;

Correspondingly, the judging whether the requester is an abnormal user according to the abnormal reference information includes:

Judging whether the account information of the requesting party is complete;

If the account information of the requesting party is incomplete, it is determined that the requesting party is an abnormal user, and the incomplete account information includes lack of phone card number and/or lack of real-name authentication information.

Further, the acquisition of abnormal reference information of the requesting party includes:

Obtain the login location information of the requesting party;

Correspondingly, the judging whether the requester is an abnormal user according to the abnormal reference information includes:

judging whether the requesting party logs in from another place according to the login location information;

If the requester logs in from a different place, it is determined that the requester is an abnormal user.

Further, the acquisition of abnormal reference information of the requesting party includes:

Obtain the number of complaints against the requesting party through the server;

Correspondingly, the judging whether the requester is an abnormal user according to the abnormal reference information includes:

Judging whether the number of complaints against the requesting party exceeds a preset complaint threshold;

If the number of times the requester is complained exceeds the preset complaint threshold, it is determined that the requester is an abnormal user.

Further, the acquisition of abnormal reference information of the requesting party includes:

Determine whether the requesting party is blacklisted by other users;

If the requesting party is pulled into the blacklist by other users, the number of chat records between the requesting party and the other users before being pulled into the blacklist is obtained;

Correspondingly, the judging whether the requester is an abnormal user according to the abnormal reference information includes:

Judging whether the number of chat records exceeds a preset chat number threshold;

If the number of chat records exceeds the preset chat number threshold, it is determined that the requester is an abnormal user.

Further, the acquisition of abnormal reference information of the requesting party includes:

Obtain the chat history between the requesting party and other users;

Correspondingly, the judging whether the requester is an abnormal user according to the abnormal reference information includes:

judging whether the requesting party has fraudulent behavior according to the chat records;

If the requesting party has fraudulent behavior, it is determined that the requesting party is an abnormal user.

Further, after judging whether the requester is an abnormal user according to the abnormal reference information, the method further includes:

If the requesting party is a non-abnormal user, output the friend request.

The embodiment of the present application also provides a storage medium containing executable instructions of the terminal device, the executable instructions of the terminal device are used to execute a friend request processing method when executed by a processor of the terminal device, the method includes:

When receiving a friend request, obtain the abnormal reference information of the requesting party;

judging whether the requester is an abnormal user according to the abnormal reference information;

If the requesting party is an abnormal user, the friend request is shielded.

Further, the acquisition of abnormal reference information of the requesting party includes:

Obtain the account information of the requesting party;

Correspondingly, the judging whether the requester is an abnormal user according to the abnormal reference information includes:

Judging whether the account information of the requesting party is complete;

If the account information of the requesting party is incomplete, it is determined that the requesting party is an abnormal user, and the incomplete account information includes lack of phone card number and/or lack of real-name authentication information.

Further, the acquisition of abnormal reference information of the requesting party includes:

Obtain the login location information of the requesting party;

Correspondingly, the judging whether the requester is an abnormal user according to the abnormal reference information includes:

judging whether the requesting party logs in from another place according to the login location information;

If the requester logs in from a different place, it is determined that the requester is an abnormal user.

Further, the acquisition of abnormal reference information of the requesting party includes:

Obtain the number of complaints against the requesting party through the server;

Correspondingly, the judging whether the requester is an abnormal user according to the abnormal reference information includes:

Judging whether the number of complaints against the requesting party exceeds a preset complaint threshold;

If the number of times the requester is complained exceeds the preset complaint threshold, it is determined that the requester is an abnormal user.

Further, the acquisition of abnormal reference information of the requesting party includes:

Determine whether the requesting party is blacklisted by other users;

If the requesting party is pulled into the blacklist by other users, the number of chat records between the requesting party and the other users before being pulled into the blacklist is obtained;

Correspondingly, the judging whether the requester is an abnormal user according to the abnormal reference information includes:

Judging whether the number of chat records exceeds a preset chat number threshold;

If the number of chat records exceeds the preset chat number threshold, it is determined that the requester is an abnormal user.

Further, the acquisition of abnormal reference information of the requesting party includes:

Obtain the chat history between the requesting party and other users;

Correspondingly, the judging whether the requester is an abnormal user according to the abnormal reference information includes:

judging whether the requesting party has fraudulent behavior according to the chat records;

If the requesting party has fraudulent behavior, it is determined that the requesting party is an abnormal user.

Further, after judging whether the requester is an abnormal user according to the abnormal reference information, the method further includes:

If the requesting party is a non-abnormal user, output the friend request.

The computer storage medium in the embodiments of the present application may use any combination of one or more computer-readable media. The computer readable medium may be a computer readable signal medium or a computer readable storage medium. A computer readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples (non-exhaustive list) of computer readable storage media include: electrical connections with one or more leads, portable computer disks, hard disks, random access memory (RAM), read only memory (ROM), Erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination of the above. In this document, a computer-readable storage medium may be any tangible medium that contains or stores a program that can be used by or in conjunction with an instruction execution system, apparatus, or device.

A computer readable signal medium may include a data signal carrying computer readable program code in baseband or as part of a carrier wave. Such propagated data signals may take many forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the foregoing. A computer-readable signal medium may also be any computer-readable medium other than a computer-readable storage medium, which can send, propagate, or transmit a program for use by or in conjunction with an instruction execution system, apparatus, or device. .

Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including - but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

Computer program code for performing the operations of the present application may be written in one or more programming languages or combinations thereof, including object-oriented programming languages—such as Java, Smalltalk, C++, and conventional procedural Programming language - such as "C" or a similar programming language. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In cases involving a remote computer, the remote computer can be connected to the user computer through any kind of network, including a local area network (LAN) or a wide area network (WAN), or it can be connected to an external computer (such as through an Internet service provider). Internet connection).

Of course, in the storage medium containing computer-executable instructions provided in the embodiments of the present application, the computer-executable instructions are not limited to the above-mentioned application recommendation operations, and can also execute the application recommendation method provided in any embodiment of the application. related operations.

Note that the above are only preferred embodiments and technical principles used in this application. Those skilled in the art will understand that the present application is not limited to the specific embodiments described herein, and various obvious changes, readjustments and substitutions can be made by those skilled in the art without departing from the protection scope of the present application. Therefore, although the present application has been described in detail through the above embodiments, the present application is not limited to the above embodiments, and can also include more other equivalent embodiments without departing from the concept of the present application, and the present application The scope is determined by the scope of the appended claims.

Claims (10)

1. a kind of processing method of good friend's request, which is characterized in that including：

When receiving good friend's request, the abnormal reference information of requesting party is obtained；

Judge whether the requesting party is abnormal user according to the abnormal reference information；

If the requesting party is abnormal user, good friend's request is shielded.

2. the processing method of good friend's request according to claim 1, which is characterized in that the abnormal reference for obtaining requesting party Information, including：

Obtain the account information of requesting party；

Correspondingly, described judge whether the requesting party is abnormal user according to the abnormal reference information, including：

Judge whether the account information of the requesting party is complete；

If the account information of the requesting party is imperfect, the requesting party is judged for abnormal user, the account information is not Completely including lacking phone card number and/or lacking system of real name authentication information.

3. the processing method of good friend's request according to claim 1, which is characterized in that the abnormal reference for obtaining requesting party Information, including：

Obtain the login position information of requesting party；

Correspondingly, described judge whether the requesting party is abnormal user according to the abnormal reference information, including：

According to the login position information judge the requesting party whether different-place login；

If requesting party's different-place login, judge the requesting party for abnormal user.

4. the processing method of good friend's request according to claim 1, which is characterized in that the abnormal reference for obtaining requesting party Information, including：

The complained number of the requesting party is obtained by server；

Correspondingly, described judge whether the requesting party is abnormal user according to the abnormal reference information, including：

Judge whether the complained number of the requesting party is more than default complaint threshold；

If the complained number of the requesting party is more than default complaint threshold, judge the requesting party for abnormal user.

5. the processing method of good friend's request according to claim 1, which is characterized in that the abnormal reference for obtaining requesting party Information, including：

Judge whether requesting party by other users pulls in blacklist；

If the requesting party pulls in blacklist by other users, acquisition pull in before blacklist the requesting party with it is described other The chat record quantity of user；

Correspondingly, described judge whether the requesting party is abnormal user according to the abnormal reference information, including：

Judge whether the chat record quantity is more than default chat amount threshold；

If the chat record quantity is more than default chat amount threshold, judge the requesting party for abnormal user.

6. the processing method of good friend's request according to claim 1, which is characterized in that the abnormal reference for obtaining requesting party Information, including：

Obtain the chat record of requesting party and other users；

Correspondingly, described judge whether the requesting party is abnormal user according to the abnormal reference information, including：

Judge that the requesting party whether there is fraudulent act according to the chat record；

If there are fraudulent acts by requesting party, judge the requesting party for abnormal user.

7. according to the processing method of any one of claim 1-6 good friend's requests, which is characterized in that according to the exception After reference information judges whether the requesting party is abnormal user, further include：

If the requesting party is non-abnormal user, good friend's request is exported.

8. a kind of processing unit of good friend's request, which is characterized in that including：

Acquisition module obtains the abnormal reference information of requesting party when for receiving good friend's request；

Judgment module, the abnormal reference information for being obtained according to the acquisition module judge whether the requesting party is different Common family；

Request processing module shields good friend's request if being abnormal user for the requesting party.

9. a kind of computer readable storage medium, is stored thereon with computer program, which is characterized in that the program is held by processor The processing method that the good friend as described in any in claim 1-7 asks is realized when row.

10. a kind of terminal, including memory, processor and storage are on a memory and can be in the computer journey of processor operation Sequence, which is characterized in that realize that the good friend as described in claim 1-7 is any asks when the processor executes the computer program The processing method asked.