Method, device, terminal, server and storage medium for processing rule-breaking account

Abstract

The application discloses a kind of processing methods, device, terminal, server and storage medium of illegal account, involve network technical field.The method comprises: in response to the account login operation in account login interface, display illegal prompt information, illegal prompt information is used to prompt that the target account of current login exists illegal behavior, and target account is in login interception state;In response to the trigger operation to illegal prompt information, display illegal behavior processing interface, and illegal behavior processing interface contains the illegal behavior processing agreement to be signed;In response to the signing operation to illegal behavior processing agreement, display the user interface after target account login, and the login interception state of target account is released after signing illegal behavior processing agreement.Through illegal warning in account login stage, improve the touch rate of warning information, and account login can be restored after agreement signing, cannot ignore or bypass warning information, further improve the warning effect to illegal account.

Description

Technical Field

[0001] This application relates to the field of network technology, and in particular to a method, apparatus, terminal, server, and storage medium for processing unauthorized accounts. Background Technology

[0002] With the continuous development of internet technology, more and more feature-rich applications have emerged, allowing users to share content or communicate with other users using applications with different functions.

[0003] Criminals use numerous unauthorized accounts across various applications, severely impacting their user environment. For example, in instant messaging applications, criminals use unauthorized accounts to send illegal messages to other instant messaging accounts; in video sharing applications, criminals use unauthorized accounts to publish illegal videos for profit. In related technologies, warnings about unauthorized accounts within applications are typically issued via system notifications or pop-ups.

[0004] However, under the above-mentioned warning methods, the reach rate of warning information is low, and the warning information may be directly ignored or bypassed, resulting in poor warning effect on violating accounts. Summary of the Invention

[0005] This application provides a method, apparatus, terminal, server, and storage medium for processing violating accounts, which can increase the trigger rate of warning information issued by the server, thereby improving the warning effect on violating accounts. The technical solution is as follows:

[0006] On the one hand, embodiments of this application provide a method for handling accounts that violate regulations, the method comprising:

[0007] In response to the client's account login request, a violation notification message is sent to the client. The violation notification message is used to indicate that the target account currently logged in by the client has violated regulations and that the target account is in a login blocking state.

[0008] The violation handling protocol is sent to the client, which is used to display the violation handling protocol in the violation handling interface. The violation handling interface is displayed by the client when it receives a trigger operation for the violation prompt information.

[0009] In response to the signing notification sent by the client, the login blocking status of the target account is lifted. The signing notification is sent by the client when it receives the signing operation for the violation handling agreement, and the target account whose login blocking status has been lifted is allowed to log in.

[0010] On the other hand, embodiments of this application provide a method for handling accounts that have violated regulations, the method comprising:

[0011] In response to an account login operation on the account login interface, a violation notification message is displayed. The violation notification message is used to indicate that the currently logged-in target account has committed a violation and that the target account is in a login blocking state.

[0012] In response to the triggering operation of the violation prompt information, a violation handling interface is displayed, which contains a violation handling agreement to be signed;

[0013] In response to the signing of the violation handling agreement, the user interface after the target account logs in is displayed, wherein the login blocking status of the target account is lifted after the violation handling agreement is signed.

[0014] On the other hand, embodiments of this application provide a device for processing violating accounts, the device comprising:

[0015] The first sending module is used to respond to the client's account login request and send a violation notification message to the client. The violation notification message is used to indicate that the target account currently logged in by the client has violated regulations and that the target account is in a login blocking state.

[0016] The second sending module is used to send a violation handling protocol to the client. The client is used to display the violation handling protocol in the violation handling interface. The violation handling interface is displayed by the client when it receives a trigger operation for the violation prompt information.

[0017] The removal module is used to remove the login blocking status of the target account in response to the signing notification sent by the client. The signing notification is sent by the client when it receives the signing operation of the violation handling agreement, and the target account whose login blocking status has been removed is allowed to log in.

[0018] On the other hand, embodiments of this application provide a device for processing violating accounts, the device comprising:

[0019] The first display module is used to respond to the account login operation in the account login interface and display violation prompt information. The violation prompt information is used to indicate that the currently logged-in target account has violated the rules and that the target account is in a login blocking state.

[0020] The second display module is used to display a violation handling interface in response to the triggering operation of the violation prompt information. The violation handling interface contains a violation handling agreement to be signed.

[0021] The login module is used to display the user interface of the target account after login in response to the signing operation of the violation handling agreement, wherein the login blocking status of the target account is lifted after signing the violation handling agreement.

[0022] On the other hand, embodiments of this application provide a server, the server including a processor and a memory, the memory storing at least one piece of program code, the at least one piece of program code being loaded and executed by the processor to implement the server-side method for handling unauthorized accounts as described above.

[0023] On the other hand, embodiments of this application provide a terminal, which includes a processor and a memory. The memory stores at least one piece of program code, which is loaded and executed by the processor to implement the method for handling unauthorized accounts on the terminal side as described above.

[0024] On the other hand, embodiments of this application provide a computer program product or computer program that includes computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the method for handling unauthorized accounts provided above.

[0025] In this embodiment, by setting the target account with violations to a login blocking state, the client is restricted from directly logging into the target account. Before the account login, the violation of the target account is prompted, guiding the user to sign a violation handling agreement in the violation handling interface, thereby lifting the login blocking state of the target account and restoring the login permission of the target account. Since the violation warning is given at the account login stage, the reach of the warning information can be improved. Moreover, since the user needs to sign the agreement before the account login can be restored, the user cannot ignore or bypass the warning information, which further improves the warning effect on the violating account. Attached Figure Description

[0026] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0027] Figure 1 A schematic diagram of an implementation environment provided by an exemplary embodiment of this application is shown;

[0028] Figure 2A flowchart illustrating a method for handling unauthorized accounts provided in an exemplary embodiment of this application is shown;

[0029] Figure 3 This is a schematic diagram of the interface illustrating the implementation process of a method for handling unauthorized accounts provided in an exemplary embodiment of this application.

[0030] Figure 4 This is a screenshot of the interface showing the process of a violating account being notified by the server to be taken offline;

[0031] Figure 5 A flowchart illustrating a method for handling unauthorized accounts provided in another exemplary embodiment of this application is shown;

[0032] Figure 6 A flowchart illustrating a method for handling unauthorized accounts provided in another exemplary embodiment of this application is shown;

[0033] Figure 7 This is a schematic diagram illustrating an exemplary embodiment of the process for handling unauthorized accounts provided in this application;

[0034] Figure 8 This is a sequence diagram of the interaction process between the client and the server during the handling of a violation account, provided in an exemplary embodiment of this application.

[0035] Figure 9 This is a structural block diagram of a device for processing unauthorized accounts provided in an exemplary embodiment of this application;

[0036] Figure 10 This is a structural block diagram of a device for processing unauthorized accounts provided in another exemplary embodiment of this application;

[0037] Figure 11 This invention provides a schematic diagram of the structure of a server according to an exemplary embodiment of the present application.

[0038] Figure 12 A structural block diagram of a terminal provided in an exemplary embodiment of this application is shown. Detailed Implementation

[0039] To make the objectives, technical solutions, and advantages of this application clearer, the embodiments of this application will be described in further detail below with reference to the accompanying drawings.

[0040] The method for handling illegal accounts provided in this application can be used to handle illegal accounts in various applications, so as to achieve the effect of warning non-malicious illegal accounts (accounts used by natural persons) and to discover and ban malicious illegal accounts (accounts controlled by plug-ins or robots).

[0041] In one possible application scenario, the method for handling violating accounts provided in this application embodiment can be applied to instant messaging applications, social applications, or video sharing applications. Taking instant messaging applications as an example, by obtaining instant messaging messages sent by an instant messaging account, and / or obtaining shared content or comments distributed by the instant messaging account on a sharing platform, the server can identify violating instant messaging accounts that have engaged in illegal activities. During the login phase of the violating instant messaging account, the server intercepts the login and sends a violation notification to the instant messaging client, informing the user of the existing violation and guiding the user to sign a violation handling agreement. Only after signing the agreement can the user remove the login interception on the server side and log in to the account again.

[0042] In another possible application scenario, the method for handling non-compliant accounts provided in this application embodiment can be applied to payment applications or shopping applications. Taking a shopping application as an example, by obtaining data such as the shopping account's historical shopping records, historical review records, and historical refund records, the server can identify non-compliant shopping accounts that have engaged in non-compliant behavior (such as malicious refunds, malicious review manipulation, and malicious order manipulation). During the login phase of the non-compliant shopping account, the server intercepts the login and sends a violation notice to the shopping client, informing the user of the non-compliant purchase behavior and guiding the user to sign a violation handling agreement. Only after signing the agreement can the user remove the login interception on the server side and log in to the account again.

[0043] Since violation alerts are issued during the account login phase, the reach rate of violation alerts can reach 100%. Furthermore, because users need to manually sign the violation handling agreement, and malicious violation accounts are usually controlled by preset programs, malicious violation accounts cannot be restored to login in a timely manner after being blocked, which improves the detection and banning efficiency of malicious violation accounts.

[0044] Of course, in addition to the above application scenarios, the solution provided in this application embodiment can also be applied to other scenarios where it is necessary to effectively warn accounts that violate regulations. The above scenarios are only for illustrative purposes and do not constitute a limitation.

[0045] Figure 1 A schematic diagram of an implementation environment provided by an exemplary embodiment of this application is shown. This implementation environment includes a terminal 110 and a server 120. The terminal 110 and the server 120 communicate via a communication network. Optionally, the communication network can be a wired network or a wireless network, and the communication network can be at least one of a local area network (LAN), a metropolitan area network (MAN), and a wide area network (WAN).

[0046] Terminal 110 is an electronic device running an application client. This electronic device can be a mobile terminal such as a smartphone, tablet, or laptop computer, or a terminal such as a desktop computer or a projector computer; this embodiment of the application does not limit the specific type of device.

[0047] The application clients running in terminal 110 may include instant messaging clients, social clients, video sharing clients, game clients, shopping clients, payment clients, news reading clients, etc., and this application embodiment does not limit them.

[0048] In one possible implementation, the client running on terminal 110 has a violation reporting function. This violation reporting function can be implemented by the client analyzing and reporting user behavior data, or by the client using a backend server (reporting user behavior data to the backend server for analysis), or by the user through a violation reporting portal provided by the client (reporting other accounts for violations).

[0049] Server 120 can be a standalone physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server providing basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, content delivery networks (CDNs), and big data and artificial intelligence platforms. In this embodiment, server 120 is the backend server for the client in terminal 110, and server 120 has the function of blocking user account logins.

[0050] In this embodiment, for accounts exhibiting violations, server 120 sets the violating account to a login blocking state. When a client attempts to log in with the violating account, server 120, based on the login blocking state, prohibits the violating account from logging in and issues a warning regarding the violation.

[0051] In one possible application scenario, such as Figure 1 As shown, server 120 receives an account login request sent by terminal 110, and when it determines that the account to be logged in is in a login blocking state based on the account information contained in the account login request, it prohibits the account from logging in, and based on the account's violation behavior, it retrieves the violation behavior handling protocol matching the violation behavior from protocol database 130, and then sends violation prompt information and violation behavior handling protocol to terminal 110.

[0052] After receiving the violation handling agreement, terminal 110 displays it and sends a signing notification to server 120 after receiving the agreement signing operation.

[0053] After receiving the signing notification, server 120 removes the login blocking status of the account and writes the agreement signing record into the historical violation database 140, so that the account can be held accountable or punished in the future based on the agreement signing record.

[0054] As can be seen from the above application scenarios, the client and server work together to issue warnings to violating accounts during the login phase, making it impossible for users to ignore or bypass the warnings. This also avoids the problem of warnings not being displayed properly due to the violating account being offline, thus improving the reach rate of violation warnings. Furthermore, by guiding users to sign a violation handling agreement, on the one hand, it can increase the awareness of non-malicious violators regarding their violations, thereby preventing them from violating the rules again. On the other hand, the signed agreement can serve as the basis for holding malicious violators accountable in the future.

[0055] For ease of description, the following embodiments are applied to methods for handling violating accounts. Figure 1 The implementation environment shown is an example for illustration.

[0056] Figure 2 A flowchart illustrating a method for handling unauthorized accounts provided in an exemplary embodiment of this application is shown. This embodiment uses this method for... Figure 1 Taking terminal 110 as an example, the method includes the following steps.

[0057] Step 201: In response to the account login operation on the account login interface, display a violation notice. The violation notice is used to indicate that the currently logged-in target account has committed a violation and that the target account is in a login blocking state.

[0058] In one possible implementation, when logging into a target account via a client, the client sends an account login request containing account information to the server. Based on the account information in the login request, the server determines whether the target account has engaged in any violations. If the target account has engaged in violations, the server rejects the client's login request and sends a violation notification to the client. The client then displays the received violation notification.

[0059] Among them, accounts that have violated regulations are in a login blocking state. This login blocking state indicates that the account login will be blocked before the violation is processed, meaning the account cannot log in. Furthermore, this login blocking state is maintained by the server, thus preventing circumvention through methods such as restarting the client or changing devices.

[0060] Optionally, the violation notification may include information about the violation committed by the target account, such as the type of violation, the time the violation was triggered, etc.

[0061] Indicative, such as Figure 3 As shown, if the currently logged-in account "Zhang San" on the client has violated the rules, when the client receives the account login operation in the account login interface 31, the client will prompt that the login is restricted through the pop-up window 311. When the user clicks the OK control in the pop-up window 311, the client will display the violation prompt information 32 sent by the server.

[0062] Step 202: In response to the triggering operation of the violation prompt information, the violation handling interface is displayed, which contains a violation handling agreement to be signed.

[0063] In one possible implementation, when a trigger operation for a violation notification is received, the client displays a violation handling interface and shows the violation handling protocol obtained from the server on this interface. This violation handling protocol can be sent by the server along with the violation notification, or it can be requested by the client from the server when it receives the trigger operation for the violation notification.

[0064] Optionally, the violation handling agreement is determined based on the violation behavior of the target account, and the violation handling agreement includes agreement content and an agreement signing control so that users can sign the agreement through the agreement signing control.

[0065] Indicative, such as Figure 3 As shown, the client displays the violation handling agreement in the violation handling interface 33, and each agreement contains a corresponding checkbox control.

[0066] Step 203: In response to the signing of the violation handling agreement, the user interface after the target account logs in is displayed, wherein the login blocking status of the target account is lifted after the violation handling agreement is signed.

[0067] In this embodiment of the application, the signing operation of the violation handling agreement is used to remove the login interception status of the target account.

[0068] In one possible implementation, upon receiving a signing request for the violation handling agreement, the client redisplays the account login interface. After the login blocking state is lifted, upon receiving another account login request on the account login interface, the client resends the account login request to the server, thereby completing the target account login and displaying the user interface after account login. Alternatively, upon receiving a signing request for the violation handling agreement, the client can directly send an account login request to the server, without requiring the user to perform the account login operation again.

[0069] Indicative, such as Figure 3 As shown, when the client receives a checkmark operation for each violation handling agreement in the violation handling interface 33 and a click operation for the submit control 331, the client confirms that it has received the agreement signing operation and displays the login redirect interface 34. When the client receives a click operation for the login confirmation control 341, the client re-logins to the account "Zhang San" and displays the post-login message interface 35.

[0070] Since the login blocking status of the target account is maintained on the server side, to ensure normal account login after the agreement is signed, optionally, in response to the signing operation of the violation handling agreement, the client sends a signing notification to the server. Upon receiving the signing notification, the server removes the login blocking status of the target account and sends a status removal command to the client. Correspondingly, after receiving the status removal command, the client sends an account login request to the server and displays the target account's logged-in user interface upon successful login.

[0071] Optionally, to ensure that users sign the agreement after reading it, the client sets a minimum display duration for the agreement. The client will only respond to the signing operation when the display duration of the violation handling agreement reaches this minimum. For example, the minimum display duration is 10 seconds.

[0072] In summary, in this embodiment, by setting the target account with violations to a login blocking state, the client is restricted from directly logging into the target account. Before the account login, the violation of the target account is prompted, guiding the user to sign a violation handling agreement in the violation handling interface. This removes the login blocking state of the target account and restores the login permission of the target account. Since the violation warning is given at the account login stage, the reach of the warning information can be improved. Moreover, since the user needs to sign the agreement before the account login can be restored, the user cannot ignore or bypass the warning information, which further improves the warning effect on the violating account.

[0073] Since violation alerts are issued during the account login phase, the reach rate of violation alerts can reach 100%. Furthermore, because users need to manually sign the violation handling agreement, and malicious violation accounts are usually controlled by preset programs, malicious violation accounts cannot be restored to login in a timely manner after being blocked, which improves the detection and banning efficiency of malicious violation accounts.

[0074] Some applications save account login status on both the server and client sides after login, thus avoiding the need to log in through the account login interface every time. To address this, and to prevent logged-in accounts from continuing to violate rules, one possible implementation is as follows: For a target account exhibiting violations, the server retrieves the target account's status. If the target account is logged in, the server sends an offline notification to the client (and deletes the login status saved on the server side). Correspondingly, the client displays the offline notification and logs out (and deletes the login status saved locally on the client). Subsequent logins will require the user to log in again through the account login interface.

[0075] Indicative, such as Figure 4 As shown, the account "Zhang San" is logged in, and the client displays message interface 41. When the account "Zhang San" has violated the rules, the server sends an offline notification to the client. After receiving the offline notification, the client displays the offline notification through pop-up window 411, instructing the client to log in to the account again.

[0076] The above embodiments illustrate the process for handling unauthorized accounts on the terminal side. The following describes the process for handling unauthorized accounts on the server side.

[0077] Figure 5 A flowchart illustrating a method for handling violating accounts provided in another exemplary embodiment of this application is shown. This embodiment uses this method for... Figure 1 Taking server 120 as an example, the method includes the following steps.

[0078] Step 501: In response to the client's account login request, send a violation notification message to the client. The violation notification message is used to inform the client that the target account currently logged in has engaged in violation behavior and that the target account is in a login blocking state.

[0079] In this embodiment, the server maintains the status information of each account. When it receives an account login request from the client, the server determines whether the target account is in a login blocking state based on the status information. If the server identifies that the target account is in a login blocking state, it sends a violation notice to the client and rejects the account login request.

[0080] In some embodiments, the login blocking status is a state set by the server for a violating account when it identifies that the account has committed a violation. The login blocking status will remain until the user takes action against the violation. Consequently, the login behavior of the violating account will be blocked, and the client will not be able to be used.

[0081] To inform users of the reason for account login failure, the server may optionally include violation information in the violation notification message sent by the target account, such as the type of violation, the time the violation was triggered, etc.

[0082] Step 502: Send the violation handling protocol to the client. The client is used to display the violation handling protocol in the violation handling interface. The violation handling interface is displayed by the client when it receives a trigger operation for the violation prompt information.

[0083] In one possible implementation, when the client receives a trigger operation for a violation alert, the client displays a violation handling interface and shows the violation handling protocol obtained from the server on this interface. This violation handling protocol can be sent by the server along with the violation alert, or it can be actively requested by the client upon receiving the trigger operation for the violation alert; this embodiment does not limit this approach.

[0084] In some embodiments, since there are a large number of different types of violations and the severity of violations varies among different violating accounts, in order to improve the accuracy and relevance of the protocol content, the server retrieves a violation handling protocol from the protocol database that matches the violation of the target account.

[0085] Optionally, the violation handling agreement includes agreement content and an agreement signing control, allowing users to sign the agreement using the agreement signing control.

[0086] Step 503: In response to the signing notification sent by the client, the login blocking status of the target account is lifted. The signing notification is sent by the client when it receives the signing operation of the violation handling agreement, and the target account whose login blocking status has been lifted is restored to login.

[0087] In this embodiment, the signing operation of the violation handling agreement is used to remove the login blocking status of the violating account. Therefore, when the client receives the signing operation of the violation handling agreement, it sends a signing notification to the server. After receiving the signing notification, the server removes the login blocking status of the target account and restores the account login function of the target account. Optionally, the signing notification includes the account information of the target account and the agreement signing content.

[0088] In one possible implementation, after the server removes the login blocking status of the target account, it sends a status removal instruction to the client. The client then resends the account login request according to the status removal instruction, thereby completing the login of the target account.

[0089] The above solution maintains the login blocking status of violating accounts through the server, and uses the agreement signing action as a condition for lifting the login blocking status. Even if users change devices or clients to log in, the server will still block the login, making it impossible for users to ignore or bypass the violation warning, thus improving the warning effect. Simultaneously, by guiding users to sign the violation handling agreement, non-malicious violators are clearly aware of the violations they have committed, thereby avoiding future violations. For malicious violators, the signed violation handling agreement serves as the basis for subsequent penalties and accountability, improving the effectiveness of penalties and accountability for violating accounts.

[0090] In summary, in this embodiment, by setting the target account with violations to a login blocking state, the client is restricted from directly logging into the target account. Before the account login, the violation of the target account is prompted, guiding the user to sign a violation handling agreement in the violation handling interface. This removes the login blocking state of the target account and restores the login permission of the target account. Since the violation warning is given at the account login stage, the reach of the warning information can be improved. Moreover, since the user needs to sign the agreement before the account login can be restored, the user cannot ignore or bypass the warning information, which further improves the warning effect on the violating account.

[0091] Figure 6 A flowchart illustrating a method for handling violating accounts provided in another exemplary embodiment of this application is shown. This embodiment uses this method for... Figure 1 Taking server 120 as an example, the method includes the following steps.

[0092] Step 601: In response to the identification of a violation by the target account based on the account behavior data of the target account, a login blocking flag is set for the target account. The login blocking flag is used to indicate that the target account is in a login blocking state.

[0093] In one possible implementation, the client reports account behavior data of the target account to the server. Upon receiving the account behavior data, the server identifies whether the target account has engaged in any violations. The server can analyze the account behavior data using a pre-set account behavior analysis program to obtain the analysis results, or it can be manually analyzed by business personnel to obtain the analysis results; this embodiment does not limit this approach. For target accounts identified as having engaged in violations, the server sets a login blocking flag for that target account, thereby indicating that the target account is in a login blocking state.

[0094] Optionally, the account behavior data may be the target account's chat history data, sharing data, comment data, payment data, order data, refund data, etc., but this embodiment does not limit this.

[0095] Step 602: Determine the target violation type for the target account and set a target violation type identifier for the target account.

[0096] Furthermore, in order to facilitate the subsequent determination of what kind of violation notice to send to the target account and the violation handling agreement, the server determines the target violation type of the target account based on the account behavior data and sets the corresponding target violation type identifier for the target account.

[0097] It should be noted that this embodiment only illustrates the example of the server side determining the account's violations and violation types. In other possible implementations, when the client has the ability to identify violations, the client can also directly report violation data to the server, and the server can directly mark the violating account. This embodiment does not limit this.

[0098] In an illustrative example, the server maintains a violation status table based on the identified account and violation type, as shown in Table 1.

[0099] Table 1

[0100] account number Login interception flag Violation type label Zhangsan √ 001 Lisi × / Wangwu √ 002

[0101] Among them, violation type identifier 001 indicates that the account has engaged in the violation of disseminating gambling information, and violation type identifier 002 indicates that the account has engaged in the violation of disseminating obscene information.

[0102] Step 603: Obtain the account status of the target account.

[0103] To avoid requiring users to log in to their accounts every time they use the client, both the server and client sides save the account login status. To prevent a logged-in account from continuing to violate the rules, the server retrieves the current account status of the identified account, which includes both logged-in and offline status.

[0104] If the target account is currently offline, the server executes step 605 below; if the target account is currently logged in, step 604 is executed to log the target account offline.

[0105] Step 604: In response to the target account being logged in, an offline notification is sent to the client. The offline notification is used to notify the target account of any violations, and the client is used to log out of the login state based on the offline notification.

[0106] In one possible implementation, when the target account is logged in, the server calls the offline application programming interface (API) to send an offline notification to the client, switching the target account from logged-in to offline status. Upon receiving the offline notification, the client logs out, and subsequent users will need to log in again through the account login interface.

[0107] Indicative, such as Figure 7 As shown, when business personnel identify that an account has violated regulations and the violating account is currently logged in, they call the offline API 72 through server 71 to notify the violating account to be taken offline.

[0108] Step 605: In response to the client's account login request and upon recognizing that the target account has a login blocking flag set, a violation notification message is sent to the client.

[0109] Because login blocking flags are pre-set for accounts exhibiting violations, the server, upon receiving a login request, can determine whether login blocking is necessary by checking if the requesting account has a login blocking flag set. In this embodiment, since the target account has a login blocking flag set, the server rejects the target account's login request and sends a violation notification to the client.

[0110] Indicative, such as Figure 7 As shown, when the violating account logged in on client 73 goes offline, the user needs to log in again through the account login interface. After client 73 sends an account login request to server 71, server 71 reads the text configuration to be displayed (i.e., violation prompt information) from the pop-up text configuration file 74 according to the type of violation of the violating account, and sends the text to client 73 for display, guiding the user to handle the violation.

[0111] Step 606: Obtain the violation handling protocol that matches the target violation type identifier, wherein different violation types correspond to different violation handling protocols.

[0112] In one possible implementation, the server has a pre-configured protocol database that stores violation handling protocols corresponding to different violation types. For example, the protocol database stores violation handling protocols for disseminating gambling or betting information, disseminating obscene information, disseminating false information, and so on.

[0113] When sending a violation handling protocol to the client, the server searches for a matching violation handling protocol in the protocol database based on the target violation type identifier corresponding to the target account.

[0114] Indicative, such as Figure 7 As shown, server 71 reads the corresponding violation handling protocol from protocol database 75 according to the violation type of the violating account, and sends it back to client 73 so that the user can sign the protocol.

[0115] Step 607: Send the obtained violation handling agreement to the client.

[0116] Furthermore, the server sends the obtained violation handling protocol to the client.

[0117] Step 608: In response to the signing notification sent by the client, delete the login blocking identifier set for the target account.

[0118] Once a user signs the issued violation handling agreement, the server receives a signing notification from the client, thereby deleting the login blocking flag previously set for the target account and lifting the login blocking status for the target account.

[0119] In some possible scenarios, when the server blocks login to a target account, it also sets a ban duration for the target account. During this ban duration, even if the user signs the violation handling agreement, the login blocking status of the target account cannot be lifted immediately.

[0120] In one possible implementation, in response to a signature notification sent by the client, the server obtains the ban duration of the target account and, upon reaching the ban duration, lifts the login blocking status of the target account (i.e., deletes the login blocking identifier). The ban duration is determined based on the target account's violations, such as the type and frequency of violations.

[0121] Step 609: Update the historical violation records corresponding to the target account in the historical violation database. The historical violation records shall at least include the violation type of the historical violation and the agreement signing record.

[0122] For maliciously violating accounts, subsequent account penalties or accountability require corresponding agreement signing records as evidence. Therefore, after the server removes the login blocking status of the target account, it writes the historical violation record corresponding to the target account into the historical violation database for retrieval during subsequent penalties and accountability. This historical violation record includes the target account's agreement signing record and the violation type corresponding to each agreement signing record. The agreement signing record includes the agreement signing time, the violation handling agreement, and the target account's signature.

[0123] Indicative, such as Figure 7 As shown, after the user reads and signs the violation handling agreement, the client 73 logs in to the account again, and the server 71 writes the historical violation record into the historical violation database 76.

[0124] In this embodiment, the server identifies and restricts the login behavior of violating accounts by setting login interception flags for them, thereby improving the accuracy of login interception. At the same time, after the user signs the agreement, the login interception flag corresponding to the account is deleted, the login function of the account is restored, and the normal use of the account is guaranteed after the violation is dealt with.

[0125] Furthermore, in this embodiment, the server sends a corresponding violation handling agreement to the client based on the type of violation, which improves the targeting of violation warnings; and after the agreement is signed, the server will update the historical violation records of the violating account in the historical violation database, providing a basis for subsequent penalties and accountability.

[0126] For accounts exhibiting the same violation, the account may be a non-malicious account (usually violating unintentionally with a low frequency of violations) or a malicious account (violating intentionally with a high frequency of violations). In order to provide different levels of violation warnings for different types of accounts, in one possible implementation, when the server obtains the violation handling protocol, it retrieves the number of violations corresponding to the target violation type from the historical violation records of the target account, and then obtains the violation handling protocol that matches the target violation type identifier and the number of violations (from the protocol database).

[0127] In an illustrative example, the correspondence between violation types, violation counts, and violation handling protocols in the protocol database is shown in Table 2.

[0128] Table 2

[0129] Violation type label Number of violations Agreement on Handling Violations 001 1-2 times Agreement A 001 More than 2 times Agreement B 002 1-2 times Protocol C 002 More than 2 times Protocol D

[0130] In other possible implementations, the server may also determine the duration of the ban on the violating account based on the type and number of violations, wherein the ban duration is positively correlated with the number of violations, and this embodiment does not limit this.

[0131] To further identify malicious accounts from among the violating accounts, in some embodiments, the historical violation records also include historical violation data. For example, for instant messaging applications, this violation data may include chat data and comment data containing violations; for video classification applications, this violation data may include video data containing violations. This application does not limit the specific form of the violation data.

[0132] Optionally, before sending the violation handling protocol to the target account, the server obtains historical violation data corresponding to the target violation type from the historical violation records of the target account, and determines the similarity between the historical violation data and the current violation data.

[0133] In one possible implementation, the server pre-trains a violation evaluation model using a deep learning neural network, thereby taking historical and current violation data as input to the model and outputting the similarity of violations through the violation evaluation model.

[0134] When the violation data is text data, the violation evaluation model can be a text similarity evaluation model (the input is the vectorized data of the file). When the violation data is video data, the violation evaluation model can be a video similarity evaluation model (the input is a sequence of video frames). This embodiment does not limit this.

[0135] If the similarity of the violation is lower than the similarity threshold (e.g., 80%), a violation handling agreement matching the target violation type identifier and the number of violations is obtained, and the target account is determined to be a non-malicious violation account.

[0136] If the similarity of the violations is higher than the similarity threshold, the server determines that the target account is a malicious violation account because the target account frequently commits violations and the similarity of the violations is high. In this way, the server obtains a violation handling protocol that matches the target violation type identifier and the weighted violation count, where the weighted violation count is greater than the number of violations.

[0137] In one possible implementation, the weighted number of violations is determined based on a weight (greater than 1) and the number of violations, and the weight is positively correlated with the similarity of the violations. For example, the weight is n × the similarity of the violations.

[0138] Optionally, for malicious accounts that violate regulations, the server may issue a violation handling agreement and simultaneously ban the malicious account.

[0139] In this embodiment, by performing similarity analysis on the historical violations of the same account, and when the similarity is high, the account is identified as a malicious violation account, and thus the account is processed in a different way than non-malicious violation accounts, thereby enhancing the processing effect of malicious violation accounts.

[0140] Furthermore, for non-malicious accounts, since these accounts are user-controlled, users typically take immediate action to address the violation when the account is notified to be offline due to misconduct. However, for malicious accounts, since these accounts are usually controlled by programs rather than real users, the violation cannot be addressed promptly when the account is notified to be offline. In one possible implementation, to further distinguish between malicious and non-malicious accounts and thus handle different types of accounts differently, after the server sends an offline notification to the client, if no signature notification is received within a predetermined time after sending the offline notification, the server sets a pending flag for the target account. The pending flag indicates that the target account is a pending malicious account, which is an account controlled by a bot.

[0141] Optionally, the predetermined duration is determined based on the historical signing duration of violation handling agreements for different accounts. In some embodiments, the server obtains the historical signing duration of similar violation handling agreements and determines the predetermined duration based on the historical signing duration. For example, the server clusters the historical signing durations and calculates the average of the historical signing durations in the clusters to obtain the predetermined duration. After issuing an offline notification, the server starts a timer for the predetermined duration and checks whether a signing notification is received within the timer duration.

[0142] Furthermore, when the target account commits another violation and the target account has a pending flag set, in order to further determine whether the target account is a malicious violation account, in one possible implementation, the server generates a violation handling protocol containing interference options and sends the violation handling protocol containing interference options to the client (sent when the target account requests login).

[0143] The "interference options" are those that do not comply with the requirements for signing the violation handling agreement. For example, these interference options might be options indicating disagreement with the agreement's terms, or options unrelated to the agreement's terms.

[0144] For maliciously violating accounts, since these accounts are usually controlled by bots, and bots cannot autonomously identify interference options, even if a bot can autonomously sign the agreement, there is still a high probability that it will choose the interference option. Accordingly, when a client receives an operation to select an interference option, it sends a signing error notification to the server. Upon receiving the signing error notification, the server sets a malicious flag for the target account, enabling special handling of maliciously violating accounts in the future.

[0145] In this embodiment, when a suspected malicious account commits another violation, a violation handling protocol containing interference options is generated for the account to test whether the account is controlled by a robot. Based on the test results, a malicious label is set for the account, thereby realizing the detection of malicious accounts through protocol signing and improving the efficiency and accuracy of malicious account identification.

[0146] In conjunction with the above embodiments, in an illustrative example, the interaction process between the client and the server when processing violating accounts is as follows: Figure 8 As shown.

[0147] 801, the user has committed a violation while using the client.

[0148] 802, the client reports account behavior data to the server.

[0149] 803, Business personnel's perceived data.

[0150] 804, Business personnel configure the server interface, configure violation notification information and protocols.

[0151] 805 indicates that the server determines the violation notification information and protocol to be issued based on the configuration file and interface parameters.

[0152] Error 806: The server flags the account as being in a login blocked state and notifies the client to log off.

[0153] 807, the client notifies the user that they have been forcibly logged out.

[0154] Error 808: The user has triggered a re-login.

[0155] 809. The client guides users to view the violation notification and sign the agreement.

[0156] 810, the user has completed the agreement signing.

[0157] 811, The client reports the signing notification to the server.

[0158] 812, the server removes the login blocking status and stores historical violation records.

[0159] 813, the client notifies the user that they can log in normally.

[0160] 814, the user is logged in and using the client normally.

[0161] Figure 9 This is a structural block diagram of a device for processing unauthorized accounts provided in an exemplary embodiment of this application, such as... Figure 9 As shown, the device includes:

[0162] The first sending module 901 is used to respond to the client's account login request and send a violation prompt message to the client. The violation prompt message is used to indicate that the target account currently logged in by the client has violated regulations and that the target account is in a login blocking state.

[0163] The second sending module 902 is used to send a violation handling protocol to the client. The client is used to display the violation handling protocol in the violation handling interface. The violation handling interface is displayed by the client when it receives a trigger operation for the violation prompt information.

[0164] The release module 903 is used to release the login blocking status of the target account in response to the signing notification sent by the client. The signing notification is sent by the client when it receives the signing operation of the violation handling agreement, and the target account whose login blocking status has been released is allowed to log in.

[0165] Optionally, the device includes:

[0166] The first identification module is used to set a login blocking identifier for the target account in response to the identification of illegal behavior of the target account based on the account behavior data of the target account. The login blocking identifier is used to indicate that the target account is in the login blocking state.

[0167] The first sending module 901 is used for:

[0168] In response to the client's account login request, and upon recognizing that the target account has the login blocking flag set, the violation notification message is sent to the client;

[0169] The release module 903 is used for:

[0170] Delete the login blocking identifier set for the target account.

[0171] Optionally, the device further includes:

[0172] The type determination module is used to determine the target violation type of the target account and set a target violation type identifier for the target account;

[0173] The second transmitting module 902 includes:

[0174] The protocol acquisition unit is used to acquire the violation behavior processing protocol that matches the target violation type identifier, wherein different violation types correspond to different violation behavior processing protocols;

[0175] The protocol sending unit is used to send the obtained violation handling protocol to the client.

[0176] Optionally, the device further includes:

[0177] The update module is used to update the historical violation records corresponding to the target account in the historical violation database. The historical violation records include at least the violation type of the historical violation and the agreement signing record.

[0178] The protocol acquisition unit is used for:

[0179] Obtain the number of violations corresponding to the target violation type from the historical violation records corresponding to the target account;

[0180] Obtain the violation handling protocol that matches the target violation type identifier and the number of violations.

[0181] Optionally, the historical violation records may also include historical violation data;

[0182] The protocol acquisition unit is further configured to:

[0183] Obtain historical violation data corresponding to the target violation type from the historical violation records corresponding to the target account;

[0184] Determine the similarity of violations between the historical violation data and the current violation data;

[0185] If the similarity of the violation is lower than the similarity threshold, then the step of obtaining the violation processing protocol that matches the target violation type identifier and the number of violations is executed;

[0186] If the similarity of the violation is higher than the similarity threshold, then the violation processing protocol that matches the target violation type identifier and the weighted violation count is obtained, wherein the weighted violation count is greater than the number of violations.

[0187] Optionally, the device further includes:

[0188] The status acquisition module is used to acquire the account status of the target account;

[0189] The offline notification module is used to send an offline notification to the client in response to the target account being in a logged-in state. The offline notification is used to notify the target account of any violations, and the client is used to log out of the logged-in state according to the offline notification.

[0190] Optionally, the device further includes:

[0191] The second identification module is used to set a pending identification for the target account if the signing notification is not received within a predetermined time after the offline notification is sent. The pending identification is used to indicate that the target account is a pending malicious violation account. The malicious violation account is an account controlled by a robot. The predetermined time is determined based on the historical signing time of different accounts for violation handling agreements.

[0192] A generation module is used to generate a violation handling protocol containing interference options in response to the target account committing a violation again and the target account having the pending identifier set.

[0193] The second sending module 902 is further configured to send a violation handling protocol containing the interference options to the client;

[0194] An identification module is used to set a malicious identifier for the target account in response to a signing error notification sent by the client. The signing error notification is sent by the client when it receives a selection operation for the interference option. The malicious identifier is used to characterize the target account as a malicious and non-compliant account.

[0195] Optionally, the release module 903 is further configured to:

[0196] In response to the signing notification sent by the client, the duration of the ban on the target account is obtained, and the duration of the ban is determined based on the violation of the target account.

[0197] When the specified ban duration is reached, the login blocking status of the target account is lifted.

[0198] Figure 10 This is a structural block diagram of a device for processing unauthorized accounts provided in another exemplary embodiment of this application, such as... Figure 10 As shown, the device includes:

[0199] The first display module 1001 is used to respond to the account login operation in the account login interface and display violation prompt information, the violation prompt information being used to indicate that the currently logged-in target account has violated regulations;

[0200] The second display module 1002 is used to display a violation handling interface in response to the triggering operation of the violation prompt information. The violation handling interface includes a violation handling agreement to be signed.

[0201] The login module 1003 is used to display the user interface of the target account after login in response to the signing operation of the violation handling agreement.

[0202] Optionally, the login module 1003 is used for:

[0203] In response to the signing operation of the violation handling agreement, a signing notification is sent to the server, the signing notification being used to instruct the server to lift the login blocking status of the target account;

[0204] In response to receiving the status cancellation instruction sent by the server, an account login request is sent to the server, and the user interface after the target account is logged in is displayed.

[0205] Optionally, the device further includes:

[0206] The offline module is used to display an offline notification and exit the login state in response to the target account being in a logged-in state. The offline notification is sent by the server.

[0207] In this embodiment, by setting the target account with violations to a login blocking state, the client is restricted from directly logging into the target account. Before the account login, the violation of the target account is prompted, guiding the user to sign a violation handling agreement in the violation handling interface, thereby lifting the login blocking state of the target account and restoring the login permission of the target account. Since the violation warning is given at the account login stage, the reach of the warning information can be improved. Moreover, since the user needs to sign the agreement before the account login can be restored, the user cannot ignore or bypass the warning information, which further improves the warning effect on the violating account.

[0208] In this embodiment, the server identifies and restricts the login behavior of violating accounts by setting login interception flags for them, thereby improving the accuracy of login interception. At the same time, after the user signs the agreement, the login interception flag corresponding to the account is deleted, the login function of the account is restored, and the normal use of the account is guaranteed after the violation is dealt with.

[0209] Furthermore, in this embodiment, the server sends a corresponding violation handling agreement to the client based on the type of violation, which improves the targeting of violation warnings; and after the agreement is signed, the server will update the historical violation records of the violating account in the historical violation database, providing a basis for subsequent penalties and accountability.

[0210] In this embodiment, by performing similarity analysis on the historical violations of the same account, and when the similarity is high, the account is identified as a malicious violation account, and thus the account is processed in a different way than non-malicious violation accounts, thereby enhancing the processing effect of malicious violation accounts.

[0211] In this embodiment, when a suspected malicious account commits another violation, a violation handling protocol containing interference options is generated for the account to test whether the account is controlled by a robot. Based on the test results, a malicious label is set for the account, thereby realizing the detection of malicious accounts through protocol signing and improving the efficiency and accuracy of malicious account identification.

[0212] It should be noted that the above-described embodiment of the device for processing violating accounts is merely an example of the division of the functional modules. In practical applications, the functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above. Furthermore, the above-described embodiment of the device for processing violating accounts and the embodiment of the method for processing violating accounts belong to the same concept, and their implementation process is detailed in the method embodiment, which will not be repeated here.

[0213] Please refer to Figure 11 This illustration shows a schematic diagram of the structure of a server provided in an exemplary embodiment of this application. Specifically, the server 1100 includes a Central Processing Unit (CPU) 1101, a system memory 1104 including random access memory 1102 and read-only memory 1103, and a system bus 1105 connecting the system memory 1104 and the CPU 1101. The server 1100 also includes a basic input / output system (I / O system) 1106 that facilitates the transfer of information between various devices within the computer, and a mass storage device 1107 for storing the operating system 1113, application programs 1114, and other program modules 1115.

[0214] The basic input / output system 1106 includes a display 1108 for displaying information and an input device 1109 for user input, such as a mouse or keyboard. Both the display 1108 and the input device 1109 are connected to the central processing unit 1101 via an input / output controller 1110 connected to the system bus 1105. The basic input / output system 1106 may also include the input / output controller 1110 for receiving and processing input from multiple other devices such as a keyboard, mouse, or electronic stylus. Similarly, the input / output controller 1110 also provides output to a display screen, printer, or other types of output devices.

[0215] The mass storage device 1107 is connected to the central processing unit 1101 via a mass storage controller (not shown) connected to the system bus 1105. The mass storage device 1107 and its associated computer-readable media provide non-volatile storage for the server 1100. That is, the mass storage device 1107 may include computer-readable media (not shown) such as a hard disk or drive.

[0216] Without loss of generality, the computer-readable medium may include computer storage media and communication media. Computer storage media include volatile and non-volatile, removable and non-removable media implemented using any method or technology for storing information such as computer-readable instructions, data structures, program modules, or other data. Computer storage media include random access memory (RAM), read-only memory (ROM), flash memory or other solid-state storage technologies, compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, magnetic tape cassettes, magnetic tape, disk storage, or other magnetic storage devices. Of course, those skilled in the art will recognize that the computer storage media are not limited to the above-mentioned types. The system memory 1104 and mass storage device 1107 described above can be collectively referred to as memory.

[0217] The memory stores one or more programs, which are configured to be executed by one or more central processing units 1101. The one or more programs contain instructions for implementing the methods described above, and the central processing unit 1101 executes the one or more programs to implement the methods provided in the various method embodiments described above.

[0218] According to various embodiments of this application, the server 1100 can also be connected to a remote computer on a network, such as the Internet. That is, the server 1100 can be connected to the network 1112 via the network interface unit 1111 connected to the system bus 1105, or the network interface unit 1111 can be used to connect to other types of networks or remote computer systems (not shown).

[0219] The memory further includes one or more programs stored in the memory, and the one or more programs include steps executed by the terminal in the method provided in the embodiments of this application.

[0220] Please refer to Figure 12This diagram illustrates a structural block diagram of a terminal 1400 provided in an exemplary embodiment of this application. The terminal 1400 may be a portable mobile terminal, such as a smartphone, tablet computer, Moving Picture Experts Group Audio Layer III (MP3) player, or Moving Picture Experts Group Audio Layer IV (MP4) player. The terminal 1400 may also be referred to as a user device, portable terminal, or other names.

[0221] Typically, terminal 1400 includes a processor 1401 and a memory 1402.

[0222] Processor 1401 may include one or more processing cores, such as a quad-core processor, an octa-core processor, etc. Processor 1401 may be implemented using at least one hardware form selected from Digital Signal Processing (DSP), Field-Programmable Gate Array (FPGA), and Programmable Logic Array (PLA). Processor 1401 may also include a main processor and a coprocessor. The main processor, also known as a central processing unit (CPU), is used to process data in the wake-up state; the coprocessor is a low-power processor used to process data in the standby state. In some embodiments, processor 1401 may integrate a Graphics Processing Unit (GPU), which is responsible for rendering and drawing the content to be displayed on the screen. In some embodiments, processor 1401 may also include an Artificial Intelligence (AI) processor, which is used to handle computational operations related to machine learning.

[0223] Memory 1402 may include one or more computer-readable storage media, which may be tangible and non-transitory. Memory 1402 may also include high-speed random access memory and non-volatile memory, such as one or more disk storage devices or flash memory devices. In some embodiments, the non-transitory computer-readable storage media in memory 1402 is used to store at least one instruction, which is executed by processor 1401 to implement the method provided in the embodiments of this application.

[0224] In some embodiments, the terminal 1400 may also optionally include: a peripheral device interface 1403 and at least one peripheral device. Specifically, the peripheral device includes at least one of: a radio frequency circuit 1404, a touch display screen 1405, a camera assembly 1406, an audio circuit 1407, a positioning assembly 1408, and a power supply 1409.

[0225] Peripheral interface 1403 can be used to connect at least one input / output (I / O) related peripheral device to processor 1401 and memory 1402. In some embodiments, processor 1401, memory 1402 and peripheral interface 1403 are integrated on the same chip or circuit board; in some other embodiments, any one or two of processor 1401, memory 1402 and peripheral interface 1403 can be implemented on separate chips or circuit boards, which is not limited in this embodiment.

[0226] The radio frequency (RF) circuit 1404 is used to receive and transmit radio frequency (RF) signals, also known as electromagnetic signals. The RF circuit 1404 communicates with communication networks and other communication devices via electromagnetic signals. The RF circuit 1404 converts electrical signals into electromagnetic signals for transmission, or converts received electromagnetic signals back into electrical signals. Optionally, the RF circuit 1404 includes: an antenna system, an RF transceiver, one or more amplifiers, a tuner, an oscillator, a digital signal processor, a codec chipset, a user identity module card, etc. The RF circuit 1404 can communicate with other terminals through at least one wireless communication protocol. This wireless communication protocol includes, but is not limited to: the World Wide Web, metropolitan area networks, intranets, various generations of mobile communication networks (2G, 3G, 4G, and 5G), wireless local area networks, and / or Wireless Fidelity (WiFi) networks. In some embodiments, the RF circuit 1404 may also include circuitry related to Near Field Communication (NFC), which is not limited in this application.

[0227] The touch display screen 1405 is used to display a user interface (UI). This UI may include graphics, text, icons, videos, and any combination thereof. The touch display screen 1405 also has the ability to collect touch signals on or above its surface. These touch signals can be input as control signals to the processor 1401 for processing. The touch display screen 1405 is used to provide virtual buttons and / or a virtual keyboard, also known as soft buttons and / or a soft keyboard. In some embodiments, there may be one touch display screen 1405, positioned on the front panel of the terminal 1400; in other embodiments, there may be at least two touch display screens, respectively positioned on different surfaces of the terminal 1400 or in a folded design; in still other embodiments, the touch display screen 1405 may be a flexible display screen, positioned on a curved or folded surface of the terminal 1400. Furthermore, the touch display screen 1405 may be configured as a non-rectangular, irregular shape, i.e., a non-rectangular screen. The touch display screen 1405 may be made of materials such as Liquid Crystal Display (LCD) or Organic Light-Emitting Diode (OLED).

[0228] The camera assembly 1406 is used to acquire images or videos. Optionally, the camera assembly 1406 includes a front-facing camera and a rear-facing camera. Typically, the front-facing camera is used for video calls or selfies, and the rear-facing camera is used for taking photos or videos. In some embodiments, there are at least two rear-facing cameras, which are any one of a main camera, a depth-sensing camera, and a wide-angle camera, to achieve background blurring by fusion of the main camera and the depth-sensing camera, and panoramic shooting and virtual reality (VR) shooting by fusion of the main camera and the wide-angle camera. In some embodiments, the camera assembly 1406 may also include a flash. The flash can be a single-color temperature flash or a dual-color temperature flash. A dual-color temperature flash is a combination of a warm-light flash and a cool-light flash, which can be used for light compensation at different color temperatures.

[0229] Audio circuitry 1407 provides an audio interface between the user and terminal 1400. Audio circuitry 1407 may include a microphone and a speaker. The microphone is used to collect sound waves from the user and the environment, converting the sound waves into electrical signals that are input to processor 1401 for processing, or input to radio frequency circuitry 1404 for voice communication. For stereo sound acquisition or noise reduction purposes, multiple microphones may be used, each located at a different part of terminal 1400. The microphone may also be an array microphone or an omnidirectional microphone. The speaker is used to convert electrical signals from processor 1401 or radio frequency circuitry 1404 into sound waves. The speaker may be a conventional diaphragm speaker or a piezoelectric ceramic speaker. When the speaker is a piezoelectric ceramic speaker, it can convert electrical signals not only into audible sound waves but also into inaudible sound waves for purposes such as distance measurement. In some embodiments, audio circuitry 1407 may also include a headphone jack.

[0230] Positioning component 1408 is used to locate the current geographic location of terminal 1400 in order to enable navigation or location-based service (LBS). Positioning component 1408 can be a positioning component based on the U.S. Global Positioning System (GPS), China's BeiDou system, or Russia's Galileo system.

[0231] Power supply 1409 is used to power the various components in terminal 1400. Power supply 1409 can be AC ​​power, DC power, a disposable battery, or a rechargeable battery. When power supply 1409 includes a rechargeable battery, the rechargeable battery can be a wired rechargeable battery or a wireless rechargeable battery. A wired rechargeable battery is a battery that is charged via a wired line, and a wireless rechargeable battery is a battery that is charged via a wireless coil. The rechargeable battery can also be used to support fast charging technology.

[0232] In some embodiments, the terminal 1400 further includes one or more sensors 1410. The one or more sensors 1410 include, but are not limited to: an accelerometer 1411, a gyroscope 1412, a pressure sensor 1413, a fingerprint sensor 1414, an optical sensor 1415, and a proximity sensor 1416.

[0233] Accelerometer 1411 can detect the magnitude of acceleration along the three coordinate axes of a coordinate system established by terminal 1400. For example, accelerometer 1411 can be used to detect the components of gravitational acceleration along the three coordinate axes. Processor 1401 can control touchscreen 1405 to display the user interface in landscape or portrait view based on the gravitational acceleration signal acquired by accelerometer 1411. Accelerometer 1411 can also be used for games or for acquiring user motion data.

[0234] The gyroscope sensor 1412 can detect the orientation and rotation angle of the terminal 1400. The gyroscope sensor 1412 can work in conjunction with the accelerometer sensor 1411 to collect the user's 3D movements on the terminal 1400. Based on the data collected by the gyroscope sensor 1412, the processor 1401 can perform the following functions: motion sensing (e.g., changing the UI based on the user's tilt), image stabilization during shooting, game control, and inertial navigation.

[0235] The pressure sensor 1413 can be disposed on the side bezel of the terminal 1400 and / or on the lower layer of the touch display screen 1405. When the pressure sensor 1413 is disposed on the side bezel of the terminal 1400, it can detect the user's grip signal on the terminal 1400 and perform left / right hand recognition or quick operation based on the grip signal. When the pressure sensor 1413 is disposed on the lower layer of the touch display screen 1405, it can control the operable controls on the UI interface based on the user's pressure operation on the touch display screen 1405. The operable controls include at least one of button controls, scroll bar controls, icon controls, and menu controls.

[0236] The fingerprint sensor 1414 is used to collect a user's fingerprint to identify the user's identity. When the user's identity is identified as trusted, the processor 1401 authorizes the user to perform relevant sensitive operations, including unlocking the screen, viewing encrypted information, downloading software, making payments, and changing settings. The fingerprint sensor 1414 can be located on the front, back, or side of the terminal 1400. When the terminal 1400 has a physical button or manufacturer logo, the fingerprint sensor 1414 can be integrated with the physical button or manufacturer logo.

[0237] An optical sensor 1415 is used to collect ambient light intensity. In one embodiment, the processor 1401 can control the display brightness of the touch screen 1405 based on the ambient light intensity collected by the optical sensor 1415. Specifically, when the ambient light intensity is high, the display brightness of the touch screen 1405 is increased; when the ambient light intensity is low, the display brightness of the touch screen 1405 is decreased. In another embodiment, the processor 1401 can also dynamically adjust the shooting parameters of the camera assembly 1406 based on the ambient light intensity collected by the optical sensor 1415.

[0238] The proximity sensor 1416, also known as a distance sensor, is typically located on the front of the terminal 1400. The proximity sensor 1416 is used to detect the distance between the user and the front of the terminal 1400. In one embodiment, when the proximity sensor 1416 detects that the distance between the user and the front of the terminal 1400 is gradually decreasing, the processor 1401 controls the touchscreen display 1405 to switch from a screen-on state to a screen-off state; when the proximity sensor 1416 detects that the distance between the user and the front of the terminal 1400 is gradually increasing, the processor 1401 controls the touchscreen display 1405 to switch from a screen-off state to a screen-on state.

[0239] Those skilled in the art will understand that Figure 12 The structure shown does not constitute a limitation on terminal 1400 and may include more or fewer components than shown, or combine certain components, or use different component arrangements.

[0240] This application also provides a computer-readable storage medium storing at least one instruction, at least one program, code set, or instruction set, wherein the at least one instruction, at least one program, code set, or instruction set is loaded and executed by a processor to implement the method for handling unauthorized accounts described in any of the above embodiments.

[0241] This application provides a computer program product or computer program that includes computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the method for handling unauthorized accounts described in the above embodiments.

[0242] Those skilled in the art will recognize that the functions described in the embodiments of this application in one or more of the above examples can be implemented using hardware, software, firmware, or any combination thereof. When implemented using software, these functions can be stored in a computer-readable storage medium or transmitted as one or more instructions or code on a computer-readable storage medium. Computer-readable storage media include computer storage media and communication media, wherein communication media include any medium that facilitates the transmission of a computer program from one place to another. Storage media can be any available medium accessible to a general-purpose or special-purpose computer.

[0243] The above description is merely an optional embodiment of this application and is not intended to limit this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the protection scope of this application.

Claims

1. A method for handling accounts that violate regulations, characterized in that, The method includes: In response to the client's account login request, a violation notification message is sent to the client. The violation notification message is used to indicate that the target account currently logged in by the client has violated regulations and that the target account is in a login blocking state. The violation handling protocol is sent to the client, which is used to display the violation handling protocol in the violation handling interface. The violation handling interface is displayed by the client when it receives a trigger operation for the violation prompt information. In response to the signing notification sent by the client, the login blocking status of the target account is lifted. The signing notification is sent by the client when it receives the signing operation for the violation handling agreement, and the target account whose login blocking status has been lifted is allowed to log in.

2. The method according to claim 1, characterized in that, Before sending a violation notification to the client in response to the client's account login request, the method includes: In response to the identification of a violation by the target account based on the account behavior data of the target account, a login blocking flag is set for the target account, the login blocking flag being used to indicate that the target account is in the login blocking state; The step of sending a violation notification to the client in response to the client's account login request includes: In response to the client's account login request, and upon recognizing that the target account has the login blocking flag set, the violation notification message is sent to the client; The removal of the login blocking status for the target account includes: Delete the login blocking identifier set for the target account.

3. The method according to claim 2, characterized in that, After setting a login interception flag for the target account, the method further includes: Determine the target violation type for the target account and set a target violation type identifier for the target account; Sending the violation handling protocol to the client includes: Obtain the violation handling protocol that matches the target violation type identifier, wherein different violation types correspond to different violation handling protocols; The obtained violation handling protocol is sent to the client.

4. The method according to claim 3, characterized in that, After removing the login blocking status of the target account, the method further includes: Update the historical violation records corresponding to the target account in the historical violation database. The historical violation records shall at least include the violation type of the historical violation and the agreement signing record. The step of obtaining the violation processing protocol that matches the target violation type identifier includes: Obtain the number of violations corresponding to the target violation type from the historical violation records corresponding to the target account; Obtain the violation handling protocol that matches the target violation type identifier and the number of violations.

5. The method according to claim 4, characterized in that, The historical violation records also include data on historical violations; Before obtaining the violation handling protocol that matches the target violation type identifier and the number of violations, the method further includes: Obtain historical violation data corresponding to the target violation type from the historical violation records corresponding to the target account; Determine the similarity of violations between the historical violation data and the current violation data; If the similarity of the violation is lower than the similarity threshold, then the step of obtaining the violation processing protocol that matches the target violation type identifier and the number of violations is executed; If the similarity of the violation is higher than the similarity threshold, then the violation processing protocol that matches the target violation type identifier and the weighted violation count is obtained, wherein the weighted violation count is greater than the number of violations.

6. The method according to any one of claims 1 to 5, characterized in that, Before sending a violation notification to the client in response to the client's account login request, the method further includes: Obtain the account status of the target account; In response to the target account being logged in, an offline notification is sent to the client. The offline notification is used to inform the target account of any violations, and the client is used to log out of the login state according to the offline notification.

7. The method according to claim 6, characterized in that, The method further includes: If the signing notification is not received within a predetermined time after the offline notification is sent, a pending flag is set for the target account. The pending flag is used to indicate that the target account is a pending malicious violation account. The malicious violation account is an account controlled by a robot. The predetermined time is determined based on the historical signing time of different accounts for violation handling agreements. In response to the target account committing another violation, and the target account having the pending flag set, a violation handling protocol containing interference options is generated; Send a violation handling protocol containing the interference options to the client; In response to a signing error notification sent by the client, a malicious identifier is set for the target account. The signing error notification is sent by the client when it receives a selection operation for the interference option. The malicious identifier is used to characterize the target account as a malicious and non-compliant account.

8. A method for handling accounts that violate regulations, characterized in that, The method includes: In response to an account login operation on the account login interface, a violation notification message is displayed. The violation notification message is used to indicate that the currently logged-in target account has committed a violation and that the target account is in a login blocking state. In response to the triggering operation of the violation prompt information, a violation handling interface is displayed, which contains a violation handling agreement to be signed; In response to the signing of the violation handling agreement, the user interface after the target account logs in is displayed, wherein the login blocking status of the target account is lifted after the violation handling agreement is signed.

9. The method according to claim 8, characterized in that, The step of displaying the user interface after the target account logs in, in response to the signing of the violation handling agreement, includes: In response to the signing operation of the violation handling agreement, a signing notification is sent to the server, the signing notification being used to instruct the server to lift the login blocking status of the target account; In response to receiving the status cancellation instruction sent by the server, an account login request is sent to the server, and the user interface after the target account is logged in is displayed.

10. The method according to claim 8 or 9, characterized in that, Before displaying the violation notification information in response to an account login operation on the account login interface, the method further includes: In response to the target account being logged in, an offline notification is displayed, and the user exits the login state. The offline notification is sent by the server.

11. A device for processing accounts that violate regulations, characterized in that, The device includes: The first sending module is used to respond to the client's account login request and send a violation notification message to the client. The violation notification message is used to indicate that the target account currently logged in by the client has violated regulations and that the target account is in a login blocking state. The second sending module is used to send a violation handling protocol to the client. The client is used to display the violation handling protocol in the violation handling interface. The violation handling interface is displayed by the client when it receives a trigger operation for the violation prompt information. The removal module is used to remove the login blocking status of the target account in response to the signing notification sent by the client. The signing notification is sent by the client when it receives the signing operation of the violation handling agreement, and the target account whose login blocking status has been removed is allowed to log in.

12. A device for processing accounts that violate regulations, characterized in that, The device includes: The first display module is used to respond to the account login operation in the account login interface and display violation prompt information, which is used to indicate that the currently logged-in target account has violated regulations; The second display module is used to display a violation handling interface in response to the triggering operation of the violation prompt information. The violation handling interface contains a violation handling agreement to be signed. The login module is used to display the user interface of the target account after login in response to the signing operation of the violation handling agreement.

13. A server, characterized in that, The server includes a processor and a memory, the memory storing at least one piece of program code, which is loaded and executed by the processor to implement the method for handling violating accounts as described in any one of claims 1 to 7.

14. A terminal, characterized in that, The terminal includes a processor and a memory, the memory storing at least one piece of program code, which is loaded and executed by the processor to implement the method for handling violating accounts as described in any one of claims 8 to 10.

15. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores at least one piece of program code, which is loaded and executed by a processor to implement the method for handling violating accounts as described in any one of claims 1 to 7, or to implement the method for handling violating accounts as described in any one of claims 8 to 10.

Images